From mailnull@www1.ietf.org Sun Jun 1 04:26: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 EAA01572 for ; Sun, 1 Jun 2003 04:26:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h518Q4928848 for manet-archive@odin.ietf.org; Sun, 1 Jun 2003 04:26: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 h518Q3B28845 for ; Sun, 1 Jun 2003 04:26: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 EAA01553 for ; Sun, 1 Jun 2003 04:26:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MO8X-0004Vb-00 for manet-web-archive@ietf.org; Sun, 01 Jun 2003 04:24:17 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19MO8X-0004VY-00 for manet-web-archive@ietf.org; Sun, 01 Jun 2003 04: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 h51881B23721; Sun, 1 Jun 2003 04:08: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 h517vcB22035 for ; Sun, 1 Jun 2003 03:57: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 DAA01227 for ; Sun, 1 Jun 2003 03:57:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MNh3-0004Ox-00 for manet@ietf.org; Sun, 01 Jun 2003 03:55:53 -0400 Received: from smtp2.libero.it ([193.70.192.52]) by ietf-mx with esmtp (Exim 4.12) id 19MNh2-0004Ot-00 for manet@ietf.org; Sun, 01 Jun 2003 03:55:52 -0400 Received: from f1u2i7 (62.98.119.71) by smtp2.libero.it (7.0.012) id 3E9BEBC30105BE9A for manet@ietf.org; Sun, 1 Jun 2003 09:57:05 +0200 Message-ID: <004001c32814$dadbca00$4777623e@f1u2i7> From: "Luca S." To: Subject: [manet] simulator for ad hoc network Date: Sun, 1 Jun 2003 10:07:05 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003D_01C32825.8DE37160" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Messaggio in formato MIME composto da piy parti. ------=_NextPart_000_003D_01C32825.8DE37160 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: Quoted-Printable I repeat msg, may I have mistaked the sendig... I suggest Omnet++, It's freeware and work very well... Regards, Luca... ----- Original Message -----=20 From: Jack Wang=20 To: manet@ietf.org=20 Sent: Friday, May 30, 2003 3:08 AM Subject: [manet] simulator for ad hoc network Hi All: Besides Qualnet, are there other commercial softwares for = simulation of ad hoc networks? Thanks, Jack=20 =20 -------------------------------------------------------------------------= ----- Join Excite! - http://www.excite.com The most personalized portal on the Web!=20 ------=_NextPart_000_003D_01C32825.8DE37160 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: Quoted-Printable
I repeat msg, may I have mistaked the=20 sendig...
 
I suggest Omnet++, It's freeware and work = very=20 well...
 
Regards,
Luca...
 
 
----- Original Message -----
From:=20 Jack = Wang=20
Sent: Friday, May 30, 2003 3:08 = AM
Subject: [manet] simulator for = ad hoc=20 network

Hi = All:

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

Thanks,

Jack=20




Join Excite! - http://www.excite.com
The = most=20 personalized portal on the Web! ------=_NextPart_000_003D_01C32825.8DE37160-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Jun 1 13:13: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 NAA22522 for ; Sun, 1 Jun 2003 13:13:34 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h51HD9225894 for manet-archive@odin.ietf.org; Sun, 1 Jun 2003 13:13: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 h51HD9B25891 for ; Sun, 1 Jun 2003 13:13: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 NAA22464 for ; Sun, 1 Jun 2003 13:13:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MWMb-0002a4-00 for manet-web-archive@ietf.org; Sun, 01 Jun 2003 13:11:21 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19MWMb-0002a0-00 for manet-web-archive@ietf.org; Sun, 01 Jun 2003 13:11: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 h51GvDB21174; Sun, 1 Jun 2003 12:57: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 h51GjeB18556 for ; Sun, 1 Jun 2003 12:45: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 MAA20845 for ; Sun, 1 Jun 2003 12:45:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MVw0-00025W-00 for manet@ietf.org; Sun, 01 Jun 2003 12:43:52 -0400 Received: from tomts26.bellnexxia.net ([209.226.175.189] helo=tomts26-srv.bellnexxia.net) by ietf-mx with esmtp (Exim 4.12) id 19MVvz-00024s-00 for manet@ietf.org; Sun, 01 Jun 2003 12:43:51 -0400 Received: from ordi ([64.228.196.177]) by tomts26-srv.bellnexxia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with SMTP id <20030601164529.CCUB18740.tomts26-srv.bellnexxia.net@ordi> for ; Sun, 1 Jun 2003 12:45:29 -0400 Message-ID: <009901c3285d$34816270$670cfea9@ordi> From: "Omar LAHLOU" To: Date: Sun, 1 Jun 2003 12:45:27 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0096_01C3283B.AD4C0DD0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [manet] ABR protocol 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: , This is a multi-part message in MIME format. ------=_NextPart_000_0096_01C3283B.AD4C0DD0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Has anyone implemented the ABR protocol in GlomoSim ? I'd like to = compare it to my routing protocol. Thanks for help. Omar. ------=_NextPart_000_0096_01C3283B.AD4C0DD0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
Has anyone=20 implemented the ABR protocol in GlomoSim ? I'd like to compare it to my = routing=20 protocol.
 
Thanks for help.

Omar.
 
------=_NextPart_000_0096_01C3283B.AD4C0DD0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 2 02:13: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 CAA24443 for ; Mon, 2 Jun 2003 02:13:26 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h526D0t10183 for manet-archive@odin.ietf.org; Mon, 2 Jun 2003 02:13: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 h526D0B10180 for ; Mon, 2 Jun 2003 02:13: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 CAA24410 for ; Mon, 2 Jun 2003 02:12:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MiXG-0007db-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 02:11:10 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19MiXF-0007dY-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 02:11:09 -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 h525sBB31306; Mon, 2 Jun 2003 01:54: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 h525ksB31067 for ; Mon, 2 Jun 2003 01:46: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 BAA12767 for ; Mon, 2 Jun 2003 01:46:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Mi81-0007UN-00 for manet@ietf.org; Mon, 02 Jun 2003 01:45:05 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19Mi80-0007UD-00 for manet@ietf.org; Mon, 02 Jun 2003 01:45:04 -0400 Received: from paulnb (paul3.etri.re.kr [129.254.112.196]) by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h525xF724987 for ; Mon, 2 Jun 2003 14:59:15 +0900 (KST) Message-ID: <018301c328ca$2c9eb810$c470fe81@etri.re.kr> From: "Jaehoon Jeong" To: "MANET WG" Date: Mon, 2 Jun 2003 14:45:29 +0900 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h525ksB31068 Subject: [manet] Ad hoc IP 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: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hello, manet guys! I would like to request your comments on my new draft, "Ad Hoc IP Address Autoconfiguration ". http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-00.txt After four basic ad hoc routing protocols (AODV, DSR, OLSR and TBRPF) become experimental RFCs, I think, it is time for us to discuss ad hoc IP address autoconfiguration again. In my draft, I considered the manet partition and mergence for detecting duplicate address. Also, I included the mechanism for supporting the survivability of upper-layer sessions in the case that the duplicate address should be replaced with a new address. In this 57th ietf meeting, I hope manet wg will discuss the topic related to ad hoc IP address autoconfiguration. I'll wait for your comments. Thanks. Regards, Jaehoon _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 2 02:41:02 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 CAA25635 for ; Mon, 2 Jun 2003 02:41:02 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h526eba14285 for manet-archive@odin.ietf.org; Mon, 2 Jun 2003 02:40:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h526ebB14282 for ; Mon, 2 Jun 2003 02:40: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 CAA25623 for ; Mon, 2 Jun 2003 02:40:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Mixy-0000HH-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 02:38:46 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Mixy-0000HE-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 02:38: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 h526LsB11996; Mon, 2 Jun 2003 02: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 h526FjB11326 for ; Mon, 2 Jun 2003 02:15: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 CAA24669 for ; Mon, 2 Jun 2003 02:15:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MiZv-0007eY-00 for manet@ietf.org; Mon, 02 Jun 2003 02:13:55 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19MiZu-0007eO-00 for manet@ietf.org; Mon, 02 Jun 2003 02:13:55 -0400 Received: from paulnb (paul3.etri.re.kr [129.254.112.196]) by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h526S5725188 for ; Mon, 2 Jun 2003 15:28:05 +0900 (KST) Message-ID: <023301c328ce$33ed9c90$c470fe81@etri.re.kr> From: "Jaehoon Jeong" To: "MANET WG" Date: Mon, 2 Jun 2003 15:14:19 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" 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: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h526FjB11327 Subject: [manet] Ad hoc IP 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: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hello, manet guys! I would like to request your comments on my new draft, "Ad Hoc IP Address Autoconfiguration ". http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-00.txt After four basic ad hoc routing protocols (AODV, DSR, OLSR and TBRPF) become experimental RFCs, I think, it is time for us to discuss ad hoc IP address autoconfiguration again. In my draft, I considered the manet partition and mergence for detecting duplicate address. Also, I included the mechanism for supporting the survivability of upper-layer sessions in the case that the duplicate address should be replaced with a new address. In this 57th ietf meeting, I hope manet wg will discuss the topic related to ad hoc IP address autoconfiguration. I'll wait for your comments. Thanks. Regards, Jaehoon _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 2 03:05: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 DAA26261 for ; Mon, 2 Jun 2003 03:05:55 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5275Vb15653 for manet-archive@odin.ietf.org; Mon, 2 Jun 2003 03:05: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 h5275VB15650 for ; Mon, 2 Jun 2003 03:05: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 DAA26255 for ; Mon, 2 Jun 2003 03:05:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MjM4-0000Va-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 03:03:40 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19MjM3-0000VX-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 03:03: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 h526l1B14620; Mon, 2 Jun 2003 02:47:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h526eMB14270 for ; Mon, 2 Jun 2003 02:40: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 CAA25616 for ; Mon, 2 Jun 2003 02:40:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Mixk-0000H8-00 for manet@ietf.org; Mon, 02 Jun 2003 02:38:32 -0400 Received: from web14711.mail.yahoo.com ([216.136.232.91]) by ietf-mx with smtp (Exim 4.12) id 19Mixj-0000H5-00 for manet@ietf.org; Mon, 02 Jun 2003 02:38:31 -0400 Message-ID: <20030602064016.86036.qmail@web14711.mail.yahoo.com> Received: from [203.197.138.163] by web14711.mail.yahoo.com via HTTP; Sun, 01 Jun 2003 23:40:16 PDT Date: Sun, 1 Jun 2003 23:40:16 -0700 (PDT) From: panneer pandi To: AODV MailingList , Glomosim MailingList , Manet MailingList MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-336338023-1054536016=:85887" Subject: [manet] reg: AODV route req Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-336338023-1054536016=:85887 Content-Type: text/plain; charset=us-ascii hai I need a help, in glomosim , they use the function RoutingAodvHandleProtocolPacket it is said that it is called from, mac layer. Can anyone say me where do they call this function. Another problem, in AODV route request if i give specific address , i am not getting route reply for it(because route request is a packet which should be broadcasted). Cannt, we use a specific address for route req, what are changes we need to do. Please help me. --------------------------------- Do you Yahoo!? Free online calendar with sync to Outlook(TM). --0-336338023-1054536016=:85887 Content-Type: text/html; charset=us-ascii
 hai
 
I need a help,
 
in glomosim , they use the function

RoutingAodvHandleProtocolPacket

it is said that it is called from, mac layer.

Can anyone say me where do they call this function.

Another problem, in AODV route request if i give specific address , i am not getting route reply for it(because route request is a packet which should be broadcasted).

Cannt, we use a specific address for route req, what are changes we need to do.

Please help me.

 

Do you Yahoo!?
Free online calendar with sync to Outlook(TM). --0-336338023-1054536016=:85887-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 2 11:29: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 LAA11975 for ; Mon, 2 Jun 2003 11:29:18 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h52FSpX24465 for manet-archive@odin.ietf.org; Mon, 2 Jun 2003 11:28: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 h52FSpB24460 for ; Mon, 2 Jun 2003 11:28: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 LAA11943 for ; Mon, 2 Jun 2003 11:28:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MrDD-000404-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 11:27:03 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19MrDD-000401-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 11:27: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 h52FAcB23175; Mon, 2 Jun 2003 11:10: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 h52F2fB21811 for ; Mon, 2 Jun 2003 11:02: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 LAA10842 for ; Mon, 2 Jun 2003 11:02:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Mqnq-0003gg-00 for manet@ietf.org; Mon, 02 Jun 2003 11:00:50 -0400 Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx with esmtp (Exim 4.12) id 19Mqnp-0003gc-00 for manet@ietf.org; Mon, 02 Jun 2003 11:00:49 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id D334A7B48E for ; Mon, 2 Jun 2003 11:02:35 -0400 (EDT) Received: from magic.internet2.edu (aa106.internet2.edu [207.75.164.106]) by basie.internet2.edu (Postfix) with ESMTP id D5E427B479 for ; Mon, 2 Jun 2003 11:02:34 -0400 (EDT) Message-Id: <5.1.0.14.2.20030602105341.015b28a0@mail.internet2.edu> X-Sender: jzeeff@mail.internet2.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 02 Jun 2003 11:02:27 -0400 To: manet@ietf.org From: Jon Zeeff Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS 0.3.12pre8 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: , > 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. DSR addresses this issue with: 3.4.1. Packet Salvaging _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 2 14:29: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 OAA18115 for ; Mon, 2 Jun 2003 14:29:08 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h52IShe08016 for manet-archive@odin.ietf.org; Mon, 2 Jun 2003 14:28: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 h52ISgB08013 for ; Mon, 2 Jun 2003 14: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 OAA18092 for ; Mon, 2 Jun 2003 14:28:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Mu1D-0005Ml-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 14:26:51 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Mu1C-0005Mf-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 14:26: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 h52IEWB07191; Mon, 2 Jun 2003 14:14: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 h52I2uB05756 for ; Mon, 2 Jun 2003 14:02: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 OAA17301 for ; Mon, 2 Jun 2003 14:02:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MtcH-0005AA-00 for manet@ietf.org; Mon, 02 Jun 2003 14:01:05 -0400 Received: from mailhost.iitb.ac.in ([203.197.74.142]) by ietf-mx with smtp (Exim 4.12) id 19MtcG-0005A7-00 for manet@ietf.org; Mon, 02 Jun 2003 14:01:05 -0400 Received: (qmail 30529 invoked from network); 2 Jun 2003 18:02:43 -0000 Received: from mailscan2.iitb.ac.in (HELO antivirus.iitb.ac.in) (144.16.108.202) by mailhost.iitb.ac.in with SMTP; 2 Jun 2003 18:02:43 -0000 Received: (qmail 11658 invoked by uid 505); 2 Jun 2003 18:02:43 -0000 Received: from mohit@ee.iitb.ac.in by localhost.localdomain by uid 502 with qmail-scanner-1.15 (clamscan: 0.54. Clear:. Processed in 0.126268 secs); 02 Jun 2003 18:02:43 -0000 Received: from unknown (HELO ee.iitb.ac.in) ([10.107.1.1]) (envelope-sender ) by antivirus.iitb.ac.in (qmail-ldap-1.03) with SMTP for ; 2 Jun 2003 18:02:43 -0000 Received: from vani.ee.iitb.ac.in (sharada.ee.iitb.ac.in [10.107.1.2]) by ee.iitb.ac.in (8.12.4/8.12.4) with ESMTP id h52I2hGY008909; Mon, 2 Jun 2003 23:32:43 +0530 (IST) Received: from vani.ee.iitb.ac.in (localhost.localdomain [127.0.0.1]) by vani.ee.iitb.ac.in (8.12.8/8.12.8) with ESMTP id h52I2g4w014097; Mon, 2 Jun 2003 23:32:42 +0530 Received: from localhost (mohit@localhost) by vani.ee.iitb.ac.in (8.12.8/8.12.8/Submit) with ESMTP id h52I2g0t014093; Mon, 2 Jun 2003 23:32:42 +0530 X-Authentication-Warning: vani.ee.iitb.ac.in: mohit owned process doing -bs Date: Mon, 2 Jun 2003 23:32:42 +0530 (IST) From: Mohit Garg To: manet@ietf.org cc: vsrp032@tcs.tifr.res.in Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] NS-2 multi-path routing Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Has anyone implemented any Multi-Path routing protocol in NS-2 for MANets? One of my friends urgently needs any code for this. Any help or pointers will be a favour. -- "What do we live for if not to make life less difficult for each other?" - George Eliot regards, Mohit Garg Senior Undergraduate Student Dept. of Electrical Engg. IIT Bombay http://www.ee.iitb.ac.in/uma/~mohit/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 2 19:01: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 TAA29114 for ; Mon, 2 Jun 2003 19:01:14 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h52N0qN31719 for manet-archive@odin.ietf.org; Mon, 2 Jun 2003 19:00: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 h52N0qB31716 for ; Mon, 2 Jun 2003 19:00: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 TAA29052 for ; Mon, 2 Jun 2003 19:00:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MyGZ-0007NF-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 18:58:59 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19MyGZ-0007NC-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 18:58: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 h52MkZB30951; Mon, 2 Jun 2003 18:46: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 h52MbwB30650 for ; Mon, 2 Jun 2003 18:37: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 SAA28212 for ; Mon, 2 Jun 2003 18:37:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MxuR-00078c-00 for manet@ietf.org; Mon, 02 Jun 2003 18:36:07 -0400 Received: from web41805.mail.yahoo.com ([66.218.93.139]) by ietf-mx with smtp (Exim 4.12) id 19MxuQ-00078Q-00 for manet@ietf.org; Mon, 02 Jun 2003 18:36:06 -0400 Message-ID: <20030602223722.49828.qmail@web41805.mail.yahoo.com> Received: from [213.78.171.244] by web41805.mail.yahoo.com via HTTP; Mon, 02 Jun 2003 23:37:22 BST Date: Mon, 2 Jun 2003 23:37:22 +0100 (BST) From: =?iso-8859-1?q?l=20s?= Subject: Re: [manet] reg: AODV route req To: panneer pandi , AODV MailingList , Glomosim MailingList , Manet MailingList In-Reply-To: <20030602064016.86036.qmail@web14711.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi RoutingAodvHandleProtocolPacket() is called from: ProcessPacketForMeFromMac() in network/nwip.pc, which is called from: ProcessPacketFromMac() in network/nwip.pc, which is called from: NetworkIpReceivePacketFromMacLayer() in network/nwip.pc, which is called from the appropriate protocol function (802.11 / CSMA / ...) in the mac/ directory When you do a RREQ you request a route to a specific address, and this address is contained within the packet but the RREQ packet itself is broadcast. Does this answer the question? Lee -S- CCSR, University of Surrey, UK --- panneer pandi wrote: > hai > > I need a help, > > in glomosim , they use the function > > RoutingAodvHandleProtocolPacket > > it is said that it is called from, mac layer. > > Can anyone say me where do they call this function. > > Another problem, in AODV route request if i give > specific address , i am not getting route reply for > it(because route request is a packet which should be > broadcasted). > > Cannt, we use a specific address for route req, what > are changes we need to do. > > Please help me. > __________________________________________________ Yahoo! Plus - For a better Internet experience http://uk.promotions.yahoo.com/yplus/yoffer.html _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 2 20:31: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 UAA01604 for ; Mon, 2 Jun 2003 20:31:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h530VPJ05935 for manet-archive@odin.ietf.org; Mon, 2 Jun 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 h530VOB05932 for ; Mon, 2 Jun 2003 20:31: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 UAA01594 for ; Mon, 2 Jun 2003 20:31:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MzgF-0000CL-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 20:29:35 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19MzgE-0000CI-00 for manet-web-archive@ietf.org; Mon, 02 Jun 2003 20:29:34 -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 h530GjB05004; Mon, 2 Jun 2003 20:16:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5307CB03991 for ; Mon, 2 Jun 2003 20:07: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 UAA00887 for ; Mon, 2 Jun 2003 20:07:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19MzIp-000014-00 for manet@ietf.org; Mon, 02 Jun 2003 20:05:23 -0400 Received: from mailf.telia.com ([194.22.194.25]) by ietf-mx with esmtp (Exim 4.12) id 19MzIo-000011-00 for manet@ietf.org; Mon, 02 Jun 2003 20:05:23 -0400 Received: from d1o1121.telia.com (d1o1121.telia.com [217.208.140.241]) by mailf.telia.com (8.12.9/8.12.9) with ESMTP id h53078Y8004904; Tue, 3 Jun 2003 02:07:08 +0200 (CEST) X-Original-Recipient: manet@ietf.org Received: from h205n2fls35o1121.telia.com (h205n2fls35o1121.telia.com [217.211.83.205]) by d1o1121.telia.com (8.10.2/8.10.1) with ESMTP id h53077r12162; Tue, 3 Jun 2003 02:07:07 +0200 (CEST) From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: AODV MailingList Cc: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Message-Id: <1054598827.4371.7.camel@replicator.hn.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.3.92 (Preview Release) Date: 03 Jun 2003 02:07:07 +0200 X-MIME-Autoconverted: from 8bit to quoted-printable by mailf.telia.com id h53078Y8004904 X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5307CB03992 Subject: [manet] AODV-UU 0.7 released! Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 h530GjB05004 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h530VOB05932 Content-Transfer-Encoding: 8bit AODV-UU 0.7 is now available. Some changes: * Draft v13 updates. * Implemented better rate limit. * Lots of cleanups. Please report bugs! Download from: http://www.docs.uu.se/docs/research/projects/scanet/aodv/ Erik Nordström Uppsala University, Sweden. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 3 04:04: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 EAA22761 for ; Tue, 3 Jun 2003 04:04:48 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5384L519137 for manet-archive@odin.ietf.org; Tue, 3 Jun 2003 04:04:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5384KB19134 for ; Tue, 3 Jun 2003 04:04: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 EAA22735 for ; Tue, 3 Jun 2003 04:04:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19N6kZ-0002tM-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 04:02:31 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19N6kY-0002tJ-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 04:02: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 h537n8B17782; Tue, 3 Jun 2003 03:49: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 h537eHB17428 for ; Tue, 3 Jun 2003 03:40: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 DAA22254 for ; Tue, 3 Jun 2003 03:40:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19N6NI-0002lW-00 for manet@ietf.org; Tue, 03 Jun 2003 03:38:28 -0400 Received: from gemini.rz.uni-ulm.de ([134.60.246.16] helo=mail.rz.uni-ulm.de) by ietf-mx with esmtp (Exim 4.12) id 19N6NH-0002lS-00 for manet@ietf.org; Tue, 03 Jun 2003 03:38:28 -0400 Received: from informatik.uni-ulm.de (delphin.informatik.uni-ulm.de [134.60.70.42]) by mail.rz.uni-ulm.de (8.12.9/8.12.9) with ESMTP id h537eDDv009753; Tue, 3 Jun 2003 09:40:13 +0200 (MEST) Message-ID: <3EDC50DE.7040601@informatik.uni-ulm.de> Date: Tue, 03 Jun 2003 09:40:14 +0200 From: Frank Kargl Organization: University of Ulm User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: Jon Zeeff CC: manet@ietf.org Subject: Re: [manet] local route repair References: <5.1.0.14.2.20030602105341.015b28a0@mail.internet2.edu> In-Reply-To: <5.1.0.14.2.20030602105341.015b28a0@mail.internet2.edu> X-Enigmail-Version: 0.74.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-DCC-MessageCare-Metrics: gemini 1108; Body=2 Fuz1=2 Fuz2=2 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jon Zeeff wrote: | DSR addresses this issue with: | | | 3.4.1. Packet Salvaging Perhaps I am wrong but when reading the DSR draft I get a different understanding of packet salvaging. This is only ment for transmitting the one packet (or a few that follow) that caused the RERR to the destination. But nevertheless there has to be a new route discovery procedure for the source to get an updated route. Otherwise the source routes that the source writes into the packet would be wrong for quite some time. Regards ... Frank - -- - ----------------------------------------------------------------------- ~ Frank Kargl Multimedia Computing, University of Ulm, Germany ~ Mail:frank.kargl@informatik.uni-ulm.de http://www.uni-ulm.de/~fkargl/ - ----------------------------------------------------------------------- ~ Use the SOURCE, Luke ! I feel a great disturbance in the SOURCE. ~ But beware of the Microsoft side of the SOURCE ! - ----------------------------------------------------------------------- ---> CFP HICSS-37 Wireless PANs Minitrack: <--- ---> http://crystal.uta.edu/~zaruba/hicss37/ <--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+3FDePfhIZ4vQvRQRAtVFAJ9YUaEtij0MLxNo7RuWEhjsh2zPCgCeOFxx M6GlV40yxrl2bS0Rv6CgY/o= =giQP -----END PGP SIGNATURE----- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 3 04:26: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 EAA23151 for ; Tue, 3 Jun 2003 04:26:05 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h538PcN21114 for manet-archive@odin.ietf.org; Tue, 3 Jun 2003 04:25: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 h538PbB21111 for ; Tue, 3 Jun 2003 04:25: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 EAA23141 for ; Tue, 3 Jun 2003 04:25:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19N759-00031M-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 04:23:47 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19N759-00031J-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 04:23:47 -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 h538AWB20279; Tue, 3 Jun 2003 04:10: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 h5383IB19076 for ; Tue, 3 Jun 2003 04:03: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 EAA22718 for ; Tue, 3 Jun 2003 04:03:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19N6jZ-0002sq-00 for manet@ietf.org; Tue, 03 Jun 2003 04:01:29 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19N6jY-0002sd-00 for manet@ietf.org; Tue, 03 Jun 2003 04:01:28 -0400 Received: from paulnb (paul3.etri.re.kr [129.254.112.196]) by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h538FX705055; Tue, 3 Jun 2003 17:15:34 +0900 (KST) Message-ID: <011f01c329a6$62294e50$c470fe81@etri.re.kr> From: "Jaehoon Jeong" To: "Zhong Fan" Cc: "MANET WG" , =?utf-8?B?67CV7KCV7IiY?= , =?utf-8?B?6rmA7ZiV7KSA?= , =?utf-8?B?7J206rK97KeE?= , =?utf-8?B?6rmA67OR7Je9?= , =?utf-8?B?7LCo7ZiE7Jqx?= , =?utf-8?B?7KCV7J6s7ZuI?= References: <59FBEBDC1C9E6A46A87DD048E762EB821CF612@exch> Subject: Re: [manet] Ad hoc IP address autoconfiguration Date: Tue, 3 Jun 2003 17:01:46 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" 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: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h5383JB19078 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 First of all, thanks for your good comments. There are my responses inlines. ----- Original Message ----- From: "Zhong Fan" To: "'Jaehoon Jeong'" Sent: Tuesday, June 03, 2003 12:42 AM Subject: RE: [manet] Ad hoc IP address autoconfiguration > Hi > > I have read your draft and here are my comments: > > 1 As I understand, in IPv6, the originator's address should be part of IPv6 > header instead of in the message itself. Maybe I'm wrong. > Yes, you're right. I agree with you. In the next version, I'am going to exclude the originator's IPv6 address field from ad hoc IPv6 address autoconf messages. But, how about IPv4? I think it is the same as IPv6. > 2 Is weak DAD in your draft the same as Vaidya's method? Yes, Prof. Vaidya agreed to give comments on my drafting. His method takes an important place in my draft. > > 3 As for upper-layer sessions, the concept of "preferred" and "deprecated" > addresses for graceful site-renumbering in RFC 2462 is very useful. I am not > sure how exactly your tunnelling method works -- perhaps you need to put in > more detail. Good comments! In the current draft, I didn't descibe the mechanism of supporting the survivability of upper-layer sessions in detail and just suggested a key idea. In the next version, I'll explain the mechanism more in details, including your comments. Thanks a lot. Jaehoon > > Cheers, > > Dr Z Fan > Toshiba > > -----Original Message----- > From: Jaehoon Jeong [mailto:paul@etri.re.kr] > Sent: 02 June 2003 07:14 > To: MANET WG > Subject: [manet] Ad hoc IP address autoconfiguration > > Hello, manet guys! > I would like to request your comments on my new draft, > "Ad Hoc IP Address Autoconfiguration ". > http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-00.txt > > > After four basic ad hoc routing protocols (AODV, DSR, OLSR and TBRPF) > become experimental RFCs, I think, it is time for us to discuss > ad hoc IP address autoconfiguration again. > In my draft, I considered the manet partition and mergence for detecting > duplicate address. > Also, I included the mechanism for supporting the survivability of > upper-layer sessions > in the case that the duplicate address should be replaced with a new > address. > In this 57th ietf meeting, I hope manet wg will discuss the topic related to > ad hoc IP address autoconfiguration. > I'll wait for your comments. > Thanks. > > Regards, > Jaehoon > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > > _________________________________________________________________ > The information contained in this message is intended for the addressee only and may contain confidential and/or privileged information. If you are not the addressee, please delete this message and notify the sender; you should not copy or distribute this message or disclose its contents to anyone. Any views or opinions expressed in this message are those of the author and do not necessarily represent those of Toshiba Research Europe limited or any of its affiliates. No reliance may be placed on this message without written confirmation from an authorised representative of its contents. Registered in England No.2519556 @ 260 Cambridge Science Park, Milton Road, Cambridge, CB4 0WE > > This message has been scanned for email content security threats > by MAILsweeper, one of Content Technologies MIMEsweeper family of products. > _________________________________________________________________ > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 3 05:18: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 FAA24061 for ; Tue, 3 Jun 2003 05:18:13 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h539HmO25493 for manet-archive@odin.ietf.org; Tue, 3 Jun 2003 05:17: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 h539HmB25490 for ; Tue, 3 Jun 2003 05:17: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 FAA24048 for ; Tue, 3 Jun 2003 05:17:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19N7td-0003IV-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 05:15:57 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19N7tc-0003IS-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 05:15: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 h5394LB23800; Tue, 3 Jun 2003 05:04:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h538veB23550 for ; Tue, 3 Jun 2003 04:57: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 EAA23652 for ; Tue, 3 Jun 2003 04:57:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19N7a9-0003AJ-00 for manet@ietf.org; Tue, 03 Jun 2003 04:55:49 -0400 Received: from web14711.mail.yahoo.com ([216.136.232.91]) by ietf-mx with smtp (Exim 4.12) id 19N7a9-0003AG-00 for manet@ietf.org; Tue, 03 Jun 2003 04:55:49 -0400 Message-ID: <20030603085736.11290.qmail@web14711.mail.yahoo.com> Received: from [203.197.138.163] by web14711.mail.yahoo.com via HTTP; Tue, 03 Jun 2003 01:57:36 PDT Date: Tue, 3 Jun 2003 01:57:36 -0700 (PDT) From: panneer pandi To: AODV MailingList , Glomosim MailingList , Manet MailingList MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-498535954-1054630656=:10256" Subject: [manet] route req unicast Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-498535954-1054630656=:10256 Content-Type: text/plain; charset=us-ascii Hello What are the changes which we have to make while we are changing the broadcasting packet to unicasting for route request in Glomosim Please reply. --------------------------------- Do you Yahoo!? Free online calendar with sync to Outlook(TM). --0-498535954-1054630656=:10256 Content-Type: text/html; charset=us-ascii
Hello
 
 
    What are the changes which we have to make while we are changing the broadcasting packet to unicasting for route request in Glomosim
 
 
Please reply.

Do you Yahoo!?
Free online calendar with sync to Outlook(TM). --0-498535954-1054630656=:10256-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 3 09:56: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 JAA04590 for ; Tue, 3 Jun 2003 09:56:11 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h53Dtju16122 for manet-archive@odin.ietf.org; Tue, 3 Jun 2003 09:55:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h53DtjB16119 for ; Tue, 3 Jun 2003 09:55: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 JAA04570 for ; Tue, 3 Jun 2003 09:55:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NCEb-0006Bp-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 09:53:53 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NCEb-0006Bm-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 09:53: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 h53DbiB15132; Tue, 3 Jun 2003 09:37: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 h53DXNB14092 for ; Tue, 3 Jun 2003 09:33: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 JAA03950 for ; Tue, 3 Jun 2003 09:33:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NBsx-00060e-00 for manet@ietf.org; Tue, 03 Jun 2003 09:31:31 -0400 Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx with esmtp (Exim 4.12) id 19NBsw-00060a-00 for manet@ietf.org; Tue, 03 Jun 2003 09:31:30 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 61BD87B4C3 for ; Tue, 3 Jun 2003 09:33:18 -0400 (EDT) Received: from magic.internet2.edu (aa106.internet2.edu [207.75.164.106]) by basie.internet2.edu (Postfix) with ESMTP id 2614D7B49E for ; Tue, 3 Jun 2003 09:33:17 -0400 (EDT) Message-Id: <5.1.0.14.2.20030603091923.015b3c10@mail.internet2.edu> X-Sender: jzeeff@mail.internet2.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 03 Jun 2003 09:33:07 -0400 To: manet@ietf.org From: Jon Zeeff Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS 0.3.12pre8 Subject: [manet] mesh 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: , I have some interest in supporting a local MANet and as I look at what protocols one might run, I find that I doubt that any of the ones being presented to the IETF would actually work well in real use. Mostly due to the selection of non-optimal routes*, congestion of shortest routes, tcps behavior when there is any packet loss/delay and routing security problems. * - hop count is not optimal in any way that real users would care about Here are MANet attributes I would like to see: Good performance with tcp - this means best route, not shortest hop count. One must be very careful about packet loss and packet delay. Not susceptible to "black hole" routing attacks (or at least some mechanism to address (route around?) them). Security built into the protocol sounds better to me than "security will be addressed elsewhere". Multipath routing (ie, the ability to send duplicate packets via 2 or more routes so that less packet loss and delay is seen by the receiver. Duplicate packets would be thrown away). Ability to control bandwidth usage - ie, if too many people are using my links bandwidth, I need a way to encourage the routing to use alternate routes (adjustable metrics). Some type of "fair queuing" congestion control (QOS) to deal with network overuse. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 3 14:12: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 OAA17532 for ; Tue, 3 Jun 2003 14:12:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h53IBiF10816 for manet-archive@odin.ietf.org; Tue, 3 Jun 2003 14:11: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 h53IBiB10813 for ; Tue, 3 Jun 2003 14:11: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 OAA17522 for ; Tue, 3 Jun 2003 14:11:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NGEJ-0001IU-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 14:09:51 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NGEJ-0001IR-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 14:09: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 h53HwHB08405; Tue, 3 Jun 2003 13:58: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 h53HldB07347 for ; Tue, 3 Jun 2003 13:47: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 NAA16265 for ; Tue, 3 Jun 2003 13:47:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NFr1-00010X-00 for manet@ietf.org; Tue, 03 Jun 2003 13:45:47 -0400 Received: from smtp1.ndsu.nodak.edu ([134.129.111.146]) by ietf-mx with esmtp (Exim 4.12) id 19NFr0-00010U-00 for manet@ietf.org; Tue, 03 Jun 2003 13:45:46 -0400 Received: from [192.168.125.22] (tiger.cs.ndsu.NoDak.edu [134.129.125.148]) by smtp1.ndsu.NoDak.edu (8.11.7/8.11.6) with ESMTP id h53HlXk15137 for ; Tue, 3 Jun 2003 12:47:33 -0500 Date: Tue, 03 Jun 2003 12:47:37 -0500 From: Sanjay Ramaswamy To: manet@ietf.org Subject: Re: [manet] mesh routing protocols Message-ID: <2377469672.1054644457@[192.168.125.22]> In-Reply-To: <5.1.0.14.2.20030603091923.015b3c10@mail.internet2.edu> Originator-Info: login-id=sanjay.ramaswamy; server=imap.ndsu.nodak.edu X-Mailer: Mulberry/2.0.8 (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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 Jon, That's a good list of requirements you have there. In a way, you are talking about single solution for all problems. That sounds ideal and impressive. But, don't you think, each of the points you listed should be dealt individually (or at least loosely coupled) so that they are incorporated based on the requirement of the application? Think that is why we have different protocols that suit well for some type of requirement. Sanjay --On Tuesday, June 03, 2003 9:33 AM -0400 Jon Zeeff wrote: > > I have some interest in supporting a local MANet and as I look at what > protocols one might run, I find that I doubt that any of the ones being > presented to the IETF would actually work well in real use. Mostly due to > the selection of non-optimal routes*, congestion of shortest routes, tcps > behavior when there is any packet loss/delay and routing security > problems. > > * - hop count is not optimal in any way that real users would care about > > Here are MANet attributes I would like to see: > > Good performance with tcp - this means best route, not shortest hop > count. One must be very careful about packet loss and packet delay. > > Not susceptible to "black hole" routing attacks (or at least some > mechanism to address (route around?) them). Security built into the > protocol sounds better to me than "security will be addressed elsewhere". > > Multipath routing (ie, the ability to send duplicate packets via 2 or more > routes so that less packet loss and delay is seen by the receiver. > Duplicate packets would be thrown away). > > Ability to control bandwidth usage - ie, if too many people are using my > links bandwidth, I need a way to encourage the routing to use alternate > routes (adjustable metrics). > > Some type of "fair queuing" congestion control (QOS) to deal with network > overuse. > > _______________________________________________ > 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 Jun 3 19:16: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 TAA29441 for ; Tue, 3 Jun 2003 19:16:14 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h53NFlH06528 for manet-archive@odin.ietf.org; Tue, 3 Jun 2003 19:15: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 h53NFlB06525 for ; Tue, 3 Jun 2003 19:15: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 TAA29403 for ; Tue, 3 Jun 2003 19:15:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NKyb-0003mf-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 19:13:57 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NKya-0003mb-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 19:13: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 h53N4oB05106; Tue, 3 Jun 2003 19: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 h53MvvB04764 for ; Tue, 3 Jun 2003 18:57: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 SAA28909 for ; Tue, 3 Jun 2003 18:57:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NKhH-0003eS-00 for manet@ietf.org; Tue, 03 Jun 2003 18:56:03 -0400 Received: from hellmouth4.gatech.edu ([130.207.165.164] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19NKhH-0003eP-00 for manet@ietf.org; Tue, 03 Jun 2003 18:56:03 -0400 Received: from hellmouth4.gatech.edu (localhost [127.0.0.1]) by hellmouth4.gatech.edu (Postfix) with SMTP id E7ED7A63F for ; Tue, 3 Jun 2003 18:57:50 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: from acmey.gatech.edu (acmey.prism.gatech.edu [130.207.171.27]) by hellmouth4.gatech.edu (Postfix) with ESMTP id D2E67A51E for ; Tue, 3 Jun 2003 18:57:50 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: by acmey.gatech.edu (Postfix, from userid 21503) id 96B6B31F20; Tue, 3 Jun 2003 18:57:50 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by acmey.gatech.edu (Postfix) with ESMTP id 90432330EE for ; Tue, 3 Jun 2003 18:57:50 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Date: Tue, 3 Jun 2003 18:57:50 -0400 (EDT) From: Young-Jun Lee X-X-Sender: To: Subject: Re: [manet] Basic question about MANET protocols In-Reply-To: <20030506161235.32DC.RYUJI@sfc.wide.ad.jp> 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, Is it also possible to retrieve the information in L2 header? Young On Tue, 6 May 2003, Ryuji Wakikawa wrote: > 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 Jun 3 19:34: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 TAA00116 for ; Tue, 3 Jun 2003 19:34:40 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h53NYDn07624 for manet-archive@odin.ietf.org; Tue, 3 Jun 2003 19:34: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 h53NYDB07621 for ; Tue, 3 Jun 2003 19:34: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 TAA00104 for ; Tue, 3 Jun 2003 19:34:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NLGQ-000425-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 19:32:22 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NLGP-000422-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 19:32: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 h53NNRB06826; Tue, 3 Jun 2003 19:23: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 h53NKtB06750 for ; Tue, 3 Jun 2003 19:20: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 TAA29662 for ; Tue, 3 Jun 2003 19:20:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NL3Z-0003rY-00 for manet@ietf.org; Tue, 03 Jun 2003 19:19:06 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19NL3Z-0003rO-00 for manet@ietf.org; Tue, 03 Jun 2003 19:19:05 -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 QAA05049; Tue, 3 Jun 2003 16:20:22 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h53NKL002724; Tue, 3 Jun 2003 16:20:21 -0700 X-mProtect: <200306032320> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.67, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdIqU8B7; Tue, 03 Jun 2003 16:20:20 PDT Message-ID: <3EDD2D60.4040800@iprg.nokia.com> Date: Tue, 03 Jun 2003 16:21:04 -0700 From: Fred Templin 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: Young-Jun Lee CC: manet@ietf.org Subject: Re: [manet] Basic question about MANET protocols References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Young-Jun Lee wrote: >Hi all, > >Is it also possible to retrieve the information in L2 header? > >Young > On linux, try the packet socket (man 7 packet). Fred ftemplin@iprg.nokia.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 3 20:38: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 UAA01602 for ; Tue, 3 Jun 2003 20:38:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h540cFn12832 for manet-archive@odin.ietf.org; Tue, 3 Jun 2003 20:38: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 h540cFB12829 for ; Tue, 3 Jun 2003 20:38: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 UAA01558 for ; Tue, 3 Jun 2003 20:38:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NMGN-0004OC-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 20:36:23 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NMGJ-0004O2-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 20:36:19 -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 h540SFB11485; Tue, 3 Jun 2003 20:28: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 h540OMB11376 for ; Tue, 3 Jun 2003 20:24: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 UAA01105 for ; Tue, 3 Jun 2003 20:24:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NM2x-0004I7-00 for manet@ietf.org; Tue, 03 Jun 2003 20:22:31 -0400 Received: from mail.cs.utexas.edu ([128.83.139.10] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19NM2w-0004I4-00 for manet@ietf.org; Tue, 03 Jun 2003 20:22:30 -0400 Received: from haarlem.cs.utexas.edu (wangf@haarlem.cs.utexas.edu [128.83.144.75]) by mail.cs.utexas.edu (8.12.9/8.12.9) with ESMTP id h540OJ8r007834 for ; Tue, 3 Jun 2003 19:24:19 -0500 (CDT) Received: (from wangf@localhost) by haarlem.cs.utexas.edu (8.12.9/8.12.9/Submit) id h540OIKp017210; Tue, 3 Jun 2003 19:24:18 -0500 Date: Tue, 3 Jun 2003 19:24:18 -0500 (CDT) From: Feng Wang To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] SINR model Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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: Does anybody know which simulator implements relatively realistic SINR model? Seems NS2 simplifies this issue too much. But it is especially necessary when power/interference related performance is concerned. Thanks a lot! Feng _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 3 21:00:28 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 VAA02203 for ; Tue, 3 Jun 2003 21:00:28 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h54101q13579 for manet-archive@odin.ietf.org; Tue, 3 Jun 2003 21:00:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54101B13576 for ; Tue, 3 Jun 2003 21:00: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 UAA02168 for ; Tue, 3 Jun 2003 20:59:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NMbR-0004ZX-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 20:58:09 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NMbQ-0004ZU-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 20:58: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 h540nUB13171; Tue, 3 Jun 2003 20:49: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 h540kaB13081 for ; Tue, 3 Jun 2003 20:46: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 UAA01792 for ; Tue, 3 Jun 2003 20:46:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NMOS-0004S8-00 for manet@ietf.org; Tue, 03 Jun 2003 20:44:44 -0400 Received: from fmr02.intel.com ([192.55.52.25] helo=caduceus.fm.intel.com) by ietf-mx with esmtp (Exim 4.12) id 19NMOR-0004S5-00 for manet@ietf.org; Tue, 03 Jun 2003 20:44:43 -0400 Received: from petasus.fm.intel.com (petasus.fm.intel.com [10.1.192.37]) by caduceus.fm.intel.com (8.11.6p2/8.11.6/d: outer.mc,v 1.66 2003/05/22 21:17:36 rfjohns1 Exp $) with ESMTP id h540cfA17821 for ; Wed, 4 Jun 2003 00:38:41 GMT Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by petasus.fm.intel.com (8.11.6p2/8.11.6/d: inner.mc,v 1.35 2003/05/22 21:18:01 rfjohns1 Exp $) with SMTP id h540dsK13852 for ; Wed, 4 Jun 2003 00:39:54 GMT Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs041.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2003060317463101807 ; Tue, 03 Jun 2003 17:46:31 -0700 Received: from orsmsx407.amr.corp.intel.com ([192.168.65.50]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 3 Jun 2003 17:46:30 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Subject: RE: [manet] SINR model Date: Tue, 3 Jun 2003 17:46:30 -0700 Message-ID: Thread-Topic: [manet] SINR model Thread-Index: AcMqMoEeloCbmjlCSyOvwSRMwZGj7wAAC0ww From: "Yang, Lily L" To: "Feng Wang" Cc: X-OriginalArrivalTime: 04 Jun 2003 00:46:31.0090 (UTC) FILETIME=[BD674920:01C32A32] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h540kaB13082 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit I was told that OpNet has a very good PHY model. But it isn't free. > -----Original Message----- > From: Feng Wang [mailto:wangf@cs.utexas.edu] > Sent: Tuesday, June 03, 2003 5:24 PM > To: manet@ietf.org > Subject: [manet] SINR model > > > Hi, all: > > Does anybody know which simulator implements relatively realistic SINR > model? Seems NS2 simplifies this issue too much. But it is especially > necessary when power/interference related performance is concerned. > > Thanks a lot! > > Feng > > _______________________________________________ > 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 Jun 3 21:35: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 VAA03293 for ; Tue, 3 Jun 2003 21:35:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h541Yu516128 for manet-archive@odin.ietf.org; Tue, 3 Jun 2003 21:34: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 h541YuB16125 for ; Tue, 3 Jun 2003 21:34: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 VAA03272 for ; Tue, 3 Jun 2003 21:34:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NN9D-0004w4-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 21:33:03 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NN9C-0004w1-00 for manet-web-archive@ietf.org; Tue, 03 Jun 2003 21:33:02 -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 h541MZB15434; Tue, 3 Jun 2003 21:22: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 h541JiB15269 for ; Tue, 3 Jun 2003 21: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 VAA02907 for ; Tue, 3 Jun 2003 21:19:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NMuW-0004oi-00 for manet@ietf.org; Tue, 03 Jun 2003 21:17:52 -0400 Received: from nn6.excitenetwork.com ([207.159.120.60] helo=xmxpita.excite.com) by ietf-mx with esmtp (Exim 4.12) id 19NMuV-0004of-00 for manet@ietf.org; Tue, 03 Jun 2003 21:17:51 -0400 Received: by xmxpita.excite.com (Postfix, from userid 110) id 9C3223E25; Tue, 3 Jun 2003 21:19:06 -0400 (EDT) To: manet@ietf.org Received: from [172.135.153.171] by xprdmailfe9.nwk.excite.com via HTTP; Tue, 03 Jun 2003 21:19:06 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = ee6980795d92c2dd71cfe60ff8ebf137 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__3501228a47083f59aa73c8f02faa7daf"; Content-Transfer-Encoding: 7bit Message-Id: <20030604011906.9C3223E25@xmxpita.excite.com> Date: Tue, 3 Jun 2003 21:19:06 -0400 (EDT) Subject: [manet] Loops of routing Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --EXCITEBOUNDARY_000__3501228a47083f59aa73c8f02faa7daf Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi all: AODV applies "destination sequence number" to prevent loops. I think another reason is that each node only processes the first RREQ received. If this requirement is removed, loop is still possible.Am I right? Thanks, Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! --EXCITEBOUNDARY_000__3501228a47083f59aa73c8f02faa7daf Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
Hi all:

AODV applies "destination sequence number" to prevent loops. I think another reason is that each node only processes the first RREQ received. If this requirement is removed, loop is still possible.
Am I right?

Thanks,

Jack




Join Excite! - http://www.excite.com
The most personalized portal on the Web! --EXCITEBOUNDARY_000__3501228a47083f59aa73c8f02faa7daf-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 4 02:11:50 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 CAA19581 for ; Wed, 4 Jun 2003 02:11:50 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h546BOF10305 for manet-archive@odin.ietf.org; Wed, 4 Jun 2003 02:11: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 h546BOB10302 for ; Wed, 4 Jun 2003 02:11: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 CAA19512 for ; Wed, 4 Jun 2003 02:11:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NRSk-0006NH-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 02:09:30 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NRSj-0006NE-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 02:09:29 -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 h5460RB01439; Wed, 4 Jun 2003 02:00: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 h545ubB01204 for ; Wed, 4 Jun 2003 01:56: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 BAA08044 for ; Wed, 4 Jun 2003 01:56:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NRER-0006Do-00 for manet@ietf.org; Wed, 04 Jun 2003 01:54:44 -0400 Received: from mail.zrz.tu-berlin.de ([130.149.4.15]) by ietf-mx with esmtp (Exim 4.12) id 19NRER-0006Dk-00 for manet@ietf.org; Wed, 04 Jun 2003 01:54:43 -0400 Received: from mail.zrz.tu-berlin.de ([130.149.4.15]) by mail.zrz.tu-berlin.de with esmtp (exim-4.20-1) id 19NRFi-00023E-LS; Wed, 04 Jun 2003 07:56:02 +0200 Received: from mail.zrz.TU-Berlin.DE ([130.149.4.15]) by mail.zrz.TU-Berlin.DE (MailMonitor for SMTP v1.2.2 ) ; Wed, 4 Jun 2003 07:56:02 +0200 (CEST) Received: from ftmail.ee.tu-berlin.de ([130.149.49.250]) by mail.zrz.tu-berlin.de with esmtp (exim-4.20-1) id 19NRFi-00022s-Jj; Wed, 04 Jun 2003 07:56:02 +0200 Received: from almathea (karl@almathea.tkn.TU-Berlin.DE [130.149.49.56]) by ftmail.ee.tu-berlin.de (8.11.3/8.11.3) with ESMTP id h545u1B07672; Wed, 4 Jun 2003 07:56:01 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Holger Karl Organization: Technische =?iso-8859-1?q?Universit=E4t?= Berlin, Telecommunication Networks Group To: Feng Wang , manet@ietf.org Subject: Re: [manet] SINR model Date: Wed, 4 Jun 2003 07:56:01 +0200 User-Agent: KMail/1.4.3 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200306040756.01398.karl@ee.tu-berlin.de> X-Virus-Scanned: Sophos MailMonitor on mail.zrz.tu-berlin.de; Wed, 04 Jun 2003 07:56:02 +0200 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 On Wednesday 04 June 2003 02:24, Feng Wang wrote: > Hi, all: > > Does anybody know which simulator implements relatively realistic SINR > model? Seems NS2 simplifies this issue too much. But it is especially > necessary when power/interference related performance is concerned. > Hi, Qualnet does, but is commercial. We are just plugging together an OMNET++-based ad-hoc simulator (http://whale.hit.bme.hu/omnetpp/) that does exactly such a realistic SINR modelling (different error rates in different parts of a packet when different modulations are used like in 802.11 broadcast packets, etc.). We plan to have this on sourceforge within this month, along with 802.11 model, etc. Best regards Holger _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 4 03:58: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 DAA07006 for ; Wed, 4 Jun 2003 03:58:55 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h547wSe21985 for manet-archive@odin.ietf.org; Wed, 4 Jun 2003 03:58:28 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h547wRB21972 for ; Wed, 4 Jun 2003 03:58: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 DAA06988 for ; Wed, 4 Jun 2003 03:58:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NT8N-0007Kv-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 03:56:35 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NT8M-0007Kk-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 03:56:34 -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 h547lCB21454; Wed, 4 Jun 2003 03:47: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 h547hAB21349 for ; Wed, 4 Jun 2003 03:43: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 DAA06664 for ; Wed, 4 Jun 2003 03:43:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NStb-0007DH-00 for manet@ietf.org; Wed, 04 Jun 2003 03:41:19 -0400 Received: from [202.108.44.212] (helo=sm212.163.com) by ietf-mx with esmtp (Exim 4.12) id 19NStZ-0007DE-00 for manet@ietf.org; Wed, 04 Jun 2003 03:41:18 -0400 Received: from localhost (localhost [127.0.0.1]) by sm212.163.com (Postfix) with SMTP id 4D5661CF2F848 for ; Wed, 4 Jun 2003 15:43:00 +0800 (CST) Received: from zyn (unknown [61.187.64.195]) by 192.168.1.212 (Coremail:www.163.com) with SMTP id pd4AAAOj3T7SAkDD.1 for ; Wed, 04 Jun 2003 15:43:00 +0800 (CST) Message-ID: <005e01c32a6d$22eb8c90$7600a8c0@zyn> From: "Zhang Yanan" To: References: <200306040756.01398.karl@ee.tu-berlin.de> Date: Wed, 4 Jun 2003 15:44:31 +0800 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h547hAB21350 Subject: [manet] flooding a new packet 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: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hi, I want to flooding a new packet to all of the node in the network in DSR protocol, then how can I set the "TTL" in the init phase. And when other node receive the packet, how to do with the "TTL"? Beside, I want to use glomosim to simulate, when I propagate the packet I use "NetworkIpSendRawGlomoMessage" or "NetworkIpSendRawGlomoMessageToMacLayer" ? Thanks a lot Zhang _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 4 04: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 EAA08378 for ; Wed, 4 Jun 2003 04:53:08 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h548qhW26712 for manet-archive@odin.ietf.org; Wed, 4 Jun 2003 04:52: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 h548qgB26709 for ; Wed, 4 Jun 2003 04:52: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 EAA08331 for ; Wed, 4 Jun 2003 04:52:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NTys-0007gU-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 04:50:50 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NTyr-0007gR-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 04:50: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 h548bnB25869; Wed, 4 Jun 2003 04:37: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 h548YfB24877 for ; Wed, 4 Jun 2003 04:34: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 EAA07911 for ; Wed, 4 Jun 2003 04:34:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NThR-0007YI-00 for manet@ietf.org; Wed, 04 Jun 2003 04:32:49 -0400 Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx with esmtp (Exim 4.12) id 19NThQ-0007YF-00 for manet@ietf.org; Wed, 04 Jun 2003 04:32:48 -0400 Received: from telecom.lth.se (lina36.tts.lth.se [130.235.18.156]) by anyida.tts.lth.se (8.9.3/8.9.3) with SMTP id KAA25579; Wed, 4 Jun 2003 10:34:47 +0200 (MET DST) From: Anders Nilsson Received: from 130.235.18.83 (SquirrelMail authenticated user andersn) by ww2.telecom.lth.se with HTTP; Wed, 4 Jun 2003 10:26:00 +0200 (CEST) Message-ID: <32799.130.235.18.83.1054715160.squirrel@ww2.telecom.lth.se> Date: Wed, 4 Jun 2003 10:26:00 +0200 (CEST) Subject: Re: [manet] SINR model To: In-Reply-To: <200306040756.01398.karl@ee.tu-berlin.de> References: <200306040756.01398.karl@ee.tu-berlin.de> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: , X-Mailer: SquirrelMail (version 1.2.6) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit You could also try glomosim. Its the academic and free and models the PHY quite well. QualNet is a commericalization of glomosim. regards, Anders > On Wednesday 04 June 2003 02:24, Feng Wang wrote: >> Hi, all: >> >> Does anybody know which simulator implements relatively realistic SINR >> model? Seems NS2 simplifies this issue too much. But it is especially >> necessary when power/interference related performance is concerned. >> > > Hi, > > Qualnet does, but is commercial. > > We are just plugging together an OMNET++-based ad-hoc simulator > (http://whale.hit.bme.hu/omnetpp/) > that does exactly such a realistic SINR modelling (different error > rates in > different parts of a packet when different modulations are used like in > 802.11 broadcast packets, etc.). We plan to have this on sourceforge > within this month, along with 802.11 model, etc. > > Best regards > > Holger > > > > _______________________________________________ > 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 Jun 4 06:28: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 GAA10346 for ; Wed, 4 Jun 2003 06:28:48 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h54ASPD01116 for manet-archive@odin.ietf.org; Wed, 4 Jun 2003 06:28: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 h54ASOB01113 for ; Wed, 4 Jun 2003 06:28: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 GAA10325 for ; Wed, 4 Jun 2003 06:28:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NVTS-0000Qm-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 06:26:30 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NVTR-0000Qj-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 06:26:29 -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 h54AIZB00679; Wed, 4 Jun 2003 06:18: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 h54AE9B00511 for ; Wed, 4 Jun 2003 06:14: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 GAA10098 for ; Wed, 4 Jun 2003 06:14:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NVFf-0000MA-00 for manet@ietf.org; Wed, 04 Jun 2003 06:12:15 -0400 Received: from yongml1sgbde002.korea.army.mil ([144.59.242.102]) by ietf-mx with esmtp (Exim 4.12) id 19NVFe-0000M1-00 for manet@ietf.org; Wed, 04 Jun 2003 06:12:14 -0400 Received: by yongml1sgbde002.korea.army.mil with Internet Mail Service (5.5.2655.55) id ; Wed, 4 Jun 2003 19:10:04 +0900 Message-ID: From: "Boleng, Jeffrey L. MAJ" To: "'manet@ietf.org'" Cc: "'tcamp@mines.edu'" Date: Wed, 4 Jun 2003 19:09:59 +0900 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" Subject: [manet] Paper 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: , CLASSIFICATION: UNCLASSIFIED The following paper has been submitted and is available at: http://toilers.mines.edu/papers/pdf/stationary.pdf Other papers by our research group are also available at: http://toilers.mines.edu/papers/ Stationary Distributions for the Random Waypoint Mobility Model? William Navidi and Tracy Camp Department of Mathematical and Computer Sciences Colorado School of Mines Golden, Colorado 80401 wnavidi@mines.edu; tcamp@mines.edu April 12th, 2002 Abstract In simulations of mobile ad hoc networks, the probability distribution governing the movement of the nodes typically varies over time, and converges to a "steady-state" distribution, known in the probability literature as the stationary distribution. Some published simulation results ignore this initialization discrepancy. For those results that attempt to account for this discrepancy, the practice is to discard an initial sequence of observations from a simulation in the hope that the remaining values will closely represent the stationary distribution. This approach is inefficient and not always reliable. However, if the initial locations and speeds of the nodes are chosen from the stationary distribution, convergence is immediate and no data need be discarded. We derive the stationary distributions for location, speed, and pause time for the random waypoint mobility model. We then show how to implement the random waypoint mobility model in order to construct more efficient and reliable simulations for mobile ad hoc networks. Simulation results, which verify the correctness of our method, are included. In addition, implementation of our method for the NS-2 simulator is available. Classification: UNCLASSIFIED _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 4 07:54: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 HAA12595 for ; Wed, 4 Jun 2003 07:54:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h54Brx207722 for manet-archive@odin.ietf.org; Wed, 4 Jun 2003 07:53: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 h54BrxB07719 for ; Wed, 4 Jun 2003 07:53: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 HAA12586 for ; Wed, 4 Jun 2003 07:53:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NWoK-00012N-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 07:52:08 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NWoJ-00012K-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 07:52: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 h54BfFB07097; Wed, 4 Jun 2003 07:41: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 h54BbHB06601 for ; Wed, 4 Jun 2003 07:37: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 HAA11935 for ; Wed, 4 Jun 2003 07:37:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NWYA-0000qV-00 for manet@ietf.org; Wed, 04 Jun 2003 07:35:26 -0400 Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx with esmtp (Exim 4.12) id 19NWY9-0000qR-00 for manet@ietf.org; Wed, 04 Jun 2003 07:35:25 -0400 Received: from steiner.cc.vt.edu (IDENT:mirapoint@evil-steiner [10.1.1.14]) by lennier.cc.vt.edu (8.12.8/8.12.8) with ESMTP id h54BbBKU020555; Wed, 4 Jun 2003 07:37:11 -0400 (EDT) Received: from tom ([198.70.228.122]) by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BKP24070 (AUTH talin); Wed, 4 Jun 2003 07:37:10 -0400 (EDT) Message-ID: <002801c32a8d$0abcb340$2502a8c0@tom> From: "Tao Lin" To: , "Boleng, Jeffrey L. MAJ" , Cc: References: Subject: Re: [manet] Paper announcement Date: Wed, 4 Jun 2003 07:32:52 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 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 William Navidi and Tracy Camp, You did a nice job in studying the stationary property of Random Waypoint model using simulations. Besides what are studied in your paper, we think another property, link connectivity changes (link lifetime or link change rate) is also very important. Because link connectivity changes are among the fundamental reasons that cause MANET topology changes and, thus, MANET protocols' operations, we believe that this kind of study is also very important for MANET simulations. We published a paper discussing a simulation study of stationary property of link stability in Random Waypoint model: Tao Lin and Scott F. Midkiff, "Mobility Versus Link Stability in Simulation of Mobile Ad Hoc Networks," in Proceedings of the Communication Networks and Distributed Systems Modeling and Simulation Conference (CNDS), pp. 3-8, Jan. 2003, Orlando, FL, USA. We found that at least with the parameters we tested, the warm up time for link stability is VERY long for the Random Waypoint model, which is usually much longer than the warm up time and simulation time used in many previous papers. Therefore, either we should choose a long enough warm up time or we should revise/choose the mobility model properly in our simulations. Hope this helps. Thanks, Tao Lin Ph. D. Candidate Laboratory for Advanced Network (LAN) ECE Dept. Virginia Tech ----- Original Message ----- From: "Boleng, Jeffrey L. MAJ" To: Cc: Sent: Wednesday, June 04, 2003 6:09 AM Subject: [manet] Paper announcement > CLASSIFICATION: UNCLASSIFIED > > The following paper has been submitted and is available at: > http://toilers.mines.edu/papers/pdf/stationary.pdf > > Other papers by our research group are also available at: > http://toilers.mines.edu/papers/ > > Stationary Distributions for the > Random Waypoint Mobility Model? > William Navidi and Tracy Camp > Department of Mathematical and Computer Sciences > Colorado School of Mines > Golden, Colorado 80401 > wnavidi@mines.edu; tcamp@mines.edu > April 12th, 2002 > Abstract > In simulations of mobile ad hoc networks, the probability distribution > governing the movement > of the nodes typically varies over time, and converges to a "steady-state" > distribution, > known in the probability literature as the stationary distribution. Some > published simulation > results ignore this initialization discrepancy. For those results that > attempt to account for this > discrepancy, the practice is to discard an initial sequence of observations > from a simulation > in the hope that the remaining values will closely represent the stationary > distribution. This > approach is inefficient and not always reliable. However, if the initial > locations and speeds of > the nodes are chosen from the stationary distribution, convergence is > immediate and no data > need be discarded. We derive the stationary distributions for location, > speed, and pause time > for the random waypoint mobility model. We then show how to implement the > random waypoint > mobility model in order to construct more efficient and reliable simulations > for mobile > ad hoc networks. Simulation results, which verify the correctness of our > method, are included. > In addition, implementation of our method for the NS-2 simulator is > available. > > > Classification: UNCLASSIFIED > > > _______________________________________________ > 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 Jun 4 09:55: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 JAA19652 for ; Wed, 4 Jun 2003 09:55:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h54DsiM17309 for manet-archive@odin.ietf.org; Wed, 4 Jun 2003 09:54: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 h54DsiB17306 for ; Wed, 4 Jun 2003 09:54: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 JAA19596 for ; Wed, 4 Jun 2003 09:54:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NYh8-0002rj-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 09:52:50 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NYh8-0002rg-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 09:52: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 h54DcSB16399; Wed, 4 Jun 2003 09:38: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 h54DUUB15183 for ; Wed, 4 Jun 2003 09:30: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 JAA18547 for ; Wed, 4 Jun 2003 09:30:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NYJg-0002fE-00 for manet@ietf.org; Wed, 04 Jun 2003 09:28:36 -0400 Received: from sp.isima.fr ([193.55.95.1]) by ietf-mx with esmtp (Exim 4.12) id 19NYJg-0002es-00 for manet@ietf.org; Wed, 04 Jun 2003 09:28:36 -0400 Received: from kang (pc158.isima.fr [193.55.95.158]) by sp.isima.fr (8.9.3/jtpda-5.3.1) with SMTP id PAA25200 for ; Wed, 4 Jun 2003 15:32:34 +0200 Message-ID: <014601c32a9d$6244e460$494110ac@kang> From: "Myoung-Ah KANG" To: Date: Wed, 4 Jun 2003 15:29:24 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_013F_01C32AAE.13DDE090" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [manet] source code implementing LAR Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_013F_01C32AAE.13DDE090 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, Is there anyone who can tell me how I could get the source code = implementing LAR, please ? Even if it's coupled with a protocol such as DSR or AODV ... , it will = be OK. Thank you for your help. Myoung ------=_NextPart_000_013F_01C32AAE.13DDE090 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
Is there anyone who can tell me = how I could=20 get the source code implementing LAR, please ?
 
Even if it's coupled with a = protocol such as=20 DSR or AODV ... , it will be OK.
 
Thank you for your help.
 
       =20 Myoung
------=_NextPart_000_013F_01C32AAE.13DDE090-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 4 12:41: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 MAA00524 for ; Wed, 4 Jun 2003 12:41:43 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h54GfIb00783 for manet-archive@odin.ietf.org; Wed, 4 Jun 2003 12:41: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 h54GfHB00780 for ; Wed, 4 Jun 2003 12:41: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 MAA00485 for ; Wed, 4 Jun 2003 12:41:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NbIK-0005PZ-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 12:39:24 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NbIK-0005PW-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 12:39: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 h54GUKB31774; Wed, 4 Jun 2003 12:30: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 h54GONB31535 for ; Wed, 4 Jun 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 MAA29679 for ; Wed, 4 Jun 2003 12:24:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nb1y-0005CD-00 for manet@ietf.org; Wed, 04 Jun 2003 12:22:30 -0400 Received: from hellmouth5.gatech.edu ([130.207.165.165] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19Nb1y-0005CA-00 for manet@ietf.org; Wed, 04 Jun 2003 12:22:30 -0400 Received: from hellmouth5.gatech.edu (localhost [127.0.0.1]) by hellmouth5.gatech.edu (Postfix) with SMTP id 450DF1D19B4; Wed, 4 Jun 2003 12:24:20 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: from acmey.gatech.edu (acmey.prism.gatech.edu [130.207.171.27]) by hellmouth5.gatech.edu (Postfix) with ESMTP id 2D1131D1989; Wed, 4 Jun 2003 12:24:20 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: by acmey.gatech.edu (Postfix, from userid 21503) id C006731F20; Wed, 4 Jun 2003 12:24:19 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by acmey.gatech.edu (Postfix) with ESMTP id B7B92330EE; Wed, 4 Jun 2003 12:24:19 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Date: Wed, 4 Jun 2003 12:24:19 -0400 (EDT) From: Young-Jun Lee X-X-Sender: To: Fred Templin Cc: Subject: Re: [manet] Basic question about MANET protocols In-Reply-To: <3EDD2D60.4040800@iprg.nokia.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, Is it possible for MANET protocols to access L2 info? The linux manual says the packet socket is used at L2. Young On Tue, 3 Jun 2003, Fred Templin wrote: > > Young-Jun Lee wrote: > > >Hi all, > > > >Is it also possible to retrieve the information in L2 header? > > > >Young > > > On linux, try the packet socket (man 7 packet). > > Fred > ftemplin@iprg.nokia.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 Wed Jun 4 14:52: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 OAA06325 for ; Wed, 4 Jun 2003 14:52:14 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h54Ipoh10131 for manet-archive@odin.ietf.org; Wed, 4 Jun 2003 14:51: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 h54IpoB10128 for ; Wed, 4 Jun 2003 14:51: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 OAA06280 for ; Wed, 4 Jun 2003 14:51:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NdKc-0006qL-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 14:49:54 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NdKc-0006qI-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 14:49:54 -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 h54IebB09370; Wed, 4 Jun 2003 14:40:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h54IZrB08315 for ; Wed, 4 Jun 2003 14:35: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 OAA05356 for ; Wed, 4 Jun 2003 14:35:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nd5B-0006bV-00 for manet@ietf.org; Wed, 04 Jun 2003 14:33:57 -0400 Received: from hawksbill.nist.gov ([129.6.13.21]) by ietf-mx with esmtp (Exim 4.12) id 19Nd56-0006bS-00 for manet@ietf.org; Wed, 04 Jun 2003 14:33:52 -0400 Received: from nist.gov (mouse.antd.nist.gov [129.6.50.84]) (authenticated bits=0) by hawksbill.nist.gov (8.12.9/8.12.9) with ESMTP id h54IYcEa026190 for ; Wed, 4 Jun 2003 14:34:38 -0400 (EDT) Message-ID: <3EDE4A5F.9AF2BE7A@nist.gov> Date: Wed, 04 Jun 2003 15:37:03 -0400 From: bjkwak Organization: NIST, MD X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.8-26mdk i686) X-Accept-Language: en, ko MIME-Version: 1.0 To: manet@ietf.org Subject: Re: [manet] Paper announcement References: <002801c32a8d$0abcb340$2502a8c0@tom> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi! Thank you for the links to the papers. I haven't read them yet, but sounds very interesting. We also have an interesting paper on mobility measure for MANET, which will appear in IEEE Communications Letters: http://www.antd.nist.gov/wctg/manet/kwak_CL2003-0133.ps As Tao pointed out, the link connectivity change is very important and significantly affects the performance of routing algorithms. In the performance studies of routing protocols, Random Waypoint (RWP) model seems to be one of the more popular mobility models used in computer simulations. One of the reasons for its popularity is because RWP model is used in many previous studies available and thus it apeals more to the audience. However, RWP model has some weaknesses, including the long warm up time, and it would be better if the routing protocols are tested using diverse mobility models. In our paper, we remedies the current situation by providing a mobility measure which can standardize different mobility models. I hope you find it helpful. Regards, Byung-Jae Kwak Advanced Network Technologies Division NIST, MD USA Tao Lin wrote: > > William Navidi and Tracy Camp, > > You did a nice job in studying the stationary property of Random Waypoint > model using simulations. > > Besides what are studied in your paper, we think another property, link > connectivity changes (link lifetime or link change rate) is also very > important. Because link connectivity changes are among the fundamental > reasons that cause MANET topology changes and, thus, MANET protocols' > operations, we believe that this kind of study is also very important for > MANET simulations. > > We published a paper discussing a simulation study of stationary property of > link stability in Random Waypoint model: > > Tao Lin and Scott F. Midkiff, "Mobility Versus Link Stability in Simulation > of Mobile Ad Hoc Networks," in Proceedings of the Communication Networks and > Distributed Systems Modeling and Simulation Conference (CNDS), pp. 3-8, Jan. > 2003, Orlando, FL, USA. > > We found that at least with the parameters we tested, the warm up time for > link stability is VERY long for the Random Waypoint model, which is usually > much longer than the warm up time and simulation time used in many previous > papers. Therefore, either we should choose a long enough warm up time or we > should revise/choose the mobility model properly in our simulations. Hope > this helps. > > Thanks, > > Tao Lin > Ph. D. Candidate > Laboratory for Advanced Network (LAN) > ECE Dept. > Virginia Tech > > ----- Original Message ----- > From: "Boleng, Jeffrey L. MAJ" > To: > Cc: > Sent: Wednesday, June 04, 2003 6:09 AM > Subject: [manet] Paper announcement > > > CLASSIFICATION: UNCLASSIFIED > > > > The following paper has been submitted and is available at: > > http://toilers.mines.edu/papers/pdf/stationary.pdf > > > > Other papers by our research group are also available at: > > http://toilers.mines.edu/papers/ > > > > Stationary Distributions for the > > Random Waypoint Mobility Model? > > William Navidi and Tracy Camp > > Department of Mathematical and Computer Sciences > > Colorado School of Mines > > Golden, Colorado 80401 > > wnavidi@mines.edu; tcamp@mines.edu > > April 12th, 2002 > > Abstract > > In simulations of mobile ad hoc networks, the probability distribution > > governing the movement > > of the nodes typically varies over time, and converges to a "steady-state" > > distribution, > > known in the probability literature as the stationary distribution. Some > > published simulation > > results ignore this initialization discrepancy. For those results that > > attempt to account for this > > discrepancy, the practice is to discard an initial sequence of > observations > > from a simulation > > in the hope that the remaining values will closely represent the > stationary > > distribution. This > > approach is inefficient and not always reliable. However, if the initial > > locations and speeds of > > the nodes are chosen from the stationary distribution, convergence is > > immediate and no data > > need be discarded. We derive the stationary distributions for location, > > speed, and pause time > > for the random waypoint mobility model. We then show how to implement the > > random waypoint > > mobility model in order to construct more efficient and reliable > simulations > > for mobile > > ad hoc networks. Simulation results, which verify the correctness of our > > method, are included. > > In addition, implementation of our method for the NS-2 simulator is > > available. > > > > > > Classification: UNCLASSIFIED > > > > > > _______________________________________________ > > 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 -- "Never be afraid to sit awhile and think." -- Lorraine Hansberry _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 4 14:54:32 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 OAA06470 for ; Wed, 4 Jun 2003 14:54:32 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h54Is8H10349 for manet-archive@odin.ietf.org; Wed, 4 Jun 2003 14:54: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 h54Is7B10346 for ; Wed, 4 Jun 2003 14:54: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 OAA06423 for ; Wed, 4 Jun 2003 14:54:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NdMq-0006tV-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 14:52:12 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19NdMp-0006tS-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 14:52:11 -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 h54IiCB09538; Wed, 4 Jun 2003 14:44: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 h54IbrB09249 for ; Wed, 4 Jun 2003 14:37: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 OAA05433 for ; Wed, 4 Jun 2003 14:37:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nd78-0006cc-00 for manet@ietf.org; Wed, 04 Jun 2003 14:35:58 -0400 Received: from smtp1.libero.it ([193.70.192.51]) by ietf-mx with esmtp (Exim 4.12) id 19Nd78-0006cY-00 for manet@ietf.org; Wed, 04 Jun 2003 14:35:58 -0400 Received: from f1u2i7 (151.25.23.120) by smtp1.libero.it (7.0.012) id 3ECB938A004C5DC5; Wed, 4 Jun 2003 20:37:17 +0200 Message-ID: <001f01c32ac9$cf606520$78171997@f1u2i7> From: "Luca S." To: "Holger Karl" , References: <200306040756.01398.karl@ee.tu-berlin.de> Subject: Re: [manet] SINR model Date: Wed, 4 Jun 2003 20:47:53 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 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 agree with my friend Holger Karl... The channel model in OMNET++ work very well... You compare SNIR (omnet++) with SNIR (COSSAP) Regards, Signorin Luca. ----- Original Message ----- From: "Holger Karl" To: "Feng Wang" ; Sent: Wednesday, June 04, 2003 7:56 AM Subject: Re: [manet] SINR model > On Wednesday 04 June 2003 02:24, Feng Wang wrote: > > Hi, all: > > > > Does anybody know which simulator implements relatively realistic SINR > > model? Seems NS2 simplifies this issue too much. But it is especially > > necessary when power/interference related performance is concerned. > > > > Hi, > > Qualnet does, but is commercial. > > We are just plugging together an OMNET++-based ad-hoc simulator > (http://whale.hit.bme.hu/omnetpp/) > that does exactly such a realistic SINR modelling (different error rates in > different parts of a packet when different modulations are used like in > 802.11 broadcast packets, etc.). We plan to have this on sourceforge within > this month, along with 802.11 model, etc. > > Best regards > > Holger > > > > _______________________________________________ > 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 Jun 4 22:05: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 WAA22112 for ; Wed, 4 Jun 2003 22:05:30 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h55255j08002 for manet-archive@odin.ietf.org; Wed, 4 Jun 2003 22:05: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 h55255B07999 for ; Wed, 4 Jun 2003 22:05: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 WAA22103 for ; Wed, 4 Jun 2003 22:04:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nk5u-0002AS-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 22:03:10 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Nk5t-0002AO-00 for manet-web-archive@ietf.org; Wed, 04 Jun 2003 22:03:09 -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 h551sWB07431; Wed, 4 Jun 2003 21:54: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 h551jkB07229 for ; Wed, 4 Jun 2003 21:45: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 VAA21681 for ; Wed, 4 Jun 2003 21:45:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NjnE-00025e-00 for manet@ietf.org; Wed, 04 Jun 2003 21:43:52 -0400 Received: from web42001.mail.yahoo.com ([66.218.93.169]) by ietf-mx with smtp (Exim 4.12) id 19NjnD-00025b-00 for manet@ietf.org; Wed, 04 Jun 2003 21:43:51 -0400 Message-ID: <20030605014512.69138.qmail@web42001.mail.yahoo.com> Received: from [68.27.203.84] by web42001.mail.yahoo.com via HTTP; Wed, 04 Jun 2003 18:45:12 PDT Date: Wed, 4 Jun 2003 18:45:12 -0700 (PDT) From: Sunil Sharma To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-365983582-1054777512=:67739" Subject: [manet] OPNET 802.11 model ? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-365983582-1054777512=:67739 Content-Type: text/plain; charset=us-ascii Hi, I am new in modeling. Does anyone know if OPNET has correctly working 802.11 model ? Does anyone even know of 802.11e or 802.16 model in OPNET ? I am starting with my M.S thesis and I need to decide if I can use OPNET 802.11 model (of which I have already had lot of negative feedback from couple of users). So any feedback and work around would be very useful. Thanks Sunil --------------------------------- Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. --0-365983582-1054777512=:67739 Content-Type: text/html; charset=us-ascii
Hi,
 
I am new in modeling. Does anyone know if OPNET has correctly working 802.11 model ? Does anyone even know of 802.11e or 802.16 model in OPNET ?
 
I am starting with my M.S thesis and I need to decide if I can use OPNET 802.11 model (of which I have already had lot of negative feedback from couple of users). So any feedback and work around would be very useful.
 
Thanks
 
Sunil

Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo. --0-365983582-1054777512=:67739-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 5 03:16: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 DAA09560 for ; Thu, 5 Jun 2003 03:16:29 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h557G0707692 for manet-archive@odin.ietf.org; Thu, 5 Jun 2003 03:16: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 h557FxB07689 for ; Thu, 5 Jun 2003 03:15: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 DAA09546 for ; Thu, 5 Jun 2003 03:15:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nowp-0003l8-00 for manet-web-archive@ietf.org; Thu, 05 Jun 2003 03:14:07 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Nowo-0003l5-00 for manet-web-archive@ietf.org; Thu, 05 Jun 2003 03:14: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 h5572LB06061; Thu, 5 Jun 2003 03:02: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 h556wvB05913 for ; Thu, 5 Jun 2003 02:58: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 CAA09142 for ; Thu, 5 Jun 2003 02:58:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NogG-0003ek-00 for manet@ietf.org; Thu, 05 Jun 2003 02:57:00 -0400 Received: from x86unx3.comp.nus.edu.sg ([137.132.90.3]) by ietf-mx with esmtp (Exim 4.12) id 19NogF-0003eh-00 for manet@ietf.org; Thu, 05 Jun 2003 02:56:59 -0400 Received: from e500a.comp.nus.edu.sg (e500a.comp.nus.edu.sg [137.132.90.23]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id OAA10759 for ; Thu, 5 Jun 2003 14:58:43 +0800 (GMT-8) From: Er Inn Inn Received: from se11.comp.nus.edu.sg(137.132.80.19) by e500a.comp.nus.edu.sg via csmap id 11036; Thu, 05 Jun 2003 14:58:39 +0800 (SGT) Received: (from http@localhost) by se11.comp.nus.edu.sg (8.12.2+Sun/8.12.5) id h556wddf028668; Thu, 5 Jun 2003 14:58:39 +0800 (SGT) X-Authentication-Warning: se11.comp.nus.edu.sg: http set sender to erinninn@comp.nus.edu.sg using -f Received: from noc.comp.nus.edu.sg ([137.132.80.35]) (proxying for 137.132.31.162) (SquirrelMail authenticated user erinninn) by mysoc.nus.edu.sg with HTTP; Thu, 5 Jun 2003 14:58:39 +0800 (SGT) Message-ID: <22137.137.132.80.35.1054796319.squirrel@mysoc.nus.edu.sg> Date: Thu, 5 Jun 2003 14:58:39 +0800 (SGT) To: In-Reply-To: <20030605014512.69138.qmail@web42001.mail.yahoo.com> References: <20030605014512.69138.qmail@web42001.mail.yahoo.com> X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Subject: [manet] Regarding monarch multicast extension Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, I m relatively new user of NS and hope that you guys can give me some help here. Actually I have downloaded ns source tree with multicast extension developed by Rice Monarch Project. I tried to install NS piece by piece. However, I seemed to be facing problem when tried to compile NS source tree (ns-2.1b8-mcast). I tried to solve the problem and the compilation turned out to be successful. Then I tried to run validation. During the validation process, I got a lot of error messages. The main error msg is "error while loading shared libraries: libotcl.so..... " I am at the end of my wit now... I hope someone can help. This is part of my master project work. Thanks in advance. regards, inn inn _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 5 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 NAA07406 for ; Thu, 5 Jun 2003 13:36:24 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h55HZvZ24378 for manet-archive@odin.ietf.org; Thu, 5 Jun 2003 13:35: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 h55HZvB24375 for ; Thu, 5 Jun 2003 13:35: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 NAA07389 for ; Thu, 5 Jun 2003 13:35:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nycj-0001Na-00 for manet-web-archive@ietf.org; Thu, 05 Jun 2003 13:34:01 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Nycj-0001NX-00 for manet-web-archive@ietf.org; Thu, 05 Jun 2003 13:34: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 h55HBLB23099; Thu, 5 Jun 2003 13:11: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 h55H60B22020 for ; Thu, 5 Jun 2003 13:06: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 NAA06625 for ; Thu, 5 Jun 2003 13:05:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ny9l-0001Aa-00 for manet@ietf.org; Thu, 05 Jun 2003 13:04:05 -0400 Received: from uni03du.unity.ncsu.edu ([152.1.13.103]) by ietf-mx with esmtp (Exim 4.12) id 19Ny9k-0001AQ-00 for manet@ietf.org; Thu, 05 Jun 2003 13:04:04 -0400 Received: (from mlsichit@localhost) by uni03du.unity.ncsu.edu (8.8.4/EC02Jan97) id NAA16354; Thu, 5 Jun 2003 13:05:51 -0400 (EDT) Date: Thu, 5 Jun 2003 13:05:51 -0400 (EDT) From: Mihail L Sichitiu To: manet@ietf.org In-Reply-To: <20030605160002.16571.2583.Mailman@www1.ietf.org> Message-ID: References: <20030605160002.16571.2583.Mailman@www1.ietf.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Re: OPNET 802.11 model ? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Sunil, I have very bad experience with the 802.11 model in Opnet. It seems to work reasonably well in managed mode (i.e. with access points), but it breaks badly in ad-hoc mode (which I assume you'd like to use, given the list orientation). The 802.11 model keeps changing with every version (every 3-6 months), so if you fix some of the bugs, you'll have to fix the *same* bug over and over again in the subsequent versions, on top of finding the new bugs. Moreover, despite the commercial nature of the product, the support is very poor: every time you call or email them you talk with a different person, that understands more or less a part of your problem (from scratch). The support persons are not the same as the programmers, so they have no idea how a specific feature is implemented, or whether is implemented at all. I am planning to switch to ns-2 this summer, and I suggest you do the same, and skip the pain we've been going through the last two years. I also found a small bug in the ns-2 code 1 year ago, I'm not sure if it's still there. I didn't see any Opnet 802.11e models, and I expect that it will be a while until they'll show up. Best regards, Mihail Sichitiu _______________________________________________________ Mihail L. Sichitiu Assistant Professor, Phone: (919) 515 7348 Dept. of ECE, Campus Box 7911 Fax: (919) 515 5523 NC State University Raleigh, NC 27695-7911 http://www4.ncsu.edu/~mlsichit _______________________________________________________ > Date: Wed, 4 Jun 2003 18:45:12 -0700 (PDT) > From: Sunil Sharma > To: manet@ietf.org > Subject: [manet] OPNET 802.11 model ? > > --0-365983582-1054777512=:67739 > Content-Type: text/plain; charset=us-ascii > > Hi, > > I am new in modeling. Does anyone know if OPNET has correctly working 802.11 model ? Does anyone even know of 802.11e or 802.16 model in OPNET ? > > I am starting with my M.S thesis and I need to decide if I can use OPNET 802.11 model (of which I have already had lot of negative feedback from couple of users). So any feedback and work around would be very useful. > > Thanks > > Sunil _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 5 14:10:01 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 OAA08841 for ; Thu, 5 Jun 2003 14:10:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h55I9Zu27857 for manet-archive@odin.ietf.org; Thu, 5 Jun 2003 14:09: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 h55I9ZB27854 for ; Thu, 5 Jun 2003 14:09: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 OAA08794 for ; Thu, 5 Jun 2003 14:09:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nz9G-0001gZ-00 for manet-web-archive@ietf.org; Thu, 05 Jun 2003 14:07:38 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Nz9G-0001gW-00 for manet-web-archive@ietf.org; Thu, 05 Jun 2003 14:07: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 h55HvRB26257; Thu, 5 Jun 2003 13:57: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 h55HrGB26102 for ; Thu, 5 Jun 2003 13:53: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 NAA08089 for ; Thu, 5 Jun 2003 13:53:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NytT-0001WN-00 for manet@ietf.org; Thu, 05 Jun 2003 13:51:19 -0400 Received: from fmr01.intel.com ([192.55.52.18] helo=hermes.fm.intel.com) by ietf-mx with esmtp (Exim 4.12) id 19NytS-0001WK-00 for manet@ietf.org; Thu, 05 Jun 2003 13:51:18 -0400 Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39]) by hermes.fm.intel.com (8.11.6p2/8.11.6/d: outer.mc,v 1.66 2003/05/22 21:17:36 rfjohns1 Exp $) with ESMTP id h55Hmet06131 for ; Thu, 5 Jun 2003 17:48:40 GMT Received: from orsmsxvs041.jf.intel.com (orsmsxvs041.jf.intel.com [192.168.65.54]) by talaria.fm.intel.com (8.11.6p2/8.11.6/d: inner.mc,v 1.35 2003/05/22 21:18:01 rfjohns1 Exp $) with SMTP id h55HrnE14783 for ; Thu, 5 Jun 2003 17:53:49 GMT Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) by orsmsxvs041.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2003060510530800044 ; Thu, 05 Jun 2003 10:53:09 -0700 Received: from orsmsx407.amr.corp.intel.com ([192.168.65.50]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 5 Jun 2003 10:53:08 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Subject: RE: [manet] Re: OPNET 802.11 model ? Date: Thu, 5 Jun 2003 10:53:08 -0700 Message-ID: Thread-Topic: [manet] Re: OPNET 802.11 model ? Thread-Index: AcMriOL4d5gPugGYTYq4hPD6K3n4gwAAc3qQ From: "Yang, Lily L" To: "Mihail L Sichitiu" Cc: X-OriginalArrivalTime: 05 Jun 2003 17:53:08.0636 (UTC) FILETIME=[52D0A5C0:01C32B8B] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h55HrGB26103 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, Mihail -- I just started using OpNet for our multi-hop ad hoc network simulation and already had issues with it. For example, static routing doesn't work at all and so it is hard to simulate multi-hop static routes unless using some cumbersome workaround. Since you've had some experience already and would you care to elaborate some of the trouble you've encountered? That might help me make up my mind in picking the right simulation tool. What I heard so far is that the PHY model in OpNet is much better than ns-2 and others. what is your opinion on that? Thanks, Lily -----Original Message----- From: Mihail L Sichitiu [mailto:mlsichit@unity.ncsu.edu] Sent: Thursday, June 05, 2003 10:06 AM To: manet@ietf.org Subject: [manet] Re: OPNET 802.11 model ? Sunil, I have very bad experience with the 802.11 model in Opnet. It seems to work reasonably well in managed mode (i.e. with access points), but it breaks badly in ad-hoc mode (which I assume you'd like to use, given the list orientation). The 802.11 model keeps changing with every version (every 3-6 months), so if you fix some of the bugs, you'll have to fix the *same* bug over and over again in the subsequent versions, on top of finding the new bugs. Moreover, despite the commercial nature of the product, the support is very poor: every time you call or email them you talk with a different person, that understands more or less a part of your problem (from scratch). The support persons are not the same as the programmers, so they have no idea how a specific feature is implemented, or whether is implemented at all. I am planning to switch to ns-2 this summer, and I suggest you do the same, and skip the pain we've been going through the last two years. I also found a small bug in the ns-2 code 1 year ago, I'm not sure if it's still there. I didn't see any Opnet 802.11e models, and I expect that it will be a while until they'll show up. Best regards, Mihail Sichitiu _______________________________________________________ Mihail L. Sichitiu Assistant Professor, Phone: (919) 515 7348 Dept. of ECE, Campus Box 7911 Fax: (919) 515 5523 NC State University Raleigh, NC 27695-7911 http://www4.ncsu.edu/~mlsichit _______________________________________________________ > Date: Wed, 4 Jun 2003 18:45:12 -0700 (PDT) > From: Sunil Sharma > To: manet@ietf.org > Subject: [manet] OPNET 802.11 model ? > > --0-365983582-1054777512=:67739 > Content-Type: text/plain; charset=us-ascii > > Hi, > > I am new in modeling. Does anyone know if OPNET has correctly working 802.11 model ? Does anyone even know of 802.11e or 802.16 model in OPNET ? > > I am starting with my M.S thesis and I need to decide if I can use OPNET 802.11 model (of which I have already had lot of negative feedback from couple of users). So any feedback and work around would be very useful. > > Thanks > > Sunil _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 5 15:17:41 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 PAA12930 for ; Thu, 5 Jun 2003 15:17:41 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h55JHCK01111 for manet-archive@odin.ietf.org; Thu, 5 Jun 2003 15:17: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 h55JHCB01107 for ; Thu, 5 Jun 2003 15:17: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 PAA12882 for ; Thu, 5 Jun 2003 15:17:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19O0Ck-0002Sa-00 for manet-web-archive@ietf.org; Thu, 05 Jun 2003 15:15:18 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19O0Ck-0002SX-00 for manet-web-archive@ietf.org; Thu, 05 Jun 2003 15:15: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 h55J5wB31753; Thu, 5 Jun 2003 15:05: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 h55J0VB31497 for ; Thu, 5 Jun 2003 15:00: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 PAA10988 for ; Thu, 5 Jun 2003 15:00:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NzwX-0002Fh-00 for manet@ietf.org; Thu, 05 Jun 2003 14:58:33 -0400 Received: from smtpproxy2.mitre.org ([192.80.55.70]) by ietf-mx with esmtp (Exim 4.12) id 19NzwW-0002Fc-00 for manet@ietf.org; Thu, 05 Jun 2003 14:58:32 -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 h55J0NAu021959; Thu, 5 Jun 2003 15:00:23 -0400 (EDT) Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31]) by smtpsrv2.mitre.org (8.12.9/8.12.8) with ESMTP id h55J0Owf022715; Thu, 5 Jun 2003 15:00:25 -0400 (EDT) Received: from m29103-pc.mitre.org (128.29.55.36) by mailhub1.mitre.org with SMTP id 2849696; Thu, 05 Jun 2003 15:00:14 -0400 Message-ID: <3EDF933D.C4762EB8@mitre.org> Date: Thu, 05 Jun 2003 15:00:13 -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: "Yang, Lily L" CC: Mihail L Sichitiu , manet@ietf.org, umoral@opnet.com Subject: Re: [manet] Re: OPNET 802.11 model ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Lily, I did some modeling with the OPNET's 802.11 model in an older version and found that it did not serve my needs so I revised it. Later I sent my revisions to OPNET and they then added the features I wanted in the next upgrade. I believe if you find a deficiency in one of their models they are more than will to correct it. The key is documenting your changes well and explaining why you are making them. I used a search string to help the OPNET engineers find my changes. They want their models to be the best they can be. The physical model in opnet is implemented in stages. You have full control of each stage and can add a number of features unique to your research, for example, a completely different modulation scheme or unique propagation model. Also, you probably can find some additional models, if not now, later, that users have developed to enhance the physical layer models. I have not worked with their 802.11 model for a while now but when I last used it, one feature I wished was modeled was the process of selecting the data rate and then the modeling of interference amongst radios using different data rates. The model I am familiar with, ( version 7), did not show this interference. John "Yang, Lily L" wrote: > Hi, Mihail -- > > I just started using OpNet for our multi-hop ad hoc network simulation and already had issues with it. For example, static routing doesn't work at all and so it is hard to simulate multi-hop static routes unless using some cumbersome workaround. Since you've had some experience already and would you care to elaborate some of the trouble you've encountered? That might help me make up my mind in picking the right simulation tool. What I heard so far is that the PHY model in OpNet is much better than ns-2 and others. what is your opinion on that? > > Thanks, > Lily > > -----Original Message----- > From: Mihail L Sichitiu [mailto:mlsichit@unity.ncsu.edu] > Sent: Thursday, June 05, 2003 10:06 AM > To: manet@ietf.org > Subject: [manet] Re: OPNET 802.11 model ? > > Sunil, > > I have very bad experience with the 802.11 model in Opnet. It seems to > work reasonably well in managed mode (i.e. with access points), but it > breaks badly in ad-hoc mode (which I assume you'd like to use, given the > list orientation). > > The 802.11 model keeps changing with every version (every 3-6 months), so > if you fix some of the bugs, you'll have to fix the *same* bug over and > over again in the subsequent versions, on top of finding the new bugs. > > Moreover, despite the commercial nature of the product, the support is > very poor: every time you call or email them you talk with a different > person, that understands more or less a part of your problem (from > scratch). The support persons are not the same as the programmers, so they > have no idea how a specific feature is implemented, or whether is > implemented at all. > > I am planning to switch to ns-2 this summer, and I suggest you do the > same, and skip the pain we've been going through the last two years. I > also found a small bug in the ns-2 code 1 year ago, I'm not sure if it's > still there. > > I didn't see any Opnet 802.11e models, and I expect that it will be a > while until they'll show up. > > Best regards, > Mihail Sichitiu > > _______________________________________________________ > Mihail L. Sichitiu > Assistant Professor, Phone: (919) 515 7348 > Dept. of ECE, Campus Box 7911 Fax: (919) 515 5523 > NC State University > Raleigh, NC 27695-7911 http://www4.ncsu.edu/~mlsichit > _______________________________________________________ > > > Date: Wed, 4 Jun 2003 18:45:12 -0700 (PDT) > > From: Sunil Sharma > > To: manet@ietf.org > > Subject: [manet] OPNET 802.11 model ? > > > > --0-365983582-1054777512=:67739 > > Content-Type: text/plain; charset=us-ascii > > > > Hi, > > > > I am new in modeling. Does anyone know if OPNET has correctly working 802.11 model ? Does anyone even know of 802.11e or 802.16 model in OPNET ? > > > > I am starting with my M.S thesis and I need to decide if I can use OPNET 802.11 model (of which I have already had lot of negative feedback from couple of users). So any feedback and work around would be very useful. > > > > Thanks > > > > Sunil > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 5 15:45:32 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 PAA13906 for ; Thu, 5 Jun 2003 15:45:32 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h55Jj3e03750 for manet-archive@odin.ietf.org; Thu, 5 Jun 2003 15:45: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 h55Jj3B03747 for ; Thu, 5 Jun 2003 15:45: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 PAA13895 for ; Thu, 5 Jun 2003 15:45:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19O0dh-0002hd-00 for manet-web-archive@ietf.org; Thu, 05 Jun 2003 15:43:09 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19O0dg-0002ha-00 for manet-web-archive@ietf.org; Thu, 05 Jun 2003 15:43: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 h55JYbB02217; Thu, 5 Jun 2003 15:34: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 h55JW1B02100 for ; Thu, 5 Jun 2003 15:32: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 PAA13517 for ; Thu, 5 Jun 2003 15:31:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19O0R5-0002bY-00 for manet@ietf.org; Thu, 05 Jun 2003 15:30:07 -0400 Received: from uni03du.unity.ncsu.edu ([152.1.13.103]) by ietf-mx with esmtp (Exim 4.12) id 19O0R4-0002bV-00 for manet@ietf.org; Thu, 05 Jun 2003 15:30:06 -0400 Received: (from mlsichit@localhost) by uni03du.unity.ncsu.edu (8.8.4/EC02Jan97) id PAA25395; Thu, 5 Jun 2003 15:31:51 -0400 (EDT) Date: Thu, 5 Jun 2003 15:31:50 -0400 (EDT) From: Mihail L Sichitiu To: John Stine cc: "Yang, Lily L" , manet@ietf.org, umoral@opnet.com, "Jun, Jangeun -- Jangeun Jun" , jjun@ncsu.edu Subject: Re: [manet] Re: OPNET 802.11 model ? In-Reply-To: <3EDF933D.C4762EB8@mitre.org> Message-ID: References: <3EDF933D.C4762EB8@mitre.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , I'm very glad you had a good experience with Opnet. Unfortunately it was not the case for us. In the end (last 2-3 months) we eventually got shut off the Opnet support completely: we are at a university (NCSU) with about 100 licenses and the only persons allowed to talk with the Opnet support are the same persons that install the software, i.e. the system admins. The students, cannot access the Opnet support, because the same password used to get on the Opnet support forum is also used to manage the licenses. Kind of like, I cannot give the key to my research lab to my students, because the same key also starts my Porche and opens the front door of my home. Regarding your observation that they want their models to be the best, I have no doubt about it; however, I don't see that they are willing to make the effort to make it so. After six-seven years after the publication of 802.11 standard, they still have bugs in their models. And 802.11 is not just one of the many wireless standards: for now is "the" standard for wireless LANs. The hardware you buy from the store works better than their models (I don't really have the experience, but I would think that the software would be easier to do than the hardware, as you can gloss over some details). For a better 802.11 physical model, look at the model in Opnet 8 (actually >8.1.C if I remember correctly): it is vastly improved (it drops the notion of a deterministic transmission radius (with zero probability of reception after a certain point), and the packets start to be received with a certain probability depending on the signal to interference + noise ratio), and yet it's not well tuned (the carrier is sensed with high probability even at distances many times the transmission radius). Also, in Opnet you would think that you can replace an Ethernet MAC layer with an 802.11 MAC and keep the rest of the stack the same, but unfortunately it's not the case. On the other hand, it has a great GUI and decent tutorials :-) Best regards, Mihail Sichitiu Thu, 5 Jun 2003, John Stine wrote: > Lily, > > I did some modeling with the OPNET's 802.11 model in an older > version and found that it did not serve my needs so I revised it. > Later I sent my revisions to OPNET and they then added the features > I wanted in the next upgrade. I believe if you find a deficiency in > one of their models they are more than will to correct it. The key > is documenting your changes well and explaining why you are making > them. I used a search string to help the OPNET engineers find my > changes. They want their models to be the best they can be. > > The physical model in opnet is implemented in stages. You have full > control of each stage and can add a number of features unique to your > research, for example, a completely different modulation scheme or > unique propagation model. Also, you probably can find some additional > models, if not now, later, that users have developed to enhance the > physical layer models. I have not worked with their 802.11 model for a > while now but when I last used it, one feature I wished was modeled was > the process of selecting the data rate and then the modeling of > interference amongst radios using different data rates. The model I am > familiar with, ( version 7), did not show this interference. > > John > > "Yang, Lily L" wrote: > > > Hi, Mihail -- > > > > I just started using OpNet for our multi-hop ad hoc network simulation and already had issues with it. For example, static routing doesn't work at all and so it is hard to simulate multi-hop static routes unless using some cumbersome workaround. Since you've had some experience already and would you care to elaborate some of the trouble you've encountered? That might help me make up my mind in picking the right simulation tool. What I heard so far is that the PHY model in OpNet is much better than ns-2 and others. what is your opinion on that? > > > > Thanks, > > Lily > > > > -----Original Message----- > > From: Mihail L Sichitiu [mailto:mlsichit@unity.ncsu.edu] > > Sent: Thursday, June 05, 2003 10:06 AM > > To: manet@ietf.org > > Subject: [manet] Re: OPNET 802.11 model ? > > > > Sunil, > > > > I have very bad experience with the 802.11 model in Opnet. It seems to > > work reasonably well in managed mode (i.e. with access points), but it > > breaks badly in ad-hoc mode (which I assume you'd like to use, given the > > list orientation). > > > > The 802.11 model keeps changing with every version (every 3-6 months), so > > if you fix some of the bugs, you'll have to fix the *same* bug over and > > over again in the subsequent versions, on top of finding the new bugs. > > > > Moreover, despite the commercial nature of the product, the support is > > very poor: every time you call or email them you talk with a different > > person, that understands more or less a part of your problem (from > > scratch). The support persons are not the same as the programmers, so they > > have no idea how a specific feature is implemented, or whether is > > implemented at all. > > > > I am planning to switch to ns-2 this summer, and I suggest you do the > > same, and skip the pain we've been going through the last two years. I > > also found a small bug in the ns-2 code 1 year ago, I'm not sure if it's > > still there. > > > > I didn't see any Opnet 802.11e models, and I expect that it will be a > > while until they'll show up. > > > > Best regards, > > Mihail Sichitiu > > > > _______________________________________________________ > > Mihail L. Sichitiu > > Assistant Professor, Phone: (919) 515 7348 > > Dept. of ECE, Campus Box 7911 Fax: (919) 515 5523 > > NC State University > > Raleigh, NC 27695-7911 http://www4.ncsu.edu/~mlsichit > > _______________________________________________________ > > > > > Date: Wed, 4 Jun 2003 18:45:12 -0700 (PDT) > > > From: Sunil Sharma > > > To: manet@ietf.org > > > Subject: [manet] OPNET 802.11 model ? > > > > > > --0-365983582-1054777512=:67739 > > > Content-Type: text/plain; charset=us-ascii > > > > > > Hi, > > > > > > I am new in modeling. Does anyone know if OPNET has correctly working 802.11 model ? Does anyone even know of 802.11e or 802.16 model in OPNET ? > > > > > > I am starting with my M.S thesis and I need to decide if I can use OPNET 802.11 model (of which I have already had lot of negative feedback from couple of users). So any feedback and work around would be very useful. > > > > > > Thanks > > > > > > Sunil > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 6 12:08:28 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 MAA00258 for ; Fri, 6 Jun 2003 12:08:28 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h56G81105313 for manet-archive@odin.ietf.org; Fri, 6 Jun 2003 12:08: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 h56G81B05310 for ; Fri, 6 Jun 2003 12:08: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 MAA00236 for ; Fri, 6 Jun 2003 12:07:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OJjB-0003Xd-00 for manet-web-archive@ietf.org; Fri, 06 Jun 2003 12:06:05 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19OJjA-0003XY-00 for manet-web-archive@ietf.org; Fri, 06 Jun 2003 12:06: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 h56FpJB03068; Fri, 6 Jun 2003 11:51: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 h56FgfB02687 for ; Fri, 6 Jun 2003 11:42: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 LAA29001 for ; Fri, 6 Jun 2003 11:42:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OJKg-0003F8-00 for manet@ietf.org; Fri, 06 Jun 2003 11:40:46 -0400 Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx with esmtp (Exim 4.12) id 19OJKf-0003F5-00 for manet@ietf.org; Fri, 06 Jun 2003 11:40:45 -0400 Received: from dagger.cc.vt.edu (IDENT:mirapoint@evil-dagger [10.1.1.11]) by lennier.cc.vt.edu (8.12.8/8.12.8) with ESMTP id h56FgbKU124609; Fri, 6 Jun 2003 11:42:37 -0400 (EDT) Received: from zathras (zathras.cc.vt.edu [198.82.162.117]) by dagger.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BMV11938; Fri, 6 Jun 2003 11:42:36 -0400 (EDT) X-WebMail-UserID: vdham Date: Fri, 6 Jun 2003 11:42:36 -0400 From: Vikram Dham To: "Yang, Lily L" , John Stine Cc: manet , Mihail L Sichitiu , umoral X-EXP32-SerialNo: 00002964 Subject: RE: [manet] Re: OPNET 802.11 model ? Message-ID: <3EE42DD7@zathras> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: WebMail (Hydra) SMTP v3.61.08 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I worked with vintage OPNET 8.0 when I was using 802.11 model and I had to make changes in physical layer to obtain even basic results. I am not sure how well it implements the features of Access Point or if it implements all the control mechanisms of 802.11. Thanks Vikram >===== Original Message From John Stine ===== >Lily, > > I did some modeling with the OPNET's 802.11 model in an older version and found that it did not serve my needs so I revised it. Later I sent my revisions to OPNET and they then added the features I wanted in the next upgrade. I believe if you find a deficiency in one of their models they are more than will to correct it. The key is documenting your changes well and explaining why you are making them. I used a search string to help the OPNET engineers find my changes. They want their models to be the best they can be. > > The physical model in opnet is implemented in stages. You have full control of each stage and can add a number of features unique to your research, for example, a completely different modulation scheme or unique propagation model. Also, you probably can find some additional models, if not now, later, that users have developed to enhance the physical layer models. I have not worked with their 802.11 model for a while now but when I last used it, one feature I wished was modeled was the process of selecting the data rate and then the modeling >of interference amongst radios using different data rates. The model I am familiar with, ( version 7), did not show this interference. > >John > >"Yang, Lily L" wrote: > >> Hi, Mihail -- >> >> I just started using OpNet for our multi-hop ad hoc network simulation and already had issues with it. For example, static routing doesn't work at all and so it is hard to simulate multi-hop static routes unless using some cumbersome workaround. Since you've had some experience already and would you care to elaborate some of the trouble you've encountered? That might help me make up my mind in picking the right simulation tool. What I heard so far is that the PHY model in OpNet is much better than ns-2 and others. what is your opinion on that? >> >> Thanks, >> Lily >> >> -----Original Message----- >> From: Mihail L Sichitiu [mailto:mlsichit@unity.ncsu.edu] >> Sent: Thursday, June 05, 2003 10:06 AM >> To: manet@ietf.org >> Subject: [manet] Re: OPNET 802.11 model ? >> >> Sunil, >> >> I have very bad experience with the 802.11 model in Opnet. It seems to >> work reasonably well in managed mode (i.e. with access points), but it >> breaks badly in ad-hoc mode (which I assume you'd like to use, given the >> list orientation). >> >> The 802.11 model keeps changing with every version (every 3-6 months), so >> if you fix some of the bugs, you'll have to fix the *same* bug over and >> over again in the subsequent versions, on top of finding the new bugs. >> >> Moreover, despite the commercial nature of the product, the support is >> very poor: every time you call or email them you talk with a different >> person, that understands more or less a part of your problem (from >> scratch). The support persons are not the same as the programmers, so they >> have no idea how a specific feature is implemented, or whether is >> implemented at all. >> >> I am planning to switch to ns-2 this summer, and I suggest you do the >> same, and skip the pain we've been going through the last two years. I >> also found a small bug in the ns-2 code 1 year ago, I'm not sure if it's >> still there. >> >> I didn't see any Opnet 802.11e models, and I expect that it will be a >> while until they'll show up. >> >> Best regards, >> Mihail Sichitiu >> >> _______________________________________________________ >> Mihail L. Sichitiu >> Assistant Professor, Phone: (919) 515 7348 >> Dept. of ECE, Campus Box 7911 Fax: (919) 515 5523 >> NC State University >> Raleigh, NC 27695-7911 http://www4.ncsu.edu/~mlsichit >> _______________________________________________________ >> >> > Date: Wed, 4 Jun 2003 18:45:12 -0700 (PDT) >> > From: Sunil Sharma >> > To: manet@ietf.org >> > Subject: [manet] OPNET 802.11 model ? >> > >> > --0-365983582-1054777512=:67739 >> > Content-Type: text/plain; charset=us-ascii >> > >> > Hi, >> > >> > I am new in modeling. Does anyone know if OPNET has correctly working 802.11 model ? Does anyone even know of 802.11e or 802.16 model in OPNET ? >> > >> > I am starting with my M.S thesis and I need to decide if I can use OPNET 802.11 model (of which I have already had lot of negative feedback from couple of users). So any feedback and work around would be very useful. >> > >> > Thanks >> > >> > Sunil >> _______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www1.ietf.org/mailman/listinfo/manet >> _______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www1.ietf.org/mailman/listinfo/manet > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 6 12:18: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 MAA00945 for ; Fri, 6 Jun 2003 12:18:05 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h56GHdS06521 for manet-archive@odin.ietf.org; Fri, 6 Jun 2003 12: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 h56GHdB06518 for ; Fri, 6 Jun 2003 12:17: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 MAA00927 for ; Fri, 6 Jun 2003 12:17:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OJsU-0003ik-00 for manet-web-archive@ietf.org; Fri, 06 Jun 2003 12:15:43 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19OJsU-0003ih-00 for manet-web-archive@ietf.org; Fri, 06 Jun 2003 12:15: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 h56G6eB04329; Fri, 6 Jun 2003 12:06: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 h56G3QB04079 for ; Fri, 6 Jun 2003 12:03: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 MAA29969 for ; Fri, 6 Jun 2003 12:03:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OJek-0003VD-00 for manet@ietf.org; Fri, 06 Jun 2003 12:01:30 -0400 Received: from newpostman.opnet.com ([12.145.55.19]) by ietf-mx with esmtp (Exim 4.12) id 19OJej-0003VA-00 for manet@ietf.org; Fri, 06 Jun 2003 12:01:29 -0400 Received: from wtn13013.opnet.com (wtn13013.opnet.com [172.16.13.13]) by newpostman.opnet.com (8.12.9/8.12.1) with ESMTP id h56G3NKZ025862 for ; Fri, 6 Jun 2003 12:03:23 -0400 (EDT) Message-Id: <5.1.0.14.2.20030606111045.00aee3b8@mailserver.opnet.com> X-Sender: scartwright@mailserver.opnet.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 06 Jun 2003 12:02:39 -0400 To: manet@ietf.org From: Sarah Cartwright Subject: Re: [manet] Re: OPNET 802.11 model ? In-Reply-To: <4.2.0.58.20030605161714.00a686a0@mailserver.opnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi everyone: I just wanted to share a few quick comments about OPNET's 802.11 model and support-- The current release of OPNET products is version 9.1. If you haven't seen us recently, it may well be worth your while, as it contain many enhancements, including: - reception power threshold (for more accurate modeling of receiver sensitivity and spatial reuse) - PLCP header and preamble overhead effects - significant performance enhancements during simulation - numerous fixes to previously reported software problems Future OPNET 802.11 model releases are expected to have further physical layer enhancements and roaming capabilities. We are dedicated to quality and accuracy in results, and we do our very best to provide a fix or workaround for any reported problem that affects customer studies. The developers who create our software are also the engineers who directly provide support, so you can count on OPNET support staff to be technical and familiar with the software, to quickly find the answers you're looking for. Support procedures have recently changed for universities as well, in response to your many requests. For instance, student access to online resources has been expanded. Thanks for your time---if you have questions or concerns about OPNET products or services, please don't hesitate to contact us at info@opnet.com. --------------------------------- Ms. Sarah CARTWRIGHT (scartwright@opnet.com) Director, Technical Support OPNET Technologies, Inc. (http://www.opnet.com/) phone 240.497.3000 --------------------------------- Register for OPNET's Online Technology Workshops (http://www.opnet.com/TechWorkshops/) --------------------------------- Register for OPNETWORK 2003 (August 25-29, in Washington DC) (http://www.opnet.com/opnetwork2003/) --------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Jun 8 10:38: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 KAA23483 for ; Sun, 8 Jun 2003 10:38:20 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h58Ebua03097 for manet-archive@odin.ietf.org; Sun, 8 Jun 2003 10:37: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 h58EbuB03094 for ; Sun, 8 Jun 2003 10:37: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 KAA23466 for ; Sun, 8 Jun 2003 10:37:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19P1Gy-0003e3-00 for manet-web-archive@ietf.org; Sun, 08 Jun 2003 10:35:52 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19P1Gx-0003dz-00 for manet-web-archive@ietf.org; Sun, 08 Jun 2003 10:35: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 h58EPFB01777; Sun, 8 Jun 2003 10:25: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 h58EBhB01404 for ; Sun, 8 Jun 2003 10:11:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22548 for ; Sun, 8 Jun 2003 10:11:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19P0rc-0003Ue-00 for manet@ietf.org; Sun, 08 Jun 2003 10:09:40 -0400 Received: from tomts24.bellnexxia.net ([209.226.175.187] helo=tomts24-srv.bellnexxia.net) by ietf-mx with esmtp (Exim 4.12) id 19P0rb-0003Ub-00 for manet@ietf.org; Sun, 08 Jun 2003 10:09:39 -0400 Received: from ordi ([64.228.198.163]) by tomts24-srv.bellnexxia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with SMTP id <20030608141136.XCVK9809.tomts24-srv.bellnexxia.net@ordi> for ; Sun, 8 Jun 2003 10:11:36 -0400 Message-ID: <005601c32dc7$dfaf8630$670cfea9@ordi> From: "Omar LAHLOU" To: Date: Sun, 8 Jun 2003 10:11:36 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0053_01C32DA6.5870BBB0" X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [manet] Need Help Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0053_01C32DA6.5870BBB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I am looking for ABR code source to simulate it and compare it to my = routing protocol. Has any one know when could I find it. Thanks for help. Omar. ------=_NextPart_000_0053_01C32DA6.5870BBB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I am looking for ABR code source to = simulate it and=20 compare it to my routing protocol. Has any one know when could I find=20 it.
 
Thanks for help.
 
Omar.
------=_NextPart_000_0053_01C32DA6.5870BBB0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 9 04:44: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 EAA24276 for ; Mon, 9 Jun 2003 04:44:59 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h598iXY13456 for manet-archive@odin.ietf.org; Mon, 9 Jun 2003 04:44:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h598iXB13453 for ; Mon, 9 Jun 2003 04:44: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 EAA24259 for ; Mon, 9 Jun 2003 04:44:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PIEY-0000k2-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 04:42:30 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PIEX-0000jz-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 04:42:29 -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 h598XiB12226; Mon, 9 Jun 2003 04:33: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 h598SjB12036 for ; Mon, 9 Jun 2003 04:28: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 EAA24065 for ; Mon, 9 Jun 2003 04:28:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PHzH-0000fB-00 for manet@ietf.org; Mon, 09 Jun 2003 04:26:43 -0400 Received: from ns.sait.samsung.co.kr ([202.20.142.13]) by ietf-mx with esmtp (Exim 4.12) id 19PHzG-0000f0-00 for manet@ietf.org; Mon, 09 Jun 2003 04:26:42 -0400 Received: from LocalHost (localhost [127.0.0.1]) by ns.sait.samsung.co.kr (8.12.8/8.12.1) with SMTP id h598SBNK004882 for ; Mon, 9 Jun 2003 17:28:11 +0900 (KST) Message-ID: <004701c32e61$114ed3f0$d92f024b@LocalHost> From: "Eunil" To: Date: Mon, 9 Jun 2003 17:28:13 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h598SjB12037 Subject: [manet] Please help me to understand, LANMAR people! Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Dear folks. I am reading the LANMAR stuffs. But there is one thing I don't understand. There is two routing tables, local routing table & LMDV in each nodes of logical group. I do understand how to make local routing table by any proactive protocol. But I don't see much how to exchang the routing information of remote nodes by landmark. As I understand the LANMAR, only the landmarks exchange information of landmark and make the routing table of landmark and broadcast routing information of landmark to neighbors in logical group. Please, do I understand correctly? And let me get what I don't understand about exchange of the routing infomation of landmark. have a good day. ---------------------------------------------------------------------- Eunil Seo Research Engineer, i-Networking Lab. Samsung Advanced Institute of Technology Tel : +82-31-280-9593 Fax: +82-31-280-9587 Mobile : +82-11-9625-8325 E-mail: seoei2@yahoo.com or seoei2@sait.samsung.co.kr ---------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 9 05:11:07 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 FAA24825 for ; Mon, 9 Jun 2003 05:11:06 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h599Afg15417 for manet-archive@odin.ietf.org; Mon, 9 Jun 2003 05:10: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 h599AfB15414 for ; Mon, 9 Jun 2003 05:10: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 FAA24814 for ; Mon, 9 Jun 2003 05:10:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PIdp-0000tH-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 05:08:37 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PIdp-0000tE-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 05:08: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 h598xVB14038; Mon, 9 Jun 2003 04: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 h598uhB13963 for ; Mon, 9 Jun 2003 04:56:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24527 for ; Mon, 9 Jun 2003 04:56:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PIQJ-0000pb-00 for manet@ietf.org; Mon, 09 Jun 2003 04:54:39 -0400 Received: from rumba.cefriel.it ([131.175.53.6]) by ietf-mx with esmtp (Exim 4.12) id 19PIQI-0000oo-00 for manet@ietf.org; Mon, 09 Jun 2003 04:54:39 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 9 Jun 2003 10:58:09 +0200 Message-ID: <28C92BFE6EB5C943B15743D0E11E60360FE7BB@rumba.cefriel.it> Thread-Topic: [manet] Implementation Issues Thread-Index: AcMWTZSVWO45VKC4Rw2cX7o8YJAQdgYFLqFA From: "Nicola Alagia" To: "manet" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h598uhB13964 Subject: [manet] AODV simulation results Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi there, During a route discovery in AODV, an intermediate node can generate a reply message instead of the destination node. I would like to know if someone has simulate the behaviour and has evaluate the performances of the AODV protocol, comparing the two following situations: (a) the intermediate nodes can reply and (b) only the destination node can generate a reply message. Thanks, Nicola _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 9 06:20: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 GAA26400 for ; Mon, 9 Jun 2003 06:20:04 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h59AJeV20011 for manet-archive@odin.ietf.org; Mon, 9 Jun 2003 06:19: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 h59AJeB20008 for ; Mon, 9 Jun 2003 06:19: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 GAA26381 for ; Mon, 9 Jun 2003 06:19:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PJiZ-0001Q6-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 06:17:35 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PJiY-0001Q3-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 06:17:34 -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 h59A9GB19464; Mon, 9 Jun 2003 06:09:16 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h59A5jB18413 for ; Mon, 9 Jun 2003 06:05: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 GAA25797 for ; Mon, 9 Jun 2003 06:05:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PJV7-0001DU-00 for manet@ietf.org; Mon, 09 Jun 2003 06:03:41 -0400 Received: from ns.sait.samsung.co.kr ([202.20.142.13]) by ietf-mx with esmtp (Exim 4.12) id 19PJV6-0001DJ-00 for manet@ietf.org; Mon, 09 Jun 2003 06:03:40 -0400 Received: from LocalHost (localhost [127.0.0.1]) by ns.sait.samsung.co.kr (8.12.8/8.12.1) with SMTP id h59A53NK012143 for ; Mon, 9 Jun 2003 19:05:03 +0900 (KST) Message-ID: <018a01c32e6e$99a1e4b0$d92f024b@LocalHost> From: "Eunil" To: Date: Mon, 9 Jun 2003 19:05:05 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-7" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h59A5jB18414 Subject: [manet] Just test, please ignore this. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Just test. Please forgive it to me. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 9 10:00: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 KAA04948 for ; Mon, 9 Jun 2003 10:00:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h59E08t03709 for manet-archive@odin.ietf.org; Mon, 9 Jun 2003 10:00: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 h59E08B03706 for ; Mon, 9 Jun 2003 10:00: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 KAA04937 for ; Mon, 9 Jun 2003 10:00:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PN9v-0003hp-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 09:58:03 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PN9u-0003hm-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 09:58:02 -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 h59DnbB03381; Mon, 9 Jun 2003 09:49:37 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h59DjlB03277 for ; Mon, 9 Jun 2003 09:45: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 JAA04624 for ; Mon, 9 Jun 2003 09:45:42 -0400 (EDT) From: idc@engineering.ucsb.edu Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PMw3-0003dD-00 for manet@ietf.org; Mon, 09 Jun 2003 09:43:43 -0400 Received: from letters.cs.ucsb.edu ([128.111.41.13]) by ietf-mx with esmtp (Exim 4.12) id 19PMw2-0003d5-00 for manet@ietf.org; Mon, 09 Jun 2003 09:43:42 -0400 Received: from KENAI.cs.ucsb.edu (moment [128.111.40.94]) by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with ESMTP id h59DjKC26846; Mon, 9 Jun 2003 06:45:27 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16100.36720.347000.318371@gargle.gargle.HOWL> Date: Mon, 9 Jun 2003 06:45:20 -0700 To: "Nicola Alagia" Cc: "manet" Subject: RE:[manet] AODV simulation results In-Reply-To: <28C92BFE6EB5C943B15743D0E11E60360FE7BB@rumba.cefriel.it> References: <28C92BFE6EB5C943B15743D0E11E60360FE7BB@rumba.cefriel.it> X-Mailer: VM 7.07 under Emacs 21.1.1 Reply-To: idc@cs.ucsb.edu 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 Luke Klein-Berndt and I examined this while looking at AODVjr. For the scenarios we ran we did not notice a significant difference in delay or overhead. The largest differences will be noticeable when simulating large networks, using expanding ring search, using local repair and scenarios with common destinations. Ian Chakeres See http://moment.cs.ucsb.edu/publications.html to download related publications. >Nicola Alagia wrote: >Hi there, > >During a route discovery in AODV, an intermediate node can generate a reply message instead of the destination node. >I would like to know if someone has simulate the behaviour and has evaluate the performances of the AODV protocol, comparing the two following situations: >(a) the intermediate nodes can reply and >(b) only the destination node can generate a reply message. > >Thanks, > Nicola >_______________________________________________ >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 Jun 9 14:03: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 OAA14634 for ; Mon, 9 Jun 2003 14:03:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h59I3QG22361 for manet-archive@odin.ietf.org; Mon, 9 Jun 2003 14:03: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 h59I3QB22358 for ; Mon, 9 Jun 2003 14:03: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 OAA14610 for ; Mon, 9 Jun 2003 14:03:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PQxN-0005p9-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 14:01:21 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PQxM-0005p5-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 14:01: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 h59HqmB21533; Mon, 9 Jun 2003 13:52: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 h59HkSB21333 for ; Mon, 9 Jun 2003 13:46: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 NAA13943 for ; Mon, 9 Jun 2003 13:46:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PQgx-0005cJ-00 for manet@ietf.org; Mon, 09 Jun 2003 13:44:23 -0400 Received: from cheetah.cs.ucla.edu ([131.179.128.24]) by ietf-mx with esmtp (Exim 4.12) id 19PQgw-0005b6-00 for manet@ietf.org; Mon, 09 Jun 2003 13:44:22 -0400 Received: from localhost (hxy@localhost) by cheetah.cs.ucla.edu (8.11.7+Sun/8.11.6/UCLACS-5.2) with ESMTP id h59Hjkk03236; Mon, 9 Jun 2003 10:45:47 -0700 (PDT) Date: Mon, 9 Jun 2003 10:45:46 -0700 (PDT) From: Xiaoyan Hong To: Eunil cc: , Xiaoyan Hong , Dr Mario Gerla Subject: Re: [manet] Please help me to understand, LANMAR people! In-Reply-To: <004701c32e61$114ed3f0$d92f024b@LocalHost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, Eunil, Actually, each node participates in the landmark information exchange and builds LMDV. They also use the table for routing. Hope this helps. Xiaoyan On Mon, 9 Jun 2003, Eunil wrote: > Dear folks. > > I am reading the LANMAR stuffs. But there is one thing I don't understand. > > There is two routing tables, local routing table & LMDV in each nodes of logical group. > I do understand how to make local routing table by any proactive protocol. > But I don't see much how to exchang the routing information of remote nodes by landmark. > As I understand the LANMAR, only the landmarks exchange information of landmark and > make the routing table of landmark and broadcast routing information of landmark to neighbors in logical group. > > Please, do I understand correctly? And let me get what I don't understand about exchange of the routing infomation of landmark. > > have a good day. > > > ---------------------------------------------------------------------- > Eunil Seo > Research Engineer, > > i-Networking Lab. Samsung Advanced Institute of Technology > Tel : +82-31-280-9593 Fax: +82-31-280-9587 Mobile : +82-11-9625-8325 > E-mail: seoei2@yahoo.com or seoei2@sait.samsung.co.kr > ---------------------------------------------------------------------- > _______________________________________________ > 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 Jun 9 20:20: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 UAA26082 for ; Mon, 9 Jun 2003 20:20:35 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5A0K8r17291 for manet-archive@odin.ietf.org; Mon, 9 Jun 2003 20:20:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5A0K7B17287 for ; Mon, 9 Jun 2003 20:20: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 UAA26063 for ; Mon, 9 Jun 2003 20:20:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PWpv-0000Cx-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 20:18:04 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PWpv-0000Cu-00 for manet-web-archive@ietf.org; Mon, 09 Jun 2003 20:18: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 h59NxsB15543; Mon, 9 Jun 2003 19:59: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 h59NutB15471 for ; Mon, 9 Jun 2003 19:56: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 TAA25575 for ; Mon, 9 Jun 2003 19:56:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PWTT-00004V-00 for manet@ietf.org; Mon, 09 Jun 2003 19:54:51 -0400 Received: from ns.sait.samsung.co.kr ([202.20.142.13]) by ietf-mx with esmtp (Exim 4.12) id 19PWTS-00004R-00 for manet@ietf.org; Mon, 09 Jun 2003 19:54:50 -0400 Received: from LocalHost (localhost [127.0.0.1]) by ns.sait.samsung.co.kr (8.12.8/8.12.1) with SMTP id h59NuKNK012188 for ; Tue, 10 Jun 2003 08:56:20 +0900 (KST) Message-ID: <009c01c32ee2$bb489a90$d92f024b@LocalHost> From: "Eunil" To: "Mobile Ad-hoc Networks" Date: Tue, 10 Jun 2003 08:56:23 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h59NutB15472 Subject: [manet] Does somebody know any kind information of ad-hoc network Consortium? Please let me know. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Dear folks. Our team jumps into ad-hoc network stuff. specially I am digging the hierarchical approach. I want to know the person who can discuss about that. And my really question is ,,,, Does somebody know any kind information of ad-hoc network Consortium? Please let me know. If it is not proper topic, let me say sorry ^^;; Have a good day. ---------------------------------------------------------------------- Eunil Seo Research Engineer, i-Networking Lab. Samsung Advanced Institute of Technology Tel : +82-31-280-9593 Fax: +82-31-280-9587 Mobile : +82-11-9625-8325 E-mail: seoei2@yahoo.com or seoei2@sait.samsung.co.kr ---------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 10 07:43: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 HAA21014 for ; Tue, 10 Jun 2003 07:43:44 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5ABhGw12424 for manet-archive@odin.ietf.org; Tue, 10 Jun 2003 07:43: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 h5ABhFB12421 for ; Tue, 10 Jun 2003 07:43: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 HAA21011 for ; Tue, 10 Jun 2003 07:43:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PhV1-0003yq-00 for manet-web-archive@ietf.org; Tue, 10 Jun 2003 07:41:11 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PhV1-0003yn-00 for manet-web-archive@ietf.org; Tue, 10 Jun 2003 07:41:11 -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 h5ABVkB10876; Tue, 10 Jun 2003 07:31:46 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5ABOjB10591 for ; Tue, 10 Jun 2003 07:24: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 HAA20444 for ; Tue, 10 Jun 2003 07:24:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PhD7-0003oC-00 for manet@ietf.org; Tue, 10 Jun 2003 07:22:41 -0400 Received: from ns.sait.samsung.co.kr ([202.20.142.13]) by ietf-mx with esmtp (Exim 4.12) id 19PhD6-0003nw-00 for manet@ietf.org; Tue, 10 Jun 2003 07:22:40 -0400 Received: from mavpc (localhost [127.0.0.1]) by ns.sait.samsung.co.kr (8.12.8/8.12.1) with SMTP id h5ABOBNK009331 for ; Tue, 10 Jun 2003 20:24:11 +0900 (KST) Message-ID: <001b01c32f42$d2ee3780$db2f024b@mavpc> From: "Jihoon Lee" To: Subject: [manet] network partitioning Date: Tue, 10 Jun 2003 20:24:14 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" 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: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h5ABOjB10592 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi. I am a newcomer in MANET. Does anyone know if there are any solutions for ad hoc network partitioning ? I am starting with scalability of ad hoc network. To reduce flooding overhead or latency of route discovery, I am considering network partitioning. So any feedback and work around would be very useful. Thanks Jihoon Lee. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 10 10:36: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 KAA03314 for ; Tue, 10 Jun 2003 10:36:36 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5AEaBo26956 for manet-archive@odin.ietf.org; Tue, 10 Jun 2003 10:36: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 h5AEaBB26953 for ; Tue, 10 Jun 2003 10:36: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 KAA03306 for ; Tue, 10 Jun 2003 10:36:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PkCJ-0006wj-00 for manet-web-archive@ietf.org; Tue, 10 Jun 2003 10:34:04 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PkCJ-0006wg-00 for manet-web-archive@ietf.org; Tue, 10 Jun 2003 10:34: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 h5AEP6B26161; Tue, 10 Jun 2003 10:25:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AEIKB25812 for ; Tue, 10 Jun 2003 10:18: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 KAA02519 for ; Tue, 10 Jun 2003 10:18:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Pjv2-0006m7-00 for manet@ietf.org; Tue, 10 Jun 2003 10:16:12 -0400 Received: from angelo.kcl.ac.uk ([137.73.66.5]) by ietf-mx with esmtp (Exim 4.12) id 19Pjv2-0006m4-00 for manet@ietf.org; Tue, 10 Jun 2003 10:16:12 -0400 Received: from MONA (EE014.eee.kcl.ac.uk [137.73.10.115]) by angelo.kcl.ac.uk with ESMTP id h5AEHsJT026051 for ; Tue, 10 Jun 2003 15:17:54 +0100 (BST) Message-ID: <00bd01c32f5c$74eafdc0$730a4989@MONA> From: "Mona" To: Date: Tue, 10 Jun 2003 15:27:42 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BA_01C32F64.D5D1AFF0" 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-MailScanner: Found to be clean Subject: [manet] A question about DSDV Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_00BA_01C32F64.D5D1AFF0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, In DSDV to maintain the consistency of routing tables in a dynamically = varying topology, each station periodically transmits updates, and = transmits updates immediately when significant new information is = available. =20 My question is how dsdv measures a significant new information about = links? And what counts as a new information? Changes in a link capacity = or only when a link fails? Regards, Mona=20 ------=_NextPart_000_00BA_01C32F64.D5D1AFF0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi all,

In DSDV to maintain the consistency of routing tables = in a=20 dynamically varying topology, each station periodically transmits = updates, and=20 transmits updates immediately when significant new information = is=20 available.    

My question is how dsdv measures a = significant new=20 information about links? And what counts as a new information? = Changes=20 in a link capacity or only when a link fails?

Regards, = Mona 

------=_NextPart_000_00BA_01C32F64.D5D1AFF0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 10 12:26: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 MAA07723 for ; Tue, 10 Jun 2003 12:26:53 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5AGQRs05380 for manet-archive@odin.ietf.org; Tue, 10 Jun 2003 12:26: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 h5AGQQB05377 for ; Tue, 10 Jun 2003 12:26: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 MAA07711 for ; Tue, 10 Jun 2003 12:26:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Plv3-0000Aj-00 for manet-web-archive@ietf.org; Tue, 10 Jun 2003 12:24:21 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Plv2-0000Ag-00 for manet-web-archive@ietf.org; Tue, 10 Jun 2003 12:24: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 h5AGE8B04470; Tue, 10 Jun 2003 12:14: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 h5AG72B02872 for ; Tue, 10 Jun 2003 12:07: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 MAA06953 for ; Tue, 10 Jun 2003 12:06:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PlcH-0007l1-00 for manet@ietf.org; Tue, 10 Jun 2003 12:04:57 -0400 Received: from law14-f109.law14.hotmail.com ([64.4.21.109] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19PlcG-0007kV-00 for manet@ietf.org; Tue, 10 Jun 2003 12:04:57 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 10 Jun 2003 09:06:24 -0700 Received: from 193.61.167.150 by lw14fd.law14.hotmail.msn.com with HTTP; Tue, 10 Jun 2003 16:06:24 GMT X-Originating-IP: [193.61.167.150] X-Originating-Email: [bilalmomani@hotmail.com] From: "Bilal Al Momani" To: manet@ietf.org Date: Tue, 10 Jun 2003 19:06:24 +0300 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 10 Jun 2003 16:06:24.0974 (UTC) FILETIME=[3E001EE0:01C32F6A] Subject: [manet] Research Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Dear friends What issues shoudl we take into consideration when researching about the Dynamic addressing for the Future Ad hoc ? ...Ensuring to support the QoS. Looking forward to hearing from you soon All the Best Bill _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 10 19:09: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 TAA22242 for ; Tue, 10 Jun 2003 19:09:16 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5AN8sX03207 for manet-archive@odin.ietf.org; Tue, 10 Jun 2003 19: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 h5AN8sB03204 for ; Tue, 10 Jun 2003 19:08: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 TAA22230 for ; Tue, 10 Jun 2003 19:08:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PsCS-0002wm-00 for manet-web-archive@ietf.org; Tue, 10 Jun 2003 19:06:44 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19PsCS-0002wi-00 for manet-web-archive@ietf.org; Tue, 10 Jun 2003 19:06: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 h5AMvfB01787; Tue, 10 Jun 2003 18:57:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5AMo8B01564 for ; Tue, 10 Jun 2003 18:50: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 SAA21844 for ; Tue, 10 Jun 2003 18:50:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19PruJ-0002q0-00 for manet@ietf.org; Tue, 10 Jun 2003 18:47:59 -0400 Received: from mail03.gmu.edu ([129.174.0.113]) by ietf-mx with esmtp (Exim 4.12) id 19PruI-0002px-00 for manet@ietf.org; Tue, 10 Jun 2003 18:47:58 -0400 Received: from Isovaio002 ([65.213.193.21]) by mserver3.gmu.edu (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTPA id <0HGA00MTEFFD8Q@mserver3.gmu.edu> for manet@ietf.org; Tue, 10 Jun 2003 18:50:02 -0400 (EDT) Date: Tue, 10 Jun 2003 18:49:55 -0400 From: Ali Nabi Zadeh To: manet@ietf.org Reply-to: anabizad@gmu.edu Message-id: <006e01c32fa2$9ce9c7c0$15c1d541@Isovaio002> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Mailer: Microsoft Outlook, Build 10.0.2627 Content-type: multipart/alternative; boundary="Boundary_(ID_/MsnzJHv2Wc8vA6amMDKqw)" Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Subject: [manet] Internetworking 2003 San Jose CA, June 22-24, Call For Participation Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --Boundary_(ID_/MsnzJHv2Wc8vA6amMDKqw) Content-type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7BIT Apologies if you receive multiple copies of this Call-For-Participation. Sincerely, Ali Nabi Zadeh. ======================================= Internetworking 2003 International Conference Hilton San Jose & Towers Hotel, California June 22-June 24, 2003 ======================================= http://www.caitr.org/internetworking03/index.htm ======================================= You are cordially invited to attend the Internetworking 2003 International Conference to be held in San Jose, California, June 22-24, 2003. The 3-day event consists of two-days of highly technical sessions, preceded by four technical tutorials. Registration for the conference is underway - online registration is now available. The early registration discounts are extremely attractive and are valid till June 15, 2003. To register, visit: http://www.caitr.org/internetworking03/registration.htm Important Dates: --------------------- - Early Registration Rates Cut-Off Date: June 15 - Tutorials: June 22, 8:15 am-5:45 pm - Conference sessions: June 23-24, 8:30am-6:00pm Program: ------------- (visit http://www.caitr.org/internetworking03/program.htm for abstracts and speaker details) Sunday June 22 Tutorial-1: MPLS VPNs Tutorial-2: IPv6 Tutorial-3: Mobile Wireless Internet Architecture and Protocols Tutorial-4: Voice over Packet Monday June 23 Welcome and Keynote Session: Network Technology Trends - Forwarding Element and Control Separation - Evolution of Inter-Domain Routing - Network Processing Building Blocks: Enabling the Routers of the Future Session: Network Architecture - An architecture for IPv6 VPNs and IPv6 transport over MPLS/GMPLS multiservice backbones IPv6 - A new routing architecture: Atomised Routing - Internetworking MPLS Layer 2 Transport with an IP Services Network Session: Storage Area Networks - Storage as a Network Node - Object-Based Storage - Design, Implementation, and P ! erformance Analysis of the iSCS Protocol for SCSI over TCP/IP - SANs Considerations Session: Mobile & Wireless Networks - CertBU: Certificate-based Techniques for Securing Mobile IPv6 Binding Updates IPv6 - Challenges and Roadmap of UMTS Network Deployment - Inter-working Mobile IPv6 with IP Multimedia Subsystem in UMTS - Mobile Authentication and QoS - Mobile Handoff Technologies Tuesday June 24 Session: Inter-Domain Routing - Optimizing Route Convergence - Traceroute and BGP AS Path Incongruities - Domain Constrained Multicast: A New Approach for IP Multicast Routing Session: Applications & Services - Securing the Web with Next Generation Encryption Technologies - Impact of the live radio on the Internet, and the real-time streaming audio, in the ComUNITY cable system from Com21 - A novel EAC semantic for the RTSP protocol - Towards an end-to-end architecture integrating new Transport and IP services in a DiffServ Internet Session: Network Management & Planning - Pseudowire OAM: A Mandatory Yet ! Often Overlooked Feature BR> - A Multicommodity Flow Formulation for the MPLS Layout Design: Reduced Complexity Layout and Minimum Relayout Probems - Design Of Fast Fault Restoration System For WDM Networks - Cross-domain multimedia service provisioning, the EVOLUTE solution Session: QoS Based Routing - QoS Routing in Networks with Non-Deterministic Information - Active Dynamic Routing - QoS routing for Differentiated Services: simulations and prototype experiments - Probabilistic routing for QoS improvement in GPS networks - Fluid flow network modeling for hop-by-hop feedback control design and analysis We look forward to seeing you at the Conference. Regards, Conference Technical Co-chairs : - Dr. Maurice Gagnaire, ENST, France - Daniel Awduche Technical Program Committee of the Internetworking 2003 Conference: - Roberto Sabella, Erisson - Dr. Moshe Zukerman, Univ. of Melbourne - Nada Golmie, NIST - Dr. Guy Pujolle, LIP6, France - Dr. Samir Tohme, ENST, France - Stefano Trumpy, Italian National Research Council - Dr. Ibrahim Habib, City Univ. of NY - Dr. Marc Lobelle, UCL University, Belgium - Dr. Parviz Yegani, Cisco Systems - Dr. G.S. Kuo - Dr. Abbas Jamalipour, Univ. of Sydney - Dr. Hussein Mouftah, Univ. of Ottawa - James Kempf - Elizabeth Rodriguez - Dr. Ferit Yegenoglu, Isocore - Dr. Ali Zadeh, George Mason University - Dr. Tony Przygienda, Xebeo - Ran Canetti, IBM --Boundary_(ID_/MsnzJHv2Wc8vA6amMDKqw) Content-type: text/html; charset=us-ascii Content-Transfer-Encoding: 7BIT Message

Apologies if you receive multiple copies of this Call-For-Participation.

Sincerely,

Ali Nabi Zadeh.


 =======================================
     Internetworking 2003 International Conference
     Hilton San Jose & Towers Hotel, California
              June 22-June 24, 2003
=======================================
    http://www.caitr.org/internetworking03/index.htm
=======================================
 
You are cordially invited to attend the Internetworking 2003 International Conference to be held in San Jose, California, June 22-24, 2003. The 3-day event consists of two-days of highly technical sessions, preceded by four technical tutorials.
 
Registration for the conference is underway - online registration is now available. The early registration discounts are extremely attractive and are valid till June 15, 2003. To register, visit:
 
Important Dates:
---------------------
- Early Registration Rates Cut-Off Date: June 15
- Tutorials: June 22, 8:15 am-5:45 pm
- Conference sessions: June 23-24, 8:30am-6:00pm
 
Program:
-------------
(visit http://www.caitr.org/internetworking03/program.htm for abstracts and speaker details)
 
Sunday June 22
    Tutorial-1: MPLS VPNs 
    Tutorial-2: IPv6 
    Tutorial-3: Mobile Wireless Internet Architecture and Protocols
    Tutorial-4: Voice over Packet 
Monday June 23
    Welcome and Keynote 
    Session: Network Technology Trends
      - Forwarding Element and Control Separation
      - Evolution of Inter-Domain Routing
      - Network Processing Building Blocks: Enabling the Routers of the Future
    Session: Network Architecture
      - An architecture for IPv6 VPNs and IPv6 transport over MPLS/GMPLS multiservice backbones IPv6
      - A new routing architecture: Atomised Routing
      - Internetworking MPLS Layer 2 Transport with an IP Services Network
    Session: Storage Area Networks
      - Storage as a Network Node
      - Object-Based Storage
      - Design, Implementation, and P ! erformance Analysis of the iSCS Protocol for SCSI over TCP/IP
      - SANs Considerations
 
    Session: Mobile & Wireless Networks
      - CertBU: Certificate-based Techniques for Securing Mobile IPv6 Binding Updates IPv6
      - Challenges and Roadmap of UMTS Network Deployment
      - Inter-working Mobile IPv6 with IP Multimedia Subsystem in UMTS 
      - Mobile Authentication and QoS 
      - Mobile Handoff Technologies 
 
Tuesday June 24
    Session: Inter-Domain Routing
      - Optimizing Route Convergence
      - Traceroute and BGP AS Path Incongruities 
      - Domain Constrained Multicast: A New Approach for IP Multicast Routing
 
    Session: Applications & Services
     -  Securing the Web with Next Generation Encryption Technologies
     - Impact of the live radio on the Internet, and the real-time streaming audio, in the ComUNITY cable system from Com21
     - A novel EAC semantic for the RTSP protocol
     - Towards an end-to-end architecture integrating new Transport and IP services in a DiffServ Internet
 
    Session: Network Management & Planning
     -  Pseudowire OAM: A Mandatory Yet ! Often Overlooked Feature  BR>     - A Multicommodity Flow Formulation for the MPLS Layout Design: Reduced Complexity Layout and Minimum Relayout Probems
     - Design Of Fast Fault Restoration System For WDM Networks
     - Cross-domain multimedia service provisioning, the EVOLUTE solution
 
    Session: QoS Based Routing
     - QoS Routing in Networks with Non-Deterministic Information
     - Active Dynamic Routing
     - QoS routing for Differentiated Services: simulations and prototype experiments
     - Probabilistic routing for QoS improvement in GPS networks
     - Fluid flow network modeling for hop-by-hop feedback control design and analysis
 
We look forward to seeing you at the Conference.
Regards,
 Conference Technical Co-chairs :
 - Dr. Maurice Gagnaire, ENST, France
 - Daniel Awduche
 Technical Program Committee of the Internetworking 2003 Conference:
 - Roberto Sabella, Erisson
 - Dr. Moshe Zukerman, Univ. of Melbourne
 - Nada Golmie, NIST
 - Dr. Guy Pujolle, LIP6, France
 - Dr. Samir Tohme, ENST, France
 - Stefano Trumpy, Italian National Research Council
 - Dr. Ibrahim Habib, City Univ. of NY
 - Dr. Marc Lobelle, UCL University, Belgium
 - Dr. Parviz Yegani, Cisco Systems
 - Dr. G.S. Kuo
 - Dr. Abbas Jamalipour, Univ. of Sydney
 - Dr. Hussein Mouftah, Univ. of Ottawa
 - James Kempf
 - Elizabeth Rodriguez
 - Dr. Ferit Yegenoglu, Isocore
 - Dr. Ali Zadeh, George Mason University
 - Dr. Tony Przygienda, Xebeo
 - Ran Canetti, IBM
--Boundary_(ID_/MsnzJHv2Wc8vA6amMDKqw)-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 11 06:05:32 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 GAA01223 for ; Wed, 11 Jun 2003 06:05:32 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5BA58p24644 for manet-archive@odin.ietf.org; Wed, 11 Jun 2003 06:05: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 h5BA58B24641 for ; Wed, 11 Jun 2003 06:05: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 GAA01209 for ; Wed, 11 Jun 2003 06:05:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Q2RX-0006Hw-00 for manet-web-archive@ietf.org; Wed, 11 Jun 2003 06:02:59 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Q2RW-0006Ht-00 for manet-web-archive@ietf.org; Wed, 11 Jun 2003 06:02: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 h5B9dVB23492; Wed, 11 Jun 2003 05:39: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 h5B9YOB22424 for ; Wed, 11 Jun 2003 05:34: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 FAA00540 for ; Wed, 11 Jun 2003 05:34:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Q1xo-00067i-00 for manet@ietf.org; Wed, 11 Jun 2003 05:32:16 -0400 Received: from [202.108.44.206] (helo=sm206.163.com) by ietf-mx with esmtp (Exim 4.12) id 19Q1xk-00067Q-00 for manet@ietf.org; Wed, 11 Jun 2003 05:32:16 -0400 Received: from localhost (localhost [127.0.0.1]) by sm206.163.com (Postfix) with SMTP id 1F4111D770B6A for ; Wed, 11 Jun 2003 17:34:03 +0800 (CST) Received: from RavProxy (unknown [61.187.64.195]) by 192.168.1.206 (Coremail:www.163.com) with SMTP id CncBAIn35j7WAEDD.1 for ; Wed, 11 Jun 2003 17:34:03 +0800 (CST) Message-ID: <000d01c32ffc$97633070$7600a8c0@zyn> From: "Zhang Yanan" To: References: <006e01c32fa2$9ce9c7c0$15c1d541@Isovaio002> Date: Wed, 11 Jun 2003 17:33:53 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01C3303F.A0E30010" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [manet] simulating WatchDog Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_0008_01C3303F.A0E30010 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 TWVzc2FnZURlYXIgZnJpZW5kLA0KDQpJJ20gc2ltdWxhdGluZyB0aGUgV2F0Y2hEb2cgUHJvY2Vz cyhzZWUgYXMgIk1pdGlnYXRpbmcgUm91dGluZyBNaXNiZWhhdmlvciBpbiBNb2JpbGUgQWQgSG9j IE5ldHdvcmtzIikgb24gRFNSIHVzaW5nIEdsb21vc2ltLCBidXQgSSBtZWV0IHNvbWUgcHJvYmxl bXMuIA0KDQpJIGRvbid0IGtub3cgd2hpY2ggcGFydCBwcm9jZXNzIHRoZSBQUk9NSVNDVU9VU0xZ IExJU1RFTklORywgYW5kIGhvdyB0byBsaXN0ZW5pbmcgbmVpZ2hib3IncyBiZWhhdmlvci4gDQoN CndoZXRoZXIgdGhlICJ2b2lkIFJvdXRpbmdEc3JQZWVrRnVuY3Rpb24iIGRvIHRoaXMgPyBIb3cg aXQgd29ya3M/IElzIHRoZXJlIGFueW9uZSBjYW4gaGVscCBtZT8NCg0KDQpUaGFua3MNCg0KWW91 cnMNCg0KWmhhbmcNCg== ------=_NextPart_000_0008_01C3303F.A0E30010 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPjxUSVRMRT5NZXNzYWdlPC9USVRMRT4NCjxNRVRBIGh0dHAtZXF1 aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD1pc28tODg1OS0xIj4N CjxNRVRBIGNvbnRlbnQ9Ik1TSFRNTCA2LjAwLjI2MDAuMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZ TEU+PC9TVFlMRT4NCjwvSEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQg ZmFjZT1BcmlhbCBzaXplPTI+RGVhciBmcmllbmQsPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBm YWNlPUFyaWFsIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9QXJp YWwgc2l6ZT0yPkknbSBzaW11bGF0aW5nIHRoZSBXYXRjaERvZyBQcm9jZXNzKHNlZSBhcyANCjxF TT4iTWl0aWdhdGluZyBSb3V0aW5nIE1pc2JlaGF2aW9yIGluIE1vYmlsZSBBZCBIb2MgTmV0d29y a3MiPC9FTT4pIG9uIERTUiANCnVzaW5nIEdsb21vc2ltLCBidXQgSSBtZWV0IHNvbWUgcHJvYmxl bXMuIDwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PC9GT05UPiZu YnNwOzwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj5JIGRvbid0IGtub3cgd2hp Y2ggcGFydCBwcm9jZXNzIHRoZSBQUk9NSVNDVU9VU0xZIA0KTElTVEVOSU5HLCBhbmQgaG93IHRv IGxpc3RlbmluZyBuZWlnaGJvcidzIGJlaGF2aW9yLiA8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05U IGZhY2U9QXJpYWwgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1B cmlhbCBzaXplPTI+d2hldGhlciB0aGUgInZvaWQgUm91dGluZ0RzclBlZWtGdW5jdGlvbiIgZG8g dGhpcyA/IA0KSG93IGl0IHdvcmtzPyBJcyB0aGVyZSBhbnlvbmUgY2FuIGhlbHAgbWU/PC9GT05U PjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+ DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+ PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+VGhhbmtzPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBm YWNlPUFyaWFsIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9QXJp YWwgc2l6ZT0yPllvdXJzPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9 Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPlpoYW5n PC9GT05UPjwvRElWPjwvQk9EWT48L0hUTUw+DQo= ------=_NextPart_000_0008_01C3303F.A0E30010-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 11 11:14:41 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 LAA13036 for ; Wed, 11 Jun 2003 11:14:41 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5BFEDf07145 for manet-archive@odin.ietf.org; Wed, 11 Jun 2003 11:14: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 h5BFEDm07142 for ; Wed, 11 Jun 2003 11:14: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 LAA13014 for ; Wed, 11 Jun 2003 11:14:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Q7Gh-000139-00 for manet-web-archive@ietf.org; Wed, 11 Jun 2003 11:12:07 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Q7Gg-000135-00 for manet-web-archive@ietf.org; Wed, 11 Jun 2003 11:12: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 h5BDiDB08500; Wed, 11 Jun 2003 09:44: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 h5BDclB08259 for ; Wed, 11 Jun 2003 09:38: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 JAA08437 for ; Wed, 11 Jun 2003 09:38:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Q5mJ-0000HA-00 for manet@ietf.org; Wed, 11 Jun 2003 09:36:39 -0400 Received: from mailhost.cs.tamu.edu ([128.194.130.106] helo=cs.tamu.edu ident=0) by ietf-mx with esmtp (Exim 4.12) id 19Q5mI-0000H7-00 for manet@ietf.org; Wed, 11 Jun 2003 09:36:38 -0400 Received: from unix.cs.tamu.edu (unix [128.194.138.13]) by cs.tamu.edu (8.11.0/8.11.0) with ESMTP id h5BDcgg27375; Wed, 11 Jun 2003 08:38:42 -0500 (CDT) Received: from localhost (b0l4549@localhost) by unix.cs.tamu.edu (8.10.2+Sun/8.10.2) with ESMTP id h5BDcgS01045; Wed, 11 Jun 2003 08:38:42 -0500 (CDT) X-Authentication-Warning: unix.cs.tamu.edu: b0l4549 owned process doing -bs Date: Wed, 11 Jun 2003 08:38:41 -0500 (CDT) From: Bin Lu To: Zhang Yanan cc: manet@ietf.org Subject: Re: [manet] simulating WatchDog In-Reply-To: <000d01c32ffc$97633070$7600a8c0@zyn> 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: , I'm sorry I don't know how to solve your problem. But I'm very interested in your simulation. Is it possible for you to make it available to us when you are finished? Thanks a million! Best regards, Bin Lu On Wed, 11 Jun 2003, Zhang Yanan wrote: > MessageDear friend, > > I'm simulating the WatchDog Process(see as "Mitigating Routing Misbehavior in Mobile Ad Hoc Networks") on DSR using Glomosim, but I meet some problems. > > I don't know which part process the PROMISCUOUSLY LISTENING, and how to listening neighbor's behavior. > > whether the "void RoutingDsrPeekFunction" do this ? How it works? Is there anyone can help me? > > > Thanks > > Yours > > Zhang > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 11 14:02: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 OAA19645 for ; Wed, 11 Jun 2003 14:02:55 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5BI2St21022 for manet-archive@odin.ietf.org; Wed, 11 Jun 2003 14:02: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 h5BI2Rm21019 for ; Wed, 11 Jun 2003 14:02: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 OAA19631 for ; Wed, 11 Jun 2003 14:02:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Q9tU-0002Ho-00 for manet-web-archive@ietf.org; Wed, 11 Jun 2003 14:00:20 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Q9tT-0002Hk-00 for manet-web-archive@ietf.org; Wed, 11 Jun 2003 14:00:19 -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 h5BHjum20058; Wed, 11 Jun 2003 13:45:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5BHQdm18442 for ; Wed, 11 Jun 2003 13:26: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 NAA18160 for ; Wed, 11 Jun 2003 13:26:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Q9Kp-0001zC-00 for manet@ietf.org; Wed, 11 Jun 2003 13:24:31 -0400 Received: from letters.cs.ucsb.edu ([128.111.41.13]) by ietf-mx with esmtp (Exim 4.12) id 19Q9Ko-0001z7-00 for manet@ietf.org; Wed, 11 Jun 2003 13:24:30 -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 h5BHQY508162; Wed, 11 Jun 2003 10:26:34 -0700 (PDT) From: Elizabeth Belding-Royer To: manet@ietf.org, aodvimpl-public@lists.sourceforge.net Content-Type: text/plain Message-Id: <1055352392.14490.34.camel@yosemite.cs.ucsb.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 11 Jun 2003 10:26:32 -0700 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] AODV Draft v13 Glomosim Code Release Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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, We are pleased to announce updated Glomosim code that is compliant with AODV draft version 13 (approved for Experimental RFC). If you are currently modeling AODV in Glomosim, please replace the AODV code included with the Glomosim package with this updated code. Hopefully this code will incorporated into the next Glomosim release. Thanks to Vrishali Wagle for updating the AODV code. http://moment.cs.ucsb.edu/AODV/ Go to simulation code, and you can find the tarball there. Elizabeth _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 11 17:58: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 RAA05024 for ; Wed, 11 Jun 2003 17:58:27 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5BLw1709325 for manet-archive@odin.ietf.org; Wed, 11 Jun 2003 17:58: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 h5BLw1m09322 for ; Wed, 11 Jun 2003 17:58: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 RAA04992 for ; Wed, 11 Jun 2003 17:57:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QDZR-0004PD-00 for manet-web-archive@ietf.org; Wed, 11 Jun 2003 17:55:53 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QDZR-0004PA-00 for manet-web-archive@ietf.org; Wed, 11 Jun 2003 17:55: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 h5BLajm07262; Wed, 11 Jun 2003 17:36:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5BLSfm06983 for ; Wed, 11 Jun 2003 17: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 RAA03932 for ; Wed, 11 Jun 2003 17:28:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QD74-00048O-00 for manet@ietf.org; Wed, 11 Jun 2003 17:26:34 -0400 Received: from clavin.cs.tamu.edu ([128.194.130.106] helo=cs.tamu.edu ident=0) by ietf-mx with esmtp (Exim 4.12) id 19QD73-00048L-00 for manet@ietf.org; Wed, 11 Jun 2003 17:26:33 -0400 Received: from dogbert.cs.tamu.edu (IDENT:4054@dogbert [128.194.130.18]) by cs.tamu.edu (8.11.0/8.11.0) with ESMTP id h5BLSNg25096 for ; Wed, 11 Jun 2003 16:28:33 -0500 (CDT) Received: from localhost (b0l4549@localhost) by dogbert.cs.tamu.edu (8.11.0/8.11.0) with ESMTP id h5BLSMj17879 for ; Wed, 11 Jun 2003 16:28:22 -0500 (CDT) X-Authentication-Warning: dogbert.cs.tamu.edu: b0l4549 owned process doing -bs Date: Wed, 11 Jun 2003 16:28:22 -0500 (CDT) From: Bin Lu X-Sender: b0l4549@dogbert To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] bandwidth reservation 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: , I apologize if this is not the appropriate place for this topic, but I posted a message on NS-2 mailing list and got no reply. I'm trying to simulate bandwidth reservation in ad hoc networks using ns-2 but can't figure out how to do it. Is there anybody who has done this or included this kind of work in your simulation? I'd appreciate it very much if you could give me a hint how to do it!! Thanks, Bin Lu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Wed Jun 11 18:25: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 SAA07107 for ; Wed, 11 Jun 2003 18:25:13 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5BMOlS11695 for manet-archive@odin.ietf.org; Wed, 11 Jun 2003 18:24: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 h5BMOkm11692 for ; Wed, 11 Jun 2003 18:24: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 SAA07063 for ; Wed, 11 Jun 2003 18:24:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QDzL-0004fR-00 for manet-web-archive@ietf.org; Wed, 11 Jun 2003 18:22:39 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QDzK-0004fO-00 for manet-web-archive@ietf.org; Wed, 11 Jun 2003 18:22: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 h5BMFGm10919; Wed, 11 Jun 2003 18:15: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 h5BM7Sm10426 for ; Wed, 11 Jun 2003 18:07: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 SAA05668 for ; Wed, 11 Jun 2003 18:07:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QDia-0004SN-00 for manet@ietf.org; Wed, 11 Jun 2003 18:05:20 -0400 Received: from clavin.cs.tamu.edu ([128.194.130.106] helo=cs.tamu.edu ident=0) by ietf-mx with esmtp (Exim 4.12) id 19QDiZ-0004SK-00 for manet@ietf.org; Wed, 11 Jun 2003 18:05:19 -0400 Received: from dogbert.cs.tamu.edu (IDENT:4054@dogbert [128.194.130.18]) by cs.tamu.edu (8.11.0/8.11.0) with ESMTP id h5BM7Ng28051 for ; Wed, 11 Jun 2003 17:07:23 -0500 (CDT) Received: from localhost (b0l4549@localhost) by dogbert.cs.tamu.edu (8.11.0/8.11.0) with ESMTP id h5BM7NF19970 for ; Wed, 11 Jun 2003 17:07:23 -0500 (CDT) X-Authentication-Warning: dogbert.cs.tamu.edu: b0l4549 owned process doing -bs Date: Wed, 11 Jun 2003 17:07:22 -0500 (CDT) From: Bin Lu X-Sender: b0l4549@dogbert To: manet@ietf.org Subject: Re: [manet] bandwidth reservation simulation 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: , I'd like to add to my previous message that: I'm not trying to simulate a QoS signaling system - but only a simple 'bandwidth allocation' mechanism. Say, I allocate 0.5M bandwidth to a flow, then this 0.5M will just be used by that flow, not by others. I looked at the insignia code but can't find this specific part. Any hint will be appreciated! Bin Lu On Wed, 11 Jun 2003, Bin Lu wrote: > > I apologize if this is not the appropriate place for this topic, but I > posted a message on NS-2 mailing list and got no reply. > > I'm trying to simulate bandwidth reservation in ad hoc networks using > ns-2 but can't figure out how to do it. Is there anybody who has done this > or included this kind of work in your simulation? I'd appreciate it very > much if you could give me a hint how to do it!! > > Thanks, > > Bin Lu > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 09:55: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 JAA10460 for ; Thu, 12 Jun 2003 09:55:48 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CDtLs23082 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 09:55: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 h5CDtLm23079 for ; Thu, 12 Jun 2003 09:55: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 JAA10443 for ; Thu, 12 Jun 2003 09:55:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QSVs-0002YB-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 09:53:12 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QSVr-0002Y8-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 09:53:11 -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 h5CDj4m22396; Thu, 12 Jun 2003 09:45: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 h5CDeAm22198 for ; Thu, 12 Jun 2003 09:40: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 JAA09984 for ; Thu, 12 Jun 2003 09:40:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QSHC-0002Pe-00 for manet@ietf.org; Thu, 12 Jun 2003 09:38:02 -0400 Received: from smtpproxy1.mitre.org ([192.160.51.75]) by ietf-mx with esmtp (Exim 4.12) id 19QSHB-0002Pa-00 for manet@ietf.org; Thu, 12 Jun 2003 09:38:01 -0400 Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.12.9/8.12.8) with ESMTP id h5CDe2n5005322 for ; Thu, 12 Jun 2003 09:40:02 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv1.mitre.org (8.12.9/8.12.8) with ESMTP id h5CDdwOJ016636 for ; Thu, 12 Jun 2003 09:39:58 -0400 (EDT) Received: from mailhubf.mitre.org (129.83.25.49) by mailhub2.mitre.org with SMTP id 2820362; Thu, 12 Jun 2003 09:39:49 -0400 Received: from jack.mitre.org (129.83.40.201) by mailhubf.mitre.org with SMTP id 734476; Thu, 12 Jun 2003 09:39:44 -0400 Date: Thu, 12 Jun 2003 09:39:43 -0400 Mime-Version: 1.0 (Apple Message framework v552) Content-Type: text/plain; charset=US-ASCII; format=flowed From: rpreston@mitre.org (Ralph Preston) To: manet@ietf.org Content-Transfer-Encoding: 7bit Message-Id: <53176C78-9CDB-11D7-A93C-0003937ADD80@mitre.org> X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [manet] Internet-MANET gateways? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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, An easy question, has it been defined how a MANET-Internet gateway will work? If it has, please point me to it and don't bother to read the rest of this message. :) I've been trying to figure out how a MANET gateway will interface with the Internet and enable nodes outside the MANET to initiate communication with nodes in the MANET. The way I see it there are three possibilities: 1) The gateway advertises routes to each node in the MANET to the entire Internet. 2) The gateway runs NAT. 3) Any node who wants to be reachable from outside the MANET must be running MobileIP and in IPv4 the gateway must be its Foreign Agent, or Home Agent. Number 1 isn't a good solution since nodes in the MANET wont necessarily be route aggregated. Solution 2 doesn't allow nodes outside the MANET to contact nodes within the MANET. Which leaves solution 3, but solution 3 wont work except for nodes that have a direct connection with the gateway. So, is there currently no way for outside nodes to contact MANET nodes? Ralph A. Preston The MITRE Corporation 202 Burlington Road MS E095 Bedford, MA 01730-1420 http://www.mitre.org _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 11:04:51 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 LAA14867 for ; Thu, 12 Jun 2003 11:04:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CF4PN29523 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 11:04: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 h5CF4Pm29520 for ; Thu, 12 Jun 2003 11:04: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 LAA14848 for ; Thu, 12 Jun 2003 11:04:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QTah-0003Gp-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 11:02:15 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QTag-0003Gm-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 11:02:14 -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 h5CEr7m28800; Thu, 12 Jun 2003 10:53:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CElYm28264 for ; Thu, 12 Jun 2003 10:47: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 KAA14223 for ; Thu, 12 Jun 2003 10:47:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QTKP-00038I-00 for manet@ietf.org; Thu, 12 Jun 2003 10:45:25 -0400 Received: from metatron.isr.umd.edu ([128.8.111.5] helo=isrmail.isr.umd.edu ident=mirapoint) by ietf-mx with esmtp (Exim 4.12) id 19QTKO-00038E-00 for manet@ietf.org; Thu, 12 Jun 2003 10:45:24 -0400 Received: from isr.umd.edu (doh.isr.umd.edu [128.8.140.151]) by isrmail.isr.umd.edu (Mirapoint Messaging Server MOS 3.3.5-GR) with ESMTP id AJO91349; Thu, 12 Jun 2003 10:47:26 -0400 (EDT) Message-ID: <3EE8927E.7000101@isr.umd.edu> Date: Thu, 12 Jun 2003 10:47:26 -0400 From: Manish Karir User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Subject: Re: [manet] Internet-MANET gateways? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit this is entirely an engineering issue, therefore a generic solution is not necessary. a network designer who deploys the network can and probably will solve the problem using method 1. unless you can make a really convincing argument why you have addresss in your MANET that can not be aggregated, I dont think there is a problem here...I dont think we can come up with generic solutions that handle every scenario. -manish Ralph Preston wrote: > Hello, > > An easy question, has it been defined how a MANET-Internet gateway will > work? If it has, please point me to it and don't bother to read the > rest of this message. :) > > I've been trying to figure out how a MANET gateway will interface with > the Internet and enable nodes outside the MANET to initiate > communication with nodes in the MANET. The way I see it there are three > possibilities: > > 1) The gateway advertises routes to each node in the MANET to the entire > Internet. > > 2) The gateway runs NAT. > > 3) Any node who wants to be reachable from outside the MANET must be > running MobileIP and in IPv4 the gateway must be its Foreign Agent, or > Home Agent. > > Number 1 isn't a good solution since nodes in the MANET wont necessarily > be route aggregated. Solution 2 doesn't allow nodes outside the MANET > to contact nodes within the MANET. Which leaves solution 3, but > solution 3 wont work except for nodes that have a direct connection with > the gateway. So, is there currently no way for outside nodes to contact > MANET nodes? > > Ralph A. Preston > The MITRE Corporation _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 12:06: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 MAA16992 for ; Thu, 12 Jun 2003 12:06:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CG6Pq02019 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 12:06: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 h5CG6Pm02015 for ; Thu, 12 Jun 2003 12:06: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 MAA16964 for ; Thu, 12 Jun 2003 12:06:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QUYj-0003ld-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 12:04:17 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QUYi-0003lZ-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 12:04:16 -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 h5CFrZm01338; Thu, 12 Jun 2003 11:53: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 h5CFVdm32139 for ; Thu, 12 Jun 2003 11:31: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 LAA16005 for ; Thu, 12 Jun 2003 11:31:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QU15-0003Wt-00 for manet@ietf.org; Thu, 12 Jun 2003 11:29:31 -0400 Received: from maile.telia.com ([194.22.190.16]) by ietf-mx with esmtp (Exim 4.12) id 19QU14-0003Wk-00 for manet@ietf.org; Thu, 12 Jun 2003 11:29:30 -0400 Received: from d1o1121.telia.com (d1o1121.telia.com [217.208.140.241]) by maile.telia.com (8.12.9/8.12.9) with ESMTP id h5CFVZHR001022; Thu, 12 Jun 2003 17:31:35 +0200 (CEST) X-Original-Recipient: manet@ietf.org Received: from h205n2fls35o1121.telia.com (h205n2fls35o1121.telia.com [217.211.83.205]) by d1o1121.telia.com (8.10.2/8.10.1) with ESMTP id h5CFVVr17015; Thu, 12 Jun 2003 17:31:35 +0200 (CEST) Subject: Re: [manet] Internet-MANET gateways? From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: Manish Karir Cc: manet@ietf.org In-Reply-To: <3EE8927E.7000101@isr.umd.edu> References: <3EE8927E.7000101@isr.umd.edu> Content-Type: text/plain Message-Id: <1055431886.4454.89.camel@replicator.hn.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 12 Jun 2003 17:31:26 +0200 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit On Thu, 2003-06-12 at 16:47, Manish Karir wrote: > this is entirely an engineering issue, therefore a generic solution is > not necessary. > I am not sure I agree here. There are unresolved issues that are related to have subnets are handled (if at all), gateway advertisement vs. node solicitations, etc. > a network designer who deploys the network can and probably will solve > the problem using method 1. > I believe gateway advertisements would make little sense in networks running on-demand protocols. I.e. why put a proactive scheme ontop of an on-demand routing algorithm? It would probably make more sense for on-demand protocols to discover gateways on-demand. > unless you can make a really convincing argument why you have addresss > in your MANET that can not be aggregated, I dont think there is a > problem here...I dont think we can come up with generic solutions that > handle every scenario. > Address/route aggregation in multi-hop ad hoc networks is inherently problematic. Either you make assumptions about how nodes are assigned addresses, i.e. it is mandated that nodes use a specific prefix in the network. This way it is easy to distinguish (ad hoc network) local packets from outbound packets (i.e. check the prefix). However, this will require specific solutions for address assignment in these networks (probably a centralized scheme). The more likely case, is that the ad hoc network is flat, i.e. nodes use any address. Internet connectivity is in this case provided through NAT. Here we have a whole range of problems related to have we forward outbound traffic. For example, for on-demand protocols it does not make since to use default route entries since nodes do not maintain routes to all nodes in the network. How will forwarding be solved in this case? How do we discover gateways? How do we switch gateways when necessary? My point is, that this is not necessarily only an engineering issue. Erik > -manish > > > Ralph Preston wrote: > > Hello, > > > > An easy question, has it been defined how a MANET-Internet gateway will > > work? If it has, please point me to it and don't bother to read the > > rest of this message. :) > > > > I've been trying to figure out how a MANET gateway will interface with > > the Internet and enable nodes outside the MANET to initiate > > communication with nodes in the MANET. The way I see it there are three > > possibilities: > > > > 1) The gateway advertises routes to each node in the MANET to the entire > > Internet. > > > > 2) The gateway runs NAT. > > > > 3) Any node who wants to be reachable from outside the MANET must be > > running MobileIP and in IPv4 the gateway must be its Foreign Agent, or > > Home Agent. > > > > Number 1 isn't a good solution since nodes in the MANET wont necessarily > > be route aggregated. Solution 2 doesn't allow nodes outside the MANET > > to contact nodes within the MANET. Which leaves solution 3, but > > solution 3 wont work except for nodes that have a direct connection with > > the gateway. So, is there currently no way for outside nodes to contact > > MANET nodes? > > > > Ralph A. Preston > > The MITRE Corporation > > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 12:20: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 MAA17394 for ; Thu, 12 Jun 2003 12:20:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CGKPc03579 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 12:20: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 h5CGKPm03576 for ; Thu, 12 Jun 2003 12:20: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 MAA17370 for ; Thu, 12 Jun 2003 12:20:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QUmG-0003t2-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 12:18:17 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QUmG-0003sz-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 12:18:16 -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 h5CG4Wm01793; Thu, 12 Jun 2003 12:04: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 h5CFVbm32135 for ; Thu, 12 Jun 2003 11:31: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 LAA16002 for ; Thu, 12 Jun 2003 11:31:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QU13-0003Wo-00 for manet@ietf.org; Thu, 12 Jun 2003 11:29:29 -0400 Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx with esmtp (Exim 4.12) id 19QU13-0003Wl-00 for manet@ietf.org; Thu, 12 Jun 2003 11:29:29 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id C08367B4BC; Thu, 12 Jun 2003 11:31:35 -0400 (EDT) Received: from magic.internet2.edu (aa106.internet2.edu [207.75.164.106]) by basie.internet2.edu (Postfix) with ESMTP id A47A27B49C; Thu, 12 Jun 2003 11:31:34 -0400 (EDT) Message-Id: <5.1.0.14.2.20030612112243.0162feb8@mail.internet2.edu> X-Sender: jzeeff@mail.internet2.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 12 Jun 2003 11:31:23 -0400 To: Manish Karir , manet@ietf.org From: Jon Zeeff Subject: Re: [manet] Internet-MANET gateways? In-Reply-To: <3EE8927E.7000101@isr.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS 0.3.12pre8 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Your MANET node can tunnel to a fixed node on the Internet and thus be reached via that fixed node. Ie, through tunneling and NAT you can have just about any connectivity. If you have a routable block of addresses, you could use these for your MANET nodes and have a gateway aggregate and announce these addresses. At 10:47 AM 6/12/2003 -0400, Manish Karir wrote: >this is entirely an engineering issue, therefore a generic solution is >not necessary. > >a network designer who deploys the network can and probably will solve >the problem using method 1. > >unless you can make a really convincing argument why you have addresss >in your MANET that can not be aggregated, I dont think there is a >problem here...I dont think we can come up with generic solutions that >handle every scenario. > >-manish > > >Ralph Preston wrote: > > Hello, > > > > An easy question, has it been defined how a MANET-Internet gateway will > > work? If it has, please point me to it and don't bother to read the > > rest of this message. :) > > > > I've been trying to figure out how a MANET gateway will interface with > > the Internet and enable nodes outside the MANET to initiate > > communication with nodes in the MANET. The way I see it there are three > > possibilities: > > > > 1) The gateway advertises routes to each node in the MANET to the entire > > Internet. > > > > 2) The gateway runs NAT. > > > > 3) Any node who wants to be reachable from outside the MANET must be > > running MobileIP and in IPv4 the gateway must be its Foreign Agent, or > > Home Agent. > > > > Number 1 isn't a good solution since nodes in the MANET wont necessarily > > be route aggregated. Solution 2 doesn't allow nodes outside the MANET > > to contact nodes within the MANET. Which leaves solution 3, but > > solution 3 wont work except for nodes that have a direct connection with > > the gateway. So, is there currently no way for outside nodes to contact > > MANET nodes? > > > > Ralph A. Preston > > The MITRE Corporation > > > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 13:15: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 NAA19220 for ; Thu, 12 Jun 2003 13:15:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CHFPC08631 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 13:15:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CHFPm08628 for ; Thu, 12 Jun 2003 13:15: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 NAA19174 for ; Thu, 12 Jun 2003 13:15:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QVdU-0004Jm-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 13:13:16 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QVdT-0004Jj-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 13: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 h5CGwRm06767; Thu, 12 Jun 2003 12:58:28 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CGcSm05647 for ; Thu, 12 Jun 2003 12:38: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 MAA17983 for ; Thu, 12 Jun 2003 12:38:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QV3k-000428-00 for manet@ietf.org; Thu, 12 Jun 2003 12:36:20 -0400 Received: from maile.telia.com ([194.22.190.16]) by ietf-mx with esmtp (Exim 4.12) id 19QV3j-00041z-00 for manet@ietf.org; Thu, 12 Jun 2003 12:36:19 -0400 Received: from d1o1121.telia.com (d1o1121.telia.com [217.208.140.241]) by maile.telia.com (8.12.9/8.12.9) with ESMTP id h5CGcOHR003341; Thu, 12 Jun 2003 18:38:24 +0200 (CEST) X-Original-Recipient: manet@ietf.org Received: from h205n2fls35o1121.telia.com (h205n2fls35o1121.telia.com [217.211.83.205]) by d1o1121.telia.com (8.10.2/8.10.1) with ESMTP id h5CGcOr05730; Thu, 12 Jun 2003 18:38:24 +0200 (CEST) Subject: Re: [manet] Internet-MANET gateways? From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: Manish Karir Cc: manet@ietf.org In-Reply-To: <3EE8A37C.8010300@isr.umd.edu> References: <3EE8927E.7000101@isr.umd.edu> <1055431886.4454.89.camel@replicator.hn.org> <3EE8A37C.8010300@isr.umd.edu> Content-Type: text/plain; charset=iso-8859-1 Message-Id: <1055435894.4454.108.camel@replicator.hn.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 12 Jun 2003 18:38:19 +0200 X-MIME-Autoconverted: from 8bit to quoted-printable by maile.telia.com id h5CGcOHR003341 X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5CGcSm05648 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 h5CGwRm06767 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5CHFPm08628 Content-Transfer-Encoding: 8bit On Thu, 2003-06-12 at 17:59, Manish Karir wrote: > Erik, > > I think we differ in our assumptions, I assume that we have a predefined > prefix that we use to allocate addresses to ad hoc nodes, you assume > that the ad hoc nodes can pick any address. Can I assume that there is no problem? ;-) I didn't assume one solution, but outlined what assumptions you can make, and the inherent problems with those solutions. In the case with predefined prefix, we seem to agree that address assignment/autoconfiguration is the problem. But I think this would be limited to just a subset of the ad hoc scenarios. For this solution you need an entity that decides on a prefix. This puts restrictions in the "ad-hocness" of ad hoc networking. > Sure, you can assume that, but why does your assumption make any more > sense than mine, why would you consider it "more likely"? > Besides your assumption creates more problems than it solves.:) > To my knowledge, it is commonly assumed (or allowed) that ad hoc networks are flat. If you for example study some drafts (e.g. AODV draft) and follow some of the discussions, you will find that this is the case. > I think the hard problem that has remained unsolved in MANETs is address > allocation/assignment. Clearly, a centralized approach is not > desirable, and clearly a distributed approach of picking random > addresses, is not scalable(birthday paradox). > So what do you propose? > I think the "more likely" case is the centralized address distribution > during deployment. The most scalable structure built to date the > Internet has followed this policy and I think that turned out "okay". :) > I thought that the whole idea of ad hoc was to not have structure? Erik > -manish > > > Erik Nordström wrote: > > > > > Address/route aggregation in multi-hop ad hoc networks is inherently > > problematic. > > > > Either you make assumptions about how nodes are assigned addresses, i.e. > > it is mandated that nodes use a specific prefix in the network. This way > > it is easy to distinguish (ad hoc network) local packets from outbound > > packets (i.e. check the prefix). However, this will require specific > > solutions for address assignment in these networks (probably a > > centralized scheme). > > > > The more likely case, is that the ad hoc network is flat, i.e. nodes use > > any address. Internet connectivity is in this case provided through NAT. > > Here we have a whole range of problems related to have we forward > > outbound traffic. For example, for on-demand protocols it does not make > > since to use default route entries since nodes do not maintain routes to > > all nodes in the network. How will forwarding be solved in this case? > > How do we discover gateways? How do we switch gateways when necessary? > > > > My point is, that this is not necessarily only an engineering issue. > > > > Erik _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 13:34: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 NAA20180 for ; Thu, 12 Jun 2003 13:34:41 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CHYDD09612 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 13:34: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 h5CHYDm09609 for ; Thu, 12 Jun 2003 13:34: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 NAA20156 for ; Thu, 12 Jun 2003 13:34:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QVvg-0004a2-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 13:32:04 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QVvg-0004Zz-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 13:32: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 h5CHNam09050; Thu, 12 Jun 2003 13:23: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 h5CGkEm06146 for ; Thu, 12 Jun 2003 12:46: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 MAA18180 for ; Thu, 12 Jun 2003 12:46:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QVBF-000451-00 for manet@ietf.org; Thu, 12 Jun 2003 12:44:05 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19QVBE-00044j-00 for manet@ietf.org; Thu, 12 Jun 2003 12:44: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 JAA19679; Thu, 12 Jun 2003 09:45:30 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h5CGjTR24265; Thu, 12 Jun 2003 09:45:29 -0700 X-mProtect: <200306121645> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.67, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdVyTzyO; Thu, 12 Jun 2003 09:45:28 PDT Message-ID: <3EE8AE85.8030404@iprg.nokia.com> Date: Thu, 12 Jun 2003 09:47:01 -0700 From: Fred Templin 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: Ralph Preston CC: manet@ietf.org Subject: Re: [manet] Internet-MANET gateways? References: <53176C78-9CDB-11D7-A93C-0003937ADD80@mitre.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Let's not forget also that IPv6 is coming online soon as a possible solution 4 alternative. Fred ftemplin@iprg.nokia.com Ralph Preston wrote: > Hello, > > An easy question, has it been defined how a MANET-Internet gateway > will work? If it has, please point me to it and don't bother to read > the rest of this message. :) > > I've been trying to figure out how a MANET gateway will interface with > the Internet and enable nodes outside the MANET to initiate > communication with nodes in the MANET. The way I see it there are > three possibilities: > > 1) The gateway advertises routes to each node in the MANET to the > entire Internet. > > 2) The gateway runs NAT. > > 3) Any node who wants to be reachable from outside the MANET must be > running MobileIP and in IPv4 the gateway must be its Foreign Agent, or > Home Agent. > > Number 1 isn't a good solution since nodes in the MANET wont > necessarily be route aggregated. Solution 2 doesn't allow nodes > outside the MANET to contact nodes within the MANET. Which leaves > solution 3, but solution 3 wont work except for nodes that have a > direct connection with the gateway. So, is there currently no way for > outside nodes to contact MANET nodes? > > Ralph A. Preston > The MITRE Corporation > 202 Burlington Road MS E095 > Bedford, MA 01730-1420 > http://www.mitre.org > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 13:47:07 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 NAA20758 for ; Thu, 12 Jun 2003 13:47:07 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CHkdY11357 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 13:46: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 h5CHkdm11354 for ; Thu, 12 Jun 2003 13:46: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 NAA20753 for ; Thu, 12 Jun 2003 13:46:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QW7h-0004lY-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 13:44:30 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QW7h-0004lV-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 13:44:29 -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 h5CHZgm09689; Thu, 12 Jun 2003 13:35:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CGmFm06329 for ; Thu, 12 Jun 2003 12:48:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18284 for ; Thu, 12 Jun 2003 12:48:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QVDC-00047G-00 for manet@ietf.org; Thu, 12 Jun 2003 12:46:06 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19QVDB-000472-00 for manet@ietf.org; Thu, 12 Jun 2003 12:46:05 -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 h5CGlbDi029130; Thu, 12 Jun 2003 12:47:37 -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 h5CGlWMF019549; Thu, 12 Jun 2003 12:47:37 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.1.1.32) with SMTP id M2003061212473610449 ; Thu, 12 Jun 2003 12:47:36 -0400 Message-Id: <5.1.1.5.2.20030612124409.014f6088@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Thu, 12 Jun 2003 12:47:28 -0400 To: rpreston@mitre.org (Ralph Preston), manet@ietf.org From: Joe Macker Subject: Re: [manet] Internet-MANET gateways? In-Reply-To: <53176C78-9CDB-11D7-A93C-0003937ADD80@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 09:39 AM 6/12/2003 -0400, Ralph Preston wrote: >Hello, > >An easy question, has it been defined how a MANET-Internet gateway will work? If it has, please point me to it and don't bother to read the rest of this message. :) > >I've been trying to figure out how a MANET gateway will interface with the Internet and enable nodes outside the MANET to initiate communication with nodes in the MANET. The way I see it there are three possibilities: > >1) The gateway advertises routes to each node in the MANET to the entire Internet. > >2) The gateway runs NAT. > >3) Any node who wants to be reachable from outside the MANET must be running MobileIP and in IPv4 the gateway must be its Foreign Agent, or Home Agent. > >Number 1 isn't a good solution since nodes in the MANET wont necessarily be route aggregated. Solution 2 doesn't allow nodes outside the MANET to contact nodes within the Why not? In many applications area aggregation is a quite natural address management approach and a prefix or set of prefixes takes care of things. In many cases, we also autoconfig locally and this is already working for both IPv4 and IPv6. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 18:37: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 SAA00272 for ; Thu, 12 Jun 2003 18:37:44 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CMbIm31115 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 18:37:18 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CMbIm31104 for ; Thu, 12 Jun 2003 18:37: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 SAA00231 for ; Thu, 12 Jun 2003 18:37:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qaey-0006ft-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 18:35:08 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qaex-0006fq-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 18:35: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 h5CHmAa11553; Thu, 12 Jun 2003 13:48: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 h5CHibm11212 for ; Thu, 12 Jun 2003 13:44: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 NAA20602 for ; Thu, 12 Jun 2003 13:44:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QW5k-0004hH-00 for manet@ietf.org; Thu, 12 Jun 2003 13:42:28 -0400 Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx with esmtp (Exim 4.12) id 19QW5j-0004hE-00 for manet@ietf.org; Thu, 12 Jun 2003 13:42:27 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 45DBB7B4C5; Thu, 12 Jun 2003 13:44:34 -0400 (EDT) Received: from magic.internet2.edu (aa106.internet2.edu [207.75.164.106]) by basie.internet2.edu (Postfix) with ESMTP id 3ADD87B4C2; Thu, 12 Jun 2003 13:44:33 -0400 (EDT) Message-Id: <5.1.0.14.2.20030612133221.027f7098@mail.internet2.edu> X-Sender: jzeeff@mail.internet2.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 12 Jun 2003 13:44:20 -0400 To: Erik =?iso-8859-1?Q?Nordstr=F6m?= , Manish Karir From: Jon Zeeff Subject: Re: [manet] Internet-MANET gateways? Cc: manet@ietf.org In-Reply-To: <1055435894.4454.108.camel@replicator.hn.org> References: <3EE8A37C.8010300@isr.umd.edu> <3EE8927E.7000101@isr.umd.edu> <1055431886.4454.89.camel@replicator.hn.org> <3EE8A37C.8010300@isr.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS 0.3.12pre8 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , One way is a central registry. There aren't many MANET users yet so there is an address for everyone. Just picking an address randomly would work if the routing protocols had mechanisms for detecting collisions. Perhaps a large number of additional bits serving as a signature would allow a node to detect that different systems are using the same ip address (and notify them to change). Or use IPV6 and don't worry about it. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 18:37: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 SAA00294 for ; Thu, 12 Jun 2003 18:37:59 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CMbXm31447 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 18:37: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 h5CMbXm31444 for ; Thu, 12 Jun 2003 18:37: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 SAA00238 for ; Thu, 12 Jun 2003 18:37:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QafD-0006g0-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 18:35:23 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QafC-0006fx-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 18:35: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 h5CJg3a19750; Thu, 12 Jun 2003 15:42: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 h5CJf4m19704 for ; Thu, 12 Jun 2003 15:41: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 PAA25030 for ; Thu, 12 Jun 2003 15:41:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QXuR-0005Wu-00 for manet@ietf.org; Thu, 12 Jun 2003 15:38:55 -0400 Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx with esmtp (Exim 4.12) id 19QXuR-0005Wr-00 for manet@ietf.org; Thu, 12 Jun 2003 15:38:55 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 3DBB07B4CA; Thu, 12 Jun 2003 15:41:02 -0400 (EDT) Received: from magic.internet2.edu (aa106.internet2.edu [207.75.164.106]) by basie.internet2.edu (Postfix) with ESMTP id 2552B7B4C5; Thu, 12 Jun 2003 15:41:01 -0400 (EDT) Message-Id: <5.1.0.14.2.20030612153625.027ade30@mail.internet2.edu> X-Sender: jzeeff@mail.internet2.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 12 Jun 2003 15:40:47 -0400 To: Joe Macker , rpreston@mitre.org (Ralph Preston), manet@ietf.org From: Jon Zeeff Subject: Re: [manet] Internet-MANET gateways? In-Reply-To: <5.1.1.5.2.20030612143009.01501810@pop.itd.nrl.navy.mil> References: <5.1.0.14.2.20030612135520.02790620@mail.internet2.edu> <5.1.1.5.2.20030612124409.014f6088@pop.itd.nrl.navy.mil> <53176C78-9CDB-11D7-A93C-0003937ADD80@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS 0.3.12pre8 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , > > >Some (most?) of the mesh routing protocols do not have a default route > concept. >If so, I disagree with your general observations. If I remember correctly, AODV and DSR don't. I didn't say all and OLSR is a good example of why not. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 19:53: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 TAA01828 for ; Thu, 12 Jun 2003 19:53:39 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5CNrAS02897 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 19:53: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 h5CNrAm02894 for ; Thu, 12 Jun 2003 19:53: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 TAA01825 for ; Thu, 12 Jun 2003 19:53:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QbqP-00076s-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 19:51:01 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QbqO-00076p-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 19:51: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 h5CI75a12821; Thu, 12 Jun 2003 14:07: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 h5CI6hm12677 for ; Thu, 12 Jun 2003 14:06:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21296 for ; Thu, 12 Jun 2003 14:06:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QWR7-0004v9-00 for manet@ietf.org; Thu, 12 Jun 2003 14:04:33 -0400 Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx with esmtp (Exim 4.12) id 19QWR7-0004v6-00 for manet@ietf.org; Thu, 12 Jun 2003 14:04:33 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 441897B4C7; Thu, 12 Jun 2003 14:06:40 -0400 (EDT) Received: from magic.internet2.edu (aa106.internet2.edu [207.75.164.106]) by basie.internet2.edu (Postfix) with ESMTP id 2A91D7B4C5; Thu, 12 Jun 2003 14:06:39 -0400 (EDT) Message-Id: <5.1.0.14.2.20030612135520.02790620@mail.internet2.edu> X-Sender: jzeeff@mail.internet2.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 12 Jun 2003 14:06:25 -0400 To: Joe Macker , rpreston@mitre.org (Ralph Preston), manet@ietf.org From: Jon Zeeff Subject: Re: [manet] Internet-MANET gateways? In-Reply-To: <5.1.1.5.2.20030612124409.014f6088@pop.itd.nrl.navy.mil> References: <53176C78-9CDB-11D7-A93C-0003937ADD80@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS 0.3.12pre8 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Some (most?) of the mesh routing protocols do not have a default route concept. This is unfortunate since it means that if you are using a mesh network to access another network (say the Internet), you have to do route discovery for every single ip address you connect to. Would be more efficient if one could supply a mask with a route (and more specific routes override less specific ones). In general, mesh routing protocols are deficient in: 1) security 2) use of metrics other than hop count 3) multipath support 4) communicating routes for more than a single ip address 5) address assignment mechanisms _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 20:38: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 UAA02919 for ; Thu, 12 Jun 2003 20:38:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D0brq06422 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 20:37:53 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D0brm06416 for ; Thu, 12 Jun 2003 20:37: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 UAA02906 for ; Thu, 12 Jun 2003 20:37:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QcXg-0007P0-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 20:35:44 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QcXf-0007Ox-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 20:35: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 h5CI23a12451; Thu, 12 Jun 2003 14:02: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 h5CI1om12433 for ; Thu, 12 Jun 2003 14:01: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 OAA21116 for ; Thu, 12 Jun 2003 14:01:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QWMP-0004ru-00 for manet@ietf.org; Thu, 12 Jun 2003 13:59:41 -0400 Received: from isrmail.isr.umd.edu ([128.8.111.5] ident=mirapoint) by ietf-mx with esmtp (Exim 4.12) id 19QWMO-0004rr-00 for manet@ietf.org; Thu, 12 Jun 2003 13:59:40 -0400 Received: from isr.umd.edu (doh.isr.umd.edu [128.8.140.151]) by isrmail.isr.umd.edu (Mirapoint Messaging Server MOS 3.3.5-GR) with ESMTP id AJO92584; Thu, 12 Jun 2003 14:01:46 -0400 (EDT) Message-ID: <3EE8C00A.70208@isr.umd.edu> Date: Thu, 12 Jun 2003 14:01:46 -0400 From: Manish Karir User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jon Zeeff , manet@ietf.org Subject: Re: [manet] Internet-MANET gateways? References: <3EE8A37C.8010300@isr.umd.edu> <3EE8927E.7000101@isr.umd.edu> <1055431886.4454.89.camel@replicator.hn.org> <3EE8A37C.8010300@isr.umd.edu> <5.1.0.14.2.20030612133221.027f7098@mail.internet2.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit the random address picking will not work, to get an idea of the problem try the following in C or matlab: pick a 3x3 array. Try to fill this array with random numbers between 1-16(4-bit address space). Check for any duplicates, if you have duplicates, try again. Count how many rounds it takes to end up with all unique numbers. and this is only for a 9 node network!. Actually, some simple analysis would show the same result. -manish karir Jon Zeeff wrote: > > One way is a central registry. There aren't many MANET users yet so > there is an address for > everyone. > > Just picking an address randomly would work if the routing protocols had > mechanisms for > detecting collisions. Perhaps a large number of additional bits serving > as a signature would allow > a node to detect that different systems are using the same ip address > (and notify them to > change). > > Or use IPV6 and don't worry about it. > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 21:36: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 VAA04025 for ; Thu, 12 Jun 2003 21:36:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D1a4c09602 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 21:36: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 h5D1a3m09599 for ; Thu, 12 Jun 2003 21:36: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 VAA04012 for ; Thu, 12 Jun 2003 21:36:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QdRy-0007l2-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 21:33:54 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QdRx-0007kz-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 21:33: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 h5CJL4a18206; Thu, 12 Jun 2003 15:21: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 h5CJKnm18178 for ; Thu, 12 Jun 2003 15: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 PAA24679 for ; Thu, 12 Jun 2003 15:20:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QXaq-0005S7-00 for manet@ietf.org; Thu, 12 Jun 2003 15:18:40 -0400 Received: from smtpproxy1.mitre.org ([192.160.51.75]) by ietf-mx with esmtp (Exim 4.12) id 19QXaq-0005S4-00 for manet@ietf.org; Thu, 12 Jun 2003 15:18:40 -0400 Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.12.9/8.12.8) with ESMTP id h5CJKln5008883; Thu, 12 Jun 2003 15:20:47 -0400 (EDT) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtpsrv1.mitre.org (8.12.9/8.12.8) with ESMTP id h5CJKjOJ026061; Thu, 12 Jun 2003 15:20:45 -0400 (EDT) Received: from mailhubf.mitre.org (129.83.25.49) by mailhub2.mitre.org with SMTP id 2831203; Thu, 12 Jun 2003 15:20:37 -0400 Received: from jack.mitre.org (129.83.40.201) by mailhubf.mitre.org with SMTP id 734665; Thu, 12 Jun 2003 15:20:33 -0400 Date: Thu, 12 Jun 2003 15:20:32 -0400 Subject: Re: [manet] Internet-MANET gateways? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) cc: manet@ietf.org To: charliep@iprg.nokia.com (Charlie Perkins) From: rpreston@mitre.org (Ralph Preston) In-Reply-To: <3EE8CA66.1010704@iprg.nokia.com> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) 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 all very much for your replies, you've been very helpful. These two drafts are exactly what I was looking for: http://www.cs.ucsb.edu/~ebelding/txt/globalv4.txt http://www.ietf.org/internet-drafts/draft-wakikawa-manet-globalv6-02.txt Charlie Perkins wrote: > > Hello Ralph, > > Did you look at our IPv6 gateways draft? > http://people.nokia.net/charliep/txt/aodvid/globalv6.txt > > There is also an IPv4 gateways draft, authored by a group of > people including Elizabeth Belding-Royer and Yuan Sun. > > These drafts are very similar. The manet nodes treat the Internet > Gateway as a "default router", even if it is multiple hops away. > > Regards. > Charlie P. Ralph A. Preston The MITRE Corporation 202 Burlington Road MS E095 Bedford, MA 01730-1420 http://www.mitre.org _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 22:47: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 WAA06025 for ; Thu, 12 Jun 2003 22:47:52 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D2lQn14729 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 22:47:26 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D2lQm14726 for ; Thu, 12 Jun 2003 22: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 WAA06008 for ; Thu, 12 Jun 2003 22:47:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QeZ1-0000Rg-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 22:45:15 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QeZ1-0000Rd-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 22:45: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 h5CIH4a14085; Thu, 12 Jun 2003 14:17: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 h5CIGgm14065 for ; Thu, 12 Jun 2003 14:16: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 OAA21558 for ; Thu, 12 Jun 2003 14:16:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QWan-0004zw-00 for manet@ietf.org; Thu, 12 Jun 2003 14:14:33 -0400 Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx with esmtp (Exim 4.12) id 19QWam-0004zt-00 for manet@ietf.org; Thu, 12 Jun 2003 14:14:32 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 132E77B4C7; Thu, 12 Jun 2003 14:16:40 -0400 (EDT) Received: from magic.internet2.edu (aa106.internet2.edu [207.75.164.106]) by basie.internet2.edu (Postfix) with ESMTP id E7A1C7B4C5; Thu, 12 Jun 2003 14:16:38 -0400 (EDT) Message-Id: <5.1.0.14.2.20030612140650.015de630@mail.internet2.edu> X-Sender: jzeeff@mail.internet2.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 12 Jun 2003 14:12:29 -0400 To: Manish Karir , manet@ietf.org From: Jon Zeeff Subject: Re: [manet] Internet-MANET gateways? In-Reply-To: <3EE8C00A.70208@isr.umd.edu> References: <3EE8A37C.8010300@isr.umd.edu> <3EE8927E.7000101@isr.umd.edu> <1055431886.4454.89.camel@replicator.hn.org> <3EE8A37C.8010300@isr.umd.edu> <5.1.0.14.2.20030612133221.027f7098@mail.internet2.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS 0.3.12pre8 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Let's try it with a 24 bit address space, a 10x10 array, and when a collision is detected, you don't throw the whole thing out and start over, you simply pick another address for that single node in the array. Answer: one round At 02:01 PM 6/12/2003 -0400, Manish Karir wrote: >the random address picking will not work, to get an idea of the problem >try the following in C or matlab: >pick a 3x3 array. Try to fill this array with random numbers between >1-16(4-bit address space). Check for any duplicates, if you have >duplicates, try again. >Count how many rounds it takes to end up with all unique numbers. > >and this is only for a 9 node network!. > >Actually, some simple analysis would show the same result. > >-manish karir > > >Jon Zeeff wrote: >>One way is a central registry. There aren't many MANET users yet so >>there is an address for >>everyone. >>Just picking an address randomly would work if the routing protocols had >>mechanisms for >>detecting collisions. Perhaps a large number of additional bits serving >>as a signature would allow >>a node to detect that different systems are using the same ip address >>(and notify them to >>change). >>Or use IPV6 and don't worry about it. > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Thu Jun 12 23:25: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 XAA06625 for ; Thu, 12 Jun 2003 23:25:17 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D3OlR17010 for manet-archive@odin.ietf.org; Thu, 12 Jun 2003 23:24:47 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D3Oem17004 for ; Thu, 12 Jun 2003 23:24: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 XAA06610 for ; Thu, 12 Jun 2003 23:24:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qf92-0000bz-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 23:22:28 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qf92-0000bw-00 for manet-web-archive@ietf.org; Thu, 12 Jun 2003 23:22: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 h5CI33a12490; Thu, 12 Jun 2003 14:03: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 h5CI24m12455 for ; Thu, 12 Jun 2003 14:02: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 OAA21122 for ; Thu, 12 Jun 2003 14:02:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QWMc-0004s0-00 for manet@ietf.org; Thu, 12 Jun 2003 13:59:55 -0400 Received: from mailc.telia.com ([194.22.190.4]) by ietf-mx with esmtp (Exim 4.12) id 19QWMc-0004rx-00 for manet@ietf.org; Thu, 12 Jun 2003 13:59:54 -0400 Received: from d1o1121.telia.com (d1o1121.telia.com [217.208.140.241]) by mailc.telia.com (8.12.9/8.12.9) with ESMTP id h5CI1x1a021564; Thu, 12 Jun 2003 20:01:59 +0200 (CEST) X-Original-Recipient: manet@ietf.org Received: from h205n2fls35o1121.telia.com (h205n2fls35o1121.telia.com [217.211.83.205]) by d1o1121.telia.com (8.10.2/8.10.1) with ESMTP id h5CI1xr27595; Thu, 12 Jun 2003 20:01:59 +0200 (CEST) Subject: Re: [manet] Internet-MANET gateways? From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: Manish Karir Cc: manet@ietf.org In-Reply-To: <3EE8BDB5.4020504@isr.umd.edu> References: <3EE8927E.7000101@isr.umd.edu> <1055431886.4454.89.camel@replicator.hn.org> <3EE8A37C.8010300@isr.umd.edu> <1055435894.4454.108.camel@replicator.hn.org> <3EE8BDB5.4020504@isr.umd.edu> Content-Type: text/plain; charset=iso-8859-1 Message-Id: <1055440911.4454.123.camel@replicator.hn.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 12 Jun 2003 20:01:54 +0200 X-MIME-Autoconverted: from 8bit to quoted-printable by mailc.telia.com id h5CI1x1a021564 X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5CI24m12456 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 h5CI33a12490 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5D3Oem17004 Content-Transfer-Encoding: 8bit On Thu, 2003-06-12 at 19:51, Manish Karir wrote: > And, no I do not have a solution to the address allocation problem > distributed or centralized. I wish I did though...:) > IPv6? Erik > > -manish > > > Erik Nordström wrote: > > > To my knowledge, it is commonly assumed (or allowed) that ad hoc > > networks are flat. If you for example study some drafts (e.g. AODV > > draft) and follow some of the discussions, you will find that this is > > the case. > > > > > >>I think the hard problem that has remained unsolved in MANETs is address > >>allocation/assignment. Clearly, a centralized approach is not > >>desirable, and clearly a distributed approach of picking random > >>addresses, is not scalable(birthday paradox). > >> > > > > > > So what do you propose? > > > > > >>I think the "more likely" case is the centralized address distribution > >>during deployment. The most scalable structure built to date the > >>Internet has followed this policy and I think that turned out "okay". :) > >> > > > > > > I thought that the whole idea of ad hoc was to not have structure? > > > > Erik > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 00:32: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 AAA08203 for ; Fri, 13 Jun 2003 00:32:23 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D4VuO21673 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 00:31:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D4Vum21670 for ; Fri, 13 Jun 2003 00:31: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 AAA08184 for ; Fri, 13 Jun 2003 00:31:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QgCA-0000xr-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 00:29:46 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QgCA-0000xo-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 00:29: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 h5CJJ3a18090; Thu, 12 Jun 2003 15:19: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 h5CJIYm18068 for ; Thu, 12 Jun 2003 15:18: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 PAA24653 for ; Thu, 12 Jun 2003 15:18:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QXYf-0005RH-00 for manet@ietf.org; Thu, 12 Jun 2003 15:16:26 -0400 Received: from isrmail.isr.umd.edu ([128.8.111.5] ident=mirapoint) by ietf-mx with esmtp (Exim 4.12) id 19QXYf-0005RD-00 for manet@ietf.org; Thu, 12 Jun 2003 15:16:25 -0400 Received: from isr.umd.edu (doh.isr.umd.edu [128.8.140.151]) by isrmail.isr.umd.edu (Mirapoint Messaging Server MOS 3.3.5-GR) with ESMTP id AJO93100; Thu, 12 Jun 2003 15:18:28 -0400 (EDT) Message-ID: <3EE8D204.10607@isr.umd.edu> Date: Thu, 12 Jun 2003 15:18:28 -0400 From: Manish Karir User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Subject: Re: [manet] Internet-MANET gateways? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit few problems with that. - your address-space to number of nodes ratio is really large, so ofcourse you will get a good answer.:) but thats okay...lets use your example anyways... - how do to propose we perform collision resolution across even 100 nodes, everybody broadcasts to everybody multi-hop(across 100 nodes, remember everyone has to hear everyone else, everyone is doing this at network bootup, so everyone is doing this at the same time, messages are lost, there are collisions)?. say node 10 hears somebody else(87) saying it has the same id, now node 10 will change its id then re-broadcast, but so will 87, which will also rebroadcast there might be another collision so again id is changed and again rebroadcast. The answer of one round is only valid in some cases. If you try enough random seeds, you will hit the scenario where it takes 10 rounds or maybe even more. Its only a matter of probability of what "state" your network comes up in, there are no gurantees that your network will intialize in say 10 seconds, or even say 600 seconds. Forget about the army even commercial devices would not want unpredictable properties like that. - what happens when messages are lost? so does this collision resolution need to be performed periodically, just in case the last time it failed to detect duplicates due to dropped pkts? - now lets scale it up, to 200 nodes, then 500 nodes then 1000 nodes, it gets harder and harder....bottom line the solution does'nt scale to even "small" numbers. -manish karir Jon Zeeff wrote: > > Let's try it with a 24 bit address space, a 10x10 array, and when a > collision is detected, you > don't throw the whole thing out and start over, you simply pick another > address for that > single node in the array. > > Answer: one round > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 00:54: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 AAA08668 for ; Fri, 13 Jun 2003 00:54:49 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D4sMa23575 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 00:54: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 h5D4sMm23572 for ; Fri, 13 Jun 2003 00:54: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 AAA08652 for ; Fri, 13 Jun 2003 00:54:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QgXs-00015b-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 00:52:12 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QgXs-00015Y-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 00:52:12 -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 h5CHmOa11714; Thu, 12 Jun 2003 13:48: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 h5CG1Gm01681 for ; Thu, 12 Jun 2003 12:01:16 -0400 Received: from smtp.web.de (smtp01.web.de [217.72.192.180]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16731 for ; Thu, 12 Jun 2003 12:01:12 -0400 (EDT) Received: from [134.102.101.207] (helo=MIPNET) by smtp.web.de with smtp (WEB.DE 4.98 #218) id 19QUU7-0003Sx-00 for manet@ietf.org; Thu, 12 Jun 2003 17:59:31 +0200 Message-ID: <000c01c330fb$e1ab99b0$cf656686@MIPNET> From: "Michael Sessinghaus" To: Date: Thu, 12 Jun 2003 18:01:26 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01C3310C.A4BEC480" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [manet] Why is QoS-AODV draft expired? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_0009_01C3310C.A4BEC480 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi manet-users, currently i study QoS routing issues and i have red the draft QoS in = AODV ver00. Why this draft is expired in year 2001? Could somebody tell me the = reasons for it, e.g. not practical, high overhead or not appropriate for = the nature of MANets. I am appreciate for comments especially from the = editors of this draft, Miss Belding-Royer or Mr. Perkins. Thanks. Kind Regards, Michael. -- Michael Sessinghaus University of Bremen Department of Communication Networks D-28359 Bremen Germany -- ------=_NextPart_000_0009_01C3310C.A4BEC480 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi manet-users,
currently i study QoS routing issues = and i have red=20 the draft QoS in AODV ver00.
Why this draft is expired in year=20 2001? Could somebody tell me the reasons for it, e.g. not = practical,=20 high overhead or not appropriate for the nature of MANets. I am = appreciate=20 for comments especially from the editors of this draft, Miss = Belding-Royer=20 or Mr. Perkins.
Thanks.
 
Kind Regards, Michael.
 
 
 
 
 
--
Michael Sessinghaus
University of Bremen
Department of Communication Networks
D-28359 Bremen
Germany
--
------=_NextPart_000_0009_01C3310C.A4BEC480-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 01:36: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 BAA09581 for ; Fri, 13 Jun 2003 01:36:13 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D5Zjp26240 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 01:35:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D5Zim26237 for ; Fri, 13 Jun 2003 01:35: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 BAA09577 for ; Fri, 13 Jun 2003 01:35:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QhBu-0001Mt-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 01:33:34 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QhBt-0001Mq-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 01:33:34 -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 h5CHmSa11724; Thu, 12 Jun 2003 13:48: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 h5CG1Jm01696 for ; Thu, 12 Jun 2003 12:01:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16737 for ; Thu, 12 Jun 2003 12:01:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QUTn-0003iD-00 for manet@ietf.org; Thu, 12 Jun 2003 11:59:11 -0400 Received: from mailc.telia.com ([194.22.190.4]) by ietf-mx with esmtp (Exim 4.12) id 19QUTm-0003hj-00 for manet@ietf.org; Thu, 12 Jun 2003 11:59:10 -0400 Received: from d1o1121.telia.com (d1o1121.telia.com [217.208.140.241]) by mailc.telia.com (8.12.9/8.12.9) with ESMTP id h5CG0C1a004743; Thu, 12 Jun 2003 18:00:12 +0200 (CEST) X-Original-Recipient: manet@ietf.org Received: from h205n2fls35o1121.telia.com (h205n2fls35o1121.telia.com [217.211.83.205]) by d1o1121.telia.com (8.10.2/8.10.1) with ESMTP id h5CG0Cr24907; Thu, 12 Jun 2003 18:00:12 +0200 (CEST) Subject: Re: [manet] Internet-MANET gateways? From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= To: Ralph Preston Cc: manet@ietf.org In-Reply-To: <53176C78-9CDB-11D7-A93C-0003937ADD80@mitre.org> References: <53176C78-9CDB-11D7-A93C-0003937ADD80@mitre.org> Content-Type: text/plain Message-Id: <1055433604.4454.97.camel@replicator.hn.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 12 Jun 2003 18:00:07 +0200 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Here are some pointers to drafts: http://www.ietf.org/internet-drafts/draft-royer-manet-globalv4-00.txt http://www.ietf.org/internet-drafts/draft-wakikawa-manet-globalv6-02.txt Erik On Thu, 2003-06-12 at 15:39, Ralph Preston wrote: > Hello, > > An easy question, has it been defined how a MANET-Internet gateway will > work? If it has, please point me to it and don't bother to read the > rest of this message. :) > > I've been trying to figure out how a MANET gateway will interface with > the Internet and enable nodes outside the MANET to initiate > communication with nodes in the MANET. The way I see it there are > three possibilities: > > 1) The gateway advertises routes to each node in the MANET to the > entire Internet. > > 2) The gateway runs NAT. > > 3) Any node who wants to be reachable from outside the MANET must be > running MobileIP and in IPv4 the gateway must be its Foreign Agent, or > Home Agent. > > Number 1 isn't a good solution since nodes in the MANET wont > necessarily be route aggregated. Solution 2 doesn't allow nodes > outside the MANET to contact nodes within the MANET. Which leaves > solution 3, but solution 3 wont work except for nodes that have a > direct connection with the gateway. So, is there currently no way for > outside nodes to contact MANET nodes? > > Ralph A. Preston > The MITRE Corporation > 202 Burlington Road MS E095 > Bedford, MA 01730-1420 > http://www.mitre.org > > > > _______________________________________________ > 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 Jun 13 02:19: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 CAA22271 for ; Fri, 13 Jun 2003 02:19:58 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D6JUB07950 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 02:19:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D6JUm07947 for ; Fri, 13 Jun 2003 02:19: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 CAA22203 for ; Fri, 13 Jun 2003 02:19:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QhsF-0001dH-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 02:17:19 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QhsE-0001dD-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 02:17: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 h5CHq3a12048; Thu, 12 Jun 2003 13:52: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 h5CHpum12026 for ; Thu, 12 Jun 2003 13:51: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 NAA20903 for ; Thu, 12 Jun 2003 13:51:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QWCp-0004nu-00 for manet@ietf.org; Thu, 12 Jun 2003 13:49:47 -0400 Received: from isrmail.isr.umd.edu ([128.8.111.5] ident=mirapoint) by ietf-mx with esmtp (Exim 4.12) id 19QWCo-0004nr-00 for manet@ietf.org; Thu, 12 Jun 2003 13:49:46 -0400 Received: from isr.umd.edu (doh.isr.umd.edu [128.8.140.151]) by isrmail.isr.umd.edu (Mirapoint Messaging Server MOS 3.3.5-GR) with ESMTP id AJO92522; Thu, 12 Jun 2003 13:51:50 -0400 (EDT) Message-ID: <3EE8BDB5.4020504@isr.umd.edu> Date: Thu, 12 Jun 2003 13:51:49 -0400 From: Manish Karir User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Erik_Nordstr=F6m?= CC: manet@ietf.org Subject: Re: [manet] Internet-MANET gateways? References: <3EE8927E.7000101@isr.umd.edu> <1055431886.4454.89.camel@replicator.hn.org> <3EE8A37C.8010300@isr.umd.edu> <1055435894.4454.108.camel@replicator.hn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , X-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h5CHq3a12048 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5D6JUm07947 Content-Transfer-Encoding: 8bit well it might be an implicit assumption, but lets try to approach it from the other side. Lets try to list the different capabilities that are added to the MANET if we allow the addresses to be randomly picked. - flat network: okay sure, but what does that allow us to do that we cannot do if the address space allowed aggregation. - easier to add/remove nodes: partially true, easy to remove nodes, but adding nodes is a horribly complex problem, try to resolve possible conflicts acrosss say a hundred nodes!! (e.g. I think appletalk used to work this way...but ofcourse they limited themselves to a single network segment with small numbers of nodes) - consistent with "ad hoc" concept: true, but does the purist view of ad hoc networks add any key functionality to the MANET And, no I do not have a solution to the address allocation problem distributed or centralized. I wish I did though...:) -manish Erik Nordström wrote: > To my knowledge, it is commonly assumed (or allowed) that ad hoc > networks are flat. If you for example study some drafts (e.g. AODV > draft) and follow some of the discussions, you will find that this is > the case. > > >>I think the hard problem that has remained unsolved in MANETs is address >>allocation/assignment. Clearly, a centralized approach is not >>desirable, and clearly a distributed approach of picking random >>addresses, is not scalable(birthday paradox). >> > > > So what do you propose? > > >>I think the "more likely" case is the centralized address distribution >>during deployment. The most scalable structure built to date the >>Internet has followed this policy and I think that turned out "okay". :) >> > > > I thought that the whole idea of ad hoc was to not have structure? > > Erik > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 02:52: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 CAA23199 for ; Fri, 13 Jun 2003 02:52:29 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D6q1V11265 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 02:52: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 h5D6q0m11255 for ; Fri, 13 Jun 2003 02:52: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 CAA23186 for ; Fri, 13 Jun 2003 02:51:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QiNh-00027E-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 02:49:49 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QiNh-00027B-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 02:49: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 h5CHmKa11701; Thu, 12 Jun 2003 13:48: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 h5CG1Gm01677 for ; Thu, 12 Jun 2003 12:01: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 MAA16733 for ; Thu, 12 Jun 2003 12:01:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QUTk-0003i8-00 for manet@ietf.org; Thu, 12 Jun 2003 11:59:08 -0400 Received: from metatron.isr.umd.edu ([128.8.111.5] helo=isrmail.isr.umd.edu ident=mirapoint) by ietf-mx with esmtp (Exim 4.12) id 19QUTj-0003hc-00 for manet@ietf.org; Thu, 12 Jun 2003 11:59:07 -0400 Received: from isr.umd.edu (doh.isr.umd.edu [128.8.140.151]) by isrmail.isr.umd.edu (Mirapoint Messaging Server MOS 3.3.5-GR) with ESMTP id AJO91920; Thu, 12 Jun 2003 11:59:56 -0400 (EDT) Message-ID: <3EE8A37C.8010300@isr.umd.edu> Date: Thu, 12 Jun 2003 11:59:56 -0400 From: Manish Karir User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Erik_Nordstr=F6m?= , manet@ietf.org Subject: Re: [manet] Internet-MANET gateways? References: <3EE8927E.7000101@isr.umd.edu> <1055431886.4454.89.camel@replicator.hn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , X-MIME-Autoconverted: from 8bit to quoted-printable by www1.ietf.org id h5CHmKa11701 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5D6q0m11255 Content-Transfer-Encoding: 8bit Erik, I think we differ in our assumptions, I assume that we have a predefined prefix that we use to allocate addresses to ad hoc nodes, you assume that the ad hoc nodes can pick any address. Sure, you can assume that, but why does your assumption make any more sense than mine, why would you consider it "more likely"? Besides your assumption creates more problems than it solves.:) I think the hard problem that has remained unsolved in MANETs is address allocation/assignment. Clearly, a centralized approach is not desirable, and clearly a distributed approach of picking random addresses, is not scalable(birthday paradox). I think the "more likely" case is the centralized address distribution during deployment. The most scalable structure built to date the Internet has followed this policy and I think that turned out "okay". :) -manish Erik Nordström wrote: > > Address/route aggregation in multi-hop ad hoc networks is inherently > problematic. > > Either you make assumptions about how nodes are assigned addresses, i.e. > it is mandated that nodes use a specific prefix in the network. This way > it is easy to distinguish (ad hoc network) local packets from outbound > packets (i.e. check the prefix). However, this will require specific > solutions for address assignment in these networks (probably a > centralized scheme). > > The more likely case, is that the ad hoc network is flat, i.e. nodes use > any address. Internet connectivity is in this case provided through NAT. > Here we have a whole range of problems related to have we forward > outbound traffic. For example, for on-demand protocols it does not make > since to use default route entries since nodes do not maintain routes to > all nodes in the network. How will forwarding be solved in this case? > How do we discover gateways? How do we switch gateways when necessary? > > My point is, that this is not necessarily only an engineering issue. > > Erik _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 03:37: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 DAA24033 for ; Fri, 13 Jun 2003 03:37:11 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D7agY14208 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 03:36: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 h5D7agm14205 for ; Fri, 13 Jun 2003 03:36: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 DAA24014 for ; Fri, 13 Jun 2003 03:36:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qj4y-0002Ow-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 03:34:32 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qj4x-0002Ot-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 03:34: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 h5CKl3a23686; Thu, 12 Jun 2003 16:47:03 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5CKknm23668 for ; Thu, 12 Jun 2003 16:46: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 QAA26471 for ; Thu, 12 Jun 2003 16:46:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QYw4-0005rl-00 for manet@ietf.org; Thu, 12 Jun 2003 16:44:40 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19QYw4-0005ra-00 for manet@ietf.org; Thu, 12 Jun 2003 16:44:40 -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 h5CKkCDi010882; Thu, 12 Jun 2003 16:46:12 -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 h5CKkCMD024881; Thu, 12 Jun 2003 16:46:12 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.1.1.32) with SMTP id M2003061216461111438 ; Thu, 12 Jun 2003 16:46:11 -0400 Message-Id: <5.1.1.5.2.20030612161824.02128b50@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Thu, 12 Jun 2003 16:46:02 -0400 To: Jon Zeeff , rpreston@mitre.org (Ralph Preston), manet@ietf.org From: Joe Macker Subject: Re: [manet] Internet-MANET gateways? In-Reply-To: <5.1.0.14.2.20030612153625.027ade30@mail.internet2.edu> References: <5.1.1.5.2.20030612143009.01501810@pop.itd.nrl.navy.mil> <5.1.0.14.2.20030612135520.02790620@mail.internet2.edu> <5.1.1.5.2.20030612124409.014f6088@pop.itd.nrl.navy.mil> <53176C78-9CDB-11D7-A93C-0003937ADD80@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 03:40 PM 6/12/2003 -0400, Jon Zeeff wrote: >>>Some (most?) of the mesh routing protocols do not have a default route concept. > >>If so, I disagree with your general observations. > >If I remember correctly, AODV and DSR don't. I didn't say all and OLSR is a good example >of why not. Right, in my last message I asked if you meant reactive..it was not implied. Taxonomy helps discussion. Also, the first caveat later devolved into implied general observations. (as an example) >In general, mesh routing protocols are deficient in: >4) communicating routes for more than a single ip address Present WG specifications support prefix advertisements and attached networks in one way or another. This was not always true but has been for awhile. >5) address assignment mechanisms For some common Internet-connected deployment cases this is quite simple engineering. As I have mentioned in the past, moderate scale operation can be done and has been demonstrated with manet routing and bootstrapping dhcp relay agents involving no specification modifications. This is just an example of one approach working. There are many scenarios that people may deploy routing protocols in requiring different considerations. Other very esoteric ad hoc methods are possible and there are papers on those. I believe the INTERNET connected case is the most interesting from the IETF engineering perspective. ---------------------------- In general, all routing protocols have problems and will need to go through evolutionary steps. This includes wired protocols relating to security,etc. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 03:49: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 DAA24323 for ; Fri, 13 Jun 2003 03:49:04 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D7mZI15666 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 03:48: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 h5D7mZm15663 for ; Fri, 13 Jun 2003 03:48: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 DAA24310 for ; Fri, 13 Jun 2003 03:48:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QjGT-0002UT-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 03:46:26 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QjGT-0002UQ-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 03:46: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 h5CIl3a16141; Thu, 12 Jun 2003 14: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 h5CIkKm16102 for ; Thu, 12 Jun 2003 14:46: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 OAA22663 for ; Thu, 12 Jun 2003 14:46:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QX3T-0005Fy-00 for manet@ietf.org; Thu, 12 Jun 2003 14:44:11 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19QX3S-0005Fu-00 for manet@ietf.org; Thu, 12 Jun 2003 14:44:10 -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 LAA25678; Thu, 12 Jun 2003 11:45:46 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h5CIjj405710; Thu, 12 Jun 2003 11:45:45 -0700 X-mProtect: <200306121845> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.22.18, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdBmnzxs; Thu, 12 Jun 2003 11:45:43 PDT Message-ID: <3EE8CA66.1010704@iprg.nokia.com> Date: Thu, 12 Jun 2003 11:45:58 -0700 From: Charlie Perkins Organization: Nokia User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ralph Preston CC: manet@ietf.org Subject: Re: [manet] Internet-MANET gateways? References: <53176C78-9CDB-11D7-A93C-0003937ADD80@mitre.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Ralph, Did you look at our IPv6 gateways draft? http://people.nokia.net/charliep/txt/aodvid/globalv6.txt There is also an IPv4 gateways draft, authored by a group of people including Elizabeth Belding-Royer and Yuan Sun. These drafts are very similar. The manet nodes treat the Internet Gateway as a "default router", even if it is multiple hops away. Regards. Charlie P. Ralph Preston wrote: > Hello, > > An easy question, has it been defined how a MANET-Internet gateway > will work? If it has, please point me to it and don't bother to read > the rest of this message. :) > > I've been trying to figure out how a MANET gateway will interface with > the Internet and enable nodes outside the MANET to initiate > communication with nodes in the MANET. The way I see it there are > three possibilities: > > 1) The gateway advertises routes to each node in the MANET to the > entire Internet. > > 2) The gateway runs NAT. > > 3) Any node who wants to be reachable from outside the MANET must be > running MobileIP and in IPv4 the gateway must be its Foreign Agent, or > Home Agent. > > Number 1 isn't a good solution since nodes in the MANET wont > necessarily be route aggregated. Solution 2 doesn't allow nodes > outside the MANET to contact nodes within the MANET. Which leaves > solution 3, but solution 3 wont work except for nodes that have a > direct connection with the gateway. So, is there currently no way for > outside nodes to contact MANET nodes? > > Ralph A. Preston > The MITRE Corporation > 202 Burlington Road MS E095 > Bedford, MA 01730-1420 > http://www.mitre.org > > > > _______________________________________________ > 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 Jun 13 04:40: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 EAA25270 for ; Fri, 13 Jun 2003 04:40:23 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D8dtk20123 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 04:39:55 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D8dtm20120 for ; Fri, 13 Jun 2003 04:39: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 EAA25267 for ; Fri, 13 Jun 2003 04:39:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qk49-0002nu-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 04:37:45 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qk48-0002nr-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 04: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 h5CJ42a16638; Thu, 12 Jun 2003 15: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 h5CJ3Fm16610 for ; Thu, 12 Jun 2003 15:03: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 PAA23057 for ; Thu, 12 Jun 2003 15:03:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QXJp-0005JW-00 for manet@ietf.org; Thu, 12 Jun 2003 15:01:06 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19QXJp-0005JN-00 for manet@ietf.org; Thu, 12 Jun 2003 15:01:05 -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 h5CJ2gDi006229; Thu, 12 Jun 2003 15:02:42 -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 h5CJ2gMD022573; Thu, 12 Jun 2003 15:02:42 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.1.1.32) with SMTP id M2003061215024111012 ; Thu, 12 Jun 2003 15:02:41 -0400 Message-Id: <5.1.1.5.2.20030612143009.01501810@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Thu, 12 Jun 2003 15:02:32 -0400 To: Jon Zeeff , rpreston@mitre.org (Ralph Preston), manet@ietf.org From: Joe Macker Subject: Re: [manet] Internet-MANET gateways? In-Reply-To: <5.1.0.14.2.20030612135520.02790620@mail.internet2.edu> References: <5.1.1.5.2.20030612124409.014f6088@pop.itd.nrl.navy.mil> <53176C78-9CDB-11D7-A93C-0003937ADD80@mitre.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 02:06 PM 6/12/2003 -0400, Jon Zeeff wrote: >Some (most?) of the mesh routing protocols do not have a default route concept. This is unfortunate since it means that if you are using a mesh network to access another network (say the Internet), you have to do route discovery for every single ip address you connect to. Are you using mesh and manet synonymously here? If so, I disagree with your general observations. This is quite easily supported with OLSR or other proactive appraoches (TBRPF I assume also)... But what do you mean? Similar to OSPF ABR functionality default routes can easily be injected for stub mobile routing areas. We have been doing this with working code for some time now (multiple addresses and connected networks are advertisable at each node). Aggregate prefixes can be discovered dynamically and appropriate route entries maintained..do you need instructions? Normal address assignment approaches (e.g., DHCP) are also supportable as I have previously posted. Transit networks of course need additional policy and management approaches to address such issues. All routing protocols tend to have extensions and specific conditions. We also have working mutiple path and other metric support code extensions working but are keeping that in the research realm for now. Or are you speaking specifically about reactive? Please be very specific. There is some support for prefix advertisement there as well. Someone else could address whether its been done in practice and how. >Would be more efficient if one could supply a mask with a route (and more specific routes >override less specific ones). > >In general, mesh routing protocols are deficient in: > >1) security >2) use of metrics other than hop count >3) multipath support >4) communicating routes for more than a single ip address >5) address assignment mechanisms _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 05:47:01 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 FAA26716 for ; Fri, 13 Jun 2003 05:47:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5D9kYu25325 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 05:46:34 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D9kYm25322 for ; Fri, 13 Jun 2003 05:46: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 FAA26706 for ; Fri, 13 Jun 2003 05:46:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ql6d-0003DR-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 05:44:23 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Ql6c-0003DM-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 05:44: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 h5D6h4a10736; Fri, 13 Jun 2003 02:43: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 h5D6gBm10679 for ; Fri, 13 Jun 2003 02:42: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 CAA22815 for ; Fri, 13 Jun 2003 02:42:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QiEC-00021e-00 for manet@ietf.org; Fri, 13 Jun 2003 02:40:00 -0400 Received: from ims21.stu.nus.edu.sg ([137.132.14.228]) by ietf-mx with esmtp (Exim 4.12) id 19QiEC-00021Y-00 for manet@ietf.org; Fri, 13 Jun 2003 02:40:00 -0400 Received: from mbxsrv22.stu.nus.edu.sg ([137.132.14.232]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.5329); Fri, 13 Jun 2003 14:42:05 +0800 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Date: Fri, 13 Jun 2003 14:42:05 +0800 Message-ID: <90291BA1D4EB8F4998A5BDD4C37DE92C549CEB@MBXSRV22.stu.nus.edu.sg> Thread-Topic: Question about aggregate traffic problem at MANET Thread-Index: AcMxdudPqkR+FFp/RqKROY622p3IvA== From: "Wu Mintao" To: X-OriginalArrivalTime: 13 Jun 2003 06:42:05.0781 (UTC) FILETIME=[E7968850:01C33176] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h5D6gBm10680 Subject: [manet] Question about aggregate traffic problem at MANET Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, I am currently studying the aggregate traffic problem at MANET. eg, let us assume one unlucky node is on the routing path of many on-going heavy communication and what's worst, it has many communication with other nodes by itself. the aggregate traffic will cause problem. I am trying to look for some papers or useful links on this topic. can anyone please tell me where i can get useful information on this particular topic? yours sincerely, Mintao _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 06:23: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 GAA27463 for ; Fri, 13 Jun 2003 06:23:26 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5DAMx528113 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 06:22: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 h5DAMxm28110 for ; Fri, 13 Jun 2003 06:22: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 GAA27448 for ; Fri, 13 Jun 2003 06:22:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qlfs-0003RP-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 06:20:48 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qlfs-0003RM-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 06:20: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 h5CNo4a02825; Thu, 12 Jun 2003 19:50: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 h5CNnom02802 for ; Thu, 12 Jun 2003 19:49: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 TAA01757 for ; Thu, 12 Jun 2003 19:49:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QbnC-00075F-00 for manet@ietf.org; Thu, 12 Jun 2003 19:47:42 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 19QbnA-00075C-00 for manet@ietf.org; Thu, 12 Jun 2003 19:47:41 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id EC79A200B for ; Thu, 12 Jun 2003 17:49:41 -0600 (MDT) From: "John Mullen" To: Subject: RE: [manet] Internet-MANET gateways? Date: Thu, 12 Jun 2003 17:49:42 -0600 Message-ID: <000001c3313d$4b598570$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: <5.1.0.14.2.20030612133221.027f7098@mail.internet2.edu> 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, There are a number of possible situations, but a common set of problems. The main problem is how an Internet user finds out that another user is available on a MANET. There is no single solution that works for all. For example, tunneling to a fixed Internet node works well as long as the mobile users are not too distant. Imagine two participants at conferences in London, located one km apart. One is from San Francisco and the other from Sydney. If they burrow to a home Internet node, they will communicate via thousands of kilometers and many, many intermediate nodes, while a much shorter path would suffice. Internet directories seem like a logical solution, but there has to be a common protocol. Also, to avoid having replicates (with possible latency) of gigantic databases all over the world, the directory would probably be distributed. Thus, even if you know a person's IP address, some system will have to try to figure out which region that user is in. Lets not forget that wireless connections are spotty and that a node may temporarily be disconnected from an Internet gateway. How will advertisements be handled in the event that a connection is not reliable? If a MANET is smallish, being flat is not a problem within the MANET. The real problem is how a mobile node that is one day in a MANET in Iowa and the next in France will be advertised in such a way that it is clear to anyone trying to reach him that he is the same person. This implies some sort of permanent IP address that the Internet can use to find the user and some other mechanism so it can find the right MANET. If burrowing isn't used, there will probably have to be some sort of directory system. A military MANET could consist of thousands of nodes, but members belong to a single organization. It might be desirable to allow members of different MANETs to communicate with each other via the Internet without revealing to outsiders who is talking and from where. Yet, members of the organization should be able to find each other quickly. Some communities have set up public wireless nets. I'm not sure if any of them are MANETs. They may be all stub nets. However, they have a similar problem in how to resolve the address problem. Whatever the solution is, it needs to be compatible with Internet protocol. I suspect, however, because of differing needs of different users, several solutions may be implemented within the MANETs themselves. That is, a person who doesn't travel much might prefer a home node while a globe trotter might prefer a directory. I suspect, there will be a virtual ISP somewhere and the tradeoffs of the differing services will be reflected in different options and fees. Truth is, there are several different cellular and other phone schemes in the world, yet it is generally possible to talk to each other, as long as we know which numbers to key in. I suspect, the same situation will evolve under pressures of technology and the market. Whether or not this is a MANET issue, though, I am not sure. As long as a gateway knows who is in the MANET, I suspect any Internet referencing scheme can be made to work with the MANET. The main issues are really Internet ones. John Mullen _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 07:58: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 HAA29381 for ; Fri, 13 Jun 2003 07:58:12 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5DBvhe02187 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 07:57:43 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DBvgm02184 for ; Fri, 13 Jun 2003 07:57: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 HAA29361 for ; Fri, 13 Jun 2003 07:57:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qn9Z-0003qR-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 07:55:33 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qn9Y-0003qO-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 07:55: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 h5D9P3a23499; Fri, 13 Jun 2003 05:25:03 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5D9OCm23439 for ; Fri, 13 Jun 2003 05:24: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 FAA26286 for ; Fri, 13 Jun 2003 05:24:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qkl0-000374-00 for manet@ietf.org; Fri, 13 Jun 2003 05:22:02 -0400 Received: from cheviot3.ncl.ac.uk ([128.240.233.117] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19Qkkz-000371-00 for manet@ietf.org; Fri, 13 Jun 2003 05:22:01 -0400 Received: from ncl.ac.uk (deerbook.ncl.ac.uk [128.240.149.114]) by cheviot3.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id h5D9O6p22001; Fri, 13 Jun 2003 10:24:06 +0100 Date: Fri, 13 Jun 2003 10:24:05 +0100 Subject: Re: [manet] Internet-MANET gateways? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: manet@ietf.org To: Manish Karir From: Einar Vollset In-Reply-To: <3EE8D204.10607@isr.umd.edu> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) X-Newcastle-MailScanner: Found to be clean 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 > - what happens when messages are lost? so does this collision > resolution > need to be performed periodically, just in case the last time it > failed to detect duplicates due to dropped pkts? Use a reliable broadcast protocol. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 13:05: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 NAA13064 for ; Fri, 13 Jun 2003 13:05:20 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5DH4si08745 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 13:04: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 h5DH4rm08742 for ; Fri, 13 Jun 2003 13:04: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 NAA13036 for ; Fri, 13 Jun 2003 13:04:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qrwo-0006vF-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 13:02:42 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qrwo-0006vB-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 13:02: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 h5DE05a12906; Fri, 13 Jun 2003 10:00: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 h5DDxFm12800 for ; Fri, 13 Jun 2003 09:59: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 JAA05321 for ; Fri, 13 Jun 2003 09:59:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qp3A-0005Qr-00 for manet@ietf.org; Fri, 13 Jun 2003 09:57:04 -0400 Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx with esmtp (Exim 4.12) id 19Qp39-0005Qo-00 for manet@ietf.org; Fri, 13 Jun 2003 09:57:03 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 367667B4C1; Fri, 13 Jun 2003 09:59:12 -0400 (EDT) Received: from magic.internet2.edu (aa106.internet2.edu [207.75.164.106]) by basie.internet2.edu (Postfix) with ESMTP id 117597B502; Fri, 13 Jun 2003 09:59:11 -0400 (EDT) Message-Id: <5.1.0.14.2.20030613095139.015fa7d8@mail.internet2.edu> X-Sender: jzeeff@mail.internet2.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 13 Jun 2003 09:59:01 -0400 To: "Wu Mintao" , From: Jon Zeeff Subject: Re: [manet] Question about aggregate traffic problem at MANET In-Reply-To: <90291BA1D4EB8F4998A5BDD4C37DE92C549CEB@MBXSRV22.stu.nus.ed u.sg> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS 0.3.12pre8 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , What you ask about is a common case. It might even be that that one node is on a slow link with lots of loss. So you want load balancing, QOS, fair queuing and non-hopcount based route selection metrics. > I am currently studying the aggregate traffic problem at MANET. eg, let > us assume one unlucky node is on the routing path of many on-going heavy > communication and what's worst, it has many communication with other > nodes by itself. the aggregate traffic will cause problem. > I am trying to look for some papers or useful links on this topic. can > anyone please tell me where i can get useful information on this > particular topic? _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 13:07: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 NAA13228 for ; Fri, 13 Jun 2003 13:07:34 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5DH77N09632 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 13:07: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 h5DH77m09629 for ; Fri, 13 Jun 2003 13:07: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 NAA13183 for ; Fri, 13 Jun 2003 13:07:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qryy-0006xw-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 13:04:56 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qryx-0006xt-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 13:04: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 h5DGt3a30689; Fri, 13 Jun 2003 12:55:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DGs5m29479 for ; Fri, 13 Jun 2003 12:54: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 MAA11807 for ; Fri, 13 Jun 2003 12:54:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QrmM-0006f3-00 for manet@ietf.org; Fri, 13 Jun 2003 12:51:54 -0400 Received: from strix.ciens.ucv.ve ([150.185.72.253]) by ietf-mx with esmtp (Exim 4.12) id 19Qrm5-0006ec-00 for manet@ietf.org; Fri, 13 Jun 2003 12:51:38 -0400 Received: from strix.ciens.ucv.ve (localhost [127.0.0.1] (may be forged)) by strix.ciens.ucv.ve (8.12.5/8.12.5) with ESMTP id h5DHNIwu008047 for ; Fri, 13 Jun 2003 13:23:18 -0400 Received: from localhost (dcobos@localhost) by strix.ciens.ucv.ve (8.12.5/8.12.5/Submit) with ESMTP id h5DHNHxv008043 for ; Fri, 13 Jun 2003 13:23:18 -0400 Date: Fri, 13 Jun 2003 13:23:17 -0400 (VET) From: Denis Cobos To: manet@ietf.org In-Reply-To: <5.1.0.14.2.20030612135520.02790620@mail.internet2.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] !!About movement models!! Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello everybody, I'm interested in using a movement model in my simulation, but I'm interested in having a tool such as Setdest already implemented for generating others movement models in NS2. I would also like to know if there exist some improvements on the waypoint model that were already defined, used or tested for NS2, or if there are new models to ensure the quality and validity of the simulation. Thanks Best regards -- ***************************************************** * * * Denis Alfonzo Cobos * * Escuela de Computacio * * Facultad de Ciencias * * Universidad Central de Venezuela * * Caracas-Venezuela * ***************************************************** ..... Saludos _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 13:10: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 NAA13350 for ; Fri, 13 Jun 2003 13:10:05 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5DH9dZ12393 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 13:09: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 h5DH9dm12390 for ; Fri, 13 Jun 2003 13:09: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 NAA13327 for ; Fri, 13 Jun 2003 13:09:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qs1P-00070T-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 13:07:27 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qs1P-00070Q-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 13:07: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 h5DEU3a15532; Fri, 13 Jun 2003 10:30:03 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DETdm15502 for ; Fri, 13 Jun 2003 10: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 KAA07972 for ; Fri, 13 Jun 2003 10:29:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QpWa-0005p6-00 for manet@ietf.org; Fri, 13 Jun 2003 10:27:28 -0400 Received: from stl-smtpout-01.boeing.com ([130.76.96.56]) by ietf-mx with esmtp (Exim 4.12) id 19QpWY-0005p3-00 for manet@ietf.org; Fri, 13 Jun 2003 10:27:27 -0400 Received: from stl-av-02.boeing.com ([192.76.190.7]) by stl-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id JAA10145; Fri, 13 Jun 2003 09:29:30 -0500 (CDT) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by stl-av-02.boeing.com (8.9.3p2/8.9.2/MBS-AV-02) with ESMTP id JAA13366; Fri, 13 Jun 2003 09:29:29 -0500 (CDT) Received: from xch-nebh-01.ne.nos.boeing.com (xch-nebh-01.ne.nos.boeing.com [128.225.80.200]) by blv-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id h5DETSC28994; Fri, 13 Jun 2003 07:29:28 -0700 (PDT) Received: from xch-ne-01.ne.nos.boeing.com ([128.225.80.201]) by xch-nebh-01.ne.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.2966); Fri, 13 Jun 2003 10:29:28 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6334.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [manet] Internet-MANET gateways? Date: Fri, 13 Jun 2003 10:29:27 -0400 Message-ID: Thread-Topic: [manet] Internet-MANET gateways? Thread-Index: AcMxd1JQc+jncy52REi0/yAQtCA1hQAPwl4Q From: "Manfredi, Albert E" To: "Manish Karir" , X-OriginalArrivalTime: 13 Jun 2003 14:29:28.0500 (UTC) FILETIME=[3259DF40:01C331B8] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5DETdm15503 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 Manish Karir wrote: > > Erik, > > I think we differ in our assumptions, I assume that we have a > predefined > prefix that we use to allocate addresses to ad hoc nodes, you assume > that the ad hoc nodes can pick any address. > Sure, you can assume that, but why does your assumption make any more > sense than mine, why would you consider it "more likely"? Erik's assumption and yours are both possible in MANETs, and have both been discussed. I have always favored the flat address space concept Erik talks about, which ignores any hierarchical nature of IP addresses inside the MANET, because it is more generic, requires no infrastructure support, and does not care about any dynamic changes of topology in this MANET. Seems to me that if that approach can work, you know you can make a MANET work. > Besides your assumption creates more problems than it solves.:) > > I think the hard problem that has remained unsolved in MANETs > is address > allocation/assignment. This is a simple problem if you use the flat address space concept. Simply use a globally unique address assigned to each mobile host before it gets deployed anywhere. You know, whatever is assigned to that mobile host when it is "home," wherever home might be. > I think the "more likely" case is the centralized address > distribution > during deployment. The most scalable structure built to date the > Internet has followed this policy and I think that turned out > "okay". :) Centralised address distribution during deployment right away places an administrative burden on the MANET that the flat address space approach doesn't. To comminicate between a MANET host and the fixed Internet, you can use various schemes, one of which is Mobile IP. But there are others too, although these others might require the mobile host to initiate any session to a host outside the MANET. Bert _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 13:37: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 NAA15155 for ; Fri, 13 Jun 2003 13:37:49 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5DHbKB13896 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 13:37:20 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DHbKm13878 for ; Fri, 13 Jun 2003 13: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 NAA15126 for ; Fri, 13 Jun 2003 13:37:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QsSD-0007WF-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 13:35:09 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QsSC-0007WC-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 13:35: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 h5DH93a11443; Fri, 13 Jun 2003 13:09: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 h5DH82m10563 for ; Fri, 13 Jun 2003 13:08: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 NAA13263 for ; Fri, 13 Jun 2003 13:07:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qrzr-0006z5-00 for manet@ietf.org; Fri, 13 Jun 2003 13:05:51 -0400 Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx with esmtp (Exim 4.12) id 19Qrzq-0006yv-00 for manet@ietf.org; Fri, 13 Jun 2003 13:05:50 -0400 Received: from dagger.cc.vt.edu (IDENT:mirapoint@evil-dagger [10.1.1.11]) by lennier.cc.vt.edu (8.12.8/8.12.8) with ESMTP id h5DH7vcs516396; Fri, 13 Jun 2003 13:07:57 -0400 (EDT) Received: from tom ([198.70.228.100]) by dagger.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BNM32983 (AUTH talin); Fri, 13 Jun 2003 13:07:54 -0400 (EDT) Message-ID: <007f01c331ce$66fbae20$2502a8c0@tom> From: "Tao Lin" To: "Denis Cobos" , References: Subject: Re: [manet] !!About movement models!! Date: Fri, 13 Jun 2003 13:08:21 -0400 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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 Search Bonnmotion on google. It is a good one. Tao Lin PhD Candidate ECE Dept. Virginia Tech ----- Original Message ----- From: "Denis Cobos" To: Sent: Friday, June 13, 2003 1:23 PM Subject: [manet] !!About movement models!! > Hello everybody, > > I'm interested in using a movement model in my > simulation, but I'm interested in having a tool such > as Setdest already implemented for generating others > movement models in NS2. I would also like to know if there > exist some improvements on the waypoint model that > were already defined, used or tested for NS2, or if > there are new models to ensure the quality and > validity of the simulation. > > Thanks > > Best regards > -- > ***************************************************** > * * > * Denis Alfonzo Cobos * > * Escuela de Computacio * > * Facultad de Ciencias * > * Universidad Central de Venezuela * > * Caracas-Venezuela * > ***************************************************** > > > ..... Saludos > > > > _______________________________________________ > 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 Jun 13 14:53:51 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 OAA18468 for ; Fri, 13 Jun 2003 14:53:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5DIrOL18693 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 14:53:24 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DIrNm18690 for ; Fri, 13 Jun 2003 14:53: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 OAA18453 for ; Fri, 13 Jun 2003 14:53:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qtdo-0000Ta-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 14:51:12 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qtdn-0000TX-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 14:51:11 -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 h5DHV4a22104; Fri, 13 Jun 2003 13:31:04 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DHUUm21441 for ; Fri, 13 Jun 2003 13:30: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 NAA14788 for ; Fri, 13 Jun 2003 13:30:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QsLa-0007PS-00 for manet@ietf.org; Fri, 13 Jun 2003 13:28:19 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19QsLa-0007Oj-00 for manet@ietf.org; Fri, 13 Jun 2003 13:28:18 -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 KAA08588; Fri, 13 Jun 2003 10:29:55 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h5DHTsP09289; Fri, 13 Jun 2003 10:29:54 -0700 X-mProtect: <200306131729> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.67, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdq1n1U0; Fri, 13 Jun 2003 10:29:53 PDT Message-ID: <3EEA0A76.6080805@iprg.nokia.com> Date: Fri, 13 Jun 2003 10:31:34 -0700 From: Fred Templin 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: John Mullen CC: manet@ietf.org Subject: Re: [manet] Internet-MANET gateways? References: <000001c3313d$4b598570$67f57b80@IEngr.ad.nmsu.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit John Mullen wrote: >Hi, > >There are a number of possible situations, but a common set of problems. >The main problem is how an Internet user finds out that another user is >available on a MANET. > When you say: "finds out", do you mean discovery by by IP address or by domain name? Fred ftemplin@iprg.nokia.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 17:29: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 RAA23824 for ; Fri, 13 Jun 2003 17:29:06 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5DLSdo22093 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 17:28: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 h5DLSdm22090 for ; Fri, 13 Jun 2003 17:28: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 RAA23805 for ; Fri, 13 Jun 2003 17:28:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qw44-0001S8-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 17:26:28 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Qw43-0001S5-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 17:26: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 h5DJ43a25904; Fri, 13 Jun 2003 15:04:03 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DJ39m24905 for ; Fri, 13 Jun 2003 15: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 PAA18811 for ; Fri, 13 Jun 2003 15:03:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QtnF-0000WN-00 for manet@ietf.org; Fri, 13 Jun 2003 15:00:57 -0400 Received: from cancun.cos.ufrj.br ([146.164.34.49] helo=cos.ufrj.br) by ietf-mx with esmtp (Exim 4.12) id 19QtnD-0000W9-00 for manet@ietf.org; Fri, 13 Jun 2003 15:00:56 -0400 Received: from localhost (carlosvc@localhost) by cos.ufrj.br (8.11.6/8.11.6) with ESMTP id h5DJOPP24722 for ; Fri, 13 Jun 2003 16:24:25 -0300 Date: Fri, 13 Jun 2003 16:24:25 -0300 (BRT) From: Carlos Alberto Vieira Campos To: manet@ietf.org Subject: Re: [manet] !!About movement models!! 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: , Denis, I recommend you to look the ScenGen Simulator, a tool to generate MANET mobility scenarios for NS-2. It support individual and group mobility models. It can be found in http://www.comp.nus.edu.sg/~liqm/scengen/ Good luck, Carlos Alberto. On Fri, 13 Jun 2003, Denis Cobos wrote: > Hello everybody, > > I'm interested in using a movement model in my > simulation, but I'm interested in having a tool such > as Setdest already implemented for generating others > movement models in NS2. I would also like to know if there > exist some improvements on the waypoint model that > were already defined, used or tested for NS2, or if > there are new models to ensure the quality and > validity of the simulation. > > Thanks > > Best regards > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 18:51: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 SAA27083 for ; Fri, 13 Jun 2003 18:51:44 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5DMpIM30355 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 18:51:18 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DMpIm30352 for ; Fri, 13 Jun 2003 18:51: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 SAA27058 for ; Fri, 13 Jun 2003 18:51:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QxM2-0001y0-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 18:49:06 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QxM1-0001xx-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 18:49: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 h5DJc3a05364; Fri, 13 Jun 2003 15:38: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 h5DJbLm04923 for ; Fri, 13 Jun 2003 15:37:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20832 for ; Fri, 13 Jun 2003 15:37:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QuKN-0000i8-00 for manet@ietf.org; Fri, 13 Jun 2003 15:35:11 -0400 Received: from cancun.cos.ufrj.br ([146.164.34.49] helo=cos.ufrj.br) by ietf-mx with esmtp (Exim 4.12) id 19QuKH-0000i3-00 for manet@ietf.org; Fri, 13 Jun 2003 15:35:10 -0400 Received: from localhost (carlosvc@localhost) by cos.ufrj.br (8.11.6/8.11.6) with ESMTP id h5DHwmP14110; Fri, 13 Jun 2003 14:58:48 -0300 Date: Fri, 13 Jun 2003 14:58:48 -0300 (BRT) From: Carlos Alberto Vieira Campos To: Denis Cobos cc: manet@ietf.org Subject: Re: [manet] !!About movement models!! 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: , Denis, I recommend to look the ScenGen Simulator, a tool for to generate MANET mobility scenarios for NS-2. It support individual and group mobility models. It can be meeted in http://www.comp.nus.edu.sg/~liqm/scengen/ Good luck, Carlos Alberto. On Fri, 13 Jun 2003, Denis Cobos wrote: > Hello everybody, > > I'm interested in using a movement model in my > simulation, but I'm interested in having a tool such > as Setdest already implemented for generating others > movement models in NS2. I would also like to know if there > exist some improvements on the waypoint model that > were already defined, used or tested for NS2, or if > there are new models to ensure the quality and > validity of the simulation. > > Thanks > > Best regards > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Fri Jun 13 21:10: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 VAA00749 for ; Fri, 13 Jun 2003 21:10:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5E19fI08540 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 21:09: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 h5E19fm08537 for ; Fri, 13 Jun 2003 21:09: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 VAA00726 for ; Fri, 13 Jun 2003 21:09:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QzVx-0002vH-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 21:07:30 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19QzVx-0002vE-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 21:07:29 -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 h5DJS3a02503; Fri, 13 Jun 2003 15:28:03 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DJRvm02486 for ; Fri, 13 Jun 2003 15:27: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 PAA20728 for ; Fri, 13 Jun 2003 15:27:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19QuBH-0000gd-00 for manet@ietf.org; Fri, 13 Jun 2003 15:25:47 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19QuBG-0000gZ-00 for manet@ietf.org; Fri, 13 Jun 2003 15:25:46 -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 h5DJRODi027919; Fri, 13 Jun 2003 15:27:24 -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 h5DJROMD022245; Fri, 13 Jun 2003 15:27:24 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.1.1.32) with SMTP id M2003061315272315453 ; Fri, 13 Jun 2003 15:27:23 -0400 Message-Id: <5.1.1.5.2.20030613152454.0251c240@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Fri, 13 Jun 2003 15:27:10 -0400 To: Fred Templin , John Mullen From: Joe Macker Subject: Re: [manet] Internet-MANET gateways? Cc: manet@ietf.org In-Reply-To: <3EEA0A76.6080805@iprg.nokia.com> References: <000001c3313d$4b598570$67f57b80@IEngr.ad.nmsu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 10:31 AM 6/13/2003 -0700, Fred Templin wrote: >John Mullen wrote: > >>Hi, >> >>There are a number of possible situations, but a common set of problems. >>The main problem is how an Internet user finds out that another user is >>available on a MANET. >When you say: "finds out", do you mean discovery by by IP address >or by domain name? How do you find me on the Internet? Good luck?! I might not be where you think I am and why do you care? >Fred >ftemplin@iprg.nokia.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 Fri Jun 13 21:54: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 VAA01874 for ; Fri, 13 Jun 2003 21:54:29 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5E1s2t10760 for manet-archive@odin.ietf.org; Fri, 13 Jun 2003 21:54: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 h5E1s2m10757 for ; Fri, 13 Jun 2003 21:54: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 VAA01864 for ; Fri, 13 Jun 2003 21:53:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19R0Cs-0003BL-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 21:51:50 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19R0Cr-0003BI-00 for manet-web-archive@ietf.org; Fri, 13 Jun 2003 21:51: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 h5DJ23a24293; Fri, 13 Jun 2003 15:02:03 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5DJ1Vm24072 for ; Fri, 13 Jun 2003 15:01: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 PAA18726 for ; Fri, 13 Jun 2003 15:01:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Qtlf-0000Va-00 for manet@ietf.org; Fri, 13 Jun 2003 14:59:19 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 19Qtle-0000VX-00 for manet@ietf.org; Fri, 13 Jun 2003 14:59:19 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 2B9C72006; Fri, 13 Jun 2003 13:01:27 -0600 (MDT) From: "John Mullen" To: "'Fred Templin'" Cc: Subject: RE: [manet] Internet-MANET gateways? Date: Fri, 13 Jun 2003 13:01:27 -0600 Message-ID: <000001c331de$310e3020$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: <3EEA0A76.6080805@iprg.nokia.com> 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 Fred, Yes! :-) I've been lurking on this topic and don't feel that this issue has been resolved. Clearly, if a user is to be found via a global search of the Internet, then some sort of permanent label is needed. I favor the idea of domain name because Internet IPs are hierarchal analogs of the Internet structure. This allows one to let the MANET assign IPs in whatever way makes sense. However, not all users have the same interests. I have accounts with two IPs. One I use for University business, the other for personal business. This allows me to get through the work day without being interrupted by personal messages and through my evening conversations without intrusions from work. Via the Internet, however, I can access my email from either IP. This allows me to control my environment. A person at a conference might have three domains of interest: 1) everyday work, 2) personal, and 3) conference. He or she might choose to use a MANET for domain 3, while using a stub or wire interconnection for the first two. That is, he or she might be comfortable with an IP address valid within the MANET, but unknown to the Internet. On the other hand, that person might want to reachable by his or her coworkers and would want an IP on the MANET that is reachable by them. In the first case, the user might simply log on using a generic domain, but in the second use an Internet domain name or report to the gateway his or her permanent IP. At any rate, it is not just that MANETs differ, but also that users differ. What works for one might be viewed as unnecessary or even intrusive to another. I think the market will sort this one out, though is certainly a good idea to keep thinking about possible solutions. John Mullen -----Original Message----- From: Fred Templin [mailto:ftemplin@iprg.nokia.com] Sent: Friday, June 13, 2003 10:32 AM To: John Mullen Cc: manet@ietf.org Subject: Re: [manet] Internet-MANET gateways? John Mullen wrote: >Hi, > >There are a number of possible situations, but a common set of >problems. The main problem is how an Internet user finds out that >another user is available on a MANET. > When you say: "finds out", do you mean discovery by by IP address or by domain name? Fred ftemplin@iprg.nokia.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sat Jun 14 17:23: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 RAA04666 for ; Sat, 14 Jun 2003 17:23:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5ELNFm28154 for manet-archive@odin.ietf.org; Sat, 14 Jun 2003 17:23: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 h5ELNFm28151 for ; Sat, 14 Jun 2003 17:23: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 RAA04654 for ; Sat, 14 Jun 2003 17:23:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RISM-0000GW-00 for manet-web-archive@ietf.org; Sat, 14 Jun 2003 17:21:02 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19RISL-0000GT-00 for manet-web-archive@ietf.org; Sat, 14 Jun 2003 17:21: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 h5EIt3a18841; Sat, 14 Jun 2003 14:55:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5EIsam18820 for ; Sat, 14 Jun 2003 14:54: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 OAA01305 for ; Sat, 14 Jun 2003 14:54:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RG8U-0007Q0-00 for manet@ietf.org; Sat, 14 Jun 2003 14:52:22 -0400 Received: from nn3.excitenetwork.com ([207.159.120.57] helo=xmxpita.excite.com) by ietf-mx with esmtp (Exim 4.12) id 19RG8U-0007Pj-00 for manet@ietf.org; Sat, 14 Jun 2003 14:52:22 -0400 Received: by xmxpita.excite.com (Postfix, from userid 110) id 506233DF4; Sat, 14 Jun 2003 14:53:56 -0400 (EDT) To: manet@ietf.org Received: from [172.145.126.168] by xprdmailfe6.nwk.excite.com via HTTP; Sat, 14 Jun 2003 14:53:56 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = 368aa9a80472b1e8240d591cb6d03677 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__8544fdd5cc0df15645fc9ac6894b38f7"; Content-Transfer-Encoding: 7bit Message-Id: <20030614185356.506233DF4@xmxpita.excite.com> Date: Sat, 14 Jun 2003 14:53:56 -0400 (EDT) Subject: [manet] About AODV Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --EXCITEBOUNDARY_000__8544fdd5cc0df15645fc9ac6894b38f7 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi All: I am studying AODV. But I can not understand why "destination sequence number" can be used to prevent loop. Could someboby please explain it? Thanks a lot. Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! --EXCITEBOUNDARY_000__8544fdd5cc0df15645fc9ac6894b38f7 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit
Hi All:

I am studying AODV. But I can not understand why "destination sequence number" can be used to prevent loop. Could someboby please explain it? Thanks a lot.

Jack




Join Excite! - http://www.excite.com
The most personalized portal on the Web! --EXCITEBOUNDARY_000__8544fdd5cc0df15645fc9ac6894b38f7-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Sun Jun 15 15:02:28 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 PAA07474 for ; Sun, 15 Jun 2003 15:02:28 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5FJ20I17383 for manet-archive@odin.ietf.org; Sun, 15 Jun 2003 15:02: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 h5FJ20m17380 for ; Sun, 15 Jun 2003 15:02: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 PAA07464 for ; Sun, 15 Jun 2003 15:01:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RcjA-0004ir-00 for manet-web-archive@ietf.org; Sun, 15 Jun 2003 14:59:44 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Rcj9-0004in-00 for manet-web-archive@ietf.org; Sun, 15 Jun 2003 14:59: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 h5FEF3a02513; Sun, 15 Jun 2003 10:15: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 h5FEE9m02457 for ; Sun, 15 Jun 2003 10:14: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 KAA02947 for ; Sun, 15 Jun 2003 10:14:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RYEb-0003ns-00 for manet@ietf.org; Sun, 15 Jun 2003 10:11:53 -0400 Received: from zrtps06s.nortelnetworks.com ([47.140.48.50]) by ietf-mx with esmtp (Exim 4.12) id 19RYEb-0003np-00 for manet@ietf.org; Sun, 15 Jun 2003 10:11:53 -0400 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps06s.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h5FEDSB01323 for ; Sun, 15 Jun 2003 10:13:29 -0400 (EDT) Received: from zrtpd0jh.us.nortel.com ([47.140.202.34]) by zrtpd0jn.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id M5CNNR45; Sun, 15 Jun 2003 10:13:29 -0400 Received: from americasm01.nt.com (wnc1h04q.us.nortel.com [47.142.211.72]) by zrtpd0jh.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id LCSSKXNB; Sun, 15 Jun 2003 10:13:29 -0400 Message-ID: <3EEC7F01.F8C5B5E6@americasm01.nt.com> Date: Sun, 15 Jun 2003 10:13:21 -0400 From: "He Huang" Organization: Nortel Networks X-Mailer: Mozilla 4.72 [en] (X11; I; HP-UX B.10.20 9000/785) X-Accept-Language: en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] RREQ aggregation 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: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, I'm not sure if this question has been addressed in some place of the draft or someone has brought it before. I'm asking it anyway. Think about such a scenario, Scenario: Many clients are connecting to a hot destination (e.g., file server or web server) in ad hoc network. When the destination moves to new location, all connections are broken and all the clients will need to reinitialize a discovery activity for the destination. Question: It is very likely that one intermediate node receives many RREQs from different SRCs but for the same destination. Section 6.5 in AODV draft mentions that all RREQs will be broadcasted except that the same RREQ (with the same SRC IP and unexpired RREQID) has been received before. My suggestion is that, except the same RREQ checking, the intermediate node will check if the destination has been request before it broadcast the RREQ. If it has received an RREQ for the destination within an unexpired period, the intermediate node will only need to record the RREQ info without broadcasting the RREQ. The RREP can still be unicasted to every requesting SRCs. The obvious benefit from such aggregation is to reduce the overhead due to the RREQ flooding. Any comment? He Huang _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 16 02:27: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 CAA03151 for ; Mon, 16 Jun 2003 02:27:35 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5G6R7Y05986 for manet-archive@odin.ietf.org; Mon, 16 Jun 2003 02:27: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 h5G6R6m05983 for ; Mon, 16 Jun 2003 02:27: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 CAA03130 for ; Mon, 16 Jun 2003 02:27:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RnQA-0007cr-00 for manet-web-archive@ietf.org; Mon, 16 Jun 2003 02:24:50 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19RnQ9-0007co-00 for manet-web-archive@ietf.org; Mon, 16 Jun 2003 02:24: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 h5G243a11120; Sun, 15 Jun 2003 22:04: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 h5G23km11107 for ; Sun, 15 Jun 2003 22:03: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 WAA16777 for ; Sun, 15 Jun 2003 22:03:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RjJK-0006TE-00 for manet@ietf.org; Sun, 15 Jun 2003 22:01:30 -0400 Received: from [137.132.31.244] (helo=gandalf.icr.a-star.edu.sg) by ietf-mx with esmtp (Exim 4.12) id 19RjJI-0006TB-00 for manet@ietf.org; Sun, 15 Jun 2003 22:01:29 -0400 Received: from mailer.icr.a-star.edu.sg (mailer.icr.a-star.edu.sg [137.132.31.243]) by gandalf.icr.a-star.edu.sg (8.12.9+Sun/8.12.2) with ESMTP id h5G23wUg026216 for ; Mon, 16 Jun 2003 10:03:58 +0800 (SGT) Received: from bkdom-MTA by mailer.icr.a-star.edu.sg with Novell_GroupWise; Mon, 16 Jun 2003 09:54:18 +0800 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.0.3 Date: Mon, 16 Jun 2003 09:54:03 +0800 From: "Paul Tan Hock Lai" To: , Subject: Re: [manet] RREQ aggregation in AODV Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h5G23km11108 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi Huang He, I also shared your similar idea, as flooding in a wireless media (delay, collision) will definitely degrade the performance. I am currently working on it. Hope to discuss with you further. However, I am also looking into the possibility of using 'aggregation mechanism' for other purposes (e.g. routing information, route maintenace). Cheers, Paul Tan >>> He Huang 15-Jun-03 10:13:21 PM >>> Hello, I'm not sure if this question has been addressed in some place of the draft or someone has brought it before. I'm asking it anyway. Think about such a scenario, Scenario: Many clients are connecting to a hot destination (e.g., file server or web server) in ad hoc network. When the destination moves to new location, all connections are broken and all the clients will need to reinitialize a discovery activity for the destination. Question: It is very likely that one intermediate node receives many RREQs from different SRCs but for the same destination. Section 6.5 in AODV draft mentions that all RREQs will be broadcasted except that the same RREQ (with the same SRC IP and unexpired RREQID) has been received before. My suggestion is that, except the same RREQ checking, the intermediate node will check if the destination has been request before it broadcast the RREQ. If it has received an RREQ for the destination within an unexpired period, the intermediate node will only need to record the RREQ info without broadcasting the RREQ. The RREP can still be unicasted to every requesting SRCs. The obvious benefit from such aggregation is to reduce the overhead due to the RREQ flooding. Any comment? He Huang _______________________________________________ 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 Jun 16 07:40: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 HAA08530 for ; Mon, 16 Jun 2003 07:40:56 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5GBeR127648 for manet-archive@odin.ietf.org; Mon, 16 Jun 2003 07:40:27 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GBeRm27645 for ; Mon, 16 Jun 2003 07:40: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 HAA08521 for ; Mon, 16 Jun 2003 07:40:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RsJP-0001Ri-00 for manet-web-archive@ietf.org; Mon, 16 Jun 2003 07:38:11 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19RsJP-0001Re-00 for manet-web-archive@ietf.org; Mon, 16 Jun 2003 07:38:11 -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 h5G5s3a24949; Mon, 16 Jun 2003 01:54: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 h5G5rim24924 for ; Mon, 16 Jun 2003 01:53: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 BAA20638 for ; Mon, 16 Jun 2003 01:53:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Rmts-0007S7-00 for manet@ietf.org; Mon, 16 Jun 2003 01:51:28 -0400 Received: from cms4.etri.re.kr ([129.254.16.14]) by ietf-mx with esmtp (Exim 4.12) id 19Rmtr-0007S4-00 for manet@ietf.org; Mon, 16 Jun 2003 01:51:27 -0400 Received: from jafymobile (6ants5.etri.re.kr [129.254.112.239]) by cms4.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NALTF8HA; Mon, 16 Jun 2003 14:53:47 +0900 Reply-To: From: "HyunWook Cha" To: Cc: Subject: RE : [manet] RREQ aggregation in AODV Date: Mon, 16 Jun 2003 14:53:25 +0900 Organization: ETRI Message-ID: <000001c333cb$9e1a5790$ef70fe81@jafymobile> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C33417.0E038630" 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.1165 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_01C33417.0E038630 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi He Huang, I think that 'RREQ aggregation' that you mentioned has one important issue to be addressed. As you know, a MANET node replies only once for multiple duplicate RREQs from same source in the route discovery in AODV. So, a RREQ for same destination from different source may not be replied in your scheme, otherwise it should have triggered RREP reply. As a result, it can not guarantee that originator of RREQ receives RREP indicating the shortest path for the destination. In 'route aggregation', gratuitous RREP should be sent for reverse paths towards originators of RREQs for same destination. (These RREPs can be merged into one extended RREP). I recommend some simulation work for the assessment. Regards, Hyunwook Cha ETRI, Korea ------=_NextPart_000_0001_01C33417.0E038630 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi He = Huang,

I = think that ‘RREQ aggregation’ that you mentioned has one important issue to be = addressed.

As = you know, a MANET node replies only once for multiple duplicate RREQs from same source in the route discovery in = AODV.

So, = a RREQ for same destination from different source may not be replied in your = scheme, otherwise it should have triggered RREP reply. =

As = a result, it can not guarantee that originator of RREQ receives RREP indicating the = shortest path for the destination.

In = ‘route aggregation’, gratuitous RREP should be sent for reverse paths towards originators of RREQs for same destination. = (These RREPs can be merged into one extended = RREP).

I = recommend some simulation work for the assessment.

 

Regards,

Hyunwook = Cha

ETRI, = Korea

 

------=_NextPart_000_0001_01C33417.0E038630-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 16 13:34: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 NAA21833 for ; Mon, 16 Jun 2003 13:34:22 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5GHXsC20317 for manet-archive@odin.ietf.org; Mon, 16 Jun 2003 13:33: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 h5GHXrm20314 for ; Mon, 16 Jun 2003 13:33: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 NAA21830 for ; Mon, 16 Jun 2003 13:33:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RxpQ-0004Ff-00 for manet-web-archive@ietf.org; Mon, 16 Jun 2003 13:31:36 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19RxpQ-0004Fc-00 for manet-web-archive@ietf.org; Mon, 16 Jun 2003 13:31: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 h5GEP4a06673; Mon, 16 Jun 2003 10:25: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 h5GEO6m06632 for ; Mon, 16 Jun 2003 10:24: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 KAA15759 for ; Mon, 16 Jun 2003 10:24:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Rurk-0002v0-00 for manet@ietf.org; Mon, 16 Jun 2003 10:21:48 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19Rurj-0002uj-00 for manet@ietf.org; Mon, 16 Jun 2003 10:21:47 -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 h5GENQDi024332 for ; Mon, 16 Jun 2003 10:23:26 -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 h5GENQMD027754 for ; Mon, 16 Jun 2003 10:23:26 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.1.1.32) with SMTP id M2003061610232520785 for ; Mon, 16 Jun 2003 10:23:25 -0400 Message-Id: <5.1.1.5.2.20030616102143.02e655d8@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Mon, 16 Jun 2003 10:23:00 -0400 To: manet@ietf.org From: Joe Macker Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: [manet] Present Vienna Agenda Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , All: At present the MANET WG mtg is scheduled for Wed, July 16 1530-1730. Be aware this is a draft agenda. -JOe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Mon Jun 16 17:34: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 RAA03619 for ; Mon, 16 Jun 2003 17:34:32 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5GLY6t06358 for manet-archive@odin.ietf.org; Mon, 16 Jun 2003 17:34:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5GLY5m06354 for ; Mon, 16 Jun 2003 17:34: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 RAA03614 for ; Mon, 16 Jun 2003 17:34:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19S1Zs-00079L-00 for manet-web-archive@ietf.org; Mon, 16 Jun 2003 17:31:48 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19S1Zr-00079I-00 for manet-web-archive@ietf.org; Mon, 16 Jun 2003 17:31:47 -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 h5GBa3a26538; Mon, 16 Jun 2003 07:36: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 h5GBZtm26508 for ; Mon, 16 Jun 2003 07:35: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 HAA08427 for ; Mon, 16 Jun 2003 07:35:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RsF1-0001Qb-00 for manet@ietf.org; Mon, 16 Jun 2003 07:33:39 -0400 Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx with esmtp (Exim 4.12) id 19RsF0-0001QW-00 for manet@ietf.org; Mon, 16 Jun 2003 07:33:39 -0400 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h5GBZBG26181; Mon, 16 Jun 2003 07:35:13 -0400 (EDT) Received: from zrtpd0jh.us.nortel.com ([47.140.202.34]) by zrtpd0jn.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NATM2MLP; Mon, 16 Jun 2003 07:35:12 -0400 Received: from americasm01.nt.com (wnc1h04q.us.nortel.com [47.142.211.72]) by zrtpd0jh.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id LCSSKX57; Mon, 16 Jun 2003 07:35:11 -0400 Message-ID: <3EEDAB6D.A449BF9A@americasm01.nt.com> Date: Mon, 16 Jun 2003 07:35:11 -0400 From: "He Huang" Organization: Nortel Networks X-Mailer: Mozilla 4.72 [en] (X11; I; HP-UX B.10.20 9000/785) X-Accept-Language: en MIME-Version: 1.0 To: jafy@etri.re.kr CC: manet@ietf.org Subject: Re: RE : [manet] RREQ aggregation in AODV References: <000001c333cb$9e1a5790$ef70fe81@jafymobile> Content-Type: multipart/alternative; boundary="------------7AC0BF7339864F779C1A0CBE" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------7AC0BF7339864F779C1A0CBE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, HyunWook, See my comment below, HyunWook Cha wrote: > Hi He Huang, > > I think that `RREQ aggregation' that you mentioned has one important > issue to be addressed. > > As you know, a MANET node replies only once for multiple > duplicate RREQs from same source in the route discovery in AODV. > > Yes, it is true for the same source. > > > > So, a RREQ for same destination from different source may not be > replied in your scheme, otherwise it should have triggered RREP > reply. > > > It is not true. An RREPs will be generated if one RREQ from different > source is received. See section 6.5 in the draft. > > > > As a result, it can not guarantee that originator of RREQ receives > RREP indicating the shortest path for the destination. > > In `route aggregation', gratuitous RREP should be sent for reverse > paths towards originators of RREQs for same destination. (These RREPs > can be merged into one extended RREP). > > If I understand correctly, gratuitous RREP is sent to the destination > of RREQ from one intermediate node. No change in generating gratuitous > reply . > No merged RREP can be assumed at this point. Anyway, RREQ aggregation > doesnot affect the existing process of gratuitous RREP. > > > > > I recommend some simulation work for the assessment. > > Regards, > > Hyunwook Cha > > ETRI, Korea > BR --------------7AC0BF7339864F779C1A0CBE Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, HyunWook,

See my comment below,

HyunWook Cha wrote:

Hi He Huang,

I think that `RREQ aggregation' that you mentioned has one important issue to be addressed.

As you know, a MANET node replies only once for multiple duplicate RREQs from same source in the route discovery in AODV.

Yes, it is true for the same source.

 
 

So, a RREQ for same destination from different source may not be replied in your scheme, otherwise it should have triggered RREP reply. 

 

It is not true. An RREPs will be generated if one RREQ from different source is received. See section 6.5 in the draft.

 
 

As a result, it can not guarantee that originator of RREQ receives RREP indicating the shortest path for the destination.

In `route aggregation', gratuitous RREP should be sent for reverse paths towards originators of RREQs for same destination. (These RREPs can be merged into one extended RREP).

If I understand correctly, gratuitous RREP is sent to the destination of RREQ from one intermediate node. No change in generating gratuitous reply .

No merged RREP can be assumed at this point.  Anyway, RREQ aggregation doesnot affect the existing process of gratuitous RREP.
 
 
 

I recommend some simulation work for the assessment.

Regards,

Hyunwook Cha

ETRI, Korea

BR --------------7AC0BF7339864F779C1A0CBE-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 17 01:13: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 BAA17200 for ; Tue, 17 Jun 2003 01:13:12 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5H5Ch307174 for manet-archive@odin.ietf.org; Tue, 17 Jun 2003 01:12:43 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H5Chm07171 for ; Tue, 17 Jun 2003 01:12:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA17183 for ; Tue, 17 Jun 2003 01:12:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19S8jh-0002fZ-00 for manet-web-archive@ietf.org; Tue, 17 Jun 2003 01:10:25 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19S8jh-0002fW-00 for manet-web-archive@ietf.org; Tue, 17 Jun 2003 01:10: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 h5GN53a12889; Mon, 16 Jun 2003 19:05: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 h5GN4Dm12851 for ; Mon, 16 Jun 2003 19:04: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 TAA07857 for ; Mon, 16 Jun 2003 19:04:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19S2z5-00008L-00 for manet@ietf.org; Mon, 16 Jun 2003 19:01:55 -0400 Received: from cms4.etri.re.kr ([129.254.16.14]) by ietf-mx with esmtp (Exim 4.12) id 19S2z4-00008I-00 for manet@ietf.org; Mon, 16 Jun 2003 19:01:54 -0400 Received: from jafywinxp (pd412h.etri.re.kr [129.254.112.174]) by cms4.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NALTF02W; Tue, 17 Jun 2003 08:04:14 +0900 Reply-To: From: "HyunWook Cha" To: Cc: Subject: RE: RE : [manet] RREQ aggregation in AODV Date: Tue, 17 Jun 2003 08:04:09 +0900 Message-ID: <000801c3345b$9e3cd140$ae70fe81@jafywinxp> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <3EEDAB6D.A449BF9A@americasm01.nt.com> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi He Huang, I think my explanation in previous mail is not sufficient. See my revised comments, below. Hi, HyunWook, See my comment below, HyunWook Cha wrote: =>Hi He Huang, =>I think that `RREQ aggregation' that you mentioned has one important issue to be addressed. =>As you know, a MANET node replies only once for multiple duplicate RREQs from same source in the route discovery in AODV. Yes, it is true for the same source. =>So, a RREQ for same destination from different source may not be replied in your scheme, otherwise it should have triggered RREP reply. It is not true. An RREPs will be generated if one RREQ from different source is received. See section 6.5 in the draft. ==>For example, let's assume multiple paths from one source to one destination can be possilbe in current topology. The source originates RREQ and then RREQ is forwarded to the destination or intermediate nodes which knows route for the destination by flooding. In any case, a MANET node replies only once for duplicate RREQs from the source. So among multiple paths, only one path which is the shortest from the source's point of view will be established. In the meanwhile, another node does route discovery for the same destination. In your scheme, an intermediate node which receives RREQ from the second source and already received RREQ from the first source does not forward the RREQ from the second source. Think about this case where this intermediate node is not on the shortest path from the first source to the destination. Then, RREP from the destination may not be received by this node. Thus, RREQ from the first souce as well as the second source may not be replied at this node. In this case, it is possilble that this node is on the shortest path from the second source to the destination. If this node has forwarded RREP from the second source, the second souce should have received RREP with route information about the shortest path. =>As a result, it can not guarantee that originator of RREQ receives RREP indicating the shortest path for the destination. =>In `route aggregation', gratuitous RREP should be sent for reverse paths towards originators of RREQs for same destination. (These RREPs can be merged into one extended RREP). If I understand correctly, gratuitous RREP is sent to the destination of RREQ from one intermediate node. No change in generating gratuitous reply . No merged RREP can be assumed at this point. Anyway, RREQ aggregation doesnot affect the existing process of gratuitous RREP. ==>I mentioned gratuitous RREP because you had not mentioned it. And I mean by the extended gratuitous RREP that multiple unicast g-RREP towards the same destination(the originator of RREP) can be merged into just one g-RREP for just optimization. =>I recommend some simulation work for the assessment. =>Regards, =>Hyunwook Cha =>ETRI, Korea BR Regards, HyunWook Cha _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 17 02:30: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 CAA00509 for ; Tue, 17 Jun 2003 02:30:29 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5H6U1I24787 for manet-archive@odin.ietf.org; Tue, 17 Jun 2003 02:30:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H6U0m24773 for ; Tue, 17 Jun 2003 02:30: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 CAA00485 for ; Tue, 17 Jun 2003 02:29:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19S9wU-000357-00 for manet-web-archive@ietf.org; Tue, 17 Jun 2003 02:27:42 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19S9wT-000354-00 for manet-web-archive@ietf.org; Tue, 17 Jun 2003 02:27:41 -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 h5GEI4a06298; Mon, 16 Jun 2003 10:18: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 h5GEHam06252 for ; Mon, 16 Jun 2003 10:17: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 KAA15548 for ; Mon, 16 Jun 2003 10:17:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RulT-0002sd-00 for manet@ietf.org; Mon, 16 Jun 2003 10:15:19 -0400 Received: from cms4.etri.re.kr ([129.254.16.14]) by ietf-mx with esmtp (Exim 4.12) id 19RulS-0002sa-00 for manet@ietf.org; Mon, 16 Jun 2003 10:15:18 -0400 Received: from jafywinxp (pd412h.etri.re.kr [129.254.112.174]) by cms4.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id NALTF9HJ; Mon, 16 Jun 2003 23:17:34 +0900 Reply-To: From: "HyunWook Cha" To: Cc: Subject: RE: RE : [manet] RREQ aggregation in AODV Date: Mon, 16 Jun 2003 23:17:38 +0900 Message-ID: <000001c33412$0a4b7980$ae70fe81@jafywinxp> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C3345D.7A332180" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <3EEDAB6D.A449BF9A@americasm01.nt.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C3345D.7A332180 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi He Huang, I think my explanation in previous mail is not sufficient. See my revised comments, below. -----Original Message----- From: huanghe@nortelnetworks.com [mailto:huanghe@nortelnetworks.com] Sent: Monday, June 16, 2003 8:35 PM To: jafy@etri.re.kr Cc: manet@ietf.org Subject: Re: RE : [manet] RREQ aggregation in AODV Hi, HyunWook, See my comment below, HyunWook Cha wrote: Hi He Huang, I think that `RREQ aggregation' that you mentioned has one important issue to be addressed. As you know, a MANET node replies only once for multiple duplicate RREQs from same source in the route discovery in AODV. Yes, it is true for the same source. So, a RREQ for same destination from different source may not be replied in your scheme, otherwise it should have triggered RREP reply. It is not true. An RREPs will be generated if one RREQ from different source is received. See section 6.5 in the draft. For example, let's assume multiple paths from one source to one destination can be possilbe in current topology. The source originates RREQ and then RREQ is forwarded to the destination or intermediate nodes which knows route for the destination by flooding. In any case, a MANET node replies only once for duplicate RREQs from the source. So among multiple paths, only one path which is the shortest from the source's point of view will be established. In the meanwhile, another node does route discovery for the same destination. In your scheme, an intermediate node which receives RREQ from the second source and already received RREQ from the first source does not forward the RREQ from the second source. Think about this case where this intermediate node is not on the shortest path from the first source to the destination. Then, RREP from the destination may not be received by this node. Thus, RREQ from the first souce as well as the second source may not be replied at this node. In this case, it is possilble that this node is on the shortest path from the second source to the destination. If this node has forwarded RREP from the second source, the second souce should have received RREP with route information about the shortest path. As a result, it can not guarantee that originator of RREQ receives RREP indicating the shortest path for the destination. In `route aggregation', gratuitous RREP should be sent for reverse paths towards originators of RREQs for same destination. (These RREPs can be merged into one extended RREP). If I understand correctly, gratuitous RREP is sent to the destination of RREQ from one intermediate node. No change in generating gratuitous reply . No merged RREP can be assumed at this point. Anyway, RREQ aggregation doesnot affect the existing process of gratuitous RREP. I mentioned gratuitous RREP because you had not mentioned it. And I mean by the extended gratuitous RREP that multiple unicast g-RREP towards the same destination(the originator of RREP) can be merged into just one g-RREP for just optimization. I recommend some simulation work for the assessment. Regards, Hyunwook Cha ETRI, Korea BR ------=_NextPart_000_0001_01C3345D.7A332180 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 메시지
Hi He=20 Huang,
 
I think=20 my explanation in previous mail is not sufficient. =
See my=20 revised comments, below.
 
 
-----Original Message-----
From: = huanghe@nortelnetworks.com=20 [mailto:huanghe@nortelnetworks.com]
Sent: Monday, June 16, = 2003=20 8:35 PM
To: jafy@etri.re.kr
Cc:=20 manet@ietf.org
Subject: Re: RE : [manet] RREQ aggregation in = AODV

Hi, HyunWook,=20

See my comment below,=20

HyunWook Cha wrote:=20

Hi He=20 Huang,

I think that `RREQ=20 aggregation' that you = mentioned=20 has one important issue to be addressed.=20

As you know, a MANET node replies only = once for=20 multiple duplicate RREQs from same = source in=20 the route discovery in AODV.=20

Yes, it is true for the same source.=20

  =
  =

So, a RREQ for same destination from = different source=20 may not be replied in your scheme, otherwise it should have = triggered RREP=20 reply. =20

  =

It is not true. An RREPs will be generated if one RREQ = from=20 different source is received. See section 6.5 in the = draft.=20

For example,=20 let's assume multiple paths from one source to one = destination can=20 be possilbe in current topology.
The source=20 originates RREQ and then RREQ is forwarded to the destination or=20 intermediate nodes which knows route for the destination by = flooding. In any=20 case, a MANET node replies only once for duplicate RREQs from the = source. So=20 among multiple paths, only one path which is the shortest = from the=20 source's point of view will be established. In the=20 meanwhile, another node does route discovery for the same=20 destination. In your scheme, an intermediate node which = receives RREQ=20 from the second source and already received RREQ from=20 the first source does not forward the RREQ from the = second=20 source. 
Think about this=20 case where this intermediate node is not on the = shortest path=20 from the first source to the destination. Then, RREP from the=20 destination may not be received by this node. Thus, = RREQ from=20 the first souce as well as the second source may not be replied at = this=20 node. In this case, it is possilble that this node is on = the=20 shortest path from the second source to the=20 destination. If this node has forwarded RREP from the = second=20 source, the second souce should have=20 received RREP with route information about the = shortest=20 path.
  =

As a result, it can not guarantee that = originator of=20 RREQ receives RREP indicating the shortest path for the=20 destination.=20

In `route=20 aggregation', = gratuitous RREP=20 should be sent for reverse paths towards originators of RREQs for same destination. (These RREPs can be merged into one extended=20 RREP).=20

If = I understand=20 correctly, gratuitous RREP is sent to the destination of RREQ = from one=20 intermediate node. No change in generating gratuitous reply .=20

No merged = RREP can=20 be assumed at this point.  Anyway, RREQ aggregation doesnot = affect the=20 existing process of gratuitous RREP.
 
I mentioned gratuitous RREP because you had = not=20 mentioned it. And I mean by the extended gratuitous=20 RREP that multiple unicast
g-RREP towards the same destination(the = originator of RREP)=20 can be merged into just one g-RREP for just=20 optimization.
  =

I recommend some simulation work for the=20 assessment.=20

Regards,=20

Hyunwook = Cha=20

ETRI, Korea<= SPAN=20 lang=3DEN-US>=20

BR=20
------=_NextPart_000_0001_01C3345D.7A332180-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailnull@www1.ietf.org Tue Jun 17 04:23: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 EAA03587 for ; Tue, 17 Jun 2003 04:23:45 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5H8NGO05232 for manet-archive@odin.ietf.org; Tue, 17 Jun 2003 04:23:16 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H8NGm05229 for ; Tue, 17 Jun 2003 04:23: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 EAA03569 for ; Tue, 17 Jun 2003 04:23:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SBi6-000447-00 for manet-web-archive@ietf.org; Tue, 17 Jun 2003 04:20:58 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19SBi5-000444-00 for manet-web-archive@ietf.org; Tue, 17 Jun 2003 04:20: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 h5H5C3a07139; Tue, 17 Jun 2003 01:12:03 -0400 Received: from ietf.org (lists.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5H5Bnm07112 for ; Tue, 17 Jun 2003 01:11: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 BAA17159 for ; Tue, 17 Jun 2003 01:11:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19S8ip-0002fJ-00 for manet@ietf.org; Tue, 17 Jun 2003 01:09:31 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19S8ip-0002fG-00 for manet@ietf.org; Tue, 17 Jun 2003 01:09:31 -0400 Received: from paulnb (paul3.etri.re.kr [129.254.112.196]) by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h5H57p717520; Tue, 17 Jun 2003 14:07:52 +0900 (KST) Message-ID: <017601c3348c$73b91100$c470fe81@etri.re.kr> From: "Jaehoon Jeong" To: "Joe Macker" Cc: "MANET WG" References: <5.1.1.5.2.20030616102143.02e655d8@pop.itd.nrl.navy.mil> Subject: Re: [manet] Present Vienna Agenda Date: Tue, 17 Jun 2003 13:53:52 +0900 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id h5H5Bnm07113 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hi, Joe. As I know, in this meeting, manet wg is going to define a further focused problem statement according to milestones. If it is right, I would like to discuss manet addressing in this meeting. How about it? I submitted a new draft about ad hoc IP address autoconfiguration. http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-00.txt Thanks. Jaehoon ----- Original Message ----- From: "Joe Macker" To: Sent: Monday, June 16, 2003 11:23 PM Subject: [manet] Present Vienna Agenda > All: > > At present the MANET WG mtg is scheduled for Wed, July 16 1530-1730. > Be aware this is a draft agenda. > > -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 Tue Jun 17 12:27: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 MAA25428 for ; Tue, 17 Jun 2003 12:27:18 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5HGQoH11832 for manet-archive@odin.ietf.org; Tue, 17 Jun 2003 12:26:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5HGQom11828 for ; Tue, 17 Jun 2003 12:26: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 MAA25387 for ; Tue, 17 Jun 2003 12:26:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SJG4-0001WH-00 for manet-web-archive@ietf.org; Tue, 17 Jun 2003 12:24:32 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19SJG3-0001WE-00 for manet-web-archive@ietf.org; Tue, 17 Jun 2003 12:24: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 h5HBL3a18693; Tue, 17 Jun 2003 07:21: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 h5HBKWm18661 for ; Tue, 17 Jun 2003 07:20:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07283 for ; Tue, 17 Jun 2003 07:20:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SETe-00050L-00 for manet@ietf.org; Tue, 17 Jun 2003 07:18:14 -0400 Received: from mail.cit.ie ([157.190.14.15]) by ietf-mx with esmtp (Exim 4.12) id 19SETe-0004zt-00 for manet@ietf.org; Tue, 17 Jun 2003 07:18:14 -0400 Received: from eeb285w2ksr (unverified [157.190.81.169]) by cit.ie (Rockliffe SMTPRA 5.3.4) with SMTP id for ; Tue, 17 Jun 2003 12:19:28 +0100 From: "susan rea" To: "manet" Date: Tue, 17 Jun 2003 12:20:19 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal Content-Transfer-Encoding: 7bit Subject: [manet] DSR caching & gratuitous route replies Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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, When a node implementing DSR & operating in promiscuous receive mode overhears a packet containing a soure route from which it can generate a gratuitous route reply does this node then add this new shorter route to its cache and does it also cache routes based on the original source route? thanks, Susan -------------------Legal Disclaimer--------------------------------------- The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt. ---------------------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jun 17 14:15: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 OAA29863 for ; Tue, 17 Jun 2003 14:15:54 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5HIFP612726 for manet-archive@odin.ietf.org; Tue, 17 Jun 2003 14:15:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19SKlG-0001rr-39 for manet-web-archive@optimus.ietf.org; Tue, 17 Jun 2003 14:00: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 OAA28672 for ; Tue, 17 Jun 2003 14:00:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SKj0-0002Ka-00 for manet-web-archive@ietf.org; Tue, 17 Jun 2003 13:58:30 -0400 Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19SKiz-0002KX-00 for manet-web-archive@ietf.org; Tue, 17 Jun 2003 13:58:29 -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 h5HGL9a11596; Tue, 17 Jun 2003 12:21: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 h5HGKFm11547 for ; Tue, 17 Jun 2003 12: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 MAA25233 for ; Tue, 17 Jun 2003 12:20:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SJ9g-0001T0-00 for manet@ietf.org; Tue, 17 Jun 2003 12:17:56 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19SJ9f-0001Sw-00 for manet@ietf.org; Tue, 17 Jun 2003 12:17:55 -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 h5HGJZDi021043; Tue, 17 Jun 2003 12:19:35 -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 h5HGJYMD028593; Tue, 17 Jun 2003 12:19:35 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.1.1.32) with SMTP id M2003061712193325374 ; Tue, 17 Jun 2003 12:19:34 -0400 Message-Id: <5.1.1.5.2.20030617100830.03572fc8@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Tue, 17 Jun 2003 12:19:43 -0400 To: "Jaehoon Jeong" From: Joe Macker Subject: Re: [manet] Present Vienna Agenda Cc: "MANET WG" In-Reply-To: <017601c3348c$73b91100$c470fe81@etri.re.kr> References: <5.1.1.5.2.20030616102143.02e655d8@pop.itd.nrl.navy.mil> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 01:53 PM 6/17/2003 +0900, Jaehoon Jeong wrote: >Hi, Joe. > >As I know, in this meeting, manet wg is going to define a further focused problem statement >according to milestones. >If it is right, I would like to discuss manet addressing in this meeting. >How about it? >I submitted a new draft about ad hoc IP address autoconfiguration. > http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-00.txt >Thanks. The EXP draft submissions took a little extra time with a few updates related to WG chair and AD nits. Several of those (OLSR, TBRPF, DSR) are still in early review progress, but they have all now been submitted for EXPERIMENTAL review. We only have 2 hour meeting and here is how I see things. I see the first order of business is to quickly address and review EXP progress and any needed action items. The second order of business is to refine the problems to be addressed and to refine the strategy to develop further, focused STANDARDS track work on routing protocols. I am willing to put aside a small timeslot (10-15 min) to discuss autoconf issues (mainly make people aware of related drafts, pragmatic approaches already working, scenario issues,etc).. -joe >Jaehoon > > >----- Original Message ----- >From: "Joe Macker" >To: >Sent: Monday, June 16, 2003 11:23 PM >Subject: [manet] Present Vienna Agenda > > >> All: >> >> At present the MANET WG mtg is scheduled for Wed, July 16 1530-1730. >> Be aware this is a draft agenda. >> >> -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 exim@www1.ietf.org Wed Jun 18 08:15: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 IAA29276 for ; Wed, 18 Jun 2003 08:15:45 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5ICFGj23784 for manet-archive@odin.ietf.org; Wed, 18 Jun 2003 08:15:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19SbqO-0006BX-3V for manet-web-archive@optimus.ietf.org; Wed, 18 Jun 2003 08: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 IAA29265 for ; Wed, 18 Jun 2003 08:15:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Sbo8-0002Vn-00 for manet-web-archive@ietf.org; Wed, 18 Jun 2003 08:12:56 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Sbo7-0002Vj-00 for manet-web-archive@ietf.org; Wed, 18 Jun 2003 08:12:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Sbq9-0006AP-MP; Wed, 18 Jun 2003 08:15:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19SbpV-00069q-Cs for manet@optimus.ietf.org; Wed, 18 Jun 2003 08:14: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 IAA29243 for ; Wed, 18 Jun 2003 08:14:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SbnF-0002VX-00 for manet@ietf.org; Wed, 18 Jun 2003 08:12:01 -0400 Received: from law15-f15.law15.hotmail.com ([64.4.23.15] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19SbnF-0002VT-00 for manet@ietf.org; Wed, 18 Jun 2003 08:12:01 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 18 Jun 2003 05:13:49 -0700 Received: from 163.121.64.164 by lw15fd.law15.hotmail.msn.com with HTTP; Wed, 18 Jun 2003 12:13:45 GMT X-Originating-IP: [163.121.64.164] X-Originating-Email: [reh_elmayet@hotmail.com] From: "reham elmayet" To: manet@ietf.org Date: Wed, 18 Jun 2003 12:13:45 +0000 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 18 Jun 2003 12:13:49.0113 (UTC) FILETIME=[12F6BA90:01C33593] 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: ,
Hello,
I want to ask about  what are the adaptive routing protocols for MANETs and If there are any links can help me to understand them.
Also, can I get the ns-2 to work under windows for free ?
regards,
Reham

MSN 8 with e-mail virus protection service: 2 months FREE* _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jun 18 14:41:32 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 OAA20489 for ; Wed, 18 Jun 2003 14:41:32 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5IIf5A29888 for manet-archive@odin.ietf.org; Wed, 18 Jun 2003 14:41:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ShPV-0006Pr-3w for manet-web-archive@optimus.ietf.org; Wed, 18 Jun 2003 14:11: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 OAA19155 for ; Wed, 18 Jun 2003 14:11:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ShND-0007WY-00 for manet-web-archive@ietf.org; Wed, 18 Jun 2003 14:09:31 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ShND-0007WV-00 for manet-web-archive@ietf.org; Wed, 18 Jun 2003 14:09:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Sgmw-0004J7-0d; Wed, 18 Jun 2003 13:32:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19SgHN-0002sM-94 for manet@optimus.ietf.org; Wed, 18 Jun 2003 12:59: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 MAA16048 for ; Wed, 18 Jun 2003 12:59:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19SgF6-0006gM-00 for manet@ietf.org; Wed, 18 Jun 2003 12:57:04 -0400 Received: from massive.its.bldrdoc.gov ([132.163.64.201]) by ietf-mx with esmtp (Exim 4.12) id 19SgF5-0006gF-00 for manet@ietf.org; Wed, 18 Jun 2003 12:57:04 -0400 Received: from andy (localhost.0.0.127.in-addr.arpa [127.0.0.1] (may be forged)) by massive.its.bldrdoc.gov (8.12.8p1/8.12.8) with ESMTP id h5IGwkxo013238; Wed, 18 Jun 2003 10:58:51 -0600 (MDT) From: "Andrew Thiessen" To: "'reham elmayet'" Cc: Subject: RE: [manet] (no subject) Date: Wed, 18 Jun 2003 10:57:47 -0600 Message-ID: <000201c335ba$bf096900$4841a384@andy> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0003_01C33588.746EF900" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_0003_01C33588.746EF900 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reham, Below are two articles that will provide a good introduction into routing protocols for MANETs. Scalable routing protocols for mobile ad hoc networks Xiaoyan Hong; Kaixin Xu; Gerla, M.; Network, IEEE , Volume: 16 Issue: 4 , July-Aug. 2002 Page(s): 11 -21 A review of current routing protocols for ad hoc mobile wireless networks Royer, E.M.; Chai-Keong Toh; Personal Communications, IEEE [see also IEEE Wireless Communications] , Volume: 6 Issue: 2 , April 1999 Page(s): 46 -55 In addition, the following is a link to getting NS-2 working under Windows. http://www.isi.edu/nsnam/ns/ns-build.html Andrew Thiessen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of reham elmayet Sent: Wednesday, June 18, 2003 6:14 AM To: manet@ietf.org Subject: [manet] (no subject) Hello, I want to ask about what are the adaptive routing protocols for MANETs and If there are any links can help me to understand them. Also, can I get the ns-2 to work under windows for free ? regards, Reham _____ MSN 8 with e-mail virus protection service: 2 months FREE* _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet ------=_NextPart_000_0003_01C33588.746EF900 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Reham,

 

Below are two articles = that will provide a good introduction into routing protocols for = MANETs.

 

Scalable routing protocols for mobile ad hoc networks
Xiaoyan Hong; Kaixin Xu; Gerla, = M.;
Network, IEEE , Volume: = 16 Issue: = 4 , July-Aug. = 2002
Page(s): 11 -21

 

A review of current routing protocols for ad = hoc mobile wireless networks
Royer, E.M.; Chai-Keong = Toh;
Personal Communications, IEEE [see also IEEE = Wireless Communications] , Volume: 6 = Issue: = 2 , April = 1999
Page(s): 46 -55

 

In addition, the following is a link to getting NS-2 = working under Windows.

 

http://www.isi.edu/nsn= am/ns/ns-build.html

 

 

Andrew Thiessen

 

-----Original = Message-----
From: = manet-admin@ietf.org [mailto:manet-admin@ietf.org] On = Behalf Of reham elmayet
Sent: Wednesday, June 18, 2003 6:14 = AM
To: manet@ietf.org
Subject: [manet] (no = subject)

 

Hello,

I want to ask about  what are the = adaptive routing protocols for MANETs and If there are any links can help me to understand them.

Also, can I get the ns-2 to work under = windows for free ?

regards,

Reham


MSN 8 with e-mail virus protection service: 2 months FREE*

_______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet ------=_NextPart_000_0003_01C33588.746EF900-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 19 11:36:50 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 LAA25790 for ; Thu, 19 Jun 2003 11:36:50 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5JFaMT30609 for manet-archive@odin.ietf.org; Thu, 19 Jun 2003 11:36:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19T1SY-0007xc-PT for manet-web-archive@optimus.ietf.org; Thu, 19 Jun 2003 11:36: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 LAA25732 for ; Thu, 19 Jun 2003 11:36:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19T1QH-0005os-00 for manet-web-archive@ietf.org; Thu, 19 Jun 2003 11:34:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19T1QG-0005oo-00 for manet-web-archive@ietf.org; Thu, 19 Jun 2003 11:34:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19T1SE-0007w7-O5; Thu, 19 Jun 2003 11:36:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19T1RW-0007vE-Nn for manet@optimus.ietf.org; Thu, 19 Jun 2003 11:35: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 LAA25704 for ; Thu, 19 Jun 2003 11:35:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19T1PE-0005oB-00 for manet@ietf.org; Thu, 19 Jun 2003 11:32:56 -0400 Received: from mta10.adelphia.net ([64.8.50.202]) by ietf-mx with esmtp (Exim 4.12) id 19T1PE-0005nw-00 for manet@ietf.org; Thu, 19 Jun 2003 11:32:56 -0400 Received: from angel ([68.70.61.77]) by mta10.adelphia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with SMTP id <20030619153445.GXQZ1347.mta10.adelphia.net@angel>; Thu, 19 Jun 2003 11:34:45 -0400 From: "George Hadjichristofi" To: Cc: "George Hadjichristofi" Date: Thu, 19 Jun 2003 11:34:40 -0400 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00BD_01C33656.C5CC8C30" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-reply-to: Subject: [manet] IP address --unique ID Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_00BD_01C33656.C5CC8C30 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, How do new nodes coming into a manet get their ip address? Is it usually pre-assigned or assigned dynamically? How can a node in a Manet be uniquely identified, if the IP and MAC address can be spoofed? I would appreciate any help on these questions. Thank you George Hadjichristofi *********************************************************** George C. Hadjichristofi Graduate Student Bradley Department of Electrical and Computer Engineering Virginia Tech,Blacksburg,VA 24061,U.S.A TEL:(540)-951-8936 *********************************************************** ------=_NextPart_000_00BD_01C33656.C5CC8C30 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
How do=20 new nodes coming into a manet get their ip = address?
Is it=20 usually pre-assigned or assigned dynamically?
 
How=20 can a node in a Manet be uniquely identified, if the IP and MAC address = can be=20 spoofed?
 
I=20 would appreciate any help on these questions.
 
Thank=20 you
George=20 Hadjichristofi
 
 
 

***********************************************************
G= eorge C.=20 Hadjichristofi
Graduate Student
Bradley Department of Electrical = and=20 Computer Engineering
Virginia Tech,Blacksburg,VA=20 24061,U.S.A
TEL:(540)-951-8936 
******************************= *****************************=20


 
------=_NextPart_000_00BD_01C33656.C5CC8C30-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jun 20 05: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 FAA22514 for ; Fri, 20 Jun 2003 05:11:49 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5K9BLj18553 for manet-archive@odin.ietf.org; Fri, 20 Jun 2003 05:11:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19THvV-0004pA-Ik for manet-web-archive@optimus.ietf.org; Fri, 20 Jun 2003 05:11:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22493 for ; Fri, 20 Jun 2003 05:11:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19THt9-0000tr-00 for manet-web-archive@ietf.org; Fri, 20 Jun 2003 05:08:55 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19THt8-0000to-00 for manet-web-archive@ietf.org; Fri, 20 Jun 2003 05:08:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19THvC-0004ef-8j; Fri, 20 Jun 2003 05:11:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19THuD-0004Xa-Cv for manet@optimus.ietf.org; Fri, 20 Jun 2003 05: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 FAA22459 for ; Fri, 20 Jun 2003 05:09:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19THrr-0000tW-00 for manet@ietf.org; Fri, 20 Jun 2003 05:07:35 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19THrq-0000tP-00 for manet@ietf.org; Fri, 20 Jun 2003 05:07:34 -0400 Received: from paulnb (paul3.etri.re.kr [129.254.112.196]) by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h5K9MU905614; Fri, 20 Jun 2003 18:22:30 +0900 (KST) Message-ID: <007d01c3370b$83f31620$c470fe81@etri.re.kr> From: "Jaehoon Jeong" To: "George Hadjichristofi" Cc: "MANET WG" , "autonet" References: Subject: Re: [manet] IP address --unique ID Date: Fri, 20 Jun 2003 18:08:28 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_007A_01C33756.F355D6B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------=_NextPart_000_007A_01C33756.F355D6B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 aW5saW5lcyA6LSkNCiAgLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCiAgRnJvbTogR2Vv cmdlIEhhZGppY2hyaXN0b2ZpIA0KICBUbzogbWFuZXRAaWV0Zi5vcmcgDQogIENjOiBHZW9yZ2Ug SGFkamljaHJpc3RvZmkgDQogIFNlbnQ6IEZyaWRheSwgSnVuZSAyMCwgMjAwMyAxMjozNCBBTQ0K ICBTdWJqZWN0OiBbbWFuZXRdIElQIGFkZHJlc3MgLS11bmlxdWUgSUQNCg0KDQogIEhpLA0KDQog IEhvdyBkbyBuZXcgbm9kZXMgY29taW5nIGludG8gYSBtYW5ldCBnZXQgdGhlaXIgaXAgYWRkcmVz cz8NCiAgSXMgaXQgdXN1YWxseSBwcmUtYXNzaWduZWQgb3IgYXNzaWduZWQgZHluYW1pY2FsbHk/ DQogICANCiAgIC0+IEFjdHVhbGx5LCBtb3N0IG9mIG1hbmV0IG5vZGVzIGdldCB0aGVpciBhZGRy ZXNzIHRocm91Z2ggbWFudWFsIGNvbmZpZ3VyYXRpb24uDQogICAgICAgIFRoZXJlIGFyZSBtYW55 IHNjaGVtZXMgZm9yIGFkZHJlc3NpbmcgbWFuZXQgbm9kZSBhdXRvbWF0aWNhbGx5Lg0KICAgICAg ICBBbW9uZyB0aGVtLCBJIHN1Z2dlc3RlZCBvbmUgcmVjZW50bHkgYXMgbWFuZXQgaW50ZXJuZXQt ZHJhZnQgZW50aXRsZWQNCiAgICAgICAgIkFkIEhvYyBJUCBBZGRyZXNzIEF1dG9jb25maWd1cmF0 aW9uIi4NCiAgICAgICAgWW91IGNhbiBmaW5kIHRoZSBkcmFmdCBpbiB0aGUgZm9sbG93aW5nIHNp dGU7DQogICAgICAgICBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1q ZW9uZy1hZGhvYy1pcC1hZGRyLWF1dG9jb25mLTAwLnR4dA0KDQogIEhvdyBjYW4gYSBub2RlIGlu IGEgTWFuZXQgYmUgdW5pcXVlbHkgaWRlbnRpZmllZCwgaWYgdGhlIElQIGFuZCBNQUMgYWRkcmVz cyBjYW4gYmUgc3Bvb2ZlZD8NCg0KICAgIC0+IEluIG15IHNjaGVtZSwgYSBtYW5ldCBub2RlIHRo YXQgZmluZHMgYW4gSVAgYWRkcmVzcyBkdXBsaWNhdGUgd2l0aCBpdHMgb3duIGFkZHJlc3MsDQog ICAgICAgICB0aGUgbm9kZSBzZWxlY3RzIGFub3RoZXIgYWRkcmVzcyBhbmQgdHJpZXMgdG8gYXV0 b2NvbmZpZ3VyZSB0aGUgbmV3IG9uZS4NCiAgICAgICAgIEZvciBNQUMgYWRkcmVzcywgdGhlcmUg aXMgbm8gY29uc2lkZXJhdGlvbi4NCg0KICAgICAgICAgL0phZWhvb24NCg0KICBJIHdvdWxkIGFw cHJlY2lhdGUgYW55IGhlbHAgb24gdGhlc2UgcXVlc3Rpb25zLg0KDQogIFRoYW5rIHlvdQ0KICBH ZW9yZ2UgSGFkamljaHJpc3RvZmkNCg0KDQoNCiAgKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioNCiAgR2VvcmdlIEMuIEhhZGppY2hyaXN0 b2ZpDQogIEdyYWR1YXRlIFN0dWRlbnQNCiAgQnJhZGxleSBEZXBhcnRtZW50IG9mIEVsZWN0cmlj YWwgYW5kIENvbXB1dGVyIEVuZ2luZWVyaW5nDQogIFZpcmdpbmlhIFRlY2gsQmxhY2tzYnVyZyxW QSAyNDA2MSxVLlMuQQ0KICBURUw6KDU0MCktOTUxLTg5MzYgDQogICoqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqIA0KDQoNCiAgICAg ------=_NextPart_000_007A_01C33756.F355D6B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWlzby04ODU5LTEiPg0KPE1FVEEgY29udGVudD0iTVNIVE1M IDYuMDAuMjgwMC4xMTA2IiBuYW1lPUdFTkVSQVRPUj4NCjxTVFlMRT48L1NUWUxFPg0KPC9IRUFE Pg0KPEJPRFkgYmdDb2xvcj0jZmZmZmZmPg0KPERJVj48Rk9OVCBmYWNlPSYjNDQ0MDQ7JiM0NzU0 ODsgc2l6ZT0yPmlubGluZXMgOi0pPC9GT05UPjwvRElWPg0KPEJMT0NLUVVPVEUgZGlyPWx0ciAN CnN0eWxlPSJQQURESU5HLVJJR0hUOiAwcHg7IFBBRERJTkctTEVGVDogNXB4OyBNQVJHSU4tTEVG VDogNXB4OyBCT1JERVItTEVGVDogIzAwMDAwMCAycHggc29saWQ7IE1BUkdJTi1SSUdIVDogMHB4 Ij4NCiAgPERJViBzdHlsZT0iRk9OVDogMTBwdCAmIzQ0NDA0OyYjNDc1NDg7Ij4tLS0tLSBPcmln aW5hbCBNZXNzYWdlIC0tLS0tIDwvRElWPg0KICA8RElWIA0KICBzdHlsZT0iQkFDS0dST1VORDog I2U0ZTRlNDsgRk9OVDogMTBwdCAmIzQ0NDA0OyYjNDc1NDg7OyBmb250LWNvbG9yOiBibGFjayI+ PEI+RnJvbTo8L0I+IDxBIA0KICB0aXRsZT1naGFkamljaEB2dC5lZHUgaHJlZj0ibWFpbHRvOmdo YWRqaWNoQHZ0LmVkdSI+R2VvcmdlIEhhZGppY2hyaXN0b2ZpPC9BPiANCiAgPC9ESVY+DQogIDxE SVYgc3R5bGU9IkZPTlQ6IDEwcHQgJiM0NDQwNDsmIzQ3NTQ4OyI+PEI+VG86PC9CPiA8QSB0aXRs ZT1tYW5ldEBpZXRmLm9yZyANCiAgaHJlZj0ibWFpbHRvOm1hbmV0QGlldGYub3JnIj5tYW5ldEBp ZXRmLm9yZzwvQT4gPC9ESVY+DQogIDxESVYgc3R5bGU9IkZPTlQ6IDEwcHQgJiM0NDQwNDsmIzQ3 NTQ4OyI+PEI+Q2M6PC9CPiA8QSB0aXRsZT1naGFkamljaEB2dC5lZHUgDQogIGhyZWY9Im1haWx0 bzpnaGFkamljaEB2dC5lZHUiPkdlb3JnZSBIYWRqaWNocmlzdG9maTwvQT4gPC9ESVY+DQogIDxE SVYgc3R5bGU9IkZPTlQ6IDEwcHQgJiM0NDQwNDsmIzQ3NTQ4OyI+PEI+U2VudDo8L0I+IEZyaWRh eSwgSnVuZSAyMCwgMjAwMyAxMjozNCBBTTwvRElWPg0KICA8RElWIHN0eWxlPSJGT05UOiAxMHB0 ICYjNDQ0MDQ7JiM0NzU0ODsiPjxCPlN1YmplY3Q6PC9CPiBbbWFuZXRdIElQIGFkZHJlc3MgLS11 bmlxdWUgDQpJRDwvRElWPg0KICA8RElWPjxCUj48L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPUFy aWFsIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjxTUEFOIA0KICBjbGFzcz03MzY1NjI4MTUtMTkwNjIw MDM+SGksPC9TUEFOPjwvRk9OVD48L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPUFyaWFsIGNvbG9y PSMwMDAwZmYgc2l6ZT0yPjxTUEFOIA0KICBjbGFzcz03MzY1NjI4MTUtMTkwNjIwMDM+PC9TUEFO PjwvRk9OVD4mbmJzcDs8L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPUFyaWFsIGNvbG9yPSMwMDAw ZmYgc2l6ZT0yPjxTUEFOIGNsYXNzPTczNjU2MjgxNS0xOTA2MjAwMz5Ib3cgDQogIGRvIG5ldyZu YnNwO25vZGVzIGNvbWluZyBpbnRvIGEgbWFuZXQgZ2V0IHRoZWlyIGlwIA0KYWRkcmVzcz88L1NQ QU4+PC9GT05UPjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBz aXplPTI+PFNQQU4gY2xhc3M9NzM2NTYyODE1LTE5MDYyMDAzPklzIA0KICBpdCB1c3VhbGx5IHBy ZS1hc3NpZ25lZCBvciBhc3NpZ25lZCBkeW5hbWljYWxseT88L1NQQU4+PC9GT05UPjwvRElWPg0K ICA8RElWPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBzaXplPTI+PFNQQU4gDQogIGNs YXNzPTczNjU2MjgxNS0xOTA2MjAwMz4mbmJzcDs8L1NQQU4+PC9GT05UPjwvRElWPg0KICA8RElW PjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBzaXplPTI+PFNQQU4gDQogIGNsYXNzPTcz NjU2MjgxNS0xOTA2MjAwMz48Rk9OVCBmYWNlPSYjNDQ0MDQ7JiM0NzU0ODsgY29sb3I9IzAwMDAw MD4mbmJzcDstJmd0OyBBY3R1YWxseSwgDQogIG1vc3Qgb2YgbWFuZXQgbm9kZXMgZ2V0IHRoZWly IGFkZHJlc3MgdGhyb3VnaCBtYW51YWwgDQogIGNvbmZpZ3VyYXRpb24uPC9GT05UPjwvU1BBTj48 L0ZPTlQ+PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj0jMDAwMGZmIHNpemU9 Mj48U1BBTiANCiAgY2xhc3M9NzM2NTYyODE1LTE5MDYyMDAzPjxGT05UIGZhY2U9JiM0NDQwNDsm IzQ3NTQ4OyANCiAgY29sb3I9IzAwMDAwMD4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg VGhlcmUgYXJlIG1hbnkgc2NoZW1lcyBmb3IgDQogIGFkZHJlc3NpbmcgbWFuZXQgbm9kZSBhdXRv bWF0aWNhbGx5LjwvRk9OVD48L1NQQU4+PC9GT05UPjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9 JiM0NDQwNDsmIzQ3NTQ4OyBzaXplPTI+PFNQQU4gY2xhc3M9NzM2NTYyODE1LTE5MDYyMDAzPiZu YnNwOyZuYnNwOyZuYnNwOyANCiAgJm5ic3A7IEFtb25nIHRoZW0sIEkgc3VnZ2VzdGVkIG9uZSBy ZWNlbnRseSBhcyBtYW5ldCZuYnNwO2ludGVybmV0LWRyYWZ0IA0KICBlbnRpdGxlZDwvU1BBTj48 L0ZPTlQ+PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT0mIzQ0NDA0OyYjNDc1NDg7IHNpemU9Mj48 U1BBTiANCiAgY2xhc3M9NzM2NTYyODE1LTE5MDYyMDAzPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyAiQWQgSG9jIElQIEFkZHJlc3MgDQogIEF1dG9jb25maWd1cmF0aW9uIi48L1NQQU4+ PC9GT05UPjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9JiM0NDQwNDsmIzQ3NTQ4OyBzaXplPTI+ PFNQQU4gDQogIGNsYXNzPTczNjU2MjgxNS0xOTA2MjAwMz4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDtZb3UgY2FuIGZpbmQgdGhlIA0KICBkcmFmdCBpbiZuYnNwO3RoZSBmb2xs b3dpbmcgc2l0ZTs8L1NQQU4+PC9GT05UPjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9JiM0NDQw NDsmIzQ3NTQ4OyBzaXplPTI+PFNQQU4gDQogIGNsYXNzPTczNjU2MjgxNS0xOTA2MjAwMz4mbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgJm5ic3A7PEEgDQogIGhyZWY9Imh0dHA6Ly93d3cu aWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWplb25nLWFkaG9jLWlwLWFkZHItYXV0b2Nv bmYtMDAudHh0Ij5odHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1qZW9u Zy1hZGhvYy1pcC1hZGRyLWF1dG9jb25mLTAwLnR4dDwvQT48L1NQQU4+PC9GT05UPjwvRElWPg0K ICA8RElWPjxGT05UIGZhY2U9JiM0NDQwNDsmIzQ3NTQ4OyBzaXplPTI+PFNQQU4gDQogIGNsYXNz PTczNjU2MjgxNS0xOTA2MjAwMz48L1NQQU4+PC9GT05UPiZuYnNwOzwvRElWPg0KICA8RElWPjxG T05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBzaXplPTI+PFNQQU4gY2xhc3M9NzM2NTYyODE1 LTE5MDYyMDAzPkhvdyANCiAgY2FuIGEgbm9kZSBpbiBhIE1hbmV0IGJlIHVuaXF1ZWx5IGlkZW50 aWZpZWQsIGlmIHRoZSBJUCBhbmQgTUFDIGFkZHJlc3MgY2FuIGJlIA0KICBzcG9vZmVkPzwvU1BB Tj48L0ZPTlQ+PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT1BcmlhbCBjb2xvcj0jMDAwMGZmIHNp emU9Mj48U1BBTiANCiAgY2xhc3M9NzM2NTYyODE1LTE5MDYyMDAzPjwvU1BBTj48L0ZPTlQ+Jm5i c3A7PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT1BcmlhbCBzaXplPTI+PFNQQU4gY2xhc3M9NzM2 NTYyODE1LTE5MDYyMDAzPiZuYnNwOyAtJmd0OyBJbiBteSANCiAgc2NoZW1lLCBhIG1hbmV0IG5v ZGUgdGhhdCBmaW5kcyBhbiBJUCBhZGRyZXNzIGR1cGxpY2F0ZSB3aXRoIGl0cyBvd24gDQogIGFk ZHJlc3MsPEJSPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0aGUgbm9kZSBz ZWxlY3RzIGFub3RoZXIgDQogIGFkZHJlc3MgYW5kIHRyaWVzIHRvIGF1dG9jb25maWd1cmUgdGhl IG5ldyANCiAgb25lLjxCUj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgRm9y IE1BQyBhZGRyZXNzLCB0aGVyZSBpcyBubyANCiAgY29uc2lkZXJhdGlvbi48L1NQQU4+PC9GT05U PjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9QXJpYWwgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJ Vj4NCiAgPERJVj48Rk9OVCBmYWNlPUFyaWFsIHNpemU9Mj48U1BBTiANCiAgY2xhc3M9NzM2NTYy ODE1LTE5MDYyMDAzPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyANCiAgL0ph ZWhvb248QlI+PC9TUEFOPjwvRk9OVD48L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPUFyaWFsIGNv bG9yPSMwMDAwZmYgc2l6ZT0yPjxTUEFOIGNsYXNzPTczNjU2MjgxNS0xOTA2MjAwMz5JIA0KICB3 b3VsZCBhcHByZWNpYXRlIGFueSBoZWxwIG9uIHRoZXNlIHF1ZXN0aW9ucy48L1NQQU4+PC9GT05U PjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBzaXplPTI+PFNQ QU4gDQogIGNsYXNzPTczNjU2MjgxNS0xOTA2MjAwMz48L1NQQU4+PC9GT05UPiZuYnNwOzwvRElW Pg0KICA8RElWPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBzaXplPTI+PFNQQU4gDQog IGNsYXNzPTczNjU2MjgxNS0xOTA2MjAwMz5UaGFuayB5b3U8L1NQQU4+PC9GT05UPjwvRElWPg0K ICA8RElWPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBzaXplPTI+PFNQQU4gDQogIGNs YXNzPTczNjU2MjgxNS0xOTA2MjAwMz5HZW9yZ2UgSGFkamljaHJpc3RvZmk8L1NQQU4+PC9GT05U PjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBzaXplPTI+PC9G T05UPiZuYnNwOzwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9IzAwMDBmZiBz aXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9QXJpYWwgY29sb3I9 IzAwMDBmZiBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KICA8UD48Rk9OVCANCiAgc2l6ZT0y PioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqPEJSPkdlb3JnZSANCiAgQy4gSGFkamljaHJpc3RvZmk8QlI+R3JhZHVhdGUgU3R1ZGVudDxC Uj5CcmFkbGV5IERlcGFydG1lbnQgb2YgRWxlY3RyaWNhbCBhbmQgDQogIENvbXB1dGVyIEVuZ2lu ZWVyaW5nPEJSPlZpcmdpbmlhIFRlY2gsQmxhY2tzYnVyZyxWQSANCiAgMjQwNjEsVS5TLkE8QlI+ VEVMOig1NDApLTk1MS04OTM2Jm5ic3A7PEJSPioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqPC9GT05UPiANCiAgPC9QPg0KICA8QkxPQ0tR VU9URT4NCiAgICA8RElWIGNsYXNzPU91dGxvb2tNZXNzYWdlSGVhZGVyIGRpcj1sdHIgYWxpZ249 bGVmdD48Rk9OVCBmYWNlPVRhaG9tYSANCiAgICBzaXplPTI+PEJSPjwvRk9OVD4mbmJzcDs8L0RJ Vj48L0JMT0NLUVVPVEU+PC9CTE9DS1FVT1RFPjwvQk9EWT48L0hUTUw+DQo= ------=_NextPart_000_007A_01C33756.F355D6B0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat Jun 21 00:10: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 AAA19019 for ; Sat, 21 Jun 2003 00:10:49 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5L4AMG08103 for manet-archive@odin.ietf.org; Sat, 21 Jun 2003 00:10:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TZhm-00026c-CS for manet-web-archive@optimus.ietf.org; Sat, 21 Jun 2003 00:10: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 AAA19004 for ; Sat, 21 Jun 2003 00:10:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TZhk-0005TA-00 for manet-web-archive@ietf.org; Sat, 21 Jun 2003 00:10:20 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19TZhj-0005T6-00 for manet-web-archive@ietf.org; Sat, 21 Jun 2003 00:10:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TZhR-00025W-KF; Sat, 21 Jun 2003 00:10:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19TZgc-00023g-Db for manet@optimus.ietf.org; Sat, 21 Jun 2003 00:09: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 AAA18988 for ; Sat, 21 Jun 2003 00:09:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19TZga-0005Sb-00 for manet@ietf.org; Sat, 21 Jun 2003 00:09:08 -0400 Received: from ns.sait.samsung.co.kr ([202.20.142.13]) by ietf-mx with esmtp (Exim 4.12) id 19TZgZ-0005SH-00 for manet@ietf.org; Sat, 21 Jun 2003 00:09:07 -0400 Received: from LocalHost (localhost [127.0.0.1]) by ns.sait.samsung.co.kr (8.12.9/8.12.1) with SMTP id h5L48aOS010464 for ; Sat, 21 Jun 2003 13:08:36 +0900 (KST) Message-ID: <007901c337aa$cca85de0$d92f024b@LocalHost> From: "Eunil" To: Date: Sat, 21 Jun 2003 13:08:41 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: base64 Subject: [manet] Question about IPv6 Autoconfiguration in MANET. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 RGVhciBNQU5FVCBwZW9wbGUuDQoNCg0KDQpJIGhhdmUgcmVhZCBzb21lIHBhcGVycyB0aGF0IGFy ZSByZWxhdGl2ZSB3aXRoIGFkZHJlc3MgY29uZmlndXJhdGlvbi4NCg0KVGhlIG9uZSBvZiBwYXBl cnMsIHdoaWNoIG1hZGUgbWUgdmVyeSBpbXByZXNzaXZlLCBpcyDigJxJUHY2IEF1dG9jb25maWd1 cmF0aW9uIGluIExhcmdlIFNjYWxlIE1vYmlsZSBBZC1Ib2MgTmV0d29ya3PigJ0uDQoNCkkgd2Fu dCB0byBrbm93IHdoYXQgdGhlIE1BTkVUIHBlb3BsZSB0aGluayBhYm91dCBJcHY2IGFnZ3JlZ2F0 aW9uIGFkZHJlc3Mgc2NoZW1lIGFzIHNhaWQgaW4gdGhhdCBwYXBlci4gSSBoYXZlIHNlZW4gZGlz Y3Vzc2lvbiBhYm91dCBwcm8gYW5kIGNvbiBvZiBhZ2dyZWdhdGlvbiBhZGRyZXNzIHNjaGVtZS4g RXZlbiB0aG91Z2ggdGhlcmUgYXJlIGNvbiBvZiBhZ2dyZWdhdGlvbiBhZGRyZXNzIHNjaGVtZSBp biBNQU5FVCwgdWx0aW1hdGVseSB0aGUgYWRkcmVzcyBzY2hlbWUgaW4gTUFORVQsIEkgYmVsaWV2 ZSwgc2hvdWxkIGJlIElwdjYuDQoNCiANCg0KV2hhdCBkbyB5b3UgdGhpbmssIGZvbGtzPyBJZiB0 aGVyZSBpcyBhbnlib2R5IHdobyBoYXMgaWRlYSwgd2hhdCBpcyBnb29kIG9yIGJhZCBpbiBNQU5F VCB3aXRoIElQdjYsIA0KDQpQbGVhc2UsLCwsIHBsZWFzZSBsZXQgbWUga25vd15eLg0KDQogDQoN CkkgYW0gYWxzbyB3b3JraW5nIG9uIElQdjYuIFRoYXQgaXMgd2h5IEkgYW0gYWJvdXQgdG8gZGln IGFkZHJlc3MgQXV0b2NvbmZpZ3VyYXRpb24gd2l0aCBJUHY2IGFkZHJlc3Mgc2NoZW1lIGFuZCBJ cHY2IGFub3RoZXIgbWV0aG9kLiBJcyB0aGVyZSBzb21lYm9keSB3aG8gaXMgd29ya2luZyBvbiBN QU5FVCB3aXRoIElQdjYuDQoNCkxldCBtZSBrbm93IHlvdXIgcGFwZXIgYW5kIGFueSByZXNlYXJj aCwgcGxlYXNlLg0KDQogDQoNCkJlc3QgcmVnYXJkcywNCg0KRXVuaWwuDQoNCg0K _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sun Jun 22 15:39: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 PAA17154 for ; Sun, 22 Jun 2003 15:39:56 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5MJdR804758 for manet-archive@odin.ietf.org; Sun, 22 Jun 2003 15:39:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UAgR-0001Ef-RX for manet-web-archive@optimus.ietf.org; Sun, 22 Jun 2003 15:39:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17149 for ; Sun, 22 Jun 2003 15:39:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UAgQ-0005Bd-00 for manet-web-archive@ietf.org; Sun, 22 Jun 2003 15:39:26 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UAgK-0005BZ-00 for manet-web-archive@ietf.org; Sun, 22 Jun 2003 15:39:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UAg1-0001Bu-Ho; Sun, 22 Jun 2003 15:39:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UAfN-0001Bg-2t for manet@optimus.ietf.org; Sun, 22 Jun 2003 15:38: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 PAA17126 for ; Sun, 22 Jun 2003 15:38:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UAf6-0005BA-00 for manet@ietf.org; Sun, 22 Jun 2003 15:38:04 -0400 Received: from strix.ciens.ucv.ve ([150.185.72.253]) by ietf-mx with esmtp (Exim 4.12) id 19UAeq-0005An-00 for manet@ietf.org; Sun, 22 Jun 2003 15:37:49 -0400 Received: from strix.ciens.ucv.ve (localhost [127.0.0.1] (may be forged)) by strix.ciens.ucv.ve (8.12.5/8.12.5) with ESMTP id h5MK9Zwu014366 for ; Sun, 22 Jun 2003 16:09:35 -0400 Received: from localhost (dcobos@localhost) by strix.ciens.ucv.ve (8.12.5/8.12.5/Submit) with ESMTP id h5MK9YT7014362 for ; Sun, 22 Jun 2003 16:09:35 -0400 Date: Sun, 22 Jun 2003 16:09:34 -0400 (VET) From: Denis Cobos To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] !!About the most recent implementation of OLSR!! Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 everybody, Thank you very much for the answers and the feedback on the movement models. I would like to know which is the last implemented version of OLSR available for ns-2. In that case, I would like to know from where could I dowloand it. I checked at INRIA web page, there, the last implemented version is version 3. Thank you very much -- ***************************************************** * * * Denis Alfonzo Cobos * * Escuela de Computacion * * Facultad de Ciencias * * Universidad Central de Venezuela * * Caracas-Venezuela * ***************************************************** ..... Saludos _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sun Jun 22 18:09: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 SAA20211 for ; Sun, 22 Jun 2003 18:09:44 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5MM9HS19747 for manet-archive@odin.ietf.org; Sun, 22 Jun 2003 18:09:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UD1R-00058Q-SB for manet-web-archive@optimus.ietf.org; Sun, 22 Jun 2003 18:09: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 SAA20177 for ; Sun, 22 Jun 2003 18:09:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UD1P-0005lA-00 for manet-web-archive@ietf.org; Sun, 22 Jun 2003 18:09:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UD1J-0005kq-00 for manet-web-archive@ietf.org; Sun, 22 Jun 2003 18:09:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UD0E-000504-5L; Sun, 22 Jun 2003 18:08:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UCzQ-0004r6-Ug for manet@optimus.ietf.org; Sun, 22 Jun 2003 18:07: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 SAA19913 for ; Sun, 22 Jun 2003 18:06:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UCz9-0005kA-00 for manet@ietf.org; Sun, 22 Jun 2003 18:06:55 -0400 Received: from hellmouth2.gatech.edu ([130.207.165.162] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19UCyy-0005k1-00 for manet@ietf.org; Sun, 22 Jun 2003 18:06:44 -0400 Received: from hellmouth2.gatech.edu (localhost [127.0.0.1]) by hellmouth2.gatech.edu (Postfix) with SMTP id 37A7CA4EC for ; Sun, 22 Jun 2003 18:06:25 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: from acmey.gatech.edu (acmey.prism.gatech.edu [130.207.171.27]) by hellmouth2.gatech.edu (Postfix) with ESMTP id 22066A4A5 for ; Sun, 22 Jun 2003 18:06:25 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: by acmey.gatech.edu (Postfix, from userid 21503) id 0BF4931F20; Sun, 22 Jun 2003 18:06:25 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by acmey.gatech.edu (Postfix) with ESMTP id 035DC330EE for ; Sun, 22 Jun 2003 18:06:24 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Date: Sun, 22 Jun 2003 18:06:24 -0400 (EDT) From: Young-Jun Lee X-X-Sender: To: Subject: [manet] Is on-demand protocol between L3 and L4? 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: , All, Where do on-demand MANET protocols reside in protocol stack? For on-demand, once a packet comes down to L3, and route query is done, it's too late. So I think the route query should be done just before a packet comes down to L3. Is this correct? Young _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 23 06:45: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 GAA15530 for ; Mon, 23 Jun 2003 06:45:47 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5NAjLS12233 for manet-archive@odin.ietf.org; Mon, 23 Jun 2003 06:45:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UOp7-0003BE-2l for manet-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 06:45: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 GAA15519 for ; Mon, 23 Jun 2003 06:45:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UOp3-0001CJ-00 for manet-web-archive@ietf.org; Mon, 23 Jun 2003 06:45:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UOox-0001CG-00 for manet-web-archive@ietf.org; Mon, 23 Jun 2003 06:45:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UOoo-0003A3-2w; Mon, 23 Jun 2003 06:45:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UOo7-00039N-E8 for manet@optimus.ietf.org; Mon, 23 Jun 2003 06:44: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 GAA15497 for ; Mon, 23 Jun 2003 06:44:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UOno-0001Bm-00 for manet@ietf.org; Mon, 23 Jun 2003 06:44:00 -0400 Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx with esmtp (Exim 4.12) id 19UOnd-0001Bj-00 for manet@ietf.org; Mon, 23 Jun 2003 06:43:49 -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 h5NAhju27441 for ; Mon, 23 Jun 2003 12:43:45 +0200 (MEST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.11.7/8.11.7) with ESMTP id h5NAhig06479 for ; Mon, 23 Jun 2003 12:43:45 +0200 (MEST) Received: from mail-y.mchp.siemens.de (mail-y.mchp.siemens.de [139.23.203.56]) by mars.cert.siemens.de (8.12.9/8.12.9/$SiemensCERT: mail/cert.mc,v 1.46 2003/05/28 09:28:32 ust Exp $) with ESMTP id h5NAhiLH015597 for ; Mon, 23 Jun 2003 12:43:44 +0200 (CEST) Received: from alpha (alpha [139.23.202.151]) by mail-y.mchp.siemens.de with SMTP id h5NAhiiO027372 for ; Mon, 23 Jun 2003 12:43:44 +0200 (MET DST) Date: Mon, 23 Jun 2003 12:43:44 +0200 (MET DST) From: Florian Schiel X-Sender: fschiel@alpha To: manet@ietf.org In-Reply-To: <20030621160002.7879.61303.Mailman@www1.ietf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Question about IPv6 Autoconfiguration in MANET. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hello Eunil, I'm working on MANET Autoconfiguration with IPv6 too. Up to now i have not yet read the Document you mention, since I have just startet on this topic a few days ago. As far as I have read, ist seems reasonable, that the standalone MANET itself (i.e. without Gateways to Networks with fixed Infrastructure and fixed addresses) should only use stateless autoconfiguration. I know, that IPv6 has very powerful means of stateless autoconfiguration, so this capability will make life much easier in a MANET. Maybe you can tell me, where you found the discussion about pro/con of adress aggregation? The latest discussion of Internet-MANET Gateways seems to get to another Goal. Florian Schiel - Siemens CT IC2 Internet and Mobility Lab --------------------------------------------------------------- Siemens AG, CT IC2 phone: +49 89 636-50686 Otto-Hahn Ring 6 mail: florian.schiel@mchp.siemens.de D-81730 Munich _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 23 11:50: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 LAA25826 for ; Mon, 23 Jun 2003 11:50:47 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5NFoKs23738 for manet-archive@odin.ietf.org; Mon, 23 Jun 2003 11:50:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UTaG-0006An-44 for manet-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 11:50: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 LAA25802 for ; Mon, 23 Jun 2003 11:50:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UTaE-0003Dx-00 for manet-web-archive@ietf.org; Mon, 23 Jun 2003 11:50:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UTa9-0003Du-00 for manet-web-archive@ietf.org; Mon, 23 Jun 2003 11:50:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UTZx-00069T-Mx; Mon, 23 Jun 2003 11:50:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UTZs-000697-Ue for manet@optimus.ietf.org; Mon, 23 Jun 2003 11:49: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 LAA25783 for ; Mon, 23 Jun 2003 11:49:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UTZr-0003Da-00 for manet@ietf.org; Mon, 23 Jun 2003 11:49:55 -0400 Received: from law14-f76.law14.hotmail.com ([64.4.21.76] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19UTZg-0003Co-00 for manet@ietf.org; Mon, 23 Jun 2003 11:49:44 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 23 Jun 2003 08:48:44 -0700 Received: from 193.61.167.147 by lw14fd.law14.hotmail.msn.com with HTTP; Mon, 23 Jun 2003 15:48:43 GMT X-Originating-IP: [193.61.167.147] X-Originating-Email: [bilalmomani@hotmail.com] From: "Bilal Al Momani" To: manet@ietf.org Date: Mon, 23 Jun 2003 18:48:43 +0300 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 23 Jun 2003 15:48:44.0143 (UTC) FILETIME=[ED10E7F0:01C3399E] Subject: [manet] NS-2 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Dear friends I have just started reading about MANET two weeks ago. I would like to do some simulation on manet routing protocols and dynamic addressing. I have been adviced to work on ns-2, but i have no idea what this simulation is and how can i get this simulation? Is it straight forward simulation? If any body can give some comments about that i would be so greatful. Thanks Bill _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 23 12:15: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 MAA26892 for ; Mon, 23 Jun 2003 12:15:16 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5NGEn830837 for manet-archive@odin.ietf.org; Mon, 23 Jun 2003 12:14:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UTxx-00081G-D1 for manet-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 12:14:49 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26859 for ; Mon, 23 Jun 2003 12:14:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UTxA-0007ts-UI; Mon, 23 Jun 2003 12:14:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UTwi-0007tP-52 for manet@optimus.ietf.org; Mon, 23 Jun 2003 12:13:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26785 for ; Mon, 23 Jun 2003 12:13:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UTwR-0003PW-00 for manet@ietf.org; Mon, 23 Jun 2003 12:13:15 -0400 Received: from isis.lip6.fr ([132.227.60.2] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19UTwG-0003PL-00 for manet@ietf.org; Mon, 23 Jun 2003 12:13:04 -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 h5NGCdGL026553 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) ; Mon, 23 Jun 2003 18:12:39 +0200 X-pt: isis.lip6.fr Received: from localhost (iannone@localhost) by tibre.lip6.fr (8.11.6p2/8.11.6) with ESMTP id h5NGCdY05083; Mon, 23 Jun 2003 18:12:39 +0200 (CEST) Date: Mon, 23 Jun 2003 18:12:39 +0200 (CEST) From: Luigi Iannone To: manet@ietf.org cc: bilalmomani@hotmail.com In-Reply-To: <20030623160002.25799.3586.Mailman@www1.ietf.org> Message-ID: References: <20030623160002.25799.3586.Mailman@www1.ietf.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: isis.lip6.fr Subject: [manet] Re: manet digest, Vol 1 #468 - 4 msgs Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , > Message: 4 > From: "Bilal Al Momani" > To: manet@ietf.org > Date: Mon, 23 Jun 2003 18:48:43 +0300 > Subject: [manet] NS-2 > > Dear friends > > I have just started reading about MANET two weeks ago. I would like to do > some simulation on manet routing protocols and dynamic addressing. I have > been adviced to work on ns-2, but i have no idea what this simulation is and > how can i get this simulation? Is it straight forward simulation? You can find NS-2 at http://www.isi.edu/nsnam/ns/ You can do your first ad-hoc simulation the same day you install the simulator! Just read marc Greig's Tutorial. On the other hand, to perform complex simulation needs some time spent working on it. Documentation is somehow lacking. Good luck! Ciao Luigi > If any body can give some comments about that i would be so greatful. > > Thanks > > Bill > > _________________________________________________________________ > Tired of spam? Get advanced junk mail protection with MSN 8. > http://join.msn.com/?page=features/junkmail > > > > ------------------------------------> Luigi Iannone - Laboratoire D'Informatique Paris 6 e.mail: luigi.iannone@lip6.fr Tel: +33 (0)1 44 27 88 48 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 23 12:16: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 MAA27019 for ; Mon, 23 Jun 2003 12:16:04 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5NGFbF32421 for manet-archive@odin.ietf.org; Mon, 23 Jun 2003 12:15:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UTyj-0008Qq-D5 for manet-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 12:15:37 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26920 for ; Mon, 23 Jun 2003 12:15:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UTyC-000830-1a; Mon, 23 Jun 2003 12:15:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UTy7-00081r-Q7 for manet@optimus.ietf.org; Mon, 23 Jun 2003 12:14: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 MAA26855 for ; Mon, 23 Jun 2003 12:14:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UTxr-0003QT-00 for manet@ietf.org; Mon, 23 Jun 2003 12:14:43 -0400 Received: from massive.its.bldrdoc.gov ([132.163.64.201]) by ietf-mx with esmtp (Exim 4.12) id 19UTxa-0003Pa-00 for manet@ietf.org; Mon, 23 Jun 2003 12:14:27 -0400 Received: from andy (localhost.0.0.127.in-addr.arpa [127.0.0.1] (may be forged)) by massive.its.bldrdoc.gov (8.12.8p1/8.12.8) with ESMTP id h5NGDExm000779; Mon, 23 Jun 2003 10:13:14 -0600 (MDT) From: "Andrew Thiessen" To: "'Bilal Al Momani'" , Subject: RE: [manet] NS-2 Date: Mon, 23 Jun 2003 10:12:07 -0600 Message-ID: <001001c339a2$31a1fa50$4841a384@andy> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Bill, I would start at the URL below. There is a lot of good documentation on the site to get you up and running. The ability to simulate MANET routing protocols is not built in (I think, someone correct me if I am wrong), but probably best not to start with that out of the box anyway. http://www.isi.edu/nsnam/ns/ Andrew Thiessen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Bilal Al Momani Sent: Monday, June 23, 2003 9:49 AM To: manet@ietf.org Subject: [manet] NS-2 Dear friends I have just started reading about MANET two weeks ago. I would like to do some simulation on manet routing protocols and dynamic addressing. I have been adviced to work on ns-2, but i have no idea what this simulation is and how can i get this simulation? Is it straight forward simulation? If any body can give some comments about that i would be so greatful. Thanks Bill _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 23 12:59: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 MAA28782 for ; Mon, 23 Jun 2003 12:59:56 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5NGxUZ08820 for manet-archive@odin.ietf.org; Mon, 23 Jun 2003 12:59:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UUfC-0002IB-2s for manet-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 12:59: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 MAA28772 for ; Mon, 23 Jun 2003 12:59:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UUfA-0003rR-00 for manet-web-archive@ietf.org; Mon, 23 Jun 2003 12:59:28 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UUf4-0003rO-00 for manet-web-archive@ietf.org; Mon, 23 Jun 2003 12:59:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UUej-0002BX-QT; Mon, 23 Jun 2003 12:59:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UUde-0002B5-C1 for manet@optimus.ietf.org; Mon, 23 Jun 2003 12:58: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 MAA28729 for ; Mon, 23 Jun 2003 12:57:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UUdc-0003qc-00 for manet@ietf.org; Mon, 23 Jun 2003 12:57:52 -0400 Received: from massive.its.bldrdoc.gov ([132.163.64.201]) by ietf-mx with esmtp (Exim 4.12) id 19UUdM-0003qI-00 for manet@ietf.org; Mon, 23 Jun 2003 12:57:36 -0400 Received: from andy (localhost.0.0.127.in-addr.arpa [127.0.0.1] (may be forged)) by massive.its.bldrdoc.gov (8.12.8p1/8.12.8) with ESMTP id h5NGupxm004504; Mon, 23 Jun 2003 10:56:52 -0600 (MDT) From: "Andrew Thiessen" To: "'Ali Hamidian'" Cc: "'Bilal Al Momani'" , Subject: RE: [manet] NS-2 Date: Mon, 23 Jun 2003 10:55:44 -0600 Message-ID: <001101c339a8$49aadfd0$4841a384@andy> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <3EF72A10.1060000@telecom.lth.se> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Thanks Ali... I do have a general question for the group. I am gearing up to simulate some modifications to some popular MANET protocols, and my organization has access to both NS2 (gotta love free stuff) and OPNET. Which would people recommend (taking into account that I have)? Andrew Thiessen -----Original Message----- From: Ali Hamidian [mailto:alexh@telecom.lth.se] Sent: Monday, June 23, 2003 10:26 AM To: Andrew Thiessen Cc: 'Bilal Al Momani'; manet@ietf.org Subject: Re: [manet] NS-2 Hi, Andrew Thiessen wrote: >Bill, > >I would start at the URL below. There is a lot of good documentation on >the site to get you up and running. The ability to simulate MANET >routing protocols is not built in (I think, someone correct me if I am >wrong), > 4 ad hoc routing protocols are implemented in ns: DSDV, TORA, DSR and AODV (moreover you can download implementations of ZRP and OLSR from the Internet). Once you've installed ns, you should start reading Marc Greis tutorial which is a very good introduction to ns: http://www.isi.edu/nsnam/ns/tutorial/index.html > but probably best not to start with that out of the box anyway. > >http://www.isi.edu/nsnam/ns/ > >Andrew Thiessen > Regards Ali Hamidian > > >-----Original Message----- >From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of >Bilal Al Momani >Sent: Monday, June 23, 2003 9:49 AM >To: manet@ietf.org >Subject: [manet] NS-2 > >Dear friends > >I have just started reading about MANET two weeks ago. I would like to >do >some simulation on manet routing protocols and dynamic addressing. I >have >been adviced to work on ns-2, but i have no idea what this simulation is >and >how can i get this simulation? Is it straight forward simulation? >If any body can give some comments about that i would be so greatful. > >Thanks > >Bill > >_________________________________________________________________ >Tired of spam? Get advanced junk mail protection with MSN 8. >http://join.msn.com/?page=features/junkmail > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 23 13:11: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 NAA29252 for ; Mon, 23 Jun 2003 13:11:15 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5NHAnI12073 for manet-archive@odin.ietf.org; Mon, 23 Jun 2003 13:10:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UUq8-00038e-Ul for manet-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 13:10:48 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29216 for ; Mon, 23 Jun 2003 13:10:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UUpO-00030U-Ec; Mon, 23 Jun 2003 13:10:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UUpI-0002zN-Cq for manet@optimus.ietf.org; Mon, 23 Jun 2003 13:09: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 NAA29134 for ; Mon, 23 Jun 2003 13:09:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UUoN-0003vL-00 for manet@ietf.org; Mon, 23 Jun 2003 13:08:59 -0400 Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx with esmtp (Exim 4.12) id 19UUoD-0003ux-00 for manet@ietf.org; Mon, 23 Jun 2003 13:08:49 -0400 Received: from telecom.lth.se (lina23.tts.lth.se [130.235.18.83]) by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id SAA28288; Mon, 23 Jun 2003 18:26:30 +0200 (MET DST) Message-ID: <3EF72A10.1060000@telecom.lth.se> Date: Mon, 23 Jun 2003 18:25:52 +0200 From: Ali Hamidian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Andrew Thiessen CC: "'Bilal Al Momani'" , manet@ietf.org Subject: Re: [manet] NS-2 References: <001001c339a2$31a1fa50$4841a384@andy> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Andrew Thiessen wrote: >Bill, > >I would start at the URL below. There is a lot of good documentation on >the site to get you up and running. The ability to simulate MANET >routing protocols is not built in (I think, someone correct me if I am >wrong), > 4 ad hoc routing protocols are implemented in ns: DSDV, TORA, DSR and AODV (moreover you can download implementations of ZRP and OLSR from the Internet). Once you've installed ns, you should start reading Marc Greis tutorial which is a very good introduction to ns: http://www.isi.edu/nsnam/ns/tutorial/index.html > but probably best not to start with that out of the box anyway. > >http://www.isi.edu/nsnam/ns/ > >Andrew Thiessen > Regards Ali Hamidian > > >-----Original Message----- >From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of >Bilal Al Momani >Sent: Monday, June 23, 2003 9:49 AM >To: manet@ietf.org >Subject: [manet] NS-2 > >Dear friends > >I have just started reading about MANET two weeks ago. I would like to >do >some simulation on manet routing protocols and dynamic addressing. I >have >been adviced to work on ns-2, but i have no idea what this simulation is >and >how can i get this simulation? Is it straight forward simulation? >If any body can give some comments about that i would be so greatful. > >Thanks > >Bill > >_________________________________________________________________ >Tired of spam? Get advanced junk mail protection with MSN 8. >http://join.msn.com/?page=features/junkmail > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 23 14:59: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 OAA04291 for ; Mon, 23 Jun 2003 14:59:43 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5NIxGE30810 for manet-archive@odin.ietf.org; Mon, 23 Jun 2003 14:59:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UWX6-00080r-6V for manet-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 14:59: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 OAA04284 for ; Mon, 23 Jun 2003 14:59:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UWX3-0004s4-00 for manet-web-archive@ietf.org; Mon, 23 Jun 2003 14:59:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UWWx-0004s1-00 for manet-web-archive@ietf.org; Mon, 23 Jun 2003 14:59:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UWWr-0007ws-He; Mon, 23 Jun 2003 14:59:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UWWT-0007we-LO for manet@optimus.ietf.org; Mon, 23 Jun 2003 14:58:37 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04272 for ; Mon, 23 Jun 2003 14:58:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UWWQ-0004rq-00 for manet@ietf.org; Mon, 23 Jun 2003 14:58:34 -0400 Received: from [204.97.190.234] (helo=highsys.com) by ietf-mx with esmtp (Exim 4.12) id 19UWWG-0004re-00 for manet@ietf.org; Mon, 23 Jun 2003 14:58:24 -0400 Received: from haggis [141.156.220.66] by highsys.com with ESMTP (SMTPD32-6.06) id ADAE21740164; Mon, 23 Jun 2003 14:57:50 -0400 From: "Michael Roberts" To: Subject: Re: [manet] NS-2 Date: Mon, 23 Jun 2003 14:57:57 -0400 Message-ID: <000001c339b9$5c556860$6401a8c0@haggis> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: quoted-printable Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Andrew, I haven't used ns, so I can only give you half an answer, but I'd advise = you to take a hard look at OPNET. We've used it extensively and had good results on several ad hoc routing studies comprising both unicast and multicast traffic. In addition to basic tool features (model architecture, UI, programming library, debug support, etc), you'll want to consider a few unique = things about ad hoc nets and how the different models/environments deal with disconnects from the standard "wired" IP paradigm: 1) Ad Hoc nodes are typically both routers and source/sinks as opposed = to being either one or the other. 2) Ad Hoc nodes are "one armed". This means that they usually want to = route traffic back out the same interface on which it arrived (i.e. the router = has only "one arm" that connects to the network). This is a pretty unusual situation for wired nets. 3) Standard address and subnet assignments don't really make sense in = the wireless world where link connectivity is dynamic and you have = asymmetric broadcast groups (e.g. B can send to A and C, but A can only send to B, = and C can only send to B). 4) ARP modeling is a big sub-problem. Three general options here: promiscuous mode, customized functionality, or standard functionality, = any of which have issues. Regarding OPNET, #1 isn't usually a problem because of code re-use in = the standard IP library (the same processes are used in workstation models = that are used in routers). #2 can create some legacy restrictions since the original models were designed with wired nets in mind, but these = problems have been simple to fix. #3 and #4 are tougher, since there is no acknowledged best approach to these problems (which might be just the = kind of thing that you are going to be studying). You'll definitely want to = see how these issues are handled in the ns models for comparison. All of our work has required modifications the standard OPNET models to address one or more of the issues above. The new DSR model (and others coming) from OPNET will probably reduce the amount of customization necessary for our ad hoc work, but we haven't had a chance to fully = assess it yet. Regards, =20 Michael Roberts Highland Systems, Inc. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 23 20:55: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 UAA16706 for ; Mon, 23 Jun 2003 20:55:54 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5O0tQw09462 for manet-archive@odin.ietf.org; Mon, 23 Jun 2003 20:55:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Uc5m-0002SX-IR for manet-web-archive@optimus.ietf.org; Mon, 23 Jun 2003 20:55: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 UAA16687 for ; Mon, 23 Jun 2003 20:55:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Uc5k-0006xJ-00 for manet-web-archive@ietf.org; Mon, 23 Jun 2003 20:55:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Uc5e-0006xC-00 for manet-web-archive@ietf.org; Mon, 23 Jun 2003 20:55:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Uc5O-0002RQ-0y; Mon, 23 Jun 2003 20:55:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Uc4X-0002Qh-Q4 for manet@optimus.ietf.org; Mon, 23 Jun 2003 20:54: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 UAA16641 for ; Mon, 23 Jun 2003 20:54:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Uc4V-0006wo-00 for manet@ietf.org; Mon, 23 Jun 2003 20:54:07 -0400 Received: from web40509.mail.yahoo.com ([66.218.78.126]) by ietf-mx with smtp (Exim 4.12) id 19Uc4K-0006wd-00 for manet@ietf.org; Mon, 23 Jun 2003 20:53:56 -0400 Message-ID: <20030624005245.25621.qmail@web40509.mail.yahoo.com> Received: from [137.132.3.7] by web40509.mail.yahoo.com via HTTP; Mon, 23 Jun 2003 17:52:45 PDT Date: Mon, 23 Jun 2003 17:52:45 -0700 (PDT) From: ng jiahui To: Michael Roberts , manet@ietf.org In-Reply-To: <000001c339b9$5c556860$6401a8c0@haggis> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] 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: , Hi; Hi, can i know when i have set up the AODV-UU testbed then does any one has setup one PC as a gateway successfully as i do not think i set it up correctly by typing the command: aodvd -w -i eth1 and can kindly guide me on this. 2nd qn: Can i know if i have 3 laptops connected wirelessly and 1 of it has eth0 connected to LAN/internet and eth1 connected to a wireless access point. When all 3 laptops are run aodvd, i notice that the other 2 laptops can ping one another but not ping external network like the internet (example: ping google.com), only the one that has eth0 connected to LAN can access internet. Can anyone help me on this? Thanks in advance =) Regards; Jiahui __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jun 24 01:36: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 BAA21997 for ; Tue, 24 Jun 2003 01:36:48 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5O5aKT04523 for manet-archive@odin.ietf.org; Tue, 24 Jun 2003 01:36:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UgTc-0001As-4M for manet-web-archive@optimus.ietf.org; Tue, 24 Jun 2003 01:36: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 BAA21993 for ; Tue, 24 Jun 2003 01:36:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UgTZ-0000Pk-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 01:36:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UgTT-0000Ph-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 01:36:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UgTJ-00015j-Sw; Tue, 24 Jun 2003 01:36:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UgSD-00014Y-4F for manet@optimus.ietf.org; Tue, 24 Jun 2003 01:35: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 BAA21961 for ; Tue, 24 Jun 2003 01:34:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UgSA-0000P5-00 for manet@ietf.org; Tue, 24 Jun 2003 01:34:50 -0400 Received: from web14711.mail.yahoo.com ([216.136.232.91]) by ietf-mx with smtp (Exim 4.12) id 19UgRz-0000Or-00 for manet@ietf.org; Tue, 24 Jun 2003 01:34:39 -0400 Message-ID: <20030624053419.21322.qmail@web14711.mail.yahoo.com> Received: from [203.197.138.163] by web14711.mail.yahoo.com via HTTP; Mon, 23 Jun 2003 22:34:19 PDT Date: Mon, 23 Jun 2003 22:34:19 -0700 (PDT) From: panneer pandi To: GLOMOSIM-USERS-L@listserv.ucla.edu, manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-271473602-1056432859=:21189" Subject: [manet] AODV-multicasting Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-271473602-1056432859=:21189 Content-Type: text/plain; charset=us-ascii Hello friends, I am using glomosim sim, if i want to send a route request to only a particular nodes, where the particular nodes are found dynamically, how to do this in AODV protocol. Bye. --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! --0-271473602-1056432859=:21189 Content-Type: text/html; charset=us-ascii
Hello friends,
 
     I am using glomosim sim, if i want to send a route request to only a particular nodes, where the particular nodes are found dynamically, how to do this in AODV protocol.
 
                  Bye.
 

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! --0-271473602-1056432859=:21189-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jun 24 03:39: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 DAA06355 for ; Tue, 24 Jun 2003 03:39:04 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5O7caZ30640 for manet-archive@odin.ietf.org; Tue, 24 Jun 2003 03:38:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UiNv-0007y7-RT for manet-web-archive@optimus.ietf.org; Tue, 24 Jun 2003 03:38: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 DAA06246 for ; Tue, 24 Jun 2003 03:31:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UiHD-0001Cg-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 03:31:39 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UiH7-0001CV-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 03:31:33 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UiGd-0007PN-I7; Tue, 24 Jun 2003 03:31:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UiFm-0007NI-W6 for manet@optimus.ietf.org; Tue, 24 Jun 2003 03:30: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 DAA06213 for ; Tue, 24 Jun 2003 03:30:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UiFk-0001C8-00 for manet@ietf.org; Tue, 24 Jun 2003 03:30:08 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19UiFZ-0001Bq-00 for manet@ietf.org; Tue, 24 Jun 2003 03:29:57 -0400 Received: from paulnb (paul3.etri.re.kr [129.254.112.196]) by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h5O7fT919188; Tue, 24 Jun 2003 16:41:29 +0900 (KST) Message-ID: <005a01c33a22$0e8f3070$c470fe81@etri.re.kr> From: "Jaehoon Jeong" To: "Ali Hamidian" Cc: "MANET WG" References: <3EF71D87.7080508@telecom.lth.se> Date: Tue, 24 Jun 2003 16:27:23 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 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: base64 Subject: [manet] Re: Ad Hoc IP 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: , Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 SGksIEFsaS4NCg0KDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkFsaSBI YW1pZGlhbiIgPGFsZXhoQHRlbGVjb20ubHRoLnNlPg0KVG86IDxwYXVsQGV0cmkucmUua3I+DQpT ZW50OiBUdWVzZGF5LCBKdW5lIDI0LCAyMDAzIDEyOjMyIEFNDQpTdWJqZWN0OiBBZCBIb2MgSVAg QWRkcmVzcyBBdXRvY29uZmlndXJhdGlvbg0KDQoNCj4gDQo+IEhpIQ0KPiANCj4gSSBzdGFydGVk IHRvIHJlYWQgeW91ciBkcmFmdCB0b2RheS4gQSBxdWVzdGlvbiBhcmlzZWQgd2hlbiBJIGNhbWUg dG8gDQo+IFNlY3Rpb24gNS4xLjEsIHN0ZXAgKGMpOg0KPiAqIFdoYXQgaXMgdGhlIFRUTCB2YWx1 ZSB1c2VkIHdoZW4gdGhlIG1vYmlsZSBub2RlIGJyb2FkY2FzdHMgdGhlIEFSRVEgDQo+IG1lc3Nh Z2U/DQogICBUVEwgdmFsdWUgaXMgYSBzeXN0ZW0gcGFyYW1ldGVyLiBJIHRoaW5rIHRoYXQgMTAg aXMgYXBwcm9wcmlhdGUuDQogICBUaGlzIHZhbHVlIHNob3VsZCBiZSB0dW5lZCBhcHByb3ByaWF0 ZWx5LCANCiAgIGNvbnNpZGVyaW5nIHRoZSBjaGFyYWN0ZXJpc3RpY3Mgb2YgdGhlIGNvcnJlc3Bv bmRpbmcgTUFORVQuDQoNCj4gSXQgc2VlbXMgdGhlIFRUTCB2YWx1ZSBtdXN0IGJlICJiaWcgZW5v dWdoIiBzbyB0aGF0IGFsbCBtb2JpbGUgbm9kZXMgaW4gDQo+IHRoZSBNQU5FVCBjYW4gcmVjZWl2 ZSB0aGUgQVJFUSBtZXNzYWdlIC0gd2hpY2ggcmVzbHV0cyBpbiBhIGxvdCBvZiANCj4gdHJhZmZp YyBjcmVhdGVkIGluIHRoZSBNQU5FVC4NCiAgIA0KICAgTm90IGF0IGFsbC4gQmVjYXVzZSBteSBz Y2hlbWUgYWRvcHRzIHRoZSB3ZWFrIG9yIGRlbGF5ZWQgREFEDQogICBmb3IgY2hlY2tpbmcgdGhl IGR1cGxpY2F0aW9uIG9mIElQIGFkZHJlc3MsIGl0IG5lZWQgbm90IGJpZyBUVEwgdmFsdWUuDQog ICANCiAgIC9KYWVob29uDQogICANCj4gDQo+IFRoYW5rcyBpbiBhZHZhbmNlDQo+IEFsaSBIYW1p ZGlhbg0KPiA= _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jun 24 05:19: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 FAA08053 for ; Tue, 24 Jun 2003 05:19:33 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5O9J6p08093 for manet-archive@odin.ietf.org; Tue, 24 Jun 2003 05:19:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UjxC-00026S-5T for manet-web-archive@optimus.ietf.org; Tue, 24 Jun 2003 05:19:06 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08041 for ; Tue, 24 Jun 2003 05:19:02 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UjrJ-0001mN-CJ; Tue, 24 Jun 2003 05:13:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Ujqg-0001ly-Ga for manet@optimus.ietf.org; Tue, 24 Jun 2003 05:12: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 FAA07904 for ; Tue, 24 Jun 2003 05:12:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ujqd-0001cE-00 for manet@ietf.org; Tue, 24 Jun 2003 05:12:19 -0400 Received: from web21208.mail.yahoo.com ([216.136.175.166]) by ietf-mx with smtp (Exim 4.12) id 19UjqS-0001bw-00 for manet@ietf.org; Tue, 24 Jun 2003 05:12:08 -0400 Message-ID: <20030624091135.18239.qmail@web21208.mail.yahoo.com> Received: from [213.212.199.5] by web21208.mail.yahoo.com via HTTP; Tue, 24 Jun 2003 02:11:35 PDT Date: Tue, 24 Jun 2003 02:11:35 -0700 (PDT) From: hanem eladly To: manet@ietf.org In-Reply-To: <20021221170003.6712.50524.Mailman@www1.ietf.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1356218565-1056445895=:18148" Subject: [manet] Simulating IEEE 802.11 DCF mode. Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --0-1356218565-1056445895=:18148 Content-Type: text/plain; charset=us-ascii Hello, I would like to simulate IEEE 802.11 DCF mode and collect some statistics to compare it with some analysis I performed. Does anybody know, what is the best simulator to use. I went through a painful process to download cygwin and then ns2 but there isn't any good documentation as to how to proceed. What do you think, is this the best of the available simulators or Opnet is better? Thanks in advance, Hanem --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! --0-1356218565-1056445895=:18148 Content-Type: text/html; charset=us-ascii

Hello,

I would like to simulate IEEE 802.11 DCF mode and collect some statistics to compare it with some analysis I performed. Does anybody know, what is the best simulator to use. I went through a painful process to download cygwin and then ns2 but there isn't any good documentation as to how to proceed. What do you think, is this the best of the available simulators or Opnet is better?

Thanks in advance,

Hanem

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! --0-1356218565-1056445895=:18148-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jun 24 06:22: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 GAA09144 for ; Tue, 24 Jun 2003 06:22:45 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5OAMJ914316 for manet-archive@odin.ietf.org; Tue, 24 Jun 2003 06:22:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UkwN-0003ip-8G for manet-web-archive@optimus.ietf.org; Tue, 24 Jun 2003 06:22: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 GAA09136 for ; Tue, 24 Jun 2003 06:22:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UkwJ-0001sQ-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 06:22:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UkwD-0001sN-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 06:22:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Ukw6-0003eg-8E; Tue, 24 Jun 2003 06:22:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Ukvn-0003eM-LC for manet@optimus.ietf.org; Tue, 24 Jun 2003 06:21:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA09121 for ; Tue, 24 Jun 2003 06:21:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Ukvj-0001s8-00 for manet@ietf.org; Tue, 24 Jun 2003 06:21:39 -0400 Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx with esmtp (Exim 4.12) id 19UkvY-0001s2-00 for manet@ietf.org; Tue, 24 Jun 2003 06:21:29 -0400 Received: from telecom.lth.se (lina23.tts.lth.se [130.235.18.83]) by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id MAA00519; Tue, 24 Jun 2003 12:21:10 +0200 (MET DST) Message-ID: <3EF825F0.2080708@telecom.lth.se> Date: Tue, 24 Jun 2003 12:20:32 +0200 From: Ali Hamidian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Jaehoon Jeong , manet@ietf.org References: <3EF71D87.7080508@telecom.lth.se> <005a01c33a22$0e8f3070$c470fe81@etri.re.kr> Content-Type: multipart/alternative; boundary="------------090500090106020206050609" Subject: [manet] Re: Ad Hoc IP 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: , --------------090500090106020206050609 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Thanks for your reply Jaehoon! Now I've also read draft-ietf-manet-autoconf-01.txt. It seems your proposal is better than the "autoconf" draft mainly because address duplication is detected not only once "at the beginning", but continuously thanks to weak DAD, step (f). Is this correct? Thanks Ali Jaehoon Jeong wrote: >Hi, Ali. > > >----- Original Message ----- >From: "Ali Hamidian" >To: >Sent: Tuesday, June 24, 2003 12:32 AM >Subject: Ad Hoc IP Address Autoconfiguration > > >>Hi! >> >>I started to read your draft today. A question arised when I came to >>Section 5.1.1, step (c): >>* What is the TTL value used when the mobile node broadcasts the AREQ >>message? >> > TTL value is a system parameter. I think that 10 is appropriate. > This value should be tuned appropriately, > considering the characteristics of the corresponding MANET. > >>It seems the TTL value must be "big enough" so that all mobile nodes in >>the MANET can receive the AREQ message - which resluts in a lot of >>traffic created in the MANET. >> > > Not at all. Because my scheme adopts the weak or delayed DAD > for checking the duplication of IP address, it need not big TTL value. > > /Jaehoon > > >>Thanks in advance >>Ali Hamidian >> > --------------090500090106020206050609 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Thanks for your reply Jaehoon!

Now I've also read draft-ietf-manet-autoconf-01.txt. It seems your proposal is better than the "autoconf" draft mainly because address duplication is detected not only once "at the beginning", but continuously thanks to weak DAD, step (f). Is this correct?

Thanks
Ali

Jaehoon Jeong wrote:
Hi, Ali.


----- Original Message ----- 
From: "Ali Hamidian" <alexh@telecom.lth.se>
To: <paul@etri.re.kr>
Sent: Tuesday, June 24, 2003 12:32 AM
Subject: Ad Hoc IP Address Autoconfiguration


Hi!

I started to read your draft today. A question arised when I came to 
Section 5.1.1, step (c):
* What is the TTL value used when the mobile node broadcasts the AREQ 
message?
   TTL value is a system parameter. I think that 10 is appropriate.
   This value should be tuned appropriately, 
   considering the characteristics of the corresponding MANET.

It seems the TTL value must be "big enough" so that all mobile nodes in 
the MANET can receive the AREQ message - which resluts in a lot of 
traffic created in the MANET.
   
   Not at all. Because my scheme adopts the weak or delayed DAD
   for checking the duplication of IP address, it need not big TTL value.
   
   /Jaehoon
   
Thanks in advance
Ali Hamidian



--------------090500090106020206050609-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jun 24 10:12: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 KAA17553 for ; Tue, 24 Jun 2003 10:12:59 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5OECW415161 for manet-archive@odin.ietf.org; Tue, 24 Jun 2003 10:12:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UoX9-0003wS-W4 for manet-web-archive@optimus.ietf.org; Tue, 24 Jun 2003 10:12:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17507 for ; Tue, 24 Jun 2003 10:12:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UoX7-0003Bn-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 10:12:29 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UoX2-0003Bk-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 10:12:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UoWf-0003vI-Iy; Tue, 24 Jun 2003 10:12:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UoVi-0003uf-Rv for manet@optimus.ietf.org; Tue, 24 Jun 2003 10:11: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 KAA17369 for ; Tue, 24 Jun 2003 10:10:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UoVg-0003BU-00 for manet@ietf.org; Tue, 24 Jun 2003 10:11:00 -0400 Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net) by ietf-mx with smtp (Exim 4.12) id 19UoVV-0003B1-00 for manet@ietf.org; Tue, 24 Jun 2003 10:10:49 -0400 Received: (qmail 26934 invoked by uid 65534); 24 Jun 2003 14:09:22 -0000 Received: from e48-2-web.dtrd.de (EHLO JUPITER) (192.166.62.143) by mail.gmx.net (mp021) with SMTP; 24 Jun 2003 16:09:22 +0200 From: "Nico Bayer" To: "IETF-MANET" Date: Tue, 24 Jun 2003 16:08:57 +0200 Message-ID: <007b01c33a5a$2784fb40$8f3ea6c0@JUPITER> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_007C_01C33A6A.EB0DCB40" 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] DHCPv6 for Addressautoconfiguration Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_007C_01C33A6A.EB0DCB40 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hello list, are there any ideas if it is possible and realistic, to use the DHCPv6 Protocol for addressautoconfiguration in a manet? Maybe someone can help me or point me to papers containing this problem. Thank you in advance. Regards, Nico ------=_NextPart_000_007C_01C33A6A.EB0DCB40 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hello list,

 

are there any ideas if = it is possible and realistic, to use the DHCPv6 Protocol for = addressautoconfiguration in a manet?

Maybe someone can help = me or point me to papers containing this problem.

 

Thank you in = advance.

 

Regards, = Nico

------=_NextPart_000_007C_01C33A6A.EB0DCB40-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jun 24 15:45: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 PAA07102 for ; Tue, 24 Jun 2003 15:45:48 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5OJjKs13130 for manet-archive@odin.ietf.org; Tue, 24 Jun 2003 15:45:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UtjE-0003Ph-Ex for manet-web-archive@optimus.ietf.org; Tue, 24 Jun 2003 15:45: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 PAA07064 for ; Tue, 24 Jun 2003 15:45:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UtjC-0006Ya-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 15:45:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Utj7-0006YW-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 15:45:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Utiw-0003KL-Bn; Tue, 24 Jun 2003 15:45:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Utiq-0003Ij-Qr for manet@optimus.ietf.org; Tue, 24 Jun 2003 15:44: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 PAA07022 for ; Tue, 24 Jun 2003 15:44:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Utia-0006Xo-00 for manet@ietf.org; Tue, 24 Jun 2003 15:44:40 -0400 Received: from sunlight.wichita.edu ([156.26.1.5]) by ietf-mx with esmtp (Exim 4.12) id 19UtiP-0006XK-00 for manet@ietf.org; Tue, 24 Jun 2003 15:44:29 -0400 Received: from CONVERSION-DAEMON.sunlight.wichita.edu by sunlight.wichita.edu (PMDF V6.1 #30593) id <0HH000001459NX@sunlight.wichita.edu> for manet@ietf.org; Tue, 24 Jun 2003 14:43:57 -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 <0HH00006G459IA@sunlight.wichita.edu> for manet@ietf.org; Tue, 24 Jun 2003 14:43:57 -0500 (CDT) Date: Tue, 24 Jun 2003 14:43:56 -0500 From: jhchauhan To: manet@ietf.org Message-id: <3EF3776E@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: jhchauhan@wichita.edu X-EXP32-SerialNo: 00003023 Content-Transfer-Encoding: 7bit Subject: [manet] Working group on IEEE 802.11 DCF ?? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 joined this group a couple of days ago. I am interested in working on IEEE 802.11 MAC Layer(DCF). I wanted to know if there's a working group exclusively for discussing issues and ideas related to the MAC layer for Ad Hoc networks like this group is for MANETs. I would appreciate any information on it. Thanks, Jasmina Jasmina Chauhan Graduate Assistant Wichita State University Kansas. Voice : 316-682-6133 (Res) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jun 24 16:16:41 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 QAA08419 for ; Tue, 24 Jun 2003 16:16:40 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5OKGDq17863 for manet-archive@odin.ietf.org; Tue, 24 Jun 2003 16:16:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UuD7-0004e2-2X for manet-web-archive@optimus.ietf.org; Tue, 24 Jun 2003 16:16: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 QAA08380 for ; Tue, 24 Jun 2003 16:16:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UuD5-0006nS-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 16:16:11 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19UuCz-0006nP-00 for manet-web-archive@ietf.org; Tue, 24 Jun 2003 16:16:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UuCv-0004X4-EE; Tue, 24 Jun 2003 16:16:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UuCn-0004Ux-5z for manet@optimus.ietf.org; Tue, 24 Jun 2003 16:15: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 QAA08366 for ; Tue, 24 Jun 2003 16:15:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UuCW-0006n6-00 for manet@ietf.org; Tue, 24 Jun 2003 16:15:36 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19UuCL-0006mS-00 for manet@ietf.org; Tue, 24 Jun 2003 16:15:25 -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 h5OKEKDi001347; Tue, 24 Jun 2003 16:14:20 -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 h5OKEKMD010732; Tue, 24 Jun 2003 16:14:20 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.1.1.32) with SMTP id M2003062416142016903 ; Tue, 24 Jun 2003 16:14:20 -0400 Message-Id: <5.1.1.5.2.20030624160145.032204a0@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Tue, 24 Jun 2003 16:15:51 -0400 To: "Nico Bayer" , "IETF-MANET" From: Joe Macker Subject: Re: [manet] DHCPv6 for Addressautoconfiguration In-Reply-To: <007b01c33a5a$2784fb40$8f3ea6c0@JUPITER> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 04:08 PM 6/24/2003 +0200, Nico Bayer wrote: >Hello list, > > > >are there any ideas if it is possible and realistic, to use the DHCPv6 Protocol for addressautoconfiguration in a manet? It is definitely possible and we have demonstrated this... William Chao (works with me) has added some relay agent functionality to the IBM DHCPv6 code release. We would hope to see this potentially integrated into the code release soon. -Joe >Maybe someone can help me or point me to papers containing this problem. > > > >Thank you in advance. > > > >Regards, Nico _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 03:04: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 DAA10718 for ; Thu, 26 Jun 2003 03:04:58 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5Q74VO01383 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 03:04:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VQo3-0000ME-Iw for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 03:04: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 DAA10711 for ; Thu, 26 Jun 2003 03:04:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VQnz-0006FR-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 03:04:27 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VQnu-0006FJ-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 03:04:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VQnZ-0000BM-MX; Thu, 26 Jun 2003 03:04:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VQnG-0000B5-2e for manet@optimus.ietf.org; Thu, 26 Jun 2003 03:03: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 DAA10702 for ; Thu, 26 Jun 2003 03:03:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VQmx-0006F8-00 for manet@ietf.org; Thu, 26 Jun 2003 03:03:23 -0400 Received: from ims21.stu.nus.edu.sg ([137.132.14.228]) by ietf-mx with esmtp (Exim 4.12) id 19VQmm-0006F4-00 for manet@ietf.org; Thu, 26 Jun 2003 03:03:12 -0400 Received: from mbxsrv22.stu.nus.edu.sg ([137.132.14.232]) by ims21.stu.nus.edu.sg with Microsoft SMTPSVC(5.0.2195.5329); Thu, 26 Jun 2003 15:02:50 +0800 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="utf-8" Content-Transfer-Encoding: base64 Date: Thu, 26 Jun 2003 15:02:50 +0800 Message-ID: <90291BA1D4EB8F4998A5BDD4C37DE92C549D05@MBXSRV22.stu.nus.edu.sg> Thread-Topic: about ns-2 codes for hybrid network Thread-Index: AcM7sPTa4pMQQCamRbKcqNCz6SYxAA== From: "Wu Mintao" To: X-OriginalArrivalTime: 26 Jun 2003 07:02:50.0758 (UTC) FILETIME=[F505B260:01C33BB0] Content-Transfer-Encoding: base64 Subject: [manet] about ns-2 codes for hybrid network Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 SGVsbG8sIERlYXIgYWxsLA0KIEkgYW0gbG9va2luZyBmb3IgbnMgc2ltdWxhdGlvbiBjb2RlcyBm b3IgaHlicmlkIG5ldHdvcmssIHdoaWNoIGlzIHRoZSBtaXh0dXJlIG9mIHdpcmVkIGFuZCB3aXJl bGVzcyBhZCBob2MgbmV0d29yay4gZG9lcyBhbnlvbmUga25vdyB3aGVyZSBpIGNhbiBnZXQgc3Vj aCBjb2Rlcz8NCiANCnlvdXJzIHNpbmNlcmVseSwNCiANCiANCm1pbnRhbw0K _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 06:07:51 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 GAA14104 for ; Thu, 26 Jun 2003 06:07:51 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QA7PF26569 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 06:07:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VTf3-0006uQ-Jg for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 06:07: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 GAA14098 for ; Thu, 26 Jun 2003 06:07:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VTez-00076h-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 06:07:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VTeu-00076e-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 06:07:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VTef-0006d3-Io; Thu, 26 Jun 2003 06:07:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VTcS-0006HX-F8 for manet@optimus.ietf.org; Thu, 26 Jun 2003 06: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 GAA14067 for ; Thu, 26 Jun 2003 06:04:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VTcO-00076I-00 for manet@ietf.org; Thu, 26 Jun 2003 06:04:40 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19VTcD-000767-00 for manet@ietf.org; Thu, 26 Jun 2003 06:04:29 -0400 Received: from paulnb (paul3.etri.re.kr [129.254.112.196]) by pec.etri.re.kr (8.11.3/8.11.3) with SMTP id h5QAFO919743; Thu, 26 Jun 2003 19:15:30 +0900 (KST) Message-ID: <00e001c3535c$de416470$c470fe81@etri.re.kr> From: "Jaehoon Jeong" To: "Ali Hamidian" Cc: , "autonet" References: <3EF71D87.7080508@telecom.lth.se> <005a01c33a22$0e8f3070$c470fe81@etri.re.kr> <3EF825F0.2080708@telecom.lth.se> Date: Sat, 26 Jul 2003 19:01:17 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DB_01C353A8.4AE83950" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [manet] Re: Ad Hoc IP 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_00DB_01C353A8.4AE83950 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 SGksIEFsaS4NCg0KICAtLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KICBGcm9tOiBBbGkg SGFtaWRpYW4gDQogIFRvOiBKYWVob29uIEplb25nIDsgbWFuZXRAaWV0Zi5vcmcgDQogIFNlbnQ6 IFR1ZXNkYXksIEp1bmUgMjQsIDIwMDMgNzoyMCBQTQ0KICBTdWJqZWN0OiBSZTogQWQgSG9jIElQ IEFkZHJlc3MgQXV0b2NvbmZpZ3VyYXRpb24NCg0KDQogIFRoYW5rcyBmb3IgeW91ciByZXBseSBK YWVob29uIQ0KDQogIE5vdyBJJ3ZlIGFsc28gcmVhZCBkcmFmdC1pZXRmLW1hbmV0LWF1dG9jb25m LTAxLnR4dC4gSXQgc2VlbXMgeW91ciBwcm9wb3NhbCBpcyBiZXR0ZXIgdGhhbiB0aGUgImF1dG9j b25mIiBkcmFmdCBtYWlubHkgYmVjYXVzZSBhZGRyZXNzIGR1cGxpY2F0aW9uIGlzIGRldGVjdGVk IG5vdCBvbmx5IG9uY2UgImF0IHRoZSBiZWdpbm5pbmciLCBidXQgY29udGludW91c2x5IHRoYW5r cyB0byB3ZWFrIERBRCwgc3RlcCAoZikuIElzIHRoaXMgY29ycmVjdD8NCg0KICAgIC0+IFllcywg aXQgaXMuDQogICAgICAgICBBbHNvLCBteSBkcmFmdCBjb25zaWRlcmVkIHRoZSBtYWludGVuYW5j ZSBvciBzdXJ2aXZhYmlsaXR5IG9mIHVwcGVyIGxheWVyIHNlc3Npb25zIGFmdGVyIHRoZSBhZGRy ZXNzIGNoYW5nZS4NCiAgICAgICAgIEkgdGhpbmsgbXkgc3VnZ2VzdGlvbiBpcyB1c2VmdWwgaW4g TUFORVQgYXV0b2NvbmZpZ3VyYXRpb24uDQogICAgDQogICAgICAgICAvSmFlaG9vbg0KDQogIFRo YW5rcw0KICBBbGkNCg0KICBKYWVob29uIEplb25nIHdyb3RlOg0KDQpIaSwgQWxpLi0tLS0tIE9y aWdpbmFsIE1lc3NhZ2UgLS0tLS0gRnJvbTogIkFsaSBIYW1pZGlhbiIgPGFsZXhoQHRlbGVjb20u bHRoLnNlPlRvOiA8cGF1bEBldHJpLnJlLmtyPlNlbnQ6IFR1ZXNkYXksIEp1bmUgMjQsIDIwMDMg MTI6MzIgQU1TdWJqZWN0OiBBZCBIb2MgSVAgQWRkcmVzcyBBdXRvY29uZmlndXJhdGlvbkhpIUkg c3RhcnRlZCB0byByZWFkIHlvdXIgZHJhZnQgdG9kYXkuIEEgcXVlc3Rpb24gYXJpc2VkIHdoZW4g SSBjYW1lIHRvIFNlY3Rpb24gNS4xLjEsIHN0ZXAgKGMpOiogV2hhdCBpcyB0aGUgVFRMIHZhbHVl IHVzZWQgd2hlbiB0aGUgbW9iaWxlIG5vZGUgYnJvYWRjYXN0cyB0aGUgQVJFUSBtZXNzYWdlPyAg IFRUTCB2YWx1ZSBpcyBhIHN5c3RlbSBwYXJhbWV0ZXIuIEkgdGhpbmsgdGhhdCAxMCBpcyBhcHBy b3ByaWF0ZS4gICBUaGlzIHZhbHVlIHNob3VsZCBiZSB0dW5lZCBhcHByb3ByaWF0ZWx5LCAgICBj b25zaWRlcmluZyB0aGUgY2hhcmFjdGVyaXN0aWNzIG9mIHRoZSBjb3JyZXNwb25kaW5nIE1BTkVU Lkl0IHNlZW1zIHRoZSBUVEwgdmFsdWUgbXVzdCBiZSAiYmlnIGVub3VnaCIgc28gdGhhdCBhbGwg bW9iaWxlIG5vZGVzIGluIHRoZSBNQU5FVCBjYW4gcmVjZWl2ZSB0aGUgQVJFUSBtZXNzYWdlIC0g d2hpY2ggcmVzbHV0cyBpbiBhIGxvdCBvZiB0cmFmZmljIGNyZWF0ZWQgaW4gdGhlIE1BTkVULiAg ICAgIE5vdCBhdCBhbGwuIEJlY2F1c2UgbXkgc2NoZW1lIGFkb3B0cyB0aGUgd2VhayBvciBkZWxh eWVkIERBRCAgIGZvciBjaGVja2luZyB0aGUgZHVwbGljYXRpb24gb2YgSVAgYWRkcmVzcywgaXQg bmVlZCBub3QgYmlnIFRUTCB2YWx1ZS4gICAgICAvSmFlaG9vbiAgIFRoYW5rcyBpbiBhZHZhbmNl QWxpIEhhbWlkaWFuDQo= ------=_NextPart_000_00DB_01C353A8.4AE83950 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWlzby04ODU5LTEiPg0KPE1FVEEgY29udGVudD0iTVNIVE1M IDYuMDAuMjgwMC4xMTA2IiBuYW1lPUdFTkVSQVRPUj4NCjxTVFlMRT48L1NUWUxFPg0KPC9IRUFE Pg0KPEJPRFkgYmdDb2xvcj0jZmZmZmZmPg0KPERJVj48Rk9OVCBmYWNlPSYjNDQ0MDQ7JiM0NzU0 ODsgc2l6ZT0yPkhpLCBBbGkuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPSYjNDQ0MDQ7 JiM0NzU0ODsgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxCTE9DS1FVT1RFIA0Kc3R5bGU9 IlBBRERJTkctUklHSFQ6IDBweDsgUEFERElORy1MRUZUOiA1cHg7IE1BUkdJTi1MRUZUOiA1cHg7 IEJPUkRFUi1MRUZUOiAjMDAwMDAwIDJweCBzb2xpZDsgTUFSR0lOLVJJR0hUOiAwcHgiPg0KICA8 RElWIHN0eWxlPSJGT05UOiAxMHB0ICYjNDQ0MDQ7JiM0NzU0ODsiPi0tLS0tIE9yaWdpbmFsIE1l c3NhZ2UgLS0tLS0gPC9ESVY+DQogIDxESVYgDQogIHN0eWxlPSJCQUNLR1JPVU5EOiAjZTRlNGU0 OyBGT05UOiAxMHB0ICYjNDQ0MDQ7JiM0NzU0ODs7IGZvbnQtY29sb3I6IGJsYWNrIj48Qj5Gcm9t OjwvQj4gPEEgDQogIHRpdGxlPWFsZXhoQHRlbGVjb20ubHRoLnNlIGhyZWY9Im1haWx0bzphbGV4 aEB0ZWxlY29tLmx0aC5zZSI+QWxpIEhhbWlkaWFuPC9BPiANCiAgPC9ESVY+DQogIDxESVYgc3R5 bGU9IkZPTlQ6IDEwcHQgJiM0NDQwNDsmIzQ3NTQ4OyI+PEI+VG86PC9CPiA8QSB0aXRsZT1wYXVs QGV0cmkucmUua3IgDQogIGhyZWY9Im1haWx0bzpwYXVsQGV0cmkucmUua3IiPkphZWhvb24gSmVv bmc8L0E+IDsgPEEgdGl0bGU9bWFuZXRAaWV0Zi5vcmcgDQogIGhyZWY9Im1haWx0bzptYW5ldEBp ZXRmLm9yZyI+bWFuZXRAaWV0Zi5vcmc8L0E+IDwvRElWPg0KICA8RElWIHN0eWxlPSJGT05UOiAx MHB0ICYjNDQ0MDQ7JiM0NzU0ODsiPjxCPlNlbnQ6PC9CPiBUdWVzZGF5LCBKdW5lIDI0LCAyMDAz IDc6MjAgUE08L0RJVj4NCiAgPERJViBzdHlsZT0iRk9OVDogMTBwdCAmIzQ0NDA0OyYjNDc1NDg7 Ij48Qj5TdWJqZWN0OjwvQj4gUmU6IEFkIEhvYyBJUCBBZGRyZXNzIA0KICBBdXRvY29uZmlndXJh dGlvbjwvRElWPg0KICA8RElWPjxCUj48L0RJVj4NCiAgPERJVj5UaGFua3MgZm9yIHlvdXIgcmVw bHkgSmFlaG9vbiE8QlI+PEJSPk5vdyBJJ3ZlIGFsc28gcmVhZCANCiAgZHJhZnQtaWV0Zi1tYW5l dC1hdXRvY29uZi0wMS50eHQuIEl0IHNlZW1zIHlvdXIgcHJvcG9zYWwgaXMgYmV0dGVyIHRoYW4g dGhlIA0KICAiYXV0b2NvbmYiIGRyYWZ0IG1haW5seSBiZWNhdXNlIGFkZHJlc3MgZHVwbGljYXRp b24gaXMgZGV0ZWN0ZWQgbm90IG9ubHkgb25jZSANCiAgImF0IHRoZSBiZWdpbm5pbmciLCBidXQg Y29udGludW91c2x5IHRoYW5rcyB0byB3ZWFrIERBRCwgc3RlcCAoZikuIElzIHRoaXMgDQogIGNv cnJlY3Q/PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT0mIzQ0NDA0OyYjNDc1NDg7IHNpemU9Mj48 L0ZPTlQ+PEJSPjxGT05UIGZhY2U9JiM0NDQwNDsmIzQ3NTQ4OyBzaXplPTI+Jm5ic3A7IC0mZ3Q7 IDxGT05UIA0KICBmYWNlPSYjNDQ0MDQ7JiM0NzU0ODsgc2l6ZT0yPlllcywgaXQgaXMuPC9GT05U PjwvRk9OVD48L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPSYjNDQ0MDQ7JiM0NzU0ODsgc2l6ZT0y PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBBbHNvPEZPTlQgDQogIGZhY2U9 JiM0NDQwNDsmIzQ3NTQ4OyBzaXplPTI+LCBteSBkcmFmdCBjb25zaWRlcmVkIHRoZSBtYWludGVu YW5jZSBvciBzdXJ2aXZhYmlsaXR5IG9mIHVwcGVyIA0KICBsYXllciBzZXNzaW9ucyA8L0ZPTlQ+ PEZPTlQgZmFjZT0mIzQ0NDA0OyYjNDc1NDg7IHNpemU9Mj5hZnRlciB0aGUgYWRkcmVzcyANCiAg Y2hhbmdlLjwvRk9OVD48L0ZPTlQ+PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT0mIzQ0NDA0OyYj NDc1NDg7IHNpemU9Mj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtJ IHRoaW5rIG15IA0KICBzdWdnZXN0aW9uIGlzIHVzZWZ1bCBpbiBNQU5FVCBhdXRvY29uZmlndXJh dGlvbi48L0ZPTlQ+PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT0mIzQ0NDA0OyYjNDc1NDg7IHNp emU9Mj4mbmJzcDsgPC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT0mIzQ0NDA0OyYjNDc1NDg7IA0K ICBzaXplPTI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7L0phZWhv b248L0ZPTlQ+PC9ESVY+PC9GT05UPg0KICA8RElWPjxGT05UIGZhY2U9JiM0NDQwNDsmIzQ3NTQ4 OyBzaXplPTI+PC9GT05UPjxCUj5UaGFua3M8QlI+QWxpPEJSPjxCUj5KYWVob29uIEplb25nIA0K ICB3cm90ZTo8QlI+PC9ESVY+DQogIDxCTE9DS1FVT1RFIGNpdGU9bWlkOjAwNWEwMWMzM2EyMiQw ZThmMzA3MCRjNDcwZmU4MUBldHJpLnJlLmtyIHR5cGU9ImNpdGUiPjxQUkUgd3JhcD0iIj5IaSwg QWxpLjxCUj48QlI+PEJSPi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gPEJSPkZyb206ICJB bGkgSGFtaWRpYW4iIDxBIGNsYXNzPW1vei10eHQtbGluay1yZmMyMzk2RSBocmVmPSJtYWlsdG86 YWxleGhAdGVsZWNvbS5sdGguc2UiPiZsdDthbGV4aEB0ZWxlY29tLmx0aC5zZSZndDs8L0E+PEJS PlRvOiA8QSBjbGFzcz1tb3otdHh0LWxpbmstcmZjMjM5NkUgaHJlZj0ibWFpbHRvOnBhdWxAZXRy aS5yZS5rciI+Jmx0O3BhdWxAZXRyaS5yZS5rciZndDs8L0E+PEJSPlNlbnQ6IFR1ZXNkYXksIEp1 bmUgMjQsIDIwMDMgMTI6MzIgQU08QlI+U3ViamVjdDogQWQgSG9jIElQIEFkZHJlc3MgQXV0b2Nv bmZpZ3VyYXRpb248QlI+PEJSPjxCUj48L1BSRT4NCiAgICA8QkxPQ0tRVU9URSB0eXBlPSJjaXRl Ij48UFJFIHdyYXA9IiI+SGkhPEJSPjxCUj5JIHN0YXJ0ZWQgdG8gcmVhZCB5b3VyIGRyYWZ0IHRv ZGF5LiBBIHF1ZXN0aW9uIGFyaXNlZCB3aGVuIEkgY2FtZSB0byA8QlI+U2VjdGlvbiA1LjEuMSwg c3RlcCAoYyk6PEJSPiogV2hhdCBpcyB0aGUgVFRMIHZhbHVlIHVzZWQgd2hlbiB0aGUgbW9iaWxl IG5vZGUgYnJvYWRjYXN0cyB0aGUgQVJFUSA8QlI+bWVzc2FnZT88QlI+PC9QUkU+PC9CTE9DS1FV T1RFPjxQUkUgd3JhcD0iIj48IS0tLS0+ICAgVFRMIHZhbHVlIGlzIGEgc3lzdGVtIHBhcmFtZXRl ci4gSSB0aGluayB0aGF0IDEwIGlzIGFwcHJvcHJpYXRlLjxCUj4gICBUaGlzIHZhbHVlIHNob3Vs ZCBiZSB0dW5lZCBhcHByb3ByaWF0ZWx5LCA8QlI+ICAgY29uc2lkZXJpbmcgdGhlIGNoYXJhY3Rl cmlzdGljcyBvZiB0aGUgY29ycmVzcG9uZGluZyBNQU5FVC48QlI+PEJSPjwvUFJFPg0KICAgIDxC TE9DS1FVT1RFIHR5cGU9ImNpdGUiPjxQUkUgd3JhcD0iIj5JdCBzZWVtcyB0aGUgVFRMIHZhbHVl IG11c3QgYmUgImJpZyBlbm91Z2giIHNvIHRoYXQgYWxsIG1vYmlsZSBub2RlcyBpbiA8QlI+dGhl IE1BTkVUIGNhbiByZWNlaXZlIHRoZSBBUkVRIG1lc3NhZ2UgLSB3aGljaCByZXNsdXRzIGluIGEg bG90IG9mIDxCUj50cmFmZmljIGNyZWF0ZWQgaW4gdGhlIE1BTkVULjxCUj48L1BSRT48L0JMT0NL UVVPVEU+PFBSRSB3cmFwPSIiPjwhLS0tLT4gICA8QlI+ICAgTm90IGF0IGFsbC4gQmVjYXVzZSBt eSBzY2hlbWUgYWRvcHRzIHRoZSB3ZWFrIG9yIGRlbGF5ZWQgREFEPEJSPiAgIGZvciBjaGVja2lu ZyB0aGUgZHVwbGljYXRpb24gb2YgSVAgYWRkcmVzcywgaXQgbmVlZCBub3QgYmlnIFRUTCB2YWx1 ZS48QlI+ICAgPEJSPiAgIC9KYWVob29uPEJSPiAgIDxCUj48L1BSRT4NCiAgICA8QkxPQ0tRVU9U RSB0eXBlPSJjaXRlIj48UFJFIHdyYXA9IiI+VGhhbmtzIGluIGFkdmFuY2U8QlI+QWxpIEhhbWlk aWFuPEJSPjxCUj48L1BSRT48L0JMT0NLUVVPVEU+PFBSRSB3cmFwPSIiPjwhLS0tLT48QlI+PC9Q UkU+PC9CTE9DS1FVT1RFPjxCUj48L0JMT0NLUVVPVEU+PC9CT0RZPjwvSFRNTD4NCg== ------=_NextPart_000_00DB_01C353A8.4AE83950-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 06:39: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 GAA14722 for ; Thu, 26 Jun 2003 06:39:49 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QAdN104313 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 06:39:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VU9z-00017U-8c for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 06:39: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 GAA14701 for ; Thu, 26 Jun 2003 06:39:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VU9v-0007Gi-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 06:39:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VU9p-0007GW-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 06:39:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VU9d-0000yB-Ni; Thu, 26 Jun 2003 06:39:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VU96-0000xN-GS for manet@optimus.ietf.org; Thu, 26 Jun 2003 06:38:43 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14688 for ; Thu, 26 Jun 2003 06:38:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VU92-0007G9-00 for manet@ietf.org; Thu, 26 Jun 2003 06:38:24 -0400 Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx with esmtp (Exim 4.12) id 19VU8r-0007G3-00 for manet@ietf.org; Thu, 26 Jun 2003 06:38:13 -0400 Received: from telecom.lth.se (lina23.tts.lth.se [130.235.18.83]) by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id MAA06970; Thu, 26 Jun 2003 12:37:48 +0200 (MET DST) Message-ID: <3EFACCD1.8040305@telecom.lth.se> Date: Thu, 26 Jun 2003 12:37:05 +0200 From: Ali Hamidian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: Wu Mintao CC: manet@ietf.org Subject: Re: [manet] about ns-2 codes for hybrid network References: <90291BA1D4EB8F4998A5BDD4C37DE92C549D05@MBXSRV22.stu.nus.edu.sg> Content-Type: multipart/alternative; boundary="------------000706030508060502080108" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------000706030508060502080108 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Mintao, Wu Mintao wrote: >Hello, Dear all, > I am looking for ns simulation codes for hybrid network, which is the mixture of wired and wireless ad hoc network. does anyone know where i can get such codes? > See Marc Greis tutorial, Section X.1 "Creating a simple wired-cum-wireless scenario": http://www.isi.edu/nsnam/ns/tutorial/index.html However, his example works only with the ad hoc routing protocol DSDV and not with the others that are implemented in ns (AODV, TORA and DSR). If you want to use AODV instead of DSDV, you can use my extended AODV code (called AODV+ and based on draft-wakikawa-manet-globalv6-01.txt) which can be downloaded from http://www.telecom.lth.se/Personal/alexh/ Regards Ali Hamidian > > >yours sincerely, > > >mintao >wx%jw'm 0)fjb > --------------000706030508060502080108 Content-Type: text/html; charset=UTF-8 X-MIME-Autoconverted: from 8bit to quoted-printable by anyida.tts.lth.se id MAA06970 Content-Transfer-Encoding: quoted-printable Hi Mintao,


Wu Mintao wrote:
Hello, Dear all,
 I am looking for ns simulation code=
s for hybrid network, which is the mixture of wired and wireless ad hoc n=
etwork. does anyone know where i can get such codes?
See Marc Greis tutorial, Section X.1 "Creating a simple wired-cum= -wireless scenario": http://www.isi.edu/nsnam/ns/tutorial/index.html
However, his example works only with the ad hoc routing protocol DSDV and not with the others that are implemented in ns (AODV, TORA and DSR). If y= ou want to use AODV instead of DSDV, you can use my extended AODV code (call= ed AODV+ and based on=C2=A0draft-wakikawa-manet-globalv6-01.txt) which can b= e downloaded from http://www.tel= ecom.lth.se/Personal/alexh/

Regards
Ali Hamidian

 
yours sincerely,
 
 
mintao
wx%jw=
'=7F=1Bm=0C0)fj=7Fb

--------------000706030508060502080108-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 10:02:50 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 KAA25436 for ; Thu, 26 Jun 2003 10:02:50 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QE2Nk04332 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 10:02:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VXKR-00017n-4i for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 10:02: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 KAA25414 for ; Thu, 26 Jun 2003 10:02:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VXKP-0001mu-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 10:02:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VXKJ-0001mr-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 10:02:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VXK5-0000zc-8x; Thu, 26 Jun 2003 10:02:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VXJD-0000zA-Ro for manet@optimus.ietf.org; Thu, 26 Jun 2003 10:01: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 KAA25370 for ; Thu, 26 Jun 2003 10:00:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VXIf-0001mP-00 for manet@ietf.org; Thu, 26 Jun 2003 10:00:33 -0400 Received: from london.unik.no ([193.156.97.32]) by ietf-mx with esmtp (Exim 4.12) id 19VXIU-0001mC-00 for manet@ietf.org; Thu, 26 Jun 2003 10:00:23 -0400 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Thu, 26 Jun 2003 15:59:28 +0200 Message-ID: Thread-Topic: OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? thread-index: AcM76yjOz4lb05ReQAaMqc/5tlCIwA== From: "Andreas Hafslund" To: Content-Transfer-Encoding: quoted-printable Subject: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable All, I am considering a "semi"-mobile wireless network with "broadband" radio = links. Typical bandwidth between 2 Mbps up to 30-40 Mbps. These radio = routers will usually not be moving, however, they need to be quickly = operational when deployd. Also, they will be deployed in vehicles, so it = can be an advantage if they also are operational when moving. Each radio = router will have one or more mobile ad hoc network running as a = subnetwork. What I am interested in knowing is if the best solution is to run OSPF = in this backbone radio network, or if there are any advantages in = running OLSR or TBRPF. What is the gain and loss (overhead etc), support = for mobility etc. I was wondering if anyone has any thoughts/real life = experience/simulation results with scenarios like this. Note, I will be running an ad hoc routing protocol in the subnetwork, = but what is the best solution for the backbone radio (IP)-network? Regards, Andreas Hafslund THALES Communication AS Norway _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 10:30: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 KAA27905 for ; Thu, 26 Jun 2003 10:29:22 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QEStr14277 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 10:28:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VXk7-0003iC-TQ for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 10:28:55 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27853 for ; Thu, 26 Jun 2003 10:27:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VXhK-0003KG-BW; Thu, 26 Jun 2003 10:26:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VXfF-0003Cg-Bj for manet@optimus.ietf.org; Thu, 26 Jun 2003 10:25: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 KAA27632 for ; Thu, 26 Jun 2003 10:23:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VXet-0001uQ-00 for manet@ietf.org; Thu, 26 Jun 2003 10:23:31 -0400 Received: from nautique.ornl.gov ([160.91.64.128]) by ietf-mx with esmtp (Exim 4.12) id 19VXeg-0001tl-00 for manet@ietf.org; Thu, 26 Jun 2003 10:23:19 -0400 Received: from LOCALHOST (LOCALHOST [127.0.0.1]) by nautique.ornl.gov (Postfix) with ESMTP id 570D23F6B; Thu, 26 Jun 2003 10:20:56 -0400 (EDT) Subject: Re: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? From: Lawrence MacIntyre To: Andreas Hafslund Cc: manet@ietf.org In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-CJ3KjwlOTOIMyCvEWgXx" Message-Id: <1056637256.1709.4025.camel@nautique> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 26 Jun 2003 10:20:56 -0400 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=-CJ3KjwlOTOIMyCvEWgXx Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Andreas: It depends on the relative movement of your backbone nodes. In general, however, OSPF is designed for infrastructured networks with relatively little change. It is conservative about noticing change, which isn't generally good in an Ad-hoc network, and it is very noisy when it finally sends the updates, which is also not usually very good in an Ad-hoc network. However, if there are only a few backbone nodes and they are always in the same relative configuration, then it really won't matter much. On Thu, 2003-06-26 at 09:59, Andreas Hafslund wrote: > All, >=20 > I am considering a "semi"-mobile wireless network with "broadband" radio = links. Typical bandwidth between 2 Mbps up to 30-40 Mbps. These radio route= rs will usually not be moving, however, they need to be quickly operational= when deployd. Also, they will be deployed in vehicles, so it can be an adv= antage if they also are operational when moving. Each radio router will hav= e one or more mobile ad hoc network running as a subnetwork. >=20 > What I am interested in knowing is if the best solution is to run OSPF in= this backbone radio network, or if there are any advantages in running OLS= R or TBRPF. What is the gain and loss (overhead etc), support for mobility = etc. >=20 > I was wondering if anyone has any thoughts/real life experience/simulatio= n results with scenarios like this. >=20 > Note, I will be running an ad hoc routing protocol in the subnetwork, but= what is the best solution for the backbone radio (IP)-network? >=20 > Regards, > Andreas Hafslund > THALES Communication AS > Norway >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet --=20 Lawrence MacIntyre 865.574.8696 lpz@ornl.gov Oak Ridge National Laboratory High Performance Information Infrastructure Technology Group --=-CJ3KjwlOTOIMyCvEWgXx Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQA++wFICNjP8rawCW4RAqtPAKCGNoc1IG1sd7KqPQEQt9/We1IksQCfRiUl RpDsGzigsTl3IGAuTiNl0bU= =zGmi -----END PGP SIGNATURE----- --=-CJ3KjwlOTOIMyCvEWgXx-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 11:32: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 LAA03487 for ; Thu, 26 Jun 2003 11:32:14 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QFVlv08318 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 11:31:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VYix-0002A5-7T for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 11:31:47 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03406 for ; Thu, 26 Jun 2003 11:31:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VYhG-000224-2d; Thu, 26 Jun 2003 11:30:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VYgY-0001z0-Vt for manet@optimus.ietf.org; Thu, 26 Jun 2003 11:29:19 -0400 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03014 for ; Thu, 26 Jun 2003 11:29:10 -0400 (EDT) Received: from yana.inria.fr (yana.inria.fr [128.93.9.62]) by concorde.inria.fr (8.11.1/8.11.1) with ESMTP id h5QFSLj23575; Thu, 26 Jun 2003 17:28:21 +0200 (MET DST) Received: from kefrida (kefrida.inria.fr [128.93.17.86]) by yana.inria.fr (8.11.1/8.11.1) with SMTP id h5QFSLT17827; Thu, 26 Jun 2003 17:28:21 +0200 (MET DST) Message-ID: <001f01c33bf7$8e49ada0$56115d80@kefrida> From: "Emmanuel Baccelli" To: "Andreas Hafslund" , References: Subject: Re: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? Date: Thu, 26 Jun 2003 17:28:12 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 In fact there are numerous problems with the use of OSPF as is on wireless links. It may work to some extent if the nodes are not moving (you were talking about semi-mobility). But on the other hand, it will essentially not work if the nodes are moving. In this case, the use of an ad-hoc protocol (like OLSR or TBRPF) is advisable for now. Actually several different efforts are under work on the subject of OSPF on wireless links and ad-hoc networks. Emmanuel ----- Original Message ----- From: "Andreas Hafslund" To: Sent: Thursday, June 26, 2003 3:59 PM Subject: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? > All, > > I am considering a "semi"-mobile wireless network with "broadband" radio links. Typical bandwidth between 2 Mbps up to 30-40 Mbps. These radio routers will usually not be moving, however, they need to be quickly operational when deployd. Also, they will be deployed in vehicles, so it can be an advantage if they also are operational when moving. Each radio router will have one or more mobile ad hoc network running as a subnetwork. > > What I am interested in knowing is if the best solution is to run OSPF in this backbone radio network, or if there are any advantages in running OLSR or TBRPF. What is the gain and loss (overhead etc), support for mobility etc. > > I was wondering if anyone has any thoughts/real life experience/simulation results with scenarios like this. > > Note, I will be running an ad hoc routing protocol in the subnetwork, but what is the best solution for the backbone radio (IP)-network? > > Regards, > Andreas Hafslund > THALES Communication AS > Norway > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 11:57: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 LAA05891 for ; Thu, 26 Jun 2003 11:57:45 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QFvIm13241 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 11:57:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VZ7e-0003RU-QX for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 11:57: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 LAA05831 for ; Thu, 26 Jun 2003 11:57:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VZ7d-0003Fb-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 11:57:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VZ7Y-0003FT-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 11:57:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VZ7P-0003KO-94; Thu, 26 Jun 2003 11:57:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VZ7B-0003IN-1s for manet@optimus.ietf.org; Thu, 26 Jun 2003 11:56: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 LAA05541 for ; Thu, 26 Jun 2003 11:56:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VYzS-00034B-00 for manet@ietf.org; Thu, 26 Jun 2003 11:48:50 -0400 Received: from capella.nps.navy.mil ([131.120.254.83] helo=[140.32.132.66]) by ietf-mx with esmtp (Exim 4.12) id 19VYzH-00032n-00 for manet@ietf.org; Thu, 26 Jun 2003 11:48:39 -0400 Received: from no.name.available by [140.32.132.66] via smtpd (for [132.151.6.1]) with ESMTP; Thu, 26 Jun 2003 08:44:46 -0700 Received: from ro178-129.ro.nps.navy.mil (ro178-129.ro.nps.navy.mil [131.120.178.129]) by capella.nps.navy.mil (8.12.9/8.12.9) with ESMTP id h5QFl81h009575; Thu, 26 Jun 2003 08:47:08 -0700 (PDT) Subject: Re: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? From: Rex Buddenberg To: Emmanuel Baccelli Cc: Andreas Hafslund , manet@ietf.org In-Reply-To: <001f01c33bf7$8e49ada0$56115d80@kefrida> References: <001f01c33bf7$8e49ada0$56115d80@kefrida> Content-Type: text/plain Message-Id: <1056642358.3728.8.camel@ro178-129.ro.nps.navy.mil> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 26 Jun 2003 08:45:58 -0700 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Andreas, It depends a lot on what you mean by 'moving' and your explanation leaves some ambiguity. One definition is a simple geographical move that may mean that a station is not operating (or is shaded) for a period of time. But when that station comes back up, the network topology isn't changed. Another definition of 'move' is topopology change, meaning that the network needs to be reconverged. In real world mobile situations, both versions happen but they affect the network in different ways. If you have links and nodes that disappear and reappear (first definition), then you want some stability in the network since that intermittency should not trigger a lot of net convergence overhead activity. If it did, you'd get oscillations and likely some instabilities. The US Navy is using OSPF in its ship-shore autonomous systems and it seems to be well suited to this situation -- a ship may go in and out of satellite connectivity, but that doesn't affect the topology -- after, say, a power failure, the ship will come back up and the net topology is unchanged. In this case, some of the things we don't like about OSPF in MANET (lethargic reactions to topology changes) are good. On Thu, 2003-06-26 at 08:28, Emmanuel Baccelli wrote: > In fact there are numerous problems with the use of OSPF as is on wireless > links. It may work to some extent if the nodes are not moving (you were > talking about semi-mobility). But on the other hand, it will essentially not > work if the nodes are moving. In this case, the use of an ad-hoc protocol > (like OLSR or TBRPF) is advisable for now. Actually several different > efforts are under work on the subject of OSPF on wireless links and ad-hoc > networks. > Emmanuel > > ----- Original Message ----- > From: "Andreas Hafslund" > To: > Sent: Thursday, June 26, 2003 3:59 PM > Subject: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? > > > > All, > > > > I am considering a "semi"-mobile wireless network with "broadband" radio > links. Typical bandwidth between 2 Mbps up to 30-40 Mbps. These radio > routers will usually not be moving, however, they need to be quickly > operational when deployd. Also, they will be deployed in vehicles, so it can > be an advantage if they also are operational when moving. Each radio router > will have one or more mobile ad hoc network running as a subnetwork. > > > > What I am interested in knowing is if the best solution is to run OSPF in > this backbone radio network, or if there are any advantages in running OLSR > or TBRPF. What is the gain and loss (overhead etc), support for mobility > etc. > > > > I was wondering if anyone has any thoughts/real life experience/simulation > results with scenarios like this. > > > > Note, I will be running an ad hoc routing protocol in the subnetwork, but > what is the best solution for the backbone radio (IP)-network? > > > > Regards, > > Andreas Hafslund > > THALES Communication AS > > Norway > > > > > > _______________________________________________ > > 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 -- Rex Buddenberg _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 15:25: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 PAA17290 for ; Thu, 26 Jun 2003 15:25:48 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QJPKU21316 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 15:25:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VcMy-0005Xj-6y for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 15:25: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 PAA17111 for ; Thu, 26 Jun 2003 15:23:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VcL6-00058T-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 15:23:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VcL0-00058Q-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 15:23:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VcKj-0004yM-Bf; Thu, 26 Jun 2003 15:23:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VcKT-0004y5-5k for manet@optimus.ietf.org; Thu, 26 Jun 2003 15:22: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 PAA17084 for ; Thu, 26 Jun 2003 15:22:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VcKC-00057a-00 for manet@ietf.org; Thu, 26 Jun 2003 15:22:28 -0400 Received: from exchange.mabuhaynetworks.com ([206.169.233.186] helo=exchange.vivato.net) by ietf-mx with esmtp (Exim 4.12) id 19VcK1-000562-00 for manet@ietf.org; Thu, 26 Jun 2003 15:22:18 -0400 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? Date: Thu, 26 Jun 2003 12:20:46 -0700 Message-ID: Thread-Topic: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? Thread-Index: AcM7+AhBit58cfc0QxiRSgPBfVmeJQAH/MSg From: "Jim Thompson" To: "Emmanuel Baccelli" , "Andreas Hafslund" , Content-Transfer-Encoding: quoted-printable Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Let us not forget that even stationary wireless links fade. > -----Original Message----- > From: Emmanuel Baccelli [mailto:Emmanuel.Baccelli@inria.fr] > Sent: Thursday, June 26, 2003 8:28 AM > To: Andreas Hafslund; manet@ietf.org > Subject: Re: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless > network? >=20 > In fact there are numerous problems with the use of OSPF as is on wireless > links. It may work to some extent if the nodes are not moving (you were > talking about semi-mobility). But on the other hand, it will essentially > not > work if the nodes are moving. In this case, the use of an ad-hoc protocol > (like OLSR or TBRPF) is advisable for now. Actually several different > efforts are under work on the subject of OSPF on wireless links and ad-hoc > networks. > Emmanuel >=20 > ----- Original Message ----- > From: "Andreas Hafslund" > To: > Sent: Thursday, June 26, 2003 3:59 PM > Subject: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? >=20 >=20 > > All, > > > > I am considering a "semi"-mobile wireless network with "broadband" radio > links. Typical bandwidth between 2 Mbps up to 30-40 Mbps. These radio > routers will usually not be moving, however, they need to be quickly > operational when deployd. Also, they will be deployed in vehicles, so it > can > be an advantage if they also are operational when moving. Each radio > router > will have one or more mobile ad hoc network running as a subnetwork. > > > > What I am interested in knowing is if the best solution is to run OSPF > in > this backbone radio network, or if there are any advantages in running > OLSR > or TBRPF. What is the gain and loss (overhead etc), support for mobility > etc. > > > > I was wondering if anyone has any thoughts/real life > experience/simulation > results with scenarios like this. > > > > Note, I will be running an ad hoc routing protocol in the subnetwork, > but > what is the best solution for the backbone radio (IP)-network? > > > > Regards, > > Andreas Hafslund > > THALES Communication AS > > Norway > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 16:22: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 QAA19946 for ; Thu, 26 Jun 2003 16:22:45 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QKMIP11849 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 16:22:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VdG5-000352-VA for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 16:22: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 QAA19898 for ; Thu, 26 Jun 2003 16:22:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VdG3-0005du-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 16:22:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VdFy-0005dr-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 16:22:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VdFp-0002pH-6H; Thu, 26 Jun 2003 16:22:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VdEi-0002jD-JK for manet@optimus.ietf.org; Thu, 26 Jun 2003 16:21: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 QAA19840 for ; Thu, 26 Jun 2003 16:20:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VdER-0005dH-00 for manet@ietf.org; Thu, 26 Jun 2003 16:20:35 -0400 Received: from paul.rutgers.edu ([128.6.5.53]) by ietf-mx with esmtp (Exim 4.12) id 19VdEH-0005c0-00 for manet@ietf.org; Thu, 26 Jun 2003 16:20:25 -0400 Received: (from pkamat@localhost) by paul.rutgers.edu (8.11.7+Sun/8.8.8) id h5QKJBT07548; Thu, 26 Jun 2003 16:19:11 -0400 (EDT) Date: Thu, 26 Jun 2003 16:19:11 -0400 (EDT) From: Pandurang Kamat X-Sender: pkamat@paul.rutgers.edu To: manet@ietf.org In-Reply-To: <1056642358.3728.8.camel@ro178-129.ro.nps.navy.mil> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] mobile code in manet Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi everyone, Can anyone please point me to some resources/papers etc that deal with 1] mobile code or agent systems in ad-hoc and/or sensor networks. 2] approaches to defending ad hoc networks against intrusions and malicious nodes Also, if there are any simulators out there that allow modelling mobile code behaviour ? - Pandurang Kamat PhD student Department of Computer Science Rutgers University _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 16:59: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 QAA21166 for ; Thu, 26 Jun 2003 16:59:43 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5QKxGG27637 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 16:59:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vdps-0007Bg-Pn for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 16:59: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 QAA21153 for ; Thu, 26 Jun 2003 16:59:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Vdpq-0005vP-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 16:59:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Vdpl-0005vM-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 16:59:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vdpe-00077P-GT; Thu, 26 Jun 2003 16:59:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vdoi-000721-Ja for manet@optimus.ietf.org; Thu, 26 Jun 2003 16:58: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 QAA21108 for ; Thu, 26 Jun 2003 16:57:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Vdo2-0005u6-00 for manet@ietf.org; Thu, 26 Jun 2003 16:57:22 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 19Vdns-0005tX-00 for manet@ietf.org; Thu, 26 Jun 2003 16:57:12 -0400 Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id C03DC1E4044; Thu, 26 Jun 2003 17:04:56 -0400 (EDT) Received: from verdi (verdi.ece.cornell.edu [128.84.210.27]) by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id h5QKuDg02948; Thu, 26 Jun 2003 16:56:13 -0400 Date: Thu, 26 Jun 2003 16:55:01 -0400 (EDT) From: "haas@ece.cornell.edu" To: Pandurang Kamat Cc: manet@ietf.org Subject: Re: [manet] mobile code in manet 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 Pandurang, > Can anyone please point me to some resources/papers etc > that deal with ... > 2] approaches to defending ad hoc networks against > intrusions and malicious nodes You will find a good summary of the security approaches for ad hoc and sensor networks at: http://www.ccs.neu.edu/home/zhufeng/security_manet.html Also, below I list some of our works in this area ... enjoy! Zygmunt. ==--==-== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Prof. Zygmunt J. Haas http://people.ece.cornell.edu/haas Wireless Networks Laboratory http://wnl.ece.cornell.edu School of Electrical Engineering Cornell University tel: +1-607-255-3454 323 Frank Rhodes Hall fax: +1-607-255-9072 Ithaca, NY 14853 e-mail: haas@ece.cornell.edu U.S.A WNL web page: http://wnl.ece.cornell.edu ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- ========================================================================== L. Zhou and Z.J. Haas, "Securing Ad Hoc Networks," IEEE Network Magazine, vol. 13, no.6, November/December 1999 P.Papadimitratos and Z.J. Haas, "Secure Routing for Mobile Ad Hoc Networks,"SCS Communication Networks and Distributed Systems Modeling and Simulation Conference (CNDS 2002), San Antonio, TX, January 27-31, 2002. P. Papadimitratos and Z.J. Haas, "Secure Routing for Mobile Ad Hoc Networks," Working Session on Security in Wireless Ad Hoc Networks, EPFL, June 12, 2002 (published in Mobile Computing and Communications Review, vol.6, no.4 ) P. Papadimitratos and Z.J. Haas, "Performance Evaluation of Secure Routing for Mobile Ad Hoc Networks," poster presentation, ACM Workshop on Wireless Security (WiSe), Atlanta, GA, September 28, 2002 P. Papadimitratos and Z.J. Haas, "Secure Mobile Ad Hoc Networks," The Handbook of Ad Hoc Wireless Networks, CRC Press 2003 P. Papadimitratos and Z.J. Haas, ``Secure Link State for Mobile Ad Hoc Networks,'' IEEE Workshop on Security and Assurance in Ad hoc Networks, in conjunction with the 2003 International Symposium on Applications and the Internet, Orlando, FL, January 28, 2003 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 ========================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jun 26 23:29: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 XAA02959 for ; Thu, 26 Jun 2003 23:29:31 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5R3T3S22113 for manet-archive@odin.ietf.org; Thu, 26 Jun 2003 23:29:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VjuQ-0005d3-8y for manet-web-archive@optimus.ietf.org; Thu, 26 Jun 2003 23:28: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 XAA02849 for ; Thu, 26 Jun 2003 23:28:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VjZ7-0000YR-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 23:06:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19VjZ1-0000YO-00 for manet-web-archive@ietf.org; Thu, 26 Jun 2003 23:06:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VjYp-0003LT-B8; Thu, 26 Jun 2003 23:06:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VjXw-00039C-QS for manet@optimus.ietf.org; Thu, 26 Jun 2003 23:05: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 XAA02310 for ; Thu, 26 Jun 2003 23:05:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VjXt-0000XP-00 for manet@ietf.org; Thu, 26 Jun 2003 23:05:05 -0400 Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu) by ietf-mx with esmtp (Exim 4.12) id 19VjXi-0000XC-00 for manet@ietf.org; Thu, 26 Jun 2003 23:04:54 -0400 Received: by mail.eecis.udel.edu (Postfix, from userid 62) id 911EF32920; Thu, 26 Jun 2003 23:04:30 -0400 (EDT) Received: from wheatgrass.cis.udel.edu (wheatgrass.cis.udel.edu [128.4.131.63]) by mail.eecis.udel.edu (Postfix) with ESMTP id D06E43291F; Thu, 26 Jun 2003 23:04:29 -0400 (EDT) Date: Thu, 26 Jun 2003 23:04:29 -0400 (EDT) From: Chien-Chung Shen X-X-Sender: To: Pandurang Kamat Cc: Subject: Re: [manet] mobile code in manet In-Reply-To: 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: , On Thu, 26 Jun 2003, Pandurang Kamat wrote: > Hi everyone, > Can anyone please point me to some resources/papers etc that deal with > 1] mobile code or agent systems in ad-hoc and/or sensor networks. Pandurang, Take a look at the following two papers. Chien-Chung Shen, Chavalit Srisathapornphat, and Chaiporn Jaikaeo, An Adaptive Management Architecture for Ad hoc Networks, IEEE Communications, Vol. 41, No. 2, February, 2003, pp. 108-115. Chien-Chung Shen, Chavalit Srisathapornphat, and Chaiporn Jaikaeo, Sensor Information Networking Architecture and Applications, IEEE Personal Communications, Vol. 8, No. 4, August 2001, pp. 52--59. > 2] approaches to defending ad hoc networks against intrusions and > malicious nodes > > Also, if there are any simulators out there that allow modelling mobile > code behaviour ? We simulated both systems in Glomosim/QualNet. Chien-Chung > - Pandurang Kamat > PhD student > Department of Computer Science > Rutgers University _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jun 27 14: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 OAA13259 for ; Fri, 27 Jun 2003 14:55:17 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5RIsm530177 for manet-archive@odin.ietf.org; Fri, 27 Jun 2003 14:54:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VyMy-0007qe-1P for manet-web-archive@optimus.ietf.org; Fri, 27 Jun 2003 14:54:48 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13219 for ; Fri, 27 Jun 2003 14:54:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VyME-0007dK-6Y; Fri, 27 Jun 2003 14:54:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VyLk-0007bW-Oe for manet@optimus.ietf.org; Fri, 27 Jun 2003 14:53:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13131 for ; Fri, 27 Jun 2003 14:53:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19VyLV-0005Iu-00 for manet@ietf.org; Fri, 27 Jun 2003 14:53:17 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19VyLK-0005I2-00 for manet@ietf.org; Fri, 27 Jun 2003 14:53:06 -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 h5RIpVDi005057; Fri, 27 Jun 2003 14:51:31 -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 h5RIpVKP005840; Fri, 27 Jun 2003 14:51:31 -0400 (EDT) Received: from SEXTANT.itd.nrl.navy.mil ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SAVSMTP 3.1.1.32) with SMTP id M2003062714513111179 ; Fri, 27 Jun 2003 14:51:31 -0400 Message-Id: <5.1.1.5.2.20030627145038.02d74ab0@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Fri, 27 Jun 2003 14:52:50 -0400 To: "Christophe Jelger" , From: Joe Macker Subject: Re: [manet] Distance vector routing and adhoc In-Reply-To: <002901c33c7d$d9e751a0$ac5a4f82@ustrasbg.fr> 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: , As far as WG documents AODV comes to mind.. At 09:29 AM 6/27/2003 +0200, Christophe Jelger wrote: >Hi all, > >I am relatively unfamiliar with some aspects of adhoc routing and was >wondering if people could point me to some key papers describing the >performance (and potential problems) of distance vector routing in adhoc >networks. I know it is probably not the best way for routing in such >networks but I'd like to know what optimizations have been proposed in order >to increase the efficiency of distance vector routing in adhoc networks. In >particular, I'd like to know if there are some relatively well admitted >methods for optimizations. > >Thanks in advance and apologies for the (quite) silly question. ;-) > >Regards, > >Christophe > > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jun 27 14:56: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 OAA13350 for ; Fri, 27 Jun 2003 14:56:40 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5RIuAK30867 for manet-archive@odin.ietf.org; Fri, 27 Jun 2003 14:56:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vxxq-0008Ks-Ld for manet-web-archive@optimus.ietf.org; Fri, 27 Jun 2003 14:28:50 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10273 for ; Fri, 27 Jun 2003 14:28:46 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vxx3-0007hF-SQ; Fri, 27 Jun 2003 14:28:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VuTW-0002NW-7B for manet@optimus.ietf.org; Fri, 27 Jun 2003 10:45:18 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22408; Fri, 27 Jun 2003 07:33:13 -0400 (EDT) Message-Id: <200306271133.HAA22408@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: Fri, 27 Jun 2003 07:33:13 -0400 Subject: [manet] I-D ACTION:draft-ietf-manet-tbrpf-09.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 : Topology Dissemination Based on Reverse-Path Forwarding (TBRPF) Author(s) : R. Ogier, M. Lewis, F. Templin Filename : draft-ietf-manet-tbrpf-09.txt Pages : 49 Date : 2003-6-26 TBRPF is a proactive, link-state routing protocol designed for mobile ad-hoc networks, which provides hop-by-hop routing along shortest paths to each destination. Each node running TBRPF computes a source tree (providing paths to all reachable nodes) based on partial topology information stored in its topology table, using a modification of Dijkstra's algorithm. To minimize overhead, each node reports only *part* of its source tree to neighbors. TBRPF uses a combination of periodic and differential updates to keep all neighbors informed of the reported part of its source tree. Each node also has the option to report additional topology information (up to the full topology), to provide improved robustness in highly mobile networks. TBRPF performs neighbor discovery using 'differential' HELLO messages which report only *changes* in the status of neighbors. This results in HELLO messages that are much smaller than those of other link-state routing protocols such as OSPF. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-manet-tbrpf-09.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-tbrpf-09.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-tbrpf-09.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-6-26162810.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-manet-tbrpf-09.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-manet-tbrpf-09.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-6-26162810.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jun 27 18:33: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 SAA23994 for ; Fri, 27 Jun 2003 18:33:21 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5RMWtk00526 for manet-archive@odin.ietf.org; Fri, 27 Jun 2003 18:32:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19W1m3-00008P-CG for manet-web-archive@optimus.ietf.org; Fri, 27 Jun 2003 18:32:55 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23945 for ; Fri, 27 Jun 2003 18:32:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19W1jY-0007XI-MW; Fri, 27 Jun 2003 18:30:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19W1Z4-0006hz-2Z for manet@optimus.ietf.org; Fri, 27 Jun 2003 18:19: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 SAA23043 for ; Fri, 27 Jun 2003 18:19:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19W1Ym-0006iX-00 for manet@ietf.org; Fri, 27 Jun 2003 18:19:12 -0400 Received: from che.ojctech.com ([209.254.133.74]) by ietf-mx with esmtp (Exim 4.12) id 19W1Yb-0006iQ-00 for manet@ietf.org; Fri, 27 Jun 2003 18:19:01 -0400 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id h5RMIZfQ004734 for ; Fri, 27 Jun 2003 17:18:35 -0500 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id h5RMIZs9004732 for manet@ietf.org; Fri, 27 Jun 2003 17:18:35 -0500 Date: Fri, 27 Jun 2003 17:18:35 -0500 From: David Young To: manet@ietf.org Subject: Re: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? Message-ID: <20030627221835.GB25041@che.ojctech.com> Mail-Followup-To: manet@ietf.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Fri, Jun 27, 2003 at 02:23:40PM +0200, Andreas Hafslund wrote: > > In fact there are numerous problems with the use of OSPF as is on wireless > > links. It may work to some extent if the nodes are not moving (you were > > talking about semi-mobility). > > What are the problems with OSPF for wireless (mostly static) links? Any > thoughts/ideas/references? I am very interested in knowing about these > problems. If you will use 802.11 wireless, you should be aware that the OSPF Hello protocol will work very poorly with default settings (10s hello interval, 40s dead interval). The hellos are multicast, and multicast is very unreliable in a busy 802.11 network. Dave -- David Young OJC Technologies dyoung@ojctech.com Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat Jun 28 15:21: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 PAA01089 for ; Sat, 28 Jun 2003 15:21:12 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5SJKho24154 for manet-archive@odin.ietf.org; Sat, 28 Jun 2003 15:20:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WLFa-0006HV-TX for manet-web-archive@optimus.ietf.org; Sat, 28 Jun 2003 15:20: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 PAA01074 for ; Sat, 28 Jun 2003 15:20:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WLFZ-00051C-00 for manet-web-archive@ietf.org; Sat, 28 Jun 2003 15:20:41 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19WLFU-000515-00 for manet-web-archive@ietf.org; Sat, 28 Jun 2003 15:20:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WLEw-0006Cq-Kb; Sat, 28 Jun 2003 15:20:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WLEH-0006CH-O4 for manet@optimus.ietf.org; Sat, 28 Jun 2003 15:19: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 PAA01065 for ; Sat, 28 Jun 2003 15:19:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WLE1-00050w-00 for manet@ietf.org; Sat, 28 Jun 2003 15:19:05 -0400 Received: from farley4.colorado.edu ([128.138.129.105]) by ietf-mx with esmtp (Exim 4.12) id 19WLDq-00050s-00 for manet@ietf.org; Sat, 28 Jun 2003 15:18:54 -0400 Received: (from nobody@localhost) by farley4.Colorado.EDU (8.12.9/8.12.8/ITS-6.0/webmail) id h5SJIYTX009510; Sat, 28 Jun 2003 13:18:34 -0600 (MDT) From: Shweta.Bhandare@colorado.edu Received: from c-67-164-182-141.client.comcast.net (c-67-164-182-141.client.comcast.net [67.164.182.141]) by webmail.colorado.edu (IMP) with HTTP for ; Sat, 28 Jun 2003 13:18:34 -0600 Message-ID: <1056827914.3efdea0a878ae@webmail.colorado.edu> Date: Sat, 28 Jun 2003 13:18:34 -0600 To: manet@ietf.org Cc: timxb@colorado.edu MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2-cvs Content-Transfer-Encoding: 8bit Subject: [manet] Energy Aware DSR ID Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit The ID titled "Energy Aware DSR (EADSR)" is available. Attached below is the title, abstract, and table of contents. Regards, Shweta Internet Draft T. X Brown Expires: 23 December 2003 S. Bhandare S. Doshi University of Colorado, Boulder 23 June 2003 The Energy Aware Dynamic Source Routing Protocol Abstract The energy aware dynamic source routing (EADSR) protocol is an extension to the dynamic source routing (DSR) protocol for mobile ad hoc networks. It retains the features and benefits of DSR while it incorporates new features for energy limited nodes. The EADSR features include (1) a DSR header option so that link power costs can be passed with source routes; (2) an extended route discovery protocol to find lower energy routes than minimum hop routes; and (3) an additional route maintenance mechanism that allows the source node to respond to link changes without route disruption. The protocol is able to find routes with minimum total transmit power cost. It is able to track changes in link power on a route, choose between routes based on cost, and notify the source of new lower cost routes as they become available. This document specifies the EADSR header option and operation changes to DSR. Table of Contents: 1. Introduction 1 2. Assumptions 2 3. EADSR Protocol Overview 4 3.1. EADSR Route Discovery . . . . . . . . . . . . . . . . . . . 4 3.2. Additional Route Discovery Mechanism . . . . . . . . . . . 6 3.3. EADSR Route Maintenance . . . . . . . . . . . . . . . . . . 7 4. Conceptual Data Structures 9 4.1. Energy Aware Link Cache . . . . . . . . . . . . . . . . . 10 4.2. Acknowledgement Table . . . . . . . . . . . . . . . . . . 10 5. EADSR Header Format 11 5.1. Fixed Portion of EADSR Header . . . . . . . . . . . . . . 13 5.2. Energy Aware Route Request Option . . . . . . . . . . . . 13 5.3. Energy Aware Route Reply Option . . . . . . . . . . . . . 13 5.4. Route Error Option . . . . . . . . . . . . . . . . . . . . 13 5.5. Acknowledgement Request Option . . . . . . . . . . . . . . 13 5.6. Acknowledgement Option . . . . . . . . . . . . . . . . . 13 5.7. Energy Aware Source Route Option . . . . . . . . . . . . . 13 5.8. Pad1 Option . . . . . . . . . . . . . . . . . . . . . . . 14 5.9. PadN Option . . . . . . . . . . . . . . . . . . . . . . . 14 6. Detailed Operation 14 6.1. General Packet Processing . . . . . . . . . . . . . . . . 14 6.2. Route Discovery Processing . . . . . . . . . . . . . . . . 17 6.3. Route Maintenance Processing . . . . . . . . . . . . . . . 19 6.4. Multiple Interface Support . . . . . . . . . . . . . . . . 21 6.5. Fragmentation and Reassembly . . . . . . . . . . . . . . . 21 6.6. Flow State Processing . . . . . . . . . . . . . . . . . . 21 7. Protocol Constants and Configuration Variables 21 8. Security Considerations 21 Appendix A. Implementation and Evaluation Status 22 References 22 ----- End forwarded message ----- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat Jun 28 16:09: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 QAA02219 for ; Sat, 28 Jun 2003 16:09:45 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5SK9GD00886 for manet-archive@odin.ietf.org; Sat, 28 Jun 2003 16:09:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WM0a-0000ED-DN for manet-web-archive@optimus.ietf.org; Sat, 28 Jun 2003 16:09: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 QAA02176 for ; Sat, 28 Jun 2003 16:09:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WM0Y-0005Mc-00 for manet-web-archive@ietf.org; Sat, 28 Jun 2003 16:09:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19WM0T-0005MZ-00 for manet-web-archive@ietf.org; Sat, 28 Jun 2003 16:09:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WM0M-00007O-Cd; Sat, 28 Jun 2003 16:09:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WLzS-00005Z-Hs for manet@optimus.ietf.org; Sat, 28 Jun 2003 16:08: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 QAA02128 for ; Sat, 28 Jun 2003 16:08:04 -0400 (EDT) From: ab36@njit.edu Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WLzQ-0005Km-00 for manet@ietf.org; Sat, 28 Jun 2003 16:08:05 -0400 Received: from mail-shield1.njit.edu ([128.235.251.171]) by ietf-mx with esmtp (Exim 4.12) id 19WLzG-0005KN-00 for manet@ietf.org; Sat, 28 Jun 2003 16:07:54 -0400 Received: (from uucp@localhost) by mail-shield1.njit.edu (8.11.6/8.11.6) id h5SK6nQ06104 for ; Sat, 28 Jun 2003 16:06:49 -0400 (EDT) Received: from nodnsquery(128.235.251.32) by mail-shield1.njit.edu via csmap (V4.1) id srcAAA9ea46l; Sat, 28 Jun 03 16:06:48 -0400 Received: from webmail.njit.edu (webmail.njit.edu [128.235.251.121]) by mail-gw4.njit.edu (8.12.9/8.12.4) with ESMTP id h5SK6m9i010140 for ; Sat, 28 Jun 2003 16:06:48 -0400 (EDT) Received: (from apache@localhost) by webmail.njit.edu (8.11.7+Sun/8.11.7) id h5SJwcB18505 for manet@ietf.org; Sat, 28 Jun 2003 15:58:38 -0400 (EDT) To: manet@ietf.org Message-ID: <1056830318.3efdf36ec0e9b@webmail.njit.edu> Date: Sat, 28 Jun 2003 15:58:38 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.4 X-Originating-IP: 128.235.207.19 Content-Transfer-Encoding: 8bit Subject: [manet] hello Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hello, I am Aditi, a Master student from NJIT. I am a new member to this group and would like to have some info... My project is based on simulation of anchored path routing for a terminode network. does anyone have an idea from where i can get the reference code or something that would give a kind of startup for my project. i have all the theorectical material ready with me. the simulation that I am going to do will be in OPNET. hope to see some valid info from u all.... bye take care Aditi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sun Jun 29 04:39: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 EAA24717 for ; Sun, 29 Jun 2003 04:39:53 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5T8dOC07353 for manet-archive@odin.ietf.org; Sun, 29 Jun 2003 04:39:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WXiW-0001uW-Ao for manet-web-archive@optimus.ietf.org; Sun, 29 Jun 2003 04:39: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 EAA24710 for ; Sun, 29 Jun 2003 04:39:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WXiT-00005e-00 for manet-web-archive@ietf.org; Sun, 29 Jun 2003 04:39:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19WXiN-00005b-00 for manet-web-archive@ietf.org; Sun, 29 Jun 2003 04:39:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WXi9-0001pu-NL; Sun, 29 Jun 2003 04:39:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WXh2-0001pH-1X for manet@optimus.ietf.org; Sun, 29 Jun 2003 04:38: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 EAA24696 for ; Sun, 29 Jun 2003 04:37:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WXgk-00005L-00 for manet@ietf.org; Sun, 29 Jun 2003 04:37:34 -0400 Received: from ftpbox.mot.com ([129.188.136.101]) by ietf-mx with esmtp (Exim 4.12) id 19WXgZ-00005G-00 for manet@ietf.org; Sun, 29 Jun 2003 04:37:23 -0400 Received: from il06exr03.mot.com (il06exr03.mot.com [129.188.137.133]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h5T8as0L011364 for ; Sun, 29 Jun 2003 01:36:54 -0700 (MST) Received: from xover.corp.mot.com (xover.corp.mot.com [10.1.148.18]) by il06exr03.mot.com (Motorola/il06exr03) with ESMTP id h5T8aqSR021110 for ; Sun, 29 Jun 2003 03:36:52 -0500 Received: by xover.corp.mot.com with Internet Mail Service (5.5.2653.19) id ; Sun, 29 Jun 2003 04:36:32 -0400 Message-ID: From: "Manral, Vishwas" To: "'Andreas Hafslund'" , Emmanuel Baccelli , manet@ietf.org Subject: RE: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless netwo rk? Date: Sat, 28 Jun 2003 04:03:12 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="windows-1252" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 Andreas, > This is very interestihng. What kind of efforts? Where can > I find out more about them? I know Fred Baker presented the folowing in one of the IETF's, which uses OSPFv3. http://inet2002.org/CD-ROM/lu65rw2n/papers/ti3-b.pdf Thomas Henderson had a paper on defining a new "wireless" interface type for OSPFv2. Besides I know Cisco is working on the effort of defining changes to OSPF for MANET. Thanks and hope this helps, Vishwas -----Original Message----- From: Andreas Hafslund [mailto:andreha@unik.no] Sent: Friday, June 27, 2003 17:54 To: Emmanuel Baccelli; manet@ietf.org Subject: Re: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? > In fact there are numerous problems with the use of OSPF as is on wireless > links. It may work to some extent if the nodes are not moving (you were > talking about semi-mobility). What are the problems with OSPF for wireless (mostly static) links? Any thoughts/ideas/references? I am very interested in knowing about these problems. The backbone radio nodes will usually not be moving. However, a solution that can handle some movements is prefered. The movement will be: "bring down the radio link, move the vehicle, put up the radio link again". I think that OSPF can handle this, because you are manually putting down and up the link again. It would be better to have the radio link up even though you are moving, but it is not necessary. But, if an ad hoc routing protocol like OLSR or TBRPF can work as effectively as OSPF for this backbone network, I would prefer an ad hoc routing protocol. Are there any thoughts about OSPF vs OLSR/TBRPF for such bacbone (mostly static) wireless networks? > Actually several different efforts are under work on the subject of OSPF on wireless links and ad-hoc networks. This is very interestihng. What kind of efforts? Where can I find out more about them? Thanks for your reply. Regards, Andreas Hafslund THALES Communications AS Norway _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sun Jun 29 08:21: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 IAA27151 for ; Sun, 29 Jun 2003 08:21:53 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5TCLNc10561 for manet-archive@odin.ietf.org; Sun, 29 Jun 2003 08:21:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WbBL-0002kG-Ij for manet-web-archive@optimus.ietf.org; Sun, 29 Jun 2003 08:21: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 IAA27147 for ; Sun, 29 Jun 2003 08:21:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WbBK-0000gT-00 for manet-web-archive@ietf.org; Sun, 29 Jun 2003 08:21:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19WbBE-0000gQ-00 for manet-web-archive@ietf.org; Sun, 29 Jun 2003 08:21:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WbB0-0002hI-5S; Sun, 29 Jun 2003 08:21:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WbA9-0002gk-Qw for manet@optimus.ietf.org; Sun, 29 Jun 2003 08:20: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 IAA27134 for ; Sun, 29 Jun 2003 08:19:53 -0400 (EDT) From: ankur.j@media.mit.edu Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Wb9t-0000g7-00 for manet@ietf.org; Sun, 29 Jun 2003 08:19:53 -0400 Received: from xenia.media.mit.edu ([18.85.3.135]) by ietf-mx with esmtp (Exim 4.12) id 19Wb9j-0000g4-00 for manet@ietf.org; Sun, 29 Jun 2003 08:19:43 -0400 Received: from ankur ([203.94.198.208]) by xenia.media.mit.edu (8.12.9/8.12.9/XENIA) with ESMTP id h5TCJ6VY317498; Sun, 29 Jun 2003 08:19:17 -0400 (EDT) To: "Bilal Al Momani" , Subject: RE: [manet] NS-2 Date: Sun, 29 Jun 2003 17:54:16 +0530 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal 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 Bill, Since you have just started simulations, I think ns2 will be a good software. You can also have a look at 14 days trial version of QualNet. But before using that, get accustomed to ns2 and then you can really benefit from QualNet. It's a great software. My friends have told me that Opnet is also a good simulator for ad hoc networks. Since it is not an open source (and is very expensive), I didn't use it. When you will be doing simulations in ns2, you have to analyze the trace files. The major difficulty of any beginner is how to analyze them and how to draw the graphs. You can use awk or perl language for that. But if you don't want to spend time in learning them, you can use the software developed by me when I was doing my bachelor thesis. You can download the software from http://www.geocities.com/ankurjain009/projects.htm I hope it helps. Best Regards, Ankur -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Bilal Al Momani Sent: Monday, June 23, 2003 9:19 PM To: manet@ietf.org Subject: [manet] NS-2 Dear friends I have just started reading about MANET two weeks ago. I would like to do some simulation on manet routing protocols and dynamic addressing. I have been adviced to work on ns-2, but i have no idea what this simulation is and how can i get this simulation? Is it straight forward simulation? If any body can give some comments about that i would be so greatful. Thanks Bill _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sun Jun 29 10:55: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 KAA00095 for ; Sun, 29 Jun 2003 10:55:56 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5TEtSl07657 for manet-archive@odin.ietf.org; Sun, 29 Jun 2003 10:55:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WdaS-0001zQ-LR for manet-web-archive@optimus.ietf.org; Sun, 29 Jun 2003 10:55: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 KAA00082 for ; Sun, 29 Jun 2003 10:55:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WdaQ-0001NH-00 for manet-web-archive@ietf.org; Sun, 29 Jun 2003 10:55:26 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19WdaK-0001NE-00 for manet-web-archive@ietf.org; Sun, 29 Jun 2003 10:55:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Wda2-0001tC-R4; Sun, 29 Jun 2003 10:55:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WdZT-0001nN-6o for manet@optimus.ietf.org; Sun, 29 Jun 2003 10:54: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 KAA00033 for ; Sun, 29 Jun 2003 10:54:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WdZB-0001MV-00 for manet@ietf.org; Sun, 29 Jun 2003 10:54:09 -0400 Received: from www.gawab.com ([204.97.230.36] helo=gawab.com) by ietf-mx with smtp (Exim 4.12) id 19WdZ0-0001MO-00 for manet@ietf.org; Sun, 29 Jun 2003 10:53:58 -0400 Received: (qmail 43092 invoked by uid 1004); 29 Jun 2003 14:50:39 -0000 Received: from unknown (HELO fahmy) (comm@gawab.com@213.212.205.79) by gawab.com with SMTP; 29 Jun 2003 14:50:34 -0000 From: "Ana Moslim" To: Date: Sun, 29 Jun 2003 17:49:36 +0300 Message-ID: <018b01c33e4d$ac04b760$4fcdd4d5@fahmy> MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_NextPart_000_018C_01C33E66.D151EF60" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Subject: [manet] Qos extensions (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_018C_01C33E66.D151EF60 Content-Type: multipart/alternative; boundary="----=_NextPart_001_018D_01C33E66.D1599080" ------=_NextPart_001_018D_01C33E66.D1599080 Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: 7bit hello i am a student making project about Qos in ad hoc i have a problem in enabling the QOSR extension for both aodv and dsdv protocols so as to make various simulations of both protocols with and without qos to make a cmparison between the two cases i will be gratfull to any one who send me 1 how to enable the qos extension in aodv and dsdv for ns 1.8 or 1.9 2 any available simulations for both protocols thank u very much for ur care ------=_NextPart_001_018D_01C33E66.D1599080 Content-Type: text/html; charset="windows-1256" Content-Transfer-Encoding: quoted-printable Message
 
 

hello

i am a student making project about Qos in ad = hoc

i have a problem in enabling the QOSR extension for = both aodv and=20 dsdv = protocols

so as to make various simulations of both protocols = with and=20 without qos=20 to make a cmparison between the = two=20 cases

i will be gratfull to any one who send me

1 how to enable = the qos=20 extension in aodv and dsdv for ns 1.8 or 1.9 2 any = available=20 simulations for both protocols

thank u very much for ur care

------=_NextPart_001_018D_01C33E66.D1599080-- ------=_NextPart_000_018C_01C33E66.D151EF60 Content-Type: application/octet-stream; name="=?windows-1256?B?x9XP3sfBLmpwZw==?=" Content-Transfer-Encoding: base64 Content-ID: <310201914@29062003-33C0> Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 /9j/4QDmRXhpZgAASUkqAAgAAAAFABIBAwABAAAAAQAAADEBAgAcAAAASgAAADIBAgAUAAAAZgAA ABMCAwABAAAAAQAAAGmHBAABAAAAegAAAAAAAABBQ0QgU3lzdGVtcyBEaWdpdGFsIEltYWdpbmcA MjAwMzowNTowMiAyMzoyOTozMAAFAACQBwAEAAAAMDIxMJCSAgAEAAAAODYxAAKgBAABAAAA+QAA AAOgBAABAAAApwAAAAWgBAABAAAAvAAAAAAAAAACAAEAAgAEAAAAUjk4AAIABwAEAAAAMDEwMAAA AAAg4wQA/8AAEQgApwD5AwEiAAIRAQMRAf/bAIQABwQFBgUEBwYFBgcHBwgKEQsKCQkKFQ8QDBEZ FhoaGBYYGBwfKCIcHSYeGBgjLyMmKSotLS0bITE0MSs0KCwtKwELCwsPDQ8eEREeQCskK0BAQEBA QEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBA/8QAlQABAAEFAQEA AAAAAAAAAAAAAAUBAgMEBgcIEAABAwIEAwQGBQgGCwAAAAABAAIDBBEFEiExBkFREyJhcQcUMoGR oSNCUrHwFTNigpLB0eEWNlNydKIkNDU3VGOUlbKz0gEBAQEBAQAAAAAAAAAAAAAAAAECAwQRAQEA AgIDAQEBAAAAAAAAAAABAhEhMQMSQVETIv/aAAwDAQACEQMRAD8A+kUREBERAREQEREBERAREQER EBERAREQEREBERAREQEREBERAREQEREBERAREQEREBERAREQEREBERAREQEREBERAREQEREBERAR EQEREBERAREQEREBERAREQEREBERARUJRBVFS6qEBERAREQEREBERAREQEREBEVCQEFUREBERARE QEREBFQuAVOe+hQVuqqw6HXbqqE6oL7qqsarkFrjqrrqhaCqbaFBddW59bDZWSusB4qxrtVBshFa xwIsrlQREQEREBERAREQERCgo42C1zLc38VZWTZRYHUmy1zLruiJRFpUlSMzYjbXYrdRRERAREQF R5ytJVToteR+d+Rutt0FA5x15FXsd3r8h8la91hYDyCsMha2xtqdgorZuFjJ+kIHJWNks27joNSs dPJncXnmb2QbQVwVgKuBRFdFR1lVWlBgqzlYD42WFr/FX4ibU4PRwWk2TkptYkIpQHAHYraUS2S1 jzCk43Zomu3uFSr0RUe4NFyqikj2saS42AVGXOp0vy6LVY81VWQPzUR1P2nfyW6BZTsERFQREQFg rKhsERe42AWWR2RhJ5Ll8axDtavsmuu1guR4oNmWqzyuffQmwurDUC+/JRT6mwBBvzWI1dngnS6k Z2mm1QaQ7NqNdFn/ACzU/Zj+BXP+t6Dvbqnr3iPiht3yIirQiIgx1D8kRPgtOgOZjpDu46eCrVyd vMIGHfVx6BZnjsoSIY7kDTkpRglmtIWchpfqrJJL5bWtdYZJy4DPEARudVgrJ8tM4scQRp5XWd8t 6bFRUNc0wRkGW9zY7BZqS7Wgc+ahKKTJLnO9rKWgqGkaA+eyJpINddXZlrskaQLb9Lq7tALghXaM xcLbq1zhbdYXyAC7TosD6g3tdS00yVrg6lkHO1x7lF9obaLbfUDKQTvoo55ym19tFmXbWmy2S43O u6mMMdmoma3touaMuQG5IB59FP4FJnwmKQne5+a1jeUybr3BrSXGwCi6ys7SUxRG7ti0b67fFYcc xJ7GCOlYJZ5HZIYzs53j4C1ytjBMNNJC0zPMkziXPedy47lW3fEZbdDTiCnDDq4m7jbcrZSyLQIi ICIiDSxaQspyQV5/VVf+nVBa7QP5ciF13FuIMpaOQudYMaTc8l5w2pfcmV2Z7zmdyuVKzlUu6rAF s2hPj8FrSVQDgSVGvqdbE6EbLFLNlaH5gBewBN/xspGUp63YC7tfFU9fPioh1TlBuedybrH68fw5 aNvd0REdBa1VPltHHq8/JKmpa1wiaRncdPBWxRdmSS4Fx3KCyKEwgm93k3JPNYquufCQ3JvpcOst pxHNaWIwCaEge0NRZZqxqyYiwPyzMdG46C+t1rYtI4CNmaznd4gcvBXCdlPTiStaLtN42kXJI5qM fK+aV0kgu4m/l4LPTemeE2G9ys7ZnNO91ptkykDU3NgALk+C3mRQNBZUPcJB7WQg5PDxKz2q9tYR yNlkGItAs5+u2iw9hSu19YmH6o+CxyUVO8Hs6tzXfptvdOU4bPrzHE94X6X0KxS1YGrnXPK5UNV0 tTHfKwTAG94nb+7dRE2MyQkslBBabWdoR4LPs1p0c+JNaR3ufVYZKsSG7X946XvyXJVOM5tWmwO1 lghxk5w0uHks3c5OHbyVAlDo4u8RZoIN7krdixH1PDGUPrERljFnOZcgX1+K5TCcXinjfFlLgJNS BYA8/NSkdfBYAuAtoALCyk8jFSuEVUVPWy1NW+Spee7FkZlZCzoLm9ydz4D39DBitLNs8ttvmFgu MgrKTNq8NAOgIvfwW76zSyC0dQxpIt3XWWsfJYy7COSN/sPa7yN1evPK2skpn3jLjbmDv8Fv4Vxj 2MgixDvMvbONwP3rePll7R2iLBR1UNZTtmppGyRuGjmm6zrsCtkIa0k8lcrJm5o3DqEHmfpKxbK6 OFxIjlkyOfyHO3vXJPqg64dqRsQdQun9JVAX0lWzYludh6EaheeNrOdgA7UX2GizXPPtLSVZDTm1 sdbaW8LLHUVeanBLrEkE66dP4KLkqnDUGwA0IuCP3q107XxyAyOALS4ENtcjW3yTplv+tlxFySN9 BchV7aLof21Dtqu7a9h0AsB4W+Ku9bZ/Zf5f5qj6iVshswkb2Vyo4XBBVdnIvxFrOI2MqnODHHIC ORKno3RgkR3J6rmOJoAcbpmNcIy+VozHYaroYI3RxtYXg5RYm1lKrZJuNR/FY35y0ticGvcCGOIu A7kfjZNgOixSuaNTe453WaOLpq2oq7zVb/pr5X8gCNLfetoSta27rgW2WGvY1mN4gG2DfWCQN9xc /MlZaOE1dXHTg5GuN3O5gLFdWYV8GFBkkzTJWTtvTwj6g+0VoU9SYInB2Vr3uzuDNrlafEVa6fG6 mRoYwtPYgNdyCiXYg9ji2S4AO5vonRpOy400XuXFw06rTnxiRrrtdcHldRM8jmntWnPERrrchXtd E9hAIyk3FjoLqCRbikjnANeQLXuOSpWhuJRBkr/pyPo5T9x8FGAmNrQ1wJAvmLtCqOqTlIBBJGhG tkVBVcklNUSRvYWvYcrmnktDFcUbR0Tpo3APdZrATbUqZxeCWpoZJYYjNWRC8Yzazgalv94cv5hY uDMDjloTjOLQulnac3YkaMZ9m3lfVTcnbnmycN14bhMcFHI2aUi5cyQHXcjdSscFcWxyVMMga7UX j38bhePYrRnAsfqsOlyu9XfdjwDZ7Dqxw8wR+Au54A4iihkZHVZpYCbOZmJI8vFXPxyc/HLeu3ZR Na94+qToWi4st1scvZFsLXC+hdlN109FwzQ11IypoZxJDKAWuYd1e/g0/VleP1ip/Df1rUc1TRyR SAytIvqARf3fi62zQsqWls0Aj07xBt7lMN4Pmae7USDycVli4ReSDLPIbbd46K/xv6cI3B31OAdp NQskqIXd6SnvY+7x+9dng2JU+L4fHWUpdkeNnCxaRuCFzzsGmwycSwvc4H2rkm6OmmwKObEsLpqi tgec9Th8RBeOr4gdz1b8LWsd443D7wrrlQ7FR3D2OUHEOGsrsJqGzQOJadCHRuG7HNOrXDmDqpJd Eef+keg9ahlikDuzkaWkg235rxScTUtRLSVRaJqd1s5Ghb9V3v8A4r6X4ioG1dG+7bkDReFekbCZ YZ2VsMb3vh+jla0Xuze/uP8A5eClZym45g1BEYJ1F7FwN0gqGdqCXHKTZ7mHXxHwuo9lVHMA9pAD gNQdfPRA4OJdu927QbZvD8BRyZmzdm0MJLnNJZYi97afj71feXw+Df4qNqZmtneGvDmmziToHXF9 fnorfWv+a39kKj7LQ6oiru4H0gxyMmErbgA3BCmcBrzV4fDK5wcS2xJ6rNxpRes4e4gXIC5jgiti hbNRzzBsgddjXG1x4KVY62Wezd7eCjqqptfvKpq4KmV8UFRG+RntNa7vBatTSyvdla03PyXOtRDY i4srpJ2FpEur27Ovt87Lbp5WYW0Vdc8QkEEh2ul9lWaKmwxprcSc5zWG0UbGlznu8BztouPxvFp8 WqjLWwvja0/RRhpyx/zVk+1pZiVQx2IVMkRc6J0znMeRa7Sbj71gNQCLudmafrHktaWQjVwkeOuU 3WlPIASQJGnoWkBTTSSEzIbAC7bXtvbxWB1S1ji6MgcyBsVFvqXNBDWuIvsReywTVDiLFjmnmbWU 0bSMuKZW2abA8ui1HYobHvd22pOl1bh+DYtjMoZQ0zn3Ni992tHvXR/0HOCiOoxB7amcG4BbZjPd +839ysx2xctPP8Ux+pqcWhiMvZ0kb8rmxGxeeYcee+33r0ygrYm0oiDh2Zt3hqSvFKGmqqrCxJSx yTVDHSVL4mNu4xRtBkd+rcfPopbC+MXU0XZlpezncXss54b6cvb9dDx9g8GNRRylz4MQpXZRIyLO XxblpFwTa5I9/guTwqjnpagGjxKkmlA1he10RPXfTpvb3LexPiJk5bNBUdm9msRcLlh8eoNlPYSa fiSgklpI88kYzVVP2eYxkfW6lviNlLllhjq9MXddL6P+O6vBan1aqvGSA59NLs+/1mnb3jQr2nAc cosbphLRSguA78Z9pnmvliv4f7YB+FVslPlcS1ucvjbfw3at3hnjPEuHayOPES+Bwt2dTG67SP5r OOepvHmfhMtPq2yLguEPSTRYjExmJvZG82DZ2Huu8+nnt5LuY3Ne0OY4OaRoQb3XfHOZTh0XPY17 SHAEFR0uHGOUPgNteSk00WxpUeHUtPUzVcVNDFU1Fu2ljaGulsNMxHtW5X2W6iILXtDmkEXBXJcX cNsnjdPEO8Bey69Y6iMSxFjhcEIPlvjvBTQ4xHUQMAinJZIxotlk3Dvfrfxt1KgJ45GOIcIw4EAd 9ot48l7R6SeGhMJY3sIa45muAvkcNQR8l5VxE1lNWtgcwwVL2WyHWOe32D8ev3FZu3HOau0BiLzn jds5wMWUki1jf36H5LBnP9qfmstW4uoSL37Etmtl0F9HHrrf5LS7B39kz9sqS8M7fcSIi29DFVQN qInRvFwRZc1PwbSvndKTYn4hdRI4MYXHYLhuK+KLVEdFDJI1z5LkRDvFjdXW+XxQnLn+LsMhwKWO cSiPPJljJcW9o/fKCF0jeKqKWkEVNSVLpQzM5gYBc9L3VuA02J8W0zJuJ8NgpI6aYyUkepedCMzu hym1vM9LdFRcPUVJJmZGL9bKdr04admLS1L53QiWVwtnIIDR9lo5D71qz4fikxu6lhv1LLlerCni Atkb8E7CL7A+Cah7V4+/hiunJLoACeYFlc3geseLFrwPAr18RRj6o+CqGNGzQmoe1eT0/o5lkd9M X2594j7lO4X6OKKnIc+NhcOZGq7ywGwVVTaMwzBKWhaAxguB0UD6Q6TNSZ2i1l2KjeIaQVVA9pF9 ER8wRyu4O9IVDWwUz5o7VEYja7LcTNeB8C7/ACqWwHgGm4s4Mw3EaqAmrZEYH1NP9G67O70sdANw pbjrhx9RC6ojjzPo39oRa5sOfu0PkT4L0v0LVuEVvAdJSYZcvoCYKqGQd9kt7m46G9weYss7/wBa Z+vCcR9GlfRE+p1LJmjXs6luU/tDT5BQclPjHC9bHiTKavw+emOaOspDnDOuov3ddcwsdd19cVuA 0VUwh0YuRvZc5ifAsTyXQaG9xZWzZcY814O9JfBXGEQpOO4KOjxQ90V1PeNstupbq0+B0+5TfEHo 44QxSkc7BuLaWFz9mz1MUsbr8tLH5lb2I+iukxEObXYfRzh5u5z4W5jf9Lf5q7CPQxgVC4GLC6Nh BBuY85B/Wusfzm9rr9eWf0H4lwPE3x4JVYZVRss52SrvCWk2BDraG41B6g68u34P4zxDhuT1fEcT wR9n2koI68SvB8LC7Xedv3rvK3giM03de5zgNLkmy8y464AirJe1c11JXM0jrI26m3Jw+sFL4/u+ STT2/h/HKLHKMVFHIbj24n6PjPQhSE0rI23e4AeJXzLwrxVivCWLxUWN54JR3aerYbse3z+s39E6 /eu/4vx3FeJ8LpqehdE2mmFqh8MhHbfojmAdbj+ZLHyc+uXZtO4h6W8JgrZ6aioaytdBI6Jz2ZWs JaSDYk6jQ6rm8Q9JGPYjO11K1uHxMN2MgGd7/wC8SPkB7yudj4ZxaJzWvEEVK0WDIozcDoNbff7l bLgfEk0jhhuH0Oh7r5J3i3uyHx5roxfZO1nGnEggc38tPaX6W7FjXDy0XJSCN0r31FQ+RznZnSvl Lnk9b3WfF+HcWooo30vZT1LB9NHK3K2Q8y065T53/etKnoMQexodh1ZBI8Wf2ronRjwu1xPyKljO UyZ8XpoaylcKeolEhOjRM8Hz8Vx2KRY9AySmmkq66nk0DZR2paeRbe7mkabEe9dKKmppqjK7CcVL gbOLIC8HwzA2ttzWenxmiqZTSn1wTtuwwtpHOI63tfqsbsZm3KYJRVOIxTGaPSE5KmI3bMIXC3a5 DqQNLkX8bbqM/JOPf8E/9sLp+JZa/BYGV8UktNCBk7Ytu1mbSzmu1AOl9FDf0pl64L/1i55e+9xv GY65fZyIi9Lqw1jS+mcBYXC5GPhUVeIQ1BnMMkM3aEhodnbzafPTVdhP+YPktLD/AM+7+7/BFjdh ibEwNYLAbBZEREEREBERAREQFa9ocwg7K5Uf7JQcPxVh/qdSamIDKfaHUfi68vxKas9GfEkXFOB3 kwqpPZ1VEH5czQLlgvuQLlp92i9g43/1V3l/FeSemT+oEH+Jd/6is1K9x4Zxui4jwGjxjC3ufSVk Qlic9pabHqDzGyk1w3oD/wBznDf+CH3ruVpVNFVUVUFDbVR+K4TT18Ja9jbkaG2ykDsVT6vuQeSc a8FwSU8sFXDHPTOJJY7cW5g7gjqF5xM3FOA5DVwzOrcHMmR3aP78JOwI+t5jXyXunG/5iX9ZeOel T+o1Z/imLGeMymqzXpXAnGdBjtFH6xASwgWky6g9CLahd7BQUrATHE2xXhPod/2RD5tXv1P7C5+D K2XaxH1eA0VU674m38lrycLUDmZezHwU39ZV5rurl6jgqjf7LQEZwhRxRjNdy6crFP8Amwg8r414 Zkc29BPTRNb7TZ6ftQfdmC4j8g479vhf/tz/AP6XrPE/5mXy/euPQf/Z ------=_NextPart_000_018C_01C33E66.D151EF60-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sun Jun 29 13:21: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 NAA02456 for ; Sun, 29 Jun 2003 13:21:05 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5THKaG08494 for manet-archive@odin.ietf.org; Sun, 29 Jun 2003 13:20:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Wfqu-0002Cv-Dd for manet-web-archive@optimus.ietf.org; Sun, 29 Jun 2003 13:20: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 NAA02398 for ; Sun, 29 Jun 2003 13:19:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Wfpj-0002vS-00 for manet-web-archive@ietf.org; Sun, 29 Jun 2003 13:19:23 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Wfpd-0002vP-00 for manet-web-archive@ietf.org; Sun, 29 Jun 2003 13:19:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WfpP-0001t6-1D; Sun, 29 Jun 2003 13:19:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WfpI-0001sE-Vx for manet@optimus.ietf.org; Sun, 29 Jun 2003 13:18: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 NAA02378 for ; Sun, 29 Jun 2003 13:18:50 -0400 (EDT) From: ab36@njit.edu Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WfpC-0002ug-00 for manet@ietf.org; Sun, 29 Jun 2003 13:18:50 -0400 Received: from mail-shield1.njit.edu ([128.235.251.171]) by ietf-mx with esmtp (Exim 4.12) id 19Wfp1-0002tP-00 for manet@ietf.org; Sun, 29 Jun 2003 13:18:39 -0400 Received: (from uucp@localhost) by mail-shield1.njit.edu (8.11.6/8.11.6) id h5THH8Y12673 for ; Sun, 29 Jun 2003 13:17:08 -0400 (EDT) Received: from nodnsquery(128.235.251.32) by mail-shield1.njit.edu via csmap (V4.1) id srcAAAOkaOVy; Sun, 29 Jun 03 13:17:07 -0400 Received: from webmail.njit.edu (webmail.njit.edu [128.235.251.121]) by mail-gw4.njit.edu (8.12.9/8.12.4) with ESMTP id h5THHV5B015434 for ; Sun, 29 Jun 2003 13:17:31 -0400 (EDT) Received: (from apache@localhost) by webmail.njit.edu (8.11.7+Sun/8.11.7) id h5TH99x23878 for manet@ietf.org; Sun, 29 Jun 2003 13:09:09 -0400 (EDT) To: manet@ietf.org Message-ID: <1056906549.3eff1d3504f3e@webmail.njit.edu> Date: Sun, 29 Jun 2003 13:09:09 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.4 X-Originating-IP: 128.235.207.19 Content-Transfer-Encoding: 8bit Subject: [manet] TRR routing with anchors..... Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit hello has anyone done any kind of simulations for the Terminode remote routing of terminode networks.... please let me know if u have. Aditi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 30 03:21:00 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 DAA03341 for ; Mon, 30 Jun 2003 03:21:00 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5U7KUb25740 for manet-archive@odin.ietf.org; Mon, 30 Jun 2003 03:20:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Wsxi-0006h5-QI for manet-web-archive@optimus.ietf.org; Mon, 30 Jun 2003 03:20: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 DAA03328 for ; Mon, 30 Jun 2003 03:20:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Wsxg-0004AM-00 for manet-web-archive@ietf.org; Mon, 30 Jun 2003 03:20:28 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Wsxb-0004AF-00 for manet-web-archive@ietf.org; Mon, 30 Jun 2003 03:20:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WsxG-0006fW-JK; Mon, 30 Jun 2003 03:20:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Wsx7-0006es-06 for manet@optimus.ietf.org; Mon, 30 Jun 2003 03:19: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 DAA03303 for ; Mon, 30 Jun 2003 03:19:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Wswp-00049u-00 for manet@ietf.org; Mon, 30 Jun 2003 03:19:35 -0400 Received: from dpt-info.u-strasbg.fr ([130.79.44.193]) by ietf-mx with esmtp (Exim 4.12) id 19Wswe-00049m-00 for manet@ietf.org; Mon, 30 Jun 2003 03:19:25 -0400 Received: from PATINET (patinet.u-strasbg.fr [130.79.90.172]) by dpt-info.u-strasbg.fr (8.12.3/8.12.3/Debian-6.4) with SMTP id h5U7J1Dc003858 for ; Mon, 30 Jun 2003 09:19:01 +0200 Message-ID: <001f01c33ed8$3c1bd1a0$ac5a4f82@ustrasbg.fr> From: "Christophe Jelger" To: References: <5.1.1.5.2.20030627145038.02d74ab0@pop.itd.nrl.navy.mil> Subject: Re: [manet] Distance vector routing and adhoc Date: Mon, 30 Jun 2003 09:21:33 +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.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 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, I forgot to mention that I was rather interested by proactive protocols, i.e. a distance vector algorithm that maintains routing tables in a continuous way (like RIP for wired networks). Cheers, Christophe ----- Original Message ----- From: "Joe Macker" To: "Christophe Jelger" ; Sent: Friday, June 27, 2003 8:52 PM Subject: Re: [manet] Distance vector routing and adhoc > As far as WG documents AODV comes to mind.. > > At 09:29 AM 6/27/2003 +0200, Christophe Jelger wrote: > >Hi all, > > > >I am relatively unfamiliar with some aspects of adhoc routing and was > >wondering if people could point me to some key papers describing the > >performance (and potential problems) of distance vector routing in adhoc > >networks. I know it is probably not the best way for routing in such > >networks but I'd like to know what optimizations have been proposed in order > >to increase the efficiency of distance vector routing in adhoc networks. In > >particular, I'd like to know if there are some relatively well admitted > >methods for optimizations. > > > >Thanks in advance and apologies for the (quite) silly question. ;-) > > > >Regards, > > > >Christophe > > > > > > > >_______________________________________________ > >manet mailing list > >manet@ietf.org > >https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 30 09:32: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 JAA22466 for ; Mon, 30 Jun 2003 09:32:49 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5UDWLn28848 for manet-archive@odin.ietf.org; Mon, 30 Jun 2003 09:32:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WylZ-0007VD-5E for manet-web-archive@optimus.ietf.org; Mon, 30 Jun 2003 09:32: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 JAA22446 for ; Mon, 30 Jun 2003 09:32:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WylX-0000Uf-00 for manet-web-archive@ietf.org; Mon, 30 Jun 2003 09:32:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19WylR-0000Uc-00 for manet-web-archive@ietf.org; Mon, 30 Jun 2003 09:32:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WylF-0007U4-Rw; Mon, 30 Jun 2003 09:32:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WykK-0007S4-Ou for manet@optimus.ietf.org; Mon, 30 Jun 2003 09:31: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 JAA22384 for ; Mon, 30 Jun 2003 09:31:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WykI-0000TI-00 for manet@ietf.org; Mon, 30 Jun 2003 09:31:02 -0400 Received: from dpt-info.u-strasbg.fr ([130.79.44.193]) by ietf-mx with esmtp (Exim 4.12) id 19Wyk7-0000Sb-00 for manet@ietf.org; Mon, 30 Jun 2003 09:30:52 -0400 Received: from PATINET (patinet.u-strasbg.fr [130.79.90.172]) by dpt-info.u-strasbg.fr (8.12.3/8.12.3/Debian-6.4) with SMTP id h5UDU7Dc009297 for ; Mon, 30 Jun 2003 15:30:07 +0200 Message-ID: <015301c33f0c$1470cc80$ac5a4f82@ustrasbg.fr> From: "Christophe Jelger" To: References: <002901c33c7d$d9e751a0$ac5a4f82@ustrasbg.fr> Date: Mon, 30 Jun 2003 15:32:41 +0200 Organization: ULP - LSIIT MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by dpt-info.u-strasbg.fr id h5UDU7Dc009297 Content-Transfer-Encoding: quoted-printable Subject: [manet] Internet connectivity and AODV paper Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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: quoted-printable Content-Transfer-Encoding: quoted-printable Hi, For people aware of the paper "Internet connectivity for mobile adhoc networks" by Perkins et al that appears in "Wireless Communications and Mobile Computing", 2, pp.465-482, 2002 (Wiley) (and also sorry for the length of this email). It is stated in this paper that an AODV node that has a default route to = an Internet Gateway, should make a route request before sending the packet i= f shortest route is required. In clear and because AODV is a reactive protocol, before sending the packet to the gateway, check if there a dire= ct route to the destination (i.e. to check if the destination is in the adho= c network). I personaly think that it is somehow strange to use a default route with = a reactive protocol, because it "stops" the protocol from being reactive (there is a default route !). That is why the above paper specifies that = is "shortest route" is required an AODV node should first send a route reque= st to find a better route. In other words, if shortest route is required it = is the same to remove the default route, with the Internet Gateway respondin= g to route requests for destinations outside the adhoc network. These thoughts are, however, personal opinions about the paper. My main concerns about this proposal are such : 1. In usual operating systems (Linux, BSD, Windows), the routing daemon i= s in charge for populating the routing table. The OS then uses the routing table information to forward packets. In the paper referenced above, this behaviour is "corrupted" : the OS, when about to forward a packet, must initiate the discovery of a route (by sending a request to the routing daemon). From an enginneering point of you (the E in IETF), I wonder if t= his behaviour is acceptable (needs strong modifications in the OS kernel code= ). I don't know if the authors are members of the list but I would appreciat= e to have their opinion (keeping in mind that their paper is research) and also, of course, the opinion of other members of the list. 2. It is mentioned in the paper that the gateway information should be ke= pt as such in the routing table : a default entry to the gateway, and a host entry to the gateway. That means that the OS should perform a double look= up operation : to send packet to X, check route to X (default and find next = hop is gateway), then check route to gateway (and find next hop direct neighbor). To my personal knowledge (I did tests with FreeBSD), this cann= ot be done in modern operating systems (although some people told me it is possible but did not tell me how ...). Also, I think it would be better t= o keep the "next hop" philosophy and install a default via the next hop (direct neighbor) to the gateway (default route is next hop to the gateway). Could I please have other peoples' opinions on this subject ? Thanks, Christophe Jelger --------------------------------------------------------------- Christophe Jelger - LSIIT jelger@dpt-info.u-strasbg.fr Universit=E9 Louis Pasteur Strasbourg - France Tel: +33 (0)3 90 24 45 90 http://www-r2.u-strasbg.fr/~jelger --------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 30 12:13: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 MAA03530 for ; Mon, 30 Jun 2003 12:13:23 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5UGCtb02250 for manet-archive@odin.ietf.org; Mon, 30 Jun 2003 12:12:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X1Gx-0000aD-Py for manet-web-archive@optimus.ietf.org; Mon, 30 Jun 2003 12:12:55 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03479 for ; Mon, 30 Jun 2003 12:12:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X1G5-0000P9-0h; Mon, 30 Jun 2003 12:12:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X1FT-0000OF-DG for manet@optimus.ietf.org; Mon, 30 Jun 2003 12:11: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 MAA03388 for ; Mon, 30 Jun 2003 12:11:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X1FP-0002Gq-00 for manet@ietf.org; Mon, 30 Jun 2003 12:11:19 -0400 Received: from shaku.sfc.wide.ad.jp ([203.178.143.49]) by ietf-mx with esmtp (Exim 4.12) id 19X1FB-0002FD-00 for manet@ietf.org; Mon, 30 Jun 2003 12:11:05 -0400 Received: from monster.sfc.wide.ad.jp.sfc.wide.ad.jp (p8be5fb.tkyoac00.ap.so-net.ne.jp [210.139.229.251]) (authenticated bits=0) by shaku.sfc.wide.ad.jp (8.12.9/8.12.0) with ESMTP id h5UG6dGi001551; Tue, 1 Jul 2003 01:06:40 +0900 Date: Tue, 01 Jul 2003 01:03:39 +0900 Message-ID: From: Ryuji Wakikawa To: jelger@dpt-info.u-strasbg.fr Cc: manet@ietf.org Subject: Re: [manet] Internet connectivity and AODV paper In-Reply-To: <015301c33f0c$1470cc80$ac5a4f82@ustrasbg.fr> References: <002901c33c7d$d9e751a0$ac5a4f82@ustrasbg.fr> <015301c33f0c$1470cc80$ac5a4f82@ustrasbg.fr> User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/20.7 (i386--freebsd) MULE/4.1 (AOI) Organization: Keio University MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hi Christophe. At Mon, 30 Jun 2003 15:32:41 +0200, Christophe Jelger wrote: >=20 > For people aware of the paper "Internet connectivity for mobile adhoc > networks" by Perkins et al that appears in "Wireless Communications and > Mobile Computing", 2, pp.465-482, 2002 (Wiley) (and also sorry for the > length of this email). Yes, I am co-author of that paper. > It is stated in this paper that an AODV node that has a default route to = an > Internet Gateway, should make a route request before sending the packet if > shortest route is required. In clear and because AODV is a reactive > protocol, before sending the packet to the gateway, check if there a dire= ct > route to the destination (i.e. to check if the destination is in the adhoc > network). correct. > I personaly think that it is somehow strange to use a default route with a > reactive protocol, because it "stops" the protocol from being reactive > (there is a default route !). That is why the above paper specifies that = is > "shortest route" is required an AODV node should first send a route reque= st > to find a better route. In other words, if shortest route is required it = is > the same to remove the default route, with the Internet Gateway responding > to route requests for destinations outside the adhoc network. see below comment > These thoughts are, however, personal opinions about the paper. My main > concerns about this proposal are such : >=20 > 1. In usual operating systems (Linux, BSD, Windows), the routing daemon is > in charge for populating the routing table. The OS then uses the routing > table information to forward packets. In the paper referenced above, this > behaviour is "corrupted" : the OS, when about to forward a packet, must > initiate the discovery of a route (by sending a request to the routing > daemon). From an enginneering point of you (the E in IETF), I wonder if t= his > behaviour is acceptable (needs strong modifications in the OS kernel code= ). > I don't know if the authors are members of the list but I would appreciate > to have their opinion (keeping in mind that their paper is research) and > also, of course, the opinion of other members of the list. I think your comment here is not only for AODV global connectivity, but is for all reactive protocols. > The OS, when about to forward a packet, must > initiate the discovery of a route (by sending a request to the routing > daemon). This is how I implemented AODV6:) The operations of handling the default route is similar to normal AODV operation. When an aodv6 nodeA sends packets to another aodv6 nodeB, it issues RREQ for the destination because there is no route. The nodeA queues the outgoing packets until the route of the nodeB is discovered. If there is no route, it gives up sending the packets. When an aodv6 nodeA sends packets to another aodv6 nodeB, it issues RREQ for the destination, because there is no route. The nodeA queues the outgoing packets until route is discovered. If the route is not discovered, the nodeA uses the default route. Can you see big differences? One more note:=20 We sometime assumed that each MANET clouds has manet specific prefix for inner routing (inside manet). =20 See draft-perkins-manet-autoconf-01.txt. The title is "IP Address Autoconfiguration for Ad Hoc Networks" All manet nodes have site-local address as a MANET specific address and may also acquire a global address if it is needed. If a destination is site-local address (i.e. the destination must be located inside the manet cloud), the sender discovers a route by RREQ. If a destination is global address, the sender just routes packets to the default route. This is simple. > 2. It is mentioned in the paper that the gateway information should be ke= pt > as such in the routing table : a default entry to the gateway, and a host > entry to the gateway. That means that the OS should perform a double look= up > operation : to send packet to X, check route to X (default and find next = hop > is gateway), then check route to gateway (and find next hop direct > neighbor). To my personal knowledge (I did tests with FreeBSD), this cann= ot > be done in modern operating systems (although some people told me it is > possible but did not tell me how ...). Also, I think it would be better to > keep the "next hop" philosophy and install a default via the next hop > (direct neighbor) to the gateway (default route is next hop to the > gateway). Could I please have other peoples' opinions on this subject ? One of advantage of this configuration is that even if a neighbor node towards a gateway is changed due to movements, the default route is not expired. Only the host route is deleted from the routing table. Manet node just requests the host route towards the gateway by RREQ. The host route may be fixed by local-repair. About the philosophy, you can configure two routes for a destination on BSD. Check your routing table. sometime the default route is configured as follows on BSD. default-route -> gw global-addr gw global-addr -> gw MAC-addr AFAIK, implementing "recursive routing table search" is easier than you expect;-) The latest document is draft-wakikawa-manet-globalv6-02.txt You may be able to find more information. regards, ryuji > Thanks, >=20 > Christophe Jelger >=20 > --------------------------------------------------------------- > Christophe Jelger - LSIIT jelger@dpt-info.u-strasbg.fr > Universit=E9 Louis Pasteur > Strasbourg - France Tel: +33 (0)3 90 24 45 90 >=20 > http://www-r2.u-strasbg.fr/~jelger > --------------------------------------------------------------- >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 30 12:19: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 MAA03886 for ; Mon, 30 Jun 2003 12:19:18 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5UGIo103934 for manet-archive@odin.ietf.org; Mon, 30 Jun 2003 12:18:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X1Mg-00011L-Sc for manet-web-archive@optimus.ietf.org; Mon, 30 Jun 2003 12:18:50 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03812 for ; Mon, 30 Jun 2003 12:18:45 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X1Lu-0000ou-5Y; Mon, 30 Jun 2003 12:18:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19X1Kv-0000nm-1l for manet@optimus.ietf.org; Mon, 30 Jun 2003 12:17: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 MAA03692 for ; Mon, 30 Jun 2003 12:16:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19X1Kp-0002Jd-00 for manet@ietf.org; Mon, 30 Jun 2003 12:16:56 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19X1KV-0002Iy-00 for manet@ietf.org; Mon, 30 Jun 2003 12:16:35 -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 JAA04237; Mon, 30 Jun 2003 09:14:51 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h5UGEo317989; Mon, 30 Jun 2003 09:14:50 -0700 X-mProtect: <200306301614> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdkTjhu9; Mon, 30 Jun 2003 09:14:48 PDT Message-ID: <3F0061F8.E78A7843@iprg.nokia.com> Date: Mon, 30 Jun 2003 09:14:48 -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: Ana Moslim CC: manet@ietf.org Subject: Re: [manet] Qos extensions (for aodv) References: <018b01c33e4d$ac04b760$4fcdd4d5@fahmy> 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 Ana, Here's a URL: http://people.nokia.net/~charliep/txt/aodvid/qos.txt Thanks! Regards, Charlie P. > Ana Moslim wrote: > > > > > hello > > i am a student making project about Qos in ad hoc > > i have a problem in enabling the QOSR extension for both aodv and dsdv > protocols > > so as to make various simulations of both protocols with and without qos to > make a cmparison between the two cases > > i will be gratfull to any one who send me > > 1 how to enable the qos extension in aodv and dsdv for ns 1.8 or 1.9 2 any > available simulations for both protocols > > thank u very much for ur care _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jun 30 23:42: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 XAA28480 for ; Mon, 30 Jun 2003 23:42:21 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h613fr627620 for manet-archive@odin.ietf.org; Mon, 30 Jun 2003 23:41:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XC1h-0007BN-9L for manet-web-archive@optimus.ietf.org; Mon, 30 Jun 2003 23:41:53 -0400 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28472 for ; Mon, 30 Jun 2003 23:41:50 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XC0s-00074k-PY; Mon, 30 Jun 2003 23:41:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XC0j-00074K-VW for manet@optimus.ietf.org; Mon, 30 Jun 2003 23:40: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 XAA28457 for ; Mon, 30 Jun 2003 23:40:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XC0h-0006gm-00 for manet@ietf.org; Mon, 30 Jun 2003 23:40:51 -0400 Received: from mail11.ntu.edu.sg ([155.69.5.163]) by ietf-mx with esmtp (Exim 4.12) id 19XC0T-0006gH-00 for manet@ietf.org; Mon, 30 Jun 2003 23:40:37 -0400 Received: from mail02.student.main.ntu.edu.sg ([155.69.5.166]) by mail11.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Tue, 1 Jul 2003 11:38:40 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C33F82.432A7323" Date: Tue, 1 Jul 2003 11:38:40 +0800 Message-ID: <295CB338B611594582D82D9F26AEF706D04647@mail02.student.main.ntu.edu.sg> X-MS-TNEF-Correlator: <295CB338B611594582D82D9F26AEF706D04647@mail02.student.main.ntu.edu.sg> Thread-Topic: manet digest, Vol 1 #472 - 4 msgs Thread-Index: AcM822oAlBTogXF/SnmFRQGAaUIjJwCprJWx From: "#GUPTA ROHIT#" To: X-OriginalArrivalTime: 01 Jul 2003 03:38:40.0331 (UTC) FILETIME=[4343A1B0:01C33F82] Subject: [manet] Integration of 3G with MANET Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. ------_=_NextPart_001_01C33F82.432A7323 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 ZGVhciBhbGwsDQpJcyB0aGVyZSBhbnlvbmUgd29ya2luZyBvbiAzRyB3aXRoIGFkIGhvYyBuZXR3 b3Jrcy4gQW55IHN1Z2dlc3Rpb25zLCBwb2ludGVycyB3b3VsZCBiZSB1c2VmdWwuDQogDQpyZWdh cmRzDQpyb2hpdA0KIA0K ------_=_NextPart_001_01C33F82.432A7323 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 eJ8+IikDAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAENgAQAAgAAAAIAAgABBYAD AA4AAADTBwcAAQALACYAKAACAD0BASCAAwAOAAAA0wcHAAEACwAmACgAAgA9AQEJgAEAIQAAADE0 NzA4NjFGQkM4REYxNEE5NjlFRkQyM0FBRTE1M0E2AFEHAQOQBgDICwAAOAAAAB8AGgABAAAAEgAA AEkAUABNAC4ATgBvAHQAZQAAAAAAAwA2AAAAAAAfADcAAQAAADoAAABJAG4AdABlAGcAcgBhAHQA aQBvAG4AIABvAGYAIAAzAEcAIAB3AGkAdABoACAATQBBAE4ARQBUAAAAAABAADkAI3MqQ4I/wwEf AD0AAQAAAAIAAAAAAAAAAgFHAAEAAAArAAAAYz1VUzthPSA7cD1OVFU7bD1NQUlMMDItMDMwNzAx MDMzODQwWi0yOTMwAAAfAEkAAQAAAEQAAABtAGEAbgBlAHQAIABkAGkAZwBlAHMAdAAsACAAVgBv AGwAIAAxACAAIwA0ADcAMgAgAC0AIAA0ACAAbQBzAGcAcwAAAEAATgAArcAqxTzDAR8AWgABAAAA LgAAAG0AYQBuAGUAdAAtAHIAZQBxAHUAZQBzAHQAQABpAGUAdABmAC4AbwByAGcAAAAAAAIBWwAB AAAASwAAAAAAAACBKx+kvqMQGZ1uAN0BD1QCAAAAAG1hbmV0LXJlcXVlc3RAaWV0Zi5vcmcAU01U UABtYW5ldC1yZXF1ZXN0QGlldGYub3JnAAACAVwAAQAAABwAAABTTVRQOk1BTkVULVJFUVVFU1RA SUVURi5PUkcAHwBdAAEAAAAuAAAAbQBhAG4AZQB0AC0AcgBlAHEAdQBlAHMAdABAAGkAZQB0AGYA LgBvAHIAZwAAAAAAAgFeAAEAAABLAAAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAAAbWFuZXQtcmVx dWVzdEBpZXRmLm9yZwBTTVRQAG1hbmV0LXJlcXVlc3RAaWV0Zi5vcmcAAAIBXwABAAAAHAAAAFNN VFA6TUFORVQtUkVRVUVTVEBJRVRGLk9SRwAfAGYAAQAAAAoAAABTAE0AVABQAAAAAAAfAGcAAQAA AC4AAABtAGEAbgBlAHQALQByAGUAcQB1AGUAcwB0AEAAaQBlAHQAZgAuAG8AcgBnAAAAAAAfAGgA AQAAAAoAAABTAE0AVABQAAAAAAAfAGkAAQAAAC4AAABtAGEAbgBlAHQALQByAGUAcQB1AGUAcwB0 AEAAaQBlAHQAZgAuAG8AcgBnAAAAAAAfAHAAAQAAAEQAAABtAGEAbgBlAHQAIABkAGkAZwBlAHMA dAAsACAAVgBvAGwAIAAxACAAIwA0ADcAMgAgAC0AIAA0ACAAbQBzAGcAcwAAAAIBcQABAAAAGwAA AAHDPNtqAJQU6IFxf0p5hUUBgGlCIycAqayVsQAfAHQAAQAAAB4AAABtAGEAbgBlAHQAQABpAGUA dABmAC4AbwByAGcAAAAAAB8AGgwBAAAAHAAAACMARwBVAFAAVABBACAAUgBPAEgASQBUACMAAAAf AB0OAQAAADoAAABJAG4AdABlAGcAcgBhAHQAaQBvAG4AIABvAGYAIAAzAEcAIAB3AGkAdABoACAA TQBBAE4ARQBUAAAAAAACAQkQAQAAABUDAAARAwAAywgAAExaRnW1f7eWAwAKAHJjcGcxMjWCMgND aHRtbDEDMD8BAwH3CoACpAPjAgBjaMEKwHNldDAgBxMCgP8QAwBQBFYIVQeyEdUOUQMB3RDXMgYA BsMR1TMERhDZbxLrEeMI7wn3OxjPDjA1OxHSDGBjAFALCQFkMzaTEWALpTQgEAIqXA6yvQGQZxTw CqMR4x3oNBTwADwhRE9DVFlQAEUgSFRNTCBQAFVCTElDICItIC8vVzNDIYBEVCJEIJQzLjIhgEVO nCI+Hu0ejyPBMTgf8G8goiMPJB8mkDMdgCVwRXxBRCXNDvEm7ylvJPQ2QQ7wPE1FVEEHsEExLGA9 IkcJ8ASQYXRFBbAiEtBPTlQi0FQTLPAF4UV4EPFuZ2U9BlJ2EzEvQQCQAiAgNoAuMC42Mzk0MBAn Iv4qzyUDNzcf8FRJ6FRMRSXONA7wA4ERQAggZGku4HN0LCBKVgbwIA7wIzQBwCCELSAdgG1zZ3Mk bvo1H/AvM08xfyZFNJE38BcoTyafO8Q1EWA8Qk+kRFk1EXI9O+ByOzDPO6MAIQMwPkFkbwDgPkH5 CrFccRiwPkEQ8AMwPqWPEWA7WxzxPF9nOTYf8HhESVY+eQAAQLc7eTY+NEPvQQIBAArBB0BsLH87 eQHAPocKoj6HCnEkfDD/KBEh4EO7SYhBP0JPQ19Eb8tFf1ArSQQgdGgEkC7wrQBweQIgLvB3BbBr C4CkZyAv0TNHVABpU0DRR5BkIGg/cCA04VQSDHMuEXBTsCBzdWc7NUIvwXM1gDncTeVwb00LgHQv kVQBdWxVUGLVLvB1ETBmWWAuR+9I//9KD0sfTC9NP05PT19Qb1F/C17fO9M4HYAmbmJz5nACgD6Y J2EBQGLPWs//W99c713/ZR9gH2EvZF9jT9VwTyAY0GcLEXNoX2lv/2p/a49sn22vbr9vz3Dfce/5 cvhvaFUAc/91D3Yfdy//eD95T3pfe298f32PhA9l//9nD2gfgE+BX4Jvg3+Ej4Wf95NvPSQlUS89 sjs/lO+XcRczETrgJZN9maAAAAAfADUQAQAAAJAAAAA8ADIAOQA1AEMAQgAzADMAOABCADYAMQAx ADUAOQA0ADUAOAAyAEQAOAAyAEQAOQBGADIANgBBAEUARgA3ADAANgBEADAANAA2ADQANwBAAG0A YQBpAGwAMAAyAC4AcwB0AHUAZABlAG4AdAAuAG0AYQBpAG4ALgBuAHQAdQAuAGUAZAB1AC4AcwBn AD4AAAAfAEcQAQAAAB4AAABtAGUAcwBzAGEAZwBlAC8AcgBmAGMAOAAyADIAAAAAAAsA8hABAAAA HwDzEAEAAABCAAAASQBuAHQAZQBnAHIAYQB0AGkAbwBuACAAbwBmACAAMwBHACAAdwBpAHQAaAAg AE0AQQBOAEUAVAAuAEUATQBMAAAAAAALAPYQAAAAAEAABzB4OVccgj/DAUAACDAcmjFDgj/DAQMA 3j/p/QAAAwDxPwkEAAAfAPg/AQAAABwAAAAjAEcAVQBQAFQAQQAgAFIATwBIAEkAVAAjAAAAAgH5 PwEAAABgAAAAAAAAANynQMjAQhAatLkIACsv4YIBAAAAAAAAAC9PPU5UVS9PVT1DRU5UUkFML0NO PVJFQ0lQSUVOVFMvQ049U1RVREVOVC9DTj1QT1NUR1JBRC9DTj1QQjU5MDExMzgAHwD6PwEAAAAq AAAAUwB5AHMAdABlAG0AIABBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAAAAAAACAfs/AQAAAB4A AAAAAAAA3KdAyMBCEBq0uQgAKy/hggEAAAAAAAAALgAAAAMA/T/kBAAAAwAZQAAAAAADABpAAAAA AAMAHUAAAAAAAwAeQAAAAAAfADBAAQAAABQAAABQAEIANQA5ADAAMQAxADMAOAAAAB8AMUABAAAA FAAAAFAAQgA1ADkAMAAxADEAMwA4AAAAHwAyQAEAAAAuAAAAbQBhAG4AZQB0AC0AcgBlAHEAdQBl AHMAdABAAGkAZQB0AGYALgBvAHIAZwAAAAAAHwAzQAEAAAAuAAAAbQBhAG4AZQB0AC0AcgBlAHEA dQBlAHMAdABAAGkAZQB0AGYALgBvAHIAZwAAAAAAHwA4QAEAAAAUAAAAUABCADUAOQAwADEAMQAz ADgAAAAfADlAAQAAAAQAAAAuAAAACwApAAAAAAALACMAAAAAAAMABhCt88fXAwAHEGEAAAADABAQ AAAAAAMAERAAAAAAHgAIEAEAAABiAAAAREVBUkFMTCxJU1RIRVJFQU5ZT05FV09SS0lOR09OM0dX SVRIQURIT0NORVRXT1JLU0FOWVNVR0dFU1RJT05TLFBPSU5URVJTV09VTERCRVVTRUZVTFJFR0FS RFNST0hJVAAAAAIBfwABAAAASAAAADwyOTVDQjMzOEI2MTE1OTQ1ODJEODJEOUYyNkFFRjcwNkQw NDY0N0BtYWlsMDIuc3R1ZGVudC5tYWluLm50dS5lZHUuc2c+AF+N ------_=_NextPart_001_01C33F82.432A7323-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet