From sip-admin@ietf.org Tue Oct 1 05:06:02 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02903 for ; Tue, 1 Oct 2002 05:06:02 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9197Tv06786 for ; Tue, 1 Oct 2002 05:07:29 -0400 Date: Tue, 01 Oct 2002 05:07:29 -0400 Message-ID: <20021001090729.2977.1890.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder To: manet-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: sip-admin@ietf.org Errors-To: sip-admin@ietf.org X-BeenThere: sip@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, manet-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@. Thanks! Passwords for manet-archive@lists.ietf.org: List Password // URL ---- -------- manet@ietf.org FtOz https://www1.ietf.org/mailman/options/manet/manet-archive%40lists.ietf.org From manet-admin@ietf.org Tue Oct 1 05:53:09 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04929 for ; Tue, 1 Oct 2002 05:53:09 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g919ogv21986; Tue, 1 Oct 2002 05:50:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g919dJv18275 for ; Tue, 1 Oct 2002 05:39:19 -0400 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04191 for ; Tue, 1 Oct 2002 05:37:21 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id g919dBq26091; Tue, 1 Oct 2002 11:39:11 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g919dAQ08059; Tue, 1 Oct 2002 11:39:10 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g919dAIu021171; Tue, 1 Oct 2002 11:39:10 +0200 (MET DST) Message-ID: <3D996E55.828D3C4A@mchp.siemens.de> Date: Tue, 01 Oct 2002 11:43:49 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Question about traces (r,s,f,d)?? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, the first column of the trace files (new traces) of the AODV simulation just confused me a little bit. s: is written once when the source sends a packet d: when a packet is dropped by some node (this line is also found only one time in the trace file when a packet is dropped) r: when a packet arrives at the destination f: when a packet is forwarded by some node. so let's assume node 1 tries to send a packet to node 3 through node 2. Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first receives ("r") the packet then forward it ("f")???? Normally we would get: Total of sent cbr packets = total of dropped cbr packets + total of received cbr packets. But while analysing my trace files i get: Total of sent cbr packets < total of dropped cbr packets + total of received cbr packets. Although the difference is not that big, i would know how it exists??? Total of sent cbr packets: Lines with s at the beginning and cbr as packet type total of dropped cbr packets: Lines with d at the beginning and cbr as packet type total of received cbr packets:Lines with r at the beginning and cbr as packet type Thanks a lot for any help or comment. Riadh _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 1 06:21:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06026 for ; Tue, 1 Oct 2002 06:21:53 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g91ANLb29522 for manet-archive@odin.ietf.org; Tue, 1 Oct 2002 06:23:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91ANKv29519 for ; Tue, 1 Oct 2002 06:23:20 -0400 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06016 for ; Tue, 1 Oct 2002 06:21:22 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g919ogv21986; Tue, 1 Oct 2002 05:50:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g919dJv18275 for ; Tue, 1 Oct 2002 05:39:19 -0400 Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04191 for ; Tue, 1 Oct 2002 05:37:21 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id g919dBq26091; Tue, 1 Oct 2002 11:39:11 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g919dAQ08059; Tue, 1 Oct 2002 11:39:10 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g919dAIu021171; Tue, 1 Oct 2002 11:39:10 +0200 (MET DST) Message-ID: <3D996E55.828D3C4A@mchp.siemens.de> Date: Tue, 01 Oct 2002 11:43:49 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Question about traces (r,s,f,d)?? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, the first column of the trace files (new traces) of the AODV simulation just confused me a little bit. s: is written once when the source sends a packet d: when a packet is dropped by some node (this line is also found only one time in the trace file when a packet is dropped) r: when a packet arrives at the destination f: when a packet is forwarded by some node. so let's assume node 1 tries to send a packet to node 3 through node 2. Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first receives ("r") the packet then forward it ("f")???? Normally we would get: Total of sent cbr packets = total of dropped cbr packets + total of received cbr packets. But while analysing my trace files i get: Total of sent cbr packets < total of dropped cbr packets + total of received cbr packets. Although the difference is not that big, i would know how it exists??? Total of sent cbr packets: Lines with s at the beginning and cbr as packet type total of dropped cbr packets: Lines with d at the beginning and cbr as packet type total of received cbr packets:Lines with r at the beginning and cbr as packet type Thanks a lot for any help or comment. Riadh _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 1 06:53:35 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07326 for ; Tue, 1 Oct 2002 06:53:35 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g91At3i06810 for manet-archive@odin.ietf.org; Tue, 1 Oct 2002 06:55:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91At3v06807 for ; Tue, 1 Oct 2002 06:55:03 -0400 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07280 for ; Tue, 1 Oct 2002 06:53:04 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91Apiv05369; Tue, 1 Oct 2002 06:51:44 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91AjOv03786 for ; Tue, 1 Oct 2002 06:45:24 -0400 Received: from lkn.e-technik.tu-muenchen.de (root@aperol.LKN.E-Technik.TU-Muenchen.DE [129.187.222.163]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06939 for ; Tue, 1 Oct 2002 06:43:21 -0400 (EDT) Received: from ei.tum.de (grasshopper [10.152.4.54]) by lkn.e-technik.tu-muenchen.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id g91AjDD21634 for ; Tue, 1 Oct 2002 12:45:13 +0200 Message-ID: <3D997FC0.276C8D91@ei.tum.de> Date: Tue, 01 Oct 2002 12:58:08 +0200 From: Christian Bettstetter Organization: http://www.lkn.ei.tum.de X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.16-4GB i686) X-Accept-Language: en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] CfP MoMuC2003 - Munich, Germany Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit ******************************************* CfP MoMuC 2003 - Munich, Germany http://www.cdtm.de/momuc/Download/CfP.pdf ******************************************* --- Please give this message to interested persons Our apologies for cross-postings Announcement and Call for Papers / Submissions Mobile Multimedia Communications Conference (MoMuC) 2003 The First Interdisciplinary International Conference on Mobile Business and Technology "Opening Up New Frontiers in Mobile Business and Technology" 6-8 October 2003, Munich, Germany refer to http://www.momuc.org or http://www.cdtm.de/momuc ---Extended abstracts of proposals can be submitted until February 28th 2003--- MoMuC 2003 is the eights in a series of international workshops - Tokyo in 1994, Bristol in 1995, Princeton in 1996, Seoul in 1997, Berlin in 1998, San Diego in 1999 and Tokyo in 2000 - aimed at stimulating knowledge exchanges in the emerging and strategically important field of Mobile Multimedia Communications. 3G, Wireless LAN and systems and technologies "beyond 3G" have been launched or are under development. For the first time in this series the business viewpoint of mobile technologies will be integrated to complement technological issues. During the last years it has become increasingly obvious that the technological push of new wireless technologies will not result in successful products if the opportunities are not carefully evaluated in particular from the customer point of view. MoMuc 2003's goal is to bring together researchers, practitioners and potential users involved in and affected by emerging wireless technologies. The workshop targets at experts in multimedia systems and mobility issues on the technological and business side. The impact of the workshop is to provide an effective forum for original and fundamental advances in Mobile Multimedia Systems and business models and to foster communication among researchers and practitioners working in a wide variety of scientific areas with a common interest in mobile multimedia communication. Also we wish to provide a timely forum for exploratory research contributions, and to promote cross-disciplinary interactions in an informal setting. -----------------Details on ways for participating----------------- --Topics-- Topics of the conference are either business-, technology- or interdiciplinary in their nature and relate to mobile technologies. Exemplarily please see the following overview of topics below. For more details please refer to the pdf Document or consult www.momuc.org: -Business models and strategic options -Market and consumer perspective -Political and societal framework -Mobile services, applications and content -Development process of mobile services -Mobile Multimedia Systems -Wireless networks for personal communication -Network management and services -Mobile terminal hardware and software --Dates and Deadlines-- Nov. 01, 2002 First date for submission of extended abstracts Feb. 28, 2003 Deadline for submission of extended abstracts for - Papers - Posters/ Demonstrations May 15, 2003 Notification of acceptance July 15, 2003 Deadline for submission of final version of accepted papers (to be published in the conference proceedings) --Proposals for participation may include-- .. papers, .. posters, incl. software and demonstrations The official conference language is English. --Information on the types of presentation-- Papers: The time for the presentation of a paper will be 20 minutes including time for discussion. Poster/Demonstration: Poster presentations are less formal and more interactive than a standard talk and will be presented in special sessions. Each presenter is provided with about 2 square meters of board space. Demonstrations will be presented in special sessions and can take a variety of forms, which should be indicated with submission of the abstract. Abstracts for posters and demonstrations can be submitted after Feb. 28 and will be included in the program as long as there is enough space available but these posters/ demonstrations will not be included in the conference proceedings book. --Abstract Submission-- The extended abstract should include the following information on a cover sheet: .. Title of the paper. .. Complete information regarding the (presenting) author, affiliation, address, phone, fax, e-mail. .. Indicate corresponding author (first author assumed unless otherwise noted). .. Indicate preferred topic areas. .. Indicate what kind of paper is submitted: Technical, business or interdisciplinary .. For demonstrations, please submit detailed requests for demonstration facilities needed. All papers will be subject to international peer review and will be evaluated for content and merit, innovative contribution, clarity, and relevance to the symposium's theme. --Abstract length (excl. pictures and diagrams)-- Paper Presentation: 1000-1500 words Poster/ Demonstrations: 500 words You can submit an abstract by sending it by e-mail to mailto:proposals@momuc.org in Microsoft Word or pdf - format. If you wish to submit more than one abstract, please submit each abstract separately. --Conference Proceedings-- The Conference Proceedings with full papers will be published at the Conference as a book and CD. Regarding Posters and Demonstrations, the abstracts will be published. For questions please contact mailto:info@momuc.org MoMuC 2003 Secretary c/o Center for Digital Technology and Management Arcisstr. 21, Room 1734 80290 Munchen Tel.: +49 (0) 89 289 28163 Fax: +49 (0) 89 289 28459 Email: mailto:info@momuc.org www.momuc.org _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 1 06:53:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07341 for ; Tue, 1 Oct 2002 06:53:38 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91Apiv05369; Tue, 1 Oct 2002 06:51:44 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91AjOv03786 for ; Tue, 1 Oct 2002 06:45:24 -0400 Received: from lkn.e-technik.tu-muenchen.de (root@aperol.LKN.E-Technik.TU-Muenchen.DE [129.187.222.163]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06939 for ; Tue, 1 Oct 2002 06:43:21 -0400 (EDT) Received: from ei.tum.de (grasshopper [10.152.4.54]) by lkn.e-technik.tu-muenchen.de (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) with ESMTP id g91AjDD21634 for ; Tue, 1 Oct 2002 12:45:13 +0200 Message-ID: <3D997FC0.276C8D91@ei.tum.de> Date: Tue, 01 Oct 2002 12:58:08 +0200 From: Christian Bettstetter Organization: http://www.lkn.ei.tum.de X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.16-4GB i686) X-Accept-Language: en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] CfP MoMuC2003 - Munich, Germany Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit ******************************************* CfP MoMuC 2003 - Munich, Germany http://www.cdtm.de/momuc/Download/CfP.pdf ******************************************* --- Please give this message to interested persons Our apologies for cross-postings Announcement and Call for Papers / Submissions Mobile Multimedia Communications Conference (MoMuC) 2003 The First Interdisciplinary International Conference on Mobile Business and Technology "Opening Up New Frontiers in Mobile Business and Technology" 6-8 October 2003, Munich, Germany refer to http://www.momuc.org or http://www.cdtm.de/momuc ---Extended abstracts of proposals can be submitted until February 28th 2003--- MoMuC 2003 is the eights in a series of international workshops - Tokyo in 1994, Bristol in 1995, Princeton in 1996, Seoul in 1997, Berlin in 1998, San Diego in 1999 and Tokyo in 2000 - aimed at stimulating knowledge exchanges in the emerging and strategically important field of Mobile Multimedia Communications. 3G, Wireless LAN and systems and technologies "beyond 3G" have been launched or are under development. For the first time in this series the business viewpoint of mobile technologies will be integrated to complement technological issues. During the last years it has become increasingly obvious that the technological push of new wireless technologies will not result in successful products if the opportunities are not carefully evaluated in particular from the customer point of view. MoMuc 2003's goal is to bring together researchers, practitioners and potential users involved in and affected by emerging wireless technologies. The workshop targets at experts in multimedia systems and mobility issues on the technological and business side. The impact of the workshop is to provide an effective forum for original and fundamental advances in Mobile Multimedia Systems and business models and to foster communication among researchers and practitioners working in a wide variety of scientific areas with a common interest in mobile multimedia communication. Also we wish to provide a timely forum for exploratory research contributions, and to promote cross-disciplinary interactions in an informal setting. -----------------Details on ways for participating----------------- --Topics-- Topics of the conference are either business-, technology- or interdiciplinary in their nature and relate to mobile technologies. Exemplarily please see the following overview of topics below. For more details please refer to the pdf Document or consult www.momuc.org: -Business models and strategic options -Market and consumer perspective -Political and societal framework -Mobile services, applications and content -Development process of mobile services -Mobile Multimedia Systems -Wireless networks for personal communication -Network management and services -Mobile terminal hardware and software --Dates and Deadlines-- Nov. 01, 2002 First date for submission of extended abstracts Feb. 28, 2003 Deadline for submission of extended abstracts for - Papers - Posters/ Demonstrations May 15, 2003 Notification of acceptance July 15, 2003 Deadline for submission of final version of accepted papers (to be published in the conference proceedings) --Proposals for participation may include-- .. papers, .. posters, incl. software and demonstrations The official conference language is English. --Information on the types of presentation-- Papers: The time for the presentation of a paper will be 20 minutes including time for discussion. Poster/Demonstration: Poster presentations are less formal and more interactive than a standard talk and will be presented in special sessions. Each presenter is provided with about 2 square meters of board space. Demonstrations will be presented in special sessions and can take a variety of forms, which should be indicated with submission of the abstract. Abstracts for posters and demonstrations can be submitted after Feb. 28 and will be included in the program as long as there is enough space available but these posters/ demonstrations will not be included in the conference proceedings book. --Abstract Submission-- The extended abstract should include the following information on a cover sheet: .. Title of the paper. .. Complete information regarding the (presenting) author, affiliation, address, phone, fax, e-mail. .. Indicate corresponding author (first author assumed unless otherwise noted). .. Indicate preferred topic areas. .. Indicate what kind of paper is submitted: Technical, business or interdisciplinary .. For demonstrations, please submit detailed requests for demonstration facilities needed. All papers will be subject to international peer review and will be evaluated for content and merit, innovative contribution, clarity, and relevance to the symposium's theme. --Abstract length (excl. pictures and diagrams)-- Paper Presentation: 1000-1500 words Poster/ Demonstrations: 500 words You can submit an abstract by sending it by e-mail to mailto:proposals@momuc.org in Microsoft Word or pdf - format. If you wish to submit more than one abstract, please submit each abstract separately. --Conference Proceedings-- The Conference Proceedings with full papers will be published at the Conference as a book and CD. Regarding Posters and Demonstrations, the abstracts will be published. For questions please contact mailto:info@momuc.org MoMuC 2003 Secretary c/o Center for Digital Technology and Management Arcisstr. 21, Room 1734 80290 Munchen Tel.: +49 (0) 89 289 28163 Fax: +49 (0) 89 289 28459 Email: mailto:info@momuc.org www.momuc.org _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 1 12:02:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23978 for ; Tue, 1 Oct 2002 12:02:25 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g91G3u612470 for manet-archive@odin.ietf.org; Tue, 1 Oct 2002 12:03:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91G3uv12467 for ; Tue, 1 Oct 2002 12:03:56 -0400 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23936 for ; Tue, 1 Oct 2002 12:01:55 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91G0hv12011; Tue, 1 Oct 2002 12:00:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91Fwuv11918 for ; Tue, 1 Oct 2002 11:58:56 -0400 Received: from barrichello.cs.ucr.edu (barrichello.cs.ucr.edu [138.23.169.5]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23663 for ; Tue, 1 Oct 2002 11:56:55 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id 06B4CAB59948; Tue, 1 Oct 2002 08:58:41 -0700 (PDT) Mailbox-Line: From zye@cs.ucr.edu Tue Oct 1 08:58:23 2002 Received: from io.cs.ucr.edu (io.cs.ucr.edu [138.23.174.180]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id 57911AB5991A; Tue, 1 Oct 2002 08:58:22 -0700 (PDT) Received: by io.cs.ucr.edu (Postfix, from userid 7296) id 05F0725B5C; Tue, 1 Oct 2002 08:58:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by io.cs.ucr.edu (Postfix) with ESMTP id F2461258B6; Tue, 1 Oct 2002 08:58:21 -0700 (PDT) Date: Tue, 1 Oct 2002 08:58:21 -0700 (PDT) From: "Zhenqiang(Frank) Ye" To: Riadh Marrakchi Cc: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Subject: Re: [manet] Question about traces (r,s,f,d)?? In-Reply-To: <3D996E55.828D3C4A@mchp.siemens.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-1.9 required=5.0 tests=IN_REP_TO,SUBJ_ENDS_IN_Q_MARK,DOUBLE_CAPSWORD, SIGNATURE_DELIM version=2.31 X-Virus-Scanned: by AMaViS perl-11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , You can not use the method you described. See the example below: (The transport and IP layer trace are ON) s 2.199994566 _1_ AGT --- 6 cbr .... r 2.199994566 _1_ RTR --- 6 cbr .... s 2.199994566 _1_ RTR --- 6 cbr .... r 2.200547959 _2_ RTR --- 6 cbr .... f 2.200547959 _2_ RTR --- 6 cbr .... r 2.201817971 _3_ AGT --- 6 cbr .... The packet 6 is marked "cbr" all the time. It is sent by node 1 two times (at different layers), and is received 3 times (by different nodes and different layers). That is why your method does not work. In order to compute correctly, you need to add "AGT" in your filter when you cout the number of packets "sent" and "received". Hope it helps, Zhenqiang(Frank) On Tue, 1 Oct 2002, Riadh Marrakchi wrote: > Hi, > the first column of the trace files (new traces) of the AODV simulation > just confused me a little bit. > s: is written once when the source sends a packet > d: when a packet is dropped by some node (this line is also found only > one time in the trace file when a packet is dropped) > r: when a packet arrives at the destination > f: when a packet is forwarded by some node. > so let's assume node 1 tries to send a packet to node 3 through node 2. > Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it > and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first > receives ("r") the packet then forward it ("f")???? > Normally we would get: Total of sent cbr packets = total of dropped cbr > packets + total of received cbr packets. But while analysing my trace > files i get: Total of sent cbr packets < total of dropped cbr packets + > total of received cbr packets. Although the difference is not that big, > i would know how it exists??? > Total of sent cbr packets: Lines with s at the beginning and cbr as > packet type > total of dropped cbr packets: Lines with d at the beginning and cbr as > packet type > total of received cbr packets:Lines with r at the beginning and cbr as > packet type > > Thanks a lot for any help or comment. > Riadh > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -- **************************************** Zhenqiang(Frank) Ye Ph.D Student Department of Electrical Engineering University of California, Riverside Phone: (909)-787-2434 email: zye@cs.ucr.edu **************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 1 12:02:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23999 for ; Tue, 1 Oct 2002 12:02:30 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91G0hv12011; Tue, 1 Oct 2002 12:00:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91Fwuv11918 for ; Tue, 1 Oct 2002 11:58:56 -0400 Received: from barrichello.cs.ucr.edu (barrichello.cs.ucr.edu [138.23.169.5]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23663 for ; Tue, 1 Oct 2002 11:56:55 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id 06B4CAB59948; Tue, 1 Oct 2002 08:58:41 -0700 (PDT) Mailbox-Line: From zye@cs.ucr.edu Tue Oct 1 08:58:23 2002 Received: from io.cs.ucr.edu (io.cs.ucr.edu [138.23.174.180]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id 57911AB5991A; Tue, 1 Oct 2002 08:58:22 -0700 (PDT) Received: by io.cs.ucr.edu (Postfix, from userid 7296) id 05F0725B5C; Tue, 1 Oct 2002 08:58:21 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by io.cs.ucr.edu (Postfix) with ESMTP id F2461258B6; Tue, 1 Oct 2002 08:58:21 -0700 (PDT) Date: Tue, 1 Oct 2002 08:58:21 -0700 (PDT) From: "Zhenqiang(Frank) Ye" To: Riadh Marrakchi Cc: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Subject: Re: [manet] Question about traces (r,s,f,d)?? In-Reply-To: <3D996E55.828D3C4A@mchp.siemens.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-1.9 required=5.0 tests=IN_REP_TO,SUBJ_ENDS_IN_Q_MARK,DOUBLE_CAPSWORD, SIGNATURE_DELIM version=2.31 X-Virus-Scanned: by AMaViS perl-11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , You can not use the method you described. See the example below: (The transport and IP layer trace are ON) s 2.199994566 _1_ AGT --- 6 cbr .... r 2.199994566 _1_ RTR --- 6 cbr .... s 2.199994566 _1_ RTR --- 6 cbr .... r 2.200547959 _2_ RTR --- 6 cbr .... f 2.200547959 _2_ RTR --- 6 cbr .... r 2.201817971 _3_ AGT --- 6 cbr .... The packet 6 is marked "cbr" all the time. It is sent by node 1 two times (at different layers), and is received 3 times (by different nodes and different layers). That is why your method does not work. In order to compute correctly, you need to add "AGT" in your filter when you cout the number of packets "sent" and "received". Hope it helps, Zhenqiang(Frank) On Tue, 1 Oct 2002, Riadh Marrakchi wrote: > Hi, > the first column of the trace files (new traces) of the AODV simulation > just confused me a little bit. > s: is written once when the source sends a packet > d: when a packet is dropped by some node (this line is also found only > one time in the trace file when a packet is dropped) > r: when a packet arrives at the destination > f: when a packet is forwarded by some node. > so let's assume node 1 tries to send a packet to node 3 through node 2. > Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it > and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first > receives ("r") the packet then forward it ("f")???? > Normally we would get: Total of sent cbr packets = total of dropped cbr > packets + total of received cbr packets. But while analysing my trace > files i get: Total of sent cbr packets < total of dropped cbr packets + > total of received cbr packets. Although the difference is not that big, > i would know how it exists??? > Total of sent cbr packets: Lines with s at the beginning and cbr as > packet type > total of dropped cbr packets: Lines with d at the beginning and cbr as > packet type > total of received cbr packets:Lines with r at the beginning and cbr as > packet type > > Thanks a lot for any help or comment. > Riadh > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -- **************************************** Zhenqiang(Frank) Ye Ph.D Student Department of Electrical Engineering University of California, Riverside Phone: (909)-787-2434 email: zye@cs.ucr.edu **************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 1 23:03:28 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13594 for ; Tue, 1 Oct 2002 23:03:28 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92354113659 for manet-archive@odin.ietf.org; Tue, 1 Oct 2002 23:05:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92353v13656 for ; Tue, 1 Oct 2002 23:05:03 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13579 for ; Tue, 1 Oct 2002 23:02:57 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g922udv13342; Tue, 1 Oct 2002 22:56:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g922r3v13244 for ; Tue, 1 Oct 2002 22:53:03 -0400 Received: from mbox1.ntu.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13379 for ; Tue, 1 Oct 2002 22:50:56 -0400 (EDT) Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Wed, 2 Oct 2002 10:52:51 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Date: Wed, 2 Oct 2002 10:52:51 +0800 Message-ID: <295CB338B611594582D82D9F26AEF7062CBEBE@mail02.student.main.ntu.edu.sg> Thread-Topic: signal to noise ratio(SNR) and GPS info.. Thread-Index: AcJpaSs/k9r4Eml1S4qNdkoo174BKgAVXYst From: "#GUPTA ROHIT#" To: X-OriginalArrivalTime: 02 Oct 2002 02:52:51.0684 (UTC) FILETIME=[CC956240:01C269BE] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id g922r3v13245 Subject: [manet] signal to noise ratio(SNR) and GPS info.. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Dear all, can anyone let me know on the work done on SNR and GPS to improve AODV. rgds rohit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 1 23:03:31 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13609 for ; Tue, 1 Oct 2002 23:03:31 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g922udv13342; Tue, 1 Oct 2002 22:56:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g922r3v13244 for ; Tue, 1 Oct 2002 22:53:03 -0400 Received: from mbox1.ntu.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13379 for ; Tue, 1 Oct 2002 22:50:56 -0400 (EDT) Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Wed, 2 Oct 2002 10:52:51 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Date: Wed, 2 Oct 2002 10:52:51 +0800 Message-ID: <295CB338B611594582D82D9F26AEF7062CBEBE@mail02.student.main.ntu.edu.sg> Thread-Topic: signal to noise ratio(SNR) and GPS info.. Thread-Index: AcJpaSs/k9r4Eml1S4qNdkoo174BKgAVXYst From: "#GUPTA ROHIT#" To: X-OriginalArrivalTime: 02 Oct 2002 02:52:51.0684 (UTC) FILETIME=[CC956240:01C269BE] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id g922r3v13245 Subject: [manet] signal to noise ratio(SNR) and GPS info.. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Dear all, can anyone let me know on the work done on SNR and GPS to improve AODV. rgds rohit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 03:50:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11872 for ; Wed, 2 Oct 2002 03:50:36 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g927hBv04121; Wed, 2 Oct 2002 03:43:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g927eOv03992 for ; Wed, 2 Oct 2002 03:40:24 -0400 Received: from thoth.sbs.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11702 for ; Wed, 2 Oct 2002 03:38:10 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g927e2B21410; Wed, 2 Oct 2002 09:40:03 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g927e1Q14807; Wed, 2 Oct 2002 09:40:01 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g927e1Iu004403; Wed, 2 Oct 2002 09:40:01 +0200 (MET DST) Message-ID: <3D9AA3F3.B08B98E0@mchp.siemens.de> Date: Wed, 02 Oct 2002 09:44:51 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Zhenqiang(Frank) Ye" CC: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Subject: Re: [manet] Question about traces (r,s,f,d)?? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, the RTR Traces are set off in my simulation scripts, so that i get only the AGT traces. "Zhenqiang(Frank) Ye" wrote: > You can not use the method you described. See the example below: > (The transport and IP layer trace are ON) > s 2.199994566 _1_ AGT --- 6 cbr .... > r 2.199994566 _1_ RTR --- 6 cbr .... > s 2.199994566 _1_ RTR --- 6 cbr .... > r 2.200547959 _2_ RTR --- 6 cbr .... > f 2.200547959 _2_ RTR --- 6 cbr .... > r 2.201817971 _3_ AGT --- 6 cbr .... > > The packet 6 is marked "cbr" all the time. It is sent by node 1 two > times (at different layers), and is received 3 times (by different nodes > and different layers). That is why your method does not work. In order > to compute correctly, you need to add "AGT" in your filter when you cout > the number of packets "sent" and "received". > > Hope it helps, > > Zhenqiang(Frank) > > On Tue, 1 Oct 2002, Riadh Marrakchi wrote: > > > Hi, > > the first column of the trace files (new traces) of the AODV simulation > > just confused me a little bit. > > s: is written once when the source sends a packet > > d: when a packet is dropped by some node (this line is also found only > > one time in the trace file when a packet is dropped) > > r: when a packet arrives at the destination > > f: when a packet is forwarded by some node. > > so let's assume node 1 tries to send a packet to node 3 through node 2. > > Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it > > and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first > > receives ("r") the packet then forward it ("f")???? > > Normally we would get: Total of sent cbr packets = total of dropped cbr > > packets + total of received cbr packets. But while analysing my trace > > files i get: Total of sent cbr packets < total of dropped cbr packets + > > total of received cbr packets. Although the difference is not that big, > > i would know how it exists??? > > Total of sent cbr packets: Lines with s at the beginning and cbr as > > packet type > > total of dropped cbr packets: Lines with d at the beginning and cbr as > > packet type > > total of received cbr packets:Lines with r at the beginning and cbr as > > packet type > > > > Thanks a lot for any help or comment. > > Riadh > > > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > -- > > **************************************** > Zhenqiang(Frank) Ye > Ph.D Student > Department of Electrical Engineering > University of California, Riverside > Phone: (909)-787-2434 > email: zye@cs.ucr.edu > **************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 03:54:45 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11935 for ; Wed, 2 Oct 2002 03:54:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g927uOh04685 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 03:56:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g927uOv04682 for ; Wed, 2 Oct 2002 03:56:24 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11929 for ; Wed, 2 Oct 2002 03:54:13 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g927hBv04121; Wed, 2 Oct 2002 03:43:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g927eOv03992 for ; Wed, 2 Oct 2002 03:40:24 -0400 Received: from thoth.sbs.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11702 for ; Wed, 2 Oct 2002 03:38:10 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g927e2B21410; Wed, 2 Oct 2002 09:40:03 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g927e1Q14807; Wed, 2 Oct 2002 09:40:01 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g927e1Iu004403; Wed, 2 Oct 2002 09:40:01 +0200 (MET DST) Message-ID: <3D9AA3F3.B08B98E0@mchp.siemens.de> Date: Wed, 02 Oct 2002 09:44:51 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Zhenqiang(Frank) Ye" CC: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Subject: Re: [manet] Question about traces (r,s,f,d)?? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, the RTR Traces are set off in my simulation scripts, so that i get only the AGT traces. "Zhenqiang(Frank) Ye" wrote: > You can not use the method you described. See the example below: > (The transport and IP layer trace are ON) > s 2.199994566 _1_ AGT --- 6 cbr .... > r 2.199994566 _1_ RTR --- 6 cbr .... > s 2.199994566 _1_ RTR --- 6 cbr .... > r 2.200547959 _2_ RTR --- 6 cbr .... > f 2.200547959 _2_ RTR --- 6 cbr .... > r 2.201817971 _3_ AGT --- 6 cbr .... > > The packet 6 is marked "cbr" all the time. It is sent by node 1 two > times (at different layers), and is received 3 times (by different nodes > and different layers). That is why your method does not work. In order > to compute correctly, you need to add "AGT" in your filter when you cout > the number of packets "sent" and "received". > > Hope it helps, > > Zhenqiang(Frank) > > On Tue, 1 Oct 2002, Riadh Marrakchi wrote: > > > Hi, > > the first column of the trace files (new traces) of the AODV simulation > > just confused me a little bit. > > s: is written once when the source sends a packet > > d: when a packet is dropped by some node (this line is also found only > > one time in the trace file when a packet is dropped) > > r: when a packet arrives at the destination > > f: when a packet is forwarded by some node. > > so let's assume node 1 tries to send a packet to node 3 through node 2. > > Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it > > and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first > > receives ("r") the packet then forward it ("f")???? > > Normally we would get: Total of sent cbr packets = total of dropped cbr > > packets + total of received cbr packets. But while analysing my trace > > files i get: Total of sent cbr packets < total of dropped cbr packets + > > total of received cbr packets. Although the difference is not that big, > > i would know how it exists??? > > Total of sent cbr packets: Lines with s at the beginning and cbr as > > packet type > > total of dropped cbr packets: Lines with d at the beginning and cbr as > > packet type > > total of received cbr packets:Lines with r at the beginning and cbr as > > packet type > > > > Thanks a lot for any help or comment. > > Riadh > > > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > -- > > **************************************** > Zhenqiang(Frank) Ye > Ph.D Student > Department of Electrical Engineering > University of California, Riverside > Phone: (909)-787-2434 > email: zye@cs.ucr.edu > **************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 10:05:54 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21504 for ; Wed, 2 Oct 2002 10:05:54 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92DwKv24034; Wed, 2 Oct 2002 09:58:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Drtv23870 for ; Wed, 2 Oct 2002 09:53:55 -0400 Received: from smtp2.opnet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20970 for ; Wed, 2 Oct 2002 09:51:27 -0400 (EDT) Received: from wtn11019 (wtn11019.opnet.com) by smtp2.opnet.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Wed, 2 Oct 2002 09:52:48 -0400 Message-Id: <4.2.0.58.20021002095216.00abb9e0@mail.opnet.com> X-Sender: krao@mail.opnet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 02 Oct 2002 09:53:22 -0400 To: manet@ietf.org From: Kartik Rao Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [manet] MANET routing protocol Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , All, Does anyone know what the most common MANET routing protocol used is? Thanks, Kartik ---------- Kartik Rao Senior Modeling Engineer OPNET Technologies krao@opnet.com www.opnet.com ========================================== Register for OPNET's Online Technology Workshops www.opnet.com/TechWorkshops ========================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 10:11:24 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21647 for ; Wed, 2 Oct 2002 10:11:19 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92ECpB25266 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 10:12:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92ECkv25254 for ; Wed, 2 Oct 2002 10:12:46 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21619 for ; Wed, 2 Oct 2002 10:10:28 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92DwKv24034; Wed, 2 Oct 2002 09:58:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Drtv23870 for ; Wed, 2 Oct 2002 09:53:55 -0400 Received: from smtp2.opnet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20970 for ; Wed, 2 Oct 2002 09:51:27 -0400 (EDT) Received: from wtn11019 (wtn11019.opnet.com) by smtp2.opnet.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Wed, 2 Oct 2002 09:52:48 -0400 Message-Id: <4.2.0.58.20021002095216.00abb9e0@mail.opnet.com> X-Sender: krao@mail.opnet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 02 Oct 2002 09:53:22 -0400 To: manet@ietf.org From: Kartik Rao Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [manet] MANET routing protocol Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , All, Does anyone know what the most common MANET routing protocol used is? Thanks, Kartik ---------- Kartik Rao Senior Modeling Engineer OPNET Technologies krao@opnet.com www.opnet.com ========================================== Register for OPNET's Online Technology Workshops www.opnet.com/TechWorkshops ========================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 10:15:55 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21772 for ; Wed, 2 Oct 2002 10:15:55 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92E8Nv25039; Wed, 2 Oct 2002 10:08:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92E7uv24994 for ; Wed, 2 Oct 2002 10:07:56 -0400 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21479 for ; Wed, 2 Oct 2002 10:05:14 -0400 (EDT) Received: from cit.ie (unverified [127.0.0.1]) by cit.ie (Rockliffe SMTPRA 5.2.3) with ESMTP id for ; Wed, 2 Oct 2002 15:05:53 +0100 Message-ID: <410-22002103214553199@cit.ie> X-EM-Version: 6, 0, 1, 3 X-EM-Registration: #00E0620610781F002A20 X-Priority: 3 From: "John Paul O'Grady" To: manet@ietf.org Date: Wed, 2 Oct 2002 15:05:53 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Subject: [manet] ip address allocation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello I have a question in regards to ip address allocation in an ad hoc environment. In an ad hoc environment presumely ip addresses will be allocated dynamically to new nodes as they attach themselves to the network. Is there much research out there into how exactly this will be done. I know in a normal network it can be done through a dhcp server, but in an ad hoc environment you cant really assume a dhcp server will be available. john paul o grady cit ireland -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 10:16:02 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21786 for ; Wed, 2 Oct 2002 10:16:01 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92E97v25077; Wed, 2 Oct 2002 10:09:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92E86v25017 for ; Wed, 2 Oct 2002 10:08:06 -0400 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21498 for ; Wed, 2 Oct 2002 10:05:40 -0400 (EDT) Received: from cit.ie (unverified [127.0.0.1]) by cit.ie (Rockliffe SMTPRA 5.2.3) with ESMTP id for ; Wed, 2 Oct 2002 15:05:59 +0100 Message-ID: <184670-2200210321455974@cit.ie> X-EM-Version: 6, 0, 1, 3 X-EM-Registration: #00E0620610781F002A20 X-Priority: 3 From: "John Paul O'Grady" To: manet@ietf.org Date: Wed, 2 Oct 2002 15:05:59 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Subject: [manet] ip address allocation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello I have a question in regards to ip address allocation in an ad hoc environment. In an ad hoc environment presumely ip addresses will be allocated dynamically to new nodes as they attach themselves to the network. Is there much research out there into how exactly this will be done. I know in a normal network it can be done through a dhcp server, but in an ad hoc environment you cant really assume a dhcp server will be available. john paul o grady cit ireland -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 10:20:50 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22013 for ; Wed, 2 Oct 2002 10:20:50 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92EMNg25910 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 10:22:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92EMMv25907 for ; Wed, 2 Oct 2002 10:22:22 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21972 for ; Wed, 2 Oct 2002 10:20:19 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92E8Nv25039; Wed, 2 Oct 2002 10:08:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92E7uv24994 for ; Wed, 2 Oct 2002 10:07:56 -0400 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21479 for ; Wed, 2 Oct 2002 10:05:14 -0400 (EDT) Received: from cit.ie (unverified [127.0.0.1]) by cit.ie (Rockliffe SMTPRA 5.2.3) with ESMTP id for ; Wed, 2 Oct 2002 15:05:53 +0100 Message-ID: <410-22002103214553199@cit.ie> X-EM-Version: 6, 0, 1, 3 X-EM-Registration: #00E0620610781F002A20 X-Priority: 3 From: "John Paul O'Grady" To: manet@ietf.org Date: Wed, 2 Oct 2002 15:05:53 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Subject: [manet] ip address allocation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello I have a question in regards to ip address allocation in an ad hoc environment. In an ad hoc environment presumely ip addresses will be allocated dynamically to new nodes as they attach themselves to the network. Is there much research out there into how exactly this will be done. I know in a normal network it can be done through a dhcp server, but in an ad hoc environment you cant really assume a dhcp server will be available. john paul o grady cit ireland -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 10:21:14 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22044 for ; Wed, 2 Oct 2002 10:21:14 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92EMlb25937 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 10:22:47 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92EMkv25934 for ; Wed, 2 Oct 2002 10:22:46 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21996 for ; Wed, 2 Oct 2002 10:20:43 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92E97v25077; Wed, 2 Oct 2002 10:09:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92E86v25017 for ; Wed, 2 Oct 2002 10:08:06 -0400 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21498 for ; Wed, 2 Oct 2002 10:05:40 -0400 (EDT) Received: from cit.ie (unverified [127.0.0.1]) by cit.ie (Rockliffe SMTPRA 5.2.3) with ESMTP id for ; Wed, 2 Oct 2002 15:05:59 +0100 Message-ID: <184670-2200210321455974@cit.ie> X-EM-Version: 6, 0, 1, 3 X-EM-Registration: #00E0620610781F002A20 X-Priority: 3 From: "John Paul O'Grady" To: manet@ietf.org Date: Wed, 2 Oct 2002 15:05:59 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Subject: [manet] ip address allocation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello I have a question in regards to ip address allocation in an ad hoc environment. In an ad hoc environment presumely ip addresses will be allocated dynamically to new nodes as they attach themselves to the network. Is there much research out there into how exactly this will be done. I know in a normal network it can be done through a dhcp server, but in an ad hoc environment you cant really assume a dhcp server will be available. john paul o grady cit ireland -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 10:44:10 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22669 for ; Wed, 2 Oct 2002 10:44:10 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92EjgP27500 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 10:45:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Ejgv27497 for ; Wed, 2 Oct 2002 10:45:42 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22658 for ; Wed, 2 Oct 2002 10:43:39 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Eadv26557; Wed, 2 Oct 2002 10:36:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92EZfv26503 for ; Wed, 2 Oct 2002 10:35:41 -0400 Received: from mail.engr.ucsb.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22408 for ; Wed, 2 Oct 2002 10:33:37 -0400 (EDT) Received: from voyageurs.cs.ucsb.edu ([128.111.40.92]:33025 helo=MESA.cs.ucsb.edu ident=idc) by mail.engr.ucsb.edu with esmtp (Exim 4.10) id 17wkb7-0006KJ-00; Wed, 02 Oct 2002 07:35:33 -0700 From: MIME-Version: 1.0 Message-ID: <15771.1078.561000.643924@gargle.gargle.HOWL> Date: Wed, 2 Oct 2002 07:35:34 -0700 To: "#GUPTA ROHIT#" Cc: In-Reply-To: <295CB338B611594582D82D9F26AEF7062CBEBE@mail02.student.main.ntu.edu.sg> References: <295CB338B611594582D82D9F26AEF7062CBEBE@mail02.student.main.ntu.edu.sg> X-Mailer: VM 7.07 under Emacs 21.1.1 Reply-To: idc@engineering.ucsb.edu Content-Type: text/plain; charset=iso-8859-1 Subject: [manet] signal to noise ratio(SNR) and GPS info.. X-Spam-Status: No, hits=-2.9 required=8.0 tests=IN_REP_TO,NO_REAL_NAME version=2.31 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g92EZgv26504 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit The paper Coping with Communication Gray Zones in IEEE 802.11b based Ad hoc Networks Henrik Lundgren, Erik Nordström, Christian Tschudin (Uppsala University, Sweden) Looks at using SNR to improve AODV. Ian Chakeres #GUPTA ROHIT# writes: > > > > Dear all, > can anyone let me know on the work done on SNR and GPS to improve AODV. > > rgds > rohit > > _______________________________________________ > 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-admin@ietf.org Wed Oct 2 10:44:12 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22682 for ; Wed, 2 Oct 2002 10:44:12 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Eadv26557; Wed, 2 Oct 2002 10:36:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92EZfv26503 for ; Wed, 2 Oct 2002 10:35:41 -0400 Received: from mail.engr.ucsb.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22408 for ; Wed, 2 Oct 2002 10:33:37 -0400 (EDT) Received: from voyageurs.cs.ucsb.edu ([128.111.40.92]:33025 helo=MESA.cs.ucsb.edu ident=idc) by mail.engr.ucsb.edu with esmtp (Exim 4.10) id 17wkb7-0006KJ-00; Wed, 02 Oct 2002 07:35:33 -0700 From: MIME-Version: 1.0 Message-ID: <15771.1078.561000.643924@gargle.gargle.HOWL> Date: Wed, 2 Oct 2002 07:35:34 -0700 To: "#GUPTA ROHIT#" Cc: In-Reply-To: <295CB338B611594582D82D9F26AEF7062CBEBE@mail02.student.main.ntu.edu.sg> References: <295CB338B611594582D82D9F26AEF7062CBEBE@mail02.student.main.ntu.edu.sg> X-Mailer: VM 7.07 under Emacs 21.1.1 Reply-To: idc@engineering.ucsb.edu Content-Type: text/plain; charset=iso-8859-1 Subject: [manet] signal to noise ratio(SNR) and GPS info.. X-Spam-Status: No, hits=-2.9 required=8.0 tests=IN_REP_TO,NO_REAL_NAME version=2.31 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g92EZgv26504 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit The paper Coping with Communication Gray Zones in IEEE 802.11b based Ad hoc Networks Henrik Lundgren, Erik Nordström, Christian Tschudin (Uppsala University, Sweden) Looks at using SNR to improve AODV. Ian Chakeres #GUPTA ROHIT# writes: > > > > Dear all, > can anyone let me know on the work done on SNR and GPS to improve AODV. > > rgds > rohit > > _______________________________________________ > 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-admin@ietf.org Wed Oct 2 10:53:48 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23001 for ; Wed, 2 Oct 2002 10:53:48 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92EjBv27477; Wed, 2 Oct 2002 10:45:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Einv27436 for ; Wed, 2 Oct 2002 10:44:49 -0400 Received: from meryl.it.uu.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22636 for ; Wed, 2 Oct 2002 10:42:44 -0400 (EDT) Received: from nebulosa.it.uu.se (nebulosa.it.uu.se [130.238.8.24]) by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id QAA22567; Wed, 2 Oct 2002 16:44:43 +0200 (MET DST) Subject: Re: [manet] signal to noise ratio(SNR) and GPS info.. From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: MANET LIST Cc: #GUPTA ROHIT# In-Reply-To: <15771.1078.561000.643924@gargle.gargle.HOWL> References: <295CB338B611594582D82D9F26AEF7062CBEBE@mail02.student.main.ntu.edu.sg> <15771.1078.561000.643924@gargle.gargle.HOWL> Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1033569883.15090.1.camel@nebulosa.it.uu.se> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.1.1 (Preview Release) Date: 02 Oct 2002 16:44:43 +0200 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Just a note. This paper has been published at WoWMoM 2002. Erik Nordström On Wed, 2002-10-02 at 16:35, idc@engineering.ucsb.edu wrote: > The paper > > Coping with Communication Gray Zones in IEEE 802.11b based Ad hoc Networks > Henrik Lundgren, Erik Nordström, Christian Tschudin (Uppsala > University, Sweden) > > Looks at using SNR to improve AODV. > > Ian Chakeres > > #GUPTA ROHIT# writes: > > > > > > > > Dear all, > > can anyone let me know on the work done on SNR and GPS to improve AODV. > > > > rgds > > rohit > > > > _______________________________________________ > > 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 -- Erik Nordström _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 10:57:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23185 for ; Wed, 2 Oct 2002 10:57:06 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92EwdG28109 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 10:58:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Ewcv28098 for ; Wed, 2 Oct 2002 10:58:38 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23156 for ; Wed, 2 Oct 2002 10:56:34 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92EjBv27477; Wed, 2 Oct 2002 10:45:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Einv27436 for ; Wed, 2 Oct 2002 10:44:49 -0400 Received: from meryl.it.uu.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22636 for ; Wed, 2 Oct 2002 10:42:44 -0400 (EDT) Received: from nebulosa.it.uu.se (nebulosa.it.uu.se [130.238.8.24]) by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id QAA22567; Wed, 2 Oct 2002 16:44:43 +0200 (MET DST) Subject: Re: [manet] signal to noise ratio(SNR) and GPS info.. From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: MANET LIST Cc: #GUPTA ROHIT# In-Reply-To: <15771.1078.561000.643924@gargle.gargle.HOWL> References: <295CB338B611594582D82D9F26AEF7062CBEBE@mail02.student.main.ntu.edu.sg> <15771.1078.561000.643924@gargle.gargle.HOWL> Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1033569883.15090.1.camel@nebulosa.it.uu.se> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.1.1 (Preview Release) Date: 02 Oct 2002 16:44:43 +0200 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Just a note. This paper has been published at WoWMoM 2002. Erik Nordström On Wed, 2002-10-02 at 16:35, idc@engineering.ucsb.edu wrote: > The paper > > Coping with Communication Gray Zones in IEEE 802.11b based Ad hoc Networks > Henrik Lundgren, Erik Nordström, Christian Tschudin (Uppsala > University, Sweden) > > Looks at using SNR to improve AODV. > > Ian Chakeres > > #GUPTA ROHIT# writes: > > > > > > > > Dear all, > > can anyone let me know on the work done on SNR and GPS to improve AODV. > > > > rgds > > rohit > > > > _______________________________________________ > > 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 -- Erik Nordström _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 11:11:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23711 for ; Wed, 2 Oct 2002 11:11:34 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92FD7E29410 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 11:13:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92FD6v29407 for ; Wed, 2 Oct 2002 11:13:06 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23703 for ; Wed, 2 Oct 2002 11:11:03 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92F4Ev28344; Wed, 2 Oct 2002 11:04:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92F2qv28287 for ; Wed, 2 Oct 2002 11:02:52 -0400 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23302 for ; Wed, 2 Oct 2002 11:00:46 -0400 (EDT) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id LAA21424 for ; Wed, 2 Oct 2002 11:02:44 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (NAVGW 2.5.2.12) with SMTP id M2002100211024327747 ; Wed, 02 Oct 2002 11:02:43 -0400 Message-Id: <5.1.1.5.2.20021002104414.0394e1b0@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 02 Oct 2002 11:01:33 -0400 To: "John Paul O'Grady" , manet@ietf.org From: Joe Macker Subject: Re: [manet] route aggregation In-Reply-To: <410-220029426143922919@cit.ie> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 03:39 PM 9/26/2002 +0100, John Paul O'Grady wrote: >Hello > >I have a question in regard to ip addresses. In the fixed internet >there is a thing called classless inter domain routing. Here an ip >address is directly related to the nodes position in relation to the >rest of the network. This allows for route aggregation of routing >updates. > >If this was applied to an ad hoc network, it would probably require >the ip address of an node to change as it moves around which in turn >would result in significant updating of routing tables. > >Is it therefore possible to have route aggregation in an ad hoc >environment? Its done all the time. A typical application is using a manet for a mobile stub network area. The area border router can use aggregation to advertise the mobile area to external networks. I run such a network frequently and even have nodes entering autoconfigure within the aggregated address space. Also, manets should also be able to handle prefix advertisements internally as well for various purposes. -joe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 11:11:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23725 for ; Wed, 2 Oct 2002 11:11:38 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92F4Ev28344; Wed, 2 Oct 2002 11:04:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92F2qv28287 for ; Wed, 2 Oct 2002 11:02:52 -0400 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23302 for ; Wed, 2 Oct 2002 11:00:46 -0400 (EDT) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id LAA21424 for ; Wed, 2 Oct 2002 11:02:44 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (NAVGW 2.5.2.12) with SMTP id M2002100211024327747 ; Wed, 02 Oct 2002 11:02:43 -0400 Message-Id: <5.1.1.5.2.20021002104414.0394e1b0@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 02 Oct 2002 11:01:33 -0400 To: "John Paul O'Grady" , manet@ietf.org From: Joe Macker Subject: Re: [manet] route aggregation In-Reply-To: <410-220029426143922919@cit.ie> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 03:39 PM 9/26/2002 +0100, John Paul O'Grady wrote: >Hello > >I have a question in regard to ip addresses. In the fixed internet >there is a thing called classless inter domain routing. Here an ip >address is directly related to the nodes position in relation to the >rest of the network. This allows for route aggregation of routing >updates. > >If this was applied to an ad hoc network, it would probably require >the ip address of an node to change as it moves around which in turn >would result in significant updating of routing tables. > >Is it therefore possible to have route aggregation in an ad hoc >environment? Its done all the time. A typical application is using a manet for a mobile stub network area. The area border router can use aggregation to advertise the mobile area to external networks. I run such a network frequently and even have nodes entering autoconfigure within the aggregated address space. Also, manets should also be able to handle prefix advertisements internally as well for various purposes. -joe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 11:37:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25034 for ; Wed, 2 Oct 2002 11:37:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92FdNX31418 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 11:39:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92FdNv31415 for ; Wed, 2 Oct 2002 11:39:23 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24990 for ; Wed, 2 Oct 2002 11:37:21 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92FUkv30224; Wed, 2 Oct 2002 11:30:46 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92FTgv30152 for ; Wed, 2 Oct 2002 11:29:42 -0400 Received: from i4mail.informatik.rwth-aachen.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24599 for ; Wed, 2 Oct 2002 11:27:39 -0400 (EDT) Received: from yigit (yigit.informatik.rwth-aachen.de [137.226.12.208]) by i4mail.informatik.rwth-aachen.de (RWTH i4) with ESMTP id A36DE9C101 for ; Wed, 2 Oct 2002 16:35:47 +0200 (CEST) From: "Mesut Günes" To: Subject: AW: [manet] ip address allocation Date: Wed, 2 Oct 2002 17:29:36 +0200 Organization: Lehrstuhl für Informatik 4, RWTH-Aachen Message-ID: <00bd01c26a28$841f11e0$d00ce289@informatik.rwthaachen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <410-22002103214553199@cit.ie> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g92FTgv30153 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, ###I have a question in regards to ip address allocation in an ###ad hoc environment. In an ad hoc environment presumely ip ###addresses will be allocated dynamically to new nodes as they ###attach themselves to the network. ### ###Is there much research out there into how exactly this will be done. ###I know in a normal network it can be done through a dhcp ###server, but in an ad hoc environment you cant really assume ###a dhcp server will be available. We have proposed a distributed dynamic configuration algorithm for mobile multi-hop ad-hoc networks which do not require human interaction. Our aim was to introduce a mechanism which is also able to recognize the splitting and merging of several ad-hoc networks. In our paper we have tried to give an overview about existing dynamic addressing approaches (DHCP, Zero Configuration, Auto-Configuration, ...). Additionally, you'll find a performance comparison of our own approach and DHCP and Auto-Configuration. All results are obtained over ns-2. Paper: ------ Mesut Günes and Jörg Reibel. An ip address configuration algorithm for zeroconf. mobile multi-hop ad-hoc networks. In Proceedings of the International Workshop on Broadband Wireless Ad-Hoc Networks and Services, Sophia Antipolis, France, September 2002. ETSI. The paper is also electronically available via: http://www.projectmesa.org/workshop2002/agenda.htm Regards Mesut Günes PS: Further information aobut our work you'll find via: http://www.adhoc-nets.de _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 11:37:54 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25049 for ; Wed, 2 Oct 2002 11:37:54 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92FUkv30224; Wed, 2 Oct 2002 11:30:46 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92FTgv30152 for ; Wed, 2 Oct 2002 11:29:42 -0400 Received: from i4mail.informatik.rwth-aachen.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24599 for ; Wed, 2 Oct 2002 11:27:39 -0400 (EDT) Received: from yigit (yigit.informatik.rwth-aachen.de [137.226.12.208]) by i4mail.informatik.rwth-aachen.de (RWTH i4) with ESMTP id A36DE9C101 for ; Wed, 2 Oct 2002 16:35:47 +0200 (CEST) From: "Mesut Günes" To: Subject: AW: [manet] ip address allocation Date: Wed, 2 Oct 2002 17:29:36 +0200 Organization: Lehrstuhl für Informatik 4, RWTH-Aachen Message-ID: <00bd01c26a28$841f11e0$d00ce289@informatik.rwthaachen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <410-22002103214553199@cit.ie> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g92FTgv30153 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi, ###I have a question in regards to ip address allocation in an ###ad hoc environment. In an ad hoc environment presumely ip ###addresses will be allocated dynamically to new nodes as they ###attach themselves to the network. ### ###Is there much research out there into how exactly this will be done. ###I know in a normal network it can be done through a dhcp ###server, but in an ad hoc environment you cant really assume ###a dhcp server will be available. We have proposed a distributed dynamic configuration algorithm for mobile multi-hop ad-hoc networks which do not require human interaction. Our aim was to introduce a mechanism which is also able to recognize the splitting and merging of several ad-hoc networks. In our paper we have tried to give an overview about existing dynamic addressing approaches (DHCP, Zero Configuration, Auto-Configuration, ...). Additionally, you'll find a performance comparison of our own approach and DHCP and Auto-Configuration. All results are obtained over ns-2. Paper: ------ Mesut Günes and Jörg Reibel. An ip address configuration algorithm for zeroconf. mobile multi-hop ad-hoc networks. In Proceedings of the International Workshop on Broadband Wireless Ad-Hoc Networks and Services, Sophia Antipolis, France, September 2002. ETSI. The paper is also electronically available via: http://www.projectmesa.org/workshop2002/agenda.htm Regards Mesut Günes PS: Further information aobut our work you'll find via: http://www.adhoc-nets.de _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 11:47:23 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25534 for ; Wed, 2 Oct 2002 11:47:23 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92Fmsw31942 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 11:48:54 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Fmsv31939 for ; Wed, 2 Oct 2002 11:48:54 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25524 for ; Wed, 2 Oct 2002 11:46:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92FeKv31513; Wed, 2 Oct 2002 11:40:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92FdCv31397 for ; Wed, 2 Oct 2002 11:39:12 -0400 Received: from godel.crhc.uiuc.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24976 for ; Wed, 2 Oct 2002 11:37:10 -0400 (EDT) Received: from localhost (nhv@localhost) by godel.crhc.uiuc.edu (8.11.6/8.11.6) with ESMTP id g92Fd3T04507; Wed, 2 Oct 2002 10:39:03 -0500 Date: Wed, 2 Oct 2002 10:39:03 -0500 (CDT) From: Nitin H Vaidya To: "John Paul O'Grady" cc: Subject: Re: [manet] ip address allocation In-Reply-To: <410-22002103214553199@cit.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Wed, 2 Oct 2002, John Paul O'Grady wrote: . >>Hello . >> . >>I have a question in regards to ip address allocation in an ad hoc . >>environment. In an ad hoc environment presumely ip addresses will be . >>allocated dynamically to new nodes as they attach themselves to the . >>network. . >> . >>Is there much research out there into how exactly this will be done. You might find the paper on Weak Duplicate Address Detection from MobiHoc'02 interesting (download from www.crhc.uiuc.edu/~nhv/). - nitin _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 11:47:26 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25548 for ; Wed, 2 Oct 2002 11:47:26 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92FeKv31513; Wed, 2 Oct 2002 11:40:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92FdCv31397 for ; Wed, 2 Oct 2002 11:39:12 -0400 Received: from godel.crhc.uiuc.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24976 for ; Wed, 2 Oct 2002 11:37:10 -0400 (EDT) Received: from localhost (nhv@localhost) by godel.crhc.uiuc.edu (8.11.6/8.11.6) with ESMTP id g92Fd3T04507; Wed, 2 Oct 2002 10:39:03 -0500 Date: Wed, 2 Oct 2002 10:39:03 -0500 (CDT) From: Nitin H Vaidya To: "John Paul O'Grady" cc: Subject: Re: [manet] ip address allocation In-Reply-To: <410-22002103214553199@cit.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Wed, 2 Oct 2002, John Paul O'Grady wrote: . >>Hello . >> . >>I have a question in regards to ip address allocation in an ad hoc . >>environment. In an ad hoc environment presumely ip addresses will be . >>allocated dynamically to new nodes as they attach themselves to the . >>network. . >> . >>Is there much research out there into how exactly this will be done. You might find the paper on Weak Duplicate Address Detection from MobiHoc'02 interesting (download from www.crhc.uiuc.edu/~nhv/). - nitin _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 13:37:29 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29996 for ; Wed, 2 Oct 2002 13:37:28 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92GeHv03224; Wed, 2 Oct 2002 12:40:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Gcjv03133 for ; Wed, 2 Oct 2002 12:38:45 -0400 Received: from meryl.it.uu.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27472 for ; Wed, 2 Oct 2002 12:36:41 -0400 (EDT) Received: from nebulosa.it.uu.se (nebulosa.it.uu.se [130.238.8.24]) by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id SAA25928; Wed, 2 Oct 2002 18:38:38 +0200 (MET DST) Subject: Re: [manet] signal to noise ratio(SNR) and GPS info.. From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: MANET LIST Cc: #GUPTA ROHIT# In-Reply-To: <1033569883.15090.1.camel@nebulosa.it.uu.se> References: <295CB338B611594582D82D9F26AEF7062CBEBE@mail02.student.main.ntu.edu.sg> <15771.1078.561000.643924@gargle.gargle.HOWL> <1033569883.15090.1.camel@nebulosa.it.uu.se> Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1033576717.16571.2.camel@nebulosa.it.uu.se> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.1.1 (Preview Release) Date: 02 Oct 2002 18:38:37 +0200 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit I've put a pdf of the paper mentioned below on the web. http://www.docs.uu.se/scanet/aodv/grayzones.pdf Erik On Wed, 2002-10-02 at 16:44, Erik Nordström wrote: > Just a note. > > This paper has been published at WoWMoM 2002. > > Erik Nordström > > On Wed, 2002-10-02 at 16:35, idc@engineering.ucsb.edu wrote: > > The paper > > > > Coping with Communication Gray Zones in IEEE 802.11b based Ad hoc Networks > > Henrik Lundgren, Erik Nordström, Christian Tschudin (Uppsala > > University, Sweden) > > > > Looks at using SNR to improve AODV. > > > > Ian Chakeres > > > > #GUPTA ROHIT# writes: > > > > > > > > > > > > Dear all, > > > can anyone let me know on the work done on SNR and GPS to improve AODV. > > > > > > rgds > > > rohit > > > > > > _______________________________________________ > > > 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 > -- > Erik Nordström > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- Erik Nordström _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 13:37:31 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00013 for ; Wed, 2 Oct 2002 13:37:30 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92Hd3N07000 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 13:39:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Hcxv06988 for ; Wed, 2 Oct 2002 13:38:59 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29983 for ; Wed, 2 Oct 2002 13:36:55 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92GeHv03224; Wed, 2 Oct 2002 12:40:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Gcjv03133 for ; Wed, 2 Oct 2002 12:38:45 -0400 Received: from meryl.it.uu.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27472 for ; Wed, 2 Oct 2002 12:36:41 -0400 (EDT) Received: from nebulosa.it.uu.se (nebulosa.it.uu.se [130.238.8.24]) by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id SAA25928; Wed, 2 Oct 2002 18:38:38 +0200 (MET DST) Subject: Re: [manet] signal to noise ratio(SNR) and GPS info.. From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: MANET LIST Cc: #GUPTA ROHIT# In-Reply-To: <1033569883.15090.1.camel@nebulosa.it.uu.se> References: <295CB338B611594582D82D9F26AEF7062CBEBE@mail02.student.main.ntu.edu.sg> <15771.1078.561000.643924@gargle.gargle.HOWL> <1033569883.15090.1.camel@nebulosa.it.uu.se> Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1033576717.16571.2.camel@nebulosa.it.uu.se> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.1.1 (Preview Release) Date: 02 Oct 2002 18:38:37 +0200 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit I've put a pdf of the paper mentioned below on the web. http://www.docs.uu.se/scanet/aodv/grayzones.pdf Erik On Wed, 2002-10-02 at 16:44, Erik Nordström wrote: > Just a note. > > This paper has been published at WoWMoM 2002. > > Erik Nordström > > On Wed, 2002-10-02 at 16:35, idc@engineering.ucsb.edu wrote: > > The paper > > > > Coping with Communication Gray Zones in IEEE 802.11b based Ad hoc Networks > > Henrik Lundgren, Erik Nordström, Christian Tschudin (Uppsala > > University, Sweden) > > > > Looks at using SNR to improve AODV. > > > > Ian Chakeres > > > > #GUPTA ROHIT# writes: > > > > > > > > > > > > Dear all, > > > can anyone let me know on the work done on SNR and GPS to improve AODV. > > > > > > rgds > > > rohit > > > > > > _______________________________________________ > > > 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 > -- > Erik Nordström > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- Erik Nordström _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 13:44:31 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00565 for ; Wed, 2 Oct 2002 13:44:31 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92GlJv03618; Wed, 2 Oct 2002 12:47:19 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Gklv03569 for ; Wed, 2 Oct 2002 12:46:47 -0400 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27842 for ; Wed, 2 Oct 2002 12:44:43 -0400 (EDT) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id MAA27849 for ; Wed, 2 Oct 2002 12:46:39 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (NAVGW 2.5.2.12) with SMTP id M2002100212463907761 ; Wed, 02 Oct 2002 12:46:39 -0400 Message-Id: <5.1.1.5.2.20021002110155.03556488@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 02 Oct 2002 12:45:29 -0400 To: "John Paul O'Grady" , manet@ietf.org From: Joe Macker Subject: Re: [manet] ip address allocation In-Reply-To: <410-22002103214553199@cit.ie> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 03:05 PM 10/2/2002 +0100, John Paul O'Grady wrote: >Hello > >I have a question in regards to ip address allocation in an ad hoc >environment. In an ad hoc environment presumely ip addresses will be >allocated dynamically to new nodes as they attach themselves to the >network. > >Is there much research out there into how exactly this will be done. >I know in a normal network it can be done through a dhcp server, but >in an ad hoc environment you cant really assume a dhcp server will be >available. In general, we need more work here on autoconfiguration but there is existing work that is related (duplicate address detection, flooding/broadcast algorithms, multi-hop stateless autoconfiguration, service discovery enhancements)... ...BUT if you just want to get something working quickly, we have demonstrated multi-hop stub network autoconfiguration using manet and dhcprelay for IPv4. The assumption is you care about connectivity to a greater network and that there is a default gateway. Useful for a home network extension,etc. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 13:52:43 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00857 for ; Wed, 2 Oct 2002 13:52:43 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92HsGa07928 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 13:54:16 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92HsFv07925 for ; Wed, 2 Oct 2002 13:54:15 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00831 for ; Wed, 2 Oct 2002 13:52:12 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92GlJv03618; Wed, 2 Oct 2002 12:47:19 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92Gklv03569 for ; Wed, 2 Oct 2002 12:46:47 -0400 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27842 for ; Wed, 2 Oct 2002 12:44:43 -0400 (EDT) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id MAA27849 for ; Wed, 2 Oct 2002 12:46:39 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (NAVGW 2.5.2.12) with SMTP id M2002100212463907761 ; Wed, 02 Oct 2002 12:46:39 -0400 Message-Id: <5.1.1.5.2.20021002110155.03556488@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 02 Oct 2002 12:45:29 -0400 To: "John Paul O'Grady" , manet@ietf.org From: Joe Macker Subject: Re: [manet] ip address allocation In-Reply-To: <410-22002103214553199@cit.ie> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 03:05 PM 10/2/2002 +0100, John Paul O'Grady wrote: >Hello > >I have a question in regards to ip address allocation in an ad hoc >environment. In an ad hoc environment presumely ip addresses will be >allocated dynamically to new nodes as they attach themselves to the >network. > >Is there much research out there into how exactly this will be done. >I know in a normal network it can be done through a dhcp server, but >in an ad hoc environment you cant really assume a dhcp server will be >available. In general, we need more work here on autoconfiguration but there is existing work that is related (duplicate address detection, flooding/broadcast algorithms, multi-hop stateless autoconfiguration, service discovery enhancements)... ...BUT if you just want to get something working quickly, we have demonstrated multi-hop stub network autoconfiguration using manet and dhcprelay for IPv4. The assumption is you care about connectivity to a greater network and that there is a default gateway. Useful for a home network extension,etc. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 14:09:33 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01737 for ; Wed, 2 Oct 2002 14:09:33 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92HCpv05274; Wed, 2 Oct 2002 13:12:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92HBCv05196 for ; Wed, 2 Oct 2002 13:11:12 -0400 Received: from barrichello.cs.ucr.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28757 for ; Wed, 2 Oct 2002 13:09:07 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id 129F3AB59963; Wed, 2 Oct 2002 10:11:06 -0700 (PDT) Mailbox-Line: From zye@cs.ucr.edu Wed Oct 2 10:11:01 2002 Received: from io.cs.ucr.edu (io.cs.ucr.edu [138.23.174.180]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id E9490AB59961; Wed, 2 Oct 2002 10:11:00 -0700 (PDT) Received: by io.cs.ucr.edu (Postfix, from userid 7296) id 2D18D264E7; Wed, 2 Oct 2002 10:11:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by io.cs.ucr.edu (Postfix) with ESMTP id 1E2B62588B; Wed, 2 Oct 2002 10:11:00 -0700 (PDT) Date: Wed, 2 Oct 2002 10:11:00 -0700 (PDT) From: "Zhenqiang(Frank) Ye" To: Riadh Marrakchi Cc: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Subject: Re: [manet] Question about traces (r,s,f,d)?? In-Reply-To: <3D9AA3F3.B08B98E0@mchp.siemens.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-1.9 required=5.0 tests=IN_REP_TO,SUBJ_ENDS_IN_Q_MARK,DOUBLE_CAPSWORD, SIGNATURE_DELIM version=2.31 X-Virus-Scanned: by AMaViS perl-11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , I don't think you can see the packet "DELETE" event in your trace file if you turn off the RTR trace. Frank On Wed, 2 Oct 2002, Riadh Marrakchi wrote: > Hi, > the RTR Traces are set off in my simulation scripts, so that i get only the > AGT traces. > > "Zhenqiang(Frank) Ye" wrote: > > > You can not use the method you described. See the example below: > > (The transport and IP layer trace are ON) > > s 2.199994566 _1_ AGT --- 6 cbr .... > > r 2.199994566 _1_ RTR --- 6 cbr .... > > s 2.199994566 _1_ RTR --- 6 cbr .... > > r 2.200547959 _2_ RTR --- 6 cbr .... > > f 2.200547959 _2_ RTR --- 6 cbr .... > > r 2.201817971 _3_ AGT --- 6 cbr .... > > > > The packet 6 is marked "cbr" all the time. It is sent by node 1 two > > times (at different layers), and is received 3 times (by different nodes > > and different layers). That is why your method does not work. In order > > to compute correctly, you need to add "AGT" in your filter when you cout > > the number of packets "sent" and "received". > > > > Hope it helps, > > > > Zhenqiang(Frank) > > > > On Tue, 1 Oct 2002, Riadh Marrakchi wrote: > > > > > Hi, > > > the first column of the trace files (new traces) of the AODV simulation > > > just confused me a little bit. > > > s: is written once when the source sends a packet > > > d: when a packet is dropped by some node (this line is also found only > > > one time in the trace file when a packet is dropped) > > > r: when a packet arrives at the destination > > > f: when a packet is forwarded by some node. > > > so let's assume node 1 tries to send a packet to node 3 through node 2. > > > Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it > > > and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first > > > receives ("r") the packet then forward it ("f")???? > > > Normally we would get: Total of sent cbr packets = total of dropped cbr > > > packets + total of received cbr packets. But while analysing my trace > > > files i get: Total of sent cbr packets < total of dropped cbr packets + > > > total of received cbr packets. Although the difference is not that big, > > > i would know how it exists??? > > > Total of sent cbr packets: Lines with s at the beginning and cbr as > > > packet type > > > total of dropped cbr packets: Lines with d at the beginning and cbr as > > > packet type > > > total of received cbr packets:Lines with r at the beginning and cbr as > > > packet type > > > > > > Thanks a lot for any help or comment. > > > Riadh > > > > > > > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > -- > > > > **************************************** > > Zhenqiang(Frank) Ye > > Ph.D Student > > Department of Electrical Engineering > > University of California, Riverside > > Phone: (909)-787-2434 > > email: zye@cs.ucr.edu > > **************************************** > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -- **************************************** Zhenqiang(Frank) Ye Ph.D Student Department of Electrical Engineering University of California, Riverside Phone: (909)-787-2434 email: zye@cs.ucr.edu **************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 14:17:32 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02065 for ; Wed, 2 Oct 2002 14:17:32 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92IJ5R09665 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 14:19:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92IJ5v09662 for ; Wed, 2 Oct 2002 14:19:05 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02045 for ; Wed, 2 Oct 2002 14:17:01 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92HCpv05274; Wed, 2 Oct 2002 13:12:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92HBCv05196 for ; Wed, 2 Oct 2002 13:11:12 -0400 Received: from barrichello.cs.ucr.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28757 for ; Wed, 2 Oct 2002 13:09:07 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id 129F3AB59963; Wed, 2 Oct 2002 10:11:06 -0700 (PDT) Mailbox-Line: From zye@cs.ucr.edu Wed Oct 2 10:11:01 2002 Received: from io.cs.ucr.edu (io.cs.ucr.edu [138.23.174.180]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id E9490AB59961; Wed, 2 Oct 2002 10:11:00 -0700 (PDT) Received: by io.cs.ucr.edu (Postfix, from userid 7296) id 2D18D264E7; Wed, 2 Oct 2002 10:11:00 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by io.cs.ucr.edu (Postfix) with ESMTP id 1E2B62588B; Wed, 2 Oct 2002 10:11:00 -0700 (PDT) Date: Wed, 2 Oct 2002 10:11:00 -0700 (PDT) From: "Zhenqiang(Frank) Ye" To: Riadh Marrakchi Cc: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Subject: Re: [manet] Question about traces (r,s,f,d)?? In-Reply-To: <3D9AA3F3.B08B98E0@mchp.siemens.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-1.9 required=5.0 tests=IN_REP_TO,SUBJ_ENDS_IN_Q_MARK,DOUBLE_CAPSWORD, SIGNATURE_DELIM version=2.31 X-Virus-Scanned: by AMaViS perl-11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , I don't think you can see the packet "DELETE" event in your trace file if you turn off the RTR trace. Frank On Wed, 2 Oct 2002, Riadh Marrakchi wrote: > Hi, > the RTR Traces are set off in my simulation scripts, so that i get only the > AGT traces. > > "Zhenqiang(Frank) Ye" wrote: > > > You can not use the method you described. See the example below: > > (The transport and IP layer trace are ON) > > s 2.199994566 _1_ AGT --- 6 cbr .... > > r 2.199994566 _1_ RTR --- 6 cbr .... > > s 2.199994566 _1_ RTR --- 6 cbr .... > > r 2.200547959 _2_ RTR --- 6 cbr .... > > f 2.200547959 _2_ RTR --- 6 cbr .... > > r 2.201817971 _3_ AGT --- 6 cbr .... > > > > The packet 6 is marked "cbr" all the time. It is sent by node 1 two > > times (at different layers), and is received 3 times (by different nodes > > and different layers). That is why your method does not work. In order > > to compute correctly, you need to add "AGT" in your filter when you cout > > the number of packets "sent" and "received". > > > > Hope it helps, > > > > Zhenqiang(Frank) > > > > On Tue, 1 Oct 2002, Riadh Marrakchi wrote: > > > > > Hi, > > > the first column of the trace files (new traces) of the AODV simulation > > > just confused me a little bit. > > > s: is written once when the source sends a packet > > > d: when a packet is dropped by some node (this line is also found only > > > one time in the trace file when a packet is dropped) > > > r: when a packet arrives at the destination > > > f: when a packet is forwarded by some node. > > > so let's assume node 1 tries to send a packet to node 3 through node 2. > > > Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it > > > and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first > > > receives ("r") the packet then forward it ("f")???? > > > Normally we would get: Total of sent cbr packets = total of dropped cbr > > > packets + total of received cbr packets. But while analysing my trace > > > files i get: Total of sent cbr packets < total of dropped cbr packets + > > > total of received cbr packets. Although the difference is not that big, > > > i would know how it exists??? > > > Total of sent cbr packets: Lines with s at the beginning and cbr as > > > packet type > > > total of dropped cbr packets: Lines with d at the beginning and cbr as > > > packet type > > > total of received cbr packets:Lines with r at the beginning and cbr as > > > packet type > > > > > > Thanks a lot for any help or comment. > > > Riadh > > > > > > > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > -- > > > > **************************************** > > Zhenqiang(Frank) Ye > > Ph.D Student > > Department of Electrical Engineering > > University of California, Riverside > > Phone: (909)-787-2434 > > email: zye@cs.ucr.edu > > **************************************** > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -- **************************************** Zhenqiang(Frank) Ye Ph.D Student Department of Electrical Engineering University of California, Riverside Phone: (909)-787-2434 email: zye@cs.ucr.edu **************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 2 16:24:32 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06601 for ; Wed, 2 Oct 2002 16:24:32 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92K4fv15765; Wed, 2 Oct 2002 16:04:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92K2Cv15688 for ; Wed, 2 Oct 2002 16:02:12 -0400 Received: from mailcity.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA05848 for ; Wed, 2 Oct 2002 16:00:06 -0400 (EDT) Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Wed, 02 Oct 2002 20:02:01 -0000 To: "John Paul O'Grady" , manet@ietf.org, "Joe Macker" Date: Wed, 02 Oct 2002 16:02:01 -0400 From: "Yasser A. Lotfy" Message-ID: Mime-Version: 1.0 X-Sent-Mail: off Reply-To: yasser.lotfy@lycos.com X-Mailer: MailCity Service X-Priority: 3 Subject: Re: [manet] ip address allocation X-Sender-Ip: 216.209.247.163 Organization: Lycos Mail (http://www.mail.lycos.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Good day, I believe your best bet in this are are Charles E. Perkins, Jari T. Malinen, Ryuji Wakikawa, Elizabeth M. Belding-Royer, Yuan Sun, “IP Address Autoconfiguration for Ad Hoc Networks”, IETF draft, MANET working group, URL:, November 2001. Ryuji Wakikawa, Jari T. Malinen, Charles E. Perkins, Anders Nilsson, Antti J. Tuominen, “Global Connectivity for IPv6 Mobile Ad Hoc Networks”, IETF draft, MANET working group, URL: , November 2001. This covers specially reactive algorithms. Proavtive algorithms followed many different avenues. Currently I'm working on enhancing the gateway information and forming sort of a gateway update protocol. If this is the way you're heading I can forward more elaborate resources. Hope this helps, Yasser Carleton U ____________________________________________________________ Tired of all the SPAM in your inbox? Switch to LYCOS MAIL PLUS http://www.mail.lycos.com/brandPage.shtml?pageId=plus _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 16:27:22 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06702 for ; Wed, 2 Oct 2002 16:27:22 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92KSvI17158 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 16:28:57 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92KSvv17155 for ; Wed, 2 Oct 2002 16:28:57 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06684 for ; Wed, 2 Oct 2002 16:26:51 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92K4fv15765; Wed, 2 Oct 2002 16:04:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92K2Cv15688 for ; Wed, 2 Oct 2002 16:02:12 -0400 Received: from mailcity.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA05848 for ; Wed, 2 Oct 2002 16:00:06 -0400 (EDT) Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Wed, 02 Oct 2002 20:02:01 -0000 To: "John Paul O'Grady" , manet@ietf.org, "Joe Macker" Date: Wed, 02 Oct 2002 16:02:01 -0400 From: "Yasser A. Lotfy" Message-ID: Mime-Version: 1.0 X-Sent-Mail: off Reply-To: yasser.lotfy@lycos.com X-Mailer: MailCity Service X-Priority: 3 Subject: Re: [manet] ip address allocation X-Sender-Ip: 216.209.247.163 Organization: Lycos Mail (http://www.mail.lycos.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Good day, I believe your best bet in this are are Charles E. Perkins, Jari T. Malinen, Ryuji Wakikawa, Elizabeth M. Belding-Royer, Yuan Sun, “IP Address Autoconfiguration for Ad Hoc Networks”, IETF draft, MANET working group, URL:, November 2001. Ryuji Wakikawa, Jari T. Malinen, Charles E. Perkins, Anders Nilsson, Antti J. Tuominen, “Global Connectivity for IPv6 Mobile Ad Hoc Networks”, IETF draft, MANET working group, URL: , November 2001. This covers specially reactive algorithms. Proavtive algorithms followed many different avenues. Currently I'm working on enhancing the gateway information and forming sort of a gateway update protocol. If this is the way you're heading I can forward more elaborate resources. Hope this helps, Yasser Carleton U ____________________________________________________________ Tired of all the SPAM in your inbox? Switch to LYCOS MAIL PLUS http://www.mail.lycos.com/brandPage.shtml?pageId=plus _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 18:20:39 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09822 for ; Wed, 2 Oct 2002 18:20:39 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92MMEI24547 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 18:22:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92MMEv24544 for ; Wed, 2 Oct 2002 18:22:14 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09803 for ; Wed, 2 Oct 2002 18:20:08 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92MEQv24192; Wed, 2 Oct 2002 18:14:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92MCjv24105 for ; Wed, 2 Oct 2002 18:12:45 -0400 Received: from research.rutgers.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09554 for ; Wed, 2 Oct 2002 18:10:40 -0400 (EDT) Received: from localhost (xili@localhost) by research.rutgers.edu (8.11.6+Sun/8.8.8) with ESMTP id g92MCIN28392; Wed, 2 Oct 2002 18:12:18 -0400 (EDT) Date: Wed, 2 Oct 2002 18:12:18 -0400 (EDT) From: Xiaoyan Li To: "Yasser A. Lotfy" cc: manet@ietf.org Subject: Re: [manet] ip address allocation In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id g92MCnv24107 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hello, I am also interested in this problem. Could you pls give more resource abt your gateway related protocol? Thanks, Xiaoyan ============================== On Wed, 2 Oct 2002, Yasser A. Lotfy wrote: > Good day, > > I believe your best bet in this are are > > Charles E. Perkins, Jari T. Malinen, Ryuji Wakikawa, Elizabeth M. Belding-Royer, Yuan Sun, “IP Address Autoconfiguration for Ad Hoc Networks”, IETF draft, MANET working group, URL:, November 2001. > > Ryuji Wakikawa, Jari T. Malinen, Charles E. Perkins, Anders Nilsson, Antti J. Tuominen, “Global Connectivity for IPv6 Mobile Ad Hoc Networks”, IETF draft, MANET working group, URL: , November 2001. > > This covers specially reactive algorithms. Proavtive algorithms followed many different avenues. Currently I'm working on enhancing the gateway information and forming sort of a gateway update protocol. If this is the way you're heading I can forward more elaborate resources. > > Hope this helps, > > Yasser > Carleton U > > > > ____________________________________________________________ > Tired of all the SPAM in your inbox? Switch to LYCOS MAIL PLUS > http://www.mail.lycos.com/brandPage.shtml?pageId=plus > _______________________________________________ > 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-admin@ietf.org Wed Oct 2 18:20:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09836 for ; Wed, 2 Oct 2002 18:20:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92MEQv24192; Wed, 2 Oct 2002 18:14:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92MCjv24105 for ; Wed, 2 Oct 2002 18:12:45 -0400 Received: from research.rutgers.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09554 for ; Wed, 2 Oct 2002 18:10:40 -0400 (EDT) Received: from localhost (xili@localhost) by research.rutgers.edu (8.11.6+Sun/8.8.8) with ESMTP id g92MCIN28392; Wed, 2 Oct 2002 18:12:18 -0400 (EDT) Date: Wed, 2 Oct 2002 18:12:18 -0400 (EDT) From: Xiaoyan Li To: "Yasser A. Lotfy" cc: manet@ietf.org Subject: Re: [manet] ip address allocation In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id g92MCnv24107 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hello, I am also interested in this problem. Could you pls give more resource abt your gateway related protocol? Thanks, Xiaoyan ============================== On Wed, 2 Oct 2002, Yasser A. Lotfy wrote: > Good day, > > I believe your best bet in this are are > > Charles E. Perkins, Jari T. Malinen, Ryuji Wakikawa, Elizabeth M. Belding-Royer, Yuan Sun, “IP Address Autoconfiguration for Ad Hoc Networks”, IETF draft, MANET working group, URL:, November 2001. > > Ryuji Wakikawa, Jari T. Malinen, Charles E. Perkins, Anders Nilsson, Antti J. Tuominen, “Global Connectivity for IPv6 Mobile Ad Hoc Networks”, IETF draft, MANET working group, URL: , November 2001. > > This covers specially reactive algorithms. Proavtive algorithms followed many different avenues. Currently I'm working on enhancing the gateway information and forming sort of a gateway update protocol. If this is the way you're heading I can forward more elaborate resources. > > Hope this helps, > > Yasser > Carleton U > > > > ____________________________________________________________ > Tired of all the SPAM in your inbox? Switch to LYCOS MAIL PLUS > http://www.mail.lycos.com/brandPage.shtml?pageId=plus > _______________________________________________ > 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-admin@ietf.org Wed Oct 2 19:19:29 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11381 for ; Wed, 2 Oct 2002 19:19:29 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92NDAv27616; Wed, 2 Oct 2002 19:13:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92NBRv27559 for ; Wed, 2 Oct 2002 19:11:27 -0400 Received: from deimos.hpl.hp.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11011 for ; Wed, 2 Oct 2002 19:09:20 -0400 (EDT) Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by deimos.hpl.hp.com (8.9.3 (PHNE_24419)/HPL-PA Relay) with ESMTP id QAA28163; Wed, 2 Oct 2002 16:11:16 -0700 (PDT) Received: from hplex1.hpl.hp.com (hplex1.hpl.hp.com [15.0.152.182]) by hplms2.hpl.hp.com (8.10.2/8.10.2 HPL-PA Hub) with SMTP id g92NBGw27898; Wed, 2 Oct 2002 16:11:16 -0700 (PDT) Received: from 15.0.152.182 by hplex1.hpl.hp.com (InterScan E-Mail VirusWall NT); Wed, 02 Oct 2002 16:11:15 -0700 Received: by hplex1.hpl.hp.com with Internet Mail Service (5.5.2653.19) id <4C0KVXJQ>; Wed, 2 Oct 2002 16:11:15 -0700 Message-ID: <75A9FEBA25015040A761C1F74975667D928F94@hplex4.hpl.hp.com> From: "Lee, Sung Ju" Reply-To: sjlee@hpl.hp.com To: "'manet@ietf.org'" Cc: "Stefano Basagni (E-mail)" , "'sjlee@hpl.hp.com'" Date: Wed, 2 Oct 2002 16:11:15 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [manet] WCMC's special issue on ad hoc networking Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Dear friends & collegues, Stefano Basagni of Northeastern University and I have guest edited a speical issue of ad hoc networks for WCMC journal. http://www3.interscience.wiley.com/cgi-bin/issuetoc?ID=98516252 We have seven excellent papers that you may be interested in checking out. You can view the papers from the above website. The papers in this issue are: - Ad hoc networks: not an ad hoc field anymore Anthony Ephremides - Quests in a tetherless world Chatschik Bisdikian, Stefan Hild, Nathan Lee, Veronique Perret, Mahmoud Naghshineh - Internet connectivity for mobile ad hoc networks Charles E. Perkins, Jari T. Malinen, Ryuji Wakikawa, Anders Nilsson, Antti J. Tuominen - A survey of mobility models for ad hoc network research Tracy Camp, Jeff Boleng, Vanessa Davies - A survey on quality-of-service support for mobile ad hoc networks Dmitri D. Perkins, Herman D. Hughes - Hierarchical routing in ad hoc mobile networks Elizabeth M. Belding-Royer - Adaptive security for multilevel ad hoc networks Jiejun Kong, Haiyun Luo, Kaixin Xu, Daniel Lihui Gu, Mario Gerla, Songwu Lu Best wishes, -- Stefano & SJ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 19:22:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11519 for ; Wed, 2 Oct 2002 19:22:36 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92NOC228030 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 19:24:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92NOCv28027 for ; Wed, 2 Oct 2002 19:24:12 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11510 for ; Wed, 2 Oct 2002 19:22:05 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92NGav27717; Wed, 2 Oct 2002 19:16:36 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92NFKv27681 for ; Wed, 2 Oct 2002 19:15:20 -0400 Received: from shaku.sfc.wide.ad.jp (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11080 for ; Wed, 2 Oct 2002 19:13:13 -0400 (EDT) Received: from monster.sfc.wide.ad.jp.sfc.wide.ad.jp (luna.sfc.wide.ad.jp [203.178.143.62]) (authenticated bits=0) by shaku.sfc.wide.ad.jp (8.12.0/8.12.0) with ESMTP id g92NF2Ma031064; Thu, 3 Oct 2002 08:15:02 +0900 Date: Thu, 03 Oct 2002 08:10:06 +0900 Message-ID: From: Ryuji Wakikawa To: yasser.lotfy@lycos.com Cc: jpogrady@cit.ie, manet@ietf.org, macker@itd.nrl.navy.mil Subject: Re: [manet] ip address allocation In-Reply-To: References: User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/20.7 (i386--freebsd) MULE/4.1 (AOI) Organization: Keio University MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, #Thanks Yasser. I am currently updating the "Global connectivity..." draft to solve the problem on proactive protocols. I hope it will be appeared soon before next IETF. regards, ryuji At Wed, 02 Oct 2002 16:02:01 -0400, Yasser A. Lotfy wrote: > > Good day, > > I believe your best bet in this are are > > Charles E. Perkins, Jari T. Malinen, Ryuji Wakikawa, Elizabeth M. Belding-Royer, Yuan Sun, “IP Address Autoconfiguration for Ad Hoc Networks”, IETF draft, MANET working group, URL:, November 2001. > > Ryuji Wakikawa, Jari T. Malinen, Charles E. Perkins, Anders Nilsson, Antti J. Tuominen, “Global Connectivity for IPv6 Mobile Ad Hoc Networks”, IETF draft, MANET working group, URL: , November 2001. > > This covers specially reactive algorithms. Proavtive algorithms followed many different avenues. Currently I'm working on enhancing the gateway information and forming sort of a gateway update protocol. If this is the way you're heading I can forward more elaborate resources. > > Hope this helps, > > Yasser > Carleton U > > > > ____________________________________________________________ > Tired of all the SPAM in your inbox? Switch to LYCOS MAIL PLUS > http://www.mail.lycos.com/brandPage.shtml?pageId=plus > _______________________________________________ > 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-admin@ietf.org Wed Oct 2 19:22:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11532 for ; Wed, 2 Oct 2002 19:22:38 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92NGav27717; Wed, 2 Oct 2002 19:16:36 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92NFKv27681 for ; Wed, 2 Oct 2002 19:15:20 -0400 Received: from shaku.sfc.wide.ad.jp (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11080 for ; Wed, 2 Oct 2002 19:13:13 -0400 (EDT) Received: from monster.sfc.wide.ad.jp.sfc.wide.ad.jp (luna.sfc.wide.ad.jp [203.178.143.62]) (authenticated bits=0) by shaku.sfc.wide.ad.jp (8.12.0/8.12.0) with ESMTP id g92NF2Ma031064; Thu, 3 Oct 2002 08:15:02 +0900 Date: Thu, 03 Oct 2002 08:10:06 +0900 Message-ID: From: Ryuji Wakikawa To: yasser.lotfy@lycos.com Cc: jpogrady@cit.ie, manet@ietf.org, macker@itd.nrl.navy.mil Subject: Re: [manet] ip address allocation In-Reply-To: References: User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/20.7 (i386--freebsd) MULE/4.1 (AOI) Organization: Keio University MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, #Thanks Yasser. I am currently updating the "Global connectivity..." draft to solve the problem on proactive protocols. I hope it will be appeared soon before next IETF. regards, ryuji At Wed, 02 Oct 2002 16:02:01 -0400, Yasser A. Lotfy wrote: > > Good day, > > I believe your best bet in this are are > > Charles E. Perkins, Jari T. Malinen, Ryuji Wakikawa, Elizabeth M. Belding-Royer, Yuan Sun, “IP Address Autoconfiguration for Ad Hoc Networks”, IETF draft, MANET working group, URL:, November 2001. > > Ryuji Wakikawa, Jari T. Malinen, Charles E. Perkins, Anders Nilsson, Antti J. Tuominen, “Global Connectivity for IPv6 Mobile Ad Hoc Networks”, IETF draft, MANET working group, URL: , November 2001. > > This covers specially reactive algorithms. Proavtive algorithms followed many different avenues. Currently I'm working on enhancing the gateway information and forming sort of a gateway update protocol. If this is the way you're heading I can forward more elaborate resources. > > Hope this helps, > > Yasser > Carleton U > > > > ____________________________________________________________ > Tired of all the SPAM in your inbox? Switch to LYCOS MAIL PLUS > http://www.mail.lycos.com/brandPage.shtml?pageId=plus > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 2 19:23:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11567 for ; Wed, 2 Oct 2002 19:23:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g92NP2P28075 for manet-archive@odin.ietf.org; Wed, 2 Oct 2002 19:25:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92NP2v28072 for ; Wed, 2 Oct 2002 19:25:02 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11546 for ; Wed, 2 Oct 2002 19:22:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92NDAv27616; Wed, 2 Oct 2002 19:13:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g92NBRv27559 for ; Wed, 2 Oct 2002 19:11:27 -0400 Received: from deimos.hpl.hp.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11011 for ; Wed, 2 Oct 2002 19:09:20 -0400 (EDT) Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by deimos.hpl.hp.com (8.9.3 (PHNE_24419)/HPL-PA Relay) with ESMTP id QAA28163; Wed, 2 Oct 2002 16:11:16 -0700 (PDT) Received: from hplex1.hpl.hp.com (hplex1.hpl.hp.com [15.0.152.182]) by hplms2.hpl.hp.com (8.10.2/8.10.2 HPL-PA Hub) with SMTP id g92NBGw27898; Wed, 2 Oct 2002 16:11:16 -0700 (PDT) Received: from 15.0.152.182 by hplex1.hpl.hp.com (InterScan E-Mail VirusWall NT); Wed, 02 Oct 2002 16:11:15 -0700 Received: by hplex1.hpl.hp.com with Internet Mail Service (5.5.2653.19) id <4C0KVXJQ>; Wed, 2 Oct 2002 16:11:15 -0700 Message-ID: <75A9FEBA25015040A761C1F74975667D928F94@hplex4.hpl.hp.com> From: "Lee, Sung Ju" Reply-To: sjlee@hpl.hp.com To: "'manet@ietf.org'" Cc: "Stefano Basagni (E-mail)" , "'sjlee@hpl.hp.com'" Date: Wed, 2 Oct 2002 16:11:15 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [manet] WCMC's special issue on ad hoc networking Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Dear friends & collegues, Stefano Basagni of Northeastern University and I have guest edited a speical issue of ad hoc networks for WCMC journal. http://www3.interscience.wiley.com/cgi-bin/issuetoc?ID=98516252 We have seven excellent papers that you may be interested in checking out. You can view the papers from the above website. The papers in this issue are: - Ad hoc networks: not an ad hoc field anymore Anthony Ephremides - Quests in a tetherless world Chatschik Bisdikian, Stefan Hild, Nathan Lee, Veronique Perret, Mahmoud Naghshineh - Internet connectivity for mobile ad hoc networks Charles E. Perkins, Jari T. Malinen, Ryuji Wakikawa, Anders Nilsson, Antti J. Tuominen - A survey of mobility models for ad hoc network research Tracy Camp, Jeff Boleng, Vanessa Davies - A survey on quality-of-service support for mobile ad hoc networks Dmitri D. Perkins, Herman D. Hughes - Hierarchical routing in ad hoc mobile networks Elizabeth M. Belding-Royer - Adaptive security for multilevel ad hoc networks Jiejun Kong, Haiyun Luo, Kaixin Xu, Daniel Lihui Gu, Mario Gerla, Songwu Lu Best wishes, -- Stefano & SJ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 3 10:55:32 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14415 for ; Thu, 3 Oct 2002 10:55:32 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93EpUv23599; Thu, 3 Oct 2002 10:51:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Ehxv23275 for ; Thu, 3 Oct 2002 10:43:59 -0400 Received: from gwserver.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13675 for ; Thu, 3 Oct 2002 10:41:52 -0400 (EDT) Received: from swl1002 ([172.16.3.193]) by gwserver.icr.a-star.edu.sg; Thu, 03 Oct 2002 22:39:02 +0800 Message-ID: <009c01c26aea$9a6e3300$c10310ac@icr.astar.edu.sg> Reply-To: "Ankur Jain" From: "Ankur Jain" To: =?iso-8859-1?Q?Mesut_G=FCnes?= , References: <00bd01c26a28$841f11e0$d00ce289@informatik.rwthaachen.de> Subject: Re: [manet] ip address allocation Date: Thu, 3 Oct 2002 22:38:53 +0800 Organization: Institute for Communications Research, Singapore MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi Your paper is not available on your website. I could only find the presentation. Could you please provide the actual paper also? Regards Ankur ----- Original Message ----- From: Mesut Günes To: Sent: Wednesday, October 02, 2002 11:29 PM Subject: AW: [manet] ip address allocation > Hi, > > ###I have a question in regards to ip address allocation in an > ###ad hoc environment. In an ad hoc environment presumely ip > ###addresses will be allocated dynamically to new nodes as they > ###attach themselves to the network. > ### > ###Is there much research out there into how exactly this will be done. > ###I know in a normal network it can be done through a dhcp > ###server, but in an ad hoc environment you cant really assume > ###a dhcp server will be available. > > We have proposed a distributed dynamic configuration algorithm for > mobile > multi-hop ad-hoc networks which do not require human interaction. Our > aim > was to introduce a mechanism which is also able to recognize the > splitting > and merging of several ad-hoc networks. > > In our paper we have tried to give an overview about existing dynamic > addressing approaches (DHCP, Zero Configuration, Auto-Configuration, > ...). > Additionally, you'll find a performance comparison of our own approach > and DHCP and Auto-Configuration. All results are obtained over ns-2. > > Paper: > ------ > Mesut Günes and Jörg Reibel. > An ip address configuration algorithm for zeroconf. mobile multi-hop > ad-hoc networks. > In Proceedings of the International Workshop on Broadband Wireless > Ad-Hoc Networks and Services, Sophia Antipolis, France, September 2002. > ETSI. > > > The paper is also electronically available via: > http://www.projectmesa.org/workshop2002/agenda.htm > > > > Regards > Mesut Günes > > PS: Further information aobut our work you'll find via: > http://www.adhoc-nets.de > > _______________________________________________ > 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-admin@ietf.org Thu Oct 3 10:58:17 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14812 for ; Thu, 3 Oct 2002 10:58:17 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Eudv23865; Thu, 3 Oct 2002 10:56:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Eigv23297 for ; Thu, 3 Oct 2002 10:44:42 -0400 Received: from mbox1.ntu.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13725 for ; Thu, 3 Oct 2002 10:42:38 -0400 (EDT) Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Thu, 3 Oct 2002 22:22:09 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Date: Thu, 3 Oct 2002 22:22:09 +0800 Message-ID: <295CB338B611594582D82D9F26AEF7062CBEC8@mail02.student.main.ntu.edu.sg> Thread-Topic: Implemetation of GPS info along with Signal to noise ratio.... Thread-Index: AcJq6EI5oR9fW4BzS7WbAUeJrpIy1Q== From: "#GUPTA ROHIT#" To: X-OriginalArrivalTime: 03 Oct 2002 14:22:09.0887 (UTC) FILETIME=[426816F0:01C26AE8] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g93Eigv23298 Subject: [manet] Implemetation of GPS info along with Signal to noise ratio.... Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Dear all, can anyone tell me whether there is any work in integrating signal to noise ratio in GPS based protocols for MANETs. cheers rohit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 3 10:58:20 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14825 for ; Thu, 3 Oct 2002 10:58:19 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Et6v23805; Thu, 3 Oct 2002 10:55:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93EiAv23281 for ; Thu, 3 Oct 2002 10:44:10 -0400 Received: from mail11.ntu.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13686 for ; Thu, 3 Oct 2002 10:42:06 -0400 (EDT) Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mail11.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Thu, 3 Oct 2002 22:20:03 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Subject: RE: [manet] signal to noise ratio(SNR) and GPS info.. Date: Thu, 3 Oct 2002 22:20:03 +0800 Message-ID: <295CB338B611594582D82D9F26AEF7062CBEC7@mail02.student.main.ntu.edu.sg> Thread-Topic: [manet] signal to noise ratio(SNR) and GPS info.. Thread-Index: AcJqMizlbm2wg3jXTSWFw6z58DanoQAtQsBr From: "#GUPTA ROHIT#" To: =?Windows-1252?Q?Erik_Nordstr=F6m?= Cc: X-OriginalArrivalTime: 03 Oct 2002 14:20:03.0523 (UTC) FILETIME=[F7167930:01C26AE7] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g93EiAv23282 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit hi erik, thks for the paper.... i hv read it but the main drawback of the SNR schem proposed is that it puts hard SNR threshold on the control packets....this will obviously result in getting good quality link but it might be the case that this approach will not be able to deliver packets when the only link thats available is very poor...i mean to say that original AODV will probably work even in poor quality link though the performance is very poor..... wud it be better if we use algo to use multiple paths and each path is indexed by SNR and then decide the optimal path.... pls let me know if there is any work in this direction.... cheers rohit -----Original Message----- From: Erik Nordström [mailto:erik.nordstrom@it.uu.se] Sent: Thu 10/3/2002 12:38 AM To: MANET LIST Cc: #GUPTA ROHIT# Subject: Re: [manet] signal to noise ratio(SNR) and GPS info.. I've put a pdf of the paper mentioned below on the web. http://www.docs.uu.se/scanet/aodv/grayzones.pdf Erik On Wed, 2002-10-02 at 16:44, Erik Nordström wrote: > Just a note. > > This paper has been published at WoWMoM 2002. > > Erik Nordström > > On Wed, 2002-10-02 at 16:35, idc@engineering.ucsb.edu wrote: > > The paper > > > > Coping with Communication Gray Zones in IEEE 802.11b based Ad hoc Networks > > Henrik Lundgren, Erik Nordström, Christian Tschudin (Uppsala > > University, Sweden) > > > > Looks at using SNR to improve AODV. > > > > Ian Chakeres > > > > #GUPTA ROHIT# writes: > > > > > > > > > > > > Dear all, > > > can anyone let me know on the work done on SNR and GPS to improve AODV. > > > > > > rgds > > > rohit > > > > > > _______________________________________________ > > > 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 > -- > Erik Nordström > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- Erik Nordström _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 3 11:05:18 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15559 for ; Thu, 3 Oct 2002 11:05:18 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g93F6oo24838 for manet-archive@odin.ietf.org; Thu, 3 Oct 2002 11:06:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93F6ov24835 for ; Thu, 3 Oct 2002 11:06:50 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15530 for ; Thu, 3 Oct 2002 11:04:46 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93F4Kv24647; Thu, 3 Oct 2002 11:04:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93F2Xv24578 for ; Thu, 3 Oct 2002 11:02:33 -0400 Received: from mailg.telia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15072 for ; Thu, 3 Oct 2002 11:00:27 -0400 (EDT) Received: from d1o1121.telia.com (d1o1121.telia.com [217.208.140.241]) by mailg.telia.com (8.12.5/8.12.5) with ESMTP id g93F2N5s026005; Thu, 3 Oct 2002 17:02:23 +0200 (CEST) X-Original-Recipient: manet@ietf.org Received: from h168n2fls35o1121.telia.com (h168n2fls35o1121.telia.com [217.211.83.168]) by d1o1121.telia.com (8.10.2/8.10.1) with ESMTP id g93F2MB17239; Thu, 3 Oct 2002 17:02:22 +0200 (CEST) Subject: RE: [manet] signal to noise ratio(SNR) and GPS info.. From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: #GUPTA ROHIT# Cc: manet@ietf.org In-Reply-To: <295CB338B611594582D82D9F26AEF7062CBEC7@mail02.student.main.ntu.edu.sg> References: <295CB338B611594582D82D9F26AEF7062CBEC7@mail02.student.main.ntu.edu.sg> Content-Type: text/plain; charset=UTF-8 X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 03 Oct 2002 17:02:18 +0200 Message-Id: <1033657339.21625.15.camel@replicator.hn.org> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g93F2Xv24579 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi Rohit The main purpose of our modifications to AODV were simply to show that there can be things done to improve AODV's performance in the presence of so called "Gray zones", which is what we did. We never intended to propose a "final" way of doing things. We also acknowledge that there are problems with the approaches we chose, but they still makes a point. Using multiple paths is a completely different modification to AODV from what we have been exploring. There is work being done on multipath AODV, although it does not necessarily use SNR information to chose the best path. I am not even sure using SNR for choosing the best path is such a good idea, since the SNR you use would have to be an average value over all hops for that path or only reflect for example the weakest link in the chain... Also this would be a snapshot of the path quality, which might change all the time due to movement and other factors. Therefore, our idea of applying an SNR threshold to control messages makes a lot of sense, since they are regularly broadcasted (in the case of HELLO beaconings), and is applied on a link-by-link basis. Erik On Thu, 2002-10-03 at 16:20, #GUPTA ROHIT# wrote: > > hi erik, > thks for the paper.... > i hv read it but the main drawback of the SNR schem proposed is that it puts hard SNR threshold on the control packets....this will obviously result in getting good quality link but it might be the case that this approach will not be able to deliver packets when the only link thats available is very poor...i mean to say that original AODV will probably work even in poor quality link though the performance is very poor..... > wud it be better if we use algo to use multiple paths and each path is indexed by SNR and then decide the optimal path.... > pls let me know if there is any work in this direction.... > > cheers > rohit > > -----Original Message----- > From: Erik Nordström [mailto:erik.nordstrom@it.uu.se] > Sent: Thu 10/3/2002 12:38 AM > To: MANET LIST > Cc: #GUPTA ROHIT# > Subject: Re: [manet] signal to noise ratio(SNR) and GPS info.. > > I've put a pdf of the paper mentioned below on the web. > > http://www.docs.uu.se/scanet/aodv/grayzones.pdf > > Erik > > On Wed, 2002-10-02 at 16:44, Erik Nordström wrote: > > Just a note. > > > > This paper has been published at WoWMoM 2002. > > > > Erik Nordström > > > > On Wed, 2002-10-02 at 16:35, idc@engineering.ucsb.edu wrote: > > > The paper > > > > > > Coping with Communication Gray Zones in IEEE 802.11b based Ad hoc Networks > > > Henrik Lundgren, Erik Nordström, Christian Tschudin (Uppsala > > > University, Sweden) > > > > > > Looks at using SNR to improve AODV. > > > > > > Ian Chakeres > > > > > > #GUPTA ROHIT# writes: > > > > > > > > > > > > > > > > Dear all, > > > > can anyone let me know on the work done on SNR and GPS to improve AODV. > > > > > > > > rgds > > > > rohit > > > > > > > > _______________________________________________ > > > > 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 > > -- > > Erik Nordström > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > -- > Erik Nordström > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 3 11:05:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15611 for ; Thu, 3 Oct 2002 11:05:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93F4Kv24647; Thu, 3 Oct 2002 11:04:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93F2Xv24578 for ; Thu, 3 Oct 2002 11:02:33 -0400 Received: from mailg.telia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15072 for ; Thu, 3 Oct 2002 11:00:27 -0400 (EDT) Received: from d1o1121.telia.com (d1o1121.telia.com [217.208.140.241]) by mailg.telia.com (8.12.5/8.12.5) with ESMTP id g93F2N5s026005; Thu, 3 Oct 2002 17:02:23 +0200 (CEST) X-Original-Recipient: manet@ietf.org Received: from h168n2fls35o1121.telia.com (h168n2fls35o1121.telia.com [217.211.83.168]) by d1o1121.telia.com (8.10.2/8.10.1) with ESMTP id g93F2MB17239; Thu, 3 Oct 2002 17:02:22 +0200 (CEST) Subject: RE: [manet] signal to noise ratio(SNR) and GPS info.. From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: #GUPTA ROHIT# Cc: manet@ietf.org In-Reply-To: <295CB338B611594582D82D9F26AEF7062CBEC7@mail02.student.main.ntu.edu.sg> References: <295CB338B611594582D82D9F26AEF7062CBEC7@mail02.student.main.ntu.edu.sg> Content-Type: text/plain; charset=UTF-8 X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 03 Oct 2002 17:02:18 +0200 Message-Id: <1033657339.21625.15.camel@replicator.hn.org> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g93F2Xv24579 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi Rohit The main purpose of our modifications to AODV were simply to show that there can be things done to improve AODV's performance in the presence of so called "Gray zones", which is what we did. We never intended to propose a "final" way of doing things. We also acknowledge that there are problems with the approaches we chose, but they still makes a point. Using multiple paths is a completely different modification to AODV from what we have been exploring. There is work being done on multipath AODV, although it does not necessarily use SNR information to chose the best path. I am not even sure using SNR for choosing the best path is such a good idea, since the SNR you use would have to be an average value over all hops for that path or only reflect for example the weakest link in the chain... Also this would be a snapshot of the path quality, which might change all the time due to movement and other factors. Therefore, our idea of applying an SNR threshold to control messages makes a lot of sense, since they are regularly broadcasted (in the case of HELLO beaconings), and is applied on a link-by-link basis. Erik On Thu, 2002-10-03 at 16:20, #GUPTA ROHIT# wrote: > > hi erik, > thks for the paper.... > i hv read it but the main drawback of the SNR schem proposed is that it puts hard SNR threshold on the control packets....this will obviously result in getting good quality link but it might be the case that this approach will not be able to deliver packets when the only link thats available is very poor...i mean to say that original AODV will probably work even in poor quality link though the performance is very poor..... > wud it be better if we use algo to use multiple paths and each path is indexed by SNR and then decide the optimal path.... > pls let me know if there is any work in this direction.... > > cheers > rohit > > -----Original Message----- > From: Erik Nordström [mailto:erik.nordstrom@it.uu.se] > Sent: Thu 10/3/2002 12:38 AM > To: MANET LIST > Cc: #GUPTA ROHIT# > Subject: Re: [manet] signal to noise ratio(SNR) and GPS info.. > > I've put a pdf of the paper mentioned below on the web. > > http://www.docs.uu.se/scanet/aodv/grayzones.pdf > > Erik > > On Wed, 2002-10-02 at 16:44, Erik Nordström wrote: > > Just a note. > > > > This paper has been published at WoWMoM 2002. > > > > Erik Nordström > > > > On Wed, 2002-10-02 at 16:35, idc@engineering.ucsb.edu wrote: > > > The paper > > > > > > Coping with Communication Gray Zones in IEEE 802.11b based Ad hoc Networks > > > Henrik Lundgren, Erik Nordström, Christian Tschudin (Uppsala > > > University, Sweden) > > > > > > Looks at using SNR to improve AODV. > > > > > > Ian Chakeres > > > > > > #GUPTA ROHIT# writes: > > > > > > > > > > > > > > > > Dear all, > > > > can anyone let me know on the work done on SNR and GPS to improve AODV. > > > > > > > > rgds > > > > rohit > > > > > > > > _______________________________________________ > > > > 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 > > -- > > Erik Nordström > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > -- > Erik Nordström > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 3 11:11:21 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16115 for ; Thu, 3 Oct 2002 11:11:17 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g93FCoQ25777 for manet-archive@odin.ietf.org; Thu, 3 Oct 2002 11:12:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93FCnv25774 for ; Thu, 3 Oct 2002 11:12:49 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16063 for ; Thu, 3 Oct 2002 11:10:45 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93EpUv23599; Thu, 3 Oct 2002 10:51:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Ehxv23275 for ; Thu, 3 Oct 2002 10:43:59 -0400 Received: from gwserver.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13675 for ; Thu, 3 Oct 2002 10:41:52 -0400 (EDT) Received: from swl1002 ([172.16.3.193]) by gwserver.icr.a-star.edu.sg; Thu, 03 Oct 2002 22:39:02 +0800 Message-ID: <009c01c26aea$9a6e3300$c10310ac@icr.astar.edu.sg> Reply-To: "Ankur Jain" From: "Ankur Jain" To: =?iso-8859-1?Q?Mesut_G=FCnes?= , References: <00bd01c26a28$841f11e0$d00ce289@informatik.rwthaachen.de> Subject: Re: [manet] ip address allocation Date: Thu, 3 Oct 2002 22:38:53 +0800 Organization: Institute for Communications Research, Singapore MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi Your paper is not available on your website. I could only find the presentation. Could you please provide the actual paper also? Regards Ankur ----- Original Message ----- From: Mesut Günes To: Sent: Wednesday, October 02, 2002 11:29 PM Subject: AW: [manet] ip address allocation > Hi, > > ###I have a question in regards to ip address allocation in an > ###ad hoc environment. In an ad hoc environment presumely ip > ###addresses will be allocated dynamically to new nodes as they > ###attach themselves to the network. > ### > ###Is there much research out there into how exactly this will be done. > ###I know in a normal network it can be done through a dhcp > ###server, but in an ad hoc environment you cant really assume > ###a dhcp server will be available. > > We have proposed a distributed dynamic configuration algorithm for > mobile > multi-hop ad-hoc networks which do not require human interaction. Our > aim > was to introduce a mechanism which is also able to recognize the > splitting > and merging of several ad-hoc networks. > > In our paper we have tried to give an overview about existing dynamic > addressing approaches (DHCP, Zero Configuration, Auto-Configuration, > ...). > Additionally, you'll find a performance comparison of our own approach > and DHCP and Auto-Configuration. All results are obtained over ns-2. > > Paper: > ------ > Mesut Günes and Jörg Reibel. > An ip address configuration algorithm for zeroconf. mobile multi-hop > ad-hoc networks. > In Proceedings of the International Workshop on Broadband Wireless > Ad-Hoc Networks and Services, Sophia Antipolis, France, September 2002. > ETSI. > > > The paper is also electronically available via: > http://www.projectmesa.org/workshop2002/agenda.htm > > > > Regards > Mesut Günes > > PS: Further information aobut our work you'll find via: > http://www.adhoc-nets.de > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 3 11:12:49 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16358 for ; Thu, 3 Oct 2002 11:12:49 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g93FEM626043 for manet-archive@odin.ietf.org; Thu, 3 Oct 2002 11:14:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93FELv26040 for ; Thu, 3 Oct 2002 11:14:21 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16298 for ; Thu, 3 Oct 2002 11:12:18 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Et6v23805; Thu, 3 Oct 2002 10:55:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93EiAv23281 for ; Thu, 3 Oct 2002 10:44:10 -0400 Received: from mail11.ntu.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13686 for ; Thu, 3 Oct 2002 10:42:06 -0400 (EDT) Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mail11.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Thu, 3 Oct 2002 22:20:03 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Subject: RE: [manet] signal to noise ratio(SNR) and GPS info.. Date: Thu, 3 Oct 2002 22:20:03 +0800 Message-ID: <295CB338B611594582D82D9F26AEF7062CBEC7@mail02.student.main.ntu.edu.sg> Thread-Topic: [manet] signal to noise ratio(SNR) and GPS info.. Thread-Index: AcJqMizlbm2wg3jXTSWFw6z58DanoQAtQsBr From: "#GUPTA ROHIT#" To: =?Windows-1252?Q?Erik_Nordstr=F6m?= Cc: X-OriginalArrivalTime: 03 Oct 2002 14:20:03.0523 (UTC) FILETIME=[F7167930:01C26AE7] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g93EiAv23282 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hi erik, thks for the paper.... i hv read it but the main drawback of the SNR schem proposed is that it puts hard SNR threshold on the control packets....this will obviously result in getting good quality link but it might be the case that this approach will not be able to deliver packets when the only link thats available is very poor...i mean to say that original AODV will probably work even in poor quality link though the performance is very poor..... wud it be better if we use algo to use multiple paths and each path is indexed by SNR and then decide the optimal path.... pls let me know if there is any work in this direction.... cheers rohit -----Original Message----- From: Erik Nordström [mailto:erik.nordstrom@it.uu.se] Sent: Thu 10/3/2002 12:38 AM To: MANET LIST Cc: #GUPTA ROHIT# Subject: Re: [manet] signal to noise ratio(SNR) and GPS info.. I've put a pdf of the paper mentioned below on the web. http://www.docs.uu.se/scanet/aodv/grayzones.pdf Erik On Wed, 2002-10-02 at 16:44, Erik Nordström wrote: > Just a note. > > This paper has been published at WoWMoM 2002. > > Erik Nordström > > On Wed, 2002-10-02 at 16:35, idc@engineering.ucsb.edu wrote: > > The paper > > > > Coping with Communication Gray Zones in IEEE 802.11b based Ad hoc Networks > > Henrik Lundgren, Erik Nordström, Christian Tschudin (Uppsala > > University, Sweden) > > > > Looks at using SNR to improve AODV. > > > > Ian Chakeres > > > > #GUPTA ROHIT# writes: > > > > > > > > > > > > Dear all, > > > can anyone let me know on the work done on SNR and GPS to improve AODV. > > > > > > rgds > > > rohit > > > > > > _______________________________________________ > > > 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 > -- > Erik Nordström > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- Erik Nordström _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 3 11:12:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16372 for ; Thu, 3 Oct 2002 11:12:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g93FEPx26066 for manet-archive@odin.ietf.org; Thu, 3 Oct 2002 11:14:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93FEOv26063 for ; Thu, 3 Oct 2002 11:14:24 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16309 for ; Thu, 3 Oct 2002 11:12:21 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Eudv23865; Thu, 3 Oct 2002 10:56:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Eigv23297 for ; Thu, 3 Oct 2002 10:44:42 -0400 Received: from mbox1.ntu.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13725 for ; Thu, 3 Oct 2002 10:42:38 -0400 (EDT) Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Thu, 3 Oct 2002 22:22:09 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Date: Thu, 3 Oct 2002 22:22:09 +0800 Message-ID: <295CB338B611594582D82D9F26AEF7062CBEC8@mail02.student.main.ntu.edu.sg> Thread-Topic: Implemetation of GPS info along with Signal to noise ratio.... Thread-Index: AcJq6EI5oR9fW4BzS7WbAUeJrpIy1Q== From: "#GUPTA ROHIT#" To: X-OriginalArrivalTime: 03 Oct 2002 14:22:09.0887 (UTC) FILETIME=[426816F0:01C26AE8] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g93Eigv23298 Subject: [manet] Implemetation of GPS info along with Signal to noise ratio.... Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Dear all, can anyone tell me whether there is any work in integrating signal to noise ratio in GPS based protocols for MANETs. cheers rohit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 3 11:42:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19280 for ; Thu, 3 Oct 2002 11:42:27 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Fd6v28606; Thu, 3 Oct 2002 11:39:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Fbwv28429 for ; Thu, 3 Oct 2002 11:37:58 -0400 Received: from ns0.utdallas.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18664 for ; Thu, 3 Oct 2002 11:35:53 -0400 (EDT) Received: from DSL08 (dsl08.utdallas.edu [129.110.94.81]) by ns0.utdallas.edu (Postfix) with SMTP id 0503E1A1A55 for ; Thu, 3 Oct 2002 10:37:51 -0500 (CDT) Message-ID: <003201c26af2$d59f6c20$515e6e81@campus.ad.utdallas.edu> From: "Mansoor Mohsin" To: References: <00bd01c26a28$841f11e0$d00ce289@informatik.rwthaachen.de> Subject: Re: [manet] ip address allocation Date: Thu, 3 Oct 2002 10:37:51 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002F_01C26AC8.EC99A190" 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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_002F_01C26AC8.EC99A190 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Ravi Prakash and I have a paper titled "IP Address Assignment in a = Mobile Ad Hoc Network". It will appear in the MILCOM 2002 conference = next week. The solution is based on the idea of "buddy list" data = structure used for memory management. There is another paper by Sanket Nasergi and Ravi Prakash titled = "MANETconf: Configuration of Hosts in a Mobile Ad Hoc Network". It = appeared in INFOCOM 2002. You can download this paper from = http://www.utdallas.edu/~ravip/. -------------------------------------------------------------------------= ------- Mansoor Mohsin=20 ----- Original Message -----=20 From: "Mesut GXnes" To: Sent: Wednesday, October 02, 2002 10:29 AM Subject: AW: [manet] ip address allocation > Hi, >=20 > ###I have a question in regards to ip address allocation in an=20 > ###ad hoc environment. In an ad hoc environment presumely ip=20 > ###addresses will be allocated dynamically to new nodes as they=20 > ###attach themselves to the network. > ### > ###Is there much research out there into how exactly this will be = done.=20 > ###I know in a normal network it can be done through a dhcp=20 > ###server, but in an ad hoc environment you cant really assume=20 > ###a dhcp server will be available. >=20 > We have proposed a distributed dynamic configuration algorithm for > mobile=20 > multi-hop ad-hoc networks which do not require human interaction. Our > aim=20 > was to introduce a mechanism which is also able to recognize the > splitting=20 > and merging of several ad-hoc networks. >=20 > In our paper we have tried to give an overview about existing dynamic=20 > addressing approaches (DHCP, Zero Configuration, Auto-Configuration, > ...).=20 > Additionally, you'll find a performance comparison of our own approach > and DHCP and Auto-Configuration. All results are obtained over ns-2. >=20 > Paper: > ------ > Mesut G=FCnes and J=F6rg Reibel.=20 > An ip address configuration algorithm for zeroconf. mobile multi-hop > ad-hoc networks.=20 > In Proceedings of the International Workshop on Broadband Wireless > Ad-Hoc Networks and Services, Sophia Antipolis, France, September = 2002. > ETSI. >=20 >=20 > The paper is also electronically available via: > http://www.projectmesa.org/workshop2002/agenda.htm >=20 >=20 >=20 > Regards > Mesut G=FCnes >=20 > PS: Further information aobut our work you'll find via: > http://www.adhoc-nets.de >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 ------=_NextPart_000_002F_01C26AC8.EC99A190 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
Ravi Prakash and I = have a paper=20 titled "IP Address Assignment in a Mobile Ad Hoc Network". It will = appear in the=20 MILCOM 2002 conference next week. The solution is based on the idea of = "buddy=20 list" data structure used for memory management.
 
There is another = paper by Sanket=20 Nasergi and Ravi Prakash titled "MANETconf: Configuration of Hosts in a = Mobile=20 Ad Hoc Network". It appeared in INFOCOM 2002. You can download this = paper from=20 http://www.utdallas.edu/~ravip/<= /A>.

Mansoor = Mohsin=20
 
 
----- Original Message -----
From: "Mesut GXnes" <mesut@i4.informatik.rwth-aachen.de>
To: <manet@ietf.org>
Sent: Wednesday, October 02, 2002 = 10:29=20 AM
Subject: AW: [manet] ip address=20 allocation

> Hi,
>
> ###I have a question in regards to ip = address=20 allocation in an
> ###ad hoc environment. In an ad hoc = environment=20 presumely ip
> ###addresses will be allocated dynamically to new = nodes as=20 they
> ###attach themselves to the network.
> ###
> = ###Is=20 there much research out there into how exactly this will be done. =
> ###I=20 know in a normal network it can be done through a dhcp
> = ###server, but=20 in an ad hoc environment you cant really assume
> ###a dhcp = server will=20 be available.
>
> We have proposed a distributed dynamic=20 configuration algorithm for
> mobile
> multi-hop ad-hoc = networks=20 which do not require human interaction. Our
> aim
> was to=20 introduce a mechanism which is also able to recognize the
> = splitting=20
> and merging of several ad-hoc networks.
>
> In our = paper=20 we have tried to give an overview about existing dynamic
> = addressing=20 approaches (DHCP, Zero Configuration, Auto-Configuration,
> ...). =
>=20 Additionally, you'll find a performance comparison of our own = approach
>=20 and  DHCP and Auto-Configuration. All results are obtained over=20 ns-2.
>
> Paper:
> ------
> Mesut G=FCnes and = J=F6rg=20 Reibel.
> An ip address configuration algorithm for zeroconf. = mobile=20 multi-hop
> ad-hoc networks.
> In Proceedings of the = International=20 Workshop on Broadband Wireless
> Ad-Hoc Networks and Services, = Sophia=20 Antipolis, France, September 2002.
> ETSI.
>
> =
> The=20 paper is also electronically available via:
> http://www.projectmesa.org/workshop2002/agenda.htm>
>
>
> Regards
> = Mesut=20 G=FCnes
>
> PS: Further information aobut our work you'll = find=20 via:
> http://www.adhoc-nets.de
>=20
> _______________________________________________
> manet = mailing=20 list
> manet@ietf.org
> = https://www1.ietf.org/mailman/listinfo/manet
> ------=_NextPart_000_002F_01C26AC8.EC99A190-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 3 11:55:06 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20238 for ; Thu, 3 Oct 2002 11:55:05 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g93Fudt29654 for manet-archive@odin.ietf.org; Thu, 3 Oct 2002 11:56:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Fudv29651 for ; Thu, 3 Oct 2002 11:56:39 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20202 for ; Thu, 3 Oct 2002 11:54:34 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Fd6v28606; Thu, 3 Oct 2002 11:39:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Fbwv28429 for ; Thu, 3 Oct 2002 11:37:58 -0400 Received: from ns0.utdallas.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18664 for ; Thu, 3 Oct 2002 11:35:53 -0400 (EDT) Received: from DSL08 (dsl08.utdallas.edu [129.110.94.81]) by ns0.utdallas.edu (Postfix) with SMTP id 0503E1A1A55 for ; Thu, 3 Oct 2002 10:37:51 -0500 (CDT) Message-ID: <003201c26af2$d59f6c20$515e6e81@campus.ad.utdallas.edu> From: "Mansoor Mohsin" To: References: <00bd01c26a28$841f11e0$d00ce289@informatik.rwthaachen.de> Subject: Re: [manet] ip address allocation Date: Thu, 3 Oct 2002 10:37:51 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002F_01C26AC8.EC99A190" 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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_002F_01C26AC8.EC99A190 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Ravi Prakash and I have a paper titled "IP Address Assignment in a = Mobile Ad Hoc Network". It will appear in the MILCOM 2002 conference = next week. The solution is based on the idea of "buddy list" data = structure used for memory management. There is another paper by Sanket Nasergi and Ravi Prakash titled = "MANETconf: Configuration of Hosts in a Mobile Ad Hoc Network". It = appeared in INFOCOM 2002. You can download this paper from = http://www.utdallas.edu/~ravip/. -------------------------------------------------------------------------= ------- Mansoor Mohsin=20 ----- Original Message -----=20 From: "Mesut GXnes" To: Sent: Wednesday, October 02, 2002 10:29 AM Subject: AW: [manet] ip address allocation > Hi, >=20 > ###I have a question in regards to ip address allocation in an=20 > ###ad hoc environment. In an ad hoc environment presumely ip=20 > ###addresses will be allocated dynamically to new nodes as they=20 > ###attach themselves to the network. > ### > ###Is there much research out there into how exactly this will be = done.=20 > ###I know in a normal network it can be done through a dhcp=20 > ###server, but in an ad hoc environment you cant really assume=20 > ###a dhcp server will be available. >=20 > We have proposed a distributed dynamic configuration algorithm for > mobile=20 > multi-hop ad-hoc networks which do not require human interaction. Our > aim=20 > was to introduce a mechanism which is also able to recognize the > splitting=20 > and merging of several ad-hoc networks. >=20 > In our paper we have tried to give an overview about existing dynamic=20 > addressing approaches (DHCP, Zero Configuration, Auto-Configuration, > ...).=20 > Additionally, you'll find a performance comparison of our own approach > and DHCP and Auto-Configuration. All results are obtained over ns-2. >=20 > Paper: > ------ > Mesut G=FCnes and J=F6rg Reibel.=20 > An ip address configuration algorithm for zeroconf. mobile multi-hop > ad-hoc networks.=20 > In Proceedings of the International Workshop on Broadband Wireless > Ad-Hoc Networks and Services, Sophia Antipolis, France, September = 2002. > ETSI. >=20 >=20 > The paper is also electronically available via: > http://www.projectmesa.org/workshop2002/agenda.htm >=20 >=20 >=20 > Regards > Mesut G=FCnes >=20 > PS: Further information aobut our work you'll find via: > http://www.adhoc-nets.de >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 ------=_NextPart_000_002F_01C26AC8.EC99A190 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
Ravi Prakash and I = have a paper=20 titled "IP Address Assignment in a Mobile Ad Hoc Network". It will = appear in the=20 MILCOM 2002 conference next week. The solution is based on the idea of = "buddy=20 list" data structure used for memory management.
 
There is another = paper by Sanket=20 Nasergi and Ravi Prakash titled "MANETconf: Configuration of Hosts in a = Mobile=20 Ad Hoc Network". It appeared in INFOCOM 2002. You can download this = paper from=20 http://www.utdallas.edu/~ravip/<= /A>.

Mansoor = Mohsin=20
 
 
----- Original Message -----
From: "Mesut GXnes" <mesut@i4.informatik.rwth-aachen.de>
To: <manet@ietf.org>
Sent: Wednesday, October 02, 2002 = 10:29=20 AM
Subject: AW: [manet] ip address=20 allocation

> Hi,
>
> ###I have a question in regards to ip = address=20 allocation in an
> ###ad hoc environment. In an ad hoc = environment=20 presumely ip
> ###addresses will be allocated dynamically to new = nodes as=20 they
> ###attach themselves to the network.
> ###
> = ###Is=20 there much research out there into how exactly this will be done. =
> ###I=20 know in a normal network it can be done through a dhcp
> = ###server, but=20 in an ad hoc environment you cant really assume
> ###a dhcp = server will=20 be available.
>
> We have proposed a distributed dynamic=20 configuration algorithm for
> mobile
> multi-hop ad-hoc = networks=20 which do not require human interaction. Our
> aim
> was to=20 introduce a mechanism which is also able to recognize the
> = splitting=20
> and merging of several ad-hoc networks.
>
> In our = paper=20 we have tried to give an overview about existing dynamic
> = addressing=20 approaches (DHCP, Zero Configuration, Auto-Configuration,
> ...). =
>=20 Additionally, you'll find a performance comparison of our own = approach
>=20 and  DHCP and Auto-Configuration. All results are obtained over=20 ns-2.
>
> Paper:
> ------
> Mesut G=FCnes and = J=F6rg=20 Reibel.
> An ip address configuration algorithm for zeroconf. = mobile=20 multi-hop
> ad-hoc networks.
> In Proceedings of the = International=20 Workshop on Broadband Wireless
> Ad-Hoc Networks and Services, = Sophia=20 Antipolis, France, September 2002.
> ETSI.
>
> =
> The=20 paper is also electronically available via:
> http://www.projectmesa.org/workshop2002/agenda.htm>
>
>
> Regards
> = Mesut=20 G=FCnes
>
> PS: Further information aobut our work you'll = find=20 via:
> http://www.adhoc-nets.de
>=20
> _______________________________________________
> manet = mailing=20 list
> manet@ietf.org
> = https://www1.ietf.org/mailman/listinfo/manet
> ------=_NextPart_000_002F_01C26AC8.EC99A190-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 3 14:00:15 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28101 for ; Thu, 3 Oct 2002 14:00:15 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g93I1mx05590 for manet-archive@odin.ietf.org; Thu, 3 Oct 2002 14:01:48 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93I1mv05587 for ; Thu, 3 Oct 2002 14:01:48 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28057 for ; Thu, 3 Oct 2002 13:59:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Hfgv04867; Thu, 3 Oct 2002 13:41:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93HXwv04048 for ; Thu, 3 Oct 2002 13:33:58 -0400 Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26716 for ; Thu, 3 Oct 2002 13:31:54 -0400 (EDT) Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA12433 for ; Thu, 3 Oct 2002 10:33:53 -0700 (PDT) X-Delivered-For: Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g93HXrJ12919; Thu, 3 Oct 2002 10:33:53 -0700 X-mProtect: <200210031733> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdirTe0J; Thu, 03 Oct 2002 10:33:51 PDT Message-ID: <3D9C7F7F.209CCD0A@iprg.nokia.com> Date: Thu, 03 Oct 2002 10:33:51 -0700 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mobile Ad Hoc IETF working group CC: Rajeev Koodli Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Service Discovery in On-Demand Ad Hoc Networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello folks, Rajeev and I have specified a mechanism by which services can be discovered in an ad hoc network. Our document has been submitted to the IETF drafts directories, but in the meantime it is available at the following URL: http://people.nokia.net/charliep/txt/aodvid/manetsrv.txt The draft seems to be missing an abstract, an omission I can quickly repair, but here is the first paragraph of the introduction: In this document, we describe extensions to suitable ad hoc network routing protocols in order to provide support for service discovery. Typical Internet applications require information such as name resolution, a web proxy IP address, access to print services etc. While [manet] protocols have focussed on providing basic routing support for communication, this document addresses the problem of discovering services along with routes to those services. Regards, Charlie P. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 3 14:00:28 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28119 for ; Thu, 3 Oct 2002 14:00:28 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93Hfgv04867; Thu, 3 Oct 2002 13:41:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93HXwv04048 for ; Thu, 3 Oct 2002 13:33:58 -0400 Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26716 for ; Thu, 3 Oct 2002 13:31:54 -0400 (EDT) Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id KAA12433 for ; Thu, 3 Oct 2002 10:33:53 -0700 (PDT) X-Delivered-For: Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g93HXrJ12919; Thu, 3 Oct 2002 10:33:53 -0700 X-mProtect: <200210031733> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdirTe0J; Thu, 03 Oct 2002 10:33:51 PDT Message-ID: <3D9C7F7F.209CCD0A@iprg.nokia.com> Date: Thu, 03 Oct 2002 10:33:51 -0700 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mobile Ad Hoc IETF working group CC: Rajeev Koodli Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Service Discovery in On-Demand Ad Hoc Networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hello folks, Rajeev and I have specified a mechanism by which services can be discovered in an ad hoc network. Our document has been submitted to the IETF drafts directories, but in the meantime it is available at the following URL: http://people.nokia.net/charliep/txt/aodvid/manetsrv.txt The draft seems to be missing an abstract, an omission I can quickly repair, but here is the first paragraph of the introduction: In this document, we describe extensions to suitable ad hoc network routing protocols in order to provide support for service discovery. Typical Internet applications require information such as name resolution, a web proxy IP address, access to print services etc. While [manet] protocols have focussed on providing basic routing support for communication, this document addresses the problem of discovering services along with routes to those services. Regards, Charlie P. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 4 04:24:58 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25899 for ; Fri, 4 Oct 2002 04:24:58 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g948Otv23966; Fri, 4 Oct 2002 04:24:55 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g948Mkv23907 for ; Fri, 4 Oct 2002 04:22:46 -0400 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25771 for ; Fri, 4 Oct 2002 04:20:30 -0400 (EDT) Received: from cit.ie (unverified [157.190.41.59]) by cit.ie (Rockliffe SMTPRA 5.2.3) with ESMTP id for ; Fri, 4 Oct 2002 09:21:05 +0100 Message-ID: <3D9D508D.EB4B7B70@cit.ie> Date: Fri, 04 Oct 2002 09:25:49 +0100 From: srea X-Mailer: Mozilla 4.79 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "manet@ietf.org" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] AODV & TTL Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, How is the TTL value of a RREQ in AODV decided and what decides the threshold value beyond which a RREQ is broadcast over the complete network? Regards, Susan Rea -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 4 04:26:13 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25965 for ; Fri, 4 Oct 2002 04:26:13 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g948Q6v24019; Fri, 4 Oct 2002 04:26:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g948Ocv23950 for ; Fri, 4 Oct 2002 04:24:38 -0400 Received: from i4mail.informatik.rwth-aachen.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25867 for ; Fri, 4 Oct 2002 04:22:26 -0400 (EDT) Received: from yigit (yigit.informatik.rwth-aachen.de [137.226.12.208]) by i4mail.informatik.rwth-aachen.de (RWTH i4) with ESMTP id 0284E9C126; Fri, 4 Oct 2002 09:30:31 +0200 (CEST) From: "Mesut Günes" To: "'Ankur Jain'" , Subject: AW: [manet] ip address allocation Date: Fri, 4 Oct 2002 10:24:25 +0200 Organization: Lehrstuhl für Informatik 4, RWTH-Aachen Message-ID: <00ee01c26b7f$7304aca0$d00ce289@informatik.rwthaachen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <009c01c26aea$9a6e3300$c10310ac@icr.astar.edu.sg> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g948Odv23951 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi, you can download the PDF document via the following URL: http://www.adhoc-nets.de/paper/2002_Addressing.pdf Regards Mesut Günes ###Hi ### ###Your paper is not available on your website. I could only ###find the presentation. ### ###Could you please provide the actual paper also? ### ###Regards ###Ankur ### ### ### ### ### ###----- Original Message ----- ###From: Mesut Günes ###To: ###Sent: Wednesday, October 02, 2002 11:29 PM ###Subject: AW: [manet] ip address allocation ### ### ###> Hi, ###> ###> ###I have a question in regards to ip address allocation ###in an ###ad ###> hoc environment. In an ad hoc environment presumely ip ######addresses ###> will be allocated dynamically to new nodes as they ###attach ###> themselves to the network. ### ###> ###Is there much research out there into how exactly this ###will be done. ###> ###I know in a normal network it can be done through a dhcp ###> ###server, but in an ad hoc environment you cant really assume ###> ###a dhcp server will be available. ###> ###> We have proposed a distributed dynamic configuration algorithm for ###> mobile multi-hop ad-hoc networks which do not require human ###> interaction. Our aim ###> was to introduce a mechanism which is also able to recognize the ###> splitting ###> and merging of several ad-hoc networks. ###> ###> In our paper we have tried to give an overview about ###existing dynamic ###> addressing approaches (DHCP, Zero Configuration, ###Auto-Configuration, ###> ...). Additionally, you'll find a performance comparison ###of our own ###> approach and DHCP and Auto-Configuration. All results are ###obtained ###> over ns-2. ###> ###> Paper: ###> ------ ###> Mesut Günes and Jörg Reibel. ###> An ip address configuration algorithm for zeroconf. mobile ###multi-hop ###> ad-hoc networks. In Proceedings of the International Workshop on ###> Broadband Wireless Ad-Hoc Networks and Services, Sophia Antipolis, ###> France, September 2002. ETSI. ###> ###> ###> The paper is also electronically available via: ###> http://www.projectmesa.org/workshop2002/agenda.htm ###> ###> ###> ###> Regards ###> Mesut Günes ###> ###> PS: Further information aobut our work you'll find via: ###> http://www.adhoc-nets.de ###> ###> _______________________________________________ ###> manet mailing list ###> manet@ietf.org ###> https://www1.ietf.org/mailman/listinfo/manet ### ###_______________________________________________ ###manet mailing list ###manet@ietf.org ###https://www1.ietf.org/mailman/listinfo/manet ### _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 4 04:31:23 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26071 for ; Fri, 4 Oct 2002 04:31:18 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g948WwC24335 for manet-archive@odin.ietf.org; Fri, 4 Oct 2002 04:32:58 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g948Wwv24332 for ; Fri, 4 Oct 2002 04:32:58 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26053 for ; Fri, 4 Oct 2002 04:30:47 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g948Q6v24019; Fri, 4 Oct 2002 04:26:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g948Ocv23950 for ; Fri, 4 Oct 2002 04:24:38 -0400 Received: from i4mail.informatik.rwth-aachen.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25867 for ; Fri, 4 Oct 2002 04:22:26 -0400 (EDT) Received: from yigit (yigit.informatik.rwth-aachen.de [137.226.12.208]) by i4mail.informatik.rwth-aachen.de (RWTH i4) with ESMTP id 0284E9C126; Fri, 4 Oct 2002 09:30:31 +0200 (CEST) From: "Mesut Günes" To: "'Ankur Jain'" , Subject: AW: [manet] ip address allocation Date: Fri, 4 Oct 2002 10:24:25 +0200 Organization: Lehrstuhl für Informatik 4, RWTH-Aachen Message-ID: <00ee01c26b7f$7304aca0$d00ce289@informatik.rwthaachen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <009c01c26aea$9a6e3300$c10310ac@icr.astar.edu.sg> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g948Odv23951 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, you can download the PDF document via the following URL: http://www.adhoc-nets.de/paper/2002_Addressing.pdf Regards Mesut Günes ###Hi ### ###Your paper is not available on your website. I could only ###find the presentation. ### ###Could you please provide the actual paper also? ### ###Regards ###Ankur ### ### ### ### ### ###----- Original Message ----- ###From: Mesut Günes ###To: ###Sent: Wednesday, October 02, 2002 11:29 PM ###Subject: AW: [manet] ip address allocation ### ### ###> Hi, ###> ###> ###I have a question in regards to ip address allocation ###in an ###ad ###> hoc environment. In an ad hoc environment presumely ip ######addresses ###> will be allocated dynamically to new nodes as they ###attach ###> themselves to the network. ### ###> ###Is there much research out there into how exactly this ###will be done. ###> ###I know in a normal network it can be done through a dhcp ###> ###server, but in an ad hoc environment you cant really assume ###> ###a dhcp server will be available. ###> ###> We have proposed a distributed dynamic configuration algorithm for ###> mobile multi-hop ad-hoc networks which do not require human ###> interaction. Our aim ###> was to introduce a mechanism which is also able to recognize the ###> splitting ###> and merging of several ad-hoc networks. ###> ###> In our paper we have tried to give an overview about ###existing dynamic ###> addressing approaches (DHCP, Zero Configuration, ###Auto-Configuration, ###> ...). Additionally, you'll find a performance comparison ###of our own ###> approach and DHCP and Auto-Configuration. All results are ###obtained ###> over ns-2. ###> ###> Paper: ###> ------ ###> Mesut Günes and Jörg Reibel. ###> An ip address configuration algorithm for zeroconf. mobile ###multi-hop ###> ad-hoc networks. In Proceedings of the International Workshop on ###> Broadband Wireless Ad-Hoc Networks and Services, Sophia Antipolis, ###> France, September 2002. ETSI. ###> ###> ###> The paper is also electronically available via: ###> http://www.projectmesa.org/workshop2002/agenda.htm ###> ###> ###> ###> Regards ###> Mesut Günes ###> ###> PS: Further information aobut our work you'll find via: ###> http://www.adhoc-nets.de ###> ###> _______________________________________________ ###> manet mailing list ###> manet@ietf.org ###> https://www1.ietf.org/mailman/listinfo/manet ### ###_______________________________________________ ###manet mailing list ###manet@ietf.org ###https://www1.ietf.org/mailman/listinfo/manet ### _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 4 04:34:01 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26115 for ; Fri, 4 Oct 2002 04:34:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g948Zgw24443 for manet-archive@odin.ietf.org; Fri, 4 Oct 2002 04:35:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g948Zgv24440 for ; Fri, 4 Oct 2002 04:35:42 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26105 for ; Fri, 4 Oct 2002 04:33:30 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g948Otv23966; Fri, 4 Oct 2002 04:24:55 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g948Mkv23907 for ; Fri, 4 Oct 2002 04:22:46 -0400 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25771 for ; Fri, 4 Oct 2002 04:20:30 -0400 (EDT) Received: from cit.ie (unverified [157.190.41.59]) by cit.ie (Rockliffe SMTPRA 5.2.3) with ESMTP id for ; Fri, 4 Oct 2002 09:21:05 +0100 Message-ID: <3D9D508D.EB4B7B70@cit.ie> Date: Fri, 04 Oct 2002 09:25:49 +0100 From: srea X-Mailer: Mozilla 4.79 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "manet@ietf.org" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] AODV & TTL Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, How is the TTL value of a RREQ in AODV decided and what decides the threshold value beyond which a RREQ is broadcast over the complete network? Regards, Susan Rea -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 4 05:23:54 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26876 for ; Fri, 4 Oct 2002 05:23:54 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g949PPT27081 for manet-archive@odin.ietf.org; Fri, 4 Oct 2002 05:25:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g949PPv27078 for ; Fri, 4 Oct 2002 05:25:25 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26867 for ; Fri, 4 Oct 2002 05:23:23 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g949Niv27034; Fri, 4 Oct 2002 05:23:44 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g949MUv26992 for ; Fri, 4 Oct 2002 05:22:30 -0400 Received: from goliath.siemens.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26844 for ; Fri, 4 Oct 2002 05:20:27 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g949MGl17928; Fri, 4 Oct 2002 11:22:16 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g949MEQ28966; Fri, 4 Oct 2002 11:22:14 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g949MEIu027693; Fri, 4 Oct 2002 11:22:14 +0200 (MET DST) Message-ID: <3D9D5F02.E376CAD@mchp.siemens.de> Date: Fri, 04 Oct 2002 11:27:30 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Zhenqiang(Frank) Ye" CC: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Subject: Re: [manet] Question about traces (r,s,f,d)?? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, of course I can see this event although the RTR traces are disabled. When a packet is deleted, I get notification in the trace line at the router level. It's the only RTR traces I get when these are disabled. "Zhenqiang(Frank) Ye" wrote: > I don't think you can see the packet "DELETE" event in your trace file if > you turn off the RTR trace. > > Frank > > On Wed, 2 Oct 2002, Riadh Marrakchi wrote: > > > Hi, > > the RTR Traces are set off in my simulation scripts, so that i get only the > > AGT traces. > > > > "Zhenqiang(Frank) Ye" wrote: > > > > > You can not use the method you described. See the example below: > > > (The transport and IP layer trace are ON) > > > s 2.199994566 _1_ AGT --- 6 cbr .... > > > r 2.199994566 _1_ RTR --- 6 cbr .... > > > s 2.199994566 _1_ RTR --- 6 cbr .... > > > r 2.200547959 _2_ RTR --- 6 cbr .... > > > f 2.200547959 _2_ RTR --- 6 cbr .... > > > r 2.201817971 _3_ AGT --- 6 cbr .... > > > > > > The packet 6 is marked "cbr" all the time. It is sent by node 1 two > > > times (at different layers), and is received 3 times (by different nodes > > > and different layers). That is why your method does not work. In order > > > to compute correctly, you need to add "AGT" in your filter when you cout > > > the number of packets "sent" and "received". > > > > > > Hope it helps, > > > > > > Zhenqiang(Frank) > > > > > > On Tue, 1 Oct 2002, Riadh Marrakchi wrote: > > > > > > > Hi, > > > > the first column of the trace files (new traces) of the AODV simulation > > > > just confused me a little bit. > > > > s: is written once when the source sends a packet > > > > d: when a packet is dropped by some node (this line is also found only > > > > one time in the trace file when a packet is dropped) > > > > r: when a packet arrives at the destination > > > > f: when a packet is forwarded by some node. > > > > so let's assume node 1 tries to send a packet to node 3 through node 2. > > > > Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it > > > > and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first > > > > receives ("r") the packet then forward it ("f")???? > > > > Normally we would get: Total of sent cbr packets = total of dropped cbr > > > > packets + total of received cbr packets. But while analysing my trace > > > > files i get: Total of sent cbr packets < total of dropped cbr packets + > > > > total of received cbr packets. Although the difference is not that big, > > > > i would know how it exists??? > > > > Total of sent cbr packets: Lines with s at the beginning and cbr as > > > > packet type > > > > total of dropped cbr packets: Lines with d at the beginning and cbr as > > > > packet type > > > > total of received cbr packets:Lines with r at the beginning and cbr as > > > > packet type > > > > > > > > Thanks a lot for any help or comment. > > > > Riadh > > > > > > > > > > > > > > > > _______________________________________________ > > > > manet mailing list > > > > manet@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > > > -- > > > > > > **************************************** > > > Zhenqiang(Frank) Ye > > > Ph.D Student > > > Department of Electrical Engineering > > > University of California, Riverside > > > Phone: (909)-787-2434 > > > email: zye@cs.ucr.edu > > > **************************************** > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > -- > > **************************************** > Zhenqiang(Frank) Ye > Ph.D Student > Department of Electrical Engineering > University of California, Riverside > Phone: (909)-787-2434 > email: zye@cs.ucr.edu > **************************************** > > _______________________________________________ > 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-admin@ietf.org Fri Oct 4 05:27:05 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26935 for ; Fri, 4 Oct 2002 05:27:05 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g949Niv27034; Fri, 4 Oct 2002 05:23:44 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g949MUv26992 for ; Fri, 4 Oct 2002 05:22:30 -0400 Received: from goliath.siemens.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26844 for ; Fri, 4 Oct 2002 05:20:27 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g949MGl17928; Fri, 4 Oct 2002 11:22:16 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g949MEQ28966; Fri, 4 Oct 2002 11:22:14 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g949MEIu027693; Fri, 4 Oct 2002 11:22:14 +0200 (MET DST) Message-ID: <3D9D5F02.E376CAD@mchp.siemens.de> Date: Fri, 04 Oct 2002 11:27:30 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Zhenqiang(Frank) Ye" CC: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Subject: Re: [manet] Question about traces (r,s,f,d)?? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, of course I can see this event although the RTR traces are disabled. When a packet is deleted, I get notification in the trace line at the router level. It's the only RTR traces I get when these are disabled. "Zhenqiang(Frank) Ye" wrote: > I don't think you can see the packet "DELETE" event in your trace file if > you turn off the RTR trace. > > Frank > > On Wed, 2 Oct 2002, Riadh Marrakchi wrote: > > > Hi, > > the RTR Traces are set off in my simulation scripts, so that i get only the > > AGT traces. > > > > "Zhenqiang(Frank) Ye" wrote: > > > > > You can not use the method you described. See the example below: > > > (The transport and IP layer trace are ON) > > > s 2.199994566 _1_ AGT --- 6 cbr .... > > > r 2.199994566 _1_ RTR --- 6 cbr .... > > > s 2.199994566 _1_ RTR --- 6 cbr .... > > > r 2.200547959 _2_ RTR --- 6 cbr .... > > > f 2.200547959 _2_ RTR --- 6 cbr .... > > > r 2.201817971 _3_ AGT --- 6 cbr .... > > > > > > The packet 6 is marked "cbr" all the time. It is sent by node 1 two > > > times (at different layers), and is received 3 times (by different nodes > > > and different layers). That is why your method does not work. In order > > > to compute correctly, you need to add "AGT" in your filter when you cout > > > the number of packets "sent" and "received". > > > > > > Hope it helps, > > > > > > Zhenqiang(Frank) > > > > > > On Tue, 1 Oct 2002, Riadh Marrakchi wrote: > > > > > > > Hi, > > > > the first column of the trace files (new traces) of the AODV simulation > > > > just confused me a little bit. > > > > s: is written once when the source sends a packet > > > > d: when a packet is dropped by some node (this line is also found only > > > > one time in the trace file when a packet is dropped) > > > > r: when a packet arrives at the destination > > > > f: when a packet is forwarded by some node. > > > > so let's assume node 1 tries to send a packet to node 3 through node 2. > > > > Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it > > > > and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first > > > > receives ("r") the packet then forward it ("f")???? > > > > Normally we would get: Total of sent cbr packets = total of dropped cbr > > > > packets + total of received cbr packets. But while analysing my trace > > > > files i get: Total of sent cbr packets < total of dropped cbr packets + > > > > total of received cbr packets. Although the difference is not that big, > > > > i would know how it exists??? > > > > Total of sent cbr packets: Lines with s at the beginning and cbr as > > > > packet type > > > > total of dropped cbr packets: Lines with d at the beginning and cbr as > > > > packet type > > > > total of received cbr packets:Lines with r at the beginning and cbr as > > > > packet type > > > > > > > > Thanks a lot for any help or comment. > > > > Riadh > > > > > > > > > > > > > > > > _______________________________________________ > > > > manet mailing list > > > > manet@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > > > -- > > > > > > **************************************** > > > Zhenqiang(Frank) Ye > > > Ph.D Student > > > Department of Electrical Engineering > > > University of California, Riverside > > > Phone: (909)-787-2434 > > > email: zye@cs.ucr.edu > > > **************************************** > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > -- > > **************************************** > Zhenqiang(Frank) Ye > Ph.D Student > Department of Electrical Engineering > University of California, Riverside > Phone: (909)-787-2434 > email: zye@cs.ucr.edu > **************************************** > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 4 13:30:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14241 for ; Fri, 4 Oct 2002 13:30:30 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g94HW5821940 for manet-archive@odin.ietf.org; Fri, 4 Oct 2002 13:32:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g94HW5v21937 for ; Fri, 4 Oct 2002 13:32:05 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14199 for ; Fri, 4 Oct 2002 13:29:58 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g94HUFv21810; Fri, 4 Oct 2002 13:30:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g94HLGv21502 for ; Fri, 4 Oct 2002 13:21:16 -0400 Received: from barrichello.cs.ucr.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13895 for ; Fri, 4 Oct 2002 13:19:09 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id 4467CAB598D0; Fri, 4 Oct 2002 10:21:10 -0700 (PDT) Mailbox-Line: From zye@cs.ucr.edu Fri Oct 4 10:21:05 2002 Received: from io.cs.ucr.edu (io.cs.ucr.edu [138.23.174.180]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id 01E9CAB598DC; Fri, 4 Oct 2002 10:21:05 -0700 (PDT) Received: by io.cs.ucr.edu (Postfix, from userid 7296) id A0EE825924; Fri, 4 Oct 2002 10:21:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by io.cs.ucr.edu (Postfix) with ESMTP id 944D025864; Fri, 4 Oct 2002 10:21:04 -0700 (PDT) Date: Fri, 4 Oct 2002 10:21:04 -0700 (PDT) From: "Zhenqiang(Frank) Ye" To: Riadh Marrakchi Cc: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Subject: Re: [manet] Question about traces (r,s,f,d)?? In-Reply-To: <3D9D5F02.E376CAD@mchp.siemens.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-1.9 required=5.0 tests=IN_REP_TO,SUBJ_ENDS_IN_Q_MARK,DOUBLE_CAPSWORD, SIGNATURE_DELIM version=2.31 X-Virus-Scanned: by AMaViS perl-11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Sorry about that. It depends on different routing protocols. How much is the difference between the packets sent and packets received+dropped? Frank On Fri, 4 Oct 2002, Riadh Marrakchi wrote: > Hi, > of course I can see this event although the RTR traces are disabled. When a > packet is deleted, I get notification in the trace line at the router level. It's > the only RTR traces I get when these are disabled. > > "Zhenqiang(Frank) Ye" wrote: > > > I don't think you can see the packet "DELETE" event in your trace file if > > you turn off the RTR trace. > > > > Frank > > > > On Wed, 2 Oct 2002, Riadh Marrakchi wrote: > > > > > Hi, > > > the RTR Traces are set off in my simulation scripts, so that i get only the > > > AGT traces. > > > > > > "Zhenqiang(Frank) Ye" wrote: > > > > > > > You can not use the method you described. See the example below: > > > > (The transport and IP layer trace are ON) > > > > s 2.199994566 _1_ AGT --- 6 cbr .... > > > > r 2.199994566 _1_ RTR --- 6 cbr .... > > > > s 2.199994566 _1_ RTR --- 6 cbr .... > > > > r 2.200547959 _2_ RTR --- 6 cbr .... > > > > f 2.200547959 _2_ RTR --- 6 cbr .... > > > > r 2.201817971 _3_ AGT --- 6 cbr .... > > > > > > > > The packet 6 is marked "cbr" all the time. It is sent by node 1 two > > > > times (at different layers), and is received 3 times (by different nodes > > > > and different layers). That is why your method does not work. In order > > > > to compute correctly, you need to add "AGT" in your filter when you cout > > > > the number of packets "sent" and "received". > > > > > > > > Hope it helps, > > > > > > > > Zhenqiang(Frank) > > > > > > > > On Tue, 1 Oct 2002, Riadh Marrakchi wrote: > > > > > > > > > Hi, > > > > > the first column of the trace files (new traces) of the AODV simulation > > > > > just confused me a little bit. > > > > > s: is written once when the source sends a packet > > > > > d: when a packet is dropped by some node (this line is also found only > > > > > one time in the trace file when a packet is dropped) > > > > > r: when a packet arrives at the destination > > > > > f: when a packet is forwarded by some node. > > > > > so let's assume node 1 tries to send a packet to node 3 through node 2. > > > > > Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it > > > > > and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first > > > > > receives ("r") the packet then forward it ("f")???? > > > > > Normally we would get: Total of sent cbr packets = total of dropped cbr > > > > > packets + total of received cbr packets. But while analysing my trace > > > > > files i get: Total of sent cbr packets < total of dropped cbr packets + > > > > > total of received cbr packets. Although the difference is not that big, > > > > > i would know how it exists??? > > > > > Total of sent cbr packets: Lines with s at the beginning and cbr as > > > > > packet type > > > > > total of dropped cbr packets: Lines with d at the beginning and cbr as > > > > > packet type > > > > > total of received cbr packets:Lines with r at the beginning and cbr as > > > > > packet type > > > > > > > > > > Thanks a lot for any help or comment. > > > > > Riadh > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > manet mailing list > > > > > manet@ietf.org > > > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > > > > > > -- > > > > > > > > **************************************** > > > > Zhenqiang(Frank) Ye > > > > Ph.D Student > > > > Department of Electrical Engineering > > > > University of California, Riverside > > > > Phone: (909)-787-2434 > > > > email: zye@cs.ucr.edu > > > > **************************************** > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > -- > > > > **************************************** > > Zhenqiang(Frank) Ye > > Ph.D Student > > Department of Electrical Engineering > > University of California, Riverside > > Phone: (909)-787-2434 > > email: zye@cs.ucr.edu > > **************************************** > > > > _______________________________________________ > > 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 > -- **************************************** Zhenqiang(Frank) Ye Ph.D Student Department of Electrical Engineering University of California, Riverside Phone: (909)-787-2434 email: zye@cs.ucr.edu **************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 4 13:30:48 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14275 for ; Fri, 4 Oct 2002 13:30:48 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g94HUFv21810; Fri, 4 Oct 2002 13:30:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g94HLGv21502 for ; Fri, 4 Oct 2002 13:21:16 -0400 Received: from barrichello.cs.ucr.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13895 for ; Fri, 4 Oct 2002 13:19:09 -0400 (EDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id 4467CAB598D0; Fri, 4 Oct 2002 10:21:10 -0700 (PDT) Mailbox-Line: From zye@cs.ucr.edu Fri Oct 4 10:21:05 2002 Received: from io.cs.ucr.edu (io.cs.ucr.edu [138.23.174.180]) by barrichello.cs.ucr.edu (Postfix) with ESMTP id 01E9CAB598DC; Fri, 4 Oct 2002 10:21:05 -0700 (PDT) Received: by io.cs.ucr.edu (Postfix, from userid 7296) id A0EE825924; Fri, 4 Oct 2002 10:21:04 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by io.cs.ucr.edu (Postfix) with ESMTP id 944D025864; Fri, 4 Oct 2002 10:21:04 -0700 (PDT) Date: Fri, 4 Oct 2002 10:21:04 -0700 (PDT) From: "Zhenqiang(Frank) Ye" To: Riadh Marrakchi Cc: Aodvimpl-Public , "ns-users@isi.edu" , "manet@ietf.org" Subject: Re: [manet] Question about traces (r,s,f,d)?? In-Reply-To: <3D9D5F02.E376CAD@mchp.siemens.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=-1.9 required=5.0 tests=IN_REP_TO,SUBJ_ENDS_IN_Q_MARK,DOUBLE_CAPSWORD, SIGNATURE_DELIM version=2.31 X-Virus-Scanned: by AMaViS perl-11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Sorry about that. It depends on different routing protocols. How much is the difference between the packets sent and packets received+dropped? Frank On Fri, 4 Oct 2002, Riadh Marrakchi wrote: > Hi, > of course I can see this event although the RTR traces are disabled. When a > packet is deleted, I get notification in the trace line at the router level. It's > the only RTR traces I get when these are disabled. > > "Zhenqiang(Frank) Ye" wrote: > > > I don't think you can see the packet "DELETE" event in your trace file if > > you turn off the RTR trace. > > > > Frank > > > > On Wed, 2 Oct 2002, Riadh Marrakchi wrote: > > > > > Hi, > > > the RTR Traces are set off in my simulation scripts, so that i get only the > > > AGT traces. > > > > > > "Zhenqiang(Frank) Ye" wrote: > > > > > > > You can not use the method you described. See the example below: > > > > (The transport and IP layer trace are ON) > > > > s 2.199994566 _1_ AGT --- 6 cbr .... > > > > r 2.199994566 _1_ RTR --- 6 cbr .... > > > > s 2.199994566 _1_ RTR --- 6 cbr .... > > > > r 2.200547959 _2_ RTR --- 6 cbr .... > > > > f 2.200547959 _2_ RTR --- 6 cbr .... > > > > r 2.201817971 _3_ AGT --- 6 cbr .... > > > > > > > > The packet 6 is marked "cbr" all the time. It is sent by node 1 two > > > > times (at different layers), and is received 3 times (by different nodes > > > > and different layers). That is why your method does not work. In order > > > > to compute correctly, you need to add "AGT" in your filter when you cout > > > > the number of packets "sent" and "received". > > > > > > > > Hope it helps, > > > > > > > > Zhenqiang(Frank) > > > > > > > > On Tue, 1 Oct 2002, Riadh Marrakchi wrote: > > > > > > > > > Hi, > > > > > the first column of the trace files (new traces) of the AODV simulation > > > > > just confused me a little bit. > > > > > s: is written once when the source sends a packet > > > > > d: when a packet is dropped by some node (this line is also found only > > > > > one time in the trace file when a packet is dropped) > > > > > r: when a packet arrives at the destination > > > > > f: when a packet is forwarded by some node. > > > > > so let's assume node 1 tries to send a packet to node 3 through node 2. > > > > > Node 1 sends (first column: "s") the packet, node 2 forwards ("f") it > > > > > and node 3 receives ("r") it. Is it right??? I mean doesn't node 2 first > > > > > receives ("r") the packet then forward it ("f")???? > > > > > Normally we would get: Total of sent cbr packets = total of dropped cbr > > > > > packets + total of received cbr packets. But while analysing my trace > > > > > files i get: Total of sent cbr packets < total of dropped cbr packets + > > > > > total of received cbr packets. Although the difference is not that big, > > > > > i would know how it exists??? > > > > > Total of sent cbr packets: Lines with s at the beginning and cbr as > > > > > packet type > > > > > total of dropped cbr packets: Lines with d at the beginning and cbr as > > > > > packet type > > > > > total of received cbr packets:Lines with r at the beginning and cbr as > > > > > packet type > > > > > > > > > > Thanks a lot for any help or comment. > > > > > Riadh > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > manet mailing list > > > > > manet@ietf.org > > > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > > > > > > -- > > > > > > > > **************************************** > > > > Zhenqiang(Frank) Ye > > > > Ph.D Student > > > > Department of Electrical Engineering > > > > University of California, Riverside > > > > Phone: (909)-787-2434 > > > > email: zye@cs.ucr.edu > > > > **************************************** > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > -- > > > > **************************************** > > Zhenqiang(Frank) Ye > > Ph.D Student > > Department of Electrical Engineering > > University of California, Riverside > > Phone: (909)-787-2434 > > email: zye@cs.ucr.edu > > **************************************** > > > > _______________________________________________ > > 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 > -- **************************************** Zhenqiang(Frank) Ye Ph.D Student Department of Electrical Engineering University of California, Riverside Phone: (909)-787-2434 email: zye@cs.ucr.edu **************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Oct 5 09:39:20 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15862 for ; Sat, 5 Oct 2002 09:39:20 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g95Desl18133 for manet-archive@odin.ietf.org; Sat, 5 Oct 2002 09:40:54 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g95Desv18130 for ; Sat, 5 Oct 2002 09:40:54 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15848 for ; Sat, 5 Oct 2002 09:38:49 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g95DdRv18084; Sat, 5 Oct 2002 09:39:27 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g95Darv17474 for ; Sat, 5 Oct 2002 09:36:53 -0400 Received: from mail11.ntu.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15821 for ; Sat, 5 Oct 2002 09:34:47 -0400 (EDT) Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mail11.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Sat, 5 Oct 2002 21:17:31 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Date: Sat, 5 Oct 2002 21:17:30 +0800 Message-ID: <295CB338B611594582D82D9F26AEF7062CBED3@mail02.student.main.ntu.edu.sg> Thread-Topic: Integrating signal to noise ratio with GPS info.. Thread-Index: AcJscY8SVSVZ93xKQGSw1fj7OXRQTA== From: "#GUPTA ROHIT#" To: X-OriginalArrivalTime: 05 Oct 2002 13:17:31.0176 (UTC) FILETIME=[8F574280:01C26C71] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id g95Darv17475 Subject: [manet] Integrating signal to noise ratio with GPS info.. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Dear all, can anyone tell me whether there is any work done on the integration of SNR info in GPS based location based protocols. rgds, rohit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sat Oct 5 09:39:24 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15875 for ; Sat, 5 Oct 2002 09:39:23 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g95DdRv18084; Sat, 5 Oct 2002 09:39:27 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g95Darv17474 for ; Sat, 5 Oct 2002 09:36:53 -0400 Received: from mail11.ntu.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15821 for ; Sat, 5 Oct 2002 09:34:47 -0400 (EDT) Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mail11.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Sat, 5 Oct 2002 21:17:31 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Date: Sat, 5 Oct 2002 21:17:30 +0800 Message-ID: <295CB338B611594582D82D9F26AEF7062CBED3@mail02.student.main.ntu.edu.sg> Thread-Topic: Integrating signal to noise ratio with GPS info.. Thread-Index: AcJscY8SVSVZ93xKQGSw1fj7OXRQTA== From: "#GUPTA ROHIT#" To: X-OriginalArrivalTime: 05 Oct 2002 13:17:31.0176 (UTC) FILETIME=[8F574280:01C26C71] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id g95Darv17475 Subject: [manet] Integrating signal to noise ratio with GPS info.. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Dear all, can anyone tell me whether there is any work done on the integration of SNR info in GPS based location based protocols. rgds, rohit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 8 11:07:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17357 for ; Tue, 8 Oct 2002 11:07:06 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g98F8hN10154 for manet-archive@odin.ietf.org; Tue, 8 Oct 2002 11:08:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98F8hv10151 for ; Tue, 8 Oct 2002 11:08:43 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17345 for ; Tue, 8 Oct 2002 11:06:36 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98F6Qv09488; Tue, 8 Oct 2002 11:06:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98F1hv09330 for ; Tue, 8 Oct 2002 11:01:43 -0400 Received: from emily.cs.bham.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16957 for ; Tue, 8 Oct 2002 10:59:36 -0400 (EDT) Received: from preston.cs.bham.ac.uk by emily.cs.bham.ac.uk (Exim 3.11 #1) with esmtp id 17yvrQ-0002uv-00 for manet@ietf.org; Tue, 08 Oct 2002 16:01:24 +0100 Message-ID: <3DA2F350.AE8D28AE@cs.bham.ac.uk> Date: Tue, 08 Oct 2002 16:01:36 +0100 From: Sibusisiwe Chiyangwa Organization: School of Computer Science, The University of Birmingham, U.K. X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: manet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] REF: AODV (Updating and creating reverse/forward route) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I got this from draft-ietf-manet-aodv-11.txt. --Everytime a node receives a RREQ message, it first creates or updates a route to the previous node, increments the hop count, then goes on to create or update a route to the originator IP address.-- Instead of first creating a route to the Originator IP address with the previous node as the next hop en-route to the Originator, why create a route to the previous hop? Is this really necessary or we could by-pass that with the above suggestion. Sibusisiwe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 8 11:07:28 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17375 for ; Tue, 8 Oct 2002 11:07:28 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98F6Qv09488; Tue, 8 Oct 2002 11:06:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98F1hv09330 for ; Tue, 8 Oct 2002 11:01:43 -0400 Received: from emily.cs.bham.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16957 for ; Tue, 8 Oct 2002 10:59:36 -0400 (EDT) Received: from preston.cs.bham.ac.uk by emily.cs.bham.ac.uk (Exim 3.11 #1) with esmtp id 17yvrQ-0002uv-00 for manet@ietf.org; Tue, 08 Oct 2002 16:01:24 +0100 Message-ID: <3DA2F350.AE8D28AE@cs.bham.ac.uk> Date: Tue, 08 Oct 2002 16:01:36 +0100 From: Sibusisiwe Chiyangwa Organization: School of Computer Science, The University of Birmingham, U.K. X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: manet Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] REF: AODV (Updating and creating reverse/forward route) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I got this from draft-ietf-manet-aodv-11.txt. --Everytime a node receives a RREQ message, it first creates or updates a route to the previous node, increments the hop count, then goes on to create or update a route to the originator IP address.-- Instead of first creating a route to the Originator IP address with the previous node as the next hop en-route to the Originator, why create a route to the previous hop? Is this really necessary or we could by-pass that with the above suggestion. Sibusisiwe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 8 13:44:46 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23495 for ; Tue, 8 Oct 2002 13:44:46 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g98HkPJ19131 for manet-archive@odin.ietf.org; Tue, 8 Oct 2002 13:46:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98HkPv19128 for ; Tue, 8 Oct 2002 13:46:25 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23464 for ; Tue, 8 Oct 2002 13:44:15 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Hj7v19104; Tue, 8 Oct 2002 13:45:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Hb4v18407 for ; Tue, 8 Oct 2002 13:37:04 -0400 Received: from mail.engr.ucsb.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23237 for ; Tue, 8 Oct 2002 13:34:54 -0400 (EDT) Received: from voyageurs.cs.ucsb.edu ([128.111.40.92]:33693 helo=MESA.cs.ucsb.edu ident=idc) by mail.engr.ucsb.edu with esmtp (Exim 4.10) id 17yyHu-0006kx-00; Tue, 08 Oct 2002 10:36:54 -0700 From: MIME-Version: 1.0 Message-ID: <15779.6069.226000.387443@gargle.gargle.HOWL> Date: Tue, 8 Oct 2002 10:36:53 -0700 To: Sibusisiwe Chiyangwa Cc: manet In-Reply-To: <3DA2F350.AE8D28AE@cs.bham.ac.uk> References: <3DA2F350.AE8D28AE@cs.bham.ac.uk> X-Mailer: VM 7.07 under Emacs 21.1.1 Reply-To: idc@engineering.ucsb.edu Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: RE:[manet] REF: AODV (Updating and creating reverse/forward route) X-Spam-Status: No, hits=-2.9 required=8.0 tests=IN_REP_TO,NO_REAL_NAME version=2.31 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit When you receive a RREQ, you know the previous hop exists. Why not create a route to the previous hop? You could ignore this information. But you should take advantage of the knowledge. Ian Chakeres Sibusisiwe Chiyangwa writes: >I got this from draft-ietf-manet-aodv-11.txt. > >--Everytime a node receives a RREQ message, it first creates or updates >a route to the previous node, increments the hop count, then goes on to >create or update a route to the originator IP address.-- > >Instead of first creating a route to the Originator IP address with the >previous node as the next hop en-route to the Originator, why create a >route to the previous hop? Is this really necessary or we could by-pass >that with the above suggestion. > >Sibusisiwe >_______________________________________________ >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-admin@ietf.org Tue Oct 8 13:44:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23508 for ; Tue, 8 Oct 2002 13:44:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Hj7v19104; Tue, 8 Oct 2002 13:45:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Hb4v18407 for ; Tue, 8 Oct 2002 13:37:04 -0400 Received: from mail.engr.ucsb.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23237 for ; Tue, 8 Oct 2002 13:34:54 -0400 (EDT) Received: from voyageurs.cs.ucsb.edu ([128.111.40.92]:33693 helo=MESA.cs.ucsb.edu ident=idc) by mail.engr.ucsb.edu with esmtp (Exim 4.10) id 17yyHu-0006kx-00; Tue, 08 Oct 2002 10:36:54 -0700 From: MIME-Version: 1.0 Message-ID: <15779.6069.226000.387443@gargle.gargle.HOWL> Date: Tue, 8 Oct 2002 10:36:53 -0700 To: Sibusisiwe Chiyangwa Cc: manet In-Reply-To: <3DA2F350.AE8D28AE@cs.bham.ac.uk> References: <3DA2F350.AE8D28AE@cs.bham.ac.uk> X-Mailer: VM 7.07 under Emacs 21.1.1 Reply-To: idc@engineering.ucsb.edu Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: RE:[manet] REF: AODV (Updating and creating reverse/forward route) X-Spam-Status: No, hits=-2.9 required=8.0 tests=IN_REP_TO,NO_REAL_NAME version=2.31 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit When you receive a RREQ, you know the previous hop exists. Why not create a route to the previous hop? You could ignore this information. But you should take advantage of the knowledge. Ian Chakeres Sibusisiwe Chiyangwa writes: >I got this from draft-ietf-manet-aodv-11.txt. > >--Everytime a node receives a RREQ message, it first creates or updates >a route to the previous node, increments the hop count, then goes on to >create or update a route to the originator IP address.-- > >Instead of first creating a route to the Originator IP address with the >previous node as the next hop en-route to the Originator, why create a >route to the previous hop? Is this really necessary or we could by-pass >that with the above suggestion. > >Sibusisiwe >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 9 08:58:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13945 for ; Wed, 9 Oct 2002 08:58:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g99D0Uq19472 for manet-archive@odin.ietf.org; Wed, 9 Oct 2002 09:00:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99D0Uv19469 for ; Wed, 9 Oct 2002 09:00:30 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13924 for ; Wed, 9 Oct 2002 08:58:21 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Cwev19399; Wed, 9 Oct 2002 08:58:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Cu2v19310 for ; Wed, 9 Oct 2002 08:56:02 -0400 Received: from parsmtp1.rd.francetelecom.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13712 for ; Wed, 9 Oct 2002 08:53:53 -0400 (EDT) Received: from LANMHS20.rd.francetelecom.fr ([10.193.21.60]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.4905); Wed, 9 Oct 2002 14:55:58 +0200 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Wed, 9 Oct 2002 14:55:58 +0200 Message-ID: <0489A7888F080B4BA73B53F7E145F29ADE2B99@LANMHS20.rd.francetelecom.fr> Thread-Topic: IPV6 and Ad Hoc Network Thread-Index: AcGf0zKpFCfWbAuSEdazZwCAXxnaMDPvVGJAAACoHPA= From: "MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN" To: "manet" X-OriginalArrivalTime: 09 Oct 2002 12:55:58.0936 (UTC) FILETIME=[36C21580:01C26F93] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g99Cu2v19311 Subject: [manet] IPV6 and Ad Hoc Network Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, I have a question about the attribution of IP address within MANET with IPV6. Is it possible to assume that a client can acquire a public IP @ from any network operator, after this, the client can use this address any-where. Any comments? Sincerely _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 9 08:58:55 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13972 for ; Wed, 9 Oct 2002 08:58:55 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Cwev19399; Wed, 9 Oct 2002 08:58:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Cu2v19310 for ; Wed, 9 Oct 2002 08:56:02 -0400 Received: from parsmtp1.rd.francetelecom.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13712 for ; Wed, 9 Oct 2002 08:53:53 -0400 (EDT) Received: from LANMHS20.rd.francetelecom.fr ([10.193.21.60]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.4905); Wed, 9 Oct 2002 14:55:58 +0200 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Wed, 9 Oct 2002 14:55:58 +0200 Message-ID: <0489A7888F080B4BA73B53F7E145F29ADE2B99@LANMHS20.rd.francetelecom.fr> Thread-Topic: IPV6 and Ad Hoc Network Thread-Index: AcGf0zKpFCfWbAuSEdazZwCAXxnaMDPvVGJAAACoHPA= From: "MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN" To: "manet" X-OriginalArrivalTime: 09 Oct 2002 12:55:58.0936 (UTC) FILETIME=[36C21580:01C26F93] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g99Cu2v19311 Subject: [manet] IPV6 and Ad Hoc Network Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi, I have a question about the attribution of IP address within MANET with IPV6. Is it possible to assume that a client can acquire a public IP @ from any network operator, after this, the client can use this address any-where. Any comments? Sincerely _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 9 10:17:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18650 for ; Wed, 9 Oct 2002 10:17:25 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EGpv24718; Wed, 9 Oct 2002 10:16:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EASv24378 for ; Wed, 9 Oct 2002 10:10:28 -0400 Received: from trac.wsmr.army.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17929 for ; Wed, 9 Oct 2002 10:08:18 -0400 (EDT) Received: by gw.trac.wsmr.army.mil id <117121>; Wed, 9 Oct 2002 08:10:14 -0600 Message-Id: <02Oct9.081014mdt.117121@gw.trac.wsmr.army.mil> From: "Mullen, John P. (Contractor)" To: Sibusisiwe Chiyangwa Cc: manet Subject: RE: [manet] REF: AODV (Updating and creating reverse/forward rout e) Date: Wed, 9 Oct 2002 08:10:04 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Sibusisiwe, Please excuse me for breaking off our conversation yesterday, but something came up and I had to go. Let me relate the sequence of events, as I see it. When a node receives the RREQ, it stores the reverse path on that RREQ as a temporary route. This route will include the previous node. Then, the node checks the sequence number in the RREQ. If that RREQ is a duplicate of a previous RREQ, it dumps the RREQ and temporary route information. Forwarding the RREQ would be duplication and the presumption is that the route taken to deliver that earlier RREQ was probably a better one. If the RREQ is not a duplicate, the node forwards it. Then, the node looks at the temporary route back to the originator taken from that RREQ. One of four things will happen: 1. If the node does not already have a route back to the Originator, the reverse route in the RREQ is the only information the node has on that route, so it will make the temporary route the "official" route back to the Originator. 2. If the node already has a route back to the Originator in its tables, but that route is older (has a smaller sequence number), the node will replace that route with the fresher route in the RREQ. 3. If the node already has a route back to the Originator and its sequence number is the same as that in the RREQ, the node will pick the better of the two routes and store that as the "official" route. 4. If the node already has route back to the Originator and that route is newer (has a higher sequence number), the node will discard the temporary route and retain the original one. The end result is that the node attempts to determine a route back to the Originator on the basis of available information without initiating a RREQ of its own. John Mullen -----Original Message----- From: Sibusisiwe Chiyangwa [mailto:S.Chiyangwa@cs.bham.ac.uk] Sent: Tuesday, October 08, 2002 9:34 AM To: Mullen, John P. (Contractor) Subject: Re: [manet] REF: AODV (Updating and creating reverse/forward route) Mullen We are creating two reverse routes (1) to the previous hop (2) to the Originating node. WHY? It is suggested that you first create a reverse route to the previous node, then another reverse route to the Originating node. Obviously this reverse route to the Originating node has the previous hop as its next hop to the Originating node. Why then in the first place did we create a reverse route to the previous hop? The RREP will find its way to the Originating node because I have a reverse route to the Originating node with that previous node as the next hop to the Originating node. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 9 10:23:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19063 for ; Wed, 9 Oct 2002 10:23:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g99EP6125265 for manet-archive@odin.ietf.org; Wed, 9 Oct 2002 10:25:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EP6v25262 for ; Wed, 9 Oct 2002 10:25:06 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19052 for ; Wed, 9 Oct 2002 10:22:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EGpv24718; Wed, 9 Oct 2002 10:16:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EASv24378 for ; Wed, 9 Oct 2002 10:10:28 -0400 Received: from trac.wsmr.army.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17929 for ; Wed, 9 Oct 2002 10:08:18 -0400 (EDT) Received: by gw.trac.wsmr.army.mil id <117121>; Wed, 9 Oct 2002 08:10:14 -0600 Message-Id: <02Oct9.081014mdt.117121@gw.trac.wsmr.army.mil> From: "Mullen, John P. (Contractor)" To: Sibusisiwe Chiyangwa Cc: manet Subject: RE: [manet] REF: AODV (Updating and creating reverse/forward rout e) Date: Wed, 9 Oct 2002 08:10:04 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Sibusisiwe, Please excuse me for breaking off our conversation yesterday, but something came up and I had to go. Let me relate the sequence of events, as I see it. When a node receives the RREQ, it stores the reverse path on that RREQ as a temporary route. This route will include the previous node. Then, the node checks the sequence number in the RREQ. If that RREQ is a duplicate of a previous RREQ, it dumps the RREQ and temporary route information. Forwarding the RREQ would be duplication and the presumption is that the route taken to deliver that earlier RREQ was probably a better one. If the RREQ is not a duplicate, the node forwards it. Then, the node looks at the temporary route back to the originator taken from that RREQ. One of four things will happen: 1. If the node does not already have a route back to the Originator, the reverse route in the RREQ is the only information the node has on that route, so it will make the temporary route the "official" route back to the Originator. 2. If the node already has a route back to the Originator in its tables, but that route is older (has a smaller sequence number), the node will replace that route with the fresher route in the RREQ. 3. If the node already has a route back to the Originator and its sequence number is the same as that in the RREQ, the node will pick the better of the two routes and store that as the "official" route. 4. If the node already has route back to the Originator and that route is newer (has a higher sequence number), the node will discard the temporary route and retain the original one. The end result is that the node attempts to determine a route back to the Originator on the basis of available information without initiating a RREQ of its own. John Mullen -----Original Message----- From: Sibusisiwe Chiyangwa [mailto:S.Chiyangwa@cs.bham.ac.uk] Sent: Tuesday, October 08, 2002 9:34 AM To: Mullen, John P. (Contractor) Subject: Re: [manet] REF: AODV (Updating and creating reverse/forward route) Mullen We are creating two reverse routes (1) to the previous hop (2) to the Originating node. WHY? It is suggested that you first create a reverse route to the previous node, then another reverse route to the Originating node. Obviously this reverse route to the Originating node has the previous hop as its next hop to the Originating node. Why then in the first place did we create a reverse route to the previous hop? The RREP will find its way to the Originating node because I have a reverse route to the Originating node with that previous node as the next hop to the Originating node. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 9 11:07:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21151 for ; Wed, 9 Oct 2002 11:07:07 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99F5jv27891; Wed, 9 Oct 2002 11:05:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99F4Jv27815 for ; Wed, 9 Oct 2002 11:04:19 -0400 Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21033 for ; Wed, 9 Oct 2002 11:02:11 -0400 (EDT) Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA07445; Wed, 9 Oct 2002 08:04:14 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g99F4D529522; Wed, 9 Oct 2002 08:04:13 -0700 X-mProtect: <200210091504> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdJb8k1t; Wed, 09 Oct 2002 08:04:12 PDT Message-ID: <3DA4456D.4C5031BC@iprg.nokia.com> Date: Wed, 09 Oct 2002 08:04:13 -0700 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN CC: manet Subject: Re: [manet] IPV6 and Ad Hoc Network References: <0489A7888F080B4BA73B53F7E145F29ADE2B99@LANMHS20.rd.francetelecom.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hello, I believe most manet protocols intend to allow arbitrary addresses within the ad hoc network, so that would include a "public" IP address. Since IPv6 addresses are typically global, I'm not quite sure what "public" means in that connection. With Mobile IP, one can migrate smoothly back and forth between the Internet and an ad hoc network that has a point of connection to the Internet. Even without Mobile IP, one could presumably migrate, just not as smoothly. Regards, Charlie P. MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN wrote: > > Hi, > I have a question about the attribution of IP address within MANET with > IPV6. Is it possible to assume that a client can acquire a public IP @ > from any network operator, after this, the client can use this address > any-where. > > Any comments? > > Sincerely > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 9 11:10:43 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21283 for ; Wed, 9 Oct 2002 11:10:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g99FCKI28770 for manet-archive@odin.ietf.org; Wed, 9 Oct 2002 11:12:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99FCKv28767 for ; Wed, 9 Oct 2002 11:12:20 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21276 for ; Wed, 9 Oct 2002 11:10:12 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99F5jv27891; Wed, 9 Oct 2002 11:05:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99F4Jv27815 for ; Wed, 9 Oct 2002 11:04:19 -0400 Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21033 for ; Wed, 9 Oct 2002 11:02:11 -0400 (EDT) Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA07445; Wed, 9 Oct 2002 08:04:14 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g99F4D529522; Wed, 9 Oct 2002 08:04:13 -0700 X-mProtect: <200210091504> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdJb8k1t; Wed, 09 Oct 2002 08:04:12 PDT Message-ID: <3DA4456D.4C5031BC@iprg.nokia.com> Date: Wed, 09 Oct 2002 08:04:13 -0700 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN CC: manet Subject: Re: [manet] IPV6 and Ad Hoc Network References: <0489A7888F080B4BA73B53F7E145F29ADE2B99@LANMHS20.rd.francetelecom.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, I believe most manet protocols intend to allow arbitrary addresses within the ad hoc network, so that would include a "public" IP address. Since IPv6 addresses are typically global, I'm not quite sure what "public" means in that connection. With Mobile IP, one can migrate smoothly back and forth between the Internet and an ad hoc network that has a point of connection to the Internet. Even without Mobile IP, one could presumably migrate, just not as smoothly. Regards, Charlie P. MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN wrote: > > Hi, > I have a question about the attribution of IP address within MANET with > IPV6. Is it possible to assume that a client can acquire a public IP @ > from any network operator, after this, the client can use this address > any-where. > > Any comments? > > Sincerely > > _______________________________________________ > 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-admin@ietf.org Wed Oct 9 11:44:02 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22547 for ; Wed, 9 Oct 2002 11:44:02 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Fgqv30883; Wed, 9 Oct 2002 11:42:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Fc1v30663 for ; Wed, 9 Oct 2002 11:38:01 -0400 Received: from mail.drexel.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22203 for ; Wed, 9 Oct 2002 11:35:51 -0400 (EDT) Received: from webmail.drexel.edu (webmail.drexel.edu [129.25.3.29]) by mail.drexel.edu (Sun Internet Mail Server sims.4.0.2001.07.26.11.50.p9) with ESMTP id <0H3Q004BJ0Q7X2@mail.drexel.edu> for manet@ietf.org; Wed, 9 Oct 2002 11:37:19 -0400 (EDT) Date: Wed, 09 Oct 2002 11:37:41 -0400 From: Harpreet Arora To: manet@ietf.org Message-id: <3DA53DD9@webmail.drexel.edu> MIME-version: 1.0 X-Mailer: WebMail (Hydra) SMTP v3.61.08 Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_zOIe0VYkP+nCm9aKk+gZGg)" X-Priority: 1 X-WebMail-Urgent: Y X-WebMail-UserID: ha33 X-EXP32-SerialNo: 00003005 Subject: [manet] ATS 2003 Call for Participation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is the preamble of a multipart MIME formatted message. If you are reading this text your mail system is most likely not capable of properly decoding MIME messages. To extract the contents of this message, save it to a file and then use an external MIME decoding utility. --Boundary_(ID_zOIe0VYkP+nCm9aKk+gZGg) Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7BIT -------------------------------------------------------------------- Harpreet S. Arora Research Assistant, ITCSL Drexel University, Philadelphia, PA-19104 Ph. # 215-895-6198 http://www.pages.drexel.edu/~ha33 ---------------------------------------------------------------------- --Boundary_(ID_zOIe0VYkP+nCm9aKk+gZGg) Content-type: text/plain; CHARSET=US-ASCII; name=ATS2003CFP.txt Content-disposition: attachment; filename=ATS2003CFP.txt Content-Transfer-Encoding: 7BIT CALL FOR PAPERS Applied Telecommunication Symposium (ATS) Part of the 2003 Advanced Simulation Technologies Conference (ASTC 2003) March 30 through April 3, 2003 Hyatt Orlando Hotel, Orlando, FL, USA The Applied Telecommunication Symposium (ATS) is an international forum for exchange of technical knowledge and presentation of original papers on the analysis of telecommunication systems and technologies. It is intended for professionals, engineers, software developers, managers, and others interested in cellular and packet traffic characteristics, analysis of telecommunication networks, and practitioners operating telecommunication networks. We are looking for innovative technical papers describing projects, applications, and research and development work pertinent to telecommunication. The following tracks (with track chairs listed) will be held; the topics are representative of the track, but are not necessarily exclusive to that track: Wireless Chairs - Dr. Hassan Rajaei, Bowling Green State University Dr. Mohsen Guizani, University of West Florida -CDMA -UMTS -GSM -2.5G/3G Wireless -Wireless Data -Cell Traffic -Network Performance and Engineering Telecommunications Business and Regulation Chair - Dr. George Kraft, Stuart School of Business, Illinois Institute of Technology -Cost modeling -Call center operations -Billing models -E-commerce Measurements Chair - Dr. Shakil Akhtar, UAE University, Al-Ain, United Arab Emirates -Measured Internet Traffic Characteristics -Wireless Traffic Characteristics -Observed Problems with Current Packet Switching Protocols -Tools Network Management and Security Chair - Dr. Axel Lehmann, Universitaet der Bundeswehr Muenchen -Operations, Administration, Maintenance -Overload control -Load balancing -Influence of security measures on network performance Networks and Multimedia Chairs - Dr. Aftab Ahmad, DePaul University -Internet -Network performance -Traffic characterization -Packet switch architecture evaluation Modeling Techniques Chair - Kamala Murti, Lucent Technologies, Inc. -Simulation techniques -Acceleration methods -Traffic synthesis -Combined simulation/analytic procedures Traffic Engineering with Protocols and Devices Chair - Dr. Junaid Zubairi, SUNY at Fredonia -Traffic Management and control -Traffic engineering architectures -Bandwidth management -GMPLS Three copies of a 300 word abstract or a draft paper should be submitted to the session organizers by November 1, 2002. Please indicate for which track(s) you wish to have your paper considered for; note that the final track selection will be at the discretion of the ATS organizers. The abstract must include the author(s), e-mail address(es), and affiliation. Abstracts may be submitted electronically to http://scs.proceedingscentral.com or directly to: Dr. Bohdan Bodnar, ATS Chair, Motorola, USA, bbodnar1@motorola.com, or to Dr. Ariel Sharon, Lucent Technologies, Inc., E-mail: asharon@lucent.com. Further information is available at http://www.scs.org/confernc/astc/astc03/cfp/ats03.htm Deadlines Abstract/Draft paper due - November 1, 2002 Notification of acceptance sent - November 30, 2002 Camera-ready paper due - January 31, 2003 Conference Committee General Chair Dr. Bohdan Bodnar Motorola, Inc. bbodnar1@motorola.com Co-Chair Dr. Ariel Sharon Lucent Technologies, Inc. asharon@lucent.com Program Chair Dr. George Kraft Illinois Institute of Technology Sponsored by The Society for Modeling and Simulation International P.O. Box 17900 San Diego, CA 92177-7900 Tel 858-277-3888 Fax: 858-277-3930 E-mail scs@scs.org http://www.scs.org --Boundary_(ID_zOIe0VYkP+nCm9aKk+gZGg)-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 9 11:47:09 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22621 for ; Wed, 9 Oct 2002 11:47:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g99FmlD31126 for manet-archive@odin.ietf.org; Wed, 9 Oct 2002 11:48:47 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Fmlv31123 for ; Wed, 9 Oct 2002 11:48:47 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22615 for ; Wed, 9 Oct 2002 11:46:38 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Fgqv30883; Wed, 9 Oct 2002 11:42:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Fc1v30663 for ; Wed, 9 Oct 2002 11:38:01 -0400 Received: from mail.drexel.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22203 for ; Wed, 9 Oct 2002 11:35:51 -0400 (EDT) Received: from webmail.drexel.edu (webmail.drexel.edu [129.25.3.29]) by mail.drexel.edu (Sun Internet Mail Server sims.4.0.2001.07.26.11.50.p9) with ESMTP id <0H3Q004BJ0Q7X2@mail.drexel.edu> for manet@ietf.org; Wed, 9 Oct 2002 11:37:19 -0400 (EDT) Date: Wed, 09 Oct 2002 11:37:41 -0400 From: Harpreet Arora To: manet@ietf.org Message-id: <3DA53DD9@webmail.drexel.edu> MIME-version: 1.0 X-Mailer: WebMail (Hydra) SMTP v3.61.08 Content-type: MULTIPART/MIXED; BOUNDARY="Boundary_(ID_zOIe0VYkP+nCm9aKk+gZGg)" X-Priority: 1 X-WebMail-Urgent: Y X-WebMail-UserID: ha33 X-EXP32-SerialNo: 00003005 Subject: [manet] ATS 2003 Call for Participation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is the preamble of a multipart MIME formatted message. If you are reading this text your mail system is most likely not capable of properly decoding MIME messages. To extract the contents of this message, save it to a file and then use an external MIME decoding utility. --Boundary_(ID_zOIe0VYkP+nCm9aKk+gZGg) Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7BIT -------------------------------------------------------------------- Harpreet S. Arora Research Assistant, ITCSL Drexel University, Philadelphia, PA-19104 Ph. # 215-895-6198 http://www.pages.drexel.edu/~ha33 ---------------------------------------------------------------------- --Boundary_(ID_zOIe0VYkP+nCm9aKk+gZGg) Content-type: text/plain; CHARSET=US-ASCII; name=ATS2003CFP.txt Content-disposition: attachment; filename=ATS2003CFP.txt Content-Transfer-Encoding: 7BIT CALL FOR PAPERS Applied Telecommunication Symposium (ATS) Part of the 2003 Advanced Simulation Technologies Conference (ASTC 2003) March 30 through April 3, 2003 Hyatt Orlando Hotel, Orlando, FL, USA The Applied Telecommunication Symposium (ATS) is an international forum for exchange of technical knowledge and presentation of original papers on the analysis of telecommunication systems and technologies. It is intended for professionals, engineers, software developers, managers, and others interested in cellular and packet traffic characteristics, analysis of telecommunication networks, and practitioners operating telecommunication networks. We are looking for innovative technical papers describing projects, applications, and research and development work pertinent to telecommunication. The following tracks (with track chairs listed) will be held; the topics are representative of the track, but are not necessarily exclusive to that track: Wireless Chairs - Dr. Hassan Rajaei, Bowling Green State University Dr. Mohsen Guizani, University of West Florida -CDMA -UMTS -GSM -2.5G/3G Wireless -Wireless Data -Cell Traffic -Network Performance and Engineering Telecommunications Business and Regulation Chair - Dr. George Kraft, Stuart School of Business, Illinois Institute of Technology -Cost modeling -Call center operations -Billing models -E-commerce Measurements Chair - Dr. Shakil Akhtar, UAE University, Al-Ain, United Arab Emirates -Measured Internet Traffic Characteristics -Wireless Traffic Characteristics -Observed Problems with Current Packet Switching Protocols -Tools Network Management and Security Chair - Dr. Axel Lehmann, Universitaet der Bundeswehr Muenchen -Operations, Administration, Maintenance -Overload control -Load balancing -Influence of security measures on network performance Networks and Multimedia Chairs - Dr. Aftab Ahmad, DePaul University -Internet -Network performance -Traffic characterization -Packet switch architecture evaluation Modeling Techniques Chair - Kamala Murti, Lucent Technologies, Inc. -Simulation techniques -Acceleration methods -Traffic synthesis -Combined simulation/analytic procedures Traffic Engineering with Protocols and Devices Chair - Dr. Junaid Zubairi, SUNY at Fredonia -Traffic Management and control -Traffic engineering architectures -Bandwidth management -GMPLS Three copies of a 300 word abstract or a draft paper should be submitted to the session organizers by November 1, 2002. Please indicate for which track(s) you wish to have your paper considered for; note that the final track selection will be at the discretion of the ATS organizers. The abstract must include the author(s), e-mail address(es), and affiliation. Abstracts may be submitted electronically to http://scs.proceedingscentral.com or directly to: Dr. Bohdan Bodnar, ATS Chair, Motorola, USA, bbodnar1@motorola.com, or to Dr. Ariel Sharon, Lucent Technologies, Inc., E-mail: asharon@lucent.com. Further information is available at http://www.scs.org/confernc/astc/astc03/cfp/ats03.htm Deadlines Abstract/Draft paper due - November 1, 2002 Notification of acceptance sent - November 30, 2002 Camera-ready paper due - January 31, 2003 Conference Committee General Chair Dr. Bohdan Bodnar Motorola, Inc. bbodnar1@motorola.com Co-Chair Dr. Ariel Sharon Lucent Technologies, Inc. asharon@lucent.com Program Chair Dr. George Kraft Illinois Institute of Technology Sponsored by The Society for Modeling and Simulation International P.O. Box 17900 San Diego, CA 92177-7900 Tel 858-277-3888 Fax: 858-277-3930 E-mail scs@scs.org http://www.scs.org --Boundary_(ID_zOIe0VYkP+nCm9aKk+gZGg)-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 9 16:09:54 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02549 for ; Wed, 9 Oct 2002 16:09:54 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g99KBZ614935 for manet-archive@odin.ietf.org; Wed, 9 Oct 2002 16:11:35 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99KBZv14932 for ; Wed, 9 Oct 2002 16:11:35 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02498 for ; Wed, 9 Oct 2002 16:09:23 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99K8pv14838; Wed, 9 Oct 2002 16:08:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99K37v14082 for ; Wed, 9 Oct 2002 16:03:07 -0400 Received: from web40613.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA01900 for ; Wed, 9 Oct 2002 16:00:55 -0400 (EDT) Message-ID: <20021009200301.61294.qmail@web40613.mail.yahoo.com> Received: from [128.6.171.235] by web40613.mail.yahoo.com via HTTP; Wed, 09 Oct 2002 13:03:01 PDT Date: Wed, 9 Oct 2002 13:03:01 -0700 (PDT) From: tiad all To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] wireless communication collision/interference Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, I have a question abt wireless communication. I know that the collision is happening at the receiving side. If there is too much interference happening at the receiving side, it won't be able to capture the correct packet. But, will the receiving side be able to tell it is a receiving failure because of collision? In general, will a node be able to tell how much interference/collision is happening around it by just eavesdroping on the channel ... ? Thanks __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 9 16:09:58 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02562 for ; Wed, 9 Oct 2002 16:09:57 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99K8pv14838; Wed, 9 Oct 2002 16:08:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99K37v14082 for ; Wed, 9 Oct 2002 16:03:07 -0400 Received: from web40613.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA01900 for ; Wed, 9 Oct 2002 16:00:55 -0400 (EDT) Message-ID: <20021009200301.61294.qmail@web40613.mail.yahoo.com> Received: from [128.6.171.235] by web40613.mail.yahoo.com via HTTP; Wed, 09 Oct 2002 13:03:01 PDT Date: Wed, 9 Oct 2002 13:03:01 -0700 (PDT) From: tiad all To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] wireless communication collision/interference Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, I have a question abt wireless communication. I know that the collision is happening at the receiving side. If there is too much interference happening at the receiving side, it won't be able to capture the correct packet. But, will the receiving side be able to tell it is a receiving failure because of collision? In general, will a node be able to tell how much interference/collision is happening around it by just eavesdroping on the channel ... ? Thanks __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 03:49:13 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24950 for ; Thu, 10 Oct 2002 03:49:13 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9A7p1B24705 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 03:51:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A7oxv24698 for ; Thu, 10 Oct 2002 03:50:59 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24944 for ; Thu, 10 Oct 2002 03:48:41 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A7nbv24644; Thu, 10 Oct 2002 03:49:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A7gMv24449 for ; Thu, 10 Oct 2002 03:42:22 -0400 Received: from mailhost.iitb.ac.in (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA24889 for ; Thu, 10 Oct 2002 03:40:02 -0400 (EDT) Received: (qmail 20632 invoked from network); 10 Oct 2002 07:42:01 -0000 Received: from mailscan2.iitb.ac.in (HELO thisdomain) (144.16.108.202) by mailhost.iitb.ac.in with SMTP; 10 Oct 2002 07:42:01 -0000 Received: from it.iitb.ac.in by iitb.ac.in ; Thu, 10 Oct 2002 13:12:06 +0530 Date: Thu, 10 Oct 2002 13:12:06 +0530 X-Originating-IP: 10.129.11.4 X-Auth-User: deepanshu@it.iitb.ac.in Message-ID: <3DA52F19.5030002@it.iitb.ac.in> Date: Thu, 10 Oct 2002 13:11:13 +0530 From: Deepanshu Shukla Reply-To: deepanshu@it.iitb.ac.in Organization: KReSIT User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 (BDP) 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 Content-Transfer-Encoding: 7bit Subject: [manet] (no subject) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit -- Deepanshu Shukla -------------------------------------------------------------------- KReSIT [ IIT Bombay ] People are just about as happy as they make up their minds to be. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 03:49:16 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24963 for ; Thu, 10 Oct 2002 03:49:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A7nbv24644; Thu, 10 Oct 2002 03:49:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A7gMv24449 for ; Thu, 10 Oct 2002 03:42:22 -0400 Received: from mailhost.iitb.ac.in (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA24889 for ; Thu, 10 Oct 2002 03:40:02 -0400 (EDT) Received: (qmail 20632 invoked from network); 10 Oct 2002 07:42:01 -0000 Received: from mailscan2.iitb.ac.in (HELO thisdomain) (144.16.108.202) by mailhost.iitb.ac.in with SMTP; 10 Oct 2002 07:42:01 -0000 Received: from it.iitb.ac.in by iitb.ac.in ; Thu, 10 Oct 2002 13:12:06 +0530 Date: Thu, 10 Oct 2002 13:12:06 +0530 X-Originating-IP: 10.129.11.4 X-Auth-User: deepanshu@it.iitb.ac.in Message-ID: <3DA52F19.5030002@it.iitb.ac.in> Date: Thu, 10 Oct 2002 13:11:13 +0530 From: Deepanshu Shukla Reply-To: deepanshu@it.iitb.ac.in Organization: KReSIT User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 (BDP) 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 Content-Transfer-Encoding: 7bit Subject: [manet] (no subject) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit -- Deepanshu Shukla -------------------------------------------------------------------- KReSIT [ IIT Bombay ] People are just about as happy as they make up their minds to be. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 03:54:22 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25027 for ; Thu, 10 Oct 2002 03:54:22 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9A7u9R24910 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 03:56:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A7u9v24907 for ; Thu, 10 Oct 2002 03:56:09 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25023 for ; Thu, 10 Oct 2002 03:53:51 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A7t0v24847; Thu, 10 Oct 2002 03:55:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A7lVv24571 for ; Thu, 10 Oct 2002 03:47:31 -0400 Received: from mailhost.iitb.ac.in (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA24925 for ; Thu, 10 Oct 2002 03:45:11 -0400 (EDT) Received: (qmail 21112 invoked from network); 10 Oct 2002 07:47:16 -0000 Received: from mailscan2.iitb.ac.in (HELO thisdomain) (144.16.108.202) by mailhost.iitb.ac.in with SMTP; 10 Oct 2002 07:47:16 -0000 Received: from it.iitb.ac.in by iitb.ac.in ; Thu, 10 Oct 2002 13:17:20 +0530 Date: Thu, 10 Oct 2002 13:17:20 +0530 X-Originating-IP: 10.129.11.4 X-Auth-User: deepanshu@it.iitb.ac.in Message-ID: <3DA53053.6030308@it.iitb.ac.in> Date: Thu, 10 Oct 2002 13:16:27 +0530 From: Deepanshu Shukla Reply-To: deepanshu@it.iitb.ac.in Organization: KReSIT User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 (BDP) 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 Content-Transfer-Encoding: 7bit Subject: [manet] test mail Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit i am sorry for spam...plz ignore. -- Deepanshu Shukla _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 03:54:24 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25040 for ; Thu, 10 Oct 2002 03:54:24 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A7t0v24847; Thu, 10 Oct 2002 03:55:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A7lVv24571 for ; Thu, 10 Oct 2002 03:47:31 -0400 Received: from mailhost.iitb.ac.in (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA24925 for ; Thu, 10 Oct 2002 03:45:11 -0400 (EDT) Received: (qmail 21112 invoked from network); 10 Oct 2002 07:47:16 -0000 Received: from mailscan2.iitb.ac.in (HELO thisdomain) (144.16.108.202) by mailhost.iitb.ac.in with SMTP; 10 Oct 2002 07:47:16 -0000 Received: from it.iitb.ac.in by iitb.ac.in ; Thu, 10 Oct 2002 13:17:20 +0530 Date: Thu, 10 Oct 2002 13:17:20 +0530 X-Originating-IP: 10.129.11.4 X-Auth-User: deepanshu@it.iitb.ac.in Message-ID: <3DA53053.6030308@it.iitb.ac.in> Date: Thu, 10 Oct 2002 13:16:27 +0530 From: Deepanshu Shukla Reply-To: deepanshu@it.iitb.ac.in Organization: KReSIT User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 (BDP) 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 Content-Transfer-Encoding: 7bit Subject: [manet] test mail Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit i am sorry for spam...plz ignore. -- Deepanshu Shukla _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 11:01:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06970 for ; Thu, 10 Oct 2002 11:01:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AF0nv14953; Thu, 10 Oct 2002 11:00:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AEwov14878 for ; Thu, 10 Oct 2002 10:58:50 -0400 Received: from thoth.sbs.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06834 for ; Thu, 10 Oct 2002 10:56:39 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g9AEwdl12029; Thu, 10 Oct 2002 16:58:39 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9AEwcQ14365; Thu, 10 Oct 2002 16:58:38 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9AEwcIu011737; Thu, 10 Oct 2002 16:58:38 +0200 (MET DST) Message-ID: <3DA59727.3D30C4F8@mchp.siemens.de> Date: Thu, 10 Oct 2002 17:05:11 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Aodvimpl-Public , "manet@ietf.org" , "ns-users@isi.edu" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] DROP_RTR_MAC_CALLBACK or DROP_RTR_NO_ROUTE?? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, i have a question about these lines in the "rt_ll_failed(packet *p)" function of aodv (ns-2.1b9): if((rt = rtable.rt_lookup(ih->daddr())) == 0) { drop(p, DROP_RTR_MAC_CALLBACK); return; after the MAC layer realizes that there is no way to forward the packet, it informs aodv about this problem. AODV looks for an entry for the given destination adress and realizes that there is no routing entry for this destination. Instead of dropping the packets with "DROP_RTR_NO_ROUTE" as reason, it drops it by giving "DROP_RTR_MAC_CALLBACK" as a reason. Can somebody tell me why?? i would say the first reason is logical because we didn't find any route entry for that destination!!!! Thanks for any help or comment. Riadh. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 11:09:21 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07244 for ; Thu, 10 Oct 2002 11:09:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AFB1F15838 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 11:11:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFB1v15835 for ; Thu, 10 Oct 2002 11:11:01 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07233 for ; Thu, 10 Oct 2002 11:08:50 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AF0nv14953; Thu, 10 Oct 2002 11:00:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AEwov14878 for ; Thu, 10 Oct 2002 10:58:50 -0400 Received: from thoth.sbs.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06834 for ; Thu, 10 Oct 2002 10:56:39 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g9AEwdl12029; Thu, 10 Oct 2002 16:58:39 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9AEwcQ14365; Thu, 10 Oct 2002 16:58:38 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9AEwcIu011737; Thu, 10 Oct 2002 16:58:38 +0200 (MET DST) Message-ID: <3DA59727.3D30C4F8@mchp.siemens.de> Date: Thu, 10 Oct 2002 17:05:11 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Aodvimpl-Public , "manet@ietf.org" , "ns-users@isi.edu" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] DROP_RTR_MAC_CALLBACK or DROP_RTR_NO_ROUTE?? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, i have a question about these lines in the "rt_ll_failed(packet *p)" function of aodv (ns-2.1b9): if((rt = rtable.rt_lookup(ih->daddr())) == 0) { drop(p, DROP_RTR_MAC_CALLBACK); return; after the MAC layer realizes that there is no way to forward the packet, it informs aodv about this problem. AODV looks for an entry for the given destination adress and realizes that there is no routing entry for this destination. Instead of dropping the packets with "DROP_RTR_NO_ROUTE" as reason, it drops it by giving "DROP_RTR_MAC_CALLBACK" as a reason. Can somebody tell me why?? i would say the first reason is logical because we didn't find any route entry for that destination!!!! Thanks for any help or comment. Riadh. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 11:36:05 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07994 for ; Thu, 10 Oct 2002 11:36:04 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AFbjJ17635 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 11:37:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFbhv17632 for ; Thu, 10 Oct 2002 11:37:43 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07943 for ; Thu, 10 Oct 2002 11:35:32 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUdv16528; Thu, 10 Oct 2002 11:30:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8TIRcv11669 for ; Sun, 29 Sep 2002 14:27:38 -0400 Received: from vip.sina.com (sina35-175.sina.com.cn [202.108.35.175] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA07125 for ; Sun, 29 Sep 2002 14:25:36 -0400 (EDT) From: lining73@vip.sina.com Received: (qmail 3004 invoked by uid 99); 29 Sep 2002 18:27:26 -0000 Message-ID: <20020929182726.3003.qmail@vip.sina.com> To: manet@ietf.org Cc: lining_nj@sina.com MIME-Version: 1.0 Date: Mon, 30 Sep 2002 02:27:26 +0800 X-Mailer: SinaMail 3.0Beta (FireToad) X-Priority: 3 Subject: [manet] help:Power-Saving mode in 802.11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , everyone: In an ad hoc network which use 802.11 as the MAC protocol, if all stations work in PS(power-saving) mode, in the ATIM window, when a station A want to send packets to station B,I want to ask the following questions: 1. does the ATIM message directed send to B or use a RTS-CTS handshake at first between A & B, and then send the ATIM? 2. if station A have tens of packets in its sending queue to different stations, should A send ATIMs to all the destination stations? If this is true, there may be the case(when the load is rather high) that in one beacon interval, A can not send out all its packets because of contention with other stations,and there may be stations which recevie ATIM from "A" and stays in active state, but receive nothing from "A" in the current beacon interval, and energy will be wasted. How to slove this problem? 3. if there is only one FIFO sending queue and there is a broadcast message(routing message etc.)at the back end of the queue(several unicast packets are preceded it), as the standard recomand that the broadcast message should send first,is it feasible?Shall I use several sending queues? 4. How to set the value of beacon interval and the ATIM window, I can't find it in the standard of 99's version? should it be realted to network loads? 5. it seems that the PS mode in 802.11 is designed for low load situations and should not be used in high load circumstance, doesn't it? Thanks in advance. Best regards! ______________________________________ =================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 11:36:16 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08020 for ; Thu, 10 Oct 2002 11:36:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUdv16528; Thu, 10 Oct 2002 11:30:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8TIRcv11669 for ; Sun, 29 Sep 2002 14:27:38 -0400 Received: from vip.sina.com (sina35-175.sina.com.cn [202.108.35.175] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA07125 for ; Sun, 29 Sep 2002 14:25:36 -0400 (EDT) From: lining73@vip.sina.com Received: (qmail 3004 invoked by uid 99); 29 Sep 2002 18:27:26 -0000 Message-ID: <20020929182726.3003.qmail@vip.sina.com> To: manet@ietf.org Cc: lining_nj@sina.com MIME-Version: 1.0 Date: Mon, 30 Sep 2002 02:27:26 +0800 X-Mailer: SinaMail 3.0Beta (FireToad) X-Priority: 3 Subject: [manet] help:Power-Saving mode in 802.11 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , everyone: In an ad hoc network which use 802.11 as the MAC protocol, if all stations work in PS(power-saving) mode, in the ATIM window, when a station A want to send packets to station B,I want to ask the following questions: 1. does the ATIM message directed send to B or use a RTS-CTS handshake at first between A & B, and then send the ATIM? 2. if station A have tens of packets in its sending queue to different stations, should A send ATIMs to all the destination stations? If this is true, there may be the case(when the load is rather high) that in one beacon interval, A can not send out all its packets because of contention with other stations,and there may be stations which recevie ATIM from "A" and stays in active state, but receive nothing from "A" in the current beacon interval, and energy will be wasted. How to slove this problem? 3. if there is only one FIFO sending queue and there is a broadcast message(routing message etc.)at the back end of the queue(several unicast packets are preceded it), as the standard recomand that the broadcast message should send first,is it feasible?Shall I use several sending queues? 4. How to set the value of beacon interval and the ATIM window, I can't find it in the standard of 99's version? should it be realted to network loads? 5. it seems that the PS mode in 802.11 is designed for low load situations and should not be used in high load circumstance, doesn't it? Thanks in advance. Best regards! ______________________________________ =================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 11:36:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08059 for ; Thu, 10 Oct 2002 11:36:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AFc7G17663 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 11:38:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFc7v17660 for ; Thu, 10 Oct 2002 11:38:07 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07975 for ; Thu, 10 Oct 2002 11:35:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUtv16609; Thu, 10 Oct 2002 11:30:55 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g950x3v11632 for ; Fri, 4 Oct 2002 20:59:03 -0400 Received: from win.isi.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27153 for ; Fri, 4 Oct 2002 20:56:53 -0400 (EDT) Received: from localhost (xuanc@localhost) by win.isi.edu (8.11.6/8.11.6) with ESMTP id g9510M909542 for ; Fri, 4 Oct 2002 18:00:22 -0700 X-Authentication-Warning: win.isi.edu: xuanc owned process doing -bs Date: Fri, 4 Oct 2002 18:00:22 -0700 (PDT) From: Xuan Chen To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Student travel grant for NS Tutorial 2002 (fwd) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , We had previously sent out an announcement (enclosed below) for the NS tutorial 2002 being held at ISI, Los Angeles on nov 21/22. This is to further confirm that we will have a student travel grant program. For qualified applicants, we will partially fund the travel costs. To get detailed information on how to apply, please visit: http://www.isi.edu/nsnam/ns/ns-tutorial/tutorial-02/award.html Please note that the application deadline is Oct 25, 2002. Thanks, Padma Haldar (haldar@isi.edu) Xuan Chen (xuanc@isi.edu) > ======= > We would like to announce an NS tutorial/workshop to be held at > Information Sciences Institute, Los Angeles on Nov 21 and 22, 2002. > > This tutorial is intended for users, researchers and developers who would > like to use ns more actively, or extend its functionality. We will discuss > the primary components of the simulator (the scheduler, connection > oriented and connectionless protocols, trace support, routing, topology > generation, multicast support, queue management), and discuss various > issues like adding new routing or transport protocols, diffserv > applications, how to use nam and the new nam-editor, a brief introduction > to OTcl, how to debug ns using the OTcl and C++ interfaces etc. > > The format of this tutorial will be very similar to the previous ns > tutorials/workshops we have held (look at > http://www.isi.edu/nsnam/ns/ns-tutorial/) with updates based on > functionality added to the ns simulator recently (including new wireless > support, diffserv etc). In addition, for attendees to get hands-on > experience using ns, exercises in various levels will be given as lectures > progress in breadth and depth. So please bring your laptop to the > tutorial. Laptops with linux/freeBSD are encouraged though windows should > also not be a problem. Also attendees are expected to have a basic > understanding of C++. > > For this event there will be a charge of $50 to cover meals on both days, > copying cost for tutorial material and a CD-ROM. For registration as well > as for details about the tutorial please go to > http://www.isi.edu/nsnam/ns/ns-tutorial/tutorial-02/ > > Due to a fixed number of seating, the total number of people we can > accomodate at the tutorial may be limited. So try to register as soon as > possible. Also note that there is a deadline of Nov 11, 2002 for > registration. > > > Thanks, > Xuan Chen (xuanc@isi.edu) > Padma Haldar (haldar@isi.edu) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 11:36:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08073 for ; Thu, 10 Oct 2002 11:36:30 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUtv16609; Thu, 10 Oct 2002 11:30:55 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g950x3v11632 for ; Fri, 4 Oct 2002 20:59:03 -0400 Received: from win.isi.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27153 for ; Fri, 4 Oct 2002 20:56:53 -0400 (EDT) Received: from localhost (xuanc@localhost) by win.isi.edu (8.11.6/8.11.6) with ESMTP id g9510M909542 for ; Fri, 4 Oct 2002 18:00:22 -0700 X-Authentication-Warning: win.isi.edu: xuanc owned process doing -bs Date: Fri, 4 Oct 2002 18:00:22 -0700 (PDT) From: Xuan Chen To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Student travel grant for NS Tutorial 2002 (fwd) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , We had previously sent out an announcement (enclosed below) for the NS tutorial 2002 being held at ISI, Los Angeles on nov 21/22. This is to further confirm that we will have a student travel grant program. For qualified applicants, we will partially fund the travel costs. To get detailed information on how to apply, please visit: http://www.isi.edu/nsnam/ns/ns-tutorial/tutorial-02/award.html Please note that the application deadline is Oct 25, 2002. Thanks, Padma Haldar (haldar@isi.edu) Xuan Chen (xuanc@isi.edu) > ======= > We would like to announce an NS tutorial/workshop to be held at > Information Sciences Institute, Los Angeles on Nov 21 and 22, 2002. > > This tutorial is intended for users, researchers and developers who would > like to use ns more actively, or extend its functionality. We will discuss > the primary components of the simulator (the scheduler, connection > oriented and connectionless protocols, trace support, routing, topology > generation, multicast support, queue management), and discuss various > issues like adding new routing or transport protocols, diffserv > applications, how to use nam and the new nam-editor, a brief introduction > to OTcl, how to debug ns using the OTcl and C++ interfaces etc. > > The format of this tutorial will be very similar to the previous ns > tutorials/workshops we have held (look at > http://www.isi.edu/nsnam/ns/ns-tutorial/) with updates based on > functionality added to the ns simulator recently (including new wireless > support, diffserv etc). In addition, for attendees to get hands-on > experience using ns, exercises in various levels will be given as lectures > progress in breadth and depth. So please bring your laptop to the > tutorial. Laptops with linux/freeBSD are encouraged though windows should > also not be a problem. Also attendees are expected to have a basic > understanding of C++. > > For this event there will be a charge of $50 to cover meals on both days, > copying cost for tutorial material and a CD-ROM. For registration as well > as for details about the tutorial please go to > http://www.isi.edu/nsnam/ns/ns-tutorial/tutorial-02/ > > Due to a fixed number of seating, the total number of people we can > accomodate at the tutorial may be limited. So try to register as soon as > possible. Also note that there is a deadline of Nov 11, 2002 for > registration. > > > Thanks, > Xuan Chen (xuanc@isi.edu) > Padma Haldar (haldar@isi.edu) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 11:36:32 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08087 for ; Thu, 10 Oct 2002 11:36:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AFcBc17687 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 11:38:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFcBv17680 for ; Thu, 10 Oct 2002 11:38:11 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07984 for ; Thu, 10 Oct 2002 11:36:00 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUlv16568; Thu, 10 Oct 2002 11:30:47 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91H0ov16096 for ; Tue, 1 Oct 2002 13:00:50 -0400 Received: from mbox1.ntu.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26820 for ; Tue, 1 Oct 2002 12:58:47 -0400 (EDT) Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Wed, 2 Oct 2002 00:39:54 +0800 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Wed, 2 Oct 2002 00:39:53 +0800 Message-ID: <295CB338B611594582D82D9F26AEF7062CBEBA@mail02.student.main.ntu.edu.sg> Thread-Topic: signal to noise ratio(SNR) and GPS info.. Thread-Index: AcJpaSs/k9r4Eml1S4qNdkoo174BKg== From: "#GUPTA ROHIT#" To: X-OriginalArrivalTime: 01 Oct 2002 16:39:54.0221 (UTC) FILETIME=[2B81E1D0:01C26969] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id g91H0ov16097 Subject: [manet] signal to noise ratio(SNR) and GPS info.. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Dear all, can anyone let me know on the work done on SNR and GPS to improve AODV. rgds rohit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 11:36:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08110 for ; Thu, 10 Oct 2002 11:36:34 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUlv16568; Thu, 10 Oct 2002 11:30:47 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91H0ov16096 for ; Tue, 1 Oct 2002 13:00:50 -0400 Received: from mbox1.ntu.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26820 for ; Tue, 1 Oct 2002 12:58:47 -0400 (EDT) Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Wed, 2 Oct 2002 00:39:54 +0800 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Wed, 2 Oct 2002 00:39:53 +0800 Message-ID: <295CB338B611594582D82D9F26AEF7062CBEBA@mail02.student.main.ntu.edu.sg> Thread-Topic: signal to noise ratio(SNR) and GPS info.. Thread-Index: AcJpaSs/k9r4Eml1S4qNdkoo174BKg== From: "#GUPTA ROHIT#" To: X-OriginalArrivalTime: 01 Oct 2002 16:39:54.0221 (UTC) FILETIME=[2B81E1D0:01C26969] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id g91H0ov16097 Subject: [manet] signal to noise ratio(SNR) and GPS info.. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Dear all, can anyone let me know on the work done on SNR and GPS to improve AODV. rgds rohit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 11:36:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08118 for ; Thu, 10 Oct 2002 11:36:34 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUpv16588; Thu, 10 Oct 2002 11:30:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g998GXv05817 for ; Wed, 9 Oct 2002 04:16:33 -0400 Received: from tokyo.ccrle.nec.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06871 for ; Wed, 9 Oct 2002 04:14:15 -0400 (EDT) Received: from imap.heidelberg.ccrle.nec.de (imap [192.168.102.11]) by tokyo.ccrle.nec.de (8.11.6/8.11.6) with ESMTP id g998GLY77973 for ; Wed, 9 Oct 2002 10:16:21 +0200 (CEST) (envelope-from Dirk.Westhoff@ccrle.nec.de) Received: by imap.heidelberg.ccrle.nec.de (Postfix on SuSE Linux eMail Server 3.0, from userid 30) id A96DD69E33; Wed, 9 Oct 2002 10:16:19 +0200 (CEST) X-Accept-Language: de, en X-Priority: 3 (Normal) X-Mailer: SKYRiXgreen_3.1 NGMime_4.2.18 From: "Dirk Westhoff" MIME-Version: 1.0 To: manet@ietf.org Organization: NEC Europe Ltd. content-type: text/plain; charset="iso-8859-1" date: Wed, 09 Oct 2002 10:16:19 +0200 content-transfer-encoding: 7bit Message-Id: <20021009081619.A96DD69E33@imap.heidelberg.ccrle.nec.de> Content-Transfer-Encoding: 7bit Subject: [manet] Workshop on Ad Hoc Security... Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear all, for those of you who are interested in security issues in ad hoc networks, the attached call for participation may be interesting. Best regards, Dirk Westhoff P.S: The URL will be available next week -------------------------------------------------------------------- 1st Workshop on Security in Ad-Hoc Networks www.crypto.rub.de/adhocsec Ruhr University Bochum, Germany December 2, 2002 Call for Participation General Information: It is expected that the next generation of IT applications will rely heavily on ad-hoc networks. Such networks are characterized by their dynamic structure, lack of fixed infrastructure, and constrained resources. In order to allow their successful deployment various security challenges must be solved. Examples include missing apriori security associations, the lack of a trusted infrastructure, as well as computing, memory and energy constrains. Due to the predicted pervasive nature of applications relying on ad-hoc networks makes effective provisions for robust security solutions must be taken. This one day workshop offers invited talks by leading experts on various aspects of ad-hoc network security. The talks will provide an overview on the various security issues involved and discuss new research in the area. In addition, the workshop will allow the informal exchange of ideas and building of a research network. Speakers: 1) Bill Arbaugh (U.S. Department of Defense) 2) Susanne Wetzel (Stevens Institute of Technology, USA) 3) Konrad Wrona (MIT Media Lab) 4) Sonja Buchegger (IBM Zuerich, Swiss) 5) Jean-Pierre Hubaux (Swiss Federal Institute of Technology - Lausanne) 6) Manel Guerrero Zapata (Nokia Research Center, Finland) Mailing List: If you want to receive emails with subsequent Call for Papers and registration information, please send a brief mail to adhocsec@crypto.rub.de Program Committee: Dirk Westhoff NEC Networks Labs Heidelberg, Germany Christof Paar Ruhr University Bochum, Germany Susanne Wetzel Stevens Institute of Technology, USA Registration: The registration form can be found at crypto.rub.de/adhocsec Workshop Proceedings: There will be no formal proceedings. However, the presentation slides of all speakers will be made available to the attendees. -- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 11:36:39 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08140 for ; Thu, 10 Oct 2002 11:36:39 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AFcJT17715 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 11:38:19 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFcJv17712 for ; Thu, 10 Oct 2002 11:38:19 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08009 for ; Thu, 10 Oct 2002 11:36:08 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUhv16548; Thu, 10 Oct 2002 11:30:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91Famv10441 for ; Tue, 1 Oct 2002 11:36:48 -0400 Received: from ece.ufl.edu (dot.ece.ufl.edu [128.227.220.22]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA22669 for ; Tue, 1 Oct 2002 11:34:47 -0400 (EDT) Received: (qmail 28716 invoked from network); 1 Oct 2002 15:33:11 -0000 Received: from fang.ece.ufl.edu (128.227.80.157) by smtp.ece.ufl.edu with SMTP; 1 Oct 2002 15:33:11 -0000 Received: (from fang@localhost) by fang.ece.ufl.edu (8.9.3/8.9.3) id LAA20326; Tue, 1 Oct 2002 11:34:11 -0400 (EDT) X-Authentication-Warning: fang.ece.ufl.edu: Processed from queue /home/faculty/fang/mqueue X-Authentication-Warning: fang.ece.ufl.edu: Processed by fang with -C /home/faculty/fang/bin/sendmail.cf Date: Tue, 1 Oct 2002 11:34:10 -0400 From: Yuguang Fang To: Yuguang Fang Message-ID: <20021001113410.B20314@ece.ufl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i Subject: [manet] SCS SPECTS'2003 Call for Papers Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , I apologize if you receive multiple copies of this message. Call For Papers %%%%%%%%%%%%%%%% 2003 International Symposium on Performance Evaluation of Computer and Telecommunication Systems (SPECTS 2003) July 20-24, 2003 Montreal, Canada http://scs.org/confernc/ssimc/ssimc03/cfp/spects03.htm Submission Deadlines Submission of Papers: January 31, 2003. Notification of Acceptance - April 25, 2003 Final Camera-Ready Submission - May 23, 2003 This annual international conference is a forum for professionals involved in performance evaluation of computer and telecommunication systems. Evaluation of computer systems and networks is needed at every stage in the life cycle of the product including design, manufacturing, sales/purchase, use, upgrade, tuning, etc. The discipline of performance evaluation has progressed rapidly in the past decade, and it has now begun to approach maturity. Significant progress has been made in analytic modeling, simulation, and measurement approaches for performance evaluation of computer and telecommunication systems. Topics of interest include, but are not limited to: Networking and Telecommunication Systems - Internet Technology - Quality of Service (QoS) - DiffServ/IntServ - MPLS - TCP - World Wide Web (WWW) Technology - Networking Techniques - Unicast and Multicast Routing - Congestion Control - Switching Techniques - Teletraffic - Network Protocols - Network Management and Control - Network Capacity Planning - Network Architecture Evaluation - Service and QoS Pricing - Security and Authentication -Broadband Networks - High-Speed Networking - ATM - Optical Networks - Wireless Systems and Networks - Satellite Systems - UMTS - Mobile Networks/Computing - Ad-hoc networks - Multimedia Communications Computer Systems - Distributed Architectures - Client/Server - Distributed Systems and Agents - Parallel and Distributed Computing - Massively Parallel Systems - Cluster Computing - Grid Computing - Interconnection Networks - Computer Architectures - Microprocessors/Microcomputers - Memory Systems - High Performance I/O - Real-time Systems - Scheduling Schemes -Software - Software Performance, Evaluation and Testing - Parallel Algorithms and Languages - Hardware and Software Monitors - High-Performance Computing - Workload and Traffic Characterization - Scientific Computing Algorithms - Reconfigurable Computing - Electronic Commerce Tools, Methodologies and Applications - Parallel and Distributed Simulation - Verification and Validation - Performance Tools and Methodologies - Neural Networks and Fuzzy Logic Applications to High Performance Computing/Networking - Performance Optimization - Queueing Systems and Networks - Scalability Studies - Integrated Modeling and Measurement - On-Line Performance Adaptation and Tuning - Process Algebra-Based Models - Performance Bounds - Integrated Design and Performance - New Performance Models - Mathematical Aspects of Performance - New Performability Schemes and Models - Case Studies General Chair Mohammad S. Obaidat Dept. of Computer Science, Monmouth University W. Long Branch, NJ 07764, USA Tel +1-732-571-4482 Fax +1-732-263-5202 E-mail: obaidat@monmouth.edu Senior Program Chair Franco Davoli DIST-University of Genoa Via Opera Pia 13, I-16145 Genoa, Italy Tel +39-010-353-2732 Fax +39-010-353-2154 E-Mail: franco@dist.unige.it Program Co-Chairs Ibrahim Onyuksel Dept. of Computer Sciences, N. Illinois Univ., USA E-mail: onyuksel@cs.niu.edu Erina Ferro ISTI, Institute of National Research Council (C.N.R.) C.N.R. Pisa Research Area, Building B, Room 73 Via G. Moruzzi, 1 56124 Pisa, Italy E-mail: erina.ferro@cnuce.cnr.it Vice Program Chair and Tutorial Chair Raffaele Bolla DIST-University of Genoa Via Opera Pia 13, I-16145 Genoa, Italy E-mail: lelus@dist.unige.it Vice Program Chair and Web Master Imad Mahgoub Department of Computer Science and Engineering Florida Atlantic University Boca Raton, FL 33431 E-mail: imad@cse.fau.edu Industrial Track and Special Sessions Chair J. Fox, Motorola Inc., UK E-mail: fox.ijcs@btinternet.com Technical Program Committee Ian Akyildiz, Georgia Tech., USA Mohammed Atiquzzaman, University of Oklahoma, USA Louis G. Birta, University of Ottawa, Canada Abdullah Abonamah, Zayed University, UAE Noureddine Boudriga, University of Tunis, Tunisia Hasan Cam, University of Arkansas, USA Andrew Campbell, Columbia University, USA Nedo Celandroni, ISTI-CNR, Italy Haitham Cruickshank, University of Surrey, UK Hassan B. Diab, American University of Beirut, Lebanon Gabor Fodor, Ericsson Radio Systems, Sweden Geoffrey Fox, Indiana University, USA Luigi Fratta, Politecnico di Milano, Italy Aura Ganz, University of Massachusetts, USA Erol Gelenbe, University of Central Florida, USA Mario Gerla, UCLA, USA Sami Habib, Kuwait University, Kuwait Omar Hammami, ENSTA, France Jarmo Harju, Tampere University of Technology, Finland Herman Hughes, Michigan State University, USA Andrzej Jajszczyk, University of Mining and Metallurgy, Poland Abbas Jamalipour, University of Sydney, Australia Ingemar Kaj, Uppsala University, Sweden Krishna Kant, Intel, USA Helen Karatza, Aristotle University of Thessalonica, Greece Demetrios Kazakos, University of Louisiana, USA Ulrich Killat, Tech Univ. of Hamburg, Germany Tag Gon Kim, KAIST, Korea Kevin Kwiat, Air Force Research Laboratory, USA Veronica Lagrange M. Reis, Compaq Computers Corp., USA Axel Lehmann, Universitdt der Bundeswehr M|nchen, Germany Daniel C. Lee, USC, USA Mike T. Liu, Ohio State University, USA Erich Lutz, DLR, Germany Sam Makki, Queensland University of Technology, Australia Krzysztof Malinowski, Warsaw Technical University, Poland Mario Marchese, University of Genoa, Italy Jose L. Marzo, Universitat de Girona, Spain Xiannong Meng, Bucknell University, USA Hussein Mouftah, Queen's University, Canada Mohamed Ould-Khaoua, University of Glasgow, UK Sergio Palazzo, Universit` di Catania, Italy Georgios I. Papadimitriou, Aristotle University, Greece Achille Pattavina, Politecnico di Milano, Italy Krzysztof Pawlikowski, University of Canterbury, New Zealand Gregory D. Peterson, University of Tennessee Steven Pink, University of Arizona, USA George Polyzos, AUEB, Greece Ramon Puigjaner, Universitat de les Illes Balears, Spain Kaliappa Ravindran, CUNY, USA Gian Paolo Rossi, Universit` di Milano, Italy Izhak Rubin, UCLA, USA Vicente Santonja, Technical University of Valencia, Spain Donald Schilling, CUNY, USA Jens B. Schmitt, TU Darmstadt, Germany Harald Skinnemoen, Nera, Norway Tatsuya Suda, UCI, USA Iwao Toda, Fujutsu Laboratories Ltd., Japan Phuoc Tran-Gia, University of Wuerzburg, Germany Kishor Trivedi, Duke University, USA Kenneth S. Vastola, Rensselaer Polytechnic Institute, USA Manuel Villen-Altamirano, Telefonica, Spain Bernd E. Wolfinger, Hamburg University, Germany Michele Zorzi, Universit` di Ferrara, Italy Publicity Chair: Yuguang (Michael) Fang, University of Florida, USA, E-mail: fang@ece.ufl.edu Publicity Committee: Jie Li, University of Tsukuba, Japan Chiara Petrioli, Universita` di Roma "La Sapienza", Italy Chuck Song, Chinese Academy of Sciences, China Ahmed Nuseirat, Al-Isra University, Jordan International Liaisons B. Sadoun, Al-Balqa' Applied University, Jordan Bsadoun@go.com.jo M. Sawan, Montreal Poly, Canada Sawan@vlsi.polymtl.ca N. Tchamov, Tampere Univ. of Technology, Finland Nikolay@cs.tut.fi Paper Submission Submit your complete papers electronically to: http://scs.proceedingscentral.com/ All required instructions will be posted on this web site. Submissions should not exceed 25 double-spaced, 8.5x11 inch pages (including figures, tables, and references) in 10-12 point font. Include five to ten keywords, complete postal and e-mail addresses, and fax and phone numbers of corresponding author. If you have difficulty in electronic submission, contact the Web Master, Program Chairs or the Conference Coordinator, Mr. Steve Branch, The Society for Modeling and Simulation International, 4838 Ronson Court, Suite L, San Diego, CA 92111, USA, Tel 858-277-3888, Fax 858-277-3930, E-mail sbranch@scs.org Extended versions of selected accepted papers in SPECTS 2003 will be considered for possible publication in scholarly journals. Proposals for tutorials should be sent to the Conference Vice Program Chair, Raffaele Bolla. Proposals for special sessions and panel sessions should be submitted to the special Sessions Chair. For more information regarding presentations or exhibitions at SPECTS 2002 contact: Mr. Steve Branch at the address shown above. Sponsored by The Society for Modeling and Simulation International. -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Yuguang "Michael" Fang, Ph.D Assistant Professor Department of Electrical and Computer Engineering University of Florida 435 Engineering Building, P.O.Box 116130 Gainesville, FL 32611 Tel: (352) 846-3043, Fax: (352) 392-0044 Email: fang@ece.ufl.edu, http://www.fang.ece.ufl.edu %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 11:36:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08155 for ; Thu, 10 Oct 2002 11:36:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AFcM317730 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 11:38:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFcLv17727 for ; Thu, 10 Oct 2002 11:38:21 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08013 for ; Thu, 10 Oct 2002 11:36:10 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUTv16484; Thu, 10 Oct 2002 11:30:29 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8Q2n8v30458 for ; Wed, 25 Sep 2002 22:49:08 -0400 Received: from mithrandir.scalable-networks.com (qmailr@adsl-63-205-33-203.fang-fashion.com [63.205.33.203] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA16597 for ; Wed, 25 Sep 2002 22:47:07 -0400 (EDT) Received: (qmail 3630 invoked from network); 26 Sep 2002 02:47:35 -0000 Received: from gateway.scalable-networks.com (HELO lbrownlaptop) (lbrown@63.205.33.202) by 192.168.0.160 with SMTP; 26 Sep 2002 02:47:35 -0000 From: "Lucinda Brown" To: Date: Wed, 25 Sep 2002 19:48:00 -0700 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C264CC.73F160E0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [manet] QualNet World Invitation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C264CC.73F160E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hello MANET list, Some of you may know about QualNet, a network simulator for MANET and other networks. Scalable Network Technologies, the company that develops QualNet, is putting on a users conference called QualNet World October 10th and 11th in Anaheim, California. Since there is good potential for cross pollination between the MANET research community and the QualNet user base, we are inviting people on the MANET mailing list to attend QualNet World. If you have used QualNet or GloMoSim for your research, we would also like to invite you to present your work at QualNet World. The audience will consist of some academic users, as well as people from commercial and military organizations who do network simulation. If you are interested in presenting your work, please send a 500 word abstract of your presentation to qualnetworld@scalable-networks.com by Sep 30th. Whether or not you are interested in speaking, we would like to invite you to attend QualNet World. For a complete schedule of events, including a 3 hour QualNet tutorial Friday afternoon, please see http://www.scalable-networks.com/qualnetworld Please RSVP by September 27th, as space is limited. You can register online at http://www.scalable-networks.com/qualnetworld/registration.html -Lucinda Brown Scalable Network Technologies ------=_NextPart_000_000E_01C264CC.73F160E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello MANET list,

Some of you may know about QualNet, a = network=20 simulator for MANET and other networks. Scalable Network Technologies, = the=20 company that develops QualNet, is putting on a users conference called = QualNet=20 World October 10th and 11th in Anaheim, California.

Since there is good potential for cross = pollination=20 between the MANET research community and the QualNet user base, we are = inviting=20 people on the MANET mailing list to attend QualNet World. If you have = used=20 QualNet or GloMoSim for your research, we would also like to invite you = to=20 present your work at QualNet World. The audience will consist of some = academic=20 users, as well as people from commercial and military organizations who = do=20 network simulation. If you are interested in presenting your work, = please send a=20 500 word abstract of your presentation to = qualnetworld@scalable-networks.com by=20 Sep 30th.

Whether or not you are interested in = speaking, we=20 would like to invite you to attend QualNet World. For a complete = schedule of=20 events, including a 3 hour QualNet tutorial Friday afternoon, please see =

http://www.scalable-networks.com/qualnetworld

Please RSVP by September 27th, as space = is limited.=20 You can register online at

http://www.scalable-networks.com/qualnetworld/registration.html<= /FONT>
-Lucinda = Brown
Scalable Network=20 Technologies

 =20
 
------=_NextPart_000_000E_01C264CC.73F160E0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 11:36:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08182 for ; Thu, 10 Oct 2002 11:36:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUTv16484; Thu, 10 Oct 2002 11:30:29 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8Q2n8v30458 for ; Wed, 25 Sep 2002 22:49:08 -0400 Received: from mithrandir.scalable-networks.com (qmailr@adsl-63-205-33-203.fang-fashion.com [63.205.33.203] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA16597 for ; Wed, 25 Sep 2002 22:47:07 -0400 (EDT) Received: (qmail 3630 invoked from network); 26 Sep 2002 02:47:35 -0000 Received: from gateway.scalable-networks.com (HELO lbrownlaptop) (lbrown@63.205.33.202) by 192.168.0.160 with SMTP; 26 Sep 2002 02:47:35 -0000 From: "Lucinda Brown" To: Date: Wed, 25 Sep 2002 19:48:00 -0700 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C264CC.73F160E0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [manet] QualNet World Invitation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C264CC.73F160E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hello MANET list, Some of you may know about QualNet, a network simulator for MANET and other networks. Scalable Network Technologies, the company that develops QualNet, is putting on a users conference called QualNet World October 10th and 11th in Anaheim, California. Since there is good potential for cross pollination between the MANET research community and the QualNet user base, we are inviting people on the MANET mailing list to attend QualNet World. If you have used QualNet or GloMoSim for your research, we would also like to invite you to present your work at QualNet World. The audience will consist of some academic users, as well as people from commercial and military organizations who do network simulation. If you are interested in presenting your work, please send a 500 word abstract of your presentation to qualnetworld@scalable-networks.com by Sep 30th. Whether or not you are interested in speaking, we would like to invite you to attend QualNet World. For a complete schedule of events, including a 3 hour QualNet tutorial Friday afternoon, please see http://www.scalable-networks.com/qualnetworld Please RSVP by September 27th, as space is limited. You can register online at http://www.scalable-networks.com/qualnetworld/registration.html -Lucinda Brown Scalable Network Technologies ------=_NextPart_000_000E_01C264CC.73F160E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello MANET list,

Some of you may know about QualNet, a = network=20 simulator for MANET and other networks. Scalable Network Technologies, = the=20 company that develops QualNet, is putting on a users conference called = QualNet=20 World October 10th and 11th in Anaheim, California.

Since there is good potential for cross = pollination=20 between the MANET research community and the QualNet user base, we are = inviting=20 people on the MANET mailing list to attend QualNet World. If you have = used=20 QualNet or GloMoSim for your research, we would also like to invite you = to=20 present your work at QualNet World. The audience will consist of some = academic=20 users, as well as people from commercial and military organizations who = do=20 network simulation. If you are interested in presenting your work, = please send a=20 500 word abstract of your presentation to = qualnetworld@scalable-networks.com by=20 Sep 30th.

Whether or not you are interested in = speaking, we=20 would like to invite you to attend QualNet World. For a complete = schedule of=20 events, including a 3 hour QualNet tutorial Friday afternoon, please see =

http://www.scalable-networks.com/qualnetworld

Please RSVP by September 27th, as space = is limited.=20 You can register online at

http://www.scalable-networks.com/qualnetworld/registration.html<= /FONT>
-Lucinda = Brown
Scalable Network=20 Technologies

 =20
 
------=_NextPart_000_000E_01C264CC.73F160E0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 11:36:51 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08204 for ; Thu, 10 Oct 2002 11:36:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AFcVK17761 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 11:38:31 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFcVv17758 for ; Thu, 10 Oct 2002 11:38:31 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08042 for ; Thu, 10 Oct 2002 11:36:20 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFV0v16629; Thu, 10 Oct 2002 11:31:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g95DbUv18044 for ; Sat, 5 Oct 2002 09:37:30 -0400 Received: from lakemtao02.cox.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15824 for ; Sat, 5 Oct 2002 09:35:25 -0400 (EDT) Received: from cx197711a ([68.9.25.104]) by lakemtao02.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20021005133727.BIVH12192.lakemtao02.cox.net@cx197711a> for ; Sat, 5 Oct 2002 09:37:27 -0400 From: "Bryan Morris" To: Date: Sat, 5 Oct 2002 09:38:07 -0400 Message-ID: <000001c26c74$7026eac0$6701a8c0@cx197711a> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C26C52.E916D160" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [manet] omnet++ fsr help Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C26C52.E916D160 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I am a grad student in Hartford, CT, USA I am looking for a seminar paper topic and would like to run a network simulation with fisheye and then try other algorithms instead and compare. if the FSR link state packet interval is const*hopcount^alpha I would like to modify that equation and rerun the simulation. I got the fsr model provided on the omnet home page I cannot find the lsp interval equation in the code that I got from the omnet homepage and all the comments are in a language that I dont understand. where is the lsp interval equation performed?? any help is appreciated thanks Bryan Morris bmorris08@cox.net ------=_NextPart_000_0001_01C26C52.E916D160 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
 
I am a = grad student=20 in Hartford, CT, USA
I am = looking for a=20 seminar paper topic and would like to run a network simulation with = fisheye and=20 then try other algorithms instead and compare.  if the FSR link = state=20 packet interval is = const*hopcount^alpha I=20 would like to modify that equation and rerun the = simulation.
 
I got the fsr model provided on the = omnet home=20 page
I = cannot find the=20 lsp interval equation in the code that I got from the omnet homepage and = all the=20 comments are in a language that I dont understand.  =
 
where is the lsp interval equation=20 performed??
 
any = help is=20 appreciated
 
thanks
Bryan=20 Morris
bmorris08@cox.net
= ------=_NextPart_000_0001_01C26C52.E916D160-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 11:36:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08218 for ; Thu, 10 Oct 2002 11:36:53 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFV0v16629; Thu, 10 Oct 2002 11:31:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g95DbUv18044 for ; Sat, 5 Oct 2002 09:37:30 -0400 Received: from lakemtao02.cox.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15824 for ; Sat, 5 Oct 2002 09:35:25 -0400 (EDT) Received: from cx197711a ([68.9.25.104]) by lakemtao02.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20021005133727.BIVH12192.lakemtao02.cox.net@cx197711a> for ; Sat, 5 Oct 2002 09:37:27 -0400 From: "Bryan Morris" To: Date: Sat, 5 Oct 2002 09:38:07 -0400 Message-ID: <000001c26c74$7026eac0$6701a8c0@cx197711a> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C26C52.E916D160" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [manet] omnet++ fsr help Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C26C52.E916D160 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I am a grad student in Hartford, CT, USA I am looking for a seminar paper topic and would like to run a network simulation with fisheye and then try other algorithms instead and compare. if the FSR link state packet interval is const*hopcount^alpha I would like to modify that equation and rerun the simulation. I got the fsr model provided on the omnet home page I cannot find the lsp interval equation in the code that I got from the omnet homepage and all the comments are in a language that I dont understand. where is the lsp interval equation performed?? any help is appreciated thanks Bryan Morris bmorris08@cox.net ------=_NextPart_000_0001_01C26C52.E916D160 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
 
I am a = grad student=20 in Hartford, CT, USA
I am = looking for a=20 seminar paper topic and would like to run a network simulation with = fisheye and=20 then try other algorithms instead and compare.  if the FSR link = state=20 packet interval is = const*hopcount^alpha I=20 would like to modify that equation and rerun the = simulation.
 
I got the fsr model provided on the = omnet home=20 page
I = cannot find the=20 lsp interval equation in the code that I got from the omnet homepage and = all the=20 comments are in a language that I dont understand.  =
 
where is the lsp interval equation=20 performed??
 
any = help is=20 appreciated
 
thanks
Bryan=20 Morris
bmorris08@cox.net
= ------=_NextPart_000_0001_01C26C52.E916D160-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 11:36:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08235 for ; Thu, 10 Oct 2002 11:36:57 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AFcbq17780 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 11:38:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFcbv17777 for ; Thu, 10 Oct 2002 11:38:37 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08056 for ; Thu, 10 Oct 2002 11:36:26 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFV4v16660; Thu, 10 Oct 2002 11:31:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A2oNv02559 for ; Wed, 9 Oct 2002 22:50:24 -0400 Received: from vip.sina.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA11677 for ; Wed, 9 Oct 2002 22:48:06 -0400 (EDT) From: lining73@vip.sina.com Received: (qmail 868 invoked by uid 99); 10 Oct 2002 02:50:09 -0000 Message-ID: <20021010025009.867.qmail@vip.sina.com> To: manet@ietf.org MIME-Version: 1.0 Date: Thu, 10 Oct 2002 10:50:09 +0800 X-Mailer: SinaMail 3.0Beta (FireToad) X-Priority: 3 Subject: [manet] radio transmission levels Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello everbody: In some papers related to power controlled MAC protocols in MANET, the power levels used are always different by different author. I want to know are there any real NICs with power control property which can be use in MANET? How many transmit power levels can be used and how much is the difference between maximum & minimum transmit power. Regards. ______________________________________ =================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 11:37:00 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08253 for ; Thu, 10 Oct 2002 11:37:00 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFV4v16660; Thu, 10 Oct 2002 11:31:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9A2oNv02559 for ; Wed, 9 Oct 2002 22:50:24 -0400 Received: from vip.sina.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA11677 for ; Wed, 9 Oct 2002 22:48:06 -0400 (EDT) From: lining73@vip.sina.com Received: (qmail 868 invoked by uid 99); 10 Oct 2002 02:50:09 -0000 Message-ID: <20021010025009.867.qmail@vip.sina.com> To: manet@ietf.org MIME-Version: 1.0 Date: Thu, 10 Oct 2002 10:50:09 +0800 X-Mailer: SinaMail 3.0Beta (FireToad) X-Priority: 3 Subject: [manet] radio transmission levels Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello everbody: In some papers related to power controlled MAC protocols in MANET, the power levels used are always different by different author. I want to know are there any real NICs with power control property which can be use in MANET? How many transmit power levels can be used and how much is the difference between maximum & minimum transmit power. Regards. ______________________________________ =================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 12:26:56 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08088 for ; Thu, 10 Oct 2002 11:36:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AFcBg17689 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 11:38:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFcBv17682 for ; Thu, 10 Oct 2002 11:38:11 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07987 for ; Thu, 10 Oct 2002 11:36:01 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUpv16588; Thu, 10 Oct 2002 11:30:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g998GXv05817 for ; Wed, 9 Oct 2002 04:16:33 -0400 Received: from tokyo.ccrle.nec.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06871 for ; Wed, 9 Oct 2002 04:14:15 -0400 (EDT) Received: from imap.heidelberg.ccrle.nec.de (imap [192.168.102.11]) by tokyo.ccrle.nec.de (8.11.6/8.11.6) with ESMTP id g998GLY77973 for ; Wed, 9 Oct 2002 10:16:21 +0200 (CEST) (envelope-from Dirk.Westhoff@ccrle.nec.de) Received: by imap.heidelberg.ccrle.nec.de (Postfix on SuSE Linux eMail Server 3.0, from userid 30) id A96DD69E33; Wed, 9 Oct 2002 10:16:19 +0200 (CEST) X-Accept-Language: de, en X-Priority: 3 (Normal) X-Mailer: SKYRiXgreen_3.1 NGMime_4.2.18 From: "Dirk Westhoff" MIME-Version: 1.0 To: manet@ietf.org Organization: NEC Europe Ltd. content-type: text/plain; charset="iso-8859-1" date: Wed, 09 Oct 2002 10:16:19 +0200 content-transfer-encoding: 7bit Message-Id: <20021009081619.A96DD69E33@imap.heidelberg.ccrle.nec.de> Content-Transfer-Encoding: 7bit Subject: [manet] Workshop on Ad Hoc Security... Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear all, for those of you who are interested in security issues in ad hoc networks, the attached call for participation may be interesting. Best regards, Dirk Westhoff P.S: The URL will be available next week -------------------------------------------------------------------- 1st Workshop on Security in Ad-Hoc Networks www.crypto.rub.de/adhocsec Ruhr University Bochum, Germany December 2, 2002 Call for Participation General Information: It is expected that the next generation of IT applications will rely heavily on ad-hoc networks. Such networks are characterized by their dynamic structure, lack of fixed infrastructure, and constrained resources. In order to allow their successful deployment various security challenges must be solved. Examples include missing apriori security associations, the lack of a trusted infrastructure, as well as computing, memory and energy constrains. Due to the predicted pervasive nature of applications relying on ad-hoc networks makes effective provisions for robust security solutions must be taken. This one day workshop offers invited talks by leading experts on various aspects of ad-hoc network security. The talks will provide an overview on the various security issues involved and discuss new research in the area. In addition, the workshop will allow the informal exchange of ideas and building of a research network. Speakers: 1) Bill Arbaugh (U.S. Department of Defense) 2) Susanne Wetzel (Stevens Institute of Technology, USA) 3) Konrad Wrona (MIT Media Lab) 4) Sonja Buchegger (IBM Zuerich, Swiss) 5) Jean-Pierre Hubaux (Swiss Federal Institute of Technology - Lausanne) 6) Manel Guerrero Zapata (Nokia Research Center, Finland) Mailing List: If you want to receive emails with subsequent Call for Papers and registration information, please send a brief mail to adhocsec@crypto.rub.de Program Committee: Dirk Westhoff NEC Networks Labs Heidelberg, Germany Christof Paar Ruhr University Bochum, Germany Susanne Wetzel Stevens Institute of Technology, USA Registration: The registration form can be found at crypto.rub.de/adhocsec Workshop Proceedings: There will be no formal proceedings. However, the presentation slides of all speakers will be made available to the attendees. -- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 12:26:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08154 for ; Thu, 10 Oct 2002 11:36:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AFUhv16548; Thu, 10 Oct 2002 11:30:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91Famv10441 for ; Tue, 1 Oct 2002 11:36:48 -0400 Received: from ece.ufl.edu (dot.ece.ufl.edu [128.227.220.22]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA22669 for ; Tue, 1 Oct 2002 11:34:47 -0400 (EDT) Received: (qmail 28716 invoked from network); 1 Oct 2002 15:33:11 -0000 Received: from fang.ece.ufl.edu (128.227.80.157) by smtp.ece.ufl.edu with SMTP; 1 Oct 2002 15:33:11 -0000 Received: (from fang@localhost) by fang.ece.ufl.edu (8.9.3/8.9.3) id LAA20326; Tue, 1 Oct 2002 11:34:11 -0400 (EDT) X-Authentication-Warning: fang.ece.ufl.edu: Processed from queue /home/faculty/fang/mqueue X-Authentication-Warning: fang.ece.ufl.edu: Processed by fang with -C /home/faculty/fang/bin/sendmail.cf Date: Tue, 1 Oct 2002 11:34:10 -0400 From: Yuguang Fang To: Yuguang Fang Message-ID: <20021001113410.B20314@ece.ufl.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i Subject: [manet] SCS SPECTS'2003 Call for Papers Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , I apologize if you receive multiple copies of this message. Call For Papers %%%%%%%%%%%%%%%% 2003 International Symposium on Performance Evaluation of Computer and Telecommunication Systems (SPECTS 2003) July 20-24, 2003 Montreal, Canada http://scs.org/confernc/ssimc/ssimc03/cfp/spects03.htm Submission Deadlines Submission of Papers: January 31, 2003. Notification of Acceptance - April 25, 2003 Final Camera-Ready Submission - May 23, 2003 This annual international conference is a forum for professionals involved in performance evaluation of computer and telecommunication systems. Evaluation of computer systems and networks is needed at every stage in the life cycle of the product including design, manufacturing, sales/purchase, use, upgrade, tuning, etc. The discipline of performance evaluation has progressed rapidly in the past decade, and it has now begun to approach maturity. Significant progress has been made in analytic modeling, simulation, and measurement approaches for performance evaluation of computer and telecommunication systems. Topics of interest include, but are not limited to: Networking and Telecommunication Systems - Internet Technology - Quality of Service (QoS) - DiffServ/IntServ - MPLS - TCP - World Wide Web (WWW) Technology - Networking Techniques - Unicast and Multicast Routing - Congestion Control - Switching Techniques - Teletraffic - Network Protocols - Network Management and Control - Network Capacity Planning - Network Architecture Evaluation - Service and QoS Pricing - Security and Authentication -Broadband Networks - High-Speed Networking - ATM - Optical Networks - Wireless Systems and Networks - Satellite Systems - UMTS - Mobile Networks/Computing - Ad-hoc networks - Multimedia Communications Computer Systems - Distributed Architectures - Client/Server - Distributed Systems and Agents - Parallel and Distributed Computing - Massively Parallel Systems - Cluster Computing - Grid Computing - Interconnection Networks - Computer Architectures - Microprocessors/Microcomputers - Memory Systems - High Performance I/O - Real-time Systems - Scheduling Schemes -Software - Software Performance, Evaluation and Testing - Parallel Algorithms and Languages - Hardware and Software Monitors - High-Performance Computing - Workload and Traffic Characterization - Scientific Computing Algorithms - Reconfigurable Computing - Electronic Commerce Tools, Methodologies and Applications - Parallel and Distributed Simulation - Verification and Validation - Performance Tools and Methodologies - Neural Networks and Fuzzy Logic Applications to High Performance Computing/Networking - Performance Optimization - Queueing Systems and Networks - Scalability Studies - Integrated Modeling and Measurement - On-Line Performance Adaptation and Tuning - Process Algebra-Based Models - Performance Bounds - Integrated Design and Performance - New Performance Models - Mathematical Aspects of Performance - New Performability Schemes and Models - Case Studies General Chair Mohammad S. Obaidat Dept. of Computer Science, Monmouth University W. Long Branch, NJ 07764, USA Tel +1-732-571-4482 Fax +1-732-263-5202 E-mail: obaidat@monmouth.edu Senior Program Chair Franco Davoli DIST-University of Genoa Via Opera Pia 13, I-16145 Genoa, Italy Tel +39-010-353-2732 Fax +39-010-353-2154 E-Mail: franco@dist.unige.it Program Co-Chairs Ibrahim Onyuksel Dept. of Computer Sciences, N. Illinois Univ., USA E-mail: onyuksel@cs.niu.edu Erina Ferro ISTI, Institute of National Research Council (C.N.R.) C.N.R. Pisa Research Area, Building B, Room 73 Via G. Moruzzi, 1 56124 Pisa, Italy E-mail: erina.ferro@cnuce.cnr.it Vice Program Chair and Tutorial Chair Raffaele Bolla DIST-University of Genoa Via Opera Pia 13, I-16145 Genoa, Italy E-mail: lelus@dist.unige.it Vice Program Chair and Web Master Imad Mahgoub Department of Computer Science and Engineering Florida Atlantic University Boca Raton, FL 33431 E-mail: imad@cse.fau.edu Industrial Track and Special Sessions Chair J. Fox, Motorola Inc., UK E-mail: fox.ijcs@btinternet.com Technical Program Committee Ian Akyildiz, Georgia Tech., USA Mohammed Atiquzzaman, University of Oklahoma, USA Louis G. Birta, University of Ottawa, Canada Abdullah Abonamah, Zayed University, UAE Noureddine Boudriga, University of Tunis, Tunisia Hasan Cam, University of Arkansas, USA Andrew Campbell, Columbia University, USA Nedo Celandroni, ISTI-CNR, Italy Haitham Cruickshank, University of Surrey, UK Hassan B. Diab, American University of Beirut, Lebanon Gabor Fodor, Ericsson Radio Systems, Sweden Geoffrey Fox, Indiana University, USA Luigi Fratta, Politecnico di Milano, Italy Aura Ganz, University of Massachusetts, USA Erol Gelenbe, University of Central Florida, USA Mario Gerla, UCLA, USA Sami Habib, Kuwait University, Kuwait Omar Hammami, ENSTA, France Jarmo Harju, Tampere University of Technology, Finland Herman Hughes, Michigan State University, USA Andrzej Jajszczyk, University of Mining and Metallurgy, Poland Abbas Jamalipour, University of Sydney, Australia Ingemar Kaj, Uppsala University, Sweden Krishna Kant, Intel, USA Helen Karatza, Aristotle University of Thessalonica, Greece Demetrios Kazakos, University of Louisiana, USA Ulrich Killat, Tech Univ. of Hamburg, Germany Tag Gon Kim, KAIST, Korea Kevin Kwiat, Air Force Research Laboratory, USA Veronica Lagrange M. Reis, Compaq Computers Corp., USA Axel Lehmann, Universitdt der Bundeswehr M|nchen, Germany Daniel C. Lee, USC, USA Mike T. Liu, Ohio State University, USA Erich Lutz, DLR, Germany Sam Makki, Queensland University of Technology, Australia Krzysztof Malinowski, Warsaw Technical University, Poland Mario Marchese, University of Genoa, Italy Jose L. Marzo, Universitat de Girona, Spain Xiannong Meng, Bucknell University, USA Hussein Mouftah, Queen's University, Canada Mohamed Ould-Khaoua, University of Glasgow, UK Sergio Palazzo, Universit` di Catania, Italy Georgios I. Papadimitriou, Aristotle University, Greece Achille Pattavina, Politecnico di Milano, Italy Krzysztof Pawlikowski, University of Canterbury, New Zealand Gregory D. Peterson, University of Tennessee Steven Pink, University of Arizona, USA George Polyzos, AUEB, Greece Ramon Puigjaner, Universitat de les Illes Balears, Spain Kaliappa Ravindran, CUNY, USA Gian Paolo Rossi, Universit` di Milano, Italy Izhak Rubin, UCLA, USA Vicente Santonja, Technical University of Valencia, Spain Donald Schilling, CUNY, USA Jens B. Schmitt, TU Darmstadt, Germany Harald Skinnemoen, Nera, Norway Tatsuya Suda, UCI, USA Iwao Toda, Fujutsu Laboratories Ltd., Japan Phuoc Tran-Gia, University of Wuerzburg, Germany Kishor Trivedi, Duke University, USA Kenneth S. Vastola, Rensselaer Polytechnic Institute, USA Manuel Villen-Altamirano, Telefonica, Spain Bernd E. Wolfinger, Hamburg University, Germany Michele Zorzi, Universit` di Ferrara, Italy Publicity Chair: Yuguang (Michael) Fang, University of Florida, USA, E-mail: fang@ece.ufl.edu Publicity Committee: Jie Li, University of Tsukuba, Japan Chiara Petrioli, Universita` di Roma "La Sapienza", Italy Chuck Song, Chinese Academy of Sciences, China Ahmed Nuseirat, Al-Isra University, Jordan International Liaisons B. Sadoun, Al-Balqa' Applied University, Jordan Bsadoun@go.com.jo M. Sawan, Montreal Poly, Canada Sawan@vlsi.polymtl.ca N. Tchamov, Tampere Univ. of Technology, Finland Nikolay@cs.tut.fi Paper Submission Submit your complete papers electronically to: http://scs.proceedingscentral.com/ All required instructions will be posted on this web site. Submissions should not exceed 25 double-spaced, 8.5x11 inch pages (including figures, tables, and references) in 10-12 point font. Include five to ten keywords, complete postal and e-mail addresses, and fax and phone numbers of corresponding author. If you have difficulty in electronic submission, contact the Web Master, Program Chairs or the Conference Coordinator, Mr. Steve Branch, The Society for Modeling and Simulation International, 4838 Ronson Court, Suite L, San Diego, CA 92111, USA, Tel 858-277-3888, Fax 858-277-3930, E-mail sbranch@scs.org Extended versions of selected accepted papers in SPECTS 2003 will be considered for possible publication in scholarly journals. Proposals for tutorials should be sent to the Conference Vice Program Chair, Raffaele Bolla. Proposals for special sessions and panel sessions should be submitted to the special Sessions Chair. For more information regarding presentations or exhibitions at SPECTS 2002 contact: Mr. Steve Branch at the address shown above. Sponsored by The Society for Modeling and Simulation International. -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Yuguang "Michael" Fang, Ph.D Assistant Professor Department of Electrical and Computer Engineering University of Florida 435 Engineering Building, P.O.Box 116130 Gainesville, FL 32611 Tel: (352) 846-3043, Fax: (352) 392-0044 Email: fang@ece.ufl.edu, http://www.fang.ece.ufl.edu %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 13:47:21 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17362 for ; Thu, 10 Oct 2002 13:47:21 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AHiPv25489; Thu, 10 Oct 2002 13:44:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AHgrv25446 for ; Thu, 10 Oct 2002 13:42:53 -0400 Received: from amber.ccs.neu.edu (postfix@amber.ccs.neu.edu [129.10.116.51]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16796 for ; Thu, 10 Oct 2002 13:40:42 -0400 (EDT) Received: from denali.ccs.neu.edu (denali.ccs.neu.edu [129.10.116.200]) by amber.ccs.neu.edu (Postfix) with ESMTP id 9F4891AA8A; Thu, 10 Oct 2002 13:39:08 -0400 (EDT) Date: Thu, 10 Oct 2002 13:39:08 -0400 (EDT) From: Guevara Noubir To: lining73@vip.sina.com Cc: manet@ietf.org Subject: Re: [manet] radio transmission levels In-Reply-To: <20021010025009.867.qmail@vip.sina.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Cisco Aironet 350 cards have 6 power levels (http://www.cisco.com/warp/public/44/jump/wireless.shtml). IEEE802.11 standard specifices 7 possible power levels. Guevara On Thu, 10 Oct 2002 lining73@vip.sina.com wrote: > Hello everbody: > In some papers related to power controlled MAC protocols in MANET, the power levels used are always different by different author. > I want to know are there any real NICs with power control property which can be use in MANET? How many transmit power levels can be used and how much is the difference between maximum & minimum transmit power. > Regards. > ______________________________________ > > =================================================================== > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 13:50:24 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17479 for ; Thu, 10 Oct 2002 13:50:24 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AHq4w25713 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 13:52:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AHq4v25710 for ; Thu, 10 Oct 2002 13:52:04 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17467 for ; Thu, 10 Oct 2002 13:49:53 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AHiPv25489; Thu, 10 Oct 2002 13:44:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AHgrv25446 for ; Thu, 10 Oct 2002 13:42:53 -0400 Received: from amber.ccs.neu.edu (postfix@amber.ccs.neu.edu [129.10.116.51]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16796 for ; Thu, 10 Oct 2002 13:40:42 -0400 (EDT) Received: from denali.ccs.neu.edu (denali.ccs.neu.edu [129.10.116.200]) by amber.ccs.neu.edu (Postfix) with ESMTP id 9F4891AA8A; Thu, 10 Oct 2002 13:39:08 -0400 (EDT) Date: Thu, 10 Oct 2002 13:39:08 -0400 (EDT) From: Guevara Noubir To: lining73@vip.sina.com Cc: manet@ietf.org Subject: Re: [manet] radio transmission levels In-Reply-To: <20021010025009.867.qmail@vip.sina.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Cisco Aironet 350 cards have 6 power levels (http://www.cisco.com/warp/public/44/jump/wireless.shtml). IEEE802.11 standard specifices 7 possible power levels. Guevara On Thu, 10 Oct 2002 lining73@vip.sina.com wrote: > Hello everbody: > In some papers related to power controlled MAC protocols in MANET, the power levels used are always different by different author. > I want to know are there any real NICs with power control property which can be use in MANET? How many transmit power levels can be used and how much is the difference between maximum & minimum transmit power. > Regards. > ______________________________________ > > =================================================================== > _______________________________________________ > 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-admin@ietf.org Thu Oct 10 14:06:35 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18153 for ; Thu, 10 Oct 2002 14:06:35 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AI3Rv26371; Thu, 10 Oct 2002 14:03:27 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AI2sv26296 for ; Thu, 10 Oct 2002 14:02:54 -0400 Received: from smtp2.libero.it (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17937 for ; Thu, 10 Oct 2002 14:00:43 -0400 (EDT) Received: from f1u2i7 (62.98.119.149) by smtp2.libero.it (6.5.028) id 3DA310EC0010C463 for manet@ietf.org; Thu, 10 Oct 2002 20:02:46 +0200 Message-ID: <001201c27088$8ab9f0e0$9577623e@f1u2i7> From: "Luca S." To: Date: Thu, 10 Oct 2002 20:07:16 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C27098.A1252060" 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 Subject: [manet] AODV and OMNET++ Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Messaggio in formato MIME composto da piy parti. ------=_NextPart_000_000B_01C27098.A1252060 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi at everyone. I am a new member in this mailing list. I am looking for = a help in my research. I should implement an ad-hoc network on the = omnetpp simulator platform. The target of my work is carry out the = routing algorithm AODV. Has someone already made something here? Can = someone send me your simulation packet? =20 =20 Thank you to all for cooperation. =20 =20 Regard, =20 Luca S. ------=_NextPart_000_000B_01C27098.A1252060 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi at everyone. I am a new member in = this mailing=20 list. I am looking for a help in my research. I should implement an = ad-hoc=20 network on the omnetpp simulator platform. The target of my work is = carry out=20 the routing algorithm AODV. Has someone already made something here? Can = someone=20 send me your simulation packet? 
 
Thank you to all = for=20 cooperation. 
 
Regard, 
Luca=20 S.
------=_NextPart_000_000B_01C27098.A1252060-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 14:10:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18366 for ; Thu, 10 Oct 2002 14:10:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AICMH27240 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 14:12:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AICMv27237 for ; Thu, 10 Oct 2002 14:12:22 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18316 for ; Thu, 10 Oct 2002 14:10:11 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AI3Rv26371; Thu, 10 Oct 2002 14:03:27 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AI2sv26296 for ; Thu, 10 Oct 2002 14:02:54 -0400 Received: from smtp2.libero.it (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17937 for ; Thu, 10 Oct 2002 14:00:43 -0400 (EDT) Received: from f1u2i7 (62.98.119.149) by smtp2.libero.it (6.5.028) id 3DA310EC0010C463 for manet@ietf.org; Thu, 10 Oct 2002 20:02:46 +0200 Message-ID: <001201c27088$8ab9f0e0$9577623e@f1u2i7> From: "Luca S." To: Date: Thu, 10 Oct 2002 20:07:16 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C27098.A1252060" 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 Subject: [manet] AODV and OMNET++ Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Messaggio in formato MIME composto da piy parti. ------=_NextPart_000_000B_01C27098.A1252060 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi at everyone. I am a new member in this mailing list. I am looking for = a help in my research. I should implement an ad-hoc network on the = omnetpp simulator platform. The target of my work is carry out the = routing algorithm AODV. Has someone already made something here? Can = someone send me your simulation packet? =20 =20 Thank you to all for cooperation. =20 =20 Regard, =20 Luca S. ------=_NextPart_000_000B_01C27098.A1252060 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi at everyone. I am a new member in = this mailing=20 list. I am looking for a help in my research. I should implement an = ad-hoc=20 network on the omnetpp simulator platform. The target of my work is = carry out=20 the routing algorithm AODV. Has someone already made something here? Can = someone=20 send me your simulation packet? 
 
Thank you to all = for=20 cooperation. 
 
Regard, 
Luca=20 S.
------=_NextPart_000_000B_01C27098.A1252060-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 14:42:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19235 for ; Thu, 10 Oct 2002 14:42:26 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AIi7128949 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 14:44:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AIi7v28946 for ; Thu, 10 Oct 2002 14:44:07 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19222 for ; Thu, 10 Oct 2002 14:41:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AIdjv28752; Thu, 10 Oct 2002 14:39:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AIc2v28701 for ; Thu, 10 Oct 2002 14:38:02 -0400 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19115 for ; Thu, 10 Oct 2002 14:35:50 -0400 (EDT) Received: (from dyoung@localhost) by che.onthejob.net (8.9.3/8.9.3) id NAA16827 for manet@ietf.org; Thu, 10 Oct 2002 13:37:56 -0500 Date: Thu, 10 Oct 2002 13:37:56 -0500 From: David Young To: manet@ietf.org Subject: Re: [manet] radio transmission levels Message-ID: <20021010133756.A13988@che.onthejob.net> Reply-To: dyoung@pobox.com Mail-Followup-To: David Young , manet@ietf.org References: <20021010025009.867.qmail@vip.sina.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20021010025009.867.qmail@vip.sina.com>; from lining73@vip.sina.com on Thu, Oct 10, 2002 at 10:50:09AM +0800 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , The Cisco Aironet 350 cards are adjustable to 1, 5, 20, 30, 50, and 100 mW. I have heard that you have to do a reset between adjustments, however. You can write a register on the baseband processor of the Prism 2.x chipsets to adjust the power setting "goal." You read another register to find out the actual level. I cannot find the units for the registers in any document, however, the firmware may store some hints produced when the manufacturer calibrated the radio. The firmware implements an automatic TX level control, I think; you will have to disable that before you make your own adjustments. I do not know the minimum TX level for any Prism radio, but there are 100, 180, and 200mW Prism radios. There may be a prohibitive time-cost to adjusting TX levels, if you want to do it on a per-packet basis. I do not know the expense of adjusting power on the Prism 2.x chipsets, but it could be high. On Cisco's 350, resets are probably very expensive. If you limit yourself to queueing just one packet at a time on the NIC, and if you accept more interrupts, then you can trade performance to ensure per-packet TX power adjustments. I think that it is desirable to be "sloppy" or "lazy" with TX power adjustments, myself: guarantee that each packet is sent at LEAST as "loudly" as its TX power label indicates. When you cannot afford a power adjustment---because, for example, you would have to wait for the TX queue to empty---send some packets more loudly than indicated. Dave On Thu, Oct 10, 2002 at 10:50:09AM +0800, lining73@vip.sina.com wrote: > Hello everbody: > In some papers related to power controlled MAC protocols in MANET, the power levels used are always different by different author. > I want to know are there any real NICs with power control property which can be use in MANET? How many transmit power levels can be used and how much is the difference between maximum & minimum transmit power. > Regards. > ______________________________________ > > =================================================================== > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 14:42:29 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19250 for ; Thu, 10 Oct 2002 14:42:29 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AIdjv28752; Thu, 10 Oct 2002 14:39:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AIc2v28701 for ; Thu, 10 Oct 2002 14:38:02 -0400 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19115 for ; Thu, 10 Oct 2002 14:35:50 -0400 (EDT) Received: (from dyoung@localhost) by che.onthejob.net (8.9.3/8.9.3) id NAA16827 for manet@ietf.org; Thu, 10 Oct 2002 13:37:56 -0500 Date: Thu, 10 Oct 2002 13:37:56 -0500 From: David Young To: manet@ietf.org Subject: Re: [manet] radio transmission levels Message-ID: <20021010133756.A13988@che.onthejob.net> Reply-To: dyoung@pobox.com Mail-Followup-To: David Young , manet@ietf.org References: <20021010025009.867.qmail@vip.sina.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20021010025009.867.qmail@vip.sina.com>; from lining73@vip.sina.com on Thu, Oct 10, 2002 at 10:50:09AM +0800 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , The Cisco Aironet 350 cards are adjustable to 1, 5, 20, 30, 50, and 100 mW. I have heard that you have to do a reset between adjustments, however. You can write a register on the baseband processor of the Prism 2.x chipsets to adjust the power setting "goal." You read another register to find out the actual level. I cannot find the units for the registers in any document, however, the firmware may store some hints produced when the manufacturer calibrated the radio. The firmware implements an automatic TX level control, I think; you will have to disable that before you make your own adjustments. I do not know the minimum TX level for any Prism radio, but there are 100, 180, and 200mW Prism radios. There may be a prohibitive time-cost to adjusting TX levels, if you want to do it on a per-packet basis. I do not know the expense of adjusting power on the Prism 2.x chipsets, but it could be high. On Cisco's 350, resets are probably very expensive. If you limit yourself to queueing just one packet at a time on the NIC, and if you accept more interrupts, then you can trade performance to ensure per-packet TX power adjustments. I think that it is desirable to be "sloppy" or "lazy" with TX power adjustments, myself: guarantee that each packet is sent at LEAST as "loudly" as its TX power label indicates. When you cannot afford a power adjustment---because, for example, you would have to wait for the TX queue to empty---send some packets more loudly than indicated. Dave On Thu, Oct 10, 2002 at 10:50:09AM +0800, lining73@vip.sina.com wrote: > Hello everbody: > In some papers related to power controlled MAC protocols in MANET, the power levels used are always different by different author. > I want to know are there any real NICs with power control property which can be use in MANET? How many transmit power levels can be used and how much is the difference between maximum & minimum transmit power. > Regards. > ______________________________________ > > =================================================================== > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 15:17:49 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20359 for ; Thu, 10 Oct 2002 15:17:49 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AJJUL30664 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 15:19:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJJUv30661 for ; Thu, 10 Oct 2002 15:19:30 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20319 for ; Thu, 10 Oct 2002 15:17:18 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJI3v30551; Thu, 10 Oct 2002 15:18:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJEhv30412 for ; Thu, 10 Oct 2002 15:14:43 -0400 Received: from smtp2.opnet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20193 for ; Thu, 10 Oct 2002 15:12:31 -0400 (EDT) Received: from wtn11019 (wtn11019.opnet.com) by smtp2.opnet.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Thu, 10 Oct 2002 15:14:30 -0400 Message-Id: <4.2.0.58.20021010151248.02126500@mail.opnet.com> X-Sender: krao@mail.opnet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 10 Oct 2002 15:14:30 -0400 To: manet@ietf.org From: Kartik Rao Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [manet] DSR in TCP/IP stack Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Does anyone know where DSR sits in the TCP/IP stack? (between IP and MAC, at IP, between TCP and IP, above TCP) Thanks, Kartik _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 15:17:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20393 for ; Thu, 10 Oct 2002 15:17:51 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJI3v30551; Thu, 10 Oct 2002 15:18:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJEhv30412 for ; Thu, 10 Oct 2002 15:14:43 -0400 Received: from smtp2.opnet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20193 for ; Thu, 10 Oct 2002 15:12:31 -0400 (EDT) Received: from wtn11019 (wtn11019.opnet.com) by smtp2.opnet.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Thu, 10 Oct 2002 15:14:30 -0400 Message-Id: <4.2.0.58.20021010151248.02126500@mail.opnet.com> X-Sender: krao@mail.opnet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 10 Oct 2002 15:14:30 -0400 To: manet@ietf.org From: Kartik Rao Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [manet] DSR in TCP/IP stack Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Does anyone know where DSR sits in the TCP/IP stack? (between IP and MAC, at IP, between TCP and IP, above TCP) Thanks, Kartik _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 15:17:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20399 for ; Thu, 10 Oct 2002 15:17:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJIPv30594; Thu, 10 Oct 2002 15:18:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJFcv30444 for ; Thu, 10 Oct 2002 15:15:38 -0400 Received: from smtp2.opnet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20209 for ; Thu, 10 Oct 2002 15:13:26 -0400 (EDT) Received: from wtn11019 (wtn11019.opnet.com) by smtp2.opnet.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Thu, 10 Oct 2002 15:15:25 -0400 Message-Id: <4.2.0.58.20021010151434.0212e9a0@mail.opnet.com> X-Sender: krao@mail.opnet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 10 Oct 2002 15:15:25 -0400 To: manet@ietf.org From: Kartik Rao Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [manet] IP routing table and DSR routing table Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Is there any interaction between the IP forwarding table and the DSR routing table (route cache)? _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 15:57:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21775 for ; Thu, 10 Oct 2002 15:57:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AJxTc32760 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 15:59:29 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJxTv32756 for ; Thu, 10 Oct 2002 15:59:29 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21749 for ; Thu, 10 Oct 2002 15:57:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJvhv32720; Thu, 10 Oct 2002 15:57:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJu5v32679 for ; Thu, 10 Oct 2002 15:56:05 -0400 Received: from mailhub.Dartmouth.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21608 for ; Thu, 10 Oct 2002 15:53:53 -0400 (EDT) Received: from newdancer.Dartmouth.EDU (newdancer.dartmouth.edu [129.170.208.31]) by mailhub.Dartmouth.EDU (8.9.3+DND/8.9.3) with ESMTP id PAA15620; Thu, 10 Oct 2002 15:55:58 -0400 (EDT) Message-id: <2437308@newdancer.Dartmouth.EDU> Date: 10 Oct 2002 15:55:54 EDT From: Noah.H.Miller@Dartmouth.EDU (Noah H. Miller) Reply-To: Noah.H.Miller@Dartmouth.EDU (TrustMeImTellingYouStories) Subject: Re: [manet] DSR in TCP/IP stack To: krao@opnet.com (Kartik Rao), manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --- You wrote: --- Does anyone know where DSR sits in the TCP/IP stack? (between IP and MAC,at IP, between TCP and IP, above TCP) Thanks,Kartik --- end of quote --- IETF Draft 7 for DSR (; Thu, 10 Oct 2002 15:57:50 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJvhv32720; Thu, 10 Oct 2002 15:57:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJu5v32679 for ; Thu, 10 Oct 2002 15:56:05 -0400 Received: from mailhub.Dartmouth.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21608 for ; Thu, 10 Oct 2002 15:53:53 -0400 (EDT) Received: from newdancer.Dartmouth.EDU (newdancer.dartmouth.edu [129.170.208.31]) by mailhub.Dartmouth.EDU (8.9.3+DND/8.9.3) with ESMTP id PAA15620; Thu, 10 Oct 2002 15:55:58 -0400 (EDT) Message-id: <2437308@newdancer.Dartmouth.EDU> Date: 10 Oct 2002 15:55:54 EDT From: Noah.H.Miller@Dartmouth.EDU (Noah H. Miller) Reply-To: Noah.H.Miller@Dartmouth.EDU (TrustMeImTellingYouStories) Subject: Re: [manet] DSR in TCP/IP stack To: krao@opnet.com (Kartik Rao), manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --- You wrote: --- Does anyone know where DSR sits in the TCP/IP stack? (between IP and MAC,at IP, between TCP and IP, above TCP) Thanks,Kartik --- end of quote --- IETF Draft 7 for DSR (; Thu, 10 Oct 2002 16:04:09 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AK4Cv00511; Thu, 10 Oct 2002 16:04:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AK11v00392 for ; Thu, 10 Oct 2002 16:01:01 -0400 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21837 for ; Thu, 10 Oct 2002 15:58:48 -0400 (EDT) Received: from e500a.comp.nus.edu.sg (e500a.comp.nus.edu.sg [137.132.90.23]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id EAA18435; Fri, 11 Oct 2002 04:00:53 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500a.comp.nus.edu.sg via csmap id 15232; Fri, 11 Oct 2002 03:51:58 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id EAA21380; Fri, 11 Oct 2002 04:00:52 +0800 (GMT-8) Date: Fri, 11 Oct 2002 04:00:52 +0800 (GMT-8) From: Sourabh Sharma To: Kartik Rao cc: manet@ietf.org Subject: Re: [manet] DSR in TCP/IP stack In-Reply-To: <4.2.0.58.20021010151248.02126500@mail.opnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Thu, 10 Oct 2002, Kartik Rao wrote: > Does anyone know where DSR sits in the TCP/IP stack? (between IP and MAC, > at IP, between TCP and IP, above TCP) hi, These are implementation details, which can vary from one impl... to another.( kernel space or user space) but the most general one is this. a virtual interface (say dsr0) is created. all the AdNETwrk packets are sent to this interface, which keeps them in a store buffer.( by the time it does a route discovery). Anyway, I am not going to explain you the whole implementation here. Cutting it short, here DSR sits at the IP layer. ( some might say .. tht its actually below it!) -Sourabh Sharma Centre for Internet Research, National University of Singapore. > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 16:08:06 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22181 for ; Thu, 10 Oct 2002 16:08:06 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AK9mW01325 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 16:09:48 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AK9mv01322 for ; Thu, 10 Oct 2002 16:09:48 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22173 for ; Thu, 10 Oct 2002 16:07:35 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AK4Cv00511; Thu, 10 Oct 2002 16:04:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AK11v00392 for ; Thu, 10 Oct 2002 16:01:01 -0400 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21837 for ; Thu, 10 Oct 2002 15:58:48 -0400 (EDT) Received: from e500a.comp.nus.edu.sg (e500a.comp.nus.edu.sg [137.132.90.23]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id EAA18435; Fri, 11 Oct 2002 04:00:53 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500a.comp.nus.edu.sg via csmap id 15232; Fri, 11 Oct 2002 03:51:58 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id EAA21380; Fri, 11 Oct 2002 04:00:52 +0800 (GMT-8) Date: Fri, 11 Oct 2002 04:00:52 +0800 (GMT-8) From: Sourabh Sharma To: Kartik Rao cc: manet@ietf.org Subject: Re: [manet] DSR in TCP/IP stack In-Reply-To: <4.2.0.58.20021010151248.02126500@mail.opnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Thu, 10 Oct 2002, Kartik Rao wrote: > Does anyone know where DSR sits in the TCP/IP stack? (between IP and MAC, > at IP, between TCP and IP, above TCP) hi, These are implementation details, which can vary from one impl... to another.( kernel space or user space) but the most general one is this. a virtual interface (say dsr0) is created. all the AdNETwrk packets are sent to this interface, which keeps them in a store buffer.( by the time it does a route discovery). Anyway, I am not going to explain you the whole implementation here. Cutting it short, here DSR sits at the IP layer. ( some might say .. tht its actually below it!) -Sourabh Sharma Centre for Internet Research, National University of Singapore. > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 16:11:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20366 for ; Thu, 10 Oct 2002 15:17:49 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AJJVl30679 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 15:19:31 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJJUv30676 for ; Thu, 10 Oct 2002 15:19:30 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20322 for ; Thu, 10 Oct 2002 15:17:18 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJIPv30594; Thu, 10 Oct 2002 15:18:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AJFcv30444 for ; Thu, 10 Oct 2002 15:15:38 -0400 Received: from smtp2.opnet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20209 for ; Thu, 10 Oct 2002 15:13:26 -0400 (EDT) Received: from wtn11019 (wtn11019.opnet.com) by smtp2.opnet.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Thu, 10 Oct 2002 15:15:25 -0400 Message-Id: <4.2.0.58.20021010151434.0212e9a0@mail.opnet.com> X-Sender: krao@mail.opnet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 10 Oct 2002 15:15:25 -0400 To: manet@ietf.org From: Kartik Rao Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [manet] IP routing table and DSR routing table Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Is there any interaction between the IP forwarding table and the DSR routing table (route cache)? _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 16:26:51 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22672 for ; Thu, 10 Oct 2002 16:26:51 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AKQov01938; Thu, 10 Oct 2002 16:26:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AKN6v01810 for ; Thu, 10 Oct 2002 16:23:06 -0400 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22472 for ; Thu, 10 Oct 2002 16:20:52 -0400 (EDT) Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g9AKMwh454650 for ; Thu, 10 Oct 2002 16:22:58 -0400 (EDT) Received: from ari424h (ari424-h.ari.vt.edu [208.17.194.135]) by vivi.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1.6-EA) with ESMTP id AKS67164; Thu, 10 Oct 2002 16:22:57 -0400 (EDT) From: "Kaustubh S. Phanse" To: Subject: RE: [manet] radio transmission levels Date: Thu, 10 Oct 2002 16:35:46 -0400 Message-ID: <001d01c2709c$9cbbd600$87c211d0@ari.vt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-reply-to: <20021010133756.A13988@che.onthejob.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Linksys IEEE 802.11b cards (based on Intersil Prism chipset) also support adjustable transmit power...I think it ranges from -44dBm to 20dBm. regards Kaustubh -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of David Young Sent: Thursday, October 10, 2002 2:38 PM To: manet@ietf.org Subject: Re: [manet] radio transmission levels The Cisco Aironet 350 cards are adjustable to 1, 5, 20, 30, 50, and 100 mW. I have heard that you have to do a reset between adjustments, however. You can write a register on the baseband processor of the Prism 2.x chipsets to adjust the power setting "goal." You read another register to find out the actual level. I cannot find the units for the registers in any document, however, the firmware may store some hints produced when the manufacturer calibrated the radio. The firmware implements an automatic TX level control, I think; you will have to disable that before you make your own adjustments. I do not know the minimum TX level for any Prism radio, but there are 100, 180, and 200mW Prism radios. There may be a prohibitive time-cost to adjusting TX levels, if you want to do it on a per-packet basis. I do not know the expense of adjusting power on the Prism 2.x chipsets, but it could be high. On Cisco's 350, resets are probably very expensive. If you limit yourself to queueing just one packet at a time on the NIC, and if you accept more interrupts, then you can trade performance to ensure per-packet TX power adjustments. I think that it is desirable to be "sloppy" or "lazy" with TX power adjustments, myself: guarantee that each packet is sent at LEAST as "loudly" as its TX power label indicates. When you cannot afford a power adjustment---because, for example, you would have to wait for the TX queue to empty---send some packets more loudly than indicated. Dave On Thu, Oct 10, 2002 at 10:50:09AM +0800, lining73@vip.sina.com wrote: > Hello everbody: > In some papers related to power controlled MAC protocols in MANET, the power levels used are always different by different author. > I want to know are there any real NICs with power control property which can be use in MANET? How many transmit power levels can be used and how much is the difference between maximum & minimum transmit power. > Regards. > ______________________________________ > > =================================================================== > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 10 16:30:04 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22812 for ; Thu, 10 Oct 2002 16:30:04 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9AKVkV02227 for manet-archive@odin.ietf.org; Thu, 10 Oct 2002 16:31:46 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AKVkv02224 for ; Thu, 10 Oct 2002 16:31:46 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22798 for ; Thu, 10 Oct 2002 16:29:33 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AKQov01938; Thu, 10 Oct 2002 16:26:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AKN6v01810 for ; Thu, 10 Oct 2002 16:23:06 -0400 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22472 for ; Thu, 10 Oct 2002 16:20:52 -0400 (EDT) Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g9AKMwh454650 for ; Thu, 10 Oct 2002 16:22:58 -0400 (EDT) Received: from ari424h (ari424-h.ari.vt.edu [208.17.194.135]) by vivi.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1.6-EA) with ESMTP id AKS67164; Thu, 10 Oct 2002 16:22:57 -0400 (EDT) From: "Kaustubh S. Phanse" To: Subject: RE: [manet] radio transmission levels Date: Thu, 10 Oct 2002 16:35:46 -0400 Message-ID: <001d01c2709c$9cbbd600$87c211d0@ari.vt.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-reply-to: <20021010133756.A13988@che.onthejob.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Linksys IEEE 802.11b cards (based on Intersil Prism chipset) also support adjustable transmit power...I think it ranges from -44dBm to 20dBm. regards Kaustubh -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of David Young Sent: Thursday, October 10, 2002 2:38 PM To: manet@ietf.org Subject: Re: [manet] radio transmission levels The Cisco Aironet 350 cards are adjustable to 1, 5, 20, 30, 50, and 100 mW. I have heard that you have to do a reset between adjustments, however. You can write a register on the baseband processor of the Prism 2.x chipsets to adjust the power setting "goal." You read another register to find out the actual level. I cannot find the units for the registers in any document, however, the firmware may store some hints produced when the manufacturer calibrated the radio. The firmware implements an automatic TX level control, I think; you will have to disable that before you make your own adjustments. I do not know the minimum TX level for any Prism radio, but there are 100, 180, and 200mW Prism radios. There may be a prohibitive time-cost to adjusting TX levels, if you want to do it on a per-packet basis. I do not know the expense of adjusting power on the Prism 2.x chipsets, but it could be high. On Cisco's 350, resets are probably very expensive. If you limit yourself to queueing just one packet at a time on the NIC, and if you accept more interrupts, then you can trade performance to ensure per-packet TX power adjustments. I think that it is desirable to be "sloppy" or "lazy" with TX power adjustments, myself: guarantee that each packet is sent at LEAST as "loudly" as its TX power label indicates. When you cannot afford a power adjustment---because, for example, you would have to wait for the TX queue to empty---send some packets more loudly than indicated. Dave On Thu, Oct 10, 2002 at 10:50:09AM +0800, lining73@vip.sina.com wrote: > Hello everbody: > In some papers related to power controlled MAC protocols in MANET, the power levels used are always different by different author. > I want to know are there any real NICs with power control property which can be use in MANET? How many transmit power levels can be used and how much is the difference between maximum & minimum transmit power. > Regards. > ______________________________________ > > =================================================================== > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 10 23:52:15 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00869 for ; Thu, 10 Oct 2002 23:52:15 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9B3hxv22693; Thu, 10 Oct 2002 23:43:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9B3fsv22630 for ; Thu, 10 Oct 2002 23:41:54 -0400 Received: from ccbsd2.csie.nctu.edu.tw (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00621 for ; Thu, 10 Oct 2002 23:39:32 -0400 (EDT) Received: from ccbsd2.csie.nctu.edu.tw (kclin@localhost [127.0.0.1]) by ccbsd2.csie.nctu.edu.tw (8.12.5/8.12.3) with ESMTP id g9B3fXBH067159; Fri, 11 Oct 2002 11:41:33 +0800 (CST) Received: (from kclin@localhost) by ccbsd2.csie.nctu.edu.tw (8.12.5/8.12.3/Submit) id g9B3fXte067158; Fri, 11 Oct 2002 11:41:33 +0800 (CST) Date: Fri, 11 Oct 2002 11:41:33 +0800 From: kclin To: manet@ietf.org Cc: kclin Subject: Re: [manet] help:Power-Saving mode in 802.11 Message-ID: <20021011034133.GA66496@ccbsd2.csie.nctu.edu.tw> References: <20020929182726.3003.qmail@vip.sina.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020929182726.3003.qmail@vip.sina.com> User-Agent: Mutt/1.3.25i Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Mon, Sep 30, 2002 at 02:27:26AM +0800, lining73@vip.sina.com wrote: > everyone: > In an ad hoc network which use 802.11 as the MAC protocol, if all stations work in PS(power-saving) mode, in the ATIM window, when a station A want to send packets to station B,I want to ask the following questions: > 1. does the ATIM message directed send to B or use a RTS-CTS handshake at first between A & B, and then send the ATIM? i think it use a RTS-CTS handshake at first, A STA shall transmit no frame types other than RTS, CTS, and ACK Control frames and Beacon and ATIM management frames during the ATIM Window. BEACON -> RTS-CTS -> ATIM -> ACK -> DATA Frame -> ACK ---------------------------------| ATIM window ------------------------------------------------------| Beacon interval > 2. if station A have tens of packets in its sending queue to different stations, should A send ATIMs to all the destination stations? If this is true, there may be the case(when the load is rather high) that in one beacon interval, A can not send out all its packets because of contention with other stations,and there may be stations which recevie ATIM from "A" and stays in active state, but receive nothing from "A" in the current beacon interval, and energy will be wasted. How to slove this problem? if it uses the traffic-indication virtual bitmap as TIM to indicate many STAs, it may cause many STAs to stay awake but just waste their power to receive nothing. so, i think it indicate just one destination station, and just its destination station is in full awake state to receive the data frame. > 3. if there is only one FIFO sending queue and there is a broadcast message(routing message etc.)at the back end of the queue(several unicast packets are preceded it), as the standard recomand that the broadcast message should send first,is it feasible?Shall I use several sending queues? > 4. How to set the value of beacon interval and the ATIM window, I can't find it in the standard of 99's version? > should it be realted to network loads? > 5. it seems that the PS mode in 802.11 is designed for low load situations and should not be used in high load circumstance, doesn't it? > > Thanks in advance. > Best regards! > > ______________________________________ > > =================================================================== > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 11 00:01:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01040 for ; Fri, 11 Oct 2002 00:01:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9B43X323251 for manet-archive@odin.ietf.org; Fri, 11 Oct 2002 00:03:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9B43Xv23248 for ; Fri, 11 Oct 2002 00:03:33 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01034 for ; Fri, 11 Oct 2002 00:01:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9B3hxv22693; Thu, 10 Oct 2002 23:43:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9B3fsv22630 for ; Thu, 10 Oct 2002 23:41:54 -0400 Received: from ccbsd2.csie.nctu.edu.tw (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00621 for ; Thu, 10 Oct 2002 23:39:32 -0400 (EDT) Received: from ccbsd2.csie.nctu.edu.tw (kclin@localhost [127.0.0.1]) by ccbsd2.csie.nctu.edu.tw (8.12.5/8.12.3) with ESMTP id g9B3fXBH067159; Fri, 11 Oct 2002 11:41:33 +0800 (CST) Received: (from kclin@localhost) by ccbsd2.csie.nctu.edu.tw (8.12.5/8.12.3/Submit) id g9B3fXte067158; Fri, 11 Oct 2002 11:41:33 +0800 (CST) Date: Fri, 11 Oct 2002 11:41:33 +0800 From: kclin To: manet@ietf.org Cc: kclin Subject: Re: [manet] help:Power-Saving mode in 802.11 Message-ID: <20021011034133.GA66496@ccbsd2.csie.nctu.edu.tw> References: <20020929182726.3003.qmail@vip.sina.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020929182726.3003.qmail@vip.sina.com> User-Agent: Mutt/1.3.25i Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Mon, Sep 30, 2002 at 02:27:26AM +0800, lining73@vip.sina.com wrote: > everyone: > In an ad hoc network which use 802.11 as the MAC protocol, if all stations work in PS(power-saving) mode, in the ATIM window, when a station A want to send packets to station B,I want to ask the following questions: > 1. does the ATIM message directed send to B or use a RTS-CTS handshake at first between A & B, and then send the ATIM? i think it use a RTS-CTS handshake at first, A STA shall transmit no frame types other than RTS, CTS, and ACK Control frames and Beacon and ATIM management frames during the ATIM Window. BEACON -> RTS-CTS -> ATIM -> ACK -> DATA Frame -> ACK ---------------------------------| ATIM window ------------------------------------------------------| Beacon interval > 2. if station A have tens of packets in its sending queue to different stations, should A send ATIMs to all the destination stations? If this is true, there may be the case(when the load is rather high) that in one beacon interval, A can not send out all its packets because of contention with other stations,and there may be stations which recevie ATIM from "A" and stays in active state, but receive nothing from "A" in the current beacon interval, and energy will be wasted. How to slove this problem? if it uses the traffic-indication virtual bitmap as TIM to indicate many STAs, it may cause many STAs to stay awake but just waste their power to receive nothing. so, i think it indicate just one destination station, and just its destination station is in full awake state to receive the data frame. > 3. if there is only one FIFO sending queue and there is a broadcast message(routing message etc.)at the back end of the queue(several unicast packets are preceded it), as the standard recomand that the broadcast message should send first,is it feasible?Shall I use several sending queues? > 4. How to set the value of beacon interval and the ATIM window, I can't find it in the standard of 99's version? > should it be realted to network loads? > 5. it seems that the PS mode in 802.11 is designed for low load situations and should not be used in high load circumstance, doesn't it? > > Thanks in advance. > Best regards! > > ______________________________________ > > =================================================================== > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 11 06:40:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15833 for ; Fri, 11 Oct 2002 06:40:44 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9BAgLr17637 for manet-archive@odin.ietf.org; Fri, 11 Oct 2002 06:42:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BAgLv17633 for ; Fri, 11 Oct 2002 06:42:21 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15828 for ; Fri, 11 Oct 2002 06:40:13 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BAeov17582; Fri, 11 Oct 2002 06:40:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BAcrv17509 for ; Fri, 11 Oct 2002 06:38:53 -0400 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15816 for ; Fri, 11 Oct 2002 06:36:39 -0400 (EDT) Received: from cit.ie (unverified [127.0.0.1]) by cit.ie (Rockliffe SMTPRA 5.2.3) with ESMTP id for ; Fri, 11 Oct 2002 11:36:53 +0100 Message-ID: <410-220021051110365381@cit.ie> X-EM-Version: 6, 0, 1, 3 X-EM-Registration: #00E0620610781F002A20 X-Priority: 3 From: "John Paul O'Grady" To: manet@ietf.org Date: Fri, 11 Oct 2002 11:36:53 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Subject: [manet] global connectivity for manets Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello I am looking for research on methods for providing global internet connectivity in manets. I have the internet drafts on Global Connectivity for IPv4 and IPv6 Mobile Ad hoc Networks, I was just wondering if there is any other information out there. I would also be interested if anybody has any info on methods of dynamic allocation of global ipv4 and ipv6 addresses in ad hoc environments without the use of a dhcp server. Most of the research papers I have seen seem to only consider a stand alone manet, and so use private addresses. Regards john paul o grady -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 11 06:40:46 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15851 for ; Fri, 11 Oct 2002 06:40:46 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BAeov17582; Fri, 11 Oct 2002 06:40:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BAcrv17509 for ; Fri, 11 Oct 2002 06:38:53 -0400 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15816 for ; Fri, 11 Oct 2002 06:36:39 -0400 (EDT) Received: from cit.ie (unverified [127.0.0.1]) by cit.ie (Rockliffe SMTPRA 5.2.3) with ESMTP id for ; Fri, 11 Oct 2002 11:36:53 +0100 Message-ID: <410-220021051110365381@cit.ie> X-EM-Version: 6, 0, 1, 3 X-EM-Registration: #00E0620610781F002A20 X-Priority: 3 From: "John Paul O'Grady" To: manet@ietf.org Date: Fri, 11 Oct 2002 11:36:53 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Subject: [manet] global connectivity for manets Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello I am looking for research on methods for providing global internet connectivity in manets. I have the internet drafts on Global Connectivity for IPv4 and IPv6 Mobile Ad hoc Networks, I was just wondering if there is any other information out there. I would also be interested if anybody has any info on methods of dynamic allocation of global ipv4 and ipv6 addresses in ad hoc environments without the use of a dhcp server. Most of the research papers I have seen seem to only consider a stand alone manet, and so use private addresses. Regards john paul o grady -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 11 07:50:10 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17513 for ; Fri, 11 Oct 2002 07:50:10 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BBlgv20655; Fri, 11 Oct 2002 07:47:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BBh8v20518 for ; Fri, 11 Oct 2002 07:43:08 -0400 Received: from webserver.redes.unb.br (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17323 for ; Fri, 11 Oct 2002 07:40:57 -0400 (EDT) Received: from piqui (redesfw.redes.unb.br [164.41.67.254]) by webserver.redes.unb.br (8.12.5/8.12.5) with SMTP id g9BBpgQR013510 for ; Fri, 11 Oct 2002 09:51:42 -0200 Message-ID: <006801c2711b$d2089a30$0e43a8c0@piqui> From: =?iso-8859-1?Q?F=E1bio_Buiati?= To: Date: Fri, 11 Oct 2002 08:46:19 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0065_01C27102.AAE7DAB0" 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 Subject: [manet] Autoconfiguration with Authentication Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0065_01C27102.AAE7DAB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello all..... On these papers about Autoconfiguration the authors have only worried = about assignment of IP addresses for news nodes. However, I would like = to known if there is a model (or paper) joining Autoconfiguration with = Authentication, in order to be possible to avoid intruders on the = networks. Thank you. Best regards.... --------------------------------------------------- F=E1bio Mesquita Buiati Universidade de Bras=EDlia - UnB - Brazil email - fabio@redes.unb.br --------------------------------------------------- ------=_NextPart_000_0065_01C27102.AAE7DAB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello=20 all.....
 
On=20 these papers about Autoconfiguration the authors have only = worried about=20 assignment of IP addresses for news nodes. However, I would like to = known=20 if there is a model (or paper) joining Autoconfiguration with=20 Authentication, in order to be possible to avoid intruders on the=20 networks.
 
Thank you.
 
Best = regards....
---------------------------------------------------
F=E1bio = Mesquita=20 Buiati
Universidade de Bras=EDlia - UnB - Brazil
email - fabio@redes.unb.br
------------= ---------------------------------------
------=_NextPart_000_0065_01C27102.AAE7DAB0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 11 07:58:08 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17909 for ; Fri, 11 Oct 2002 07:58:07 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9BBxjj21151 for manet-archive@odin.ietf.org; Fri, 11 Oct 2002 07:59:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BBxjv21148 for ; Fri, 11 Oct 2002 07:59:45 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17892 for ; Fri, 11 Oct 2002 07:57:37 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BBlgv20655; Fri, 11 Oct 2002 07:47:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BBh8v20518 for ; Fri, 11 Oct 2002 07:43:08 -0400 Received: from webserver.redes.unb.br (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17323 for ; Fri, 11 Oct 2002 07:40:57 -0400 (EDT) Received: from piqui (redesfw.redes.unb.br [164.41.67.254]) by webserver.redes.unb.br (8.12.5/8.12.5) with SMTP id g9BBpgQR013510 for ; Fri, 11 Oct 2002 09:51:42 -0200 Message-ID: <006801c2711b$d2089a30$0e43a8c0@piqui> From: =?iso-8859-1?Q?F=E1bio_Buiati?= To: Date: Fri, 11 Oct 2002 08:46:19 -0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0065_01C27102.AAE7DAB0" 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 Subject: [manet] Autoconfiguration with Authentication Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0065_01C27102.AAE7DAB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello all..... On these papers about Autoconfiguration the authors have only worried = about assignment of IP addresses for news nodes. However, I would like = to known if there is a model (or paper) joining Autoconfiguration with = Authentication, in order to be possible to avoid intruders on the = networks. Thank you. Best regards.... --------------------------------------------------- F=E1bio Mesquita Buiati Universidade de Bras=EDlia - UnB - Brazil email - fabio@redes.unb.br --------------------------------------------------- ------=_NextPart_000_0065_01C27102.AAE7DAB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello=20 all.....
 
On=20 these papers about Autoconfiguration the authors have only = worried about=20 assignment of IP addresses for news nodes. However, I would like to = known=20 if there is a model (or paper) joining Autoconfiguration with=20 Authentication, in order to be possible to avoid intruders on the=20 networks.
 
Thank you.
 
Best = regards....
---------------------------------------------------
F=E1bio = Mesquita=20 Buiati
Universidade de Bras=EDlia - UnB - Brazil
email - fabio@redes.unb.br
------------= ---------------------------------------
------=_NextPart_000_0065_01C27102.AAE7DAB0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 11 10:49:11 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24151 for ; Fri, 11 Oct 2002 10:49:11 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9BEopI30044 for manet-archive@odin.ietf.org; Fri, 11 Oct 2002 10:50:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BEopv30041 for ; Fri, 11 Oct 2002 10:50:51 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24140 for ; Fri, 11 Oct 2002 10:48:40 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BEn2v29922; Fri, 11 Oct 2002 10:49:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BEkNv29818 for ; Fri, 11 Oct 2002 10:46:23 -0400 Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23946 for ; Fri, 11 Oct 2002 10:44:11 -0400 (EDT) Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id HAA25480; Fri, 11 Oct 2002 07:46:18 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g9BEkHe11552; Fri, 11 Oct 2002 07:46:17 -0700 X-mProtect: <200210111446> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdDtZiy5; Fri, 11 Oct 2002 07:46:15 PDT Message-ID: <3DA6E438.C183CFF2@iprg.nokia.com> Date: Fri, 11 Oct 2002 07:46:16 -0700 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "John Paul O'Grady" CC: manet@ietf.org Subject: Re: [manet] global connectivity for manets References: <410-220021051110365381@cit.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello John, John Paul O'Grady wrote: > I would also be interested if anybody has any info on methods of > dynamic allocation of global ipv4 and ipv6 addresses in ad hoc > environments without the use of a dhcp server. Most of the research > papers I have seen seem to only consider a stand alone manet, and so > use private addresses. If a manet node discovers an Internet Gateway, then the gateway "should" provide the node with prefix information so that the node can formulate an address which is topologically correct for the Gateway's attachment to the Internet. That prefix can be used for dynamic address autoconfiguration (e.g., RFC 2462). The dynamic address can even be used as a care-of address for Mobile IP. All of this is documented in Internet Drafts and some other recent publications. Regards, Charlie P. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 11 10:49:13 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24164 for ; Fri, 11 Oct 2002 10:49:13 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BEn2v29922; Fri, 11 Oct 2002 10:49:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BEkNv29818 for ; Fri, 11 Oct 2002 10:46:23 -0400 Received: from mailhost.iprg.nokia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23946 for ; Fri, 11 Oct 2002 10:44:11 -0400 (EDT) Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69]) by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id HAA25480; Fri, 11 Oct 2002 07:46:18 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g9BEkHe11552; Fri, 11 Oct 2002 07:46:17 -0700 X-mProtect: <200210111446> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdDtZiy5; Fri, 11 Oct 2002 07:46:15 PDT Message-ID: <3DA6E438.C183CFF2@iprg.nokia.com> Date: Fri, 11 Oct 2002 07:46:16 -0700 From: "Charles E. Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: "John Paul O'Grady" CC: manet@ietf.org Subject: Re: [manet] global connectivity for manets References: <410-220021051110365381@cit.ie> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hello John, John Paul O'Grady wrote: > I would also be interested if anybody has any info on methods of > dynamic allocation of global ipv4 and ipv6 addresses in ad hoc > environments without the use of a dhcp server. Most of the research > papers I have seen seem to only consider a stand alone manet, and so > use private addresses. If a manet node discovers an Internet Gateway, then the gateway "should" provide the node with prefix information so that the node can formulate an address which is topologically correct for the Gateway's attachment to the Internet. That prefix can be used for dynamic address autoconfiguration (e.g., RFC 2462). The dynamic address can even be used as a care-of address for Mobile IP. All of this is documented in Internet Drafts and some other recent publications. Regards, Charlie P. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 11 15:15:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02763 for ; Fri, 11 Oct 2002 15:15:07 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9BJGnp11370 for manet-archive@odin.ietf.org; Fri, 11 Oct 2002 15:16:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BJGmv11367 for ; Fri, 11 Oct 2002 15:16:48 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02752 for ; Fri, 11 Oct 2002 15:14:36 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BJEEv11254; Fri, 11 Oct 2002 15:14:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BJAnv11150 for ; Fri, 11 Oct 2002 15:10:49 -0400 Received: from stl-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02630 for ; Fri, 11 Oct 2002 15:08:35 -0400 (EDT) Received: from stl-av-02.boeing.com ([192.76.190.7]) by stl-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id OAA29511; Fri, 11 Oct 2002 14:10:39 -0500 (CDT) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by stl-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id OAA25037; Fri, 11 Oct 2002 14:10:38 -0500 (CDT) Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4]) by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g9BJAaF17346; Fri, 11 Oct 2002 12:10:37 -0700 (PDT) Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2650.21) id ; Fri, 11 Oct 2002 15:10:36 -0400 Message-ID: From: "Manfredi, Albert E" To: "'Charles E. Perkins'" Cc: manet@ietf.org Subject: RE: [manet] global connectivity for manets Date: Fri, 11 Oct 2002 15:10:34 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , > -----Original Message----- > From: Charles E. Perkins [mailto:charliep@iprg.nokia.com] > > If a manet node discovers an Internet Gateway, then the > gateway "should" provide the node with prefix information > so that the node can formulate an address which is topologically > correct for the Gateway's attachment to the Internet. That > prefix can be used for dynamic address autoconfiguration (e.g., > RFC 2462). The dynamic address can even be used as a care-of > address for Mobile IP. All of this is documented in Internet > Drafts and some other recent publications. I agree that this scheme for autoconfiguration should work (it uses ICMP router discover protocol vs DHCP, which some might argue amounts to the same thing in the greater scheme of things). But the Mobile IP part I don't understand. The problem with any autoconfiguration scheme is always that no one outside that walled garden knows how to reach you unless you, the autoconfigured host, initiate the session to begin with. Same happens with DHCP. Unless you have some other protocol, like maybe SIP (which is just adding another server requirement on top of router discovery), how would your host be identifiable to the outside world? Thanks. Bert _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 11 15:15:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02780 for ; Fri, 11 Oct 2002 15:15:27 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BJEEv11254; Fri, 11 Oct 2002 15:14:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BJAnv11150 for ; Fri, 11 Oct 2002 15:10:49 -0400 Received: from stl-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02630 for ; Fri, 11 Oct 2002 15:08:35 -0400 (EDT) Received: from stl-av-02.boeing.com ([192.76.190.7]) by stl-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id OAA29511; Fri, 11 Oct 2002 14:10:39 -0500 (CDT) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by stl-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id OAA25037; Fri, 11 Oct 2002 14:10:38 -0500 (CDT) Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4]) by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g9BJAaF17346; Fri, 11 Oct 2002 12:10:37 -0700 (PDT) Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2650.21) id ; Fri, 11 Oct 2002 15:10:36 -0400 Message-ID: From: "Manfredi, Albert E" To: "'Charles E. Perkins'" Cc: manet@ietf.org Subject: RE: [manet] global connectivity for manets Date: Fri, 11 Oct 2002 15:10:34 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , > -----Original Message----- > From: Charles E. Perkins [mailto:charliep@iprg.nokia.com] > > If a manet node discovers an Internet Gateway, then the > gateway "should" provide the node with prefix information > so that the node can formulate an address which is topologically > correct for the Gateway's attachment to the Internet. That > prefix can be used for dynamic address autoconfiguration (e.g., > RFC 2462). The dynamic address can even be used as a care-of > address for Mobile IP. All of this is documented in Internet > Drafts and some other recent publications. I agree that this scheme for autoconfiguration should work (it uses ICMP router discover protocol vs DHCP, which some might argue amounts to the same thing in the greater scheme of things). But the Mobile IP part I don't understand. The problem with any autoconfiguration scheme is always that no one outside that walled garden knows how to reach you unless you, the autoconfigured host, initiate the session to begin with. Same happens with DHCP. Unless you have some other protocol, like maybe SIP (which is just adding another server requirement on top of router discovery), how would your host be identifiable to the outside world? Thanks. Bert _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 11 20:34:39 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07979 for ; Fri, 11 Oct 2002 20:34:39 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9C0aOb25763 for manet-archive@odin.ietf.org; Fri, 11 Oct 2002 20:36:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9C0aNv25760 for ; Fri, 11 Oct 2002 20:36:23 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07974 for ; Fri, 11 Oct 2002 20:34:08 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9C0YYv25707; Fri, 11 Oct 2002 20:34:34 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9C0V0v25574 for ; Fri, 11 Oct 2002 20:31:00 -0400 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07903 for ; Fri, 11 Oct 2002 20:28:45 -0400 (EDT) Received: from colorado.edu (ecee189-227-dhcp.Colorado.EDU [128.138.189.227]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9C0UoY28608; Fri, 11 Oct 2002 18:30:50 -0600 (MDT) Message-ID: <3DA76D34.9040606@colorado.edu> Date: Fri, 11 Oct 2002 18:30:44 -0600 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kartik Rao , manet@ietf.org Subject: Re: [manet] IP routing table and DSR routing table References: <4.2.0.58.20021010151434.0212e9a0@mail.opnet.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Kartik, The DSR implementation suggests that the routing table for DSR should be distinct due to the source route nature of the protocol. We implemented the routing table for DSR in user mode for routing DSR packets. We use ethertap to get these DSR packets from the kernel, did user level routing using the DSR routing table and re-insert the source routed packets on to the tap. Lemme know if you need more details abt our implementation. Regards, Shweta. Kartik Rao wrote: > Is there any interaction between the IP forwarding table and the DSR > routing table (route cache)? _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 11 20:34:41 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07992 for ; Fri, 11 Oct 2002 20:34:41 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9C0YYv25707; Fri, 11 Oct 2002 20:34:34 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9C0V0v25574 for ; Fri, 11 Oct 2002 20:31:00 -0400 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07903 for ; Fri, 11 Oct 2002 20:28:45 -0400 (EDT) Received: from colorado.edu (ecee189-227-dhcp.Colorado.EDU [128.138.189.227]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9C0UoY28608; Fri, 11 Oct 2002 18:30:50 -0600 (MDT) Message-ID: <3DA76D34.9040606@colorado.edu> Date: Fri, 11 Oct 2002 18:30:44 -0600 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kartik Rao , manet@ietf.org Subject: Re: [manet] IP routing table and DSR routing table References: <4.2.0.58.20021010151434.0212e9a0@mail.opnet.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Kartik, The DSR implementation suggests that the routing table for DSR should be distinct due to the source route nature of the protocol. We implemented the routing table for DSR in user mode for routing DSR packets. We use ethertap to get these DSR packets from the kernel, did user level routing using the DSR routing table and re-insert the source routed packets on to the tap. Lemme know if you need more details abt our implementation. Regards, Shweta. Kartik Rao wrote: > Is there any interaction between the IP forwarding table and the DSR > routing table (route cache)? _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sat Oct 12 02:23:43 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21548 for ; Sat, 12 Oct 2002 02:23:43 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9C6Nqv14774; Sat, 12 Oct 2002 02:23:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9C6L8v14726 for ; Sat, 12 Oct 2002 02:21:08 -0400 Received: from peoplemail.com.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA21510 for ; Sat, 12 Oct 2002 02:18:44 -0400 (EDT) Received: from adhoc([166.111.65.30]) by peoplemail.com.cn(JetMail 2.5.3.0) with SMTP id jmf3da80572; Sat, 12 Oct 2002 06:20:07 -0000 Message-ID: <004c01c271b7$cf344ba0$1e416fa6@adhoc> From: "liucrenmin" To: Date: Sat, 12 Oct 2002 14:22:55 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0049_01C271FA.DB4637D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Subject: [manet] the 802.11 PCF simulation in ns Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0049_01C271FA.DB4637D0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGVsbG8gLCBldmVyeWJvZHksDQogICAgQXMgZmFyIGFzIEkga25vdyB0aGUgbnMtYWxsaW5vbmUt Mi4xYjggb25seSBpbXBsZW1lbnRlZCB0aGUgRENGIG9mIDgwMi4xMS4gRG9lcyBhbnlvbmUga25v dyB3aGVyZSBJIGNhbiBnZXQgdGhlIFBDRiBpbXBsZW1lbnRhdGlvbj8gSWYgdGhlcmUgYXJlIG5v IHN1Y2ggdGhpbmdzICwgd2h5Py4NCg0KUmVnYXJkcywNCmxpdWNoLA0K ------=_NextPart_000_0049_01C271FA.DB4637D0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w MC4zMzE1LjI4NzAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8 Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5IZWxsbyAsIGV2ZXJ5Ym9k eSw8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4mbmJzcDsmbmJzcDsmbmJzcDsgQXMg ZmFyIGFzIEkga25vdyB0aGUgbnMtYWxsaW5vbmUtMi4xYjggb25seSANCmltcGxlbWVudGVkIHRo ZSBEQ0Ygb2YgODAyLjExLiBEb2VzIGFueW9uZSBrbm93IHdoZXJlIEkgY2FuIGdldCB0aGUgUENG IA0KaW1wbGVtZW50YXRpb24/IElmIHRoZXJlIGFyZSBubyBzdWNoIHRoaW5ncyAsIHdoeT8uPC9G T05UPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPlJlZ2FyZHMs PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+bGl1Y2gsPC9GT05UPjwvRElWPjwvQk9E WT48L0hUTUw+DQo= ------=_NextPart_000_0049_01C271FA.DB4637D0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Oct 12 02:30:03 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21653 for ; Sat, 12 Oct 2002 02:30:03 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9C6Vo015232 for manet-archive@odin.ietf.org; Sat, 12 Oct 2002 02:31:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9C6Vnv15229 for ; Sat, 12 Oct 2002 02:31:49 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21636 for ; Sat, 12 Oct 2002 02:29:32 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9C6Nqv14774; Sat, 12 Oct 2002 02:23:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9C6L8v14726 for ; Sat, 12 Oct 2002 02:21:08 -0400 Received: from peoplemail.com.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA21510 for ; Sat, 12 Oct 2002 02:18:44 -0400 (EDT) Received: from adhoc([166.111.65.30]) by peoplemail.com.cn(JetMail 2.5.3.0) with SMTP id jmf3da80572; Sat, 12 Oct 2002 06:20:07 -0000 Message-ID: <004c01c271b7$cf344ba0$1e416fa6@adhoc> From: "liucrenmin" To: Date: Sat, 12 Oct 2002 14:22:55 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0049_01C271FA.DB4637D0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Subject: [manet] the 802.11 PCF simulation in ns Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0049_01C271FA.DB4637D0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGVsbG8gLCBldmVyeWJvZHksDQogICAgQXMgZmFyIGFzIEkga25vdyB0aGUgbnMtYWxsaW5vbmUt Mi4xYjggb25seSBpbXBsZW1lbnRlZCB0aGUgRENGIG9mIDgwMi4xMS4gRG9lcyBhbnlvbmUga25v dyB3aGVyZSBJIGNhbiBnZXQgdGhlIFBDRiBpbXBsZW1lbnRhdGlvbj8gSWYgdGhlcmUgYXJlIG5v IHN1Y2ggdGhpbmdzICwgd2h5Py4NCg0KUmVnYXJkcywNCmxpdWNoLA0K ------=_NextPart_000_0049_01C271FA.DB4637D0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWdi MjMxMiIgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNS4w MC4zMzE1LjI4NzAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8 Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5IZWxsbyAsIGV2ZXJ5Ym9k eSw8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj4mbmJzcDsmbmJzcDsmbmJzcDsgQXMg ZmFyIGFzIEkga25vdyB0aGUgbnMtYWxsaW5vbmUtMi4xYjggb25seSANCmltcGxlbWVudGVkIHRo ZSBEQ0Ygb2YgODAyLjExLiBEb2VzIGFueW9uZSBrbm93IHdoZXJlIEkgY2FuIGdldCB0aGUgUENG IA0KaW1wbGVtZW50YXRpb24/IElmIHRoZXJlIGFyZSBubyBzdWNoIHRoaW5ncyAsIHdoeT8uPC9G T05UPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPlJlZ2FyZHMs PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+bGl1Y2gsPC9GT05UPjwvRElWPjwvQk9E WT48L0hUTUw+DQo= ------=_NextPart_000_0049_01C271FA.DB4637D0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Oct 12 07:35:11 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24499 for ; Sat, 12 Oct 2002 07:35:10 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9CBam926710 for manet-archive@odin.ietf.org; Sat, 12 Oct 2002 07:36:48 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CBamv26707 for ; Sat, 12 Oct 2002 07:36:48 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24492 for ; Sat, 12 Oct 2002 07:34:39 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CBZav26687; Sat, 12 Oct 2002 07:35:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CBXDv26656 for ; Sat, 12 Oct 2002 07:33:13 -0400 Received: from sm.luth.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24465 for ; Sat, 12 Oct 2002 07:31:04 -0400 (EDT) Received: from dugdale.cdt.luth.se (dugdale.cdt.luth.se [130.240.64.172]) by sm.luth.se (8.12.3/8.12.3) with ESMTP id g9CBX6dU016928; Sat, 12 Oct 2002 13:33:07 +0200 (MET DST) Date: Sat, 12 Oct 2002 13:37:59 +0200 (CEST) From: Anders Lindgren X-X-Sender: dugdale@dugdale.cdt.luth.se To: liucrenmin cc: manet@ietf.org, Subject: Re: [manet] the 802.11 PCF simulation in ns In-Reply-To: <004c01c271b7$cf344ba0$1e416fa6@adhoc> Message-ID: <20021012133312.X19670-100000@dugdale.cdt.luth.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.11 (www dot roaringpenguin dot com slash mimedefang) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , We have made a PCF implementation for ns, available at http://www.sm.luth.se/~dugdale/index/software.shtml /Anders (I don't think the MANET list really is the appropriate forum for this question... Use the ns-users list for questions like this in the future.) On Sat, 12 Oct 2002, liucrenmin wrote: > Hello , everybody, > As far as I know the ns-allinone-2.1b8 only implemented the DCF of > 802.11. Does anyone know where I can get the PCF implementation? If > there are no such things , why?. > > Regards, > liuch, > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sat Oct 12 07:35:13 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24512 for ; Sat, 12 Oct 2002 07:35:13 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CBZav26687; Sat, 12 Oct 2002 07:35:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CBXDv26656 for ; Sat, 12 Oct 2002 07:33:13 -0400 Received: from sm.luth.se (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24465 for ; Sat, 12 Oct 2002 07:31:04 -0400 (EDT) Received: from dugdale.cdt.luth.se (dugdale.cdt.luth.se [130.240.64.172]) by sm.luth.se (8.12.3/8.12.3) with ESMTP id g9CBX6dU016928; Sat, 12 Oct 2002 13:33:07 +0200 (MET DST) Date: Sat, 12 Oct 2002 13:37:59 +0200 (CEST) From: Anders Lindgren X-X-Sender: dugdale@dugdale.cdt.luth.se To: liucrenmin cc: manet@ietf.org, Subject: Re: [manet] the 802.11 PCF simulation in ns In-Reply-To: <004c01c271b7$cf344ba0$1e416fa6@adhoc> Message-ID: <20021012133312.X19670-100000@dugdale.cdt.luth.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.11 (www dot roaringpenguin dot com slash mimedefang) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , We have made a PCF implementation for ns, available at http://www.sm.luth.se/~dugdale/index/software.shtml /Anders (I don't think the MANET list really is the appropriate forum for this question... Use the ns-users list for questions like this in the future.) On Sat, 12 Oct 2002, liucrenmin wrote: > Hello , everybody, > As far as I know the ns-allinone-2.1b8 only implemented the DCF of > 802.11. Does anyone know where I can get the PCF implementation? If > there are no such things , why?. > > Regards, > liuch, > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sat Oct 12 15:14:19 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29334 for ; Sat, 12 Oct 2002 15:14:19 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CJD6v11600; Sat, 12 Oct 2002 15:13:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CJ8Wv11545 for ; Sat, 12 Oct 2002 15:08:32 -0400 Received: from SMTP1.ECE.NEU.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29268 for ; Sat, 12 Oct 2002 15:06:20 -0400 (EDT) Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (NUECE 1.1.4) with SMTP id g9CJ8R9L016874 for ; Sat, 12 Oct 2002 15:08:27 -0400 (EDT) Received: from bibbiena.ece.neu.edu ([129.10.60.216]) by calvin.ece.neu.edu (NAVGW 2.5.2.9) with SMTP id M2002101215082709919 for ; Sat, 12 Oct 2002 15:08:27 -0400 Received: from localhost (basagni@localhost) by bibbiena.ece.neu.edu (8.11.6+Sun/8.9.3) with ESMTP id g9CJ8Rr23863 for ; Sat, 12 Oct 2002 15:08:27 -0400 (EDT) X-Authentication-Warning: bibbiena.ece.neu.edu: basagni owned process doing -bs Date: Sat, 12 Oct 2002 15:08:27 -0400 (EDT) From: Stefano Basagni X-X-Sender: basagni@bibbiena To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id g9CJ8Xv11546 Subject: [manet] IEEE PERCOM 2003 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit --------------------------------------------------------------- Dear Colleagues, Please, find the enclosed CfP. Our apologies for duplicates. (NOTE that the submission deadline, October 31st 2002, is a firm deadline.) Regards. --------------------------------------------------------------- P E R C O M 2 0 0 3 Dallas-Fort Worth Metroplex, Texas March 23-26, 2003 Conference Announcement and Call for Papers --------------------------------------------------------------- IEEE International Conference on Pervasive Computing and Communications (PerCom), **** Extended Paper Submission Deadline---October 31, 2002 **** (There will be no extensions after this date.) Sponsored by the IEEE Computer Society --------------------------------------------------------------- Pervasive computing and communications is emerging as an exciting new paradigm with a goal to provide computing and communication services all the time everywhere. This is a natural outcome of research and technological advances in wireless networks, mobile computing, distributed computing and agent technologies. PerCom is the annual IEEE conference on pervasive computing and communications. PerCom2003 will provide a high profile, leading edge forum for researchers and engineers alike to present their latest advances in the field of pervasive computing and communications. PerCom2003 will also feature two special tracks on intelligent environments and mobile agents. Feature Topics: ---------------- Contributions are solicited in all pervasive computing research and applied areas. These include, but are not limited to, the following feature topics: · Pervasive computing architectures · Intelligent environments · Wearable computers · Smart devices and smart spaces · Location-dependent / personalized applications · Service discovery mechanisms · Agent technologies · Sensors and actuators · Positioning and tracking technologies · Identification and authentication technologies · Integration of wired and wireless networks · Personal area networks · Enabling technologies such as Bluetooth, 802.11 and 802.15 · Software coordination models · Mobile / wireless computing systems and services · Context based and implicit computing · Speech processing / advanced computer vision · User interfaces and interaction models · Wireless/mobile service management and delivery · Ad hoc networking protocols and service discovery · Resource management in pervasive computing platforms · Security and privacy issues for pervasive computing systems Submission Guidelines: Papers must be unpublished and must not be submitted for publication elsewhere. Authors are encouraged to submit papers in electronic form, postscript or PDF only. The page limit for submissions is 15 pages (1.5 line spaced, excluding references, figures and tables). More details on submission procedures will be posted on the official PerCom website: http://www.percom.org. All submitted papers will undergo a rigorous review process managed by the technical program committee. Conference proceedings will be published by IEEE. Papers of particular merit will be considered for publication in a special issue of a leading journal. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Important Dates / Deadlines: Paper Submission: October 31, 2002 Tutorial Submission: October 31, 2002 Demonstration proposals: December 1, 2002 Acceptance Notification: December 10, 2002 Camera Ready Manuscript: January 10, 2003 Conference Dates: March 23-26, 2003 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Organizing Committee: General Chair Behrooz A. Shirazi University of Texas at Arlington General Vice Chair: Sajal K. Das University of Texas at Arlington Technical Program Committee Chair Mohan Kumar University of Texas at Arlington Local Chair: Gergely V. Záruba University of Texas at Arlington Finance Chair: David Levine University of Texas at Arlington Intelligent Environments Track Chair: Diane Cook University of Texas at Arlington Mobile Agents Track Chair: Anand Tripathi University of Minnesota Tutorials Chair: Azzedine Boukerche University of North Texas Industry Liaison: Kalyan Basu University of Texas at Arlington Demonstrations Chair: Farhad Kamangar University of Texas at Arlington Publicity Chairs: Stefano Basagni Northeastern University Chiara Petrioli University of Rome Albert Zomaya University of Sydney Technical Program Committee: --------------------------- Giuseppe Anastasi, University of Pisa, Italy Jean Bacon, University of Cambridge, UK Chatschik Bisdikian, IBM, USA Lisa Burnell, Texas Christian University, USA Roy Campbell, University of Illinois at Urbana-Champaign, USA Liang Cheng, Lehigh University, USA Lucy Cherkasova, Hewlett Packard Labs Marco Conti, National Research Council, Italy Diane Cook, University of Texas at Arlington, USA Antonio Corradi, University of Bologna, Italy Skevos Evripidou, University of Cyprus, Cyprus Jason Flinn, Carnegie Mellon University, USA Robert Gray, Dartmouth College, USA Liviu Iftode, Rutgers University, USA Archan Misra, IBM Center, USA Yannis Labrou, Fujitsu, USA Mohan Kumar, University of Texas at Arlington, USA Phil McKinley, Michigan State University, USA Paddy Nixon, The University of Strathclyde, UK Gian Pietro Picco, Politecnico di Milano, Italy Cauligi S. Raghavendra, University of Southern California, USA Ichiro Satoh, National Institute of Informatics, Japan Steven Shafer, Microsoft Corporation, USA H.J. Siegel, Colorado State University, USA Mukesh Singhal, University of Kentucky, USA Anand Tripathi, University of Minnesota, USA Mohan Trivedi, University of California, San Diego, USA Taieb Znati, University of Pittsburgh, USA --------------------------------------------------------------- -- Stefano Basagni, Ph.D. Assistant Professor of Computer Engineering Dept. of Electrical and Computer Engineering 312 Dana Research Center Northeastern University 360 Huntigton Ave. Boston, MA 02115 Tel. 617 373 3061, Fax 617 373 8970 E-mail: basagni@ece.neu.edu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Oct 12 15:17:23 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29382 for ; Sat, 12 Oct 2002 15:17:23 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9CJJ5U11747 for manet-archive@odin.ietf.org; Sat, 12 Oct 2002 15:19:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CJJ5v11744 for ; Sat, 12 Oct 2002 15:19:05 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29379 for ; Sat, 12 Oct 2002 15:16:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CJD6v11600; Sat, 12 Oct 2002 15:13:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CJ8Wv11545 for ; Sat, 12 Oct 2002 15:08:32 -0400 Received: from SMTP1.ECE.NEU.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29268 for ; Sat, 12 Oct 2002 15:06:20 -0400 (EDT) Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (NUECE 1.1.4) with SMTP id g9CJ8R9L016874 for ; Sat, 12 Oct 2002 15:08:27 -0400 (EDT) Received: from bibbiena.ece.neu.edu ([129.10.60.216]) by calvin.ece.neu.edu (NAVGW 2.5.2.9) with SMTP id M2002101215082709919 for ; Sat, 12 Oct 2002 15:08:27 -0400 Received: from localhost (basagni@localhost) by bibbiena.ece.neu.edu (8.11.6+Sun/8.9.3) with ESMTP id g9CJ8Rr23863 for ; Sat, 12 Oct 2002 15:08:27 -0400 (EDT) X-Authentication-Warning: bibbiena.ece.neu.edu: basagni owned process doing -bs Date: Sat, 12 Oct 2002 15:08:27 -0400 (EDT) From: Stefano Basagni X-X-Sender: basagni@bibbiena To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by www1.ietf.org id g9CJ8Xv11546 Subject: [manet] IEEE PERCOM 2003 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit --------------------------------------------------------------- Dear Colleagues, Please, find the enclosed CfP. Our apologies for duplicates. (NOTE that the submission deadline, October 31st 2002, is a firm deadline.) Regards. --------------------------------------------------------------- P E R C O M 2 0 0 3 Dallas-Fort Worth Metroplex, Texas March 23-26, 2003 Conference Announcement and Call for Papers --------------------------------------------------------------- IEEE International Conference on Pervasive Computing and Communications (PerCom), **** Extended Paper Submission Deadline---October 31, 2002 **** (There will be no extensions after this date.) Sponsored by the IEEE Computer Society --------------------------------------------------------------- Pervasive computing and communications is emerging as an exciting new paradigm with a goal to provide computing and communication services all the time everywhere. This is a natural outcome of research and technological advances in wireless networks, mobile computing, distributed computing and agent technologies. PerCom is the annual IEEE conference on pervasive computing and communications. PerCom2003 will provide a high profile, leading edge forum for researchers and engineers alike to present their latest advances in the field of pervasive computing and communications. PerCom2003 will also feature two special tracks on intelligent environments and mobile agents. Feature Topics: ---------------- Contributions are solicited in all pervasive computing research and applied areas. These include, but are not limited to, the following feature topics: · Pervasive computing architectures · Intelligent environments · Wearable computers · Smart devices and smart spaces · Location-dependent / personalized applications · Service discovery mechanisms · Agent technologies · Sensors and actuators · Positioning and tracking technologies · Identification and authentication technologies · Integration of wired and wireless networks · Personal area networks · Enabling technologies such as Bluetooth, 802.11 and 802.15 · Software coordination models · Mobile / wireless computing systems and services · Context based and implicit computing · Speech processing / advanced computer vision · User interfaces and interaction models · Wireless/mobile service management and delivery · Ad hoc networking protocols and service discovery · Resource management in pervasive computing platforms · Security and privacy issues for pervasive computing systems Submission Guidelines: Papers must be unpublished and must not be submitted for publication elsewhere. Authors are encouraged to submit papers in electronic form, postscript or PDF only. The page limit for submissions is 15 pages (1.5 line spaced, excluding references, figures and tables). More details on submission procedures will be posted on the official PerCom website: http://www.percom.org. All submitted papers will undergo a rigorous review process managed by the technical program committee. Conference proceedings will be published by IEEE. Papers of particular merit will be considered for publication in a special issue of a leading journal. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Important Dates / Deadlines: Paper Submission: October 31, 2002 Tutorial Submission: October 31, 2002 Demonstration proposals: December 1, 2002 Acceptance Notification: December 10, 2002 Camera Ready Manuscript: January 10, 2003 Conference Dates: March 23-26, 2003 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Organizing Committee: General Chair Behrooz A. Shirazi University of Texas at Arlington General Vice Chair: Sajal K. Das University of Texas at Arlington Technical Program Committee Chair Mohan Kumar University of Texas at Arlington Local Chair: Gergely V. Záruba University of Texas at Arlington Finance Chair: David Levine University of Texas at Arlington Intelligent Environments Track Chair: Diane Cook University of Texas at Arlington Mobile Agents Track Chair: Anand Tripathi University of Minnesota Tutorials Chair: Azzedine Boukerche University of North Texas Industry Liaison: Kalyan Basu University of Texas at Arlington Demonstrations Chair: Farhad Kamangar University of Texas at Arlington Publicity Chairs: Stefano Basagni Northeastern University Chiara Petrioli University of Rome Albert Zomaya University of Sydney Technical Program Committee: --------------------------- Giuseppe Anastasi, University of Pisa, Italy Jean Bacon, University of Cambridge, UK Chatschik Bisdikian, IBM, USA Lisa Burnell, Texas Christian University, USA Roy Campbell, University of Illinois at Urbana-Champaign, USA Liang Cheng, Lehigh University, USA Lucy Cherkasova, Hewlett Packard Labs Marco Conti, National Research Council, Italy Diane Cook, University of Texas at Arlington, USA Antonio Corradi, University of Bologna, Italy Skevos Evripidou, University of Cyprus, Cyprus Jason Flinn, Carnegie Mellon University, USA Robert Gray, Dartmouth College, USA Liviu Iftode, Rutgers University, USA Archan Misra, IBM Center, USA Yannis Labrou, Fujitsu, USA Mohan Kumar, University of Texas at Arlington, USA Phil McKinley, Michigan State University, USA Paddy Nixon, The University of Strathclyde, UK Gian Pietro Picco, Politecnico di Milano, Italy Cauligi S. Raghavendra, University of Southern California, USA Ichiro Satoh, National Institute of Informatics, Japan Steven Shafer, Microsoft Corporation, USA H.J. Siegel, Colorado State University, USA Mukesh Singhal, University of Kentucky, USA Anand Tripathi, University of Minnesota, USA Mohan Trivedi, University of California, San Diego, USA Taieb Znati, University of Pittsburgh, USA --------------------------------------------------------------- -- Stefano Basagni, Ph.D. Assistant Professor of Computer Engineering Dept. of Electrical and Computer Engineering 312 Dana Research Center Northeastern University 360 Huntigton Ave. Boston, MA 02115 Tel. 617 373 3061, Fax 617 373 8970 E-mail: basagni@ece.neu.edu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Oct 13 23:44:08 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29321 for ; Sun, 13 Oct 2002 23:44:08 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9E3juU28135 for manet-archive@odin.ietf.org; Sun, 13 Oct 2002 23:45:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E3juv28132 for ; Sun, 13 Oct 2002 23:45:56 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29305 for ; Sun, 13 Oct 2002 23:43:37 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E3fEv28045; Sun, 13 Oct 2002 23:41:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E3XNv27374 for ; Sun, 13 Oct 2002 23:33:23 -0400 Received: from stephens.ittc.ku.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29228 for ; Sun, 13 Oct 2002 23:31:05 -0400 (EDT) Received: from ittc.ku.edu (fiasco.ittc.ku.edu [129.237.125.27]) by stephens.ittc.ku.edu (8.12.6/8.12.6/ITTC-ANTISPAM-ANTIVIRUS-3.0) with SMTP id g9E3X4OU009307 for ; Sun, 13 Oct 2002 22:33:04 -0500 From: Pradeepkumar Mani Received: from 179.61.cm.sunflower.com ([24.124.61.179]) (SquirrelMail authenticated user mpradeep) by secure.ittc.ukans.edu with HTTP; Sun, 13 Oct 2002 22:33:04 -0500 (CDT) Message-ID: <33307.24.124.61.179.1034566384.squirrel@secure.ittc.ukans.edu> Date: Sun, 13 Oct 2002 22:33:04 -0500 (CDT) To: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-VirusScan: Clean Content-Transfer-Encoding: 8bit Subject: [manet] DSR implementation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi Does anybody know of any linux-based implementation for DSR (other than the one fond in monarch website)? any info on this will be greatly appreciated. Thanks Pradeep _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sun Oct 13 23:44:24 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29334 for ; Sun, 13 Oct 2002 23:44:24 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E3fEv28045; Sun, 13 Oct 2002 23:41:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E3XNv27374 for ; Sun, 13 Oct 2002 23:33:23 -0400 Received: from stephens.ittc.ku.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29228 for ; Sun, 13 Oct 2002 23:31:05 -0400 (EDT) Received: from ittc.ku.edu (fiasco.ittc.ku.edu [129.237.125.27]) by stephens.ittc.ku.edu (8.12.6/8.12.6/ITTC-ANTISPAM-ANTIVIRUS-3.0) with SMTP id g9E3X4OU009307 for ; Sun, 13 Oct 2002 22:33:04 -0500 From: Pradeepkumar Mani Received: from 179.61.cm.sunflower.com ([24.124.61.179]) (SquirrelMail authenticated user mpradeep) by secure.ittc.ukans.edu with HTTP; Sun, 13 Oct 2002 22:33:04 -0500 (CDT) Message-ID: <33307.24.124.61.179.1034566384.squirrel@secure.ittc.ukans.edu> Date: Sun, 13 Oct 2002 22:33:04 -0500 (CDT) To: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-VirusScan: Clean Content-Transfer-Encoding: 8bit Subject: [manet] DSR implementation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi Does anybody know of any linux-based implementation for DSR (other than the one fond in monarch website)? any info on this will be greatly appreciated. Thanks Pradeep _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 14 00:09:58 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29854 for ; Mon, 14 Oct 2002 00:09:58 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E49Gv29433; Mon, 14 Oct 2002 00:09:16 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E46Rv28798 for ; Mon, 14 Oct 2002 00:06:27 -0400 Received: from gwserver.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29764 for ; Mon, 14 Oct 2002 00:04:03 -0400 (EDT) Received: from swl1002 ([172.16.3.193]) by gwserver.icr.a-star.edu.sg; Mon, 14 Oct 2002 12:00:49 +0800 Message-ID: <007c01c27336$48110b60$c10310ac@icr.astar.edu.sg> Reply-To: "Ankur Jain" From: "Ankur Jain" To: Cc: "Ankur Jain" , Date: Mon, 14 Oct 2002 12:00:40 +0800 Organization: Institute for Communications Research, Singapore MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0077_01C27379.51189DC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Subject: [manet] About IP Address Autoconf Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0077_01C27379.51189DC0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello I have some questions about the IP Address Autoconf IETF Draft. 1. Is it possible for some intermediate node "X" to send a particular = message like "ADDR_FOUND" in response to an AREQ message, which is = requesting an IP Address that is already used by some node in the = network. This message will be sent by the node X if it is having some = communication with that IP Address. This will be helpful in very quick = Duplicate Address Detection. It will also save time which is otherwise = wasted in sending the request for the same packet AREQ_RETRIES time. 2. What happens when the temporary IP Address chosen by a node is = already taken by some other node which is also doing DAD. Is there a = some special method to obtain that IP Address? I know the probability is = less. But, still it can happen and what are the actions taken at that = time?=20 =20 Any comments ??? Regards Ankur ~...~...~...~...~...~...~...~...~...~...~...~...~...~...~... ANKUR JAIN Institute for Communications Research (ICR) (formerly Centre for Wireless Communications) 20 Science Park Road, #02-34/37, TeleTech Park, Singapore Science Park II, SINGAPORE 117674=20 Website: http://www.icr.a-star.edu.sg Phone # 68709266 Email # stujaina@icr.a-star.edu.sg ankurjain@ieee.org ankurjain@softhome.net ~...~...~...~...~...~...~...~...~...~...~...~...~...~...~... ------=_NextPart_000_0077_01C27379.51189DC0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hello
 
I have some questions about the IP = Address Autoconf=20 IETF Draft.
 
1. Is it possible for some intermediate = node "X" to=20 send a particular message like "ADDR_FOUND" in response to an AREQ = message,=20 which is requesting an IP Address that is already used by some node in = the=20 network. This message will be sent by the node X if it is having some=20 communication with that IP Address. = This will be=20 helpful in very quick Duplicate Address Detection. It will also save = time which=20 is otherwise wasted in sending the request for the same packet = AREQ_RETRIES=20 time.
 
2. What happens when the temporary IP = Address=20 chosen by a node is already taken by some other node which is also = doing=20 DAD. Is there a some special method to obtain that IP Address? I know = the=20 probability is less. But, still it can happen and what are the actions = taken at=20 that time?
 
 
Any comments ???
 
Regards
Ankur
 
 
 
 
~...~...~...~...~...~...~...~...~...~...~...~...~...~...~...
= ANKUR=20 JAIN
 
Institute for Communications Research=20 (ICR)
(formerly Centre for Wireless Communications)
20 Science = Park Road,=20 #02-34/37,
TeleTech Park, Singapore Science Park II,
SINGAPORE = 117674=20
 
Website: http://www.icr.a-star.edu.sg
 
Phone #    = 68709266
Email =20 #     stujaina@icr.a-star.edu.sg=
           &nb= sp;    =20 ankurjain@ieee.org
  =             &= nbsp; =20 ankurjain@softhome.net
~...= ~...~...~...~...~...~...~...~...~...~...~...~...~...~...
= ------=_NextPart_000_0077_01C27379.51189DC0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 14 00:12:58 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29914 for ; Mon, 14 Oct 2002 00:12:58 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9E4Ekh29595 for manet-archive@odin.ietf.org; Mon, 14 Oct 2002 00:14:46 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E4Ekv29592 for ; Mon, 14 Oct 2002 00:14:46 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29902 for ; Mon, 14 Oct 2002 00:12:27 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E49Gv29433; Mon, 14 Oct 2002 00:09:16 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E46Rv28798 for ; Mon, 14 Oct 2002 00:06:27 -0400 Received: from gwserver.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29764 for ; Mon, 14 Oct 2002 00:04:03 -0400 (EDT) Received: from swl1002 ([172.16.3.193]) by gwserver.icr.a-star.edu.sg; Mon, 14 Oct 2002 12:00:49 +0800 Message-ID: <007c01c27336$48110b60$c10310ac@icr.astar.edu.sg> Reply-To: "Ankur Jain" From: "Ankur Jain" To: Cc: "Ankur Jain" , Date: Mon, 14 Oct 2002 12:00:40 +0800 Organization: Institute for Communications Research, Singapore MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0077_01C27379.51189DC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Subject: [manet] About IP Address Autoconf Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0077_01C27379.51189DC0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello I have some questions about the IP Address Autoconf IETF Draft. 1. Is it possible for some intermediate node "X" to send a particular = message like "ADDR_FOUND" in response to an AREQ message, which is = requesting an IP Address that is already used by some node in the = network. This message will be sent by the node X if it is having some = communication with that IP Address. This will be helpful in very quick = Duplicate Address Detection. It will also save time which is otherwise = wasted in sending the request for the same packet AREQ_RETRIES time. 2. What happens when the temporary IP Address chosen by a node is = already taken by some other node which is also doing DAD. Is there a = some special method to obtain that IP Address? I know the probability is = less. But, still it can happen and what are the actions taken at that = time?=20 =20 Any comments ??? Regards Ankur ~...~...~...~...~...~...~...~...~...~...~...~...~...~...~... ANKUR JAIN Institute for Communications Research (ICR) (formerly Centre for Wireless Communications) 20 Science Park Road, #02-34/37, TeleTech Park, Singapore Science Park II, SINGAPORE 117674=20 Website: http://www.icr.a-star.edu.sg Phone # 68709266 Email # stujaina@icr.a-star.edu.sg ankurjain@ieee.org ankurjain@softhome.net ~...~...~...~...~...~...~...~...~...~...~...~...~...~...~... ------=_NextPart_000_0077_01C27379.51189DC0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hello
 
I have some questions about the IP = Address Autoconf=20 IETF Draft.
 
1. Is it possible for some intermediate = node "X" to=20 send a particular message like "ADDR_FOUND" in response to an AREQ = message,=20 which is requesting an IP Address that is already used by some node in = the=20 network. This message will be sent by the node X if it is having some=20 communication with that IP Address. = This will be=20 helpful in very quick Duplicate Address Detection. It will also save = time which=20 is otherwise wasted in sending the request for the same packet = AREQ_RETRIES=20 time.
 
2. What happens when the temporary IP = Address=20 chosen by a node is already taken by some other node which is also = doing=20 DAD. Is there a some special method to obtain that IP Address? I know = the=20 probability is less. But, still it can happen and what are the actions = taken at=20 that time?
 
 
Any comments ???
 
Regards
Ankur
 
 
 
 
~...~...~...~...~...~...~...~...~...~...~...~...~...~...~...
= ANKUR=20 JAIN
 
Institute for Communications Research=20 (ICR)
(formerly Centre for Wireless Communications)
20 Science = Park Road,=20 #02-34/37,
TeleTech Park, Singapore Science Park II,
SINGAPORE = 117674=20
 
Website: http://www.icr.a-star.edu.sg
 
Phone #    = 68709266
Email =20 #     stujaina@icr.a-star.edu.sg=
           &nb= sp;    =20 ankurjain@ieee.org
  =             &= nbsp; =20 ankurjain@softhome.net
~...= ~...~...~...~...~...~...~...~...~...~...~...~...~...~...
= ------=_NextPart_000_0077_01C27379.51189DC0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 14 01:28:16 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00725 for ; Mon, 14 Oct 2002 01:28:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E5Rqv32036; Mon, 14 Oct 2002 01:27:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E5O6v31959 for ; Mon, 14 Oct 2002 01:24:06 -0400 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00641 for ; Mon, 14 Oct 2002 01:21:45 -0400 (EDT) Received: from colorado.edu (ecee189-227-dhcp.Colorado.EDU [128.138.189.227]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9E5NoB26015; Sun, 13 Oct 2002 23:23:50 -0600 (MDT) Message-ID: <3DAA54DD.2000502@colorado.edu> Date: Sun, 13 Oct 2002 23:23:41 -0600 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pradeepkumar Mani CC: manet@ietf.org Subject: Re: [manet] DSR implementation References: <33307.24.124.61.179.1034566384.squirrel@secure.ittc.ukans.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit We at University of Colorado at Boulder have a full fledged userlevel implementation of DSR. Infact, we have the energy aware version of DSR which we denote as EADSR. Do let me know if you are interested in the same. Regards, Shweta _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 14 01:32:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00872 for ; Mon, 14 Oct 2002 01:32:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9E5Yao32249 for manet-archive@odin.ietf.org; Mon, 14 Oct 2002 01:34:36 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E5Yav32246 for ; Mon, 14 Oct 2002 01:34:36 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00854 for ; Mon, 14 Oct 2002 01:32:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E5Rqv32036; Mon, 14 Oct 2002 01:27:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9E5O6v31959 for ; Mon, 14 Oct 2002 01:24:06 -0400 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00641 for ; Mon, 14 Oct 2002 01:21:45 -0400 (EDT) Received: from colorado.edu (ecee189-227-dhcp.Colorado.EDU [128.138.189.227]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9E5NoB26015; Sun, 13 Oct 2002 23:23:50 -0600 (MDT) Message-ID: <3DAA54DD.2000502@colorado.edu> Date: Sun, 13 Oct 2002 23:23:41 -0600 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pradeepkumar Mani CC: manet@ietf.org Subject: Re: [manet] DSR implementation References: <33307.24.124.61.179.1034566384.squirrel@secure.ittc.ukans.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit We at University of Colorado at Boulder have a full fledged userlevel implementation of DSR. Infact, we have the energy aware version of DSR which we denote as EADSR. Do let me know if you are interested in the same. Regards, Shweta _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 15 05:32:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24625 for ; Tue, 15 Oct 2002 05:32:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9F9YQA02821 for manet-archive@odin.ietf.org; Tue, 15 Oct 2002 05:34:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F9YQv02818 for ; Tue, 15 Oct 2002 05:34:26 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24615 for ; Tue, 15 Oct 2002 05:32:17 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F9Vuv02737; Tue, 15 Oct 2002 05:31:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F9PZv02577 for ; Tue, 15 Oct 2002 05:25:35 -0400 Received: from thoth.sbs.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24483 for ; Tue, 15 Oct 2002 05:23:25 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g9F9PUo26997; Tue, 15 Oct 2002 11:25:30 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9F9PUQ05573; Tue, 15 Oct 2002 11:25:30 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9F9PTIu005499; Tue, 15 Oct 2002 11:25:29 +0200 (MET DST) Message-ID: <3DABE0CE.BB5E0E58@mchp.siemens.de> Date: Tue, 15 Oct 2002 11:33:02 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Aodvimpl-Public , "manet@ietf.org" , "ns-users@isi.edu" Content-Type: multipart/alternative; boundary="------------A801350D754A430A73739743" Subject: [manet] Local Repair Timer Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------A801350D754A430A73739743 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, i did some simulations with the local repair feature and i realized that the function "LocalRepairTimer::handle(Event* P)" is not called at all. Normally we have to get there after the timeout in a local repair attempt. But it doesn't seem to be the case!! Does anyone have any idea?? Thanks Riadh --------------A801350D754A430A73739743 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit 
Hi,
i did some simulations with the local repair feature and i realized that the function "LocalRepairTimer::handle(Event* P)"
is not called at all. Normally we have to get there after the timeout in a local repair attempt. But it doesn't seem to be the case!!
Does anyone have any idea??
Thanks
Riadh
  --------------A801350D754A430A73739743-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 15 05:33:00 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24645 for ; Tue, 15 Oct 2002 05:33:00 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F9Vuv02737; Tue, 15 Oct 2002 05:31:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F9PZv02577 for ; Tue, 15 Oct 2002 05:25:35 -0400 Received: from thoth.sbs.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24483 for ; Tue, 15 Oct 2002 05:23:25 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g9F9PUo26997; Tue, 15 Oct 2002 11:25:30 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9F9PUQ05573; Tue, 15 Oct 2002 11:25:30 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9F9PTIu005499; Tue, 15 Oct 2002 11:25:29 +0200 (MET DST) Message-ID: <3DABE0CE.BB5E0E58@mchp.siemens.de> Date: Tue, 15 Oct 2002 11:33:02 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Aodvimpl-Public , "manet@ietf.org" , "ns-users@isi.edu" Content-Type: multipart/alternative; boundary="------------A801350D754A430A73739743" Subject: [manet] Local Repair Timer Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------A801350D754A430A73739743 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, i did some simulations with the local repair feature and i realized that the function "LocalRepairTimer::handle(Event* P)" is not called at all. Normally we have to get there after the timeout in a local repair attempt. But it doesn't seem to be the case!! Does anyone have any idea?? Thanks Riadh --------------A801350D754A430A73739743 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit 
Hi,
i did some simulations with the local repair feature and i realized that the function "LocalRepairTimer::handle(Event* P)"
is not called at all. Normally we have to get there after the timeout in a local repair attempt. But it doesn't seem to be the case!!
Does anyone have any idea??
Thanks
Riadh
  --------------A801350D754A430A73739743-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 15 11:24:17 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04780 for ; Tue, 15 Oct 2002 11:24:17 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9FFPxZ21771 for manet-archive@odin.ietf.org; Tue, 15 Oct 2002 11:25:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FFPxv21768 for ; Tue, 15 Oct 2002 11:25:59 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04775 for ; Tue, 15 Oct 2002 11:23:46 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FFNmv21682; Tue, 15 Oct 2002 11:23:48 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FFLEv21601 for ; Tue, 15 Oct 2002 11:21:14 -0400 Received: from postfix.informatik.uni-bonn.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04680 for ; Tue, 15 Oct 2002 11:19:01 -0400 (EDT) Received: from cs.uni-bonn.de (bratislava.informatik.uni-bonn.de [131.220.6.147]) by postfix.informatik.uni-bonn.de (Postfix) with ESMTP id 96CEE70C8F; Tue, 15 Oct 2002 17:21:10 +0200 (MEST) (envelope-from deWaal@cs.uni-bonn.de) (envelope-to manet@ietf.org) (2) (internal use: ta=1, tu=1, te=0, am=-, au=NULL) Message-ID: <3DAC3266.1090303@cs.uni-bonn.de> Date: Tue, 15 Oct 2002 17:21:10 +0200 From: Christian de Waal Organization: University of Bonn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org, ns-users@isi.edu Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Announcement: Java mobility scenario generator & analyser "BonnMotion" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear Mobile Ad Hoc Networkers, we would like to announce that "BonnMotion", the mobility scenario generator and analysis tool we are developing at the University of Bonn, is now available under the terms of the GPL at http://www.cs.uni-bonn.de/IV/BonnMotion/ The software is able to create scenarios according to several mobility models and to analyse characteristics as e.g. connectedness or node degrees. The scenarios can also be converted to a format such that they can be used for simulations with ns-2. Any feedback is welcome. Regards, Christian de Waal -- _____________________________________________________________________ Christian de Waal University of Bonn Tel.: +49-228-73-4548 Institute of Computer Science IV Fax: +49-228-73-4571 Roemerstr. 164 E-mail: dewaal@cs.uni-bonn.de D-53117 Bonn, Germany http: www.cs.uni-bonn.de/IV/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 15 11:24:21 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04797 for ; Tue, 15 Oct 2002 11:24:21 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FFNmv21682; Tue, 15 Oct 2002 11:23:48 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FFLEv21601 for ; Tue, 15 Oct 2002 11:21:14 -0400 Received: from postfix.informatik.uni-bonn.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04680 for ; Tue, 15 Oct 2002 11:19:01 -0400 (EDT) Received: from cs.uni-bonn.de (bratislava.informatik.uni-bonn.de [131.220.6.147]) by postfix.informatik.uni-bonn.de (Postfix) with ESMTP id 96CEE70C8F; Tue, 15 Oct 2002 17:21:10 +0200 (MEST) (envelope-from deWaal@cs.uni-bonn.de) (envelope-to manet@ietf.org) (2) (internal use: ta=1, tu=1, te=0, am=-, au=NULL) Message-ID: <3DAC3266.1090303@cs.uni-bonn.de> Date: Tue, 15 Oct 2002 17:21:10 +0200 From: Christian de Waal Organization: University of Bonn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org, ns-users@isi.edu Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Announcement: Java mobility scenario generator & analyser "BonnMotion" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear Mobile Ad Hoc Networkers, we would like to announce that "BonnMotion", the mobility scenario generator and analysis tool we are developing at the University of Bonn, is now available under the terms of the GPL at http://www.cs.uni-bonn.de/IV/BonnMotion/ The software is able to create scenarios according to several mobility models and to analyse characteristics as e.g. connectedness or node degrees. The scenarios can also be converted to a format such that they can be used for simulations with ns-2. Any feedback is welcome. Regards, Christian de Waal -- _____________________________________________________________________ Christian de Waal University of Bonn Tel.: +49-228-73-4548 Institute of Computer Science IV Fax: +49-228-73-4571 Roemerstr. 164 E-mail: dewaal@cs.uni-bonn.de D-53117 Bonn, Germany http: www.cs.uni-bonn.de/IV/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 16 10:19:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00208 for ; Wed, 16 Oct 2002 10:19:57 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9GELfF04618 for manet-archive@odin.ietf.org; Wed, 16 Oct 2002 10:21:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GELev04615 for ; Wed, 16 Oct 2002 10:21:40 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00173 for ; Wed, 16 Oct 2002 10:19:26 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GEIdv04432; Wed, 16 Oct 2002 10:18:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GDGKv01540 for ; Wed, 16 Oct 2002 09:16:20 -0400 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28119 for ; Wed, 16 Oct 2002 09:12:01 -0400 (EDT) Received: from cit.ie (mail.cit.ie [127.0.0.1]) by cit.ie (Rockliffe SMTPRA 5.2.3) with ESMTP id for ; Wed, 16 Oct 2002 14:10:53 +0100 Message-ID: <410-2200210316131053243@cit.ie> X-EM-Version: 6, 0, 1, 3 X-EM-Registration: #00E0620610781F002A20 X-Priority: 3 From: "John Paul O'Grady" To: manet@ietf.org Date: Wed, 16 Oct 2002 14:10:53 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Subject: [manet] ipv4 address and network address translation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello I have a question in regard to ipv4 addresses in autoconfiguration in manets. I know globally unique ipv6 addresses can be created dynamically using for example a nodes mac addresses. This wont be possible for ipv4 addresses (32 bit addresses)and so if a globally unique ipv4 addresses cant be created will private addresses have to be used in the manet? Then if the node wants to access the internet, will network address translation (NAT) have to be used to translate the private address into a public address? john paul o grady -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 16 10:20:23 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00236 for ; Wed, 16 Oct 2002 10:20:23 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GEIdv04432; Wed, 16 Oct 2002 10:18:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GDGKv01540 for ; Wed, 16 Oct 2002 09:16:20 -0400 Received: from mail.cit.ie (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28119 for ; Wed, 16 Oct 2002 09:12:01 -0400 (EDT) Received: from cit.ie (mail.cit.ie [127.0.0.1]) by cit.ie (Rockliffe SMTPRA 5.2.3) with ESMTP id for ; Wed, 16 Oct 2002 14:10:53 +0100 Message-ID: <410-2200210316131053243@cit.ie> X-EM-Version: 6, 0, 1, 3 X-EM-Registration: #00E0620610781F002A20 X-Priority: 3 From: "John Paul O'Grady" To: manet@ietf.org Date: Wed, 16 Oct 2002 14:10:53 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Subject: [manet] ipv4 address and network address translation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello I have a question in regard to ipv4 addresses in autoconfiguration in manets. I know globally unique ipv6 addresses can be created dynamically using for example a nodes mac addresses. This wont be possible for ipv4 addresses (32 bit addresses)and so if a globally unique ipv4 addresses cant be created will private addresses have to be used in the manet? Then if the node wants to access the internet, will network address translation (NAT) have to be used to translate the private address into a public address? john paul o grady -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 16 11:06:26 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02437 for ; Wed, 16 Oct 2002 11:06:26 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9GF89v08757 for manet-archive@odin.ietf.org; Wed, 16 Oct 2002 11:08:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GF89v08754 for ; Wed, 16 Oct 2002 11:08:09 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02420 for ; Wed, 16 Oct 2002 11:05:54 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GF6Xv08097; Wed, 16 Oct 2002 11:06:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GEx8v07755 for ; Wed, 16 Oct 2002 10:59:08 -0400 Received: from meshpdc.meshnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02105 for ; Wed, 16 Oct 2002 10:56:53 -0400 (EDT) Received: from neumillersimul (neumiller-simul.meshnetworks.com [172.16.1.171]) by meshpdc.meshnetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 410BY36Z; Wed, 16 Oct 2002 10:58:58 -0400 Message-ID: <000701c27524$8e623b30$ab0110ac@meshnetworks.com> Reply-To: "Phil Neumiller" From: "Phil Neumiller" To: , Subject: RE: [manet] ipv4 address and network address translation Date: Wed, 16 Oct 2002 10:58:58 -0400 Organization: MeshNetworks, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi John Paul, I have probably stated this more than a few times on this list, but what the heck. A mobile IPv4 static home addresses is a logical and convenient choice for routing in MANETS (I think :-). A). MIPv4 addresses are unique by definition B). If you use DHCP in your MANET (that happens to have gateways to fixed infrastructure) to acquire a topologically correct address (maybe behind a NAT too), you can still be globally reached using MIPv4. C). When you lose connectivity to the mobility agents you don't have to lose your manet routes because your were already routing peer-to-peer with MIP home addresses D). The downside seems to be all those extra unicast routes and the lack of any aggregation possibility if you are using all those home addresses from different networks. Some issues crop up here (besides security of course). It is my understanding that RFC 1256 is not widely implemented in the global Internet (i.e. Cisco routers) and MIPv4 also puts a dependency on this RFC for its own ICMP based agent advertisements. Lets suppose you have a mobility agent upstream in your backhaul somewhere advertising into your attached ad hoc network. Should the TTL field be used to limit the flood of these ICMP broadcasts over the MANET? It seems you need to get MIPv4 to update your MANET route table with the default route being to the mobility agent whenever one is discovered or a new registration occurs. One can think of optimizations that allow a reduction in flooding like proxy responses to agent solicitations etc. Thanks, Phil -----Original Message----- From: John Paul O'Grady [mailto:jpogrady@cit.ie] Sent: Wednesday, October 16, 2002 9:11 AM To: manet@ietf.org Subject: [manet] ipv4 address and network address translation Hello I have a question in regard to ipv4 addresses in autoconfiguration in manets. I know globally unique ipv6 addresses can be created dynamically using for example a nodes mac addresses. This wont be possible for ipv4 addresses (32 bit addresses)and so if a globally unique ipv4 addresses cant be created will private addresses have to be used in the manet? Then if the node wants to access the internet, will network address translation (NAT) have to be used to translate the private address into a public address? john paul o grady -- Phillip D. Neumiller (pneumiller@meshnetworks.com) My PGP key can be imported from the following URL: http://pgpkeys.mit.edu BTW: It is undecidable whether an arithmetical formula is true! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 16 11:06:37 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02456 for ; Wed, 16 Oct 2002 11:06:37 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GF6Xv08097; Wed, 16 Oct 2002 11:06:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GEx8v07755 for ; Wed, 16 Oct 2002 10:59:08 -0400 Received: from meshpdc.meshnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02105 for ; Wed, 16 Oct 2002 10:56:53 -0400 (EDT) Received: from neumillersimul (neumiller-simul.meshnetworks.com [172.16.1.171]) by meshpdc.meshnetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 410BY36Z; Wed, 16 Oct 2002 10:58:58 -0400 Message-ID: <000701c27524$8e623b30$ab0110ac@meshnetworks.com> Reply-To: "Phil Neumiller" From: "Phil Neumiller" To: , Subject: RE: [manet] ipv4 address and network address translation Date: Wed, 16 Oct 2002 10:58:58 -0400 Organization: MeshNetworks, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi John Paul, I have probably stated this more than a few times on this list, but what the heck. A mobile IPv4 static home addresses is a logical and convenient choice for routing in MANETS (I think :-). A). MIPv4 addresses are unique by definition B). If you use DHCP in your MANET (that happens to have gateways to fixed infrastructure) to acquire a topologically correct address (maybe behind a NAT too), you can still be globally reached using MIPv4. C). When you lose connectivity to the mobility agents you don't have to lose your manet routes because your were already routing peer-to-peer with MIP home addresses D). The downside seems to be all those extra unicast routes and the lack of any aggregation possibility if you are using all those home addresses from different networks. Some issues crop up here (besides security of course). It is my understanding that RFC 1256 is not widely implemented in the global Internet (i.e. Cisco routers) and MIPv4 also puts a dependency on this RFC for its own ICMP based agent advertisements. Lets suppose you have a mobility agent upstream in your backhaul somewhere advertising into your attached ad hoc network. Should the TTL field be used to limit the flood of these ICMP broadcasts over the MANET? It seems you need to get MIPv4 to update your MANET route table with the default route being to the mobility agent whenever one is discovered or a new registration occurs. One can think of optimizations that allow a reduction in flooding like proxy responses to agent solicitations etc. Thanks, Phil -----Original Message----- From: John Paul O'Grady [mailto:jpogrady@cit.ie] Sent: Wednesday, October 16, 2002 9:11 AM To: manet@ietf.org Subject: [manet] ipv4 address and network address translation Hello I have a question in regard to ipv4 addresses in autoconfiguration in manets. I know globally unique ipv6 addresses can be created dynamically using for example a nodes mac addresses. This wont be possible for ipv4 addresses (32 bit addresses)and so if a globally unique ipv4 addresses cant be created will private addresses have to be used in the manet? Then if the node wants to access the internet, will network address translation (NAT) have to be used to translate the private address into a public address? john paul o grady -- Phillip D. Neumiller (pneumiller@meshnetworks.com) My PGP key can be imported from the following URL: http://pgpkeys.mit.edu BTW: It is undecidable whether an arithmetical formula is true! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 18 14:51:28 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06808 for ; Fri, 18 Oct 2002 14:51:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9IIrEH02453 for manet-archive@odin.ietf.org; Fri, 18 Oct 2002 14:53:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9IIrEv02450 for ; Fri, 18 Oct 2002 14:53:14 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06793 for ; Fri, 18 Oct 2002 14:50:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9IIowv02336; Fri, 18 Oct 2002 14:50:58 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9IIhfv02104 for ; Fri, 18 Oct 2002 14:43:41 -0400 Received: from smtpproxy2.mitre.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06454 for ; Fri, 18 Oct 2002 14:41:24 -0400 (EDT) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id g9IIhaV09835; Fri, 18 Oct 2002 14:43:36 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id g9IIhYt18019; Fri, 18 Oct 2002 14:43:34 -0400 (EDT) Received: from kb.mitre.org (129.83.65.31) by mailhub2.mitre.org with SMTP id 12000385; Fri, 18 Oct 2002 14:43:21 -0400 Message-ID: <3DB0564B.DD0CD773@mitre.org> Date: Fri, 18 Oct 2002 14:43:25 -0400 From: Kenneth Brayer Reply-To: kb@mitre.org Organization: The MITRE Corporation X-Mailer: Mozilla 4.76C-20010313M (Macintosh; U; PPC) X-Accept-Language: en MIME-Version: 1.0 To: manet , ns-users Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Call for Papers for IEEE J-SAC Issue on Variable Topology QoS Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit To all Members of the MANET and NS-USERS Groups The following is a call for papers for the IEEE Journal on Selected Areas on Communications for Extended Abstracts for papers on Quality of Service Delivery in Variable Topology Networks. Please feel free to further distribute this call. Call for Papers Quality of Service Delivery in Variable Topology Networks IEEE Journal on Selected Areas in Communications Topics of keen interest today in networking technology include methods of delivering services over variable topology networks, such as variable point-to-point and Ad Hoc networks, in which the user is mobile and inter-router connections are time varying. We seek here to gather a body of work that reports the state of the art and practice in assessment of the quality of service (QoS) that can be delivered over such networks. We specifically seek contributions that will be of value to system architects in selecting collections of technologies and methodologies that meet their needs and establish standards for user responsive system performance. We are especially seeking contributions that report QoS delivery in clearly defined network settings under clearly defined metrics for a specific service or collection of services. Such contributions might focus specifically on comparing alternative technological or methodological approaches to delivering services with quality guarantee, such as bi-directional versus unidirectional connectivity, source-based versus dynamic routing, proactive versus reactive organization, transmission control at the transport layer versus the MAC layer, retransmission versus forward error correction and the relation of these to timeliness and priority. Variable topology peer-to-peer and Ad Hoc constructions in both flat and hierarchical environments are of interest. Alternatively, a contribution might focus on the performance that can be achieved using a single technological and methodological approach, but varying key factors of interest, such as the number of end systems, end-system density, or the delivery physical environment. Throughout, the central theme should be service delivery, and the metrics used should enable potential users to clearly see patterns of performance in one or more of the following dimensions: cost, complexity, timely delivery, traffic handling capacity, or the number of end systems the system can handle. Methods for achieving quality of service under conditions of varying topology, and new concepts for providing quality of service are likewise of interest. In this context, the topics for this issue include: Variable Point-to-Point and Ad Hoc Routing o New methodologies o Bi-directional vs. unidirectional connectivity o Source based vs. dynamic routing o Unicast vs. multicast, content-based routing Variable Topology Network Architectures and Reconfiguration Techniques o Flat vs. hierarchical organizations o Proactive vs. reactive reconfiguration o MAC vs. upper layer implementations o Self-configurations o Distributed algorithms (group and resource management) Quality of Service (QoS) Delivery o Methodologies for timely message delivery o Providing predictable performance o Error coding for achieving Quality of Service o Methods of measuring QoS in operational networks Performance Analysis o Comparative study (analysis, simulation, emulation and/or implementation) o New analytical approaches o Definition of performance metrics o Optimizing the system performance (capacity, response time, throughput, etc.) Testbed and Applications o Testbed descriptions and objectives o Experimental results based on testbeds o Unique applications of testbeds Standards o Definition of common and desirable features of standards o Matching current and emerging standards to applications o Applications requirements versus features provided by standards Original, unpublished contributions and invited articles will be considered for the issue. The call for papers is for extended abstracts that propose development of papers to meet the goals of the issue. The proposal shall comprehensively describe the area of the paper relative to the areas of interest of the call. These extended abstracts will be reviewed and the editors will invite final papers, which will be refereed. Extended abstracts not to exceed 5 pages in .pdf format should be submitted by April 1, 2003. To submit your extended abstract 1) go to http://edas.cs.columbia.edu, 2) establish an account, 3) receive an e-mail from edas with your password, 4) login to the edas system, 5) select the J-SAC issue, 6) click on view, 7) click on submit paper and follow the instructions. Upon invitation papers should be submitted in .pdf format. Papers should follow the IEEE J-SAC manuscript format described in the Information for Authors of the Journal which can be found at http://www.argreenhouse.com/society/J-SAC/Guidelines/info.html or in any issue, and be no longer than 25 double-spaced pages, excluding illustrations and graphs. The name of the submitted file should be aaaaJsacVtn.pdf , where aaaa is the first four letters of the authors surname. If an author submits more than one paper then aaaa shall be replaced by aaaan where n is a sequential paper number (e.g. 1, 2, ...). All submissions must be electronically generated. Scanned documents are not acceptable. All papers will be peer reviewed and revisions of acceptable papers may be required prior to publication. The following timetable will apply: Extended Abstract Submission Deadline: April 1, 2003 Acceptance Notification of Proposed Paper: June 1, 2003 Submission of Invited Papers: October 1, 2003 Acceptance Notification: February 1, 2004 Final Revised Manuscript Due: March 1, 2004 Publication of issue: 3rd-4th Quarter 2004 Guest Editors: Nicola Blefari-Melazzi, University of Perugia, Italy , blefari@diei.unipg.it Kenneth Brayer, The MITRE Corporation, USA, k.brayer@ieee.org John N. Daigle, The University of Mississippi, USA, wcdaigle@cotton.vislab.olemiss.edu Jean-Yves Le Boudec, Ecole Polytechnique Federale de Lausanne, Switzerland, jean-yves.leboudec@epfl.ch Bo Li, Hong Kong University of Science and Technology, China, BLI@cs.ust.hk -- Kenneth Brayer M/S B312 The MITRE Corporation 202 Burlington Road Bedford, MA 01730 e-mail: kb@mitre.org tele: 781-271-5254 fax: 781-271-2841 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 18 14:51:41 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06824 for ; Fri, 18 Oct 2002 14:51:41 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9IIowv02336; Fri, 18 Oct 2002 14:50:58 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9IIhfv02104 for ; Fri, 18 Oct 2002 14:43:41 -0400 Received: from smtpproxy2.mitre.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06454 for ; Fri, 18 Oct 2002 14:41:24 -0400 (EDT) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id g9IIhaV09835; Fri, 18 Oct 2002 14:43:36 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id g9IIhYt18019; Fri, 18 Oct 2002 14:43:34 -0400 (EDT) Received: from kb.mitre.org (129.83.65.31) by mailhub2.mitre.org with SMTP id 12000385; Fri, 18 Oct 2002 14:43:21 -0400 Message-ID: <3DB0564B.DD0CD773@mitre.org> Date: Fri, 18 Oct 2002 14:43:25 -0400 From: Kenneth Brayer Reply-To: kb@mitre.org Organization: The MITRE Corporation X-Mailer: Mozilla 4.76C-20010313M (Macintosh; U; PPC) X-Accept-Language: en MIME-Version: 1.0 To: manet , ns-users Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Call for Papers for IEEE J-SAC Issue on Variable Topology QoS Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit To all Members of the MANET and NS-USERS Groups The following is a call for papers for the IEEE Journal on Selected Areas on Communications for Extended Abstracts for papers on Quality of Service Delivery in Variable Topology Networks. Please feel free to further distribute this call. Call for Papers Quality of Service Delivery in Variable Topology Networks IEEE Journal on Selected Areas in Communications Topics of keen interest today in networking technology include methods of delivering services over variable topology networks, such as variable point-to-point and Ad Hoc networks, in which the user is mobile and inter-router connections are time varying. We seek here to gather a body of work that reports the state of the art and practice in assessment of the quality of service (QoS) that can be delivered over such networks. We specifically seek contributions that will be of value to system architects in selecting collections of technologies and methodologies that meet their needs and establish standards for user responsive system performance. We are especially seeking contributions that report QoS delivery in clearly defined network settings under clearly defined metrics for a specific service or collection of services. Such contributions might focus specifically on comparing alternative technological or methodological approaches to delivering services with quality guarantee, such as bi-directional versus unidirectional connectivity, source-based versus dynamic routing, proactive versus reactive organization, transmission control at the transport layer versus the MAC layer, retransmission versus forward error correction and the relation of these to timeliness and priority. Variable topology peer-to-peer and Ad Hoc constructions in both flat and hierarchical environments are of interest. Alternatively, a contribution might focus on the performance that can be achieved using a single technological and methodological approach, but varying key factors of interest, such as the number of end systems, end-system density, or the delivery physical environment. Throughout, the central theme should be service delivery, and the metrics used should enable potential users to clearly see patterns of performance in one or more of the following dimensions: cost, complexity, timely delivery, traffic handling capacity, or the number of end systems the system can handle. Methods for achieving quality of service under conditions of varying topology, and new concepts for providing quality of service are likewise of interest. In this context, the topics for this issue include: Variable Point-to-Point and Ad Hoc Routing o New methodologies o Bi-directional vs. unidirectional connectivity o Source based vs. dynamic routing o Unicast vs. multicast, content-based routing Variable Topology Network Architectures and Reconfiguration Techniques o Flat vs. hierarchical organizations o Proactive vs. reactive reconfiguration o MAC vs. upper layer implementations o Self-configurations o Distributed algorithms (group and resource management) Quality of Service (QoS) Delivery o Methodologies for timely message delivery o Providing predictable performance o Error coding for achieving Quality of Service o Methods of measuring QoS in operational networks Performance Analysis o Comparative study (analysis, simulation, emulation and/or implementation) o New analytical approaches o Definition of performance metrics o Optimizing the system performance (capacity, response time, throughput, etc.) Testbed and Applications o Testbed descriptions and objectives o Experimental results based on testbeds o Unique applications of testbeds Standards o Definition of common and desirable features of standards o Matching current and emerging standards to applications o Applications requirements versus features provided by standards Original, unpublished contributions and invited articles will be considered for the issue. The call for papers is for extended abstracts that propose development of papers to meet the goals of the issue. The proposal shall comprehensively describe the area of the paper relative to the areas of interest of the call. These extended abstracts will be reviewed and the editors will invite final papers, which will be refereed. Extended abstracts not to exceed 5 pages in .pdf format should be submitted by April 1, 2003. To submit your extended abstract 1) go to http://edas.cs.columbia.edu, 2) establish an account, 3) receive an e-mail from edas with your password, 4) login to the edas system, 5) select the J-SAC issue, 6) click on view, 7) click on submit paper and follow the instructions. Upon invitation papers should be submitted in .pdf format. Papers should follow the IEEE J-SAC manuscript format described in the Information for Authors of the Journal which can be found at http://www.argreenhouse.com/society/J-SAC/Guidelines/info.html or in any issue, and be no longer than 25 double-spaced pages, excluding illustrations and graphs. The name of the submitted file should be aaaaJsacVtn.pdf , where aaaa is the first four letters of the authors surname. If an author submits more than one paper then aaaa shall be replaced by aaaan where n is a sequential paper number (e.g. 1, 2, ...). All submissions must be electronically generated. Scanned documents are not acceptable. All papers will be peer reviewed and revisions of acceptable papers may be required prior to publication. The following timetable will apply: Extended Abstract Submission Deadline: April 1, 2003 Acceptance Notification of Proposed Paper: June 1, 2003 Submission of Invited Papers: October 1, 2003 Acceptance Notification: February 1, 2004 Final Revised Manuscript Due: March 1, 2004 Publication of issue: 3rd-4th Quarter 2004 Guest Editors: Nicola Blefari-Melazzi, University of Perugia, Italy , blefari@diei.unipg.it Kenneth Brayer, The MITRE Corporation, USA, k.brayer@ieee.org John N. Daigle, The University of Mississippi, USA, wcdaigle@cotton.vislab.olemiss.edu Jean-Yves Le Boudec, Ecole Polytechnique Federale de Lausanne, Switzerland, jean-yves.leboudec@epfl.ch Bo Li, Hong Kong University of Science and Technology, China, BLI@cs.ust.hk -- Kenneth Brayer M/S B312 The MITRE Corporation 202 Burlington Road Bedford, MA 01730 e-mail: kb@mitre.org tele: 781-271-5254 fax: 781-271-2841 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sat Oct 19 19:42:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09062 for ; Sat, 19 Oct 2002 19:42:06 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9JNebv16932; Sat, 19 Oct 2002 19:40:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9JNZSv16292 for ; Sat, 19 Oct 2002 19:35:28 -0400 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08940 for ; Sat, 19 Oct 2002 19:33:06 -0400 (EDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 19 Oct 2002 16:35:19 -0700 Received: from 129.119.251.157 by lw15fd.law15.hotmail.msn.com with HTTP; Sat, 19 Oct 2002 23:35:18 GMT X-Originating-IP: [129.119.251.157] From: "A A" To: pneumiller@meshnetworks.com, manet@ietf.org Subject: RE: [manet] ipv4 address and network address translation Date: Sat, 19 Oct 2002 23:35:18 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 19 Oct 2002 23:35:19.0510 (UTC) FILETIME=[2F92A760:01C277C8] Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Phil, Is there any RFC/Document stating how mobile IPv4 static home addresses are assigned. My understanding is that for assigning topological correct address to nodes in adhoc network you have to go through a DHCP server. Which might be one or more hops away. There might be several issues involved in the process. The prominent one i see is routing using MAC address till the node gets an IP address i.e. a node is trying to get to DHCP server. This offcourse raise concerns about security. Is there any other method to get IPv4 address for a mobile node. Thanks, Abdul >From: "Phil Neumiller" >Reply-To: "Phil Neumiller" >To: , >Subject: RE: [manet] ipv4 address and network address translation >Date: Wed, 16 Oct 2002 10:58:58 -0400 > >Hi John Paul, > >I have probably stated this more than a few times on this list, but >what the heck. A mobile IPv4 static home addresses is a logical >and convenient choice for routing in MANETS (I think :-). > >A). MIPv4 addresses are unique by definition > >B). If you use DHCP in your MANET (that happens to have gateways > to fixed infrastructure) to acquire a topologically correct address > (maybe behind a NAT too), you can still be globally reached using > MIPv4. > >C). When you lose connectivity to the mobility agents you > don't have to lose your manet routes because your were > already routing peer-to-peer with MIP home addresses > >D). The downside seems to be all those extra unicast routes and > the lack of any aggregation possibility if you are using all > those home addresses from different networks. > >Some issues crop up here (besides security of course). It is my >understanding that RFC 1256 is not widely implemented in the global >Internet (i.e. Cisco routers) and MIPv4 also puts a dependency on this >RFC for its own ICMP based agent advertisements. Lets suppose you >have a mobility agent upstream in your backhaul somewhere advertising >into your attached ad hoc network. Should the TTL field be used to limit >the flood of these ICMP broadcasts over the MANET? > >It seems you need to get MIPv4 to update your MANET route table >with the default route being to the mobility agent whenever one is >discovered or a new registration occurs. > >One can think of optimizations that allow a reduction in flooding >like proxy responses to agent solicitations etc. > >Thanks, > >Phil >-----Original Message----- >From: John Paul O'Grady [mailto:jpogrady@cit.ie] >Sent: Wednesday, October 16, 2002 9:11 AM >To: manet@ietf.org >Subject: [manet] ipv4 address and network address translation > >Hello >I have a question in regard to ipv4 addresses in autoconfiguration in >manets. I know globally unique ipv6 addresses can be created >dynamically using for example a nodes mac addresses. >This wont be possible for ipv4 addresses (32 bit addresses)and so if >a globally unique ipv4 addresses cant be created will private >addresses have to be used in the manet? >Then if the node wants to access the internet, will network address >translation (NAT) have to be used to translate the private address >into a public address? >john paul o grady > >-- >Phillip D. Neumiller (pneumiller@meshnetworks.com) >My PGP key can be imported from the following URL: http://pgpkeys.mit.edu >BTW: It is undecidable whether an arithmetical formula is true! >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _________________________________________________________________ Unlimited Internet access for only $21.95/month.  Try MSN! http://resourcecenter.msn.com/access/plans/2monthsfree.asp _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Oct 19 19:48:48 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09143 for ; Sat, 19 Oct 2002 19:48:48 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9JNoed17173 for manet-archive@odin.ietf.org; Sat, 19 Oct 2002 19:50:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9JNodv17170 for ; Sat, 19 Oct 2002 19:50:39 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09140 for ; Sat, 19 Oct 2002 19:48:17 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9JNebv16932; Sat, 19 Oct 2002 19:40:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9JNZSv16292 for ; Sat, 19 Oct 2002 19:35:28 -0400 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08940 for ; Sat, 19 Oct 2002 19:33:06 -0400 (EDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 19 Oct 2002 16:35:19 -0700 Received: from 129.119.251.157 by lw15fd.law15.hotmail.msn.com with HTTP; Sat, 19 Oct 2002 23:35:18 GMT X-Originating-IP: [129.119.251.157] From: "A A" To: pneumiller@meshnetworks.com, manet@ietf.org Subject: RE: [manet] ipv4 address and network address translation Date: Sat, 19 Oct 2002 23:35:18 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 19 Oct 2002 23:35:19.0510 (UTC) FILETIME=[2F92A760:01C277C8] Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Phil, Is there any RFC/Document stating how mobile IPv4 static home addresses are assigned. My understanding is that for assigning topological correct address to nodes in adhoc network you have to go through a DHCP server. Which might be one or more hops away. There might be several issues involved in the process. The prominent one i see is routing using MAC address till the node gets an IP address i.e. a node is trying to get to DHCP server. This offcourse raise concerns about security. Is there any other method to get IPv4 address for a mobile node. Thanks, Abdul >From: "Phil Neumiller" >Reply-To: "Phil Neumiller" >To: , >Subject: RE: [manet] ipv4 address and network address translation >Date: Wed, 16 Oct 2002 10:58:58 -0400 > >Hi John Paul, > >I have probably stated this more than a few times on this list, but >what the heck. A mobile IPv4 static home addresses is a logical >and convenient choice for routing in MANETS (I think :-). > >A). MIPv4 addresses are unique by definition > >B). If you use DHCP in your MANET (that happens to have gateways > to fixed infrastructure) to acquire a topologically correct address > (maybe behind a NAT too), you can still be globally reached using > MIPv4. > >C). When you lose connectivity to the mobility agents you > don't have to lose your manet routes because your were > already routing peer-to-peer with MIP home addresses > >D). The downside seems to be all those extra unicast routes and > the lack of any aggregation possibility if you are using all > those home addresses from different networks. > >Some issues crop up here (besides security of course). It is my >understanding that RFC 1256 is not widely implemented in the global >Internet (i.e. Cisco routers) and MIPv4 also puts a dependency on this >RFC for its own ICMP based agent advertisements. Lets suppose you >have a mobility agent upstream in your backhaul somewhere advertising >into your attached ad hoc network. Should the TTL field be used to limit >the flood of these ICMP broadcasts over the MANET? > >It seems you need to get MIPv4 to update your MANET route table >with the default route being to the mobility agent whenever one is >discovered or a new registration occurs. > >One can think of optimizations that allow a reduction in flooding >like proxy responses to agent solicitations etc. > >Thanks, > >Phil >-----Original Message----- >From: John Paul O'Grady [mailto:jpogrady@cit.ie] >Sent: Wednesday, October 16, 2002 9:11 AM >To: manet@ietf.org >Subject: [manet] ipv4 address and network address translation > >Hello >I have a question in regard to ipv4 addresses in autoconfiguration in >manets. I know globally unique ipv6 addresses can be created >dynamically using for example a nodes mac addresses. >This wont be possible for ipv4 addresses (32 bit addresses)and so if >a globally unique ipv4 addresses cant be created will private >addresses have to be used in the manet? >Then if the node wants to access the internet, will network address >translation (NAT) have to be used to translate the private address >into a public address? >john paul o grady > >-- >Phillip D. Neumiller (pneumiller@meshnetworks.com) >My PGP key can be imported from the following URL: http://pgpkeys.mit.edu >BTW: It is undecidable whether an arithmetical formula is true! >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _________________________________________________________________ Unlimited Internet access for only $21.95/month.  Try MSN! http://resourcecenter.msn.com/access/plans/2monthsfree.asp _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Oct 20 17:00:54 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03096 for ; Sun, 20 Oct 2002 17:00:54 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9KL2hR10043 for manet-archive@odin.ietf.org; Sun, 20 Oct 2002 17:02:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9KL2hv10040 for ; Sun, 20 Oct 2002 17:02:43 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03089 for ; Sun, 20 Oct 2002 17:00:23 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9KKw7v09415; Sun, 20 Oct 2002 16:58:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9KKsSv09352 for ; Sun, 20 Oct 2002 16:54:28 -0400 Received: from tesla.eecs.ku.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02920 for ; Sun, 20 Oct 2002 16:52:09 -0400 (EDT) Received: from tesla.eecs.ku.edu (tesla.eecs.ku.edu [129.237.87.2]) by tesla.eecs.ku.edu (8.10.2/8.10.2) with ESMTP id g9KKsM085215 for ; Sun, 20 Oct 2002 15:54:22 -0500 (CDT) Date: Sun, 20 Oct 2002 15:54:22 -0500 (CDT) From: Gayathri Chandrasekaran To: manet@ietf.org Message-ID: <20021020154937.K84991-100000@tesla.eecs.ku.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] OLSR implementation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, I would like to know if OLSR runs over ATM interfaces.I'm trying to implement some version 7 features to the INRIA version 3 OLSR linux implementation. So for initial testing purposes can ATM interfaces be used? thanks gayathri Gayathri Chandrasekaran Department of Electrical Engineering and Computer Science University of Kansas Lawrence,KS-66045. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sun Oct 20 17:00:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03109 for ; Sun, 20 Oct 2002 17:00:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9KKw7v09415; Sun, 20 Oct 2002 16:58:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9KKsSv09352 for ; Sun, 20 Oct 2002 16:54:28 -0400 Received: from tesla.eecs.ku.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02920 for ; Sun, 20 Oct 2002 16:52:09 -0400 (EDT) Received: from tesla.eecs.ku.edu (tesla.eecs.ku.edu [129.237.87.2]) by tesla.eecs.ku.edu (8.10.2/8.10.2) with ESMTP id g9KKsM085215 for ; Sun, 20 Oct 2002 15:54:22 -0500 (CDT) Date: Sun, 20 Oct 2002 15:54:22 -0500 (CDT) From: Gayathri Chandrasekaran To: manet@ietf.org Message-ID: <20021020154937.K84991-100000@tesla.eecs.ku.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] OLSR implementation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, I would like to know if OLSR runs over ATM interfaces.I'm trying to implement some version 7 features to the INRIA version 3 OLSR linux implementation. So for initial testing purposes can ATM interfaces be used? thanks gayathri Gayathri Chandrasekaran Department of Electrical Engineering and Computer Science University of Kansas Lawrence,KS-66045. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Oct 20 19:30:48 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04494 for ; Sun, 20 Oct 2002 19:30:48 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9KNWdb15511 for manet-archive@odin.ietf.org; Sun, 20 Oct 2002 19:32:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9KNWdv15508 for ; Sun, 20 Oct 2002 19:32:39 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04490 for ; Sun, 20 Oct 2002 19:30:17 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9KNQdv15338; Sun, 20 Oct 2002 19:26:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9KNOuv15296 for ; Sun, 20 Oct 2002 19:24:56 -0400 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04408 for ; Sun, 20 Oct 2002 19:22:35 -0400 (EDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 20 Oct 2002 16:24:48 -0700 Received: from 62.255.32.5 by lw14fd.law14.hotmail.msn.com with HTTP; Sun, 20 Oct 2002 23:24:48 GMT X-Originating-IP: [62.255.32.5] From: "hussam amin" To: manet@ietf.org Date: Mon, 21 Oct 2002 00:24:48 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 20 Oct 2002 23:24:48.0970 (UTC) FILETIME=[E227A2A0:01C2788F] Subject: [manet] (no subject) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , hi _________________________________________________________________ Get a speedy connection with MSN Broadband.  Join now! http://resourcecenter.msn.com/access/plans/freeactivation.asp _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sun Oct 20 19:30:51 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04507 for ; Sun, 20 Oct 2002 19:30:50 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9KNQdv15338; Sun, 20 Oct 2002 19:26:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9KNOuv15296 for ; Sun, 20 Oct 2002 19:24:56 -0400 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04408 for ; Sun, 20 Oct 2002 19:22:35 -0400 (EDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 20 Oct 2002 16:24:48 -0700 Received: from 62.255.32.5 by lw14fd.law14.hotmail.msn.com with HTTP; Sun, 20 Oct 2002 23:24:48 GMT X-Originating-IP: [62.255.32.5] From: "hussam amin" To: manet@ietf.org Date: Mon, 21 Oct 2002 00:24:48 +0100 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 20 Oct 2002 23:24:48.0970 (UTC) FILETIME=[E227A2A0:01C2788F] Subject: [manet] (no subject) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , hi _________________________________________________________________ Get a speedy connection with MSN Broadband.  Join now! http://resourcecenter.msn.com/access/plans/freeactivation.asp _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 21 05:44:17 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22406 for ; Mon, 21 Oct 2002 05:44:16 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9L9k0n18275 for manet-archive@odin.ietf.org; Mon, 21 Oct 2002 05:46:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9L9k0v18268 for ; Mon, 21 Oct 2002 05:46:00 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22377 for ; Mon, 21 Oct 2002 05:43:45 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9L9hrv18171; Mon, 21 Oct 2002 05:43:53 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9L9dXv18055 for ; Mon, 21 Oct 2002 05:39:33 -0400 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22329 for ; Mon, 21 Oct 2002 05:37:19 -0400 (EDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 21 Oct 2002 02:39:32 -0700 Received: from 212.4.33.133 by lw12fd.law12.hotmail.msn.com with HTTP; Mon, 21 Oct 2002 09:39:32 GMT X-Originating-IP: [212.4.33.133] From: "Berner Vegge" To: manet@ietf.org Date: Mon, 21 Oct 2002 11:39:32 +0200 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 21 Oct 2002 09:39:32.0750 (UTC) FILETIME=[C299D2E0:01C278E5] Subject: [manet] Management of Ad Hoc networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: ,
Hello!
An Ad-Hoc network should not require a lot of management. Still it may be
relevant to have some fault, performance, security and configuration management.
For example it may be important to detect bottlenecks, nodes about to loose their
connection to the network, nodes about to loose their battery power etc.
 
How do you think such management should be performed? Should we use
SNMP and existing MIBs or are there other ideas? Do you think existing
MIBs cover all what an Ad-Hoc network requires, or do we need something
more/new?
 
Do you know about any work ongoing or papers etc regarding management of Ad-Hoc networks?
 
Thanks!
 
Best Regards  Berner
 
 
 

Broadband? Dial-up? Get reliable MSN Internet Access. Click Here _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 21 05:44:29 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22419 for ; Mon, 21 Oct 2002 05:44:29 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9L9hrv18171; Mon, 21 Oct 2002 05:43:53 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9L9dXv18055 for ; Mon, 21 Oct 2002 05:39:33 -0400 Received: from hotmail.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22329 for ; Mon, 21 Oct 2002 05:37:19 -0400 (EDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 21 Oct 2002 02:39:32 -0700 Received: from 212.4.33.133 by lw12fd.law12.hotmail.msn.com with HTTP; Mon, 21 Oct 2002 09:39:32 GMT X-Originating-IP: [212.4.33.133] From: "Berner Vegge" To: manet@ietf.org Date: Mon, 21 Oct 2002 11:39:32 +0200 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 21 Oct 2002 09:39:32.0750 (UTC) FILETIME=[C299D2E0:01C278E5] Subject: [manet] Management of Ad Hoc networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: ,
Hello!
An Ad-Hoc network should not require a lot of management. Still it may be
relevant to have some fault, performance, security and configuration management.
For example it may be important to detect bottlenecks, nodes about to loose their
connection to the network, nodes about to loose their battery power etc.
 
How do you think such management should be performed? Should we use
SNMP and existing MIBs or are there other ideas? Do you think existing
MIBs cover all what an Ad-Hoc network requires, or do we need something
more/new?
 
Do you know about any work ongoing or papers etc regarding management of Ad-Hoc networks?
 
Thanks!
 
Best Regards  Berner
 
 
 

Broadband? Dial-up? Get reliable MSN Internet Access. Click Here _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 21 08:23:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25257 for ; Mon, 21 Oct 2002 08:23:25 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9LCPBX25292 for manet-archive@odin.ietf.org; Mon, 21 Oct 2002 08:25:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LCPBv25289 for ; Mon, 21 Oct 2002 08:25:11 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25213 for ; Mon, 21 Oct 2002 08:22:54 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LCMVv25099; Mon, 21 Oct 2002 08:22:31 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LCKJv24961 for ; Mon, 21 Oct 2002 08:20:19 -0400 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25057 for ; Mon, 21 Oct 2002 08:18:02 -0400 (EDT) Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g9LCKHi496324; Mon, 21 Oct 2002 08:20:17 -0400 (EDT) Received: from zathras (zathras.cc.vt.edu [198.82.162.117]) by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1.6-EA) with ESMTP id AQN12774; Mon, 21 Oct 2002 08:20:16 -0400 (EDT) X-WebMail-UserID: kphanse Date: Mon, 21 Oct 2002 08:20:16 -0400 From: kphanse To: Berner Vegge , manet X-EXP32-SerialNo: 00002964 Subject: RE: [manet] Management of Ad Hoc networks Message-ID: <3DB5CEAE@zathras> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: WebMail (Hydra) SMTP v3.61.08 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Berner, Some work has been done with this regards, e.g., W. Chen, N. Jain and S. Singh, ANMP: Ad hoc network network management protocol, IEEE Journal on Selected Areas in Communications 17(8) (August 1999) 1506--1531. Also some work is being currently done at Virginia Tech in the field of policy-based QoS management in ad hoc networks. Relevant papers (submitted for publication), including a survey paper, are available at: http://www.ee.vt.edu/~kphanse/unpublished.html Hope this helps. If you have any questions, please feel free to contact me at: kphanse@vt.edu regards Kaustubh ---------------------- PhD student, ECE Dept. Alexandria Research Institute Virginia Tech _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 21 08:23:29 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25273 for ; Mon, 21 Oct 2002 08:23:29 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LCMVv25099; Mon, 21 Oct 2002 08:22:31 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LCKJv24961 for ; Mon, 21 Oct 2002 08:20:19 -0400 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25057 for ; Mon, 21 Oct 2002 08:18:02 -0400 (EDT) Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g9LCKHi496324; Mon, 21 Oct 2002 08:20:17 -0400 (EDT) Received: from zathras (zathras.cc.vt.edu [198.82.162.117]) by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1.6-EA) with ESMTP id AQN12774; Mon, 21 Oct 2002 08:20:16 -0400 (EDT) X-WebMail-UserID: kphanse Date: Mon, 21 Oct 2002 08:20:16 -0400 From: kphanse To: Berner Vegge , manet X-EXP32-SerialNo: 00002964 Subject: RE: [manet] Management of Ad Hoc networks Message-ID: <3DB5CEAE@zathras> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: WebMail (Hydra) SMTP v3.61.08 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Berner, Some work has been done with this regards, e.g., W. Chen, N. Jain and S. Singh, ANMP: Ad hoc network network management protocol, IEEE Journal on Selected Areas in Communications 17(8) (August 1999) 1506--1531. Also some work is being currently done at Virginia Tech in the field of policy-based QoS management in ad hoc networks. Relevant papers (submitted for publication), including a survey paper, are available at: http://www.ee.vt.edu/~kphanse/unpublished.html Hope this helps. If you have any questions, please feel free to contact me at: kphanse@vt.edu regards Kaustubh ---------------------- PhD student, ECE Dept. Alexandria Research Institute Virginia Tech _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 21 15:08:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11144 for ; Mon, 21 Oct 2002 15:08:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LJ8hv16575; Mon, 21 Oct 2002 15:08:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LJ6Hv15971 for ; Mon, 21 Oct 2002 15:06:17 -0400 Received: from cantelli.csl.uiuc.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10961 for ; Mon, 21 Oct 2002 15:03:57 -0400 (EDT) Received: from localhost (kawadia@localhost) by cantelli.csl.uiuc.edu (8.11.6/8.11.6) with ESMTP id g9LJ6Ck10643 for ; Mon, 21 Oct 2002 14:06:12 -0500 X-Authentication-Warning: cantelli.csl.uiuc.edu: kawadia owned process doing -bs Date: Mon, 21 Oct 2002 14:06:12 -0500 (CDT) From: Vikas Kawadia X-X-Sender: kawadia@cantelli.csl.uiuc.edu To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Network Information Theory Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a message from Prof. P. R. Kumar. I am posting for him, since he had some problems posting from his account. Thanks Vikas -------------------------- Dear Manet colleagues: Attached is the link of a paper that may be of interest to MANET members: http://black.csl.uiuc.edu/~prkumar/ps_files/net_inf_theory.pdf Here is the core of the issue that the paper deals with. The present proposal for ad hoc networks, around which many efforts in this group are centered, is to operate them in a multi-hop manner, where, at each hop, packets are fully decoded, treating all interference as noise. This mode of operation has several advantages. First, the receivers can be simple, since all interference can simply be treated as noise. Second, the multi-hop operation allows us to think of the hops as traversing "links," and so gives rise to the convenient abstraction of "links in space." This proposed mode of operation gives rise to several protocol needs. First, since we one needs to find multi-hop paths to destinations, it gives rise to the "routing problem." Second, since all interference is treated as noise, it is desirable to reduce interference in the vicinity of the receiver. This gives rise to the "media access control problem." Third, since all interference is treated as noise, one attempts to reduce the power levels of transmissions to reduce the interference. This gives rise to the "power control problem." However, a fundamental question that one should first ask, before doing any protocol design, is: Is this really the right way to operate wireless ad hoc networks? For example, is it really fine to treat interference as noise? Note that doing so gives rise to the notion of "collisions." However, packets need not collide. For example, if a node is transmitting at low power to an intended receiver, and simultaneously there is a high powered interferer, then the receiving node can first estimate the high powered interference, and subtract it, thus recovering the low powered packet. The packets thus do not destructively collide. The problem is that wireless networks do not come with links, and so they can be operated in all kinds of ways. For example, one could simply broadcast signals at high power level, without any relaying. Then receivers could simply do sophisticated multi-user detection. This alternative would give rise to the need for a separate set of protocols. For example the need for multi-user detection would give rise to the need for more sophisticated signal processing algorithms. On the other hand there would be no routing problem, etc. Other possibilities exist too, which cannot be ruled out a priori. For example a group of nodes could try to cancel the interference of another group of nodes at a third set of nodes, rather than more "positively" cooperating by relaying each others packets. The problem is that nothing can be ruled out a priori. This paper addresses the fundamental issue of how nodes should cooperate in a wireless network. One result that should be of interest to this group is that when the medium has any absorption or high attenuation, then the proposed multi-hop mode of operation is indeed order optimal. This provides a sound foundation for all the protocol work going on. However, when the medium has no absorption all then other interesting for operating wireless networks emerge, which are described in the paper. The paper also shows a fundamental bound on the information that can be transported across a wireless network in terms of the total power used for transmissions, etc. To cut a long story short, the paper attempts to provide a sound foundation to the whole problem of protocol development for ad hoc networks. It provides a connection between network information theory and protocol development. --Kumar -------------- P. R. Kumar Franklin W. Woeltge Professor Dept. of Electrical and Computer Engineering, and Research Professor, Coordinated Science Lab Campus Office: Room 163, C&SRL Bldg Campus Mail Code: MC-228 Mailing Address: Office: 217-333-7476 Univ. of Illinois Secretary: 217-333-0282 CSL Fax: 217-244-1653 1308 West Main St WWW: http://black.csl.uiuc.edu/~prkumar Urbana, IL 61801 Email: prkumar@uiuc.edu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 21 15:11:46 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11382 for ; Mon, 21 Oct 2002 15:11:46 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9LJDZD16799 for manet-archive@odin.ietf.org; Mon, 21 Oct 2002 15:13:35 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LJDZv16796 for ; Mon, 21 Oct 2002 15:13:35 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11347 for ; Mon, 21 Oct 2002 15:11:15 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LJ8hv16575; Mon, 21 Oct 2002 15:08:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LJ6Hv15971 for ; Mon, 21 Oct 2002 15:06:17 -0400 Received: from cantelli.csl.uiuc.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10961 for ; Mon, 21 Oct 2002 15:03:57 -0400 (EDT) Received: from localhost (kawadia@localhost) by cantelli.csl.uiuc.edu (8.11.6/8.11.6) with ESMTP id g9LJ6Ck10643 for ; Mon, 21 Oct 2002 14:06:12 -0500 X-Authentication-Warning: cantelli.csl.uiuc.edu: kawadia owned process doing -bs Date: Mon, 21 Oct 2002 14:06:12 -0500 (CDT) From: Vikas Kawadia X-X-Sender: kawadia@cantelli.csl.uiuc.edu To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Network Information Theory Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a message from Prof. P. R. Kumar. I am posting for him, since he had some problems posting from his account. Thanks Vikas -------------------------- Dear Manet colleagues: Attached is the link of a paper that may be of interest to MANET members: http://black.csl.uiuc.edu/~prkumar/ps_files/net_inf_theory.pdf Here is the core of the issue that the paper deals with. The present proposal for ad hoc networks, around which many efforts in this group are centered, is to operate them in a multi-hop manner, where, at each hop, packets are fully decoded, treating all interference as noise. This mode of operation has several advantages. First, the receivers can be simple, since all interference can simply be treated as noise. Second, the multi-hop operation allows us to think of the hops as traversing "links," and so gives rise to the convenient abstraction of "links in space." This proposed mode of operation gives rise to several protocol needs. First, since we one needs to find multi-hop paths to destinations, it gives rise to the "routing problem." Second, since all interference is treated as noise, it is desirable to reduce interference in the vicinity of the receiver. This gives rise to the "media access control problem." Third, since all interference is treated as noise, one attempts to reduce the power levels of transmissions to reduce the interference. This gives rise to the "power control problem." However, a fundamental question that one should first ask, before doing any protocol design, is: Is this really the right way to operate wireless ad hoc networks? For example, is it really fine to treat interference as noise? Note that doing so gives rise to the notion of "collisions." However, packets need not collide. For example, if a node is transmitting at low power to an intended receiver, and simultaneously there is a high powered interferer, then the receiving node can first estimate the high powered interference, and subtract it, thus recovering the low powered packet. The packets thus do not destructively collide. The problem is that wireless networks do not come with links, and so they can be operated in all kinds of ways. For example, one could simply broadcast signals at high power level, without any relaying. Then receivers could simply do sophisticated multi-user detection. This alternative would give rise to the need for a separate set of protocols. For example the need for multi-user detection would give rise to the need for more sophisticated signal processing algorithms. On the other hand there would be no routing problem, etc. Other possibilities exist too, which cannot be ruled out a priori. For example a group of nodes could try to cancel the interference of another group of nodes at a third set of nodes, rather than more "positively" cooperating by relaying each others packets. The problem is that nothing can be ruled out a priori. This paper addresses the fundamental issue of how nodes should cooperate in a wireless network. One result that should be of interest to this group is that when the medium has any absorption or high attenuation, then the proposed multi-hop mode of operation is indeed order optimal. This provides a sound foundation for all the protocol work going on. However, when the medium has no absorption all then other interesting for operating wireless networks emerge, which are described in the paper. The paper also shows a fundamental bound on the information that can be transported across a wireless network in terms of the total power used for transmissions, etc. To cut a long story short, the paper attempts to provide a sound foundation to the whole problem of protocol development for ad hoc networks. It provides a connection between network information theory and protocol development. --Kumar -------------- P. R. Kumar Franklin W. Woeltge Professor Dept. of Electrical and Computer Engineering, and Research Professor, Coordinated Science Lab Campus Office: Room 163, C&SRL Bldg Campus Mail Code: MC-228 Mailing Address: Office: 217-333-7476 Univ. of Illinois Secretary: 217-333-0282 CSL Fax: 217-244-1653 1308 West Main St WWW: http://black.csl.uiuc.edu/~prkumar Urbana, IL 61801 Email: prkumar@uiuc.edu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 04:17:15 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08615 for ; Tue, 22 Oct 2002 04:17:15 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M8Fnv29819; Tue, 22 Oct 2002 04:15:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M8Cfv29727 for ; Tue, 22 Oct 2002 04:12:41 -0400 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08500 for ; Tue, 22 Oct 2002 04:10:12 -0400 (EDT) Message-Id: <200210220810.EAA08500@ietf.org> Received: (eyou send program); Tue, 22 Oct 2002 16:10:18 +0800 Received: from unknown (HELO yangwh) (unknown@166.111.67.88) by 166.111.8.16 with SMTP; Tue, 22 Oct 2002 16:10:18 +0800 Date: Tue, 22 Oct 2002 16:13:10 +0800 From: "yang weihua" To: "manet@ietf.org" X-mailer: Foxmail 4.1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9M8Cfv29728 Subject: [manet] AODV hello and neighbor Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit hi, When i run a simple simulation on aodv, i found that NeighborTimer and HelloTimer handles have never been invoked. I just cann't understand this phenomenon.why? What's more, i want to do some modifications by adding infomation to hello messages. If the NeighborTimer or HelloTimer don't work, what i can do? Sincely for your help. Best regards! ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yang weihua ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yangwh00@mails.tsinghua.edu.cn ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-22 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 04:26:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08770 for ; Tue, 22 Oct 2002 04:26:44 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9M8Sem30214 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 04:28:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M8Sev30211 for ; Tue, 22 Oct 2002 04:28:40 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08737 for ; Tue, 22 Oct 2002 04:26:12 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M8Fnv29819; Tue, 22 Oct 2002 04:15:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M8Cfv29727 for ; Tue, 22 Oct 2002 04:12:41 -0400 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08500 for ; Tue, 22 Oct 2002 04:10:12 -0400 (EDT) Message-Id: <200210220810.EAA08500@ietf.org> Received: (eyou send program); Tue, 22 Oct 2002 16:10:18 +0800 Received: from unknown (HELO yangwh) (unknown@166.111.67.88) by 166.111.8.16 with SMTP; Tue, 22 Oct 2002 16:10:18 +0800 Date: Tue, 22 Oct 2002 16:13:10 +0800 From: "yang weihua" To: "manet@ietf.org" X-mailer: Foxmail 4.1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9M8Cfv29728 Subject: [manet] AODV hello and neighbor Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hi, When i run a simple simulation on aodv, i found that NeighborTimer and HelloTimer handles have never been invoked. I just cann't understand this phenomenon.why? What's more, i want to do some modifications by adding infomation to hello messages. If the NeighborTimer or HelloTimer don't work, what i can do? Sincely for your help. Best regards! ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yang weihua ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yangwh00@mails.tsinghua.edu.cn ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-22 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 04:48:45 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09036 for ; Tue, 22 Oct 2002 04:48:44 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9M8of431507 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 04:50:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M8ofv31504 for ; Tue, 22 Oct 2002 04:50:41 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09028 for ; Tue, 22 Oct 2002 04:48:13 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M8iXv31257; Tue, 22 Oct 2002 04:44:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M8fLv31174 for ; Tue, 22 Oct 2002 04:41:21 -0400 Received: from thoth.sbs.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08918 for ; Tue, 22 Oct 2002 04:38:52 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g9M8XYP14448; Tue, 22 Oct 2002 10:33:38 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9M8XXc16135; Tue, 22 Oct 2002 10:33:34 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9M8XUIu028013; Tue, 22 Oct 2002 10:33:30 +0200 (MET DST) Message-ID: <3DB50F74.417C85BA@mchp.siemens.de> Date: Tue, 22 Oct 2002 10:42:28 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: yang weihua , "manet@ietf.org" Subject: Re: [manet] AODV hello and neighbor References: <200210220810.EAA08500@ietf.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, the reason is simple!! we have this piece of code in aodv.cc int AODV::command(int argc, const char*const* argv) { if(argc == 2) { Tcl& tcl = Tcl::instance(); if(strncasecmp(argv[1], "id", 2) == 0) { tcl.resultf("%d", index); return TCL_OK; } if(strncasecmp(argv[1], "start", 2) == 0) { btimer.handle((Event*) 0); #ifndef AODV_LINK_LAYER_DETECTION htimer.handle((Event*) 0); ntimer.handle((Event*) 0); #endif // LINK LAYER DETECTION rtimer.handle((Event*) 0); return TCL_OK; } } As you can see, htimer (hello timer)and ntimer(neighbor timer) are only invoked when AODV_LINK_LAYER_DETECTION (allows using the link layer feedback to determine if a link is down) is not defined. To ativate these too timers you must NOT define AODV_LINK_LAYER_DETECTION in your aodv.h file. yang weihua wrote: > hi, > When i run a simple simulation on aodv, i found that NeighborTimer and HelloTimer > handles have never been invoked. I just cann't understand this phenomenon.why? > What's more, i want to do some modifications by adding infomation to hello messages. > If the NeighborTimer or HelloTimer don't work, what i can do? > Sincely for your help. > > > > Best regards! > > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yang weihua > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yangwh00@mails.tsinghua.edu.cn > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-22 > > _______________________________________________ > 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-admin@ietf.org Tue Oct 22 04:48:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09054 for ; Tue, 22 Oct 2002 04:48:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M8iXv31257; Tue, 22 Oct 2002 04:44:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M8fLv31174 for ; Tue, 22 Oct 2002 04:41:21 -0400 Received: from thoth.sbs.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08918 for ; Tue, 22 Oct 2002 04:38:52 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g9M8XYP14448; Tue, 22 Oct 2002 10:33:38 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9M8XXc16135; Tue, 22 Oct 2002 10:33:34 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9M8XUIu028013; Tue, 22 Oct 2002 10:33:30 +0200 (MET DST) Message-ID: <3DB50F74.417C85BA@mchp.siemens.de> Date: Tue, 22 Oct 2002 10:42:28 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: yang weihua , "manet@ietf.org" Subject: Re: [manet] AODV hello and neighbor References: <200210220810.EAA08500@ietf.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi, the reason is simple!! we have this piece of code in aodv.cc int AODV::command(int argc, const char*const* argv) { if(argc == 2) { Tcl& tcl = Tcl::instance(); if(strncasecmp(argv[1], "id", 2) == 0) { tcl.resultf("%d", index); return TCL_OK; } if(strncasecmp(argv[1], "start", 2) == 0) { btimer.handle((Event*) 0); #ifndef AODV_LINK_LAYER_DETECTION htimer.handle((Event*) 0); ntimer.handle((Event*) 0); #endif // LINK LAYER DETECTION rtimer.handle((Event*) 0); return TCL_OK; } } As you can see, htimer (hello timer)and ntimer(neighbor timer) are only invoked when AODV_LINK_LAYER_DETECTION (allows using the link layer feedback to determine if a link is down) is not defined. To ativate these too timers you must NOT define AODV_LINK_LAYER_DETECTION in your aodv.h file. yang weihua wrote: > hi, > When i run a simple simulation on aodv, i found that NeighborTimer and HelloTimer > handles have never been invoked. I just cann't understand this phenomenon.why? > What's more, i want to do some modifications by adding infomation to hello messages. > If the NeighborTimer or HelloTimer don't work, what i can do? > Sincely for your help. > > > > Best regards! > > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yang weihua > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yangwh00@mails.tsinghua.edu.cn > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-22 > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 05:18:33 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09558 for ; Tue, 22 Oct 2002 05:18:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9M9KKa00712 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 05:20:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M9KJv00709 for ; Tue, 22 Oct 2002 05:20:19 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09554 for ; Tue, 22 Oct 2002 05:18:02 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M9Irv00558; Tue, 22 Oct 2002 05:18:53 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M9CAv00344 for ; Tue, 22 Oct 2002 05:12:10 -0400 Received: from relay2.clb.oleane.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09392 for ; Tue, 22 Oct 2002 05:09:51 -0400 (EDT) Received: from chantal (upper-side.rain.fr [194.250.212.114]) by relay2.clb.oleane.net with SMTP id g9M9C73u013985 for ; Tue, 22 Oct 2002 11:12:07 +0200 Message-ID: <00df01c279ab$c2e744a0$0701a8c0@upperside> From: "Peter Lewis" To: Date: Tue, 22 Oct 2002 11:16:53 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DB_01C279BC.862CF120" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [manet] IP-Based Cellular Networks (IPCN) 2003 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_00DB_01C279BC.862CF120 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit IP-Based Cellular Networks (IPCN) 2003 Paris, June 17-20, 2003 IPCN has been for four years now one of the most interesting event focusing on the evolution of mobile networks in connection with the Internet protocol. A call for proposals is online at: http://www.upperside.fr/ipcn03/ipcn03cfp.htm ------=_NextPart_000_00DB_01C279BC.862CF120 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

IP-Based Cellular Networks (IPCN) 2003
Paris, = June 17-20,=20 2003

IPCN has been for four years now one of the most interesting event = focusing=20 on the evolution of mobile networks in connection with the Internet=20 protocol.

A call for proposals is online at:
http://www.uppersid= e.fr/ipcn03/ipcn03cfp.htm
 
------=_NextPart_000_00DB_01C279BC.862CF120-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 05:18:35 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09571 for ; Tue, 22 Oct 2002 05:18:35 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M9Irv00558; Tue, 22 Oct 2002 05:18:53 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M9CAv00344 for ; Tue, 22 Oct 2002 05:12:10 -0400 Received: from relay2.clb.oleane.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09392 for ; Tue, 22 Oct 2002 05:09:51 -0400 (EDT) Received: from chantal (upper-side.rain.fr [194.250.212.114]) by relay2.clb.oleane.net with SMTP id g9M9C73u013985 for ; Tue, 22 Oct 2002 11:12:07 +0200 Message-ID: <00df01c279ab$c2e744a0$0701a8c0@upperside> From: "Peter Lewis" To: Date: Tue, 22 Oct 2002 11:16:53 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DB_01C279BC.862CF120" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [manet] IP-Based Cellular Networks (IPCN) 2003 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_00DB_01C279BC.862CF120 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit IP-Based Cellular Networks (IPCN) 2003 Paris, June 17-20, 2003 IPCN has been for four years now one of the most interesting event focusing on the evolution of mobile networks in connection with the Internet protocol. A call for proposals is online at: http://www.upperside.fr/ipcn03/ipcn03cfp.htm ------=_NextPart_000_00DB_01C279BC.862CF120 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

IP-Based Cellular Networks (IPCN) 2003
Paris, = June 17-20,=20 2003

IPCN has been for four years now one of the most interesting event = focusing=20 on the evolution of mobile networks in connection with the Internet=20 protocol.

A call for proposals is online at:
http://www.uppersid= e.fr/ipcn03/ipcn03cfp.htm
 
------=_NextPart_000_00DB_01C279BC.862CF120-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 05:55:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10283 for ; Tue, 22 Oct 2002 05:55:44 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9M9vVQ02713 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 05:57:31 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M9vVv02710 for ; Tue, 22 Oct 2002 05:57:31 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10265 for ; Tue, 22 Oct 2002 05:55:13 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M9uAv02425; Tue, 22 Oct 2002 05:56:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M9pcv02326 for ; Tue, 22 Oct 2002 05:51:38 -0400 Received: from mailhub1.shef.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10055 for ; Tue, 22 Oct 2002 05:49:20 -0400 (EDT) Received: from impala.shef.ac.uk ([143.167.2.25]) by mailhub1.shef.ac.uk with esmtp (Exim 3.22 #4) id 183vhJ-0007P5-00; Tue, 22 Oct 2002 10:51:37 +0100 Received: from [143.167.251.101] (helo=dell) by impala.shef.ac.uk with esmtp (Exim 3.33 #3) id 183vhI-0005W9-00; Tue, 22 Oct 2002 10:51:37 +0100 From: "G.Lu" To: "'yang weihua'" , Subject: RE: [manet] AODV hello and neighbor Date: Tue, 22 Oct 2002 10:54:25 +0100 Message-ID: <000501c279b1$014fbb50$65fba78f@dell> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <200210220810.EAA08500@ietf.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9M9pcv02327 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, If you use NS2b8, just comment out the AODV_LINK_LAYER_DETECTION in aodv.h. -------------------------------------------------- Mr Gang Lu ************************************************** Centre for Mobile Communications Research Department of Electronics & Electrical Engineering The University of Sheffield Mobile: +44-(0)7786-554632 (Voda) Office: +44-(0)1142225182 HomePage: http://www.dcs.shef.ac.uk/~ganglu ************************************************** -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of yang weihua Sent: 22 October 2002 09:13 To: manet@ietf.org Subject: [manet] AODV hello and neighbor hi, When i run a simple simulation on aodv, i found that NeighborTimer and HelloTimer handles have never been invoked. I just cann't understand this phenomenon.why? What's more, i want to do some modifications by adding infomation to hello messages. If the NeighborTimer or HelloTimer don't work, what i can do? Sincely for your help. Best regards! ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yang weihua ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yangwh00@mails.tsinghua.edu.cn ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-22 _______________________________________________ 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-admin@ietf.org Tue Oct 22 05:56:02 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10296 for ; Tue, 22 Oct 2002 05:56:02 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M9uAv02425; Tue, 22 Oct 2002 05:56:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9M9pcv02326 for ; Tue, 22 Oct 2002 05:51:38 -0400 Received: from mailhub1.shef.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10055 for ; Tue, 22 Oct 2002 05:49:20 -0400 (EDT) Received: from impala.shef.ac.uk ([143.167.2.25]) by mailhub1.shef.ac.uk with esmtp (Exim 3.22 #4) id 183vhJ-0007P5-00; Tue, 22 Oct 2002 10:51:37 +0100 Received: from [143.167.251.101] (helo=dell) by impala.shef.ac.uk with esmtp (Exim 3.33 #3) id 183vhI-0005W9-00; Tue, 22 Oct 2002 10:51:37 +0100 From: "G.Lu" To: "'yang weihua'" , Subject: RE: [manet] AODV hello and neighbor Date: Tue, 22 Oct 2002 10:54:25 +0100 Message-ID: <000501c279b1$014fbb50$65fba78f@dell> MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <200210220810.EAA08500@ietf.org> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9M9pcv02327 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi, If you use NS2b8, just comment out the AODV_LINK_LAYER_DETECTION in aodv.h. -------------------------------------------------- Mr Gang Lu ************************************************** Centre for Mobile Communications Research Department of Electronics & Electrical Engineering The University of Sheffield Mobile: +44-(0)7786-554632 (Voda) Office: +44-(0)1142225182 HomePage: http://www.dcs.shef.ac.uk/~ganglu ************************************************** -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of yang weihua Sent: 22 October 2002 09:13 To: manet@ietf.org Subject: [manet] AODV hello and neighbor hi, When i run a simple simulation on aodv, i found that NeighborTimer and HelloTimer handles have never been invoked. I just cann't understand this phenomenon.why? What's more, i want to do some modifications by adding infomation to hello messages. If the NeighborTimer or HelloTimer don't work, what i can do? Sincely for your help. Best regards! ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yang weihua ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yangwh00@mails.tsinghua.edu.cn ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-22 _______________________________________________ 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-admin@ietf.org Tue Oct 22 08:07:58 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13147 for ; Tue, 22 Oct 2002 08:07:58 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MC7hv09415; Tue, 22 Oct 2002 08:07:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MC4Sv08733 for ; Tue, 22 Oct 2002 08:04:28 -0400 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13037 for ; Tue, 22 Oct 2002 08:02:10 -0400 (EDT) Message-Id: <200210221202.IAA13037@ietf.org> Received: (eyou send program); Tue, 22 Oct 2002 20:02:20 +0800 Received: from 166.111.66.148 by mails.tsinghua.edu.cn with HTTP; Tue, 22 Oct 2002 20:02:20 +0800 X-WebMAIL-MUA: [166.111.66.148] From: "3fad9ca8ab7fa48557" To: manet@ietf.org Date: Tue, 22 Oct 2002 20:02:20 +0800 Reply-To: "3fad9ca8ab7fa48557" Content-Type: text/plain Subject: [manet] (no subject) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , hi. But i have another question.During the simulation, i found that the length of route queue is sometimes large, but at the same time the length of Prime queue (queue between ll and mac) always remains to be zero, (except one time equals to 1). why? i cann't understand. for your help. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 08:13:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13326 for ; Tue, 22 Oct 2002 08:13:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9MCFPO09770 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 08:15:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MCFPv09763 for ; Tue, 22 Oct 2002 08:15:25 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13322 for ; Tue, 22 Oct 2002 08:13:07 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MC7hv09415; Tue, 22 Oct 2002 08:07:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MC4Sv08733 for ; Tue, 22 Oct 2002 08:04:28 -0400 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13037 for ; Tue, 22 Oct 2002 08:02:10 -0400 (EDT) Message-Id: <200210221202.IAA13037@ietf.org> Received: (eyou send program); Tue, 22 Oct 2002 20:02:20 +0800 Received: from 166.111.66.148 by mails.tsinghua.edu.cn with HTTP; Tue, 22 Oct 2002 20:02:20 +0800 X-WebMAIL-MUA: [166.111.66.148] From: "3fad9ca8ab7fa48557" To: manet@ietf.org Date: Tue, 22 Oct 2002 20:02:20 +0800 Reply-To: "3fad9ca8ab7fa48557" Content-Type: text/plain Subject: [manet] (no subject) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , hi. But i have another question.During the simulation, i found that the length of route queue is sometimes large, but at the same time the length of Prime queue (queue between ll and mac) always remains to be zero, (except one time equals to 1). why? i cann't understand. for your help. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 09:05:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15220 for ; Tue, 22 Oct 2002 09:05:36 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9MD7O512692 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 09:07:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MD7Ov12689 for ; Tue, 22 Oct 2002 09:07:24 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15187 for ; Tue, 22 Oct 2002 09:05:05 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MD5qv12085; Tue, 22 Oct 2002 09:05:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MD4Sv12040 for ; Tue, 22 Oct 2002 09:04:28 -0400 Received: from webmails.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA15082 for ; Tue, 22 Oct 2002 09:02:00 -0400 (EDT) Received: (qmail 22011 invoked by uid 511); 22 Oct 2002 13:04:15 -0000 Message-ID: <20021022130415.22010.qmail@webmails.com> Content-Type: multipart/alternative; boundary="----------=_1035291854-21766-0" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.411 (Entity 5.404) From: "moez gadri" To: manet@ietf.org Organization: WebMailS - http://www.webmails.com Date: Tue, 22 Oct 2002 15:4:14 +0100 X-Originating-Ip: 193.95.3.132 Subject: [manet] Basic routing protocol of ad hoc networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format... ------------=_1035291854-21766-0 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi,=0D I want to know what are the basic routing protocols used in ad hoc networks.=0D thanks. ____________________________________________________________________ - http://www.WebMailSPro.com - >>=20 VOTRE service d'email sans pub avec VOTRE nom de domaine ------------=_1035291854-21766-0 Content-Type: text/html Content-Disposition: inline Content-Transfer-Encoding: 7bit 
Hi,
I want to know what are the basic routing protocols used in ad hoc
networks.
thanks.

____________________________________________________________________
- http://www.WebMailSPro.com - >> 
VOTRE service d'email sans pub avec VOTRE nom de domaine
------------=_1035291854-21766-0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 09:05:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15234 for ; Tue, 22 Oct 2002 09:05:38 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MD5qv12085; Tue, 22 Oct 2002 09:05:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MD4Sv12040 for ; Tue, 22 Oct 2002 09:04:28 -0400 Received: from webmails.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA15082 for ; Tue, 22 Oct 2002 09:02:00 -0400 (EDT) Received: (qmail 22011 invoked by uid 511); 22 Oct 2002 13:04:15 -0000 Message-ID: <20021022130415.22010.qmail@webmails.com> Content-Type: multipart/alternative; boundary="----------=_1035291854-21766-0" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.411 (Entity 5.404) From: "moez gadri" To: manet@ietf.org Organization: WebMailS - http://www.webmails.com Date: Tue, 22 Oct 2002 15:4:14 +0100 X-Originating-Ip: 193.95.3.132 Subject: [manet] Basic routing protocol of ad hoc networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format... ------------=_1035291854-21766-0 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi,=0D I want to know what are the basic routing protocols used in ad hoc networks.=0D thanks. ____________________________________________________________________ - http://www.WebMailSPro.com - >>=20 VOTRE service d'email sans pub avec VOTRE nom de domaine ------------=_1035291854-21766-0 Content-Type: text/html Content-Disposition: inline Content-Transfer-Encoding: 7bit 
Hi,
I want to know what are the basic routing protocols used in ad hoc
networks.
thanks.

____________________________________________________________________
- http://www.WebMailSPro.com - >> 
VOTRE service d'email sans pub avec VOTRE nom de domaine
------------=_1035291854-21766-0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 09:21:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15964 for ; Tue, 22 Oct 2002 09:21:47 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MDLev13288; Tue, 22 Oct 2002 09:21:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MDJEv13125 for ; Tue, 22 Oct 2002 09:19:14 -0400 Received: from zaz.kom.auc.dk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15722 for ; Tue, 22 Oct 2002 09:16:55 -0400 (EDT) Received: from winglab.kom.auc.dk ([192.168.110.83] helo=Emetin) by zaz.kom.auc.dk with smtp (Exim 2.05 #3) id 183yvl-0004qJ-00; Tue, 22 Oct 2002 15:18:45 +0200 Message-ID: <001901c279cd$68ef6050$1709a8c0@Emetin> From: "Efrayim Metin" To: "moez gadri" , References: <20021022130415.22010.qmail@webmails.com> Subject: Re: [manet] Basic routing protocol of ad hoc networks Date: Tue, 22 Oct 2002 15:17:45 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01C279DE.2C5C9200" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0016_01C279DE.2C5C9200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Check http://www.google.com and type in Ad-hoc routing Protocols. ----- Original Message -----=20 From: moez gadri=20 To: manet@ietf.org=20 Sent: Tuesday, October 22, 2002 4:00 PM Subject: [manet] Basic routing protocol of ad hoc networks Hi, I want to know what are the basic routing protocols used in ad hoc networks. thanks. ____________________________________________________________________ - http://www.WebMailSPro.com - >>=20 VOTRE service d'email sans pub avec VOTRE nom de domaine ------=_NextPart_000_0016_01C279DE.2C5C9200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Check http://www.google.com and type in = Ad-hoc=20 routing Protocols.
----- Original Message -----
From:=20 moez=20 gadri
Sent: Tuesday, October 22, 2002 = 4:00=20 PM
Subject: [manet] Basic routing = protocol=20 of ad hoc networks

Hi,
I want to know what are the basic routing protocols used in ad hoc
networks.
thanks.

____________________________________________________________________
- http://www.WebMailSPro.com =
- >>=20
VOTRE service d'email sans pub avec VOTRE nom de =
domaine
------=_NextPart_000_0016_01C279DE.2C5C9200-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 09:25:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16078 for ; Tue, 22 Oct 2002 09:25:36 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9MDRO713599 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 09:27:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MDROv13596 for ; Tue, 22 Oct 2002 09:27:24 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16067 for ; Tue, 22 Oct 2002 09:25:05 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MDLev13288; Tue, 22 Oct 2002 09:21:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MDJEv13125 for ; Tue, 22 Oct 2002 09:19:14 -0400 Received: from zaz.kom.auc.dk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15722 for ; Tue, 22 Oct 2002 09:16:55 -0400 (EDT) Received: from winglab.kom.auc.dk ([192.168.110.83] helo=Emetin) by zaz.kom.auc.dk with smtp (Exim 2.05 #3) id 183yvl-0004qJ-00; Tue, 22 Oct 2002 15:18:45 +0200 Message-ID: <001901c279cd$68ef6050$1709a8c0@Emetin> From: "Efrayim Metin" To: "moez gadri" , References: <20021022130415.22010.qmail@webmails.com> Subject: Re: [manet] Basic routing protocol of ad hoc networks Date: Tue, 22 Oct 2002 15:17:45 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01C279DE.2C5C9200" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0016_01C279DE.2C5C9200 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Check http://www.google.com and type in Ad-hoc routing Protocols. ----- Original Message -----=20 From: moez gadri=20 To: manet@ietf.org=20 Sent: Tuesday, October 22, 2002 4:00 PM Subject: [manet] Basic routing protocol of ad hoc networks Hi, I want to know what are the basic routing protocols used in ad hoc networks. thanks. ____________________________________________________________________ - http://www.WebMailSPro.com - >>=20 VOTRE service d'email sans pub avec VOTRE nom de domaine ------=_NextPart_000_0016_01C279DE.2C5C9200 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Check http://www.google.com and type in = Ad-hoc=20 routing Protocols.
----- Original Message -----
From:=20 moez=20 gadri
Sent: Tuesday, October 22, 2002 = 4:00=20 PM
Subject: [manet] Basic routing = protocol=20 of ad hoc networks

Hi,
I want to know what are the basic routing protocols used in ad hoc
networks.
thanks.

____________________________________________________________________
- http://www.WebMailSPro.com =
- >>=20
VOTRE service d'email sans pub avec VOTRE nom de =
domaine
------=_NextPart_000_0016_01C279DE.2C5C9200-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 11:45:45 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22977 for ; Tue, 22 Oct 2002 11:45:45 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MFZbv20502; Tue, 22 Oct 2002 11:35:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MFXSv20391 for ; Tue, 22 Oct 2002 11:33:28 -0400 Received: from liman.rutgers.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22213 for ; Tue, 22 Oct 2002 11:31:07 -0400 (EDT) Received: from liman1 (sachin@liman1 [128.6.110.14]) by liman.rutgers.edu (8.12.2/8.12.2) with ESMTP id g9MFXNxe007875; Tue, 22 Oct 2002 11:33:23 -0400 (EDT) Date: Tue, 22 Oct 2002 11:33:23 -0400 (EDT) From: Sachin Ganu X-Sender: sachin@liman1 To: moez gadri cc: manet@ietf.org Subject: Re: [manet] Basic routing protocol of ad hoc networks In-Reply-To: <20021022130415.22010.qmail@webmails.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , HI Moez, The routing protocols in ad-hoc networks fall under the following categories 1) Proactive protocols OLSR, DSDV etc 2) Reactive protocols E.g Dynamic Source Routing, AODV There are some versions that do power aware routing, or location aware routing.. You may want to look at an useful presentation/tutorial on various routing mechanisms by Dr. Vaidya at http://www.crhc.uiuc.edu/~nhv/presentations.html Thanks Sachin On Tue, 22 Oct 2002, moez gadri wrote: > Hi, > I want to know what are the basic routing protocols used in ad hoc > networks. > thanks. > > ____________________________________________________________________ > - http://www.WebMailSPro.com - >> > VOTRE service d'email sans pub avec VOTRE nom de domaine > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 11:48:35 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23090 for ; Tue, 22 Oct 2002 11:48:35 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9MFoPH21678 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 11:50:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MFoPv21675 for ; Tue, 22 Oct 2002 11:50:25 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23068 for ; Tue, 22 Oct 2002 11:48:04 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MFZbv20502; Tue, 22 Oct 2002 11:35:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MFXSv20391 for ; Tue, 22 Oct 2002 11:33:28 -0400 Received: from liman.rutgers.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22213 for ; Tue, 22 Oct 2002 11:31:07 -0400 (EDT) Received: from liman1 (sachin@liman1 [128.6.110.14]) by liman.rutgers.edu (8.12.2/8.12.2) with ESMTP id g9MFXNxe007875; Tue, 22 Oct 2002 11:33:23 -0400 (EDT) Date: Tue, 22 Oct 2002 11:33:23 -0400 (EDT) From: Sachin Ganu X-Sender: sachin@liman1 To: moez gadri cc: manet@ietf.org Subject: Re: [manet] Basic routing protocol of ad hoc networks In-Reply-To: <20021022130415.22010.qmail@webmails.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , HI Moez, The routing protocols in ad-hoc networks fall under the following categories 1) Proactive protocols OLSR, DSDV etc 2) Reactive protocols E.g Dynamic Source Routing, AODV There are some versions that do power aware routing, or location aware routing.. You may want to look at an useful presentation/tutorial on various routing mechanisms by Dr. Vaidya at http://www.crhc.uiuc.edu/~nhv/presentations.html Thanks Sachin On Tue, 22 Oct 2002, moez gadri wrote: > Hi, > I want to know what are the basic routing protocols used in ad hoc > networks. > thanks. > > ____________________________________________________________________ > - http://www.WebMailSPro.com - >> > VOTRE service d'email sans pub avec VOTRE nom de domaine > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 13:13:05 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26668 for ; Tue, 22 Oct 2002 13:13:05 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MHCHv26617; Tue, 22 Oct 2002 13:12:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MHAhv26571 for ; Tue, 22 Oct 2002 13:10:43 -0400 Received: from meshpdc.meshnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26505 for ; Tue, 22 Oct 2002 13:08:23 -0400 (EDT) Received: from neumillersimul (neumiller-simul.meshnetworks.com [172.16.1.171]) by meshpdc.meshnetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VLMJLCM3; Tue, 22 Oct 2002 13:10:37 -0400 Message-ID: <000701c279ed$f08fc840$ab0110ac@meshnetworks.com> Reply-To: "Phil Neumiller" From: "Phil Neumiller" To: "Phil Neumiller" , , Subject: RE: [manet] ipv4 address and network address translation Date: Tue, 22 Oct 2002 13:10:36 -0400 Organization: MeshNetworks, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Abdul, There are the following drafts: draft-royer-manet-globalv4-00.txt draft-wakikawa-manet-globalv6-00.txt Which I have commented on w/respect to addressing and mobile IP on this list (i.e. the thread is in the archives). I have yet to get back to Charlie, on his last response (which I must apologize for). I guess I would like to see these drafts talk up the MIP / MANET interaction a bit more than they do, and precisely which changes (and how) need to be made to accomodate RFC 1256. I have not had time to articulate these changes myself. In general, I think MIP addresses could be used for unicast routing in MANETs and allow for a smooth transition from ad hoc to ad hoc with infrastructure modes. The whole issue of agent/router/ (default gateway) discovery vs SeaMoby CAR needs some attention rather quickly I think. I see SeaMoby going one way, and MIP another. How manet could/should fit into this remains foggy (at least to me). The question involves support of multi-cast, TTL treatment (limited manet flooding), and handling of security associations for starters. Hopefully, I can get back to this subject soon. More specifically, yes you would typically use DHCP to obtain topologically correct addresses in a globally connected MANET when you were using MIP, however, that does NOT mean you need to use those addresses for MANET routing! I am advocating using the MIP unicast home addresses for MANET routing, thus allowing a smooth transition in an out of "Connected MANET" or NEMO/MONET modes and allowing global reachability when it is available. This seems to offer the most flexibility to me in practical MANET but does NOT allow for any sort of address aggregation in the MANET. Thanks, Phil -----Original Message----- From: A A [mailto:saeen47@hotmail.com] Sent: Saturday, October 19, 2002 7:35 PM To: pneumiller@meshnetworks.com; manet@ietf.org Subject: RE: [manet] ipv4 address and network address translation Hi Phil, Is there any RFC/Document stating how mobile IPv4 static home addresses are assigned. My understanding is that for assigning topological correct address to nodes in adhoc network you have to go through a DHCP server. Which might be one or more hops away. There might be several issues involved in the process. The prominent one i see is routing using MAC address till the node gets an IP address i.e. a node is trying to get to DHCP server. This offcourse raise concerns about security. Is there any other method to get IPv4 address for a mobile node. Thanks, Abdul -- Phillip D. Neumiller (pneumiller@meshnetworks.com) My PGP key can be imported from the following URL: http://pgpkeys.mit.edu BTW: It is undecidable whether an arithmetical formula is true! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 13:22:19 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27066 for ; Tue, 22 Oct 2002 13:22:19 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9MHO8727053 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 13:24:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MHO8v27050 for ; Tue, 22 Oct 2002 13:24:08 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27054 for ; Tue, 22 Oct 2002 13:21:48 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MHCHv26617; Tue, 22 Oct 2002 13:12:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MHAhv26571 for ; Tue, 22 Oct 2002 13:10:43 -0400 Received: from meshpdc.meshnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26505 for ; Tue, 22 Oct 2002 13:08:23 -0400 (EDT) Received: from neumillersimul (neumiller-simul.meshnetworks.com [172.16.1.171]) by meshpdc.meshnetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id VLMJLCM3; Tue, 22 Oct 2002 13:10:37 -0400 Message-ID: <000701c279ed$f08fc840$ab0110ac@meshnetworks.com> Reply-To: "Phil Neumiller" From: "Phil Neumiller" To: "Phil Neumiller" , , Subject: RE: [manet] ipv4 address and network address translation Date: Tue, 22 Oct 2002 13:10:36 -0400 Organization: MeshNetworks, Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Abdul, There are the following drafts: draft-royer-manet-globalv4-00.txt draft-wakikawa-manet-globalv6-00.txt Which I have commented on w/respect to addressing and mobile IP on this list (i.e. the thread is in the archives). I have yet to get back to Charlie, on his last response (which I must apologize for). I guess I would like to see these drafts talk up the MIP / MANET interaction a bit more than they do, and precisely which changes (and how) need to be made to accomodate RFC 1256. I have not had time to articulate these changes myself. In general, I think MIP addresses could be used for unicast routing in MANETs and allow for a smooth transition from ad hoc to ad hoc with infrastructure modes. The whole issue of agent/router/ (default gateway) discovery vs SeaMoby CAR needs some attention rather quickly I think. I see SeaMoby going one way, and MIP another. How manet could/should fit into this remains foggy (at least to me). The question involves support of multi-cast, TTL treatment (limited manet flooding), and handling of security associations for starters. Hopefully, I can get back to this subject soon. More specifically, yes you would typically use DHCP to obtain topologically correct addresses in a globally connected MANET when you were using MIP, however, that does NOT mean you need to use those addresses for MANET routing! I am advocating using the MIP unicast home addresses for MANET routing, thus allowing a smooth transition in an out of "Connected MANET" or NEMO/MONET modes and allowing global reachability when it is available. This seems to offer the most flexibility to me in practical MANET but does NOT allow for any sort of address aggregation in the MANET. Thanks, Phil -----Original Message----- From: A A [mailto:saeen47@hotmail.com] Sent: Saturday, October 19, 2002 7:35 PM To: pneumiller@meshnetworks.com; manet@ietf.org Subject: RE: [manet] ipv4 address and network address translation Hi Phil, Is there any RFC/Document stating how mobile IPv4 static home addresses are assigned. My understanding is that for assigning topological correct address to nodes in adhoc network you have to go through a DHCP server. Which might be one or more hops away. There might be several issues involved in the process. The prominent one i see is routing using MAC address till the node gets an IP address i.e. a node is trying to get to DHCP server. This offcourse raise concerns about security. Is there any other method to get IPv4 address for a mobile node. Thanks, Abdul -- Phillip D. Neumiller (pneumiller@meshnetworks.com) My PGP key can be imported from the following URL: http://pgpkeys.mit.edu BTW: It is undecidable whether an arithmetical formula is true! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 14:30:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29425 for ; Tue, 22 Oct 2002 14:30:07 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9MIVvE30350 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 14:31:57 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MIVvv30347 for ; Tue, 22 Oct 2002 14:31:57 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29402 for ; Tue, 22 Oct 2002 14:29:36 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MIUHv30295; Tue, 22 Oct 2002 14:30:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MISxv30225 for ; Tue, 22 Oct 2002 14:28:59 -0400 Received: from mailwest.unispherenetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29316 for ; Tue, 22 Oct 2002 14:26:38 -0400 (EDT) Received: by uniwest1.unispherenetworks.com with Internet Mail Service (5.5.2653.19) id ; Tue, 22 Oct 2002 14:28:47 -0400 Message-ID: <49FF5C6DDBD8D311BBBD009027DE980C03FC3048@uniwest1.unispherenetworks.com> From: "Syed, Jeelani" To: "'Sachin Ganu'" , moez gadri Cc: manet@ietf.org Subject: RE: [manet] Basic routing protocol of ad hoc networks Date: Tue, 22 Oct 2002 14:28:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Among these protocols what are mostly adopted in industry? Regards -jeelani.sm -----Original Message----- From: Sachin Ganu [mailto:sachin@liman.rutgers.edu] Sent: Tuesday, October 22, 2002 11:33 AM To: moez gadri Cc: manet@ietf.org Subject: Re: [manet] Basic routing protocol of ad hoc networks HI Moez, The routing protocols in ad-hoc networks fall under the following categories 1) Proactive protocols OLSR, DSDV etc 2) Reactive protocols E.g Dynamic Source Routing, AODV There are some versions that do power aware routing, or location aware routing.. You may want to look at an useful presentation/tutorial on various routing mechanisms by Dr. Vaidya at http://www.crhc.uiuc.edu/~nhv/presentations.html Thanks Sachin On Tue, 22 Oct 2002, moez gadri wrote: > Hi, > I want to know what are the basic routing protocols used in ad hoc > networks. > thanks. > > ____________________________________________________________________ > - http://www.WebMailSPro.com - >> > VOTRE service d'email sans pub avec VOTRE nom de domaine > > _______________________________________________ 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-admin@ietf.org Tue Oct 22 14:30:09 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29441 for ; Tue, 22 Oct 2002 14:30:09 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MIUHv30295; Tue, 22 Oct 2002 14:30:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MISxv30225 for ; Tue, 22 Oct 2002 14:28:59 -0400 Received: from mailwest.unispherenetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29316 for ; Tue, 22 Oct 2002 14:26:38 -0400 (EDT) Received: by uniwest1.unispherenetworks.com with Internet Mail Service (5.5.2653.19) id ; Tue, 22 Oct 2002 14:28:47 -0400 Message-ID: <49FF5C6DDBD8D311BBBD009027DE980C03FC3048@uniwest1.unispherenetworks.com> From: "Syed, Jeelani" To: "'Sachin Ganu'" , moez gadri Cc: manet@ietf.org Subject: RE: [manet] Basic routing protocol of ad hoc networks Date: Tue, 22 Oct 2002 14:28:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Among these protocols what are mostly adopted in industry? Regards -jeelani.sm -----Original Message----- From: Sachin Ganu [mailto:sachin@liman.rutgers.edu] Sent: Tuesday, October 22, 2002 11:33 AM To: moez gadri Cc: manet@ietf.org Subject: Re: [manet] Basic routing protocol of ad hoc networks HI Moez, The routing protocols in ad-hoc networks fall under the following categories 1) Proactive protocols OLSR, DSDV etc 2) Reactive protocols E.g Dynamic Source Routing, AODV There are some versions that do power aware routing, or location aware routing.. You may want to look at an useful presentation/tutorial on various routing mechanisms by Dr. Vaidya at http://www.crhc.uiuc.edu/~nhv/presentations.html Thanks Sachin On Tue, 22 Oct 2002, moez gadri wrote: > Hi, > I want to know what are the basic routing protocols used in ad hoc > networks. > thanks. > > ____________________________________________________________________ > - http://www.WebMailSPro.com - >> > VOTRE service d'email sans pub avec VOTRE nom de domaine > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 17:03:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04460 for ; Tue, 22 Oct 2002 17:03:34 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9ML5Qs06312 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 17:05:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ML5Qv06309 for ; Tue, 22 Oct 2002 17:05:26 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04438 for ; Tue, 22 Oct 2002 17:03:03 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ML40v06238; Tue, 22 Oct 2002 17:04:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ML1mv06169 for ; Tue, 22 Oct 2002 17:01:48 -0400 Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04349 for ; Tue, 22 Oct 2002 16:59:25 -0400 (EDT) From: haas@ece.cornell.edu Received: from verdi.ece.cornell.edu (verdi.ece.cornell.edu [128.84.210.27]) by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id g9ML1e505091; Tue, 22 Oct 2002 17:01:40 -0400 Date: Tue, 22 Oct 2002 17:01:26 -0400 (EDT) To: Sachin Ganu cc: moez gadri , manet@ietf.org Subject: Re: [manet] Basic routing protocol of ad hoc networks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , And then, of course, are also *hybrid* routing protcols, such as Fisheye State Routing (FSR), Zone Routing Protocol (ZRP), Zone-Based Hierarchical link State (ZHLS), etc. Zygmunt. ==-=-==== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Prof. Zygmunt J. Haas http://people.ece.cornell.edu/haas Wireless Networks Laboratory http://wnl.ece.cornell.edu School of Electrical Engineering Cornell University tel: +1-607-255-3454 323 Frank Rhodes Hall fax: +1-607-255-9072 Ithaca, NY 14853 e-mail: haas@ece.cornell.edu U.S.A WNL web page: http://wnl.ece.cornell.edu ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- On Tue, 22 Oct 2002, Sachin Ganu wrote: > > HI Moez, > > The routing protocols in ad-hoc networks fall under the following > categories > > 1) Proactive protocols > OLSR, DSDV etc > > 2) Reactive protocols > > E.g Dynamic Source Routing, AODV > > There are some versions that do power aware routing, or location aware > routing.. > > You may want to look at an useful presentation/tutorial on various routing > mechanisms by Dr. Vaidya at > > http://www.crhc.uiuc.edu/~nhv/presentations.html > > > Thanks > Sachin > > > On Tue, 22 Oct 2002, moez gadri wrote: > > > Hi, > > I want to know what are the basic routing protocols used in ad hoc > > networks. > > thanks. > > > > ____________________________________________________________________ > > - http://www.WebMailSPro.com - >> > > VOTRE service d'email sans pub avec VOTRE nom de domaine > > > > > > _______________________________________________ > 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-admin@ietf.org Tue Oct 22 17:03:54 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04492 for ; Tue, 22 Oct 2002 17:03:54 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ML40v06238; Tue, 22 Oct 2002 17:04:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ML1mv06169 for ; Tue, 22 Oct 2002 17:01:48 -0400 Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04349 for ; Tue, 22 Oct 2002 16:59:25 -0400 (EDT) From: haas@ece.cornell.edu Received: from verdi.ece.cornell.edu (verdi.ece.cornell.edu [128.84.210.27]) by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id g9ML1e505091; Tue, 22 Oct 2002 17:01:40 -0400 Date: Tue, 22 Oct 2002 17:01:26 -0400 (EDT) To: Sachin Ganu cc: moez gadri , manet@ietf.org Subject: Re: [manet] Basic routing protocol of ad hoc networks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , And then, of course, are also *hybrid* routing protcols, such as Fisheye State Routing (FSR), Zone Routing Protocol (ZRP), Zone-Based Hierarchical link State (ZHLS), etc. Zygmunt. ==-=-==== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Prof. Zygmunt J. Haas http://people.ece.cornell.edu/haas Wireless Networks Laboratory http://wnl.ece.cornell.edu School of Electrical Engineering Cornell University tel: +1-607-255-3454 323 Frank Rhodes Hall fax: +1-607-255-9072 Ithaca, NY 14853 e-mail: haas@ece.cornell.edu U.S.A WNL web page: http://wnl.ece.cornell.edu ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- On Tue, 22 Oct 2002, Sachin Ganu wrote: > > HI Moez, > > The routing protocols in ad-hoc networks fall under the following > categories > > 1) Proactive protocols > OLSR, DSDV etc > > 2) Reactive protocols > > E.g Dynamic Source Routing, AODV > > There are some versions that do power aware routing, or location aware > routing.. > > You may want to look at an useful presentation/tutorial on various routing > mechanisms by Dr. Vaidya at > > http://www.crhc.uiuc.edu/~nhv/presentations.html > > > Thanks > Sachin > > > On Tue, 22 Oct 2002, moez gadri wrote: > > > Hi, > > I want to know what are the basic routing protocols used in ad hoc > > networks. > > thanks. > > > > ____________________________________________________________________ > > - http://www.WebMailSPro.com - >> > > VOTRE service d'email sans pub avec VOTRE nom de domaine > > > > > > _______________________________________________ > 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-admin@ietf.org Tue Oct 22 19:35:59 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07538 for ; Tue, 22 Oct 2002 19:35:59 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MNZtv12631; Tue, 22 Oct 2002 19:35:55 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MNXwv12588 for ; Tue, 22 Oct 2002 19:33:58 -0400 Received: from engr.UVic.CA (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07466 for ; Tue, 22 Oct 2002 19:31:34 -0400 (EDT) Received: from ece.uvic.ca (muller.ece [142.104.115.126]) by engr.UVic.CA (8.11.1/8.11.1-Engr.UVic.CA-L) with ESMTP id g9MNXhr24458 for ; Tue, 22 Oct 2002 16:33:43 -0700 (PDT) Message-ID: <3DB5E0A4.42488729@ece.uvic.ca> Date: Tue, 22 Oct 2002 16:35:01 -0700 From: Caner Budakoglu Organization: University of Victoria, Dept. of Electrical &Computer Eng. X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Mailing List about Security? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear Colleagues; I am currently investigating security issues in Mobile Ad-Hoc Networks. Do you know any mailing list in which MANET Security issues are mainly discussed? Thank you for your help. Take Care Caner _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 19:38:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07680 for ; Tue, 22 Oct 2002 19:38:53 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9MNejV13341 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 19:40:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MNejv13338 for ; Tue, 22 Oct 2002 19:40:45 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07650 for ; Tue, 22 Oct 2002 19:38:22 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MNZtv12631; Tue, 22 Oct 2002 19:35:55 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MNXwv12588 for ; Tue, 22 Oct 2002 19:33:58 -0400 Received: from engr.UVic.CA (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07466 for ; Tue, 22 Oct 2002 19:31:34 -0400 (EDT) Received: from ece.uvic.ca (muller.ece [142.104.115.126]) by engr.UVic.CA (8.11.1/8.11.1-Engr.UVic.CA-L) with ESMTP id g9MNXhr24458 for ; Tue, 22 Oct 2002 16:33:43 -0700 (PDT) Message-ID: <3DB5E0A4.42488729@ece.uvic.ca> Date: Tue, 22 Oct 2002 16:35:01 -0700 From: Caner Budakoglu Organization: University of Victoria, Dept. of Electrical &Computer Eng. X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Mailing List about Security? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear Colleagues; I am currently investigating security issues in Mobile Ad-Hoc Networks. Do you know any mailing list in which MANET Security issues are mainly discussed? Thank you for your help. Take Care Caner _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 20:25:03 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08865 for ; Tue, 22 Oct 2002 20:25:03 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N0Iev14979; Tue, 22 Oct 2002 20:18:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N0H3v14933 for ; Tue, 22 Oct 2002 20:17:03 -0400 Received: from smtp.covadmail.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08539 for ; Tue, 22 Oct 2002 20:14:39 -0400 (EDT) Received: (covad.net 11815 invoked from network); 23 Oct 2002 00:16:55 -0000 Received: from h-64-105-208-34.mclnva23.covad.net (HELO amd2100) (64.105.208.34) by sun-qmail09 with SMTP; 23 Oct 2002 00:16:55 -0000 Reply-To: From: "Herbert Rubens" To: "'Caner Budakoglu'" , Subject: RE: [manet] Mailing List about Security? Date: Tue, 22 Oct 2002 20:16:45 -0400 Organization: Center for Networking and Distributed Systems Message-ID: <000201c27a29$7c7f98e0$cf01010a@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.1106 Importance: Normal In-Reply-To: <3DB5E0A4.42488729@ece.uvic.ca> Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit This page should get you started. It contains a fairly comprehensive listing of papers regarding security issues in ad hoc networks. http://www.ccs.neu.edu/home/zhufeng/security_manet.html Regards, Herb -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Caner Budakoglu Sent: Tuesday, October 22, 2002 7:35 PM To: manet@ietf.org Subject: [manet] Mailing List about Security? Dear Colleagues; I am currently investigating security issues in Mobile Ad-Hoc Networks. Do you know any mailing list in which MANET Security issues are mainly discussed? Thank you for your help. Take Care Caner _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 20:27:45 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08943 for ; Tue, 22 Oct 2002 20:27:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9N0Tcn15405 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 20:29:38 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N0Tbv15402 for ; Tue, 22 Oct 2002 20:29:37 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08935 for ; Tue, 22 Oct 2002 20:27:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N0Iev14979; Tue, 22 Oct 2002 20:18:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N0H3v14933 for ; Tue, 22 Oct 2002 20:17:03 -0400 Received: from smtp.covadmail.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA08539 for ; Tue, 22 Oct 2002 20:14:39 -0400 (EDT) Received: (covad.net 11815 invoked from network); 23 Oct 2002 00:16:55 -0000 Received: from h-64-105-208-34.mclnva23.covad.net (HELO amd2100) (64.105.208.34) by sun-qmail09 with SMTP; 23 Oct 2002 00:16:55 -0000 Reply-To: From: "Herbert Rubens" To: "'Caner Budakoglu'" , Subject: RE: [manet] Mailing List about Security? Date: Tue, 22 Oct 2002 20:16:45 -0400 Organization: Center for Networking and Distributed Systems Message-ID: <000201c27a29$7c7f98e0$cf01010a@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.1106 Importance: Normal In-Reply-To: <3DB5E0A4.42488729@ece.uvic.ca> Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit This page should get you started. It contains a fairly comprehensive listing of papers regarding security issues in ad hoc networks. http://www.ccs.neu.edu/home/zhufeng/security_manet.html Regards, Herb -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Caner Budakoglu Sent: Tuesday, October 22, 2002 7:35 PM To: manet@ietf.org Subject: [manet] Mailing List about Security? Dear Colleagues; I am currently investigating security issues in Mobile Ad-Hoc Networks. Do you know any mailing list in which MANET Security issues are mainly discussed? Thank you for your help. Take Care Caner _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 21:14:05 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10332 for ; Tue, 22 Oct 2002 21:14:05 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9N1FxL17955 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 21:15:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N1Fxv17952 for ; Tue, 22 Oct 2002 21:15:59 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10319 for ; Tue, 22 Oct 2002 21:13:34 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N1Euv17893; Tue, 22 Oct 2002 21:14:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N1C7v17781 for ; Tue, 22 Oct 2002 21:12:07 -0400 Received: from engr.UVic.CA (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10149 for ; Tue, 22 Oct 2002 21:09:42 -0400 (EDT) Received: from ece.uvic.ca (muller.ece [142.104.115.126]) by engr.UVic.CA (8.11.1/8.11.1-Engr.UVic.CA-L) with ESMTP id g9N1Bor04083; Tue, 22 Oct 2002 18:11:50 -0700 (PDT) Message-ID: <3DB5F7A3.661F98BB@ece.uvic.ca> Date: Tue, 22 Oct 2002 18:13:07 -0700 From: Caner Budakoglu Organization: University of Victoria, Dept. of Electrical &Computer Eng. X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: herb@cnds.jhu.edu CC: manet@ietf.org Subject: Re: [manet] Mailing List about Security? References: <000201c27a29$7c7f98e0$cf01010a@amd2100> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Herbert, Thank you for your response.I am really appreciated.But I am not looking for resources for papers, books etc...Iam just wondering whether there is any mailing list about MANET Security or not? Best Regards, Caner Herbert Rubens wrote: > > This page should get you started. It contains a fairly comprehensive > listing of papers regarding security issues in ad hoc networks. > > http://www.ccs.neu.edu/home/zhufeng/security_manet.html > > Regards, > Herb > > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of > Caner Budakoglu > Sent: Tuesday, October 22, 2002 7:35 PM > To: manet@ietf.org > Subject: [manet] Mailing List about Security? > > Dear Colleagues; > > I am currently investigating security issues in Mobile Ad-Hoc Networks. > Do you know any mailing list in which MANET Security issues are mainly > discussed? > > Thank you for your help. > Take Care > Caner > _______________________________________________ > 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 -- --------------------------------- Caner Budakoglu Graduate Student University of Victoria Dept. of Electrical&Computer Engr. Room B350, Engineering Labratory Wing P.O. Box 3055 STN CSC Victoria,B.C. V8W 3P6 Canada Phone:+ 1 250 721 8773 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 21:14:10 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10345 for ; Tue, 22 Oct 2002 21:14:10 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N1Euv17893; Tue, 22 Oct 2002 21:14:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N1C7v17781 for ; Tue, 22 Oct 2002 21:12:07 -0400 Received: from engr.UVic.CA (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10149 for ; Tue, 22 Oct 2002 21:09:42 -0400 (EDT) Received: from ece.uvic.ca (muller.ece [142.104.115.126]) by engr.UVic.CA (8.11.1/8.11.1-Engr.UVic.CA-L) with ESMTP id g9N1Bor04083; Tue, 22 Oct 2002 18:11:50 -0700 (PDT) Message-ID: <3DB5F7A3.661F98BB@ece.uvic.ca> Date: Tue, 22 Oct 2002 18:13:07 -0700 From: Caner Budakoglu Organization: University of Victoria, Dept. of Electrical &Computer Eng. X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: zh, zh-CN, en MIME-Version: 1.0 To: herb@cnds.jhu.edu CC: manet@ietf.org Subject: Re: [manet] Mailing List about Security? References: <000201c27a29$7c7f98e0$cf01010a@amd2100> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Herbert, Thank you for your response.I am really appreciated.But I am not looking for resources for papers, books etc...Iam just wondering whether there is any mailing list about MANET Security or not? Best Regards, Caner Herbert Rubens wrote: > > This page should get you started. It contains a fairly comprehensive > listing of papers regarding security issues in ad hoc networks. > > http://www.ccs.neu.edu/home/zhufeng/security_manet.html > > Regards, > Herb > > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of > Caner Budakoglu > Sent: Tuesday, October 22, 2002 7:35 PM > To: manet@ietf.org > Subject: [manet] Mailing List about Security? > > Dear Colleagues; > > I am currently investigating security issues in Mobile Ad-Hoc Networks. > Do you know any mailing list in which MANET Security issues are mainly > discussed? > > Thank you for your help. > Take Care > Caner > _______________________________________________ > 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 -- --------------------------------- Caner Budakoglu Graduate Student University of Victoria Dept. of Electrical&Computer Engr. Room B350, Engineering Labratory Wing P.O. Box 3055 STN CSC Victoria,B.C. V8W 3P6 Canada Phone:+ 1 250 721 8773 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 22:17:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12239 for ; Tue, 22 Oct 2002 22:17:53 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2I1v21226; Tue, 22 Oct 2002 22:18:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2Gvv21183 for ; Tue, 22 Oct 2002 22:16:57 -0400 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12180 for ; Tue, 22 Oct 2002 22:14:30 -0400 (EDT) Message-Id: <200210230214.WAA12180@ietf.org> Received: (eyou send program); Wed, 23 Oct 2002 10:14:41 +0800 Received: from 166.111.67.254 by mails.tsinghua.edu.cn with HTTP; Wed, 23 Oct 2002 10:14:41 +0800 X-WebMAIL-MUA: [166.111.67.254] From: "3fad9ca8ab7fa48557" To: manet@ietf.org Date: Wed, 23 Oct 2002 10:14:41 +0800 Reply-To: "3fad9ca8ab7fa48557" Content-Type: text/plain Subject: [manet] queue length of mobile node Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , hi, Thanks for G.Lu's explaination. But have another question. When I ran AODV over ns2b8, i found that queue length between LL and MAC always remains to zero. Meanwhile,the queue length of route agent itself is not the case, even maybe high. What's the problem? Thanks for your help in advance. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 22:18:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12267 for ; Tue, 22 Oct 2002 22:18:47 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2J8v21275; Tue, 22 Oct 2002 22:19:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2H9v21193 for ; Tue, 22 Oct 2002 22:17:09 -0400 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12183 for ; Tue, 22 Oct 2002 22:14:43 -0400 (EDT) Message-Id: <200210230214.WAA12183@ietf.org> Received: (eyou send program); Wed, 23 Oct 2002 10:14:48 +0800 Received: from 166.111.67.254 by mails.tsinghua.edu.cn with HTTP; Wed, 23 Oct 2002 10:14:48 +0800 X-WebMAIL-MUA: [166.111.67.254] From: "3fad9ca8ab7fa48557" To: manet@ietf.org Date: Wed, 23 Oct 2002 10:14:48 +0800 Reply-To: "3fad9ca8ab7fa48557" Content-Type: text/plain Subject: [manet] queue length of mobile node Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , hi, Thanks for G.Lu's explaination. But have another question. When I ran AODV over ns2b8, i found that queue length between LL and MAC always remains to zero. Meanwhile,the queue length of route agent itself is not the case, even maybe high. What's the problem? Thanks for your help in advance. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 22:22:29 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12403 for ; Tue, 22 Oct 2002 22:22:29 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9N2ONJ21646 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 22:24:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2ONv21643 for ; Tue, 22 Oct 2002 22:24:23 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12392 for ; Tue, 22 Oct 2002 22:21:58 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2J8v21275; Tue, 22 Oct 2002 22:19:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2H9v21193 for ; Tue, 22 Oct 2002 22:17:09 -0400 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12183 for ; Tue, 22 Oct 2002 22:14:43 -0400 (EDT) Message-Id: <200210230214.WAA12183@ietf.org> Received: (eyou send program); Wed, 23 Oct 2002 10:14:48 +0800 Received: from 166.111.67.254 by mails.tsinghua.edu.cn with HTTP; Wed, 23 Oct 2002 10:14:48 +0800 X-WebMAIL-MUA: [166.111.67.254] From: "3fad9ca8ab7fa48557" To: manet@ietf.org Date: Wed, 23 Oct 2002 10:14:48 +0800 Reply-To: "3fad9ca8ab7fa48557" Content-Type: text/plain Subject: [manet] queue length of mobile node Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , hi, Thanks for G.Lu's explaination. But have another question. When I ran AODV over ns2b8, i found that queue length between LL and MAC always remains to zero. Meanwhile,the queue length of route agent itself is not the case, even maybe high. What's the problem? Thanks for your help in advance. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 22:24:16 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12463 for ; Tue, 22 Oct 2002 22:24:16 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9N2QB921726 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 22:26:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2QBv21723 for ; Tue, 22 Oct 2002 22:26:11 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12451 for ; Tue, 22 Oct 2002 22:23:45 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2I1v21226; Tue, 22 Oct 2002 22:18:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2Gvv21183 for ; Tue, 22 Oct 2002 22:16:57 -0400 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12180 for ; Tue, 22 Oct 2002 22:14:30 -0400 (EDT) Message-Id: <200210230214.WAA12180@ietf.org> Received: (eyou send program); Wed, 23 Oct 2002 10:14:41 +0800 Received: from 166.111.67.254 by mails.tsinghua.edu.cn with HTTP; Wed, 23 Oct 2002 10:14:41 +0800 X-WebMAIL-MUA: [166.111.67.254] From: "3fad9ca8ab7fa48557" To: manet@ietf.org Date: Wed, 23 Oct 2002 10:14:41 +0800 Reply-To: "3fad9ca8ab7fa48557" Content-Type: text/plain Subject: [manet] queue length of mobile node Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , hi, Thanks for G.Lu's explaination. But have another question. When I ran AODV over ns2b8, i found that queue length between LL and MAC always remains to zero. Meanwhile,the queue length of route agent itself is not the case, even maybe high. What's the problem? Thanks for your help in advance. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 22:30:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12633 for ; Tue, 22 Oct 2002 22:30:57 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9N2WqS21931 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 22:32:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2Wqv21928 for ; Tue, 22 Oct 2002 22:32:52 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12570 for ; Tue, 22 Oct 2002 22:30:26 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2VGv21873; Tue, 22 Oct 2002 22:31:16 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2ULv21830 for ; Tue, 22 Oct 2002 22:30:21 -0400 Received: from mail.eecis.udel.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA12493 for ; Tue, 22 Oct 2002 22:27:55 -0400 (EDT) Received: by mail.eecis.udel.edu id aa06054; 22 Oct 2002 19:51 EDT Received: from frink.ece.udel.edu by mail.eecis.udel.edu id aa29413; 22 Oct 2002 18:52 EDT Date: Tue, 22 Oct 2002 18:51:32 -0400 (EDT) From: Liangping Ma To: manet@ietf.org MMDF-Warning: Parse error in original version of preceding line at mail.eecis.udel.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Mathematical analysis of TCP over mobile IP networks? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, Does anyone know if there is already any work on mathematical analysis of TCP over mobile IP networks? As far as I know, there are some simulation-based studies about TCP over mobile IP networks. But I am looking for deterministic/stochastic modeling of TCP in mobile IP networks, which have one hop of wireless link as compared to the conventional IP networks. Thanks! Liangping Ma ----------------------- ECE Dept. University of Delaware Newark, Delaware, 19716 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 22:31:01 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12652 for ; Tue, 22 Oct 2002 22:31:01 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2VGv21873; Tue, 22 Oct 2002 22:31:16 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N2ULv21830 for ; Tue, 22 Oct 2002 22:30:21 -0400 Received: from mail.eecis.udel.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA12493 for ; Tue, 22 Oct 2002 22:27:55 -0400 (EDT) Received: by mail.eecis.udel.edu id aa06054; 22 Oct 2002 19:51 EDT Received: from frink.ece.udel.edu by mail.eecis.udel.edu id aa29413; 22 Oct 2002 18:52 EDT Date: Tue, 22 Oct 2002 18:51:32 -0400 (EDT) From: Liangping Ma To: manet@ietf.org MMDF-Warning: Parse error in original version of preceding line at mail.eecis.udel.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Mathematical analysis of TCP over mobile IP networks? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, Does anyone know if there is already any work on mathematical analysis of TCP over mobile IP networks? As far as I know, there are some simulation-based studies about TCP over mobile IP networks. But I am looking for deterministic/stochastic modeling of TCP in mobile IP networks, which have one hop of wireless link as compared to the conventional IP networks. Thanks! Liangping Ma ----------------------- ECE Dept. University of Delaware Newark, Delaware, 19716 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 22 23:39:50 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13869 for ; Tue, 22 Oct 2002 23:39:50 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9N3fjo25573 for manet-archive@odin.ietf.org; Tue, 22 Oct 2002 23:41:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N3fjv25570 for ; Tue, 22 Oct 2002 23:41:45 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13865 for ; Tue, 22 Oct 2002 23:39:19 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N3e0v25471; Tue, 22 Oct 2002 23:40:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N3cKv25431 for ; Tue, 22 Oct 2002 23:38:20 -0400 Received: from smtp-send.myrealbox.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13853 for ; Tue, 22 Oct 2002 23:35:53 -0400 (EDT) Received: from nppham [130.220.36.156] by myrealbox.com with NetMail ModWeb Module; Wed, 23 Oct 2002 13:08:12 +0950 Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? From: "Peter Pham" To: lma@mail.eecis.udel.edu CC: manet@ietf.org Date: Wed, 23 Oct 2002 13:08:12 +0950 X-Mailer: NetMail ModWeb Module X-Sender: nppham MIME-Version: 1.0 Message-ID: <1035344292.1bcec140nppham@myrealbox.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9N3cKv25432 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi , if you found one, please let me know as well. I am doing some work on TCP now and trying to prove that my method is better than conventional TCP mathematically. Thanks Peter Pham -----Original Message----- From: Liangping Ma To: manet@ietf.org Date: Tue, 22 Oct 2002 18:51:32 -0400 (EDT) Subject: [manet] Mathematical analysis of TCP over mobile IP networks? Hello, Does anyone know if there is already any work on mathematical analysis of TCP over mobile IP networks? As far as I know, there are some simulation-based studies about TCP over mobile IP networks. But I am looking for deterministic/stochastic modeling of TCP in mobile IP networks, which have one hop of wireless link as compared to the conventional IP networks. Thanks! Liangping Ma ----------------------- ECE Dept. University of Delaware Newark, Delaware, 19716 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet Peter Phuc Pham University of South Australia Institute for Telecommunication Research Phone: 61-883023869 Email: ppham@spri.levels.unisa.edu.au WWW: www.itr.unisa.edu.au/~ppham _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 22 23:39:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13882 for ; Tue, 22 Oct 2002 23:39:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N3e0v25471; Tue, 22 Oct 2002 23:40:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9N3cKv25431 for ; Tue, 22 Oct 2002 23:38:20 -0400 Received: from smtp-send.myrealbox.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13853 for ; Tue, 22 Oct 2002 23:35:53 -0400 (EDT) Received: from nppham [130.220.36.156] by myrealbox.com with NetMail ModWeb Module; Wed, 23 Oct 2002 13:08:12 +0950 Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? From: "Peter Pham" To: lma@mail.eecis.udel.edu CC: manet@ietf.org Date: Wed, 23 Oct 2002 13:08:12 +0950 X-Mailer: NetMail ModWeb Module X-Sender: nppham MIME-Version: 1.0 Message-ID: <1035344292.1bcec140nppham@myrealbox.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9N3cKv25432 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi , if you found one, please let me know as well. I am doing some work on TCP now and trying to prove that my method is better than conventional TCP mathematically. Thanks Peter Pham -----Original Message----- From: Liangping Ma To: manet@ietf.org Date: Tue, 22 Oct 2002 18:51:32 -0400 (EDT) Subject: [manet] Mathematical analysis of TCP over mobile IP networks? Hello, Does anyone know if there is already any work on mathematical analysis of TCP over mobile IP networks? As far as I know, there are some simulation-based studies about TCP over mobile IP networks. But I am looking for deterministic/stochastic modeling of TCP in mobile IP networks, which have one hop of wireless link as compared to the conventional IP networks. Thanks! Liangping Ma ----------------------- ECE Dept. University of Delaware Newark, Delaware, 19716 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet Peter Phuc Pham University of South Australia Institute for Telecommunication Research Phone: 61-883023869 Email: ppham@spri.levels.unisa.edu.au WWW: www.itr.unisa.edu.au/~ppham _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 23 08:30:02 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15652 for ; Wed, 23 Oct 2002 08:30:02 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9NCVn025982 for manet-archive@odin.ietf.org; Wed, 23 Oct 2002 08:31:49 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NCVnv25979 for ; Wed, 23 Oct 2002 08:31:49 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15646 for ; Wed, 23 Oct 2002 08:29:31 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NCT0v25837; Wed, 23 Oct 2002 08:29:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NCMrv25615 for ; Wed, 23 Oct 2002 08:22:53 -0400 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15283 for ; Wed, 23 Oct 2002 08:20:32 -0400 (EDT) Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id UAA10955 for ; Wed, 23 Oct 2002 20:22:42 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500b.comp.nus.edu.sg via csmap id 998; Wed, 23 Oct 2002 20:10:21 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id UAA20672 for ; Wed, 23 Oct 2002 20:22:41 +0800 (GMT-8) Date: Wed, 23 Oct 2002 20:22:41 +0800 (GMT-8) From: Sourabh Sharma To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Cisco Aironet Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, I am trying to get an ad-hoc testbed on laptops using Cisco Aironet 350 series wireless cards. However, using the aironet client utility, when I change the status of the card to "ad-hoc" under System Parameters as well as Home Netowrking, The aironet cleint shows "Your radio is diabled" Any idea how to get the card working in Ad-hoc mode?? Thanks. Sourabh. Cir, NUS. -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 23 08:30:22 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15675 for ; Wed, 23 Oct 2002 08:30:21 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NCT0v25837; Wed, 23 Oct 2002 08:29:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NCMrv25615 for ; Wed, 23 Oct 2002 08:22:53 -0400 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15283 for ; Wed, 23 Oct 2002 08:20:32 -0400 (EDT) Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id UAA10955 for ; Wed, 23 Oct 2002 20:22:42 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500b.comp.nus.edu.sg via csmap id 998; Wed, 23 Oct 2002 20:10:21 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id UAA20672 for ; Wed, 23 Oct 2002 20:22:41 +0800 (GMT-8) Date: Wed, 23 Oct 2002 20:22:41 +0800 (GMT-8) From: Sourabh Sharma To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Cisco Aironet Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, I am trying to get an ad-hoc testbed on laptops using Cisco Aironet 350 series wireless cards. However, using the aironet client utility, when I change the status of the card to "ad-hoc" under System Parameters as well as Home Netowrking, The aironet cleint shows "Your radio is diabled" Any idea how to get the card working in Ad-hoc mode?? Thanks. Sourabh. Cir, NUS. -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 23 10:06:16 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00252 for ; Wed, 23 Oct 2002 10:06:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NDuDv30884; Wed, 23 Oct 2002 09:56:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NDnHv30695 for ; Wed, 23 Oct 2002 09:49:17 -0400 Received: from mail.eecis.udel.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26567 for ; Wed, 23 Oct 2002 09:46:57 -0400 (EDT) Received: from frink.ece.udel.edu by mail.eecis.udel.edu id aa28326; 23 Oct 2002 09:48 EDT Date: Wed, 23 Oct 2002 09:48:21 -0400 (EDT) From: Liangping Ma To: Pete Sholander cc: manet@ietf.org MMDF-Warning: Parse error in original version of preceding line at mail.eecis.udel.edu Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Pete, I think you referred to the paper "Modeling TCP throughput: a simple model and its empirical validation" by J. Padhye, V. Firoiu, D. Towsley and J. Kurose in ACM SIGCOMM'98. This paper is easy to be found on the web. In fact, I am looking for something a little bit different from this paper if it exists at all. In the paper above, the analysis is for wired networks, where packet loss is due to network congestion. But in the _mobile_ IP networks, there is one hop of wireless link in a TCP conneciton. The packet loss is affected also by the signal-to-noise ratio and other factors in the wireless environment. I think these factors should be incorporated to the so called TCP formula. Sincerely yours, Liangping Ma On Wed, 23 Oct 2002, Pete Sholander wrote: > Look at SIGCOMM '98. There was a oft-cited paper on a mathematical > analysis of TCP throughput versus RTT and packet-loss rate. (I can't > recall the author's name.) You could then do a lit-search to see who > subsequently referenced that work. > > >>> Liangping Ma 10/22/02 06:51PM >>> > Hello, > > Does anyone know if there is already any work on mathematical > analysis of TCP over mobile IP networks? As far as I know, there > are some simulation-based studies about TCP over mobile IP networks. > But I am looking for deterministic/stochastic modeling of TCP in > mobile IP networks, which have one hop of wireless link as compared > to the conventional IP networks. > > Thanks! > > Liangping Ma > > ----------------------- > > ECE Dept. > University of Delaware > Newark, Delaware, 19716 > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 23 10:13:35 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01760 for ; Wed, 23 Oct 2002 10:13:35 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9NEFOQ32090 for manet-archive@odin.ietf.org; Wed, 23 Oct 2002 10:15:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NEFOv32087 for ; Wed, 23 Oct 2002 10:15:24 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01651 for ; Wed, 23 Oct 2002 10:13:04 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NDuDv30884; Wed, 23 Oct 2002 09:56:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NDnHv30695 for ; Wed, 23 Oct 2002 09:49:17 -0400 Received: from mail.eecis.udel.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26567 for ; Wed, 23 Oct 2002 09:46:57 -0400 (EDT) Received: from frink.ece.udel.edu by mail.eecis.udel.edu id aa28326; 23 Oct 2002 09:48 EDT Date: Wed, 23 Oct 2002 09:48:21 -0400 (EDT) From: Liangping Ma To: Pete Sholander cc: manet@ietf.org MMDF-Warning: Parse error in original version of preceding line at mail.eecis.udel.edu Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Pete, I think you referred to the paper "Modeling TCP throughput: a simple model and its empirical validation" by J. Padhye, V. Firoiu, D. Towsley and J. Kurose in ACM SIGCOMM'98. This paper is easy to be found on the web. In fact, I am looking for something a little bit different from this paper if it exists at all. In the paper above, the analysis is for wired networks, where packet loss is due to network congestion. But in the _mobile_ IP networks, there is one hop of wireless link in a TCP conneciton. The packet loss is affected also by the signal-to-noise ratio and other factors in the wireless environment. I think these factors should be incorporated to the so called TCP formula. Sincerely yours, Liangping Ma On Wed, 23 Oct 2002, Pete Sholander wrote: > Look at SIGCOMM '98. There was a oft-cited paper on a mathematical > analysis of TCP throughput versus RTT and packet-loss rate. (I can't > recall the author's name.) You could then do a lit-search to see who > subsequently referenced that work. > > >>> Liangping Ma 10/22/02 06:51PM >>> > Hello, > > Does anyone know if there is already any work on mathematical > analysis of TCP over mobile IP networks? As far as I know, there > are some simulation-based studies about TCP over mobile IP networks. > But I am looking for deterministic/stochastic modeling of TCP in > mobile IP networks, which have one hop of wireless link as compared > to the conventional IP networks. > > Thanks! > > Liangping Ma > > ----------------------- > > ECE Dept. > University of Delaware > Newark, Delaware, 19716 > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 23 10:14:37 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01956 for ; Wed, 23 Oct 2002 10:14:37 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9NEGQT32137 for manet-archive@odin.ietf.org; Wed, 23 Oct 2002 10:16:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NEGQv32134 for ; Wed, 23 Oct 2002 10:16:26 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01868 for ; Wed, 23 Oct 2002 10:14:06 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NEFPv32104; Wed, 23 Oct 2002 10:15:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NE9Ev31934 for ; Wed, 23 Oct 2002 10:09:14 -0400 Received: from Eng.Auburn.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00388 for ; Wed, 23 Oct 2002 10:06:54 -0400 (EDT) Received: from chadia.eng.auburn.edu (IDENT:31366@chadia.eng.auburn.edu [131.204.19.11]) by Eng.Auburn.EDU (8.11.6/8.11.6) with ESMTP id g9NE9A609214; Wed, 23 Oct 2002 09:09:10 -0500 (CDT) Received: from localhost (sbiaz@localhost) by chadia.eng.auburn.edu (8.10.2+Sun/8.6.4) with ESMTP id g9NE98w06392; Wed, 23 Oct 2002 09:09:08 -0500 (CDT) X-Authentication-Warning: chadia.eng.auburn.edu: sbiaz owned process doing -bs Date: Wed, 23 Oct 2002 09:09:08 -0500 (CDT) From: Saad Biaz To: Liangping Ma cc: Pete Sholander , Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , > In fact, I am looking for something a little bit different from this > paper if it exists at all. In the paper above, the analysis is for wired > networks, where packet loss is due to network congestion. But in the > _mobile_ IP networks, there is one hop of wireless link in a TCP > conneciton. The packet loss is affected also by the signal-to-noise ratio > and other factors in the wireless environment. I think these factors > should be incorporated to the so called TCP formula. Padhye et al. make only one assumption regarding the losses: losses are independent from round to round. I bet that transmission losses on the wireless hop are independent from round to round. This assumption is more valid with wireless losses that with congestion losses. Check Padhye's model with a wireless hop to see whether the model is that "bad" before rejecting it. Just an advice. Saad. ---------------------------------------------------------------------- Saad Biaz, Ph.D., Assistant Prof. Voice: (334) 844 6307 114 Dunstan Hall Auburn University Fax : (334) 844 6329 Auburn, AL 36849-5347, USA http://www.eng.auburn.edu/~sbiaz ---------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 23 10:14:39 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01974 for ; Wed, 23 Oct 2002 10:14:39 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NEFPv32104; Wed, 23 Oct 2002 10:15:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NE9Ev31934 for ; Wed, 23 Oct 2002 10:09:14 -0400 Received: from Eng.Auburn.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00388 for ; Wed, 23 Oct 2002 10:06:54 -0400 (EDT) Received: from chadia.eng.auburn.edu (IDENT:31366@chadia.eng.auburn.edu [131.204.19.11]) by Eng.Auburn.EDU (8.11.6/8.11.6) with ESMTP id g9NE9A609214; Wed, 23 Oct 2002 09:09:10 -0500 (CDT) Received: from localhost (sbiaz@localhost) by chadia.eng.auburn.edu (8.10.2+Sun/8.6.4) with ESMTP id g9NE98w06392; Wed, 23 Oct 2002 09:09:08 -0500 (CDT) X-Authentication-Warning: chadia.eng.auburn.edu: sbiaz owned process doing -bs Date: Wed, 23 Oct 2002 09:09:08 -0500 (CDT) From: Saad Biaz To: Liangping Ma cc: Pete Sholander , Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , > In fact, I am looking for something a little bit different from this > paper if it exists at all. In the paper above, the analysis is for wired > networks, where packet loss is due to network congestion. But in the > _mobile_ IP networks, there is one hop of wireless link in a TCP > conneciton. The packet loss is affected also by the signal-to-noise ratio > and other factors in the wireless environment. I think these factors > should be incorporated to the so called TCP formula. Padhye et al. make only one assumption regarding the losses: losses are independent from round to round. I bet that transmission losses on the wireless hop are independent from round to round. This assumption is more valid with wireless losses that with congestion losses. Check Padhye's model with a wireless hop to see whether the model is that "bad" before rejecting it. Just an advice. Saad. ---------------------------------------------------------------------- Saad Biaz, Ph.D., Assistant Prof. Voice: (334) 844 6307 114 Dunstan Hall Auburn University Fax : (334) 844 6329 Auburn, AL 36849-5347, USA http://www.eng.auburn.edu/~sbiaz ---------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 23 10:28:12 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04628 for ; Wed, 23 Oct 2002 10:28:11 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9NEU1432684 for manet-archive@odin.ietf.org; Wed, 23 Oct 2002 10:30:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NEU1v32681 for ; Wed, 23 Oct 2002 10:30:01 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04521 for ; Wed, 23 Oct 2002 10:27:40 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NESNv32606; Wed, 23 Oct 2002 10:28:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NEN8v32448 for ; Wed, 23 Oct 2002 10:23:09 -0400 Received: from liman.rutgers.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03186 for ; Wed, 23 Oct 2002 10:20:48 -0400 (EDT) Received: from liman1 (sachin@liman1 [128.6.110.14]) by liman.rutgers.edu (8.12.2/8.12.2) with ESMTP id g9NEMOXc015318; Wed, 23 Oct 2002 10:22:26 -0400 (EDT) Date: Wed, 23 Oct 2002 10:22:24 -0400 (EDT) From: Sachin Ganu X-Sender: sachin@liman1 To: Sourabh Sharma cc: manet@ietf.org Subject: Re: [manet] Cisco Aironet In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Sourabh, If you are working with Linux, you could try the wireless tool, iwconfig to see if that works. The command is iwconfig mode ad-hoc Hope that helps, Sachin On Wed, 23 Oct 2002, Sourabh Sharma wrote: > > Hello, > I am trying to get an ad-hoc testbed on laptops > using Cisco Aironet 350 series wireless cards. > However, using the aironet client utility, > when I change the status of the card to "ad-hoc" > under System Parameters as well as Home Netowrking, > The aironet cleint shows "Your radio is diabled" > Any idea how to get the card working in Ad-hoc mode?? > > Thanks. > Sourabh. > Cir, NUS. > -------------------------------------------------- > There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > _______________________________________________ > 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-admin@ietf.org Wed Oct 23 10:28:15 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04649 for ; Wed, 23 Oct 2002 10:28:15 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NESNv32606; Wed, 23 Oct 2002 10:28:23 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NEN8v32448 for ; Wed, 23 Oct 2002 10:23:09 -0400 Received: from liman.rutgers.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03186 for ; Wed, 23 Oct 2002 10:20:48 -0400 (EDT) Received: from liman1 (sachin@liman1 [128.6.110.14]) by liman.rutgers.edu (8.12.2/8.12.2) with ESMTP id g9NEMOXc015318; Wed, 23 Oct 2002 10:22:26 -0400 (EDT) Date: Wed, 23 Oct 2002 10:22:24 -0400 (EDT) From: Sachin Ganu X-Sender: sachin@liman1 To: Sourabh Sharma cc: manet@ietf.org Subject: Re: [manet] Cisco Aironet In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Sourabh, If you are working with Linux, you could try the wireless tool, iwconfig to see if that works. The command is iwconfig mode ad-hoc Hope that helps, Sachin On Wed, 23 Oct 2002, Sourabh Sharma wrote: > > Hello, > I am trying to get an ad-hoc testbed on laptops > using Cisco Aironet 350 series wireless cards. > However, using the aironet client utility, > when I change the status of the card to "ad-hoc" > under System Parameters as well as Home Netowrking, > The aironet cleint shows "Your radio is diabled" > Any idea how to get the card working in Ad-hoc mode?? > > Thanks. > Sourabh. > Cir, NUS. > -------------------------------------------------- > There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 23 11:03:56 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11110 for ; Wed, 23 Oct 2002 11:03:56 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9NF5k102426 for manet-archive@odin.ietf.org; Wed, 23 Oct 2002 11:05:46 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NF5jv02423 for ; Wed, 23 Oct 2002 11:05:45 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10997 for ; Wed, 23 Oct 2002 11:03:25 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NF0dv02051; Wed, 23 Oct 2002 11:00:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NEumv01888 for ; Wed, 23 Oct 2002 10:56:48 -0400 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09500 for ; Wed, 23 Oct 2002 10:54:27 -0400 (EDT) Received: from colorado.edu (ecee189-245-dhcp.Colorado.EDU [128.138.189.245]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9NEu9B09491; Wed, 23 Oct 2002 08:56:09 -0600 (MDT) Message-ID: <3DB6B888.1090304@colorado.edu> Date: Wed, 23 Oct 2002 08:56:08 -0600 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sourabh Sharma , manet@ietf.org Subject: Re: [manet] Cisco Aironet References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, If you are using Linux, you set the cards in ad hoc mode using iwconfig mode ad-hoc for Windows, use the ACU and try using the Enterprise configuration. It has worked for me so far :) Shweta Sourabh Sharma wrote: > Hello, > I am trying to get an ad-hoc testbed on laptops > using Cisco Aironet 350 series wireless cards. > However, using the aironet client utility, > when I change the status of the card to "ad-hoc" > under System Parameters as well as Home Netowrking, > The aironet cleint shows "Your radio is diabled" > Any idea how to get the card working in Ad-hoc mode?? > > Thanks. > Sourabh. > Cir, NUS. > -------------------------------------------------- > There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > _______________________________________________ > 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-admin@ietf.org Wed Oct 23 11:04:01 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA11145 for ; Wed, 23 Oct 2002 11:04:01 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NF0dv02051; Wed, 23 Oct 2002 11:00:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NEumv01888 for ; Wed, 23 Oct 2002 10:56:48 -0400 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09500 for ; Wed, 23 Oct 2002 10:54:27 -0400 (EDT) Received: from colorado.edu (ecee189-245-dhcp.Colorado.EDU [128.138.189.245]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9NEu9B09491; Wed, 23 Oct 2002 08:56:09 -0600 (MDT) Message-ID: <3DB6B888.1090304@colorado.edu> Date: Wed, 23 Oct 2002 08:56:08 -0600 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sourabh Sharma , manet@ietf.org Subject: Re: [manet] Cisco Aironet References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, If you are using Linux, you set the cards in ad hoc mode using iwconfig mode ad-hoc for Windows, use the ACU and try using the Enterprise configuration. It has worked for me so far :) Shweta Sourabh Sharma wrote: > Hello, > I am trying to get an ad-hoc testbed on laptops > using Cisco Aironet 350 series wireless cards. > However, using the aironet client utility, > when I change the status of the card to "ad-hoc" > under System Parameters as well as Home Netowrking, > The aironet cleint shows "Your radio is diabled" > Any idea how to get the card working in Ad-hoc mode?? > > Thanks. > Sourabh. > Cir, NUS. > -------------------------------------------------- > There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > _______________________________________________ > 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-admin@ietf.org Wed Oct 23 13:44:05 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26978 for ; Wed, 23 Oct 2002 13:44:05 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NHiBv13486; Wed, 23 Oct 2002 13:44:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MECuv16379 for ; Tue, 22 Oct 2002 10:12:56 -0400 Received: from SMTP1.ECE.NEU.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18197 for ; Tue, 22 Oct 2002 10:10:36 -0400 (EDT) Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (NUECE 1.1.4) with SMTP id g9MECq9L022123 for ; Tue, 22 Oct 2002 10:12:52 -0400 (EDT) Received: from runner.ece.neu.edu ([129.10.60.136]) by calvin.ece.neu.edu (NAVGW 2.5.2.9) with SMTP id M2002102210125118192 ; Tue, 22 Oct 2002 10:12:52 -0400 Received: from localhost (mcdonald@localhost) by runner.ece.neu.edu (8.11.6+Sun/8.9.3) with ESMTP id g9MECq812939; Tue, 22 Oct 2002 10:12:52 -0400 (EDT) X-Authentication-Warning: runner.ece.neu.edu: mcdonald owned process doing -bs Date: Tue, 22 Oct 2002 10:12:52 -0400 (EDT) From: "A. Bruce McDonald" X-X-Sender: mcdonald@runner To: Efrayim Metin cc: moez gadri , Subject: Re: [manet] Basic routing protocol of ad hoc networks In-Reply-To: <001901c279cd$68ef6050$1709a8c0@Emetin> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Efrayim; In all honesty there is no such thing as the topic remains widely contested in many dimensions. The answer in some sense depends on your precise definition of ad hoc network, which, ought to imply your expected range of operational scenarios. Enough vague narratives... At the risk of sounding like I am preaching: Routing in ad hoc networks remains a wide open topic largely because there is so much that remains (a) not well understood; and, (b) not well integrated across disciplines---ergo, the ad hoc folks need to incorporate the massive knowledge of the wireless comms folks into their (our) approaches in a rigorous manner... I suggest that you scan the literature---recent Proc from Infocom, Mobicom, MobiHoc, etc., will reveal a wide range of approaches and problems. Journals such as IEEE Trans. on Wireless, IEEE J-Sac, Wireless Networks etc., will also show the range of approaches and where we are. In short---there is no short answer in a practical sense. From a conceptual/tactical perspective there are indeed, however, some basic strategies that have been receiving a great deal of attention---these include the 'reactive or on-demand' route search approaches, 'geographic or location' based approaches (which are typically reactive but need not be), 'minimal energy' approaches, hybrid table-driven/on-demand, cluster-based approaches, 'virtual' backbone approaches, stable-path approaches etc.... These are not neccessarily mutually exclusive. Look at the literature :-) Best regards, --bruce -------------------------------------------------------- A. Bruce McDonald f:617.373.8970 Assistant Prof. v:617.373.3028 ECE Dept., 417 Dana mcdonald@ece.neu.edu 360 Huntington Ave. www.ece.neu.edu/faculty/mcdonald Northeastern University Boston, MA 02115 -------------------------------------------------------- On Tue, 22 Oct 2002, Efrayim Metin wrote: > Check http://www.google.com and type in Ad-hoc routing Protocols. > ----- Original Message ----- > From: moez gadri > To: manet@ietf.org > Sent: Tuesday, October 22, 2002 4:00 PM > Subject: [manet] Basic routing protocol of ad hoc networks > > > Hi, > I want to know what are the basic routing protocols used in ad hoc > networks. > thanks. > > ____________________________________________________________________ > - http://www.WebMailSPro.com - >> > VOTRE service d'email sans pub avec VOTRE nom de domaine > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 23 13:47:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27045 for ; Wed, 23 Oct 2002 13:47:30 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NHhsv13449; Wed, 23 Oct 2002 13:43:54 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ICo8v12704 for ; Fri, 18 Oct 2002 08:50:08 -0400 Received: from tokyo.ccrle.nec.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23655 for ; Fri, 18 Oct 2002 08:47:54 -0400 (EDT) Received: from imap.heidelberg.ccrle.nec.de (imap [192.168.102.11]) by tokyo.ccrle.nec.de (8.11.6/8.11.6) with ESMTP id g9ICo6Y45269 for ; Fri, 18 Oct 2002 14:50:06 +0200 (CEST) (envelope-from Dirk.Westhoff@ccrle.nec.de) Received: by imap.heidelberg.ccrle.nec.de (Postfix on SuSE Linux eMail Server 3.0, from userid 30) id 71FE86CFCA; Fri, 18 Oct 2002 14:50:04 +0200 (CEST) X-Accept-Language: de, en X-Priority: 3 (Normal) X-Mailer: SKYRiXgreen_3.1 NGMime_4.2.18 From: "Dirk Westhoff" MIME-Version: 1.0 To: manet@ietf.org Organization: NEC Europe Ltd. content-type: text/plain; charset="iso-8859-1" date: Fri, 18 Oct 2002 14:50:04 +0200 content-transfer-encoding: 7bit Message-Id: <20021018125004.71FE86CFCA@imap.heidelberg.ccrle.nec.de> Content-Transfer-Encoding: 7bit Subject: [manet] '1st Workshop on Security in Ad-Hoc Networks' Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear all, the URL(www.crypto.rub.de/adhocsec) for the '1st Workshop on Security in Ad-Hoc Networks' is now available..... Best regards, Dirk Westhoff -- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 23 13:50:12 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27109 for ; Wed, 23 Oct 2002 13:50:12 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9NHq4u13771 for manet-archive@odin.ietf.org; Wed, 23 Oct 2002 13:52:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NHq4v13768 for ; Wed, 23 Oct 2002 13:52:04 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27101 for ; Wed, 23 Oct 2002 13:49:41 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NHiBv13486; Wed, 23 Oct 2002 13:44:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MECuv16379 for ; Tue, 22 Oct 2002 10:12:56 -0400 Received: from SMTP1.ECE.NEU.EDU (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18197 for ; Tue, 22 Oct 2002 10:10:36 -0400 (EDT) Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (NUECE 1.1.4) with SMTP id g9MECq9L022123 for ; Tue, 22 Oct 2002 10:12:52 -0400 (EDT) Received: from runner.ece.neu.edu ([129.10.60.136]) by calvin.ece.neu.edu (NAVGW 2.5.2.9) with SMTP id M2002102210125118192 ; Tue, 22 Oct 2002 10:12:52 -0400 Received: from localhost (mcdonald@localhost) by runner.ece.neu.edu (8.11.6+Sun/8.9.3) with ESMTP id g9MECq812939; Tue, 22 Oct 2002 10:12:52 -0400 (EDT) X-Authentication-Warning: runner.ece.neu.edu: mcdonald owned process doing -bs Date: Tue, 22 Oct 2002 10:12:52 -0400 (EDT) From: "A. Bruce McDonald" X-X-Sender: mcdonald@runner To: Efrayim Metin cc: moez gadri , Subject: Re: [manet] Basic routing protocol of ad hoc networks In-Reply-To: <001901c279cd$68ef6050$1709a8c0@Emetin> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Efrayim; In all honesty there is no such thing as the topic remains widely contested in many dimensions. The answer in some sense depends on your precise definition of ad hoc network, which, ought to imply your expected range of operational scenarios. Enough vague narratives... At the risk of sounding like I am preaching: Routing in ad hoc networks remains a wide open topic largely because there is so much that remains (a) not well understood; and, (b) not well integrated across disciplines---ergo, the ad hoc folks need to incorporate the massive knowledge of the wireless comms folks into their (our) approaches in a rigorous manner... I suggest that you scan the literature---recent Proc from Infocom, Mobicom, MobiHoc, etc., will reveal a wide range of approaches and problems. Journals such as IEEE Trans. on Wireless, IEEE J-Sac, Wireless Networks etc., will also show the range of approaches and where we are. In short---there is no short answer in a practical sense. From a conceptual/tactical perspective there are indeed, however, some basic strategies that have been receiving a great deal of attention---these include the 'reactive or on-demand' route search approaches, 'geographic or location' based approaches (which are typically reactive but need not be), 'minimal energy' approaches, hybrid table-driven/on-demand, cluster-based approaches, 'virtual' backbone approaches, stable-path approaches etc.... These are not neccessarily mutually exclusive. Look at the literature :-) Best regards, --bruce -------------------------------------------------------- A. Bruce McDonald f:617.373.8970 Assistant Prof. v:617.373.3028 ECE Dept., 417 Dana mcdonald@ece.neu.edu 360 Huntington Ave. www.ece.neu.edu/faculty/mcdonald Northeastern University Boston, MA 02115 -------------------------------------------------------- On Tue, 22 Oct 2002, Efrayim Metin wrote: > Check http://www.google.com and type in Ad-hoc routing Protocols. > ----- Original Message ----- > From: moez gadri > To: manet@ietf.org > Sent: Tuesday, October 22, 2002 4:00 PM > Subject: [manet] Basic routing protocol of ad hoc networks > > > Hi, > I want to know what are the basic routing protocols used in ad hoc > networks. > thanks. > > ____________________________________________________________________ > - http://www.WebMailSPro.com - >> > VOTRE service d'email sans pub avec VOTRE nom de domaine > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 23 13:57:19 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27398 for ; Wed, 23 Oct 2002 13:57:19 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9NHxCL14059 for manet-archive@odin.ietf.org; Wed, 23 Oct 2002 13:59:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NHxCv14056 for ; Wed, 23 Oct 2002 13:59:12 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27385 for ; Wed, 23 Oct 2002 13:56:48 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NHhsv13449; Wed, 23 Oct 2002 13:43:54 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ICo8v12704 for ; Fri, 18 Oct 2002 08:50:08 -0400 Received: from tokyo.ccrle.nec.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23655 for ; Fri, 18 Oct 2002 08:47:54 -0400 (EDT) Received: from imap.heidelberg.ccrle.nec.de (imap [192.168.102.11]) by tokyo.ccrle.nec.de (8.11.6/8.11.6) with ESMTP id g9ICo6Y45269 for ; Fri, 18 Oct 2002 14:50:06 +0200 (CEST) (envelope-from Dirk.Westhoff@ccrle.nec.de) Received: by imap.heidelberg.ccrle.nec.de (Postfix on SuSE Linux eMail Server 3.0, from userid 30) id 71FE86CFCA; Fri, 18 Oct 2002 14:50:04 +0200 (CEST) X-Accept-Language: de, en X-Priority: 3 (Normal) X-Mailer: SKYRiXgreen_3.1 NGMime_4.2.18 From: "Dirk Westhoff" MIME-Version: 1.0 To: manet@ietf.org Organization: NEC Europe Ltd. content-type: text/plain; charset="iso-8859-1" date: Fri, 18 Oct 2002 14:50:04 +0200 content-transfer-encoding: 7bit Message-Id: <20021018125004.71FE86CFCA@imap.heidelberg.ccrle.nec.de> Content-Transfer-Encoding: 7bit Subject: [manet] '1st Workshop on Security in Ad-Hoc Networks' Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear all, the URL(www.crypto.rub.de/adhocsec) for the '1st Workshop on Security in Ad-Hoc Networks' is now available..... Best regards, Dirk Westhoff -- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 23 22:28:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13968 for ; Wed, 23 Oct 2002 22:28:38 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O2K8v05521; Wed, 23 Oct 2002 22:20:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O2Hfv05412 for ; Wed, 23 Oct 2002 22:17:41 -0400 Received: from sm4.163.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13737 for ; Wed, 23 Oct 2002 22:15:14 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by sm4.163.com (Postfix) with SMTP id E62B91C6E5C48 for ; Thu, 24 Oct 2002 10:16:39 +0800 (CST) Received: from RavProxy (unknown [61.187.64.26]) by 192.168.1.206 (Coremail) with SMTP id y34AAAZYtz3LfUAa.1 for ; Thu, 24 Oct 2002 10:16:39 +0800 (CST) Message-ID: <001101c27b02$e7369420$7600a8c0@zyn> From: "Zhang Yanan" To: Date: Thu, 24 Oct 2002 10:13:10 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C27B45.F480D940" 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 Subject: [manet] A question about Glomosim Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C27B45.F480D940 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SSdtIGRvaW5nIHNvbWUgc2ltdWxhdG9yIG9uIFdpbmRvd3MgdXNpbmcgR2xvbW9zaW0uIEkgbW9k aWZpZWQgdGhlICJOT0RFLVBMQUNFTUVOVCBSQU5ET00iIGluIHRoZSAiY29uZmlnLmluICIgZmls ZSwgYnV0IHRoZSBOb2RlUGxhY2VtZW50IGlzIGFsd2F5cyB0aGUgc2FtZSBlYWNoIHRpbWUuIEhv dyBjYW4gSSBkbyB0aGlzPw0K ------=_NextPart_000_000E_01C27B45.F480D940 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5JJ20gZG9pbmcgc29tZSBzaW11 bGF0b3Igb24gV2luZG93cyB1c2luZyBHbG9tb3NpbS4mbmJzcDtJIA0KbW9kaWZpZWQgdGhlICJO T0RFLVBMQUNFTUVOVCZuYnNwO1JBTkRPTSIgaW4gdGhlICJjb25maWcuaW4gIiBmaWxlLCBidXQg dGhlIA0KTm9kZVBsYWNlbWVudCBpcyBhbHdheXMgdGhlIHNhbWUgZWFjaCB0aW1lLiBIb3cgY2Fu IEkgZG8gDQp0aGlzPzwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K ------=_NextPart_000_000E_01C27B45.F480D940-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 23 22:35:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14347 for ; Wed, 23 Oct 2002 22:35:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9O2bYH06675 for manet-archive@odin.ietf.org; Wed, 23 Oct 2002 22:37:34 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O2bXv06672 for ; Wed, 23 Oct 2002 22:37:33 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14343 for ; Wed, 23 Oct 2002 22:35:07 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O2K8v05521; Wed, 23 Oct 2002 22:20:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O2Hfv05412 for ; Wed, 23 Oct 2002 22:17:41 -0400 Received: from sm4.163.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13737 for ; Wed, 23 Oct 2002 22:15:14 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by sm4.163.com (Postfix) with SMTP id E62B91C6E5C48 for ; Thu, 24 Oct 2002 10:16:39 +0800 (CST) Received: from RavProxy (unknown [61.187.64.26]) by 192.168.1.206 (Coremail) with SMTP id y34AAAZYtz3LfUAa.1 for ; Thu, 24 Oct 2002 10:16:39 +0800 (CST) Message-ID: <001101c27b02$e7369420$7600a8c0@zyn> From: "Zhang Yanan" To: Date: Thu, 24 Oct 2002 10:13:10 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C27B45.F480D940" 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 Subject: [manet] A question about Glomosim Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C27B45.F480D940 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SSdtIGRvaW5nIHNvbWUgc2ltdWxhdG9yIG9uIFdpbmRvd3MgdXNpbmcgR2xvbW9zaW0uIEkgbW9k aWZpZWQgdGhlICJOT0RFLVBMQUNFTUVOVCBSQU5ET00iIGluIHRoZSAiY29uZmlnLmluICIgZmls ZSwgYnV0IHRoZSBOb2RlUGxhY2VtZW50IGlzIGFsd2F5cyB0aGUgc2FtZSBlYWNoIHRpbWUuIEhv dyBjYW4gSSBkbyB0aGlzPw0K ------=_NextPart_000_000E_01C27B45.F480D940 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPjxGT05UIHNpemU9Mj5JJ20gZG9pbmcgc29tZSBzaW11 bGF0b3Igb24gV2luZG93cyB1c2luZyBHbG9tb3NpbS4mbmJzcDtJIA0KbW9kaWZpZWQgdGhlICJO T0RFLVBMQUNFTUVOVCZuYnNwO1JBTkRPTSIgaW4gdGhlICJjb25maWcuaW4gIiBmaWxlLCBidXQg dGhlIA0KTm9kZVBsYWNlbWVudCBpcyBhbHdheXMgdGhlIHNhbWUgZWFjaCB0aW1lLiBIb3cgY2Fu IEkgZG8gDQp0aGlzPzwvRk9OVD48L0RJVj48L0JPRFk+PC9IVE1MPg0K ------=_NextPart_000_000E_01C27B45.F480D940-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 23 23:12:55 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15125 for ; Wed, 23 Oct 2002 23:12:55 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9O3EpX08649 for manet-archive@odin.ietf.org; Wed, 23 Oct 2002 23:14:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O3Eov08645 for ; Wed, 23 Oct 2002 23:14:50 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15119 for ; Wed, 23 Oct 2002 23:12:24 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O35Tv07692; Wed, 23 Oct 2002 23:05:29 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O32Cv07538 for ; Wed, 23 Oct 2002 23:02:12 -0400 Received: from hades.snrc.uow.edu.au (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14849 for ; Wed, 23 Oct 2002 22:59:44 -0400 (EDT) Received: from there (justin@eros [130.130.10.74]) by hades.snrc.uow.edu.au (8.11.2/8.11.2) with SMTP id g9O31KB16096; Thu, 24 Oct 2002 13:01:20 +1000 (EST) Message-Id: <200210240301.g9O31KB16096@hades.snrc.uow.edu.au> Content-Type: text/plain; charset="gb2312" From: Justin Lipman Reply-To: justin@titr.uow.edu.au Organization: TITR To: Subject: Re: [manet] A question about Glomosim Date: Thu, 24 Oct 2002 13:05:40 +1000 X-Mailer: KMail [version 1.3.2] References: <001101c27b02$e7369420$7600a8c0@zyn> In-Reply-To: <001101c27b02$e7369420$7600a8c0@zyn> Cc: "Zhang Yanan" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9O32Cv07539 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Try changing the "SEED" value... regards, Justin On Thu, 24 Oct 2002 12:13, you wrote: > I'm doing some simulator on Windows using Glomosim. I modified the > "NODE-PLACEMENT RANDOM" in the "config.in " file, but the NodePlacement is > always the same each time. How can I do this? -- Telecommunications & Information Technology Research Institute University of Wollongong, Australia http://www.titr.uow.edu.au _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 23 23:12:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15139 for ; Wed, 23 Oct 2002 23:12:57 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O35Tv07692; Wed, 23 Oct 2002 23:05:29 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O32Cv07538 for ; Wed, 23 Oct 2002 23:02:12 -0400 Received: from hades.snrc.uow.edu.au (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14849 for ; Wed, 23 Oct 2002 22:59:44 -0400 (EDT) Received: from there (justin@eros [130.130.10.74]) by hades.snrc.uow.edu.au (8.11.2/8.11.2) with SMTP id g9O31KB16096; Thu, 24 Oct 2002 13:01:20 +1000 (EST) Message-Id: <200210240301.g9O31KB16096@hades.snrc.uow.edu.au> Content-Type: text/plain; charset="gb2312" From: Justin Lipman Reply-To: justin@titr.uow.edu.au Organization: TITR To: Subject: Re: [manet] A question about Glomosim Date: Thu, 24 Oct 2002 13:05:40 +1000 X-Mailer: KMail [version 1.3.2] References: <001101c27b02$e7369420$7600a8c0@zyn> In-Reply-To: <001101c27b02$e7369420$7600a8c0@zyn> Cc: "Zhang Yanan" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9O32Cv07539 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Try changing the "SEED" value... regards, Justin On Thu, 24 Oct 2002 12:13, you wrote: > I'm doing some simulator on Windows using Glomosim. I modified the > "NODE-PLACEMENT RANDOM" in the "config.in " file, but the NodePlacement is > always the same each time. How can I do this? -- Telecommunications & Information Technology Research Institute University of Wollongong, Australia http://www.titr.uow.edu.au _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 24 02:04:06 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23387 for ; Thu, 24 Oct 2002 02:04:06 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O5w7v16001; Thu, 24 Oct 2002 01:58:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O5lHv15778 for ; Thu, 24 Oct 2002 01:47:17 -0400 Received: from iisc.ernet.in (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17987 for ; Thu, 24 Oct 2002 01:44:47 -0400 (EDT) Received: from ankoff.ece.iisc.ernet.in (ankoff.ece.iisc.ernet.in [144.16.64.37]) by iisc.ernet.in (8.9.2/8.9.0) with ESMTP id LAA18402; Thu, 24 Oct 2002 11:16:52 +0530 (IST) Received: from localhost (anurag@localhost) by ankoff.ece.iisc.ernet.in (8.11.6/8.11.6) with ESMTP id g9O5l1Q06336; Thu, 24 Oct 2002 11:17:02 +0530 X-Authentication-Warning: ankoff.ece.iisc.ernet.in: anurag owned process doing -bs Date: Thu, 24 Oct 2002 11:17:01 +0530 (IST) From: "Prof.Anurag Kumar" To: Liangping Ma cc: Pete Sholander , Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Please look at the following two papers on my site http://ece.iisc.ernet.in/~anurag/ * Anurag Kumar and Jack Holtzman, ``Performance Analysis of Versions of TCP in a Local Network with a Mobile Radio Link, '' Sadhana: Indian Academy of Sciences Proceedings in Engg. Sciences, February 1998. * Anurag Kumar, ``Comparative Performance Analysis of Versions of TCP in a Local Network with a Lossy Link, '' IEEE/ACM Transactions on Networking, August 1998. There are many other papers; e.g., do a search for Chockalingam, Zorzi, Rao. best Anurag On Wed, 23 Oct 2002, Liangping Ma wrote: > Hi, Pete, > > I think you referred to the paper "Modeling TCP throughput: a simple > model and its empirical validation" by J. Padhye, V. Firoiu, D. Towsley > and J. Kurose in ACM SIGCOMM'98. This paper is easy to be found on the > web. > > In fact, I am looking for something a little bit different from this > paper if it exists at all. In the paper above, the analysis is for wired > networks, where packet loss is due to network congestion. But in the > _mobile_ IP networks, there is one hop of wireless link in a TCP > conneciton. The packet loss is affected also by the signal-to-noise ratio > and other factors in the wireless environment. I think these factors > should be incorporated to the so called TCP formula. > > > Sincerely yours, > Liangping Ma > > > On Wed, 23 Oct 2002, Pete Sholander wrote: > > > Look at SIGCOMM '98. There was a oft-cited paper on a mathematical > > analysis of TCP throughput versus RTT and packet-loss rate. (I can't > > recall the author's name.) You could then do a lit-search to see who > > subsequently referenced that work. > > > > >>> Liangping Ma 10/22/02 06:51PM >>> > > Hello, > > > > Does anyone know if there is already any work on mathematical > > analysis of TCP over mobile IP networks? As far as I know, there > > are some simulation-based studies about TCP over mobile IP networks. > > But I am looking for deterministic/stochastic modeling of TCP in > > mobile IP networks, which have one hop of wireless link as compared > > to the conventional IP networks. > > > > Thanks! > > > > Liangping Ma > > > > ----------------------- > > > > ECE Dept. > > University of Delaware > > Newark, Delaware, 19716 > > > > _______________________________________________ > > 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 > -- _______________________________________________________________________________ Anurag Kumar |e-mail: anurag@ece.iisc.ernet.in Professor |Phone: (+91)-80-360 0855 or and Associate Chairman | (+91)-80-394 2387 Dept. of Electrical Communication Engg. (ECE)|Fax: (+91)-80-360 0991 or Indian Institute of Science (IISc) | (+91)-80-360 0683 Bangalore, 560 012, INDIA |http://ece.iisc.ernet.in/~anurag ------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 02:10:10 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27462 for ; Thu, 24 Oct 2002 02:10:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9O6C8D24792 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 02:12:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O6C7v24780 for ; Thu, 24 Oct 2002 02:12:07 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27453 for ; Thu, 24 Oct 2002 02:09:38 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O5w7v16001; Thu, 24 Oct 2002 01:58:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9O5lHv15778 for ; Thu, 24 Oct 2002 01:47:17 -0400 Received: from iisc.ernet.in (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17987 for ; Thu, 24 Oct 2002 01:44:47 -0400 (EDT) Received: from ankoff.ece.iisc.ernet.in (ankoff.ece.iisc.ernet.in [144.16.64.37]) by iisc.ernet.in (8.9.2/8.9.0) with ESMTP id LAA18402; Thu, 24 Oct 2002 11:16:52 +0530 (IST) Received: from localhost (anurag@localhost) by ankoff.ece.iisc.ernet.in (8.11.6/8.11.6) with ESMTP id g9O5l1Q06336; Thu, 24 Oct 2002 11:17:02 +0530 X-Authentication-Warning: ankoff.ece.iisc.ernet.in: anurag owned process doing -bs Date: Thu, 24 Oct 2002 11:17:01 +0530 (IST) From: "Prof.Anurag Kumar" To: Liangping Ma cc: Pete Sholander , Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Please look at the following two papers on my site http://ece.iisc.ernet.in/~anurag/ * Anurag Kumar and Jack Holtzman, ``Performance Analysis of Versions of TCP in a Local Network with a Mobile Radio Link, '' Sadhana: Indian Academy of Sciences Proceedings in Engg. Sciences, February 1998. * Anurag Kumar, ``Comparative Performance Analysis of Versions of TCP in a Local Network with a Lossy Link, '' IEEE/ACM Transactions on Networking, August 1998. There are many other papers; e.g., do a search for Chockalingam, Zorzi, Rao. best Anurag On Wed, 23 Oct 2002, Liangping Ma wrote: > Hi, Pete, > > I think you referred to the paper "Modeling TCP throughput: a simple > model and its empirical validation" by J. Padhye, V. Firoiu, D. Towsley > and J. Kurose in ACM SIGCOMM'98. This paper is easy to be found on the > web. > > In fact, I am looking for something a little bit different from this > paper if it exists at all. In the paper above, the analysis is for wired > networks, where packet loss is due to network congestion. But in the > _mobile_ IP networks, there is one hop of wireless link in a TCP > conneciton. The packet loss is affected also by the signal-to-noise ratio > and other factors in the wireless environment. I think these factors > should be incorporated to the so called TCP formula. > > > Sincerely yours, > Liangping Ma > > > On Wed, 23 Oct 2002, Pete Sholander wrote: > > > Look at SIGCOMM '98. There was a oft-cited paper on a mathematical > > analysis of TCP throughput versus RTT and packet-loss rate. (I can't > > recall the author's name.) You could then do a lit-search to see who > > subsequently referenced that work. > > > > >>> Liangping Ma 10/22/02 06:51PM >>> > > Hello, > > > > Does anyone know if there is already any work on mathematical > > analysis of TCP over mobile IP networks? As far as I know, there > > are some simulation-based studies about TCP over mobile IP networks. > > But I am looking for deterministic/stochastic modeling of TCP in > > mobile IP networks, which have one hop of wireless link as compared > > to the conventional IP networks. > > > > Thanks! > > > > Liangping Ma > > > > ----------------------- > > > > ECE Dept. > > University of Delaware > > Newark, Delaware, 19716 > > > > _______________________________________________ > > 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 > -- _______________________________________________________________________________ Anurag Kumar |e-mail: anurag@ece.iisc.ernet.in Professor |Phone: (+91)-80-360 0855 or and Associate Chairman | (+91)-80-394 2387 Dept. of Electrical Communication Engg. (ECE)|Fax: (+91)-80-360 0991 or Indian Institute of Science (IISc) | (+91)-80-360 0683 Bangalore, 560 012, INDIA |http://ece.iisc.ernet.in/~anurag ------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 08:01:40 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03191 for ; Thu, 24 Oct 2002 08:01:40 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OC3Uu10805 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 08:03:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OC3Uv10802 for ; Thu, 24 Oct 2002 08:03:30 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03180 for ; Thu, 24 Oct 2002 08:01:09 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OBtav10444; Thu, 24 Oct 2002 07:55:36 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OBpNv10310 for ; Thu, 24 Oct 2002 07:51:23 -0400 Received: from mail.rz.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02856 for ; Thu, 24 Oct 2002 07:49:02 -0400 (EDT) Received: from informatik.uni-ulm.de (delphin.informatik.uni-ulm.de [134.60.70.42]) by mail.rz.uni-ulm.de (8.12.5/8.12.5) with ESMTP id g9OBpJcD006092 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Thu, 24 Oct 2002 13:51:20 +0200 (MEST) Message-ID: <3DB7DEB3.80200@informatik.uni-ulm.de> Date: Thu, 24 Oct 2002 13:51:15 +0200 From: Frank Kargl Organization: University of Ulm, Germany User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910 X-Accept-Language: de, en MIME-Version: 1.0 To: manet@ietf.org X-Enigmail-Version: 0.65.4.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] OPNET Modeler Version 9 and MANET models Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear all, I'm currently evaluation OPNET Modeler (Version 9.0.A PL2) for doing some studies about MANETs. Most of the existing modules (DSR, AODV, MobileMesh ...) rely on older versions of the Modeler to run correctly, e.g. there is a problem with the DSR module that Marc Ribet ported to 8.1.A PL2 that seems to be related to timing issues in the 802.11 module. I already had contact with Marc, but he is currently busy with other things but gave me some good ideas what to look for. Before starting any effort to adapt these modules myself, has anyone started a siminlar try before? Finished? Run into what problems? Regards ... Frank -- ----------------------------------------------------------------------- Frank Kargl Multimedia Computing, University of Ulm, Germany Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/ ----------------------------------------------------------------------- Use the SOURCE, Luke ! I feel a great disturbance in the SOURCE. But beware of the Microsoft side of the SOURCE ! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 24 08:01:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03204 for ; Thu, 24 Oct 2002 08:01:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OBtav10444; Thu, 24 Oct 2002 07:55:36 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OBpNv10310 for ; Thu, 24 Oct 2002 07:51:23 -0400 Received: from mail.rz.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02856 for ; Thu, 24 Oct 2002 07:49:02 -0400 (EDT) Received: from informatik.uni-ulm.de (delphin.informatik.uni-ulm.de [134.60.70.42]) by mail.rz.uni-ulm.de (8.12.5/8.12.5) with ESMTP id g9OBpJcD006092 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Thu, 24 Oct 2002 13:51:20 +0200 (MEST) Message-ID: <3DB7DEB3.80200@informatik.uni-ulm.de> Date: Thu, 24 Oct 2002 13:51:15 +0200 From: Frank Kargl Organization: University of Ulm, Germany User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910 X-Accept-Language: de, en MIME-Version: 1.0 To: manet@ietf.org X-Enigmail-Version: 0.65.4.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] OPNET Modeler Version 9 and MANET models Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear all, I'm currently evaluation OPNET Modeler (Version 9.0.A PL2) for doing some studies about MANETs. Most of the existing modules (DSR, AODV, MobileMesh ...) rely on older versions of the Modeler to run correctly, e.g. there is a problem with the DSR module that Marc Ribet ported to 8.1.A PL2 that seems to be related to timing issues in the 802.11 module. I already had contact with Marc, but he is currently busy with other things but gave me some good ideas what to look for. Before starting any effort to adapt these modules myself, has anyone started a siminlar try before? Finished? Run into what problems? Regards ... Frank -- ----------------------------------------------------------------------- Frank Kargl Multimedia Computing, University of Ulm, Germany Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/ ----------------------------------------------------------------------- Use the SOURCE, Luke ! I feel a great disturbance in the SOURCE. But beware of the Microsoft side of the SOURCE ! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 24 08:51:29 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04854 for ; Thu, 24 Oct 2002 08:51:29 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OCiPv13446; Thu, 24 Oct 2002 08:44:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OCdJv13267 for ; Thu, 24 Oct 2002 08:39:19 -0400 Received: from rasheen.osdp.is.tsukuba.ac.jp (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04277 for ; Thu, 24 Oct 2002 08:36:57 -0400 (EDT) Received: from John (bill.is.tsukuba.ac.jp [130.158.81.66]) by rasheen.osdp.is.tsukuba.ac.jp (8.12.6/8.12.5) with SMTP id g9OCdEDm062347 for ; Thu, 24 Oct 2002 21:39:14 +0900 (JST) (envelope-from lijie@is.tsukuba.ac.jp) Message-ID: <018901c27b59$8e24aff0$42519e82@John> From: "Jie Li" To: Date: Thu, 24 Oct 2002 21:33:28 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Subject: [manet] CFP SPCTS 2003 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I apologize if you receive multiple copies of this message. Call For Papers %%%%%%%%%%%%%%%% 2003 International Symposium on Performance Evaluation of Computer and Telecommunication Systems (SPECTS 2003) July 20-24, 2003 Montreal, Canada http://scs.org/confernc/ssimc/ssimc03/cfp/spects03.htm Submission Deadlines Submission of Papers: January 31, 2003. Notification of Acceptance - April 25, 2003 Final Camera-Ready Submission - May 23, 2003 This annual international conference is a forum for professionals involved in performance evaluation of computer and telecommunication systems. Evaluation of computer systems and networks is needed at every stage in the life cycle of the product including design, manufacturing, sales/purchase, use, upgrade, tuning, etc. The discipline of performance evaluation has progressed rapidly in the past decade, and it has now begun to approach maturity. Significant progress has been made in analytic modeling, simulation, and measurement approaches for performance evaluation of computer and telecommunication systems. Topics of interest include, but are not limited to: Networking and Telecommunication Systems - Internet Technology - Quality of Service (QoS) - DiffServ/IntServ - MPLS - TCP - World Wide Web (WWW) Technology - Networking Techniques - Unicast and Multicast Routing - Congestion Control - Switching Techniques - Teletraffic - Network Protocols - Network Management and Control - Network Capacity Planning - Network Architecture Evaluation - Service and QoS Pricing - Security and Authentication -Broadband Networks - High-Speed Networking - ATM - Optical Networks - Wireless Systems and Networks - Satellite Systems - UMTS - Mobile Networks/Computing - Ad-hoc networks - Multimedia Communications Computer Systems - Distributed Architectures - Client/Server - Distributed Systems and Agents - Parallel and Distributed Computing - Massively Parallel Systems - Cluster Computing - Grid Computing - Interconnection Networks - Computer Architectures - Microprocessors/Microcomputers - Memory Systems - High Performance I/O - Real-time Systems - Scheduling Schemes -Software - Software Performance, Evaluation and Testing - Parallel Algorithms and Languages - Hardware and Software Monitors - High-Performance Computing - Workload and Traffic Characterization - Scientific Computing Algorithms - Reconfigurable Computing - Electronic Commerce Tools, Methodologies and Applications - Parallel and Distributed Simulation - Verification and Validation - Performance Tools and Methodologies - Neural Networks and Fuzzy Logic Applications to High Performance Computing/Networking - Performance Optimization - Queueing Systems and Networks - Scalability Studies - Integrated Modeling and Measurement - On-Line Performance Adaptation and Tuning - Process Algebra-Based Models - Performance Bounds - Integrated Design and Performance - New Performance Models - Mathematical Aspects of Performance - New Performability Schemes and Models - Case Studies General Chair Mohammad S. Obaidat Dept. of Computer Science, Monmouth University W. Long Branch, NJ 07764, USA Tel +1-732-571-4482 Fax +1-732-263-5202 E-mail: obaidat@monmouth.edu Senior Program Chair Franco Davoli DIST-University of Genoa Via Opera Pia 13, I-16145 Genoa, Italy Tel +39-010-353-2732 Fax +39-010-353-2154 E-Mail: franco@dist.unige.it Program Co-Chairs Ibrahim Onyuksel Dept. of Computer Sciences, N. Illinois Univ., USA E-mail: onyuksel@cs.niu.edu Erina Ferro ISTI, Institute of National Research Council (C.N.R.) C.N.R. Pisa Research Area, Building B, Room 73 Via G. Moruzzi, 1 56124 Pisa, Italy E-mail: erina.ferro@cnuce.cnr.it Vice Program Chair and Tutorial Chair Raffaele Bolla DIST-University of Genoa Via Opera Pia 13, I-16145 Genoa, Italy E-mail: lelus@dist.unige.it Vice Program Chair and Web Master Imad Mahgoub Department of Computer Science and Engineering Florida Atlantic University Boca Raton, FL 33431 E-mail: imad@cse.fau.edu Industrial Track and Special Sessions Chair J. Fox, Motorola Inc., UK E-mail: fox.ijcs@btinternet.com Technical Program Committee Ian Akyildiz, Georgia Tech., USA Mohammed Atiquzzaman, University of Oklahoma, USA Louis G. Birta, University of Ottawa, Canada Abdullah Abonamah, Zayed University, UAE Noureddine Boudriga, University of Tunis, Tunisia Hasan Cam, Arizona State University, USA Andrew Campbell, Columbia University, USA Nedo Celandroni, ISTI-CNR, Italy Haitham Cruickshank, University of Surrey, UK Hassan B. Diab, American University of Beirut, Lebanon Gabor Fodor, Ericsson Radio Systems, Sweden Geoffrey Fox, Indiana University, USA Luigi Fratta, Politecnico di Milano, Italy Aura Ganz, University of Massachusetts, USA Erol Gelenbe, University of Central Florida, USA Mario Gerla, UCLA, USA Sami Habib, Kuwait University, Kuwait Omar Hammami, ENSTA, France Jarmo Harju, Tampere University of Technology, Finland Herman Hughes, Michigan State University, USA Andrzej Jajszczyk, University of Mining and Metallurgy, Poland Abbas Jamalipour, University of Sydney, Australia Ingemar Kaj, Uppsala University, Sweden Krishna Kant, Intel, USA Helen Karatza, Aristotle University of Thessalonica, Greece Demetrios Kazakos, University of Louisiana, USA Ulrich Killat, Tech Univ. of Hamburg, Germany Tag Gon Kim, KAIST, Korea Kevin Kwiat, Air Force Research Laboratory, USA Veronica Lagrange M. Reis, Compaq Computers Corp., USA Axel Lehmann, Universit$BgU(B der Bundeswehr M$B!&(Bchen, Germany Daniel C. Lee, USC, USA Mike T. Liu, Ohio State University, USA Erich Lutz, DLR, Germany Sam Makki, Queensland University of Technology, Australia Krzysztof Malinowski, Warsaw Technical University, Poland Mario Marchese, University of Genoa, Italy Jose L. Marzo, Universitat de Girona, Spain Xiannong Meng, Bucknell University, USA Hussein Mouftah, Queen's University, Canada Mohamed Ould-Khaoua, University of Glasgow, UK Sergio Palazzo, Universit$B!&(Bdi Catania, Italy Georgios I. Papadimitriou, Aristotle University, Greece Achille Pattavina, Politecnico di Milano, Italy Krzysztof Pawlikowski, University of Canterbury, New Zealand Gregory D. Peterson, University of Tennessee Steven Pink, University of Arizona, USA George Polyzos, AUEB, Greece Ramon Puigjaner, Universitat de les Illes Balears, Spain Kaliappa Ravindran, CUNY, USA Gian Paolo Rossi, Universit$B!&(Bdi Milano, Italy Izhak Rubin, UCLA, USA Vicente Santonja, Technical University of Valencia, Spain Donald Schilling, CUNY, USA Jens B. Schmitt, TU Darmstadt, Germany Harald Skinnemoen, Nera, Norway Tatsuya Suda, UCI, USA Iwao Toda, Fujutsu Laboratories Ltd., Japan Phuoc Tran-Gia, University of Wuerzburg, Germany Kishor Trivedi, Duke University, USA Kenneth S. Vastola, Rensselaer Polytechnic Institute, USA Manuel Villen-Altamirano, Telefonica, Spain Bernd E. Wolfinger, Hamburg University, Germany Michele Zorzi, Universit$B!&(Bdi Ferrara, Italy Publicity Chair: Yuguang (Michael) Fang, University of Florida, USA Publicity Committee: Vice Chair: Jie Li, University of Tsukuba, Japan Chiara Petrioli, Universita` di Roma "La Sapienza", Italy Chuck Song, Chinese Academy of Sciences, China Ahmed Nuseirat, Al-Isra University, Jordan International Liaisons B. Sadoun, Al-Balqa' Applied University, Jordan Bsadoun@go.com.jo M. Sawan, Montreal Poly, Canada Sawan@vlsi.polymtl.ca N. Tchamov, Tampere Univ. of Technology, Finland Nikolay@cs.tut.fi Paper Submission Submit your complete papers electronically to: http://scs.proceedingscentral.com/ All required instructions will be posted on this web site. Submissions should not exceed 25 double-spaced, 8.5x11 inch pages (including figures, tables, and references) in 10-12 point font. Include five to ten keywords, complete postal and e-mail addresses, and fax and phone numbers of corresponding author. If you have difficulty in electronic submission, contact the Web Master, Program Chairs or the Conference Coordinator, Mr. Steve Branch, The Society for Modeling and Simulation International, 4838 Ronson Court, Suite L, San Diego, CA 92111, USA, Tel 858-277-3888, Fax 858-277-3930, E-mail sbranch@scs.org Extended versions of selected accepted papers in SPECTS 2003 will be considered for possible publication in scholarly journals. Proposals for tutorials should be sent to the Conference Vice Program Chair, Raffaele Bolla. Proposals for special sessions and panel sessions should be submitted to the special Sessions Chair. For more information regarding presentations or exhibitions at SPECTS 2002 contact: Mr. Steve Branch at the address shown above. Sponsored by The Society for Modeling and Simulation International. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 09:05:18 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05416 for ; Thu, 24 Oct 2002 09:05:18 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OD78u14767 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 09:07:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OD78v14749 for ; Thu, 24 Oct 2002 09:07:08 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05370 for ; Thu, 24 Oct 2002 09:04:46 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OCiPv13446; Thu, 24 Oct 2002 08:44:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OCdJv13267 for ; Thu, 24 Oct 2002 08:39:19 -0400 Received: from rasheen.osdp.is.tsukuba.ac.jp (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04277 for ; Thu, 24 Oct 2002 08:36:57 -0400 (EDT) Received: from John (bill.is.tsukuba.ac.jp [130.158.81.66]) by rasheen.osdp.is.tsukuba.ac.jp (8.12.6/8.12.5) with SMTP id g9OCdEDm062347 for ; Thu, 24 Oct 2002 21:39:14 +0900 (JST) (envelope-from lijie@is.tsukuba.ac.jp) Message-ID: <018901c27b59$8e24aff0$42519e82@John> From: "Jie Li" To: Date: Thu, 24 Oct 2002 21:33:28 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Subject: [manet] CFP SPCTS 2003 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I apologize if you receive multiple copies of this message. Call For Papers %%%%%%%%%%%%%%%% 2003 International Symposium on Performance Evaluation of Computer and Telecommunication Systems (SPECTS 2003) July 20-24, 2003 Montreal, Canada http://scs.org/confernc/ssimc/ssimc03/cfp/spects03.htm Submission Deadlines Submission of Papers: January 31, 2003. Notification of Acceptance - April 25, 2003 Final Camera-Ready Submission - May 23, 2003 This annual international conference is a forum for professionals involved in performance evaluation of computer and telecommunication systems. Evaluation of computer systems and networks is needed at every stage in the life cycle of the product including design, manufacturing, sales/purchase, use, upgrade, tuning, etc. The discipline of performance evaluation has progressed rapidly in the past decade, and it has now begun to approach maturity. Significant progress has been made in analytic modeling, simulation, and measurement approaches for performance evaluation of computer and telecommunication systems. Topics of interest include, but are not limited to: Networking and Telecommunication Systems - Internet Technology - Quality of Service (QoS) - DiffServ/IntServ - MPLS - TCP - World Wide Web (WWW) Technology - Networking Techniques - Unicast and Multicast Routing - Congestion Control - Switching Techniques - Teletraffic - Network Protocols - Network Management and Control - Network Capacity Planning - Network Architecture Evaluation - Service and QoS Pricing - Security and Authentication -Broadband Networks - High-Speed Networking - ATM - Optical Networks - Wireless Systems and Networks - Satellite Systems - UMTS - Mobile Networks/Computing - Ad-hoc networks - Multimedia Communications Computer Systems - Distributed Architectures - Client/Server - Distributed Systems and Agents - Parallel and Distributed Computing - Massively Parallel Systems - Cluster Computing - Grid Computing - Interconnection Networks - Computer Architectures - Microprocessors/Microcomputers - Memory Systems - High Performance I/O - Real-time Systems - Scheduling Schemes -Software - Software Performance, Evaluation and Testing - Parallel Algorithms and Languages - Hardware and Software Monitors - High-Performance Computing - Workload and Traffic Characterization - Scientific Computing Algorithms - Reconfigurable Computing - Electronic Commerce Tools, Methodologies and Applications - Parallel and Distributed Simulation - Verification and Validation - Performance Tools and Methodologies - Neural Networks and Fuzzy Logic Applications to High Performance Computing/Networking - Performance Optimization - Queueing Systems and Networks - Scalability Studies - Integrated Modeling and Measurement - On-Line Performance Adaptation and Tuning - Process Algebra-Based Models - Performance Bounds - Integrated Design and Performance - New Performance Models - Mathematical Aspects of Performance - New Performability Schemes and Models - Case Studies General Chair Mohammad S. Obaidat Dept. of Computer Science, Monmouth University W. Long Branch, NJ 07764, USA Tel +1-732-571-4482 Fax +1-732-263-5202 E-mail: obaidat@monmouth.edu Senior Program Chair Franco Davoli DIST-University of Genoa Via Opera Pia 13, I-16145 Genoa, Italy Tel +39-010-353-2732 Fax +39-010-353-2154 E-Mail: franco@dist.unige.it Program Co-Chairs Ibrahim Onyuksel Dept. of Computer Sciences, N. Illinois Univ., USA E-mail: onyuksel@cs.niu.edu Erina Ferro ISTI, Institute of National Research Council (C.N.R.) C.N.R. Pisa Research Area, Building B, Room 73 Via G. Moruzzi, 1 56124 Pisa, Italy E-mail: erina.ferro@cnuce.cnr.it Vice Program Chair and Tutorial Chair Raffaele Bolla DIST-University of Genoa Via Opera Pia 13, I-16145 Genoa, Italy E-mail: lelus@dist.unige.it Vice Program Chair and Web Master Imad Mahgoub Department of Computer Science and Engineering Florida Atlantic University Boca Raton, FL 33431 E-mail: imad@cse.fau.edu Industrial Track and Special Sessions Chair J. Fox, Motorola Inc., UK E-mail: fox.ijcs@btinternet.com Technical Program Committee Ian Akyildiz, Georgia Tech., USA Mohammed Atiquzzaman, University of Oklahoma, USA Louis G. Birta, University of Ottawa, Canada Abdullah Abonamah, Zayed University, UAE Noureddine Boudriga, University of Tunis, Tunisia Hasan Cam, Arizona State University, USA Andrew Campbell, Columbia University, USA Nedo Celandroni, ISTI-CNR, Italy Haitham Cruickshank, University of Surrey, UK Hassan B. Diab, American University of Beirut, Lebanon Gabor Fodor, Ericsson Radio Systems, Sweden Geoffrey Fox, Indiana University, USA Luigi Fratta, Politecnico di Milano, Italy Aura Ganz, University of Massachusetts, USA Erol Gelenbe, University of Central Florida, USA Mario Gerla, UCLA, USA Sami Habib, Kuwait University, Kuwait Omar Hammami, ENSTA, France Jarmo Harju, Tampere University of Technology, Finland Herman Hughes, Michigan State University, USA Andrzej Jajszczyk, University of Mining and Metallurgy, Poland Abbas Jamalipour, University of Sydney, Australia Ingemar Kaj, Uppsala University, Sweden Krishna Kant, Intel, USA Helen Karatza, Aristotle University of Thessalonica, Greece Demetrios Kazakos, University of Louisiana, USA Ulrich Killat, Tech Univ. of Hamburg, Germany Tag Gon Kim, KAIST, Korea Kevin Kwiat, Air Force Research Laboratory, USA Veronica Lagrange M. Reis, Compaq Computers Corp., USA Axel Lehmann, Universit$BgU(B der Bundeswehr M$B!&(Bchen, Germany Daniel C. Lee, USC, USA Mike T. Liu, Ohio State University, USA Erich Lutz, DLR, Germany Sam Makki, Queensland University of Technology, Australia Krzysztof Malinowski, Warsaw Technical University, Poland Mario Marchese, University of Genoa, Italy Jose L. Marzo, Universitat de Girona, Spain Xiannong Meng, Bucknell University, USA Hussein Mouftah, Queen's University, Canada Mohamed Ould-Khaoua, University of Glasgow, UK Sergio Palazzo, Universit$B!&(Bdi Catania, Italy Georgios I. Papadimitriou, Aristotle University, Greece Achille Pattavina, Politecnico di Milano, Italy Krzysztof Pawlikowski, University of Canterbury, New Zealand Gregory D. Peterson, University of Tennessee Steven Pink, University of Arizona, USA George Polyzos, AUEB, Greece Ramon Puigjaner, Universitat de les Illes Balears, Spain Kaliappa Ravindran, CUNY, USA Gian Paolo Rossi, Universit$B!&(Bdi Milano, Italy Izhak Rubin, UCLA, USA Vicente Santonja, Technical University of Valencia, Spain Donald Schilling, CUNY, USA Jens B. Schmitt, TU Darmstadt, Germany Harald Skinnemoen, Nera, Norway Tatsuya Suda, UCI, USA Iwao Toda, Fujutsu Laboratories Ltd., Japan Phuoc Tran-Gia, University of Wuerzburg, Germany Kishor Trivedi, Duke University, USA Kenneth S. Vastola, Rensselaer Polytechnic Institute, USA Manuel Villen-Altamirano, Telefonica, Spain Bernd E. Wolfinger, Hamburg University, Germany Michele Zorzi, Universit$B!&(Bdi Ferrara, Italy Publicity Chair: Yuguang (Michael) Fang, University of Florida, USA Publicity Committee: Vice Chair: Jie Li, University of Tsukuba, Japan Chiara Petrioli, Universita` di Roma "La Sapienza", Italy Chuck Song, Chinese Academy of Sciences, China Ahmed Nuseirat, Al-Isra University, Jordan International Liaisons B. Sadoun, Al-Balqa' Applied University, Jordan Bsadoun@go.com.jo M. Sawan, Montreal Poly, Canada Sawan@vlsi.polymtl.ca N. Tchamov, Tampere Univ. of Technology, Finland Nikolay@cs.tut.fi Paper Submission Submit your complete papers electronically to: http://scs.proceedingscentral.com/ All required instructions will be posted on this web site. Submissions should not exceed 25 double-spaced, 8.5x11 inch pages (including figures, tables, and references) in 10-12 point font. Include five to ten keywords, complete postal and e-mail addresses, and fax and phone numbers of corresponding author. If you have difficulty in electronic submission, contact the Web Master, Program Chairs or the Conference Coordinator, Mr. Steve Branch, The Society for Modeling and Simulation International, 4838 Ronson Court, Suite L, San Diego, CA 92111, USA, Tel 858-277-3888, Fax 858-277-3930, E-mail sbranch@scs.org Extended versions of selected accepted papers in SPECTS 2003 will be considered for possible publication in scholarly journals. Proposals for tutorials should be sent to the Conference Vice Program Chair, Raffaele Bolla. Proposals for special sessions and panel sessions should be submitted to the special Sessions Chair. For more information regarding presentations or exhibitions at SPECTS 2002 contact: Mr. Steve Branch at the address shown above. Sponsored by The Society for Modeling and Simulation International. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 09:37:33 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07198 for ; Thu, 24 Oct 2002 09:37:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9ODdMx17276 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 09:39:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ODdMv17273 for ; Thu, 24 Oct 2002 09:39:22 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07151 for ; Thu, 24 Oct 2002 09:37:02 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ODVKv16404; Thu, 24 Oct 2002 09:31:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ODSCv16273 for ; Thu, 24 Oct 2002 09:28:12 -0400 Received: from smtp1.opnet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06470 for ; Thu, 24 Oct 2002 09:25:52 -0400 (EDT) Received: from WTN11073.opnet.com (unverified) by smtp1.opnet.com (Content Technologies SMTPRS 4.2.10) with ESMTP id ; Thu, 24 Oct 2002 09:28:04 -0400 Message-Id: <5.1.0.14.2.20021024091314.05d916e8@mail.opnet.com> X-Sender: psingh@mail.opnet.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 24 Oct 2002 09:28:04 -0400 To: Frank Kargl , manet@ietf.org From: "Pradeep K. Singh" Subject: Re: [manet] OPNET Modeler Version 9 and MANET models In-Reply-To: <3DB7DEB3.80200@informatik.uni-ulm.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Dear Frank: We are currently working on building a generic framework for creating routing models for simulating MANETs. Using this generic framework, we plan on releasing DSR and TORA with the initial release. However, the generic framework, will also allow you add new algorithms, modify existing ones easily. We are aggressively aiming to have this ready for release with OPNET's 9.0.A software around December 2002 timeframe. The new models will be integrated with existing TCP/IP and Wireless LAN standard models -- if you have any special requirements, you can privately contact us. In fact, there is a separate mailing list that we have set up for Modeler users (as I don't think this forum will be an appropriate for discussing OPNET specific issues). We can add you to that list, if you are not already on it. Sincerely, Pradeep OPNET Technologies, Inc. At 01:51 PM 10/24/2002 +0200, Frank Kargl wrote: >Dear all, > >I'm currently evaluation OPNET Modeler (Version 9.0.A PL2) for doing some >studies about MANETs. Most of the existing modules (DSR, AODV, MobileMesh >...) rely on older versions of the Modeler to run correctly, e.g. there is >a problem with the DSR module that Marc Ribet ported to 8.1.A PL2 that >seems to be related to timing issues in the 802.11 module. I already had >contact with Marc, but he is currently busy with other things but gave me >some good ideas what to look for. > >Before starting any effort to adapt these modules myself, has anyone >started a siminlar try before? Finished? Run into what problems? > >Regards ... Frank > >-- >----------------------------------------------------------------------- > Frank Kargl Multimedia Computing, University of Ulm, Germany > Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/ >----------------------------------------------------------------------- > Use the SOURCE, Luke ! I feel a great disturbance in the SOURCE. > But beware of the Microsoft side of the SOURCE ! > >_______________________________________________ >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-admin@ietf.org Thu Oct 24 09:37:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07212 for ; Thu, 24 Oct 2002 09:37:38 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ODVKv16404; Thu, 24 Oct 2002 09:31:20 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ODSCv16273 for ; Thu, 24 Oct 2002 09:28:12 -0400 Received: from smtp1.opnet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06470 for ; Thu, 24 Oct 2002 09:25:52 -0400 (EDT) Received: from WTN11073.opnet.com (unverified) by smtp1.opnet.com (Content Technologies SMTPRS 4.2.10) with ESMTP id ; Thu, 24 Oct 2002 09:28:04 -0400 Message-Id: <5.1.0.14.2.20021024091314.05d916e8@mail.opnet.com> X-Sender: psingh@mail.opnet.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 24 Oct 2002 09:28:04 -0400 To: Frank Kargl , manet@ietf.org From: "Pradeep K. Singh" Subject: Re: [manet] OPNET Modeler Version 9 and MANET models In-Reply-To: <3DB7DEB3.80200@informatik.uni-ulm.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Dear Frank: We are currently working on building a generic framework for creating routing models for simulating MANETs. Using this generic framework, we plan on releasing DSR and TORA with the initial release. However, the generic framework, will also allow you add new algorithms, modify existing ones easily. We are aggressively aiming to have this ready for release with OPNET's 9.0.A software around December 2002 timeframe. The new models will be integrated with existing TCP/IP and Wireless LAN standard models -- if you have any special requirements, you can privately contact us. In fact, there is a separate mailing list that we have set up for Modeler users (as I don't think this forum will be an appropriate for discussing OPNET specific issues). We can add you to that list, if you are not already on it. Sincerely, Pradeep OPNET Technologies, Inc. At 01:51 PM 10/24/2002 +0200, Frank Kargl wrote: >Dear all, > >I'm currently evaluation OPNET Modeler (Version 9.0.A PL2) for doing some >studies about MANETs. Most of the existing modules (DSR, AODV, MobileMesh >...) rely on older versions of the Modeler to run correctly, e.g. there is >a problem with the DSR module that Marc Ribet ported to 8.1.A PL2 that >seems to be related to timing issues in the 802.11 module. I already had >contact with Marc, but he is currently busy with other things but gave me >some good ideas what to look for. > >Before starting any effort to adapt these modules myself, has anyone >started a siminlar try before? Finished? Run into what problems? > >Regards ... Frank > >-- >----------------------------------------------------------------------- > Frank Kargl Multimedia Computing, University of Ulm, Germany > Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/ >----------------------------------------------------------------------- > Use the SOURCE, Luke ! I feel a great disturbance in the SOURCE. > But beware of the Microsoft side of the SOURCE ! > >_______________________________________________ >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-admin@ietf.org Thu Oct 24 10:51:59 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10417 for ; Thu, 24 Oct 2002 10:51:59 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OEjHv21480; Thu, 24 Oct 2002 10:45:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OEh1v21367 for ; Thu, 24 Oct 2002 10:43:01 -0400 Received: from webmails.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10043 for ; Thu, 24 Oct 2002 10:40:40 -0400 (EDT) Received: (qmail 30023 invoked by uid 511); 24 Oct 2002 14:42:56 -0000 Message-ID: <20021024144256.30022.qmail@webmails.com> Content-Type: multipart/alternative; boundary="----------=_1035470576-30009-0" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.411 (Entity 5.404) From: "moez gadri" To: manet@ietf.org Organization: WebMailS - http://www.webmails.com Date: Thu, 24 Oct 2002 16:42:56 +0100 X-Originating-Ip: 193.95.3.132 Subject: [manet] RE : Re : basic routing protocol Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format... ------------=_1035470576-30009-0 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi,=0D =0D Thanks for advice to search in www.google.com,=0D =0D I'm interresting to QoS routing protocols for ad hoc networks, witch are in general a variant of basic routing protocols, so i search a full list of basic routing protocol. I found a list below in=0D http://www.cis.ohio-state.edu/~jain/cis788-99/adhoc_routing/index.html=0D =0D there are other protocols like DREAM and RDMAR. but is it the full list of protocol ? there is the question. =0D =0D =0D table-driven Protocols:=0D DSDV - Dynamic Destination-Sequenced Distance-Vector Routing Protocol =0D WRP - The Wireless Routing Protocol =0D GSR - Global State Routing =0D FSR - Fisheye State Routing =0D HSR - Hierarchical State Routing =0D ZHLS - Zone-based Hierarchical Link State Routing Protocol =0D CGSR - Clusterhead Gateway Switch Routing Protocol =0D =0D on-demond Protocols : =0D CBRP - Cluster based Routing Protocols =0D AODV - Ad Hoc On-demand Distance Vector Routing =0D DSRP - Dynamic Source Routing Protocol =0D TORA - Temporally Ordered Routing Algorithm =0D ABR - Associativity Based Routing =0D SSR - Signal Stability Routing ____________________________________________________________________ - http://www.WebMailSPro.com - >>=20 VOTRE service d'email sans pub avec VOTRE nom de domaine ------------=_1035470576-30009-0 Content-Type: text/html Content-Disposition: inline Content-Transfer-Encoding: 7bit 
Hi,

Thanks for advice to search in www.google.com,

I'm interresting to QoS routing protocols for ad hoc networks, witch
are in general a variant of basic routing protocols, so i search a full
list of basic routing protocol. I found a list below in
http://www.cis.ohio-state.edu/~jain/cis788-99/adhoc_routing/index.html

there are other protocols like DREAM and RDMAR. but is it the full list
of protocol ? there is the question. 


table-driven Protocols:
DSDV - Dynamic Destination-Sequenced Distance-Vector Routing Protocol 
WRP - The Wireless Routing Protocol 
GSR - Global State Routing 
FSR - Fisheye State Routing 
HSR - Hierarchical State Routing 
ZHLS - Zone-based Hierarchical Link State Routing Protocol 
CGSR - Clusterhead Gateway Switch Routing Protocol 

on-demond Protocols : 
CBRP - Cluster based Routing Protocols 
AODV - Ad Hoc On-demand Distance Vector Routing 
DSRP - Dynamic Source Routing Protocol 
TORA - Temporally Ordered Routing Algorithm 
ABR - Associativity Based Routing 
SSR - Signal Stability Routing

____________________________________________________________________
- http://www.WebMailSPro.com - >> 
VOTRE service d'email sans pub avec VOTRE nom de domaine
------------=_1035470576-30009-0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 10:55:01 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10498 for ; Thu, 24 Oct 2002 10:55:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OEupe21932 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 10:56:51 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OEupv21929 for ; Thu, 24 Oct 2002 10:56:51 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10482 for ; Thu, 24 Oct 2002 10:54:30 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OEjHv21480; Thu, 24 Oct 2002 10:45:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OEh1v21367 for ; Thu, 24 Oct 2002 10:43:01 -0400 Received: from webmails.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA10043 for ; Thu, 24 Oct 2002 10:40:40 -0400 (EDT) Received: (qmail 30023 invoked by uid 511); 24 Oct 2002 14:42:56 -0000 Message-ID: <20021024144256.30022.qmail@webmails.com> Content-Type: multipart/alternative; boundary="----------=_1035470576-30009-0" Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.411 (Entity 5.404) From: "moez gadri" To: manet@ietf.org Organization: WebMailS - http://www.webmails.com Date: Thu, 24 Oct 2002 16:42:56 +0100 X-Originating-Ip: 193.95.3.132 Subject: [manet] RE : Re : basic routing protocol Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format... ------------=_1035470576-30009-0 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi,=0D =0D Thanks for advice to search in www.google.com,=0D =0D I'm interresting to QoS routing protocols for ad hoc networks, witch are in general a variant of basic routing protocols, so i search a full list of basic routing protocol. I found a list below in=0D http://www.cis.ohio-state.edu/~jain/cis788-99/adhoc_routing/index.html=0D =0D there are other protocols like DREAM and RDMAR. but is it the full list of protocol ? there is the question. =0D =0D =0D table-driven Protocols:=0D DSDV - Dynamic Destination-Sequenced Distance-Vector Routing Protocol =0D WRP - The Wireless Routing Protocol =0D GSR - Global State Routing =0D FSR - Fisheye State Routing =0D HSR - Hierarchical State Routing =0D ZHLS - Zone-based Hierarchical Link State Routing Protocol =0D CGSR - Clusterhead Gateway Switch Routing Protocol =0D =0D on-demond Protocols : =0D CBRP - Cluster based Routing Protocols =0D AODV - Ad Hoc On-demand Distance Vector Routing =0D DSRP - Dynamic Source Routing Protocol =0D TORA - Temporally Ordered Routing Algorithm =0D ABR - Associativity Based Routing =0D SSR - Signal Stability Routing ____________________________________________________________________ - http://www.WebMailSPro.com - >>=20 VOTRE service d'email sans pub avec VOTRE nom de domaine ------------=_1035470576-30009-0 Content-Type: text/html Content-Disposition: inline Content-Transfer-Encoding: 7bit 
Hi,

Thanks for advice to search in www.google.com,

I'm interresting to QoS routing protocols for ad hoc networks, witch
are in general a variant of basic routing protocols, so i search a full
list of basic routing protocol. I found a list below in
http://www.cis.ohio-state.edu/~jain/cis788-99/adhoc_routing/index.html

there are other protocols like DREAM and RDMAR. but is it the full list
of protocol ? there is the question. 


table-driven Protocols:
DSDV - Dynamic Destination-Sequenced Distance-Vector Routing Protocol 
WRP - The Wireless Routing Protocol 
GSR - Global State Routing 
FSR - Fisheye State Routing 
HSR - Hierarchical State Routing 
ZHLS - Zone-based Hierarchical Link State Routing Protocol 
CGSR - Clusterhead Gateway Switch Routing Protocol 

on-demond Protocols : 
CBRP - Cluster based Routing Protocols 
AODV - Ad Hoc On-demand Distance Vector Routing 
DSRP - Dynamic Source Routing Protocol 
TORA - Temporally Ordered Routing Algorithm 
ABR - Associativity Based Routing 
SSR - Signal Stability Routing

____________________________________________________________________
- http://www.WebMailSPro.com - >> 
VOTRE service d'email sans pub avec VOTRE nom de domaine
------------=_1035470576-30009-0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 24 12:02:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13625 for ; Thu, 24 Oct 2002 12:02:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OFpFv25745; Thu, 24 Oct 2002 11:51:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OFn0v25655 for ; Thu, 24 Oct 2002 11:49:00 -0400 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12984 for ; Thu, 24 Oct 2002 11:46:38 -0400 (EDT) Received: from colorado.edu (ecee189-245-dhcp.Colorado.EDU [128.138.189.245]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9OFmpB13922; Thu, 24 Oct 2002 09:48:51 -0600 (MDT) Message-ID: <3DB8165F.3050708@colorado.edu> Date: Thu, 24 Oct 2002 09:48:47 -0600 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Frank Kargl CC: manet@ietf.org Subject: Re: [manet] OPNET Modeler Version 9 and MANET models References: <3DB7DEB3.80200@informatik.uni-ulm.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, Our research group at University of Colorado at Boulder have a full fledged implementation of DSR running on a hardware test-bed. We have the implementation in the user space. We have about 10 laptops running Red Hat Linux equipped with Cisco 350 Series Wireless Ethernet cards. Our research group woul dbe more than helpful to let you know abt the implementation and help you guys out. Regards, Shweta, Sheetal, Sagar, Tim. Frank Kargl wrote: > Dear all, > > I'm currently evaluation OPNET Modeler (Version 9.0.A PL2) for doing > some studies about MANETs. Most of the existing modules (DSR, AODV, > MobileMesh ...) rely on older versions of the Modeler to run correctly, > e.g. there is a problem with the DSR module that Marc Ribet ported to > 8.1.A PL2 that seems to be related to timing issues in the 802.11 > module. I already had contact with Marc, but he is currently busy with > other things but gave me some good ideas what to look for. > > Before starting any effort to adapt these modules myself, has anyone > started a siminlar try before? Finished? Run into what problems? > > Regards ... Frank > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 12:14:13 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14139 for ; Thu, 24 Oct 2002 12:14:13 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OGG4A27723 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 12:16:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OGG4v27720 for ; Thu, 24 Oct 2002 12:16:04 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14127 for ; Thu, 24 Oct 2002 12:13:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OFpFv25745; Thu, 24 Oct 2002 11:51:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OFn0v25655 for ; Thu, 24 Oct 2002 11:49:00 -0400 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12984 for ; Thu, 24 Oct 2002 11:46:38 -0400 (EDT) Received: from colorado.edu (ecee189-245-dhcp.Colorado.EDU [128.138.189.245]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9OFmpB13922; Thu, 24 Oct 2002 09:48:51 -0600 (MDT) Message-ID: <3DB8165F.3050708@colorado.edu> Date: Thu, 24 Oct 2002 09:48:47 -0600 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Frank Kargl CC: manet@ietf.org Subject: Re: [manet] OPNET Modeler Version 9 and MANET models References: <3DB7DEB3.80200@informatik.uni-ulm.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Our research group at University of Colorado at Boulder have a full fledged implementation of DSR running on a hardware test-bed. We have the implementation in the user space. We have about 10 laptops running Red Hat Linux equipped with Cisco 350 Series Wireless Ethernet cards. Our research group woul dbe more than helpful to let you know abt the implementation and help you guys out. Regards, Shweta, Sheetal, Sagar, Tim. Frank Kargl wrote: > Dear all, > > I'm currently evaluation OPNET Modeler (Version 9.0.A PL2) for doing > some studies about MANETs. Most of the existing modules (DSR, AODV, > MobileMesh ...) rely on older versions of the Modeler to run correctly, > e.g. there is a problem with the DSR module that Marc Ribet ported to > 8.1.A PL2 that seems to be related to timing issues in the 802.11 > module. I already had contact with Marc, but he is currently busy with > other things but gave me some good ideas what to look for. > > Before starting any effort to adapt these modules myself, has anyone > started a siminlar try before? Finished? Run into what problems? > > Regards ... Frank > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 12:21:11 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14434 for ; Thu, 24 Oct 2002 12:21:10 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OGN2n28177 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 12:23:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OGN1v28174 for ; Thu, 24 Oct 2002 12:23:01 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14388 for ; Thu, 24 Oct 2002 12:20:39 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OGF9v27692; Thu, 24 Oct 2002 12:15:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OG78v27102 for ; Thu, 24 Oct 2002 12:07:08 -0400 Received: from mail.eecis.udel.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13750 for ; Thu, 24 Oct 2002 12:04:47 -0400 (EDT) Received: from stimpy.eecis.udel.edu by mail.eecis.udel.edu id aa18367; 24 Oct 2002 12:06 EDT Date: Thu, 24 Oct 2002 12:06:35 -0400 (EDT) From: Girish Borkar To: manet@ietf.org In-Reply-To: <20021024144256.30022.qmail@webmails.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Hidden and Exposed terminal problem in wireless communication Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi all, I am having some trouble with some fundamental concepts in wireless communication. Its about hidden and exposed nodes. I guess if I am clear on one of those, I'll be clear on the the other too. So, here is my confusion.... Lets say we have 2 nodes A and B and A is sending data to B. And, there are other nodes (C, D and E) around B that cannot hear A, but can communicate with B. E A ------> B C D So are all of these nodes(C, D and E) considered hidden even though they may not be trying to tranmit ? OR Are they considered hidden only if they try to transmit ? Another question is .... Does A have to be tranmitting to make any or all of C, D and E as hidden terminal(s) ? OR... Can we call C, D and E as hidden with respect to A even if A is not transmitting ? Is there some term called "geographically hidden" ?? I hope my doubts are clear. Any clarifications ?? Thanks Girish Borkar --------------------------------------------- Univ. of Delaware Ph: 302-731-7504 (Home) 302-831-3643 (Lab) --------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 24 12:21:13 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14447 for ; Thu, 24 Oct 2002 12:21:12 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OGF9v27692; Thu, 24 Oct 2002 12:15:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OG78v27102 for ; Thu, 24 Oct 2002 12:07:08 -0400 Received: from mail.eecis.udel.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13750 for ; Thu, 24 Oct 2002 12:04:47 -0400 (EDT) Received: from stimpy.eecis.udel.edu by mail.eecis.udel.edu id aa18367; 24 Oct 2002 12:06 EDT Date: Thu, 24 Oct 2002 12:06:35 -0400 (EDT) From: Girish Borkar To: manet@ietf.org In-Reply-To: <20021024144256.30022.qmail@webmails.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Hidden and Exposed terminal problem in wireless communication Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi all, I am having some trouble with some fundamental concepts in wireless communication. Its about hidden and exposed nodes. I guess if I am clear on one of those, I'll be clear on the the other too. So, here is my confusion.... Lets say we have 2 nodes A and B and A is sending data to B. And, there are other nodes (C, D and E) around B that cannot hear A, but can communicate with B. E A ------> B C D So are all of these nodes(C, D and E) considered hidden even though they may not be trying to tranmit ? OR Are they considered hidden only if they try to transmit ? Another question is .... Does A have to be tranmitting to make any or all of C, D and E as hidden terminal(s) ? OR... Can we call C, D and E as hidden with respect to A even if A is not transmitting ? Is there some term called "geographically hidden" ?? I hope my doubts are clear. Any clarifications ?? Thanks Girish Borkar --------------------------------------------- Univ. of Delaware Ph: 302-731-7504 (Home) 302-831-3643 (Lab) --------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 13:09:06 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16048 for ; Thu, 24 Oct 2002 13:09:06 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OHAwe30809 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 13:10:58 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OHAwv30806 for ; Thu, 24 Oct 2002 13:10:58 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16019 for ; Thu, 24 Oct 2002 13:08:35 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OH3Ov29863; Thu, 24 Oct 2002 13:03:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OH2wv29840 for ; Thu, 24 Oct 2002 13:02:58 -0400 Received: from blv-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15719 for ; Thu, 24 Oct 2002 13:00:35 -0400 (EDT) Received: from stl-av-02.boeing.com ([192.76.190.7]) by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id KAA09670; Thu, 24 Oct 2002 10:02:52 -0700 (PDT) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by stl-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id MAA17794; Thu, 24 Oct 2002 12:02:50 -0500 (CDT) Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4]) by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g9OH2nr24190; Thu, 24 Oct 2002 10:02:49 -0700 (PDT) Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2653.19) id ; Thu, 24 Oct 2002 13:02:48 -0400 Message-ID: From: "Manfredi, Albert E" To: "'Girish Borkar'" , manet@ietf.org Subject: RE: [manet] Hidden and Exposed terminal problem in wireless commu nication Date: Thu, 24 Oct 2002 13:02:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Girish, My answer would be that even if a terminal is not transmitting, it would be hidden. Why? Because whether you use proactive or reactive routing protocols, those hidden nodes must be reachable for the MANET to be viable. In your example, C, D, and E are hidden from A, but are reachable from A, thanks to B being there. Bert > -----Original Message----- > From: Girish Borkar [mailto:girish@mail.eecis.udel.edu] > Sent: Thursday, October 24, 2002 12:07 PM > To: manet@ietf.org > Subject: [manet] Hidden and Exposed terminal problem in wireless > communication > > > > Hi all, > > I am having some trouble with some fundamental concepts in wireless > communication. Its about hidden and exposed nodes. I guess if > I am clear > on one of those, I'll be clear on the the other too. > > So, here is my confusion.... > > Lets say we have 2 nodes A and B and A is sending data to B. > And, there > are other nodes (C, D and E) around B that cannot hear A, but can > communicate with B. > > E > > > A ------> B C > > > D > > > > So are all of these nodes(C, D and E) considered hidden even > though they > may not be trying to tranmit ? > OR > Are they considered hidden only if they try to transmit ? > > > Another question is .... > > Does A have to be tranmitting to make any or all of C, D and E as > hidden terminal(s) ? > OR... > Can we call C, D and E as hidden with respect to A even if A is not > transmitting ? Is there some term called "geographically hidden" ?? > > > I hope my doubts are clear. > > Any clarifications ?? > Thanks > > Girish Borkar > > --------------------------------------------- > Univ. of Delaware > > Ph: 302-731-7504 (Home) > 302-831-3643 (Lab) > --------------------------------------------- > > _______________________________________________ > 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-admin@ietf.org Thu Oct 24 13:09:08 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16066 for ; Thu, 24 Oct 2002 13:09:08 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OH3Ov29863; Thu, 24 Oct 2002 13:03:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OH2wv29840 for ; Thu, 24 Oct 2002 13:02:58 -0400 Received: from blv-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15719 for ; Thu, 24 Oct 2002 13:00:35 -0400 (EDT) Received: from stl-av-02.boeing.com ([192.76.190.7]) by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id KAA09670; Thu, 24 Oct 2002 10:02:52 -0700 (PDT) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by stl-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id MAA17794; Thu, 24 Oct 2002 12:02:50 -0500 (CDT) Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4]) by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g9OH2nr24190; Thu, 24 Oct 2002 10:02:49 -0700 (PDT) Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2653.19) id ; Thu, 24 Oct 2002 13:02:48 -0400 Message-ID: From: "Manfredi, Albert E" To: "'Girish Borkar'" , manet@ietf.org Subject: RE: [manet] Hidden and Exposed terminal problem in wireless commu nication Date: Thu, 24 Oct 2002 13:02:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Girish, My answer would be that even if a terminal is not transmitting, it would be hidden. Why? Because whether you use proactive or reactive routing protocols, those hidden nodes must be reachable for the MANET to be viable. In your example, C, D, and E are hidden from A, but are reachable from A, thanks to B being there. Bert > -----Original Message----- > From: Girish Borkar [mailto:girish@mail.eecis.udel.edu] > Sent: Thursday, October 24, 2002 12:07 PM > To: manet@ietf.org > Subject: [manet] Hidden and Exposed terminal problem in wireless > communication > > > > Hi all, > > I am having some trouble with some fundamental concepts in wireless > communication. Its about hidden and exposed nodes. I guess if > I am clear > on one of those, I'll be clear on the the other too. > > So, here is my confusion.... > > Lets say we have 2 nodes A and B and A is sending data to B. > And, there > are other nodes (C, D and E) around B that cannot hear A, but can > communicate with B. > > E > > > A ------> B C > > > D > > > > So are all of these nodes(C, D and E) considered hidden even > though they > may not be trying to tranmit ? > OR > Are they considered hidden only if they try to transmit ? > > > Another question is .... > > Does A have to be tranmitting to make any or all of C, D and E as > hidden terminal(s) ? > OR... > Can we call C, D and E as hidden with respect to A even if A is not > transmitting ? Is there some term called "geographically hidden" ?? > > > I hope my doubts are clear. > > Any clarifications ?? > Thanks > > Girish Borkar > > --------------------------------------------- > Univ. of Delaware > > Ph: 302-731-7504 (Home) > 302-831-3643 (Lab) > --------------------------------------------- > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 14:52:37 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19538 for ; Thu, 24 Oct 2002 14:52:37 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OIsUw03881 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 14:54:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OIsUv03878 for ; Thu, 24 Oct 2002 14:54:30 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19525 for ; Thu, 24 Oct 2002 14:52:06 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OIl1v03533; Thu, 24 Oct 2002 14:47:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OIjmv03479 for ; Thu, 24 Oct 2002 14:45:48 -0400 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19270 for ; Thu, 24 Oct 2002 14:43:24 -0400 (EDT) Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g9OIjgn428736; Thu, 24 Oct 2002 14:45:42 -0400 (EDT) Received: from tlin (E112224.vtacs.com [208.138.112.224]) by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1-GA) with ESMTP id AQW45958 (AUTH talin); Thu, 24 Oct 2002 14:45:37 -0400 (EDT) Message-ID: <001f01c27b8d$5e4ceca0$755a640a@vtacs.com> From: "Tao Lin" To: "moez gadri" , References: <20021024144256.30022.qmail@webmails.com> Subject: Re: [manet] RE : Re : basic routing protocol Date: Thu, 24 Oct 2002 14:44:21 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01C27B6B.D6DFBF20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_001C_01C27B6B.D6DFBF20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable There are some of others listed in www.ietf.org =3D> MANET group web = site. ----- Original Message -----=20 From: moez gadri=20 To: manet@ietf.org=20 Sent: Thursday, October 24, 2002 11:42 AM Subject: [manet] RE : Re : basic routing protocol Hi, Thanks for advice to search in www.google.com, I'm interresting to QoS routing protocols for ad hoc networks, witch are in general a variant of basic routing protocols, so i search a full list of basic routing protocol. I found a list below in http://www.cis.ohio-state.edu/~jain/cis788-99/adhoc_routing/index.html there are other protocols like DREAM and RDMAR. but is it the full list of protocol ? there is the question.=20 table-driven Protocols: DSDV - Dynamic Destination-Sequenced Distance-Vector Routing Protocol=20 WRP - The Wireless Routing Protocol=20 GSR - Global State Routing=20 FSR - Fisheye State Routing=20 HSR - Hierarchical State Routing=20 ZHLS - Zone-based Hierarchical Link State Routing Protocol=20 CGSR - Clusterhead Gateway Switch Routing Protocol=20 on-demond Protocols :=20 CBRP - Cluster based Routing Protocols=20 AODV - Ad Hoc On-demand Distance Vector Routing=20 DSRP - Dynamic Source Routing Protocol=20 TORA - Temporally Ordered Routing Algorithm=20 ABR - Associativity Based Routing=20 SSR - Signal Stability Routing ____________________________________________________________________ - http://www.WebMailSPro.com - >>=20 VOTRE service d'email sans pub avec VOTRE nom de domaine ------=_NextPart_000_001C_01C27B6B.D6DFBF20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
There are some of others listed in = www.ietf.org=20 =3D> MANET group web = site.
 
----- Original Message -----
From:=20 moez=20 gadri
Sent: Thursday, October 24, = 2002 11:42=20 AM
Subject: [manet] RE : Re : = basic routing=20 protocol

Hi,

Thanks for advice to search in www.google.com,

I'm interresting to QoS routing protocols for ad hoc networks, witch
are in general a variant of basic routing protocols, so i search a full
list of basic routing protocol. I found a list below in
http://www.cis.ohio-state.edu/~jain/cis788-99/adhoc_routing/index.=
html

there are other protocols like DREAM and RDMAR. but is it the full list
of protocol ? there is the question.=20


table-driven Protocols:
DSDV - Dynamic Destination-Sequenced Distance-Vector Routing Protocol=20
WRP - The Wireless Routing Protocol=20
GSR - Global State Routing=20
FSR - Fisheye State Routing=20
HSR - Hierarchical State Routing=20
ZHLS - Zone-based Hierarchical Link State Routing Protocol=20
CGSR - Clusterhead Gateway Switch Routing Protocol=20

on-demond Protocols :=20
CBRP - Cluster based Routing Protocols=20
AODV - Ad Hoc On-demand Distance Vector Routing=20
DSRP - Dynamic Source Routing Protocol=20
TORA - Temporally Ordered Routing Algorithm=20
ABR - Associativity Based Routing=20
SSR - Signal Stability Routing

____________________________________________________________________
- http://www.WebMailSPro.com =
- >>=20
VOTRE service d'email sans pub avec VOTRE nom de =
domaine
------=_NextPart_000_001C_01C27B6B.D6DFBF20-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 24 14:52:39 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19551 for ; Thu, 24 Oct 2002 14:52:39 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OIl1v03533; Thu, 24 Oct 2002 14:47:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OIjmv03479 for ; Thu, 24 Oct 2002 14:45:48 -0400 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19270 for ; Thu, 24 Oct 2002 14:43:24 -0400 (EDT) Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g9OIjgn428736; Thu, 24 Oct 2002 14:45:42 -0400 (EDT) Received: from tlin (E112224.vtacs.com [208.138.112.224]) by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1-GA) with ESMTP id AQW45958 (AUTH talin); Thu, 24 Oct 2002 14:45:37 -0400 (EDT) Message-ID: <001f01c27b8d$5e4ceca0$755a640a@vtacs.com> From: "Tao Lin" To: "moez gadri" , References: <20021024144256.30022.qmail@webmails.com> Subject: Re: [manet] RE : Re : basic routing protocol Date: Thu, 24 Oct 2002 14:44:21 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01C27B6B.D6DFBF20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_001C_01C27B6B.D6DFBF20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable There are some of others listed in www.ietf.org =3D> MANET group web = site. ----- Original Message -----=20 From: moez gadri=20 To: manet@ietf.org=20 Sent: Thursday, October 24, 2002 11:42 AM Subject: [manet] RE : Re : basic routing protocol Hi, Thanks for advice to search in www.google.com, I'm interresting to QoS routing protocols for ad hoc networks, witch are in general a variant of basic routing protocols, so i search a full list of basic routing protocol. I found a list below in http://www.cis.ohio-state.edu/~jain/cis788-99/adhoc_routing/index.html there are other protocols like DREAM and RDMAR. but is it the full list of protocol ? there is the question.=20 table-driven Protocols: DSDV - Dynamic Destination-Sequenced Distance-Vector Routing Protocol=20 WRP - The Wireless Routing Protocol=20 GSR - Global State Routing=20 FSR - Fisheye State Routing=20 HSR - Hierarchical State Routing=20 ZHLS - Zone-based Hierarchical Link State Routing Protocol=20 CGSR - Clusterhead Gateway Switch Routing Protocol=20 on-demond Protocols :=20 CBRP - Cluster based Routing Protocols=20 AODV - Ad Hoc On-demand Distance Vector Routing=20 DSRP - Dynamic Source Routing Protocol=20 TORA - Temporally Ordered Routing Algorithm=20 ABR - Associativity Based Routing=20 SSR - Signal Stability Routing ____________________________________________________________________ - http://www.WebMailSPro.com - >>=20 VOTRE service d'email sans pub avec VOTRE nom de domaine ------=_NextPart_000_001C_01C27B6B.D6DFBF20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
There are some of others listed in = www.ietf.org=20 =3D> MANET group web = site.
 
----- Original Message -----
From:=20 moez=20 gadri
Sent: Thursday, October 24, = 2002 11:42=20 AM
Subject: [manet] RE : Re : = basic routing=20 protocol

Hi,

Thanks for advice to search in www.google.com,

I'm interresting to QoS routing protocols for ad hoc networks, witch
are in general a variant of basic routing protocols, so i search a full
list of basic routing protocol. I found a list below in
http://www.cis.ohio-state.edu/~jain/cis788-99/adhoc_routing/index.=
html

there are other protocols like DREAM and RDMAR. but is it the full list
of protocol ? there is the question.=20


table-driven Protocols:
DSDV - Dynamic Destination-Sequenced Distance-Vector Routing Protocol=20
WRP - The Wireless Routing Protocol=20
GSR - Global State Routing=20
FSR - Fisheye State Routing=20
HSR - Hierarchical State Routing=20
ZHLS - Zone-based Hierarchical Link State Routing Protocol=20
CGSR - Clusterhead Gateway Switch Routing Protocol=20

on-demond Protocols :=20
CBRP - Cluster based Routing Protocols=20
AODV - Ad Hoc On-demand Distance Vector Routing=20
DSRP - Dynamic Source Routing Protocol=20
TORA - Temporally Ordered Routing Algorithm=20
ABR - Associativity Based Routing=20
SSR - Signal Stability Routing

____________________________________________________________________
- http://www.WebMailSPro.com =
- >>=20
VOTRE service d'email sans pub avec VOTRE nom de =
domaine
------=_NextPart_000_001C_01C27B6B.D6DFBF20-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 14:57:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19752 for ; Thu, 24 Oct 2002 14:57:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OIxRr04105 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 14:59:27 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OIxRv04102 for ; Thu, 24 Oct 2002 14:59:27 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19716 for ; Thu, 24 Oct 2002 14:57:02 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OIqBv03698; Thu, 24 Oct 2002 14:52:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OIp6v03674 for ; Thu, 24 Oct 2002 14:51:06 -0400 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19390 for ; Thu, 24 Oct 2002 14:48:42 -0400 (EDT) Received: from colorado.edu (ecee189-245-dhcp.Colorado.EDU [128.138.189.245]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9OIp0B25014; Thu, 24 Oct 2002 12:51:00 -0600 (MDT) Message-ID: <3DB8410F.7070704@colorado.edu> Date: Thu, 24 Oct 2002 12:50:55 -0600 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org, Brown Tim Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] [Fwd: Re: ISART 2003] Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, The following symposium will have sessions devoted to wireless networking and its relationship to capacity and spectrum usage. I encourage you to submit a paper. --------------------------------------------------------------------------- INTERNATIONAL SYMPOSIUM ON ADVANCED RADIO TECHNOLOGIES (ISART 2003) CALL FOR PAPERS =========================== The ISART 2003 conference to be held this coming March 4 - 7, 2003 seeks to bring together business leaders, policy makers, and technical researchers from the telecommunications industry with a focus on wireless communications. Each of these groups shapes the industry, and by creating a meeting where they can interact with each other, we plan to create a window through which the present and future state of the industry can be viewed. The ISART program committee is soliciting papers describing new radio technologies, analysis, and innovative business, economic, and policy concepts, in any of the following topic areas: - Spectrum (usage, policy, management, regulation, economics, sharing mechanisms) - Electromagnetics (propagation, antennas, RF-front ends) - Broadband Deployment (regulation, marketing, economics, wireless systems) - Wireless Networks (scaling to large networks, ad hoc networks, Internet over wireless, convergence of WLANs and 3G) - Telecommunications in Developing Countries (policy, economics, regulation, and technology) - Radios (software defined radios, RF software, spectrally efficient systems) - Homeland Security (emergency response communications, public safety, wireless network security) Students are especially encouraged to submit their work. Deadlines: Nov. 6, 2002 - Deadline for submission of one page abstract. Dec. 4, 2002 - Notification of acceptance to authors. Jan. 15, 2003 - Deadline for submission of paper. Abstract Format: - One page total - At least 10pt font - May be double column - Indicate the contact author with an e-mail address - Indicate the topic area from the above list The abstract should summarize research results and not be a proposal for research since very little time is available between the acceptance notification and the final paper submission. The final paper will be 4 pages, double column, 10pt text (approximately 2500 words). If you have questions about submitting abstracts contact either: Dr. Timothy X Brown Interdisciplinary Telecommunications Electrical and Computer Engineering EC-OT 331 Campus Box 530 University of Colorado Boulder, CO 80309 Tel: (303) 492-1630 Fax: (303) 492-1112 e-mail: Timxb@Colorado.EDU or J. Wayde Allen DOC/NTIA/ITS.M 325 Broadway Boulder, CO 80305-3328 Tel: (303) 497-5871 Fax: (303) 497-5323 e-mail: wallen@its.bldrdoc.gov General Information: http://www.its.bldrdoc.gov/meetings/art/index.html _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 24 14:57:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19765 for ; Thu, 24 Oct 2002 14:57:36 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OIqBv03698; Thu, 24 Oct 2002 14:52:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OIp6v03674 for ; Thu, 24 Oct 2002 14:51:06 -0400 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19390 for ; Thu, 24 Oct 2002 14:48:42 -0400 (EDT) Received: from colorado.edu (ecee189-245-dhcp.Colorado.EDU [128.138.189.245]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9OIp0B25014; Thu, 24 Oct 2002 12:51:00 -0600 (MDT) Message-ID: <3DB8410F.7070704@colorado.edu> Date: Thu, 24 Oct 2002 12:50:55 -0600 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org, Brown Tim Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] [Fwd: Re: ISART 2003] Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, The following symposium will have sessions devoted to wireless networking and its relationship to capacity and spectrum usage. I encourage you to submit a paper. --------------------------------------------------------------------------- INTERNATIONAL SYMPOSIUM ON ADVANCED RADIO TECHNOLOGIES (ISART 2003) CALL FOR PAPERS =========================== The ISART 2003 conference to be held this coming March 4 - 7, 2003 seeks to bring together business leaders, policy makers, and technical researchers from the telecommunications industry with a focus on wireless communications. Each of these groups shapes the industry, and by creating a meeting where they can interact with each other, we plan to create a window through which the present and future state of the industry can be viewed. The ISART program committee is soliciting papers describing new radio technologies, analysis, and innovative business, economic, and policy concepts, in any of the following topic areas: - Spectrum (usage, policy, management, regulation, economics, sharing mechanisms) - Electromagnetics (propagation, antennas, RF-front ends) - Broadband Deployment (regulation, marketing, economics, wireless systems) - Wireless Networks (scaling to large networks, ad hoc networks, Internet over wireless, convergence of WLANs and 3G) - Telecommunications in Developing Countries (policy, economics, regulation, and technology) - Radios (software defined radios, RF software, spectrally efficient systems) - Homeland Security (emergency response communications, public safety, wireless network security) Students are especially encouraged to submit their work. Deadlines: Nov. 6, 2002 - Deadline for submission of one page abstract. Dec. 4, 2002 - Notification of acceptance to authors. Jan. 15, 2003 - Deadline for submission of paper. Abstract Format: - One page total - At least 10pt font - May be double column - Indicate the contact author with an e-mail address - Indicate the topic area from the above list The abstract should summarize research results and not be a proposal for research since very little time is available between the acceptance notification and the final paper submission. The final paper will be 4 pages, double column, 10pt text (approximately 2500 words). If you have questions about submitting abstracts contact either: Dr. Timothy X Brown Interdisciplinary Telecommunications Electrical and Computer Engineering EC-OT 331 Campus Box 530 University of Colorado Boulder, CO 80309 Tel: (303) 492-1630 Fax: (303) 492-1112 e-mail: Timxb@Colorado.EDU or J. Wayde Allen DOC/NTIA/ITS.M 325 Broadway Boulder, CO 80305-3328 Tel: (303) 497-5871 Fax: (303) 497-5323 e-mail: wallen@its.bldrdoc.gov General Information: http://www.its.bldrdoc.gov/meetings/art/index.html _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 16:16:56 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21873 for ; Thu, 24 Oct 2002 16:16:56 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OKImX08506 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 16:18:48 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OKImv08503 for ; Thu, 24 Oct 2002 16:18:48 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21841 for ; Thu, 24 Oct 2002 16:16:24 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OKAqv08205; Thu, 24 Oct 2002 16:10:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OK84v08134 for ; Thu, 24 Oct 2002 16:08:04 -0400 Received: from smtpproxy2.mitre.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21547 for ; Thu, 24 Oct 2002 16:05:40 -0400 (EDT) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id g9OK7pV16836; Thu, 24 Oct 2002 16:07:51 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id g9OK7mt09561; Thu, 24 Oct 2002 16:07:48 -0400 (EDT) Received: from m29103-pc.mitre.org (128.29.56.49) by mailhub2.mitre.org with SMTP id 12068772; Thu, 24 Oct 2002 16:07:20 -0400 Message-ID: <3DB852FA.D5D893F2@mitre.org> Date: Thu, 24 Oct 2002 16:07:22 -0400 From: John Stine Organization: The MITRE Corporation X-Mailer: Mozilla 4.79 [en]C-20020130M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Girish Borkar CC: manet@ietf.org Subject: Re: [manet] Hidden and Exposed terminal problem in wireless communication References: Content-Type: multipart/alternative; boundary="------------B97E1F4D8E11A3A63F00CD2D" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------B97E1F4D8E11A3A63F00CD2D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Girish, Hidden and exposed nodes are a phenomenon of carrier sensing and packet sensing MAC protocols. These protocols regulate access by the mechansim where nodes defer from attempting to gain access when they sense another node using the channel. A hidden node is a node that does not hear the transmission that a node within its range is receiving and thus does not defer from attempting to gain access. (The reason for not hearing the transmission can be distance, be an obstacle in the propagation path, be being in the null of an antenna, or in the case of DSSS, be the use of a different code) When it tries to gain access it interferes with the reception at the destination. The exposed node problem is very different. An exposed node is a node that hears multiple disjoint sections of a network and never gets the opportunity to contend since it is always deferring to someone. Technically, Aloha, Slotted Aloha, and TDMA do not suffer from these problems since they do not use carrier sensing to regulate their access attempts. Collisions may occur but this has nothing to do with them hearing each other. Carrier sensing protocols that provide no hidden node suppression will perform as Aloha in congested environments. So, in conclusion, in your example, hidden nodes only occur when you are using a carrier sensing access protocol and there is nothing in place to cause C, D, or E to defer from contending when A is sending data to B. Your illustration does not provide an example of an exposed node so consider the following: A B C D E F G H I Say A, B, F, G, and C can hear each other and C, D, E, H, and I can hear each other but A,B, F, G cannot hear D, E, H, I and vice versa. Then C is exposed to these two partitions in the network. In order for C to contend, both partitions must be quiet. Addionally, all nodes in each partition have the potential to be hidden nodes when a node in the opposite partition tries to communicate with C. The term "hidden node" and "exposed node" refer to the problems described above, not really to the layout of the nodes. So in the example above, C is not exposed if no one else is transmitting. Another way to understand this, consider a continuous tessellation of nodes on a rectangular grid where each node can hear transmissions up to two nodes away in each direction. Such a grid could be separted into partitions of transmitting nodes where any node could be an exposed node at different times in its operation. Similarly, any node could be a hidden node. John Girish Borkar wrote: > Hi all, > > I am having some trouble with some fundamental concepts in wireless > communication. Its about hidden and exposed nodes. I guess if I am clear > on one of those, I'll be clear on the the other too. > > So, here is my confusion.... > > Lets say we have 2 nodes A and B and A is sending data to B. And, there > are other nodes (C, D and E) around B that cannot hear A, but can > communicate with B. > > E > > A ------> B C > > D > > So are all of these nodes(C, D and E) considered hidden even though they > may not be trying to tranmit ? > OR > Are they considered hidden only if they try to transmit ? > > Another question is .... > > Does A have to be tranmitting to make any or all of C, D and E as > hidden terminal(s) ? > OR... > Can we call C, D and E as hidden with respect to A even if A is not > transmitting ? Is there some term called "geographically hidden" ?? > > I hope my doubts are clear. > > Any clarifications ?? > Thanks > > Girish Borkar > > --------------------------------------------- > Univ. of Delaware > > Ph: 302-731-7504 (Home) > 302-831-3643 (Lab) > --------------------------------------------- > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet --------------B97E1F4D8E11A3A63F00CD2D Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Girish,

    Hidden and exposed nodes are a phenomenon of carrier sensing and packet sensing MAC protocols.  These protocols regulate access by the mechansim where nodes defer from attempting to gain access when they sense another node using the channel.  A hidden node is a node that does not hear the transmission that a node within its range is receiving and thus does not defer from attempting to gain access. (The reason for not hearing the transmission can be distance, be an obstacle in the propagation path, be being in the null of an antenna,  or in the case of DSSS, be the use of a different code) When it tries to gain access it interferes with the reception at the destination.  The exposed node problem is very different.  An exposed node is a node that hears multiple disjoint sections of a network and never gets the opportunity to contend since it is always deferring to someone.  Technically, Aloha, Slotted Aloha, and TDMA do not suffer from these problems since they do not use carrier sensing to regulate their access attempts.  Collisions may occur but this has nothing to do with them hearing each other.  Carrier sensing protocols that provide no hidden node suppression will perform as Aloha in congested environments.

So, in conclusion, in your example, hidden nodes only occur when you are using a carrier sensing access protocol and there is nothing in place to cause C, D, or E to defer from contending when A is sending data to B.  Your illustration does not provide an example of an exposed node so consider the following:

A   B      C      D   E
F   G             H   I

Say A, B, F, G, and C can hear each other and C, D, E, H, and I can hear each other but A,B, F, G cannot hear D, E, H, I and vice versa.  Then C is exposed to these two partitions in the network.  In order for C to contend, both partitions must be quiet.  Addionally, all nodes in each partition have the potential to be hidden nodes when a node in the opposite partition tries to communicate with C.

The term "hidden node" and "exposed node" refer to the problems described above, not really to the layout of the nodes.  So in the example above, C is not exposed if no one else is transmitting.  Another way to understand this, consider a continuous tessellation of nodes on a rectangular grid where each node can hear transmissions up to two nodes away in each direction.  Such a grid could be separted into partitions of transmitting nodes where any node could be an exposed node at different times in its operation.  Similarly, any node could be a hidden node.

John

Girish Borkar wrote:

Hi all,

I am having some trouble with some fundamental concepts in wireless
communication. Its about hidden and exposed nodes. I guess if I am clear
on one of those, I'll be clear on the the other too.

So, here is my confusion....

Lets say we have 2 nodes A and B and A is sending data to B. And, there
are other nodes (C, D and E)  around B that cannot hear A, but can
communicate with B.

                          E

                A ------> B      C

                           D

So are all of these nodes(C, D and E) considered hidden even though they
may not be trying to tranmit ?
OR
Are they considered hidden only if they try to transmit ?

Another question is ....

Does A have to be tranmitting to make any or all of C, D and E  as
hidden terminal(s) ?
OR...
Can we call C, D and E as hidden with respect to A even if A is not
transmitting ? Is there some term called "geographically hidden" ??

I hope my doubts are clear.

Any clarifications ??
Thanks

Girish Borkar

---------------------------------------------
Univ. of Delaware

Ph: 302-731-7504 (Home)
    302-831-3643 (Lab)
---------------------------------------------

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

--------------B97E1F4D8E11A3A63F00CD2D-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 24 16:17:00 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21886 for ; Thu, 24 Oct 2002 16:17:00 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OKAqv08205; Thu, 24 Oct 2002 16:10:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OK84v08134 for ; Thu, 24 Oct 2002 16:08:04 -0400 Received: from smtpproxy2.mitre.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21547 for ; Thu, 24 Oct 2002 16:05:40 -0400 (EDT) Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id g9OK7pV16836; Thu, 24 Oct 2002 16:07:51 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id g9OK7mt09561; Thu, 24 Oct 2002 16:07:48 -0400 (EDT) Received: from m29103-pc.mitre.org (128.29.56.49) by mailhub2.mitre.org with SMTP id 12068772; Thu, 24 Oct 2002 16:07:20 -0400 Message-ID: <3DB852FA.D5D893F2@mitre.org> Date: Thu, 24 Oct 2002 16:07:22 -0400 From: John Stine Organization: The MITRE Corporation X-Mailer: Mozilla 4.79 [en]C-20020130M (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Girish Borkar CC: manet@ietf.org Subject: Re: [manet] Hidden and Exposed terminal problem in wireless communication References: Content-Type: multipart/alternative; boundary="------------B97E1F4D8E11A3A63F00CD2D" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------B97E1F4D8E11A3A63F00CD2D Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Girish, Hidden and exposed nodes are a phenomenon of carrier sensing and packet sensing MAC protocols. These protocols regulate access by the mechansim where nodes defer from attempting to gain access when they sense another node using the channel. A hidden node is a node that does not hear the transmission that a node within its range is receiving and thus does not defer from attempting to gain access. (The reason for not hearing the transmission can be distance, be an obstacle in the propagation path, be being in the null of an antenna, or in the case of DSSS, be the use of a different code) When it tries to gain access it interferes with the reception at the destination. The exposed node problem is very different. An exposed node is a node that hears multiple disjoint sections of a network and never gets the opportunity to contend since it is always deferring to someone. Technically, Aloha, Slotted Aloha, and TDMA do not suffer from these problems since they do not use carrier sensing to regulate their access attempts. Collisions may occur but this has nothing to do with them hearing each other. Carrier sensing protocols that provide no hidden node suppression will perform as Aloha in congested environments. So, in conclusion, in your example, hidden nodes only occur when you are using a carrier sensing access protocol and there is nothing in place to cause C, D, or E to defer from contending when A is sending data to B. Your illustration does not provide an example of an exposed node so consider the following: A B C D E F G H I Say A, B, F, G, and C can hear each other and C, D, E, H, and I can hear each other but A,B, F, G cannot hear D, E, H, I and vice versa. Then C is exposed to these two partitions in the network. In order for C to contend, both partitions must be quiet. Addionally, all nodes in each partition have the potential to be hidden nodes when a node in the opposite partition tries to communicate with C. The term "hidden node" and "exposed node" refer to the problems described above, not really to the layout of the nodes. So in the example above, C is not exposed if no one else is transmitting. Another way to understand this, consider a continuous tessellation of nodes on a rectangular grid where each node can hear transmissions up to two nodes away in each direction. Such a grid could be separted into partitions of transmitting nodes where any node could be an exposed node at different times in its operation. Similarly, any node could be a hidden node. John Girish Borkar wrote: > Hi all, > > I am having some trouble with some fundamental concepts in wireless > communication. Its about hidden and exposed nodes. I guess if I am clear > on one of those, I'll be clear on the the other too. > > So, here is my confusion.... > > Lets say we have 2 nodes A and B and A is sending data to B. And, there > are other nodes (C, D and E) around B that cannot hear A, but can > communicate with B. > > E > > A ------> B C > > D > > So are all of these nodes(C, D and E) considered hidden even though they > may not be trying to tranmit ? > OR > Are they considered hidden only if they try to transmit ? > > Another question is .... > > Does A have to be tranmitting to make any or all of C, D and E as > hidden terminal(s) ? > OR... > Can we call C, D and E as hidden with respect to A even if A is not > transmitting ? Is there some term called "geographically hidden" ?? > > I hope my doubts are clear. > > Any clarifications ?? > Thanks > > Girish Borkar > > --------------------------------------------- > Univ. of Delaware > > Ph: 302-731-7504 (Home) > 302-831-3643 (Lab) > --------------------------------------------- > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet --------------B97E1F4D8E11A3A63F00CD2D Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Girish,

    Hidden and exposed nodes are a phenomenon of carrier sensing and packet sensing MAC protocols.  These protocols regulate access by the mechansim where nodes defer from attempting to gain access when they sense another node using the channel.  A hidden node is a node that does not hear the transmission that a node within its range is receiving and thus does not defer from attempting to gain access. (The reason for not hearing the transmission can be distance, be an obstacle in the propagation path, be being in the null of an antenna,  or in the case of DSSS, be the use of a different code) When it tries to gain access it interferes with the reception at the destination.  The exposed node problem is very different.  An exposed node is a node that hears multiple disjoint sections of a network and never gets the opportunity to contend since it is always deferring to someone.  Technically, Aloha, Slotted Aloha, and TDMA do not suffer from these problems since they do not use carrier sensing to regulate their access attempts.  Collisions may occur but this has nothing to do with them hearing each other.  Carrier sensing protocols that provide no hidden node suppression will perform as Aloha in congested environments.

So, in conclusion, in your example, hidden nodes only occur when you are using a carrier sensing access protocol and there is nothing in place to cause C, D, or E to defer from contending when A is sending data to B.  Your illustration does not provide an example of an exposed node so consider the following:

A   B      C      D   E
F   G             H   I

Say A, B, F, G, and C can hear each other and C, D, E, H, and I can hear each other but A,B, F, G cannot hear D, E, H, I and vice versa.  Then C is exposed to these two partitions in the network.  In order for C to contend, both partitions must be quiet.  Addionally, all nodes in each partition have the potential to be hidden nodes when a node in the opposite partition tries to communicate with C.

The term "hidden node" and "exposed node" refer to the problems described above, not really to the layout of the nodes.  So in the example above, C is not exposed if no one else is transmitting.  Another way to understand this, consider a continuous tessellation of nodes on a rectangular grid where each node can hear transmissions up to two nodes away in each direction.  Such a grid could be separted into partitions of transmitting nodes where any node could be an exposed node at different times in its operation.  Similarly, any node could be a hidden node.

John

Girish Borkar wrote:

Hi all,

I am having some trouble with some fundamental concepts in wireless
communication. Its about hidden and exposed nodes. I guess if I am clear
on one of those, I'll be clear on the the other too.

So, here is my confusion....

Lets say we have 2 nodes A and B and A is sending data to B. And, there
are other nodes (C, D and E)  around B that cannot hear A, but can
communicate with B.

                          E

                A ------> B      C

                           D

So are all of these nodes(C, D and E) considered hidden even though they
may not be trying to tranmit ?
OR
Are they considered hidden only if they try to transmit ?

Another question is ....

Does A have to be tranmitting to make any or all of C, D and E  as
hidden terminal(s) ?
OR...
Can we call C, D and E as hidden with respect to A even if A is not
transmitting ? Is there some term called "geographically hidden" ??

I hope my doubts are clear.

Any clarifications ??
Thanks

Girish Borkar

---------------------------------------------
Univ. of Delaware

Ph: 302-731-7504 (Home)
    302-831-3643 (Lab)
---------------------------------------------

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

--------------B97E1F4D8E11A3A63F00CD2D-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 16:52:51 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22900 for ; Thu, 24 Oct 2002 16:52:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OKshc10411 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 16:54:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OKshv10408 for ; Thu, 24 Oct 2002 16:54:43 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22885 for ; Thu, 24 Oct 2002 16:52:19 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OKgQv09939; Thu, 24 Oct 2002 16:42:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OKfCv09914 for ; Thu, 24 Oct 2002 16:41:12 -0400 Received: from mta04ps.bigpond.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22556 for ; Thu, 24 Oct 2002 16:38:48 -0400 (EDT) Received: from moon ([144.135.25.75]) by mta04ps.bigpond.com (Netscape Messaging Server 4.15 mta04ps Jul 16 2002 22:47:55) with SMTP id H4I6SE00.0VG for ; Fri, 25 Oct 2002 06:41:02 +1000 Received: from wnpp-p-144-134-175-243.prem.tmns.net.au ([144.134.175.243]) by PSMAM03.mailsvc.email.bigpond.com(MailRouter V3.0n 83/21912632); 25 Oct 2002 06:41:02 Message-ID: <00b101c27b9e$08cd80d0$6500a8c0@moon> From: "Anshul Gupta" To: Date: Fri, 25 Oct 2002 06:43:37 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 7bit Subject: [manet] Multicast Protocol for Ad Hoc Wireless Networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi all, I was searching for efficient and reliable multicast protocol for ad hoc wireless networks on google but I was amazed to see how many are there. Which is the most reliable and efficient protocol ? Does anybody has experience with any of them ? Cheers, Anshul Gupta _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 24 16:52:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22915 for ; Thu, 24 Oct 2002 16:52:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OKgQv09939; Thu, 24 Oct 2002 16:42:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OKfCv09914 for ; Thu, 24 Oct 2002 16:41:12 -0400 Received: from mta04ps.bigpond.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22556 for ; Thu, 24 Oct 2002 16:38:48 -0400 (EDT) Received: from moon ([144.135.25.75]) by mta04ps.bigpond.com (Netscape Messaging Server 4.15 mta04ps Jul 16 2002 22:47:55) with SMTP id H4I6SE00.0VG for ; Fri, 25 Oct 2002 06:41:02 +1000 Received: from wnpp-p-144-134-175-243.prem.tmns.net.au ([144.134.175.243]) by PSMAM03.mailsvc.email.bigpond.com(MailRouter V3.0n 83/21912632); 25 Oct 2002 06:41:02 Message-ID: <00b101c27b9e$08cd80d0$6500a8c0@moon> From: "Anshul Gupta" To: Date: Fri, 25 Oct 2002 06:43:37 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: 7bit Subject: [manet] Multicast Protocol for Ad Hoc Wireless Networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi all, I was searching for efficient and reliable multicast protocol for ad hoc wireless networks on google but I was amazed to see how many are there. Which is the most reliable and efficient protocol ? Does anybody has experience with any of them ? Cheers, Anshul Gupta _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 24 19:15:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26638 for ; Thu, 24 Oct 2002 19:15:27 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ON8dv17817; Thu, 24 Oct 2002 19:08:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ON6Sv17213 for ; Thu, 24 Oct 2002 19:06:28 -0400 Received: from po4.wam.umd.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26368 for ; Thu, 24 Oct 2002 19:04:02 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA23041; Thu, 24 Oct 2002 19:06:20 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id TAA25675; Thu, 24 Oct 2002 19:06:19 -0400 (EDT) Received: from localhost (prabha@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA25671; Thu, 24 Oct 2002 19:06:19 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: prabha owned process doing -bs Date: Thu, 24 Oct 2002 19:06:19 -0400 (EDT) From: Prabha Ramachandran To: manet@ietf.org cc: prabha@glue.umd.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] MAODV Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi all, I am a graduate student working towards the simulation of a multicast authentication scheme for MANETs. Does anyone have an MAODV simulation in OPnet / NS-2 / GlomoSim ? Any pointers would be helpful. Thanks Prabha PRABHA RAMACHANDRAN Graduate Research Assistant Institute for Systems Research University of Maryland College Park, MD 20742 email: prabha@wam.umd.edu Ph: (W) : 301-405-6594 (H) : 301-441-2277 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 24 19:19:23 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26719 for ; Thu, 24 Oct 2002 19:19:23 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9ONLI318162 for manet-archive@odin.ietf.org; Thu, 24 Oct 2002 19:21:18 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ONLIv18159 for ; Thu, 24 Oct 2002 19:21:18 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26704 for ; Thu, 24 Oct 2002 19:18:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ON8dv17817; Thu, 24 Oct 2002 19:08:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9ON6Sv17213 for ; Thu, 24 Oct 2002 19:06:28 -0400 Received: from po4.wam.umd.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26368 for ; Thu, 24 Oct 2002 19:04:02 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:root@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA23041; Thu, 24 Oct 2002 19:06:20 -0400 (EDT) Received: from rac2.wam.umd.edu (IDENT:sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id TAA25675; Thu, 24 Oct 2002 19:06:19 -0400 (EDT) Received: from localhost (prabha@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA25671; Thu, 24 Oct 2002 19:06:19 -0400 (EDT) X-Authentication-Warning: rac2.wam.umd.edu: prabha owned process doing -bs Date: Thu, 24 Oct 2002 19:06:19 -0400 (EDT) From: Prabha Ramachandran To: manet@ietf.org cc: prabha@glue.umd.edu Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] MAODV Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi all, I am a graduate student working towards the simulation of a multicast authentication scheme for MANETs. Does anyone have an MAODV simulation in OPnet / NS-2 / GlomoSim ? Any pointers would be helpful. Thanks Prabha PRABHA RAMACHANDRAN Graduate Research Assistant Institute for Systems Research University of Maryland College Park, MD 20742 email: prabha@wam.umd.edu Ph: (W) : 301-405-6594 (H) : 301-441-2277 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 25 00:06:51 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02366 for ; Fri, 25 Oct 2002 00:06:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9P48mQ31721 for manet-archive@odin.ietf.org; Fri, 25 Oct 2002 00:08:48 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P48mv31718 for ; Fri, 25 Oct 2002 00:08:48 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02362 for ; Fri, 25 Oct 2002 00:06:20 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P40kv30822; Fri, 25 Oct 2002 00:00:46 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P3uBv30704 for ; Thu, 24 Oct 2002 23:56:11 -0400 Received: from ims21.stu.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02099 for ; Thu, 24 Oct 2002 23:53:42 -0400 (EDT) Received: from mbxsrv26.stu.nus.edu.sg ([137.132.14.236]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.4905); Fri, 25 Oct 2002 11:55:58 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Date: Fri, 25 Oct 2002 11:55:58 +0800 Message-ID: <6330DC96389A924A804F52FA3848930E01234D82@MBXSRV26.stu.nus.edu.sg> Thread-Topic: How to increase packet delivery ratio in MANETs Thread-Index: AcJ22BkoxRdQ6BhBTBiaLcNejsXX6wDYhLzw From: "Marwaha Shivanajay" To: X-OriginalArrivalTime: 25 Oct 2002 03:55:58.0412 (UTC) FILETIME=[6D2678C0:01C27BDA] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9P3uBv30705 Subject: [manet] How to increase packet delivery ratio in MANETs Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Dear All, How would we select routes in MANETs if we want to ensure/meet high packet delivery ratio (PDR) requirements. Are there any papers which deal with this. Also are there any papers/mechanisms developed for achieving higher packet delivery ratio for certain class of traffic which have specific packet loss requirements. Can we compromise delay to ensure high PDR in MANETs?? (In my view, we need to know the stability of the links in a route to ensure high packet delivery ratio. For this we may use eiter "HELLO Messages" or "GPS information". Using HELLO messages has the disadvantage of more power & bandwidth consumption and NS-2 results have shown that HELLO messages (when used with AODV) decrease the PDR in the first place by 5-10% compared to AODV with link layer notification. On the other hand, GPS assisted routing has constraints working indoors.) So how to ensure/meet packet loss requirement (atleast for some classes of traffic) ? Regards, Shivanajay Marwaha *********************** Research Scholar ECE Dept, NUS, 10 Kent Ridge Crescent, Singapore 119260 *********************** -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ -~-~-~-~-~-~-~-~-~-~ An expert is someone who can tell you exactly afterwards, why his prognosis was not correct. Winston Churchill -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ -~-~-~-~-~-~-~-~-~-~ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 25 00:06:56 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02380 for ; Fri, 25 Oct 2002 00:06:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P40kv30822; Fri, 25 Oct 2002 00:00:46 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P3uBv30704 for ; Thu, 24 Oct 2002 23:56:11 -0400 Received: from ims21.stu.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02099 for ; Thu, 24 Oct 2002 23:53:42 -0400 (EDT) Received: from mbxsrv26.stu.nus.edu.sg ([137.132.14.236]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.4905); Fri, 25 Oct 2002 11:55:58 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Date: Fri, 25 Oct 2002 11:55:58 +0800 Message-ID: <6330DC96389A924A804F52FA3848930E01234D82@MBXSRV26.stu.nus.edu.sg> Thread-Topic: How to increase packet delivery ratio in MANETs Thread-Index: AcJ22BkoxRdQ6BhBTBiaLcNejsXX6wDYhLzw From: "Marwaha Shivanajay" To: X-OriginalArrivalTime: 25 Oct 2002 03:55:58.0412 (UTC) FILETIME=[6D2678C0:01C27BDA] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9P3uBv30705 Subject: [manet] How to increase packet delivery ratio in MANETs Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Dear All, How would we select routes in MANETs if we want to ensure/meet high packet delivery ratio (PDR) requirements. Are there any papers which deal with this. Also are there any papers/mechanisms developed for achieving higher packet delivery ratio for certain class of traffic which have specific packet loss requirements. Can we compromise delay to ensure high PDR in MANETs?? (In my view, we need to know the stability of the links in a route to ensure high packet delivery ratio. For this we may use eiter "HELLO Messages" or "GPS information". Using HELLO messages has the disadvantage of more power & bandwidth consumption and NS-2 results have shown that HELLO messages (when used with AODV) decrease the PDR in the first place by 5-10% compared to AODV with link layer notification. On the other hand, GPS assisted routing has constraints working indoors.) So how to ensure/meet packet loss requirement (atleast for some classes of traffic) ? Regards, Shivanajay Marwaha *********************** Research Scholar ECE Dept, NUS, 10 Kent Ridge Crescent, Singapore 119260 *********************** -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ -~-~-~-~-~-~-~-~-~-~ An expert is someone who can tell you exactly afterwards, why his prognosis was not correct. Winston Churchill -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ -~-~-~-~-~-~-~-~-~-~ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 25 05:50:14 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17559 for ; Fri, 25 Oct 2002 05:50:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9b7v22973; Fri, 25 Oct 2002 05:37:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9Yav22641 for ; Fri, 25 Oct 2002 05:34:36 -0400 Received: from david.siemens.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16942 for ; Fri, 25 Oct 2002 05:32:16 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id g9P9YVX17758; Fri, 25 Oct 2002 11:34:31 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9P9YUV20978; Fri, 25 Oct 2002 11:34:31 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9P9YVIu008924; Fri, 25 Oct 2002 11:34:31 +0200 (MET DST) Message-ID: <3DB91026.6824ED14@mchp.siemens.de> Date: Fri, 25 Oct 2002 11:34:31 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Aodvimpl-Public , "manet@ietf.org" , "ns-users@isi.edu" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] AODV performance comparison in ns-2.1b9 and ns-2.1b8a Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, I just mentioned one reason for the better performance of aodv in ns-2.1b8a in my last email. Another reason is that the buffered packets are not dropped from the router queue (rqueue) in the sendRequest function in aodv.cc (version ns-2.1b8a) when RREQ_RETRIES is reached, so that these packets have the chance to be sent later. In the newer version (ns-2.1b9) they are dropped. I think the second behaviour is right because in the real world we assume that the node is not existing anymore and we drop all the packets destinated to it. This difference is one other reason for the better performance of the older version while testing AODV. Thanks in advance for any comments Regards Riadh _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 25 05:51:19 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17601 for ; Fri, 25 Oct 2002 05:51:19 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9P9r7B24196 for manet-archive@odin.ietf.org; Fri, 25 Oct 2002 05:53:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9r7v24193 for ; Fri, 25 Oct 2002 05:53:07 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17579 for ; Fri, 25 Oct 2002 05:50:48 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9Tav22387; Fri, 25 Oct 2002 05:29:36 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9Pdv22301 for ; Fri, 25 Oct 2002 05:25:39 -0400 Received: from goliath.siemens.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16705 for ; Fri, 25 Oct 2002 05:23:20 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g9P9PYd19913; Fri, 25 Oct 2002 11:25:34 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9P9PYV14038; Fri, 25 Oct 2002 11:25:34 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9P9PXIu008811; Fri, 25 Oct 2002 11:25:33 +0200 (MET DST) Message-ID: <3DB90E0D.CF38C288@mchp.siemens.de> Date: Fri, 25 Oct 2002 11:25:33 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Aodvimpl-Public , "manet@ietf.org" , "ns-users@isi.edu" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Access to interface queue at routing level?? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, can someone tell me if we could access to the interface queue and to the IP packets in that queue (I mean in the real world. In NS-2 it is not a problem)?? is it also possible to access to the IP-Header of these packets?? This access is allowed in the aodv version under ns-2.1b8a but not in ns-2.1b9, so that it is possible to salvage the packets even if they are already in the interface queue (see rt_down in aodv.cc, ns-2.1b8a). That's one reason for the better simulation results of aodv in the older version. I don't know if it is fair!!! One other reason is in my next email. Regards Riadh _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 25 05:51:21 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17619 for ; Fri, 25 Oct 2002 05:51:21 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9Tav22387; Fri, 25 Oct 2002 05:29:36 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9Pdv22301 for ; Fri, 25 Oct 2002 05:25:39 -0400 Received: from goliath.siemens.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16705 for ; Fri, 25 Oct 2002 05:23:20 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g9P9PYd19913; Fri, 25 Oct 2002 11:25:34 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9P9PYV14038; Fri, 25 Oct 2002 11:25:34 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9P9PXIu008811; Fri, 25 Oct 2002 11:25:33 +0200 (MET DST) Message-ID: <3DB90E0D.CF38C288@mchp.siemens.de> Date: Fri, 25 Oct 2002 11:25:33 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Aodvimpl-Public , "manet@ietf.org" , "ns-users@isi.edu" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Access to interface queue at routing level?? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, can someone tell me if we could access to the interface queue and to the IP packets in that queue (I mean in the real world. In NS-2 it is not a problem)?? is it also possible to access to the IP-Header of these packets?? This access is allowed in the aodv version under ns-2.1b8a but not in ns-2.1b9, so that it is possible to salvage the packets even if they are already in the interface queue (see rt_down in aodv.cc, ns-2.1b8a). That's one reason for the better simulation results of aodv in the older version. I don't know if it is fair!!! One other reason is in my next email. Regards Riadh _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 25 05:55:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17734 for ; Fri, 25 Oct 2002 05:55:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9P9vfL24387 for manet-archive@odin.ietf.org; Fri, 25 Oct 2002 05:57:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9vfv24384 for ; Fri, 25 Oct 2002 05:57:41 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17726 for ; Fri, 25 Oct 2002 05:55:21 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9oCv23848; Fri, 25 Oct 2002 05:50:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9lPv23727 for ; Fri, 25 Oct 2002 05:47:25 -0400 Received: from nathan.informatik.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17185 for ; Fri, 25 Oct 2002 05:45:05 -0400 (EDT) Received: from orca.informatik.uni-ulm.de (orca.informatik.uni-ulm.de [134.60.70.16]) by nathan.informatik.uni-ulm.de (8.11.3/any version) with ESMTP id g9P9lNa24446; Fri, 25 Oct 2002 11:47:23 +0200 Received: by orca.informatik.uni-ulm.de (Postfix on SuSE Linux 8.0 (i386), from userid 508) id 913011B90E; Fri, 25 Oct 2002 11:47:23 +0200 (CEST) Date: Fri, 25 Oct 2002 11:47:23 +0200 From: Stefan Schlott To: Riadh Marrakchi Cc: manet@ietf.org Subject: Re: [manet] Access to interface queue at routing level?? Message-ID: <20021025094723.GA25873@orca.informatik.uni-ulm.de> References: <3DB90E0D.CF38C288@mchp.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DB90E0D.CF38C288@mchp.siemens.de> User-Agent: Mutt/1.4i Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, > can someone tell me if we could access to the interface queue and to the > IP packets in that queue (I mean in the real world. In NS-2 it is not a > problem)?? is it also possible to access to the IP-Header of these > packets?? You can send arbitrary packet data and receive all packets sent to a machine by using raw sockets - this is a generic interface (even present in some windows versions), but if you want to manipulate the routing decision, this won't be the interface you want. On Linux, there is a interface to the kernel network stack called "netfilter modules". Basically, these are kernel modules which allow inspection and manipulation of raw packets in several different processing stages. Unfortunately, this is a Linux-specific interface. Hope it helps, Stefan. -- *--- please cut here... -------------------------------------- thanks! ---* |-> E-Mail: stefan.schlott@informatik.uni-ulm.de PGP-Key: 0x2F36F4FE <-| | There are only 10 types of people in this world -- those that | | understand binary and those that don't. | *-------------------------------------------------------------------------* _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 25 05:55:55 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17747 for ; Fri, 25 Oct 2002 05:55:55 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9oCv23848; Fri, 25 Oct 2002 05:50:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9lPv23727 for ; Fri, 25 Oct 2002 05:47:25 -0400 Received: from nathan.informatik.uni-ulm.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17185 for ; Fri, 25 Oct 2002 05:45:05 -0400 (EDT) Received: from orca.informatik.uni-ulm.de (orca.informatik.uni-ulm.de [134.60.70.16]) by nathan.informatik.uni-ulm.de (8.11.3/any version) with ESMTP id g9P9lNa24446; Fri, 25 Oct 2002 11:47:23 +0200 Received: by orca.informatik.uni-ulm.de (Postfix on SuSE Linux 8.0 (i386), from userid 508) id 913011B90E; Fri, 25 Oct 2002 11:47:23 +0200 (CEST) Date: Fri, 25 Oct 2002 11:47:23 +0200 From: Stefan Schlott To: Riadh Marrakchi Cc: manet@ietf.org Subject: Re: [manet] Access to interface queue at routing level?? Message-ID: <20021025094723.GA25873@orca.informatik.uni-ulm.de> References: <3DB90E0D.CF38C288@mchp.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DB90E0D.CF38C288@mchp.siemens.de> User-Agent: Mutt/1.4i Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, > can someone tell me if we could access to the interface queue and to the > IP packets in that queue (I mean in the real world. In NS-2 it is not a > problem)?? is it also possible to access to the IP-Header of these > packets?? You can send arbitrary packet data and receive all packets sent to a machine by using raw sockets - this is a generic interface (even present in some windows versions), but if you want to manipulate the routing decision, this won't be the interface you want. On Linux, there is a interface to the kernel network stack called "netfilter modules". Basically, these are kernel modules which allow inspection and manipulation of raw packets in several different processing stages. Unfortunately, this is a Linux-specific interface. Hope it helps, Stefan. -- *--- please cut here... -------------------------------------- thanks! ---* |-> E-Mail: stefan.schlott@informatik.uni-ulm.de PGP-Key: 0x2F36F4FE <-| | There are only 10 types of people in this world -- those that | | understand binary and those that don't. | *-------------------------------------------------------------------------* _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 25 05:58:13 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17884 for ; Fri, 25 Oct 2002 05:58:13 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9PA01W24562 for manet-archive@odin.ietf.org; Fri, 25 Oct 2002 06:00:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PA01v24555 for ; Fri, 25 Oct 2002 06:00:01 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17872 for ; Fri, 25 Oct 2002 05:57:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9b7v22973; Fri, 25 Oct 2002 05:37:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9Yav22641 for ; Fri, 25 Oct 2002 05:34:36 -0400 Received: from david.siemens.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16942 for ; Fri, 25 Oct 2002 05:32:16 -0400 (EDT) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.11.6/8.11.6) with ESMTP id g9P9YVX17758; Fri, 25 Oct 2002 11:34:31 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9P9YUV20978; Fri, 25 Oct 2002 11:34:31 +0200 (MEST) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9P9YVIu008924; Fri, 25 Oct 2002 11:34:31 +0200 (MET DST) Message-ID: <3DB91026.6824ED14@mchp.siemens.de> Date: Fri, 25 Oct 2002 11:34:31 +0200 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: Aodvimpl-Public , "manet@ietf.org" , "ns-users@isi.edu" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] AODV performance comparison in ns-2.1b9 and ns-2.1b8a Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I just mentioned one reason for the better performance of aodv in ns-2.1b8a in my last email. Another reason is that the buffered packets are not dropped from the router queue (rqueue) in the sendRequest function in aodv.cc (version ns-2.1b8a) when RREQ_RETRIES is reached, so that these packets have the chance to be sent later. In the newer version (ns-2.1b9) they are dropped. I think the second behaviour is right because in the real world we assume that the node is not existing anymore and we drop all the packets destinated to it. This difference is one other reason for the better performance of the older version while testing AODV. Thanks in advance for any comments Regards Riadh _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 25 06:04:02 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17991 for ; Fri, 25 Oct 2002 06:04:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9PA5o424814 for manet-archive@odin.ietf.org; Fri, 25 Oct 2002 06:05:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PA5ov24811 for ; Fri, 25 Oct 2002 06:05:50 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17983 for ; Fri, 25 Oct 2002 06:03:30 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9wEv24414; Fri, 25 Oct 2002 05:58:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9tBv24302 for ; Fri, 25 Oct 2002 05:55:11 -0400 Received: from cheviot1.ncl.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17683 for ; Fri, 25 Oct 2002 05:52:50 -0400 (EDT) Received: from stavanger (stavanger.ncl.ac.uk [128.240.149.6]) by cheviot1.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id g9P9smd13997; Fri, 25 Oct 2002 10:54:48 +0100 From: "Einar Vollset" To: "'Anshul Gupta'" , Subject: RE: [manet] Multicast Protocol for Ad Hoc Wireless Networks Date: Fri, 25 Oct 2002 10:54:35 +0100 Organization: University of Newcastle upon Tyne Message-ID: <000c01c27c0c$86899310$0695f080@stavanger> 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.3416 In-Reply-To: <00b101c27b9e$08cd80d0$6500a8c0@moon> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Newcastle-MailScanner: Found to be clean (of known viruses) Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Anshul. As you mention, there are several multicast protocols available, and when it comes down to it, which one you choose is often determined by which operating environment you are targeting and various other considerations. That being said, there are several studies which look at the performance (in terms of messaging overhead) and reliability (in terms of packet delivery ratio). Here is one done at UCLA. I think it's fairly comprehensive except it doesn't cover MAODV: A Performance Comparison Study of Ad Hoc Wireless Multicast Protocols: http://citeseer.nj.nec.com/cache/papers/cs/12975/http:zSzzSzwww.ieee-inf ocom.orgzSz2000zSzpaperszSz361.pdf/lee00performance.pdf (cached citeseer copies) As for actual implementations, we implemented a Java, application-level version of ODMRP (On Demand Multicast Routing Protocol), which has performed well for our purposes. If you are interested, the following page describes it in a bit more detail (also allows you to download it): http://www.cs.ncl.ac.uk/people/einar.vollset/home.formal/jomp.html Hope that helps, Einar --------------------------- Einar Vollset PhD Student School of Computing Science University of Newcastle http://vollset.org ---------------------------- > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of > Anshul Gupta > Sent: 24 October 2002 21:44 > To: manet@ietf.org > Subject: [manet] Multicast Protocol for Ad Hoc Wireless Networks > > Hi all, > > I was searching for efficient and reliable multicast protocol for ad hoc > wireless networks on google but I was amazed to see how many are there. > > Which is the most reliable and efficient protocol ? Does anybody has > experience with any of them ? > > Cheers, > Anshul Gupta > > > > > _______________________________________________ > 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-admin@ietf.org Fri Oct 25 06:04:04 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18004 for ; Fri, 25 Oct 2002 06:04:04 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9wEv24414; Fri, 25 Oct 2002 05:58:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9P9tBv24302 for ; Fri, 25 Oct 2002 05:55:11 -0400 Received: from cheviot1.ncl.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17683 for ; Fri, 25 Oct 2002 05:52:50 -0400 (EDT) Received: from stavanger (stavanger.ncl.ac.uk [128.240.149.6]) by cheviot1.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id g9P9smd13997; Fri, 25 Oct 2002 10:54:48 +0100 From: "Einar Vollset" To: "'Anshul Gupta'" , Subject: RE: [manet] Multicast Protocol for Ad Hoc Wireless Networks Date: Fri, 25 Oct 2002 10:54:35 +0100 Organization: University of Newcastle upon Tyne Message-ID: <000c01c27c0c$86899310$0695f080@stavanger> 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.3416 In-Reply-To: <00b101c27b9e$08cd80d0$6500a8c0@moon> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal X-Newcastle-MailScanner: Found to be clean (of known viruses) Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Anshul. As you mention, there are several multicast protocols available, and when it comes down to it, which one you choose is often determined by which operating environment you are targeting and various other considerations. That being said, there are several studies which look at the performance (in terms of messaging overhead) and reliability (in terms of packet delivery ratio). Here is one done at UCLA. I think it's fairly comprehensive except it doesn't cover MAODV: A Performance Comparison Study of Ad Hoc Wireless Multicast Protocols: http://citeseer.nj.nec.com/cache/papers/cs/12975/http:zSzzSzwww.ieee-inf ocom.orgzSz2000zSzpaperszSz361.pdf/lee00performance.pdf (cached citeseer copies) As for actual implementations, we implemented a Java, application-level version of ODMRP (On Demand Multicast Routing Protocol), which has performed well for our purposes. If you are interested, the following page describes it in a bit more detail (also allows you to download it): http://www.cs.ncl.ac.uk/people/einar.vollset/home.formal/jomp.html Hope that helps, Einar --------------------------- Einar Vollset PhD Student School of Computing Science University of Newcastle http://vollset.org ---------------------------- > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of > Anshul Gupta > Sent: 24 October 2002 21:44 > To: manet@ietf.org > Subject: [manet] Multicast Protocol for Ad Hoc Wireless Networks > > Hi all, > > I was searching for efficient and reliable multicast protocol for ad hoc > wireless networks on google but I was amazed to see how many are there. > > Which is the most reliable and efficient protocol ? Does anybody has > experience with any of them ? > > Cheers, > Anshul Gupta > > > > > _______________________________________________ > 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-admin@ietf.org Fri Oct 25 07:45:14 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21017 for ; Fri, 25 Oct 2002 07:45:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PBYMv29623; Fri, 25 Oct 2002 07:34:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PBTjv29303 for ; Fri, 25 Oct 2002 07:29:45 -0400 Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19774 for ; Fri, 25 Oct 2002 07:27:24 -0400 (EDT) Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g9PBTc522542; Fri, 25 Oct 2002 13:29:38 +0200 (MET DST) Message-ID: <00c401c27c1c$31692ca0$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Marwaha Shivanajay" , References: <6330DC96389A924A804F52FA3848930E01234D82@MBXSRV26.stu.nus.edu.sg> Subject: Re: [manet] How to increase packet delivery ratio in MANETs Date: Fri, 25 Oct 2002 13:46:44 +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.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Is not the PDR discrepancy between AODV with link layer notification and AODV with HELLO due to the fact that with the latter one has to wait for a periodic hello to detect link failure and meanwhile packets are lost? Philippe ----- Original Message ----- From: Marwaha Shivanajay To: Sent: Friday, October 25, 2002 5:55 AM Subject: [manet] How to increase packet delivery ratio in MANETs > Dear All, > How would we select routes in MANETs if we want to ensure/meet high > packet delivery ratio (PDR) requirements. Are there any papers which > deal with this. Also are there any papers/mechanisms developed for > achieving higher packet delivery ratio for certain class of traffic > which have specific packet loss requirements. Can we compromise delay to > ensure high PDR in MANETs?? > > (In my view, we need to know the stability of the links in a route to > ensure high packet delivery ratio. For this we may use eiter "HELLO > Messages" or "GPS information". Using HELLO messages has the > disadvantage of more power & bandwidth consumption and NS-2 results have > shown that HELLO messages (when used with AODV) decrease the PDR in the > first place by 5-10% compared to AODV with link layer notification. On > the other hand, GPS assisted routing has constraints working indoors.) > > So how to ensure/meet packet loss requirement (atleast for some classes > of traffic) ? > > Regards, > Shivanajay Marwaha > *********************** > Research Scholar > ECE Dept, NUS, > 10 Kent Ridge Crescent, > Singapore 119260 > *********************** > > -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ > -~-~-~-~-~-~-~-~-~-~ > An expert is someone who can tell you exactly afterwards, why his > prognosis was not correct. > Winston Churchill > -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ > -~-~-~-~-~-~-~-~-~-~ > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 25 07:58:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21473 for ; Fri, 25 Oct 2002 07:58:06 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9PBxu331320 for manet-archive@odin.ietf.org; Fri, 25 Oct 2002 07:59:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PBxuv31317 for ; Fri, 25 Oct 2002 07:59:56 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21457 for ; Fri, 25 Oct 2002 07:57:35 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PBYMv29623; Fri, 25 Oct 2002 07:34:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PBTjv29303 for ; Fri, 25 Oct 2002 07:29:45 -0400 Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19774 for ; Fri, 25 Oct 2002 07:27:24 -0400 (EDT) Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g9PBTc522542; Fri, 25 Oct 2002 13:29:38 +0200 (MET DST) Message-ID: <00c401c27c1c$31692ca0$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Marwaha Shivanajay" , References: <6330DC96389A924A804F52FA3848930E01234D82@MBXSRV26.stu.nus.edu.sg> Subject: Re: [manet] How to increase packet delivery ratio in MANETs Date: Fri, 25 Oct 2002 13:46:44 +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.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Is not the PDR discrepancy between AODV with link layer notification and AODV with HELLO due to the fact that with the latter one has to wait for a periodic hello to detect link failure and meanwhile packets are lost? Philippe ----- Original Message ----- From: Marwaha Shivanajay To: Sent: Friday, October 25, 2002 5:55 AM Subject: [manet] How to increase packet delivery ratio in MANETs > Dear All, > How would we select routes in MANETs if we want to ensure/meet high > packet delivery ratio (PDR) requirements. Are there any papers which > deal with this. Also are there any papers/mechanisms developed for > achieving higher packet delivery ratio for certain class of traffic > which have specific packet loss requirements. Can we compromise delay to > ensure high PDR in MANETs?? > > (In my view, we need to know the stability of the links in a route to > ensure high packet delivery ratio. For this we may use eiter "HELLO > Messages" or "GPS information". Using HELLO messages has the > disadvantage of more power & bandwidth consumption and NS-2 results have > shown that HELLO messages (when used with AODV) decrease the PDR in the > first place by 5-10% compared to AODV with link layer notification. On > the other hand, GPS assisted routing has constraints working indoors.) > > So how to ensure/meet packet loss requirement (atleast for some classes > of traffic) ? > > Regards, > Shivanajay Marwaha > *********************** > Research Scholar > ECE Dept, NUS, > 10 Kent Ridge Crescent, > Singapore 119260 > *********************** > > -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ > -~-~-~-~-~-~-~-~-~-~ > An expert is someone who can tell you exactly afterwards, why his > prognosis was not correct. > Winston Churchill > -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ > -~-~-~-~-~-~-~-~-~-~ > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 25 08:01:08 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21610 for ; Fri, 25 Oct 2002 08:01:08 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9PC2wc31504 for manet-archive@odin.ietf.org; Fri, 25 Oct 2002 08:02:58 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PC2wv31501 for ; Fri, 25 Oct 2002 08:02:58 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21561 for ; Fri, 25 Oct 2002 08:00:37 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PBsSv31045; Fri, 25 Oct 2002 07:54:28 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PBrWv30982 for ; Fri, 25 Oct 2002 07:53:32 -0400 Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21261 for ; Fri, 25 Oct 2002 07:51:11 -0400 (EDT) Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g9PBrE523495; Fri, 25 Oct 2002 13:53:15 +0200 (MET DST) Message-ID: <00ce01c27c1f$6d102440$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Liangping Ma" , "Pete Sholander" Cc: References: Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? Date: Fri, 25 Oct 2002 14:09:52 +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.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I think most simple mathematical results on TCP are under the assumption of an independent packet loss rate, therefore very close to the cases you are looking for. In this case the window size evolution is a "simple" Markov process, for which one derives stationary results about the window size distribution and packet retransmission numbers, throughput, etc. There is a nice paper of Savari and Telatar: "the behavior of stochastic processes arising in window protocols" (ISIT 99). The cases with a single TCP with buffer congestion and cross interference with other UDP traffic are more intricate even restricted on wired networks, a paper of Baccelli and Hong: "TCP is max-plus linear" (SIGCOM2000). In particular there are some chaotic effects that make the TCP process very sensitive to small variations in the initial conditions. The case where several TCP connections share the same links became recently an hot issue because of long term dependencies in internet traffic. One funny outcome is that asymptotically each TCP connection behaves as if it was experiencing an independent packet loss rate, exactly like the wireless links case (although the analysis is carried in a wired network and loss ocur locally in router buffer). You can take a look at our paper: http://www.inria.fr/rrrt/rr-4478.html Philippe ----- Original Message ----- From: Liangping Ma To: Pete Sholander Cc: Sent: Wednesday, October 23, 2002 3:48 PM Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? > Hi, Pete, > > I think you referred to the paper "Modeling TCP throughput: a simple > model and its empirical validation" by J. Padhye, V. Firoiu, D. Towsley > and J. Kurose in ACM SIGCOMM'98. This paper is easy to be found on the > web. > > In fact, I am looking for something a little bit different from this > paper if it exists at all. In the paper above, the analysis is for wired > networks, where packet loss is due to network congestion. But in the > _mobile_ IP networks, there is one hop of wireless link in a TCP > conneciton. The packet loss is affected also by the signal-to-noise ratio > and other factors in the wireless environment. I think these factors > should be incorporated to the so called TCP formula. > > > Sincerely yours, > Liangping Ma > > > On Wed, 23 Oct 2002, Pete Sholander wrote: > > > Look at SIGCOMM '98. There was a oft-cited paper on a mathematical > > analysis of TCP throughput versus RTT and packet-loss rate. (I can't > > recall the author's name.) You could then do a lit-search to see who > > subsequently referenced that work. > > > > >>> Liangping Ma 10/22/02 06:51PM >>> > > Hello, > > > > Does anyone know if there is already any work on mathematical > > analysis of TCP over mobile IP networks? As far as I know, there > > are some simulation-based studies about TCP over mobile IP networks. > > But I am looking for deterministic/stochastic modeling of TCP in > > mobile IP networks, which have one hop of wireless link as compared > > to the conventional IP networks. > > > > Thanks! > > > > Liangping Ma > > > > ----------------------- > > > > ECE Dept. > > University of Delaware > > Newark, Delaware, 19716 > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 25 08:01:10 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21624 for ; Fri, 25 Oct 2002 08:01:10 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PBsSv31045; Fri, 25 Oct 2002 07:54:28 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PBrWv30982 for ; Fri, 25 Oct 2002 07:53:32 -0400 Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21261 for ; Fri, 25 Oct 2002 07:51:11 -0400 (EDT) Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g9PBrE523495; Fri, 25 Oct 2002 13:53:15 +0200 (MET DST) Message-ID: <00ce01c27c1f$6d102440$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Liangping Ma" , "Pete Sholander" Cc: References: Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? Date: Fri, 25 Oct 2002 14:09:52 +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.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I think most simple mathematical results on TCP are under the assumption of an independent packet loss rate, therefore very close to the cases you are looking for. In this case the window size evolution is a "simple" Markov process, for which one derives stationary results about the window size distribution and packet retransmission numbers, throughput, etc. There is a nice paper of Savari and Telatar: "the behavior of stochastic processes arising in window protocols" (ISIT 99). The cases with a single TCP with buffer congestion and cross interference with other UDP traffic are more intricate even restricted on wired networks, a paper of Baccelli and Hong: "TCP is max-plus linear" (SIGCOM2000). In particular there are some chaotic effects that make the TCP process very sensitive to small variations in the initial conditions. The case where several TCP connections share the same links became recently an hot issue because of long term dependencies in internet traffic. One funny outcome is that asymptotically each TCP connection behaves as if it was experiencing an independent packet loss rate, exactly like the wireless links case (although the analysis is carried in a wired network and loss ocur locally in router buffer). You can take a look at our paper: http://www.inria.fr/rrrt/rr-4478.html Philippe ----- Original Message ----- From: Liangping Ma To: Pete Sholander Cc: Sent: Wednesday, October 23, 2002 3:48 PM Subject: Re: [manet] Mathematical analysis of TCP over mobile IP networks? > Hi, Pete, > > I think you referred to the paper "Modeling TCP throughput: a simple > model and its empirical validation" by J. Padhye, V. Firoiu, D. Towsley > and J. Kurose in ACM SIGCOMM'98. This paper is easy to be found on the > web. > > In fact, I am looking for something a little bit different from this > paper if it exists at all. In the paper above, the analysis is for wired > networks, where packet loss is due to network congestion. But in the > _mobile_ IP networks, there is one hop of wireless link in a TCP > conneciton. The packet loss is affected also by the signal-to-noise ratio > and other factors in the wireless environment. I think these factors > should be incorporated to the so called TCP formula. > > > Sincerely yours, > Liangping Ma > > > On Wed, 23 Oct 2002, Pete Sholander wrote: > > > Look at SIGCOMM '98. There was a oft-cited paper on a mathematical > > analysis of TCP throughput versus RTT and packet-loss rate. (I can't > > recall the author's name.) You could then do a lit-search to see who > > subsequently referenced that work. > > > > >>> Liangping Ma 10/22/02 06:51PM >>> > > Hello, > > > > Does anyone know if there is already any work on mathematical > > analysis of TCP over mobile IP networks? As far as I know, there > > are some simulation-based studies about TCP over mobile IP networks. > > But I am looking for deterministic/stochastic modeling of TCP in > > mobile IP networks, which have one hop of wireless link as compared > > to the conventional IP networks. > > > > Thanks! > > > > Liangping Ma > > > > ----------------------- > > > > ECE Dept. > > University of Delaware > > Newark, Delaware, 19716 > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 25 17:10:46 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12087 for ; Fri, 25 Oct 2002 17:10:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9PLCd200320 for manet-archive@odin.ietf.org; Fri, 25 Oct 2002 17:12:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PLCdv00317 for ; Fri, 25 Oct 2002 17:12:39 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12024 for ; Fri, 25 Oct 2002 17:10:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PL4Lv31904; Fri, 25 Oct 2002 17:04:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PL0bv31586 for ; Fri, 25 Oct 2002 17:00:37 -0400 Received: from strix.ciens.ucv.ve (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11708 for ; Fri, 25 Oct 2002 16:58:08 -0400 (EDT) Received: from dircompucv2.strix.ciens.ucv.ve (dircompucv.ciens.ucv.ve [150.185.75.85]) by strix.ciens.ucv.ve (SGI-8.9.3/8.9.3) with ESMTP id SAA39055 for ; Fri, 25 Oct 2002 18:01:12 -0700 (PDT) Message-Id: <5.0.0.25.0.20021025145519.024432b0@strix.ciens.ucv.ve> X-Sender: dcobos@strix.ciens.ucv.ve X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 25 Oct 2002 17:03:07 -0400 To: manet@ietf.org From: Denis Cobos Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [manet] !!About Addresing of MANET!! Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi everybody Iam writing from Venezuela, and my english is not very good... I'm sorry do anyone of you know about a good reference or paper that explain the consideration at addressing about the MANET's Protocols, also the cause about having always the same address while moving through the MANET. Thanks :-) Denis Cobos Central University of Venezuela sciences faculty Computation's School ICARO _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 25 17:17:31 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12382 for ; Fri, 25 Oct 2002 17:17:31 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PL4Lv31904; Fri, 25 Oct 2002 17:04:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9PL0bv31586 for ; Fri, 25 Oct 2002 17:00:37 -0400 Received: from strix.ciens.ucv.ve (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11708 for ; Fri, 25 Oct 2002 16:58:08 -0400 (EDT) Received: from dircompucv2.strix.ciens.ucv.ve (dircompucv.ciens.ucv.ve [150.185.75.85]) by strix.ciens.ucv.ve (SGI-8.9.3/8.9.3) with ESMTP id SAA39055 for ; Fri, 25 Oct 2002 18:01:12 -0700 (PDT) Message-Id: <5.0.0.25.0.20021025145519.024432b0@strix.ciens.ucv.ve> X-Sender: dcobos@strix.ciens.ucv.ve X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Fri, 25 Oct 2002 17:03:07 -0400 To: manet@ietf.org From: Denis Cobos Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [manet] !!About Addresing of MANET!! Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi everybody Iam writing from Venezuela, and my english is not very good... I'm sorry do anyone of you know about a good reference or paper that explain the consideration at addressing about the MANET's Protocols, also the cause about having always the same address while moving through the MANET. Thanks :-) Denis Cobos Central University of Venezuela sciences faculty Computation's School ICARO _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Fri Oct 25 22:36:43 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19228 for ; Fri, 25 Oct 2002 22:36:43 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q2UYv14408; Fri, 25 Oct 2002 22:30:34 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q2S4v14335 for ; Fri, 25 Oct 2002 22:28:04 -0400 Received: from noya.bupt.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18767 for ; Fri, 25 Oct 2002 22:25:34 -0400 (EDT) Received: from CHUNJBUPT ([202.204.4.35]) by noya.bupt.edu.cn (8.11.4/8.11.4) with SMTP id g9Q2RpF00195 for ; Sat, 26 Oct 2002 10:27:52 +0800 (CST) Message-ID: <011a01c27c97$5e9ba600$2304ccca@CHUNJBUPT> From: "chunj_sohu" To: Date: Sat, 26 Oct 2002 10:28:23 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0117_01C27CDA.695973E0" 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 Subject: [manet] Is routing protocol independent of routing protocol in manet? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0117_01C27CDA.695973E0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 DQo= ------=_NextPart_000_0117_01C27CDA.695973E0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPiZuYnNwOzwvRElWPjwvQk9EWT48L0hUTUw+DQo= ------=_NextPart_000_0117_01C27CDA.695973E0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Oct 25 22:45:01 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19446 for ; Fri, 25 Oct 2002 22:45:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9Q2kxe15474 for manet-archive@odin.ietf.org; Fri, 25 Oct 2002 22:46:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q2kxv15471 for ; Fri, 25 Oct 2002 22:46:59 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19416 for ; Fri, 25 Oct 2002 22:44:30 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q2UYv14408; Fri, 25 Oct 2002 22:30:34 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q2S4v14335 for ; Fri, 25 Oct 2002 22:28:04 -0400 Received: from noya.bupt.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA18767 for ; Fri, 25 Oct 2002 22:25:34 -0400 (EDT) Received: from CHUNJBUPT ([202.204.4.35]) by noya.bupt.edu.cn (8.11.4/8.11.4) with SMTP id g9Q2RpF00195 for ; Sat, 26 Oct 2002 10:27:52 +0800 (CST) Message-ID: <011a01c27c97$5e9ba600$2304ccca@CHUNJBUPT> From: "chunj_sohu" To: Date: Sat, 26 Oct 2002 10:28:23 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0117_01C27CDA.695973E0" 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 Subject: [manet] Is routing protocol independent of routing protocol in manet? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0117_01C27CDA.695973E0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 DQo= ------=_NextPart_000_0117_01C27CDA.695973E0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w MC4yNjAwLjAiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9E WSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPiZuYnNwOzwvRElWPjwvQk9EWT48L0hUTUw+DQo= ------=_NextPart_000_0117_01C27CDA.695973E0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sat Oct 26 00:24:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21334 for ; Sat, 26 Oct 2002 00:24:07 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q4H1v19472; Sat, 26 Oct 2002 00:17:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q4Fov19450 for ; Sat, 26 Oct 2002 00:15:50 -0400 Received: from ims21.stu.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21129 for ; Sat, 26 Oct 2002 00:13:19 -0400 (EDT) Received: from mbxsrv26.stu.nus.edu.sg ([137.132.14.236]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.4905); Sat, 26 Oct 2002 12:15:35 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: RE: [manet] How to increase packet delivery ratio in MANETs Date: Sat, 26 Oct 2002 12:15:34 +0800 Message-ID: <6330DC96389A924A804F52FA3848930E703D9A@MBXSRV26.stu.nus.edu.sg> Thread-Topic: [manet] How to increase packet delivery ratio in MANETs Thread-Index: AcJ8GdDOhqpnM1L/SWugHFFxzIPNiQAe0r3w From: "Marwaha Shivanajay" To: , Cc: "Dipti Srinivasan" , "Tham Chen Khong" , "Marwaha Shivanajay" X-OriginalArrivalTime: 26 Oct 2002 04:15:35.0037 (UTC) FILETIME=[54E2F2D0:01C27CA6] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9Q4Fov19451 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit The reason seems to be correct, that the packets will be dropped untill the link failure is detected via periodic HELLO beacons. Additionally, HELLO messages consume extra bandwidth & battery power. An advantage of using periodic HELLO beacons is that nodes know their neighbors & the respective link stabilities (from signal strength of the received beacons) which can be used for selecting stable links in a route (this should decrease pkt drop). I'm not too sure how fast and robust is LL notification, someone may kindly explain or give some pointers. A small doubt in my mind about LL responding quickly as against periodic HELLO beacons: In case there is no mobility but very high traffic exists, will the LL permanently report LL-errors because it couldn't obtain the medium due to high traffic and this may unneseccarily trigger route discovery by AODV although no node is moving???? Regards, Shivanajay Marwaha ****************************** Research Scholar Elec. & Comp Eng. Dept., National Univ. of S'pore (NUS) 10 Kent Ridge Crescent, Singapore 119260 ****************************** The pessimist complains about the wind; the optimist expects it to change; the realist adjusts the sails. -----Original Message----- From: Philippe Jacquet [mailto:philippe.jacquet@inria.fr] Sent: Friday, October 25, 2002 7:47 PM To: Marwaha Shivanajay; manet@ietf.org Subject: Re: [manet] How to increase packet delivery ratio in MANETs Is not the PDR discrepancy between AODV with link layer notification and AODV with HELLO due to the fact that with the latter one has to wait for a periodic hello to detect link failure and meanwhile packets are lost? Philippe ----- Original Message ----- From: Marwaha Shivanajay To: Sent: Friday, October 25, 2002 5:55 AM Subject: [manet] How to increase packet delivery ratio in MANETs > Dear All, > How would we select routes in MANETs if we want to ensure/meet high > packet delivery ratio (PDR) requirements. Are there any papers which > deal with this. Also are there any papers/mechanisms developed for > achieving higher packet delivery ratio for certain class of traffic > which have specific packet loss requirements. Can we compromise delay > to ensure high PDR in MANETs?? > > (In my view, we need to know the stability of the links in a route to > ensure high packet delivery ratio. For this we may use eiter "HELLO > Messages" or "GPS information". Using HELLO messages has the > disadvantage of more power & bandwidth consumption and NS-2 results > have shown that HELLO messages (when used with AODV) decrease the PDR > in the first place by 5-10% compared to AODV with link layer > notification. On the other hand, GPS assisted routing has constraints > working indoors.) > > So how to ensure/meet packet loss requirement (atleast for some > classes of traffic) ? > > Regards, > Shivanajay Marwaha > *********************** > Research Scholar > ECE Dept, NUS, > 10 Kent Ridge Crescent, > Singapore 119260 > *********************** > > -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ > -~ > -~-~-~-~-~-~-~-~-~-~ > An expert is someone who can tell you exactly afterwards, why his > prognosis was not correct. > Winston Churchill > -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ > -~-~-~-~-~-~-~-~-~-~ > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Oct 26 00:29:58 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21449 for ; Sat, 26 Oct 2002 00:29:58 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9Q4Vte19823 for manet-archive@odin.ietf.org; Sat, 26 Oct 2002 00:31:55 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q4Vtv19820 for ; Sat, 26 Oct 2002 00:31:55 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21446 for ; Sat, 26 Oct 2002 00:29:26 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q4H1v19472; Sat, 26 Oct 2002 00:17:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q4Fov19450 for ; Sat, 26 Oct 2002 00:15:50 -0400 Received: from ims21.stu.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21129 for ; Sat, 26 Oct 2002 00:13:19 -0400 (EDT) Received: from mbxsrv26.stu.nus.edu.sg ([137.132.14.236]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.4905); Sat, 26 Oct 2002 12:15:35 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Subject: RE: [manet] How to increase packet delivery ratio in MANETs Date: Sat, 26 Oct 2002 12:15:34 +0800 Message-ID: <6330DC96389A924A804F52FA3848930E703D9A@MBXSRV26.stu.nus.edu.sg> Thread-Topic: [manet] How to increase packet delivery ratio in MANETs Thread-Index: AcJ8GdDOhqpnM1L/SWugHFFxzIPNiQAe0r3w From: "Marwaha Shivanajay" To: , Cc: "Dipti Srinivasan" , "Tham Chen Khong" , "Marwaha Shivanajay" X-OriginalArrivalTime: 26 Oct 2002 04:15:35.0037 (UTC) FILETIME=[54E2F2D0:01C27CA6] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9Q4Fov19451 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit The reason seems to be correct, that the packets will be dropped untill the link failure is detected via periodic HELLO beacons. Additionally, HELLO messages consume extra bandwidth & battery power. An advantage of using periodic HELLO beacons is that nodes know their neighbors & the respective link stabilities (from signal strength of the received beacons) which can be used for selecting stable links in a route (this should decrease pkt drop). I'm not too sure how fast and robust is LL notification, someone may kindly explain or give some pointers. A small doubt in my mind about LL responding quickly as against periodic HELLO beacons: In case there is no mobility but very high traffic exists, will the LL permanently report LL-errors because it couldn't obtain the medium due to high traffic and this may unneseccarily trigger route discovery by AODV although no node is moving???? Regards, Shivanajay Marwaha ****************************** Research Scholar Elec. & Comp Eng. Dept., National Univ. of S'pore (NUS) 10 Kent Ridge Crescent, Singapore 119260 ****************************** The pessimist complains about the wind; the optimist expects it to change; the realist adjusts the sails. -----Original Message----- From: Philippe Jacquet [mailto:philippe.jacquet@inria.fr] Sent: Friday, October 25, 2002 7:47 PM To: Marwaha Shivanajay; manet@ietf.org Subject: Re: [manet] How to increase packet delivery ratio in MANETs Is not the PDR discrepancy between AODV with link layer notification and AODV with HELLO due to the fact that with the latter one has to wait for a periodic hello to detect link failure and meanwhile packets are lost? Philippe ----- Original Message ----- From: Marwaha Shivanajay To: Sent: Friday, October 25, 2002 5:55 AM Subject: [manet] How to increase packet delivery ratio in MANETs > Dear All, > How would we select routes in MANETs if we want to ensure/meet high > packet delivery ratio (PDR) requirements. Are there any papers which > deal with this. Also are there any papers/mechanisms developed for > achieving higher packet delivery ratio for certain class of traffic > which have specific packet loss requirements. Can we compromise delay > to ensure high PDR in MANETs?? > > (In my view, we need to know the stability of the links in a route to > ensure high packet delivery ratio. For this we may use eiter "HELLO > Messages" or "GPS information". Using HELLO messages has the > disadvantage of more power & bandwidth consumption and NS-2 results > have shown that HELLO messages (when used with AODV) decrease the PDR > in the first place by 5-10% compared to AODV with link layer > notification. On the other hand, GPS assisted routing has constraints > working indoors.) > > So how to ensure/meet packet loss requirement (atleast for some > classes of traffic) ? > > Regards, > Shivanajay Marwaha > *********************** > Research Scholar > ECE Dept, NUS, > 10 Kent Ridge Crescent, > Singapore 119260 > *********************** > > -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ > -~ > -~-~-~-~-~-~-~-~-~-~ > An expert is someone who can tell you exactly afterwards, why his > prognosis was not correct. > Winston Churchill > -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ > -~-~-~-~-~-~-~-~-~-~ > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Oct 26 05:56:40 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04107 for ; Sat, 26 Oct 2002 05:56:40 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9Q9wSP08682 for manet-archive@odin.ietf.org; Sat, 26 Oct 2002 05:58:28 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q9wSv08679 for ; Sat, 26 Oct 2002 05:58:28 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04100 for ; Sat, 26 Oct 2002 05:56:09 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q9odv08520; Sat, 26 Oct 2002 05:50:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q9lNv08444 for ; Sat, 26 Oct 2002 05:47:23 -0400 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03969 for ; Sat, 26 Oct 2002 05:45:03 -0400 (EDT) Message-Id: <200210260945.FAA03969@ietf.org> Received: (eyou send program); Sat, 26 Oct 2002 17:45:15 +0800 Received: from unknown (HELO yangwh) (unknown@166.111.67.88) by 166.111.8.16 with SMTP; Sat, 26 Oct 2002 17:45:15 +0800 Date: Sat, 26 Oct 2002 17:48:25 +0800 From: "yang weihua" To: "manet@ietf.org" X-mailer: Foxmail 4.1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9Q9lNv08445 Subject: [manet] About ifqueue length Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit everyone£¬ Does anybody know how to get the ifqueue(between MAC and LL) length from the route agent? I have attempted to get the value by doing this in the AODV C++ source code: queue_len=agent->ifqueue->getLen(); where agent is the aodv route agent. But to my disappointment, the result always remained to be zero! what's the problem? Appreciate your any help! Best regards! ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yang weihua ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yangwh00@mails.tsinghua.edu.cn ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-26 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sat Oct 26 05:56:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04120 for ; Sat, 26 Oct 2002 05:56:42 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q9odv08520; Sat, 26 Oct 2002 05:50:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9Q9lNv08444 for ; Sat, 26 Oct 2002 05:47:23 -0400 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03969 for ; Sat, 26 Oct 2002 05:45:03 -0400 (EDT) Message-Id: <200210260945.FAA03969@ietf.org> Received: (eyou send program); Sat, 26 Oct 2002 17:45:15 +0800 Received: from unknown (HELO yangwh) (unknown@166.111.67.88) by 166.111.8.16 with SMTP; Sat, 26 Oct 2002 17:45:15 +0800 Date: Sat, 26 Oct 2002 17:48:25 +0800 From: "yang weihua" To: "manet@ietf.org" X-mailer: Foxmail 4.1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9Q9lNv08445 Subject: [manet] About ifqueue length Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit everyone£¬ Does anybody know how to get the ifqueue(between MAC and LL) length from the route agent? I have attempted to get the value by doing this in the AODV C++ source code: queue_len=agent->ifqueue->getLen(); where agent is the aodv route agent. But to my disappointment, the result always remained to be zero! what's the problem? Appreciate your any help! Best regards! ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yang weihua ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yangwh00@mails.tsinghua.edu.cn ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-26 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sat Oct 26 09:19:54 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06225 for ; Sat, 26 Oct 2002 09:19:54 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9QDDLv15976; Sat, 26 Oct 2002 09:13:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9QDBSv15937 for ; Sat, 26 Oct 2002 09:11:28 -0400 Received: from gwserver.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06121 for ; Sat, 26 Oct 2002 09:08:58 -0400 (EDT) Received: from swl1002 ([172.16.3.193]) by gwserver.icr.a-star.edu.sg; Sat, 26 Oct 2002 21:05:43 +0800 Message-ID: <004501c27cf0$5abe2040$c10310ac@icr.astar.edu.sg> Reply-To: "Ankur Jain" From: "Ankur Jain" To: , "Denis Cobos" References: <5.0.0.25.0.20021025145519.024432b0@strix.ciens.ucv.ve> Subject: Re: [manet] !!About Addresing of MANET!! Date: Sat, 26 Oct 2002 21:05:08 +0800 Organization: Institute for Communications Research, Singapore MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi Dennis If you are interested in addressing in Manets, you can have a look at the following papers. 1. "Weak Duplicate Address Detection in Mobile Ad Hoc Networks" by Nitin H. Vaidya. 2. "An IP Address Configuration Algorithm for Zeroconf. Mobile Multi-hop Ad-Hoc Networks" by Mesut Gunes, Jorg Reibel. 3. "IP address autoconfiguration for ad hoc networks" by C. E. Perkins, E. M. Royer, and S. R. Das (Internet Draft) 4. "MANETconf: Configuration of hosts in a mobile ad hoc network" by S. Nesargi and R. Prakash (INFOCOM 2002) 5. "Efficient network layer addressing for mobile ad hoc networks" by J. Boleng (Colorado School of Mines) You can find other papers by refering to the references written in these papers. Regards Ankur Jain ----- Original Message ----- From: Denis Cobos To: Sent: Saturday, October 26, 2002 5:03 AM Subject: [manet] !!About Addresing of MANET!! > > Hi everybody > Iam writing from Venezuela, and my english is not very good... I'm sorry > > do anyone of you know about a good reference or paper that explain the > consideration at addressing > about the MANET's Protocols, also the cause about having always the same > address while moving through the MANET. > > Thanks :-) > Denis Cobos > Central University of Venezuela > sciences faculty > Computation's School > ICARO > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Oct 26 09:30:58 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06592 for ; Sat, 26 Oct 2002 09:30:58 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9QDWog16379 for manet-archive@odin.ietf.org; Sat, 26 Oct 2002 09:32:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9QDWlv16374 for ; Sat, 26 Oct 2002 09:32:47 -0400 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06589 for ; Sat, 26 Oct 2002 09:30:24 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9QDDLv15976; Sat, 26 Oct 2002 09:13:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9QDBSv15937 for ; Sat, 26 Oct 2002 09:11:28 -0400 Received: from gwserver.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06121 for ; Sat, 26 Oct 2002 09:08:58 -0400 (EDT) Received: from swl1002 ([172.16.3.193]) by gwserver.icr.a-star.edu.sg; Sat, 26 Oct 2002 21:05:43 +0800 Message-ID: <004501c27cf0$5abe2040$c10310ac@icr.astar.edu.sg> Reply-To: "Ankur Jain" From: "Ankur Jain" To: , "Denis Cobos" References: <5.0.0.25.0.20021025145519.024432b0@strix.ciens.ucv.ve> Subject: Re: [manet] !!About Addresing of MANET!! Date: Sat, 26 Oct 2002 21:05:08 +0800 Organization: Institute for Communications Research, Singapore MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Dennis If you are interested in addressing in Manets, you can have a look at the following papers. 1. "Weak Duplicate Address Detection in Mobile Ad Hoc Networks" by Nitin H. Vaidya. 2. "An IP Address Configuration Algorithm for Zeroconf. Mobile Multi-hop Ad-Hoc Networks" by Mesut Gunes, Jorg Reibel. 3. "IP address autoconfiguration for ad hoc networks" by C. E. Perkins, E. M. Royer, and S. R. Das (Internet Draft) 4. "MANETconf: Configuration of hosts in a mobile ad hoc network" by S. Nesargi and R. Prakash (INFOCOM 2002) 5. "Efficient network layer addressing for mobile ad hoc networks" by J. Boleng (Colorado School of Mines) You can find other papers by refering to the references written in these papers. Regards Ankur Jain ----- Original Message ----- From: Denis Cobos To: Sent: Saturday, October 26, 2002 5:03 AM Subject: [manet] !!About Addresing of MANET!! > > Hi everybody > Iam writing from Venezuela, and my english is not very good... I'm sorry > > do anyone of you know about a good reference or paper that explain the > consideration at addressing > about the MANET's Protocols, also the cause about having always the same > address while moving through the MANET. > > Thanks :-) > Denis Cobos > Central University of Venezuela > sciences faculty > Computation's School > ICARO > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Oct 27 22:18:56 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14813 for ; Sun, 27 Oct 2002 22:18:56 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9S3KtW17520 for manet-archive@odin.ietf.org; Sun, 27 Oct 2002 22:20:55 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S3Ktv17517 for ; Sun, 27 Oct 2002 22:20:55 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14803 for ; Sun, 27 Oct 2002 22:18:25 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S3Bev17270; Sun, 27 Oct 2002 22:11:40 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S35Hv16616 for ; Sun, 27 Oct 2002 22:05:17 -0500 Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14594 for ; Sun, 27 Oct 2002 22:02:47 -0500 (EST) Received: from photon.ece.cornell.edu (photon.ece.cornell.edu [128.84.81.138]) by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id g9S358529921 for ; Sun, 27 Oct 2002 22:05:08 -0500 Date: Sun, 27 Oct 2002 21:50:40 -0500 (EST) From: Edward Hua X-X-Sender: eyh5@photon.ece.cornell.edu To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] wireless interface not brought up in a Gateway Solo1450 SE laptop Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I have two Gateway laptops. One is Solo 1400 SE (node01), and the other Solo 1450 SE (node02). Both have RedHat 7.3 installed (with Linux kernel version 2.4.18-3). I also have two Cisco Aironet 350 wireless PC cards and use them on the laptops. I'm working on integrating a routing algorithm, Zone Routing Protocol (ZRP), into a testbed called Ad hoc Performance Evaluation (APE). APE is nothing but a stripped-down version of the Linux kernl, including only the essential commands and some Wireless Tools (iwconfig, etc.). Of course, APE-related files are bundled into the kernel, and the whole thing is called an APE distribution package. The idea is that once a distribution package is created (it's nothing but a .zip file) in one laptop, it can be transferred to the other laptops and installed there. Then these laptops can be used to form an ad hoc network, and you can run tests using scripts written in APE to gather and analyze the data. My problems are the following. Following the APE developers' manual, I was able to create the APE distrubtion package on node01. I then transferred it to node02, and installed it there. Then, on both machines, I booted into the APE mode (which is essentially Run Level 3 in the Linux mode). I then ran an APE-provided script, which would bring up the PCMCIAinterface (with the Aironet card), allow you to choose a routing algorithm you wish to test (ZRP, OLSR, AODV, etc.), and initiate the test. Anyways, what happened after I ran this script is that only node01 brought up the PCMCIA interface (eth0), whereas node02, with all the identical APE-related system files as node01 uses, did not. I then took a different approach: I created the APE distribution package on node02 and transferred it to node01 to be installed. Yet this time, result was the same: node01 could bring up the wireless PC card interface with no problem, and node02 was still unable to do that. I did a number of trials, and installed and re-installed Linux on both laptops a couple times, but couldn't find out what was wrong with node02 not being able to bring up the wireless interface. It must be said, however, that in the Linux mode in both machines, the wireless interface was brought up normally without a problem. One error message that I got in the APE mode on node02 that is related to my problem is: cs: socket 0 timed out during rest Further investigation shows that this error message comes up when a module called ds (i.e., is installed (insmod ds, which is done by the APE script). But I don't know anything about ds, and am not familiar with the kernel source code either. Does anybody have an idea as to what might have caused my problem of not getting the wireless interface up in the Solo 1450SE in the APE mode? Thanks. -Ed _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Sun Oct 27 22:19:14 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14827 for ; Sun, 27 Oct 2002 22:19:14 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S3Bev17270; Sun, 27 Oct 2002 22:11:40 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S35Hv16616 for ; Sun, 27 Oct 2002 22:05:17 -0500 Received: from memphis.ece.cornell.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14594 for ; Sun, 27 Oct 2002 22:02:47 -0500 (EST) Received: from photon.ece.cornell.edu (photon.ece.cornell.edu [128.84.81.138]) by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id g9S358529921 for ; Sun, 27 Oct 2002 22:05:08 -0500 Date: Sun, 27 Oct 2002 21:50:40 -0500 (EST) From: Edward Hua X-X-Sender: eyh5@photon.ece.cornell.edu To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] wireless interface not brought up in a Gateway Solo1450 SE laptop Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I have two Gateway laptops. One is Solo 1400 SE (node01), and the other Solo 1450 SE (node02). Both have RedHat 7.3 installed (with Linux kernel version 2.4.18-3). I also have two Cisco Aironet 350 wireless PC cards and use them on the laptops. I'm working on integrating a routing algorithm, Zone Routing Protocol (ZRP), into a testbed called Ad hoc Performance Evaluation (APE). APE is nothing but a stripped-down version of the Linux kernl, including only the essential commands and some Wireless Tools (iwconfig, etc.). Of course, APE-related files are bundled into the kernel, and the whole thing is called an APE distribution package. The idea is that once a distribution package is created (it's nothing but a .zip file) in one laptop, it can be transferred to the other laptops and installed there. Then these laptops can be used to form an ad hoc network, and you can run tests using scripts written in APE to gather and analyze the data. My problems are the following. Following the APE developers' manual, I was able to create the APE distrubtion package on node01. I then transferred it to node02, and installed it there. Then, on both machines, I booted into the APE mode (which is essentially Run Level 3 in the Linux mode). I then ran an APE-provided script, which would bring up the PCMCIAinterface (with the Aironet card), allow you to choose a routing algorithm you wish to test (ZRP, OLSR, AODV, etc.), and initiate the test. Anyways, what happened after I ran this script is that only node01 brought up the PCMCIA interface (eth0), whereas node02, with all the identical APE-related system files as node01 uses, did not. I then took a different approach: I created the APE distribution package on node02 and transferred it to node01 to be installed. Yet this time, result was the same: node01 could bring up the wireless PC card interface with no problem, and node02 was still unable to do that. I did a number of trials, and installed and re-installed Linux on both laptops a couple times, but couldn't find out what was wrong with node02 not being able to bring up the wireless interface. It must be said, however, that in the Linux mode in both machines, the wireless interface was brought up normally without a problem. One error message that I got in the APE mode on node02 that is related to my problem is: cs: socket 0 timed out during rest Further investigation shows that this error message comes up when a module called ds (i.e., is installed (insmod ds, which is done by the APE script). But I don't know anything about ds, and am not familiar with the kernel source code either. Does anybody have an idea as to what might have caused my problem of not getting the wireless interface up in the Solo 1450SE in the APE mode? Thanks. -Ed _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 28 00:11:49 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16918 for ; Mon, 28 Oct 2002 00:11:49 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9S5DnO22542 for manet-archive@odin.ietf.org; Mon, 28 Oct 2002 00:13:49 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S5Dnv22539 for ; Mon, 28 Oct 2002 00:13:49 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16909 for ; Mon, 28 Oct 2002 00:11:17 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S55sv21533; Mon, 28 Oct 2002 00:05:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S4tvv21264 for ; Sun, 27 Oct 2002 23:55:57 -0500 Received: from bjapp5.163.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16529 for ; Sun, 27 Oct 2002 23:53:21 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by bjapp5.163.net (Postfix) with SMTP id D92E21CB0887B for ; Mon, 28 Oct 2002 12:55:29 +0800 (CST) Received: from befine (unknown [211.71.13.13]) by bjapp5.163.net (Coremail) with SMTP id fAEAAEDDvD0uNA0N.1 for ; Mon, 28 Oct 2002 12:55:29 +0800 (CST) Date: Mon, 28 Oct 2002 12:53:44 +0800 From: "Harry" Reply-To: hr_befine@163.net To: MANET mail list X-mailer: Foxmail 4.1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Message-Id: <20021028045529.D92E21CB0887B@bjapp5.163.net> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9S4tvv21265 Subject: [manet] Any special isssues on MANET? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hi, Is there anyone knowing some journals or magazines focusing on MANETs? Who are so kind to list them here. thank u so much! ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Harry ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-28 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 28 00:11:50 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16933 for ; Mon, 28 Oct 2002 00:11:50 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S55sv21533; Mon, 28 Oct 2002 00:05:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S4tvv21264 for ; Sun, 27 Oct 2002 23:55:57 -0500 Received: from bjapp5.163.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16529 for ; Sun, 27 Oct 2002 23:53:21 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by bjapp5.163.net (Postfix) with SMTP id D92E21CB0887B for ; Mon, 28 Oct 2002 12:55:29 +0800 (CST) Received: from befine (unknown [211.71.13.13]) by bjapp5.163.net (Coremail) with SMTP id fAEAAEDDvD0uNA0N.1 for ; Mon, 28 Oct 2002 12:55:29 +0800 (CST) Date: Mon, 28 Oct 2002 12:53:44 +0800 From: "Harry" Reply-To: hr_befine@163.net To: MANET mail list X-mailer: Foxmail 4.1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Message-Id: <20021028045529.D92E21CB0887B@bjapp5.163.net> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9S4tvv21265 Subject: [manet] Any special isssues on MANET? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit hi, Is there anyone knowing some journals or magazines focusing on MANETs? Who are so kind to list them here. thank u so much! ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Harry ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-28 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 28 00:44:51 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17887 for ; Mon, 28 Oct 2002 00:44:51 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S5cFv23765; Mon, 28 Oct 2002 00:38:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S5UWv23047 for ; Mon, 28 Oct 2002 00:30:32 -0500 Received: from gwserver.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17380 for ; Mon, 28 Oct 2002 00:28:00 -0500 (EST) Received: from swl1002 ([172.16.3.193]) by gwserver.icr.a-star.edu.sg; Mon, 28 Oct 2002 13:24:44 +0800 Message-ID: <005401c27e42$52a0b3c0$c10310ac@icr.astar.edu.sg> Reply-To: "Ankur Jain" From: "Ankur Jain" To: References: Date: Mon, 28 Oct 2002 13:24:37 +0800 Organization: Institute for Communications Research, Singapore MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Subject: [manet] Directional Antennas and Multipath Routing Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hi, Does anybody working on Directional Antennas with Multipath Routing? Please tell me who all are currently working on this and where I can find some good papers. Also, is there any actual device like Lucent's Orinoco card which has directional antenna and the modified MAC? Regards Ankur ~...~...~...~...~...~...~...~...~...~...~...~...~...~...~... ANKUR JAIN Institute for Communications Research (ICR) (formerly Centre for Wireless Communications) 20 Science Park Road, #02-34/37, TeleTech Park, Singapore Science Park II, SINGAPORE 117674 Website: http://www.icr.a-star.edu.sg Phone # 68709266 Email # stujaina@icr.a-star.edu.sg ankurjain@ieee.org ankurjain@softhome.net ~...~...~...~...~...~...~...~...~...~...~...~...~...~...~... _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 28 00:44:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17901 for ; Mon, 28 Oct 2002 00:44:53 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9S5kqO24202 for manet-archive@odin.ietf.org; Mon, 28 Oct 2002 00:46:52 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S5kov24199 for ; Mon, 28 Oct 2002 00:46:50 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17852 for ; Mon, 28 Oct 2002 00:44:18 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S5cFv23765; Mon, 28 Oct 2002 00:38:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9S5UWv23047 for ; Mon, 28 Oct 2002 00:30:32 -0500 Received: from gwserver.icr.a-star.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17380 for ; Mon, 28 Oct 2002 00:28:00 -0500 (EST) Received: from swl1002 ([172.16.3.193]) by gwserver.icr.a-star.edu.sg; Mon, 28 Oct 2002 13:24:44 +0800 Message-ID: <005401c27e42$52a0b3c0$c10310ac@icr.astar.edu.sg> Reply-To: "Ankur Jain" From: "Ankur Jain" To: References: Date: Mon, 28 Oct 2002 13:24:37 +0800 Organization: Institute for Communications Research, Singapore MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Subject: [manet] Directional Antennas and Multipath Routing Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Does anybody working on Directional Antennas with Multipath Routing? Please tell me who all are currently working on this and where I can find some good papers. Also, is there any actual device like Lucent's Orinoco card which has directional antenna and the modified MAC? Regards Ankur ~...~...~...~...~...~...~...~...~...~...~...~...~...~...~... ANKUR JAIN Institute for Communications Research (ICR) (formerly Centre for Wireless Communications) 20 Science Park Road, #02-34/37, TeleTech Park, Singapore Science Park II, SINGAPORE 117674 Website: http://www.icr.a-star.edu.sg Phone # 68709266 Email # stujaina@icr.a-star.edu.sg ankurjain@ieee.org ankurjain@softhome.net ~...~...~...~...~...~...~...~...~...~...~...~...~...~...~... _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 28 07:26:26 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05574 for ; Mon, 28 Oct 2002 07:26:25 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9SCSGU19896 for manet-archive@odin.ietf.org; Mon, 28 Oct 2002 07:28:16 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SCSGv19893 for ; Mon, 28 Oct 2002 07:28:16 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05509 for ; Mon, 28 Oct 2002 07:25:54 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SC6rv18625; Mon, 28 Oct 2002 07:06:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SC2tv18544 for ; Mon, 28 Oct 2002 07:02:55 -0500 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04742 for ; Mon, 28 Oct 2002 07:00:32 -0500 (EST) Message-Id: <200210281200.HAA04742@ietf.org> Received: (eyou send program); Mon, 28 Oct 2002 20:00:41 +0800 Received: from unknown (HELO yangwh) (unknown@166.111.67.88) by 166.111.8.16 with SMTP; Mon, 28 Oct 2002 20:00:41 +0800 Date: Mon, 28 Oct 2002 20:4:0 +0800 From: "yang weihua" To: "manet@ietf.org" X-mailer: Foxmail 4.1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9SC2tv18545 Subject: [manet] NS queue lenth Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hi£¬ During the wireless simulation, I want to investigate the dynamic characters of the queue(between LL and MAC), how can access the queue length of the queue? Thanks in advance? Best regards! yang weihua yangwh00@mails.tsinghua.edu.cn 2002-10-28 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 28 07:26:28 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05620 for ; Mon, 28 Oct 2002 07:26:28 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SC6rv18625; Mon, 28 Oct 2002 07:06:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SC2tv18544 for ; Mon, 28 Oct 2002 07:02:55 -0500 Received: from mails.tsinghua.edu.cn (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04742 for ; Mon, 28 Oct 2002 07:00:32 -0500 (EST) Message-Id: <200210281200.HAA04742@ietf.org> Received: (eyou send program); Mon, 28 Oct 2002 20:00:41 +0800 Received: from unknown (HELO yangwh) (unknown@166.111.67.88) by 166.111.8.16 with SMTP; Mon, 28 Oct 2002 20:00:41 +0800 Date: Mon, 28 Oct 2002 20:4:0 +0800 From: "yang weihua" To: "manet@ietf.org" X-mailer: Foxmail 4.1 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9SC2tv18545 Subject: [manet] NS queue lenth Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit hi£¬ During the wireless simulation, I want to investigate the dynamic characters of the queue(between LL and MAC), how can access the queue length of the queue? Thanks in advance? Best regards! yang weihua yangwh00@mails.tsinghua.edu.cn 2002-10-28 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 28 10:58:26 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15676 for ; Mon, 28 Oct 2002 10:58:26 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9SG0K631518 for manet-archive@odin.ietf.org; Mon, 28 Oct 2002 11:00:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SG0Kv31515 for ; Mon, 28 Oct 2002 11:00:20 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15665 for ; Mon, 28 Oct 2002 10:57:55 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SFksv30939; Mon, 28 Oct 2002 10:46:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SFiqv30827 for ; Mon, 28 Oct 2002 10:44:52 -0500 Received: from ing.puc.cl (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14807 for ; Mon, 28 Oct 2002 10:42:26 -0500 (EST) Received: from gus.ing.puc.cl (gus.ing.puc.cl [146.155.4.5]) by ing.puc.cl (8.9.3/8.9.3) with ESMTP id MAA06124 for ; Mon, 28 Oct 2002 12:44:32 -0300 (CDT) From: Roberto Aldunate Vera Received: from ing.puc.cl (zadkiel.ing.puc.cl [146.155.4.11]) by gus.ing.puc.cl (Postfix) with SMTP id 089D47B06 for ; Mon, 28 Oct 2002 12:36:30 -0300 (CLST) Received: from 146.83.210.6 (SquirrelMail authenticated user raldunat) by www.ing.puc.cl with HTTP; Mon, 28 Oct 2002 13:36:29 -0300 (CLST) Message-ID: <1155.146.83.210.6.1035822989.squirrel@www.ing.puc.cl> Date: Mon, 28 Oct 2002 13:36:29 -0300 (CLST) Subject: Re: [manet] Any special isssues on MANET? To: manet@ietf.org In-Reply-To: <20021028045529.D92E21CB0887B@bjapp5.163.net> References: <20021028045529.D92E21CB0887B@bjapp5.163.net> X-Mailer: SquirrelMail (version 1.0.6) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit A couple of Journals from Kluwer could help you: http://www.kluweronline.com/issn/1383-469X/ http://www.kluweronline.com/issn/1022-0038/ roberto. > hi, > Is there anyone knowing some journals or magazines focusing on > MANETs? Who are so kind to list them here. thank u so much! > > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Harry > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-28 > > > _______________________________________________ > 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-admin@ietf.org Mon Oct 28 10:58:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15689 for ; Mon, 28 Oct 2002 10:58:30 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SFksv30939; Mon, 28 Oct 2002 10:46:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SFiqv30827 for ; Mon, 28 Oct 2002 10:44:52 -0500 Received: from ing.puc.cl (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14807 for ; Mon, 28 Oct 2002 10:42:26 -0500 (EST) Received: from gus.ing.puc.cl (gus.ing.puc.cl [146.155.4.5]) by ing.puc.cl (8.9.3/8.9.3) with ESMTP id MAA06124 for ; Mon, 28 Oct 2002 12:44:32 -0300 (CDT) From: Roberto Aldunate Vera Received: from ing.puc.cl (zadkiel.ing.puc.cl [146.155.4.11]) by gus.ing.puc.cl (Postfix) with SMTP id 089D47B06 for ; Mon, 28 Oct 2002 12:36:30 -0300 (CLST) Received: from 146.83.210.6 (SquirrelMail authenticated user raldunat) by www.ing.puc.cl with HTTP; Mon, 28 Oct 2002 13:36:29 -0300 (CLST) Message-ID: <1155.146.83.210.6.1035822989.squirrel@www.ing.puc.cl> Date: Mon, 28 Oct 2002 13:36:29 -0300 (CLST) Subject: Re: [manet] Any special isssues on MANET? To: manet@ietf.org In-Reply-To: <20021028045529.D92E21CB0887B@bjapp5.163.net> References: <20021028045529.D92E21CB0887B@bjapp5.163.net> X-Mailer: SquirrelMail (version 1.0.6) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit A couple of Journals from Kluwer could help you: http://www.kluweronline.com/issn/1383-469X/ http://www.kluweronline.com/issn/1022-0038/ roberto. > hi, > Is there anyone knowing some journals or magazines focusing on > MANETs? Who are so kind to list them here. thank u so much! > > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Harry > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-28 > > > _______________________________________________ > 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-admin@ietf.org Mon Oct 28 11:15:06 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16498 for ; Mon, 28 Oct 2002 11:15:06 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SG8iv32375; Mon, 28 Oct 2002 11:08:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SG7Yv32321 for ; Mon, 28 Oct 2002 11:07:34 -0500 Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16045 for ; Mon, 28 Oct 2002 11:05:09 -0500 (EST) Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g9SG7H511855; Mon, 28 Oct 2002 17:07:18 +0100 (MET) Message-ID: <005c01c27e9f$a2fa2ec0$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Gayathri Chandrasekaran" , References: <20021020154937.K84991-100000@tesla.eecs.ku.edu> Subject: Re: [manet] OLSR implementation Date: Mon, 28 Oct 2002 17:32:40 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Dear Gayathri, Sorry to have been late to answer. As far as I can see, the main problem with ATM interfaces is the broadcast, which is used in OLSR for control traffic and I don't know how it will work with ATM. Maybe a kind of MARS could be useful... Philippe ----- Original Message ----- From: Gayathri Chandrasekaran To: Sent: Sunday, October 20, 2002 9:54 PM Subject: [manet] OLSR implementation > Hello, > I would like to know if OLSR runs over ATM interfaces.I'm trying to > implement some version 7 features to the INRIA version 3 OLSR linux > implementation. So for initial testing purposes can ATM interfaces be > used? > > thanks > gayathri > > Gayathri Chandrasekaran > Department of Electrical > Engineering and Computer Science > University of Kansas > Lawrence,KS-66045. > > _______________________________________________ > 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-admin@ietf.org Mon Oct 28 11:22:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16926 for ; Mon, 28 Oct 2002 11:22:25 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SGFOv32621; Mon, 28 Oct 2002 11:15:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SGEpv32588 for ; Mon, 28 Oct 2002 11:14:51 -0500 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16364 for ; Mon, 28 Oct 2002 11:12:25 -0500 (EST) Received: from colorado.edu (ecee189-245-dhcp.Colorado.EDU [128.138.189.245]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9SGEMd01592; Mon, 28 Oct 2002 09:14:23 -0700 (MST) Message-ID: <3DBD625A.4050702@colorado.edu> Date: Mon, 28 Oct 2002 09:14:18 -0700 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hr_befine@163.net CC: MANET mail list Subject: Re: [manet] Any special isssues on MANET? References: <20021028045529.D92E21CB0887B@bjapp5.163.net> Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit I know of Mobile Computing and Communications Review a.k.a MC2R whicih is a publication of SIGMOBILE. Shweta. Harry wrote: > hi, > Is there anyone knowing some journals or magazines focusing on MANETs? Who are so kind to list them here. > thank u so much! > > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Harry > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-28 > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 28 11:28:10 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17298 for ; Mon, 28 Oct 2002 11:28:10 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9SGU4l00826 for manet-archive@odin.ietf.org; Mon, 28 Oct 2002 11:30:04 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SGU4v00823 for ; Mon, 28 Oct 2002 11:30:04 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17267 for ; Mon, 28 Oct 2002 11:27:39 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SG8iv32375; Mon, 28 Oct 2002 11:08:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SG7Yv32321 for ; Mon, 28 Oct 2002 11:07:34 -0500 Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16045 for ; Mon, 28 Oct 2002 11:05:09 -0500 (EST) Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g9SG7H511855; Mon, 28 Oct 2002 17:07:18 +0100 (MET) Message-ID: <005c01c27e9f$a2fa2ec0$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Gayathri Chandrasekaran" , References: <20021020154937.K84991-100000@tesla.eecs.ku.edu> Subject: Re: [manet] OLSR implementation Date: Mon, 28 Oct 2002 17:32:40 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear Gayathri, Sorry to have been late to answer. As far as I can see, the main problem with ATM interfaces is the broadcast, which is used in OLSR for control traffic and I don't know how it will work with ATM. Maybe a kind of MARS could be useful... Philippe ----- Original Message ----- From: Gayathri Chandrasekaran To: Sent: Sunday, October 20, 2002 9:54 PM Subject: [manet] OLSR implementation > Hello, > I would like to know if OLSR runs over ATM interfaces.I'm trying to > implement some version 7 features to the INRIA version 3 OLSR linux > implementation. So for initial testing purposes can ATM interfaces be > used? > > thanks > gayathri > > Gayathri Chandrasekaran > Department of Electrical > Engineering and Computer Science > University of Kansas > Lawrence,KS-66045. > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 28 11:35:46 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17668 for ; Mon, 28 Oct 2002 11:35:46 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9SGbex01676 for manet-archive@odin.ietf.org; Mon, 28 Oct 2002 11:37:40 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SGbcv01673 for ; Mon, 28 Oct 2002 11:37:38 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17632 for ; Mon, 28 Oct 2002 11:35:12 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SGFOv32621; Mon, 28 Oct 2002 11:15:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SGEpv32588 for ; Mon, 28 Oct 2002 11:14:51 -0500 Received: from edgar.colorado.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16364 for ; Mon, 28 Oct 2002 11:12:25 -0500 (EST) Received: from colorado.edu (ecee189-245-dhcp.Colorado.EDU [128.138.189.245]) by edgar.colorado.edu (8.11.2/8.11.2/ITS-5.0/student) with ESMTP id g9SGEMd01592; Mon, 28 Oct 2002 09:14:23 -0700 (MST) Message-ID: <3DBD625A.4050702@colorado.edu> Date: Mon, 28 Oct 2002 09:14:18 -0700 From: Shweta Bhandare Reply-To: Shweta.Bhandare@colorado.edu Organization: University of Colorado at Boulder User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hr_befine@163.net CC: MANET mail list Subject: Re: [manet] Any special isssues on MANET? References: <20021028045529.D92E21CB0887B@bjapp5.163.net> Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit I know of Mobile Computing and Communications Review a.k.a MC2R whicih is a publication of SIGMOBILE. Shweta. Harry wrote: > hi, > Is there anyone knowing some journals or magazines focusing on MANETs? Who are so kind to list them here. > thank u so much! > > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡Harry > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-28 > > > _______________________________________________ > 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-admin@ietf.org Mon Oct 28 14:52:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26826 for ; Mon, 28 Oct 2002 14:52:42 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SJkUv12886; Mon, 28 Oct 2002 14:46:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SJiCv12833 for ; Mon, 28 Oct 2002 14:44:12 -0500 Received: from ocelot.cs.odu.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26326 for ; Mon, 28 Oct 2002 14:41:46 -0500 (EST) Received: from cs.odu.edu (xenon.cs.odu.edu [128.82.4.2]) by ocelot.cs.odu.edu (8.10.1/8.10.1) with SMTP id g9SJhfg25301 for ; Mon, 28 Oct 2002 14:43:41 -0500 (EST) From: tcp Received: from 128.82.8.72 (SquirrelMail authenticated user tcp) by www.cs.odu.edu with HTTP; Mon, 28 Oct 2002 14:44:07 -0500 (EST) Message-ID: <1207.128.82.8.72.1035834247.squirrel@www.cs.odu.edu> Date: Mon, 28 Oct 2002 14:44:07 -0500 (EST) Subject: Re: [manet] About ifqueue length To: manet@ietf.org In-Reply-To: <20021026160003.21729.42432.Mailman@www1.ietf.org> References: <20021026160003.21729.42432.Mailman@www1.ietf.org> X-Mailer: SquirrelMail (version 1.0.6) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi, Weihua, "agent->ifqueue" is defined but not used. The actual interface queue being used is: "agent->target_->downtarget_" (if trace between "Agent" and "LL" is disabled), or "agent->target_->downtarget_->downtarget_". You can find these details in ns-mobilenode.tcl. Hope it helps! Alan > Date: Sat, 26 Oct 2002 17:48:25 +0800 > From: "yang weihua" > To: "manet@ietf.org" > Subject: [manet] About ifqueue length > > everyone£¬ > Does anybody know how to get the ifqueue(between MAC and LL) > length from the route agent? I have attempted to get the value > by doing this in the AODV C++ source code: > queue_len=agent->ifqueue->getLen(); > where agent is the aodv route agent. But to my disappointment, > the result always remained to be zero! what's the problem? > Appreciate your any help! > > > > Best regards! > > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yang weihua > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yangwh00@mails.tsinghua.edu.cn > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-26 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 28 15:01:06 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27194 for ; Mon, 28 Oct 2002 15:01:06 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SJsTv13300; Mon, 28 Oct 2002 14:54:29 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SJrVv13203 for ; Mon, 28 Oct 2002 14:53:31 -0500 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26732 for ; Mon, 28 Oct 2002 14:51:04 -0500 (EST) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id OAA23496 for ; Mon, 28 Oct 2002 14:53:21 -0500 (EST) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002102814532230076 for ; Mon, 28 Oct 2002 14:53:22 -0500 Message-Id: <5.1.1.5.2.20021028145307.02de63e8@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Mon, 28 Oct 2002 14:55:10 -0500 To: manet@ietf.org From: Joe Macker Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [manet] manet meeting shift Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , All: I noticed the manet schedule got moved from Monday to early Thursday afternoon. I thought I would warn people that might have been planning to attend. It took me by surprise. -joe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 28 15:01:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27212 for ; Mon, 28 Oct 2002 15:01:34 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9SK3Tu13852 for manet-archive@odin.ietf.org; Mon, 28 Oct 2002 15:03:29 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SK3Tv13849 for ; Mon, 28 Oct 2002 15:03:29 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27191 for ; Mon, 28 Oct 2002 15:01:03 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SJkUv12886; Mon, 28 Oct 2002 14:46:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SJiCv12833 for ; Mon, 28 Oct 2002 14:44:12 -0500 Received: from ocelot.cs.odu.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26326 for ; Mon, 28 Oct 2002 14:41:46 -0500 (EST) Received: from cs.odu.edu (xenon.cs.odu.edu [128.82.4.2]) by ocelot.cs.odu.edu (8.10.1/8.10.1) with SMTP id g9SJhfg25301 for ; Mon, 28 Oct 2002 14:43:41 -0500 (EST) From: tcp Received: from 128.82.8.72 (SquirrelMail authenticated user tcp) by www.cs.odu.edu with HTTP; Mon, 28 Oct 2002 14:44:07 -0500 (EST) Message-ID: <1207.128.82.8.72.1035834247.squirrel@www.cs.odu.edu> Date: Mon, 28 Oct 2002 14:44:07 -0500 (EST) Subject: Re: [manet] About ifqueue length To: manet@ietf.org In-Reply-To: <20021026160003.21729.42432.Mailman@www1.ietf.org> References: <20021026160003.21729.42432.Mailman@www1.ietf.org> X-Mailer: SquirrelMail (version 1.0.6) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, Weihua, "agent->ifqueue" is defined but not used. The actual interface queue being used is: "agent->target_->downtarget_" (if trace between "Agent" and "LL" is disabled), or "agent->target_->downtarget_->downtarget_". You can find these details in ns-mobilenode.tcl. Hope it helps! Alan > Date: Sat, 26 Oct 2002 17:48:25 +0800 > From: "yang weihua" > To: "manet@ietf.org" > Subject: [manet] About ifqueue length > > everyone£¬ > Does anybody know how to get the ifqueue(between MAC and LL) > length from the route agent? I have attempted to get the value > by doing this in the AODV C++ source code: > queue_len=agent->ifqueue->getLen(); > where agent is the aodv route agent. But to my disappointment, > the result always remained to be zero! what's the problem? > Appreciate your any help! > > > > Best regards! > > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yang weihua > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡yangwh00@mails.tsinghua.edu.cn > ¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡2002-10-26 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 28 15:04:29 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27385 for ; Mon, 28 Oct 2002 15:04:28 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9SK6Of13945 for manet-archive@odin.ietf.org; Mon, 28 Oct 2002 15:06:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SK6Ov13942 for ; Mon, 28 Oct 2002 15:06:24 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27367 for ; Mon, 28 Oct 2002 15:03:58 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SJsTv13300; Mon, 28 Oct 2002 14:54:29 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SJrVv13203 for ; Mon, 28 Oct 2002 14:53:31 -0500 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26732 for ; Mon, 28 Oct 2002 14:51:04 -0500 (EST) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id OAA23496 for ; Mon, 28 Oct 2002 14:53:21 -0500 (EST) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002102814532230076 for ; Mon, 28 Oct 2002 14:53:22 -0500 Message-Id: <5.1.1.5.2.20021028145307.02de63e8@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Mon, 28 Oct 2002 14:55:10 -0500 To: manet@ietf.org From: Joe Macker Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [manet] manet meeting shift Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , All: I noticed the manet schedule got moved from Monday to early Thursday afternoon. I thought I would warn people that might have been planning to attend. It took me by surprise. -joe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 28 15:23:37 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28251 for ; Mon, 28 Oct 2002 15:23:37 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9SKPWY15455 for manet-archive@odin.ietf.org; Mon, 28 Oct 2002 15:25:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SKPWv15452 for ; Mon, 28 Oct 2002 15:25:32 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28222 for ; Mon, 28 Oct 2002 15:23:06 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SKHpv14993; Mon, 28 Oct 2002 15:17:51 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SKGYv14962 for ; Mon, 28 Oct 2002 15:16:34 -0500 Received: from smtp2.opnet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27804 for ; Mon, 28 Oct 2002 15:14:07 -0500 (EST) Received: from wtn11019 (wtn11019.opnet.com) by smtp2.opnet.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Mon, 28 Oct 2002 15:16:22 -0500 Message-Id: <4.2.0.58.20021028150925.02106f00@mail.opnet.com> X-Sender: krao@mail.opnet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 28 Oct 2002 15:16:21 -0500 To: manet@ietf.org From: Kartik Rao Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1977557226==_.ALT" Subject: [manet] External Network support for DSR Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=====================_1977557226==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed In the IETF Draft "draft-ietf-manet-dsr_07", "The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR)", in section "4.1 Route Cache", it states that "It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet, or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document" Does anyone know which document has this extension of connecting external networks to a DSR network? Thanks, Kartik --=====================_1977557226==_.ALT Content-Type: text/html; charset="us-ascii" In the IETF Draft "draft-ietf-manet-dsr_07", "The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR)",  in section "4.1 Route Cache", it states that "It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet, or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document"

Does anyone know which document has this extension of connecting external networks to a DSR network?

Thanks,
Kartik --=====================_1977557226==_.ALT-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 28 15:23:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28269 for ; Mon, 28 Oct 2002 15:23:47 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SKHpv14993; Mon, 28 Oct 2002 15:17:51 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SKGYv14962 for ; Mon, 28 Oct 2002 15:16:34 -0500 Received: from smtp2.opnet.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27804 for ; Mon, 28 Oct 2002 15:14:07 -0500 (EST) Received: from wtn11019 (wtn11019.opnet.com) by smtp2.opnet.com (Content Technologies SMTPRS 4.2.10) with ESMTP id for ; Mon, 28 Oct 2002 15:16:22 -0500 Message-Id: <4.2.0.58.20021028150925.02106f00@mail.opnet.com> X-Sender: krao@mail.opnet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 28 Oct 2002 15:16:21 -0500 To: manet@ietf.org From: Kartik Rao Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1977557226==_.ALT" Subject: [manet] External Network support for DSR Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=====================_1977557226==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed In the IETF Draft "draft-ietf-manet-dsr_07", "The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR)", in section "4.1 Route Cache", it states that "It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet, or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document" Does anyone know which document has this extension of connecting external networks to a DSR network? Thanks, Kartik --=====================_1977557226==_.ALT Content-Type: text/html; charset="us-ascii" In the IETF Draft "draft-ietf-manet-dsr_07", "The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR)",  in section "4.1 Route Cache", it states that "It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet, or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document"

Does anyone know which document has this extension of connecting external networks to a DSR network?

Thanks,
Kartik --=====================_1977557226==_.ALT-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Oct 28 18:51:23 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04302 for ; Mon, 28 Oct 2002 18:51:23 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9SNrLM25529 for manet-archive@odin.ietf.org; Mon, 28 Oct 2002 18:53:21 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SNrLv25526 for ; Mon, 28 Oct 2002 18:53:21 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04278 for ; Mon, 28 Oct 2002 18:50:52 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SNj1v25309; Mon, 28 Oct 2002 18:45:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SNe2v25188 for ; Mon, 28 Oct 2002 18:40:02 -0500 Received: from stl-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03865 for ; Mon, 28 Oct 2002 18:37:33 -0500 (EST) Received: from stl-av-02.boeing.com ([192.76.190.7]) by stl-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id RAA26612; Mon, 28 Oct 2002 17:39:55 -0600 (CST) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by stl-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id RAA29931; Mon, 28 Oct 2002 17:39:53 -0600 (CST) Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4]) by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g9SNdqr08827; Mon, 28 Oct 2002 15:39:52 -0800 (PST) Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2653.19) id ; Mon, 28 Oct 2002 18:39:52 -0500 Message-ID: From: "Manfredi, Albert E" To: "'Kartik Rao'" , manet@ietf.org Subject: RE: [manet] External Network support for DSR Date: Mon, 28 Oct 2002 18:39:46 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Not sure what you're asking. All that quote means is that the MANET can be connected to an edge router, or "border gateway," which ties the MANET to any other network. This router may be announced, for example, using ICMP Router Discovery protocol (RFC 1256). Or some other means may be used, such as static configuration (static config doesn't seem the best idea for a MANET). Once you've reached this router, the network on the other side can be anything you like: the wired Internet, with perhaps OSPF, another MANET with some other routing protocol, or even another MANET with DSR. Whatever it is on the other side, that border router isolates that other network from this DSR MANET we're talking about here. Bert -----Original Message----- From: Kartik Rao [mailto:krao@opnet.com] Sent: Monday, October 28, 2002 3:16 PM To: manet@ietf.org Subject: [manet] External Network support for DSR In the IETF Draft "draft-ietf-manet-dsr_07", "The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR)", in section "4.1 Route Cache", it states that "It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet, or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document" Does anyone know which document has this extension of connecting external networks to a DSR network? Thanks, Kartik _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Mon Oct 28 18:51:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04320 for ; Mon, 28 Oct 2002 18:51:25 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SNj1v25309; Mon, 28 Oct 2002 18:45:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SNe2v25188 for ; Mon, 28 Oct 2002 18:40:02 -0500 Received: from stl-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03865 for ; Mon, 28 Oct 2002 18:37:33 -0500 (EST) Received: from stl-av-02.boeing.com ([192.76.190.7]) by stl-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id RAA26612; Mon, 28 Oct 2002 17:39:55 -0600 (CST) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by stl-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id RAA29931; Mon, 28 Oct 2002 17:39:53 -0600 (CST) Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4]) by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g9SNdqr08827; Mon, 28 Oct 2002 15:39:52 -0800 (PST) Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2653.19) id ; Mon, 28 Oct 2002 18:39:52 -0500 Message-ID: From: "Manfredi, Albert E" To: "'Kartik Rao'" , manet@ietf.org Subject: RE: [manet] External Network support for DSR Date: Mon, 28 Oct 2002 18:39:46 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Not sure what you're asking. All that quote means is that the MANET can be connected to an edge router, or "border gateway," which ties the MANET to any other network. This router may be announced, for example, using ICMP Router Discovery protocol (RFC 1256). Or some other means may be used, such as static configuration (static config doesn't seem the best idea for a MANET). Once you've reached this router, the network on the other side can be anything you like: the wired Internet, with perhaps OSPF, another MANET with some other routing protocol, or even another MANET with DSR. Whatever it is on the other side, that border router isolates that other network from this DSR MANET we're talking about here. Bert -----Original Message----- From: Kartik Rao [mailto:krao@opnet.com] Sent: Monday, October 28, 2002 3:16 PM To: manet@ietf.org Subject: [manet] External Network support for DSR In the IETF Draft "draft-ietf-manet-dsr_07", "The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR)", in section "4.1 Route Cache", it states that "It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet, or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document" Does anyone know which document has this extension of connecting external networks to a DSR network? Thanks, Kartik _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 29 00:32:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11694 for ; Tue, 29 Oct 2002 00:32:42 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T5Osv09362; Tue, 29 Oct 2002 00:24:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T5FHv09038 for ; Tue, 29 Oct 2002 00:15:17 -0500 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11044 for ; Tue, 29 Oct 2002 00:12:44 -0500 (EST) Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id NAA21191; Tue, 29 Oct 2002 13:14:59 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500b.comp.nus.edu.sg via csmap id 6177; Tue, 29 Oct 2002 13:02:54 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id NAA10677; Tue, 29 Oct 2002 13:14:55 +0800 (GMT-8) Date: Tue, 29 Oct 2002 13:14:55 +0800 (GMT-8) From: Sourabh Sharma To: "Manfredi, Albert E" cc: manet@ietf.org Subject: RE: [manet] External Network support for DSR In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Mon, 28 Oct 2002, Manfredi, Albert E wrote: > Once you've reached this router, the network on the other side can be >anything you like: the wired Internet, with perhaps OSPF, another MANET >with some other routing protocol, or even another MANET with DSR. >Whatever it is on the other side, that border router isolates that >other network from this DSR MANET we're talking about here. > Hi all, just some food for thought... Here above,we are talking about different manets, where the difference basically lies in the routing protocol ,addressibng scheme, etc.- basically connecting to IP Networks. What I was wondering was, has any body tried connecting 2 manets with different MAC layers? which may or may no be running the same routing protocol. Like connecting a Bluetooth manet with a 802.11 manet? Is there any paper which focuses on this ? Regards, Sourabh. > > > -----Original Message----- > From: Kartik Rao [mailto:krao@opnet.com] > Sent: Monday, October 28, 2002 3:16 PM > To: manet@ietf.org > Subject: [manet] External Network support for DSR > > > In the IETF Draft "draft-ietf-manet-dsr_07", "The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR)", in section "4.1 Route Cache", it states that "It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet, or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document" > > Does anyone know which document has this extension of connecting external networks to a DSR network? > > Thanks, > Kartik > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 29 00:39:43 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11876 for ; Tue, 29 Oct 2002 00:39:43 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9T5fi410670 for manet-archive@odin.ietf.org; Tue, 29 Oct 2002 00:41:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T5fiv10667 for ; Tue, 29 Oct 2002 00:41:44 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11869 for ; Tue, 29 Oct 2002 00:39:12 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T5Osv09362; Tue, 29 Oct 2002 00:24:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T5FHv09038 for ; Tue, 29 Oct 2002 00:15:17 -0500 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11044 for ; Tue, 29 Oct 2002 00:12:44 -0500 (EST) Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id NAA21191; Tue, 29 Oct 2002 13:14:59 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500b.comp.nus.edu.sg via csmap id 6177; Tue, 29 Oct 2002 13:02:54 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id NAA10677; Tue, 29 Oct 2002 13:14:55 +0800 (GMT-8) Date: Tue, 29 Oct 2002 13:14:55 +0800 (GMT-8) From: Sourabh Sharma To: "Manfredi, Albert E" cc: manet@ietf.org Subject: RE: [manet] External Network support for DSR In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Mon, 28 Oct 2002, Manfredi, Albert E wrote: > Once you've reached this router, the network on the other side can be >anything you like: the wired Internet, with perhaps OSPF, another MANET >with some other routing protocol, or even another MANET with DSR. >Whatever it is on the other side, that border router isolates that >other network from this DSR MANET we're talking about here. > Hi all, just some food for thought... Here above,we are talking about different manets, where the difference basically lies in the routing protocol ,addressibng scheme, etc.- basically connecting to IP Networks. What I was wondering was, has any body tried connecting 2 manets with different MAC layers? which may or may no be running the same routing protocol. Like connecting a Bluetooth manet with a 802.11 manet? Is there any paper which focuses on this ? Regards, Sourabh. > > > -----Original Message----- > From: Kartik Rao [mailto:krao@opnet.com] > Sent: Monday, October 28, 2002 3:16 PM > To: manet@ietf.org > Subject: [manet] External Network support for DSR > > > In the IETF Draft "draft-ietf-manet-dsr_07", "The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR)", in section "4.1 Route Cache", it states that "It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet, or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document" > > Does anyone know which document has this extension of connecting external networks to a DSR network? > > Thanks, > Kartik > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 29 01:11:04 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12544 for ; Tue, 29 Oct 2002 01:11:04 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9T6D5112211 for manet-archive@odin.ietf.org; Tue, 29 Oct 2002 01:13:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T6D5v12208 for ; Tue, 29 Oct 2002 01:13:05 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12534 for ; Tue, 29 Oct 2002 01:10:33 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T659v11273; Tue, 29 Oct 2002 01:05:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T5x9v11100 for ; Tue, 29 Oct 2002 00:59:09 -0500 Received: from post2.inre.asu.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12245 for ; Tue, 29 Oct 2002 00:56:37 -0500 (EST) Received: from conversion.post2.inre.asu.edu by asu.edu (PMDF V6.1 #40111) id <0H4Q00201BABZ9@asu.edu> for manet@ietf.org; Mon, 28 Oct 2002 22:58:59 -0700 (MST) Received: from smtp.asu.edu (smtp.asu.edu [129.219.110.107]) by asu.edu (PMDF V6.1 #40111) with ESMTP id <0H4Q0026NBABQI@asu.edu> for manet@ietf.org; Mon, 28 Oct 2002 22:58:59 -0700 (MST) Received: from general1.asu.edu (general1.asu.edu [129.219.10.241]) by smtp.asu.edu (8.11.0/8.11.0/asu_smtp_relay,nullclient,tcp_wrapped) with ESMTP id g9T5wwa14773 for ; Mon, 28 Oct 2002 22:58:58 -0700 (MST) Date: Mon, 28 Oct 2002 22:58:57 -0700 (MST) From: Rakesh Kumar Banka X-Sender: rbanka@general1.asu.edu To: manet@ietf.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Heterogeneous networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Can someone tell me how to change the transmission ranges of the nodes in the NS-2 simulator? Are there any Ad-hoc clustering algorithms implemented in NS ? Any patches ?? Rakesh. ------------------------------------------------------------------------- Graduate Research Assistant Email: Rakesh@asu.edu Department Of Computer Science. Phone(R):480-736-1078 Arizona State University. AZ-85281. http://www.public.asu.edu/~rbanka ------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 29 01:11:08 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12558 for ; Tue, 29 Oct 2002 01:11:08 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T659v11273; Tue, 29 Oct 2002 01:05:09 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T5x9v11100 for ; Tue, 29 Oct 2002 00:59:09 -0500 Received: from post2.inre.asu.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12245 for ; Tue, 29 Oct 2002 00:56:37 -0500 (EST) Received: from conversion.post2.inre.asu.edu by asu.edu (PMDF V6.1 #40111) id <0H4Q00201BABZ9@asu.edu> for manet@ietf.org; Mon, 28 Oct 2002 22:58:59 -0700 (MST) Received: from smtp.asu.edu (smtp.asu.edu [129.219.110.107]) by asu.edu (PMDF V6.1 #40111) with ESMTP id <0H4Q0026NBABQI@asu.edu> for manet@ietf.org; Mon, 28 Oct 2002 22:58:59 -0700 (MST) Received: from general1.asu.edu (general1.asu.edu [129.219.10.241]) by smtp.asu.edu (8.11.0/8.11.0/asu_smtp_relay,nullclient,tcp_wrapped) with ESMTP id g9T5wwa14773 for ; Mon, 28 Oct 2002 22:58:58 -0700 (MST) Date: Mon, 28 Oct 2002 22:58:57 -0700 (MST) From: Rakesh Kumar Banka X-Sender: rbanka@general1.asu.edu To: manet@ietf.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Heterogeneous networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Can someone tell me how to change the transmission ranges of the nodes in the NS-2 simulator? Are there any Ad-hoc clustering algorithms implemented in NS ? Any patches ?? Rakesh. ------------------------------------------------------------------------- Graduate Research Assistant Email: Rakesh@asu.edu Department Of Computer Science. Phone(R):480-736-1078 Arizona State University. AZ-85281. http://www.public.asu.edu/~rbanka ------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 29 02:24:50 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23498 for ; Tue, 29 Oct 2002 02:24:49 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9T7QoX24460 for manet-archive@odin.ietf.org; Tue, 29 Oct 2002 02:26:50 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7Qnv24457 for ; Tue, 29 Oct 2002 02:26:49 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23478 for ; Tue, 29 Oct 2002 02:24:18 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7HEv23170; Tue, 29 Oct 2002 02:17:14 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7AFv21814 for ; Tue, 29 Oct 2002 02:10:15 -0500 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22848 for ; Tue, 29 Oct 2002 02:07:44 -0500 (EST) Received: (from dyoung@localhost) by che.onthejob.net (8.9.3/8.9.3) id BAA01113 for manet@ietf.org; Tue, 29 Oct 2002 01:10:04 -0600 Date: Tue, 29 Oct 2002 01:10:04 -0600 From: David Young To: manet@ietf.org Message-ID: <20021029011004.A31545@che.onthejob.net> Reply-To: dyoung@pobox.com Mail-Followup-To: David Young , manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Subject: [manet] controlling virtual carrier sense in 802.11 radios Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , If researchers were able to exercise fine-grained control over the virtual carrier sense in 802.11 radios, that would make possible a lot of interesting experiments in arbitrating media access. Just for an example of a desirable control, say it is possible to upload to an 802.11b radio, at regular intervals of time, a bitmap which describes the time slots where the radio should regard the virtual carrier sense as "positive," regardless of what transpires on the medium. Then certain sophisticated MAC algorithms can be implemented in the radio's host computer, and the results transformed into a virtual carrier sense bitmap which is uploaded to the radio. Now the radio can transmit at its full speed under influence of the virtual carrier sense uploaded by the host. If consumer radios allowed this sort of control over the virtual carrier sense, would that make them more desirable for research? Dave -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 29 02:24:51 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23511 for ; Tue, 29 Oct 2002 02:24:51 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7HEv23170; Tue, 29 Oct 2002 02:17:14 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7AFv21814 for ; Tue, 29 Oct 2002 02:10:15 -0500 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22848 for ; Tue, 29 Oct 2002 02:07:44 -0500 (EST) Received: (from dyoung@localhost) by che.onthejob.net (8.9.3/8.9.3) id BAA01113 for manet@ietf.org; Tue, 29 Oct 2002 01:10:04 -0600 Date: Tue, 29 Oct 2002 01:10:04 -0600 From: David Young To: manet@ietf.org Message-ID: <20021029011004.A31545@che.onthejob.net> Reply-To: dyoung@pobox.com Mail-Followup-To: David Young , manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Subject: [manet] controlling virtual carrier sense in 802.11 radios Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , If researchers were able to exercise fine-grained control over the virtual carrier sense in 802.11 radios, that would make possible a lot of interesting experiments in arbitrating media access. Just for an example of a desirable control, say it is possible to upload to an 802.11b radio, at regular intervals of time, a bitmap which describes the time slots where the radio should regard the virtual carrier sense as "positive," regardless of what transpires on the medium. Then certain sophisticated MAC algorithms can be implemented in the radio's host computer, and the results transformed into a virtual carrier sense bitmap which is uploaded to the radio. Now the radio can transmit at its full speed under influence of the virtual carrier sense uploaded by the host. If consumer radios allowed this sort of control over the virtual carrier sense, would that make them more desirable for research? Dave -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 29 02:33:31 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23767 for ; Tue, 29 Oct 2002 02:33:31 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9T7ZWF25025 for manet-archive@odin.ietf.org; Tue, 29 Oct 2002 02:35:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7ZVv25022 for ; Tue, 29 Oct 2002 02:35:31 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23762 for ; Tue, 29 Oct 2002 02:33:00 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7Qdv24442; Tue, 29 Oct 2002 02:26:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7PRv24385 for ; Tue, 29 Oct 2002 02:25:27 -0500 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23468 for ; Tue, 29 Oct 2002 02:22:55 -0500 (EST) Received: (from dyoung@localhost) by che.onthejob.net (8.9.3/8.9.3) id BAA01884 for manet@ietf.org; Tue, 29 Oct 2002 01:25:16 -0600 Date: Tue, 29 Oct 2002 01:25:16 -0600 From: David Young To: manet@ietf.org Subject: Re: [manet] External Network support for DSR Message-ID: <20021029012516.B31545@che.onthejob.net> Reply-To: dyoung@pobox.com Mail-Followup-To: David Young , manet@ietf.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from sourabhs@comp.nus.edu.sg on Tue, Oct 29, 2002 at 01:14:55PM +0800 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Typically routing information is shared by one protocol with another through the routing information block (RIB) in a routing daemon such as GateD or Zebra. I think that in open source, Zebra took the torch from GateD, but you can license a high-quality commercial GateD. Besides redistributing routes from one protocol to another, a routing daemon typically contains an abstract API for controlling the operating system's routing table, so you get some portability "for free" when you implement for a routing daemon. I am anxious to see ad hoc routing protocols brought to Zebra, myself. Dave On Tue, Oct 29, 2002 at 01:14:55PM +0800, Sourabh Sharma wrote: > On Mon, 28 Oct 2002, Manfredi, Albert E wrote: > > Once you've reached this router, the network on the other side can be > >anything you like: the wired Internet, with perhaps OSPF, another MANET > >with some other routing protocol, or even another MANET with DSR. > >Whatever it is on the other side, that border router isolates that > >other network from this DSR MANET we're talking about here. > > > > Hi all, > just some food for thought... > Here above,we are talking about different manets, where the > difference basically lies in the routing protocol ,addressibng scheme, > etc.- basically connecting to IP Networks. > What I was wondering was, has any body tried connecting > 2 manets with different MAC layers? which may or may no be running the > same routing protocol. > Like connecting a Bluetooth manet with a 802.11 manet? > Is there any paper which focuses on this ? > > Regards, > Sourabh. > > > > > > > -----Original Message----- > > From: Kartik Rao [mailto:krao@opnet.com] > > Sent: Monday, October 28, 2002 3:16 PM > > To: manet@ietf.org > > Subject: [manet] External Network support for DSR > > > > > > In the IETF Draft "draft-ietf-manet-dsr_07", "The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR)", in section "4.1 Route Cache", it states that "It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet, or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document" > > > > Does anyone know which document has this extension of connecting external networks to a DSR network? > > > > Thanks, > > Kartik > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > -------------------------------------------------- > There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 29 02:33:33 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23780 for ; Tue, 29 Oct 2002 02:33:33 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7Qdv24442; Tue, 29 Oct 2002 02:26:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7PRv24385 for ; Tue, 29 Oct 2002 02:25:27 -0500 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23468 for ; Tue, 29 Oct 2002 02:22:55 -0500 (EST) Received: (from dyoung@localhost) by che.onthejob.net (8.9.3/8.9.3) id BAA01884 for manet@ietf.org; Tue, 29 Oct 2002 01:25:16 -0600 Date: Tue, 29 Oct 2002 01:25:16 -0600 From: David Young To: manet@ietf.org Subject: Re: [manet] External Network support for DSR Message-ID: <20021029012516.B31545@che.onthejob.net> Reply-To: dyoung@pobox.com Mail-Followup-To: David Young , manet@ietf.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from sourabhs@comp.nus.edu.sg on Tue, Oct 29, 2002 at 01:14:55PM +0800 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Typically routing information is shared by one protocol with another through the routing information block (RIB) in a routing daemon such as GateD or Zebra. I think that in open source, Zebra took the torch from GateD, but you can license a high-quality commercial GateD. Besides redistributing routes from one protocol to another, a routing daemon typically contains an abstract API for controlling the operating system's routing table, so you get some portability "for free" when you implement for a routing daemon. I am anxious to see ad hoc routing protocols brought to Zebra, myself. Dave On Tue, Oct 29, 2002 at 01:14:55PM +0800, Sourabh Sharma wrote: > On Mon, 28 Oct 2002, Manfredi, Albert E wrote: > > Once you've reached this router, the network on the other side can be > >anything you like: the wired Internet, with perhaps OSPF, another MANET > >with some other routing protocol, or even another MANET with DSR. > >Whatever it is on the other side, that border router isolates that > >other network from this DSR MANET we're talking about here. > > > > Hi all, > just some food for thought... > Here above,we are talking about different manets, where the > difference basically lies in the routing protocol ,addressibng scheme, > etc.- basically connecting to IP Networks. > What I was wondering was, has any body tried connecting > 2 manets with different MAC layers? which may or may no be running the > same routing protocol. > Like connecting a Bluetooth manet with a 802.11 manet? > Is there any paper which focuses on this ? > > Regards, > Sourabh. > > > > > > > -----Original Message----- > > From: Kartik Rao [mailto:krao@opnet.com] > > Sent: Monday, October 28, 2002 3:16 PM > > To: manet@ietf.org > > Subject: [manet] External Network support for DSR > > > > > > In the IETF Draft "draft-ietf-manet-dsr_07", "The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR)", in section "4.1 Route Cache", it states that "It is possible to interface a DSR network with other networks, external to this DSR network. Such external networks may, for example, be the Internet, or may be other ad hoc networks routed with a routing protocol other than DSR. Such external networks may also be other DSR networks that are treated as external networks in order to improve scalability. The complete handling of such external networks is beyond the scope of this document" > > > > Does anyone know which document has this extension of connecting external networks to a DSR network? > > > > Thanks, > > Kartik > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > -------------------------------------------------- > There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 29 03:06:23 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24493 for ; Tue, 29 Oct 2002 03:06:23 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7viv26380; Tue, 29 Oct 2002 02:57:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7uQv26306 for ; Tue, 29 Oct 2002 02:56:26 -0500 Received: from zeus.soft.uni-linz.ac.at (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24164 for ; Tue, 29 Oct 2002 02:53:54 -0500 (EST) Received: from soft.uni-linz.ac.at (frank.soft.uni-linz.ac.at [140.78.95.149]) by zeus.soft.uni-linz.ac.at (8.11.6+Sun/8.11.1) with ESMTP id g9T7uEp20010 for ; Tue, 29 Oct 2002 08:56:14 +0100 (MET) Message-ID: <3DBE3F3A.6030904@soft.uni-linz.ac.at> Date: Tue, 29 Oct 2002 08:56:42 +0100 From: Rene Mayrhofer User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 X-Accept-Language: en MIME-Version: 1.0 To: manet@ietf.org Subject: Re: [manet] External Network support for DSR References: X-Enigmail-Version: 0.63.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I am subsribed to this list since a few days, so please excuse if this has already been discussed. Sourabh Sharma wrote: | just some food for thought... | Here above,we are talking about different manets, where the | difference basically lies in the routing protocol ,addressibng scheme, | etc.- basically connecting to IP Networks. | What I was wondering was, has any body tried connecting | 2 manets with different MAC layers? which may or may no be running the | same routing protocol. | Like connecting a Bluetooth manet with a 802.11 manet? | Is there any paper which focuses on this ? As far as I understood some protocols (e.g. OLSR, please correct me if I am wrong), they should be independent of the MAC layer. Therefore it should in principle be possible to have a hybrid manet with the same protocol and without "edge" routers (problems could arise when the different MAC types have very different characteristics). E.g. when some devices have Bluetooth as well as 802.11, both types of links can be used between devices within the same manet. Of course, this doesn't anser your question if anybody has already tried such hybrid networks. best regards, Rene Mayrhofer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQE9vj84pjfDF4Wpd7gRAgpNAKCSa4OxecEZbrEIPBd5A6qlexMsFgCfa2jT vxeYXAwkW0nyrB7Apu2Z6Fo= =tLEi -----END PGP SIGNATURE----- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 29 03:20:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24706 for ; Tue, 29 Oct 2002 03:20:47 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9T8MmE27882 for manet-archive@odin.ietf.org; Tue, 29 Oct 2002 03:22:48 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T8Mlv27879 for ; Tue, 29 Oct 2002 03:22:47 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24689 for ; Tue, 29 Oct 2002 03:20:15 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7viv26380; Tue, 29 Oct 2002 02:57:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T7uQv26306 for ; Tue, 29 Oct 2002 02:56:26 -0500 Received: from zeus.soft.uni-linz.ac.at (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24164 for ; Tue, 29 Oct 2002 02:53:54 -0500 (EST) Received: from soft.uni-linz.ac.at (frank.soft.uni-linz.ac.at [140.78.95.149]) by zeus.soft.uni-linz.ac.at (8.11.6+Sun/8.11.1) with ESMTP id g9T7uEp20010 for ; Tue, 29 Oct 2002 08:56:14 +0100 (MET) Message-ID: <3DBE3F3A.6030904@soft.uni-linz.ac.at> Date: Tue, 29 Oct 2002 08:56:42 +0100 From: Rene Mayrhofer User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020623 Debian/1.0.0-0.woody.1 X-Accept-Language: en MIME-Version: 1.0 To: manet@ietf.org Subject: Re: [manet] External Network support for DSR References: X-Enigmail-Version: 0.63.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I am subsribed to this list since a few days, so please excuse if this has already been discussed. Sourabh Sharma wrote: | just some food for thought... | Here above,we are talking about different manets, where the | difference basically lies in the routing protocol ,addressibng scheme, | etc.- basically connecting to IP Networks. | What I was wondering was, has any body tried connecting | 2 manets with different MAC layers? which may or may no be running the | same routing protocol. | Like connecting a Bluetooth manet with a 802.11 manet? | Is there any paper which focuses on this ? As far as I understood some protocols (e.g. OLSR, please correct me if I am wrong), they should be independent of the MAC layer. Therefore it should in principle be possible to have a hybrid manet with the same protocol and without "edge" routers (problems could arise when the different MAC types have very different characteristics). E.g. when some devices have Bluetooth as well as 802.11, both types of links can be used between devices within the same manet. Of course, this doesn't anser your question if anybody has already tried such hybrid networks. best regards, Rene Mayrhofer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQE9vj84pjfDF4Wpd7gRAgpNAKCSa4OxecEZbrEIPBd5A6qlexMsFgCfa2jT vxeYXAwkW0nyrB7Apu2Z6Fo= =tLEi -----END PGP SIGNATURE----- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 29 05:03:45 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26468 for ; Tue, 29 Oct 2002 05:03:45 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T9nlv00679; Tue, 29 Oct 2002 04:49:47 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T9d9v00376 for ; Tue, 29 Oct 2002 04:39:09 -0500 Received: from infres.enst.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26092 for ; Tue, 29 Oct 2002 04:36:36 -0500 (EST) Received: from schaula (dhcp162-221.enst.fr [137.194.162.221]) by infres.enst.fr (Postfix) with SMTP id 1C6661915 for ; Tue, 29 Oct 2002 10:38:57 +0100 (MET) Message-ID: <009c01c27f2f$12ece260$dda2c289@galaxy.enst.fr> From: "Moustafa Hasnaa" To: Date: Tue, 29 Oct 2002 10:39:27 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0099_01C27F37.74995590" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Subject: [manet] Concerning DSR neighbor info. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , C'est un message de format MIME en plusieurs parties. ------=_NextPart_000_0099_01C27F37.74995590 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi All, As far as i know that DSR relies on mac layer for neighbor existance = info. and Link failure detection... The part concerning consulting the mac layer is not clear for me in the = code of dsr (dsragent.cc). If i need to access the info. of neighbors, the beacons i mean... Where can i get this... I will be so thankful for a reply. Regards. ------=_NextPart_000_0099_01C27F37.74995590 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi All,
 As far as i know = that DSR=20 relies on mac layer for neighbor existance info. and
 Link failure=20 detection...
 The part concerning = consulting=20 the mac layer is not clear for me in the code of dsr = (dsragent.cc).
If i need to access the = info. of=20 neighbors, the beacons i mean...
Where can i get = this...
 
I will be so thankful for = a=20 reply.
 
Regards.
------=_NextPart_000_0099_01C27F37.74995590-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 29 05:13:45 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26639 for ; Tue, 29 Oct 2002 05:13:45 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9TAFb202078 for manet-archive@odin.ietf.org; Tue, 29 Oct 2002 05:15:37 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TAFbv02075 for ; Tue, 29 Oct 2002 05:15:37 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26609 for ; Tue, 29 Oct 2002 05:13:14 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T9nlv00679; Tue, 29 Oct 2002 04:49:47 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9T9d9v00376 for ; Tue, 29 Oct 2002 04:39:09 -0500 Received: from infres.enst.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26092 for ; Tue, 29 Oct 2002 04:36:36 -0500 (EST) Received: from schaula (dhcp162-221.enst.fr [137.194.162.221]) by infres.enst.fr (Postfix) with SMTP id 1C6661915 for ; Tue, 29 Oct 2002 10:38:57 +0100 (MET) Message-ID: <009c01c27f2f$12ece260$dda2c289@galaxy.enst.fr> From: "Moustafa Hasnaa" To: Date: Tue, 29 Oct 2002 10:39:27 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0099_01C27F37.74995590" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Subject: [manet] Concerning DSR neighbor info. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , C'est un message de format MIME en plusieurs parties. ------=_NextPart_000_0099_01C27F37.74995590 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi All, As far as i know that DSR relies on mac layer for neighbor existance = info. and Link failure detection... The part concerning consulting the mac layer is not clear for me in the = code of dsr (dsragent.cc). If i need to access the info. of neighbors, the beacons i mean... Where can i get this... I will be so thankful for a reply. Regards. ------=_NextPart_000_0099_01C27F37.74995590 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi All,
 As far as i know = that DSR=20 relies on mac layer for neighbor existance info. and
 Link failure=20 detection...
 The part concerning = consulting=20 the mac layer is not clear for me in the code of dsr = (dsragent.cc).
If i need to access the = info. of=20 neighbors, the beacons i mean...
Where can i get = this...
 
I will be so thankful for = a=20 reply.
 
Regards.
------=_NextPart_000_0099_01C27F37.74995590-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 29 09:51:00 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06867 for ; Tue, 29 Oct 2002 09:51:00 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9TEqs917160 for manet-archive@odin.ietf.org; Tue, 29 Oct 2002 09:52:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TEqsv17157 for ; Tue, 29 Oct 2002 09:52:54 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06798 for ; Tue, 29 Oct 2002 09:50:29 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TEiZv16805; Tue, 29 Oct 2002 09:44:36 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TEg4v16700 for ; Tue, 29 Oct 2002 09:42:04 -0500 Received: from crystal.bbn.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05933 for ; Tue, 29 Oct 2002 09:39:40 -0500 (EST) Received: from crystal.bbn.com (localhost.bbn.com [127.0.0.1]) by crystal.bbn.com (8.9.3/8.8.8) with ESMTP id JAA43920; Tue, 29 Oct 2002 09:44:37 -0500 (EST) (envelope-from ramanath@crystal.bbn.com) Message-Id: <200210291444.JAA43920@crystal.bbn.com> To: dyoung@pobox.com cc: manet@ietf.org Subject: Re: [manet] controlling virtual carrier sense in 802.11 radios In-reply-to: Your message of "Tue, 29 Oct 2002 01:10:04 CST." <20021029011004.A31545@che.onthejob.net> Date: Tue, 29 Oct 2002 09:44:37 -0500 From: Ram Ramanathan Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , David, That is a great thought, and yes, I believe researchers can make use of it. An obvious application is to use 802.11 radios to do TDMA -- by computing the schedules in the host computer and downloading it into the radio. At least for stationary ad hoc networks (the kind most applicable currently commercially), this should sort of work. If such a bitmap could be AND'ed or OR'd with real VCS, then there could be other applications too. For example, you could create a protected channel for sending network control messages (Hello's, route query's etc.). E.g, during a particular "slot" all nodes in a neighborhood except one is forced to desist. I am sure there are other sophisticated uses, and there is no dearth of fertile minds in ad hoc networking:) In general, radio vendors have been poor at providing controls over radio parameters, and I wholeheartedly applaud and encourage any effort in this direction as eminently healthy for ad hoc networking. But there is a big "If" here. Do I dare hope that you are actually a radio vendor and might actually be considering this?:) -Ram. > Date: Tue, 29 Oct 2002 01:10:04 -0600 > From: David Young > To: manet@ietf.org > Message-ID: <20021029011004.A31545@che.onthejob.net> > Reply-To: dyoung@pobox.com > Mail-Followup-To: David Young , manet@ietf.org > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > User-Agent: Mutt/1.2.5i > Subject: [manet] controlling virtual carrier sense in 802.11 radios > Sender: manet-admin@ietf.org > Errors-To: manet-admin@ietf.org > X-BeenThere: manet@ietf.org > X-Mailman-Version: 2.0.12 > Precedence: bulk > List-Unsubscribe: , > > List-Id: Mobile Ad-hoc Networks > List-Post: > List-Help: > List-Subscribe: , > > X-Spam-Status: NO > X-Scanned-By: MIMEDefang 2.19 (www . roaringpenguin . com / mimedefang) > > > If researchers were able to exercise fine-grained control over the > virtual carrier sense in 802.11 radios, that would make possible a lot > of interesting experiments in arbitrating media access. > > Just for an example of a desirable control, say it is possible to > upload to an 802.11b radio, at regular intervals of time, a bitmap > which describes the time slots where the radio should regard the virtual > carrier sense as "positive," regardless of what transpires on the medium. > Then certain sophisticated MAC algorithms can be implemented in the > radio's host computer, and the results transformed into a virtual carrier > sense bitmap which is uploaded to the radio. Now the radio can transmit > at its full speed under influence of the virtual carrier sense uploaded > by the host. > > If consumer radios allowed this sort of control over the virtual carrier > sense, would that make them more desirable for research? > > Dave > > -- > David Young OJC Technologies > dyoung@ojctech.com Engineering from the Right Brain > Urbana, IL * (217) 278-3933 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 29 09:51:03 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06881 for ; Tue, 29 Oct 2002 09:51:03 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TEiZv16805; Tue, 29 Oct 2002 09:44:36 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TEg4v16700 for ; Tue, 29 Oct 2002 09:42:04 -0500 Received: from crystal.bbn.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05933 for ; Tue, 29 Oct 2002 09:39:40 -0500 (EST) Received: from crystal.bbn.com (localhost.bbn.com [127.0.0.1]) by crystal.bbn.com (8.9.3/8.8.8) with ESMTP id JAA43920; Tue, 29 Oct 2002 09:44:37 -0500 (EST) (envelope-from ramanath@crystal.bbn.com) Message-Id: <200210291444.JAA43920@crystal.bbn.com> To: dyoung@pobox.com cc: manet@ietf.org Subject: Re: [manet] controlling virtual carrier sense in 802.11 radios In-reply-to: Your message of "Tue, 29 Oct 2002 01:10:04 CST." <20021029011004.A31545@che.onthejob.net> Date: Tue, 29 Oct 2002 09:44:37 -0500 From: Ram Ramanathan Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , David, That is a great thought, and yes, I believe researchers can make use of it. An obvious application is to use 802.11 radios to do TDMA -- by computing the schedules in the host computer and downloading it into the radio. At least for stationary ad hoc networks (the kind most applicable currently commercially), this should sort of work. If such a bitmap could be AND'ed or OR'd with real VCS, then there could be other applications too. For example, you could create a protected channel for sending network control messages (Hello's, route query's etc.). E.g, during a particular "slot" all nodes in a neighborhood except one is forced to desist. I am sure there are other sophisticated uses, and there is no dearth of fertile minds in ad hoc networking:) In general, radio vendors have been poor at providing controls over radio parameters, and I wholeheartedly applaud and encourage any effort in this direction as eminently healthy for ad hoc networking. But there is a big "If" here. Do I dare hope that you are actually a radio vendor and might actually be considering this?:) -Ram. > Date: Tue, 29 Oct 2002 01:10:04 -0600 > From: David Young > To: manet@ietf.org > Message-ID: <20021029011004.A31545@che.onthejob.net> > Reply-To: dyoung@pobox.com > Mail-Followup-To: David Young , manet@ietf.org > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > User-Agent: Mutt/1.2.5i > Subject: [manet] controlling virtual carrier sense in 802.11 radios > Sender: manet-admin@ietf.org > Errors-To: manet-admin@ietf.org > X-BeenThere: manet@ietf.org > X-Mailman-Version: 2.0.12 > Precedence: bulk > List-Unsubscribe: , > > List-Id: Mobile Ad-hoc Networks > List-Post: > List-Help: > List-Subscribe: , > > X-Spam-Status: NO > X-Scanned-By: MIMEDefang 2.19 (www . roaringpenguin . com / mimedefang) > > > If researchers were able to exercise fine-grained control over the > virtual carrier sense in 802.11 radios, that would make possible a lot > of interesting experiments in arbitrating media access. > > Just for an example of a desirable control, say it is possible to > upload to an 802.11b radio, at regular intervals of time, a bitmap > which describes the time slots where the radio should regard the virtual > carrier sense as "positive," regardless of what transpires on the medium. > Then certain sophisticated MAC algorithms can be implemented in the > radio's host computer, and the results transformed into a virtual carrier > sense bitmap which is uploaded to the radio. Now the radio can transmit > at its full speed under influence of the virtual carrier sense uploaded > by the host. > > If consumer radios allowed this sort of control over the virtual carrier > sense, would that make them more desirable for research? > > Dave > > -- > David Young OJC Technologies > dyoung@ojctech.com Engineering from the Right Brain > Urbana, IL * (217) 278-3933 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 29 10:46:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09587 for ; Tue, 29 Oct 2002 10:46:33 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9TFmSu20505 for manet-archive@odin.ietf.org; Tue, 29 Oct 2002 10:48:28 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TFmSv20502 for ; Tue, 29 Oct 2002 10:48:28 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09531 for ; Tue, 29 Oct 2002 10:46:02 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TFeXv20033; Tue, 29 Oct 2002 10:40:33 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SH9dv04133 for ; Mon, 28 Oct 2002 12:09:39 -0500 Received: from mail.scires.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19070 for ; Mon, 28 Oct 2002 12:07:12 -0500 (EST) Received: from SRCATL-MTA by mail.scires.com with Novell_GroupWise; Mon, 28 Oct 2002 12:10:29 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta Date: Mon, 28 Oct 2002 12:09:56 -0500 From: "Pete Sholander" To: , , Subject: Re: [manet] OLSR implementation Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Gayathri, As another (possibly bogus!) thought ... OSPF runs over Non-Broadcast Multicast Access (NBMA) networks. (Check the RFC for details. Not sure if the code at opsf.org implements that feature though!) Maybe there's someway to extend OLSR to map its MPRs onto OSPF's "Designated Router" concept. Sounds like an interesing thesis topic. However, mobile ad hoc ATM networks are kind of passe by now. Do you have a end-user application in mind? --Pete Sholander >>> "Philippe Jacquet" 10/28/02 11:32AM >>> Dear Gayathri, Sorry to have been late to answer. As far as I can see, the main problem with ATM interfaces is the broadcast, which is used in OLSR for control traffic and I don't know how it will work with ATM. Maybe a kind of MARS could be useful... Philippe ----- Original Message ----- From: Gayathri Chandrasekaran To: Sent: Sunday, October 20, 2002 9:54 PM Subject: [manet] OLSR implementation > Hello, > I would like to know if OLSR runs over ATM interfaces.I'm trying to > implement some version 7 features to the INRIA version 3 OLSR linux > implementation. So for initial testing purposes can ATM interfaces be > used? > > thanks > gayathri > > Gayathri Chandrasekaran > Department of Electrical > Engineering and Computer Science > University of Kansas > Lawrence,KS-66045. > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 29 10:46:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09600 for ; Tue, 29 Oct 2002 10:46:36 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TFeXv20033; Tue, 29 Oct 2002 10:40:33 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9SH9dv04133 for ; Mon, 28 Oct 2002 12:09:39 -0500 Received: from mail.scires.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19070 for ; Mon, 28 Oct 2002 12:07:12 -0500 (EST) Received: from SRCATL-MTA by mail.scires.com with Novell_GroupWise; Mon, 28 Oct 2002 12:10:29 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta Date: Mon, 28 Oct 2002 12:09:56 -0500 From: "Pete Sholander" To: , , Subject: Re: [manet] OLSR implementation Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Gayathri, As another (possibly bogus!) thought ... OSPF runs over Non-Broadcast Multicast Access (NBMA) networks. (Check the RFC for details. Not sure if the code at opsf.org implements that feature though!) Maybe there's someway to extend OLSR to map its MPRs onto OSPF's "Designated Router" concept. Sounds like an interesing thesis topic. However, mobile ad hoc ATM networks are kind of passe by now. Do you have a end-user application in mind? --Pete Sholander >>> "Philippe Jacquet" 10/28/02 11:32AM >>> Dear Gayathri, Sorry to have been late to answer. As far as I can see, the main problem with ATM interfaces is the broadcast, which is used in OLSR for control traffic and I don't know how it will work with ATM. Maybe a kind of MARS could be useful... Philippe ----- Original Message ----- From: Gayathri Chandrasekaran To: Sent: Sunday, October 20, 2002 9:54 PM Subject: [manet] OLSR implementation > Hello, > I would like to know if OLSR runs over ATM interfaces.I'm trying to > implement some version 7 features to the INRIA version 3 OLSR linux > implementation. So for initial testing purposes can ATM interfaces be > used? > > thanks > gayathri > > Gayathri Chandrasekaran > Department of Electrical > Engineering and Computer Science > University of Kansas > Lawrence,KS-66045. > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 29 15:41:46 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23907 for ; Tue, 29 Oct 2002 15:41:46 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9TKhg105258 for manet-archive@odin.ietf.org; Tue, 29 Oct 2002 15:43:42 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TKhgv05255 for ; Tue, 29 Oct 2002 15:43:42 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23883 for ; Tue, 29 Oct 2002 15:41:15 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TKZJv04326; Tue, 29 Oct 2002 15:35:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TKW5v04214 for ; Tue, 29 Oct 2002 15:32:05 -0500 Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23347 for ; Tue, 29 Oct 2002 15:29:35 -0500 (EST) Received: from mail.nps.navy.mil by [140.32.132.66] via smtpd (for [132.151.6.1]) with ESMTP; Tue, 29 Oct 2002 12:29:17 -0800 Received: from ro178-88.ro.nps.navy.mil (ro178-88.ro.nps.navy.mil [131.120.178.88]) by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id g9TKUUb9002592; Tue, 29 Oct 2002 12:30:30 -0800 (PST) Subject: Re: [manet] controlling virtual carrier sense in 802.11 radios From: Rex Buddenberg To: dyoung@pobox.com Cc: manet@ietf.org In-Reply-To: <20021029011004.A31545@che.onthejob.net> References: <20021029011004.A31545@che.onthejob.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 29 Oct 2002 13:28:45 -0800 Message-Id: <1035926926.1068.74.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit David, First, a caveat: we're outside the scope of MANET and into the data link layer. That out of the way, you're right. The MAC (CSMA/CA) algorithm locked into 802.11 chips has a lot of room for improvement for wireless LANs. And a whole lot of need for improvement as soon as we get to larger scale such as satellite systems with significant propagation delay. You need either scheduling (all cases) or polling (where you have good interactivity) MAC. Algorithm aside, there appears to be no good way to insert such a tweak ... if you find one, let me know. On Mon, 2002-10-28 at 23:10, David Young wrote: > > If researchers were able to exercise fine-grained control over the > virtual carrier sense in 802.11 radios, that would make possible a lot > of interesting experiments in arbitrating media access. > > Just for an example of a desirable control, say it is possible to > upload to an 802.11b radio, at regular intervals of time, a bitmap > which describes the time slots where the radio should regard the virtual > carrier sense as "positive," regardless of what transpires on the medium. > Then certain sophisticated MAC algorithms can be implemented in the > radio's host computer, and the results transformed into a virtual carrier > sense bitmap which is uploaded to the radio. Now the radio can transmit > at its full speed under influence of the virtual carrier sense uploaded > by the host. > > If consumer radios allowed this sort of control over the virtual carrier > sense, would that make them more desirable for research? > > Dave > > -- > David Young OJC Technologies > dyoung@ojctech.com Engineering from the Right Brain > Urbana, IL * (217) 278-3933 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 29 15:41:48 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23922 for ; Tue, 29 Oct 2002 15:41:48 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TKZJv04326; Tue, 29 Oct 2002 15:35:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TKW5v04214 for ; Tue, 29 Oct 2002 15:32:05 -0500 Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23347 for ; Tue, 29 Oct 2002 15:29:35 -0500 (EST) Received: from mail.nps.navy.mil by [140.32.132.66] via smtpd (for [132.151.6.1]) with ESMTP; Tue, 29 Oct 2002 12:29:17 -0800 Received: from ro178-88.ro.nps.navy.mil (ro178-88.ro.nps.navy.mil [131.120.178.88]) by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id g9TKUUb9002592; Tue, 29 Oct 2002 12:30:30 -0800 (PST) Subject: Re: [manet] controlling virtual carrier sense in 802.11 radios From: Rex Buddenberg To: dyoung@pobox.com Cc: manet@ietf.org In-Reply-To: <20021029011004.A31545@che.onthejob.net> References: <20021029011004.A31545@che.onthejob.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 29 Oct 2002 13:28:45 -0800 Message-Id: <1035926926.1068.74.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit David, First, a caveat: we're outside the scope of MANET and into the data link layer. That out of the way, you're right. The MAC (CSMA/CA) algorithm locked into 802.11 chips has a lot of room for improvement for wireless LANs. And a whole lot of need for improvement as soon as we get to larger scale such as satellite systems with significant propagation delay. You need either scheduling (all cases) or polling (where you have good interactivity) MAC. Algorithm aside, there appears to be no good way to insert such a tweak ... if you find one, let me know. On Mon, 2002-10-28 at 23:10, David Young wrote: > > If researchers were able to exercise fine-grained control over the > virtual carrier sense in 802.11 radios, that would make possible a lot > of interesting experiments in arbitrating media access. > > Just for an example of a desirable control, say it is possible to > upload to an 802.11b radio, at regular intervals of time, a bitmap > which describes the time slots where the radio should regard the virtual > carrier sense as "positive," regardless of what transpires on the medium. > Then certain sophisticated MAC algorithms can be implemented in the > radio's host computer, and the results transformed into a virtual carrier > sense bitmap which is uploaded to the radio. Now the radio can transmit > at its full speed under influence of the virtual carrier sense uploaded > by the host. > > If consumer radios allowed this sort of control over the virtual carrier > sense, would that make them more desirable for research? > > Dave > > -- > David Young OJC Technologies > dyoung@ojctech.com Engineering from the Right Brain > Urbana, IL * (217) 278-3933 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Oct 29 18:33:28 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01681 for ; Tue, 29 Oct 2002 18:33:27 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9TNZQG14509 for manet-archive@odin.ietf.org; Tue, 29 Oct 2002 18:35:26 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TNZQv14506 for ; Tue, 29 Oct 2002 18:35:26 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01593 for ; Tue, 29 Oct 2002 18:32:56 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TNM1v14059; Tue, 29 Oct 2002 18:22:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TNHsv13903 for ; Tue, 29 Oct 2002 18:17:54 -0500 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01082 for ; Tue, 29 Oct 2002 18:15:24 -0500 (EST) Received: (from dyoung@localhost) by che.onthejob.net (8.9.3/8.9.3) id RAA16673 for manet@ietf.org; Tue, 29 Oct 2002 17:17:46 -0600 Date: Tue, 29 Oct 2002 17:17:46 -0600 From: David Young To: manet@ietf.org Subject: Re: [manet] controlling virtual carrier sense in 802.11 radios Message-ID: <20021029171746.A15276@che.onthejob.net> Reply-To: dyoung@pobox.com Mail-Followup-To: David Young , manet@ietf.org References: <20021029011004.A31545@che.onthejob.net> <1035926926.1068.74.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1035926926.1068.74.camel@localhost.localdomain>; from budden@nps.navy.mil on Tue, Oct 29, 2002 at 01:28:45PM -0800 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Tue, Oct 29, 2002 at 01:28:45PM -0800, Rex Buddenberg wrote: > David, > > First, a caveat: we're outside the scope of MANET and into the data link > layer. Ok. I brought the topic to the list because I know for certain that many subscribers are concerned with it. Does someone know a more suitable venue for a MAC discussion? Dave -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Tue Oct 29 18:33:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01696 for ; Tue, 29 Oct 2002 18:33:30 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TNM1v14059; Tue, 29 Oct 2002 18:22:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TNHsv13903 for ; Tue, 29 Oct 2002 18:17:54 -0500 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01082 for ; Tue, 29 Oct 2002 18:15:24 -0500 (EST) Received: (from dyoung@localhost) by che.onthejob.net (8.9.3/8.9.3) id RAA16673 for manet@ietf.org; Tue, 29 Oct 2002 17:17:46 -0600 Date: Tue, 29 Oct 2002 17:17:46 -0600 From: David Young To: manet@ietf.org Subject: Re: [manet] controlling virtual carrier sense in 802.11 radios Message-ID: <20021029171746.A15276@che.onthejob.net> Reply-To: dyoung@pobox.com Mail-Followup-To: David Young , manet@ietf.org References: <20021029011004.A31545@che.onthejob.net> <1035926926.1068.74.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1035926926.1068.74.camel@localhost.localdomain>; from budden@nps.navy.mil on Tue, Oct 29, 2002 at 01:28:45PM -0800 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Tue, Oct 29, 2002 at 01:28:45PM -0800, Rex Buddenberg wrote: > David, > > First, a caveat: we're outside the scope of MANET and into the data link > layer. Ok. I brought the topic to the list because I know for certain that many subscribers are concerned with it. Does someone know a more suitable venue for a MAC discussion? Dave -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 30 05:36:26 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07589 for ; Wed, 30 Oct 2002 05:36:26 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9UAcJn24667 for manet-archive@odin.ietf.org; Wed, 30 Oct 2002 05:38:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UAcIv24664 for ; Wed, 30 Oct 2002 05:38:18 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07578 for ; Wed, 30 Oct 2002 05:35:55 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UATkv23627; Wed, 30 Oct 2002 05:29:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UAPNv23494 for ; Wed, 30 Oct 2002 05:25:23 -0500 Received: from thoth.sbs.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07214 for ; Wed, 30 Oct 2002 05:22:59 -0500 (EST) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g9UAP3N07083; Wed, 30 Oct 2002 11:25:03 +0100 (MET) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9UAP2V13288; Wed, 30 Oct 2002 11:25:02 +0100 (MET) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9UAP2Iu012079; Wed, 30 Oct 2002 11:25:03 +0100 (MET) Message-ID: <3DBFB37E.C69BB8F4@mchp.siemens.de> Date: Wed, 30 Oct 2002 11:25:02 +0100 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: tcp , Aodvimpl-Public , Mahesh Marina , "ns-users@isi.edu" CC: manet@ietf.org Subject: Re: [manet] About ifqueue length References: <20021026160003.21729.42432.Mailman@www1.ietf.org> <1207.128.82.8.72.1035834247.squirrel@www.cs.odu.edu> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit tcp wrote: > Hi, what do you mean with "not used"?? is agent->ifqueue empty?? But it's used in recvReply as well as in AODV::rt_ll_failed to drop the packets in the interface queue, that also could not be forwarded!!!! Does it have any effect now, since ifqueue is empty?? while((p = ifqueue->filter(broken_nbr))) { drop(p, DROP_RTR_MAC_CALLBACK); } Can omebody clarify it. This is a little confusing. Thanks Riadh > Hi, Weihua, > > "agent->ifqueue" is defined but not used. > The actual interface queue being used is: > "agent->target_->downtarget_" > (if trace between "Agent" and "LL" is disabled), or > "agent->target_->downtarget_->downtarget_". > > You can find these details in ns-mobilenode.tcl. > Hope it helps! > > Alan > > > Date: Sat, 26 Oct 2002 17:48:25 +0800 > > From: "yang weihua" > > To: "manet@ietf.org" > > Subject: [manet] About ifqueue length > > > > everyone£¬ > > Does anybody know how to get the ifqueue(between MAC and LL) > > length from the route agent? I have attempted to get the value > > by doing this in the AODV C++ source code: > > queue_len=agent->ifqueue->getLen(); > > where agent is the aodv route agent. But to my disappointment, > > the result always remained to be zero! what's the problem? > > Appreciate your any help! > > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 30 05:36:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07604 for ; Wed, 30 Oct 2002 05:36:38 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UATkv23627; Wed, 30 Oct 2002 05:29:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UAPNv23494 for ; Wed, 30 Oct 2002 05:25:23 -0500 Received: from thoth.sbs.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07214 for ; Wed, 30 Oct 2002 05:22:59 -0500 (EST) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.6/8.11.6) with ESMTP id g9UAP3N07083; Wed, 30 Oct 2002 11:25:03 +0100 (MET) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g9UAP2V13288; Wed, 30 Oct 2002 11:25:02 +0100 (MET) Received: from mchp.siemens.de (aspen [139.23.201.155]) by mail-y.mchp.siemens.de with ESMTP id g9UAP2Iu012079; Wed, 30 Oct 2002 11:25:03 +0100 (MET) Message-ID: <3DBFB37E.C69BB8F4@mchp.siemens.de> Date: Wed, 30 Oct 2002 11:25:02 +0100 From: Riadh Marrakchi X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.7-10 i686) X-Accept-Language: en MIME-Version: 1.0 To: tcp , Aodvimpl-Public , Mahesh Marina , "ns-users@isi.edu" CC: manet@ietf.org Subject: Re: [manet] About ifqueue length References: <20021026160003.21729.42432.Mailman@www1.ietf.org> <1207.128.82.8.72.1035834247.squirrel@www.cs.odu.edu> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit tcp wrote: > Hi, what do you mean with "not used"?? is agent->ifqueue empty?? But it's used in recvReply as well as in AODV::rt_ll_failed to drop the packets in the interface queue, that also could not be forwarded!!!! Does it have any effect now, since ifqueue is empty?? while((p = ifqueue->filter(broken_nbr))) { drop(p, DROP_RTR_MAC_CALLBACK); } Can omebody clarify it. This is a little confusing. Thanks Riadh > Hi, Weihua, > > "agent->ifqueue" is defined but not used. > The actual interface queue being used is: > "agent->target_->downtarget_" > (if trace between "Agent" and "LL" is disabled), or > "agent->target_->downtarget_->downtarget_". > > You can find these details in ns-mobilenode.tcl. > Hope it helps! > > Alan > > > Date: Sat, 26 Oct 2002 17:48:25 +0800 > > From: "yang weihua" > > To: "manet@ietf.org" > > Subject: [manet] About ifqueue length > > > > everyone£¬ > > Does anybody know how to get the ifqueue(between MAC and LL) > > length from the route agent? I have attempted to get the value > > by doing this in the AODV C++ source code: > > queue_len=agent->ifqueue->getLen(); > > where agent is the aodv route agent. But to my disappointment, > > the result always remained to be zero! what's the problem? > > Appreciate your any help! > > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 30 06:44:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10142 for ; Wed, 30 Oct 2002 06:44:34 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9UBkST28770 for manet-archive@odin.ietf.org; Wed, 30 Oct 2002 06:46:28 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UBkSv28767 for ; Wed, 30 Oct 2002 06:46:28 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10137 for ; Wed, 30 Oct 2002 06:44:04 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UBcJv28462; Wed, 30 Oct 2002 06:38:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UBaNv27779 for ; Wed, 30 Oct 2002 06:36:23 -0500 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09820 for ; Wed, 30 Oct 2002 06:33:57 -0500 (EST) Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id TAA05909 for ; Wed, 30 Oct 2002 19:36:18 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500b.comp.nus.edu.sg via csmap id 18739; Wed, 30 Oct 2002 19:24:17 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id TAA28673 for ; Wed, 30 Oct 2002 19:36:18 +0800 (GMT-8) Date: Wed, 30 Oct 2002 19:36:18 +0800 (GMT-8) From: Sourabh Sharma To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Ad-hoc --> Ip of Nodes. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, Recently, I have set up an ad-hoc network. But I noticed that somehow, the node's needed to be configured to be in the same subnet. By right, in ad-hoc , nodes having any random IP addr should be able to find routes to any Ipaddr and the underlying Ad-hoc routing protocol should update the source's routing table accordingly. In the case when the nodes are in the same subnet, you actually dun need an ad-hoc routing protocol! as long you have the routing entries correctly configured, you can make the nodes forward each others data packets, and thus have an ad-hoc network without the use of any special "ad-hoc" routing protocol.!! Secondly, I wanted to ask, out of the many ( ok, not so many) real ad-hoc test beds set up at CMU, MIT, INRIA etc. did any of you guys use any autoconf scheme ( like Zeroconf) or all the nodes were manually configured? Thirdly, since we now have an implementation of zerconf, known as zcip( available at http://zeroconf.sourceforge.net) has anyone tried using an Autoconfiguration scheme on ad-hoc? Probably we can have seperate discussions on the 3 topics. Regards, Sourabh Sharma Centre for Internet Research National University of Singapore -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 30 06:44:37 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10156 for ; Wed, 30 Oct 2002 06:44:37 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UBcJv28462; Wed, 30 Oct 2002 06:38:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UBaNv27779 for ; Wed, 30 Oct 2002 06:36:23 -0500 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09820 for ; Wed, 30 Oct 2002 06:33:57 -0500 (EST) Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id TAA05909 for ; Wed, 30 Oct 2002 19:36:18 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500b.comp.nus.edu.sg via csmap id 18739; Wed, 30 Oct 2002 19:24:17 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id TAA28673 for ; Wed, 30 Oct 2002 19:36:18 +0800 (GMT-8) Date: Wed, 30 Oct 2002 19:36:18 +0800 (GMT-8) From: Sourabh Sharma To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Ad-hoc --> Ip of Nodes. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, Recently, I have set up an ad-hoc network. But I noticed that somehow, the node's needed to be configured to be in the same subnet. By right, in ad-hoc , nodes having any random IP addr should be able to find routes to any Ipaddr and the underlying Ad-hoc routing protocol should update the source's routing table accordingly. In the case when the nodes are in the same subnet, you actually dun need an ad-hoc routing protocol! as long you have the routing entries correctly configured, you can make the nodes forward each others data packets, and thus have an ad-hoc network without the use of any special "ad-hoc" routing protocol.!! Secondly, I wanted to ask, out of the many ( ok, not so many) real ad-hoc test beds set up at CMU, MIT, INRIA etc. did any of you guys use any autoconf scheme ( like Zeroconf) or all the nodes were manually configured? Thirdly, since we now have an implementation of zerconf, known as zcip( available at http://zeroconf.sourceforge.net) has anyone tried using an Autoconfiguration scheme on ad-hoc? Probably we can have seperate discussions on the 3 topics. Regards, Sourabh Sharma Centre for Internet Research National University of Singapore -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 30 07:28:55 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11558 for ; Wed, 30 Oct 2002 07:28:55 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UCMOv30598; Wed, 30 Oct 2002 07:22:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UCLvv30567 for ; Wed, 30 Oct 2002 07:21:57 -0500 Received: from seraph2.grc.nasa.gov (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11254 for ; Wed, 30 Oct 2002 07:19:31 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 17178C69D0 for ; Wed, 30 Oct 2002 07:21:54 -0500 (EST) Received: from doldham.lerc.nasa.gov (doldham.lerc.nasa.gov [139.88.111.83]) by lombok-fi.lerc.nasa.gov (NASA GRC 8.12.3/8.12.3) with SMTP id g9UCLrwg000534; Wed, 30 Oct 2002 07:21:53 -0500 (EST) From: Daniel Oldham Date: Wed, 30 Oct 2002 12:23:10 GMT Message-ID: <20021030.12231000@doldham.lerc.nasa.gov> Subject: Re: [manet] controlling virtual carrier sense in 802.11 radios To: Rex Buddenberg , manet@ietf.org In-Reply-To: <1035926926.1068.74.camel@localhost.localdomain> References: <20021029011004.A31545@che.onthejob.net> <1035926926.1068.74.camel@localhost.localdomain> X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.2;Linux) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9UCLvv30568 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Rex: If you need "either scheduling (all cases) or polling" then please explain why you need an ad hoc algorithm for satellite communications. Once a satellite establishes a link layer connection then the information for routing is implied in the connection. The ad hoc algorithm then seems to be just extra overhead on the satellite. -- Daniel R. Oldham NASA Glenn Research Center Oldham@grc.nasa.gov >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 10/29/02, 4:28:45 PM, Rex Buddenberg wrote regarding Re: [manet] controlling virtual carrier sense in 802.11 radios: > David, > First, a caveat: we're outside the scope of MANET and into the data link > layer. > That out of the way, you're right. The MAC (CSMA/CA) algorithm locked > into 802.11 chips has a lot of room for improvement for wireless LANs. > And a whole lot of need for improvement as soon as we get to larger > scale such as satellite systems with significant propagation delay. You > need either scheduling (all cases) or polling (where you have good > interactivity) MAC. Algorithm aside, there appears to be no good way to > insert such a tweak ... if you find one, let me know. > On Mon, 2002-10-28 at 23:10, David Young wrote: > > > > If researchers were able to exercise fine-grained control over the > > virtual carrier sense in 802.11 radios, that would make possible a lot > > of interesting experiments in arbitrating media access. > > > > Just for an example of a desirable control, say it is possible to > > upload to an 802.11b radio, at regular intervals of time, a bitmap > > which describes the time slots where the radio should regard the virtual > > carrier sense as "positive," regardless of what transpires on the medium. > > Then certain sophisticated MAC algorithms can be implemented in the > > radio's host computer, and the results transformed into a virtual carrier > > sense bitmap which is uploaded to the radio. Now the radio can transmit > > at its full speed under influence of the virtual carrier sense uploaded > > by the host. > > > > If consumer radios allowed this sort of control over the virtual carrier > > sense, would that make them more desirable for research? > > > > Dave > > > > -- > > David Young OJC Technologies > > dyoung@ojctech.com Engineering from the Right Brain > > Urbana, IL * (217) 278-3933 > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 30 07:34:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11691 for ; Wed, 30 Oct 2002 07:34:38 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9UCaW431154 for manet-archive@odin.ietf.org; Wed, 30 Oct 2002 07:36:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UCaWv31151 for ; Wed, 30 Oct 2002 07:36:32 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11682 for ; Wed, 30 Oct 2002 07:34:07 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UCMOv30598; Wed, 30 Oct 2002 07:22:24 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UCLvv30567 for ; Wed, 30 Oct 2002 07:21:57 -0500 Received: from seraph2.grc.nasa.gov (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11254 for ; Wed, 30 Oct 2002 07:19:31 -0500 (EST) Received: from lombok-fi.lerc.nasa.gov (lombok-fi.lerc.nasa.gov [139.88.112.33]) by seraph2.grc.nasa.gov (Postfix) with ESMTP id 17178C69D0 for ; Wed, 30 Oct 2002 07:21:54 -0500 (EST) Received: from doldham.lerc.nasa.gov (doldham.lerc.nasa.gov [139.88.111.83]) by lombok-fi.lerc.nasa.gov (NASA GRC 8.12.3/8.12.3) with SMTP id g9UCLrwg000534; Wed, 30 Oct 2002 07:21:53 -0500 (EST) From: Daniel Oldham Date: Wed, 30 Oct 2002 12:23:10 GMT Message-ID: <20021030.12231000@doldham.lerc.nasa.gov> Subject: Re: [manet] controlling virtual carrier sense in 802.11 radios To: Rex Buddenberg , manet@ietf.org In-Reply-To: <1035926926.1068.74.camel@localhost.localdomain> References: <20021029011004.A31545@che.onthejob.net> <1035926926.1068.74.camel@localhost.localdomain> X-Mailer: Mozilla/3.0 (compatible; StarOffice/5.2;Linux) X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9UCLvv30568 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Rex: If you need "either scheduling (all cases) or polling" then please explain why you need an ad hoc algorithm for satellite communications. Once a satellite establishes a link layer connection then the information for routing is implied in the connection. The ad hoc algorithm then seems to be just extra overhead on the satellite. -- Daniel R. Oldham NASA Glenn Research Center Oldham@grc.nasa.gov >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 10/29/02, 4:28:45 PM, Rex Buddenberg wrote regarding Re: [manet] controlling virtual carrier sense in 802.11 radios: > David, > First, a caveat: we're outside the scope of MANET and into the data link > layer. > That out of the way, you're right. The MAC (CSMA/CA) algorithm locked > into 802.11 chips has a lot of room for improvement for wireless LANs. > And a whole lot of need for improvement as soon as we get to larger > scale such as satellite systems with significant propagation delay. You > need either scheduling (all cases) or polling (where you have good > interactivity) MAC. Algorithm aside, there appears to be no good way to > insert such a tweak ... if you find one, let me know. > On Mon, 2002-10-28 at 23:10, David Young wrote: > > > > If researchers were able to exercise fine-grained control over the > > virtual carrier sense in 802.11 radios, that would make possible a lot > > of interesting experiments in arbitrating media access. > > > > Just for an example of a desirable control, say it is possible to > > upload to an 802.11b radio, at regular intervals of time, a bitmap > > which describes the time slots where the radio should regard the virtual > > carrier sense as "positive," regardless of what transpires on the medium. > > Then certain sophisticated MAC algorithms can be implemented in the > > radio's host computer, and the results transformed into a virtual carrier > > sense bitmap which is uploaded to the radio. Now the radio can transmit > > at its full speed under influence of the virtual carrier sense uploaded > > by the host. > > > > If consumer radios allowed this sort of control over the virtual carrier > > sense, would that make them more desirable for research? > > > > Dave > > > > -- > > David Young OJC Technologies > > dyoung@ojctech.com Engineering from the Right Brain > > Urbana, IL * (217) 278-3933 > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 30 13:24:21 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01803 for ; Wed, 30 Oct 2002 13:24:21 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9UIQIa23774 for manet-archive@odin.ietf.org; Wed, 30 Oct 2002 13:26:18 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIQIv23771 for ; Wed, 30 Oct 2002 13:26:18 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01789 for ; Wed, 30 Oct 2002 13:23:50 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIITv23317; Wed, 30 Oct 2002 13:18:29 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIEvv23190 for ; Wed, 30 Oct 2002 13:14:57 -0500 Received: from parsmtp2.rd.francetelecom.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00357 for ; Wed, 30 Oct 2002 13:12:29 -0500 (EST) Received: from LANMHS20.rd.francetelecom.fr ([10.193.21.60]) by parsmtp2.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 30 Oct 2002 19:14:51 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Wed, 30 Oct 2002 19:14:51 +0100 Message-ID: <0489A7888F080B4BA73B53F7E145F29A03C0ED@lanmhs20.rd.francetelecom.fr> Thread-Topic: Bootstrap mechanism in Ad Hoc network Thread-Index: AcIX0x7WOuI3txYnSpehXgiGet9R8xoaJudAAADEvzA= From: "MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN" To: X-OriginalArrivalTime: 30 Oct 2002 18:14:51.0542 (UTC) FILETIME=[3D5AD360:01C28040] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9UIEwv23191 Subject: [manet] Bootstrap mechanism in Ad Hoc network Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi Dear What are the necessaries mechanisms allowing any host to form/join/leave an adhoc network? Any comments Cincerly Djamal _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 30 13:24:23 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01816 for ; Wed, 30 Oct 2002 13:24:23 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIITv23317; Wed, 30 Oct 2002 13:18:29 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIEvv23190 for ; Wed, 30 Oct 2002 13:14:57 -0500 Received: from parsmtp2.rd.francetelecom.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00357 for ; Wed, 30 Oct 2002 13:12:29 -0500 (EST) Received: from LANMHS20.rd.francetelecom.fr ([10.193.21.60]) by parsmtp2.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 30 Oct 2002 19:14:51 +0100 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Wed, 30 Oct 2002 19:14:51 +0100 Message-ID: <0489A7888F080B4BA73B53F7E145F29A03C0ED@lanmhs20.rd.francetelecom.fr> Thread-Topic: Bootstrap mechanism in Ad Hoc network Thread-Index: AcIX0x7WOuI3txYnSpehXgiGet9R8xoaJudAAADEvzA= From: "MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN" To: X-OriginalArrivalTime: 30 Oct 2002 18:14:51.0542 (UTC) FILETIME=[3D5AD360:01C28040] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9UIEwv23191 Subject: [manet] Bootstrap mechanism in Ad Hoc network Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi Dear What are the necessaries mechanisms allowing any host to form/join/leave an adhoc network? Any comments Cincerly Djamal _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 30 13:38:31 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02869 for ; Wed, 30 Oct 2002 13:38:31 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIWRv24036; Wed, 30 Oct 2002 13:32:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIV4v23971 for ; Wed, 30 Oct 2002 13:31:04 -0500 Received: from stl-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02080 for ; Wed, 30 Oct 2002 13:28:35 -0500 (EST) Received: from slb-av-02.boeing.com ([129.172.13.7]) by stl-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id MAA10951; Wed, 30 Oct 2002 12:30:57 -0600 (CST) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by slb-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id KAA22312; Wed, 30 Oct 2002 10:30:56 -0800 (PST) Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4]) by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g9UIUnr09946; Wed, 30 Oct 2002 10:30:50 -0800 (PST) Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2653.19) id ; Wed, 30 Oct 2002 13:30:49 -0500 Message-ID: From: "Manfredi, Albert E" To: "'MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN'" , manet@ietf.org Subject: RE: [manet] Bootstrap mechanism in Ad Hoc network Date: Wed, 30 Oct 2002 13:30:46 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN wrote: > Hi Dear > What are the necessaries mechanisms allowing any host to > form/join/leave > an adhoc network? > > Any comments MANET concerns itself primarily with routing inside this wireless network environment. Joining and leaving are going to impact routing tables, which would hopefully be dynamic and automatic. There _may_ be other mechanisms, such as DHCP, Router Discovery, Mobile IP registration with home agent, security logon requirements, IGMP join/leave reports if multicasting is used, and so on, added to the basic MANET routing protocols. I don't believe there is a single answer to your question. I believe that the answer is "it depends." Bert _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 30 13:41:33 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03059 for ; Wed, 30 Oct 2002 13:41:32 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9UIhUV25167 for manet-archive@odin.ietf.org; Wed, 30 Oct 2002 13:43:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIhUv25164 for ; Wed, 30 Oct 2002 13:43:30 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03030 for ; Wed, 30 Oct 2002 13:41:01 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIWRv24036; Wed, 30 Oct 2002 13:32:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIV4v23971 for ; Wed, 30 Oct 2002 13:31:04 -0500 Received: from stl-smtpout-01.boeing.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02080 for ; Wed, 30 Oct 2002 13:28:35 -0500 (EST) Received: from slb-av-02.boeing.com ([129.172.13.7]) by stl-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id MAA10951; Wed, 30 Oct 2002 12:30:57 -0600 (CST) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by slb-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id KAA22312; Wed, 30 Oct 2002 10:30:56 -0800 (PST) Received: from xch-phl-02p.ne.nos.boeing.com (xch-phl-02p.ne.nos.boeing.com [128.225.22.4]) by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id g9UIUnr09946; Wed, 30 Oct 2002 10:30:50 -0800 (PST) Received: by xch-phl-02p.ne.nos.boeing.com with Internet Mail Service (5.5.2653.19) id ; Wed, 30 Oct 2002 13:30:49 -0500 Message-ID: From: "Manfredi, Albert E" To: "'MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN'" , manet@ietf.org Subject: RE: [manet] Bootstrap mechanism in Ad Hoc network Date: Wed, 30 Oct 2002 13:30:46 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , MEDDOUR Djamal Eddine thesard FTRD/DAC/LAN wrote: > Hi Dear > What are the necessaries mechanisms allowing any host to > form/join/leave > an adhoc network? > > Any comments MANET concerns itself primarily with routing inside this wireless network environment. Joining and leaving are going to impact routing tables, which would hopefully be dynamic and automatic. There _may_ be other mechanisms, such as DHCP, Router Discovery, Mobile IP registration with home agent, security logon requirements, IGMP join/leave reports if multicasting is used, and so on, added to the basic MANET routing protocols. I don't believe there is a single answer to your question. I believe that the answer is "it depends." Bert _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 30 14:08:19 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04599 for ; Wed, 30 Oct 2002 14:08:19 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UJ1Tv25900; Wed, 30 Oct 2002 14:01:29 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIxCv25760 for ; Wed, 30 Oct 2002 13:59:12 -0500 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03960 for ; Wed, 30 Oct 2002 13:56:42 -0500 (EST) Received: from e500a.comp.nus.edu.sg (e500a.comp.nus.edu.sg [137.132.90.23]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id CAA00308 for ; Thu, 31 Oct 2002 02:59:04 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500a.comp.nus.edu.sg via csmap id 8188; Thu, 31 Oct 2002 02:51:13 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id CAA18314 for ; Thu, 31 Oct 2002 02:59:04 +0800 (GMT-8) Date: Thu, 31 Oct 2002 02:59:04 +0800 (GMT-8) From: Sourabh Sharma To: manet@ietf.org Subject: Re: [manet] Ad-hoc --> Ip of Nodes. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Wed, 30 Oct 2002 jomullen@nmsu.edu wrote: > In response to your first statement: > All nodes being on the same subnet means they share the same subnet mask, but > not necessarily that each has a direct connection to every other. Unless they > all are directly connected, you will need some routing protocol. If they are > also in motion, you will need a protocol that exchanges topological information > and updates routing tables as nodes change position. Yeah, you'll need a routing protocol definitely! What I said,which probably din get across properly, was that there is no need for a _special_ "adhoc" routing protocol, if we (manually) configure the routing table of the participating nodes to forward each other's packet correctly. Anyway, my main concern is --> why do the nodes need to be in the same subnet!!... AODV,DSR or any other RP for that matter should be able to find and consequently update routes, for sources (with random IP) trying to reach destinations with random IP which may or MAY NOT be in the same subnet. The RP should work for random IP addresses -- thats the bottomline for any ad-hoc routing protocol!! Regards, Sourabh. CiR, NUS. Singapore > > > > > Hello, > > Recently, I have set up an ad-hoc network. > > But I noticed that somehow, the node's needed to be > > configured to be in the same subnet. > > By right, in ad-hoc , nodes having any random IP addr > > should be able to find routes to any Ipaddr and the > > underlying Ad-hoc routing protocol should update the > > source's routing table accordingly. > > > > In the case when the nodes are in the same subnet, you > > actually dun need an ad-hoc routing protocol! as long > > you have the routing entries correctly configured, you > > can make the nodes forward each others data packets, and > > thus have an ad-hoc network without the use of any special > > "ad-hoc" routing protocol.!! > > > > > -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 30 14:12:50 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04868 for ; Wed, 30 Oct 2002 14:12:50 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9UJEmw27293 for manet-archive@odin.ietf.org; Wed, 30 Oct 2002 14:14:48 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UJEmv27290 for ; Wed, 30 Oct 2002 14:14:48 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04835 for ; Wed, 30 Oct 2002 14:12:19 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UJ1Tv25900; Wed, 30 Oct 2002 14:01:29 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UIxCv25760 for ; Wed, 30 Oct 2002 13:59:12 -0500 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03960 for ; Wed, 30 Oct 2002 13:56:42 -0500 (EST) Received: from e500a.comp.nus.edu.sg (e500a.comp.nus.edu.sg [137.132.90.23]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id CAA00308 for ; Thu, 31 Oct 2002 02:59:04 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500a.comp.nus.edu.sg via csmap id 8188; Thu, 31 Oct 2002 02:51:13 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id CAA18314 for ; Thu, 31 Oct 2002 02:59:04 +0800 (GMT-8) Date: Thu, 31 Oct 2002 02:59:04 +0800 (GMT-8) From: Sourabh Sharma To: manet@ietf.org Subject: Re: [manet] Ad-hoc --> Ip of Nodes. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Wed, 30 Oct 2002 jomullen@nmsu.edu wrote: > In response to your first statement: > All nodes being on the same subnet means they share the same subnet mask, but > not necessarily that each has a direct connection to every other. Unless they > all are directly connected, you will need some routing protocol. If they are > also in motion, you will need a protocol that exchanges topological information > and updates routing tables as nodes change position. Yeah, you'll need a routing protocol definitely! What I said,which probably din get across properly, was that there is no need for a _special_ "adhoc" routing protocol, if we (manually) configure the routing table of the participating nodes to forward each other's packet correctly. Anyway, my main concern is --> why do the nodes need to be in the same subnet!!... AODV,DSR or any other RP for that matter should be able to find and consequently update routes, for sources (with random IP) trying to reach destinations with random IP which may or MAY NOT be in the same subnet. The RP should work for random IP addresses -- thats the bottomline for any ad-hoc routing protocol!! Regards, Sourabh. CiR, NUS. Singapore > > > > > Hello, > > Recently, I have set up an ad-hoc network. > > But I noticed that somehow, the node's needed to be > > configured to be in the same subnet. > > By right, in ad-hoc , nodes having any random IP addr > > should be able to find routes to any Ipaddr and the > > underlying Ad-hoc routing protocol should update the > > source's routing table accordingly. > > > > In the case when the nodes are in the same subnet, you > > actually dun need an ad-hoc routing protocol! as long > > you have the routing entries correctly configured, you > > can make the nodes forward each others data packets, and > > thus have an ad-hoc network without the use of any special > > "ad-hoc" routing protocol.!! > > > > > -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Wed Oct 30 14:59:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07292 for ; Wed, 30 Oct 2002 14:59:07 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UJltv29322; Wed, 30 Oct 2002 14:47:55 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UJkvv29252 for ; Wed, 30 Oct 2002 14:46:57 -0500 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06497 for ; Wed, 30 Oct 2002 14:44:26 -0500 (EST) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id OAA07086; Wed, 30 Oct 2002 14:45:48 -0500 (EST) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002103014454927160 ; Wed, 30 Oct 2002 14:45:49 -0500 Message-Id: <5.1.1.5.2.20021030144357.03186440@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 30 Oct 2002 14:47:43 -0500 To: Sourabh Sharma , manet@ietf.org From: Joe Macker Subject: Re: [manet] Ad-hoc --> Ip of Nodes. In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 02:59 AM 10/31/2002 +0800, Sourabh Sharma wrote: >On Wed, 30 Oct 2002 jomullen@nmsu.edu wrote: >> In response to your first statement: >> All nodes being on the same subnet means they share the same subnet mask, but >> not necessarily that each has a direct connection to every other. Unless they >> all are directly connected, you will need some routing protocol. If they are >> also in motion, you will need a protocol that exchanges topological information >> and updates routing tables as nodes change position. > > Yeah, you'll need a routing protocol definitely! What I said,which >probably din get across properly, was that there is no need for a >_special_ "adhoc" routing protocol, if we (manually) configure the routing > table of the participating nodes to forward each other's packet >correctly. > > Anyway, my main concern is --> why do the nodes need to be in the same >subnet!!... They don't need to be. Perhaps an implementation limitation. > AODV,DSR or any other RP for that matter should be able to find > and consequently update routes, for sources (with random IP) trying > to reach destinations with random IP which may or MAY NOT be in the > same subnet. > The RP should work for random IP addresses -- thats the bottomline > for any ad-hoc routing protocol!! > > Regards, > Sourabh. > CiR, NUS. > Singapore > >> >> > >> > Hello, >> > Recently, I have set up an ad-hoc network. >> > But I noticed that somehow, the node's needed to be >> > configured to be in the same subnet. >> > By right, in ad-hoc , nodes having any random IP addr >> > should be able to find routes to any Ipaddr and the >> > underlying Ad-hoc routing protocol should update the >> > source's routing table accordingly. >> > >> > In the case when the nodes are in the same subnet, you >> > actually dun need an ad-hoc routing protocol! as long >> > you have the routing entries correctly configured, you >> > can make the nodes forward each others data packets, and >> > thus have an ad-hoc network without the use of any special >> > "ad-hoc" routing protocol.!! >> > >> > >> > >-------------------------------------------------- >There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 30 15:02:56 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07531 for ; Wed, 30 Oct 2002 15:02:55 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9UK4s530091 for manet-archive@odin.ietf.org; Wed, 30 Oct 2002 15:04:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UK4sv30088 for ; Wed, 30 Oct 2002 15:04:54 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07481 for ; Wed, 30 Oct 2002 15:02:24 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UJltv29322; Wed, 30 Oct 2002 14:47:55 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UJkvv29252 for ; Wed, 30 Oct 2002 14:46:57 -0500 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06497 for ; Wed, 30 Oct 2002 14:44:26 -0500 (EST) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id OAA07086; Wed, 30 Oct 2002 14:45:48 -0500 (EST) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002103014454927160 ; Wed, 30 Oct 2002 14:45:49 -0500 Message-Id: <5.1.1.5.2.20021030144357.03186440@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 30 Oct 2002 14:47:43 -0500 To: Sourabh Sharma , manet@ietf.org From: Joe Macker Subject: Re: [manet] Ad-hoc --> Ip of Nodes. In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 02:59 AM 10/31/2002 +0800, Sourabh Sharma wrote: >On Wed, 30 Oct 2002 jomullen@nmsu.edu wrote: >> In response to your first statement: >> All nodes being on the same subnet means they share the same subnet mask, but >> not necessarily that each has a direct connection to every other. Unless they >> all are directly connected, you will need some routing protocol. If they are >> also in motion, you will need a protocol that exchanges topological information >> and updates routing tables as nodes change position. > > Yeah, you'll need a routing protocol definitely! What I said,which >probably din get across properly, was that there is no need for a >_special_ "adhoc" routing protocol, if we (manually) configure the routing > table of the participating nodes to forward each other's packet >correctly. > > Anyway, my main concern is --> why do the nodes need to be in the same >subnet!!... They don't need to be. Perhaps an implementation limitation. > AODV,DSR or any other RP for that matter should be able to find > and consequently update routes, for sources (with random IP) trying > to reach destinations with random IP which may or MAY NOT be in the > same subnet. > The RP should work for random IP addresses -- thats the bottomline > for any ad-hoc routing protocol!! > > Regards, > Sourabh. > CiR, NUS. > Singapore > >> >> > >> > Hello, >> > Recently, I have set up an ad-hoc network. >> > But I noticed that somehow, the node's needed to be >> > configured to be in the same subnet. >> > By right, in ad-hoc , nodes having any random IP addr >> > should be able to find routes to any Ipaddr and the >> > underlying Ad-hoc routing protocol should update the >> > source's routing table accordingly. >> > >> > In the case when the nodes are in the same subnet, you >> > actually dun need an ad-hoc routing protocol! as long >> > you have the routing entries correctly configured, you >> > can make the nodes forward each others data packets, and >> > thus have an ad-hoc network without the use of any special >> > "ad-hoc" routing protocol.!! >> > >> > >> > >-------------------------------------------------- >There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Oct 30 17:46:09 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17004 for ; Wed, 30 Oct 2002 17:46:09 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9UMm8X09038 for manet-archive@odin.ietf.org; Wed, 30 Oct 2002 17:48:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UMm8v09035 for ; Wed, 30 Oct 2002 17:48:08 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16956 for ; Wed, 30 Oct 2002 17:45:38 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UMeEv08635; Wed, 30 Oct 2002 17:40:14 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UMcav08549 for ; Wed, 30 Oct 2002 17:38:36 -0500 Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16557 for ; Wed, 30 Oct 2002 17:36:06 -0500 (EST) Received: from mail.nps.navy.mil by [140.32.132.66] via smtpd (for [132.151.6.1]) with ESMTP; Wed, 30 Oct 2002 14:35:45 -0800 Received: from ro178-88.ro.nps.navy.mil (ro178-88.ro.nps.navy.mil [131.120.178.88]) by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id g9UMavb9028671; Wed, 30 Oct 2002 14:36:58 -0800 (PST) Subject: Re: [manet] controlling virtual carrier sense in 802.11 radios From: Rex Buddenberg To: Daniel Oldham Cc: manet@ietf.org In-Reply-To: <20021030.12231000@doldham.lerc.nasa.gov> References: <20021029011004.A31545@che.onthejob.net> <1035926926.1068.74.camel@localhost.localdomain> <20021030.12231000@doldham.lerc.nasa.gov> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 30 Oct 2002 15:35:07 -0800 Message-Id: <1036020908.1057.141.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Daniel, My vision of a scheduling algorithm would be a dual-queue affair where one queue is contention-based and is the means of entry into the second queue which is disciplined by the net controller publishing a schedule telling emitters how to take turns (i.e. no contention). So the net controller (satellite in your apparent vision, commsta ashore in mine (satellite is a bent pipe) obviously has some state knowledge at the data link layer -- knows who the subscribers in the second queue are. Pushing that data up to the routing information protocol is certainly a feasible action and an economical one because it entails no additional bits on the wire. The 'manet' aspect is that departures from the second (scheduled) queue might be less than graceful: - the graceful exit would be issuance of the data link equivalent of a FIN message and an Ack. No issue here. - in a dynamic topology (the point of MANET), exits would simply be registered as a station not transmitting at its scheduled time. Unfortunately, this silence could come from several causes many of which would be transient (momentary antenna shading, for example). How 'serious' should an outage be to be recognized as a topology change? And would this be a piece of data that the network scheduler would have in the normal course of business (I think the datum 'station x has missed n schedules' would be readily available)? Of the network segments that, say, an Army division might employ, I'd expect that the satellite segments to be among the most stable -- far more so than terrestrial LOS segments. This tends to mean to me that the MANET issues are less pressing in satcom network segments but the silent host problem is endemic. Any where near what you thought you were asking? On Wed, 2002-10-30 at 04:23, Daniel Oldham wrote: > Rex: > > If you need "either scheduling (all cases) or polling" then please > explain why you need an ad hoc algorithm for satellite communications. > Once a satellite establishes a link layer connection then the information > for routing is implied in the connection. The ad hoc algorithm then seems > to be just extra overhead on the satellite. > -- > Daniel R. Oldham > NASA Glenn Research Center > Oldham@grc.nasa.gov > > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< > > On 10/29/02, 4:28:45 PM, Rex Buddenberg wrote > regarding Re: [manet] controlling virtual carrier sense in 802.11 radios: > > > > David, > > > First, a caveat: we're outside the scope of MANET and into the data link > > layer. > > > That out of the way, you're right. The MAC (CSMA/CA) algorithm locked > > into 802.11 chips has a lot of room for improvement for wireless LANs. > > And a whole lot of need for improvement as soon as we get to larger > > scale such as satellite systems with significant propagation delay. You > > need either scheduling (all cases) or polling (where you have good > > interactivity) MAC. Algorithm aside, there appears to be no good way to > > insert such a tweak ... if you find one, let me know. > > > On Mon, 2002-10-28 at 23:10, David Young wrote: > > > > > > If researchers were able to exercise fine-grained control over the > > > virtual carrier sense in 802.11 radios, that would make possible a lot > > > of interesting experiments in arbitrating media access. > > > > > > Just for an example of a desirable control, say it is possible to > > > upload to an 802.11b radio, at regular intervals of time, a bitmap > > > which describes the time slots where the radio should regard the virtual > > > carrier sense as "positive," regardless of what transpires on the medium. > > > Then certain sophisticated MAC algorithms can be implemented in the > > > radio's host computer, and the results transformed into a virtual carrier > > > sense bitmap which is uploaded to the radio. Now the radio can transmit > > > at its full speed under influence of the virtual carrier sense uploaded > > > by the host. > > > > > > If consumer radios allowed this sort of control over the virtual carrier > > > sense, would that make them more desirable for research? > > > > > > Dave > > > > > > -- > > > David Young OJC Technologies > > > dyoung@ojctech.com Engineering from the Right Brain > > > Urbana, IL * (217) 278-3933 > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > _______________________________________________ > > 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-admin@ietf.org Wed Oct 30 17:46:14 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17017 for ; Wed, 30 Oct 2002 17:46:13 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UMeEv08635; Wed, 30 Oct 2002 17:40:14 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UMcav08549 for ; Wed, 30 Oct 2002 17:38:36 -0500 Received: from [140.32.132.66] (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16557 for ; Wed, 30 Oct 2002 17:36:06 -0500 (EST) Received: from mail.nps.navy.mil by [140.32.132.66] via smtpd (for [132.151.6.1]) with ESMTP; Wed, 30 Oct 2002 14:35:45 -0800 Received: from ro178-88.ro.nps.navy.mil (ro178-88.ro.nps.navy.mil [131.120.178.88]) by capella.nps.navy.mil (8.12.2/8.12.2) with ESMTP id g9UMavb9028671; Wed, 30 Oct 2002 14:36:58 -0800 (PST) Subject: Re: [manet] controlling virtual carrier sense in 802.11 radios From: Rex Buddenberg To: Daniel Oldham Cc: manet@ietf.org In-Reply-To: <20021030.12231000@doldham.lerc.nasa.gov> References: <20021029011004.A31545@che.onthejob.net> <1035926926.1068.74.camel@localhost.localdomain> <20021030.12231000@doldham.lerc.nasa.gov> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 30 Oct 2002 15:35:07 -0800 Message-Id: <1036020908.1057.141.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Daniel, My vision of a scheduling algorithm would be a dual-queue affair where one queue is contention-based and is the means of entry into the second queue which is disciplined by the net controller publishing a schedule telling emitters how to take turns (i.e. no contention). So the net controller (satellite in your apparent vision, commsta ashore in mine (satellite is a bent pipe) obviously has some state knowledge at the data link layer -- knows who the subscribers in the second queue are. Pushing that data up to the routing information protocol is certainly a feasible action and an economical one because it entails no additional bits on the wire. The 'manet' aspect is that departures from the second (scheduled) queue might be less than graceful: - the graceful exit would be issuance of the data link equivalent of a FIN message and an Ack. No issue here. - in a dynamic topology (the point of MANET), exits would simply be registered as a station not transmitting at its scheduled time. Unfortunately, this silence could come from several causes many of which would be transient (momentary antenna shading, for example). How 'serious' should an outage be to be recognized as a topology change? And would this be a piece of data that the network scheduler would have in the normal course of business (I think the datum 'station x has missed n schedules' would be readily available)? Of the network segments that, say, an Army division might employ, I'd expect that the satellite segments to be among the most stable -- far more so than terrestrial LOS segments. This tends to mean to me that the MANET issues are less pressing in satcom network segments but the silent host problem is endemic. Any where near what you thought you were asking? On Wed, 2002-10-30 at 04:23, Daniel Oldham wrote: > Rex: > > If you need "either scheduling (all cases) or polling" then please > explain why you need an ad hoc algorithm for satellite communications. > Once a satellite establishes a link layer connection then the information > for routing is implied in the connection. The ad hoc algorithm then seems > to be just extra overhead on the satellite. > -- > Daniel R. Oldham > NASA Glenn Research Center > Oldham@grc.nasa.gov > > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< > > On 10/29/02, 4:28:45 PM, Rex Buddenberg wrote > regarding Re: [manet] controlling virtual carrier sense in 802.11 radios: > > > > David, > > > First, a caveat: we're outside the scope of MANET and into the data link > > layer. > > > That out of the way, you're right. The MAC (CSMA/CA) algorithm locked > > into 802.11 chips has a lot of room for improvement for wireless LANs. > > And a whole lot of need for improvement as soon as we get to larger > > scale such as satellite systems with significant propagation delay. You > > need either scheduling (all cases) or polling (where you have good > > interactivity) MAC. Algorithm aside, there appears to be no good way to > > insert such a tweak ... if you find one, let me know. > > > On Mon, 2002-10-28 at 23:10, David Young wrote: > > > > > > If researchers were able to exercise fine-grained control over the > > > virtual carrier sense in 802.11 radios, that would make possible a lot > > > of interesting experiments in arbitrating media access. > > > > > > Just for an example of a desirable control, say it is possible to > > > upload to an 802.11b radio, at regular intervals of time, a bitmap > > > which describes the time slots where the radio should regard the virtual > > > carrier sense as "positive," regardless of what transpires on the medium. > > > Then certain sophisticated MAC algorithms can be implemented in the > > > radio's host computer, and the results transformed into a virtual carrier > > > sense bitmap which is uploaded to the radio. Now the radio can transmit > > > at its full speed under influence of the virtual carrier sense uploaded > > > by the host. > > > > > > If consumer radios allowed this sort of control over the virtual carrier > > > sense, would that make them more desirable for research? > > > > > > Dave > > > > > > -- > > > David Young OJC Technologies > > > dyoung@ojctech.com Engineering from the Right Brain > > > Urbana, IL * (217) 278-3933 > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 02:09:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08978 for ; Thu, 31 Oct 2002 02:09:42 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9V7Bki09470 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 02:11:46 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V7Bjv09467 for ; Thu, 31 Oct 2002 02:11:45 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08961 for ; Thu, 31 Oct 2002 02:09:11 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V73gv01063; Thu, 31 Oct 2002 02:03:42 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V6xlv00788 for ; Thu, 31 Oct 2002 01:59:47 -0500 Received: from stephens.ittc.ku.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29228 for ; Thu, 31 Oct 2002 01:57:12 -0500 (EST) Received: from ittc.ku.edu (fiasco.ittc.ku.edu [129.237.125.27]) by stephens.ittc.ku.edu (8.12.6/8.12.6/ITTC-ANTISPAM-ANTIVIRUS-3.0) with SMTP id g9V6xWbb008762 for ; Thu, 31 Oct 2002 00:59:32 -0600 From: Pradeepkumar Mani Received: from 221-sno-fw.eecs.ku.edu ([129.237.80.15]) (SquirrelMail authenticated user mpradeep) by secure.ittc.ukans.edu with HTTP; Thu, 31 Oct 2002 00:59:32 -0600 (CST) Message-ID: <1265.129.237.80.15.1036047572.squirrel@secure.ittc.ukans.edu> Date: Thu, 31 Oct 2002 00:59:32 -0600 (CST) To: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-VirusScan: Clean Content-Transfer-Encoding: 8bit Subject: [manet] Testing DSR over ethernet Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hi My apologies if you get multiple copies of this email. My friend, who is not a member of the group, tried to send the same email. Since he was not successful, I am sending it now. Sorry about that!! we are trying to run DSR (Alex Song's implementation) over an ethernet LAN. we are trying to set up a network (with eight nodes) as follows: node 1 is within the transmission range of nodes 2 and 3 but not other nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ (route request) and only nodes 2 and 3 have to send RREPs (route replies) and not the other nodes (including node 4 though they are all in the same broadcast medium - the wired ethernet). this is just to setup a multihop network. at node 4, we tried to block broadcast packets from node 1 using iptables so that node 4 would not reply to RREQs from node 1. when nodes 1 and 4 were the only ones up, this seemed to work (ie. we were not able to ping node 4 from node 1). then we up- ed node 3 (which is in the "transmission range" of both node 1 and node 4. we were able to ping node 3 from both node 1 and node 4). but we still we were unable to ping node 4 from node 1 (we were expecting node 3, being within the "transmission range" of node 4 to aid node 1 in reaching node 4. but this didnt happen). could anyone help us in figuring out what the problem is ? Any suggestions are most welcome (we have setting up VLANs in mind instead of using iptables, but would like to explore other options before disturbing the current network setup) we have tried to be as clear as possible in stating our problem. thanks in advance! regards girish & pradeep. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 02:09:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08991 for ; Thu, 31 Oct 2002 02:09:44 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V73gv01063; Thu, 31 Oct 2002 02:03:42 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V6xlv00788 for ; Thu, 31 Oct 2002 01:59:47 -0500 Received: from stephens.ittc.ku.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29228 for ; Thu, 31 Oct 2002 01:57:12 -0500 (EST) Received: from ittc.ku.edu (fiasco.ittc.ku.edu [129.237.125.27]) by stephens.ittc.ku.edu (8.12.6/8.12.6/ITTC-ANTISPAM-ANTIVIRUS-3.0) with SMTP id g9V6xWbb008762 for ; Thu, 31 Oct 2002 00:59:32 -0600 From: Pradeepkumar Mani Received: from 221-sno-fw.eecs.ku.edu ([129.237.80.15]) (SquirrelMail authenticated user mpradeep) by secure.ittc.ukans.edu with HTTP; Thu, 31 Oct 2002 00:59:32 -0600 (CST) Message-ID: <1265.129.237.80.15.1036047572.squirrel@secure.ittc.ukans.edu> Date: Thu, 31 Oct 2002 00:59:32 -0600 (CST) To: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal X-Mailer: SquirrelMail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-VirusScan: Clean Content-Transfer-Encoding: 8bit Subject: [manet] Testing DSR over ethernet Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit hi My apologies if you get multiple copies of this email. My friend, who is not a member of the group, tried to send the same email. Since he was not successful, I am sending it now. Sorry about that!! we are trying to run DSR (Alex Song's implementation) over an ethernet LAN. we are trying to set up a network (with eight nodes) as follows: node 1 is within the transmission range of nodes 2 and 3 but not other nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ (route request) and only nodes 2 and 3 have to send RREPs (route replies) and not the other nodes (including node 4 though they are all in the same broadcast medium - the wired ethernet). this is just to setup a multihop network. at node 4, we tried to block broadcast packets from node 1 using iptables so that node 4 would not reply to RREQs from node 1. when nodes 1 and 4 were the only ones up, this seemed to work (ie. we were not able to ping node 4 from node 1). then we up- ed node 3 (which is in the "transmission range" of both node 1 and node 4. we were able to ping node 3 from both node 1 and node 4). but we still we were unable to ping node 4 from node 1 (we were expecting node 3, being within the "transmission range" of node 4 to aid node 1 in reaching node 4. but this didnt happen). could anyone help us in figuring out what the problem is ? Any suggestions are most welcome (we have setting up VLANs in mind instead of using iptables, but would like to explore other options before disturbing the current network setup) we have tried to be as clear as possible in stating our problem. thanks in advance! regards girish & pradeep. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 02:53:21 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09803 for ; Thu, 31 Oct 2002 02:53:21 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V7kWv12179; Thu, 31 Oct 2002 02:46:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V7hGv12115 for ; Thu, 31 Oct 2002 02:43:16 -0500 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09591 for ; Thu, 31 Oct 2002 02:40:41 -0500 (EST) Received: (from dyoung@localhost) by che.onthejob.net (8.9.3/8.9.3) id BAA05571 for manet@ietf.org; Thu, 31 Oct 2002 01:43:05 -0600 Date: Thu, 31 Oct 2002 01:43:05 -0600 From: David Young To: manet@ietf.org Subject: Re: [manet] Testing DSR over ethernet Message-ID: <20021031014305.A4992@che.onthejob.net> Reply-To: dyoung@pobox.com Mail-Followup-To: David Young , manet@ietf.org References: <1265.129.237.80.15.1036047572.squirrel@secure.ittc.ukans.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1265.129.237.80.15.1036047572.squirrel@secure.ittc.ukans.edu>; from mpradeep@ittc.ku.edu on Thu, Oct 31, 2002 at 12:59:32AM -0600 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Have you monitored the network using tcpdump or ethereal? Also, have you compared the routing table with your expectations? That will help you to see what is going on, "on the wire." I think I might know what is happening. If nodes 1, 3, and 4 are configured as hosts on the same IP subnet, then node 3 will send ICMP Redirects to 1 and 4 whenever one tries to contact the other through 3. The reason is that as far as node 3 is concerned, 1 and 4 can reach each other directly, and so it tells them so. In a lot of IP implementations, such as NetBSD's and Linux's, it is default behavior for a router to honor ICMP Redirects. In Linux and in NetBSD, there are sysctl's which will turn off ICMP Redirects. (In Linux, a zillion sysctl's affect ICMP Redirects, and you may have to turn off more than one.) Dave On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > hi > > My apologies if you get multiple copies of this email. My friend, who is > not a member of the group, tried to send the same email. Since he was not > successful, I am sending it now. Sorry about that!! > > we are trying to run DSR (Alex Song's implementation) over an ethernet > LAN. we are trying to set up a network (with eight nodes) as follows: > node 1 is within the transmission range of nodes 2 and 3 but not other > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > (route request) and only nodes 2 and 3 have to send RREPs (route > replies) and not the other nodes (including node 4 though they are all > in the same broadcast medium - the wired ethernet). this is just to > setup a multihop network. > > at node 4, we tried to block broadcast packets from node 1 using > iptables so that node 4 would not reply to RREQs from node 1. > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > were not able to ping node 4 from node 1). then we up- ed node 3 (which > is in the "transmission range" of both node 1 and node 4. we were able > to ping node 3 from both node 1 and node 4). but we still we were > unable to ping node 4 from node 1 (we were expecting node 3, being > within the "transmission range" of node 4 to aid node 1 in reaching > node 4. but this didnt happen). > > could anyone help us in figuring out what the problem is ? Any suggestions > are most welcome (we have setting up VLANs in mind instead of using > iptables, but would like to explore other options before disturbing the > current network setup) > > we have tried to be as clear as possible in stating our problem. > > thanks in advance! > regards > girish & pradeep. > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 02:58:13 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09879 for ; Thu, 31 Oct 2002 02:58:13 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9V80IW12547 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 03:00:18 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V80Hv12544 for ; Thu, 31 Oct 2002 03:00:17 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09873 for ; Thu, 31 Oct 2002 02:57:42 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V7kWv12179; Thu, 31 Oct 2002 02:46:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V7hGv12115 for ; Thu, 31 Oct 2002 02:43:16 -0500 Received: from che.onthejob.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA09591 for ; Thu, 31 Oct 2002 02:40:41 -0500 (EST) Received: (from dyoung@localhost) by che.onthejob.net (8.9.3/8.9.3) id BAA05571 for manet@ietf.org; Thu, 31 Oct 2002 01:43:05 -0600 Date: Thu, 31 Oct 2002 01:43:05 -0600 From: David Young To: manet@ietf.org Subject: Re: [manet] Testing DSR over ethernet Message-ID: <20021031014305.A4992@che.onthejob.net> Reply-To: dyoung@pobox.com Mail-Followup-To: David Young , manet@ietf.org References: <1265.129.237.80.15.1036047572.squirrel@secure.ittc.ukans.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1265.129.237.80.15.1036047572.squirrel@secure.ittc.ukans.edu>; from mpradeep@ittc.ku.edu on Thu, Oct 31, 2002 at 12:59:32AM -0600 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Have you monitored the network using tcpdump or ethereal? Also, have you compared the routing table with your expectations? That will help you to see what is going on, "on the wire." I think I might know what is happening. If nodes 1, 3, and 4 are configured as hosts on the same IP subnet, then node 3 will send ICMP Redirects to 1 and 4 whenever one tries to contact the other through 3. The reason is that as far as node 3 is concerned, 1 and 4 can reach each other directly, and so it tells them so. In a lot of IP implementations, such as NetBSD's and Linux's, it is default behavior for a router to honor ICMP Redirects. In Linux and in NetBSD, there are sysctl's which will turn off ICMP Redirects. (In Linux, a zillion sysctl's affect ICMP Redirects, and you may have to turn off more than one.) Dave On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > hi > > My apologies if you get multiple copies of this email. My friend, who is > not a member of the group, tried to send the same email. Since he was not > successful, I am sending it now. Sorry about that!! > > we are trying to run DSR (Alex Song's implementation) over an ethernet > LAN. we are trying to set up a network (with eight nodes) as follows: > node 1 is within the transmission range of nodes 2 and 3 but not other > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > (route request) and only nodes 2 and 3 have to send RREPs (route > replies) and not the other nodes (including node 4 though they are all > in the same broadcast medium - the wired ethernet). this is just to > setup a multihop network. > > at node 4, we tried to block broadcast packets from node 1 using > iptables so that node 4 would not reply to RREQs from node 1. > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > were not able to ping node 4 from node 1). then we up- ed node 3 (which > is in the "transmission range" of both node 1 and node 4. we were able > to ping node 3 from both node 1 and node 4). but we still we were > unable to ping node 4 from node 1 (we were expecting node 3, being > within the "transmission range" of node 4 to aid node 1 in reaching > node 4. but this didnt happen). > > could anyone help us in figuring out what the problem is ? Any suggestions > are most welcome (we have setting up VLANs in mind instead of using > iptables, but would like to explore other options before disturbing the > current network setup) > > we have tried to be as clear as possible in stating our problem. > > thanks in advance! > regards > girish & pradeep. > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- David Young OJC Technologies dyoung@ojctech.com Engineering from the Right Brain Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 05:29:33 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11967 for ; Thu, 31 Oct 2002 05:29:33 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VANFv20933; Thu, 31 Oct 2002 05:23:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VAH9v20730 for ; Thu, 31 Oct 2002 05:17:09 -0500 Received: from cheviot1.ncl.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11730 for ; Thu, 31 Oct 2002 05:14:45 -0500 (EST) Received: from stavanger (stavanger.ncl.ac.uk [128.240.149.6]) by cheviot1.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id g9VAGM315377; Thu, 31 Oct 2002 10:16:22 GMT From: "Einar Vollset" To: "'Sourabh Sharma'" , Subject: RE: [manet] Ad-hoc --> Ip of Nodes. Date: Thu, 31 Oct 2002 10:16:08 -0000 Organization: University of Newcastle upon Tyne Message-ID: <001801c280c6$8adf5fd0$0695f080@stavanger> 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.3416 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Newcastle-MailScanner: Found to be clean (of known viruses) Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hello Sourabh, > Yeah, you'll need a routing protocol definitely! What I said,which > probably din get across properly, was that there is no need for a > _special_ "adhoc" routing protocol, if we (manually) configure the routing > table of the participating nodes to forward each other's packet > correctly. I'm confused. What do you mean by "(manually) configure" the routing table? The whole concept of a MANET is the requirement for packets to be multi-hop to reach their intended destination (if nodes are not direct neighbours). In addition to this, a MANET is by definition mobile, so the network topology changes rapidly, thus making the use of conventional routing protocols cumbersome as they were designed for fairly static networks with (conceptually) unlimited energy supply. I can't see how the nodes being on the same subnet will change any of this, as, in a MANET, IP addresses being on the same subnet means very little.. Cheers, Einar --------------------------- Einar Vollset PhD Student School of Computing Science University of Newcastle, UK http://vollset.org --------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 05:32:17 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12042 for ; Thu, 31 Oct 2002 05:32:17 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VAYAF21644 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 05:34:10 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VAYAv21641 for ; Thu, 31 Oct 2002 05:34:10 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12039 for ; Thu, 31 Oct 2002 05:31:46 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VANFv20933; Thu, 31 Oct 2002 05:23:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VAH9v20730 for ; Thu, 31 Oct 2002 05:17:09 -0500 Received: from cheviot1.ncl.ac.uk (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11730 for ; Thu, 31 Oct 2002 05:14:45 -0500 (EST) Received: from stavanger (stavanger.ncl.ac.uk [128.240.149.6]) by cheviot1.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id g9VAGM315377; Thu, 31 Oct 2002 10:16:22 GMT From: "Einar Vollset" To: "'Sourabh Sharma'" , Subject: RE: [manet] Ad-hoc --> Ip of Nodes. Date: Thu, 31 Oct 2002 10:16:08 -0000 Organization: University of Newcastle upon Tyne Message-ID: <001801c280c6$8adf5fd0$0695f080@stavanger> 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.3416 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Newcastle-MailScanner: Found to be clean (of known viruses) Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Sourabh, > Yeah, you'll need a routing protocol definitely! What I said,which > probably din get across properly, was that there is no need for a > _special_ "adhoc" routing protocol, if we (manually) configure the routing > table of the participating nodes to forward each other's packet > correctly. I'm confused. What do you mean by "(manually) configure" the routing table? The whole concept of a MANET is the requirement for packets to be multi-hop to reach their intended destination (if nodes are not direct neighbours). In addition to this, a MANET is by definition mobile, so the network topology changes rapidly, thus making the use of conventional routing protocols cumbersome as they were designed for fairly static networks with (conceptually) unlimited energy supply. I can't see how the nodes being on the same subnet will change any of this, as, in a MANET, IP addresses being on the same subnet means very little.. Cheers, Einar --------------------------- Einar Vollset PhD Student School of Computing Science University of Newcastle, UK http://vollset.org --------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 09:20:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20434 for ; Thu, 31 Oct 2002 09:20:44 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VEE1v01359; Thu, 31 Oct 2002 09:14:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VE87v01172 for ; Thu, 31 Oct 2002 09:08:07 -0500 Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19754 for ; Thu, 31 Oct 2002 09:05:39 -0500 (EST) Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g9VE80505565; Thu, 31 Oct 2002 15:08:00 +0100 (MET) Message-ID: <00a201c280ea$909ff5a0$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Pete Sholander" , References: Subject: Re: [manet] OLSR implementation Date: Thu, 31 Oct 2002 15:34:04 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Hello, Pete, Do you think that the MPR could be used on OSPF only for the wireless interfaces but also for the wired interface (as for the designated routers)? For the latter case, are the links enough sufficiently redundant to take advantage of MPRs? In the first case, one could imagine an extension of OSPF for wireless links (I think it is an original idea of Fred Backer). Philippe ----- Original Message ----- From: Pete Sholander To: ; ; Sent: Monday, October 28, 2002 6:09 PM Subject: Re: [manet] OLSR implementation > Gayathri, > > As another (possibly bogus!) thought ... > > OSPF runs over Non-Broadcast Multicast Access (NBMA) networks. (Check > the RFC for details. Not sure if the code at opsf.org implements that > feature though!) > > Maybe there's someway to extend OLSR to map its MPRs onto OSPF's > "Designated Router" concept. Sounds like an interesing thesis topic. > However, mobile ad hoc ATM networks are kind of passe by now. Do you > have a end-user application in mind? > > --Pete Sholander > > >>> "Philippe Jacquet" 10/28/02 11:32AM > >>> > Dear Gayathri, > > Sorry to have been late to answer. As far as I can see, the main > problem > with ATM interfaces is the broadcast, which is used in OLSR for > control > traffic and I don't know how it will work with ATM. Maybe a kind of > MARS > could be useful... > > Philippe > ----- Original Message ----- > From: Gayathri Chandrasekaran > To: > Sent: Sunday, October 20, 2002 9:54 PM > Subject: [manet] OLSR implementation > > > > Hello, > > I would like to know if OLSR runs over ATM interfaces.I'm trying to > > implement some version 7 features to the INRIA version 3 OLSR linux > > implementation. So for initial testing purposes can ATM interfaces > be > > used? > > > > thanks > > gayathri > > > > Gayathri Chandrasekaran > > Department of Electrical > > Engineering and Computer Science > > University of Kansas > > Lawrence,KS-66045. > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 09:26:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20833 for ; Thu, 31 Oct 2002 09:26:47 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VEShB02124 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 09:28:43 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VEShv02121 for ; Thu, 31 Oct 2002 09:28:43 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20796 for ; Thu, 31 Oct 2002 09:26:16 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VEE1v01359; Thu, 31 Oct 2002 09:14:01 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VE87v01172 for ; Thu, 31 Oct 2002 09:08:07 -0500 Received: from concorde.inria.fr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19754 for ; Thu, 31 Oct 2002 09:05:39 -0500 (EST) Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g9VE80505565; Thu, 31 Oct 2002 15:08:00 +0100 (MET) Message-ID: <00a201c280ea$909ff5a0$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Pete Sholander" , References: Subject: Re: [manet] OLSR implementation Date: Thu, 31 Oct 2002 15:34:04 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, Pete, Do you think that the MPR could be used on OSPF only for the wireless interfaces but also for the wired interface (as for the designated routers)? For the latter case, are the links enough sufficiently redundant to take advantage of MPRs? In the first case, one could imagine an extension of OSPF for wireless links (I think it is an original idea of Fred Backer). Philippe ----- Original Message ----- From: Pete Sholander To: ; ; Sent: Monday, October 28, 2002 6:09 PM Subject: Re: [manet] OLSR implementation > Gayathri, > > As another (possibly bogus!) thought ... > > OSPF runs over Non-Broadcast Multicast Access (NBMA) networks. (Check > the RFC for details. Not sure if the code at opsf.org implements that > feature though!) > > Maybe there's someway to extend OLSR to map its MPRs onto OSPF's > "Designated Router" concept. Sounds like an interesing thesis topic. > However, mobile ad hoc ATM networks are kind of passe by now. Do you > have a end-user application in mind? > > --Pete Sholander > > >>> "Philippe Jacquet" 10/28/02 11:32AM > >>> > Dear Gayathri, > > Sorry to have been late to answer. As far as I can see, the main > problem > with ATM interfaces is the broadcast, which is used in OLSR for > control > traffic and I don't know how it will work with ATM. Maybe a kind of > MARS > could be useful... > > Philippe > ----- Original Message ----- > From: Gayathri Chandrasekaran > To: > Sent: Sunday, October 20, 2002 9:54 PM > Subject: [manet] OLSR implementation > > > > Hello, > > I would like to know if OLSR runs over ATM interfaces.I'm trying to > > implement some version 7 features to the INRIA version 3 OLSR linux > > implementation. So for initial testing purposes can ATM interfaces > be > > used? > > > > thanks > > gayathri > > > > Gayathri Chandrasekaran > > Department of Electrical > > Engineering and Computer Science > > University of Kansas > > Lawrence,KS-66045. > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 10:40:40 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25908 for ; Thu, 31 Oct 2002 10:40:40 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VFgZJ07695 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 10:42:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VFgZv07692 for ; Thu, 31 Oct 2002 10:42:35 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25898 for ; Thu, 31 Oct 2002 10:40:08 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VFYEv06572; Thu, 31 Oct 2002 10:34:14 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VFV1v06385 for ; Thu, 31 Oct 2002 10:31:01 -0500 Received: from mx05.cluster1.charter.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25114 for ; Thu, 31 Oct 2002 10:28:34 -0500 (EST) Received: from [24.196.101.199] (HELO Dhcvkjx) by mx05.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 18406127 for manet@ietf.org; Thu, 31 Oct 2002 10:30:34 -0500 From: ccarter To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=UJV838Z622107EA8F0mB7xt6 Date: Thu, 31 Oct 2002 10:30:34 -0500 Message-ID: Subject: [manet] A very good tool Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --UJV838Z622107EA8F0mB7xt6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ------------------ Virus Warning Message (on ietf-mx) gen_background2 is of type executable and is removed. Please contact your network administrator for further information. --------------------------------------------------------- --UJV838Z622107EA8F0mB7xt6 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable This is a special good tool
I expect you would like it. --UJV838Z622107EA8F0mB7xt6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ------------------ Virus Warning Message (on ietf-mx) gen_background2 is removed from here because it is of type executable --------------------------------------------------------- --UJV838Z622107EA8F0mB7xt6 Content-Type: application/octet-stream; name=gen_background2[1].jpg Content-Transfer-Encoding: base64 Content-ID: /9j/4AAQSkZJRgABAQEASABIAAD/2wBDAAUDBAQEAwUEBAQFBQUGBwwIBwcHBw8LCwkMEQ8S EhEPERETFhwXExQaFRERGCEYGh0dHx8fExciJCIeJBweHx7/2wBDAQUFBQcGBw4ICA4eFBEU Hh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh7/wAAR CAElAWgDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl 5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk 5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDxT7q0Ou1fvbd1N8xVZVkWmzyeZIu37q1J qCrt+Wp2XbH/AL1QxbZPmanNJ5nzfwrQIeqsse1f4qZLGy05GaT5v7v3asLJ5se5lqhEUDSL Cyr95vu1NGNq7WWqjSKzfe27fu1dilVod391aAIXlW2/d7vvNUzRfu/lqi8HmrJN/E33atWt z/oO6T70f3qAIldopNrSfLVj+L5vm3VnMvnRtI3ys33as2cm63+b70fytUjJbl1Rmj3bWZar 3MWxVXb8u2kSPzWaZvvNU9sytbtHcf8ALOqEUHZo2X5tu6tW2tlWGNtv3l+9VBoPMWSZv+A1 bsZd1r5bfw1JRW1FVimVY22tJ96mxQtEy/3ad5TbmnZdzN93/ZqzBIrR/N95VoAqX7bWXa33 l+arSL5dqu2qu3zJGZv4vu1btmVYW8xv9X/eoAoXjLGy7fvN96plVW2+X92m/LM0km3733aj ik8lfLZvm+8tAEl0vk7fm+ZqtW0a+WtV7ONp5JJJPmX7q06KXypGhZtqr8ytQIj1aKOJlZZG 8xqkitla3/dtUXzSyNcyLu/hWlsZPKZlZvl+9QMkuolXa3mbZKmggj8v5W3L/FVLzGmmaX+H 7q1LYjyJGVm+VvmoFzFi5ZY4d33WrOlj2t8rfep91L503+ytNiX98sbfdb+KgYW/yt5n92rE EO35t27dVaX/AF3lL91at2u2GTazfK1ABPEsarJu+aiKBfvf3qjupfMuNqt8q0QTMs3l/wAN BXMWJVWONWb+Go4tqru3VXup/Mk2r91aW1k2ybZKCCeXaq+c33Vqozbm3Mv3qfdSefN5a/dW li+Vlib7rUDI4mVf3jL/ALtSxQrIu7+9RcMrSLCvyqtPi/dybd3y0ASyxbYfMb+H7tUfszMu 5W3NVqeTzZNu75VoVlVtu6gBsEar8zVG/wArbqLyb5vLX+GhdrMsbfxVRJJAu1fM3fLRTZ/v LHH91aKAJrnau3+9VX7r0StK0m7+GnKu6T5vu0AKi+WvzfxVJb1CzeY3+ytSQdGqRFxtq7VW omVd23d96kVv3bSNTPvbmaqGLLaeY37tvmpYk8v5ZG+996pY7mP7OzN95flqPa0i7m+9QBdV Nq7aoXnlwN5bfdb71W4Lr93833lqtPB57Nu/ioAseVHt+WqU6+Xdfu/u/wAVS2135Vm0cn+u j+Vf9qhImaPzG+83zNQA+JWX+Gqs+1r5V/u/6ypoLvy0kjk/1kf3aIrNmVpGb5m+ZqkZdZY9 vy7WWqE8ixyMqr/vVYtnWKNlk+8tCwM+6T+981AyeLa0a/3arTsq3W1V+X+KpHmWK3k3feX7 tU1W5jj3bdzNQBaiTbN/s/w1X1H/AFyqv/Aqt20qpbt5i/NHUECSSySM38VADn8to/lqndbf ljWPdJVhV8rzFb+H7tQxLtbzP4qALlqn+ix+X8rMvzVT1ZWZlX/lovzNUkc/kLI38P3qrRbm 3Tt95qBGtY+XLartWqGoosTeSv8ArG+ao45fskm7/lnIv/j1MiZtrTyfM38NAy7YyK0Ksq/7 NGo+Wyqv/LRaqwSLBcM3/LOSl8xmbzGX5moAkghjZfl+9TLyJY1/2v4aWD93J833WpJW8+b/ AGaAJrXa0K/L8y1JP5ca7mqGDdC21vutUd1KzMrMv7v+GgRJBHHJ8y0SxLGu7+Jvu0kCssi7 fu09l82bd/CtACxRr5fyr81RzxqnzMv7z+Gl/wBVdL/dps7+bcf7K/doAii27v7v96lg2w7p G+b+6tK0e2T5f4qc0e79383y0DIXVpGaSP8A4FTvO2qrSL838K0Luhk2/wALUt0vnSbv4Y6A I2k3SK33V/iqaJlXdI3/AAGmwW+5fm+61NuflmWNf9XHVEkN0u797T7LbHukb+H7tWNu1t38 LUrKrSfu12xrUlEibWXd/eopm5o2Xau5aKAG/wCsWnM3kx7f4mp/lbdu2ofL8y4ZpG+7QIR9 u5f/AB6plXcu1aiWP/vmpoFZYZJG+9/DQMbFIu7y5P4fvVK33lXb8tVoEZ23bf8Aeqbc0ce3 +KqJIvljk+Zfl/irR2r/AMBrNaNY490n3mq1A6rb+X/EtSMhnkZZflX92rfNVxVXb8rblpnl bY2X+9VTdMlm1uqtuZvlaqEQSzbrr7Sq/u42/wC+q1oJFkhWT+Fl3VUisljhVf8AZ+aplbyL XavzMv3VqRlG8XzJGuY1+WOtWJt+2SP7rVWePy7WTd95qqxSzWitbMrbpF/d0AXWdZJmZV3K rbd1XoPmjX+7tqnbQeVCq/eaqstzNFI0a7ttUIsSfvbptq/LH96rqqrR1iy3LRQ7V/i+9VqC eRrf5f4lqSh08q+cyxru2/eq1bNHKqyL/F8tZvlyRR7tu5mp0TNFu2/xfdWgCS+ZftW1dvy/ eoWBZ/3it/wGqcqtHIu77zVYilaL7v3aAG3Ue5lhX7y/eoeHzNv91vvUNuWTcy/NJ81Dy/Zm aTb8rfLQIjv4/M22y/dX5qZFJujZWX7vy09maNWkkX5mpjt5f75fur96gZHPGzSLAv3vvM1T 2u6Rfm+9HUEDbfmb7zVI8nlTLPH838LUAWbyRY4/JX71Ntm3yKtQIzbmkk/ip25tyzqtAE95 Nt2xr95qj+Wby1b7y01l3bpm+9/DSbWaSOT+7QIsvuijbb95vu0QSM25W+8tNVvMkZm+Vdvy 0iKyybv4qAFumaNd3/LRqWDbIq/3lqtfSM0m5v4fu0QNIzbqBlvcsat/eqvu8yTcv3qLxd0j N92o4Pmk+Wggkn3L+8b733VpsXnN8rfKtST/ALy6X5vlWn7JGb5aCyOVvIhb+9uqtF/db71W 5Y/Nbc33VpfKX5dv3qAGLN5a7tv+7SKzeZt3fLQ0bNJ833ajghkWRf7tAFnzFihbd95vlWik ePe3zfw0UALOzKqr/eqNv3f+7VjasjM27dTZY18vzG+WgRH8rbaHkZW2/wANLBtb5qllT93u /u0ADbWVVWq/mfvtv92nxeZ8y/3qRofL/ef3aAF8iR7j943y1Iz/AOkfL91aYskiWrL96o1j mf5l+7VCNB9qqu37tZ19PIsitH91auRqyx7Wp3kKy/8AAaAJYmWW3WRfustVmlXd935Votkk gVl/hapdqsv8O6gAiZZ1WZW2x/xVSl8668y6X/Vw/KtMl86JZId37uSrrQeXbqsbfdoAltpd 8PmN/wACrPubnfdMq/dVqjaSSP8Adr/y0p0UDM3yr81AF+0itXhfcvzbflqtK6rJ+7+VVpqs 0TNH/eq01pH9n3L97bUjLNttnj3VSnX5m8tvu1HA8iRt5bfep26Nbdo2bbJQMljVZ13N83y1 BOqrIsK/dptnOwjZt3+zUkUEjQtIy7m3UATQSxsjRtt3LWfeSefdeWrfu1ov2a3jWRflb7rV DErKq/7XzUATxSbYWWT7y/8AoNRXDecywK37v+KnTxttWf7tJFC0cbfxM1ADYo2aRo/7v3aS 4/dqsf8AFV1F2ssi/wAP3qq3sbM3mUALaq0kbR/xL92pWjaNfL/iam2qsy+Yv3lqdd0m6T+K gCJN33W/hpZ23Ksa/wDLShlk/vVIqtu3N93+GgBsEix/K33tvy1JOzLH975qZ5e6So5Vlk+a gQ2ddyqv8S/dqSJtkO7+9SQRM+7b/DSTxs0m5fmX+GgYeZ5y7d1CRtDCzfdZvlWo4o5FkVfu tU06ySN5nysq/L8tBAWrL5m1v+A1LO3kx/L/AKxvlWq6xfxL8tTKnntu/u0FEUCsvy7qlZmj X/apzQ7qasfmTfK27bQA2Ntsnzf3ac6si/7TfdqZo4/4fvU0LukVv7tAEO1kZf8Aaoqxt3vt ooArwfKytu+WpLyT7q/w0NAqSN/Cqr81N2xyR/7X8VADVVd27+9Ul0+1VjX7v8VL+7ZfvfKt MX51ZV+9QBHF95Wq9Jt8tf7tV5YP3dNTd5Pl7vu0ADKzL8v3atrtWHd/DTIl3Qq22o1Xa3l7 vvN92qJKfms115jfdVvlrV3L5aybvlpi2y/N8tQvG0jeX91d33aAFaVmZm/hqfdHHD5jf3aR rZWj21Ql8x2+zq25Y6BibWud0m7bV2RZHtVZW2t/FtqG1ZY/lZasQS7d0bVIzLSCSRWl+b5f u061lZVk+95i/LurSVNn3qzLpfLvv9mT71AD0jklXzm3bV+7V6zn+VtzVPFHG0Kqv3aoX22C barfe+8tAETSNIzbfu7vlpt0u7azN838VX18uK3VqyLqXczNQMGk3MqrV3Tp5GbyZN3+zUOj QebN5n92rmobYpFl+7JtoAp3n764bcv7uP5aVJFVljb+7VuK2jnt1ZWb5vmaqusRLEse1v3l AEG5ppP+mcdWbOZVmWNv4vu1U/1cKqv8VPl/49Wbd+8/hoAt3MqtJ5a/dX71RxL5zKu7/dqF 1X7OrL/wKrUUflwxyNUC5hJVWNlhX/gVNV/LmVf4WoZd26RW3bqY6+ZCzbfmX+KrGSv/AKza vzbvvU6JVf8Ad0yzj/d7m+9Uqp8zSbtqrQA2f5dsa/e/iogXb8rN8rU7buXzFbczUQR5hbzG oENlXyF8v+Jqjg2x/L/epsv7xt33ttPgXzN1Awddit837xqbA3k/Lu3K1TKqvuaoVhVm/urQ QSttVVVfvNUm7ypF8v7rVX/1m5l/hqaBVaFt33qCgumbbtX7zVHA2z/Zb+KpIG3N5n8S0792 yt/eWgBsrNFDu+8zNTWZlZdrU1ZtzM33mp8XlyUAJLM0ce7+JqKPLjlbb/wGigCSdt8ir/31 UMrbm+X/AIFTolZvvfeapmVYo/ur81AFdlwqqrbv71Iissm6jbtb5qniXbHuagBzSK3zfw1C zeWyt/FTomVf3dO+zbvmZqAJ2lXy1kX/AFdVGXzN0i/ep67VkWHdUk6NtZVWqESxTxtB5it8 y/L/AMCpvzN+8/iqnEqxzeX/ALVaCfMu2gBk8jNB5i1St4/Kbc33m+9U0+1f4v3a/eqPz49v 3vmqRk0+1Y/Mqsu5m8xvvU9l3r975akgVWVqAJp22w+Y1UXga5bzf++ajaTdcbWb92tacC/u 12/d20AQWk/lRt5n3o6qNulkaZl+9Rq237Uu3+H71TRNG6szN/u0EjYP9TJE33ttUVt2Zm3N 8tSX/wAzLtb5v4q0VgWSzVl+9QBDp0qxLJG3y7fmWoWZp5POb+H7tR3sTLGu1vmqVVVo/loL LNjOsW5ZG+Vvu1UZvtNxJM38P3aS8X9zGv8Ay0q5ZpbywrtX5lqQKG3Py/8AfNNi/eTL/dWp 9RiaKFVX7zN8tOsI1kjVvu7W+akA2D9zdKsi/u5KsXMvmSbV/wBWtF4sfk/N/rP4aLNVaP8A 2l+9TERq3lyKrfdkqSVVWRY4/wDgVF0sfltuotVXbuoAjWXy5tu75asXMitthX/gVRtEu1pG X5V+7REsc3+9VASR7Vb737tvvUXTR7VjX/eaneUqxs38K1XZVePd91t3zUAOZljZWX7rUTsv yqv8X3qP3cki/N+7X71OXbIrfL81ADUZY1+Wmy7WbatO27vvUKqsv+1QMbKrf3ac/wAy7V+9 /FTotzbmZv3a02Blk3fL96gQMqqu5aink2/8CqfbtZmb/vmmxKskbMy/7tAEUU3+z92pdscU LL/y0b7tTKse3bt3NVTc0jf7NAD4pFVflbdJRTrOJVkaSRflVd1FADm+7uX71SN+/Zd3y7aa kirHu3URSfN96pAc0H8X92o/N3Nt/hWrG7ZGzNVOL5ZKoAbd5n3atSy7Y121G7YqNZF8xY2o AieORW8z+KrMtz/oqyfxfd21JOuFqFljaRo2+796gCBFaSNmXd/vVOs7fZ/M/iX5dtOli2qv l1Vlby5I1Vfl3fNQMFikkhk3N96nR+RHbyNIu6SP5auMu2PatZt0u26Vv4V+9QIf9o2rtZfm qVZ4/s7fN81Vp4pGuG2r8v8AC1QzttuVZfmWP71Ay4se6Nv9qpbO7WK3mjk/1kf3aasqrtXb u3fdqveMrXSsq7lX5moAdFG3zST/AHmpkS7dy1fvNskatGvytVCVv3ny/eX71QBLa2jOvnt/ FU2nM0Ukkbf6v71SQTx/Z9u6qjzNHub+JqYiy0Mbs0jN96qkH7i6VWX5d1W7ORZ4/wDaouvL Vf8App/DQA23i8yaSZv4m+Wo4I1gvmjb/VyVasZY2jb+8v3qrzt+8X5dzNQMjnkVptv8K/dp 0W2G6jk3bof4qd9mWZd1NljWP5W+ZqAC5l8+6Zl+6v3aji8yCRZP4W+9U0Cq33V+ZadKvlw7 ZPmZvlWgRDPK0lx9zdGtPWRlkX+7RA235dvzVOyqv75v4VqgIZ5dzLH/AArUe5opGkWpN3mR t93dRA3mKzSfdWpAkeXzNsf8P3mps/8ArPl+7TIm8yTbtqfbGq7m/hqgImVVVY1b/aZqN7bq bu3Lu+61SIyrDub71BIxju2qv8VSSrtZdv8ADUbNJ5bNt+Zvu021maT5moLJJ2XyVjVvvfM1 RureX+7b7v3ak8xmZt38X3ab8qtQAN8yxru3SSfeqTayr8q7dtOgkbd5jL8rfdqSVtvzNQIj ldWhVo/9Y33qarRtH8v3qjVmZtzfKrU6DcrNu+7/ABNQA66nVrWOH+996ioZf3kjfN/u0VIy RY/M2q3+81DRfN8v3qYkjK3+9U8sm2PdQIZ9+Tazfdp7Rf3f4aqou6rTs23/AGaAGs25d38V NaBv733aakjK33amWf5fu1QCSybY1aqKbvM/2qk89t3zfd3U3b/F/DQSXVnVbXcv3vu1F5TN bs1QxTKu1V+ZW+9WjGsfl7dytuoAqLJKunsv/LZflWlS28y3Xc3zMvzUku6Ob5f9WtTxLu2t /C1ADVZYLFo/+Wi/dqklp5cO772771WJ23XDbV+VWps80isqq33qAIbX92zRyfNt+aNqnijV oWk/iaobpmaT5f4fvVatfmjVW/ioLI7GVY4ZIWX/AGlqKJfIjZpPvNSzt5cjLF822pGZbmFd v3qBDYIt3mfN8u3ctIse3bI33aJd0bKqt822p7Vlnh+b71SBVtW8i6kZf9Wy1E0kkjeZJ/wG n3Ssv7tW+am+c08axsvzL8tIY1JGt5Gk/hb71XbNlkbzG+9/DVN5G+WDb9771OgkZVZdvzLQ BdikZZtv8LUSx+fJu+7tqHzmjX/ptTop220xDtrRMskbf71MeRpZN392nvKvk/L97+Gki+6y t95aAIJ1ZdskfzMv3qfLM0v8O2p93lQs38TfKtQMu75d3zUDIUVmZv7ytT5Zv4VXaq1JFC0O 5mp6qrKytt3fw0AV9zbtzVNLKsu1d3yqvzUr7WXd5f3agi+8y7fvVQDt393738NSvHukVv4W +9TIPLWTd/CtOi3bm3fxUAS3Xyxr/wCO0eWrbV27d33qJW/75WmMzfeZvvUCGT/NcfK3yr92 ny/LtX+L+KnRKqx7m/hpu1mVZGb71AD1Vnh/2Vo3M+1W+7/FTtyxLtX/AIFULMy/vG/iqQLE u2T5VX5ahZpNvl/3qmV1Rdy1VinZpPMb7tAD2h2q3y/NRUsske1WX+Jd1FAyBm3R7ttOi/eL t3bttNlXatCbY/mX/gVIglWOkbczKv8AdpWkbb975aavyruplD3Xcu3bULt+7+X71TSyLt/3 qhgVf+A1RI3bHtVWpz7fs/3f9mrDRrtqGJvLkVv+Wf3aAKe5VVl/hWrlrL5drtVf92nz20cq /wB2mKzLt2/6tfloAmRf3f8AvUxn227R/wAVTeWrN/srVaVl+0bv4V+WgBq+Wv7tmb5qbFDt WRf7v3WonjaRlaP5lo8xl+7QBMixwxruXc396iCRUWT5f92rarbtCrSfxfxVRupId22H7qt9 6gBdqxru/vfeqqrNBJIyruVquPH5kKsrfLVWdWWbarfKq1AEO5l+b+KpvtEkKrJ95WqN18/a y/eX71OlXzdsC/w/eoAdEzSSbpPvNUd1G0Mn2lV+796nRNuX5v8AWK22i6Zmk8lW+X+KgBlv 8sbTt96SpVba3mR/8CWmr5e1o9vzKtOibb+4/ioLCKOSRpJG/i+7/s01Vkjjbb96rNr8ysv9 2ll27dv8TUEEcDedJu+6tSfxblot41VWj/iWmyzLFHtX/WNQA5tzTLu+6tN27fm/iogk3Kqt 95akbcsbf3qsAldmVf7qrVeVZPl/u1IjNt2tUzMsa1ACMu7b/Cv8VJJtZvlpNrL975lanfdX d/FTLIpVZtqqu1V+9T1+6u771I26NV/vN96i2bczNIu3y/u0iB7K0m1W+VVpyReb8tR/vFbc 38X3qsMyrHuplEbKzbV/hWmq25v9mhkaNtzN8zfep0UaxqzM25f4aAI542aNV3bfmpvlt8q0 bWb9438VSSyeWrNQBHOu393upGVW+792k8ttvmM25mqTcsfzN91VoAZ/sUVD8zM0n+1RQA+X +7u3bae0e5qgi+X5mqdplWP7tAxyru+X+7T2Xcu2q8TN96nPM23733qBCr838Py1N5dRp93/ ANBp2/5aokdLukVVX+9TZ4v3e2mozN977tWWVVX/AGaAIEeSSz2t96q6zfvFiWplkbc0n8P9 2m/ZvLkWT+KgByLcR+dH/C33arpG25lb+GrDTt53+zUu1XZW/vUARWbMtuy/xN92oZ4JlZak lZvOVlX5Y6sMyuvy0AQrHItvJHu3VC/7mPa1Tbvm2r91abdR+ZtagBtqzRqzL93+Gq9xJ5O2 rX3f3a/w1HLA1ztb/aoAbZsys0ka/eqNmaFmjVfmb71SSrtby/4VpsTNtk+T9592kBGm5f8A SV/4FUkUUnltIy/NQ/lsqw7vu/eqezkaTda/xN93dTApvHJ/rl+8tT2sO795/E1SzrsWOHd8 38VNgVo2Zd3+7UFkvlsreYv8NNRvNk87b92pJ2+6v8TURbV3R/3qCAVP4qhnj3SKzfd/hqSW Tavlr/rKNv3VZqsCNV+bctOeRpF3L/DTm/d/u2b5mpsH7tvL2/LQAf6xV/vf3qJFb5f7q05t yMzbfvfdprfL8qtQA7+FVp23c33vur92oVk2q38TU2Vmg+ZfvfxUASxNub5mp7fvJNv9371I qxrH5n3mb7tHl+W3zfe/iqSiT/WRsq1Hu2sqt/DUiMscbNULwbWWT+KgCw3zs3y/eqNV+ZY2 b7v3lqbcqx+c33aqLJtXzNvzNQBbkKyN8tVZV8xvL3fdqZpNse7+Ko/L2x7v4v4qAGuzbdv8 NN2/L5O7czU9Vby91RJEyx7v4qBlhYtqqu35qKiSRvvM3yrRQIc8a7fl+81QN5bMsf8AdapJ ZNsfy/eampbqsO3dQMejfM1N27pNyr+7pqMvl/e/efd21JEzKu3b96qAcq/do8xpfl2/damv Jt+Whfl/4FQQTMv7tlpv7xrdY6du2puqNd27zKAJfLwyr/DUV5uaPy/4t1P89vm/2ai+ZmWb /wAdoAr26t5ix7qvfMsO2moq7vMprSNJJu/u0APRaZL+5b723d8q1ZVVba38NVpf38itt+Vf u0ACqy1JtZVZqlVt8fy1UvJGeZV/u/KtADYty7l2/NT1WaCPzFqWJVZfMX738VV7qXzW27vl WgBvlbmZWb5qJYWVWbdRLC0+3b95fvVGzS+c0G75VWgA2rDb+Xt3SN826iBmWNrlfvR1Iisy 7V+9Tp28tfLVflb5moAZLHIyrcSfxfNSxMzfN/EtPgl3QtDtpNu1Vj/76oLG7ZGkZvvf3acj SMy/L81Ogk2t5H8P8NSMu2Py/wCJqCCPbt3SfeZqdt3bW/iWhI/JZl3bl/hp0rbflX7zUAR+ Vuk85W3fw02Xd9oVaGbyf4vlpzNuXd/FQASs27733ajiXdJTl+X/ANmoRWT5t25v4agAaNdz Nu+ZabtZmb5fvVL/AKtdv8VErbY/l+81WWMiVY/lWT7tSxbmm/vK1MdfK2/xf3qldlht/MqB CKsazbWb5VqXbu/4DVRJI2X/AGqsSy7bfcv8Xy0EkW7dJ5e7ctG3bu3VBFH5LK26rLsu3c33 qCyN5F3KrVaVlb+LatQLtaFo9vzfe3UiTrHC3y7mpiHO0ccjf3ac37yNlX71MijVo2Zm+Zm+ amRTtHGzfxL92gCSWNfLVf4v4qKIt0kfmN95vmopDKittuFaT5l+7V5Y1kVt1UWjZW+b71WG mbydq/eoII2jXzty/dq0q/LVfayrUbStGvl/xUAWHXzWVv7tSMvy1DFuVfmqRpGVf9lqsBrq 0nyr91akVV8uo1Xaqt/F/FUnmKse6gBvyt8v97+GpPLqHb8vmfxVbVla387d8yr92gCt5e3c u75aNqqu2my7mDSU613NHuZfmWgBX3LHt3bd1SeUq7V/u1BLukk3f3angdWj+b7y0AMaNo92 1vvVnyyMslXmbzW3L/DUbRrJu+X5loAbEzRrub5d1R3Uflqq1M7LI391VqSNPP8AvfeWgBsD N5e77rNTliVW3N96o5WVpNq/dWnKzSfLuoAd5flyeZuqu25ZNrfMrfxVJOzblXd8tR+Z5n7v dQAQR7ZJGX7tDqyxySfxU15Nv7tadasrfK33aAG2H7xWZv4f4qsfK37zdRcsqqsMa/dqNNys vy/LQBN95fvVG/zq0i02VtreX/E1OWRV3L/DQBXVWaRV/vVNtVvut8y1I+5VVfl3N92msvlr uX7y1AEa7V3Kyt81OiVfL3R/eX+9TlmZo9u35mpzKsarVgL95fmpjeWrbf7tObdHDu/h/hpr R/u12/eqAI/O+bbt3VIyq3y/3akRvLt9u395TW+7tVdzL95qAK8sf7yplWNZFVvur/6FUi+W qrJ/F/do8tfLX+JmoAhl+9ToFVZPLanNt27v4loiVVXazfM38VACrH8rf7VRxLHHMu77tOef bC21vmpqKvlr8vzNTLLXlqzf7NQTsvnKv8P8VOilZflb71CxrtZm/ipEDtrNHtX5aKYs6rHI q/w0UchQ9trN5lVXkb/XqvyrTpZJFt9u35mpsUe6NVagkmRvMj8yqu3zG8+jay/um+61TeWv +rWgByyKy0L+827m+7Ubo0cbVIu6NVagCR9snyrTVh8xtrN8q0Ntjj3L/FTVXy49y/eqwJG3 L8tNiVf9Xu+9Tmk2x+Y38VVYmkeT5l+9QBoIm1aj3Ku5aXd+5Zm/hqt5y7m3UAWol2rUcu2N m/h3UJPGy/7tRu3mbmb/AIDQBZj+Vf8AZqKdV+b+81EG1tu5vu1DOvmTNIrf7K0ASRQfu6c2 2BdzfKtLZy/u2jb7y1FLIskzM33VoAd5fy7l+61N2+T826nRP83lt/FUdwvnNt/hWoANrN83 96oXi/dtJt+Zfu05FZW27vlWpp1Zv91aAI/J/wBHWT+LbUNrHtZmZvlWrEE21tv3lp0u2RvL VdtWAIiyfvFanbo2+9u2rUf+r/3aJ22x7V/i+9UAR/61vMX/AHakWHb8zVD+8VVZfl+app/3 irGv8VAEMsm1ty/NtqaKTzP4qb5arQkax/d+81AEkW3zv92pmZWX+9Vdl8xf3f3lp3mfu/L2 /NQAeYu77u7bUi7mXdULrtVdtSPL+52r95qABPvNuX/dqNGZflp3mKv7tqc+1l3KvzUAEW3d tZfu06B18xVZabuWPbG33moZfm3L96gBJZV+0fd+WnSptZVX+KpEj+XbUbNujb/np91aZQz5 VkVVXcq/epzN8yqq02WNvLVV/h+9RE37v9595fu0iRsrN5m1W+Vam3blqPYrL833qjVWVW/8 doAm2ru/9Cop0UX7n73zNRQBXlVmXzN33amWRfJ3LTvu/u1qm67Z1g3bVagA8tpI2k3fN/DU 0DfKrVMqqrLt+aqs6+XJtX7rUATffb71Tbf3fzVXRWWpJZNsf+9QAKqttqb7y7du2q8Stt3V JPJtj3LQBHuVv3f91qmZFb921RxKzLu/iqWdv3PmL95asCKXbHIq7v3f8VQzxx/eWpEXzFZm +81QxfKzK38NAEcTK061YlVmmVf4Voigjjh3bfm3VHLJt/4DUAOVtu5dv/AqkVvLhqukjTLu /hq1EyzR7f4qAKrblk8xW27qN3l/K38VOul8yT5furTYl85vL/iWgCw7KsaybfmpybfL+X+K o4vmm2t91akVtu5WoAa+2Ndzfep0Um5d23+L7tQrukuP92ppd0bbWX71ADpVXa0jKu3/AGaj 3blZlX5qa0jSMqr91aJaAHbt0fmMvy0QeXJ8rLTXXcyr/CtNdvm3f3aAJrpvLXbHUcDLJ/D8 1OaTzNv/AI9UbLtVmX+GgCRo1/75o3bv4f8AdpryLNt2/wDAqkZfu7f4aACJF+Zvu02Lczf7 P8NDNvZV3f71O8r+CgB0UTM3zL8v96oX+aT7vy7vlpzySLHtXdVd5JN/3W20ASRW8jSbmqws n7z7v7v7tR28zSR7dvzVY2qqrHQAyWDd83/fNIsrK3+r+VaRmk8vbup6xtt+agCVfmVpP4ag 8xmkaRf9WtOWVlhaNf4mpzKvl+Wv/AqAI3k2/dbduqq8kkkm7b8tTPBt3L/e+7UjR+WqrQAb WkjXbTZPvVIsjIv+zTUXdQAJIrf8BoqFo2jZv9qigB0Um75mWqrK0m6T+992nXEjL+7X+KnM 21VWgB1vI21m/u01G8xtzfeqGX5W+X+KpD99aALSt8rVGq+cu2my/wAP+1UjLtX5asCSJWjV lb7tQuyqu2pp5Y/s6qv3mqNYvl/2qAHWsn8LU5mjVtv8NR7lVVbb81NdZG2rUAWlVWX5fu1X l8tWap4pVW0aPb+8qKKP5W3fxVYEqR/u938NVJW2ybf4f4qsRT7I5FqFY13MzfxUANl/dxrt /iotV+9J93dQrbo9tG7c21furQBDdM0a/wC1REzbVkb5WqZYfP8AlZvmWo7jasu3+FaAB2ZW VV+anNJtiZl+9uptuu1m/u0eWzTK+35d1QBNF8zbl+VqkZVaP5pNzVCu6Obd/DTpZNzfL92g ARvlb+9RKqrGv8TU35o2X5vlanOrSttVflWgAtV2sys26nSqq/M33ajVvLk+VaklbdQARf3W Wjy2jVmqP958zM1SMzSbY1+9/FQA2Bvm+7tqzLFtXzv7tRMrLGtO8z/R/L+agCNGZZN2371S LJ83+7TX+ZVVajb5V2/xfxUAHmN5jSfwtUm3d977rVD95l+X5asKzLH5a/eoAj+ZW8xfu1Zi G5VkamfKqqtR/N/qf9qgAaSSRmkX7q1Mrbm3fw03aySKu35dtNYSI3l/3qAGvuZmkX7q1LH8 y7v4f4qXbsXazVDKkke5Vb5WoAGZpJNy/dj+7U+7zFpEXy49tQs7L8v96rAGb5tu6nJJ/dqP dtX/AGqbBIyqy/3qgCRm8xm+b7tFN27V3UUAV33NI1O2/wAX8K03bTd3l/J/eoAEb73y1JE3 97+Gms3y01/m20ATQMrM27+KrES7flb7tRpH8q7aWT7tAEStum+78tWkXFQ7f3dO8z93t/iq wI926Tbt+WrMqeXD5jfMyrUSruXbt+ajc3lsslAFVJ5JJNy/dq40m2Nd38VNS22r/vUeXuVl b+GgCvLJub5V+WrSKsirtqGKL+Jl+9TkXy2ZW+7/AA7aAG3TbflWqqrctI237tXlh3LuZfma iL93I1ICvL+5j3M3zf7NNVdzbl+ZWqwsPmyNuX5mpyQfZmZo/wCGmBDLuj+Vf7tTRbpI1jb7 y0RLu3SN96nfdbzFqAI5/lVV/iamou1trL8392pEWSWbc1E8Ui/M27dQAXC7Y1og+6y/xU3a 0n/AVprqy/vKsCR12wtuX5qjTcu1W/iqRtzf7tQ/M0lAEj7l27vu06JfLbc38VO2tIy7vlVa c/zfdqAGyttX733ajRm/1jfdqPczNtpyxySNtX+KgCTdt+b+Gmq7M25l+VqbtbcsLL/FUzqs a0AN2szKu3aq/wAVNZmbdIrfL/dpz+YsbRrRErbfm+7VgOWRWXdT42j2tNMzLJ/yzqDy2Vtv 96nTx7mX/ZqAJ2lWSNWVfu1A26Vmk3fd+7TUjbdt/vVNsZfl2/doAr+Z81OdmZtyt92ieNt2 7+9Tol2/7VAEit5kdV22tI3+zUyLtVm3bd38NRqtADdrSfdprx7dzLUjfJ826mp80fy0AEUu 5vL/AIqKjVdsjN/FRQAituXdTEj3SbqklXa1ORW21ZY1futSwR7tzUfw1Jt2xqv8VADom2/e +7QrbpKR91ES7V20CJ0X5f8AZqDd+8+VflqX5vLZai2tH8tAEsrL8u2o2Zt3y07a21aPKkVf m+9QBaX5o91VZfMZpNtTQM0cbR/3vu0RRt827/gVABEvmKrVBdMzSbV+6tSqrR7tv8X3aFgX btb71ABA3mx/7VQz7vM+X+GpPL8lmZf4qmji/dtu/ioAbEyyKrfxLUM8jMzKtSNG0bfL/FUs UCrH81AEUSq8K/3qjuP+ecdSS/uG+X+KpIk2rub7zfdoAjtm2fK1E7NItR3W6Jlbdt3VaWL9 2rUAV4F3fu93zVHc7VZlVqdeK0TKyt8zVCsMkki0ATQbtvl0rMq/d+9TLmNolX5/vVGsMjbd v3aBk8W5m+ZvmpZdqttX7tSJFt+Zm+bbVafd8q0CHL/ealjlaCTcvzLTYo/3bN/epPKZodtA D2fzZPO/ianK25fm/hqu8bIqt/tVMkTbaAGxN+8Zv4mp0snzfLR5fl/M1M27W27qAFRfM+b/ AJaU/c38P8NI0nlruoVfl3f3qBjdrSNu/ioll3Mq/wB2n7fl3btq1VRVWT5moEP3eY25af5n y7aVI1j+b+GkdVjVf9qgZH80n8VSrKu3b/dqNW8ptzfdallVfloAa22ZqRPlkVf4akij8td3 8NMlXbJtoAdu3SNt+7RRBGyqzUUiCWLa3zN92olbczNUrIqx7d3zNUWymUKq+Y3zfw1JEvmb pGpGXau3+Jlp0TN92gAVlZt38K1Iu1vmoaJVbbTZU2fxfe+WqEMZtzbl/h+7U8SLKqyULBtG 2m/6ptu7arUARyMzSbl+6tW1ljlVWpViXaq1Xb5Jdv8AC33qAHXLbplaNdqrU8EivHu/iX71 OWNVXbVaeNVuNqs25loArTu0km5fur92rdt88ayf99VWSDa21qnaSOKP5m2tJQUVrlpZZv3a /KtWrZmZdrfw/eoVW8tfL/76pty0cLKzN+82/NUiFk+dWbd8tOs5/MVlk+9H/wCg0+OJXj/2 WqlfQLHIu1mZtvzVQhGbz5mb+GpraVgrK38NWbaOOOHcv3WqpfbfMVV+9/Ft/u1IyNkknVpN v+7UtjOscbRyN935lq3A0bQrt+6y1S1BI0ZVVf3jLVCIpX8ySSRvu/dWptOuVVWjkb7vzVHA jMv3flbbTb6CNGWONf3n3mqSh08/mszfw/dWnWL+X+7b/eotoNzLJuXy6LyOONdq/NI392gQ 5JGnk3fw/wANO8uPbtb71SWyxtArLUd40ca7W+aRqADbvX5furUkW3btpYNrQLt+7UF1KsP/ AF0b7tAFe8k8yTb/AAq22rFnKrLtb+GnRQRyxLJ/F/FVeUR2y/N8zN92gAupfMk2r91aWDbL 9771RRRbm+X7tTbY4P3jfe/hoGRXUm6Tav3VqW2bcu3+KhIVZt38LU5ljjj3L97d8tAEd5Ou 7b/d+7SRKtxtVvvUkscbfvNzf7tMRlj+b/vmgCy7LLJt/hWmqu6RlpsDbWXb92ppWWNlb+9Q Iq3CtNJtX/Vx1LArM23+KliVW3baJdsK+Y3/AAGgZHdS/wDLNfmVaWKPzG3fxURbVqTd5a7v urQAfxbf7tFM8z7vy/eooAk+87E06HmiigQxR5kshaiMsSCW6UUVQixAfMGWqvK7SM26iigC 5bHzIlLVC4yxfuKKKAJ7aRpYlLdqikHmFi1FFAE1v88Sk9qhlGZWNFFBRKoyAfSs6djJLIW/ hGBRRQSWNOYrbvu+fZ0zVTc0s8rM3VmooqSi9p0rYkRvmEYytVIXaSR5GPzGiiiQFrTpGAnQ /MEORUVn+9aWVvvGiigBbDh5kHSM5WmW5+0M0kn3qKKokfaf6907A5pyfvJJHbqaKKAK9kxW WSEfdzmktZGlZ5G+8GxRRQBLYOYriSFfu4zUO8yCSVvvUUVJRbsmIOztVK6fzbklh0GKKKBE +nyN5jxfwmoZv3twd3aiigcSSHicp2NMmOZj7UUUAWLfgAetJIMzBV+UCiij7IiNVGSPVqrX JxcvF/CnSiigY6zJW6EZ+YGpLt/MlY42+V93FFFAiWH5cY71XvpGadEPQUUVQhYjwop00jNK qHpRRUlD7f5gymiiipYH/9=9 --UJV838Z622107EA8F0mB7xt6-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 10:40:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25921 for ; Thu, 31 Oct 2002 10:40:42 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VFYEv06572; Thu, 31 Oct 2002 10:34:14 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VFV1v06385 for ; Thu, 31 Oct 2002 10:31:01 -0500 Received: from mx05.cluster1.charter.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25114 for ; Thu, 31 Oct 2002 10:28:34 -0500 (EST) Received: from [24.196.101.199] (HELO Dhcvkjx) by mx05.cluster1.charter.net (CommuniGate Pro SMTP 3.5.9) with SMTP id 18406127 for manet@ietf.org; Thu, 31 Oct 2002 10:30:34 -0500 From: ccarter To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=UJV838Z622107EA8F0mB7xt6 Date: Thu, 31 Oct 2002 10:30:34 -0500 Message-ID: Subject: [manet] A very good tool Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --UJV838Z622107EA8F0mB7xt6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ------------------ Virus Warning Message (on ietf-mx) gen_background2 is of type executable and is removed. Please contact your network administrator for further information. --------------------------------------------------------- --UJV838Z622107EA8F0mB7xt6 Content-Type: text/html; Content-Transfer-Encoding: quoted-printable This is a special good tool
I expect you would like it. --UJV838Z622107EA8F0mB7xt6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ------------------ Virus Warning Message (on ietf-mx) gen_background2 is removed from here because it is of type executable --------------------------------------------------------- --UJV838Z622107EA8F0mB7xt6 Content-Type: application/octet-stream; name=gen_background2[1].jpg Content-Transfer-Encoding: base64 Content-ID: /9j/4AAQSkZJRgABAQEASABIAAD/2wBDAAUDBAQEAwUEBAQFBQUGBwwIBwcHBw8LCwkMEQ8S EhEPERETFhwXExQaFRERGCEYGh0dHx8fExciJCIeJBweHx7/2wBDAQUFBQcGBw4ICA4eFBEU Hh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh7/wAAR CAElAWgDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl 5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk 5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDxT7q0Ou1fvbd1N8xVZVkWmzyeZIu37q1J qCrt+Wp2XbH/AL1QxbZPmanNJ5nzfwrQIeqsse1f4qZLGy05GaT5v7v3asLJ5se5lqhEUDSL Cyr95vu1NGNq7WWqjSKzfe27fu1dilVod391aAIXlW2/d7vvNUzRfu/lqi8HmrJN/E33atWt z/oO6T70f3qAIldopNrSfLVj+L5vm3VnMvnRtI3ys33as2cm63+b70fytUjJbl1Rmj3bWZar 3MWxVXb8u2kSPzWaZvvNU9sytbtHcf8ALOqEUHZo2X5tu6tW2tlWGNtv3l+9VBoPMWSZv+A1 bsZd1r5bfw1JRW1FVimVY22tJ96mxQtEy/3ad5TbmnZdzN93/ZqzBIrR/N95VoAqX7bWXa33 l+arSL5dqu2qu3zJGZv4vu1btmVYW8xv9X/eoAoXjLGy7fvN96plVW2+X92m/LM0km3733aj ik8lfLZvm+8tAEl0vk7fm+ZqtW0a+WtV7ONp5JJJPmX7q06KXypGhZtqr8ytQIj1aKOJlZZG 8xqkitla3/dtUXzSyNcyLu/hWlsZPKZlZvl+9QMkuolXa3mbZKmggj8v5W3L/FVLzGmmaX+H 7q1LYjyJGVm+VvmoFzFi5ZY4d33WrOlj2t8rfep91L503+ytNiX98sbfdb+KgYW/yt5n92rE EO35t27dVaX/AF3lL91at2u2GTazfK1ABPEsarJu+aiKBfvf3qjupfMuNqt8q0QTMs3l/wAN BXMWJVWONWb+Go4tqru3VXup/Mk2r91aW1k2ybZKCCeXaq+c33Vqozbm3Mv3qfdSefN5a/dW li+Vlib7rUDI4mVf3jL/ALtSxQrIu7+9RcMrSLCvyqtPi/dybd3y0ASyxbYfMb+H7tUfszMu 5W3NVqeTzZNu75VoVlVtu6gBsEar8zVG/wArbqLyb5vLX+GhdrMsbfxVRJJAu1fM3fLRTZ/v LHH91aKAJrnau3+9VX7r0StK0m7+GnKu6T5vu0AKi+WvzfxVJb1CzeY3+ytSQdGqRFxtq7VW omVd23d96kVv3bSNTPvbmaqGLLaeY37tvmpYk8v5ZG+996pY7mP7OzN95flqPa0i7m+9QBdV Nq7aoXnlwN5bfdb71W4Lr93833lqtPB57Nu/ioAseVHt+WqU6+Xdfu/u/wAVS2135Vm0cn+u j+Vf9qhImaPzG+83zNQA+JWX+Gqs+1r5V/u/6ypoLvy0kjk/1kf3aIrNmVpGb5m+ZqkZdZY9 vy7WWqE8ixyMqr/vVYtnWKNlk+8tCwM+6T+981AyeLa0a/3arTsq3W1V+X+KpHmWK3k3feX7 tU1W5jj3bdzNQBaiTbN/s/w1X1H/AFyqv/Aqt20qpbt5i/NHUECSSySM38VADn8to/lqndbf ljWPdJVhV8rzFb+H7tQxLtbzP4qALlqn+ix+X8rMvzVT1ZWZlX/lovzNUkc/kLI38P3qrRbm 3Tt95qBGtY+XLartWqGoosTeSv8ArG+ao45fskm7/lnIv/j1MiZtrTyfM38NAy7YyK0Ksq/7 NGo+Wyqv/LRaqwSLBcM3/LOSl8xmbzGX5moAkghjZfl+9TLyJY1/2v4aWD93J833WpJW8+b/ AGaAJrXa0K/L8y1JP5ca7mqGDdC21vutUd1KzMrMv7v+GgRJBHHJ8y0SxLGu7+Jvu0kCssi7 fu09l82bd/CtACxRr5fyr81RzxqnzMv7z+Gl/wBVdL/dps7+bcf7K/doAii27v7v96lg2w7p G+b+6tK0e2T5f4qc0e79383y0DIXVpGaSP8A4FTvO2qrSL838K0Luhk2/wALUt0vnSbv4Y6A I2k3SK33V/iqaJlXdI3/AAGmwW+5fm+61NuflmWNf9XHVEkN0u797T7LbHukb+H7tWNu1t38 LUrKrSfu12xrUlEibWXd/eopm5o2Xau5aKAG/wCsWnM3kx7f4mp/lbdu2ofL8y4ZpG+7QIR9 u5f/AB6plXcu1aiWP/vmpoFZYZJG+9/DQMbFIu7y5P4fvVK33lXb8tVoEZ23bf8Aeqbc0ce3 +KqJIvljk+Zfl/irR2r/AMBrNaNY490n3mq1A6rb+X/EtSMhnkZZflX92rfNVxVXb8rblpnl bY2X+9VTdMlm1uqtuZvlaqEQSzbrr7Sq/u42/wC+q1oJFkhWT+Fl3VUisljhVf8AZ+aplbyL XavzMv3VqRlG8XzJGuY1+WOtWJt+2SP7rVWePy7WTd95qqxSzWitbMrbpF/d0AXWdZJmZV3K rbd1XoPmjX+7tqnbQeVCq/eaqstzNFI0a7ttUIsSfvbptq/LH96rqqrR1iy3LRQ7V/i+9VqC eRrf5f4lqSh08q+cyxru2/eq1bNHKqyL/F8tZvlyRR7tu5mp0TNFu2/xfdWgCS+ZftW1dvy/ eoWBZ/3it/wGqcqtHIu77zVYilaL7v3aAG3Ue5lhX7y/eoeHzNv91vvUNuWTcy/NJ81Dy/Zm aTb8rfLQIjv4/M22y/dX5qZFJujZWX7vy09maNWkkX5mpjt5f75fur96gZHPGzSLAv3vvM1T 2u6Rfm+9HUEDbfmb7zVI8nlTLPH838LUAWbyRY4/JX71Ntm3yKtQIzbmkk/ip25tyzqtAE95 Nt2xr95qj+Wby1b7y01l3bpm+9/DSbWaSOT+7QIsvuijbb95vu0QSM25W+8tNVvMkZm+Vdvy 0iKyybv4qAFumaNd3/LRqWDbIq/3lqtfSM0m5v4fu0QNIzbqBlvcsat/eqvu8yTcv3qLxd0j N92o4Pmk+Wggkn3L+8b733VpsXnN8rfKtST/ALy6X5vlWn7JGb5aCyOVvIhb+9uqtF/db71W 5Y/Nbc33VpfKX5dv3qAGLN5a7tv+7SKzeZt3fLQ0bNJ833ajghkWRf7tAFnzFihbd95vlWik ePe3zfw0UALOzKqr/eqNv3f+7VjasjM27dTZY18vzG+WgRH8rbaHkZW2/wANLBtb5qllT93u /u0ADbWVVWq/mfvtv92nxeZ8y/3qRofL/ef3aAF8iR7j943y1Iz/AOkfL91aYskiWrL96o1j mf5l+7VCNB9qqu37tZ19PIsitH91auRqyx7Wp3kKy/8AAaAJYmWW3WRfustVmlXd935Votkk gVl/hapdqsv8O6gAiZZ1WZW2x/xVSl8668y6X/Vw/KtMl86JZId37uSrrQeXbqsbfdoAltpd 8PmN/wACrPubnfdMq/dVqjaSSP8Adr/y0p0UDM3yr81AF+0itXhfcvzbflqtK6rJ+7+VVpqs 0TNH/eq01pH9n3L97bUjLNttnj3VSnX5m8tvu1HA8iRt5bfep26Nbdo2bbJQMljVZ13N83y1 BOqrIsK/dptnOwjZt3+zUkUEjQtIy7m3UATQSxsjRtt3LWfeSefdeWrfu1ov2a3jWRflb7rV DErKq/7XzUATxSbYWWT7y/8AoNRXDecywK37v+KnTxttWf7tJFC0cbfxM1ADYo2aRo/7v3aS 4/dqsf8AFV1F2ssi/wAP3qq3sbM3mUALaq0kbR/xL92pWjaNfL/iam2qsy+Yv3lqdd0m6T+K gCJN33W/hpZ23Ksa/wDLShlk/vVIqtu3N93+GgBsEix/K33tvy1JOzLH975qZ5e6So5Vlk+a gQ2ddyqv8S/dqSJtkO7+9SQRM+7b/DSTxs0m5fmX+GgYeZ5y7d1CRtDCzfdZvlWo4o5FkVfu tU06ySN5nysq/L8tBAWrL5m1v+A1LO3kx/L/AKxvlWq6xfxL8tTKnntu/u0FEUCsvy7qlZmj X/apzQ7qasfmTfK27bQA2Ntsnzf3ac6si/7TfdqZo4/4fvU0LukVv7tAEO1kZf8Aaoqxt3vt ooArwfKytu+WpLyT7q/w0NAqSN/Cqr81N2xyR/7X8VADVVd27+9Ul0+1VjX7v8VL+7ZfvfKt MX51ZV+9QBHF95Wq9Jt8tf7tV5YP3dNTd5Pl7vu0ADKzL8v3atrtWHd/DTIl3Qq22o1Xa3l7 vvN92qJKfms115jfdVvlrV3L5aybvlpi2y/N8tQvG0jeX91d33aAFaVmZm/hqfdHHD5jf3aR rZWj21Ql8x2+zq25Y6BibWud0m7bV2RZHtVZW2t/FtqG1ZY/lZasQS7d0bVIzLSCSRWl+b5f u061lZVk+95i/LurSVNn3qzLpfLvv9mT71AD0jklXzm3bV+7V6zn+VtzVPFHG0Kqv3aoX22C barfe+8tAETSNIzbfu7vlpt0u7azN838VX18uK3VqyLqXczNQMGk3MqrV3Tp5GbyZN3+zUOj QebN5n92rmobYpFl+7JtoAp3n764bcv7uP5aVJFVljb+7VuK2jnt1ZWb5vmaqusRLEse1v3l AEG5ppP+mcdWbOZVmWNv4vu1U/1cKqv8VPl/49Wbd+8/hoAt3MqtJ5a/dX71RxL5zKu7/dqF 1X7OrL/wKrUUflwxyNUC5hJVWNlhX/gVNV/LmVf4WoZd26RW3bqY6+ZCzbfmX+KrGSv/AKza vzbvvU6JVf8Ad0yzj/d7m+9Uqp8zSbtqrQA2f5dsa/e/iogXb8rN8rU7buXzFbczUQR5hbzG oENlXyF8v+Jqjg2x/L/epsv7xt33ttPgXzN1Awddit837xqbA3k/Lu3K1TKqvuaoVhVm/urQ QSttVVVfvNUm7ypF8v7rVX/1m5l/hqaBVaFt33qCgumbbtX7zVHA2z/Zb+KpIG3N5n8S0792 yt/eWgBsrNFDu+8zNTWZlZdrU1ZtzM33mp8XlyUAJLM0ce7+JqKPLjlbb/wGigCSdt8ir/31 UMrbm+X/AIFTolZvvfeapmVYo/ur81AFdlwqqrbv71Iissm6jbtb5qniXbHuagBzSK3zfw1C zeWyt/FTomVf3dO+zbvmZqAJ2lXy1kX/AFdVGXzN0i/ep67VkWHdUk6NtZVWqESxTxtB5it8 y/L/AMCpvzN+8/iqnEqxzeX/ALVaCfMu2gBk8jNB5i1St4/Kbc33m+9U0+1f4v3a/eqPz49v 3vmqRk0+1Y/Mqsu5m8xvvU9l3r975akgVWVqAJp22w+Y1UXga5bzf++ajaTdcbWb92tacC/u 12/d20AQWk/lRt5n3o6qNulkaZl+9Rq237Uu3+H71TRNG6szN/u0EjYP9TJE33ttUVt2Zm3N 8tSX/wAzLtb5v4q0VgWSzVl+9QBDp0qxLJG3y7fmWoWZp5POb+H7tR3sTLGu1vmqVVVo/loL LNjOsW5ZG+Vvu1UZvtNxJM38P3aS8X9zGv8Ay0q5ZpbywrtX5lqQKG3Py/8AfNNi/eTL/dWp 9RiaKFVX7zN8tOsI1kjVvu7W+akA2D9zdKsi/u5KsXMvmSbV/wBWtF4sfk/N/rP4aLNVaP8A 2l+9TERq3lyKrfdkqSVVWRY4/wDgVF0sfltuotVXbuoAjWXy5tu75asXMitthX/gVRtEu1pG X5V+7REsc3+9VASR7Vb737tvvUXTR7VjX/eaneUqxs38K1XZVePd91t3zUAOZljZWX7rUTsv yqv8X3qP3cki/N+7X71OXbIrfL81ADUZY1+Wmy7WbatO27vvUKqsv+1QMbKrf3ac/wAy7V+9 /FTotzbmZv3a02Blk3fL96gQMqqu5aink2/8CqfbtZmb/vmmxKskbMy/7tAEUU3+z92pdscU LL/y0b7tTKse3bt3NVTc0jf7NAD4pFVflbdJRTrOJVkaSRflVd1FADm+7uX71SN+/Zd3y7aa kirHu3URSfN96pAc0H8X92o/N3Nt/hWrG7ZGzNVOL5ZKoAbd5n3atSy7Y121G7YqNZF8xY2o AieORW8z+KrMtz/oqyfxfd21JOuFqFljaRo2+796gCBFaSNmXd/vVOs7fZ/M/iX5dtOli2qv l1Vlby5I1Vfl3fNQMFikkhk3N96nR+RHbyNIu6SP5auMu2PatZt0u26Vv4V+9QIf9o2rtZfm qVZ4/s7fN81Vp4pGuG2r8v8AC1QzttuVZfmWP71Ay4se6Nv9qpbO7WK3mjk/1kf3aasqrtXb u3fdqveMrXSsq7lX5moAdFG3zST/AHmpkS7dy1fvNskatGvytVCVv3ny/eX71QBLa2jOvnt/ FU2nM0Ukkbf6v71SQTx/Z9u6qjzNHub+JqYiy0Mbs0jN96qkH7i6VWX5d1W7ORZ4/wDaouvL Vf8App/DQA23i8yaSZv4m+Wo4I1gvmjb/VyVasZY2jb+8v3qrzt+8X5dzNQMjnkVptv8K/dp 0W2G6jk3bof4qd9mWZd1NljWP5W+ZqAC5l8+6Zl+6v3aji8yCRZP4W+9U0Cq33V+ZadKvlw7 ZPmZvlWgRDPK0lx9zdGtPWRlkX+7RA235dvzVOyqv75v4VqgIZ5dzLH/AArUe5opGkWpN3mR t93dRA3mKzSfdWpAkeXzNsf8P3mps/8ArPl+7TIm8yTbtqfbGq7m/hqgImVVVY1b/aZqN7bq bu3Lu+61SIyrDub71BIxju2qv8VSSrtZdv8ADUbNJ5bNt+Zvu021maT5moLJJ2XyVjVvvfM1 RureX+7b7v3ak8xmZt38X3ab8qtQAN8yxru3SSfeqTayr8q7dtOgkbd5jL8rfdqSVtvzNQIj ldWhVo/9Y33qarRtH8v3qjVmZtzfKrU6DcrNu+7/ABNQA66nVrWOH+996ioZf3kjfN/u0VIy RY/M2q3+81DRfN8v3qYkjK3+9U8sm2PdQIZ9+Tazfdp7Rf3f4aqou6rTs23/AGaAGs25d38V NaBv733aakjK33amWf5fu1QCSybY1aqKbvM/2qk89t3zfd3U3b/F/DQSXVnVbXcv3vu1F5TN bs1QxTKu1V+ZW+9WjGsfl7dytuoAqLJKunsv/LZflWlS28y3Xc3zMvzUku6Ob5f9WtTxLu2t /C1ADVZYLFo/+Wi/dqklp5cO772771WJ23XDbV+VWps80isqq33qAIbX92zRyfNt+aNqnijV oWk/iaobpmaT5f4fvVatfmjVW/ioLI7GVY4ZIWX/AGlqKJfIjZpPvNSzt5cjLF822pGZbmFd v3qBDYIt3mfN8u3ctIse3bI33aJd0bKqt822p7Vlnh+b71SBVtW8i6kZf9Wy1E0kkjeZJ/wG n3Ssv7tW+am+c08axsvzL8tIY1JGt5Gk/hb71XbNlkbzG+9/DVN5G+WDb9771OgkZVZdvzLQ BdikZZtv8LUSx+fJu+7tqHzmjX/ptTop220xDtrRMskbf71MeRpZN392nvKvk/L97+Gki+6y t95aAIJ1ZdskfzMv3qfLM0v8O2p93lQs38TfKtQMu75d3zUDIUVmZv7ytT5Zv4VXaq1JFC0O 5mp6qrKytt3fw0AV9zbtzVNLKsu1d3yqvzUr7WXd5f3agi+8y7fvVQDt393738NSvHukVv4W +9TIPLWTd/CtOi3bm3fxUAS3Xyxr/wCO0eWrbV27d33qJW/75WmMzfeZvvUCGT/NcfK3yr92 ny/LtX+L+KnRKqx7m/hpu1mVZGb71AD1Vnh/2Vo3M+1W+7/FTtyxLtX/AIFULMy/vG/iqQLE u2T5VX5ahZpNvl/3qmV1Rdy1VinZpPMb7tAD2h2q3y/NRUsske1WX+Jd1FAyBm3R7ttOi/eL t3bttNlXatCbY/mX/gVIglWOkbczKv8AdpWkbb975aavyruplD3Xcu3bULt+7+X71TSyLt/3 qhgVf+A1RI3bHtVWpz7fs/3f9mrDRrtqGJvLkVv+Wf3aAKe5VVl/hWrlrL5drtVf92nz20cq /wB2mKzLt2/6tfloAmRf3f8AvUxn227R/wAVTeWrN/srVaVl+0bv4V+WgBq+Wv7tmb5qbFDt WRf7v3WonjaRlaP5lo8xl+7QBMixwxruXc396iCRUWT5f92rarbtCrSfxfxVRupId22H7qt9 6gBdqxru/vfeqqrNBJIyruVquPH5kKsrfLVWdWWbarfKq1AEO5l+b+KpvtEkKrJ95WqN18/a y/eX71OlXzdsC/w/eoAdEzSSbpPvNUd1G0Mn2lV+796nRNuX5v8AWK22i6Zmk8lW+X+KgBlv 8sbTt96SpVba3mR/8CWmr5e1o9vzKtOibb+4/ioLCKOSRpJG/i+7/s01Vkjjbb96rNr8ysv9 2ll27dv8TUEEcDedJu+6tSfxblot41VWj/iWmyzLFHtX/WNQA5tzTLu+6tN27fm/iogk3Kqt 95akbcsbf3qsAldmVf7qrVeVZPl/u1IjNt2tUzMsa1ACMu7b/Cv8VJJtZvlpNrL975lanfdX d/FTLIpVZtqqu1V+9T1+6u771I26NV/vN96i2bczNIu3y/u0iB7K0m1W+VVpyReb8tR/vFbc 38X3qsMyrHuplEbKzbV/hWmq25v9mhkaNtzN8zfep0UaxqzM25f4aAI542aNV3bfmpvlt8q0 bWb9438VSSyeWrNQBHOu393upGVW+792k8ttvmM25mqTcsfzN91VoAZ/sUVD8zM0n+1RQA+X +7u3bae0e5qgi+X5mqdplWP7tAxyru+X+7T2Xcu2q8TN96nPM23733qBCr838Py1N5dRp93/ ANBp2/5aokdLukVVX+9TZ4v3e2mozN977tWWVVX/AGaAIEeSSz2t96q6zfvFiWplkbc0n8P9 2m/ZvLkWT+KgByLcR+dH/C33arpG25lb+GrDTt53+zUu1XZW/vUARWbMtuy/xN92oZ4JlZak lZvOVlX5Y6sMyuvy0AQrHItvJHu3VC/7mPa1Tbvm2r91abdR+ZtagBtqzRqzL93+Gq9xJ5O2 rX3f3a/w1HLA1ztb/aoAbZsys0ka/eqNmaFmjVfmb71SSrtby/4VpsTNtk+T9592kBGm5f8A SV/4FUkUUnltIy/NQ/lsqw7vu/eqezkaTda/xN93dTApvHJ/rl+8tT2sO795/E1SzrsWOHd8 38VNgVo2Zd3+7UFkvlsreYv8NNRvNk87b92pJ2+6v8TURbV3R/3qCAVP4qhnj3SKzfd/hqSW Tavlr/rKNv3VZqsCNV+bctOeRpF3L/DTm/d/u2b5mpsH7tvL2/LQAf6xV/vf3qJFb5f7q05t yMzbfvfdprfL8qtQA7+FVp23c33vur92oVk2q38TU2Vmg+ZfvfxUASxNub5mp7fvJNv9371I qxrH5n3mb7tHl+W3zfe/iqSiT/WRsq1Hu2sqt/DUiMscbNULwbWWT+KgCw3zs3y/eqNV+ZY2 b7v3lqbcqx+c33aqLJtXzNvzNQBbkKyN8tVZV8xvL3fdqZpNse7+Ko/L2x7v4v4qAGuzbdv8 NN2/L5O7czU9Vby91RJEyx7v4qBlhYtqqu35qKiSRvvM3yrRQIc8a7fl+81QN5bMsf8AdapJ ZNsfy/eampbqsO3dQMejfM1N27pNyr+7pqMvl/e/efd21JEzKu3b96qAcq/do8xpfl2/damv Jt+Whfl/4FQQTMv7tlpv7xrdY6du2puqNd27zKAJfLwyr/DUV5uaPy/4t1P89vm/2ai+ZmWb /wAdoAr26t5ix7qvfMsO2moq7vMprSNJJu/u0APRaZL+5b723d8q1ZVVba38NVpf38itt+Vf u0ACqy1JtZVZqlVt8fy1UvJGeZV/u/KtADYty7l2/NT1WaCPzFqWJVZfMX738VV7qXzW27vl WgBvlbmZWb5qJYWVWbdRLC0+3b95fvVGzS+c0G75VWgA2rDb+Xt3SN826iBmWNrlfvR1Iisy 7V+9Tp28tfLVflb5moAZLHIyrcSfxfNSxMzfN/EtPgl3QtDtpNu1Vj/76oLG7ZGkZvvf3acj SMy/L81Ogk2t5H8P8NSMu2Py/wCJqCCPbt3SfeZqdt3bW/iWhI/JZl3bl/hp0rbflX7zUAR+ Vuk85W3fw02Xd9oVaGbyf4vlpzNuXd/FQASs27733ajiXdJTl+X/ANmoRWT5t25v4agAaNdz Nu+ZabtZmb5fvVL/AKtdv8VErbY/l+81WWMiVY/lWT7tSxbmm/vK1MdfK2/xf3qldlht/MqB CKsazbWb5VqXbu/4DVRJI2X/AGqsSy7bfcv8Xy0EkW7dJ5e7ctG3bu3VBFH5LK26rLsu3c33 qCyN5F3KrVaVlb+LatQLtaFo9vzfe3UiTrHC3y7mpiHO0ccjf3ac37yNlX71MijVo2Zm+Zm+ amRTtHGzfxL92gCSWNfLVf4v4qKIt0kfmN95vmopDKittuFaT5l+7V5Y1kVt1UWjZW+b71WG mbydq/eoII2jXzty/dq0q/LVfayrUbStGvl/xUAWHXzWVv7tSMvy1DFuVfmqRpGVf9lqsBrq 0nyr91akVV8uo1Xaqt/F/FUnmKse6gBvyt8v97+GpPLqHb8vmfxVbVla387d8yr92gCt5e3c u75aNqqu2my7mDSU613NHuZfmWgBX3LHt3bd1SeUq7V/u1BLukk3f3angdWj+b7y0AMaNo92 1vvVnyyMslXmbzW3L/DUbRrJu+X5loAbEzRrub5d1R3Uflqq1M7LI391VqSNPP8AvfeWgBsD N5e77rNTliVW3N96o5WVpNq/dWnKzSfLuoAd5flyeZuqu25ZNrfMrfxVJOzblXd8tR+Z5n7v dQAQR7ZJGX7tDqyxySfxU15Nv7tadasrfK33aAG2H7xWZv4f4qsfK37zdRcsqqsMa/dqNNys vy/LQBN95fvVG/zq0i02VtreX/E1OWRV3L/DQBXVWaRV/vVNtVvut8y1I+5VVfl3N92msvlr uX7y1AEa7V3Kyt81OiVfL3R/eX+9TlmZo9u35mpzKsarVgL95fmpjeWrbf7tObdHDu/h/hpr R/u12/eqAI/O+bbt3VIyq3y/3akRvLt9u395TW+7tVdzL95qAK8sf7yplWNZFVvur/6FUi+W qrJ/F/do8tfLX+JmoAhl+9ToFVZPLanNt27v4loiVVXazfM38VACrH8rf7VRxLHHMu77tOef bC21vmpqKvlr8vzNTLLXlqzf7NQTsvnKv8P8VOilZflb71CxrtZm/ipEDtrNHtX5aKYs6rHI q/w0UchQ9trN5lVXkb/XqvyrTpZJFt9u35mpsUe6NVagkmRvMj8yqu3zG8+jay/um+61TeWv +rWgByyKy0L+827m+7Ubo0cbVIu6NVagCR9snyrTVh8xtrN8q0Ntjj3L/FTVXy49y/eqwJG3 L8tNiVf9Xu+9Tmk2x+Y38VVYmkeT5l+9QBoIm1aj3Ku5aXd+5Zm/hqt5y7m3UAWol2rUcu2N m/h3UJPGy/7tRu3mbmb/AIDQBZj+Vf8AZqKdV+b+81EG1tu5vu1DOvmTNIrf7K0ASRQfu6c2 2BdzfKtLZy/u2jb7y1FLIskzM33VoAd5fy7l+61N2+T826nRP83lt/FUdwvnNt/hWoANrN83 96oXi/dtJt+Zfu05FZW27vlWpp1Zv91aAI/J/wBHWT+LbUNrHtZmZvlWrEE21tv3lp0u2RvL VdtWAIiyfvFanbo2+9u2rUf+r/3aJ22x7V/i+9UAR/61vMX/AHakWHb8zVD+8VVZfl+app/3 irGv8VAEMsm1ty/NtqaKTzP4qb5arQkax/d+81AEkW3zv92pmZWX+9Vdl8xf3f3lp3mfu/L2 /NQAeYu77u7bUi7mXdULrtVdtSPL+52r95qABPvNuX/dqNGZflp3mKv7tqc+1l3KvzUAEW3d tZfu06B18xVZabuWPbG33moZfm3L96gBJZV+0fd+WnSptZVX+KpEj+XbUbNujb/np91aZQz5 VkVVXcq/epzN8yqq02WNvLVV/h+9RE37v9595fu0iRsrN5m1W+Vam3blqPYrL833qjVWVW/8 doAm2ru/9Cop0UX7n73zNRQBXlVmXzN33amWRfJ3LTvu/u1qm67Z1g3bVagA8tpI2k3fN/DU 0DfKrVMqqrLt+aqs6+XJtX7rUATffb71Tbf3fzVXRWWpJZNsf+9QAKqttqb7y7du2q8Stt3V JPJtj3LQBHuVv3f91qmZFb921RxKzLu/iqWdv3PmL95asCKXbHIq7v3f8VQzxx/eWpEXzFZm +81QxfKzK38NAEcTK061YlVmmVf4Voigjjh3bfm3VHLJt/4DUAOVtu5dv/AqkVvLhqukjTLu /hq1EyzR7f4qAKrblk8xW27qN3l/K38VOul8yT5furTYl85vL/iWgCw7KsaybfmpybfL+X+K o4vmm2t91akVtu5WoAa+2Ndzfep0Um5d23+L7tQrukuP92ppd0bbWX71ADpVXa0jKu3/AGaj 3blZlX5qa0jSMqr91aJaAHbt0fmMvy0QeXJ8rLTXXcyr/CtNdvm3f3aAJrpvLXbHUcDLJ/D8 1OaTzNv/AI9UbLtVmX+GgCRo1/75o3bv4f8AdpryLNt2/wDAqkZfu7f4aACJF+Zvu02Lczf7 P8NDNvZV3f71O8r+CgB0UTM3zL8v96oX+aT7vy7vlpzySLHtXdVd5JN/3W20ASRW8jSbmqws n7z7v7v7tR28zSR7dvzVY2qqrHQAyWDd83/fNIsrK3+r+VaRmk8vbup6xtt+agCVfmVpP4ag 8xmkaRf9WtOWVlhaNf4mpzKvl+Wv/AqAI3k2/dbduqq8kkkm7b8tTPBt3L/e+7UjR+WqrQAb WkjXbTZPvVIsjIv+zTUXdQAJIrf8BoqFo2jZv9qigB0Um75mWqrK0m6T+992nXEjL+7X+KnM 21VWgB1vI21m/u01G8xtzfeqGX5W+X+KpD99aALSt8rVGq+cu2my/wAP+1UjLtX5asCSJWjV lb7tQuyqu2pp5Y/s6qv3mqNYvl/2qAHWsn8LU5mjVtv8NR7lVVbb81NdZG2rUAWlVWX5fu1X l8tWap4pVW0aPb+8qKKP5W3fxVYEqR/u938NVJW2ybf4f4qsRT7I5FqFY13MzfxUANl/dxrt /iotV+9J93dQrbo9tG7c21furQBDdM0a/wC1REzbVkb5WqZYfP8AlZvmWo7jasu3+FaAB2ZW VV+anNJtiZl+9uptuu1m/u0eWzTK+35d1QBNF8zbl+VqkZVaP5pNzVCu6Obd/DTpZNzfL92g ARvlb+9RKqrGv8TU35o2X5vlanOrSttVflWgAtV2sys26nSqq/M33ajVvLk+VaklbdQARf3W Wjy2jVmqP958zM1SMzSbY1+9/FQA2Bvm+7tqzLFtXzv7tRMrLGtO8z/R/L+agCNGZZN2371S LJ83+7TX+ZVVajb5V2/xfxUAHmN5jSfwtUm3d977rVD95l+X5asKzLH5a/eoAj+ZW8xfu1Zi G5VkamfKqqtR/N/qf9qgAaSSRmkX7q1Mrbm3fw03aySKu35dtNYSI3l/3qAGvuZmkX7q1LH8 y7v4f4qXbsXazVDKkke5Vb5WoAGZpJNy/dj+7U+7zFpEXy49tQs7L8v96rAGb5tu6nJJ/dqP dtX/AGqbBIyqy/3qgCRm8xm+b7tFN27V3UUAV33NI1O2/wAX8K03bTd3l/J/eoAEb73y1JE3 97+Gms3y01/m20ATQMrM27+KrES7flb7tRpH8q7aWT7tAEStum+78tWkXFQ7f3dO8z93t/iq wI926Tbt+WrMqeXD5jfMyrUSruXbt+ajc3lsslAFVJ5JJNy/dq40m2Nd38VNS22r/vUeXuVl b+GgCvLJub5V+WrSKsirtqGKL+Jl+9TkXy2ZW+7/AA7aAG3TbflWqqrctI237tXlh3LuZfma iL93I1ICvL+5j3M3zf7NNVdzbl+ZWqwsPmyNuX5mpyQfZmZo/wCGmBDLuj+Vf7tTRbpI1jb7 y0RLu3SN96nfdbzFqAI5/lVV/iamou1trL8392pEWSWbc1E8Ui/M27dQAXC7Y1og+6y/xU3a 0n/AVprqy/vKsCR12wtuX5qjTcu1W/iqRtzf7tQ/M0lAEj7l27vu06JfLbc38VO2tIy7vlVa c/zfdqAGyttX733ajRm/1jfdqPczNtpyxySNtX+KgCTdt+b+Gmq7M25l+VqbtbcsLL/FUzqs a0AN2szKu3aq/wAVNZmbdIrfL/dpz+YsbRrRErbfm+7VgOWRWXdT42j2tNMzLJ/yzqDy2Vtv 96nTx7mX/ZqAJ2lWSNWVfu1A26Vmk3fd+7TUjbdt/vVNsZfl2/doAr+Z81OdmZtyt92ieNt2 7+9Tol2/7VAEit5kdV22tI3+zUyLtVm3bd38NRqtADdrSfdprx7dzLUjfJ826mp80fy0AEUu 5vL/AIqKjVdsjN/FRQAituXdTEj3SbqklXa1ORW21ZY1futSwR7tzUfw1Jt2xqv8VADom2/e +7QrbpKR91ES7V20CJ0X5f8AZqDd+8+VflqX5vLZai2tH8tAEsrL8u2o2Zt3y07a21aPKkVf m+9QBaX5o91VZfMZpNtTQM0cbR/3vu0RRt827/gVABEvmKrVBdMzSbV+6tSqrR7tv8X3aFgX btb71ABA3mx/7VQz7vM+X+GpPL8lmZf4qmji/dtu/ioAbEyyKrfxLUM8jMzKtSNG0bfL/FUs UCrH81AEUSq8K/3qjuP+ecdSS/uG+X+KpIk2rub7zfdoAjtm2fK1E7NItR3W6Jlbdt3VaWL9 2rUAV4F3fu93zVHc7VZlVqdeK0TKyt8zVCsMkki0ATQbtvl0rMq/d+9TLmNolX5/vVGsMjbd v3aBk8W5m+ZvmpZdqttX7tSJFt+Zm+bbVafd8q0CHL/ealjlaCTcvzLTYo/3bN/epPKZodtA D2fzZPO/ianK25fm/hqu8bIqt/tVMkTbaAGxN+8Zv4mp0snzfLR5fl/M1M27W27qAFRfM+b/ AJaU/c38P8NI0nlruoVfl3f3qBjdrSNu/ioll3Mq/wB2n7fl3btq1VRVWT5moEP3eY25af5n y7aVI1j+b+GkdVjVf9qgZH80n8VSrKu3b/dqNW8ptzfdallVfloAa22ZqRPlkVf4akij8td3 8NMlXbJtoAdu3SNt+7RRBGyqzUUiCWLa3zN92olbczNUrIqx7d3zNUWymUKq+Y3zfw1JEvmb pGpGXau3+Jlp0TN92gAVlZt38K1Iu1vmoaJVbbTZU2fxfe+WqEMZtzbl/h+7U8SLKqyULBtG 2m/6ptu7arUARyMzSbl+6tW1ljlVWpViXaq1Xb5Jdv8AC33qAHXLbplaNdqrU8EivHu/iX71 OWNVXbVaeNVuNqs25loArTu0km5fur92rdt88ayf99VWSDa21qnaSOKP5m2tJQUVrlpZZv3a /KtWrZmZdrfw/eoVW8tfL/76pty0cLKzN+82/NUiFk+dWbd8tOs5/MVlk+9H/wCg0+OJXj/2 WqlfQLHIu1mZtvzVQhGbz5mb+GpraVgrK38NWbaOOOHcv3WqpfbfMVV+9/Ft/u1IyNkknVpN v+7UtjOscbRyN935lq3A0bQrt+6y1S1BI0ZVVf3jLVCIpX8ySSRvu/dWptOuVVWjkb7vzVHA jMv3flbbTb6CNGWONf3n3mqSh08/mszfw/dWnWL+X+7b/eotoNzLJuXy6LyOONdq/NI392gQ 5JGnk3fw/wANO8uPbtb71SWyxtArLUd40ca7W+aRqADbvX5furUkW3btpYNrQLt+7UF1KsP/ AF0b7tAFe8k8yTb/AAq22rFnKrLtb+GnRQRyxLJ/F/FVeUR2y/N8zN92gAupfMk2r91aWDbL 9771RRRbm+X7tTbY4P3jfe/hoGRXUm6Tav3VqW2bcu3+KhIVZt38LU5ljjj3L97d8tAEd5Ou 7b/d+7SRKtxtVvvUkscbfvNzf7tMRlj+b/vmgCy7LLJt/hWmqu6RlpsDbWXb92ppWWNlb+9Q Iq3CtNJtX/Vx1LArM23+KliVW3baJdsK+Y3/AAGgZHdS/wDLNfmVaWKPzG3fxURbVqTd5a7v urQAfxbf7tFM8z7vy/eooAk+87E06HmiigQxR5kshaiMsSCW6UUVQixAfMGWqvK7SM26iigC 5bHzIlLVC4yxfuKKKAJ7aRpYlLdqikHmFi1FFAE1v88Sk9qhlGZWNFFBRKoyAfSs6djJLIW/ hGBRRQSWNOYrbvu+fZ0zVTc0s8rM3VmooqSi9p0rYkRvmEYytVIXaSR5GPzGiiiQFrTpGAnQ /MEORUVn+9aWVvvGiigBbDh5kHSM5WmW5+0M0kn3qKKokfaf6907A5pyfvJJHbqaKKAK9kxW WSEfdzmktZGlZ5G+8GxRRQBLYOYriSFfu4zUO8yCSVvvUUVJRbsmIOztVK6fzbklh0GKKKBE +nyN5jxfwmoZv3twd3aiigcSSHicp2NMmOZj7UUUAWLfgAetJIMzBV+UCiij7IiNVGSPVqrX JxcvF/CnSiigY6zJW6EZ+YGpLt/MlY42+V93FFFAiWH5cY71XvpGadEPQUUVQhYjwop00jNK qHpRRUlD7f5gymiiipYH/9=9 --UJV838Z622107EA8F0mB7xt6-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 11:35:31 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29743 for ; Thu, 31 Oct 2002 11:35:31 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VGPDv10293; Thu, 31 Oct 2002 11:25:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VGLov10120 for ; Thu, 31 Oct 2002 11:21:50 -0500 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28489 for ; Thu, 31 Oct 2002 11:19:22 -0500 (EST) Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id AAA18257 for ; Fri, 1 Nov 2002 00:21:43 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500b.comp.nus.edu.sg via csmap id 29923; Fri, 01 Nov 2002 00:09:45 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id AAA29609 for ; Fri, 1 Nov 2002 00:21:43 +0800 (GMT-8) Date: Fri, 1 Nov 2002 00:21:43 +0800 (GMT-8) From: Sourabh Sharma cc: manet@ietf.org Subject: Re: [manet] Testing DSR over ethernet In-Reply-To: <20021031014305.A4992@che.onthejob.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Thu, 31 Oct 2002, David Young wrote: > If nodes 1, 3, and 4 are configured as hosts on the same IP subnet, then > node 3 will send ICMP Redirects to 1 and 4 whenever one tries to contact > the other through 3. The reason is that as far as node 3 is concerned, > 1 and 4 can reach each other directly, and so it tells them so. > > In a lot of IP implementations, such as NetBSD's and Linux's, it is > default behavior for a router to honor ICMP Redirects. In Linux and in > NetBSD, there are sysctl's which will turn off ICMP Redirects. (In Linux, > a zillion sysctl's affect ICMP Redirects, and you may have to turn off > more than one.) Instead of all this trouble why doesn't Pradeep configue the nodes to be in different subnets.I've said this before and emphasize again: Apart from the automatic update of routing tables- and this finding routes to new nodes, the test of an ad-hoc routing protocol is to find routes when the nodes have totally different/unrelated Ipaddreses. Pradeep, I strongly , suggest you try this, if what Dave says is the actual problem, viz ICMP redirects. -Sourabh > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > hi > > > > My apologies if you get multiple copies of this email. My friend, who is > > not a member of the group, tried to send the same email. Since he was not > > successful, I am sending it now. Sorry about that!! > > > > we are trying to run DSR (Alex Song's implementation) over an ethernet > > LAN. we are trying to set up a network (with eight nodes) as follows: > > node 1 is within the transmission range of nodes 2 and 3 but not other > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > (route request) and only nodes 2 and 3 have to send RREPs (route > > replies) and not the other nodes (including node 4 though they are all > > in the same broadcast medium - the wired ethernet). this is just to > > setup a multihop network. > > > > at node 4, we tried to block broadcast packets from node 1 using > > iptables so that node 4 would not reply to RREQs from node 1. > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > > were not able to ping node 4 from node 1). then we up- ed node 3 (which > > is in the "transmission range" of both node 1 and node 4. we were able > > to ping node 3 from both node 1 and node 4). but we still we were > > unable to ping node 4 from node 1 (we were expecting node 3, being > > within the "transmission range" of node 4 to aid node 1 in reaching > > node 4. but this didnt happen). > > > > could anyone help us in figuring out what the problem is ? Any suggestions > > are most welcome (we have setting up VLANs in mind instead of using > > iptables, but would like to explore other options before disturbing the > > current network setup) > > > > we have tried to be as clear as possible in stating our problem. > > > > thanks in advance! > > regards > > girish & pradeep. > > > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > -- > David Young OJC Technologies > dyoung@ojctech.com Engineering from the Right Brain > Urbana, IL * (217) 278-3933 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 11:38:00 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29895 for ; Thu, 31 Oct 2002 11:38:00 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VGdut11537 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 11:39:56 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VGduv11534 for ; Thu, 31 Oct 2002 11:39:56 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29826 for ; Thu, 31 Oct 2002 11:37:28 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VGPDv10293; Thu, 31 Oct 2002 11:25:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VGLov10120 for ; Thu, 31 Oct 2002 11:21:50 -0500 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28489 for ; Thu, 31 Oct 2002 11:19:22 -0500 (EST) Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id AAA18257 for ; Fri, 1 Nov 2002 00:21:43 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500b.comp.nus.edu.sg via csmap id 29923; Fri, 01 Nov 2002 00:09:45 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id AAA29609 for ; Fri, 1 Nov 2002 00:21:43 +0800 (GMT-8) Date: Fri, 1 Nov 2002 00:21:43 +0800 (GMT-8) From: Sourabh Sharma cc: manet@ietf.org Subject: Re: [manet] Testing DSR over ethernet In-Reply-To: <20021031014305.A4992@che.onthejob.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Thu, 31 Oct 2002, David Young wrote: > If nodes 1, 3, and 4 are configured as hosts on the same IP subnet, then > node 3 will send ICMP Redirects to 1 and 4 whenever one tries to contact > the other through 3. The reason is that as far as node 3 is concerned, > 1 and 4 can reach each other directly, and so it tells them so. > > In a lot of IP implementations, such as NetBSD's and Linux's, it is > default behavior for a router to honor ICMP Redirects. In Linux and in > NetBSD, there are sysctl's which will turn off ICMP Redirects. (In Linux, > a zillion sysctl's affect ICMP Redirects, and you may have to turn off > more than one.) Instead of all this trouble why doesn't Pradeep configue the nodes to be in different subnets.I've said this before and emphasize again: Apart from the automatic update of routing tables- and this finding routes to new nodes, the test of an ad-hoc routing protocol is to find routes when the nodes have totally different/unrelated Ipaddreses. Pradeep, I strongly , suggest you try this, if what Dave says is the actual problem, viz ICMP redirects. -Sourabh > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > hi > > > > My apologies if you get multiple copies of this email. My friend, who is > > not a member of the group, tried to send the same email. Since he was not > > successful, I am sending it now. Sorry about that!! > > > > we are trying to run DSR (Alex Song's implementation) over an ethernet > > LAN. we are trying to set up a network (with eight nodes) as follows: > > node 1 is within the transmission range of nodes 2 and 3 but not other > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > (route request) and only nodes 2 and 3 have to send RREPs (route > > replies) and not the other nodes (including node 4 though they are all > > in the same broadcast medium - the wired ethernet). this is just to > > setup a multihop network. > > > > at node 4, we tried to block broadcast packets from node 1 using > > iptables so that node 4 would not reply to RREQs from node 1. > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > > were not able to ping node 4 from node 1). then we up- ed node 3 (which > > is in the "transmission range" of both node 1 and node 4. we were able > > to ping node 3 from both node 1 and node 4). but we still we were > > unable to ping node 4 from node 1 (we were expecting node 3, being > > within the "transmission range" of node 4 to aid node 1 in reaching > > node 4. but this didnt happen). > > > > could anyone help us in figuring out what the problem is ? Any suggestions > > are most welcome (we have setting up VLANs in mind instead of using > > iptables, but would like to explore other options before disturbing the > > current network setup) > > > > we have tried to be as clear as possible in stating our problem. > > > > thanks in advance! > > regards > > girish & pradeep. > > > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > -- > David Young OJC Technologies > dyoung@ojctech.com Engineering from the Right Brain > Urbana, IL * (217) 278-3933 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 12:05:46 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01506 for ; Thu, 31 Oct 2002 12:05:46 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VGxiv12312; Thu, 31 Oct 2002 11:59:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VGuKv12186 for ; Thu, 31 Oct 2002 11:56:20 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00800 for ; Thu, 31 Oct 2002 11:53:53 -0500 (EST) Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g9VGuFj442031 for ; Thu, 31 Oct 2002 11:56:15 -0500 (EST) Received: from TNT (h80ad3776.dhcp.vt.edu [128.173.55.118]) by vivi.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1-GA) with SMTP id AMK56075; Thu, 31 Oct 2002 11:56:13 -0500 (EST) Message-ID: <002f01c280fe$73815720$7637ad80@workgroup> From: "Tao Lin" To: References: Subject: Re: [manet] Testing DSR over ethernet Date: Thu, 31 Oct 2002 11:56:26 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Turning off ICMP Redirects is not difficult. For example, AODV Linux distribution at http://www.docs.uu.se/~henrikl/aodv/. Bascially, just echo 0 to /proc/sys/net/ipv4/conf/wlan0/send_redirects, /proc/sys/net/ipv4/conf/wlan0/accept_redirects (here wlan0 is the NIC used for ad hoc routing), and similar files in /proc/sys/net/ipv4/conf/all/ directory. Hope this helps. ----- Original Message ----- From: "Sourabh Sharma" Cc: Sent: Thursday, October 31, 2002 11:21 AM Subject: Re: [manet] Testing DSR over ethernet > On Thu, 31 Oct 2002, David Young wrote: > > If nodes 1, 3, and 4 are configured as hosts on the same IP subnet, then > > node 3 will send ICMP Redirects to 1 and 4 whenever one tries to contact > > the other through 3. The reason is that as far as node 3 is concerned, > > 1 and 4 can reach each other directly, and so it tells them so. > > > > In a lot of IP implementations, such as NetBSD's and Linux's, it is > > default behavior for a router to honor ICMP Redirects. In Linux and in > > NetBSD, there are sysctl's which will turn off ICMP Redirects. (In Linux, > > a zillion sysctl's affect ICMP Redirects, and you may have to turn off > > more than one.) > > Instead of all this trouble why doesn't Pradeep configue > the nodes to be in different subnets.I've said this before > and emphasize again: > Apart from the automatic update of routing tables- and this finding > routes to new nodes, the > test of an ad-hoc routing protocol is to find routes when > the nodes have totally different/unrelated Ipaddreses. > > Pradeep, I strongly , suggest you try this, if what Dave says > is the actual problem, viz ICMP redirects. > > -Sourabh > > > > > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > > hi > > > > > > My apologies if you get multiple copies of this email. My friend, who is > > > not a member of the group, tried to send the same email. Since he was not > > > successful, I am sending it now. Sorry about that!! > > > > > > we are trying to run DSR (Alex Song's implementation) over an ethernet > > > LAN. we are trying to set up a network (with eight nodes) as follows: > > > node 1 is within the transmission range of nodes 2 and 3 but not other > > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > > (route request) and only nodes 2 and 3 have to send RREPs (route > > > replies) and not the other nodes (including node 4 though they are all > > > in the same broadcast medium - the wired ethernet). this is just to > > > setup a multihop network. > > > > > > at node 4, we tried to block broadcast packets from node 1 using > > > iptables so that node 4 would not reply to RREQs from node 1. > > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > > > were not able to ping node 4 from node 1). then we up- ed node 3 (which > > > is in the "transmission range" of both node 1 and node 4. we were able > > > to ping node 3 from both node 1 and node 4). but we still we were > > > unable to ping node 4 from node 1 (we were expecting node 3, being > > > within the "transmission range" of node 4 to aid node 1 in reaching > > > node 4. but this didnt happen). > > > > > > could anyone help us in figuring out what the problem is ? Any suggestions > > > are most welcome (we have setting up VLANs in mind instead of using > > > iptables, but would like to explore other options before disturbing the > > > current network setup) > > > > > > we have tried to be as clear as possible in stating our problem. > > > > > > thanks in advance! > > > regards > > > girish & pradeep. > > > > > > > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > -- > > David Young OJC Technologies > > dyoung@ojctech.com Engineering from the Right Brain > > Urbana, IL * (217) 278-3933 > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > -------------------------------------------------- > There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 12:11:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01770 for ; Thu, 31 Oct 2002 12:11:27 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VHDNL13931 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 12:13:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHDNv13928 for ; Thu, 31 Oct 2002 12:13:23 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01752 for ; Thu, 31 Oct 2002 12:10:56 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VGxiv12312; Thu, 31 Oct 2002 11:59:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VGuKv12186 for ; Thu, 31 Oct 2002 11:56:20 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00800 for ; Thu, 31 Oct 2002 11:53:53 -0500 (EST) Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g9VGuFj442031 for ; Thu, 31 Oct 2002 11:56:15 -0500 (EST) Received: from TNT (h80ad3776.dhcp.vt.edu [128.173.55.118]) by vivi.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1-GA) with SMTP id AMK56075; Thu, 31 Oct 2002 11:56:13 -0500 (EST) Message-ID: <002f01c280fe$73815720$7637ad80@workgroup> From: "Tao Lin" To: References: Subject: Re: [manet] Testing DSR over ethernet Date: Thu, 31 Oct 2002 11:56:26 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Turning off ICMP Redirects is not difficult. For example, AODV Linux distribution at http://www.docs.uu.se/~henrikl/aodv/. Bascially, just echo 0 to /proc/sys/net/ipv4/conf/wlan0/send_redirects, /proc/sys/net/ipv4/conf/wlan0/accept_redirects (here wlan0 is the NIC used for ad hoc routing), and similar files in /proc/sys/net/ipv4/conf/all/ directory. Hope this helps. ----- Original Message ----- From: "Sourabh Sharma" Cc: Sent: Thursday, October 31, 2002 11:21 AM Subject: Re: [manet] Testing DSR over ethernet > On Thu, 31 Oct 2002, David Young wrote: > > If nodes 1, 3, and 4 are configured as hosts on the same IP subnet, then > > node 3 will send ICMP Redirects to 1 and 4 whenever one tries to contact > > the other through 3. The reason is that as far as node 3 is concerned, > > 1 and 4 can reach each other directly, and so it tells them so. > > > > In a lot of IP implementations, such as NetBSD's and Linux's, it is > > default behavior for a router to honor ICMP Redirects. In Linux and in > > NetBSD, there are sysctl's which will turn off ICMP Redirects. (In Linux, > > a zillion sysctl's affect ICMP Redirects, and you may have to turn off > > more than one.) > > Instead of all this trouble why doesn't Pradeep configue > the nodes to be in different subnets.I've said this before > and emphasize again: > Apart from the automatic update of routing tables- and this finding > routes to new nodes, the > test of an ad-hoc routing protocol is to find routes when > the nodes have totally different/unrelated Ipaddreses. > > Pradeep, I strongly , suggest you try this, if what Dave says > is the actual problem, viz ICMP redirects. > > -Sourabh > > > > > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > > hi > > > > > > My apologies if you get multiple copies of this email. My friend, who is > > > not a member of the group, tried to send the same email. Since he was not > > > successful, I am sending it now. Sorry about that!! > > > > > > we are trying to run DSR (Alex Song's implementation) over an ethernet > > > LAN. we are trying to set up a network (with eight nodes) as follows: > > > node 1 is within the transmission range of nodes 2 and 3 but not other > > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > > (route request) and only nodes 2 and 3 have to send RREPs (route > > > replies) and not the other nodes (including node 4 though they are all > > > in the same broadcast medium - the wired ethernet). this is just to > > > setup a multihop network. > > > > > > at node 4, we tried to block broadcast packets from node 1 using > > > iptables so that node 4 would not reply to RREQs from node 1. > > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > > > were not able to ping node 4 from node 1). then we up- ed node 3 (which > > > is in the "transmission range" of both node 1 and node 4. we were able > > > to ping node 3 from both node 1 and node 4). but we still we were > > > unable to ping node 4 from node 1 (we were expecting node 3, being > > > within the "transmission range" of node 4 to aid node 1 in reaching > > > node 4. but this didnt happen). > > > > > > could anyone help us in figuring out what the problem is ? Any suggestions > > > are most welcome (we have setting up VLANs in mind instead of using > > > iptables, but would like to explore other options before disturbing the > > > current network setup) > > > > > > we have tried to be as clear as possible in stating our problem. > > > > > > thanks in advance! > > > regards > > > girish & pradeep. > > > > > > > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > -- > > David Young OJC Technologies > > dyoung@ojctech.com Engineering from the Right Brain > > Urbana, IL * (217) 278-3933 > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > -------------------------------------------------- > There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > _______________________________________________ > 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-admin@ietf.org Thu Oct 31 12:27:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02637 for ; Thu, 31 Oct 2002 12:27:07 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHL0v14338; Thu, 31 Oct 2002 12:21:00 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHHav14175 for ; Thu, 31 Oct 2002 12:17:36 -0500 Received: from cheech.nmsu.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01957 for ; Thu, 31 Oct 2002 12:15:07 -0500 (EST) From: jomullen@nmsu.edu Received: (from nobody@localhost) by cheech.nmsu.edu (8.11.6/8.11.6) id g9VHU9K20268; Thu, 31 Oct 2002 10:30:09 -0700 Received: from 155.148.36.131 ( [155.148.36.131]) as user jomullen@imap.nmsu.edu by webmail.nmsu.edu with HTTP; Thu, 31 Oct 2002 10:30:09 -0700 Message-ID: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> Date: Thu, 31 Oct 2002 10:30:09 -0700 To: Sourabh Sharma Cc: manet@ietf.org Subject: Re: [manet] Testing DSR over ethernet References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.0 X-Originating-IP: 155.148.36.131 Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Hi Sourabh, The issue of IP addresses is not so simple. I believe Pradeep is trying to emulate a MANET situation on a Eithernet. If so, he wants Node 3 to be reachable by Node 1 and Node 4. To try to do this with subnet addresses, he would have to have Node 3 in two diferent subnets; one for Node 1 and one for Node 4. In addition, to simulate movement, he would have to reassign subnets to different nodes as the simulation progresses. That would mean changing IP addresses as he goes. If Node 3 is reachable by Nodes 1 and 4, then it must be in a supernet. If this changes, not only will Node 3 get a new IP, but it may have to change levels within the hierarchy. Sounds pretty complicated to me. Also, there are schemes by which a MANET assigns internal IPs to or augments existing IP addresses of its nodes, thereby permitting aggregation of routes by IP subnets. In effect, part of the routing update problem is replaced by the dynamic IP update and forwarding address problems. For smallish MANETS, it offers no clear advantage, but for very large ones, it might be beneficial. There doesn't seem to be a consensus on if and when this is a good strategy at this time. Point is, the dealing with unrelated IP addresses can be done in a number of ways within a MANET and, in some schemes, the routing algorithm might actually "see" related IP addresses. John Mullen Quoting Sourabh Sharma : > > > Instead of all this trouble why doesn't Pradeep configue > the nodes to be in different subnets.I've said this before > and emphasize again: > Apart from the automatic update of routing tables- and this finding > routes to new nodes, the > test of an ad-hoc routing protocol is to find routes when > the nodes have totally different/unrelated Ipaddreses. > > Pradeep, I strongly , suggest you try this, if what Dave says > is the actual problem, viz ICMP redirects. > > -Sourabh > > > > > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > > hi > > > > > > My apologies if you get multiple copies of this email. My friend, who > is > > > not a member of the group, tried to send the same email. Since he was > not > > > successful, I am sending it now. Sorry about that!! > > > > > > we are trying to run DSR (Alex Song's implementation) over an ethernet > > > LAN. we are trying to set up a network (with eight nodes) as follows: > > > node 1 is within the transmission range of nodes 2 and 3 but not other > > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > > (route request) and only nodes 2 and 3 have to send RREPs (route > > > replies) and not the other nodes (including node 4 though they are all > > > in the same broadcast medium - the wired ethernet). this is just to > > > setup a multihop network. > > > > > > at node 4, we tried to block broadcast packets from node 1 using > > > iptables so that node 4 would not reply to RREQs from node 1. > > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > > > were not able to ping node 4 from node 1). then we up- ed node 3 > (which > > > is in the "transmission range" of both node 1 and node 4. we were able > > > to ping node 3 from both node 1 and node 4). but we still we were > > > unable to ping node 4 from node 1 (we were expecting node 3, being > > > within the "transmission range" of node 4 to aid node 1 in reaching > > > node 4. but this didnt happen). > > > > > > could anyone help us in figuring out what the problem is ? Any > suggestions > > > are most welcome (we have setting up VLANs in mind instead of using > > > iptables, but would like to explore other options before disturbing the > > > current network setup) > > > > > > we have tried to be as clear as possible in stating our problem. > > > > > > thanks in advance! > > > regards > > > girish & pradeep. > > > > > > > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > -- > > David Young OJC Technologies > > dyoung@ojctech.com Engineering from the Right Brain > > Urbana, IL * (217) 278-3933 > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > -------------------------------------------------- > There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 12:31:59 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02937 for ; Thu, 31 Oct 2002 12:31:59 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VHXuU15119 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 12:33:56 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHXuv15116 for ; Thu, 31 Oct 2002 12:33:56 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02904 for ; Thu, 31 Oct 2002 12:31:28 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHL0v14338; Thu, 31 Oct 2002 12:21:00 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHHav14175 for ; Thu, 31 Oct 2002 12:17:36 -0500 Received: from cheech.nmsu.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01957 for ; Thu, 31 Oct 2002 12:15:07 -0500 (EST) From: jomullen@nmsu.edu Received: (from nobody@localhost) by cheech.nmsu.edu (8.11.6/8.11.6) id g9VHU9K20268; Thu, 31 Oct 2002 10:30:09 -0700 Received: from 155.148.36.131 ( [155.148.36.131]) as user jomullen@imap.nmsu.edu by webmail.nmsu.edu with HTTP; Thu, 31 Oct 2002 10:30:09 -0700 Message-ID: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> Date: Thu, 31 Oct 2002 10:30:09 -0700 To: Sourabh Sharma Cc: manet@ietf.org Subject: Re: [manet] Testing DSR over ethernet References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.0 X-Originating-IP: 155.148.36.131 Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi Sourabh, The issue of IP addresses is not so simple. I believe Pradeep is trying to emulate a MANET situation on a Eithernet. If so, he wants Node 3 to be reachable by Node 1 and Node 4. To try to do this with subnet addresses, he would have to have Node 3 in two diferent subnets; one for Node 1 and one for Node 4. In addition, to simulate movement, he would have to reassign subnets to different nodes as the simulation progresses. That would mean changing IP addresses as he goes. If Node 3 is reachable by Nodes 1 and 4, then it must be in a supernet. If this changes, not only will Node 3 get a new IP, but it may have to change levels within the hierarchy. Sounds pretty complicated to me. Also, there are schemes by which a MANET assigns internal IPs to or augments existing IP addresses of its nodes, thereby permitting aggregation of routes by IP subnets. In effect, part of the routing update problem is replaced by the dynamic IP update and forwarding address problems. For smallish MANETS, it offers no clear advantage, but for very large ones, it might be beneficial. There doesn't seem to be a consensus on if and when this is a good strategy at this time. Point is, the dealing with unrelated IP addresses can be done in a number of ways within a MANET and, in some schemes, the routing algorithm might actually "see" related IP addresses. John Mullen Quoting Sourabh Sharma : > > > Instead of all this trouble why doesn't Pradeep configue > the nodes to be in different subnets.I've said this before > and emphasize again: > Apart from the automatic update of routing tables- and this finding > routes to new nodes, the > test of an ad-hoc routing protocol is to find routes when > the nodes have totally different/unrelated Ipaddreses. > > Pradeep, I strongly , suggest you try this, if what Dave says > is the actual problem, viz ICMP redirects. > > -Sourabh > > > > > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > > hi > > > > > > My apologies if you get multiple copies of this email. My friend, who > is > > > not a member of the group, tried to send the same email. Since he was > not > > > successful, I am sending it now. Sorry about that!! > > > > > > we are trying to run DSR (Alex Song's implementation) over an ethernet > > > LAN. we are trying to set up a network (with eight nodes) as follows: > > > node 1 is within the transmission range of nodes 2 and 3 but not other > > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > > (route request) and only nodes 2 and 3 have to send RREPs (route > > > replies) and not the other nodes (including node 4 though they are all > > > in the same broadcast medium - the wired ethernet). this is just to > > > setup a multihop network. > > > > > > at node 4, we tried to block broadcast packets from node 1 using > > > iptables so that node 4 would not reply to RREQs from node 1. > > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > > > were not able to ping node 4 from node 1). then we up- ed node 3 > (which > > > is in the "transmission range" of both node 1 and node 4. we were able > > > to ping node 3 from both node 1 and node 4). but we still we were > > > unable to ping node 4 from node 1 (we were expecting node 3, being > > > within the "transmission range" of node 4 to aid node 1 in reaching > > > node 4. but this didnt happen). > > > > > > could anyone help us in figuring out what the problem is ? Any > suggestions > > > are most welcome (we have setting up VLANs in mind instead of using > > > iptables, but would like to explore other options before disturbing the > > > current network setup) > > > > > > we have tried to be as clear as possible in stating our problem. > > > > > > thanks in advance! > > > regards > > > girish & pradeep. > > > > > > > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > -- > > David Young OJC Technologies > > dyoung@ojctech.com Engineering from the Right Brain > > Urbana, IL * (217) 278-3933 > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > -------------------------------------------------- > There is an answer to everything in this world. > The only question which remains to be answered > IS whether we know the answers or not. > > > _______________________________________________ > 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-admin@ietf.org Thu Oct 31 12:55:58 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04595 for ; Thu, 31 Oct 2002 12:55:58 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHo5v16735; Thu, 31 Oct 2002 12:50:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHj8v16526 for ; Thu, 31 Oct 2002 12:45:08 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03751 for ; Thu, 31 Oct 2002 12:42:40 -0500 (EST) Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g9VHj3j459612 for ; Thu, 31 Oct 2002 12:45:03 -0500 (EST) Received: from tlin (E112210.vtacs.com [208.138.112.210]) by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1-GA) with ESMTP id ARJ62899 (AUTH talin); Thu, 31 Oct 2002 12:45:01 -0500 (EST) Message-ID: <003001c28105$08ffda00$755a640a@vtacs.com> From: "Tao Lin" To: References: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> Subject: Re: [manet] Testing DSR over ethernet Date: Thu, 31 Oct 2002 12:43:34 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit For the topology emulation of wireless ad hoc networks in a wired testbed, we developed such a tool in our lab. The link for this free software at http://io.irean.vt.edu/~tlin/ (196 downloads till now) and a paper for it can also be found at this web page. Use this tool, users only need to setup a wired testbed. No need to modify mobile nodes. Mobile nodes can be configured using IP addresses in one subnet or different subnets if they may talk to each other directly. Thanks, Tao ----- Original Message ----- From: To: "Sourabh Sharma" Cc: Sent: Thursday, October 31, 2002 12:30 PM Subject: Re: [manet] Testing DSR over ethernet > Hi Sourabh, > > The issue of IP addresses is not so simple. > > I believe Pradeep is trying to emulate a MANET situation on a Eithernet. If > so, he wants Node 3 to be reachable by Node 1 and Node 4. To try to do this > with subnet addresses, he would have to have Node 3 in two diferent subnets; > one for Node 1 and one for Node 4. In addition, to simulate movement, he would > have to reassign subnets to different nodes as the simulation progresses. That > would mean changing IP addresses as he goes. If Node 3 is reachable by Nodes 1 > and 4, then it must be in a supernet. If this changes, not only will Node 3 > get a new IP, but it may have to change levels within the hierarchy. > > Sounds pretty complicated to me. > > Also, there are schemes by which a MANET assigns internal IPs to or augments > existing IP addresses of its nodes, thereby permitting aggregation of routes by > IP subnets. In effect, part of the routing update problem is replaced by the > dynamic IP update and forwarding address problems. For smallish MANETS, it > offers no clear advantage, but for very large ones, it might be beneficial. > There doesn't seem to be a consensus on if and when this is a good strategy at > this time. > > Point is, the dealing with unrelated IP addresses can be done in a number of > ways within a MANET and, in some schemes, the routing algorithm might > actually "see" related IP addresses. > > John Mullen > > Quoting Sourabh Sharma : > > > > > > > Instead of all this trouble why doesn't Pradeep configue > > the nodes to be in different subnets.I've said this before > > and emphasize again: > > Apart from the automatic update of routing tables- and this finding > > routes to new nodes, the > > test of an ad-hoc routing protocol is to find routes when > > the nodes have totally different/unrelated Ipaddreses. > > > > Pradeep, I strongly , suggest you try this, if what Dave says > > is the actual problem, viz ICMP redirects. > > > > -Sourabh > > > > > > > > > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > > > hi > > > > > > > > My apologies if you get multiple copies of this email. My friend, who > > is > > > > not a member of the group, tried to send the same email. Since he was > > not > > > > successful, I am sending it now. Sorry about that!! > > > > > > > > we are trying to run DSR (Alex Song's implementation) over an ethernet > > > > LAN. we are trying to set up a network (with eight nodes) as follows: > > > > node 1 is within the transmission range of nodes 2 and 3 but not other > > > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > > > (route request) and only nodes 2 and 3 have to send RREPs (route > > > > replies) and not the other nodes (including node 4 though they are all > > > > in the same broadcast medium - the wired ethernet). this is just to > > > > setup a multihop network. > > > > > > > > at node 4, we tried to block broadcast packets from node 1 using > > > > iptables so that node 4 would not reply to RREQs from node 1. > > > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > > > > were not able to ping node 4 from node 1). then we up- ed node 3 > > (which > > > > is in the "transmission range" of both node 1 and node 4. we were able > > > > to ping node 3 from both node 1 and node 4). but we still we were > > > > unable to ping node 4 from node 1 (we were expecting node 3, being > > > > within the "transmission range" of node 4 to aid node 1 in reaching > > > > node 4. but this didnt happen). > > > > > > > > could anyone help us in figuring out what the problem is ? Any > > suggestions > > > > are most welcome (we have setting up VLANs in mind instead of using > > > > iptables, but would like to explore other options before disturbing the > > > > current network setup) > > > > > > > > we have tried to be as clear as possible in stating our problem. > > > > > > > > thanks in advance! > > > > regards > > > > girish & pradeep. > > > > > > > > > > > > > > > > _______________________________________________ > > > > manet mailing list > > > > manet@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > -- > > > David Young OJC Technologies > > > dyoung@ojctech.com Engineering from the Right Brain > > > Urbana, IL * (217) 278-3933 > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > -------------------------------------------------- > > There is an answer to everything in this world. > > The only question which remains to be answered > > IS whether we know the answers or not. > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 12:56:50 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04641 for ; Thu, 31 Oct 2002 12:56:50 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHlUv16629; Thu, 31 Oct 2002 12:47:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHifv16509 for ; Thu, 31 Oct 2002 12:44:41 -0500 Received: from c000.snv.cp.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03733 for ; Thu, 31 Oct 2002 12:42:13 -0500 (EST) Received: (cpmta 23541 invoked from network); 31 Oct 2002 09:44:32 -0800 Received: from 128.174.253.126 (HELO cs.uiuc.edu) by smtp.carter.net (209.228.32.65) with SMTP; 31 Oct 2002 09:44:32 -0800 X-Sent: 31 Oct 2002 17:44:32 GMT Message-ID: <3DC16BFF.4@cs.uiuc.edu> Date: Thu, 31 Oct 2002 11:44:31 -0600 From: Casey Carter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020606 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Subject: Re: [manet] A very good tool References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit ccarter wrote: >Content-Type: application/octet-stream; > name=gen_background2[1].jpg >Content-Transfer-Encoding: base64 >Content-ID: > > > Just so everyone knows, I did not send this. The message headers say it came from mx05.cluster1.charter.net, so I figure charter.net is hosting an open-relay mail server that allowed someone to forge my address as the source. If I was going to send a virus to the list, I'm sure I could at least do a better job of it. ;) -- Casey Carter Casey@Carter.net ccarter@uiuc.edu AIM: cartec69 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 12:58:47 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04811 for ; Thu, 31 Oct 2002 12:58:47 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VI0iO17470 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 13:00:44 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VI0iv17467 for ; Thu, 31 Oct 2002 13:00:44 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04775 for ; Thu, 31 Oct 2002 12:58:16 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHo5v16735; Thu, 31 Oct 2002 12:50:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHj8v16526 for ; Thu, 31 Oct 2002 12:45:08 -0500 Received: from lennier.cc.vt.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03751 for ; Thu, 31 Oct 2002 12:42:40 -0500 (EST) Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14]) by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g9VHj3j459612 for ; Thu, 31 Oct 2002 12:45:03 -0500 (EST) Received: from tlin (E112210.vtacs.com [208.138.112.210]) by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.2.1-GA) with ESMTP id ARJ62899 (AUTH talin); Thu, 31 Oct 2002 12:45:01 -0500 (EST) Message-ID: <003001c28105$08ffda00$755a640a@vtacs.com> From: "Tao Lin" To: References: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> Subject: Re: [manet] Testing DSR over ethernet Date: Thu, 31 Oct 2002 12:43:34 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit For the topology emulation of wireless ad hoc networks in a wired testbed, we developed such a tool in our lab. The link for this free software at http://io.irean.vt.edu/~tlin/ (196 downloads till now) and a paper for it can also be found at this web page. Use this tool, users only need to setup a wired testbed. No need to modify mobile nodes. Mobile nodes can be configured using IP addresses in one subnet or different subnets if they may talk to each other directly. Thanks, Tao ----- Original Message ----- From: To: "Sourabh Sharma" Cc: Sent: Thursday, October 31, 2002 12:30 PM Subject: Re: [manet] Testing DSR over ethernet > Hi Sourabh, > > The issue of IP addresses is not so simple. > > I believe Pradeep is trying to emulate a MANET situation on a Eithernet. If > so, he wants Node 3 to be reachable by Node 1 and Node 4. To try to do this > with subnet addresses, he would have to have Node 3 in two diferent subnets; > one for Node 1 and one for Node 4. In addition, to simulate movement, he would > have to reassign subnets to different nodes as the simulation progresses. That > would mean changing IP addresses as he goes. If Node 3 is reachable by Nodes 1 > and 4, then it must be in a supernet. If this changes, not only will Node 3 > get a new IP, but it may have to change levels within the hierarchy. > > Sounds pretty complicated to me. > > Also, there are schemes by which a MANET assigns internal IPs to or augments > existing IP addresses of its nodes, thereby permitting aggregation of routes by > IP subnets. In effect, part of the routing update problem is replaced by the > dynamic IP update and forwarding address problems. For smallish MANETS, it > offers no clear advantage, but for very large ones, it might be beneficial. > There doesn't seem to be a consensus on if and when this is a good strategy at > this time. > > Point is, the dealing with unrelated IP addresses can be done in a number of > ways within a MANET and, in some schemes, the routing algorithm might > actually "see" related IP addresses. > > John Mullen > > Quoting Sourabh Sharma : > > > > > > > Instead of all this trouble why doesn't Pradeep configue > > the nodes to be in different subnets.I've said this before > > and emphasize again: > > Apart from the automatic update of routing tables- and this finding > > routes to new nodes, the > > test of an ad-hoc routing protocol is to find routes when > > the nodes have totally different/unrelated Ipaddreses. > > > > Pradeep, I strongly , suggest you try this, if what Dave says > > is the actual problem, viz ICMP redirects. > > > > -Sourabh > > > > > > > > > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > > > hi > > > > > > > > My apologies if you get multiple copies of this email. My friend, who > > is > > > > not a member of the group, tried to send the same email. Since he was > > not > > > > successful, I am sending it now. Sorry about that!! > > > > > > > > we are trying to run DSR (Alex Song's implementation) over an ethernet > > > > LAN. we are trying to set up a network (with eight nodes) as follows: > > > > node 1 is within the transmission range of nodes 2 and 3 but not other > > > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > > > (route request) and only nodes 2 and 3 have to send RREPs (route > > > > replies) and not the other nodes (including node 4 though they are all > > > > in the same broadcast medium - the wired ethernet). this is just to > > > > setup a multihop network. > > > > > > > > at node 4, we tried to block broadcast packets from node 1 using > > > > iptables so that node 4 would not reply to RREQs from node 1. > > > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > > > > were not able to ping node 4 from node 1). then we up- ed node 3 > > (which > > > > is in the "transmission range" of both node 1 and node 4. we were able > > > > to ping node 3 from both node 1 and node 4). but we still we were > > > > unable to ping node 4 from node 1 (we were expecting node 3, being > > > > within the "transmission range" of node 4 to aid node 1 in reaching > > > > node 4. but this didnt happen). > > > > > > > > could anyone help us in figuring out what the problem is ? Any > > suggestions > > > > are most welcome (we have setting up VLANs in mind instead of using > > > > iptables, but would like to explore other options before disturbing the > > > > current network setup) > > > > > > > > we have tried to be as clear as possible in stating our problem. > > > > > > > > thanks in advance! > > > > regards > > > > girish & pradeep. > > > > > > > > > > > > > > > > _______________________________________________ > > > > manet mailing list > > > > manet@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > -- > > > David Young OJC Technologies > > > dyoung@ojctech.com Engineering from the Right Brain > > > Urbana, IL * (217) 278-3933 > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > -------------------------------------------------- > > There is an answer to everything in this world. > > The only question which remains to be answered > > IS whether we know the answers or not. > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 13:00:06 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04910 for ; Thu, 31 Oct 2002 13:00:06 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VI23w17604 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 13:02:03 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VI23v17601 for ; Thu, 31 Oct 2002 13:02:03 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04872 for ; Thu, 31 Oct 2002 12:59:35 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHlUv16629; Thu, 31 Oct 2002 12:47:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHifv16509 for ; Thu, 31 Oct 2002 12:44:41 -0500 Received: from c000.snv.cp.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA03733 for ; Thu, 31 Oct 2002 12:42:13 -0500 (EST) Received: (cpmta 23541 invoked from network); 31 Oct 2002 09:44:32 -0800 Received: from 128.174.253.126 (HELO cs.uiuc.edu) by smtp.carter.net (209.228.32.65) with SMTP; 31 Oct 2002 09:44:32 -0800 X-Sent: 31 Oct 2002 17:44:32 GMT Message-ID: <3DC16BFF.4@cs.uiuc.edu> Date: Thu, 31 Oct 2002 11:44:31 -0600 From: Casey Carter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020606 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Subject: Re: [manet] A very good tool References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit ccarter wrote: >Content-Type: application/octet-stream; > name=gen_background2[1].jpg >Content-Transfer-Encoding: base64 >Content-ID: > > > Just so everyone knows, I did not send this. The message headers say it came from mx05.cluster1.charter.net, so I figure charter.net is hosting an open-relay mail server that allowed someone to forge my address as the source. If I was going to send a virus to the list, I'm sure I could at least do a better job of it. ;) -- Casey Carter Casey@Carter.net ccarter@uiuc.edu AIM: cartec69 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 13:27:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06622 for ; Thu, 31 Oct 2002 13:27:52 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VITo119897 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 13:29:50 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VITov19894 for ; Thu, 31 Oct 2002 13:29:50 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06604 for ; Thu, 31 Oct 2002 13:27:21 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VIJpv19310; Thu, 31 Oct 2002 13:19:51 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VIGDv19169 for ; Thu, 31 Oct 2002 13:16:13 -0500 Received: from nautique.ornl.gov (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05849 for ; Thu, 31 Oct 2002 13:13:44 -0500 (EST) Received: from localhost.localdomain (LOCALHOST [127.0.0.1]) by nautique.ornl.gov (Postfix) with ESMTP id 1B07F6FD3; Thu, 31 Oct 2002 13:16:04 -0500 (EST) Subject: Re: [manet] Testing DSR over ethernet From: Lawrence MacIntyre To: jomullen@nmsu.edu Cc: Sourabh Sharma , manet@ietf.org In-Reply-To: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> References: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-2eai/AZoEBwJFizRykLa" X-Mailer: Ximian Evolution 1.0.8 Date: 31 Oct 2002 13:16:03 -0500 Message-Id: <1036088164.20309.5.camel@nautique> Mime-Version: 1.0 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=-2eai/AZoEBwJFizRykLa Content-Type: text/plain Content-Transfer-Encoding: quoted-printable A simple way is to configure the machines with different subnet addresses, but hook them to the same layer 2 network (e.g. ethernet switch). By adding interface routes to the machines, you can simulate reachability. e.g. Laptop 1: 10.100.0.1/24 Laptop 2: 10.100.1.1/24 Laptop 3: 10.100.2.1/24 On Laptop 1: route add -host 10.100.1.1 eth0 On Laptop 2: route add -host 10.100.0.1 eth0 route add -host 10.100.2.1 eth0 On Laptop 3: route add -host 10.100.1.1 eth0 Now Laptop 1 can only see Laptop 2, Laptop 3 can only see Laptop 2, and Laptop 2 can see both other machines. If your Ad-Hoc routing is working correctly, you should be able to communicate from Laptop 3 to Laptop 1 via Laptop 2. On Thu, 2002-10-31 at 12:30, jomullen@nmsu.edu wrote: > Hi Sourabh, >=20 > The issue of IP addresses is not so simple. >=20 > I believe Pradeep is trying to emulate a MANET situation on a Eithernet. = If=20 > so, he wants Node 3 to be reachable by Node 1 and Node 4. To try to do t= his=20 > with subnet addresses, he would have to have Node 3 in two diferent subne= ts;=20 > one for Node 1 and one for Node 4. In addition, to simulate movement, he= would=20 > have to reassign subnets to different nodes as the simulation progresses.= That=20 > would mean changing IP addresses as he goes. If Node 3 is reachable by N= odes 1=20 > and 4, then it must be in a supernet. If this changes, not only will Nod= e 3=20 > get a new IP, but it may have to change levels within the hierarchy. >=20 > Sounds pretty complicated to me. >=20 > Also, there are schemes by which a MANET assigns internal IPs to or augme= nts=20 > existing IP addresses of its nodes, thereby permitting aggregation of rou= tes by=20 > IP subnets. In effect, part of the routing update problem is replaced by= the=20 > dynamic IP update and forwarding address problems. For smallish MANETS, = it=20 > offers no clear advantage, but for very large ones, it might be beneficia= l. =20 > There doesn't seem to be a consensus on if and when this is a good strate= gy at=20 > this time. =20 >=20 > Point is, the dealing with unrelated IP addresses can be done in a number= of=20 > ways within a MANET and, in some schemes, the routing algorithm might=20 > actually "see" related IP addresses. >=20 > John Mullen >=20 > Quoting Sourabh Sharma : >=20 > > > >=20 > > Instead of all this trouble why doesn't Pradeep configue > > the nodes to be in different subnets.I've said this before > > and emphasize again: > > Apart from the automatic update of routing tables- and this finding > > routes to new nodes, the > > test of an ad-hoc routing protocol is to find routes when > > the nodes have totally different/unrelated Ipaddreses. > > =20 > > Pradeep, I strongly , suggest you try this, if what Dave says > > is the actual problem, viz ICMP redirects. > >=20 > > -Sourabh > >=20 > >=20 > > >=20 > > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > > > hi > > > >=20 > > > > My apologies if you get multiple copies of this email. My friend, w= ho > > is > > > > not a member of the group, tried to send the same email. Since he w= as > > not > > > > successful, I am sending it now. Sorry about that!! > > > >=20 > > > > we are trying to run DSR (Alex Song's implementation) over an ether= net > > > > LAN. we are trying to set up a network (with eight nodes) as follow= s: > > > > node 1 is within the transmission range of nodes 2 and 3 but not ot= her > > > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > > > (route request) and only nodes 2 and 3 have to send RREPs (route > > > > replies) and not the other nodes (including node 4 though they are= all > > > > in the same broadcast medium - the wired ethernet). this is just t= o > > > > setup a multihop network. > > > >=20 > > > > at node 4, we tried to block broadcast packets from node 1 using > > > > iptables so that node 4 would not reply to RREQs from node 1. > > > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. = we > > > > were not able to ping node 4 from node 1). then we up- ed node 3 > > (which > > > > is in the "transmission range" of both node 1 and node 4. we were = able > > > > to ping node 3 from both node 1 and node 4). but we still we were > > > > unable to ping node 4 from node 1 (we were expecting node 3, being > > > > within the "transmission range" of node 4 to aid node 1 in reachin= g > > > > node 4. but this didnt happen). > > > >=20 > > > > could anyone help us in figuring out what the problem is ? Any > > suggestions > > > > are most welcome (we have setting up VLANs in mind instead of using > > > > iptables, but would like to explore other options before disturbing= the > > > > current network setup) > > > >=20 > > > > we have tried to be as clear as possible in stating our problem. > > > >=20 > > > > thanks in advance! > > > > regards > > > > girish & pradeep. > > > >=20 > > > >=20 > > > >=20 > > > > _______________________________________________ > > > > manet mailing list > > > > manet@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/manet > > >=20 > > > --=20 > > > David Young OJC Technologies > > > dyoung@ojctech.com Engineering from the Right Brain > > > Urbana, IL * (217) 278-3933 > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > >=20 > >=20 > > -------------------------------------------------- > > There is an answer to everything in this world. > > The only question which remains to be answered > > IS whether we know the answers or not. > >=20 > >=20 > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > >=20 >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet --=20 Lawrence MacIntyre 865.574.8696 lpz@ornl.gov Oak Ridge National Laboratory Center for High Performance Information Infrastructure Technology --=-2eai/AZoEBwJFizRykLa Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9wXNjCNjP8rawCW4RAhg9AJ9BJgh8Xdi+U+JJOeSQdnxUXGJ4IwCfRJWm 2F9tY6J7gYm0rG9XwXF3jiY= =OVfE -----END PGP SIGNATURE----- --=-2eai/AZoEBwJFizRykLa-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 13:27:59 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06639 for ; Thu, 31 Oct 2002 13:27:58 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VIJpv19310; Thu, 31 Oct 2002 13:19:51 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VIGDv19169 for ; Thu, 31 Oct 2002 13:16:13 -0500 Received: from nautique.ornl.gov (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05849 for ; Thu, 31 Oct 2002 13:13:44 -0500 (EST) Received: from localhost.localdomain (LOCALHOST [127.0.0.1]) by nautique.ornl.gov (Postfix) with ESMTP id 1B07F6FD3; Thu, 31 Oct 2002 13:16:04 -0500 (EST) Subject: Re: [manet] Testing DSR over ethernet From: Lawrence MacIntyre To: jomullen@nmsu.edu Cc: Sourabh Sharma , manet@ietf.org In-Reply-To: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> References: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-2eai/AZoEBwJFizRykLa" X-Mailer: Ximian Evolution 1.0.8 Date: 31 Oct 2002 13:16:03 -0500 Message-Id: <1036088164.20309.5.camel@nautique> Mime-Version: 1.0 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=-2eai/AZoEBwJFizRykLa Content-Type: text/plain Content-Transfer-Encoding: quoted-printable A simple way is to configure the machines with different subnet addresses, but hook them to the same layer 2 network (e.g. ethernet switch). By adding interface routes to the machines, you can simulate reachability. e.g. Laptop 1: 10.100.0.1/24 Laptop 2: 10.100.1.1/24 Laptop 3: 10.100.2.1/24 On Laptop 1: route add -host 10.100.1.1 eth0 On Laptop 2: route add -host 10.100.0.1 eth0 route add -host 10.100.2.1 eth0 On Laptop 3: route add -host 10.100.1.1 eth0 Now Laptop 1 can only see Laptop 2, Laptop 3 can only see Laptop 2, and Laptop 2 can see both other machines. If your Ad-Hoc routing is working correctly, you should be able to communicate from Laptop 3 to Laptop 1 via Laptop 2. On Thu, 2002-10-31 at 12:30, jomullen@nmsu.edu wrote: > Hi Sourabh, >=20 > The issue of IP addresses is not so simple. >=20 > I believe Pradeep is trying to emulate a MANET situation on a Eithernet. = If=20 > so, he wants Node 3 to be reachable by Node 1 and Node 4. To try to do t= his=20 > with subnet addresses, he would have to have Node 3 in two diferent subne= ts;=20 > one for Node 1 and one for Node 4. In addition, to simulate movement, he= would=20 > have to reassign subnets to different nodes as the simulation progresses.= That=20 > would mean changing IP addresses as he goes. If Node 3 is reachable by N= odes 1=20 > and 4, then it must be in a supernet. If this changes, not only will Nod= e 3=20 > get a new IP, but it may have to change levels within the hierarchy. >=20 > Sounds pretty complicated to me. >=20 > Also, there are schemes by which a MANET assigns internal IPs to or augme= nts=20 > existing IP addresses of its nodes, thereby permitting aggregation of rou= tes by=20 > IP subnets. In effect, part of the routing update problem is replaced by= the=20 > dynamic IP update and forwarding address problems. For smallish MANETS, = it=20 > offers no clear advantage, but for very large ones, it might be beneficia= l. =20 > There doesn't seem to be a consensus on if and when this is a good strate= gy at=20 > this time. =20 >=20 > Point is, the dealing with unrelated IP addresses can be done in a number= of=20 > ways within a MANET and, in some schemes, the routing algorithm might=20 > actually "see" related IP addresses. >=20 > John Mullen >=20 > Quoting Sourabh Sharma : >=20 > > > >=20 > > Instead of all this trouble why doesn't Pradeep configue > > the nodes to be in different subnets.I've said this before > > and emphasize again: > > Apart from the automatic update of routing tables- and this finding > > routes to new nodes, the > > test of an ad-hoc routing protocol is to find routes when > > the nodes have totally different/unrelated Ipaddreses. > > =20 > > Pradeep, I strongly , suggest you try this, if what Dave says > > is the actual problem, viz ICMP redirects. > >=20 > > -Sourabh > >=20 > >=20 > > >=20 > > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > > > hi > > > >=20 > > > > My apologies if you get multiple copies of this email. My friend, w= ho > > is > > > > not a member of the group, tried to send the same email. Since he w= as > > not > > > > successful, I am sending it now. Sorry about that!! > > > >=20 > > > > we are trying to run DSR (Alex Song's implementation) over an ether= net > > > > LAN. we are trying to set up a network (with eight nodes) as follow= s: > > > > node 1 is within the transmission range of nodes 2 and 3 but not ot= her > > > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > > > (route request) and only nodes 2 and 3 have to send RREPs (route > > > > replies) and not the other nodes (including node 4 though they are= all > > > > in the same broadcast medium - the wired ethernet). this is just t= o > > > > setup a multihop network. > > > >=20 > > > > at node 4, we tried to block broadcast packets from node 1 using > > > > iptables so that node 4 would not reply to RREQs from node 1. > > > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. = we > > > > were not able to ping node 4 from node 1). then we up- ed node 3 > > (which > > > > is in the "transmission range" of both node 1 and node 4. we were = able > > > > to ping node 3 from both node 1 and node 4). but we still we were > > > > unable to ping node 4 from node 1 (we were expecting node 3, being > > > > within the "transmission range" of node 4 to aid node 1 in reachin= g > > > > node 4. but this didnt happen). > > > >=20 > > > > could anyone help us in figuring out what the problem is ? Any > > suggestions > > > > are most welcome (we have setting up VLANs in mind instead of using > > > > iptables, but would like to explore other options before disturbing= the > > > > current network setup) > > > >=20 > > > > we have tried to be as clear as possible in stating our problem. > > > >=20 > > > > thanks in advance! > > > > regards > > > > girish & pradeep. > > > >=20 > > > >=20 > > > >=20 > > > > _______________________________________________ > > > > manet mailing list > > > > manet@ietf.org > > > > https://www1.ietf.org/mailman/listinfo/manet > > >=20 > > > --=20 > > > David Young OJC Technologies > > > dyoung@ojctech.com Engineering from the Right Brain > > > Urbana, IL * (217) 278-3933 > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > >=20 > >=20 > > -------------------------------------------------- > > There is an answer to everything in this world. > > The only question which remains to be answered > > IS whether we know the answers or not. > >=20 > >=20 > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > >=20 >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet --=20 Lawrence MacIntyre 865.574.8696 lpz@ornl.gov Oak Ridge National Laboratory Center for High Performance Information Infrastructure Technology --=-2eai/AZoEBwJFizRykLa Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9wXNjCNjP8rawCW4RAhg9AJ9BJgh8Xdi+U+JJOeSQdnxUXGJ4IwCfRJWm 2F9tY6J7gYm0rG9XwXF3jiY= =OVfE -----END PGP SIGNATURE----- --=-2eai/AZoEBwJFizRykLa-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 14:07:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08815 for ; Thu, 31 Oct 2002 14:07:35 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VJ9Xg22770 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 14:09:33 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VJ9Xv22767 for ; Thu, 31 Oct 2002 14:09:33 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08810 for ; Thu, 31 Oct 2002 14:07:04 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHsBv16921; Thu, 31 Oct 2002 12:54:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHp9v16791 for ; Thu, 31 Oct 2002 12:51:09 -0500 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04054 for ; Thu, 31 Oct 2002 12:48:40 -0500 (EST) Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id BAA23463; Fri, 1 Nov 2002 01:50:58 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500b.comp.nus.edu.sg via csmap id 29251; Fri, 01 Nov 2002 01:39:00 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id BAA16045; Fri, 1 Nov 2002 01:50:57 +0800 (GMT-8) Date: Fri, 1 Nov 2002 01:50:57 +0800 (GMT-8) From: Sourabh Sharma To: jomullen@nmsu.edu cc: manet@ietf.org, Sandeep Kumar In-Reply-To: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] [IPAddr] Final Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi all, I think there has been too much discussion on Ipadresses and subnetting. I would like to put a clearer picture for everyone. Please continue reading. On Thu, 31 Oct 2002 jomullen@nmsu.edu wrote: > The issue of IP addresses is not so simple. > > I believe Pradeep is trying to emulate a MANET situation on a Eithernet. If > so, he wants Node 3 to be reachable by Node 1 and Node 4. To try to do this > with subnet addresses, he would have to have Node 3 in two diferent subnets; > one for Node 1 and one for Node 4. John, Thanks for the insight. I agree of this. This holds well for Ethernet and normal routing protocols. Now for mobile nodes(802.11): Iamgine this situation with me. Node A : Ip: 97.98.99.100 (class A /8 ) Node B: Ip: 147.148.149.150 (Class B /16) Under normal IP "circumstances": these nodes will not ping each other. As soon as we run AODV (on both the nodes) they both discover each other as neighbours and consequently can communicate.( As a proof we see A and B's routing table being updated. I've experimented and have actually seen this happen.) Now when we bring in a new node C. ( which is within the transmission range of B but not A) Node C: ip: 201.202.203.204 (class C /24) Now, I see no reason why B and C should not be able to communicate with each other. Since AODV helps them detect each other as neighbour. Following up with AODv's capabilty to allow discovery of new paths, I see no reason why A should not be able to reach C using B as a hop. So in the ideal scenario: A -- B -- C All 3 nodes can have IPaddresses of diff classes but should still be able to route packets to each other though A and C are not in each other's direct transmission range! I see no reason, why this should not work. I hope everyone agrees with me on this. -Sourabh . -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. > > > > Instead of all this trouble why doesn't Pradeep configue > > the nodes to be in different subnets.I've said this before > > and emphasize again: > > Apart from the automatic update of routing tables- and this finding > > routes to new nodes, the > > test of an ad-hoc routing protocol is to find routes when > > the nodes have totally different/unrelated Ipaddreses. > > > > Pradeep, I strongly , suggest you try this, if what Dave says > > is the actual problem, viz ICMP redirects. > > > > -Sourabh > > > > > > > > > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > > > hi > > > > > > > > My apologies if you get multiple copies of this email. My friend, who > > is > > > > not a member of the group, tried to send the same email. Since he was > > not > > > > successful, I am sending it now. Sorry about that!! > > > > > > > > we are trying to run DSR (Alex Song's implementation) over an ethernet > > > > LAN. we are trying to set up a network (with eight nodes) as follows: > > > > node 1 is within the transmission range of nodes 2 and 3 but not other > > > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > > > (route request) and only nodes 2 and 3 have to send RREPs (route > > > > replies) and not the other nodes (including node 4 though they are all > > > > in the same broadcast medium - the wired ethernet). this is just to > > > > setup a multihop network. > > > > > > > > at node 4, we tried to block broadcast packets from node 1 using > > > > iptables so that node 4 would not reply to RREQs from node 1. > > > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > > > > were not able to ping node 4 from node 1). then we up- ed node 3 > > (which > > > > is in the "transmission range" of both node 1 and node 4. we were able > > > > to ping node 3 from both node 1 and node 4). but we still we were > > > > unable to ping node 4 from node 1 (we were expecting node 3, being > > > > within the "transmission range" of node 4 to aid node 1 in reaching > > > > node 4. but this didnt happen). > > > > > > > > could anyone help us in figuring out what the problem is ? Any > > suggestions > > > > are most welcome (we have setting up VLANs in mind instead of using > > > > iptables, but would like to explore other options before disturbing the > > > > current network setup) > > > > > > > > we have tried to be as clear as possible in stating our problem. > > > > > > > > thanks in advance! > > > > regards > > > > girish & pradeep. > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 14:07:37 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08828 for ; Thu, 31 Oct 2002 14:07:37 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHsBv16921; Thu, 31 Oct 2002 12:54:11 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VHp9v16791 for ; Thu, 31 Oct 2002 12:51:09 -0500 Received: from x86unx3.comp.nus.edu.sg (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04054 for ; Thu, 31 Oct 2002 12:48:40 -0500 (EST) Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id BAA23463; Fri, 1 Nov 2002 01:50:58 +0800 (GMT-8) Received: from sf3.comp.nus.edu.sg(137.132.90.55) by e500b.comp.nus.edu.sg via csmap id 29251; Fri, 01 Nov 2002 01:39:00 +0800 (SGT) Received: from localhost (sourabhs@localhost) by sf3.comp.nus.edu.sg (8.8.5/8.8.5) with ESMTP id BAA16045; Fri, 1 Nov 2002 01:50:57 +0800 (GMT-8) Date: Fri, 1 Nov 2002 01:50:57 +0800 (GMT-8) From: Sourabh Sharma To: jomullen@nmsu.edu cc: manet@ietf.org, Sandeep Kumar In-Reply-To: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] [IPAddr] Final Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi all, I think there has been too much discussion on Ipadresses and subnetting. I would like to put a clearer picture for everyone. Please continue reading. On Thu, 31 Oct 2002 jomullen@nmsu.edu wrote: > The issue of IP addresses is not so simple. > > I believe Pradeep is trying to emulate a MANET situation on a Eithernet. If > so, he wants Node 3 to be reachable by Node 1 and Node 4. To try to do this > with subnet addresses, he would have to have Node 3 in two diferent subnets; > one for Node 1 and one for Node 4. John, Thanks for the insight. I agree of this. This holds well for Ethernet and normal routing protocols. Now for mobile nodes(802.11): Iamgine this situation with me. Node A : Ip: 97.98.99.100 (class A /8 ) Node B: Ip: 147.148.149.150 (Class B /16) Under normal IP "circumstances": these nodes will not ping each other. As soon as we run AODV (on both the nodes) they both discover each other as neighbours and consequently can communicate.( As a proof we see A and B's routing table being updated. I've experimented and have actually seen this happen.) Now when we bring in a new node C. ( which is within the transmission range of B but not A) Node C: ip: 201.202.203.204 (class C /24) Now, I see no reason why B and C should not be able to communicate with each other. Since AODV helps them detect each other as neighbour. Following up with AODv's capabilty to allow discovery of new paths, I see no reason why A should not be able to reach C using B as a hop. So in the ideal scenario: A -- B -- C All 3 nodes can have IPaddresses of diff classes but should still be able to route packets to each other though A and C are not in each other's direct transmission range! I see no reason, why this should not work. I hope everyone agrees with me on this. -Sourabh . -------------------------------------------------- There is an answer to everything in this world. The only question which remains to be answered IS whether we know the answers or not. > > > > Instead of all this trouble why doesn't Pradeep configue > > the nodes to be in different subnets.I've said this before > > and emphasize again: > > Apart from the automatic update of routing tables- and this finding > > routes to new nodes, the > > test of an ad-hoc routing protocol is to find routes when > > the nodes have totally different/unrelated Ipaddreses. > > > > Pradeep, I strongly , suggest you try this, if what Dave says > > is the actual problem, viz ICMP redirects. > > > > -Sourabh > > > > > > > > > > On Thu, Oct 31, 2002 at 12:59:32AM -0600, Pradeepkumar Mani wrote: > > > > hi > > > > > > > > My apologies if you get multiple copies of this email. My friend, who > > is > > > > not a member of the group, tried to send the same email. Since he was > > not > > > > successful, I am sending it now. Sorry about that!! > > > > > > > > we are trying to run DSR (Alex Song's implementation) over an ethernet > > > > LAN. we are trying to set up a network (with eight nodes) as follows: > > > > node 1 is within the transmission range of nodes 2 and 3 but not other > > > > nodes. if node 1 has to reach node 4, node 1 will broadcast a RREQ > > > > (route request) and only nodes 2 and 3 have to send RREPs (route > > > > replies) and not the other nodes (including node 4 though they are all > > > > in the same broadcast medium - the wired ethernet). this is just to > > > > setup a multihop network. > > > > > > > > at node 4, we tried to block broadcast packets from node 1 using > > > > iptables so that node 4 would not reply to RREQs from node 1. > > > > when nodes 1 and 4 were the only ones up, this seemed to work (ie. we > > > > were not able to ping node 4 from node 1). then we up- ed node 3 > > (which > > > > is in the "transmission range" of both node 1 and node 4. we were able > > > > to ping node 3 from both node 1 and node 4). but we still we were > > > > unable to ping node 4 from node 1 (we were expecting node 3, being > > > > within the "transmission range" of node 4 to aid node 1 in reaching > > > > node 4. but this didnt happen). > > > > > > > > could anyone help us in figuring out what the problem is ? Any > > suggestions > > > > are most welcome (we have setting up VLANs in mind instead of using > > > > iptables, but would like to explore other options before disturbing the > > > > current network setup) > > > > > > > > we have tried to be as clear as possible in stating our problem. > > > > > > > > thanks in advance! > > > > regards > > > > girish & pradeep. > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 15:10:37 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12600 for ; Thu, 31 Oct 2002 15:10:37 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VKCaM26545 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 15:12:36 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VKCav26542 for ; Thu, 31 Oct 2002 15:12:36 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12591 for ; Thu, 31 Oct 2002 15:10:06 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VK4Sv25597; Thu, 31 Oct 2002 15:04:28 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VK0Pv25428 for ; Thu, 31 Oct 2002 15:00:25 -0500 Received: from meshpdc.meshnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12041 for ; Thu, 31 Oct 2002 14:57:54 -0500 (EST) Received: from meshnetworks.com (172.16.1.171 [172.16.1.171]) by meshpdc.meshnetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id V0RTK2MJ; Thu, 31 Oct 2002 15:00:15 -0500 Message-ID: <3DC18BD7.1080403@meshnetworks.com> Date: Thu, 31 Oct 2002 15:00:23 -0500 From: "Phillip D. Neumiller" Organization: www.meshnetworks.com (MeshNetworks, Inc.) User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] 802.11a and Linux drivers (any luck?) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I realize that this is a bit off topic, but many folks on this list may have an answer for this question. Has anybody had any luck running ANY 802.11A (54 Mbps OFDM) cards on Linux? I can't seem to locate a driver that works properly for cards based on the Atheros chip set (Proxim, D-Link, Netgear)... Any hits/pointers would be greatly appreciated! Thanks, Phil _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 15:10:40 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12613 for ; Thu, 31 Oct 2002 15:10:39 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VK4Sv25597; Thu, 31 Oct 2002 15:04:28 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VK0Pv25428 for ; Thu, 31 Oct 2002 15:00:25 -0500 Received: from meshpdc.meshnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12041 for ; Thu, 31 Oct 2002 14:57:54 -0500 (EST) Received: from meshnetworks.com (172.16.1.171 [172.16.1.171]) by meshpdc.meshnetworks.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id V0RTK2MJ; Thu, 31 Oct 2002 15:00:15 -0500 Message-ID: <3DC18BD7.1080403@meshnetworks.com> Date: Thu, 31 Oct 2002 15:00:23 -0500 From: "Phillip D. Neumiller" Organization: www.meshnetworks.com (MeshNetworks, Inc.) User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] 802.11a and Linux drivers (any luck?) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit I realize that this is a bit off topic, but many folks on this list may have an answer for this question. Has anybody had any luck running ANY 802.11A (54 Mbps OFDM) cards on Linux? I can't seem to locate a driver that works properly for cards based on the Atheros chip set (Proxim, D-Link, Netgear)... Any hits/pointers would be greatly appreciated! Thanks, Phil _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Oct 31 15:36:35 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13693 for ; Thu, 31 Oct 2002 15:36:35 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9VKcYr28186 for manet-archive@odin.ietf.org; Thu, 31 Oct 2002 15:38:34 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VKcYv28183 for ; Thu, 31 Oct 2002 15:38:34 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13675 for ; Thu, 31 Oct 2002 15:36:04 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VKUZv27151; Thu, 31 Oct 2002 15:30:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VKRPv27053 for ; Thu, 31 Oct 2002 15:27:25 -0500 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13087 for ; Thu, 31 Oct 2002 15:24:51 -0500 (EST) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id PAA00921; Thu, 31 Oct 2002 15:25:46 -0500 (EST) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002103115254605205 ; Thu, 31 Oct 2002 15:25:46 -0500 Message-Id: <5.1.1.5.2.20021031152252.019d1498@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Thu, 31 Oct 2002 15:25:41 -0500 To: jomullen@nmsu.edu, Sourabh Sharma From: Joe Macker Subject: Re: [manet] Testing DSR over ethernet Cc: manet@ietf.org In-Reply-To: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 10:30 AM 10/31/2002 -0700, jomullen@nmsu.edu wrote: >Hi Sourabh, > >The issue of IP addresses is not so simple. > >I believe Pradeep is trying to emulate a MANET situation on a Eithernet. If >so, he wants Node 3 to be reachable by Node 1 and Node 4. To try to do this >with subnet addresses, he would have to have Node 3 in two diferent subnets; >one for Node 1 and one for Node 4. In addition, to simulate movement, he would >have to reassign subnets to different nodes as the simulation progresses. That dynamic filtering works fine as an emulator.. and isn't complex. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-admin@ietf.org Thu Oct 31 15:36:37 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13706 for ; Thu, 31 Oct 2002 15:36:37 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VKUZv27151; Thu, 31 Oct 2002 15:30:35 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VKRPv27053 for ; Thu, 31 Oct 2002 15:27:25 -0500 Received: from itd.nrl.navy.mil (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13087 for ; Thu, 31 Oct 2002 15:24:51 -0500 (EST) Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by itd.nrl.navy.mil (8.8.8+Sun/8.8.8) with SMTP id PAA00921; Thu, 31 Oct 2002 15:25:46 -0500 (EST) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.0.0.44) with SMTP id M2002103115254605205 ; Thu, 31 Oct 2002 15:25:46 -0500 Message-Id: <5.1.1.5.2.20021031152252.019d1498@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Thu, 31 Oct 2002 15:25:41 -0500 To: jomullen@nmsu.edu, Sourabh Sharma From: Joe Macker Subject: Re: [manet] Testing DSR over ethernet Cc: manet@ietf.org In-Reply-To: <1036085409.3dc168a1b31b5@webmail.nmsu.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 10:30 AM 10/31/2002 -0700, jomullen@nmsu.edu wrote: >Hi Sourabh, > >The issue of IP addresses is not so simple. > >I believe Pradeep is trying to emulate a MANET situation on a Eithernet. If >so, he wants Node 3 to be reachable by Node 1 and Node 4. To try to do this >with subnet addresses, he would have to have Node 3 in two diferent subnets; >one for Node 1 and one for Node 4. In addition, to simulate movement, he would >have to reassign subnets to different nodes as the simulation progresses. That dynamic filtering works fine as an emulator.. and isn't complex. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet