From mailnull@www1.ietf.org Thu May 1 16:08:14 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06715 for ; Thu, 1 May 2003 16:08:14 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h41KEOW32585 for manet-archive@odin.ietf.org; Thu, 1 May 2003 16:14: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 h41KEO832582 for ; Thu, 1 May 2003 16:14:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06272 for ; Thu, 1 May 2003 16:04:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BKKE-00061r-00 for manet-web-archive@ietf.org; Thu, 01 May 2003 16:06:38 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19BKKE-00061n-00 for manet-web-archive@ietf.org; Thu, 01 May 2003 16:06:38 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h41JxX828239; Thu, 1 May 2003 15:59: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 h41JnY826021 for ; Thu, 1 May 2003 15:49:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04473 for ; Thu, 1 May 2003 15:42:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19BJzM-0005oq-00 for manet@ietf.org; Thu, 01 May 2003 15:45:04 -0400 Received: from f117.law12.hotmail.com ([64.4.19.117] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19BJzG-0005mA-00 for manet@ietf.org; Thu, 01 May 2003 15:44:58 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 1 May 2003 12:43:40 -0700 Received: from 141.84.69.17 by lw12fd.law12.hotmail.msn.com with HTTP; Thu, 01 May 2003 19:43:35 GMT X-Originating-IP: [141.84.69.17] X-Originating-Email: [wliangy@hotmail.com] From: "Wang Liangyou" To: manet@ietf.org Date: Thu, 01 May 2003 19:43:35 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed Message-ID: X-OriginalArrivalTime: 01 May 2003 19:43:40.0773 (UTC) FILETIME=[F76B3150:01C31019] Subject: [manet] Helf! Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h41JxX828239 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h41KEO832582 Content-Transfer-Encoding: 8bit Hello! everyone, now I have a question about Multicast Listener Discovery (MLD) for IPv6 (RFC2710): why must that node send a Report, if a node's timer for a particular multicast address on a particular interface expires? thank you very much!! liangyou wang in munich _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun May 4 22:08:10 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11170 for ; Sun, 4 May 2003 22:08:10 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h452FuI15604 for manet-archive@odin.ietf.org; Sun, 4 May 2003 22:15: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 h452Fu815601 for ; Sun, 4 May 2003 22:15:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11127 for ; Sun, 4 May 2003 22:07:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CVQI-0003HE-00 for manet-web-archive@ietf.org; Sun, 04 May 2003 22:09:46 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CVQH-0003HA-00 for manet-web-archive@ietf.org; Sun, 04 May 2003 22:09:45 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45242814321; Sun, 4 May 2003 22:04: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 h451qk814032 for ; Sun, 4 May 2003 21:52:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10572 for ; Sun, 4 May 2003 21:44:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CV3d-00038g-00 for manet@ietf.org; Sun, 04 May 2003 21:46:21 -0400 Received: from patty.levels.unisa.edu.au ([130.220.36.156] helo=localhost) by ietf-mx with esmtp (Exim 4.12) id 19CV3X-00038c-00 for manet@ietf.org; Sun, 04 May 2003 21:46:16 -0400 Date: Mon, 5 May 2003 11:16:10 +0930 From: Peter Pham X-Mailer: The Bat! (v1.62 Christmas Edition) Personal Reply-To: Peter Pham Organization: ITR X-Priority: 3 (Normal) Message-ID: <1893646192.20030505111610@myrealbox.com> To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Wireless Lan On OPNET Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello All, I am interested in working on crosslayer design in Ad hoc network. I want to try out my ideas on OPNET 8.1. However, there are some concerns regarding the validity of the OPNET model on 802.11...Has anyone validate the correctness of the model in OPNET version 8.1 Please let me know, i really appreciate that.. -- Best regards, Peter mailto:nppham@myrealbox.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 5 05:27:57 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27743 for ; Mon, 5 May 2003 05:27:57 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h459ZrC17728 for manet-archive@odin.ietf.org; Mon, 5 May 2003 05:35: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 h459Zq817725 for ; Mon, 5 May 2003 05:35:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27735 for ; Mon, 5 May 2003 05:27:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CcHt-0004jU-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 05:29:33 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CcHt-0004jR-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 05:29:33 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h459QL817336; Mon, 5 May 2003 05:26: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 h459Kx817195 for ; Mon, 5 May 2003 05:20:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27510 for ; Mon, 5 May 2003 05:12:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cc3U-0004fR-00 for manet@ietf.org; Mon, 05 May 2003 05:14:40 -0400 Received: from mail.gmx.de ([213.165.65.60] helo=mail.gmx.net) by ietf-mx with smtp (Exim 4.12) id 19Cc3P-0004fN-00 for manet@ietf.org; Mon, 05 May 2003 05:14:35 -0400 Received: (qmail 28424 invoked by uid 65534); 5 May 2003 09:14:33 -0000 Received: from e48-2-web.dtrd.de (EHLO JUPITER) (192.166.62.143) by mail.gmx.net (mp001-rz3) with SMTP; 05 May 2003 11:14:33 +0200 From: "Nico Bayer" To: "IETF-MANET" Date: Mon, 5 May 2003 11:14:17 +0200 Message-ID: <003c01c312e6$b49445e0$8f3ea6c0@JUPITER> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003D_01C312F7.781D15E0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Subject: [manet] test - please ignore Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_003D_01C312F7.781D15E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit ------=_NextPart_000_003D_01C312F7.781D15E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

------=_NextPart_000_003D_01C312F7.781D15E0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 5 06:13:57 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28317 for ; Mon, 5 May 2003 06:13:57 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45ALsM21005 for manet-archive@odin.ietf.org; Mon, 5 May 2003 06:21: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 h45ALs821002 for ; Mon, 5 May 2003 06:21:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28308 for ; Mon, 5 May 2003 06:13:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cd0P-0004ut-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 06:15:33 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Cd0P-0004un-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 06:15:33 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45ACN820668; Mon, 5 May 2003 06:12: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 h45A7V820471 for ; Mon, 5 May 2003 06:07:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28157 for ; Mon, 5 May 2003 05:58:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CcmH-0004re-00 for manet@ietf.org; Mon, 05 May 2003 06:00:57 -0400 Received: from smtpproxy2.mitre.org ([192.80.55.70]) by ietf-mx with esmtp (Exim 4.12) id 19CcmB-0004r6-00 for manet@ietf.org; Mon, 05 May 2003 06:00:51 -0400 Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4]) by smtpproxy2.mitre.org (8.12.9/8.12.8) with ESMTP id h45A1FNe006896; Mon, 5 May 2003 06:01:15 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv2.mitre.org (8.12.9/8.12.8) with ESMTP id h45A1Dmp010957; Mon, 5 May 2003 06:01:13 -0400 (EDT) Received: from wmodempoo1-30.mitre.org (128.29.251.30) by mailhub2.mitre.org with SMTP id 2246430; Mon, 05 May 2003 06:01:09 -0400 Message-ID: <3EB63661.2FF8EC0E@mitre.org> Date: Mon, 05 May 2003 06:01:05 -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: Peter Pham CC: manet@ietf.org Subject: Re: [manet] Wireless Lan On OPNET References: <1893646192.20030505111610@myrealbox.com> 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 If you want to observe spatial reuse of the channel, you should use OPNET version 8.1.A or later. John Peter Pham wrote: > Hello All, > I am interested in working on crosslayer design in Ad hoc network. I > want to try out my ideas on OPNET 8.1. > > However, there are some concerns regarding the validity of the OPNET > model on 802.11...Has anyone validate the correctness of the model in > OPNET version 8.1 > > Please let me know, i really appreciate that.. > > > -- > Best regards, > Peter mailto:nppham@myrealbox.com > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 5 08:32:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00131 for ; Mon, 5 May 2003 08:32:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45Ce7a30008 for manet-archive@odin.ietf.org; Mon, 5 May 2003 08:40: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 h45Ce7830005 for ; Mon, 5 May 2003 08:40:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00121 for ; Mon, 5 May 2003 08:31:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CfA8-0005QC-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 08:33:44 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CfA7-0005Q9-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 08:33:43 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45CUh828700; Mon, 5 May 2003 08: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 h45CMi828475 for ; Mon, 5 May 2003 08:22:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29928 for ; Mon, 5 May 2003 08:14:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CetJ-0005MX-00 for manet@ietf.org; Mon, 05 May 2003 08:16:21 -0400 Received: from imap.gmx.net ([213.165.65.60] helo=mail.gmx.net) by ietf-mx with smtp (Exim 4.12) id 19CetE-0005MC-00 for manet@ietf.org; Mon, 05 May 2003 08:16:16 -0400 Received: (qmail 23838 invoked by uid 65534); 5 May 2003 12:15:59 -0000 Received: from e48-2-web.dtrd.de (EHLO JUPITER) (192.166.62.143) by mail.gmx.net (mp005-rz3) with SMTP; 05 May 2003 14:15:59 +0200 From: "Nico Bayer" To: "IETF-MANET" Date: Mon, 5 May 2003 14:15:43 +0200 Message-ID: <008201c31300$0d0d9eb0$8f3ea6c0@JUPITER> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0083_01C31310.D0966EB0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Subject: [manet] Address autoconfiguration Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_0083_01C31310.D0966EB0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello list, I am using the AODV6 protocol in my MANET and wanted to know if there are any ideas or papers about how to configure addresses in a MANET. If hope someone can give me some information. Thanks in advance Regards, Nico ------=_NextPart_000_0083_01C31310.D0966EB0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello list,

 

I am using the AODV6 = protocol in my MANET and wanted to know if there are any ideas or papers about = how to configure addresses in a MANET.

If hope someone can = give me some information.

 

Thanks in = advance

 

Regards, = Nico

------=_NextPart_000_0083_01C31310.D0966EB0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 5 09:39:05 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01537 for ; Mon, 5 May 2003 09:39:05 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45Dl5v02205 for manet-archive@odin.ietf.org; Mon, 5 May 2003 09:47: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 h45Dl5802202 for ; Mon, 5 May 2003 09:47:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01527 for ; Mon, 5 May 2003 09:38:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CgCv-0005nS-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 09:40:41 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CgCu-0005nO-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 09:40:40 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45DbI801108; Mon, 5 May 2003 09:37: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 h45DSf832750 for ; Mon, 5 May 2003 09:28:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01025 for ; Mon, 5 May 2003 09:19:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cfus-0005eD-00 for manet@ietf.org; Mon, 05 May 2003 09:22:02 -0400 Received: from 66-152-29-4.ded.btitelecom.net ([66.152.29.4] helo=mail.scires.com) by ietf-mx with esmtp (Exim 4.12) id 19Cfum-0005e0-00 for manet@ietf.org; Mon, 05 May 2003 09:21:56 -0400 Received: from SRCATL-MTA by mail.scires.com with Novell_GroupWise; Mon, 05 May 2003 09:22:35 -0400 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta Date: Mon, 05 May 2003 09:22:19 -0400 From: "Pete Sholander" To: , Subject: Re: [manet] Address autoconfiguration 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 Tony McAuley, et al at Telcordia have some interesting auto-configuration ideas for MANET extensions to backbone networks. Protocol acronyms are DAAP, DRCP and DCDP. Try searching at google.com ... >>> "Nico Bayer" 05/05/03 08:15AM >>> Hello list, I am using the AODV6 protocol in my MANET and wanted to know if there are any ideas or papers about how to configure addresses in a MANET. If hope someone can give me some information. Thanks in advance Regards, Nico _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 5 18:30:47 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19940 for ; Mon, 5 May 2003 18:30:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45McxC10038 for manet-archive@odin.ietf.org; Mon, 5 May 2003 18:38: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 h45Mcx810035 for ; Mon, 5 May 2003 18:38:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19918 for ; Mon, 5 May 2003 18:30:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CoVT-0001Tc-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 18:32:23 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CoVS-0001TZ-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 18:32:22 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45MT2808615; Mon, 5 May 2003 18:29: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 h45MKr808400 for ; Mon, 5 May 2003 18:20:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18245 for ; Mon, 5 May 2003 18:11:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CoDj-0001Ld-00 for manet@ietf.org; Mon, 05 May 2003 18:14:03 -0400 Received: from hellmouth3.gatech.edu ([130.207.165.163] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19CoDd-0001La-00 for manet@ietf.org; Mon, 05 May 2003 18:13:57 -0400 Received: from hellmouth3.gatech.edu (localhost [127.0.0.1]) by hellmouth3.gatech.edu (Postfix) with SMTP id 695412224F4 for ; Mon, 5 May 2003 17:44:09 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: from acmez.gatech.edu (acmez.prism.gatech.edu [130.207.171.28]) by hellmouth3.gatech.edu (Postfix) with ESMTP id 515362224F0 for ; Mon, 5 May 2003 17:44:09 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: by acmez.gatech.edu (Postfix, from userid 21503) id 3B1E34ECA9; Mon, 5 May 2003 17:44:09 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by acmez.gatech.edu (Postfix) with ESMTP id 330824FE77 for ; Mon, 5 May 2003 17:44:09 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Date: Mon, 5 May 2003 17:44:09 -0400 (EDT) From: Young-Jun Lee X-X-Sender: To: Subject: [manet] Basic question about MANET protocols 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 all, I think MANET protocols belong to the application layer in the sense that they utilize L3 (IP) or L4 (udp broadcast) functions. But I guess that when the IP layer receives a control packet (like RREQ in AODV) and passes it up to a higher layer (AODV), the information in the IP header is not available to the higher layer any more. If this is correct, how can the higher layer like AODV still use that information in the IP header like TTL? Young _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 5 19:09:04 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21108 for ; Mon, 5 May 2003 19:09:04 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45NHHb12813 for manet-archive@odin.ietf.org; Mon, 5 May 2003 19:17: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 h45NHH812810 for ; Mon, 5 May 2003 19:17:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21100 for ; Mon, 5 May 2003 19:08:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cp6W-0001lK-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 19:10:40 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Cp6V-0001lH-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 19:10:39 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45N88812353; Mon, 5 May 2003 19:08: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 h45N0p811224 for ; Mon, 5 May 2003 19:00:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20654 for ; Mon, 5 May 2003 18:52:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Coqd-0001bu-00 for manet@ietf.org; Mon, 05 May 2003 18:54:15 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19CoqS-0001b5-00 for manet@ietf.org; Mon, 05 May 2003 18:54:04 -0400 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 PAA11582 for ; Mon, 5 May 2003 15:53:48 -0700 (PDT) X-Delivered-For: Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h45MrlW02315 for ; Mon, 5 May 2003 15:53:47 -0700 X-mProtect: <200305052253> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdeqYCbV; Mon, 05 May 2003 15:53:45 PDT Message-ID: <3EB6EB7A.3B8552CE@iprg.nokia.com> Date: Mon, 05 May 2003 15:53:46 -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: IETF-MANET Subject: [Fwd: Re: [manet] Address autoconfiguration] 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 folks, I probably should have also CC:'d the mailing list for this discussion... Regards, Charlie P. -------- Original Message -------- From: "Charles E. Perkins" Subject: Re: [manet] Address autoconfiguration To: Nico Bayer Hello Nico, We have some experience with an autoconfiguration approach that is lightweight and compatible with the basic ideas of IPv6 router advertisements. You can see our protocol specification at the following URL: http://people.nokia.net/~charliep/txt/aodvid/globalv6.txt Comments are welcome! Regards, Charlie P. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 5 20:32:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22570 for ; Mon, 5 May 2003 20:32:48 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h460f3S18370 for manet-archive@odin.ietf.org; Mon, 5 May 2003 20:41: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 h460f3818367 for ; Mon, 5 May 2003 20:41:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22562 for ; Mon, 5 May 2003 20:32:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CqPY-0002Ae-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 20:34:24 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CqPY-0002Ab-00 for manet-web-archive@ietf.org; Mon, 05 May 2003 20:34:24 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h460VP816947; Mon, 5 May 2003 20:31: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 h460MU816748 for ; Mon, 5 May 2003 20:22:30 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22302 for ; Mon, 5 May 2003 20:13:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cq7N-000264-00 for manet@ietf.org; Mon, 05 May 2003 20:15:37 -0400 Received: from motgate4.mot.com ([144.189.100.102]) by ietf-mx with esmtp (Exim 4.12) id 19Cq7I-000260-00 for manet@ietf.org; Mon, 05 May 2003 20:15:32 -0400 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate4.mot.com (Motorola/Motgate4) with ESMTP id h460Fq9J019037 for ; Mon, 5 May 2003 17:15:53 -0700 (MST) Received: from homer.arc.corp.mot.com (homer.arc.corp.mot.com [10.238.80.38]) by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id h460Fn2J014067 for ; Mon, 5 May 2003 19:15:50 -0500 Received: from arc.corp.mot.com (kwchin.arc.corp.mot.com [10.238.80.134]) by homer.arc.corp.mot.com (8.12.9/8.12.8) with ESMTP id h460FmVI019138 for ; Tue, 6 May 2003 10:15:48 +1000 (EST) Message-ID: <3EB6FEB3.A45F059F@arc.corp.mot.com> Date: Tue, 06 May 2003 10:15:47 +1000 From: Kwan-Wu Chin Organization: Motorola Lab. Australia X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: manet@ietf.org Content-Type: multipart/mixed; boundary="------------37DD480BA3C11F71EB0B026C" Subject: [manet] CFP: PerCom 2004 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --------------37DD480BA3C11F71EB0B026C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------37DD480BA3C11F71EB0B026C Content-Type: text/plain; charset=us-ascii; name="CFP.txt" Content-Disposition: inline; filename="CFP.txt" Content-Transfer-Encoding: 7bit -------------------------------------------------------------------------------- *** OUR SINCERE APOLOGIES IF YOU RECEIVE MULTIPLE COPIES OF THIS CFP *** -------------------------------------------------------------------------------- CONFERENCE ANNOUNCEMENT AND CALL FOR PAPERS AND WORKSHOPS Second IEEE International Conference on Pervasive Computing and Communications PerCom 2004 (http//www.percom.org) March 14-17, 2004 Orlando, FLORIDA -------------------------------------------------------------------------------- **** Paper Submission Deadline --- September 1, 2003 **** **** Workshop Proposals Deadline --- June 1, 2003 **** Sponsored by The IEEE Computer Society and The University of Texas at Arlington Cosponsored by the IEEE TCCC and the IEEE TCPP -------------------------------------------------------------------------------- IEEE PerCom 2004 will be the second annual conference on the emerging area of pervasive computing and communications aimed at providing an exciting platform and paradigm for all the time, everywhere services. This emergence is a natural outcome of the tremendous advances in wireless networks, mobile computing, sensor networks, distributed computing, and agent technologies. PerCom 2004 will provide a high profile, leading edge forum for researchers and engineers alike to present their latest research in the field of pervasive computing and communications. As in PerCom 2003, the Mark Weiser Best Paper Award will be given to the best paper judged by the award subcommittee. Also, as in PerCom 2003, a special issue of a leading journal will be published out of the selected papers. Proposals to organize Workshops are also invited. PerCom 2004 will also feature industry exhibits and demonstrations. -------------------------------------------------------------------------------- Feature Topics: ---------------- Contributions are solicited in all areas and topics pertaining to pervasive computing research and applications. These include, but are not limited to, the following 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: ---------------------------------- Submitted papers must be unpublished and not currently under consideration elsewhere for publication. Only electronic submissions (PS or PDF) will be considered. Page limit is 12 pages (single column, 11 pt fonts and 1.5 line spaced, excluding references, figures and tables). Detailed procedure will be available at http://www.percom.org. All submitted papers will undergo a rigorous review process managed by the technical program committee. IEEE Computer Society Press will publish the conference proceedings. Papers of particular merit will be considered for a special issue of a journal. For organizing a workshop at PerCom'2004, please contact the Workshop Chairs. A separate proceedings of workshop papers will be published by the IEEE Computer Society Press. ###################################################### IMPORTANT DATES: Paper Submission: September 1, 2003 Workshop Proposal: June 1, 2003 Demonstration Proposal: October 31, 2003 Acceptance Notification: November 15, 2003 Camera Ready Manuscripts: December 10, 2003 Conference Dates: March 14-17, 2004 ###################################################### --------------------------------------------------------------------------------- Program Chair: Anand Tripathi University of Minnesota, Twin Cities Email: tripathi@cs.umn.edu Vice Program Committee Chairs: Liviu Iftode University of Maryland, College Park Klara Nahrstedt University of Illinois at Urbana Champaign Paddy Nixon University of Strathclyde, UK Technical Program Committee: ---------------------------- Jean Bacon, Cambridge University, UK B.R. Badrinath, Rutgers University, USA Stefano Basagni, Northeastern University, USA Bharat Bhargava, Purdue University, USA Vinny Cahill, Trinity College Dublin, Ireland Andrew Campbell, Columbia University, USA Roy Campbell, University of Illinois at Urbana-Champaign, USA Matthew Chalmers, Glasgow University, UK Marco Conti, Council of National Research, Italy Diane Cook, University of Texas at Arlington, USA Antonio Corradi, University of Bologna, Italy Kieran Delaney, NMRC, Ireland Armando Fox, Stanford University, USA Dave Garlan, Carnegie Mellon University, USA Amir Herzberg, Bar-Ilan University, Israel Lars Holmquist, Viktoria Institute, Sweden Viktor K. Prasanna, University of Southern California, USA Robin Kravets, University of Illinois at Urbana-Champaign, USA Hui Lei, IBM T.J. Watson Research Center, USA Diana Marculescu, Carnegie Mellon University, USA Dave Marples, Telecordia, USA Phil McKinley, Michigan State University, USA Lionel Ni, Hong Kong University of Science and Technology, Hong Kong Sotiris Nikoletseas, Patras University, Greece Chiara Petrioli, Rome University `La Sapienza', Italy Gopal Pingali, IBM T.J. Watson Research Center, USA Ravi Prakash, University of Texas at Dallas, USA Kishore Ramachandran, Georgia Institute of Technology, USA Ichiro Satoh, National Institute of Informatics, Tokyo, Japan Steve Shafer, Microsoft Research, USA Mukesh Singhal, University of Kentucky, USA Dave Snowdon, Xerox Research Europe, France Maarten van Steen, Vrije Universiteit, The Netherlands Roy Want, Intel Research, USA Zhi-Li Zhang, University of Minnesota, Minneapolis, USA Taieb Znati, University of Pittsburgh and NSF, USA ------------------------------------------------------------ Organizing Committee: ------------------------- General Chair: Sajal K. Das, University of Texas at Arlington, USA General Vice Chair: Mohan Kumar, University of Texas at Arlington, USA Steering Committee Chair: Behrooz A. Shirazi, University of Texas at Arlington, USA Keynote Lecture Chair: Roy Want, Intel Research, Santa Clara, USA Panel Chair: Chatschik Bisdikian, IBM T.J. Watson Research, USA Workshop Chairs: Hui Lei, IBM Research and Francis Lau, University of Hong Kong Education Workshop Chair: Scott Midkiff, Virginia Tech, USA NIST-Industry Workshop Chair: Vince Stanford, National Institute of Standards and Technology (NIST), USA Industry Liaison: Sumi Helal, University of Florida at Gainesville, USA Demonstration and Exhibit Chairs: Gopal Pingali, IBM T.J. Watson Research Center, USA Chistian Becker, University of Stuttgart, Germany Publicity Chairs: Diana Marculescu, Carnegie Mellon University, USA Kwan-Wu Chin, Motorola Australia, Sydney, Australia Sotirios Terzis, University of Strathclyde, UK Registration Chair: Gergely Zaruba, University of Texas at Arlington, USA Finance Chair: David Levine, University of Texas at Arlington, USA Local Arrangements : Ratan Guha (Chair) University of Central Florida, USA Mostafa Bassiouni, University of Central Florida, USA Mainak Chatterjee, University of Central Florida, USA Damla Turgut, University of Central Florida, USA --------------------------------------------------------------------------------- --------------37DD480BA3C11F71EB0B026C-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 6 03:36:24 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10628 for ; Tue, 6 May 2003 03:36:24 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h467ikF23940 for manet-archive@odin.ietf.org; Tue, 6 May 2003 03:44: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 h467ij823937 for ; Tue, 6 May 2003 03:44:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10614 for ; Tue, 6 May 2003 03:35:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cx1S-000403-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 03:37:58 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Cx1R-0003zw-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 03:37:57 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h467W1822545; Tue, 6 May 2003 03:32: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 h467KF822183 for ; Tue, 6 May 2003 03:20:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10289 for ; Tue, 6 May 2003 03:11:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CwdV-0003sq-00 for manet@ietf.org; Tue, 06 May 2003 03:13:13 -0400 Received: from promet2.deis.unibo.it ([137.204.59.2]) by ietf-mx with esmtp (Exim 4.12) id 19CwdP-0003sn-00 for manet@ietf.org; Tue, 06 May 2003 03:13:07 -0400 Received: from manson.deis.unibo.it (edu201.deis.unibo.it [137.204.45.201]) by promet2.deis.unibo.it (8.12.2/8.12.2) with ESMTP id h467DRjr022932 for ; Tue, 6 May 2003 09:13:27 +0200 (MEST) Message-Id: <5.2.0.9.0.20030506090559.02a40820@rdn.it> X-Sender: p30820@mail.deis.unibo.it X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Tue, 06 May 2003 09:13:52 +0200 To: manet@ietf.org From: Dario Bottazzi Subject: Re: [manet] Address autoconfiguration 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: , Several efforts are underway to enable auto-configuration of manet networks. Some of the most remarkable works in this field are in the list below - IPv6 stateless address autoconfiguration - PMWRS - MANETconf This list is fairly not complete... regards dario _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 6 03:47:54 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10995 for ; Tue, 6 May 2003 03:47:54 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h467uGH24650 for manet-archive@odin.ietf.org; Tue, 6 May 2003 03:56: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 h467uF824647 for ; Tue, 6 May 2003 03:56:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10983 for ; Tue, 6 May 2003 03:47:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CxCa-00045Q-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 03:49:28 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CxCZ-00045F-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 03:49:27 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h467fg823805; Tue, 6 May 2003 03: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 h467WJ822554 for ; Tue, 6 May 2003 03:32:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA10416 for ; Tue, 6 May 2003 03:23:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CwpB-0003vF-00 for manet@ietf.org; Tue, 06 May 2003 03:25:17 -0400 Received: from shaku.sfc.wide.ad.jp ([203.178.143.49]) by ietf-mx with esmtp (Exim 4.12) id 19Cwp5-0003v5-00 for manet@ietf.org; Tue, 06 May 2003 03:25:11 -0400 Received: from [192.168.0.11] (pdd8831.tkyoac00.ap.so-net.ne.jp [218.221.136.49]) (authenticated bits=0) by shaku.sfc.wide.ad.jp (8.12.9/8.12.0) with ESMTP id h467Ov4X020452; Tue, 6 May 2003 16:24:58 +0900 Date: Tue, 06 May 2003 16:14:24 +0900 From: Ryuji Wakikawa To: Young-Jun Lee Subject: Re: [manet] Basic question about MANET protocols Cc: In-Reply-To: References: Message-Id: <20030506161235.32DC.RYUJI@sfc.wide.ad.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.05.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 Young. I use advanced socket API (RFC2292) to retrieve HOPLIMIT(TTL) at application layer. If you are working on IPv4, you can use IP_TTL socket option to retrieve TTL. Try "%man ip", you could get more information. regards, ryuji > Hi all, > > I think MANET protocols belong to the application layer in the sense that > they utilize L3 (IP) or L4 (udp broadcast) functions. > But I guess that when the IP layer receives a control packet > (like RREQ in AODV) and passes it up to a higher layer (AODV), > the information in the IP header is not available to the higher layer any > more. > If this is correct, how can the higher layer like AODV still use that > information in the IP header like TTL? > > Young > > _______________________________________________ > 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 May 6 05:34:44 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12687 for ; Tue, 6 May 2003 05:34:43 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h469h8g05144 for manet-archive@odin.ietf.org; Tue, 6 May 2003 05:43: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 h469h8805141 for ; Tue, 6 May 2003 05:43:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12678 for ; Tue, 6 May 2003 05:34:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cyry-0004Yl-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 05:36:18 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Cyry-0004Yh-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 05:36:18 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h469Xp803818; Tue, 6 May 2003 05:33: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 h469Sg803606 for ; Tue, 6 May 2003 05:28:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12430 for ; Tue, 6 May 2003 05:19:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cye0-0004Tl-00 for manet@ietf.org; Tue, 06 May 2003 05:21:52 -0400 Received: from f66.law15.hotmail.com ([64.4.23.66] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19Cydv-0004T0-00 for manet@ietf.org; Tue, 06 May 2003 05:21:47 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 6 May 2003 02:20:44 -0700 Received: from 61.187.56.10 by lw15fd.law15.hotmail.msn.com with HTTP; Tue, 06 May 2003 09:20:43 GMT X-Originating-IP: [61.187.56.10] X-Originating-Email: [xiaohui_kuang@hotmail.com] From: "kuang xiaohui" To: manet@ietf.org Date: Tue, 06 May 2003 17:20:43 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed Message-ID: X-OriginalArrivalTime: 06 May 2003 09:20:44.0070 (UTC) FILETIME=[C53BAC60:01C313B0] Subject: [manet] clusterhead resource limitations? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h469Xp803818 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h469h8805141 Content-Transfer-Encoding: 8bit hi I am working on clustering algorithm in MANET.Could the clusterhead handle a large numberof nodes if the clusterhead has many neighbors. dose it has any limitation, such as MAC or other resources? Thanks in advance hidden dragon _________________________________________________________________ 享用世界上最大的电子邮件系统— MSN Hotmail。 http://www.hotmail.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 6 06:56:24 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14141 for ; Tue, 6 May 2003 06:56:24 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46B4oZ10654 for manet-archive@odin.ietf.org; Tue, 6 May 2003 07:04: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 h46B4o810651 for ; Tue, 6 May 2003 07:04:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14133 for ; Tue, 6 May 2003 06:55:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D091-0004vy-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 06:57:59 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19D090-0004vv-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 06:57:58 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46As9810184; Tue, 6 May 2003 06:54: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 h46Anv809994 for ; Tue, 6 May 2003 06:49:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13932 for ; Tue, 6 May 2003 06:40:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CzuN-0004rZ-00 for manet@ietf.org; Tue, 06 May 2003 06:42:51 -0400 Received: from dire.bris.ac.uk ([137.222.10.60]) by ietf-mx with esmtp (Exim 4.12) id 19CzuH-0004rA-00 for manet@ietf.org; Tue, 06 May 2003 06:42:45 -0400 Received: from eis.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Tue, 6 May 2003 11:42:34 +0100 Received: from EEN9097.een.bris.ac.uk (een9097.een.bris.ac.uk [137.222.189.97]) by eis.bris.ac.uk (8.11.6p2/8.11.6) with ESMTP id h46AgCE00633 for ; Tue, 6 May 2003 11:42:12 +0100 (BST) Date: Tue, 06 May 2003 11:42:11 +0100 From: "D Kothris, Electrical & Electronic Engineering" To: manet@ietf.org Message-ID: <323895747.1052221331@EEN9097.een.bris.ac.uk> Originator-Info: login-token=Mulberry:01lJOvmvj+6NGUyfX5zvUD3A3RCuP1xgLBEQzIB+PxxMIIGg==; token_authority=postmaster@bristol.ac.uk X-Mailer: Mulberry/2.2.1 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Subject: [manet] Publication sources Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Does anyone know of any source or web site that can provide a continuously UPDATED list of information for upcomming journals, conferences, letters and magazines relevant to ad hoc networks and mobile communications in general? Cheers Dimos _______________________________________________________________________ *********************************************************************** Dimosthenis Kothris Centre for Communications Research, University of Bristol, Network & Protocols group Address: Contact numbers: _______________________________________________________________________ Network & Protocols Center for Communcations research Merchant Venturers Building Tel : +44 117 903 1104 Woodland Road Fax : +44 117 954 5206 Bristol BS8 1UB Mobile: +44 7779 40 48 42 United Kingdom Email : d.kothris@bristol.ac.uk *********************************************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 6 08:10:25 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16655 for ; Tue, 6 May 2003 08:10:25 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46CIs017120 for manet-archive@odin.ietf.org; Tue, 6 May 2003 08:18: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 h46CIs817117 for ; Tue, 6 May 2003 08:18:54 -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 IAA16618 for ; Tue, 6 May 2003 08:09: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 h46C8X816483; Tue, 6 May 2003 08:08: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 h46C48815267 for ; Tue, 6 May 2003 08:04:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15897 for ; Tue, 6 May 2003 07:54:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D148-0005IL-00 for manet@ietf.org; Tue, 06 May 2003 07:57:00 -0400 Received: from zaz.kom.auc.dk ([130.225.51.10] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19D143-0005IB-00 for manet@ietf.org; Tue, 06 May 2003 07:56:55 -0400 Received: from petarp-w2k.kom.auc.dk ([192.168.110.200] helo=PETARPW2K) by zaz.kom.auc.dk with smtp (Exim 2.05 #3) id 19D14E-0002BY-00; Tue, 6 May 2003 13:57:06 +0200 Message-ID: <002401c313c6$9df46dc0$c86ea8c0@kom.auc.dk> From: "Petar Popovski" To: "D Kothris, Electrical & Electronic Engineering" , References: <323895747.1052221331@EEN9097.een.bris.ac.uk> Subject: Re: [manet] Publication sources Date: Tue, 6 May 2003 13:57:01 +0200 Organization: Center for PersonKommunikation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 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, This could help: http://dutetvg.et.tudelft.nl/~alex/CFP/ Best, Petar ----- Original Message ----- From: "D Kothris, Electrical & Electronic Engineering" To: Sent: Tuesday, May 06, 2003 12:42 PM Subject: [manet] Publication sources > Hi, > > Does anyone know of any source or web site that can provide a continuously > UPDATED list of information for upcomming journals, conferences, letters > and magazines relevant to ad hoc networks and mobile communications in > general? > > > Cheers > > Dimos > _______________________________________________________________________ > *********************************************************************** > Dimosthenis Kothris Centre for Communications Research, > University of Bristol, > Network & Protocols group > > Address: Contact numbers: > _______________________________________________________________________ > Network & Protocols > Center for Communcations research > Merchant Venturers Building Tel : +44 117 903 1104 > Woodland Road Fax : +44 117 954 5206 > Bristol BS8 1UB Mobile: +44 7779 40 48 42 > United Kingdom Email : d.kothris@bristol.ac.uk > *********************************************************************** > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 6 13:36:25 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00769 for ; Tue, 6 May 2003 13:36:25 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46Hj0F12268 for manet-archive@odin.ietf.org; Tue, 6 May 2003 13:45: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 h46Hj0812263 for ; Tue, 6 May 2003 13:45:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00727 for ; Tue, 6 May 2003 13:35:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D6O8-0000te-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 13:38:00 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19D6O7-0000tb-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 13:37:59 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46HYe810689; Tue, 6 May 2003 13:34: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 h46HQY810314 for ; Tue, 6 May 2003 13:26:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00031 for ; Tue, 6 May 2003 13:17:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D66I-0000iX-00 for manet@ietf.org; Tue, 06 May 2003 13:19:34 -0400 Received: from bubba.nmsu.edu ([128.123.3.39]) by ietf-mx with esmtp (Exim 4.12) id 19D66H-0000iH-00 for manet@ietf.org; Tue, 06 May 2003 13:19:33 -0400 Received: from dns1.nmsu.edu (dns1.NMSU.Edu [128.123.3.5]) by bubba.NMSU.Edu (8.10.2+Sun/8.9.0) with ESMTP id h46HKFU23937 for ; Tue, 6 May 2003 11:20:15 -0600 (MDT) Received: from nestor.NMSU.Edu (nestor.NMSU.Edu [128.123.34.146]) by dns1.nmsu.edu (8.9.3/8.9.0) with ESMTP id LAA71459 for ; Tue, 6 May 2003 11:20:18 -0600 (MDT) Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by nestor.NMSU.Edu (AIX4.3/8.9.3/8.9.0) with ESMTP id LAA278056 for ; Tue, 6 May 2003 11:20:17 -0600 From: "John Mullen" To: Subject: RE: [manet] clusterhead resource limitations? Date: Tue, 6 May 2003 11:20:17 -0600 Message-ID: <000001c313f3$c3ce8c60$67f57b80@IEngr.ad.nmsu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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 HD, The answer to your question would depend on what it is you are working with. Every "real-world" system has limitations, but they differ from system to system. John Mullen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of kuang xiaohui Sent: Tuesday, May 06, 2003 2:21 AM To: manet@ietf.org Subject: [manet] clusterhead resource limitations? hi I am working on clustering algorithm in MANET.Could the clusterhead handle a large numberof nodes if the clusterhead has many neighbors. dose it has any limitation, such as MAC or other resources? Thanks in advance hidden dragon _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 6 20:20:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15139 for ; Tue, 6 May 2003 20:20:56 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h470Td211483 for manet-archive@odin.ietf.org; Tue, 6 May 2003 20:29: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 h470Td811480 for ; Tue, 6 May 2003 20:29:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15123 for ; Tue, 6 May 2003 20:20:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DChb-0003jv-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 20:22:31 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DCha-0003js-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 20:22:30 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h470Gf810804; Tue, 6 May 2003 20:16: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 h470Bs810625 for ; Tue, 6 May 2003 20:11:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14669 for ; Tue, 6 May 2003 20:02:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DCQQ-0003bJ-00 for manet@ietf.org; Tue, 06 May 2003 20:04:46 -0400 Received: from f49.law15.hotmail.com ([64.4.23.49] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19DCQP-0003b9-00 for manet@ietf.org; Tue, 06 May 2003 20:04:46 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 6 May 2003 17:05:05 -0700 Received: from 61.187.56.10 by lw15fd.law15.hotmail.msn.com with HTTP; Wed, 07 May 2003 00:05:05 GMT X-Originating-IP: [61.187.56.10] X-Originating-Email: [xiaohui_kuang@hotmail.com] From: "kuang xiaohui" To: manet@ietf.org Subject: RE: [manet] clusterhead resource limitations? Date: Wed, 07 May 2003 08:05:05 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed Message-ID: X-OriginalArrivalTime: 07 May 2003 00:05:05.0929 (UTC) FILETIME=[5090CF90:01C3142C] Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h470Gf810804 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h470Td811480 Content-Transfer-Encoding: 8bit Hi Mullen I am working on clustering Algorithms. If there are some systems need clustering, but the clusterhead in the system cannot handle a large number of nodes because of some limitations, I can do the research on the clustering algorithm for them. Can you give me some read list about it? Do you think it is worth to do? Thanks for you advices. Hidden Dragon _________________________________________________________________ 享用世界上最大的电子邮件系统— MSN Hotmail。 http://www.hotmail.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 6 20:42:11 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15692 for ; Tue, 6 May 2003 20:42:11 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h470otb13418 for manet-archive@odin.ietf.org; Tue, 6 May 2003 20:50: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 h470ot813415 for ; Tue, 6 May 2003 20:50:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15683 for ; Tue, 6 May 2003 20:41:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DD2A-0003tZ-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 20:43:46 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DD29-0003tW-00 for manet-web-archive@ietf.org; Tue, 06 May 2003 20:43:45 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h470cd812763; Tue, 6 May 2003 20:38: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 h470Yp811746 for ; Tue, 6 May 2003 20:34:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15275 for ; Tue, 6 May 2003 20:25:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DCmc-0003mX-00 for manet@ietf.org; Tue, 06 May 2003 20:27:42 -0400 Received: from fsc.cpsc.ucalgary.ca ([136.159.2.3]) by ietf-mx with esmtp (Exim 4.12) id 19DCmc-0003mU-00 for manet@ietf.org; Tue, 06 May 2003 20:27:42 -0400 Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsc.cpsc.ucalgary.ca (8.12.9/8.12.9) with ESMTP id h470SRLg013271 for ; Tue, 6 May 2003 18:28:28 -0600 Received: from cpsc.ucalgary.ca (ict719g [136.159.15.15]) by imgw1.cpsc.ucalgary.ca (8.12.9/8.12.3) with ESMTP id h470SN79010399 for ; Tue, 6 May 2003 18:28:23 -0600 Message-ID: <3EB85327.5090306@cpsc.ucalgary.ca> Date: Tue, 06 May 2003 18:28:23 -0600 From: Abhinav Gupta Reply-To: gupta@cpsc.ucalgary.ca Organization: University of Calgary User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=3.3 required=6.8 X-Spam-Level: *** Content-Transfer-Encoding: 7bit Subject: [manet] APIs for implementing routing protocols Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I am looking for APIs for implementing routing in manets. Can someone provide me with the information on the APIs available for implementing the routing protocols? Thanks, Abhinav. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 7 04:26:46 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20612 for ; Wed, 7 May 2003 04:26:46 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h478ZeX24855 for manet-archive@odin.ietf.org; Wed, 7 May 2003 04:35: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 h478Ze824852 for ; Wed, 7 May 2003 04:35:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20590 for ; Wed, 7 May 2003 04:26:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DKHl-0006VC-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 04:28:21 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DKHk-0006V8-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 04:28:20 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h478MS823993; Wed, 7 May 2003 04:22: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 h47898823420 for ; Wed, 7 May 2003 04:09:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19919 for ; Wed, 7 May 2003 03:59:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DJs6-0006JV-00 for manet@ietf.org; Wed, 07 May 2003 04:01:50 -0400 Received: from marfik.cc.upv.es ([158.42.2.61] helo=marfik.upv.es) by ietf-mx with esmtp (Exim 4.12) id 19DJs4-0006JR-00 for manet@ietf.org; Wed, 07 May 2003 04:01:49 -0400 Received: from pop.upv.es (maia.cc.upv.es [158.42.4.11]) by marfik.upv.es (8.11.6/8.11.6) with ESMTP id h4782MM04597; Wed, 7 May 2003 10:02:22 +0200 Received: from smtp2.upv.es (smtp02.cc.upv.es [158.42.249.52]) by pop.upv.es (8.11.3/8.11.3) with ESMTP id h4784d629168; Wed, 7 May 2003 10:04:39 +0200 (METDST) Received: from nao.disca.upv.es (nao.disca.upv.es [158.42.53.70]) by smtp2.upv.es (8.11.4p2/8.11.4) with ESMTP id h4782Lv11515; Wed, 7 May 2003 10:02:22 +0200 Received: from disca.upv.es (tux.grc.upv.es [158.42.61.34]) by nao.disca.upv.es (Postfix on SuSE eMail Server 2.0) with ESMTP id 9666A1FE8B; Wed, 7 May 2003 10:02:12 +0200 (CEST) Message-ID: <3EB8BD95.40904@disca.upv.es> Date: Wed, 07 May 2003 10:02:29 +0200 From: Carlos Miguel Calafate User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204 X-Accept-Language: en-us MIME-Version: 1.0 To: gupta@cpsc.ucalgary.ca Cc: manet@ietf.org Subject: Re: [manet] APIs for implementing routing protocols References: <3EB85327.5090306@cpsc.ucalgary.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-MIME-Autoconverted: from 8bit to quoted-printable by marfik.upv.es id h4782MM04597 X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h47898823421 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h478MS823993 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h478Ze824852 Content-Transfer-Encoding: 8bit Hi, I have implemented a simple library that allows the implementation of routing protocols and also achieves inter-platform compatibility for WinNT, Linux and WinCE. It's available at: http://pica-api.sourceforge.net/ For an example you can check the OLSR implementation at my home page: http://reptar.grc.upv.es/~calafate/ Best regards, Carlos Abhinav Gupta wrote: > I am looking for APIs for implementing routing in manets. Can someone > provide me with the information on the APIs available for implementing > the routing protocols? > > Thanks, > Abhinav. > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -- _________________________________________________ Carlos Miguel Tavares de Ara鷍o Cesariny Calafate Bec醨io de la Universidad Polit閏nica de Valencia e-mail: calafate@disca.upv.es http://reptar.grc.upv.es/~calafate/ _________________________________________________ \"In an open world without walls and fences who needs Windows and Gates?\" _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 7 08:27:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27747 for ; Wed, 7 May 2003 08:27:58 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h47CauK10858 for manet-archive@odin.ietf.org; Wed, 7 May 2003 08:36: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 h47Cau810855 for ; Wed, 7 May 2003 08:36:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27725 for ; Wed, 7 May 2003 08:27:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DO3A-0000hZ-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 08:29:32 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DO3A-0000hW-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 08:29:32 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47CIt809723; Wed, 7 May 2003 08:18: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 h47CDR809474 for ; Wed, 7 May 2003 08:13:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26163 for ; Wed, 7 May 2003 08:03:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DNgR-0000Ap-00 for manet@ietf.org; Wed, 07 May 2003 08:06:03 -0400 Received: from f31.law15.hotmail.com ([64.4.23.31] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19DNgR-00009m-00 for manet@ietf.org; Wed, 07 May 2003 08:06:03 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 7 May 2003 05:06:19 -0700 Received: from 61.187.56.10 by lw15fd.law15.hotmail.msn.com with HTTP; Wed, 07 May 2003 12:06:17 GMT X-Originating-IP: [61.187.56.10] X-Originating-Email: [xiaohui_kuang@hotmail.com] From: "kuang xiaohui" To: manet@ietf.org Date: Wed, 07 May 2003 20:06:17 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed Message-ID: X-OriginalArrivalTime: 07 May 2003 12:06:19.0638 (UTC) FILETIME=[11B4C960:01C31491] Subject: [manet] Discuss and Help Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , X-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h47CIt809723 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h47Cau810855 Content-Transfer-Encoding: 8bit Hi all Is there a kind of MANET with these characteristic : * Every node has many neighbors, that means the node density is high. * It need some hierarchical organization to increase scalability, improve bandwidth, or to reduce delays for route. why or why not? dose the MANET for sports meeting belong to it? Thanks for you any help! Hidden Dragon _________________________________________________________________ 与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 7 09:08:40 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29158 for ; Wed, 7 May 2003 09:08:39 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h47DHd414842 for manet-archive@odin.ietf.org; Wed, 7 May 2003 09:17: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 h47DHc814839 for ; Wed, 7 May 2003 09:17:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29146 for ; Wed, 7 May 2003 09:08:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DOgX-000126-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 09:10:13 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DOgX-000123-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 09:10:13 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47D4q813088; Wed, 7 May 2003 09:04: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 h47Cx9812863 for ; Wed, 7 May 2003 08:59:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28435 for ; Wed, 7 May 2003 08:49:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DOOf-0000rw-00 for manet@ietf.org; Wed, 07 May 2003 08:51:45 -0400 Received: from ai.uwf.edu ([65.212.118.136]) by ietf-mx with esmtp (Exim 4.12) id 19DOOe-0000rt-00 for manet@ietf.org; Wed, 07 May 2003 08:51:44 -0400 Received: from [65.212.118.129] (account mcarvalho HELO oberon) by ai.uwf.edu (CommuniGate Pro SMTP 4.1b1) with ESMTP id 984633 for manet@ietf.org; Wed, 07 May 2003 07:53:54 -0500 Reply-To: From: "Marco Carvalho" To: Date: Wed, 7 May 2003 07:52:37 -0500 Organization: IHMC Message-ID: <000001c31497$895349a0$b864000a@oberon> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C3146D.A07D41A0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [manet] Network Simulator Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_01C3146D.A07D41A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Does anybody know what simulation package would be generally accepted as good for Ad hoc networks? I've heard that the ns2 simulator has an extension for wireless but I haven't tried it yet. I was curious to know if there is something better that I ought to try first. Many thanks, Marco ------=_NextPart_000_0001_01C3146D.A07D41A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Does anybody know what simulation package would be = generally accepted as good for Ad hoc networks?

I’ve heard that the ns2 simulator has an = extension for wireless but I haven’t tried it yet.

I was curious to know if there is something better = that I ought to try first.

 

Many thanks,

Marco

 

------=_NextPart_000_0001_01C3146D.A07D41A0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 7 10:22:44 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02788 for ; Wed, 7 May 2003 10:22:43 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h47EVi020684 for manet-archive@odin.ietf.org; Wed, 7 May 2003 10:31: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 h47EVi820678 for ; Wed, 7 May 2003 10:31:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02769 for ; Wed, 7 May 2003 10:22:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DPqE-0001an-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 10:24:18 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DPqD-0001ak-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 10:24:17 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47EGV819723; Wed, 7 May 2003 10:16: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 h47E9x819467 for ; Wed, 7 May 2003 10:09:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00977 for ; Wed, 7 May 2003 10:00:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DPVB-0001Qh-00 for manet@ietf.org; Wed, 07 May 2003 10:02:33 -0400 Received: from amber.crhc.uiuc.edu ([130.126.143.254]) by ietf-mx with esmtp (Exim 4.12) id 19DPVA-0001Qe-00 for manet@ietf.org; Wed, 07 May 2003 10:02:32 -0400 Received: from metric.crhc.uiuc.edu (metric.crhc.uiuc.edu [130.126.142.151]) by amber.crhc.uiuc.edu (8.12.9/8.12.9) with ESMTP id h47E2mFc004759; Wed, 7 May 2003 09:02:49 -0500 (CDT) Received: from localhost (mjmille2@localhost) by metric.crhc.uiuc.edu (8.11.6/8.11.6) with ESMTP id h47E2mJ11612; Wed, 7 May 2003 09:02:48 -0500 Date: Wed, 7 May 2003 09:02:47 -0500 (CDT) From: Matt Miller To: Carlos Miguel Calafate cc: gupta@cpsc.ucalgary.ca, Subject: Re: [manet] APIs for implementing routing protocols In-Reply-To: <3EB8BD95.40904@disca.upv.es> 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: , You should also check out the Ad-hoc Support Library by Vikas Kawadia, Yongguang Zhang and Binita Gupta. It's at: http://aslib.sourceforge.net/ -Matt On Wed, 7 May 2003, Carlos Miguel Calafate wrote: > Hi, > > I have implemented a simple library that allows the implementation of > routing protocols and also achieves inter-platform compatibility for > WinNT, Linux and WinCE. > > It's available at: > > http://pica-api.sourceforge.net/ > > For an example you can check the OLSR implementation at my home page: > > http://reptar.grc.upv.es/~calafate/ > > Best regards, > > Carlos > > > > > Abhinav Gupta wrote: > > I am looking for APIs for implementing routing in manets. Can someone > > provide me with the information on the APIs available for implementing > > the routing protocols? > > > > Thanks, > > Abhinav. > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 7 11:12:18 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05281 for ; Wed, 7 May 2003 11:12:18 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h47FLJJ25402 for manet-archive@odin.ietf.org; Wed, 7 May 2003 11:21: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 h47FLI825399 for ; Wed, 7 May 2003 11:21:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05247 for ; Wed, 7 May 2003 11:11:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DQcB-0002E9-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 11:13:51 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DQcA-0002E6-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 11:13:50 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47FAn824710; Wed, 7 May 2003 11:10: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 h47ExB823313 for ; Wed, 7 May 2003 10:59:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04654 for ; Wed, 7 May 2003 10:49:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DQGm-00024Z-00 for manet@ietf.org; Wed, 07 May 2003 10:51:44 -0400 Received: from vsmtp4.tin.it ([212.216.176.224] helo=smtp4.cp.tin.it) by ietf-mx with esmtp (Exim 4.12) id 19DQGl-00024K-00 for manet@ietf.org; Wed, 07 May 2003 10:51:43 -0400 Received: from oreste (80.116.31.188) by smtp4.cp.tin.it (6.7.016) id 3E8D751D00D5BEB1 for manet@ietf.org; Wed, 7 May 2003 16:52:05 +0200 Message-ID: <008c01c314a7$bab05c80$821f7450@oreste> From: "Eugenio Magistretti" To: References: <3EB85327.5090306@cpsc.ucalgary.ca> Subject: Re: [manet] APIs for implementing routing protocols Date: Wed, 7 May 2003 16:48:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.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 Abhinav, An API to develop on-demand protocols under Linux operating system is discussed in V. Kawadia, Y. Zhang, B. Gupta, "System Services for Implementing Ad-Hoc Routing Protocols" Best regards, Eugenio ----- Original Message ----- From: "Abhinav Gupta" To: Sent: Wednesday, May 07, 2003 2:28 AM Subject: [manet] APIs for implementing routing protocols > I am looking for APIs for implementing routing in manets. Can someone > provide me with the information on the APIs available for implementing > the routing protocols? > > Thanks, > Abhinav. > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 7 13:32:22 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09400 for ; Wed, 7 May 2003 13:32:22 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h47HfQ705517 for manet-archive@odin.ietf.org; Wed, 7 May 2003 13:41: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 h47HfQ805514 for ; Wed, 7 May 2003 13:41:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09363 for ; Wed, 7 May 2003 13:31:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DSnj-0003AI-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 13:33:56 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DSnj-0003AE-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 13:33:55 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47HQW803775; Wed, 7 May 2003 13:26:32 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47HHQ803380 for ; Wed, 7 May 2003 13:17:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08610 for ; Wed, 7 May 2003 13:07:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DSQW-000305-00 for manet@ietf.org; Wed, 07 May 2003 13:09:56 -0400 Received: from pollux.cse.buffalo.edu ([128.205.35.2] ident=daemon) by ietf-mx with esmtp (Exim 4.12) id 19DSQV-000301-00 for manet@ietf.org; Wed, 07 May 2003 13:09:55 -0400 Received: (from ab42@localhost) by pollux.cse.buffalo.edu (8.11.6+Sun/8.10.1) id h47HAmW20162; Wed, 7 May 2003 13:10:48 -0400 (EDT) Date: Wed, 7 May 2003 13:10:48 -0400 (EDT) From: Aruna Balasubramanian To: In-Reply-To: <20030507160003.28400.34511.Mailman@www1.ietf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Simulation tools Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 have heard that GlomoSim is ideal for simulating ad hoc network. It has a wireless component and its easy to use But it depends on what you are shooting for, if you want simulation for publication work, I think NS 2 is preferred I want to develop a simulation model for an ad hoc security protocol that i have developed. Has anyone used NS2 for simulating security models for wireless Thanks Aruna _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 7 14:11:52 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10776 for ; Wed, 7 May 2003 14:11:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h47IKve08837 for manet-archive@odin.ietf.org; Wed, 7 May 2003 14:20: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 h47IKu808830 for ; Wed, 7 May 2003 14:20:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10769 for ; Wed, 7 May 2003 14:11:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DTPx-0003T8-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 14:13:25 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DTPx-0003T5-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 14:13:25 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47I7T807622; Wed, 7 May 2003 14:07: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 h47I2S806854 for ; Wed, 7 May 2003 14:02:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10104 for ; Wed, 7 May 2003 13:52:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DT85-0003JV-00 for manet@ietf.org; Wed, 07 May 2003 13:54:57 -0400 Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu) by ietf-mx with esmtp (Exim 4.12) id 19DT85-0003JS-00 for manet@ietf.org; Wed, 07 May 2003 13:54:57 -0400 Received: by mail.eecis.udel.edu (Postfix, from userid 62) id A2E01328F8; Wed, 7 May 2003 13:55:50 -0400 (EDT) Received: from buckwheat.cis.udel.edu (buckwheat.cis.udel.edu [128.4.131.43]) by mail.eecis.udel.edu (Postfix) with ESMTP id E3DB9328E7; Wed, 7 May 2003 13:55:49 -0400 (EDT) Date: Wed, 7 May 2003 13:55:49 -0400 (EDT) From: Sonny Rajagopalan X-X-Sender: To: Marco Carvalho Cc: Subject: Re: [manet] Network Simulator In-Reply-To: <000001c31497$895349a0$b864000a@oberon> Message-ID: X-Spam-Status: No, hits=-5.0 required=6.0 tests=DEPT_RCVD,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01,USER_AGENT_PINE version=2.43 X-Sanitizer: This message has been sanitized! X-Sanitizer-URL: http://mailtools.anomy.net/ X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset="US-ASCII" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , I use QualNet and it is very good. I see QualNet as a simulator similar to GloMoSim, only substantially faster with more tools (QualNet has a very sophisticated GUI tool for demo'ing your protocols etc.). My 2 cents... Cheers, Sonny. ---- >From the desk of Sonny Rajagopalan @ http://www.cis.udel.edu/~rajagopa ---- On Wed, 7 May 2003, Marco Carvalho wrote: > Does anybody know what simulation package would be generally accepted as > good for Ad hoc networks? > I've heard that the ns2 simulator has an extension for wireless but I > haven't tried it yet. > I was curious to know if there is something better that I ought to try > first. > > Many thanks, > Marco > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 7 14:16:23 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10947 for ; Wed, 7 May 2003 14:16:23 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h47IPSS09281 for manet-archive@odin.ietf.org; Wed, 7 May 2003 14:25: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 h47IPS809278 for ; Wed, 7 May 2003 14:25:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10926 for ; Wed, 7 May 2003 14:15:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DTUK-0003W1-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 14:17:57 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DTUK-0003Vw-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 14:17:56 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47IFF808319; Wed, 7 May 2003 14:15: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 h47I8M807990 for ; Wed, 7 May 2003 14:08:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10260 for ; Wed, 7 May 2003 13:58:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DTDn-0003Lm-00 for manet@ietf.org; Wed, 07 May 2003 14:00:51 -0400 Received: from ai.uwf.edu ([65.212.118.136]) by ietf-mx with esmtp (Exim 4.12) id 19DTDm-0003Lf-00 for manet@ietf.org; Wed, 07 May 2003 14:00:50 -0400 Received: from [65.212.118.129] (account mcarvalho HELO oberon) by ai.uwf.edu (CommuniGate Pro SMTP 4.1b1) with ESMTP id 986225 for manet@ietf.org; Wed, 07 May 2003 13:03:00 -0500 Reply-To: From: "Marco Carvalho" To: Subject: RE: [manet] Simulation tools Date: Wed, 7 May 2003 13:01:42 -0500 Organization: IHMC Message-ID: <002e01c314c2$b71fc770$b864000a@oberon> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-reply-to: Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Thank you for all the suggestions, In fact, Like Aruna, I would also like to work on some security models for ad hoc and that's why I'm looking for the simulator that would work best for this specific task. I don't really need something very complicated since I wouldn't have much time to learn the simulator in detail. Thanks again, Marco > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of > Aruna Balasubramanian > Sent: Wednesday, May 07, 2003 12:11 PM > To: manet@ietf.org > Subject: [manet] Simulation tools > > I have heard that GlomoSim is ideal for simulating ad hoc network. > It has a wireless component and its easy to use > But it depends on what you are shooting for, if you want simulation for > publication work, I think NS 2 is preferred > I want to develop a simulation model for an ad hoc security protocol that > i have developed. Has anyone used NS2 for simulating security models for > wireless > > Thanks > Aruna > > _______________________________________________ > 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 May 7 14:32:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11723 for ; Wed, 7 May 2003 14:32:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h47IfcV11581 for manet-archive@odin.ietf.org; Wed, 7 May 2003 14:41: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 h47Ifc811578 for ; Wed, 7 May 2003 14:41:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11714 for ; Wed, 7 May 2003 14:32:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DTjy-0003hL-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 14:34:06 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DTjy-0003hI-00 for manet-web-archive@ietf.org; Wed, 07 May 2003 14:34:06 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47IVM809665; Wed, 7 May 2003 14:31: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 h47IMQ808923 for ; Wed, 7 May 2003 14:22:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10826 for ; Wed, 7 May 2003 14:12:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DTRP-0003Tr-00 for manet@ietf.org; Wed, 07 May 2003 14:14:55 -0400 Received: from ai.uwf.edu ([65.212.118.136]) by ietf-mx with esmtp (Exim 4.12) id 19DTRO-0003To-00 for manet@ietf.org; Wed, 07 May 2003 14:14:54 -0400 Received: from [65.212.118.129] (account mcarvalho HELO oberon) by ai.uwf.edu (CommuniGate Pro SMTP 4.1b1) with ESMTP id 986311 for manet@ietf.org; Wed, 07 May 2003 13:17:05 -0500 Reply-To: From: "Marco Carvalho" To: Date: Wed, 7 May 2003 13:15:47 -0500 Organization: IHMC Message-ID: <002f01c314c4$aec02780$b864000a@oberon> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0030_01C3149A.C5EA1F80" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [manet] previous posting Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_0030_01C3149A.C5EA1F80 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, This is in regards to a previous posting (I missed it for a few days) but I would like to check on something in regards to Philippe's answer: As far as I know (somebody please correct me if I'm wrong) the reactive protocols take no advantage of distance-vector or link-state information during the RREQ/RREP phase. The point of this stage would actually be to discover the routes (on demand). So RREQ packets are either flooded to all nodes (or to nodes in some limited region, like in the directed diffusion case). Does that sound reasonable? I was wondering if maybe I have a misconception on reactive protocols. Thanks, Marco --------------- previous posting ------------------ Yes OLSR uses Dijkstra, but DSDV uses Belman-Ford. It depends whether the proactive protocol is link state or not. Philippe ----- Original Message ----- From: jian wu To: Sent: Wednesday, April 30, 2003 5:17 PM Subject: [manet] routing > > Dear all > > I am a student currently working on ad hoc routing. I have a question here: > I know that in reactive protocols such as DSR or AODV, source nodes send out > RREQ to discover routes and expect RREP back. I wonder whether there is any > route computation (e.g. using Dijkstra's or Bellman Ford algorithm) involved > in this process? And how about proactive protocols such as OLSR, is Dijkstra > used there when computing the routing table? > > Many thanks, Jian Wu > > > ------=_NextPart_000_0030_01C3149A.C5EA1F80 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 
Hi, 
This is in regards =
to a previous posting (I missed it for a few days) but I would like to =
check on something in regards to Philippe’s =
answer:
 
As far as =
I know (somebody please correct me if I’m wrong) the reactive =
protocols take no advantage of distance-vector or link-state information =
during the RREQ/RREP phase. The point of this stage would actually be to =
discover the routes (on demand). So RREQ packets are either flooded to =
all nodes (or to nodes in some limited region, like in the directed =
diffusion case).


Does that sound reasonable? 
I was wondering if =
maybe I have a misconception on reactive =
protocols.
Thanks,
Marco
 =

 
--------------- previous posting =
------------------
 
Yes OLSR =
uses Dijkstra, but DSDV uses Belman-Ford. It depends whether =
the
proactive protocol is =
link state or not.
 
Philippe
----- =
Original Message -----
From: =
jian wu =
<jianwu53@hotmail.com>
To: =
<manet@ietf.org>
Sent: =
Wednesday, April 30, =
2003 5:17 PM
Subject: [manet] =
routing
 
 
>
> Dear =
all
>
> I am =
a student currently working on ad hoc routing. I have a =
question
here:
> I = know that in reactive protocols such as DSR or AODV, source nodes = send
out
=
> RREQ =
to discover routes and expect RREP back. I wonder whether there =
is
any
=
> =
route computation (e.g. using Dijkstra's or Bellman Ford =
algorithm)
involved
= 
> =
in this process? And how about proactive protocols =
such as OLSR, is
Dijkstra
= 
> used =
there when computing the routing =
table?
>
> Many =
thanks, Jian Wu
>
>
>

 

------=_NextPart_000_0030_01C3149A.C5EA1F80-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu May 8 12:14:52 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28518 for ; Thu, 8 May 2003 12:14:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h48GONs26559 for manet-archive@odin.ietf.org; Thu, 8 May 2003 12: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 h48GON826556 for ; Thu, 8 May 2003 12:24:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28486 for ; Thu, 8 May 2003 12:14:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Do4F-0003wL-00 for manet-web-archive@ietf.org; Thu, 08 May 2003 12:16:23 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Do4F-0003wH-00 for manet-web-archive@ietf.org; Thu, 08 May 2003 12:16:23 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h48GCv825714; Thu, 8 May 2003 12:12: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 h48G4S824281 for ; Thu, 8 May 2003 12:04:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27831 for ; Thu, 8 May 2003 11:54:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Dnkz-0003mJ-00 for manet@ietf.org; Thu, 08 May 2003 11:56:29 -0400 Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112]) by ietf-mx with esmtp (Exim 4.12) id 19Dnkz-0003lv-00 for manet@ietf.org; Thu, 08 May 2003 11:56:29 -0400 Received: from zrc2c011.us.nortel.com (zrc2c011.us.nortel.com [47.103.120.51]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h48FukV10480 for ; Thu, 8 May 2003 10:56:47 -0500 (CDT) Received: by zrc2c011.us.nortel.com with Internet Mail Service (5.5.2653.19) id ; Thu, 8 May 2003 10:56:47 -0500 Message-ID: <933FADF5E673D411B8A30002A5608A0E53AF76@zrc2c012.us.nortel.com> From: "William Lee" To: "'manet@ietf.org'" Date: Thu, 8 May 2003 10:56:44 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/related; boundary="----_=_NextPart_000_01C3157A.6C11B3DE"; type="multipart/alternative" Subject: [manet] OSPF 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: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C3157A.6C11B3DE Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3157A.6C11B3DE" ------_=_NextPart_001_01C3157A.6C11B3DE Content-Type: text/plain Are their any disadvantages of using OSPF in a MANET, particularly if the network is not very dynamic? How does the performance of OSPF change as node mobility increases? How does it change if only the links are transient, but mobility is minimal? William Lee ------_=_NextPart_001_01C3157A.6C11B3DE Content-Type: text/html Content-Transfer-Encoding: quoted-printable

Are their any disadvantages of using OSPF in a = MANET, particularly if the network is not very dynamic?  How does the performance of = OSPF change as node mobility increases? How does it change if only the links are = transient, but mobility is minimal?

 

William = Lee

  =

------_=_NextPart_001_01C3157A.6C11B3DE-- ------_=_NextPart_000_01C3157A.6C11B3DE Content-Type: image/gif; name="image001.gif" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="image001.gif" Content-ID: Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 R0lGODlh/wNdAPf/AP///4SEhIyMjJSUlJycnKWlpa2trbW1tb29vcbGxs7OztbW1t7e3ufn5+/v 7/f3987GxtbOzt7W1r21ta2lpbWtrca9vZyUlKWcnMa9td7WztbOxr21rc7Gvefezt7Wxt7Wve/v 5/f37///987OxtbWzt7e1ufn3r29ta2tpbW1rcbGvZSUjJyclKWlnIyMhN7ezufn1u/v3tbWxr29 rcbGtc7OvbW1pf//562tnPf33qWllO/v1t7exufnztbWvc7Otb29pcbGrf//3vf31u/vzufnxt7e vdbWtc7Orf//1u/vxufnvff/zvf/1u/3zufvxt7nvff/3u/31ufvztbevc7WtcbOrd7nxr3Gpff/ 5+/33ufv1tbexs7WvcbOtbW9pa21nO//zt7vvdbntd7nzr3Gre//1uf3ztbnvd7vxufv3sbOvaWt nPf/79bezs7WxrW9ra21pe//3uf31s7evcbWtd7vztbnxr3Ord7n1r3Gtef33sbWvd7v1s7extbn zr3OtbXGrefv5+/378bOxs7Wztbe1t7n3rW9taWtpa21rb3GvYyUjJSclJylnISMhM7ezsbWxrXG tb3OvcbOzq21tZScnMbGzq2lrcDAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAEAAJoALAAAAAD/A10A QAj/AGmYMUND4BcgVuxc2cMwkJk9NFAgQFCghQ0fT6BQUYMFS5cub94kIEASwYIGmlKqXMmypcuX MGPKnEmzps2bOHPq3Mmzp8+fQIMKHUq0qNGjSJMqXcq0qdOnUKNKVUowzp44cWhgRaGoxQABYAMI 6NEDCZQoUWCs4cKjTBc4IBe5oNGlRxm4f+rAgRNpBpxDChY4eDC1sOHDiBMrXsy4sePHkCNLnky5 MlA5KGhARKGCBgEBYr1EwVKlx48jU7z48NLFRxcsM/T4wFIGBgy/Nmb8gFGmDAkXAw4oQGm5uPHj yJMrX868ufPn0KPbHGgGjBw5i1Sk2H5ATxnTXqr8/wBZhocWPTO8eJnh9sePHh/hrN/b5UsCBIOl 69/Pv7///wAGKOCAAgbwQgCY7FEDG/IF0kcNM9jWQxUiLLhCCSSQsAJooAUQACQE6AEDFx/N0IV7 cCSQAAP5EejiizDGKOOMNNZo42Qx+OADDjx44AEMJpjAAAMw6HECCV/UEMYNYIBhxhVmCAFRIioo UgABGKigggEUuFDAlwYskkAhCUTAAAkLEHbjmmy26eabcMYpZ2VTOEHFFDwUceIRpVUBRRV1ePFH aV3M8EUcTtbwBSM1oOAoCgeg8IUQVwiR5ENm1KCgAg+oOeenoIYq6qikllqjiD3wBoNdM7AxA3sx xP9QYkh7laAAko5qWsMKbKywhyAoMIICAV8NQNIBCAw3WKemNuvss9BGK+20RcH2BRWj+TVDHyEV kkIOZnzhhbgM9WpGIo8yMmVWKiRCwCVgJsuAp9TWa++9+OarL5twwIAFWVV0UQcbLuzgQg5MslFC CSbEICIMJXhhw2444DDHEE44MQUVHPtwh3d6rKGHCQ0Qt+/JKKes8sosJ1aAlSkkUogJM5BAQxhx uEBsIwas4N6/VJTRURVOSEEFGlPcAcgfMOAByBtdlAGIW288fYiQiNDb8tZcd+311y0TkAICAJgQ RpJJ1lBDhnr8UIIBBHg1QAF74GFEFUVA0UUVVeD/UaghZBYwwOAEfFkCHCWUAXVIJWgN9uOQRy75 5DYKYoYdA+Ux0B5CeGHHVXFomYgLixzASJB2lcFFRz/4JUEij8hhRm4wFDqDCS1SrvvuvPfue3NV gVGQlma40KEAA0x4xA91qJEGFGf9O4Wsb/haA1w9eARXJCG9lWEhCiBgrAEJnOT47+inr/767O8k Rw4uPJKCClelQGwLH6m3txFWeEEFD1ywjV9i4C+AvccvcIGDJBjxCAM04Hzti6AEJ0hB9mVKCANh AxCS8AWGfMEG3+kCHjxSBSqQpVAksAFcbMAF77AmVR+BQUhIcB8HVPCGOMyhDsHGIQscAF4pMAAC /xhhKCDIEAby8QsCUsCCFrDAESwYXCPAQkUBEGAFNHuDbeBQCAsIBoI7DKMYx0hGOXXkCdgCGhX4 9hG+1S5IXajUF7IwEAyaISsoWAENhAAEzqnNUSswX6cckLsyGvKQiExkgMRDhSIUwQh1mQEexgOf LnxgBn+Awx9YUwJDfMEOXxjIFfpghzyAUlFf2OShQreI+c0vEchKVgMKqcha2vKWuGRMXbLHt4Dp pmY2YEQFqOgIF7SBSQLZw0MiwoYvCAIrcWjUHlQApgMk4AS0zKU2t8nNbirFD1zAwxv00AUghWQF o5PDDaxghS984Qqh3EMiSGC6A1hCiGdaAQr2EP++Axjgn8gaDrO8SdCCGvSgNfGSAdgwzpqxYQAu kIMNCACcFHwhkl74gQ8C9gMcnEEKU9jCHbBABzrcgQ5U8IFGylCHGcwzTQiNqUxnys0CbMcAKagA ChBXAkWogAN5hMMbhNYRKnjkB2UoIRpGAwWP0KYOAesCa0zEBUBMrXvgmxdNt8rVrt6QBnQUSJSS 1K9LKeghjtJOAeCABY00FT548MEM3kACYxHAml/0ql73ytcICsKdX2gmG9QT2A4yBAU1SMQeUJCI FUCgBFPwwQ+40ANazcBWBnBBChiBoVkOtK+gDa1owSYIOuaBBpZTZiLk8IgWtIAAHhJLARLgIx3/ VKEMGPFBql4FhxTMJRAqRGBIJIGIB4JxtMhNrnJNJbys0CAIBYkDCtrQAg8J4BFA4NN7mNARI/SA DlzgwhuE6q0atC6jvNWWfAzBXgjcBwEMeOBy50vf+rYpK2YIQlb2ayCw2IAMfAtPFZZQBSz4gA49 8AIB9VADMwjKL1Z9QwtrI9XwAdSaCVBAfLNp3w57+MP6cYELblCQKX3mBQIwQhT49gMrPGEGNlij D47Qg9hwAbcU/kgI1WMDwuUVxEAOspClQxA5KCIFbXDUy7bDHthITDx22cIUZEgCOACCsv+qwqtM VCiQsGEiHB6ymMdM5sdY6p0D0QoNtEQDt1RB/z1DM7BRocCGH0gMPlgABBu6AIUY3AFqQv0yfo5b 5kIb+tBLIbEZgLCCGgAhXIP9AhxExBqPRA2Jb5jBBlYglgOUkwtCvQMcTACxINmghoRGtKpXzWqd WJciyHuEChjBCInZYM8nklgKSYACDoXF1wNQgYmqpsW90PAkrU62spdNEwxcaQEmOEABMnGAcb3z CmmY2cJKsAckywFRYBAEB+LQSmIZ60skKYABbKAHPZBgBvKyIbPnTe9WP6GEVOgCFXRTmjLEykha nIEQxJoFStVAMwdQwSL++QMbQAQMN0AWhhWgAEwkwBAa/my9N85xIWtECUNoAhurcAeOfSR7vf95 VSECC4S0EaQqujIDEoAghIIPfLEokG/Hd85zIHvkTj6wjaU/kOAZJBgOfikB0+BAgj6YwQpmsNyu 9oCACdSgD55zp68YIt3FMkLDs+y52McuWo1y4Q5luINU1VM1cgo1EnAJyWXlw5AVrIARvMJ7HRvM WIXj9J/qPoA1A2Ncshv+8DP9s9TKwKcud+EPIXGLekhQCEaMqRIkUIAh2KApNjDk8wpaLCwDfxJ5 I/70qI8pwOCTnkjOwBCUWAELGjGAFqRAeJr6vCCSyRAaJCkOES/clwIa5tQb//i2xAJc8KCHqs3n VSmQnR0896Cz3tFRCEhEArJSAzwe4ALCF2L/xpFP/vLbUnUnF1EJFpCAR+wgB3IQ3uxMAO2FIf2S PcgYxpxAhClsrDwt9AbsF2/mV4AGGEYDYAA/4AclADElUAiP4AJhYAYKE15Cs0ZaxhpSZSdPMAUd 2IEbgwYlhwVosAIGUADmc4AquIIS9CWLsAIkkGlM1wIjpjMCcCAFwBtRo1sbVQVS8AQdKIJeQIL/ Qhsg8RHjVAKH4Fks2IROuDteogg4lQIoYAgLwFgpkB0qgAAMo29thQXvwRocgwVjGBISlj35g4Th 1W4mABgs8oRwGIdc8yWZsAIgsBpIYAOaYnclEAE+4F1ogAQ1RhpHwCcm5zfjZWwL4xchAQNL/9MH egEIIGEI2JRqcniJmNgsVmADV6ApdWQFlZIFJAADOLclKVAAj1AANeADbjEHWJAGXcAGmwQX3mJX BWAJE7EA8fUAItCLg5SJwBiM0bIH1edO0+cFfeBObKAZXCd6CZAIXrAFFzgbvIUhJ2gAKLBhliiM 3NiNoeJ7fRAIg/UgeaAeTsd1WKECB5csvSE0d3AHeIBAJkACp/iC41UCs2R63riP/AgqvvcFDmFH HUQl2bEIcfMZtncCJ6ADWOBdZ8AF+RYShpBZ0WQHJWIiSjgI+tiPHNmRNTIQcWAGWQBNBOECjkAA jjAAYhEAB/ADVXBv+cYD/pdvhaIHqwUG4v+iZXBQB5u0HoZgA0NiMh45lEQZIDQABnEgCBAROhmA AinQAh3iISpwBCtmBIXoB2UAXgTEGm8QBzmwB3BRO2mAdLXjFyRQAhBQCbqoc0XZlm7pHOkYXdGl Ap+xknvDN1bQVGPQVFTABVsgXkiEAnGQG5bGF+P1B2+hSYWwmAnwTxpWfG8ZmZLZGGqGlFlwAyoQ B8ejCFbQS0eQBkRwBG1FBTDgBWsAJIwCIW8BCH7QfLUBAy1FeSNROP8kL4U3mbiZm4vRGQeHR3Fg AB2SAj2wYkhQBUBgBKShb1NQY28QJFVgA+rhBXUAEjPgA33pPTglHLoYX561jbr5neBpFKT/YxVa gRWwBRZVQGMuOYRU4AVl4AUAgwUmsAZBwxu9oWPxYQMHYEUr4p3h+Z8AWhSK0AaalQiJUBDAiTxY sGLrUWDPyTEpVQav8prZkx4mgkA2sAIHQAAO5J8B+qEgyhPWkQME4FPZpwiPQBIf8RF2hgUZ5QM8 4BqHA0Kz0QWAMCGF8gNwUQIzwAgFcABsGaJCOqRAASVemQNtEAcHcIpaMlelmVExVB5bEBIM8gau gaN+wRqZFGgJcAAbSaRgGqY2oR4HB5KCGTpxsCoJZgOrR4ZBYwNdAJ0BQxZwITRl8AcwJpv4IaZ8 2qcyIRBCwE4NRhARQQM2QGo/QxZYoAZU/3BJ5pVCrVEb+qM4taEHh0BDe+qnmrqpmnBmD1ED8GQH irIHo+hmM1YFRiChh8MgkcIG7Rgh9qmEh7AAGpIAX8qpuCqkA3BkGmJeNjApA1FZSSU0KyAxhrAX hZAIKskhB0ACXMAHMaAbLFoFKYIAYZer2CqkHUIRikADDBIIimIDJfAGWAAEbsBjulYAK8khYsEG JFAGa4RUWCCAG1A+QZqt+AqeK4kAmWBF6pYAdmcFQAA1t5FENLQIVYRiVSQWKsAgXDCuSJehlaBV +Vqxukk4GlAClvAlKnBrBwEEl6UHx1ozBNoG8YcdcpACVvIIg2NXhYMChZA4GFIIJgGZFv97s/0Y S/SXeYWwAoYiBIFqBaNGV4wAf0sSkgMnmAv3FbR5JSRBAAhQCM1pCCRgEkKJs1jbkUtgBEYQo2X5 BogQKwrZADPwcGAQBFlAA5UiEGu2JQXgAiqAAhkABr71TwaALAlgAV9nAlZ4q1n7t8I4nBmRPSnl ogHzLz3gMOjxA1dQKQwRJXiEAhxwAO1UppkBKSuSjyVTMh4KuJ6rgnsJhFHAJ1HAAyR0oVpUAmvA ozVgB0IAXVFCEIsFEZ+qKNLkKBSrCZ37ubxbgGrwBBnzBKTRS3hgVL1UYJeFJFcArgvyR4+yT51j KZmSZo2yAlfbu9grhzfWSGMIG5U0V+3/cVlewKPc5itfIFY4NwH71E6GZVgRARGBxITZO79N+B1l MAXfMa+Ztirp8QaQ9wc6+gYL8wZeUI4PsQcdZHeMYAGB0kziiFpnylgSUQiCRL8WXIAm0jH7ViJw waJS1S+F8ge24gULwgZ5xAZ6CEqBkAcfixWLcAPboQiKgC4TkXnye8E4nHowQEA7rCpJVE5loAd7 ATUfUQjHagihtwe0tja0hgKeFwctSzg/miwnkY8al8NYbHj5pqgrKlUwZlS9gUSJuRfHSgKToMR7 UAhs4HmgByk6c24ZxiK7m8V0zGymUYQlkqMTMx6LgiwroMbvZgg1EwjlYgaZIV0FkUfS/6Zu8HWv dfzIZHci32siXiBUXmB3XyEALBBRWKFYg8qMDAEsJaYCKRovmGCzkJzK9VYGeMAaMICneFrJXQBL tRdRz0QDffCrDJF7+6QriXADMDw3w1c+fqvKxlxvT2oXfvAWeHoiJKBO7zQufaBMipKUNIAAKGAB NHBwmaECBzAAF/AlFCAvc3zM5kxmWnSfUdN8bwA4BwMGntNyVyCqBEEljJAIFYCLJhAHjJCZFKFu tUnM5XzOBA1kPIAeb5CxJiDAlGdMwMxOQFAp4NorClAIEsyFDRACbSgkJmArCBBLmTvQBT3S9aVv 7xkwW/SUIqZOA3E7J5BFJVBj7zEEOP+QMWIgBmhkVHggNXrwNLYSXyQd1KrmAgwiiT69AjSYAlnB bjJwY6vDouPxA2iUMVTNf0eDBnSgEUFDArso1F5daIVTCOiBRDMYUV8AAzLAilhAYzNQB3YmHl4w BGhwBnfwBGhw12iwEVAwQncwLATQn18d2GKmbiqgAA0YMWxAgzcgB58BFgZwQj9QhHa2f3QwBVzw B/CKY1jgN1MDErZSzIId2soFJgZgAUJFedF3A8TCAqCBAnszIVSgYnwCvEiTNG4hNH3Tjj7dnPQH 1KL92/PlJTe1AoeAIQShCPFDABTAWYWCqlAASeLhBGj0BO94F4DgiP6rY+oMAycwq4T+BNzgPVpf sh0quwKGTY8GkJlx8G61MRsmpF0vaVSLqgYjpDgyxMGYTQdl4AeA0IZWeL3hHeBbZVPeDCEXqiGe pzA9UAQdAQV/SBqVxDF4MOGFcmsfDBJ/IImJOANPEwllYIVXLOAijlCFY1H/Mim70igokEImFAVI MAOOsAJH4AUjVEJrrWVlAHdsgHELsAIqwi0fTB+pAgOHANojfuTb5ChxQAhmsAgDYbukinSQcoIp Wjg1cJdo0BHhMYtcZAAtW+LkExgOsAaHEBKIgORoflBPMnCUsmju5AWGgAID90eM4E9v2wFadAer 0xHx0QWFADeFgywbNgJpXugzFRAAOw== ------_=_NextPart_000_01C3157A.6C11B3DE-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu May 8 12:47:26 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29724 for ; Thu, 8 May 2003 12:47:26 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h48Guvs29899 for manet-archive@odin.ietf.org; Thu, 8 May 2003 12:56: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 h48Guv829896 for ; Thu, 8 May 2003 12:56:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29692 for ; Thu, 8 May 2003 12:46:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DoZl-0004E9-00 for manet-web-archive@ietf.org; Thu, 08 May 2003 12:48:57 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DoZl-0004E6-00 for manet-web-archive@ietf.org; Thu, 08 May 2003 12:48:57 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h48GkA829067; Thu, 8 May 2003 12:46: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 h48Gfs828769 for ; Thu, 8 May 2003 12:41:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29091 for ; Thu, 8 May 2003 12:31:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DoLC-00044R-00 for manet@ietf.org; Thu, 08 May 2003 12:33:54 -0400 Received: from 66-152-29-4.ded.btitelecom.net ([66.152.29.4] helo=mail.scires.com) by ietf-mx with esmtp (Exim 4.12) id 19DoLB-00043v-00 for manet@ietf.org; Thu, 08 May 2003 12:33:54 -0400 Received: from SRCATL-MTA by mail.scires.com with Novell_GroupWise; Thu, 08 May 2003 12:35:10 -0400 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta Date: Thu, 08 May 2003 12:34:49 -0400 From: "Andreas Yankopolus" To: , Subject: Re: [manet] OSPF in MANETs 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 > Are their any disadvantages of using OSPF in a MANET, > particularly if the network is not very dynamic? If the network is not very dynamic, is it really a MANET :-) > How does the performance of OSPF change as node > mobility increases? How does it change if only the links > are transient, but mobility is minimal? Link flapping causes OSPF to re-flood link state advertisement packets. The Army used OSPF and BGP4 during a Force XXI advanced warfighting experiment (AWE) in 1997. The network bogged down due to the large number of OSPF updates, many of which resulted from unstable links. Cheers, Andreas _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu May 8 12:49:55 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29849 for ; Thu, 8 May 2003 12:49:55 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h48GxR330189 for manet-archive@odin.ietf.org; Thu, 8 May 2003 12: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 h48GxQ830186 for ; Thu, 8 May 2003 12:59:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29826 for ; Thu, 8 May 2003 12:49:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DocB-0004Ft-00 for manet-web-archive@ietf.org; Thu, 08 May 2003 12:51:27 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DocA-0004Fq-00 for manet-web-archive@ietf.org; Thu, 08 May 2003 12:51:26 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h48GmU829211; Thu, 8 May 2003 12:48: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 h48Gfs828773 for ; Thu, 8 May 2003 12:41:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29094 for ; Thu, 8 May 2003 12:31:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DoLC-00044U-00 for manet@ietf.org; Thu, 08 May 2003 12:33:54 -0400 Received: from 66-152-29-4.ded.btitelecom.net ([66.152.29.4] helo=mail.scires.com) by ietf-mx with esmtp (Exim 4.12) id 19DoLB-00043u-00 for manet@ietf.org; Thu, 08 May 2003 12:33:54 -0400 Received: from SRCATL-MTA by mail.scires.com with Novell_GroupWise; Thu, 08 May 2003 12:35:10 -0400 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta Date: Thu, 08 May 2003 12:34:33 -0400 From: "Pete Sholander" To: , Subject: Re: [manet] OSPF in MANETs 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 William, This (IMHO) is a good reference on protocol scaling ... C. Santivanez, "Asymptotic Behavior of Mobile Ad hoc Routing Protocols with respect to Traffic, Mobility and Size", Northeastern University CDSP Tech. Report TR-CDSP-00-52, Oct. 2000. (I think he also published some refereed papers on this topic in the past few years, while at BBN. Try google.com) The short answer to your questions though is that the O(N) overhead roughly scales as (mu)*N**2, where N is the number of nodes and mu is the "link breakage rate", which may be caused by either mobility or RF effects. So, OSPF may work fine in some MANETs depending on the relative ratios of number of nodes, link breakage rates, and the wireless links speeds. Unmodified OSPFv1 and OSPFv2 are known to work poorly in typical military networks. (I'm not aware of any real-world experimental results for the newer OSPFv3. Other posters may ...) Hope this helps! --Pete Sholander >>> "William Lee" 05/08/03 11:56AM >>> Are their any disadvantages of using OSPF in a MANET, particularly if the network is not very dynamic? How does the performance of OSPF change as node mobility increases? How does it change if only the links are transient, but mobility is minimal? William Lee _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu May 8 18:08:22 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13745 for ; Thu, 8 May 2003 18:08:22 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h48MI0F25480 for manet-archive@odin.ietf.org; Thu, 8 May 2003 18:18: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 h48MHx825477 for ; Thu, 8 May 2003 18:17:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13679 for ; Thu, 8 May 2003 18:07:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DtaL-00070r-00 for manet-web-archive@ietf.org; Thu, 08 May 2003 18:09:53 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19DtaK-00070o-00 for manet-web-archive@ietf.org; Thu, 08 May 2003 18:09:52 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h48M5k823867; Thu, 8 May 2003 18: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 h48M1L823718 for ; Thu, 8 May 2003 18:01:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12716 for ; Thu, 8 May 2003 17:51:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DtKE-0006sb-00 for manet@ietf.org; Thu, 08 May 2003 17:53:14 -0400 Received: from aragorn.bbn.com ([128.33.0.62]) by ietf-mx with esmtp (Exim 4.12) id 19DtKE-0006sN-00 for manet@ietf.org; Thu, 08 May 2003 17:53:14 -0400 Received: from bbn.com (raisin.bbn.com [128.89.80.35]) by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id h48Lrd5v000806; Thu, 8 May 2003 17:53:39 -0400 (EDT) Message-ID: <3EBAD297.22462A5F@bbn.com> Date: Thu, 08 May 2003 17:56:39 -0400 From: Cesar Santivanez Organization: BBN Technologies (a Verizon's unit) X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 CC: manet@ietf.org, williaml@nortelnetworks.com Subject: Re: [manet] OSPF in MANETs References: Content-Type: multipart/alternative; boundary="------------461AD002E8F2FBB90264E156" X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------461AD002E8F2FBB90264E156 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit William, The `reader-friendly', peer-reviewed version of that tech report was published on Infocom 2002: C. Santivanez, Bruce McDonald, Ioannis Stavrakakis, Ram Ramanathan. ``On the Scalability of Ad Hoc Routing Protocols,'' in {\em Proceedings of IEEE Infocom'2002}, pp. 1688-1697, New York, USA, June 2002. Also, you may be interested in a modification to OSPF's link state mechanism that although simply it greatly increases the routing protocol scalability properties: C. Santivanez, S. Ramanathan, and I. Stavrakakis,``Making Link State Routing Scale for Ad Hoc Networks'', In {\em Proceedings of MobiHOC'2001}, Long Beach, CA, Oct. 2001. Hope this helps Cesar Pete Sholander wrote: > William, > > This (IMHO) is a good reference on protocol scaling ... > > C. Santivanez, "Asymptotic Behavior of Mobile Ad hoc Routing Protocols > with respect to Traffic, Mobility and Size", Northeastern University > CDSP Tech. Report TR-CDSP-00-52, Oct. 2000. > > (I think he also published some refereed papers on this topic in the > past few years, while at BBN. Try google.com) > > The short answer to your questions though is that the O(N) overhead > roughly scales as (mu)*N**2, where N is the number of nodes and mu is > the "link breakage rate", which may be caused by either mobility or RF > effects. > > So, OSPF may work fine in some MANETs depending on the relative ratios > of number of nodes, link breakage rates, and the wireless links speeds. > Unmodified OSPFv1 and OSPFv2 are known to work poorly in typical > military networks. (I'm not aware of any real-world experimental > results for the newer OSPFv3. Other posters may ...) > > Hope this helps! > > --Pete Sholander > > >>> "William Lee" 05/08/03 11:56AM >>> > > Are their any disadvantages of using OSPF in a MANET, particularly if > the > network is not very dynamic? How does the performance of OSPF change > as > node mobility increases? How does it change if only the links are > transient, > but mobility is minimal? > > William Lee > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- Cesar Santivanez, Ph.D. Network Scientist Internetwork Research BBN Technologies (A verizon unit) --------------461AD002E8F2FBB90264E156 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit William,

The `reader-friendly', peer-reviewed version of that tech report
was published on Infocom 2002:

C. Santivanez, Bruce McDonald, Ioannis Stavrakakis, Ram Ramanathan.
``On the Scalability of Ad Hoc Routing Protocols,'' in {\em Proceedings of
IEEE Infocom'2002}, pp. 1688-1697, New York, USA, June 2002.

Also, you may be interested in a modification to OSPF's link state mechanism
that although simply it greatly increases the routing protocol scalability
properties:

C. Santivanez, S. Ramanathan, and I. Stavrakakis,``Making Link State Routing
Scale for Ad Hoc Networks'', In {\em Proceedings of MobiHOC'2001},
Long Beach, CA, Oct.  2001.

Hope this helps

Cesar

Pete Sholander wrote:

William,

This (IMHO) is a good reference on protocol scaling ...

C. Santivanez, "Asymptotic Behavior of Mobile Ad hoc Routing Protocols
with respect to Traffic, Mobility and Size", Northeastern University
CDSP Tech. Report TR-CDSP-00-52, Oct. 2000.

(I think he also published some refereed papers on this topic in the
past few years, while at BBN.  Try google.com)

The short answer to your questions though is that the O(N) overhead
roughly scales as (mu)*N**2, where N is the number of nodes and mu is
the "link breakage rate", which may be caused by either mobility or RF
effects.

So, OSPF may work fine in some MANETs depending on the relative ratios
of number of nodes, link breakage rates, and the wireless links speeds.
Unmodified OSPFv1 and OSPFv2 are known to work poorly in typical
military networks.  (I'm not aware of any real-world experimental
results for the newer OSPFv3.  Other posters may ...)

Hope this helps!

--Pete Sholander

>>> "William Lee" <williaml@nortelnetworks.com> 05/08/03 11:56AM >>>

Are their any disadvantages of using OSPF in a MANET, particularly if
the
network is not very dynamic?  How does the performance of OSPF change
as
node mobility increases? How does it change if only the links are
transient,
but mobility is minimal?

William Lee

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

-- 
Cesar Santivanez, Ph.D. 
Network Scientist
Internetwork Research
BBN Technologies (A verizon unit)
  --------------461AD002E8F2FBB90264E156-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 9 06:08:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11306 for ; Fri, 9 May 2003 06:08:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h49AIRe23495 for manet-archive@odin.ietf.org; Fri, 9 May 2003 06:18: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 h49AIR823491 for ; Fri, 9 May 2003 06:18:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11297 for ; Fri, 9 May 2003 06:08:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E4pJ-0003ET-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 06:10:05 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19E4pJ-0003EP-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 06:10:05 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h49A6S821977; Fri, 9 May 2003 06:06: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 h49A0T821772 for ; Fri, 9 May 2003 06:00:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10979 for ; Fri, 9 May 2003 05:50:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E4Xw-00037G-00 for manet@ietf.org; Fri, 09 May 2003 05:52:08 -0400 Received: from concorde.inria.fr ([192.93.2.39]) by ietf-mx with esmtp (Exim 4.12) id 19E4Xv-00036r-00 for manet@ietf.org; Fri, 09 May 2003 05:52:07 -0400 Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id h499qVH28372; Fri, 9 May 2003 11:52:31 +0200 (MET DST) Message-ID: <002101c31611$1e32b2c0$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Pete Sholander" , , References: Subject: Re: [manet] OSPF in MANETs Date: Fri, 9 May 2003 11:55:26 +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 Hello, Even in a static network, OSPF may experience problems. During a link state period update an OSPF network must exchange (M*N)**2 node identifiers where N is the number of nodes and M the average number of links (neighbors) per node. Each node must flood an LSA message, each LSA message contains in average M links, each LSA message must be sent and acknowledged on all links in the network (ie M*N times). This broadcast storm in general makes the network collapsing when the number of nodes exceeds few dozens. In a dynamic network, should not the overhead be mu*M*N**2 if the broadcast is a link broadcast? In MANET word, OLSR looks the closest to OSPF. It was made originally to improve the link state update overhead in a MANET network. The broadcast is made by MPR nodes and via node broadcasts not ink broadcast (i.e. message are send only once, not sent separately on each link). The LSA may be limited to a subset of links (the MPR selector links). These policies drastically reduce the overhead. The next step could be to design a wireless extension of OSPF that could fit MANET requirements in an hybrid network. Philippe ----- Original Message ----- From: Pete Sholander To: ; Sent: Thursday, May 08, 2003 6:34 PM Subject: Re: [manet] OSPF in MANETs > William, > > This (IMHO) is a good reference on protocol scaling ... > > C. Santivanez, "Asymptotic Behavior of Mobile Ad hoc Routing Protocols > with respect to Traffic, Mobility and Size", Northeastern University > CDSP Tech. Report TR-CDSP-00-52, Oct. 2000. > > (I think he also published some refereed papers on this topic in the > past few years, while at BBN. Try google.com) > > The short answer to your questions though is that the O(N) overhead > roughly scales as (mu)*N**2, where N is the number of nodes and mu is > the "link breakage rate", which may be caused by either mobility or RF > effects. > > So, OSPF may work fine in some MANETs depending on the relative ratios > of number of nodes, link breakage rates, and the wireless links speeds. > Unmodified OSPFv1 and OSPFv2 are known to work poorly in typical > military networks. (I'm not aware of any real-world experimental > results for the newer OSPFv3. Other posters may ...) > > Hope this helps! > > --Pete Sholander > > >>> "William Lee" 05/08/03 11:56AM >>> > > Are their any disadvantages of using OSPF in a MANET, particularly if > the > network is not very dynamic? How does the performance of OSPF change > as > node mobility increases? How does it change if only the links are > transient, > but mobility is minimal? > > William Lee > > _______________________________________________ > 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 May 9 08:14:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13584 for ; Fri, 9 May 2003 08:14:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h49COTD00929 for manet-archive@odin.ietf.org; Fri, 9 May 2003 08:24: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 h49COT800926 for ; Fri, 9 May 2003 08:24:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13564 for ; Fri, 9 May 2003 08:14:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E6nE-0003rK-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 08:16:05 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19E6nE-0003rH-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 08:16:04 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h49CEH800367; Fri, 9 May 2003 08:14: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 h49C6S831673 for ; Fri, 9 May 2003 08:06:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA13156 for ; Fri, 9 May 2003 07:56:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E6Vo-0003lP-00 for manet@ietf.org; Fri, 09 May 2003 07:58:04 -0400 Received: from iproxy1.ericsson.dk ([213.159.160.68]) by ietf-mx with esmtp (Exim 4.12) id 19E6Vn-0003lK-00 for manet@ietf.org; Fri, 09 May 2003 07:58:03 -0400 Received: from unixmail.ted.dk.eu.ericsson.se (knud.ted.dk.eu.ericsson.se [213.159.188.246]) by iproxy1.ericsson.dk (8.12.9/8.12.8) with ESMTP id h49C1XTL028528 for ; Fri, 9 May 2003 14:01:33 +0200 (CEST) Received: from geku (geku.ted.dk.eu.ericsson.se [213.159.189.38]) by unixmail.ted.dk.eu.ericsson.se (8.10.1/8.10.1/TEDmain-1.0) with ESMTP id h49BwFx02506 for ; Fri, 9 May 2003 13:58:15 +0200 (MEST) From: Gerben Kuijpers To: manet@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 09 May 2003 13:58:15 +0200 Message-Id: <1052481495.13970.174.camel@geku> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [manet] OLSR: Update of 2-hop neighbour set Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Does anyone know why in OLSR the 2-hop neighbour set only SHOULD be updated based on the contents of an HELLO-message, received from a SYMMETRIC neighbour (draft-ietf-manet-olsr-09, section 8.2.1)? This is clear for point 1, adding a 2-hop tuple, but not for point 2, where 2-hop tuples are removed. Consider the following scenario: 1 Node A and B have symmetrical links to each other 2 Node B does not receive HELLO messages for some time (e.g. due to congestion) and the link to node A becomes asymmetric 3 Node B sends an HELLO message, where the interface address of node A is included with link type = LOST_LINK 4 Node A receives this HELLO and changes the link to node B to asymmetric and the status of node B to NOT_SYM 5 If the HELLO message included any more nodes with link type LOST_LINK, these are not updated in Node A's 2-hop neighbour set, since the status of node B is NOT_SYM. Why not use the information from the HELLO message and remove the 2-hop tuples? Best regards, /Gerben Kuijpers _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 9 09:46:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15714 for ; Fri, 9 May 2003 09:46:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h49Du7708320 for manet-archive@odin.ietf.org; Fri, 9 May 2003 09:56: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 h49Du7808316 for ; Fri, 9 May 2003 09:56:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15702 for ; Fri, 9 May 2003 09:45:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E8Ds-0004Pr-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 09:47:40 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19E8Ds-0004Po-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 09:47:40 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h49Djr807545; Fri, 9 May 2003 09:45: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 h49Dg3807395 for ; Fri, 9 May 2003 09:42:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15313 for ; Fri, 9 May 2003 09:31:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E80H-0004Is-00 for manet@ietf.org; Fri, 09 May 2003 09:33:37 -0400 Received: from 66-152-29-4.ded.btitelecom.net ([66.152.29.4] helo=mail.scires.com) by ietf-mx with esmtp (Exim 4.12) id 19E80G-0004Ie-00 for manet@ietf.org; Fri, 09 May 2003 09:33:36 -0400 Received: from SRCATL-MTA by mail.scires.com with Novell_GroupWise; Fri, 09 May 2003 09:35:00 -0400 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.2 Beta Date: Fri, 09 May 2003 09:34:48 -0400 From: "Pete Sholander" To: , , Subject: Re: [manet] OSPF in MANETs 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 Phillipe, You're correct that mu*M*N**2 is a "sharper" estimate of the LS overhead. Thanks for the correction. Also, thanks to Cesar for pointing out a newer reference to his work. --Peter Sholander >>> "Philippe Jacquet" 05/09/03 05:55AM >>> Hello, Even in a static network, OSPF may experience problems. During a link state period update an OSPF network must exchange (M*N)**2 node identifiers where N is the number of nodes and M the average number of links (neighbors) per node. Each node must flood an LSA message, each LSA message contains in average M links, each LSA message must be sent and acknowledged on all links in the network (ie M*N times). This broadcast storm in general makes the network collapsing when the number of nodes exceeds few dozens. In a dynamic network, should not the overhead be mu*M*N**2 if the broadcast is a link broadcast? In MANET word, OLSR looks the closest to OSPF. It was made originally to improve the link state update overhead in a MANET network. The broadcast is made by MPR nodes and via node broadcasts not ink broadcast (i.e. message are send only once, not sent separately on each link). The LSA may be limited to a subset of links (the MPR selector links). These policies drastically reduce the overhead. The next step could be to design a wireless extension of OSPF that could fit MANET requirements in an hybrid network. Philippe ----- Original Message ----- From: Pete Sholander To: ; Sent: Thursday, May 08, 2003 6:34 PM Subject: Re: [manet] OSPF in MANETs > William, > > This (IMHO) is a good reference on protocol scaling ... > > C. Santivanez, "Asymptotic Behavior of Mobile Ad hoc Routing Protocols > with respect to Traffic, Mobility and Size", Northeastern University > CDSP Tech. Report TR-CDSP-00-52, Oct. 2000. > > (I think he also published some refereed papers on this topic in the > past few years, while at BBN. Try google.com) > > The short answer to your questions though is that the O(N) overhead > roughly scales as (mu)*N**2, where N is the number of nodes and mu is > the "link breakage rate", which may be caused by either mobility or RF > effects. > > So, OSPF may work fine in some MANETs depending on the relative ratios > of number of nodes, link breakage rates, and the wireless links speeds. > Unmodified OSPFv1 and OSPFv2 are known to work poorly in typical > military networks. (I'm not aware of any real-world experimental > results for the newer OSPFv3. Other posters may ...) > > Hope this helps! > > --Pete Sholander > > >>> "William Lee" 05/08/03 11:56AM >>> > > Are their any disadvantages of using OSPF in a MANET, particularly if > the > network is not very dynamic? How does the performance of OSPF change > as > node mobility increases? How does it change if only the links are > transient, > but mobility is minimal? > > William Lee > > _______________________________________________ > 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 May 9 10:21:36 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17703 for ; Fri, 9 May 2003 10:21:36 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h49EVZs11083 for manet-archive@odin.ietf.org; Fri, 9 May 2003 10:31: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 h49EVZ811077 for ; Fri, 9 May 2003 10:31:35 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17699 for ; Fri, 9 May 2003 10:21:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E8mB-0004cv-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 10:23:07 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19E8mB-0004cs-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 10:23:07 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h49ELg810575; Fri, 9 May 2003 10:21: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 h49EIv810456 for ; Fri, 9 May 2003 10:18:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16820 for ; Fri, 9 May 2003 10:08:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E8Zy-0004Z4-00 for manet@ietf.org; Fri, 09 May 2003 10:10:30 -0400 Received: from cse.uta.edu ([129.107.12.1]) by ietf-mx with esmtp (Exim 4.12) id 19E8Zx-0004Z1-00 for manet@ietf.org; Fri, 09 May 2003 10:10:29 -0400 Received: from uta.edu (gergo.uta.edu [129.107.22.44]) by cse.uta.edu (8.12.8/8.12.8) with ESMTP id h49EFm6e021108 for ; Fri, 9 May 2003 09:15:48 -0500 (CDT) Message-ID: <3EBBB706.108@uta.edu> Date: Fri, 09 May 2003 09:11:18 -0500 From: Gergely Zaruba User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en,pdf MIME-Version: 1.0 To: "'manet@ietf.org'" Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Call for Papers on WPANs at HICSS37 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 Our apologies if this is a duplicate ********************************************************************** Call for Papers Minitrack on Wireless Personal Area Networks (WPANs) Part of the Software Track at the Thirty-seventh Annual Hawaiian International Conference on System Sciences (HICSS37), Big Island of Hawaii, January 5-8, 2004 http://crystal.uta.edu/~zaruba/hicss37/ Submission deadline: June 1, 2003 ********************************************************************** Overview: Wireless personal area networks (WPANs) are short to very short-range wireless networks that can be used to exchange information between devices in the reach of a person. WPANs can be used to replace cables between computers and their peripherals, to establish communities helping people do their everyday chores making them more productive, or to establish location aware services. It is predicted that not only will most PDAs, phones, laptops include WPAN technology but that the number of small WPAN enabled devices (e.g., pens, cameras, headsets, various sensors) will soon outnumber the computers on the Internet. The best example representing WPANs is the recent industry standard: Bluetooth, other examples include Spike (for real time gaming - proprietary technology), and in the broad sense HomeRF. The IEEE 802 committee has also realized the importance of short-range wireless networking and initiated the establishment of the IEEE 802.15 working group to standardize protocols and interfaces for wireless personal area networking. Another key issue is the inter-working of wireless technologies to create heterogeneous wireless networks. For instance, WPANs and WLANs will enable an extension of the third generation (3G) cellular networks (i.e., UMTS and cdma2000) into devices without direct cellular access thus pointing towards next generation wireless networking. Moreover, devices interconnected in a WPAN may be able to utilize a combination of 3G access and WLAN access by selecting the access that is best for the moment. In such networks 3G, WLAN and WPAN technologies do not compete against each other but enable the user to select the best connectivity for his/her purposes. Today, WPAN research covers a very broad area, starting from technical issues like automatic formation of networks or security issues and going up all the stack to the question what kind of applications will be used in WPANs. We expect that the availability of a cheap short-range wireless technology will further fuel research and development in what, where and most importantly how WPAN technologies could be used for. Minitrack chairs: Frank Kargl, University of Ulm, Germany (frank.kargl@informatik.uni-ulm.edu) Dr. Elaine Lawrence, University of Technology, Sydney (elaine@it.uts.edu.au) Dr. Gergely V. Zaruba, The University of Texas at Arlington, USA (zaruba@uta.edu) Important Deadlines: June 1, 2003 Full papers submitted to Minitrack Chairs through instructions at the Minitrack's Website. August 31, 2003 Notice of accepted papers sent to Authors. October 1, 2003 Accepted manuscripts sent electronically to the publisher. Authors must be registered for the conference by this date. Submission Guidelines: Abstracts need to be submitted via email to Gergely Zaruba at: zaruba@uta.edu in pdf format only. For full paper submission instructions please read and follow the online submission instructions at the minitrack's web-site: http://crystal.uta.edu/~zaruba/hicss37/ (The final paper must be no longer than 10 pages, double-column, single spaced.) Scope: The minitrack will concentrate on completed or ongoing research in the area of wireless local area networking and wireless personal area networking (excluding manufacturing). Areas of interest include but are not limited to research in: - Protocols tailored to WPANs - QoS provisioning in WPANs - WPAN applications - Performance evaluation - TCP performance of WPANs - Bluetooth for ad hoc networks (scatternets) - Bluetooth performance evaluation - Routing in Bluetooth scatternets - Security issues of WPANs - IP over Bluetooth - Mobility management and seamless integration of WPANs - Interoperability, interference and co-existence of WPANs, WLANs and 3G networks - WPANs vs. WLANs - Caching in WPANs - Service discovery in WPANs - Integration and heterogeneous wireless infrastructures employing WPANs - WPAN specific applications _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 9 10:56:18 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19062 for ; Fri, 9 May 2003 10:56:18 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h49F6Is14071 for manet-archive@odin.ietf.org; Fri, 9 May 2003 11:06: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 h49F6I814068 for ; Fri, 9 May 2003 11:06:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19047 for ; Fri, 9 May 2003 10:55:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E9Jm-0004tc-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 10:57:50 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19E9Jl-0004tZ-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 10:57:49 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h49Esw813324; Fri, 9 May 2003 10:54: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 h49Eo2813006 for ; Fri, 9 May 2003 10:50:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18582 for ; Fri, 9 May 2003 10:39:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E943-0004lN-00 for manet@ietf.org; Fri, 09 May 2003 10:41:35 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19E942-0004lK-00 for manet@ietf.org; Fri, 09 May 2003 10:41:34 -0400 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.12.9+Sun/8.12.8) with ESMTP id h49EfwDi011265; Fri, 9 May 2003 10:41:58 -0400 (EDT) Received: from smtp.itd.nrl.navy.mil (localhost [127.0.0.1]) by smtp.itd.nrl.navy.mil (8.12.9+Sun/8.12.2) with SMTP id h49EfwFI013867; Fri, 9 May 2003 10:41:58 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.1.0.29) with SMTP id M2003050910415719916 ; Fri, 09 May 2003 10:41:57 -0400 Message-Id: <5.1.1.5.2.20030509102626.014e9ea8@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Fri, 09 May 2003 10:41:50 -0400 To: "William Lee" , "'manet@ietf.org'" From: Joe Macker Subject: Re: [manet] OSPF in MANETs In-Reply-To: <933FADF5E673D411B8A30002A5608A0E53AF76@zrc2c012.us.nortel. com> 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: , >Are their any disadvantages of using OSPF in a MANET, particularly if the network is not very dynamic? How does the performance of OSPF change as node mobility increases? How does it change if only the links are transient, but mobility is minimal? Some manet-ish extensions to OSPF would help scalability and dynamic, wireless performance... There is a good niche of applications for this type of capability. We have discussed this at various times in the past and several of us have supported strawman proposals. There is a set of efforts exploring concepts at the present time. I, for one, believe we could have a focused engineering effort here. -Joe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 9 11:55:17 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21047 for ; Fri, 9 May 2003 11:55:17 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h49G5I819818 for manet-archive@odin.ietf.org; Fri, 9 May 2003 12:05: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 h49G5I819815 for ; Fri, 9 May 2003 12:05:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21034 for ; Fri, 9 May 2003 11:54:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EAEr-0005Pg-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 11:56:49 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19EAEq-0005Pc-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 11:56:48 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h49Fbw817707; Fri, 9 May 2003 11:37: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 h49FXT816536 for ; Fri, 9 May 2003 11:33:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19934 for ; Fri, 9 May 2003 11:22:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E9k5-00056E-00 for manet@ietf.org; Fri, 09 May 2003 11:25:01 -0400 Received: from fsc.cpsc.ucalgary.ca ([136.159.2.3]) by ietf-mx with esmtp (Exim 4.12) id 19E9k4-00056B-00 for manet@ietf.org; Fri, 09 May 2003 11:25:00 -0400 Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsc.cpsc.ucalgary.ca (8.12.9/8.12.9) with ESMTP id h49FPes1009348 for ; Fri, 9 May 2003 09:25:40 -0600 Received: from cpsc.ucalgary.ca (ict719g [136.159.15.15]) by imgw1.cpsc.ucalgary.ca (8.12.9/8.12.3) with ESMTP id h49FPa79020046 for ; Fri, 9 May 2003 09:25:36 -0600 Message-ID: <3EBBC86F.3030606@cpsc.ucalgary.ca> Date: Fri, 09 May 2003 09:25:35 -0600 From: Abhinav Gupta Reply-To: gupta@cpsc.ucalgary.ca Organization: University of Calgary User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=3.3 required=6.8 X-Spam-Level: *** Content-Transfer-Encoding: 7bit Subject: [manet] Implementation Issues Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 there, I am a newbie. I would like to know if the implementation of on-demand routing protocols more efficient through the use of APIs or without it? Also I would be grateful if someone could guide me about a good starting point to get started on implementation of on demand routing protocols for manets. Thanks, Abhinav. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 9 15:08:16 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28057 for ; Fri, 9 May 2003 15:08:15 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h49JIKO04258 for manet-archive@odin.ietf.org; Fri, 9 May 2003 15:18: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 h49JIJ804254 for ; Fri, 9 May 2003 15:18:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28003 for ; Fri, 9 May 2003 15:07:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EDFa-0006kz-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 15:09:46 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19EDFZ-0006kw-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 15:09:45 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h49J82803778; Fri, 9 May 2003 15:08: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 h49J2K802732 for ; Fri, 9 May 2003 15:02:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27069 for ; Fri, 9 May 2003 14:51:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ED07-0006eK-00 for manet@ietf.org; Fri, 09 May 2003 14:53:47 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 19ED06-0006eH-00 for manet@ietf.org; Fri, 09 May 2003 14:53:46 -0400 Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 3AA681E4032 for ; Fri, 9 May 2003 13:55:25 -0400 (EDT) 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 h49Ish425735 for ; Fri, 9 May 2003 14:54:43 -0400 Date: Fri, 9 May 2003 14:58:10 -0400 (EDT) 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] A question concerning the DSR Opnet code Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I'm modifying a DSR OPNET code that I downloaded from NIST (It's a Unix-based code, called nist_dsr_model.tar.pl). I have a question about how to generate a stream of DATA packets and send them from the source to destination. I'm not sure if this isn't the right venue for this OPNET-related question, but appreciate whatever advice and help you can give me. I've noticed that in this DSR code, after a route is found, the source sends a single data packet to the destinatin on that route. In other words, it seems that each source-destination connection session only transmits one data packet. What I'd like to do is to send a stream of data packets (say, 10 of them) from src to dest. To that end, I've been going over the code to see where the first DATA packet is created. Because I'm very new with OPNET, I have been unable to find it. So far, I'm narrowing my search down to the dsr_upper_layer_data_arrival function, in the dsr_routing_layer process, and the Enter executive of the Upper_Layer state in the same processs. I have a hunch these two places are where I'm most likely to find that generator of the data packets. But so far, I haven't pinpointed the exact lines yet. My hope is that once I know how this single data packet is generated, I'll be able to modify it (maybe some sort of for loop to let it run 10 times?) to get a stream of DATA packets. So could someone with OPNET programming experience give me some help on that? Maybe someone can tell me what "catchy words" or KPs in the OPNET code I should be looking for with regard to generating DATA packets? Thanks in advance. -Ed _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 9 15:32:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29330 for ; Fri, 9 May 2003 15:32:37 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h49JggB06419 for manet-archive@odin.ietf.org; Fri, 9 May 2003 15:42: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 h49Jgg806416 for ; Fri, 9 May 2003 15:42:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29323 for ; Fri, 9 May 2003 15:32:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EDdA-0006u7-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 15:34:08 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19EDd9-0006u4-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 15:34:07 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h49JXP805020; Fri, 9 May 2003 15:33: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 h49JUt804901 for ; Fri, 9 May 2003 15:30:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29073 for ; Fri, 9 May 2003 15:20:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EDRm-0006pn-00 for manet@ietf.org; Fri, 09 May 2003 15:22:22 -0400 Received: from sp44en1.nerdc.ufl.edu ([128.227.74.44] helo=smtp.ufl.edu) by ietf-mx with esmtp (Exim 4.12) id 19EDRl-0006pk-00 for manet@ietf.org; Fri, 09 May 2003 15:22:21 -0400 Received: from WINNET02 (p80-155.dhcp.ece.ufl.edu [10.227.80.155]) by smtp.ufl.edu (8.12.9/8.12.7/2.4.2) with SMTP id h49JNCas109894 for ; Fri, 9 May 2003 15:23:14 -0400 Message-ID: <007a01c31660$76d1fa90$9b50e30a@WINNET02> From: "Byung-Seo Kim" To: Date: Fri, 9 May 2003 15:23:24 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0077_01C3163E.EEE75FB0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Scanned-By: NERDC Open Systems Group (http://open-systems.ufl.edu/services/virus-scan/) Subject: [manet] The way for a node to decide a link failure in 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: , This is a multi-part message in MIME format. ------=_NextPart_000_0077_01C3163E.EEE75FB0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable Hello, all. I am looking for the answer about "how does the IP or routing layer of a = node decide that the link is broken or unavailable using DSR routing = protocol? Is there any frame life time for the routing frame? so that if = the time is expired, the frame is discarded or the destination address = for the next hop is changed. Or, is the decision made based on the MAC = failure? For example, in MAC of WLAN, the node tries 7 times and the = frame is discarded. At this moment, what does IP layer do? I will appreciate if anyone answer this question. Thank you. Byung-Seo Kim ------=_NextPart_000_0077_01C3163E.EEE75FB0 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable
Hello, all.
 
I am looking for the answer = about "how does=20 the IP or routing layer of a node decide that the link is broken or = unavailable using DSR routing protocol? Is there any frame life = time for=20 the routing frame? so that if the time is expired, the frame is = discarded=20 or the destination address for the next hop is changed. Or, is = the=20 decision made based on the MAC failure? For example, in MAC of WLAN, the = node=20 tries 7 times and the frame is discarded. At this moment, what does = IP=20 layer do?
 
I will appreciate if anyone answer this = question.
 
Thank you.
 
Byung-Seo=20 Kim
------=_NextPart_000_0077_01C3163E.EEE75FB0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 9 21:16:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08923 for ; Fri, 9 May 2003 21:16:58 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4A1RAC31621 for manet-archive@odin.ietf.org; Fri, 9 May 2003 21:27: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 h4A1RA831618 for ; Fri, 9 May 2003 21:27:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08916 for ; Fri, 9 May 2003 21:16:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EJ0P-00010C-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 21:18:29 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19EJ0O-000109-00 for manet-web-archive@ietf.org; Fri, 09 May 2003 21:18:28 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4A1Hw831285; Fri, 9 May 2003 21:17: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 h4A1CA831116 for ; Fri, 9 May 2003 21:12:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08767 for ; Fri, 9 May 2003 21:01:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EIlt-0000x6-00 for manet@ietf.org; Fri, 09 May 2003 21:03:29 -0400 Received: from mailserver1.opnet.com ([12.145.55.23]) by ietf-mx with esmtp (Exim 4.12) id 19EIls-0000x3-00 for manet@ietf.org; Fri, 09 May 2003 21:03:28 -0400 Received: from wtn11055.opnet.com (wtn11055.opnet.com [172.16.11.55]) by mailserver1.opnet.com (8.12.9/8.12.8) with ESMTP id h4A14Jx2026476; Fri, 9 May 2003 21:04:19 -0400 (EDT) Message-Id: <5.1.0.14.2.20030509203237.01ba8c38@mailserver.opnet.com> X-Sender: jlee@mailserver.opnet.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 09 May 2003 21:04:19 -0400 To: manet@ietf.org, wireless_community@opnet.com From: Jay J Lee Subject: Re: [manet] A question concerning the DSR Opnet code In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-MailScanner: Not scanned: Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 OPNET, "DATA" packets are usually generated by configuring either the typical (FTP, HTTP and etc.) or the custom application models. You could create a custom application which will generate a stream of UDP packets. The obvious advantage of this method is that you do not have to modify the code. Consult the OPNET product documentation for the detailed description of the custom application model. If you still have to modify the code, look for the kernel procedures for handling packets which should look like "op_pk_...". Basically you want to make multiple copies of the packet using "op_pk_copy()" before it is sent out through "op_pk_send()". Good luck, - Jay At 02:58 PM 5/9/2003 -0400, you wrote: >Hi, > > I'm modifying a DSR OPNET code that I downloaded from NIST (It's a >Unix-based code, called nist_dsr_model.tar.pl). I have a question about >how to generate a stream of DATA packets and send them from the source to >destination. I'm not sure if this isn't the right venue for this >OPNET-related question, but appreciate whatever advice and help you can >give me. > > I've noticed that in this DSR code, after a route is found, >the source sends a single data packet to the destinatin on that route. In >other words, it seems that each source-destination connection session only >transmits one data packet. > > What I'd like to do is to send a stream of data packets (say, 10 of >them) from src to dest. To that end, I've been going over the code to see >where the first DATA packet is created. Because I'm very new with OPNET, I >have been unable to find it. So far, I'm narrowing my search down to the >dsr_upper_layer_data_arrival function, in the dsr_routing_layer process, >and the Enter executive of the Upper_Layer state in the same processs. I >have a hunch these two places are where I'm most likely to find that >generator of the data packets. But so far, I haven't pinpointed the exact >lines yet. My hope is that once I know how this single data packet is >generated, I'll be able to modify it (maybe some sort of for loop to let >it run 10 times?) to get a stream of DATA packets. > > So could someone with OPNET programming experience give me some help >on that? Maybe someone can tell me what "catchy words" or KPs in the >OPNET code I should be looking for with regard to generating DATA packets? >Thanks in advance. > >-Ed > > > > >_______________________________________________ >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 May 10 05:38:47 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27416 for ; Sat, 10 May 2003 05:38:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4A9n9n09625 for manet-archive@odin.ietf.org; Sat, 10 May 2003 05:49: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 h4A9n9809622 for ; Sat, 10 May 2003 05:49:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27408 for ; Sat, 10 May 2003 05:38:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EQq2-00039C-00 for manet-web-archive@ietf.org; Sat, 10 May 2003 05:40:18 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19EQq1-000399-00 for manet-web-archive@ietf.org; Sat, 10 May 2003 05:40:17 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4A9dm809253; Sat, 10 May 2003 05:39: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 h4A9Zp808308 for ; Sat, 10 May 2003 05:35:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27263 for ; Sat, 10 May 2003 05:24:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EQdA-00035O-00 for manet@ietf.org; Sat, 10 May 2003 05:27:00 -0400 Received: from pedigree.cs.ubc.ca ([142.103.6.50]) by ietf-mx with esmtp (Exim 4.12) id 19EQd9-00035L-00 for manet@ietf.org; Sat, 10 May 2003 05:26:59 -0400 Received: from doraemon.cs.ubc.ca (IDENT:vOv4zurY3ek5XVe6udkiV5BLs074kfPO@doraemon.cs.ubc.ca [142.103.10.79]) by pedigree.cs.ubc.ca (8.12.9/8.11.4) with ESMTP id h4A9Rv0V015152 for ; Sat, 10 May 2003 02:27:57 -0700 (PDT) Date: Sat, 10 May 2003 02:27:57 -0700 (PDT) From: Suprio Ray To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] parallelizing GloMoSim Simulation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I am running a GloMoSim simulation with 5000 nodes and it takes several days to finish. I want to run it on our server (having 8 processors) to speed up. Does anyone know if there is any option in GloMoSim (like compiler or config file option) so that the simulation is automatically parallelized i.e. run on all available processors, when run on a multi-processor machine? Or do I have to change the simulation code and how? Thanks in advance. -Suprio --------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat May 10 14:36:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05069 for ; Sat, 10 May 2003 14:36:56 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4AI1ad06935 for manet-archive@odin.ietf.org; Sat, 10 May 2003 14:01: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 h4AI1aB06932 for ; Sat, 10 May 2003 14:01:36 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05057 for ; Sat, 10 May 2003 14:36:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EZEn-0004f4-00 for manet-web-archive@ietf.org; Sat, 10 May 2003 14:38:25 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19EZEn-0004er-00 for manet-web-archive@ietf.org; Sat, 10 May 2003 14:38:25 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4AHppB06302; Sat, 10 May 2003 13:51: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 h4AHdBB06045 for ; Sat, 10 May 2003 13:39:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04632 for ; Sat, 10 May 2003 14:13:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EYss-0004XP-00 for manet@ietf.org; Sat, 10 May 2003 14:15:46 -0400 Received: from [203.199.93.81] (helo=w16.indiatimes.com) by ietf-mx with esmtp (Exim 4.12) id 19EYsl-0004Wf-00 for manet@ietf.org; Sat, 10 May 2003 14:15:40 -0400 Received: from 192.168.57.81 ([192.168.57.22]) by w16.indiatimes.com (8.9.3/8.9.3) with SMTP id XAA14541 for ; Sat, 10 May 2003 23:08:50 +0530 From: "jyothi_017" Message-Id: <200305101738.XAA14541@w16.indiatimes.com> To: Reply-To: "jyothi_017" Date: Sat, 10 May 2003 23:46:45 +0530 X-URL: http://indiatimes.com Content-Type: multipart/alternative; boundary="=_MAILER_ATTACH_BOUNDARY1_20035106234645846930886" MIME-Version: 1.0 Subject: [manet] Security model 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: , --=_MAILER_ATTACH_BOUNDARY1_20035106234645846930886 Content-Type: text/plain; charset=us-ascii Hi everybody, I am a beginner to NS2. I am doing work in key management for MANETs.I request all of you to send any info regarding security issues for MANETs and also about NS2. Thanking in advance Jyothi B.S. Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now ! --=_MAILER_ATTACH_BOUNDARY1_20035106234645846930886 Content-Type: text/html; charset=us-ascii

Hi everybody,

I am a beginner to NS2. I am doing work in key management for MANETs.I request all of you to send any info regarding security issues for MANETs and also about NS2.

Thanking in advance

Jyothi B.S.

Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com
Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com
Bid for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now ! --=_MAILER_ATTACH_BOUNDARY1_20035106234645846930886-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat May 10 15:02:31 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05707 for ; Sat, 10 May 2003 15:02:30 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4AIRBC09205 for manet-archive@odin.ietf.org; Sat, 10 May 2003 14:27: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 h4AIQuB09188 for ; Sat, 10 May 2003 14:26:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05697 for ; Sat, 10 May 2003 15:01:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EZdJ-0004qh-00 for manet-web-archive@ietf.org; Sat, 10 May 2003 15:03:45 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19EZdI-0004qe-00 for manet-web-archive@ietf.org; Sat, 10 May 2003 15:03:44 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4AIGUB08339; Sat, 10 May 2003 14:16: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 h4AI9tB08085 for ; Sat, 10 May 2003 14:09:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05252 for ; Sat, 10 May 2003 14:44:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EZMc-0004iL-00 for manet@ietf.org; Sat, 10 May 2003 14:46:30 -0400 Received: from mx03.covadmail.net ([63.65.120.63] helo=smtp.covadmail.net) by ietf-mx with smtp (Exim 4.12) id 19EZMW-0004i5-00 for manet@ietf.org; Sat, 10 May 2003 14:46:24 -0400 Received: (covad.net 3748 invoked from network); 10 May 2003 18:46:27 -0000 Received: from unknown (HELO amd2100) (65.114.175.65) by sun-qmail02 with SMTP; 10 May 2003 18:46:27 -0000 Reply-To: From: "Herbert Rubens" To: "'jyothi_017'" , Subject: RE: [manet] Security model in MANETs Date: Sat, 10 May 2003 14:46:30 -0400 Organization: Center for Networking and Distributed Systems Message-ID: <001201c31724$78997410$6401a8c0@amd2100> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0013_01C31702.F187D410" 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.1165 Importance: Normal In-Reply-To: <200305101738.XAA14541@w16.indiatimes.com> Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_0013_01C31702.F187D410 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit This should get you started: http://www.ccs.neu.edu/home/zhufeng/security_manet.html -Herb -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of jyothi_017 Sent: Saturday, May 10, 2003 2:17 PM To: manet@ietf.org Subject: [manet] Security model in MANETs Hi everybody, I am a beginner to NS2. I am doing work in key management for MANETs.I request all of you to send any info regarding security issues for MANETs and also about NS2. Thanking in advance Jyothi B.S. _____ Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now ! ------=_NextPart_000_0013_01C31702.F187D410 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

This should get you = started:

 

http://w= ww.ccs.neu.edu/home/zhufeng/security_manet.html

 

 

-Herb

 

 

-----Original = Message-----
From: = manet-admin@ietf.org [mailto:manet-admin@ietf.org] On = Behalf Of jyothi_017
Sent: Saturday, May 10, = 2003 2:17 PM
To: manet@ietf.org
Subject: [manet] Security = model in MANETs

 

Hi everybody,

I am a beginner to NS2. I am doing work in = key management for MANETs.I request all of you to send any info regarding = security issues for MANETs and also about NS2.

Thanking in = advance

Jyothi B.S.

Get Your = Private, Free E-mail from Indiatimes at http://email.indiatimes.com<= /span>
Buy The Best In BOOKS at = http://www.bestsellers.ind= iatimes.com
Bid for Air Tickets @ = Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com<= /a> and Bid Now !

------=_NextPart_000_0013_01C31702.F187D410-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun May 11 10:23:30 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05386 for ; Sun, 11 May 2003 10:23:30 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4BDmYe24304 for manet-archive@odin.ietf.org; Sun, 11 May 2003 09:48: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 h4BDmYB24301 for ; Sun, 11 May 2003 09:48:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05379 for ; Sun, 11 May 2003 10:23:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Erl5-0001Bc-00 for manet-web-archive@ietf.org; Sun, 11 May 2003 10:24:59 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Erl4-0001BZ-00 for manet-web-archive@ietf.org; Sun, 11 May 2003 10:24:58 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4BDctB23905; Sun, 11 May 2003 09:38: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 h4BDS3B22751 for ; Sun, 11 May 2003 09:28:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04030 for ; Sun, 11 May 2003 10:02:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ErRE-00016k-00 for manet@ietf.org; Sun, 11 May 2003 10:04:28 -0400 Received: from web41810.mail.yahoo.com ([66.218.93.144]) by ietf-mx with smtp (Exim 4.12) id 19ErRD-00016f-00 for manet@ietf.org; Sun, 11 May 2003 10:04:27 -0400 Message-ID: <20030511140457.92273.qmail@web41810.mail.yahoo.com> Received: from [213.78.78.240] by web41810.mail.yahoo.com via HTTP; Sun, 11 May 2003 15:04:57 BST Date: Sun, 11 May 2003 15:04:57 +0100 (BST) From: =?iso-8859-1?q?l=20s?= Subject: RE: [manet] Security model in MANETs To: Herbert Rubens , manet@ietf.org In-Reply-To: <001201c31724$78997410$6401a8c0@amd2100> 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 Herb, Thanks, this is very useful to me too, however 99% of links give a '404 Not Found' in: http://www.ccs.neu.edu/papers/ I guess they are not globally viewable. cheers, Lee -S- CCSR Uni of Surrey UK --- Herbert Rubens wrote: > This should get you started: > > http://www.ccs.neu.edu/home/zhufeng/security_manet.html > > > -Herb > > > -----Original Message----- > From: manet-admin@ietf.org > [mailto:manet-admin@ietf.org] On Behalf Of > jyothi_017 > Sent: Saturday, May 10, 2003 2:17 PM > To: manet@ietf.org > Subject: [manet] Security model in MANETs > > Hi everybody, > I am a beginner to NS2. I am doing work in key > management for MANETs.I request all of you to send > any info regarding security issues for MANETs and > also about NS2. > Thanking in advance > Jyothi B.S. > __________________________________________________ Yahoo! Plus For a better Internet experience http://www.yahoo.co.uk/btoffer _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun May 11 10:50:30 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05845 for ; Sun, 11 May 2003 10:50:30 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4BEFYI26013 for manet-archive@odin.ietf.org; Sun, 11 May 2003 10:15: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 h4BEFYB26010 for ; Sun, 11 May 2003 10:15:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05836 for ; Sun, 11 May 2003 10:49:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EsBC-0001K9-00 for manet-web-archive@ietf.org; Sun, 11 May 2003 10:51:58 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19EsBC-0001K6-00 for manet-web-archive@ietf.org; Sun, 11 May 2003 10:51:58 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4BE6NB24846; Sun, 11 May 2003 10:06: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 h4BDkDB24204 for ; Sun, 11 May 2003 09:46:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05319 for ; Sun, 11 May 2003 10:20:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Erin-0001AG-00 for manet@ietf.org; Sun, 11 May 2003 10:22:37 -0400 Received: from mx03.covadmail.net ([63.65.120.63] helo=smtp.covadmail.net) by ietf-mx with smtp (Exim 4.12) id 19Erim-0001AD-00 for manet@ietf.org; Sun, 11 May 2003 10:22:36 -0400 Received: (covad.net 18564 invoked from network); 11 May 2003 14:23:05 -0000 Received: from unknown (HELO amd2100) (65.114.175.65) by sun-qmail15 with SMTP; 11 May 2003 14:23:05 -0000 Reply-To: From: "Herbert Rubens" To: "'l s'" , "'Herbert Rubens'" , Subject: RE: [manet] Security model in MANETs Date: Sun, 11 May 2003 10:23:08 -0400 Organization: Center for Networking and Distributed Systems Message-ID: <002a01c317c8$d8ad7410$6401a8c0@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.1165 Importance: Normal In-Reply-To: <20030511140457.92273.qmail@web41810.mail.yahoo.com> Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Just put the title of the paper into Google and you should be able to track any of them down. There is actually a link to Google on that page. Feng Zhu did a great job of organizing the page for everyone. It's a great resource. -Herb -----Original Message----- From: l s [mailto:quantumparadox@yahoo.co.uk] Sent: Sunday, May 11, 2003 10:05 AM To: Herbert Rubens; manet@ietf.org Subject: RE: [manet] Security model in MANETs Herb, Thanks, this is very useful to me too, however 99% of links give a '404 Not Found' in: http://www.ccs.neu.edu/papers/ I guess they are not globally viewable. cheers, Lee -S- CCSR Uni of Surrey UK --- Herbert Rubens wrote: > This should get you started: > > http://www.ccs.neu.edu/home/zhufeng/security_manet.html > > > -Herb > > > -----Original Message----- > From: manet-admin@ietf.org > [mailto:manet-admin@ietf.org] On Behalf Of > jyothi_017 > Sent: Saturday, May 10, 2003 2:17 PM > To: manet@ietf.org > Subject: [manet] Security model in MANETs > > Hi everybody, > I am a beginner to NS2. I am doing work in key > management for MANETs.I request all of you to send > any info regarding security issues for MANETs and > also about NS2. > Thanking in advance > Jyothi B.S. > __________________________________________________ Yahoo! Plus For a better Internet experience http://www.yahoo.co.uk/btoffer _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun May 11 12:47:08 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08019 for ; Sun, 11 May 2003 12:47:08 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4BGCGk01565 for manet-archive@odin.ietf.org; Sun, 11 May 2003 12:12: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 h4BGCGB01562 for ; Sun, 11 May 2003 12:12:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08002 for ; Sun, 11 May 2003 12:46:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Eu05-0001wc-00 for manet-web-archive@ietf.org; Sun, 11 May 2003 12:48:37 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Eu05-0001wZ-00 for manet-web-archive@ietf.org; Sun, 11 May 2003 12:48:37 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4BG2oB32181; Sun, 11 May 2003 12:02: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 h4BFPQB29764 for ; Sun, 11 May 2003 11:25:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07117 for ; Sun, 11 May 2003 11:59:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EtGm-0001fQ-00 for manet@ietf.org; Sun, 11 May 2003 12:01:48 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 19EtGm-0001fN-00 for manet@ietf.org; Sun, 11 May 2003 12:01:48 -0400 Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 379321E403B; Sun, 11 May 2003 11:03:53 -0400 (EDT) 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 h4BG2m407104; Sun, 11 May 2003 12:02:48 -0400 Date: Sun, 11 May 2003 12:01:45 -0400 (EDT) From: "haas@ece.cornell.edu" To: =?iso-8859-1?q?l=20s?= Cc: Herbert Rubens , manet@ietf.org Subject: RE: [manet] Security model in MANETs In-Reply-To: <20030511140457.92273.qmail@web41810.mail.yahoo.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 Lee, Cannot speak for others, but you can view our papers on ad hoc security at: http://wnl.ece.cornell.edu/wnlprojects.html 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 Sun, 11 May 2003, [iso-8859-1] l s wrote: > Herb, > > Thanks, this is very useful to me too, however 99% of > links give a '404 Not Found' in: > http://www.ccs.neu.edu/papers/ > I guess they are not globally viewable. > > cheers, > Lee -S- > CCSR > Uni of Surrey > UK > > --- Herbert Rubens wrote: > > This should get you started: > > > > > http://www.ccs.neu.edu/home/zhufeng/security_manet.html > > > > > > -Herb > > > > > > -----Original Message----- > > From: manet-admin@ietf.org > > [mailto:manet-admin@ietf.org] On Behalf Of > > jyothi_017 > > Sent: Saturday, May 10, 2003 2:17 PM > > To: manet@ietf.org > > Subject: [manet] Security model in MANETs > > > > Hi everybody, > > I am a beginner to NS2. I am doing work in key > > management for MANETs.I request all of you to send > > any info regarding security issues for MANETs and > > also about NS2. > > Thanking in advance > > Jyothi B.S. > > > > > __________________________________________________ > Yahoo! Plus > For a better Internet experience > http://www.yahoo.co.uk/btoffer > _______________________________________________ > 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 May 11 15:20:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11290 for ; Sun, 11 May 2003 15:20:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4BIjvJ10384 for manet-archive@odin.ietf.org; Sun, 11 May 2003 14:45: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 h4BIjvB10381 for ; Sun, 11 May 2003 14:45:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11287 for ; Sun, 11 May 2003 15:20:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19EwOl-0002aw-00 for manet-web-archive@ietf.org; Sun, 11 May 2003 15:22:15 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19EwOl-0002as-00 for manet-web-archive@ietf.org; Sun, 11 May 2003 15:22:15 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4BIYpB09192; Sun, 11 May 2003 14:34: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 h4BIPSB08990 for ; Sun, 11 May 2003 14:25:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09975 for ; Sun, 11 May 2003 14:59:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ew4x-0002WZ-00 for manet@ietf.org; Sun, 11 May 2003 15:01:47 -0400 Received: from ux6.sp.cs.cmu.edu ([128.2.181.250]) by ietf-mx with smtp (Exim 4.12) id 19Ew4w-0002WW-00 for manet@ietf.org; Sun, 11 May 2003 15:01:46 -0400 Date: Sun, 11 May 2003 15:02:19 -0400 (EDT) From: Yih-Chun Hu X-Sender: yihchun@ux6.sp.cs.cmu.edu To: manet@ietf.org Subject: RE: [manet] Security model in MANETs In-Reply-To: <20030511140457.92273.qmail@web41810.mail.yahoo.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: , Jyothi, Our papers are at http://www.monarch.cs.rice.edu/papers.html I also have ns implementations of Ariadne and SEAD at http://www.monarch.cs.rice.edu/software.html Hope this helps, Yih-Chun >> Hi everybody, >> I am a beginner to NS2. I am doing work in key >> management for MANETs.I request all of you to send >> any info regarding security issues for MANETs and >> also about NS2. >> Thanking in advance >> Jyothi B.S. >> > > >__________________________________________________ >Yahoo! Plus >For a better Internet experience >http://www.yahoo.co.uk/btoffer >_______________________________________________ >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 May 12 00:11:10 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18986 for ; Mon, 12 May 2003 00:11:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4C3aV308430 for manet-archive@odin.ietf.org; Sun, 11 May 2003 23:36: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 h4C3aVB08427 for ; Sun, 11 May 2003 23:36:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18979 for ; Mon, 12 May 2003 00:10:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F4g2-0004UX-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 00:12:38 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19F4g1-0004UU-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 00:12:37 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4C3NMB07779; Sun, 11 May 2003 23:23: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 h4C3HjB07659 for ; Sun, 11 May 2003 23:17:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18604 for ; Sun, 11 May 2003 23:51:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F4Ns-0004OL-00 for manet@ietf.org; Sun, 11 May 2003 23:53:52 -0400 Received: from den.erg.sri.com ([128.18.100.23]) by ietf-mx with esmtp (Exim 4.12) id 19F4Nr-0004O8-00 for manet@ietf.org; Sun, 11 May 2003 23:53:52 -0400 Received: from den.erg.sri.com (localhost [127.0.0.1]) by den.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id UAA08334; Sun, 11 May 2003 20:54:14 -0700 (PDT) Message-Id: <200305120354.UAA08334@den.erg.sri.com> To: "Philippe Jacquet" cc: manet@ietf.org Reply-To: ogier@erg.sri.com From: ogier@erg.sri.com Subject: Re: [manet] OSPF in MANETs In-reply-to: Your message of "Fri, 09 May 2003 11:55:26 +0200." Date: Sun, 11 May 2003 20:54:14 -0700 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Philippe, > Hello, > > Even in a static network, OSPF may experience problems. > > During a link state period update an OSPF network must exchange (M*N)**2 > node identifiers where N is the number of nodes and M the average number of > links (neighbors) per node. Each node must flood an LSA message, each LSA > message contains in average M links, each LSA message must be sent and > acknowledged on all links in the network (ie M*N times). This broadcast > storm in general makes the network collapsing when the number of nodes > exceeds few dozens. First, OSPF sends updates reliably, and therefore does not strictly need to generate periodic updates, although it does this occasionally to add robustness. Therefore, the update period can be much longer than for OLSR (for example) in static networks. Thus, the use of reliable updates can be a big advantage in static networks. Second, most people who implement OSPF in MANETs do not use "link broadcast", i.e., they do not unicast each LSA on each link; they use "node broadcast", i.e., each node sends an LSA to all neighbors using a single local broadcast. Each neighbor must ACK the LSA, but ACKs are smaller and can be aggregated, and can often be implicit. With node broadcast, we get M*N**2 overhead per period instead of (M*N)**2. > > In a dynamic network, should not the overhead be mu*M*N**2 if the broadcast > is a link broadcast? Maybe there is some confusion with mu. We must assume that mu is the breakage rate per link and not per node (since otherwise mu depends on M). Thus, the breakage rate per node is mu*M. Since OSPF sends only "full" updates (even if only one link breaks), to get the overhead in a dynamic network, we multiply mu*M by M*N**2, which gives mu*(M*N)**2. However, OSPF has a minimum time MinLSInterval between originations of a particular LSA, so the updates will become periodic if mu is large enough. > > In MANET word, OLSR looks the closest to OSPF. It was made originally to > improve the link state update overhead in a MANET network. The broadcast is > made by MPR nodes and via node broadcasts not ink broadcast (i.e. message > are send only once, not sent separately on each link). The LSA may be > limited to a subset of links (the MPR selector links). These policies > drastically reduce the overhead. I agree that the concept of MPRs can be used to reduce the overhead of OSPF. But there are many questions and issues. One of them regards the concept of "adjacency" in OSPF. A link (u,v) can be used for routing only if it is an adjacency, which requires u and v to synchronize their databases. Since different nodes report different LSAs when MPRs are used, it is not clear how to form adjacencies when MPRs are used. In OLSR, no such synchronization is required. As a result, it is possible for node i to forward a packet to neighbor j to get to destination u, even though node j might not (yet) know of a path to node u. Another question is how to compute MPRs in OSPF (e.g., TBRPF computes MPRs differently from OLSR). Also, MPRs might not be the best way to reduce overhead in OSPF. Richard > > The next step could be to design a wireless extension of OSPF that could fit > MANET requirements in an hybrid network. > > Philippe > > > ----- Original Message ----- > From: Pete Sholander > To: ; > Sent: Thursday, May 08, 2003 6:34 PM > Subject: Re: [manet] OSPF in MANETs > > > > William, > > > > This (IMHO) is a good reference on protocol scaling ... > > > > C. Santivanez, "Asymptotic Behavior of Mobile Ad hoc Routing Protocols > > with respect to Traffic, Mobility and Size", Northeastern University > > CDSP Tech. Report TR-CDSP-00-52, Oct. 2000. > > > > (I think he also published some refereed papers on this topic in the > > past few years, while at BBN. Try google.com) > > > > The short answer to your questions though is that the O(N) overhead > > roughly scales as (mu)*N**2, where N is the number of nodes and mu is > > the "link breakage rate", which may be caused by either mobility or RF > > effects. > > > > So, OSPF may work fine in some MANETs depending on the relative ratios > > of number of nodes, link breakage rates, and the wireless links speeds. > > Unmodified OSPFv1 and OSPFv2 are known to work poorly in typical > > military networks. (I'm not aware of any real-world experimental > > results for the newer OSPFv3. Other posters may ...) > > > > Hope this helps! > > > > --Pete Sholander > > > > >>> "William Lee" 05/08/03 11:56AM >>> > > > > Are their any disadvantages of using OSPF in a MANET, particularly if > > the > > network is not very dynamic? How does the performance of OSPF change > > as > > node mobility increases? How does it change if only the links are > > transient, > > but mobility is minimal? > > > > William Lee > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 00:32:40 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19344 for ; Mon, 12 May 2003 00:32:40 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4C3w2o09955 for manet-archive@odin.ietf.org; Sun, 11 May 2003 23:58: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 h4C3w2B09952 for ; Sun, 11 May 2003 23:58:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19310 for ; Mon, 12 May 2003 00:32:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F50q-0004Zm-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 00:34:08 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19F50q-0004Zj-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 00:34:08 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4C3l3B09593; Sun, 11 May 2003 23:47: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 h4C3g2B09485 for ; Sun, 11 May 2003 23:42:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19037 for ; Mon, 12 May 2003 00:16:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F4lN-0004VL-00 for manet@ietf.org; Mon, 12 May 2003 00:18:09 -0400 Received: from den.erg.sri.com ([128.18.100.23]) by ietf-mx with esmtp (Exim 4.12) id 19F4lM-0004V8-00 for manet@ietf.org; Mon, 12 May 2003 00:18:08 -0400 Received: from den.erg.sri.com (localhost [127.0.0.1]) by den.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id VAA08388; Sun, 11 May 2003 21:11:08 -0700 (PDT) Message-Id: <200305120411.VAA08388@den.erg.sri.com> To: Joe Macker cc: manet@ietf.org Reply-To: ogier@erg.sri.com From: ogier@erg.sri.com Subject: Re: [manet] OSPF in MANETs In-reply-to: Your message of "Fri, 09 May 2003 10:41:50 EDT." <5.1.1.5.2.20030509102626.014e9ea8@pop.itd.nrl.navy.mil> Date: Sun, 11 May 2003 21:11:08 -0700 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Joe, > >Are their any disadvantages of using OSPF in a MANET, particularly if the network is not very dynami c? How does the performance of OSPF change as node mobility increases? How does it change if only the links are transient, but mobility is minimal? > > Some manet-ish extensions to OSPF would help scalability and dynamic, wireless performance... > There is a good niche of applications for this type of capability. > > We have discussed this at various times in the past and several of us have supported strawman proposa ls. There is a set of efforts exploring concepts at the present time. I, for one, believe we could ha ve a focused engineering effort here. Can you list the candidate strawman proposals for MANET extensions to OSPF? Also, if possible, can you list the "set of efforts" that you mention? I know about some of the work Fred Baker has done in this area, but it would be nice to get more complete and up-to-date information on the candidate proposals. Richard > > -Joe > > > _______________________________________________ > 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 May 12 01:57:45 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20470 for ; Mon, 12 May 2003 01:57:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4C5N9u15318 for manet-archive@odin.ietf.org; Mon, 12 May 2003 01:23: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 h4C5N9B15315 for ; Mon, 12 May 2003 01:23:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20467 for ; Mon, 12 May 2003 01:57:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F6LC-0004vY-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 01:59:14 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19F6LB-0004vV-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 01:59:13 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4C5DkB14809; Mon, 12 May 2003 01:13: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 h4C58mB14541 for ; Mon, 12 May 2003 01:08:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20136 for ; Mon, 12 May 2003 01:42:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F67J-0004pB-00 for manet@ietf.org; Mon, 12 May 2003 01:44:53 -0400 Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx with esmtp (Exim 4.12) id 19F67I-0004p8-00 for manet@ietf.org; Mon, 12 May 2003 01:44:52 -0400 Received: from il06exr04.mot.com (il06exr04.mot.com [129.188.137.134]) by motgate5.mot.com (Motorola/Motgate5) with ESMTP id h4C5jrp2013526 for ; Sun, 11 May 2003 22:45:53 -0700 (MST) Received: from xover.corp.mot.com (xover.corp.mot.com [10.1.148.18]) by il06exr04.mot.com (Motorola/il06exr04) with ESMTP id h4C5jpQx022128 for ; Mon, 12 May 2003 00:45:52 -0500 Received: by xover.corp.mot.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 May 2003 01:45:38 -0400 Message-ID: From: "Manral, Vishwas" To: "'ogier@erg.sri.com'" , Philippe Jacquet , "'gchoudhury@ATT.COM'" Cc: manet@ietf.org Subject: RE: [manet] OSPF in MANETs Date: Mon, 12 May 2003 01:22:05 -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: , Hi Philippe/Richard, We did do some simulations of various flooding algorithms on OSPF in wireline networks and measured flooding load based on that. Although different this could be of some relevence in this discussion. Thanks, Vishwas -----Original Message----- From: ogier@erg.sri.com [mailto:ogier@erg.sri.com] Sent: Monday, May 12, 2003 9:24 AM To: Philippe Jacquet Cc: manet@ietf.org Subject: Re: [manet] OSPF in MANETs Philippe, > Hello, > > Even in a static network, OSPF may experience problems. > > During a link state period update an OSPF network must exchange (M*N)**2 > node identifiers where N is the number of nodes and M the average number of > links (neighbors) per node. Each node must flood an LSA message, each LSA > message contains in average M links, each LSA message must be sent and > acknowledged on all links in the network (ie M*N times). This broadcast > storm in general makes the network collapsing when the number of nodes > exceeds few dozens. First, OSPF sends updates reliably, and therefore does not strictly need to generate periodic updates, although it does this occasionally to add robustness. Therefore, the update period can be much longer than for OLSR (for example) in static networks. Thus, the use of reliable updates can be a big advantage in static networks. Second, most people who implement OSPF in MANETs do not use "link broadcast", i.e., they do not unicast each LSA on each link; they use "node broadcast", i.e., each node sends an LSA to all neighbors using a single local broadcast. Each neighbor must ACK the LSA, but ACKs are smaller and can be aggregated, and can often be implicit. With node broadcast, we get M*N**2 overhead per period instead of (M*N)**2. > > In a dynamic network, should not the overhead be mu*M*N**2 if the broadcast > is a link broadcast? Maybe there is some confusion with mu. We must assume that mu is the breakage rate per link and not per node (since otherwise mu depends on M). Thus, the breakage rate per node is mu*M. Since OSPF sends only "full" updates (even if only one link breaks), to get the overhead in a dynamic network, we multiply mu*M by M*N**2, which gives mu*(M*N)**2. However, OSPF has a minimum time MinLSInterval between originations of a particular LSA, so the updates will become periodic if mu is large enough. > > In MANET word, OLSR looks the closest to OSPF. It was made originally to > improve the link state update overhead in a MANET network. The broadcast is > made by MPR nodes and via node broadcasts not ink broadcast (i.e. message > are send only once, not sent separately on each link). The LSA may be > limited to a subset of links (the MPR selector links). These policies > drastically reduce the overhead. I agree that the concept of MPRs can be used to reduce the overhead of OSPF. But there are many questions and issues. One of them regards the concept of "adjacency" in OSPF. A link (u,v) can be used for routing only if it is an adjacency, which requires u and v to synchronize their databases. Since different nodes report different LSAs when MPRs are used, it is not clear how to form adjacencies when MPRs are used. In OLSR, no such synchronization is required. As a result, it is possible for node i to forward a packet to neighbor j to get to destination u, even though node j might not (yet) know of a path to node u. Another question is how to compute MPRs in OSPF (e.g., TBRPF computes MPRs differently from OLSR). Also, MPRs might not be the best way to reduce overhead in OSPF. Richard > > The next step could be to design a wireless extension of OSPF that could fit > MANET requirements in an hybrid network. > > Philippe > > > ----- Original Message ----- > From: Pete Sholander > To: ; > Sent: Thursday, May 08, 2003 6:34 PM > Subject: Re: [manet] OSPF in MANETs > > > > William, > > > > This (IMHO) is a good reference on protocol scaling ... > > > > C. Santivanez, "Asymptotic Behavior of Mobile Ad hoc Routing Protocols > > with respect to Traffic, Mobility and Size", Northeastern University > > CDSP Tech. Report TR-CDSP-00-52, Oct. 2000. > > > > (I think he also published some refereed papers on this topic in the > > past few years, while at BBN. Try google.com) > > > > The short answer to your questions though is that the O(N) overhead > > roughly scales as (mu)*N**2, where N is the number of nodes and mu is > > the "link breakage rate", which may be caused by either mobility or RF > > effects. > > > > So, OSPF may work fine in some MANETs depending on the relative ratios > > of number of nodes, link breakage rates, and the wireless links speeds. > > Unmodified OSPFv1 and OSPFv2 are known to work poorly in typical > > military networks. (I'm not aware of any real-world experimental > > results for the newer OSPFv3. Other posters may ...) > > > > Hope this helps! > > > > --Pete Sholander > > > > >>> "William Lee" 05/08/03 11:56AM >>> > > > > Are their any disadvantages of using OSPF in a MANET, particularly if > > the > > network is not very dynamic? How does the performance of OSPF change > > as > > node mobility increases? How does it change if only the links are > > transient, > > but mobility is minimal? > > > > William Lee > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 03:09:17 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03868 for ; Mon, 12 May 2003 03:09:17 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4C6Yhu31087 for manet-archive@odin.ietf.org; Mon, 12 May 2003 02:34: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 h4C6YgB31084 for ; Mon, 12 May 2003 02:34:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03849 for ; Mon, 12 May 2003 03:08:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F7SQ-0005gL-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 03:10:46 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19F7SP-0005gI-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 03:10:45 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4C6KkB29722; Mon, 12 May 2003 02:20: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 h4C6FGB29459 for ; Mon, 12 May 2003 02:15:16 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03415 for ; Mon, 12 May 2003 02:49:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F79b-0005YG-00 for manet@ietf.org; Mon, 12 May 2003 02:51:19 -0400 Received: from motgate6.mot.com ([144.189.100.106]) by ietf-mx with esmtp (Exim 4.12) id 19F79a-0005Y7-00 for manet@ietf.org; Mon, 12 May 2003 02:51:18 -0400 Received: from il06exr02.mot.com (il06exr02.mot.com [129.188.137.132]) by motgate6.mot.com (Motorola/Motgate6) with ESMTP id h4C6qKq2019384 for ; Sun, 11 May 2003 23:52:20 -0700 (MST) Received: from xover.corp.mot.com (xover.corp.mot.com [10.1.148.18]) by il06exr02.mot.com (Motorola/il06exr02) with ESMTP id h4C6qI2J019052 for ; Mon, 12 May 2003 01:52:18 -0500 Received: by xover.corp.mot.com with Internet Mail Service (5.5.2653.19) id ; Mon, 12 May 2003 02:52:05 -0400 Message-ID: From: "Manral, Vishwas" To: "'ogier@erg.sri.com'" , "'Philippe Jacquet'" , "'gchoudhury@ATT.COM'" Cc: "'manet@ietf.org'" Subject: RE: [manet] OSPF in MANETs Date: Mon, 12 May 2003 02:53:41 -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: , Just to add we did use a variant of MRP in one of the simulations. The link to the document is http://www.ietf.org/internet-drafts/draft-choudhury-manral-flooding-simulati on-00.txt Thanks, Vishwas -----Original Message----- From: Manral, Vishwas Sent: Monday, May 12, 2003 10:52 AM To: 'ogier@erg.sri.com'; Philippe Jacquet; 'gchoudhury@ATT.COM' Cc: manet@ietf.org Subject: RE: [manet] OSPF in MANETs Hi Philippe/Richard, We did do some simulations of various flooding algorithms on OSPF in wireline networks and measured flooding load based on that. Although different this could be of some relevence in this discussion. Thanks, Vishwas -----Original Message----- From: ogier@erg.sri.com [mailto:ogier@erg.sri.com] Sent: Monday, May 12, 2003 9:24 AM To: Philippe Jacquet Cc: manet@ietf.org Subject: Re: [manet] OSPF in MANETs Philippe, > Hello, > > Even in a static network, OSPF may experience problems. > > During a link state period update an OSPF network must exchange (M*N)**2 > node identifiers where N is the number of nodes and M the average number of > links (neighbors) per node. Each node must flood an LSA message, each LSA > message contains in average M links, each LSA message must be sent and > acknowledged on all links in the network (ie M*N times). This broadcast > storm in general makes the network collapsing when the number of nodes > exceeds few dozens. First, OSPF sends updates reliably, and therefore does not strictly need to generate periodic updates, although it does this occasionally to add robustness. Therefore, the update period can be much longer than for OLSR (for example) in static networks. Thus, the use of reliable updates can be a big advantage in static networks. Second, most people who implement OSPF in MANETs do not use "link broadcast", i.e., they do not unicast each LSA on each link; they use "node broadcast", i.e., each node sends an LSA to all neighbors using a single local broadcast. Each neighbor must ACK the LSA, but ACKs are smaller and can be aggregated, and can often be implicit. With node broadcast, we get M*N**2 overhead per period instead of (M*N)**2. > > In a dynamic network, should not the overhead be mu*M*N**2 if the broadcast > is a link broadcast? Maybe there is some confusion with mu. We must assume that mu is the breakage rate per link and not per node (since otherwise mu depends on M). Thus, the breakage rate per node is mu*M. Since OSPF sends only "full" updates (even if only one link breaks), to get the overhead in a dynamic network, we multiply mu*M by M*N**2, which gives mu*(M*N)**2. However, OSPF has a minimum time MinLSInterval between originations of a particular LSA, so the updates will become periodic if mu is large enough. > > In MANET word, OLSR looks the closest to OSPF. It was made originally to > improve the link state update overhead in a MANET network. The broadcast is > made by MPR nodes and via node broadcasts not ink broadcast (i.e. message > are send only once, not sent separately on each link). The LSA may be > limited to a subset of links (the MPR selector links). These policies > drastically reduce the overhead. I agree that the concept of MPRs can be used to reduce the overhead of OSPF. But there are many questions and issues. One of them regards the concept of "adjacency" in OSPF. A link (u,v) can be used for routing only if it is an adjacency, which requires u and v to synchronize their databases. Since different nodes report different LSAs when MPRs are used, it is not clear how to form adjacencies when MPRs are used. In OLSR, no such synchronization is required. As a result, it is possible for node i to forward a packet to neighbor j to get to destination u, even though node j might not (yet) know of a path to node u. Another question is how to compute MPRs in OSPF (e.g., TBRPF computes MPRs differently from OLSR). Also, MPRs might not be the best way to reduce overhead in OSPF. Richard > > The next step could be to design a wireless extension of OSPF that could fit > MANET requirements in an hybrid network. > > Philippe > > > ----- Original Message ----- > From: Pete Sholander > To: ; > Sent: Thursday, May 08, 2003 6:34 PM > Subject: Re: [manet] OSPF in MANETs > > > > William, > > > > This (IMHO) is a good reference on protocol scaling ... > > > > C. Santivanez, "Asymptotic Behavior of Mobile Ad hoc Routing Protocols > > with respect to Traffic, Mobility and Size", Northeastern University > > CDSP Tech. Report TR-CDSP-00-52, Oct. 2000. > > > > (I think he also published some refereed papers on this topic in the > > past few years, while at BBN. Try google.com) > > > > The short answer to your questions though is that the O(N) overhead > > roughly scales as (mu)*N**2, where N is the number of nodes and mu is > > the "link breakage rate", which may be caused by either mobility or RF > > effects. > > > > So, OSPF may work fine in some MANETs depending on the relative ratios > > of number of nodes, link breakage rates, and the wireless links speeds. > > Unmodified OSPFv1 and OSPFv2 are known to work poorly in typical > > military networks. (I'm not aware of any real-world experimental > > results for the newer OSPFv3. Other posters may ...) > > > > Hope this helps! > > > > --Pete Sholander > > > > >>> "William Lee" 05/08/03 11:56AM >>> > > > > Are their any disadvantages of using OSPF in a MANET, particularly if > > the > > network is not very dynamic? How does the performance of OSPF change > > as > > node mobility increases? How does it change if only the links are > > transient, > > but mobility is minimal? > > > > William Lee > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 05:11:53 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05983 for ; Mon, 12 May 2003 05:11:53 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4C8bKb08041 for manet-archive@odin.ietf.org; Mon, 12 May 2003 04:37: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 h4C8bKB08038 for ; Mon, 12 May 2003 04:37:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05978 for ; Mon, 12 May 2003 05:11:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F9N2-0006FF-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 05:13:20 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19F9N2-0006FC-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 05:13:20 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4C8RNB07069; Mon, 12 May 2003 04:27: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 h4C8NrB06950 for ; Mon, 12 May 2003 04:23:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05639 for ; Mon, 12 May 2003 04:57:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19F9A2-00069w-00 for manet@ietf.org; Mon, 12 May 2003 04:59:54 -0400 Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx with esmtp (Exim 4.12) id 19F9A1-00069t-00 for manet@ietf.org; Mon, 12 May 2003 04:59:53 -0400 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h4C90sl26572 for ; Mon, 12 May 2003 11:00:54 +0200 (MEST) Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99]) by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h4C90ra14382 for ; Mon, 12 May 2003 11:00:54 +0200 (MEST) Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19) id ; Mon, 12 May 2003 11:00:53 +0200 Message-ID: <12D31B803B18D4119958009027FD42B80405D28F@mchp952a.mch.sbs.de> From: Bahr Michael To: manet@ietf.org Date: Mon, 12 May 2003 11:00:50 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [manet] Sequence Number for Gateway Nodes in AODV Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello, I'm refering to draft-ietf-manet-aodv-13, section 8. This section is about using AODV with other networks (usually called AODV with gateway node). The draft says, that "This includes the need for maintaining a destination sequence number for that external subnet." Since the only necessary property of the destination sequence number is the monotonous increase of its value, it is not necessary to have more than one destination sequence number at the AODV gateway node. This means, the external subnet uses the same destination sequence number variable as the AODV gateway node uses for its own paths. Maybe, I've missed something. Best regards, Michael Bahr Siemens AG Corporate Technology Munich, Germany _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 07:53:15 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09410 for ; Mon, 12 May 2003 07:53:15 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CBIkM19348 for manet-archive@odin.ietf.org; Mon, 12 May 2003 07:18: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 h4CBIjB19344 for ; Mon, 12 May 2003 07:18:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09396 for ; Mon, 12 May 2003 07:52:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FBtD-00075t-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 07:54:43 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FBtC-00075q-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 07:54:42 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CB8sB18888; Mon, 12 May 2003 07:08: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 h4CB5vB17937 for ; Mon, 12 May 2003 07:05:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09056 for ; Mon, 12 May 2003 07:39:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FBgo-00071E-00 for manet@ietf.org; Mon, 12 May 2003 07:41:54 -0400 Received: from inet-tsb.toshiba.co.jp ([202.33.96.40]) by ietf-mx with esmtp (Exim 4.12) id 19FBgn-00071B-00 for manet@ietf.org; Mon, 12 May 2003 07:41:53 -0400 Received: from tsb-wall.toshiba.co.jp ([133.199.160.134]) by inet-tsb.toshiba.co.jp with ESMTP id h4CBgsVj020686; Mon, 12 May 2003 20:42:54 +0900 (JST) Received: (from root@localhost) by tsb-wall.toshiba.co.jp id h4CBgsGu009761; Mon, 12 May 2003 20:42:54 +0900 (JST) Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id WAA09758 ; Mon, 12 May 2003 20:42:54 +0900 Received: from mx4.toshiba.co.jp by tis2.tis.toshiba.co.jp id UAA22169; Mon, 12 May 2003 20:42:54 +0900 (JST) Received: from isl.rdc.toshiba.co.jp by toshiba.co.jp id UAA17763; Mon, 12 May 2003 20:42:53 +0900 (JST) Received: from localhost (inoue@flowerpark [133.196.16.25]) by isl.rdc.toshiba.co.jp (8.11.7/8.11.6/1.4) with ESMTP id h4CBgqj08310; Mon, 12 May 2003 20:42:52 +0900 (JST) To: nemo@nal.motlabs.com, manet@ietf.org, mobile-ip@sunroof.eng.sun.com, pana@research.telcordia.com In-Reply-To: Your message of "Fri, 09 May 2003 10:39:12 +0900" <4.2.0.58.J.20030509103119.047acc78@localhost> References: <4.2.0.58.J.20030509103119.047acc78@localhost> X-Mailer: Mew version 1.93 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20030512204252N.inoue@isl.rdc.toshiba.co.jp> Date: Mon, 12 May 2003 20:42:52 +0900 From: Atsushi Inoue X-Dispatcher: imput version 980905(IM100) Lines: 85 Content-Transfer-Encoding: 7bit Subject: [manet] CFP:: First International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2004) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit (Apologies if you receive multiple copies) CALL FOR PAPERS =============== First International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2004) January 8 and 9, 2004 NTT DoCoMo R&D Center, Yokosuka Rsearch Park, Yokosuka, JAPAN http://www.ipsj.or.jp/sig/mbl/icmu2004/ Deadline for submissions: August 1 2003 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Co-sponsored by IPSJ SIG-MBL (Informaiton Processing Society of Japan, Special Interest Group of Mobile Computing and Ubiquitous Networking) and IPSJ SG-BCC (Study Group of Broadcast Communicaiton and Computing) Scope: ~~~~~~ Mobile computing aims at ubiquitous user access to computer application. To make it possible, networking technology which enables Internet access anytime and everywhere, i.e. ubiquitous networking is necessary. It is obvious that with the accelerating trends towards mobile networks, ad-hoc networks, and wireless networks, mobile computing and ubiquitous networking will play an important role in future network. This conference is aimed at providing researchers and practitioners in this hot research area a forum for discussion and collaboration. Authors are invited to submit papers addressing, but not limited to, the following topics: - Applications and services for mobile computing - Network architectures, protocols, or service models for ubiquitous networking - Network management for ubiquitous networking - Data management for mobile computing - Security in mobile computing and ubiquitous networking - Wireless and mobile communications - Nomadic computing - Ad-hoc networks - Mobile Internetworking - Performance evaluation for mobile computing and ubiquitous networking systems - Broadcast communication Submission Instructions: ~~~~~~~~~~~~~~~~~~~~~~~~ Papers are solicited as full papers of no more than 6 pages, each of which will be subject to a full review process. Submission should already follow the author guidelines as specified in the web site below. An electronic, PDF-based submission of papers is mandatory. Please check Submission Guideline (http://www.ipsj.or.jp/sig/mbl/icmu2004/guide.html) for further submission instructions. Important Dates: ~~~~~~~~~~~~~~~~ - Deadline for submissions August 1, 2003 - Notification of acceptance October 1, 2003 - Camera ready due November 1, 2003 - Conference January 8-9, 2004 Location and Date: ~~~~~~~~~~~~~~~~~~ The location of the NTT DoCoMo R&D Center is in the heart of Yokosuka Research Park(YRP) where a lot of wireless communication related research institutes are established. YRP is really the heart of wireless communications research in Japan. Japanese old city Kamakura, a famous historic city, is 30 minutes by train. Beginning of the year is one of the best seasons for visiting Japan. You can also get PDF version of Call for Papers from http://www.ipsj.or.jp/sig/mbl/icmu2004/cfp-icmu2004.pdf -- inoue@toshiba Atsushi Inoue # Phone: +81-44-549-2065 Communication Platform Lab. # Fax: +81-44-520-1806 TOSHIBA R&D Center # inoue@isl.rdc.toshiba.co.jp _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 10:11:49 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13702 for ; Mon, 12 May 2003 10:11:49 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CDbM730016 for manet-archive@odin.ietf.org; Mon, 12 May 2003 09:37: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 h4CDbMB30013 for ; Mon, 12 May 2003 09:37:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13661 for ; Mon, 12 May 2003 10:11:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FE3I-0000Fq-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 10:13:16 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FE3H-0000Fn-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 10:13:15 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CDPKB28476; Mon, 12 May 2003 09:25: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 h4CDI4B28071 for ; Mon, 12 May 2003 09:18:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12227 for ; Mon, 12 May 2003 09:51:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FDkc-00000s-00 for manet@ietf.org; Mon, 12 May 2003 09:53:58 -0400 Received: from web40704.mail.yahoo.com ([66.218.78.161]) by ietf-mx with smtp (Exim 4.12) id 19FDkc-00000P-00 for manet@ietf.org; Mon, 12 May 2003 09:53:58 -0400 Message-ID: <20030512135430.70812.qmail@web40704.mail.yahoo.com> Received: from [129.10.110.140] by web40704.mail.yahoo.com via HTTP; Mon, 12 May 2003 06:54:30 PDT Date: Mon, 12 May 2003 06:54:30 -0700 (PDT) From: feng zhu Subject: RE: [manet] Security model in MANETs To: l s , Herbert Rubens , manet@ietf.org In-Reply-To: <20030511140457.92273.qmail@web41810.mail.yahoo.com> 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, Thank you for your interest in my web page. But, I am sorry, as I said in my web page, those links in that page are for local use only because of copyright issue. But, if there is a link to a certain paper, it means that I can find and download it somewhere. So, usually, you can also do the same thing, I mean, find the paper by using any search engine and download it from web. BTW, --If you know of any papers concerning security for ad hoc networks that are not listed here, please let me know --If you know the citation for some papers or you found some errors in the list, please let me know. --If you have any suggestion or comments, please let me know. Thank you. Best, --Feng --- l s wrote: > Herb, > > Thanks, this is very useful to me too, however 99% > of > links give a '404 Not Found' in: > http://www.ccs.neu.edu/papers/ > I guess they are not globally viewable. > > cheers, > Lee -S- > CCSR > Uni of Surrey > UK > > > > --- Herbert Rubens wrote: > > This should get you started: > > > > > http://www.ccs.neu.edu/home/zhufeng/security_manet.html > > > > > > -Herb > > > > > > -----Original Message----- > > From: manet-admin@ietf.org > > [mailto:manet-admin@ietf.org] On Behalf Of > > jyothi_017 > > Sent: Saturday, May 10, 2003 2:17 PM > > To: manet@ietf.org > > Subject: [manet] Security model in MANETs > > > > Hi everybody, > > I am a beginner to NS2. I am doing work in key > > management for MANETs.I request all of you to send > > any info regarding security issues for MANETs and > > also about NS2. > > Thanking in advance > > Jyothi B.S. > > > > > __________________________________________________ > Yahoo! Plus > For a better Internet experience > http://www.yahoo.co.uk/btoffer > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet ===== ============================== ZHU, Feng zf_manet@yahoo.com http://www.ccs.neu.edu/home/zhufeng/security_manet.html __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 10:11:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13731 for ; Mon, 12 May 2003 10:11:59 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CDbWG30235 for manet-archive@odin.ietf.org; Mon, 12 May 2003 09:37:32 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CDbOB30033 for ; Mon, 12 May 2003 09:37:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13669 for ; Mon, 12 May 2003 10:11:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FE3K-0000Fw-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 10:13:18 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FE3K-0000Ft-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 10:13:18 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CDRfB28575; Mon, 12 May 2003 09:27: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 h4CDIsB28141 for ; Mon, 12 May 2003 09:18:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12259 for ; Mon, 12 May 2003 09:52:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FDlQ-000019-00 for manet@ietf.org; Mon, 12 May 2003 09:54:48 -0400 Received: from smtp03.uc3m.es ([163.117.136.123] helo=smtp.uc3m.es) by ietf-mx with esmtp (Exim 4.12) id 19FDlQ-00000w-00 for manet@ietf.org; Mon, 12 May 2003 09:54:48 -0400 Received: from smtp03.uc3m.es (localhost [127.0.0.1]) by smtp.uc3m.es (Postfix) with ESMTP id E4CA2433D6 for ; Mon, 12 May 2003 15:55:15 +0200 (CEST) Received: from varpa.it.uc3m.es (varpa.it.uc3m.es [163.117.139.253]) by smtp03.uc3m.es (Postfix) with ESMTP id D923E2B667 for ; Mon, 12 May 2003 15:55:15 +0200 (CEST) Received: from pandora (pandora.it.uc3m.es [163.117.139.89]) by varpa.it.uc3m.es (8.9.3/8.9.3/Debian 8.9.3-21) with SMTP id PAA32086 for ; Mon, 12 May 2003 15:55:07 +0200 X-Authentication-Warning: varpa.it.uc3m.es: Host pandora.it.uc3m.es [163.117.139.89] claimed to be pandora Message-ID: <01c201c3188e$2f77d130$598b75a3@pandora> From: =?iso-8859-1?Q?Carlos_Garc=EDa?= To: Date: Mon, 12 May 2003 15:55:43 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Subject: [manet] CEDAR Question Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 have read some papers about CEDAR, but I don't how does it really works. As long as I know, when some node wants to calculate a route from source to destination, then the source dominator sends a message (dom(s), dom(d), b, PATH). Any core node that takes this message adds itself to the PATH until the message reach the destination dominator. So .... this means that every packet carries the PATH that it will follow through the manet to reach the destination???? It will be very useful if you could help me. Thank you very much, Carlos _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 10:14:39 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14008 for ; Mon, 12 May 2003 10:14:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CDeB630662 for manet-archive@odin.ietf.org; Mon, 12 May 2003 09:40: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 h4CDeBB30659 for ; Mon, 12 May 2003 09:40:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13962 for ; Mon, 12 May 2003 10:14:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FE61-0000HB-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 10:16:06 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FE61-0000H8-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 10:16:05 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CDUTB28870; Mon, 12 May 2003 09: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 h4CDOtB28440 for ; Mon, 12 May 2003 09:24:55 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12606 for ; Mon, 12 May 2003 09:58:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FDrF-00005y-00 for manet@ietf.org; Mon, 12 May 2003 10:00:49 -0400 Received: from isis.lip6.fr ([132.227.60.2] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19FDrE-00005u-00 for manet@ietf.org; Mon, 12 May 2003 10:00:49 -0400 Received: from tibre.lip6.fr (tibre.lip6.fr [132.227.74.2]) by isis.lip6.fr (8.12.9/jtpda-5.4+victor) with ESMTP id h4CE1oA8028218 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 12 May 2003 16:01:50 +0200 X-pt: isis.lip6.fr Received: from ancee (ancee [132.227.61.74]) by tibre.lip6.fr (8.11.6p2/8.11.6) with ESMTP id h4CE1ob18307 for ; Mon, 12 May 2003 16:01:50 +0200 (CEST) Subject: [manet] Geographical Routing Protocols under NS-2 From: Erwan Ermel Reply-To: erwan.ermel@lip6.fr To: manet@ietf.org In-Reply-To: <20030512204252N.inoue@isl.rdc.toshiba.co.jp> References: <4.2.0.58.J.20030509103119.047acc78@localhost> <20030512204252N.inoue@isl.rdc.toshiba.co.jp> Content-Type: text/plain Message-Id: <1052748109.1995.10.camel@ancee> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-4) Date: 12 May 2003 16:01:50 +0200 Content-Transfer-Encoding: 7bit X-Scanned-By: isis.lip6.fr 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'm looking for geographical routing protocols codes under NS-2 (running codes). Thanks in advance. Regards. Erwan _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 13:09:12 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24288 for ; Mon, 12 May 2003 13:09:11 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CGYnY12933 for manet-archive@odin.ietf.org; Mon, 12 May 2003 12:34: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 h4CGYmB12929 for ; Mon, 12 May 2003 12:34:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24254 for ; Mon, 12 May 2003 13:08:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FGox-0002nu-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 13:10:39 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FGow-0002nr-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 13:10:38 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CFCkB07109; Mon, 12 May 2003 11:12: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 h4CF5NB05940 for ; Mon, 12 May 2003 11:05:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21310 for ; Mon, 12 May 2003 11:39:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FFQS-0002C6-00 for manet@ietf.org; Mon, 12 May 2003 11:41:16 -0400 Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx with esmtp (Exim 4.12) id 19FFQR-0002C2-00 for manet@ietf.org; Mon, 12 May 2003 11:41:15 -0400 Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h4CFgHW20494; Mon, 12 May 2003 17:42:17 +0200 (MEST) Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99]) by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h4CFgHG03661; Mon, 12 May 2003 17:42:17 +0200 (MEST) Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19) id ; Mon, 12 May 2003 17:42:16 +0200 Message-ID: <12D31B803B18D4119958009027FD42B80405D2DD@mchp952a.mch.sbs.de> From: Bahr Michael To: "Sudanthi, Sudha (Sudha)" Cc: manet@ietf.org Subject: AW: [manet] Sequence Number for Gateway Nodes in AODV Date: Mon, 12 May 2003 17:42:15 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4CF5OB05941 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h4CFCkB07109 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4CGYmB12929 Content-Transfer-Encoding: 8bit Sudha, Thank you for your reply. I realized my question was a little bit misleading. Since an external network has to be handled as any other MANET node in the routing tables, there has to be a sequence number for it. My actual question was, whether it is necessary to maintain two separate sequence number _counters_ at the gateway node - one for the gateway node as MANET node, and one for the external network. This can not be seen from the the Internet draft. I think, only one sequence number counter is needed, which is used for both the gateway node and the external network. Best regards, Michael Bahr > -----Urspr黱gliche Nachricht----- > Von: Sudanthi, Sudha (Sudha) [mailto:sudanthi@lucent.com] > Gesendet am: Montag, 12. Mai 2003 16:51 > An: Bahr Michael > Betreff: RE: [manet] Sequence Number for Gateway Nodes in AODV > > Michael, > > The external network would be treated as one node and it > would maintain a sequence number for it as it would for any > other node. (A destination sequence number is maintained for > all destinations in its cache.) Therefore, this sentence you > quoted just restates that a destination sequence number must > be maintained for that external subnet...similar to if the > external subnet was just another node... > > Hope that helped...sorry if it didn't... > > -----Original Message----- > From: Bahr Michael [mailto:bahr@siemens.com] > Sent: Monday, May 12, 2003 5:01 AM > To: manet@ietf.org > Subject: [manet] Sequence Number for Gateway Nodes in AODV > > > > > Hello, > > I'm refering to draft-ietf-manet-aodv-13, section 8. This > section is about > using AODV with other networks (usually called AODV with > gateway node). The > draft says, that "This includes the need for maintaining a destination > sequence number for that external subnet." > > Since the only necessary property of the destination sequence > number is the > monotonous increase of its value, it is not necessary to have > more than one > destination sequence number at the AODV gateway node. This means, the > external subnet uses the same destination sequence number > variable as the > AODV gateway node uses for its own paths. > > Maybe, I've missed something. > > > Best regards, > > Michael Bahr > > Siemens AG > Corporate Technology > Munich, Germany > > _______________________________________________ > 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 May 12 14:53:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27706 for ; Mon, 12 May 2003 14:53:08 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CIInt20616 for manet-archive@odin.ietf.org; Mon, 12 May 2003 14:18: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 h4CIImB20612 for ; Mon, 12 May 2003 14:18:48 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27688 for ; Mon, 12 May 2003 14:52:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FIRZ-0003Sf-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 14:54:37 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FIRY-0003Sc-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 14:54:36 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CI3uB19029; Mon, 12 May 2003 14: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 h4CHvUB18806 for ; Mon, 12 May 2003 13:57:30 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26867 for ; Mon, 12 May 2003 14:31:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FI6x-0003Jz-00 for manet@ietf.org; Mon, 12 May 2003 14:33:19 -0400 Received: from pushme.nist.gov ([129.6.16.92] helo=postmark.nist.gov) by ietf-mx with esmtp (Exim 4.12) id 19FI6x-0003Jw-00 for manet@ietf.org; Mon, 12 May 2003 14:33:19 -0400 Received: from gwialo (camelot.antd.nist.gov [129.6.50.51]) by postmark.nist.gov (8.12.5/8.12.5) with ESMTP id h4CIXlbd013375; Mon, 12 May 2003 14:33:47 -0400 (EDT) From: "Luke Klein-Berndt" To: Cc: Date: Mon, 12 May 2003 14:33:47 -0400 Message-ID: <001901c318b5$06703530$33320681@campus.nist.gov> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <12D31B803B18D4119958009027FD42B80405D2DD@mchp952a.mch.sbs.de> Importance: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Subject: [manet] Kernel AODV 2.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: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I have just finished a long delayed update of Kernel AODV, v2.1 Version 2.1 includes: - Better internet gatewaying, fixes problems people were having with it only working for one hop - Basic Multicasting, all multicast packets are now broadcast flooded to everyone - Improved stability, locks have been added around shared areas of code The updated version can be found at: http://w3.antd.nist.gov/wctg/aodv_kernel/kaodv_download.htm Thanks! Luke Klein-Berndt _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 15:40:52 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00744 for ; Mon, 12 May 2003 15:40:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CJ6YP24451 for manet-archive@odin.ietf.org; Mon, 12 May 2003 15:06: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 h4CJ6XB24448 for ; Mon, 12 May 2003 15:06:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00723 for ; Mon, 12 May 2003 15:40:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FJBl-0003ti-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 15:42:21 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FJBk-0003te-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 15:42:20 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CIuSB23359; Mon, 12 May 2003 14:56: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 h4CIlQB22825 for ; Mon, 12 May 2003 14:47:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29736 for ; Mon, 12 May 2003 15:21:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FItG-0003gq-00 for manet@ietf.org; Mon, 12 May 2003 15:23:14 -0400 Received: from pushme.nist.gov ([129.6.16.92] helo=postmark.nist.gov) by ietf-mx with esmtp (Exim 4.12) id 19FItF-0003gm-00 for manet@ietf.org; Mon, 12 May 2003 15:23:13 -0400 Received: from gwialo (camelot.antd.nist.gov [129.6.50.51]) by postmark.nist.gov (8.12.5/8.12.5) with ESMTP id h4CJNqbd010029; Mon, 12 May 2003 15:23:52 -0400 (EDT) From: "Luke Klein-Berndt" To: "'Bahr Michael'" Cc: , Subject: RE: [manet] Sequence Number for Gateway Nodes in AODV Date: Mon, 12 May 2003 15:23:52 -0400 Message-ID: <002101c318bc$05f22760$33320681@campus.nist.gov> 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.4024 In-Reply-To: <12D31B803B18D4119958009027FD42B80405D2DD@mchp952a.mch.sbs.de> Importance: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4CIlRB22826 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h4CIuSB23359 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4CJ6XB24448 Content-Transfer-Encoding: 8bit Hi Michael, This should work in practice, but it might cause some trouble later on down the road. While the most important property of the AODV Dst Seq Num is that it is monotonously increases, I think another important property it that it only increases when the route has been changed. This might mess up some latter enchantment which depends on this. Also if you have two Gateway nodes for the same external networks, some instability might develop. That being said, only having one seq number might make it easier to sync between gateways that have the same external network. -Luke Klein-Berndt > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On > Behalf Of Bahr Michael > Sent: Monday, May 12, 2003 11:42 AM > To: Sudanthi, Sudha (Sudha) > Cc: manet@ietf.org > Subject: AW: [manet] Sequence Number for Gateway Nodes in AODV > > > > Sudha, > > Thank you for your reply. > > I realized my question was a little bit misleading. Since an > external network has to be handled as any other MANET node in > the routing tables, there has to be a sequence number for it. > My actual question was, whether it is necessary to maintain > two separate sequence number _counters_ at the gateway node - > one for the gateway node as MANET node, and one for the > external network. This can not be seen from the the Internet > draft. I think, only one sequence number counter is needed, > which is used for both the gateway node and the external network. > > Best regards, > Michael Bahr > > > -----Urspr黱gliche Nachricht----- > > Von: Sudanthi, Sudha (Sudha) [mailto:sudanthi@lucent.com] > Gesendet am: > > Montag, 12. Mai 2003 16:51 > > An: Bahr Michael > > Betreff: RE: [manet] Sequence Number for Gateway Nodes in AODV > > > > Michael, > > > > The external network would be treated as one node and it > > would maintain a sequence number for it as it would for any > > other node. (A destination sequence number is maintained for > > all destinations in its cache.) Therefore, this sentence you > > quoted just restates that a destination sequence number must > > be maintained for that external subnet...similar to if the > > external subnet was just another node... > > > > Hope that helped...sorry if it didn't... > > > > -----Original Message----- > > From: Bahr Michael [mailto:bahr@siemens.com] > > Sent: Monday, May 12, 2003 5:01 AM > > To: manet@ietf.org > > Subject: [manet] Sequence Number for Gateway Nodes in AODV > > > > > > > > > > Hello, > > > > I'm refering to draft-ietf-manet-aodv-13, section 8. This > > section is about > > using AODV with other networks (usually called AODV with > > gateway node). The > > draft says, that "This includes the need for maintaining a > destination > > sequence number for that external subnet." > > > > Since the only necessary property of the destination sequence > > number is the > > monotonous increase of its value, it is not necessary to have > > more than one > > destination sequence number at the AODV gateway node. This > means, the > > external subnet uses the same destination sequence number > > variable as the > > AODV gateway node uses for its own paths. > > > > Maybe, I've missed something. > > > > > > Best regards, > > > > Michael Bahr > > > > Siemens AG > > Corporate Technology > > Munich, Germany > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 15:45:22 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00989 for ; Mon, 12 May 2003 15:45:22 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CJB4325944 for manet-archive@odin.ietf.org; Mon, 12 May 2003 15:11: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 h4CJB3B25941 for ; Mon, 12 May 2003 15:11:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00979 for ; Mon, 12 May 2003 15:44:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FJG7-0003xm-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 15:46:51 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FJG6-0003xj-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 15:46:50 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CJ1VB23631; Mon, 12 May 2003 15:01: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 h4CIm0B22840 for ; Mon, 12 May 2003 14:48:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29767 for ; Mon, 12 May 2003 15:21:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FIto-0003hM-00 for manet@ietf.org; Mon, 12 May 2003 15:23:48 -0400 Received: from mail.cs.fsu.edu ([128.186.121.245]) by ietf-mx with esmtp (Exim 4.12) id 19FItn-0003h4-00 for manet@ietf.org; Mon, 12 May 2003 15:23:47 -0400 Received: from diablo.cs.fsu.edu (diablo [128.186.121.40]) by mail.cs.fsu.edu (8.12.9/8.12.8) with ESMTP id h4CJgqAG024860 for ; Mon, 12 May 2003 15:42:52 -0400 Received: from localhost (kaliaper@localhost) by diablo.cs.fsu.edu (8.11.6+Sun/8.11.3) with ESMTP id h4CJOKO03354 for ; Mon, 12 May 2003 15:24:20 -0400 (EDT) X-Authentication-Warning: diablo.cs.fsu.edu: kaliaper owned process doing -bs Date: Mon, 12 May 2003 15:24:20 -0400 (EDT) From: Sankar Kaliaperumal To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Adhoc network algorithm Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 am working on man in the middle attack in an ad hoc network. I would like to know is there any known algorithm which is secure for K bad nodes in a K+1 connected graph. Thanks, Sankar _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon May 12 19:09:06 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08115 for ; Mon, 12 May 2003 19:09:05 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CMYou08785 for manet-archive@odin.ietf.org; Mon, 12 May 2003 18:34: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 h4CMYnB08782 for ; Mon, 12 May 2003 18:34:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08109 for ; Mon, 12 May 2003 19:08:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FMRD-0005Q8-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 19:10:31 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FMRC-0005Q5-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 19:10:30 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CMOeB08147; Mon, 12 May 2003 18:24: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 h4CMJiB07991 for ; Mon, 12 May 2003 18:19:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07571 for ; Mon, 12 May 2003 18:53:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FMCd-0005HQ-00 for manet@ietf.org; Mon, 12 May 2003 18:55:27 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 19FMCd-0005HN-00 for manet@ietf.org; Mon, 12 May 2003 18:55:27 -0400 Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 05C121E400A; Mon, 12 May 2003 17:57:50 -0400 (EDT) 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 h4CMuU410593; Mon, 12 May 2003 18:56:30 -0400 Date: Mon, 12 May 2003 18:55:27 -0400 (EDT) From: "haas@ece.cornell.edu" To: Sankar Kaliaperumal Cc: manet@ietf.org, Zygmunt Haas Subject: Re: [manet] Adhoc network algorithm 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 Sankar, We have a paper that could help you with your question. However, as it was not publised yet, we cannot distribute it until end of May. The paper is: P. Papadimitratos and Z.J. Haas, ``Secure Message Transmission in Mobile Ad Hoc Networks,'' Elsevier Ad Hoc Networks Journal, vol. 1, no. 1, Jan/Feb/March 2003 and you will be able to find it on our web page at: http://wnl.ece.cornell.edu/wnlprojects.html#Publications2 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 Mon, 12 May 2003, Sankar Kaliaperumal wrote: > Hi, > I am working on man in the middle attack in an > ad hoc network. I would like to know is there any known algorithm > which is secure for K bad nodes in a K+1 connected graph. > > Thanks, > > Sankar > > _______________________________________________ > 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 May 12 20:11:03 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09537 for ; Mon, 12 May 2003 20:11:03 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4CNao813123 for manet-archive@odin.ietf.org; Mon, 12 May 2003 19:36: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 h4CNanB13120 for ; Mon, 12 May 2003 19:36:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA09530 for ; Mon, 12 May 2003 20:10:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FNPD-0005pU-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 20:12:31 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FNPC-0005pR-00 for manet-web-archive@ietf.org; Mon, 12 May 2003 20:12:30 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4CNQnB12630; Mon, 12 May 2003 19:26: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 h4CNMKB12435 for ; Mon, 12 May 2003 19:22:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09040 for ; Mon, 12 May 2003 19:56:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FNBC-0005hA-00 for manet@ietf.org; Mon, 12 May 2003 19:58:02 -0400 Received: from [156.26.1.5] (helo=sunlight.wichita.edu) by ietf-mx with esmtp (Exim 4.12) id 19FNBB-0005gs-00 for manet@ietf.org; Mon, 12 May 2003 19:58:01 -0400 Received: from CONVERSION-DAEMON.sunlight.wichita.edu by sunlight.wichita.edu (PMDF V6.1 #30593) id <0HES00F01T8US6@sunlight.wichita.edu> for manet@ietf.org; Mon, 12 May 2003 18:58:06 -0500 (CDT) Received: from webmail.wichita.edu (BIERSTADT.WICHITA.EDU [156.26.1.165]) by sunlight.wichita.edu (PMDF V6.1 #30593) with ESMTP id <0HES00FGOT8UCQ@sunlight.wichita.edu> for manet@ietf.org; Mon, 12 May 2003 18:58:06 -0500 (CDT) Date: Mon, 12 May 2003 18:58:06 -0500 From: lxsaripalli To: "manet@ietf.org" Message-id: <3EBC4368@webmail.wichita.edu> MIME-version: 1.0 X-Mailer: WebMail (Hydra) SMTP v3.62 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-WebMail-UserID: lxsaripalli@wichita.edu X-EXP32-SerialNo: 00003023 Content-Transfer-Encoding: 7bit Subject: [manet] Unsubscribe me Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 Plzz unsubscribe me and i wanted to join Diffserv mailing list Lavanya Saripalli Graduate Research Assistant Department of Psychology National Institute of Aviation and Research Wichita State University. Ph.316.978.5776 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 01:08:20 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15161 for ; Tue, 13 May 2003 01:08:20 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4D4YCT31657 for manet-archive@odin.ietf.org; Tue, 13 May 2003 00:34: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 h4D4YCB31654 for ; Tue, 13 May 2003 00:34:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15155 for ; Tue, 13 May 2003 01:07:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FS2s-0007GV-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 01:09:47 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FS2s-0007GS-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 01:09:46 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4D4GpB30529; Tue, 13 May 2003 00: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 h4D4A2B30333 for ; Tue, 13 May 2003 00:10:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14538 for ; Tue, 13 May 2003 00:43:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FRfV-00073V-00 for manet@ietf.org; Tue, 13 May 2003 00:45:37 -0400 Received: from sundance.cse.ucsc.edu ([128.114.48.62]) by ietf-mx with smtp (Exim 4.12) id 19FRfV-00073S-00 for manet@ietf.org; Tue, 13 May 2003 00:45:37 -0400 Received: (from tjiang@localhost) by sundance.cse.ucsc.edu (8.6.10/8.6.12) id VAA18398; Mon, 12 May 2003 21:46:41 -0700 Date: Mon, 12 May 2003 21:46:41 -0700 From: Tao Jiang Message-Id: <200305130446.VAA18398@sundance.cse.ucsc.edu> To: manet@ietf.org Subject: [manet] 802.11 PCF implementation under 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: , Hi there, I'm now working on a class project of implementing PCF under Glomosim. Has anybody done it before? I would like to ask some questions. If you would like to help, please contact me. Best regards, Tao Jiang University of California P.S.: Please don't respond to the group. Send me an e-mail directly. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 04:23:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00688 for ; Tue, 13 May 2003 04:23:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4D7nTf29340 for manet-archive@odin.ietf.org; Tue, 13 May 2003 03:49: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 h4D7nDB29321 for ; Tue, 13 May 2003 03:49:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00676 for ; Tue, 13 May 2003 04:22:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FV5X-0000tJ-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 04:24:43 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FV5W-0000tG-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 04:24:42 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4D7VRB23284; Tue, 13 May 2003 03:31: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 h4D7RXB23115 for ; Tue, 13 May 2003 03:27:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00297 for ; Tue, 13 May 2003 04:01:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FUka-0000lo-00 for manet@ietf.org; Tue, 13 May 2003 04:03:04 -0400 Received: from [202.108.44.181] (helo=sm181.163.com) by ietf-mx with esmtp (Exim 4.12) id 19FUkZ-0000ll-00 for manet@ietf.org; Tue, 13 May 2003 04:03:03 -0400 Received: from localhost (localhost [127.0.0.1]) by sm181.163.com (Postfix) with SMTP id 3A26A1C72C490 for ; Tue, 13 May 2003 16:04:04 +0800 (CST) Received: from sui4 (unknown [61.170.234.144]) by 192.168.1.181 (Coremail:www.163.com) with SMTP id BRsAAPKmwD4mAuqQ.1 for ; Tue, 13 May 2003 16:04:04 +0800 (CST) From: "=?GB2312?Q?=D5=C5=C7=E4?=" To: "manet@ietf.org" X-mailer: Foxmail 4.2 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 7bit Date: Tue, 13 May 2003 16:9:9 +0800 Message-Id: <20030513080404.3A26A1C72C490@sm181.163.com> X-Warning: 202.108.44.181 is a known spammer listed at sbl.spamhaus.org Content-Transfer-Encoding: 7bit Subject: [manet] data management 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 hi,all I am a novice to ad-hoc networks. I want to do research related to data management in ad-hoc networks(our group focus on database). I read some papers and find most of them related to routing algorithms. Are there any data management problems in ad-hoc networks? Can you give me advice about what I can do and what papers I can read if I want to do research related to data management problems in ad-hoc networks? thanks great! Best regards brucesea Fudan University, China _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 07:57:10 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04920 for ; Tue, 13 May 2003 07:57:10 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DBNAY12096 for manet-archive@odin.ietf.org; Tue, 13 May 2003 07:23: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 h4DBNAB12093 for ; Tue, 13 May 2003 07:23:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04910 for ; Tue, 13 May 2003 07:56:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FYQW-00020A-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 07:58:36 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FYQW-000207-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 07:58:36 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DB2gB10331; Tue, 13 May 2003 07:02: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 h4DAvkB10131 for ; Tue, 13 May 2003 06:57:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04224 for ; Tue, 13 May 2003 07:31:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FY1x-0001pE-00 for manet@ietf.org; Tue, 13 May 2003 07:33:13 -0400 Received: from web14803.mail.yahoo.com ([216.136.224.219]) by ietf-mx with smtp (Exim 4.12) id 19FY1w-0001pB-00 for manet@ietf.org; Tue, 13 May 2003 07:33:12 -0400 Message-ID: <20030513113417.67135.qmail@web14803.mail.yahoo.com> Received: from [202.125.153.129] by web14803.mail.yahoo.com via HTTP; Tue, 13 May 2003 12:34:17 BST Date: Tue, 13 May 2003 12:34:17 +0100 (BST) From: =?iso-8859-1?q?Kashif=20Sharif?= To: AODV MailingList , Manet MailingList MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-361911708-1052825657=:66262" Content-Transfer-Encoding: 8bit Subject: [manet] AODV - Sequence Number Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --0-361911708-1052825657=:66262 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit The following para is from draft-ietf-manet-aodv-13, page 16, article 6.6.1 Route Reply Generation by the Destination. "If the generating node is the destination itself, it MUST increment its own sequence number by one if the sequence number in the RREQ packet is equal to that incremented value. Otherwise, the destination does not change its sequence number before generating the RREP message. The destination node places its perhaps newly incremented) sequence number into the Destination Sequence Number field of the RREP, and enters the value zero in the Hop Count field of the RREP." the text in bold implies that the sequence number in RREQ message is greater than the sequence number of the destination. How is that possible? Please any one comment one it!!! --------------------------------- Yahoo! Plus - For a better Internet experience --0-361911708-1052825657=:66262 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
The following para is from draft-ietf-manet-aodv-13, page 16, article 6.6.1 Route Reply Generation by the Destination.
 

"If the generating node is the destination itself, it MUST increment its own sequence number by one if the sequence number in the RREQ packet is equal to that incremented value. Otherwise, the destination does not change its sequence number before generating the RREP message. The destination node places its  perhaps newly incremented) sequence number into the Destination Sequence Number field of the RREP, and enters the value zero in the Hop Count field of the RREP."

 

the text in bold implies that the sequence number in RREQ message is greater than the sequence number of the destination.

How is that possible?

 

Please any one comment one it!!!


Yahoo! Plus - For a better Internet experience
--0-361911708-1052825657=:66262-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 08:28:19 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07118 for ; Tue, 13 May 2003 08:28:19 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DBsKm15074 for manet-archive@odin.ietf.org; Tue, 13 May 2003 07:54: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 h4DBsKB15070 for ; Tue, 13 May 2003 07:54:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07043 for ; Tue, 13 May 2003 08:27:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FYuf-0002Uf-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 08:29:45 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FYue-0002Uc-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 08:29:44 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DBVHB12491; Tue, 13 May 2003 07:31: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 h4DBQpB12304 for ; Tue, 13 May 2003 07:26:51 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05299; Tue, 13 May 2003 08:00:20 -0400 (EDT) Message-Id: <200305131200.IAA05299@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: manet@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 13 May 2003 08:00:20 -0400 Subject: [manet] I-D ACTION:draft-ietf-manet-olsr-10.txt Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF. Title : Optimized Link State Routing Protocol Author(s) : T. Clausen, P. Jacquet Filename : draft-ietf-manet-olsr-10.txt Pages : 77 Date : 2003-5-12 This document describes the Optimized Link State Routing (OLSR) protocol for mobile ad hoc networks. The protocol is an optimization of the classical link state algorithm tailored to the requirements of a mobile wireless LAN. The key concept used in the protocol is that of multipoint relays (MPRs) [1], [2]. MPRs are selected nodes which forward broadcast messages during the flooding process. This technique substantially reduces the message overhead as compared to a classical flooding mechanism, where every node retransmits each message when it receives the first copy of the message. In OLSR, link state information is generated only by nodes elected as MPRs. Thus, a second optimization is achieved by minimizing the number of control messages flooded in the network. As a third optimization, an MPR node may chose to report only links between itself and its MPR selectors. Hence, as contrary to the classic link state algorithm, partial link state information is distributed in the network. This information is then used by for route calculation. OLSR provides optimal routes (in terms of number of hops). The protocol is particularly suitable for large and dense networks as the technique of MPRs works well in this context. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-manet-olsr-10.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-manet-olsr-10.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-manet-olsr-10.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-5-12152633.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-manet-olsr-10.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-manet-olsr-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-12152633.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 09:09:38 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10027 for ; Tue, 13 May 2003 09:09:38 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DCZeo19379 for manet-archive@odin.ietf.org; Tue, 13 May 2003 08:35: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 h4DCZdB19371 for ; Tue, 13 May 2003 08:35:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09998 for ; Tue, 13 May 2003 09:09:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FZYd-0003UL-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 09:11:03 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FZYX-0003UA-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 09:10:57 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DCKuB17991; Tue, 13 May 2003 08:20: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 h4DCDVB17439 for ; Tue, 13 May 2003 08:13:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08152 for ; Tue, 13 May 2003 08:46:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FZDE-0002rY-00 for manet@ietf.org; Tue, 13 May 2003 08:48:56 -0400 Received: from rumba.cefriel.it ([131.175.53.6]) by ietf-mx with esmtp (Exim 4.12) id 19FZDD-0002qY-00 for manet@ietf.org; Tue, 13 May 2003 08:48:55 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3194E.5FE851D3" Subject: RE: [manet] AODV - Sequence Number Date: Tue, 13 May 2003 14:51:30 +0200 Message-ID: <28C92BFE6EB5C943B15743D0E11E60360FE7AA@rumba.cefriel.it> Thread-Topic: [manet] AODV - Sequence Number Thread-Index: AcMZSbKfhwvzkJCRR/uwgGwk0iJSxAAAQvrw From: "Nicola Alagia" To: "Kashif Sharif" , "Manet MailingList" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_001_01C3194E.5FE851D3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Kashif, it is possible and here is an example. =20 Suppose that node S has a route towards node D with a sequence number = (X).=20 If S reports a link breakage between it and the next hop toward D (say A = the next hop), the node S itself increases the sequence number at (X+1) and sends a = RERR message=20 to its neighbor nodes that are in the precursors lists for the = destinations that use A as next hop. =20 Now, if S attemps a new route discovery for the destination node D, it = broadcasts a new=20 RREQ message and puts (X+1) in the Destination Sequence Number field. So = the RREQ has a Destination Sequence Number greater than the sequence number known by = the destination D. =20 A more detailed description of the RERR message is in the section 6.11 = of the draft-13. =20 Bye, Nicola =20 =20 =20 -----Original Message----- From: Kashif Sharif [mailto:manet_project_niit@yahoo.co.uk] Sent: Tuesday, May 13, 2003 13:34 To: AODV MailingList; Manet MailingList Subject: [manet] AODV - Sequence Number The following para is from draft-ietf-manet-aodv-13, page 16, article = 6.6.1 Route Reply Generation by the Destination. =20 "If the generating node is the destination itself, it MUST increment its = own sequence number by one if the sequence number in the RREQ packet is = equal to that incremented value. Otherwise, the destination does not = change its sequence number before generating the RREP message. The = destination node places its perhaps newly incremented) sequence number = into the Destination Sequence Number field of the RREP, and enters the = value zero in the Hop Count field of the RREP." =20 the text in bold implies that the sequence number in RREQ message is = greater than the sequence number of the destination.=20 How is that possible? =20 Please any one comment one it!!! _____ =20 = Yahoo! Plus - For a = better Internet experience ------_=_NextPart_001_01C3194E.5FE851D3 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi=20 Kashif, it is possible and here is an example.
 
Suppose that node S has a route towards=20 node D with a sequence number (X).
If S reports a link breakage between it = and the=20 next hop toward D (say A the next hop),
the=20 node S itself increases the sequence number at (X+1) and = sends a RERR=20 message
to its neighbor nodes that are in the = precursors=20 lists for the destinations that use A as next hop.
 
Now,=20 if S attemps a new route discovery for the destination node D, it = broadcasts a=20 new
RREQ=20 message and puts (X+1) in the Destination Sequence Number field. So = the=20 RREQ has
a=20 Destination Sequence Number greater than the sequence = number known=20 by the destination D.
 
A more detailed description of the RERR = message is=20 in the section 6.11 of the draft-13.
 
Bye,=20 Nicola
 
 
 
 -----Original = Message-----
From:=20 Kashif Sharif [mailto:manet_project_niit@yahoo.co.uk]
Sent: = Tuesday,=20 May 13, 2003 13:34
To: AODV MailingList; Manet=20 MailingList
Subject: [manet] AODV - Sequence=20 Number

The following para is from draft-ietf-manet-aodv-13, page 16, = article=20 6.6.1 Route Reply Generation by the Destination.
 

"If the generating node is the destination = itself, it=20 MUST increment its own sequence number by one if the sequence number = in the=20 RREQ packet is equal to that incremented value. Otherwise, = the=20 destination does not change its sequence number before generating the = RREP=20 message. The destination node places its  perhaps newly = incremented)=20 sequence number into the Destination Sequence Number field of the = RREP, and=20 enters the value zero in the Hop Count field of the RREP."

 

the text in bold implies that the sequence number in = RREQ=20 message is greater than the sequence number of the destination.

How is that possible?

 

Please any one comment one = it!!!


Yahoo! Plus - For a better Internet=20 experience
------_=_NextPart_001_01C3194E.5FE851D3-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 10:18:25 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14250 for ; Tue, 13 May 2003 10:18:25 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DDiTh26363 for manet-archive@odin.ietf.org; Tue, 13 May 2003 09:44: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 h4DDiSB26360 for ; Tue, 13 May 2003 09:44:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14238 for ; Tue, 13 May 2003 10:17:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FadD-0004Lw-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 10:19:51 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FadD-0004Lr-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 10:19:51 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DDRIB24178; Tue, 13 May 2003 09:27: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 h4DD2kB22042 for ; Tue, 13 May 2003 09:02:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11666 for ; Tue, 13 May 2003 09:36:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FZys-0003zw-00 for manet@ietf.org; Tue, 13 May 2003 09:38:10 -0400 Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19FZyr-0003zr-00 for manet@ietf.org; Tue, 13 May 2003 09:38:09 -0400 Received: from nj0117exch001p.wins.lucent.com (h135-5-177-157.lucent.com [135.5.177.157]) by ihemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h4DDchF18455 for ; Tue, 13 May 2003 09:38:44 -0400 (EDT) Received: by nj0117exch001p.wh.lucent.com with Internet Mail Service (5.5.2653.19) id ; Tue, 13 May 2003 09:38:43 -0400 Message-ID: From: "Sudanthi, Sudha (Sudha)" To: "'Kashif Sharif'" , AODV MailingList , Manet MailingList Subject: RE: [manet] AODV - Sequence Number Date: Tue, 13 May 2003 09:38:42 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C31954.F7DF493E" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C31954.F7DF493E Content-Type: text/plain; charset="iso-8859-1" The generating node increments the destination sequence number it is requesting in the RREQ packet before sending, so if it previously received a RREP from this destination with a sequence number X, it is going to ask for X+1 next time and the destination will increment its own sequence number from X to X+1 before sending a RREP. Therefore, receiving a RREQ with a sequence number greater than what the destination has for itself does not mean that the requesting node has a more fresh route for the destination--just that a more fresh route is being asked for than what it previously received. I hope that makes some sense and helps... -----Original Message----- From: Kashif Sharif [mailto:manet_project_niit@yahoo.co.uk] Sent: Tuesday, May 13, 2003 7:34 AM To: AODV MailingList; Manet MailingList Subject: [manet] AODV - Sequence Number The following para is from draft-ietf-manet-aodv-13, page 16, article 6.6.1 Route Reply Generation by the Destination. "If the generating node is the destination itself, it MUST increment its own sequence number by one if the sequence number in the RREQ packet is equal to that incremented value. Otherwise, the destination does not change its sequence number before generating the RREP message. The destination node places its perhaps newly incremented) sequence number into the Destination Sequence Number field of the RREP, and enters the value zero in the Hop Count field of the RREP." the text in bold implies that the sequence number in RREQ message is greater than the sequence number of the destination. How is that possible? Please any one comment one it!!! _____ Yahoo! Plus - For a better Internet experience ------_=_NextPart_001_01C31954.F7DF493E Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
The=20 generating node increments the destination sequence number it is = requesting in=20 the RREQ packet before sending, so if it previously received a RREP = from this=20 destination with a sequence number X, it is going to ask for X+1 next = time and=20 the destination will increment its own sequence number from X to X+1 = before=20 sending a RREP. 
 
Therefore, receiving a RREQ with a sequence number greater = than what the=20 destination has for itself does not mean that the requesting node has a = more=20 fresh route for the destination--just that a more fresh route is = being=20 asked for than what it previously received.
 
I hope=20 that makes some sense and helps...
-----Original Message-----
From: Kashif Sharif=20 [mailto:manet_project_niit@yahoo.co.uk]
Sent: Tuesday, May = 13, 2003=20 7:34 AM
To: AODV MailingList; Manet = MailingList
Subject:=20 [manet] AODV - Sequence Number

The following para is from draft-ietf-manet-aodv-13, page 16, = article=20 6.6.1 Route Reply Generation by the Destination.
 

"If the generating node is the destination = itself, it=20 MUST increment its own sequence number by one if the sequence number = in the=20 RREQ packet is equal to that incremented value. Otherwise, = the=20 destination does not change its sequence number before generating the = RREP=20 message. The destination node places its  perhaps newly = incremented)=20 sequence number into the Destination Sequence Number field of the = RREP, and=20 enters the value zero in the Hop Count field of the RREP."

 

the text in bold implies that the sequence number in = RREQ=20 message is greater than the sequence number of the destination.

How is that possible?

 

Please any one comment one = it!!!


Yahoo! Plus - For a better Internet=20 experience
------_=_NextPart_001_01C31954.F7DF493E-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 10:33:27 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14863 for ; Tue, 13 May 2003 10:33:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DDxVt27475 for manet-archive@odin.ietf.org; Tue, 13 May 2003 09:59: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 h4DDxVB27472 for ; Tue, 13 May 2003 09:59:31 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14830 for ; Tue, 13 May 2003 10:32:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Farl-0004Ve-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 10:34:54 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Farl-0004Vb-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 10:34:53 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DDl9B26518; Tue, 13 May 2003 09:47: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 h4DDg8B26239 for ; Tue, 13 May 2003 09:42:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14090 for ; Tue, 13 May 2003 10:15:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Faax-0004Ky-00 for manet@ietf.org; Tue, 13 May 2003 10:17:31 -0400 Received: from pollux.cse.buffalo.edu ([128.205.35.2] ident=daemon) by ietf-mx with esmtp (Exim 4.12) id 19Faaw-0004Kv-00 for manet@ietf.org; Tue, 13 May 2003 10:17:30 -0400 Received: (from ab42@localhost) by pollux.cse.buffalo.edu (8.11.6+Sun/8.10.1) id h4DEIaK21436; Tue, 13 May 2003 10:18:36 -0400 (EDT) Date: Tue, 13 May 2003 10:18:36 -0400 (EDT) From: Aruna Balasubramanian To: In-Reply-To: <20030513131722.23300.43792.Mailman@www1.ietf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] K bad nodes, K+1 good 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: , Sankar, The paper 'Securing Ad Hoc Networks' found in http://citeseer.nj.nec.com/zhou99securing.html by Dr. Haas and Zhou uses threshold cryptography which assumes that at the max k nodes can be bad and if there are k+1 nodes, their is atleast one good node Hope this helps Aruna _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 11:14:34 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16147 for ; Tue, 13 May 2003 11:14:34 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DEed431697 for manet-archive@odin.ietf.org; Tue, 13 May 2003 10:40: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 h4DEedB31694 for ; Tue, 13 May 2003 10:40:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16127 for ; Tue, 13 May 2003 11:14:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FbVY-0004qo-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 11:16:00 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FbVY-0004ql-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 11:16:00 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DEOSB29567; Tue, 13 May 2003 10:24: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 h4DEJ1B29315 for ; Tue, 13 May 2003 10:19:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15286 for ; Tue, 13 May 2003 10:52:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FbAd-0004cn-00 for manet@ietf.org; Tue, 13 May 2003 10:54:23 -0400 Received: from rumba.cefriel.it ([131.175.53.6]) by ietf-mx with esmtp (Exim 4.12) id 19FbAc-0004cE-00 for manet@ietf.org; Tue, 13 May 2003 10:54:22 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3195F.E580049B" Subject: RE: [manet] AODV - Sequence Number Date: Tue, 13 May 2003 16:56:55 +0200 Message-ID: <28C92BFE6EB5C943B15743D0E11E60360FE7AB@rumba.cefriel.it> Thread-Topic: [manet] AODV - Sequence Number Thread-Index: AcMZXONa31Ry86Z9Qf+jOh6/W4w+8wAAGHNw From: "Nicola Alagia" To: "Sudanthi, Sudha (Sudha)" , "Kashif Sharif" , "AODV MailingList" , "Manet MailingList" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_001_01C3195F.E580049B Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Sudha, I don't agree with you and here is my motivation: =20 according to the draft 13, the Originator node increments its own = sequence number=20 and copies (without modification) the Destination sequence number from = its routing table=20 (if the Destination sequence number is not known, the U bit in the RREQ = is set).=20 =20 You can read this in the first paragraphs of the sections 6.1 and 6.3 of = the draft. =20 Am I right? Is there something that I'm missing?=20 =20 Bye, Nicola. =20 =20 The generating node increments the destination sequence number it is = requesting in the RREQ packet before sending, so if it previously = received a RREP from this destination with a sequence number X, it is = going to ask for X+1 next time and the destination will increment its = own sequence number from X to X+1 before sending a RREP. =20 =20 Therefore, receiving a RREQ with a sequence number greater than what the = destination has for itself does not mean that the requesting node has a = more fresh route for the destination--just that a more fresh route is = being asked for than what it previously received. =20 I hope that makes some sense and helps... -----Original Message----- From: Kashif Sharif [mailto:manet_project_niit@yahoo.co.uk] Sent: Tuesday, May 13, 2003 7:34 AM To: AODV MailingList; Manet MailingList Subject: [manet] AODV - Sequence Number The following para is from draft-ietf-manet-aodv-13, page 16, article = 6.6.1 Route Reply Generation by the Destination. =20 "If the generating node is the destination itself, it MUST increment its = own sequence number by one if the sequence number in the RREQ packet is = equal to that incremented value. Otherwise, the destination does not = change its sequence number before generating the RREP message. The = destination node places its perhaps newly incremented) sequence number = into the Destination Sequence Number field of the RREP, and enters the = value zero in the Hop Count field of the RREP." =20 the text in bold implies that the sequence number in RREQ message is = greater than the sequence number of the destination.=20 How is that possible? =20 Please any one comment one it!!! _____ =20 = Yahoo! Plus - For a = better Internet experience ------_=_NextPart_001_01C3195F.E580049B Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi=20 Sudha, I don't agree with you and here is my = motivation:
 
according to the draft 13, the Originator = node=20 increments its own sequence number
and=20 copies (without modification) the Destination sequence number from its = routing=20 table
(if=20 the Destination sequence number is not known, the U bit in the RREQ is = set).=20
 
You=20 can read this in the first paragraphs of the sections 6.1 and 6.3 = of the=20 draft.
 
Am I=20 right? Is there something that I'm missing?
 
Bye,=20 Nicola.
 
 
The=20 generating node increments the destination sequence number it is = requesting in=20 the RREQ packet before sending, so if it previously received a RREP = from this=20 destination with a sequence number X, it is going to ask for X+1 next = time and=20 the destination will increment its own sequence number from X to X+1 = before=20 sending a RREP. 
 
Therefore, receiving a RREQ with a sequence number greater = than what=20 the destination has for itself does not mean that the requesting node = has a=20 more fresh route for the destination--just that a more fresh = route is=20 being asked for than what it previously received.
 
I=20 hope that makes some sense and helps...
-----Original Message-----
From: Kashif Sharif=20 [mailto:manet_project_niit@yahoo.co.uk]
Sent: Tuesday, May = 13,=20 2003 7:34 AM
To: AODV MailingList; Manet=20 MailingList
Subject: [manet] AODV - Sequence=20 Number

The following para is from draft-ietf-manet-aodv-13, page 16, = article=20 6.6.1 Route Reply Generation by the Destination.
 

"If the generating node is the destination = itself, it=20 MUST increment its own sequence number by one if the sequence number = in the=20 RREQ packet is equal to that incremented value. Otherwise, = the=20 destination does not change its sequence number before generating = the RREP=20 message. The destination node places its  perhaps newly = incremented)=20 sequence number into the Destination Sequence Number field of the = RREP, and=20 enters the value zero in the Hop Count field of the RREP."

 

the text in bold implies that the sequence number in = RREQ=20 message is greater than the sequence number of the destination.

How is that possible?

 

Please any one comment one = it!!!


Yahoo! Plus - For a better Internet=20 = experience
------_=_NextPart_001_01C3195F.E580049B-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 11:18:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16289 for ; Tue, 13 May 2003 11:18:37 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DEifL31948 for manet-archive@odin.ietf.org; Tue, 13 May 2003 10:44: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 h4DEifB31945 for ; Tue, 13 May 2003 10:44:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16275 for ; Tue, 13 May 2003 11:18:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FbZS-0004td-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 11:20:02 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FbZR-0004ta-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 11:20:01 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DEWXB30047; Tue, 13 May 2003 10:32: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 h4DERBB29760 for ; Tue, 13 May 2003 10:27:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15577 for ; Tue, 13 May 2003 11:00:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FbIX-0004fy-00 for manet@ietf.org; Tue, 13 May 2003 11:02:33 -0400 Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19FbIX-0004fd-00 for manet@ietf.org; Tue, 13 May 2003 11:02:33 -0400 Received: from nj0117exch001p.wins.lucent.com (h135-5-177-157.lucent.com [135.5.177.157]) by hoemail2.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h4DF37j02516 for ; Tue, 13 May 2003 11:03:07 -0400 (EDT) Received: by nj0117exch001p.wh.lucent.com with Internet Mail Service (5.5.2653.19) id ; Tue, 13 May 2003 11:03:07 -0400 Message-ID: From: "Sudanthi, Sudha (Sudha)" To: "'Nicola Alagia'" , "Sudanthi, Sudha (Sudha)" , Kashif Sharif , AODV MailingList , Manet MailingList Subject: RE: [manet] AODV - Sequence Number Date: Tue, 13 May 2003 11:03:05 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C31960.C1998C2A" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C31960.C1998C2A Content-Type: text/plain; charset="iso-8859-1" oops. You are completely right in that it does not increment its own sequence number before sending a RREQ, sorry about that. And yes, as you said, after a RERR is sent for a destination D, a RREQ sent with a destination sequence number greater than what the destination D has for itself is likely... my apologies! -----Original Message----- From: Nicola Alagia [mailto:nicola.alagia@cefriel.it] Sent: Tuesday, May 13, 2003 10:57 AM To: Sudanthi, Sudha (Sudha); Kashif Sharif; AODV MailingList; Manet MailingList Subject: RE: [manet] AODV - Sequence Number Hi Sudha, I don't agree with you and here is my motivation: according to the draft 13, the Originator node increments its own sequence number and copies (without modification) the Destination sequence number from its routing table (if the Destination sequence number is not known, the U bit in the RREQ is set). You can read this in the first paragraphs of the sections 6.1 and 6.3 of the draft. Am I right? Is there something that I'm missing? Bye, Nicola. The generating node increments the destination sequence number it is requesting in the RREQ packet before sending, so if it previously received a RREP from this destination with a sequence number X, it is going to ask for X+1 next time and the destination will increment its own sequence number from X to X+1 before sending a RREP. Therefore, receiving a RREQ with a sequence number greater than what the destination has for itself does not mean that the requesting node has a more fresh route for the destination--just that a more fresh route is being asked for than what it previously received. I hope that makes some sense and helps... -----Original Message----- From: Kashif Sharif [mailto:manet_project_niit@yahoo.co.uk] Sent: Tuesday, May 13, 2003 7:34 AM To: AODV MailingList; Manet MailingList Subject: [manet] AODV - Sequence Number The following para is from draft-ietf-manet-aodv-13, page 16, article 6.6.1 Route Reply Generation by the Destination. "If the generating node is the destination itself, it MUST increment its own sequence number by one if the sequence number in the RREQ packet is equal to that incremented value. Otherwise, the destination does not change its sequence number before generating the RREP message. The destination node places its perhaps newly incremented) sequence number into the Destination Sequence Number field of the RREP, and enters the value zero in the Hop Count field of the RREP." the text in bold implies that the sequence number in RREQ message is greater than the sequence number of the destination. How is that possible? Please any one comment one it!!! _____ Yahoo! Plus - For a better Internet experience ------_=_NextPart_001_01C31960.C1998C2A Content-Type: text/html; charset="iso-8859-1"
oops.  You are completely right in that it does not increment its own sequence number before sending a RREQ, sorry about that.   And yes, as you said, after a RERR is sent for a destination D, a RREQ sent with a destination sequence number greater than what the destination D has for itself is likely...
 
my apologies!
-----Original Message-----
From: Nicola Alagia [mailto:nicola.alagia@cefriel.it]
Sent: Tuesday, May 13, 2003 10:57 AM
To: Sudanthi, Sudha (Sudha); Kashif Sharif; AODV MailingList; Manet MailingList
Subject: RE: [manet] AODV - Sequence Number

Hi Sudha, I don't agree with you and here is my motivation:
 
according to the draft 13, the Originator node increments its own sequence number
and copies (without modification) the Destination sequence number from its routing table
(if the Destination sequence number is not known, the U bit in the RREQ is set).
 
You can read this in the first paragraphs of the sections 6.1 and 6.3 of the draft.
 
Am I right? Is there something that I'm missing?
 
Bye, Nicola.
 
 
The generating node increments the destination sequence number it is requesting in the RREQ packet before sending, so if it previously received a RREP from this destination with a sequence number X, it is going to ask for X+1 next time and the destination will increment its own sequence number from X to X+1 before sending a RREP. 
 
Therefore, receiving a RREQ with a sequence number greater than what the destination has for itself does not mean that the requesting node has a more fresh route for the destination--just that a more fresh route is being asked for than what it previously received.
 
I hope that makes some sense and helps...
-----Original Message-----
From: Kashif Sharif [mailto:manet_project_niit@yahoo.co.uk]
Sent: Tuesday, May 13, 2003 7:34 AM
To: AODV MailingList; Manet MailingList
Subject: [manet] AODV - Sequence Number

The following para is from draft-ietf-manet-aodv-13, page 16, article 6.6.1 Route Reply Generation by the Destination.
 

"If the generating node is the destination itself, it MUST increment its own sequence number by one if the sequence number in the RREQ packet is equal to that incremented value. Otherwise, the destination does not change its sequence number before generating the RREP message. The destination node places its  perhaps newly incremented) sequence number into the Destination Sequence Number field of the RREP, and enters the value zero in the Hop Count field of the RREP."

 

the text in bold implies that the sequence number in RREQ message is greater than the sequence number of the destination.

How is that possible?

 

Please any one comment one it!!!


Yahoo! Plus - For a better Internet experience
------_=_NextPart_001_01C31960.C1998C2A-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 11:26:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16639 for ; Tue, 13 May 2003 11:26:59 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DEr2f32501 for manet-archive@odin.ietf.org; Tue, 13 May 2003 10:53: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 h4DEr2B32498 for ; Tue, 13 May 2003 10:53:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16613 for ; Tue, 13 May 2003 11:26:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FbhX-0004zJ-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 11:28:23 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FbhX-0004zG-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 11:28:23 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DEbSB30957; Tue, 13 May 2003 10:37: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 h4DESnB29865 for ; Tue, 13 May 2003 10:28:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15683 for ; Tue, 13 May 2003 11:02:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FbK6-0004hR-00 for manet@ietf.org; Tue, 13 May 2003 11:04:11 -0400 Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by ietf-mx with esmtp (Exim 4.12) id 19FbK6-0004hO-00 for manet@ietf.org; Tue, 13 May 2003 11:04:10 -0400 Received: from blv-av-02.boeing.com ([192.42.227.217]) by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id IAA03016; Tue, 13 May 2003 08:05:15 -0700 (PDT) Received: from slb-hub-01.boeing.com (localhost [127.0.0.1]) by blv-av-02.boeing.com (8.9.3p2/8.9.2/MBS-AV-02) with ESMTP id IAA02608; Tue, 13 May 2003 08:05:14 -0700 (PDT) Received: from XCH-NWBH-01.nw.nos.boeing.com (xch-nwbh-01.nw.nos.boeing.com [192.33.62.231]) by slb-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id h4DF52905234; Tue, 13 May 2003 08:05:02 -0700 (PDT) Received: from XCH-NW-27.nw.nos.boeing.com ([192.48.4.101]) by XCH-NWBH-01.nw.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6662); Tue, 13 May 2003 08:03:47 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [manet] OSPF in MANETs Date: Tue, 13 May 2003 08:03:46 -0700 Message-ID: <6938661A6EDA8A4EA8D1419BCE46F24C01483CFA@xch-nw-27.nw.nos.boeing.com> Thread-Topic: [manet] OSPF in MANETs Thread-Index: AcMYPpB8RpHebwUpRValm7D/fLhPUQBHrm0Q From: "Henderson, Thomas R" To: , "Joe Macker" Cc: X-OriginalArrivalTime: 13 May 2003 15:03:47.0167 (UTC) FILETIME=[DA9B46F0:01C31960] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4DESnB29866 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit > -----Original Message----- > From: ogier@erg.sri.com [mailto:ogier@erg.sri.com] > Sent: Sunday, May 11, 2003 9:11 PM > To: Joe Macker > Cc: manet@ietf.org > Subject: Re: [manet] OSPF in MANETs > > > Can you list the candidate strawman proposals for MANET > extensions to OSPF? > Also, if possible, can you list the "set of efforts" that you mention? > I know about some of the work Fred Baker has done in this > area, but it would be > nice to get more complete and up-to-date information on the > candidate proposals. > Here is one. We have a paper under review for MILCOM 2003 conference where we define a new "wireless" interface type for OSPF that, from the outside of the subnet, is represented as a point-multipoint network, but from within the wireless multihop network, uses OLSRs MPR mechanism to flood LSAs. It is a full link state approach (every node floods its LSA) and the bandwidth utilization approaches that of OLSR (draft 7) in the wireless network, significantly outperforming that of the OSPF point-multipoint interface type. Tom _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 11:32:22 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16942 for ; Tue, 13 May 2003 11:32:22 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DEwQ400381 for manet-archive@odin.ietf.org; Tue, 13 May 2003 10:58: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 h4DEwQB00378 for ; Tue, 13 May 2003 10:58:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16903 for ; Tue, 13 May 2003 11:31:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Fbml-00054f-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 11:33:47 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Fbmk-00054Z-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 11:33:46 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DEmCB32113; Tue, 13 May 2003 10:48: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 h4DEhNB31886 for ; Tue, 13 May 2003 10:43:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16244 for ; Tue, 13 May 2003 11:16:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FbYC-0004t8-00 for manet@ietf.org; Tue, 13 May 2003 11:18:44 -0400 Received: from eigen.ee.ualberta.ca ([129.128.68.7]) by ietf-mx with esmtp (Exim 4.12) id 19FbYB-0004t3-00 for manet@ietf.org; Tue, 13 May 2003 11:18:43 -0400 Received: from webmail.ualberta.ca (webmail.srv.ualberta.ca [129.128.5.105]) by eigen.ee.ualberta.ca (8.9.3 (PHNE_24419+JAGae58098)/8.9.3) with ESMTP id JAA00681; Tue, 13 May 2003 09:10:59 -0600 (MDT) X-WebMail-UserID: snagaraj@mail.ee.ualberta.ca Date: Tue, 13 May 2003 09:22:00 -0600 From: snagaraj To: AODV MailingList , Manet MailingList X-EXP32-SerialNo: 00003228 Subject: RE: [manet] AODV - Sequence Number Message-ID: <3EC18E45@webmail.ualberta.ca> 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 I guess what Sudha mentioned is OK if the node is performing a LOCAL_REPAIR? Best Regards, Sumeeth >===== Original Message From "Nicola Alagia" ===== >Hi Sudha, I don't agree with you and here is my motivation: > >according to the draft 13, the Originator node increments its own sequence number >and copies (without modification) the Destination sequence number from its routing table >(if the Destination sequence number is not known, the U bit in the RREQ is set). > >You can read this in the first paragraphs of the sections 6.1 and 6.3 of the draft. > >Am I right? Is there something that I'm missing? > >Bye, Nicola. > > > >The generating node increments the destination sequence number it is requesting in the RREQ packet before sending, so if it previously received a RREP from this destination with a sequence number X, it is going to ask for X+1 next time and the destination will increment its own sequence number from X to X+1 before sending a RREP. > >Therefore, receiving a RREQ with a sequence number greater than what the destination has for itself does not mean that the requesting node has a more fresh route for the destination--just that a more fresh route is being asked for than what it previously received. > >I hope that makes some sense and helps... > >-----Original Message----- >From: Kashif Sharif [mailto:manet_project_niit@yahoo.co.uk] >Sent: Tuesday, May 13, 2003 7:34 AM >To: AODV MailingList; Manet MailingList >Subject: [manet] AODV - Sequence Number > > >The following para is from draft-ietf-manet-aodv-13, page 16, article 6.6.1 Route Reply Generation by the Destination. > >"If the generating node is the destination itself, it MUST increment its own sequence number by one if the sequence number in the RREQ packet is equal to that incremented value. Otherwise, the destination does not change its sequence number before generating the RREP message. The destination node places its perhaps newly incremented) sequence number into the Destination Sequence Number field of the RREP, and enters the value zero in the Hop Count field of the RREP." > > > >the text in bold implies that the sequence number in RREQ message is greater than the sequence number of the destination. > >How is that possible? > > > >Please any one comment one it!!! > > > > > > _____ > > Yahoo! Plus - For a better Internet experience _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 12:20:17 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18944 for ; Tue, 13 May 2003 12:20:17 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DFkMa05470 for manet-archive@odin.ietf.org; Tue, 13 May 2003 11:46: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 h4DFkMB05467 for ; Tue, 13 May 2003 11:46:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18936 for ; Tue, 13 May 2003 12:19:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FcX8-0005e3-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 12:21:42 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FcX8-0005e0-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 12:21:42 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DFPvB03114; Tue, 13 May 2003 11:25: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 h4DFKJB02853 for ; Tue, 13 May 2003 11:20:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17769 for ; Tue, 13 May 2003 11:53:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Fc7v-0005JC-00 for manet@ietf.org; Tue, 13 May 2003 11:55:39 -0400 Received: from angelo.kcl.ac.uk ([137.73.66.5]) by ietf-mx with esmtp (Exim 4.12) id 19Fc7v-0005J3-00 for manet@ietf.org; Tue, 13 May 2003 11:55:39 -0400 Received: from MONA (EE014.eee.kcl.ac.uk [137.73.10.115]) by angelo.kcl.ac.uk with ESMTP id h4DFuVA8001131 for < manet@ietf.org>; Tue, 13 May 2003 16:56:31 +0100 (BST) Message-ID: <018601c31969$8bb4ac80$730a4989@MONA> From: "Mona" To: Date: Tue, 13 May 2003 17:05:57 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0183_01C31971.EBAA9610" 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 X-MailScanner: Found to be clean Subject: [manet] QoS extension for AODV Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0183_01C31971.EBAA9610 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hello, I have read "QoS extension for aodv" draft and I intend to implement = this protocol under ns2. =20 1) I am curios to know why there is no update on this draft since July = 2000. Once in MANET mailing list Professor Perkins mentioned that "Yes, = with a better way to specify QoS needs". What is a better way to = support QoS routing in ad hoc networks? 2) Also I like to know if any codes are available or under progress for = this protocol. I would appreciate any guide me in this matter.=20 Kind regards, Mona ----------------------------------------------------------- Mona Ghassemian, PhD student Centre for Telecommunications Research Kings College London Strand, London WC2R 2LS UK TEL: +44 20 7848 2596 FAX: +44 20 7848 2664 Mona.Ghassemian@kcl.ac.uk Tehran@ieee.org ------=_NextPart_000_0183_01C31971.EBAA9610 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hello,
 
I have read "QoS extension for aodv" draft and = I intend=20 to implement this protocol under ns2. 
 
1)  I am curios to know why there is = no update=20 on this draft since July 2000. Once in MANET mailing list Professor = Perkins mentioned that "Yes, with=20 a better way to specify QoS needs".  What is a better way = to support=20 QoS routing in ad hoc networks?
 
2) Also I like to know if any codes are available or = under=20 progress for this protocol.
 
I would appreciate any guide me = in this=20 matter.
 
Kind regards,
Mona

-----------------------------------------------------------
Mona Ghassemian, PhD student
Centre for Telecommunications=20 Research
Kings College=20 London
Strand,=20 London WC2R=20 2LS
UK
TEL: = +44 20 7848=20 2596
FAX: +44 20 7848 2664
Mona.Ghassemian@kcl.ac.ukTehran@ieee.org
 
 
------=_NextPart_000_0183_01C31971.EBAA9610-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue May 13 18:17:13 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02044 for ; Tue, 13 May 2003 18:17:13 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4DLhPn02131 for manet-archive@odin.ietf.org; Tue, 13 May 2003 17:43: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 h4DLhPB02128 for ; Tue, 13 May 2003 17:43:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02040 for ; Tue, 13 May 2003 18:16:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Fi6X-0000JF-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 18:18:37 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Fi6X-0000JB-00 for manet-web-archive@ietf.org; Tue, 13 May 2003 18:18:37 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4DLVYB00531; Tue, 13 May 2003 17:31: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 h4DLKMB32631 for ; Tue, 13 May 2003 17:20:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00285 for ; Tue, 13 May 2003 17:53:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FhkF-00008H-00 for manet@ietf.org; Tue, 13 May 2003 17:55:35 -0400 Received: from [128.114.48.62] (helo=sundance.cse.ucsc.edu) by ietf-mx with smtp (Exim 4.12) id 19FhkF-000088-00 for manet@ietf.org; Tue, 13 May 2003 17:55:35 -0400 Received: (from tjiang@localhost) by sundance.cse.ucsc.edu (8.6.10/8.6.12) id OAA14716; Tue, 13 May 2003 14:56:26 -0700 Date: Tue, 13 May 2003 14:56:26 -0700 From: Tao Jiang Message-Id: <200305132156.OAA14716@sundance.cse.ucsc.edu> To: manet@ietf.org Subject: [manet] MAC PCF implementation under 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: , Hi there, I'm now working on a class project of implementing PCF under Glomosim. Has anybody done it before? I would like to ask some questions. If you would like to help, please contact me. Best regards, Tao Jiang University of California tjiang@cse.ucsc.edu P.S.: Please don't respond to the group. Send me an e-mail directly. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 14 03:08:40 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07635 for ; Wed, 14 May 2003 03:08:40 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4E6Z4j16437 for manet-archive@odin.ietf.org; Wed, 14 May 2003 02:35: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 h4E6Z4B16431 for ; Wed, 14 May 2003 02:35:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA07626 for ; Wed, 14 May 2003 03:08:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FqOr-0003Dj-00 for manet-web-archive@ietf.org; Wed, 14 May 2003 03:10:05 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FqOq-0003Dg-00 for manet-web-archive@ietf.org; Wed, 14 May 2003 03:10:04 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4E6MtB15460; Wed, 14 May 2003 02:22: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 h4E6IcB14807 for ; Wed, 14 May 2003 02:18:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07342 for ; Wed, 14 May 2003 02:51:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Fq8y-00037q-00 for manet@ietf.org; Wed, 14 May 2003 02:53:40 -0400 Received: from waldorf.cs.uni-dortmund.de ([129.217.4.42]) by ietf-mx with esmtp (Exim 4.12) id 19Fq8w-00037j-00 for manet@ietf.org; Wed, 14 May 2003 02:53:39 -0400 Received: from postamt.cs.uni-dortmund.de (postamt [129.217.4.40]) by waldorf.cs.uni-dortmund.de with ESMTP id h4E6sDL24755; Wed, 14 May 2003 08:54:13 +0200 (MES) Received: from grant.cs.uni-dortmund.de (grant [129.217.16.109]) (authenticated bits=0) by postamt.cs.uni-dortmund.de (8.12.8/8.12.8) with ESMTP id h4E6sCI9013367 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 14 May 2003 08:54:13 +0200 (MEST) From: Oliver Waldhorst Organization: University of Dortmund To: "=?gb2312?q?=D5=C5=C7=E4?=" Subject: Re: [manet] data management in ad-hoc networks Date: Wed, 14 May 2003 08:54:12 +0200 User-Agent: KMail/1.5.1 References: <20030513080404.3A26A1C72C490@sm181.163.com> In-Reply-To: <20030513080404.3A26A1C72C490@sm181.163.com> Cc: "manet@ietf.org" MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305140854.12072.waldhorst@ls4.cs.uni-dortmund.de> 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 Brucesea, our group at University of Dortmund works on Peer-to-Peer computing in MANET and recent work covers issues related to data management. You can find a survey of the project and recent publications on our website http://www4.cs.uni-dortmund.de/~Lindemann/projects/MobileP2P/ Regards, Oliver > hi,all > I am a novice to ad-hoc networks. I want to do research related to data > management in ad-hoc networks(our group focus on database). I read some > papers and find most of them related to routing algorithms. Are there any > data management problems in ad-hoc networks? > Can you give me advice about what I can do and what papers I can read > if I want to do research related to data management problems in ad-hoc > networks? > > thanks great! > > Best regards > > brucesea > Fudan University, China > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- ------------------------------------------------------------------------ Oliver Waldhorst, M.S. University of Dortmund Department of Computer Science Computer Systems and Performance Evaluation Phone: +49 (231) 755-4797 August-Schmidt-Str. 12 Fax: +49 (231) 755-2417 44227 Dortmund, Germany E-mail:ow@ls4.cs.uni-dortmund.de WWW: http://www4.cs.uni-dortmund.de/~Waldhorst/ ------------------------------------------------------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 14 12:19:24 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23776 for ; Wed, 14 May 2003 12:19:24 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4EFk0V26534 for manet-archive@odin.ietf.org; Wed, 14 May 2003 11: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 h4EFk0B26530 for ; Wed, 14 May 2003 11:46:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23647 for ; Wed, 14 May 2003 12:18:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Fyzq-00079e-00 for manet-web-archive@ietf.org; Wed, 14 May 2003 12:20:50 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Fyzp-00079b-00 for manet-web-archive@ietf.org; Wed, 14 May 2003 12:20:49 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4EFXDB25041; Wed, 14 May 2003 11:33: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 h4EFIFB24479 for ; Wed, 14 May 2003 11:18:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22753 for ; Wed, 14 May 2003 11:51:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FyZ0-0006yw-00 for manet@ietf.org; Wed, 14 May 2003 11:53:06 -0400 Received: from mailserver1.opnet.com ([12.145.55.23]) by ietf-mx with esmtp (Exim 4.12) id 19FyYz-0006yt-00 for manet@ietf.org; Wed, 14 May 2003 11:53:05 -0400 Received: from wtn11055.opnet.com (wtn11055.opnet.com [172.16.11.55]) by mailserver1.opnet.com (8.12.9/8.12.8) with ESMTP id h4EFs4FK010045 for ; Wed, 14 May 2003 11:54:04 -0400 (EDT) Message-Id: <5.1.0.14.2.20030514114220.01ccaf28@mailserver.opnet.com> X-Sender: jlee@mailserver.opnet.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 14 May 2003 11:54:04 -0400 To: manet@ietf.org From: Jay J Lee Subject: Re: [manet] A question concerning the DSR Opnet code In-Reply-To: References: <5.1.0.14.2.20030509203237.01ba8c38@mailserver.opnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-MailScanner: Not scanned: Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Ed, Please post your OPNET specific questions to the modeler_community@opnet.com or wireless_Community@opnet.com where other OPNET experts can give you more insights. I will also try to answer some of your questions in those mailing lists rather than going off in the MANET mailing list. - Jay At 12:44 AM 5/14/2003 -0400, you wrote: >Hi Jay, > > Thanks so much for your reply. I'm now providing below more details >and hope you can help me create a stream of data packets. And, because it >seems the contributed DSR model that I'm using right now already uses >its custom application that sends a data packet, I'm going to just go ahead >and modify it instead of using the OPNET-provided TCP/HTTP application. > > 1) This model has the followig node model: > > > receiver_sink src (with the "I" icon) > > > dsr_interface > > > dsr_routing_layer > > > wlan_mac_dsr_interface > > > wlan_mac_dsr_Sep00 > > > wireless_lan_receiver_0 wireless_lan_transmitter_0 > > > >In the above model, I'm focusing on dsr_interface, dsr_routing_layer, >and wlan_mac_dsr_interface, and am not touching wlan_mac_dsr_Sep00, which >I believe deals with the MAC layer transmissions and is not what I'm >concerned with. > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > 2)With some degree of certainty, I've now narrowed down my search for >the generator of upper-layer data packets to the following. It seems to me >that the upper-layer data packet is recieved (not generated, but received) >in a state called "tx" in dsr_interface, and it gets passed to a state >called "Upper_Layer_Arrival" in dsr_routing_layer, where the upper-layer >data packet gets encapsulated in a routing-layer data packet for >transmissions later. > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > 3)Specifically, the code in the Enter exec of the > dsr_interface-->tx state is the following: > > // Inside the tx state (Call it State 3) > > // extract the packet from the source stream > pk_ptr=op_pk_get(FROM_SRC_STRM); > > if (TRANSMIT) { //TRANSMIT is a SV & a model attribute default at Yes > // compute randomly a destination dsr address > destination_dsr_address=(int)op_dist_outcome(address_dist); > // check that this destination is not "myself" > while (destination_dsr_address==my_dsr_address) { > destination_dsr_address=(int)op_dist_outcome(address_dist); > } > // create and install an ici to communicate the > // dsr address of the packet destination to the dsr process model > iciptr = op_ici_create("Dsr_Dest_Ici"); > op_ici_attr_set(iciptr,"Packet_Destination",destination_dsr_address); > op_ici_install(iciptr); > > // send the packet to the DSR layer > printf("A packet to send to Node %d\n",destination_dsr_address); > op_pk_send (pk_ptr,TO_ROUTING_LAYER_STRM); > > // and update statistics > op_stat_write(stat_packet_transmited,++packet_transmited); > } > else { // if the node should not send any new packet > op_pk_destroy(pk_ptr) // destroy packet > } > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > 4)And the code in the Enter exec of > dsr_routing_layer-->Upper_Layer_Arrival state is the following: > > // Inside the Upper_Layer_Arrival state (call it State 4) > // extract the packet from the stream coming from the upper layer > pk_ptr = op_pk_get(FROM_UPPER_LAYER_STRM); > > // extract the dsr address of the packet destination from the ici > // associated strm interrupt > ici_dest_address = op_intrpt_ici(); > > op_ici_attr_get(ici_dest_address,"Packet_Destination", > &destination_dsr_address); > > // call the transmit data function > dsr_upper_layer_data_arrival(pk_ptr, destination_dsr_address); > // Note: in the function definition, it's > // dsr_upper_layer_data_arrival(Packet* data_pk_ptr, > // int destination_dsr_address); > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > 5)I inserted many printf lines throughout the node model to try to >trace how states transition from one to another. I am fairly certain to >say that from State 3 to State 4, it undergoes the following transition: > > State 3(i.e., the tx state) returns to the "idle" state of the >dsr_interface process, which then goes to State 4 (the >Upper_Layer_Arrival state) of the dsr_routing_layer process. > >So, as you see, the only state between 3 and 4 is the idle state of the >dsr_interface process. (A side note here: I was kind of expecting a >transition from the idle state of dsr_interface to the idle state of >dsr_routing_layer before reaching the Upper_Layer_Arrival state (i.e., >State 4), but appearantly that's not the case. Is there any reason why >this is not so?) > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > 6)In State 4, the function call dsr_upper_layer_data_arrival() >has some commands which are related to creating a routing-layer data packet, >i.e., the following lines appear in that function: > > // Create the data packet which is going to transport the upper layer > // packet, and set its Type field > pk_ptr=op_pk_create_fmt("Dsr_Data"); > op_pk_nfd_set(pk_ptr,"Type",DATA_PACKET_TYPE); > > // insert the upper layer data in the dsr data packet > op_pk_nfd_set(pk_ptr, "data", data_pk_ptr); > ... > ... > >where data_pk_ptr is the first argument in the function definition of >dsr_upper_layer_data_arrival(). > > *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** > > 7)So, State 3 above is as far back as I can trace to where the >upper-layer data packet comes from. Again, State 3, with its use of >"pk_ptr=op_pk_get(FROM_SRC_STRM)", tells me this upper-layer data packet >comes from somewhere still "further up". And this is where I got lost: I >don't know where this "further-up" place is. > > So I'm wondering, if it's not too much to ask, if you could help me >find the true source of where the true point of origin of the data packet >might be located. And, what I'd like to achieve is to generate a stream of >such data packets (say 10) to be transmitted to the same destination in my >simulations. If you could give me some directions on how to do that, I'll >be very grateful. I've been trying to do it with a number of things >myself, with your suggestions. For example, one thing I did was that at >the end of the State 3 code, following the last statement in the "if" >clause, (i.e., op_stat_write(stat_packet_transmited,++packet_transmited) ), >I tried to add the following lines: > > cp_pk_ptr=op_pk_copy(pk_ptr); // a copy of the current data packet > op_pk_send(cp_pk_ptr,TO_ROUTING_LAYER_STRM+1); > op_stat_write(stat_packet_transmited,++packet_transmited); > >just to see if I can somehow generate a second data packet. Of course, it >failed when running the simulation, and the following error occurs: > ><<< Program Abort >>> > * Time: 00:18:55 Wed May 14 2003 > * Product: modeler > * Package: process (dsr_interface) at module (top.Office >Network.mobile_node_11.dsr_intf) > * Function: sim_err_print (severity_level, str0, str1) > * Error: Packet pointer references unowned packet (0) > T (0.114926), EV (193), MOD > (top.Office Network.mobile_node_11.dsr_intf), > KP (op_pk_copy) > > >Which indicates the op_pk_copy is wrongfully used. > > So Jay, you are my savior if you can help me with my problem in >OPNET coding here. I don't yet have a good understanding of how the logic >behind state transitioning works yet, which I believe may be the key to >solve this issue (am I correct?). Your and expertise and guidance is very >much needed and appreciated. > > Thanks again, and hope to hear from you soon. I apologize for >dumping all this on you. > >Best, > >Ed > >------------------------------------------------------------------------- > >On Fri, 9 May 2003, Jay J Lee wrote: > > > In OPNET, "DATA" packets are usually generated by configuring either the > > typical (FTP, HTTP and etc.) or the custom application models. You could > > create a custom application which will generate a stream of UDP > > packets. The obvious advantage of this method is that you do not have to > > modify the code. Consult the OPNET product documentation for the detailed > > description of the custom application model. > > > > If you still have to modify the code, look for the kernel procedures for > > handling packets which should look like "op_pk_...". Basically you > want to > > make multiple copies of the packet using "op_pk_copy()" before it is sent > > out through "op_pk_send()". > > > > Good luck, - Jay > > > > At 02:58 PM 5/9/2003 -0400, you wrote: > > >Hi, > > > > > > I'm modifying a DSR OPNET code that I downloaded from NIST (It's a > > >Unix-based code, called nist_dsr_model.tar.pl). I have a question about > > >how to generate a stream of DATA packets and send them from the source to > > >destination. I'm not sure if this isn't the right venue for this > > >OPNET-related question, but appreciate whatever advice and help you can > > >give me. > > > > > > I've noticed that in this DSR code, after a route is found, > > >the source sends a single data packet to the destinatin on that route. In > > >other words, it seems that each source-destination connection session only > > >transmits one data packet. > > > > > > What I'd like to do is to send a stream of data packets (say, 10 of > > >them) from src to dest. To that end, I've been going over the code to see > > >where the first DATA packet is created. Because I'm very new with OPNET, I > > >have been unable to find it. So far, I'm narrowing my search down to the > > >dsr_upper_layer_data_arrival function, in the dsr_routing_layer process, > > >and the Enter executive of the Upper_Layer state in the same processs. I > > >have a hunch these two places are where I'm most likely to find that > > >generator of the data packets. But so far, I haven't pinpointed the exact > > >lines yet. My hope is that once I know how this single data packet is > > >generated, I'll be able to modify it (maybe some sort of for loop to let > > >it run 10 times?) to get a stream of DATA packets. > > > > > > So could someone with OPNET programming experience give me some help > > >on that? Maybe someone can tell me what "catchy words" or KPs in the > > >OPNET code I should be looking for with regard to generating DATA packets? > > >Thanks in advance. > > > > > >-Ed > > > > > > > > > > > > > > >_______________________________________________ > > >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 May 14 12:44:08 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26901 for ; Wed, 14 May 2003 12:44:08 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4EGAg529567 for manet-archive@odin.ietf.org; Wed, 14 May 2003 12:10: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 h4EGAgB29564 for ; Wed, 14 May 2003 12:10:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26832 for ; Wed, 14 May 2003 12:43:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FzNk-0007Px-00 for manet-web-archive@ietf.org; Wed, 14 May 2003 12:45:32 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19FzNj-0007Pu-00 for manet-web-archive@ietf.org; Wed, 14 May 2003 12:45:31 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4EFvGB27453; Wed, 14 May 2003 11:57: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 h4EFqvB27228 for ; Wed, 14 May 2003 11:52:57 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25350 for ; Wed, 14 May 2003 12:25:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Fz6Y-0007FP-00 for manet@ietf.org; Wed, 14 May 2003 12:27:46 -0400 Received: from amber.ccs.neu.edu ([129.10.116.51]) by ietf-mx with esmtp (Exim 4.12) id 19Fz6Y-0007FL-00 for manet@ietf.org; Wed, 14 May 2003 12:27:46 -0400 Received: from denali.ccs.neu.edu (denali.ccs.neu.edu [129.10.116.200]) by amber.ccs.neu.edu (Postfix) with ESMTP id 1AC9473FBC; Wed, 14 May 2003 12:28:53 -0400 (EDT) Date: Wed, 14 May 2003 12:28:53 -0400 (EDT) From: Guevara Noubir To: manet@ietf.org, mobile-ip@sunroof.eng.sun.com, MOBICOM@acm.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Reminder CFP: ACM Workshop on Wireless Security (WiSe) in conjunction with ACM MobiCom Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , ----------------------------------------------------------------- Our apologies if you receive multiple copies of the CFP. ----------------------------------------------------------------- Call for Papers ACM Workshop on Wireless Security (WiSe) in conjunction with ACM MobiCom 2003 September 19, 2003 San Diego, CA http://www.ece.cmu.edu/~adrian/wise2003 Sponsored by SIGMOBILE The workshop on Wireless Security will be held in conjunction with ACM MobiCom 2003. The objective of this workshop is to bring together researchers from research communities in wireless networking, security, applied cryptography, and dependability; with the goal of fostering interaction. With the proliferation of wireless networks, issues related to secure and dependable operation of such networks are gaining importance. Topics of interest include, but are not limited to: * Key management in wireless/mobile environments * Trust establishment * Intrusion detection, detection of malicious behaviour * Revocation of malicious parties * Secure PHY/MAC/routing protocols * Secure location determination * Denial of service * User privacy * Anonymity, prevention of traffic analysis * Dependable wireless networking * Monitoring and surveillance Paper submission instructions: Submission of papers based on work-in-progress is encouraged. Submitted papers must not be previously published elsewhere or currently under review for any other publication. Please direct any questions about the paper submission process to the Program Co-Chairs. All paper submissions will be handled electronically. Authors should prepare a PostScript or Portable Document Format (PDF) version of their paper. Papers must meet the following restrictions: No longer than 10 pages (single or double column); in font no smaller than 11 points; must fit properly on US Letter-sized paper (8.5 inch x 11 inch) with reasonable margins. Instructions for electronic submission of papers will be posted at http://www.ece.cmu.edu/~adrian/wise2003/submission.html Important dates: Paper submissions due: May 27, 2003 Notification of acceptance: July 25, 2003 Camera-ready papers due: August 1, 2003 Workshop date: September 19, 2003 Workshop Co-Chairs: * Douglas Maughan, Defense Advanced Research Projects Agency (dmaughan@darpa.mil) * Adrian Perrig, Carnegie Mellon University (perrig@cmu.edu) Program Committee: Bill Arbaugh, University of Maryland Brian Noble, University of Michigan Brian Van Leeuwen, Sandia National Laboratories Chinya Ravishankar, University of California at Riverside Jean-Pierre Hubaux, Swiss Federal Institute of Technology, Lausanne Jonathan Smith, University of Pennsylvania Leendert van Doorn, IBM Markus Jakobsson, RSA Security Radha Poovendran, University of Washington Stephen Zabele, Alphatech Wenke Lee, Georgia Institute of Technology Yair Amir, Johns Hopkins University Publicity Co-Chairs: Mohsen Guizani, University of West Florida Guevara Noubir, Northeastern University Publication Chair: Saad Biaz, Auburn University Registration Chair: Robin Kravets, University of Illinois at Urbana-Champaign Treasurer Yongguang Zhang, HRL Labs and UT-Austin _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu May 15 13:36:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16108 for ; Thu, 15 May 2003 13:36:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4FH3Re18358 for manet-archive@odin.ietf.org; Thu, 15 May 2003 13: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 h4FH3RB18355 for ; Thu, 15 May 2003 13:03:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16104 for ; Thu, 15 May 2003 13:35:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GMfp-00011s-00 for manet-web-archive@ietf.org; Thu, 15 May 2003 13:37:45 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19GMfo-00011o-00 for manet-web-archive@ietf.org; Thu, 15 May 2003 13:37:44 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4FGYQB15911; Thu, 15 May 2003 12: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 h4FGPXB15598 for ; Thu, 15 May 2003 12:25:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15072 for ; Thu, 15 May 2003 12:57:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GM5A-0000lu-00 for manet@ietf.org; Thu, 15 May 2003 12:59:52 -0400 Received: from letters.cs.ucsb.edu ([128.111.41.13]) by ietf-mx with esmtp (Exim 4.12) id 19GM59-0000lq-00 for manet@ietf.org; Thu, 15 May 2003 12:59:51 -0400 Received: from yosemite.cs.ucsb.edu (yosemite [128.111.40.103]) by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with ESMTP id h4FH0sC24746; Thu, 15 May 2003 10:00:58 -0700 (PDT) From: Elizabeth Belding-Royer To: manet@ietf.org Cc: corson@flarion.com, ebelding@cs.ucsb.edu Content-Type: text/plain Message-Id: <1053018054.26200.16.camel@yosemite.cs.ucsb.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 15 May 2003 10:00:54 -0700 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] IRTF ANS Meeting Announcement Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 Announcement and Call for Participation --------------------------------------- The first meeting of the new IRTF Ad hoc Network Scalability (ANS) Research Group will be held on Sunday, June 1st, from 7-10pm, in conjunction with the Mobihoc 2003 Symposium in Annapolis, Maryland. The focus of the group is to investigate scalability techniques for ad hoc mobile networks. Insufficient understanding of the basic scalability problem exists within the IETF community to properly address the development of large-scale, ad hoc network routing standards. We are seeking presentations on recent research that addresses the scalability of ad hoc networks in a number of areas: * definition of scalability metrics * definition of "black box" criteria by which routing protocol performance/stability may be measured * exploration of protocol attributes and mechanisms that affect scalability/performance - Proacitve/Reactive/Hybrid routing mechanisms - QoS mechanisms - Address assignment mechanisms The aim of the RG is to seek to develop an understanding of the basic dynamics of large-scale routing in various dynamic network contexts (e.g. standalone and hybrid fixed/ad hoc), and attempt to identify key attributes and properties necessary for a feasible, scalable routing protocol. If you would like to give a presentation, please email corson@flarion.com and ebelding@cs.ucsb.edu with up to 1 page describing your research and your results. We will announce the meeting schedule closer to the meeting date. The meeting will consist of continued discussion from the group mailing list on the specific direction of the group, as well as presentations on the above scalability topics. One of the first milestones of the group is to produce an Informational RFC detailing the dimensions along which scalability can be defined. The ANS RG website can be found at http://www.flarion.com/ans-research This website includes the charter of the research group and information for subscribing to the group mailing list. We are looking forward to this first meeting and encourage participation from persons both previously and not previously involved with the IETF MANET working group. Scott and Elizabeth _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 16 11:40:35 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29902 for ; Fri, 16 May 2003 11:40:35 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4GF88j19328 for manet-archive@odin.ietf.org; Fri, 16 May 2003 11:08: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 h4GF87B19325 for ; Fri, 16 May 2003 11:08:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29868 for ; Fri, 16 May 2003 11:40:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GhLJ-0000bb-00 for manet-web-archive@ietf.org; Fri, 16 May 2003 11:41:57 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19GhLJ-0000bY-00 for manet-web-archive@ietf.org; Fri, 16 May 2003 11:41:57 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4GEerB16943; Fri, 16 May 2003 10:40: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 h4GEYHB15809 for ; Fri, 16 May 2003 10:34:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28426 for ; Fri, 16 May 2003 11:06:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ggoa-0000H7-00 for manet@ietf.org; Fri, 16 May 2003 11:08:08 -0400 Received: from moby.atcorp.com ([204.72.172.2]) by ietf-mx with esmtp (Exim 4.12) id 19GgoZ-0000H0-00 for manet@ietf.org; Fri, 16 May 2003 11:08:07 -0400 Received: from mahi-mahi (mahi-mahi.atcorp.com [204.72.172.9]) by moby.atcorp.com (8.11.6/8.11.2) with SMTP id h4GF9lu31577 for ; Fri, 16 May 2003 10:09:47 -0500 Received: by localhost with Microsoft MAPI; Fri, 16 May 2003 10:11:33 -0500 Message-ID: <01C31B93.86CF9780.mkaddoura@atcorp.com> From: Maher Kaddoura Reply-To: "mkaddoura@atcorp.com" To: "'manet@ietf.org'" Date: Fri, 16 May 2003 10:11:32 -0500 Organization: ATC X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] Local route repair Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, I am trying to develop a method to reconnect a route when it breaks, by trying to connect the node where there break took place to a node downstream from it along the route. However, all the method that I developed so far causes loops. I was wondering if anyone was able to solve this problem. Thank you, Maher _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 16 12:21:14 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01448 for ; Fri, 16 May 2003 12:21:13 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4GFml322389 for manet-archive@odin.ietf.org; Fri, 16 May 2003 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 h4GFmlB22386 for ; Fri, 16 May 2003 11:48:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01437 for ; Fri, 16 May 2003 12:20:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ghye-0000xR-00 for manet-web-archive@ietf.org; Fri, 16 May 2003 12:22:36 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Ghyd-0000xO-00 for manet-web-archive@ietf.org; Fri, 16 May 2003 12:22:35 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4GFUcB20460; Fri, 16 May 2003 11:30: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 h4GFPNB20268 for ; Fri, 16 May 2003 11:25:23 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00698 for ; Fri, 16 May 2003 11:57:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ghc0-0000nP-00 for manet@ietf.org; Fri, 16 May 2003 11:59:12 -0400 Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu) by ietf-mx with esmtp (Exim 4.12) id 19Ghbz-0000nM-00 for manet@ietf.org; Fri, 16 May 2003 11:59:12 -0400 Received: by mail.eecis.udel.edu (Postfix, from userid 62) id D0C16329D5; Fri, 16 May 2003 12:00:22 -0400 (EDT) Received: from buckwheat.cis.udel.edu (buckwheat.cis.udel.edu [128.4.131.43]) by mail.eecis.udel.edu (Postfix) with ESMTP id 20019329AE; Fri, 16 May 2003 12:00:22 -0400 (EDT) Date: Fri, 16 May 2003 12:00:22 -0400 (EDT) From: Sonny Rajagopalan X-X-Sender: To: Maher Kaddoura Cc: "'manet@ietf.org'" Subject: Re: [manet] Local route repair In-Reply-To: <01C31B93.86CF9780.mkaddoura@atcorp.com> Message-ID: X-Spam-Status: No, hits=-4.2 required=6.0 tests=DEPT_RCVD,EMAIL_ATTRIBUTION,IN_REP_TO,SPAM_PHRASE_02_03, USER_AGENT_PINE version=2.43 X-Sanitizer: This message has been sanitized! X-Sanitizer-URL: http://mailtools.anomy.net/ X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0 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: , Two methods that will guarantee loop freedom (a) use source routing! (b) use sequence numbers for routing information updates. Cheers, Sonny. ---- >From the desk of Sonny Rajagopalan @ http://www.cis.udel.edu/~rajagopa ---- On Fri, 16 May 2003, Maher Kaddoura wrote: > 7bit > MIME-Version: 1.0 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > 7bit > > Hi, > > I am trying to develop a method to reconnect a route when it breaks, by trying to connect > the node where there break took place to a node downstream from it along the route. > However, all the method that I developed so far causes loops. I was wondering if anyone > was able to solve this problem. > > Thank you, > > Maher > > _______________________________________________ > 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 May 16 12:31:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01877 for ; Fri, 16 May 2003 12:31:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4GFwsX23194 for manet-archive@odin.ietf.org; Fri, 16 May 2003 11:58: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 h4GFwpB23189 for ; Fri, 16 May 2003 11:58:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01838 for ; Fri, 16 May 2003 12:30:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Gi8O-000150-00 for manet-web-archive@ietf.org; Fri, 16 May 2003 12:32:40 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Gi8N-00014x-00 for manet-web-archive@ietf.org; Fri, 16 May 2003 12:32:39 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4GFgiB21956; Fri, 16 May 2003 11:42: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 h4GFaCB20765 for ; Fri, 16 May 2003 11:36:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00929 for ; Fri, 16 May 2003 12:08:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GhmU-0000qx-00 for manet@ietf.org; Fri, 16 May 2003 12:10:02 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19GhmT-0000qo-00 for manet@ietf.org; Fri, 16 May 2003 12:10:01 -0400 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 JAA00429; Fri, 16 May 2003 09:10:40 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h4GGAdY24156; Fri, 16 May 2003 09:10:39 -0700 X-mProtect: <200305161610> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdLPsOHg; Fri, 16 May 2003 09:10:37 PDT Message-ID: <3EC50D7E.F4A801D0@iprg.nokia.com> Date: Fri, 16 May 2003 09:10:38 -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: "mkaddoura@atcorp.com" CC: "'manet@ietf.org'" Subject: Re: [manet] Local route repair References: <01C31B93.86CF9780.mkaddoura@atcorp.com> 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 Maher, AODV specifies a loop-free route repair mechanism that does what you request. Regards, Charlie P. Maher Kaddoura wrote: > > Hi, > > I am trying to develop a method to reconnect a route when it breaks, by trying to connect > the node where there break took place to a node downstream from it along the route. > However, all the method that I developed so far causes loops. I was wondering if anyone > was able to solve this problem. > > Thank you, > > Maher > > _______________________________________________ > 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 May 16 15:53:57 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09457 for ; Fri, 16 May 2003 15:53:57 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4GJLY806249 for manet-archive@odin.ietf.org; Fri, 16 May 2003 15:21: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 h4GJLYB06246 for ; Fri, 16 May 2003 15:21:34 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09443 for ; Fri, 16 May 2003 15:53:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GlIU-0002Yo-00 for manet-web-archive@ietf.org; Fri, 16 May 2003 15:55:18 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19GlIT-0002Yk-00 for manet-web-archive@ietf.org; Fri, 16 May 2003 15:55:17 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4GIxMB04243; Fri, 16 May 2003 14:59: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 h4GIjwB03807 for ; Fri, 16 May 2003 14:45:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08561 for ; Fri, 16 May 2003 15:17:51 -0400 (EDT) From: idc@engineering.ucsb.edu Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Gkk3-0002MA-00 for manet@ietf.org; Fri, 16 May 2003 15:19:43 -0400 Received: from letters.cs.ucsb.edu ([128.111.41.13]) by ietf-mx with esmtp (Exim 4.12) id 19Gkk2-0002M6-00 for manet@ietf.org; Fri, 16 May 2003 15:19:42 -0400 Received: from KENAI.cs.ucsb.edu (cypress [128.111.40.165]) by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with ESMTP id h4GJKmC07715; Fri, 16 May 2003 12:20:49 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16069.14859.437000.189107@gargle.gargle.HOWL> Date: Fri, 16 May 2003 12:20:43 -0700 To: MANET Mailing List X-Mailer: VM 7.07 under Emacs 21.1.1 Reply-To: idc@cs.ucsb.edu Content-Transfer-Encoding: 7bit Subject: [manet] Gilbert Error Model Settings Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 anyone out there using the Gilbert error model while simulating MANET? I'm looking for realistic settings (or functions) for the time spent in each state, probability of transition between states and error probability for IEEE 802.11. Even if you don't have realistic values but just use certain values, what values are you using and why? Thanks in advance for any replies. Ian Chakeres _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat May 17 09:42:47 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07291 for ; Sat, 17 May 2003 09:42:47 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4HDAko14826 for manet-archive@odin.ietf.org; Sat, 17 May 2003 09:10: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 h4HDAiB14823 for ; Sat, 17 May 2003 09:10:44 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07286 for ; Sat, 17 May 2003 09:42:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19H1yo-0006pa-00 for manet-web-archive@ietf.org; Sat, 17 May 2003 09:44:06 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19H1yo-0006pX-00 for manet-web-archive@ietf.org; Sat, 17 May 2003 09:44:06 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4HCpPB13305; Sat, 17 May 2003 08:51: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 h4HCiwB13191 for ; Sat, 17 May 2003 08:44:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07038 for ; Sat, 17 May 2003 09:16:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19H1Zr-0006jm-00 for manet@ietf.org; Sat, 17 May 2003 09:18:19 -0400 Received: from [61.140.60.52] (helo=21cn.com) by ietf-mx with smtp (Exim 4.12) id 19H1Zm-0006jj-00 for manet@ietf.org; Sat, 17 May 2003 09:18:15 -0400 Received: from 21cn.com([127.0.0.1]) by 21cn.com(AIMC 2.9.5.6) with SMTP id jm123ec69360; Sat, 17 May 2003 21:30:38 +0800 Received: from 21cn.com([10.2.2.4]) by 21cn.com(AIMC 2.9.5.6) with SMTP id jmc3ec67750; Sat, 17 May 2003 21:30:38 +0800 Content-Type: text/plain MIME-Version: 1.0 Message-ID: X-AIMailer: AIMC 2.9.5.6 2002.10.10 X-AIMime: MIME/SMIME Lib 2.9 2.9 2002.10.10 Date: Sat, 17 May 2003 21:14:44 +0800 (CST) From: "安辉" To: manet@ietf.org X-Priority: 3 X-Originating-IP: 61.187.56.10 X-AIMC-AUTH: (null) X-AIMC-MAILFROM: anthony_cs@21cn.com Subject: [manet] some advice or document about rsvp in ad hoc networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , X-MIME-Autoconverted: from 8bit to base64 by www1.ietf.org id h4HCpPB13305 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h4HDAiB14823 Content-Transfer-Encoding: 8bit Hi,anybody.I'm ready to research rsvp in Ad hoc networks.Anybody know about the document or paper about it and give me advice about it.thanks great! Best regards ---------------------------------------------- 免费玩苹果派网络游戏，用21CN邮箱注册送彩屏手机及价值数十万的精美奖品 http://www.appie.com.cn 留给张国荣最爱的说话 http://sms.21cn.com/leslie/ 健康性观念享受美妙的时刻 http://sms.21cn.com/sexxy.jsp 21CN彩信邮，声色彩信，自由收发 http://mail.21cn.com/huodong/0304/ 新增HTML编辑器，令邮件更出色 http://mail.21cn.com/bijiao/02.html _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun May 18 07:34:43 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07051 for ; Sun, 18 May 2003 07:34:43 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4IB39I04343 for manet-archive@odin.ietf.org; Sun, 18 May 2003 07:03: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 h4IB39B04340 for ; Sun, 18 May 2003 07:03:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07041 for ; Sun, 18 May 2003 07:34:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19HMSR-0003G9-00 for manet-web-archive@ietf.org; Sun, 18 May 2003 07:36:03 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19HMSR-0003G5-00 for manet-web-archive@ietf.org; Sun, 18 May 2003 07:36:03 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4IAkbB03765; Sun, 18 May 2003 06:46: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 h4IAgSB03652 for ; Sun, 18 May 2003 06:42:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06823 for ; Sun, 18 May 2003 07:13:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19HM8Q-0003B8-00 for manet@ietf.org; Sun, 18 May 2003 07:15:22 -0400 Received: from mail.flarion.com ([63.103.94.23] helo=rrmail01.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 19HM8P-0003Ay-00 for manet@ietf.org; Sun, 18 May 2003 07:15:21 -0400 Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2656.59) id ; Sun, 18 May 2003 07:16:07 -0400 Message-ID: <748C6D0A58C0F94CA63C198B6674697A01510DF8@ftmail.lab.flarion.com> From: Scott Corson To: "'manet@ietf.org'" Date: Sun, 18 May 2003 07:16:03 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain Subject: [manet] FW: : Re: Routing Directorate Review Comments on draft-ietf-mane t-tbrpf-08.txt Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Folks, FYI... here are some comments on TBRPF from its Routing Directorate review and a corresponding response. Some of the items have more general applicability. Cheers, -Scott Monday, May 12, 2003, 11:39:28 PM, mike shand wrote: >>To: mike shand >>cc: ogier@erg.sri.com, lewis@erg.sri.com, ftemplin@iprg.nokia.com, >> Joseph Macker , >> Scott Corson >>Reply-To: ogier@erg.sri.com >>From: ogier@erg.sri.com >>Subject: Re: Routing Directorate Review Comments on >>draft-ietf-manet-tbrpf-08.txt >>Date: Mon, 12 May 2003 12:54:09 -0700 >>Sender: ogier@erg.sri.com >> >> >>Hello Mike, >> >>Thank you for comments/questions. I have discussed them with >>Mark Lewis and Fred Templin. Please see our responses below. >> >> > I am conducting a routing directorate (rtg-dir) review of this draft, and >> > I have a few (relatively trivial) comments/questions. I would be grateful >> > for your responses. >> > >> > Mike Shand >> > >> > >> > >> > >> > 1. Introduction >> > >> > The term "proactive routing protocol" has a specific meaning >> within the >> > MANET context. It might be useful for readers unfamiliar with the concept >> > to give a brief definition in the "terminology" section. >> >>We can add the following definition: >> >> Proactive routing protocol >> A routing prototocol in which each node maintains routes to all >> reachable >> destinations at all times, whether or not there is currently any need to >> deliver packets to those destinations. In contrast, an "on-demand" >> routing >> protocol discovers and maintains routes only when they are needed. >> >> > >> > 4. Applicability Section >> > >> > Is there some evidence to support the claim "it can support networks with >> > up to a few hundred nodes".? >> > e.g. that is the design scope, or simulations and or implementations >> > support this. >> >>We can change this to the following: >> >> Simulations have shown that TBRPF can support up to 250 nodes >> in mobile networks using IEEE 802.11 with a data rate of 2 Mbps. >> The number of nodes that can be supported depends on several factors, >> including the data rate, the rate of topology changes, and the network >> density (average number of neighbors)." >> >> > 5.1 Overview of neighbor discovery >> > >> > There seems to be an inconsistency in the use of MUST/MAY in this section >> > (and possibly in other sections as well). >> > >> > In para 7 "must" appears uncapitalized. This seems reasonable, given that >> > this is just an overview. >> > >> > However, in the last para we have "MAY". >> >>We will change this so that only lower case "must"s and "may"s are used in >>the overview section. There is another "MAY" in Section 5.2 (Overview of >>Routing) that will also be changed to lower case. >> >> > 6.1 TBRFP Packet header >> > F- flag extension. Should it say that when using F to insert single octet >> > of padding, the flag extension bits MUST be zero? >> >>OK, we will change this to make it clear. >>(However, I think it is already implied.) >> >> > C- Checksum included. >> > The phrase "a 16 bit checksum beginning in the first octet of the header >> > extension" is ambiguous, since it is not (yet) clear whether the >> > "beginning" refers to the data over which the checksum is calculated, or >> > the location of the computed checksum. Subsequent text reveals that it is >> > the latter, but this could be made clear by saying something like >> > >> > "a 16 bit checksum in the first two octets of the header extension". >> >>OK. We will use your suggested wording. >> >> > Also, this mechanism means that a single bit error (clearing the C bit) >> can >> > result in undetected corruption. Note that in this case the 16 bits of >> > checksum will be interpreted as something else. Is that a concern? >> >>Good point. We can fix this by eliminating the C bit and always including >>the checksum. >> >> > >> > 6.2 TBRPF Packet Body >> > >> > This use of TLVs is somewhat strange. Normally the L field is always >> > present immediately after the T field and hence a new (and not recognized) >> > type can be introduced, such that it is simply parsed over and ignored. >> > This cannot be done with the proposed structure. IPv6 option TLVs DO have >> > the normal property. It is probably confusing to call the TBRPF >> messages TLVs >> >>Good point. We will remove the reference to TLV. I think this was left >>over from a previous version of TBRPF that included the L field. >>We omitted the L field in order to minimize overhead, which is an >>important objective for MANETs. >> >> > The draft doesn't say what to do with non-recognized type values. Drop the >> > packet? >> >>Yes, we will add that no further messages in the packet are to be >>processed when a non-recognized type is encountered. (Since messages >>are processed in order, this still allows new types to be introduced >>in future versions, as long as new message types are placed after >>old message types in a given packet.) >> >> > >> > 6.2.1 Padding Options >> > >> > Senders MAY >> >>OK. >> >> > Is the use of the F bit to insert a one octet pad redundant because of >> the >> > existence of the Pad1 option? Or are the two intended to serve different >> > purposes. (the former inserts padding prior to the length and router ID >> > header extensions). It seems odd to have TWO mechanisms to achieve the >> same >> > ends. >> >>You are correct that the two mechanisms are intended to serve different >>purposes, since the Pad1 option cannot be used to separate the first >>octet of the header from any header extensions that follow. >> >> > >> > 7.8 Configurable parameters. >> > >> > MAX_JITTER Jitter is usually expressed as a percentage, not an absolute >> > value, and value of 25% is typical. Is there a particular reason for >> > specifying it this way? >> >>I have seen it both ways. Is there a good technical reason for using >>percentage instead of an absolute value? >>Can you give me a well-known reference that uses percentage? >> >>It seems to me that the amount of jitter required to avoid collisions is >>best expressed as an absolute value (e.g., 0.1 sec), which does not depend >>on the HELLO interval. >> >>One reason for not expressing it as a percentage is that this might >>unintentionally imply that it is OK, for example, to reduce the HELLO >>interval from 1 sec to .1 sec while keeping the jitter at 10%. >>(10% would be OK for 1 sec but is probably too small for .1 sec.) >> >>Also, a larger jitter increases overhead (since it is subtracted and >>therefore >>results in more frequent messages) so we want to keep it at a minimum. >>For example, we would not want to use .25 sec if .1 sec is sufficient. >> >> > >> > 10.6 Support for nonMANET Hosts >> > >> > Should there be a section about how a TBRPF domain interfaces with the >> > internet at large? Are there any special considerations? Or is everything >> > which needs to be covered dealt with in section 10.5? >> >>Note that Network Prefix messages are described in in detail Section 8. >>(Section 10.5 discusses how these messages might be used in MANETs.) >> >>We believe that anything beyond this is beyond the scope of the document >>(e.g., how to obtain a global address from a gateway or the use of mobile >>IP). >>We do note in Section 8.1 that gateway routers can advertise default >>prefixes. >>If you think it would help, we could explain more clearly (in a few sentences) >>that gateway routers can be used to provide Internet connectivity and that >>they can use Network Prefix messages to advertise external prefixes to the >>MANET nodes. >> >> > >> > That's all I have. I haven't reviewed the protocol specification for >> > correctness. I assume the authors and WG have already done that:-) >> > >> >>----------------------- >>Richard Ogier >>Sr. Research Engineer >>SRI International >>333 Ravenswood Ave. >>Menlo Park, CA 94025 >>Tel: 650-859-4216 >>Fax: 650-859-4812 >>Email: ogier@erg.sri.com >>------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed May 28 16:18:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21794 for ; Wed, 28 May 2003 16:18:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4SKIE907077 for manet-archive@odin.ietf.org; Wed, 28 May 2003 16:18: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 h4SKIEB07074 for ; Wed, 28 May 2003 16:18:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21786 for ; Wed, 28 May 2003 16:18:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19L7Lf-0007L3-00 for manet-web-archive@ietf.org; Wed, 28 May 2003 16:16:35 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19L7Lf-0007Kz-00 for manet-web-archive@ietf.org; Wed, 28 May 2003 16:16:35 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4SK6fB05407; Wed, 28 May 2003 16:06: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 h4SJsqB04919 for ; Wed, 28 May 2003 15:54:52 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20425 for ; Wed, 28 May 2003 15:54:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19L6z4-0006xr-00 for manet@ietf.org; Wed, 28 May 2003 15:53:14 -0400 Received: from [164.41.67.130] (helo=webserver.redes.unb.br) by ietf-mx with esmtp (Exim 4.12) id 19L6z0-0006x4-00 for manet@ietf.org; Wed, 28 May 2003 15:53:12 -0400 Received: from piqui (redesfw.redes.unb.br [164.41.67.254]) by webserver.redes.unb.br (8.12.9/8.12.5) with SMTP id h4SJseIJ027996 for ; Wed, 28 May 2003 16:54:40 -0300 Message-ID: <00a401c32554$40f933e0$0e43a8c0@piqui> From: =?iso-8859-1?Q?F=E1bio_Buiati?= To: Date: Wed, 28 May 2003 17:03:48 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-MIME-Autoconverted: from 8bit to quoted-printable by webserver.redes.unb.br id h4SJseIJ027996 X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4SJsqB04920 Subject: [manet] Autoconfiguration Implementation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , X-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h4SK6fB05407 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4SKIEB07074 Content-Transfer-Encoding: 8bit Hi all, Is there an implementation of these protocols? . DCDP (Dynamic Configuration Distribution Protocol) . DHCP (Dynamic Host Configuration Protocol) . DRCP (Dynamic and Rapid Configuration Protocol) Is there a daemon? Thanks a lot. --------------------------------------------------- F醔io Mesquita Buiati Universidade de Bras韑ia - Brazil email - fabio@redes.unb.br --------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu May 29 07:34:10 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27572 for ; Thu, 29 May 2003 07:34:10 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4TBXfd12798 for manet-archive@odin.ietf.org; Thu, 29 May 2003 07:33: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 h4TBXfB12795 for ; Thu, 29 May 2003 07:33:41 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27553 for ; Thu, 29 May 2003 07:33:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LLdZ-0005b3-00 for manet-web-archive@ietf.org; Thu, 29 May 2003 07:32:01 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19LLdZ-0005b0-00 for manet-web-archive@ietf.org; Thu, 29 May 2003 07:32:01 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TBOLB12133; Thu, 29 May 2003 07:24: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 h4TBJOB11957 for ; Thu, 29 May 2003 07:19:24 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26741; Thu, 29 May 2003 07:19:23 -0400 (EDT) Message-Id: <200305291119.HAA26741@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: manet@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 29 May 2003 07:19:22 -0400 Subject: [manet] I-D ACTION:draft-jeong-adhoc-ip-addr-autoconf-00.txt Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Ad Hoc IP Address Autoconfiguration Author(s) : J. Jeong et al. Filename : draft-jeong-adhoc-ip-addr-autoconf-00.txt Pages : 11 Date : 2003-5-28 This document specifies the steps a node in ad hoc network takes in deciding how to autoconfigure its IPv4 or IPv6 address in network interface. Because the ad hoc IP address autoconfiguration in this document considers ad hoc network's partition and mergence, the address duplication that can be caused by ad hoc network's mergence can be resolved. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-jeong-adhoc-ip-addr-autoconf-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-5-29072616.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-jeong-adhoc-ip-addr-autoconf-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-5-29072616.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu May 29 20:29:05 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29610 for ; Thu, 29 May 2003 20:29:05 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4U0Sb503620 for manet-archive@odin.ietf.org; Thu, 29 May 2003 20:28: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 h4U0SbB03617 for ; Thu, 29 May 2003 20:28:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA29547 for ; Thu, 29 May 2003 20:28:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LXjU-0004sB-00 for manet-web-archive@ietf.org; Thu, 29 May 2003 20:26:56 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19LXjT-0004s7-00 for manet-web-archive@ietf.org; Thu, 29 May 2003 20:26:55 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U0ItB02962; Thu, 29 May 2003 20:18: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 h4U0C6B02712 for ; Thu, 29 May 2003 20:12:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA28773 for ; Thu, 29 May 2003 20:12:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LXTV-0004d0-00 for manet@ietf.org; Thu, 29 May 2003 20:10:25 -0400 Received: from letters.cs.ucsb.edu ([128.111.41.13]) by ietf-mx with esmtp (Exim 4.12) id 19LXTU-0004cr-00 for manet@ietf.org; Thu, 29 May 2003 20:10:24 -0400 Received: from yosemite.cs.ucsb.edu (yosemite [128.111.40.103]) by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with ESMTP id h4U0BoC02707; Thu, 29 May 2003 17:11:50 -0700 (PDT) From: Elizabeth Belding-Royer To: ans-research@www1.ietf.org, manet@ietf.org Cc: corson@flarion.com, ebelding@cs.ucsb.edu Content-Type: text/plain Message-Id: <1054253509.24461.64.camel@yosemite.cs.ucsb.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 29 May 2003 17:11:49 -0700 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] IRTF ANS Meeting Announcement Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 meeting of the new IRTF Ad hoc Network Scalability (ANS) research group will occur this Sunday at the Mobihoc conference hotel. Included is the agenda for this meeting. This is a somewhat fluid agenda as we are still finalizing the speakers. However, the meeting will definitely start at 7pm Sunday evening. We look forward to seeing many of you at the meeting. Scott and Elizabeth ***************************************************************** Date: Sunday, June 1, 2003 Time: 7-10pm Location: Sheraton Barcelo Hotel (Mobihoc hotel) I don't have the exact room at the moment - an email will be sent later with that information. Scott and Elizabeth (10 min) - Welcome - Overview of research group charter, objectives Scott and Elizabeth (30 min) - Recap of mailing list discussion on direction of research group - Group discussion on direction/objectives Presentations * Zygmunt Haas (20 min) - Hybridization and Adaptivity as Means to Scalability - Scalability Bounds in Wireless Networks * Joe Macker (15 min) - Link state scaling approaches * Mario Gerla (15 min) - Routing approaches and scalability metrics. * Radha Poovendran (15 min) - Greedy Perimeter Routing * Christian Bettstetter (15 min) - Interconnection of Ad hoc Networks to IPv6 Networks Open Forum for Discussions (1 hour) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu May 29 21:23:31 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02696 for ; Thu, 29 May 2003 21:23:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4U1N5807940 for manet-archive@odin.ietf.org; Thu, 29 May 2003 21:23: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 h4U1N4B07937 for ; Thu, 29 May 2003 21:23:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02571 for ; Thu, 29 May 2003 21:23:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LYaA-0005i1-00 for manet-web-archive@ietf.org; Thu, 29 May 2003 21:21:22 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19LYa9-0005hy-00 for manet-web-archive@ietf.org; Thu, 29 May 2003 21:21:21 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U1CAB07396; Thu, 29 May 2003 21:12: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 h4U18rB07260 for ; Thu, 29 May 2003 21:08:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01584 for ; Thu, 29 May 2003 21:08:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LYMQ-0005Ok-00 for manet@ietf.org; Thu, 29 May 2003 21:07:10 -0400 Received: from nn3.excitenetwork.com ([207.159.120.57] helo=xmxpita.excite.com) by ietf-mx with esmtp (Exim 4.12) id 19LYMQ-0005Og-00 for manet@ietf.org; Thu, 29 May 2003 21:07:10 -0400 Received: by xmxpita.excite.com (Postfix, from userid 110) id 14D563E1C; Thu, 29 May 2003 21:08:15 -0400 (EDT) To: manet@ietf.org Received: from [172.159.68.115] by xprdmailfe6.nwk.excite.com via HTTP; Thu, 29 May 2003 21:08:14 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b2a1836c3aaf6ef26199249a5725f5d0 Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: multipart/alternative; boundary="EXCITEBOUNDARY_000__0e9f813a5abe907c6ba450991a036cf6"; Content-Transfer-Encoding: 7bit Message-Id: <20030530010815.14D563E1C@xmxpita.excite.com> Date: Thu, 29 May 2003 21:08:15 -0400 (EDT) Subject: [manet] simulator for 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: , --EXCITEBOUNDARY_000__0e9f813a5abe907c6ba450991a036cf6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi All: Besides Qualnet, are there other commercial softwares for simulation of ad hoc networks? Thanks, Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! --EXCITEBOUNDARY_000__0e9f813a5abe907c6ba450991a036cf6 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
Hi All:

Besides Qualnet, are there other commercial softwares for simulation of ad hoc networks?

Thanks,

Jack




Join Excite! - http://www.excite.com
The most personalized portal on the Web! --EXCITEBOUNDARY_000__0e9f813a5abe907c6ba450991a036cf6-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 30 03:20:48 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22480 for ; Fri, 30 May 2003 03:20:48 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4U7KJ708991 for manet-archive@odin.ietf.org; Fri, 30 May 2003 03:20: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 h4U7KIB08987 for ; Fri, 30 May 2003 03:20:18 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22470 for ; Fri, 30 May 2003 03:20:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Le9u-0000Ut-00 for manet-web-archive@ietf.org; Fri, 30 May 2003 03:18:38 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Le9t-0000Uq-00 for manet-web-archive@ietf.org; Fri, 30 May 2003 03:18:37 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4U77kB08444; Fri, 30 May 2003 03:07: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 h4U6wQB07304 for ; Fri, 30 May 2003 02:58:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21766 for ; Fri, 30 May 2003 02:58:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ldof-0000Ik-00 for manet@ietf.org; Fri, 30 May 2003 02:56:41 -0400 Received: from mail-relay-1.warwick.ac.uk ([137.205.128.7] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19Ldof-0000Ih-00 for manet@ietf.org; Fri, 30 May 2003 02:56:41 -0400 Received: from dominator.csv.warwick.ac.uk (host-97-8-205-137 [137.205.8.97]) by mail-relay-1.csv.warwick.ac.uk (8.12.9/8.12.9) with ESMTP id h4U6wF6f014781 for ; Fri, 30 May 2003 07:58:16 +0100 (BST) Received: from Warwick-MTA by dominator.csv.warwick.ac.uk with Novell_GroupWise; Fri, 30 May 2003 07:58:14 +0100 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.3 Date: Fri, 30 May 2003 07:57:59 +0100 From: "Zurkarmawan Abu Bakar" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4U6wQB07305 Subject: [manet] (no subject) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri May 30 10:38:49 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10779 for ; Fri, 30 May 2003 10:38:49 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4UEcOv08730 for manet-archive@odin.ietf.org; Fri, 30 May 2003 10:38: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 h4UEcOB08727 for ; Fri, 30 May 2003 10:38:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10756 for ; Fri, 30 May 2003 10:38:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Lkzn-0005ET-00 for manet-web-archive@ietf.org; Fri, 30 May 2003 10:36:39 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Lkzm-0005EQ-00 for manet-web-archive@ietf.org; Fri, 30 May 2003 10:36:38 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4UEPJB07108; Fri, 30 May 2003 10:25: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 h4UEKnB06854 for ; Fri, 30 May 2003 10:20:49 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09971 for ; Fri, 30 May 2003 10:20:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Lkin-000537-00 for manet@ietf.org; Fri, 30 May 2003 10:19:05 -0400 Received: from fsa.cpsc.ucalgary.ca ([136.159.2.1]) by ietf-mx with esmtp (Exim 4.12) id 19Lkim-000534-00 for manet@ietf.org; Fri, 30 May 2003 10:19:04 -0400 Received: from imgw1.cpsc.ucalgary.ca (ons-imgw1 [192.168.1.66]) by fsa.cpsc.ucalgary.ca (8.12.9/8.12.9) with ESMTP id h4UEKetX020848; Fri, 30 May 2003 08:20:40 -0600 Received: from cpsc.ucalgary.ca (ict719g [136.159.15.15]) by imgw1.cpsc.ucalgary.ca (8.12.9/8.12.3) with ESMTP id h4UEKa79011862; Fri, 30 May 2003 08:20:36 -0600 Message-ID: <3ED768B4.8060408@cpsc.ucalgary.ca> Date: Fri, 30 May 2003 08:20:36 -0600 From: Abhinav Gupta Reply-To: gupta@cpsc.ucalgary.ca Organization: University of Calgary User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jw2000@excite.com CC: manet@ietf.org Subject: Re: [manet] simulator for ad hoc network References: <20030530010815.14D563E1C@xmxpita.excite.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavis-milter (http://amavis.org/) X-Spam-Status: No, hits=-6.4 required=6.8 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 The other simulators avalable include : GloMoSim (academic version of Qualnet) OpNet ns-2 Cheers, Abhinav. Jack Wang wrote: > Hi All: > > Besides Qualnet, are there other commercial softwares for simulation > of ad hoc networks? > > Thanks, > > Jack > > > > > ------------------------------------------------------------------------ > Join Excite! - http://www.excite.com > The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat May 31 12:58:29 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05644 for ; Sat, 31 May 2003 12:58:29 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4VGw3V26558 for manet-archive@odin.ietf.org; Sat, 31 May 2003 12:58: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 h4VGw3B26555 for ; Sat, 31 May 2003 12:58:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05631 for ; Sat, 31 May 2003 12:57:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19M9eU-0000PO-00 for manet-web-archive@ietf.org; Sat, 31 May 2003 12:56:18 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19M9eT-0000PK-00 for manet-web-archive@ietf.org; Sat, 31 May 2003 12:56:17 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4VGfrB25933; Sat, 31 May 2003 12:41: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 h4VGXsB24828 for ; Sat, 31 May 2003 12:33:54 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05391 for ; Sat, 31 May 2003 12:33:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19M9H7-0000KJ-00 for manet@ietf.org; Sat, 31 May 2003 12:32:09 -0400 Received: from amber.ccs.neu.edu ([129.10.116.51]) by ietf-mx with esmtp (Exim 4.12) id 19M9H6-0000KG-00 for manet@ietf.org; Sat, 31 May 2003 12:32:08 -0400 Received: from denali.ccs.neu.edu (denali.ccs.neu.edu [129.10.116.200]) by amber.ccs.neu.edu (Postfix) with ESMTP id 51F5E542CF for ; Sat, 31 May 2003 12:33:39 -0400 (EDT) Date: Sat, 31 May 2003 12:33:39 -0400 (EDT) From: Guevara Noubir To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] ACM Workshop on Wireless Security (WiSe) in conjunction with ACM MobiCom (Deadline June 3rd) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , ----------------------------------------------------------------- Our apologies if you receive multiple copies of the CFP. ----------------------------------------------------------------- Call for Papers ACM Workshop on Wireless Security (WiSe) in conjunction with ACM MobiCom 2003 September 19, 2003 San Diego, CA http://www.ece.cmu.edu/~adrian/wise2003 Sponsored by SIGMOBILE The workshop on Wireless Security will be held in conjunction with ACM MobiCom 2003. The objective of this workshop is to bring together researchers from research communities in wireless networking, security, applied cryptography, and dependability; with the goal of fostering interaction. With the proliferation of wireless networks, issues related to secure and dependable operation of such networks are gaining importance. Topics of interest include, but are not limited to: * Key management in wireless/mobile environments * Trust establishment * Intrusion detection, detection of malicious behaviour * Revocation of malicious parties * Secure PHY/MAC/routing protocols * Secure location determination * Denial of service * User privacy * Anonymity, prevention of traffic analysis * Dependable wireless networking * Monitoring and surveillance Paper submission instructions: Submission of papers based on work-in-progress is encouraged. Submitted papers must not be previously published elsewhere or currently under review for any other publication. Please direct any questions about the paper submission process to the Program Co-Chairs. All paper submissions will be handled electronically. Authors should prepare a PostScript or Portable Document Format (PDF) version of their paper. Papers must meet the following restrictions: No longer than 10 pages (single or double column); in font no smaller than 11 points; must fit properly on US Letter-sized paper (8.5 inch x 11 inch) with reasonable margins. Electronic submissions webpage: http://web.iaands.org/wise2003/submit/ Important dates: Paper submissions due ** extended ** to: June 3, 2003 Notification of acceptance: July 25, 2003 Camera-ready papers due: August 1, 2003 Workshop date: September 19, 2003 Workshop Co-Chairs: * Douglas Maughan, Defense Advanced Research Projects Agency (dmaughan@darpa.mil) * Adrian Perrig, Carnegie Mellon University (perrig@cmu.edu) Program Committee: Bill Arbaugh, University of Maryland Brian Noble, University of Michigan Brian Van Leeuwen, Sandia National Laboratories Chinya Ravishankar, University of California at Riverside Jean-Pierre Hubaux, Swiss Federal Institute of Technology, Lausanne Jonathan Smith, University of Pennsylvania Leendert van Doorn, IBM Markus Jakobsson, RSA Security Radha Poovendran, University of Washington Stephen Zabele, Alphatech Wenke Lee, Georgia Institute of Technology Yair Amir, Johns Hopkins University Publicity Co-Chairs: Mohsen Guizani, University of West Florida Guevara Noubir, Northeastern University Publication Chair: Saad Biaz, Auburn University Registration Chair: Robin Kravets, University of Illinois at Urbana-Champaign Treasurer Yongguang Zhang, HRL Labs and UT-Austin _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet