From exim@www1.ietf.org Tue Jul 1 13:47: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 NAA08074 for ; Tue, 1 Jul 2003 13:47:48 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5RITYM00634 for manet-archive@odin.ietf.org; Fri, 27 Jun 2003 14:29:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vxxq-0008Ku-01 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 OAA10274 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 19Vxx5-0007kr-SE; Fri, 27 Jun 2003 14:28:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VuZT-0002NW-13 for manet@optimus.ietf.org; Fri, 27 Jun 2003 10:51:27 -0400 Received: from dpt-info.u-strasbg.fr (dpt-info.u-strasbg.fr [130.79.44.193]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19906 for ; Fri, 27 Jun 2003 03:34:05 -0400 (EDT) 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 h5R7QkDc005012 for ; Fri, 27 Jun 2003 09:26:46 +0200 Message-ID: <002901c33c7d$d9e751a0$ac5a4f82@ustrasbg.fr> From: "Christophe Jelger" To: Date: Fri, 27 Jun 2003 09:29:31 +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 Subject: [manet] Distance vector routing and adhoc Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi all, I am 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 From exim@www1.ietf.org Tue Jul 1 13:48: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 NAA08295 for ; Tue, 1 Jul 2003 13:48:06 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5RIRoE28610 for manet-archive@odin.ietf.org; Fri, 27 Jun 2003 14:27:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Vxwp-0007RM-Hy for manet-web-archive@optimus.ietf.org; Fri, 27 Jun 2003 14:27: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 OAA09950 for ; Fri, 27 Jun 2003 14:27: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 19VxuB-00069z-IB; Fri, 27 Jun 2003 14:25:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19VuQY-0002NW-Oi for manet@optimus.ietf.org; Fri, 27 Jun 2003 10:43:39 -0400 Received: from london.unik.no ([193.156.97.32]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25509 for ; Fri, 27 Jun 2003 08:24:51 -0400 (EDT) Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Subject: Re: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Fri, 27 Jun 2003 14:23:40 +0200 Message-ID: Thread-Topic: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless network? thread-index: AcM798kS/4EXntXwSEaW6P2BWkxDawArbjhD From: "Andreas Hafslund" To: "Emmanuel Baccelli" , 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 > 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).=20 =20 What are the problems with OSPF for wireless (mostly static) links? Any = thoughts/ideas/references? I am very interested in knowing about these = problems. =20 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. =20 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? =20 Thanks for your reply. =20 Regards, Andreas Hafslund THALES Communications AS Norway =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 1 19:55:56 2003 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 TAA21372 for ; Tue, 1 Jul 2003 19:55:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XUy8-0005ia-FO for manet-archive@odin.ietf.org; Tue, 01 Jul 2003 19:55:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h61NtSOE021976 for manet-archive@odin.ietf.org; Tue, 1 Jul 2003 19: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 19XUy8-0005iN-CE for manet-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 19: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 TAA21330 for ; Tue, 1 Jul 2003 19:55:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XUy6-0002ZB-00 for manet-web-archive@ietf.org; Tue, 01 Jul 2003 19:55:26 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XUy5-0002Z4-00 for manet-web-archive@ietf.org; Tue, 01 Jul 2003 19:55:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XUxj-0005at-0Z; Tue, 01 Jul 2003 19:55:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XUxL-0005ZO-FG for manet@optimus.ietf.org; Tue, 01 Jul 2003 19: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 TAA21302 for ; Tue, 1 Jul 2003 19:54:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XUxJ-0002Y7-00 for manet@ietf.org; Tue, 01 Jul 2003 19:54:37 -0400 Received: from portal.east.saic.com ([198.151.13.15]) by ietf-mx with smtp (Exim 4.12) id 19XUxI-0002Y4-00 for manet@ietf.org; Tue, 01 Jul 2003 19:54:36 -0400 Received: from mcl-its-dq.saic.com by portal.east.saic.com via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with SMTP; Tue, 1 Jul 2003 19:54:37 -0400 Received: from mcl-its-ieg01.mail.saic.com by mcl-its-dq.saic.com for manet@ietf.org; Tue, 1 Jul 2003 19:54:37 -0400 Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12]) by mcl-its-ieg01.mail.saic.com (NAVGW 2.5.2.21) with SMTP id M2003070119543612996 ; Tue, 01 Jul 2003 19:54:36 -0400 Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service (5.5.2653.19) id ; Tue, 1 Jul 2003 19:53:50 -0400 Message-Id: <8A443FA5598F9545A4583F9D3BECE43F01174790@mcl-its-exs01> From: "Krishnaswamy, Padma" To: "Manral, Vishwas" , "'Andreas Hafslund'" , Emmanuel Baccelli , manet@ietf.org Subject: RE: [manet] OSPF vs OLSR/TBRPF for a "semi"*or highly* -mobile wi reless network? Date: Tue, 1 Jul 2003 19:54:29 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Some questions and observations re OSPF adaptations, and other protocols extending the earlier question from semi- to highly mobile settings- 1)what is the current assessment on how many nodes the various routing protocol choices scale to? Ive seen references to 200 nodes as the area limit for OSPF on the mailing list from a long while ago.I dont remember if that was for Area 0 or not. Im sure software's been optimized to do better now. So what is the current ballpark for OSPF? (Bearing in mind that the limits stated are for a wireline net, we can assume the numbers handleable for mobile nets would be less) 2)Is there similar data for the number of nodes that can be handled by OLSR/TBRPF/AODV? (presumably simulation based, in which case which mobility models were used?) 3) From some of the cited references, OSPF adaptations are stated as being desirable becasue OSPF unlike the MANET wg-developed protocols is intrinsically geared to handling heterogeneous (hybrid?) adhoc nets -can handle varying metrics,and can be used to fit into larger internets easier than a totally different protocol. 4) Some prospective applications also lean towards the use of OSPF but are looking at highly mobile scenarios. The ID by Fred Baker states that the point to multipoint interface is probably the best, with some other features needed for multi area operation. TOm Henderson mentioned their work on a new wireless interface that externally could be abstracted as a pt-multipt.So point to multipoint looks like the abstraction of choice, to represent the MANEt to OSPF. In this case, in a hypothetical scenario with high mobility, would multiarea operation be feasible given ABRs/DRs/MPRs might change the whole time? Is there a way to let the underlying layer 2 protocols- (these are not usually commercially available yet; are often proprietary and combine a lot self organization capabilities along with routing) take over dealing with the mobility as much as possible- assuming they scale- by using a limited number of IP ospf routers at layer 3 to function as ABRs and letting the subsequent forwarding be handled at layer 2? A simplistic analogy would be with an Ethernet where the default router would arp for the destination, then the forwarding would occur via the MAC layer. regards and tia for any information on the above- Padma > -----Original Message----- > From: Manral, Vishwas [mailto:VishwasM@netplane.com] > Sent: Saturday, June 28, 2003 4:03 AM > To: 'Andreas Hafslund'; Emmanuel Baccelli; manet@ietf.org > Subject: RE: [manet] OSPF vs OLSR/TBRPF for a "semi"-mobile wireless > network? > > > 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 > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 1 23:53:41 2003 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 XAA26878 for ; Tue, 1 Jul 2003 23:53:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XYgD-0004MQ-JY for manet-archive@odin.ietf.org; Tue, 01 Jul 2003 23:53:14 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h623rDZ0016756 for manet-archive@odin.ietf.org; Tue, 1 Jul 2003 23:53:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XYgD-0004MB-GD for manet-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 23:53: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 XAA26860 for ; Tue, 1 Jul 2003 23:53:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XYgB-00053l-00 for manet-web-archive@ietf.org; Tue, 01 Jul 2003 23:53:11 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XYgA-00053i-00 for manet-web-archive@ietf.org; Tue, 01 Jul 2003 23:53:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XYg1-0004IK-3J; Tue, 01 Jul 2003 23:53:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XYfi-0004I0-W7 for manet@optimus.ietf.org; Tue, 01 Jul 2003 23:52: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 XAA26852 for ; Tue, 1 Jul 2003 23:52:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XYfg-00053e-00 for manet@ietf.org; Tue, 01 Jul 2003 23:52:40 -0400 Received: from web21307.mail.yahoo.com ([216.136.128.232]) by ietf-mx with smtp (Exim 4.12) id 19XYfg-00053b-00 for manet@ietf.org; Tue, 01 Jul 2003 23:52:40 -0400 Message-ID: <20030702035240.29311.qmail@web21307.mail.yahoo.com> Received: from [137.132.3.7] by web21307.mail.yahoo.com via HTTP; Tue, 01 Jul 2003 20:52:40 PDT Date: Tue, 1 Jul 2003 20:52:40 -0700 (PDT) From: Rohit Gupta To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] Integration of 3G with AD hoc network Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , hi all, Is there anyone working on integration of 3G with ad hoc networks. Any pointers or links would be useful. regards, rohit __________________________________ 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 Wed Jul 2 03:39:46 2003 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 DAA27176 for ; Wed, 2 Jul 2003 03:39: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 19XcCz-0002Zl-MI for manet-archive@odin.ietf.org; Wed, 02 Jul 2003 03:39:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h627dHrP009898 for manet-archive@odin.ietf.org; Wed, 2 Jul 2003 03:39:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XcCz-0002ZZ-GS for manet-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 03:39: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 DAA27168 for ; Wed, 2 Jul 2003 03:39:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XcCx-0006tM-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 03:39:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XcCw-0006tJ-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 03:39:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XcCk-0002VX-7O; Wed, 02 Jul 2003 03:39:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XcBp-0002Sw-Fu for manet@optimus.ietf.org; Wed, 02 Jul 2003 03:38: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 DAA27152 for ; Wed, 2 Jul 2003 03:38:03 -0400 (EDT) From: jm.orset@free.fr Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XcBn-0006t0-00 for manet@ietf.org; Wed, 02 Jul 2003 03:38:03 -0400 Received: from postfix3-2.free.fr ([213.228.0.169]) by ietf-mx with esmtp (Exim 4.12) id 19XcBm-0006sx-00 for manet@ietf.org; Wed, 02 Jul 2003 03:38:02 -0400 Received: from imp3-1.free.fr (imp3-1.free.fr [213.228.0.28]) by postfix3-2.free.fr (Postfix) with ESMTP id 98A5BC5EE for ; Wed, 2 Jul 2003 09:38:02 +0200 (CEST) Received: by imp3-1.free.fr (Postfix, from userid 33) id 99E9EFBE0; Wed, 2 Jul 2003 09:41:55 +0200 (CEST) To: manet@ietf.org Message-ID: <1057131714.3f028cc259bb1@imp.free.fr> Date: Wed, 02 Jul 2003 09:41:54 +0200 (CEST) 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.6 X-Originating-IP: 157.159.100.240 Content-Transfer-Encoding: 8bit Subject: [manet] IP adressing in Manet 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: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Hello, forgive me if the following question appears stupid to you. In fact, I wondered simply if the concept of IP addressing such as one conceives it in the wired networks or some wireless (wifi) isn't incompatible with Manet model. Let me explain: a priori, there are two different manners to allocate an address IP with a computer.: - by a provider or - by a DHCP server inside the network However the concept of provider does not have any more sense in AD Hoc networks. Ad indeed each node offers its resources (band-width, processor) to the other nodes in a Community manner, so one can estimate that the need for a provider becomes totally obsolete. Concerning a dhcp server, on which certain articles are based, the difficulty of independence with respect to any infrastructure arises. This is however the base of Manet concep. That's why I wondered whether one could not consider that IP addresse of a node is allotted by the Ad hoc network itself, i.e. by the other nodes. This could perhaps even make it possible to ensure a better autentification. Forgive me if the question were already tackled but I did not find similar thread in the archives. Cordially, Jean-Marie ORSET _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 2 04:20:32 2003 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 EAA28123 for ; Wed, 2 Jul 2003 04:20:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XcqS-0005rd-Kz for manet-archive@odin.ietf.org; Wed, 02 Jul 2003 04:20:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h628K4PT022534 for manet-archive@odin.ietf.org; Wed, 2 Jul 2003 04:20:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XcqS-0005rG-7n for manet-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 04:20: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 EAA28090 for ; Wed, 2 Jul 2003 04:20:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XcqP-0007Fu-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 04:20:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XcqO-0007Fn-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 04:20:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XcpT-0005dI-Da; Wed, 02 Jul 2003 04: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 19Xcol-0005cI-Jj for manet@optimus.ietf.org; Wed, 02 Jul 2003 04:18:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28005 for ; Wed, 2 Jul 2003 04:18:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xcoi-0007DY-00 for manet@ietf.org; Wed, 02 Jul 2003 04:18:17 -0400 Received: from dpt-info.u-strasbg.fr ([130.79.44.193]) by ietf-mx with esmtp (Exim 4.12) id 19Xcoh-0007DV-00 for manet@ietf.org; Wed, 02 Jul 2003 04:18:16 -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 h628IFqK007477 for ; Wed, 2 Jul 2003 10:18:15 +0200 Message-ID: <003301c34072$db217c00$ac5a4f82@ustrasbg.fr> From: "Christophe Jelger" To: References: <002901c33c7d$d9e751a0$ac5a4f82@ustrasbg.fr><015301c33f0c$1470cc80$ac5a4f82@ustrasbg.fr> Subject: Re: [manet] Internet connectivity and AODV paper Date: Wed, 2 Jul 2003 10:20:54 +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 h628IFqK007477 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 Ryuji and thanks for your answer, Just a quick remark about routing in BSD when you say : > 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 > > 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. While this is correct, note that the gw is directly accessible at the MAC layer, i.e. the gw is a directly connected neighbor because it is reachab= le via its MAC address. This is indeed a "classical" and correct routing ent= ry with IPv6. However, this is far too simple. The problem arises when you have : default-route -> gw global-addr gw global-addr -> next_hop_neighbor addr This is not so trivial any more ... I did a few testing with BSD and this kind of entry does not work (with current implementations). While I agree that it is the best way to record the route to the gateway because only t= he host route needs to be changed in case of movements, it requires modifications in the OS code. This is why I rather advocate the use of a default route to the next_hop_neighbor to the gateway. This, of course, leads to a more complicated maintenance of this routing entry, but the go= od point is that we can use this mechanism with any OS without having to mod= ify kernel code. It is the routing daemon job to maintain the default route. Also note that I only consider this mechanism for proactive protocols. Fo= r reactive protocols, I would rather prefer not to use a default route, and the gateway should answer to RREQ for nodes outside the MANET. Regards, Christophe --------------------------------------------------------------- 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 Wed Jul 2 09:56:20 2003 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 JAA19598 for ; Wed, 2 Jul 2003 09:56:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xi5R-0002S7-4t for manet-archive@odin.ietf.org; Wed, 02 Jul 2003 09:55:53 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62DtrGW009427 for manet-archive@odin.ietf.org; Wed, 2 Jul 2003 09:55:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xi5R-0002Ry-26 for manet-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 09:55: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 JAA19524 for ; Wed, 2 Jul 2003 09:55:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xi5O-0007CY-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 09:55:51 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Xi5O-0007CV-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 09:55:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xi4b-0002OI-W6; Wed, 02 Jul 2003 09:55:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xi4Y-0002Nb-Mb for manet@optimus.ietf.org; Wed, 02 Jul 2003 09:54: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 JAA19407 for ; Wed, 2 Jul 2003 09:54:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xi4T-00079t-00 for manet@ietf.org; Wed, 02 Jul 2003 09:54:53 -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 19Xi4T-00079o-00 for manet@ietf.org; Wed, 02 Jul 2003 09:54:53 -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 AJP88776; Wed, 2 Jul 2003 09:54:47 -0400 (EDT) Message-ID: <3F02E427.5010501@isr.umd.edu> Date: Wed, 02 Jul 2003 09:54:47 -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] IP adressing in Manet model References: <1057131714.3f028cc259bb1@imp.free.fr> 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 you might also want to checkout: http://www.ee.ucl.ac.uk/lcs/papers2002/LCS120.pdf for a third, hybrid kind of scheme for autoconfiguration, pick a random address first, then try to get a valid one from the nearest gateway... -manish jm.orset@free.fr wrote: > Hello, forgive me if the following question appears stupid to you. > In fact, I wondered simply if the concept of IP addressing such as one conceives > it in the wired networks or some wireless (wifi) isn't incompatible with Manet > model. > Let me explain: a priori, there are two different manners to allocate an address IP > with a computer.: > - by a provider or > - by a DHCP server inside the network > > However the concept of provider does not have any more sense in AD Hoc networks. > Ad indeed each node offers its resources (band-width, processor) to the other > nodes in a Community manner, so one can estimate that the need for a provider > becomes totally obsolete. Concerning a dhcp server, on which certain articles > are based, the difficulty of independence with respect to any infrastructure > arises. This is however the base of Manet concep. That's why I wondered whether > one could not consider that IP addresse of a node is allotted by the Ad hoc > network itself, i.e. by the other nodes. This could perhaps even make it > possible to ensure a better autentification. > Forgive me if the question were already tackled but I did not find similar > thread in the archives. > > Cordially, > Jean-Marie ORSET _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 2 12:59:56 2003 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 MAA01363 for ; Wed, 2 Jul 2003 12:59:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xkx5-00074t-Bi for manet-archive@odin.ietf.org; Wed, 02 Jul 2003 12:59:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62GxRDD027201 for manet-archive@odin.ietf.org; Wed, 2 Jul 2003 12:59:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xkx5-00074e-6m for manet-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 12:59: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 MAA01322 for ; Wed, 2 Jul 2003 12:59:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xkx3-00040o-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 12:59:25 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Xkx3-00040l-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 12:59:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xkwf-00070S-IB; Wed, 02 Jul 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 19XkwP-0006zv-T4 for manet@optimus.ietf.org; Wed, 02 Jul 2003 12:58: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 MAA01303 for ; Wed, 2 Jul 2003 12:58:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XkwO-000408-00 for manet@ietf.org; Wed, 02 Jul 2003 12:58:44 -0400 Received: from web40902.mail.yahoo.com ([66.218.78.199]) by ietf-mx with smtp (Exim 4.12) id 19XkwN-0003zq-00 for manet@ietf.org; Wed, 02 Jul 2003 12:58:43 -0400 Message-ID: <20030702165812.1997.qmail@web40902.mail.yahoo.com> Received: from [158.94.84.174] by web40902.mail.yahoo.com via HTTP; Wed, 02 Jul 2003 09:58:12 PDT Date: Wed, 2 Jul 2003 09:58:12 -0700 (PDT) From: Hari Sivaramakrishnan To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1693501396-1057165092=:702" Subject: [manet] query Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-1693501396-1057165092=:702 Content-Type: text/plain; charset=us-ascii hi, i m a very novice user of qualnet. how can i use it to implement aodv simulations?? regs, hari --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! --0-1693501396-1057165092=:702 Content-Type: text/html; charset=us-ascii
hi,
 
    i m a very novice user of qualnet. how can i use it to implement aodv simulations??
 
regs,
hari


Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! --0-1693501396-1057165092=:702-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 2 13:14:46 2003 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 NAA02438 for ; Wed, 2 Jul 2003 13: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 19XlBS-0000O0-A7 for manet-archive@odin.ietf.org; Wed, 02 Jul 2003 13:14:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62HEIBg001478 for manet-archive@odin.ietf.org; Wed, 2 Jul 2003 13:14:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XlBS-0000Nl-5D for manet-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 13:14: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 NAA02404 for ; Wed, 2 Jul 2003 13:14:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XlBQ-0004N4-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 13:14:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XlBP-0004N1-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 13:14:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XlBB-0000Cv-W4; Wed, 02 Jul 2003 13:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XlAZ-0000Bp-8a for manet@optimus.ietf.org; Wed, 02 Jul 2003 13:13: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 NAA02326 for ; Wed, 2 Jul 2003 13:13:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XlAX-0004LS-00 for manet@ietf.org; Wed, 02 Jul 2003 13:13:21 -0400 Received: from web40905.mail.yahoo.com ([66.218.78.202]) by ietf-mx with smtp (Exim 4.12) id 19XlAW-0004I5-00 for manet@ietf.org; Wed, 02 Jul 2003 13:13:20 -0400 Message-ID: <20030702171245.3922.qmail@web40905.mail.yahoo.com> Received: from [158.94.84.174] by web40905.mail.yahoo.com via HTTP; Wed, 02 Jul 2003 10:12:45 PDT Date: Wed, 2 Jul 2003 10:12:45 -0700 (PDT) From: Hari Sivaramakrishnan To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1763409296-1057165965=:1133" Subject: [manet] query regarding my Msc project Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-1763409296-1057165965=:1133 Content-Type: text/plain; charset=us-ascii hi, at a very basic level, i would like to compare three routing protocols for ad-hoc networks. i have taken on the paper " performance comparision of three routing protocols for ad-hoc networks". can anyone please given me some kind of guidance as to how i should start my simulations for this comparision. i have 15 day evaluation copy of qualnet simulator(commercial glomosim). please give me a helping hand in this aspect. thanks. regards, Hari --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! --0-1763409296-1057165965=:1133 Content-Type: text/html; charset=us-ascii
hi,
 
    at a very basic level, i would like to compare three routing protocols for ad-hoc networks. i have taken on the paper  " performance comparision of three routing protocols for ad-hoc networks". can anyone please given me some kind of guidance as to how i should start my simulations for this comparision. i have 15 day evaluation copy of qualnet simulator(commercial glomosim). please give me a helping hand in this aspect. thanks.
 
regards,
Hari


Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! --0-1763409296-1057165965=:1133-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 2 14:07:17 2003 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 OAA04471 for ; Wed, 2 Jul 2003 14:07:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xm0H-0002oR-Ep for manet-archive@odin.ietf.org; Wed, 02 Jul 2003 14:06:49 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62I6nsX010805 for manet-archive@odin.ietf.org; Wed, 2 Jul 2003 14:06:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xm0H-0002oC-Ad for manet-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 14:06: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 OAA04450 for ; Wed, 2 Jul 2003 14:06:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xm0F-00057T-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 14:06:47 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Xm0E-00057Q-00 for manet-web-archive@ietf.org; Wed, 02 Jul 2003 14:06:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XlzV-0002h1-09; Wed, 02 Jul 2003 14:06:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XlzH-0002go-8N for manet@optimus.ietf.org; Wed, 02 Jul 2003 14:05: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 OAA04407 for ; Wed, 2 Jul 2003 14:05:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XlzF-00056G-00 for manet@ietf.org; Wed, 02 Jul 2003 14:05:45 -0400 Received: from mail.flarion.com ([63.103.94.23] helo=rrmail01.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 19XlzE-00055t-00 for manet@ietf.org; Wed, 02 Jul 2003 14:05:44 -0400 Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2656.59) id <3D5F3GV6>; Wed, 2 Jul 2003 14:05:08 -0400 Message-ID: <748C6D0A58C0F94CA63C198B6674697A01719DE0@ftmail.lab.flarion.com> From: Corson Scott To: "'manet@ietf.org'" Date: Wed, 2 Jul 2003 14:05:08 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C340C4.78F4E970" Subject: [manet] Agenda Presentation Request for upcoming Manet WG Mtg Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C340C4.78F4E970 Content-Type: text/plain Anyone wishing to present at the upcoming mtg in Austria, please let me know. Thx, Scott ------_=_NextPart_001_01C340C4.78F4E970 Content-Type: text/html Message
Anyone wishing to present at the upcoming mtg in Austria, please let me know.
 
Thx,  Scott
 
 
------_=_NextPart_001_01C340C4.78F4E970-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 3 08:21:53 2003 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 IAA08152 for ; Thu, 3 Jul 2003 08:21:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Y35Y-0001T5-Df for manet-archive@odin.ietf.org; Thu, 03 Jul 2003 08:21:24 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h63CLOjX005643 for manet-archive@odin.ietf.org; Thu, 3 Jul 2003 08:21:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Y35Y-0001Sw-Aj for manet-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 08:21: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 IAA08122 for ; Thu, 3 Jul 2003 08:21:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Y35X-0005hD-00 for manet-web-archive@ietf.org; Thu, 03 Jul 2003 08:21:23 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Y35W-0005h9-00 for manet-web-archive@ietf.org; Thu, 03 Jul 2003 08:21:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Y35B-0001Rb-RA; Thu, 03 Jul 2003 08:21:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Y35A-0001R9-7b for manet@optimus.ietf.org; Thu, 03 Jul 2003 08:21: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 IAA08111 for ; Thu, 3 Jul 2003 08:20:59 -0400 (EDT) From: jm.orset@free.fr Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Y359-0005gu-00 for manet@ietf.org; Thu, 03 Jul 2003 08:20:59 -0400 Received: from postfix3-2.free.fr ([213.228.0.169]) by ietf-mx with esmtp (Exim 4.12) id 19Y358-0005gq-00 for manet@ietf.org; Thu, 03 Jul 2003 08:20:58 -0400 Received: from impt2-2.proxad.net (impt2-2.free.fr [213.228.0.203]) by postfix3-2.free.fr (Postfix) with ESMTP id E5FF0C091 for ; Thu, 3 Jul 2003 14:20:39 +0200 (CEST) Received: by impt2-2.proxad.net (Postfix, from userid 33) id D694BB274; Thu, 3 Jul 2003 14:20:39 +0200 (MEST) Received: from 157.159.100.240 ([157.159.100.240]) by impt2-2.free.fr (IMP) with HTTP for ; Thu, 3 Jul 2003 14:20:38 +0200 Message-ID: <1057234838.3f041f96aa2f5@impt2-2.free.fr> Date: Thu, 3 Jul 2003 14:20:38 +0200 To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.1 Content-Transfer-Encoding: 8bit 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: 8bit Content-Transfer-Encoding: 8bit Hi, i've just read your draft and i find it very interesting. However, i wonder myself some questions: 1)Doesn't The fact that a node chooses randomly its address affect the hierarchical aspect of IP adressing? Because there is no more relation between the ip address of a node and the network it belongs to. Then if a node have to perform a broadcast it is obliged of flood the entire network. 2) What happens when 2 networks of 100 nodes or more, each one, merge to form a new network? I suppose that all nodes of both networks must reconfigure their IP address. This will result in a lot of control traffic in the both? 3) For security reasons, couldn't we consider that a node join a public key with its request: a) The node sends AREQ and join its public key b) The direct neighbours send him a "challenge", i mean a nonce ciphered with the public key at witch the node should answer by increasing it, in order to verify that it is really the owner of the key c) The node answers and only if this is correct, the neighbours accept to forward the request. if not The request is discarded. Thus, we could avoid the Denial of service attack wich would consist to always send AREQ through the network, in order to flood it with control paquets. Moreover the public key could then be used to sign the messages. I'll wait for your comments. Cordially, Jean-Marie Orset _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 3 14:25:47 2003 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 OAA29900 for ; Thu, 3 Jul 2003 14:25: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 19Y8lj-0003Du-HN for manet-archive@odin.ietf.org; Thu, 03 Jul 2003 14:25:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h63IPJaL012384 for manet-archive@odin.ietf.org; Thu, 3 Jul 2003 14:25:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Y8lj-0003Df-Cc for manet-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 14:25: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 OAA29874 for ; Thu, 3 Jul 2003 14:25:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Y8lg-00069b-00 for manet-web-archive@ietf.org; Thu, 03 Jul 2003 14:25:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Y8lg-00069Y-00 for manet-web-archive@ietf.org; Thu, 03 Jul 2003 14:25:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Y8lS-0003CV-68; Thu, 03 Jul 2003 14:25:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Y8l7-0003Bi-Lq for manet@optimus.ietf.org; Thu, 03 Jul 2003 14:24:41 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29839; Thu, 3 Jul 2003 14:24:39 -0400 (EDT) Message-Id: <200307031824.OAA29839@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: manet@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Thu, 03 Jul 2003 14:24:38 -0400 Subject: [manet] I-D ACTION:draft-ietf-manet-olsr-11.txt Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF. Title : Optimized Link State Routing Protocol Author(s) : T. Clausen, P. Jacquet Filename : draft-ietf-manet-olsr-11.txt Pages : 77 Date : 2003-7-3 This document describes the Optimized Link State Routing (OLSR) protocol for mobile ad hoc networks. The protocol is an optimization of the classical link state algorithm tailored to the requirements of a mobile wireless LAN. The key concept used in the protocol is that of multipoint relays (MPRs). MPRs are selected nodes which forward broadcast messages during the flooding process. This technique substantially reduces the message overhead as compared to a classical flooding mechanism, where every node retransmits each message when it receives the first copy of the message. In OLSR, link state information is generated only by nodes elected as MPRs. Thus, a second optimization is achieved by minimizing the number of control messages flooded in the network. As a third optimization, an MPR node may chose to report only links between itself and its MPR selectors. Hence, as contrary to the classic link state algorithm, partial link state information is distributed in the network. This information is then used by for route calculation. OLSR provides optimal routes (in terms of number of hops). The protocol is particularly suitable for large and dense networks as the technique of MPRs works well in this context. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-manet-olsr-11.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-manet-olsr-11.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-manet-olsr-11.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-7-3144357.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-manet-olsr-11.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-manet-olsr-11.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-3144357.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 3 17:25:48 2003 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 RAA07452 for ; Thu, 3 Jul 2003 17:25:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YBZw-0002t8-Ry for manet-archive@odin.ietf.org; Thu, 03 Jul 2003 17:25:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h63LPK0K011101 for manet-archive@odin.ietf.org; Thu, 3 Jul 2003 17: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 19YBZw-0002sy-N1 for manet-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 17: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 RAA07430 for ; Thu, 3 Jul 2003 17:25:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YBZu-0003br-00 for manet-web-archive@ietf.org; Thu, 03 Jul 2003 17:25:18 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YBZt-0003bo-00 for manet-web-archive@ietf.org; Thu, 03 Jul 2003 17:25:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YBZe-0002rl-Ti; Thu, 03 Jul 2003 17:25:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YBZ0-0002qt-8s for manet@optimus.ietf.org; Thu, 03 Jul 2003 17: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 RAA07414 for ; Thu, 3 Jul 2003 17:24:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YBYw-0003ap-00 for manet@ietf.org; Thu, 03 Jul 2003 17:24:18 -0400 Received: from smtpproxy2.mitre.org ([192.80.55.70]) by ietf-mx with esmtp (Exim 4.12) id 19YBYv-0003ak-00 for manet@ietf.org; Thu, 03 Jul 2003 17:24:17 -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 h63LOA6r010371 for ; Thu, 3 Jul 2003 17:24:10 -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 h63LO8OD028932 for ; Thu, 3 Jul 2003 17:24:09 -0400 (EDT) Received: from mailhubf.mitre.org (129.83.25.49) by mailhub1.mitre.org with SMTP id 3232774; Thu, 03 Jul 2003 17:24:04 -0400 Received: from jack.mitre.org (129.83.40.201) by mailhubf.mitre.org with SMTP id 1169; Thu, 03 Jul 2003 17:23:59 -0400 Date: Thu, 3 Jul 2003 17:23:56 -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: X-Mailer: Apple Mail (2.552) Content-Transfer-Encoding: 7bit Subject: [manet] Address Autoconfiguration Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, I'm looking for papers regarding IP address autoconfiguration. So far these are all I've located: IPv6 Stateless Address Autoconfiguration IPv6 Stateful Address Autoconfiguration draft-jeong-adhoc-ip-addr-autoconf-00.txt "Experience with Autoconfiguring a Network with IP-addresses" by McAuley, Misra, Wong and Manousakis., 2001. "Providing internet access to mobile ad hoc networks" by Andreadis. "Autoconfiguration for IP Networking: Enabling Local Communciation" by Guttman from IEEE Internet Computing, 2001. "MANETconf: Configuration of Hosts in a Mobile Ad Hoc Network" by Nesargi and Prakash, 2002 IEEE. "IPv6 Autconfiguration in Large Scale Mobile Ad-Hoc Networks" by Weniger and Zitterbart. Is there anything I'm missing, or does anyone know of newer versions than the ones listed? Anything even remotely related to Address Autoconfiguration would be very appreciated. Thanks for your assistance, 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 exim@www1.ietf.org Thu Jul 3 18:22:43 2003 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 SAA11452 for ; Thu, 3 Jul 2003 18:22:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YCT2-0000sG-UC for manet-archive@odin.ietf.org; Thu, 03 Jul 2003 18:22:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h63MMGdU003356 for manet-archive@odin.ietf.org; Thu, 3 Jul 2003 18:22:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YCT2-0000s3-Qw for manet-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 18:22: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 SAA11428 for ; Thu, 3 Jul 2003 18:22:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YCSz-0005b2-00 for manet-web-archive@ietf.org; Thu, 03 Jul 2003 18:22:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YCSz-0005az-00 for manet-web-archive@ietf.org; Thu, 03 Jul 2003 18:22:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YCSn-0000lW-9X; Thu, 03 Jul 2003 18: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 19YCST-0000lG-H4 for manet@optimus.ietf.org; Thu, 03 Jul 2003 18:21: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 SAA11412 for ; Thu, 3 Jul 2003 18:21:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YCSQ-0005aY-00 for manet@ietf.org; Thu, 03 Jul 2003 18:21:38 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19YCSP-0005aS-00 for manet@ietf.org; Thu, 03 Jul 2003 18:21:37 -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 PAA01514; Thu, 3 Jul 2003 15:21:05 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h63ML4M23818; Thu, 3 Jul 2003 15:21:04 -0700 X-mProtect: <200307032221> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.22.18, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdgAQMuY; Thu, 03 Jul 2003 15:21:02 PDT Message-ID: <3F04AC59.3090403@iprg.nokia.com> Date: Thu, 03 Jul 2003 15:21:13 -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] Address Autoconfiguration 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 Hello Ralph, You might take a look at our autoconfiguration draft: http://people.nokia.net/charliep/txt/aodvid/autoconf.txt Regards, Charlie P. Ralph Preston wrote: > Hello, > > I'm looking for papers regarding IP address autoconfiguration. So far > these are all I've located: > > IPv6 Stateless Address Autoconfiguration > IPv6 Stateful Address Autoconfiguration > draft-jeong-adhoc-ip-addr-autoconf-00.txt > "Experience with Autoconfiguring a Network with IP-addresses" by > McAuley, Misra, Wong and Manousakis., 2001. > "Providing internet access to mobile ad hoc networks" by Andreadis. > "Autoconfiguration for IP Networking: Enabling Local Communciation" by > Guttman from IEEE Internet Computing, 2001. > "MANETconf: Configuration of Hosts in a Mobile Ad Hoc Network" by > Nesargi and Prakash, 2002 IEEE. > "IPv6 Autconfiguration in Large Scale Mobile Ad-Hoc Networks" by > Weniger and Zitterbart. > > Is there anything I'm missing, or does anyone know of newer versions > than the ones listed? Anything even remotely related to Address > Autoconfiguration would be very appreciated. > > Thanks for your assistance, > > 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 exim@www1.ietf.org Thu Jul 3 20:05:46 2003 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 UAA27542 for ; Thu, 3 Jul 2003 20:05: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 19YE4i-0003pp-BZ for manet-archive@odin.ietf.org; Thu, 03 Jul 2003 20:05:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6405Gwh014738 for manet-archive@odin.ietf.org; Thu, 3 Jul 2003 20:05:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YE4i-0003pd-79 for manet-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 20:05: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 UAA27521 for ; Thu, 3 Jul 2003 20:05:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YE4g-0005bH-00 for manet-web-archive@ietf.org; Thu, 03 Jul 2003 20:05:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YE4f-0005bE-00 for manet-web-archive@ietf.org; Thu, 03 Jul 2003 20:05:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YE4T-0003oT-UA; Thu, 03 Jul 2003 20:05:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YE3h-0003nw-Js for manet@optimus.ietf.org; Thu, 03 Jul 2003 20: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 UAA27501 for ; Thu, 3 Jul 2003 20:04:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YE3f-0005Zi-00 for manet@ietf.org; Thu, 03 Jul 2003 20:04:11 -0400 Received: from ns.sait.samsung.co.kr ([202.20.142.13]) by ietf-mx with esmtp (Exim 4.12) id 19YE3e-0005Y4-00 for manet@ietf.org; Thu, 03 Jul 2003 20:04:10 -0400 Received: from mavpc (localhost [127.0.0.1]) by ns.sait.samsung.co.kr (8.12.9/8.12.1) with SMTP id h6403UOT012668; Fri, 4 Jul 2003 09:03:31 +0900 (KST) Message-ID: <002a01c341bf$bcd88010$db2f024b@mavpc> From: "Jihoon Lee" To: "Ralph Preston" , References: Subject: Re: [manet] Address Autoconfiguration Date: Fri, 4 Jul 2003 09:03:45 +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.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: base64 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 SGVsbG8uDQoNCkFkZGl0aW9uYWwgaW5mb3JtYXRpb24NCg0KIklQIEFkZHJlc3MgQXNzaWdubWVu dCBpbiBhIE1vYmlsZSBBZCBIb2MgTmV0d29yayIgYnkgTWFuc29vciBmcm9tIE1pbGNvbTAyDQoN Ci0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQpGcm9tOiAiUmFscGggUHJlc3RvbiIgPHJw cmVzdG9uQG1pdHJlLm9yZz4NClRvOiA8bWFuZXRAaWV0Zi5vcmc+DQpTZW50OiBGcmlkYXksIEp1 bHkgMDQsIDIwMDMgNjoyMyBBTQ0KU3ViamVjdDogW21hbmV0XSBBZGRyZXNzIEF1dG9jb25maWd1 cmF0aW9uDQoNCg0KPiBIZWxsbywNCj4gDQo+IEknbSBsb29raW5nIGZvciBwYXBlcnMgcmVnYXJk aW5nIElQIGFkZHJlc3MgYXV0b2NvbmZpZ3VyYXRpb24uICBTbyBmYXIgDQo+IHRoZXNlIGFyZSBh bGwgSSd2ZSBsb2NhdGVkOg0KPiANCj4gSVB2NiBTdGF0ZWxlc3MgQWRkcmVzcyBBdXRvY29uZmln dXJhdGlvbg0KPiBJUHY2IFN0YXRlZnVsIEFkZHJlc3MgQXV0b2NvbmZpZ3VyYXRpb24NCj4gZHJh ZnQtamVvbmctYWRob2MtaXAtYWRkci1hdXRvY29uZi0wMC50eHQNCj4gIkV4cGVyaWVuY2Ugd2l0 aCBBdXRvY29uZmlndXJpbmcgYSBOZXR3b3JrIHdpdGggSVAtYWRkcmVzc2VzIiBieSANCj4gTWNB dWxleSwgTWlzcmEsIFdvbmcgYW5kIE1hbm91c2FraXMuLCAyMDAxLg0KPiAiUHJvdmlkaW5nIGlu dGVybmV0IGFjY2VzcyB0byBtb2JpbGUgYWQgaG9jIG5ldHdvcmtzIiBieSBBbmRyZWFkaXMuDQo+ ICJBdXRvY29uZmlndXJhdGlvbiBmb3IgSVAgTmV0d29ya2luZzogRW5hYmxpbmcgTG9jYWwgQ29t bXVuY2lhdGlvbiIgYnkgDQo+IEd1dHRtYW4gZnJvbSBJRUVFIEludGVybmV0IENvbXB1dGluZywg MjAwMS4NCj4gIk1BTkVUY29uZjogQ29uZmlndXJhdGlvbiBvZiBIb3N0cyBpbiBhIE1vYmlsZSBB ZCBIb2MgTmV0d29yayIgYnkgDQo+IE5lc2FyZ2kgYW5kIFByYWthc2gsIDIwMDIgSUVFRS4NCj4g IklQdjYgQXV0Y29uZmlndXJhdGlvbiBpbiBMYXJnZSBTY2FsZSBNb2JpbGUgQWQtSG9jIE5ldHdv cmtzIiBieSANCj4gV2VuaWdlciBhbmQgWml0dGVyYmFydC4NCj4gDQo+IElzIHRoZXJlIGFueXRo aW5nIEknbSBtaXNzaW5nLCBvciBkb2VzIGFueW9uZSBrbm93IG9mIG5ld2VyIHZlcnNpb25zIA0K PiB0aGFuIHRoZSBvbmVzIGxpc3RlZD8gICBBbnl0aGluZyBldmVuIHJlbW90ZWx5IHJlbGF0ZWQg dG8gQWRkcmVzcyANCj4gQXV0b2NvbmZpZ3VyYXRpb24gd291bGQgYmUgdmVyeSBhcHByZWNpYXRl ZC4NCj4gDQo+IFRoYW5rcyBmb3IgeW91ciBhc3Npc3RhbmNlLA0KPiANCj4gUmFscGggQS4gUHJl c3Rvbg0KPiBUaGUgTUlUUkUgQ29ycG9yYXRpb24NCj4gMjAyIEJ1cmxpbmd0b24gUm9hZCAgTVMg RTA5NQ0KPiBCZWRmb3JkLCBNQSAwMTczMC0xNDIwDQo+IGh0dHA6Ly93d3cubWl0cmUub3JnDQo+ IA0KPiANCj4gDQo+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXw0KPiBtYW5ldCBtYWlsaW5nIGxpc3QNCj4gbWFuZXRAaWV0Zi5vcmcNCj4gaHR0cHM6 Ly93d3cxLmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWFuZXQNCj4gDQo+IA== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 4 02:53:44 2003 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 CAA18248 for ; Fri, 4 Jul 2003 02:53:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YKRT-0001hN-Kl for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 02:53:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h646rBKQ006528 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 02:53:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YKRT-0001hD-D3 for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 02:53: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 CAA18214 for ; Fri, 4 Jul 2003 02:53:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YKRP-0002jp-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 02:53:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YKRP-0002jm-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 02:53:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YKRI-0001fl-UI; Fri, 04 Jul 2003 02:53:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YKQe-0001ZT-VC for manet@optimus.ietf.org; Fri, 04 Jul 2003 02:52: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 CAA18164 for ; Fri, 4 Jul 2003 02:52:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YKQb-0002jL-00 for manet@ietf.org; Fri, 04 Jul 2003 02:52:17 -0400 Received: from [202.38.193.39] (helo=scutsv39.scut.edu.cn) by ietf-mx with esmtp (Exim 4.12) id 19YKQX-0002iy-00 for manet@ietf.org; Fri, 04 Jul 2003 02:52:15 -0400 Received: from scut.edu.cn (smtp.scut.edu.cn [202.38.193.34]) by scutsv39.scut.edu.cn (8.9.3/8.9.3) with ESMTP id OAA19672 for ; Fri, 4 Jul 2003 14:44:47 +0800 (CST) Received: from cs7116 ([158.182.7.116]) (authenticated bits=0) by scut.edu.cn (8.12.7/8.12.7) with ESMTP id h646ikps016814 for ; Fri, 4 Jul 2003 14:44:49 +0800 Message-Id: <200307040644.h646ikps016814@scut.edu.cn> From: "Jinglun Shi" To: "manet@ietf.org" X-mailer: Foxmail 4.2 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 4 Jul 2003 14:51:29 +0800 Content-Transfer-Encoding: quoted-printable Subject: [manet] address the self-organization agents system and the ad hoc networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Hello, Now I'm in charge of the project "Autonomic Computing in the= adaptive Systems" and "The QoS provision for Ad hoc networks"= http://www.comp.hkbu.edu.hk/~aoc/index.htm. I want to integrate the multi-agent system with the Ad hoc networks, is= there any other related works done, or does anyone know of the= related people? Anything even remotely related to Address the= topic would be very appreciated. Thanks for your assistance, =09 Best regards, =09=09=09=09 =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1Jinglun Shi =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1jlshi@scut.edu.cn =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12003-07-04 =3D=3D=3D=3D=3D=3D=3D=3D Shi Jinglun Department of Computer Science Hong Kong Baptist University Kowloon Tong, Hong Kong Office: R726 Tel: (852) 3411-5964 jlshi@scut.edu.cn,jlshi@comp.hkbu.edu.hk _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 4 03:05:56 2003 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 DAA18739 for ; Fri, 4 Jul 2003 03:05:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YKdM-00038m-TM for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 03:05:28 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6475S59012069 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 03:05:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YKXG-0002YT-Na for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 02:59: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 CAA18483 for ; Fri, 4 Jul 2003 02:59:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YKXC-0002q8-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 02:59:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YKXB-0002q3-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 02:59:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YKX8-0002TQ-7T; Fri, 04 Jul 2003 02: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 19YKWZ-0002So-G7 for manet@optimus.ietf.org; Fri, 04 Jul 2003 02: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 CAA18458 for ; Fri, 4 Jul 2003 02:58:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YKWV-0002pU-00 for manet@ietf.org; Fri, 04 Jul 2003 02:58:23 -0400 Received: from [202.38.193.39] (helo=scutsv39.scut.edu.cn) by ietf-mx with esmtp (Exim 4.12) id 19YKWS-0002pB-00 for manet@ietf.org; Fri, 04 Jul 2003 02:58:21 -0400 Received: from scut.edu.cn (smtp.scut.edu.cn [202.38.193.34]) by scutsv39.scut.edu.cn (8.9.3/8.9.3) with ESMTP id OAA22064 for ; Fri, 4 Jul 2003 14:50:50 +0800 (CST) Received: from cs7116 ([158.182.7.116]) (authenticated bits=0) by scut.edu.cn (8.12.7/8.12.7) with ESMTP id h646oops001784 for ; Fri, 4 Jul 2003 14:50:53 +0800 Message-Id: <200307040650.h646oops001784@scut.edu.cn> From: "Jinglun Shi" To: "manet@ietf.org" X-mailer: Foxmail 4.2 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 4 Jul 2003 14:57:33 +0800 Content-Transfer-Encoding: quoted-printable Subject: [manet] about the PIMRC 2003 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable hi,all. Is there anyone who's paper about ad hoc was accepted by PIMRC= 2003 or attend the PIMRC 2003? Best regards, =09=09=09=09 =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1Jinglun Shi =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1jlshi@scut.edu.cn =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12003-07-04 =3D=3D=3D=3D=3D=3D=3D=3D Shi Jinglun Department of Computer Science Hong Kong Baptist University Kowloon Tong, Hong Kong Office: R726 Tel: (852) 3411-5964 jlshi@scut.edu.cn,jlshi@comp.hkbu.edu.hk _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 4 04:31:45 2003 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 EAA20361 for ; Fri, 4 Jul 2003 04:31: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 19YLyP-00009O-T8 for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 04:31:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h648VHPu000577 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 04:31:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YLyP-00009E-NO for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 04:31: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 EAA20318 for ; Fri, 4 Jul 2003 04:31:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YLyM-0003Or-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 04:31:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YLyM-0003Oo-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 04:31:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YLyB-00007N-86; Fri, 04 Jul 2003 04: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 19YLxY-000065-20 for manet@optimus.ietf.org; Fri, 04 Jul 2003 04:30: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 EAA20291 for ; Fri, 4 Jul 2003 04:30:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YLxV-0003OP-00 for manet@ietf.org; Fri, 04 Jul 2003 04:30:21 -0400 Received: from roura.ac.upc.es ([147.83.33.10]) by ietf-mx with esmtp (Exim 4.12) id 19YLxU-0003O4-00 for manet@ietf.org; Fri, 04 Jul 2003 04:30:20 -0400 Received: from rogent.ac.upc.es (rogent.ac.upc.es [147.83.31.7]) by roura.ac.upc.es (8.12.8/8.12.8) with ESMTP id h648Tn44011460 for ; Fri, 4 Jul 2003 10:29:49 +0200 (MET DST) Received: (from ew2004@localhost) by rogent.ac.upc.es (8.12.8/8.12.8) id h648Tntn024910 for manet@ietf.org; Fri, 4 Jul 2003 10:29:49 +0200 (MET DST) Date: Fri, 4 Jul 2003 10:29:49 +0200 From: Conferencia ew2004 To: manet@ietf.org Message-ID: <20030704082948.GA24905@ac.upc.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.4.1i Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by roura.ac.upc.es id h648Tn44011460 Content-Transfer-Encoding: quoted-printable Subject: [manet] European Wireless'04 CFP reminder Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 Dear Colleague, We would like to draw your attention to the "5th European Wireless Conference" Barcelona, Spain, February 2004. We would appreciate your assistance in distributing this call for papers to your colleagues. All the details about the conference can be found at: http://www.ac.upc.es/EW2004 Best regards, EW2004 organizing committee. ------------------------------------------------------------------------- EW2004 The 5th European Wireless Conference Mobile and Wireless Systems beyond 3G http://www.ac.upc.es/EW2004=20 February 24-27, 2004 Technical University of Catalonia (UPC) - Barcelona, Spain CONFERENCE SCOPE In order to be able to be connected anywhere and at anytime a seamless ac= cess to the various access technologies is needed providing the adequate QoS t= o=20 diverse applications.=20 The 5th European Wireless Conference focuses on technologies, protocols,=20 services and applications that will enable a full seamless and nomadic us= er=20 access to new classes of person to person, device to device and device=20 to person applications. TOPICS Technical papers describing original, previously unpublished research are= solicited.=20 Specific topics of interest include, but are not limited to, the followin= g: * Adaptive Antennas * Base Station Technology * Indoor Channel Modeling( Wave Propagation and Measurements * Integration of Radio Localization Systems into Wireless User Terminals * Integration of Terrestrial and Satellite Networks * Interference Mitigation and Management Techniques * Power and Interference Control * Power Management for small terminals * Protocols for Air Interfaces and Networks * Short Range Communication Systems * Signal Processing Techniques for Communications * Analysis( Simulation and Measurements of Mobile and Wireless Systems * High Altitude Platforms and Satellites * Internetworking between Different Access Technologies * Mobile Agents * Mobile and Wireless Applications * Mobility Management * Multiple Access Schemes * Positioning=20 * QoS in Mobile and Wireless Networks * Routing in Ad hoc Networks * Security and robustness in wireless networks * Sensor Network Planning and Deployment * Wireless Ad hoc Networks * Wireless LANs PAPER SUBMISSION INSTRUCTIONS Papers for the conference should be written in English and with a limit o= f 12 double=20 spaced pages. All paper submissions will be handled electronically, following the instr= uctions at: http://www.ac.upc.es/EW2004 All papers will be reviewed by the program committee members. Accepted papers will be published in the conference proceedings.=20 IMPORTANT DATES Full papers due: September 10th 2003 Notification of Acceptance: November 14th 2003 Camera Ready due: December 12th 2003 GENERAL CHAIR:=20 Olga Casals, (Technical University of Catalonia, UPC, Spain) Jorge Garcia-Vidal (Technical University of Catalonia, UPC, Spain) STEERING COMMITTEE CHAIR:=20 Bernhard Walke (Aachen University of Technology, Germany) TECHNICAL PROGRAM CO-CHAIRS: Miguel A. Lagunas (CTTC, Spain) Ioannis Stavrakakis (University of Athens, Greece) TUTORIAL CHAIR: Jorge Garc=EDa-Vidal (UPC, Spain) LOCAL ARRANGEMENTS CO-CHAIRS: Carles Ant=F3n (CTTC, Spain) Jose M. Barcel=F3 (UPC, Spain) Lloren=E7 Cerd=E0 (UPC, Spain) TECHNICAL PROGRAM COMMITTEE: R. Agust=ED (UPC, Spain) I. Akyildiz (Georgia Ins. of Technology, USA) E. Altman (INRIA, France) A. Art=E9s (Univ. Carlos III, Spain) S. Benedetto (Politecnico de Torino, Italy) C. Blondia (Univ. of Antwerp, Belgium) E. Bonek (TU of Viena, Austria) A. Campbell (Columbia University, USA) V. Casares (UPV, Spain) E. Casilari (Univ. de Malaga, Spain) L. Castedo (Univ. de La Coru=F1a, Spain) M. Conti (IIT/CNR, Italy) L. Correia (IST, Portugal) L. Cuthbert (Univ. of London, UK) J. Dunlop (Univ. of Strathclyde, UK) S. Giordano (EPFL, Switzerland) H. Kawashima (Tokio Univ. of Agriculture & Technology, Japan) U. K=F6rner (Univ. of Lund, Sweden) P. Kuehn (Univ. of Stuttgart, Germany) L. Lenzini (Univ. of Pisa, Italy) J. M. Paez Borrallo (UPM, Spain) J. Paradells (UPC, Spain) C. Rosenberg (Purdue University, USA) H. St=FCttgen (NEC, Germany) A. Svensson (Chalmers, Sweden) R. Tafazolli (Univ. of Surrey, UK) Y. Takahashi (Kyoto University, Japan) L. Tassiulas (Univ. of Maryland, USA) S. Tohme (ENST, France) P. Tran-Gia (Univ. of W=FCrzburg, Germany) M. Uylat (Univ. of Waterloo, Canada) A. Valko (Ericsson, Sweden) A. Vilavaara (Nokia Research Center, Finland) A. Wolisz (Univ. of Berlin, Germany) J. Zander (KTH Stockholm, Sweden) M. Zukerman (Univ. of Melbourne, Australia) EW2004 CONTACT e-mail: ew2004@ac.upc.es FINANCE CHAIR Volker Schanz, VDE/ITG, Germany CONFERENCE SECRETARIAT VDE-Conference Department Stresemannallee 1560596 Frankfurt-Main Germany Phone: +49-69-6308-202 Fax: +49-69-97315213 e-mail: vde-conferences@vde.com URL: www.vde.com=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 4 06:56:38 2003 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 GAA23066 for ; Fri, 4 Jul 2003 06:56:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YOEe-0001Fw-GB for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 06:56:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h64AuChV004827 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 06:56:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YOEe-0001Fm-D7 for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 06:56: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 GAA23054 for ; Fri, 4 Jul 2003 06:56:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YOEa-0004BE-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 06:56:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YOEZ-0004BB-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 06:56:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YOEV-0001Ea-5a; Fri, 04 Jul 2003 06:56:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YOEA-0001EE-3d for manet@optimus.ietf.org; Fri, 04 Jul 2003 06:55: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 GAA23048 for ; Fri, 4 Jul 2003 06:55:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YOE5-0004B2-00 for manet@ietf.org; Fri, 04 Jul 2003 06:55:37 -0400 Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx with esmtp (Exim 4.12) id 19YOE5-0004Ay-00 for manet@ietf.org; Fri, 04 Jul 2003 06:55:37 -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 MAA29211 for ; Fri, 4 Jul 2003 12:55:37 +0200 (MET DST) Message-ID: <3F055D46.8010803@telecom.lth.se> Date: Fri, 04 Jul 2003 12:56:06 +0200 From: Anders Nilsson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: MANET mailing list Subject: Re: [manet] Internet-MANET gateways? References: <000001c3313d$4b598570$67f57b80@IEngr.ad.nmsu.edu> <5.1.1.5.2.20030613152454.0251c240@pop.itd.nrl.navy.mil> Content-Type: multipart/alternative; boundary="------------070708090206020400090204" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------070708090206020400090204 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hello All, I haven't read this thread until now and is almost amazed that none has mentioned Mobile IP. When using mobile IP, you still have your home address and a newly configured c-o address pointing towards the manet. There you have an available solution for being accessible while away from home and still being able to access the internet. Isn't that what we wanted? regards, Anders Joe Macker wrote: >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 > > > --------------070708090206020400090204 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello All,

I haven't read this thread until now and is almost amazed that none has mentioned Mobile IP. When using
mobile IP, you still have your home address and a newly configured c-o address pointing towards the manet.
There you have an available solution for being accessible while away from home and still being able to access the internet. Isn't that what we wanted?

regards,

Anders

Joe Macker wrote:
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

--------------070708090206020400090204-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 4 12:18:50 2003 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 MAA01072 for ; Fri, 4 Jul 2003 12:18: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 19YTGQ-0000v8-Nl for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 12:18:23 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h64GIM0a003539 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 12:18:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YTGQ-0000uz-K8 for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 12:18: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 MAA01050 for ; Fri, 4 Jul 2003 12:18:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YTGP-0007OQ-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 12:18:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YTGO-0007OM-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 12:18:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YTG5-0000to-AY; Fri, 04 Jul 2003 12:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YTFr-0000ta-Qq for manet@optimus.ietf.org; Fri, 04 Jul 2003 12:17: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 MAA01041 for ; Fri, 4 Jul 2003 12:17:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YTFq-0007O3-00 for manet@ietf.org; Fri, 04 Jul 2003 12:17:46 -0400 Received: from mail.ncc.up.pt ([193.136.39.2]) by ietf-mx with esmtp (Exim 4.12) id 19YTFp-0007Nr-00 for manet@ietf.org; Fri, 04 Jul 2003 12:17:45 -0400 Received: from ncc.up.pt (khanna.ncc.up.pt [10.0.0.71]) by mail.ncc.up.pt (Postfix) with ESMTP id 29F20E98C for ; Fri, 4 Jul 2003 17:17:11 +0100 (WEST) Message-ID: <3F05A886.8030108@ncc.up.pt> Date: Fri, 04 Jul 2003 17:17:10 +0100 From: Sergio Crisostomo User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org X-Enigmail-Version: 0.74.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id MAA01042 Subject: [manet] HELLO messages 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: quoted-printable Content-Transfer-Encoding: quoted-printable Hi all, I've a question regarding HELLO message processing in AODV. In draft-ietf-manet-aodv-13.txt, section 6.9 states: 1) " A node SHOULD only use hello messages if it is part of an active=20 route.". Then, below in the same section it is stated: 2) "Whenever a node receives a Hello message from a neighbor, the node SHOULD make sure that it has an active route to the neighbor, and create one if necessary." In the draft, active route is defined as: " active route - A route towards a destination that has a routing table=20 entry that is marked as valid. Only active routes can be used to=20 forward data packets. " From my understanding, this implies that once a node (say n1)=20 broadcasts an HELLO, all neighboor nodes 'hearing' that HELLO=20 (Neigh(n1)) will creat an ACTIVE routing entry to n1... So, all Neigh(n1) MAY start brodcasting HELLOs.. Let's assume they do... This implies that all nodes that have multihop radio connectivity to=20 some node n1 which started brodcasting HELLOs will have active routes=20 and all will brodcast HELLOs.... Please tell me if I'm wright... If so, tell me if this correction to statement 1) above is correct: "A node SHOULD only use hello messages if it is part of an active route=20 WITH A NON EMPTY PRECURSOR LIST.". Best Regards, S=E9rgio. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 4 12:23:46 2003 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 MAA01309 for ; Fri, 4 Jul 2003 12:23: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 19YTL5-0001Ur-E6 for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 12:23:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h64GNBMP005754 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 12:23:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YTL5-0001Uj-7g for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 12:23: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 MAA01244 for ; Fri, 4 Jul 2003 12:23:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YTL3-0007Uw-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 12:23:09 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YTL3-0007Ut-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 12:23:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YTKv-0001JA-Uz; Fri, 04 Jul 2003 12: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 19YTK2-0001Ih-ND for manet@optimus.ietf.org; Fri, 04 Jul 2003 12:22: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 MAA01218 for ; Fri, 4 Jul 2003 12:22:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YTK1-0007U0-00 for manet@ietf.org; Fri, 04 Jul 2003 12:22:05 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19YTK0-0007TW-00 for manet@ietf.org; Fri, 04 Jul 2003 12:22:04 -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 h64GLTDi006482; Fri, 4 Jul 2003 12:21:29 -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 h64GLSKN020483; Fri, 4 Jul 2003 12:21:29 -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 M2003070412212813386 ; Fri, 04 Jul 2003 12:21:28 -0400 Message-Id: <5.1.1.5.2.20030704121519.0349d6e8@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Fri, 04 Jul 2003 12:23:15 -0400 To: Anders Nilsson , MANET mailing list From: Joe Macker Subject: Re: [manet] Internet-MANET gateways? In-Reply-To: <3F055D46.8010803@telecom.lth.se> References: <000001c3313d$4b598570$67f57b80@IEngr.ad.nmsu.edu> <5.1.1.5.2.20030613152454.0251c240@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 12:56 PM 7/4/2003 +0200, Anders Nilsson wrote: >Hello All, > >I haven't read this thread until now and is almost amazed that none has mentioned Mobile IP. When using >mobile IP, you still have your home address and a newly configured c-o address pointing towards the manet. >There you have an available solution for being accessible while away from home and still being able to access the internet. Isn't that what we wanted? If a node needs a global identifier mobileIP is one workable solution. (I think you are right that that is workable). My only point was there are application areas that don't require that level of functionality. -Joe >regards, > >Anders > >Joe Macker wrote: >> >>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 >> >> _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 4 13:56:58 2003 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 NAA03134 for ; Fri, 4 Jul 2003 13:56:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YUnN-0000qx-Ah for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 13:56:30 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h64HuTau003276 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 13:56:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YUnN-0000ql-7X for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 13:56:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03109 for ; Fri, 4 Jul 2003 13:56:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YUnK-0000Uy-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 13:56:26 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YUnK-0000Uv-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 13:56:26 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YUmw-0000mZ-4Q; Fri, 04 Jul 2003 13:56:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YUmV-0000lj-AR for manet@optimus.ietf.org; Fri, 04 Jul 2003 13:55: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 NAA03067 for ; Fri, 4 Jul 2003 13:55:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YUmS-0000U4-00 for manet@ietf.org; Fri, 04 Jul 2003 13:55:32 -0400 Received: from rdu163-96-075.nc.rr.com ([24.163.96.75] helo=data.ece.ncsu.edu) by ietf-mx with esmtp (Exim 4.12) id 19YUmS-0000U0-00 for manet@ietf.org; Fri, 04 Jul 2003 13:55:32 -0400 Received: from localhost (mlsichit@localhost) by data.ece.ncsu.edu (8.11.6/8.11.6) with ESMTP id h64HllB03374 for ; Fri, 4 Jul 2003 13:47:47 -0400 X-Authentication-Warning: data.ece.ncsu.edu: mlsichit owned process doing -bs Date: Fri, 4 Jul 2003 13:47:47 -0400 (EDT) From: "Mihail L. Sichitiu" X-X-Sender: mlsichit@data.ece.ncsu.edu To: manet@ietf.org In-Reply-To: <20030704160003.27294.49666.Mailman@www1.ietf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Re: 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: , Not my work, but I think that there exists an approach with very good scalability, and not very well known. The idea is presented in detail in a thesis of an MS student at U.T. Dallas in August 2002. The old link is http://www.utdallas.edu/~mansi/, but it's not longer active. The main idea, was first published (unpolished) by a student in Maryland (his papers were references [12] and [13] in the thesis). Unfortunately I didn't see any publications following that thesis. It's a pity, the idea is very nice. The main idea of the thesis (and original papers) is simple: each node in the ad-hoc network acts like a DHCP server that has besides its IP address a range of IP addresses that can offer. When a new node joins an already existing node it offers an IP address and half of its IP addresses in its care. The thesis takes care of other details like network merging and partitioning, and address reclaiming. Happy digging for that thesis. Mihai _______________________________________________________ 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 _______________________________________________________ > Hello, > > I'm looking for papers regarding IP address autoconfiguration. So far > these are all I've located: > > IPv6 Stateless Address Autoconfiguration > IPv6 Stateful Address Autoconfiguration > draft-jeong-adhoc-ip-addr-autoconf-00.txt > "Experience with Autoconfiguring a Network with IP-addresses" by > McAuley, Misra, Wong and Manousakis., 2001. > "Providing internet access to mobile ad hoc networks" by Andreadis. > "Autoconfiguration for IP Networking: Enabling Local Communciation" by > Guttman from IEEE Internet Computing, 2001. > "MANETconf: Configuration of Hosts in a Mobile Ad Hoc Network" by > Nesargi and Prakash, 2002 IEEE. > "IPv6 Autconfiguration in Large Scale Mobile Ad-Hoc Networks" by > Weniger and Zitterbart. > > Is there anything I'm missing, or does anyone know of newer versions > than the ones listed? Anything even remotely related to Address > Autoconfiguration would be very appreciated. > > Thanks for your assistance, > > 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 exim@www1.ietf.org Fri Jul 4 16:09:58 2003 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 QAA06617 for ; Fri, 4 Jul 2003 16:09:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YWs5-0004Ez-Ne for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 16:09:30 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h64K9TUu016285 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 16:09:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YWs5-0004Ea-Jr for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 16:09:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06598 for ; Fri, 4 Jul 2003 16:09:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YWs3-0001r6-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 16:09:27 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YWs3-0001r3-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 16:09:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YWrd-000404-3V; Fri, 04 Jul 2003 16:09:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YWrH-0003zq-MY for manet@optimus.ietf.org; Fri, 04 Jul 2003 16:08: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 QAA06594 for ; Fri, 4 Jul 2003 16:08:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YWrF-0001qg-00 for manet@ietf.org; Fri, 04 Jul 2003 16:08:37 -0400 Received: from pickering.cc.nd.edu ([129.74.250.225]) by ietf-mx with esmtp (Exim 4.12) id 19YWrF-0001qO-00 for manet@ietf.org; Fri, 04 Jul 2003 16:08:37 -0400 Received: from sys.cse.ND.EDU (sys.cse.nd.edu [129.74.50.188]) by pickering.cc.nd.edu (Switch-3.0.4/Switch-3.0.0) with ESMTP id h64K86RR018208 for ; Fri, 4 Jul 2003 15:08:06 -0500 (EST) Received: by sys.cse.ND.EDU (Postfix, from userid 9403) id 8B3A5176BBE; Fri, 4 Jul 2003 15:09:46 -0500 (EST) Date: Fri, 4 Jul 2003 15:09:46 -0500 From: Surendar Chandra To: manet@ietf.org Message-ID: <20030704200946.GA21173@sys.cse.nd.edu> Reply-To: surendar@nd.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-ND-MTA-Date: Fri, 04 Jul 2003 15:08:07 -0500 (EST) X-ND-Virus-Scan: engine v4.2.40; dat v4275 Subject: [manet] CFP: Trusted Internet Workshop (TIW03) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , We apologize if you received multiple copies of this Call for Papers. Please feel free to distribute it to those who might be interested. ================================+========================================== Second International Trusted Internet Workshop TIW 2003 Held in conjunction with Intl. Conference on High-Performance Computing 2003 December 17, 2003 Hyderabad, INDIA URLs: http://www.ee.iastate.edu/~gmani/tiw-2003 http://www.hipc.org Submission Deadline: August 15, 2003 For more information, please contact: Prof. Manimaran (gmani@iastate.edu) and Prof. Sivalingam (krishna@umbc.edu) ==============================++=========================================== SCOPE In recent years, there has been a tremendous push from both civil and military communities for next generation applications demanding Quality of Service (QoS), reliability, and security guarantees. The goal of Trusted Internet workshop is to provide a forum for researchers and practitioners to present and discuss their work and exchange ideas in the areas of Internet QoS, Internet Reliability, and Internet Security. To achieve this goal, this workshop solicits original, previously unpublished research contributions on (but not restricted to) the following subject categories of Trusted Internet: -- Internet QoS & VPN Design -- Content Distribution Networks -- Media Servers and Web Caching -- MPLS Networks & IP over WDM -- Denial of Service (DoS) & IP Traceback -- QoS/FT/Secure Routing and Multicasting -- QoS/FT/Security in Wireless, Mobile and Sensor Networks SUBMISSION INSTRUCTIONS All paper submissions will be handled electronically. Authors should prepare a PostScript or Portable Document Format (PDF) version of their paper. No other format will be accepted. By the submission deadline, please do the following: A. Send an Email with the title, authors and abstract to: Prof. Manimaran (gmani@iastate.edu) and Prof. Sivalingam (krishna@umbc.edu) B. Send the Final PDF/PS file by email to Prof. Krishna Sivalingam at krishna@umbc.edu Papers must meet the following restrictions: - The paper must be original material that has not been previously published nor is currently under review by another conference or journal. - Papers should be no longer than *8 pages* (two column is acceptable), in font no smaller than 10 points. These page limits include *all* material, i.e., figures, bibliography, etc. - The paper should fit properly on US Letter-sized paper (8.5x11 inches) - PostScript version 2 or later, or Portable Document Format (PDF) - Use only Computer Modern or standard Adobe printer fonts (i.e., Courier, Times, Roman, or Helvetica) - Other fonts may be used, but must be included in the PostScript/PDF file - The paper must be formatted for b/w printers and not color printers. All contributions will be refereed by the Program Committee. Each accepted paper must be presented at the workshop. Accepted papers will be available as part of the proceedings, at the workshop. IMPORTANT DATES --------------- * Submissions due: August 15, 2003 * Notification of acceptance: Sept. 15, 2003 * Final manuscript due: Sept. 30, 2003 * Workshop date: December 17, 2003 ORGANIZING COMMITTEE -------------------- GENERAL CO-CHAIRS ----------------- G. Manimaran Assistant Professor Dept. of ECpE Iowa State University Ames, IA 50011, USA Phone: 515 294 9175 Fax: 515 294 8432 Email: gmani@iastate.edu C. Siva Ram Murthy Professor Department of Computer Science IIT Chennai (formerly Madras) Chennai - 600 036, INDIA Email: murthy@iitm.ac.in TECHNICAL PROGRAM CHAIR ----------------------- Krishna Sivalingam Associate Professor Department of CSEE 1000 Hilltop Circle University of Maryland Baltimore County Baltimore, MD 21250 Email: krishna@cs.umbc.edu Phone: 1-410-455-3961 Fax: 1-410-455-3969 TECHNICAL PROGRAM COMMITTEE --------------------------- Abdelmadjid Bouabdallah, UTC, France Albert Banchs, NEC Europe, Germany Arul Sironmoney, Anna University, India Byrav Ramamurthy, University of Nebraska, USA Mohan Gurusamy, NUS, Singapore Padma Mundur, UMBC, USA Prasant Mohapatra, University of California, Davis, USA Sudebkumar Prasant Pal, IIT Kharagpur, India Surendar Chandra, Univ. of Notre Dame, USA Suresh Subramaniam, George Washington University, USA PUBLICITY CHAIR --------------- Surendar Chandra, Univ. of Notre Dame, USA ====================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 4 20:39:03 2003 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 UAA13604 for ; Fri, 4 Jul 2003 20:39:03 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Yb4S-0007n0-Vo for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 20:38:35 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h650cWZV029938 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 20:38:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Yb4S-0007mn-RD for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 20:38: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 UAA13584 for ; Fri, 4 Jul 2003 20:38:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Yb4Q-0004Sx-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 20:38:30 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Yb4Q-0004Su-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 20:38:30 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Yb3x-0007im-5u; Fri, 04 Jul 2003 20:38:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Yb3K-0007Xt-NT for manet@optimus.ietf.org; Fri, 04 Jul 2003 20:37:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13578 for ; Fri, 4 Jul 2003 20:37:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Yb3I-0004S8-00 for manet@ietf.org; Fri, 04 Jul 2003 20:37:20 -0400 Received: from [202.38.193.39] (helo=scutsv39.scut.edu.cn) by ietf-mx with esmtp (Exim 4.12) id 19Yb3G-0004Rl-00 for manet@ietf.org; Fri, 04 Jul 2003 20:37:19 -0400 Received: from scut.edu.cn (smtp.scut.edu.cn [202.38.193.34]) by scutsv39.scut.edu.cn (8.9.3/8.9.3) with ESMTP id IAA29307; Sat, 5 Jul 2003 08:29:49 +0800 (CST) Received: from cs7116 ([158.182.7.116]) (authenticated bits=0) by scut.edu.cn (8.12.7/8.12.7) with ESMTP id h650Tkps022830; Sat, 5 Jul 2003 08:29:48 +0800 Message-Id: <200307050029.h650Tkps022830@scut.edu.cn> From: "Jinglun Shi" To: "mobile-ip@sunroof.eng.sun.com" , "manet@ietf.org" X-mailer: Foxmail 4.2 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sat, 5 Jul 2003 8:34:3 +0800 Content-Transfer-Encoding: quoted-printable Subject: [manet] address the communication in the Anycast members Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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, all. Is there any paper for the communication between the anycast= members, how do they exchange their information? Best regards, =09=09=09=09 =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1Jinglun Shi =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1jlshi@scut.edu.cn =A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A1=A12003-07-05 =3D=3D=3D=3D=3D=3D=3D=3D Shi Jinglun Department of Computer Science Hong Kong Baptist University Kowloon Tong, Hong Kong Office: R726 Tel: (852) 3411-5964 jlshi@scut.edu.cn,jlshi@comp.hkbu.edu.hk _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 4 20:40:38 2003 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 UAA13765 for ; Fri, 4 Jul 2003 20:40:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Yb60-0008EV-Hp for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 20:40:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h650e80G031638 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 20:40:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Yb5z-0008EB-SZ for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 20:40:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA13686 for ; Fri, 4 Jul 2003 20:40:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Yb5x-0004Vt-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 20:40:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Yb5w-0004Vq-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 20:40:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Yb5v-00086q-82; Fri, 04 Jul 2003 20:40:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Yb5K-0007q9-El for manet@optimus.ietf.org; Fri, 04 Jul 2003 20:39: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 UAA13636 for ; Fri, 4 Jul 2003 20:39:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Yb5I-0004UN-00 for manet@ietf.org; Fri, 04 Jul 2003 20:39:24 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19Yb5G-0004TQ-00 for manet@ietf.org; Fri, 04 Jul 2003 20:39:23 -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 h650q5918171; Sat, 5 Jul 2003 09:52:05 +0900 (KST) Message-ID: <007701c3428d$abf79fa0$c470fe81@etri.re.kr> From: "Jaehoon Jeong" To: "Corson Scott" Cc: "MANET WG" References: <748C6D0A58C0F94CA63C198B6674697A01719DE0@ftmail.lab.flarion.com> Subject: Re: [manet] Agenda Presentation Request for upcoming Manet WG Mtg Date: Sat, 5 Jul 2003 09:37:53 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" 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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 TWVzc2FnZUhpLCBTY290dC4gDQpJIHdvdWxkIGxpa2UgdG8gcHJlc2VudCBhbmQgZGlzY3VzcyBt eSBuZXcgSS1EIGluIHRoaXMgbWVldGluZyBpbiA1IG1pbnV0ZXMsIGlmIHBvc3NpYmxlLiANCiAg IDxBZCBIb2MgSVAgQWRkcmVzcyBBdXRvY29uZmlndXJhdGlvbj4gDQogICBodHRwOi8vd3d3Lmll dGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1qZW9uZy1hZGhvYy1pcC1hZGRyLWF1dG9jb25m LTAwLnR4dCANCg0KVGhhbmtzLiANCi9KYWVob29uIA0KDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3Nh Z2UgLS0tLS0gDQpGcm9tOiBDb3Jzb24gU2NvdHQgDQpUbzogJ21hbmV0QGlldGYub3JnJyANClNl bnQ6IFRodXJzZGF5LCBKdWx5IDAzLCAyMDAzIDM6MDUgQU0NClN1YmplY3Q6IFttYW5ldF0gQWdl bmRhIFByZXNlbnRhdGlvbiBSZXF1ZXN0IGZvciB1cGNvbWluZyBNYW5ldCBXRyBNdGcNCg0KDQpB bnlvbmUgd2lzaGluZyB0byBwcmVzZW50IGF0IHRoZSB1cGNvbWluZyBtdGcgaW4gQXVzdHJpYSwg cGxlYXNlIGxldCBtZSBrbm93Lg0KDQpUaHgsICBTY290dA== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 4 21:02:55 2003 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 VAA14264 for ; Fri, 4 Jul 2003 21:02:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YbRb-0001UK-A8 for manet-archive@odin.ietf.org; Fri, 04 Jul 2003 21:02:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6512RvU005716 for manet-archive@odin.ietf.org; Fri, 4 Jul 2003 21:02:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YbRb-0001U7-7K for manet-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 21: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 VAA14237 for ; Fri, 4 Jul 2003 21:02:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YbRY-0004rS-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 21:02:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YbRY-0004rP-00 for manet-web-archive@ietf.org; Fri, 04 Jul 2003 21:02:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YbRB-0001NO-PP; Fri, 04 Jul 2003 21: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 19YbQf-0001N7-Po for manet@optimus.ietf.org; Fri, 04 Jul 2003 21:01: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 VAA14221 for ; Fri, 4 Jul 2003 21:01:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YbQd-0004qa-00 for manet@ietf.org; Fri, 04 Jul 2003 21:01:27 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19YbQc-0004qE-00 for manet@ietf.org; Fri, 04 Jul 2003 21:01:26 -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 h651E5918327; Sat, 5 Jul 2003 10:14:06 +0900 (KST) Message-ID: <009101c34290$bf613ad0$c470fe81@etri.re.kr> From: "Jaehoon Jeong" To: "Jean-Marie ORSET" Cc: "MANET WG" References: <9E664A0522ABD711827B00D0B7A8AC4A373891@cms3.etri.re.kr> <20030704110130.0b71f038.jean-marie.orset@int-evry.fr> Subject: Re: [Re] [manet] Re: Ad Hoc IP Address Autoconfiguration Date: Sat, 5 Jul 2003 09:59:53 +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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 SGksIEplYW4tTWFyaWUuDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQpGcm9tOiAi SmVhbi1NYXJpZSBPUlNFVCIgPGplYW4tbWFyaWUub3JzZXRAaW50LWV2cnkuZnI+DQpUbzogPHBh dWxAZXRyaS5yZS5rcj4NClNlbnQ6IEZyaWRheSwgSnVseSAwNCwgMjAwMyA2OjAxIFBNDQpTdWJq ZWN0OiBSZTogW1JlXSBbbWFuZXRdIFJlOiBBZCBIb2MgSVAgQWRkcmVzcyBBdXRvY29uZmlndXJh dGlvbg0KDQoNCj4gDQo+IExlIEZyaSwgNCBKdWwgMjAwMyAxNzoxNDozOSArMDkwMCANCj4gcGF1 bEBldHJpLnJlLmtyIGEg6WNyaXQ6DQo+IA0KPiANCj4gPiAxKURvZXNuJ3QgVGhlIGZhY3QgdGhh dCBhIG5vZGUgY2hvb3NlcyByYW5kb21seSBpdHMgYWRkcmVzcyBhZmZlY3QgdGhlIA0KPiA+IGhp ZXJhcmNoaWNhbCBhc3BlY3Qgb2YgSVAgYWRyZXNzaW5nPyANCj4gPiBCZWNhdXNlIHRoZXJlIGlz IG5vIG1vcmUgcmVsYXRpb24gYmV0d2VlbiB0aGUgaXAgYWRkcmVzcyBvZiBhIG5vZGUgYW5kIHRo ZSANCj4gPiBuZXR3b3JrIGl0IGJlbG9uZ3MgdG8uIA0KPiA+IA0KPiA+ICAgLT4gTm8sIG15IGFk ZHJlc3Npbmcgc2NoZW1lIGlzIG9ubHkgZm9yIGFkIGhvYyBuZXR3b3JrLCANCj4gPiAgICAgICB1 c2luZyAvNjQgSVBWNl9NQU5FVF9QUkVGSVgsIHdoaWNoIHVzdWFsbHkgaGFzIGZsYXQgYXJjaGl0 ZWN0dXJlLg0KPiANCj4gSW4gZmFjdCwgSSB3YW50ZWQgdG8gc2F5IHdpdGhpbiB0aGUgc2FtZSBh ZCBob2MgbmV0d29yay4NCj4gQnJvYWRjYXN0cyBpbiBBZCBIb2MgbmV0d29ya3MgYXJlIHF1aWV0 IGV4cGVuc2l2ZSBhbmQgd2UgY291bGQgY29uc2lkZXIgdGhhdCB0aGVyZSBzaG91bGQgc29tZXRp bWVzIGJlIHNldmVyYWwgc3VibmV0DQo+IGZvcm1pbmcgdGhlIGFkIGhvYyBuZXR3b3JrLiBUaGVu IGEgbm9kZSBjb3VsZCB3aXNoLCBmb3IgYW4gdW5zcGVjaWZpZWQgcmVhc29uLCB0byBicm9hZGNh c3QganVzdCB0byBhIGxpbWl0ZWQgc3VibmV0Lg0KPiBCdXQgSSBrbm93IHRoYXQgYWxsb2NhdGlv biBvZiBJUCBhZGRyZXNzIHdoaWxlIHRha2luZyBpbnRvIGFjY291bnQgc29tZSBwb3NzaWJsZSBz dWJuZXRzIHdvdWxzIGJlIHZlcnkgZGlmZmljdWx0Lg0KPiANCg0KVGhlIHN1Ym5ldCBpbiBNQU5F VCBpcyB2ZXJ5IGRpZmZpY3VsdCBwcm9ibGVtLCBJIHRoaW5rLg0KSWYgYSBncm91cCBvZiBtb2Jp bGUgbm9kZXMgbW92ZSB0b2dldGhlciwgdGhlIHN1Ym5ldCBpbiBNQU5FVCBtYXkgYmUgcG9zc2li bGUuDQoNCj4gDQo+IA0KPiA+IDIpIFdoYXQgaGFwcGVucyB3aGVuIDIgbmV0d29ya3Mgb2YgMTAw IG5vZGVzIG9yIG1vcmUsIGVhY2ggb25lLCBtZXJnZSB0bw0KPiA+IGZvcm0gYSANCj4gPiBuZXcg bmV0d29yaz8gDQo+ID4gSSBzdXBwb3NlIHRoYXQgYWxsIG5vZGVzIG9mIGJvdGggbmV0d29ya3Mg bXVzdCByZWNvbmZpZ3VyZSB0aGVpciBJUA0KPiA+IGFkZHJlc3MuIA0KPiA+IFRoaXMgd2lsbCBy ZXN1bHQgaW4gYSBsb3Qgb2YgY29udHJvbCB0cmFmZmljIGluIHRoZSBib3RoPw0KPiANCj4gPiAg IC0+IFRoZXJlIGlzIG5vIGNvbnRyb2wgdHJhZmZpYydzIHN0b3JtLCANCj4gPiAgICAgICBiZWNh dXNlIHRoZSBjaGVjayBvZiBhZGRyZXNzIGR1cGxpY2F0aW9uIGlzIHBlcmZvcm1lZCBpbiByb3V0 aW5nDQo+ID4gbGV2ZWwuDQo+IA0KPiBNaGgsIEkgc3VwcG9zZSB0aGF0IGkgYW55IGV2ZW50IHdl IGNhbiBub3QgcHJldmVudCBpbmNyZWFzZSBvZiB0aGUgb3ZlcmhlYWQuDQo+IA0KDQpZZWFoLCB0 aGVyZSBtYXkgYmUgc29tZSBvdmVyaGVhZCwgbm90IG11Y2ggb3ZlcmhlYWQuDQpJZiB0aGVyZSBh cmUgbWFueSBhZGRyZXNzIGR1cGxpY2F0aW9ucywgdGhlcmUgd2lsbCBiZSBtdWNoIGNvbnRyb2wg dHJhZmZpYy4NCg0KPiANCj4gDQo+ID4gMykgRm9yIHNlY3VyaXR5IHJlYXNvbnMsIGNvdWxkbid0 IHdlIGNvbnNpZGVyIHRoYXQgYSBub2RlIGpvaW4gYSBwdWJsaWMga2V5DQo+ID4gd2l0aCANCj4g PiBpdHMgcmVxdWVzdDoNCj4gPiANCj4gPiAgIC0+ICBPZiBjb3Vyc2Ugbm90LCB3ZSBjYW4gY29u c2lkZXIgaXQuDQo+ID4gIA0KPiA+IA0KPiA+ICAgICBhKSBUaGUgbm9kZSBzZW5kcyBBUkVRIGFu ZCBqb2luIGl0cyBwdWJsaWMga2V5IA0KPiA+ICAgICBiKSBUaGUgZGlyZWN0IG5laWdoYm91cnMg c2VuZCBoaW0gYSAiY2hhbGxlbmdlIiwgaSBtZWFuIGEgbm9uY2UNCj4gPiBjaXBoZXJlZCB3aXRo IHRoZSANCj4gPiBwdWJsaWMga2V5IGF0IHdpdGNoIHRoZSBub2RlIHNob3VsZCBhbnN3ZXIgYnkg aW5jcmVhc2luZyBpdCwgaW4gb3JkZXIgdG8NCj4gPiB2ZXJpZnkgDQo+ID4gdGhhdCBpdCBpcyBy ZWFsbHkgdGhlIG93bmVyIG9mIHRoZSBrZXkgDQo+ID4gICAgIGMpIFRoZSBub2RlIGFuc3dlcnMg YW5kIG9ubHkgaWYgdGhpcyBpcyBjb3JyZWN0LCB0aGUgbmVpZ2hib3Vycw0KPiA+IGFjY2VwdCB0 byBmb3J3YXJkIA0KPiA+IHRoZSByZXF1ZXN0LiBpZiBub3QsIHRoZSByZXF1ZXN0IGlzIGRpc2Nh cmRlZC4NCj4gPiBUaHVzLCB3ZSBjb3VsZCBhdm9pZCB0aGUgRGVuaWFsIG9mIHNlcnZpY2UgYXR0 YWNrIHdoaWNoIHdvdWxkIGNvbnNpc3QgdG8NCj4gPiBhbHdheXMgDQo+ID4gc2VuZCBBUkVRIHRo cm91Z2ggdGhlIG5ldHdvcmssIGluIG9yZGVyIHRvIGZsb29kIGl0IHdpdGggY29udHJvbCBwYWNr ZXRzLiANCj4gPiBNb3Jlb3ZlciB0aGUgcHVibGljIGtleSBjb3VsZCB0aGVuIGJlIHVzZWQgdG8g c2lnbiB0aGUgbWVzc2FnZXMuDQo+ID4gDQo+ID4gDQo+ID4gICAgLT4gR29vZCBzdWdnZXN0aW9u ISANCj4gPiAgICAgICAgSSB0aGluayB5b3VyIGlkZWEgaXMgYSB1c2VmdWwgd2F5IG9mIGFubm91 bmNpbmcgaXRzIG93biBwdWJsaWMga2V5DQo+ID4gdG8gb3RoZXIgbm9kZXMuDQo+ID4gICAgICAg IEluIG15IGRyYWZ0LCBXRUFLIERBRCBuZWVkcyBhIGtleSBmb3IgZGlmZmVyZW50aWF0aW5nIGR1 cGxpY2F0ZQ0KPiA+IGFkZHJlc3NzZXMuDQo+ID4gICAgICAgIFRoZSBrZXkgY2FuIGJlIGEgcHVi bGljIGtleSBvZiB0aGUgbm9kZS4NCj4gPiAgICAgICAgRHVyaW5nIFNUUk9ORyBEQUQsIHRoZSBh bm5vdWNlbWVudCBvZiBwdWJsaWMga2V5IGNhbiBiZSB1c2VmdWwgDQo+ID4gICAgICAgIGluIHRo ZSBhdXRoZW50aWNhdGlvbiBhbmQgZGlnaXRhbCBzaWduYXR1cmUuDQo+IA0KPiBUaGFua3MsIGJ1 dCB1bmZvcnR1bmF0ZWx5LCB3ZSB3aWxsIGhhdmUgdGhlbiB0byBzb2x2ZSB0aGUgcHJvYmxlbSBv ZiB2ZXJ5IGV4cGVuc2l2ZSBjb3N0IG9mIHB1YmxpYyBrZXkgdGVjaG5pcXVlcy4NCj4gYnV0IHRo aXMgaXMgYW5vdGhlciBwcm9ibGVtLi4uDQo+IA0KDQpJIGFncmVlIHdpdGggeW91IHRoYXQgdGhl IHB1YmxpYyBjcnlwdG9ncmFwaHkgaXMgdmVyeSBleHBlbnNpdmUsIGVzcGVjaWFsbHkgaW4gTUFO RVQuDQpJbiBteSBzY2hlbWUsIGEga2V5IGlzIHVzZWQgZm9yIGlkZW50aWZ5aW5nIHRoZSBhZGRy ZXNzIGR1cGxpY2F0aW9uLiANClNvLCBrZXkncyB1bmlxdWVuZXNzIGlzIGltcG9ydGFudC4NCklu IG9yZGVyIHRvIGd1YXJhbnRlZSB0aGUgdW5pcXVlbmVzcyBvZiBwdWJsaWMga2V5LCANCldlIHNo b3VsZCB1c2UgYSBjZXJ0aWZpY2F0ZSBmb3IgYSBwdWJsaWMga2V5Pw0KSG93IGFib3V0Pw0KDQov SmFlaG9vbg0KDQo+IENvcmRpYWxseSwgSmVhbi1NYXJpZSBPcnNldA0KPiA= _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 7 05:08:33 2003 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 FAA17907 for ; Mon, 7 Jul 2003 05:08:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZRyf-00078P-Cs for manet-archive@odin.ietf.org; Mon, 07 Jul 2003 05:08:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67985Ju027402 for manet-archive@odin.ietf.org; Mon, 7 Jul 2003 05:08:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZRyf-00077d-0J for manet-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 05:08: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 FAA17841 for ; Mon, 7 Jul 2003 05:06:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZRxb-0002Pj-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 05:06:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZRxa-0002Pe-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 05:06:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZRwg-0006i3-FB; Mon, 07 Jul 2003 05:06:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZRvv-0006hl-HP for manet@optimus.ietf.org; Mon, 07 Jul 2003 05:05: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 FAA17826 for ; Mon, 7 Jul 2003 05:05:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZRvp-0002PF-00 for manet@ietf.org; Mon, 07 Jul 2003 05:05:09 -0400 Received: from ms01.net.ie.niigata-u.ac.jp ([133.35.156.1] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19ZRvo-0002PB-00 for manet@ietf.org; Mon, 07 Jul 2003 05:05:09 -0400 Received: from msq114 (ms02.net.ie.niigata-u.ac.jp [133.35.156.2]) by ms01.net.ie.niigata-u.ac.jp (Postfix) with SMTP id ACC8911E2F; Mon, 7 Jul 2003 18:04:54 +0900 (JST) Date: Mon, 7 Jul 2003 18:18:54 +0900 From: skame To: manet@ietf.org Cc: syoshida@net.ie.niigata-u.ac.jp Message-Id: <20030707181854.4e7492c8.skame@net.ie.niigata-u.ac.jp> X-Mailer: Sylpheed version 0.8.5 (GTK+ 1.2.10; i386-vine-linux) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] About changing bandwidth Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 want to know the way of changing bandwidth. The defalut bandwidth in ns2 is 2[Mb/s]. I suppose 802.11b in maclayer. Now bandwidth in 802.11b is 11[Mb/s]. So I want to change the bandwidth from 2[Mb/s] to 11[Mb/s]. Please tell me how to change bandwidth. Thank you. skame _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 7 06:01:28 2003 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 GAA19289 for ; Mon, 7 Jul 2003 06:01:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZSns-0000rz-3J for manet-archive@odin.ietf.org; Mon, 07 Jul 2003 06:01:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67A107k003331 for manet-archive@odin.ietf.org; Mon, 7 Jul 2003 06:01:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZSnr-0000re-LG for manet-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 06:00: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 GAA19260 for ; Mon, 7 Jul 2003 06:00:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZSnn-0002ms-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 06:00:56 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZSnn-0002mp-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 06:00:55 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZSmw-0000gq-LS; Mon, 07 Jul 2003 06:00:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZSmn-0000fy-Ox for manet@optimus.ietf.org; Mon, 07 Jul 2003 05:59: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 FAA19205 for ; Mon, 7 Jul 2003 05:59:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZSmk-0002lj-00 for manet@ietf.org; Mon, 07 Jul 2003 05:59:50 -0400 Received: from rover.inria.fr ([138.96.88.61] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19ZSmj-0002lg-00 for manet@ietf.org; Mon, 07 Jul 2003 05:59:49 -0400 Received: from sophia.inria.fr (localhost [127.0.0.1]) by rover.inria.fr (8.12.8/8.12.5) with ESMTP id h679xjbs010805; Mon, 7 Jul 2003 11:59:46 +0200 Message-ID: <3F094491.5060003@sophia.inria.fr> Date: Mon, 07 Jul 2003 11:59:45 +0200 From: Fethi Filali Organization: INRIA Sophia-Antipolis (http://www.inria.fr) User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: fr-FR, en MIME-Version: 1.0 To: skame CC: manet@ietf.org, syoshida@net.ie.niigata-u.ac.jp Subject: Re: [manet] About changing bandwidth References: <20030707181854.4e7492c8.skame@net.ie.niigata-u.ac.jp> 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 skmae, The default rate in ns2 seems to be 1Mb. See file ns-2.26/tcl/lan/mac.tcl , u can find the line: Mac/802_11 set dataRate_ 1Mb ;# both control and data pkts the tcl variable dataRate_ is binded to the c++ variable dataRate_ in the mac-802_11.cc file you can change the default value in mac.tcl and recompiling ns. Fethi. skame wrote: > Hi,all. > > I want to know the way of changing bandwidth. > The defalut bandwidth in ns2 is 2[Mb/s]. > I suppose 802.11b in maclayer. > Now bandwidth in 802.11b is 11[Mb/s]. > So I want to change the bandwidth from 2[Mb/s] to 11[Mb/s]. > Please tell me how to change bandwidth. > > Thank you. > skame > > _______________________________________________ > 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 Jul 7 07:02:23 2003 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 HAA20595 for ; Mon, 7 Jul 2003 07:02:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZTks-00039F-1o for manet-archive@odin.ietf.org; Mon, 07 Jul 2003 07:01:58 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67B1wVL012095 for manet-archive@odin.ietf.org; Mon, 7 Jul 2003 07:01:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZTkr-000390-Tt for manet-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 07:01: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 HAA20580 for ; Mon, 7 Jul 2003 07:01:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZTkn-0003BA-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 07:01:53 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZTkn-0003B7-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 07:01:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZTjx-0002wd-CW; Mon, 07 Jul 2003 07:01:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZTjl-0002w7-L8 for manet@optimus.ietf.org; Mon, 07 Jul 2003 07:00: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 HAA20540 for ; Mon, 7 Jul 2003 07:00:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZTjh-0003A4-00 for manet@ietf.org; Mon, 07 Jul 2003 07:00:45 -0400 Received: from law15-f47.law15.hotmail.com ([64.4.23.47] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19ZTjg-0003A0-00 for manet@ietf.org; Mon, 07 Jul 2003 07:00:45 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 7 Jul 2003 04:00:16 -0700 Received: from 203.129.220.119 by lw15fd.law15.hotmail.msn.com with HTTP; Mon, 07 Jul 2003 11:00:15 GMT X-Originating-IP: [203.129.220.119] X-Originating-Email: [karun8880@hotmail.com] From: "Karun Verma" To: manet@ietf.org Date: Mon, 07 Jul 2003 16:30:15 +0530 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 07 Jul 2003 11:00:16.0148 (UTC) FILETIME=[F27AF540:01C34476] 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 have some information on SLURP and GLS in Wireless Adhoc networks. Please provide me some links.

Karun  

See you


Watch Hallmark. Enjoy cool movies. Win hot prizes! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 7 07:22:30 2003 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 HAA21059 for ; Mon, 7 Jul 2003 07:22:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZU3d-0004D9-3Q for manet-archive@odin.ietf.org; Mon, 07 Jul 2003 07:22:00 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67BLLoP016183 for manet-archive@odin.ietf.org; Mon, 7 Jul 2003 07:21:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZU3c-0004Cw-TJ for manet-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 07:21: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 HAA20998 for ; Mon, 7 Jul 2003 07:19:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZU2J-0003JA-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 07:19:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZU2I-0003J7-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 07:19:58 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZU1O-0003sh-0c; Mon, 07 Jul 2003 07:19:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZTzF-0003rP-0J for manet@optimus.ietf.org; Mon, 07 Jul 2003 07: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 HAA20839 for ; Mon, 7 Jul 2003 07:16:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZTzE-0003Gw-00 for manet@ietf.org; Mon, 07 Jul 2003 07:16:48 -0400 Received: from inet-tsb.toshiba.co.jp ([202.33.96.40]) by ietf-mx with esmtp (Exim 4.12) id 19ZTzD-0003Gj-00 for manet@ietf.org; Mon, 07 Jul 2003 07:16:47 -0400 Received: from tsb-wall.toshiba.co.jp ([133.199.160.134]) by inet-tsb.toshiba.co.jp with ESMTP id h67BFNVj005294; Mon, 7 Jul 2003 20:15:23 +0900 (JST) Received: (from root@localhost) by tsb-wall.toshiba.co.jp id h67BFNDK010406; Mon, 7 Jul 2003 20:15:23 +0900 (JST) Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id WAA10405 ; Mon, 7 Jul 2003 20:15:23 +0900 Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp id UAA17829; Mon, 7 Jul 2003 20:15:22 +0900 (JST) Received: from isl.rdc.toshiba.co.jp by toshiba.co.jp id UAA04834; Mon, 7 Jul 2003 20:15:22 +0900 (JST) Received: from localhost (inoue@flowerpark [133.196.16.25]) by isl.rdc.toshiba.co.jp (8.11.7/8.11.6/1.4) with ESMTP id h67BFLb26338; Mon, 7 Jul 2003 20:15:21 +0900 (JST) To: nemo@nal.motlabs.com, manet@ietf.org, mobile-ip@sunroof.eng.sun.com, pana@research.telcordia.com Cc: inoue@isl.rdc.toshiba.co.jp In-Reply-To: Your message of "Mon, 12 May 2003 20:42:52 +0900" <20030512204252N.inoue@isl.rdc.toshiba.co.jp> References: <20030512204252N.inoue@isl.rdc.toshiba.co.jp> X-Mailer: Mew version 1.93 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20030707201521A.inoue@isl.rdc.toshiba.co.jp> Date: Mon, 07 Jul 2003 20:15:21 +0900 From: Atsushi Inoue X-Dispatcher: imput version 980905(IM100) Lines: 84 Content-Transfer-Encoding: 7bit Subject: [manet] CFP:: First International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2004) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit (Apologies if you receive multiple copies) CALL FOR PAPERS =============== First International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2004) January 8 and 9, 2004 NTT DoCoMo R&D Center, Yokosuka Rsearch Park, Yokosuka, JAPAN http://www.ipsj.or.jp/sig/mbl/icmu2004/ Deadline for submissions: August 1 2003 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Co-sponsored by IPSJ SIG-MBL (Informaiton Processing Society of Japan, Special Interest Group of Mobile Computing and Ubiquitous Networking) and IPSJ SG-BCC (Study Group of Broadcast Communicaiton and Computing) Scope: ~~~~~~ Mobile computing aims at ubiquitous user access to computer application. To make it possible, networking technology which enables Internet access anytime and everywhere, i.e. ubiquitous networking is necessary. It is obvious that with the accelerating trends towards mobile networks, ad-hoc networks, and wireless networks, mobile computing and ubiquitous networking will play an important role in future network. This conference is aimed at providing researchers and practitioners in this hot research area a forum for discussion and collaboration. Authors are invited to submit papers addressing, but not limited to, the following topics: - Applications and services for mobile computing - Network architectures, protocols, or service models for ubiquitous networking - Network management for ubiquitous networking - Data management for mobile computing - Security in mobile computing and ubiquitous networking - Wireless and mobile communications - Nomadic computing - Ad-hoc networks - Mobile Internetworking - Performance evaluation for mobile computing and ubiquitous networking systems - Broadcast communication Submission Instructions: ~~~~~~~~~~~~~~~~~~~~~~~~ Papers are solicited as full papers of no more than 6 pages, each of which will be subject to a full review process. Submission should already follow the author guidelines as specified in the web site below. An electronic, PDF-based submission of papers is mandatory. Please check Submission Guideline (http://www.ipsj.or.jp/sig/mbl/icmu2004/guide.html) for further submission instructions. Important Dates: ~~~~~~~~~~~~~~~~ - Deadline for submissions August 1, 2003 - Notification of acceptance October 1, 2003 - Camera ready due November 1, 2003 - Conference January 8-9, 2004 Location and Date: ~~~~~~~~~~~~~~~~~~ The location of the NTT DoCoMo R&D Center is in the heart of Yokosuka Research Park(YRP) where a lot of wireless communication related research institutes are established. YRP is really the heart of wireless communications research in Japan. Japanese old city Kamakura, a famous historic city, is 30 minutes by train. Beginning of the year is one of the best seasons for visiting Japan. You can also get PDF version of Call for Papers from http://www.ipsj.or.jp/sig/mbl/icmu2004/cfp-icmu2004.pdf Atsushi Inoue # Phone: +81-44-549-2065 Communication Platform Lab. # Fax: +81-44-520-1806 TOSHIBA R&D Center # inoue@isl.rdc.toshiba.co.jp _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 7 12:09:39 2003 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 MAA01384 for ; Mon, 7 Jul 2003 12:09:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZYYB-0001ke-Vl for manet-archive@odin.ietf.org; Mon, 07 Jul 2003 12:09:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67G9Bo6006726 for manet-archive@odin.ietf.org; Mon, 7 Jul 2003 12:09:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZYYB-0001kP-S7 for manet-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 12:09: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 MAA01371 for ; Mon, 7 Jul 2003 12:09:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZYYA-00062X-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 12:09:10 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZYY9-00062U-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 12: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 19ZYY0-0001j7-Th; Mon, 07 Jul 2003 12:09:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZYXt-0001iq-PE for manet@optimus.ietf.org; Mon, 07 Jul 2003 12: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 MAA01366 for ; Mon, 7 Jul 2003 12:08:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZYXs-00062Q-00 for manet@ietf.org; Mon, 07 Jul 2003 12:08:52 -0400 Received: from smtpproxy1.mitre.org ([192.160.51.75]) by ietf-mx with esmtp (Exim 4.12) id 19ZYXr-00062N-00 for manet@ietf.org; Mon, 07 Jul 2003 12:08:51 -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 h67G8lEx019709 for ; Mon, 7 Jul 2003 12:08:48 -0400 (EDT) Received: from linus.mitre.org (linus.mitre.org [129.83.10.1]) by smtpsrv1.mitre.org (8.12.9/8.12.8) with ESMTP id h67G8kpj004591 for ; Mon, 7 Jul 2003 12:08:46 -0400 (EDT) Received: from faron.mitre.org (faron.mitre.org [129.83.10.2]) by linus.mitre.org (8.12.8p1/8.12.8) with ESMTP id h67G8kA4008802 for ; Mon, 7 Jul 2003 12:08:46 -0400 (EDT) Message-Id: <200307071608.h67G8kA4008802@linus.mitre.org> To: manet@ietf.org X-Mailer: nmh 1.0.4 From: Vipin Swarup Reply-to: swarup@mitre.org Date: Mon, 07 Jul 2003 12:08:46 -0400 Subject: [manet] Final CFP: Security of Ad Hoc and Sensor Networks Workshop Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Final Call for Papers (Submissions due: July 18, 2003) [ Our apologies if you receive multiple copies of this CFP ] ______________________________________________________________________ 2003 ACM Workshop on Security of Ad Hoc and Sensor Networks (SASN 2003) To be held in conjunction with the 10th ACM Conference on Computer and Communications Security October 31, 2003, George Mason University, Fairfax, VA Sponsored by ACM SIGSAC http://www.cs.gmu.edu/sasn CALL FOR PAPERS Ad hoc and sensor networks are expected to become an integral part of the future computing landscape. However, these networks introduce new security challenges due to their dynamic topology, severe resource constraints, and absence of a trusted infrastructure. This workshop seeks submissions from academia and industry presenting novel research on all aspects of security for ad hoc and sensor networks, as well as experimental studies of fielded systems. Submission of papers based on work-in-progress is encouraged. Topics of interest include, but are not limited to, the following as they relate to wireless networks, mobile ad hoc networks, or sensor networks: * Security under resource constraints, e.g., energy, bandwidth, memory, and computation constraints * Performance and security tradeoffs * Secure roaming across administrative domains * Key management * Cryptographic protocols * Authentication and access control * Trust establishment, negotiation, and management * Intrusion detection and tolerance * Secure location services * Privacy and anonymity * Secure routing * Secure MAC protocols * Denial of service * Prevention of traffic analysis Submission Instructions: Submitted papers must not substantially overlap with papers that have been published or that are simultaneously submitted to a journal or a conference with proceedings. Papers should be at most 15 pages excluding the bibliography and well-marked appendices, using at least 11-point font and reasonable margins on US letter-size paper (8.5 inch x 11 inch). Committee members are not required to read the appendices, and so submissions should be intelligible without them. Each submission should start with the title, abstract, and names and contact information of authors. The introduction should give background and summarize the contributions of the paper at a level appropriate for a non-specialist reader. To submit a paper, send to swarup@mitre.org a plain ASCII text email containing the title and abstract of your paper, the authors' names, email and postal addresses, phone and fax numbers, and identification of the contact author. To the same message, attach your submission (as a MIME attachment) in PDF or portable postscript format. Do NOT send files formatted for word processing packages (e.g., Microsoft Word or WordPerfect files). Papers must be received by the deadline of July 18, 2003. Conference proceedings will be published by the ACM and made available at the workshop. Authors of accepted papers must guarantee that their paper will be presented at the workshop. Important Dates: Paper submissions due: July 18, 2003 Acceptance notifications: August 29, 2003 Camera-ready papers due: September 26, 2003 SASN Workshop: October 31, 2003 Program Co-Chairs: Vipin Swarup, MITRE (swarup@mitre.org) Sanjeev Setia, George Mason University (setia@gmu.edu) Program Committee: Virgil Gligor, University of Maryland at College Park Zygmunt Haas, Cornell University Jean-Pierre Hubaux, Swiss Federal Institute of Technology, Lausanne Brian Levine, University of Massachusetts at Amherst Songwu Lu, University of California at Los Angeles Doug Maughan, DARPA Luigi Mancini, University of Rome Adrian Perrig, Carnegie Mellon University Radha Poovendran, University of Washington at Seattle Emilia Rosti, University of Milan David Wagner, University of California at Berkeley For further information, contact: Vipin Swarup MITRE, Mail Stop W424 7515 Colshire Drive McLean, VA 22102 USA Phone: +1 703 883 7625 Fax: +1 703 883 1397 Email: swarup@mitre.org ______________________________________________________________________ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 7 12:14:05 2003 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 MAA01612 for ; Mon, 7 Jul 2003 12:14:05 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZYcP-0002ST-Dn for manet-archive@odin.ietf.org; Mon, 07 Jul 2003 12:13:38 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67GDX1o009444 for manet-archive@odin.ietf.org; Mon, 7 Jul 2003 12:13:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZYcP-0002SF-9v for manet-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 12:13: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 MAA01566 for ; Mon, 7 Jul 2003 12:13:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZYcN-00066M-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 12:13:31 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZYcN-00066J-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 12:13:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZYbt-0002Ce-Fe; Mon, 07 Jul 2003 12: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 19ZYb1-00029W-7t for manet@optimus.ietf.org; Mon, 07 Jul 2003 12:12: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 MAA01526 for ; Mon, 7 Jul 2003 12:12:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZYaz-00065O-00 for manet@ietf.org; Mon, 07 Jul 2003 12:12:05 -0400 Received: from angelo.kcl.ac.uk ([137.73.66.5]) by ietf-mx with esmtp (Exim 4.12) id 19ZYay-00065L-00 for manet@ietf.org; Mon, 07 Jul 2003 12:12:04 -0400 Received: from MONA (EE014.eee.kcl.ac.uk [137.73.10.115]) by angelo.kcl.ac.uk with ESMTP id h67GBnJT015463; Mon, 7 Jul 2003 17:11:49 +0100 (BST) Message-ID: <00e901c344a3$ea2272b0$730a4989@MONA> From: "Mona" To: Cc: Subject: Re: [manet] About changing bandwidth Date: Mon, 7 Jul 2003 17:22:07 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E6_01C344AC.4B0442E0" 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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_00E6_01C344AC.4B0442E0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Dear Fathi, I have tried to change this value in ns2. However it seems if I changed = it, all the wireless link bandwidths will change. I want to have different wireless link bandwidths between mobile nodes. = Do you have any idea how I can make this scenario?=20 Any comment would be appreciated. Kind Regards, Mona Date: Mon, 07 Jul 2003 11:59:45 +0200 From: Fethi Filali Organization: INRIA Sophia-Antipolis (http://www.inria.fr) To: skame CC: manet@ietf.org, syoshida@net.ie.niigata-u.ac.jp Subject: Re: [manet] About changing bandwidth skmae, The default rate in ns2 seems to be 1Mb. See file ns-2.26/tcl/lan/mac.tcl , u can find the line: Mac/802_11 set dataRate_ 1Mb ;# both control and data pkts the tcl variable dataRate_ is binded to the c++ variable dataRate_ in=20 the mac-802_11.cc file you can change the default value in mac.tcl and recompiling ns. Fethi. skame wrote: > Hi,all. >=20 > I want to know the way of changing bandwidth. > The defalut bandwidth in ns2 is 2[Mb/s]. > I suppose 802.11b in maclayer. > Now bandwidth in 802.11b is 11[Mb/s]. > So I want to change the bandwidth from 2[Mb/s] to 11[Mb/s]. > Please tell me how to change bandwidth. >=20 > Thank you. > skame >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 ----------------------------------------------------------- Mona Ghassemian, PhD student Centre for Telecommunications Research Kings College London Strand, London WC2R 2LS UK TEL: +44 20 7848 2596 FAX: +44 20 7848 2664 Mona.Ghassemian@kcl.ac.uk Tehran@ieee.org ------=_NextPart_000_00E6_01C344AC.4B0442E0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Dear Fathi,
 
I have tried to change this value in ns2. However it = seems if=20 I changed it, all the wireless link bandwidths will change.
I want to have different wireless link bandwidths = between=20 mobile nodes. Do you have any idea how I can make this scenario? =
Any comment would be appreciated.
 
Kind Regards, Mona
 
 
Date: Mon, 07 Jul 2003 11:59:45 = +0200
From:=20 Fethi Filali <Fethi.Filali@sophia.inria.fr>
Organization:=20 INRIA Sophia-Antipolis (http://www.inria.fr)
To: skame = <skame@net.ie.niigata-u.ac.jp>
CC: manet@ietf.org, syoshida@net.ie.niigata-u.ac.jp
Subject: Re:=20 [manet] About changing bandwidth

skmae,

The default rate = in ns2=20 seems to be 1Mb.

See file ns-2.26/tcl/lan/mac.tcl , u can find = the=20 line:

   Mac/802_11 set dataRate_ 1Mb   ;# = both=20 control and data pkts

the tcl variable dataRate_ is binded to the = c++=20 variable dataRate_ in
the mac-802_11.cc file

you can change = the=20 default value in mac.tcl and recompiling ns.

Fethi.

skame=20 wrote:
> Hi,all.
>
> I want to know the way of = changing=20 bandwidth.
> The defalut bandwidth in ns2 is 2[Mb/s].
> I = suppose=20 802.11b in maclayer.
> Now bandwidth in 802.11b is = 11[Mb/s].
> So I=20 want to change the bandwidth from 2[Mb/s] to 11[Mb/s].
> Please = tell me=20 how to change bandwidth.
>
> Thank you.
> = skame
>=20
> _______________________________________________
> manet = mailing=20 list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>




-----------------------------------------------------------
M= ona=20 Ghassemian, PhD student
Centre for Telecommunications = Research
Kings=20 College London
Strand, London WC2R 2LS
UK
TEL: +44 20 7848 = 2596
FAX:=20 +44 20 7848 2664
Mona.Ghassemian@kcl.ac.ukTehran@ieee.org
------=_NextPart_000_00E6_01C344AC.4B0442E0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 7 12:19:57 2003 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 MAA01862 for ; Mon, 7 Jul 2003 12:19:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZYi7-0002qA-P0 for manet-archive@odin.ietf.org; Mon, 07 Jul 2003 12:19:30 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67GJR7Z010915 for manet-archive@odin.ietf.org; Mon, 7 Jul 2003 12:19:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZYi7-0002py-Ls for manet-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 12:19: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 MAA01817 for ; Mon, 7 Jul 2003 12:19:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZYi6-0006Bh-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 12:19:26 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZYi5-0006Be-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 12:19:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZYhg-0002j5-L6; Mon, 07 Jul 2003 12:19:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZYhE-0002hF-Po for manet@optimus.ietf.org; Mon, 07 Jul 2003 12:18: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 MAA01772 for ; Mon, 7 Jul 2003 12:18:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZYhD-0006Ai-00 for manet@ietf.org; Mon, 07 Jul 2003 12:18:31 -0400 Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx with esmtp (Exim 4.12) id 19ZYhC-0006Aa-00 for manet@ietf.org; Mon, 07 Jul 2003 12:18:30 -0400 Received: from vivi.cc.vt.edu (IDENT:mirapoint@evil-vivi [10.1.1.12]) by lennier.cc.vt.edu (8.12.8/8.12.8) with ESMTP id h67GHiCT397647; Mon, 7 Jul 2003 12:17:44 -0400 (EDT) Received: from tom ([198.70.228.73]) by vivi.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BIS44296 (AUTH talin); Mon, 7 Jul 2003 12:17:41 -0400 (EDT) Message-ID: <003d01c344a3$50c435e0$2502a8c0@tom> From: "Tao Lin" To: "Mona" , Cc: References: <00e901c344a3$ea2272b0$730a4989@MONA> Subject: Re: [manet] About changing bandwidth Date: Mon, 7 Jul 2003 12:17:50 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003A_01C34481.C8B85760" 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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_003A_01C34481.C8B85760 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable You may set this value according to the end node IDs in ns2. In this = way, you can assign different bandwidths to different links. Tao Lin PhD Candidate ECE Dept. Virginia Tech ----- Original Message -----=20 From: Mona=20 To: Fethi.Filali@sophia.inria.fr=20 Cc: manet@ietf.org=20 Sent: Monday, July 07, 2003 12:22 PM Subject: Re: [manet] About changing bandwidth Dear Fathi, I have tried to change this value in ns2. However it seems if I = changed it, all the wireless link bandwidths will change. I want to have different wireless link bandwidths between mobile = nodes. Do you have any idea how I can make this scenario?=20 Any comment would be appreciated. Kind Regards, Mona Date: Mon, 07 Jul 2003 11:59:45 +0200 From: Fethi Filali Organization: INRIA Sophia-Antipolis (http://www.inria.fr) To: skame CC: manet@ietf.org, syoshida@net.ie.niigata-u.ac.jp Subject: Re: [manet] About changing bandwidth skmae, The default rate in ns2 seems to be 1Mb. See file ns-2.26/tcl/lan/mac.tcl , u can find the line: Mac/802_11 set dataRate_ 1Mb ;# both control and data pkts the tcl variable dataRate_ is binded to the c++ variable dataRate_ in=20 the mac-802_11.cc file you can change the default value in mac.tcl and recompiling ns. Fethi. skame wrote: > Hi,all. >=20 > I want to know the way of changing bandwidth. > The defalut bandwidth in ns2 is 2[Mb/s]. > I suppose 802.11b in maclayer. > Now bandwidth in 802.11b is 11[Mb/s]. > So I want to change the bandwidth from 2[Mb/s] to 11[Mb/s]. > Please tell me how to change bandwidth. >=20 > Thank you. > skame >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 ----------------------------------------------------------- Mona Ghassemian, PhD student Centre for Telecommunications Research Kings College London Strand, London WC2R 2LS UK TEL: +44 20 7848 2596 FAX: +44 20 7848 2664 Mona.Ghassemian@kcl.ac.uk Tehran@ieee.org ------=_NextPart_000_003A_01C34481.C8B85760 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
You may set this value according to the = end node=20 IDs in ns2.  In this way, you can assign different bandwidths to = different=20 links.
 
 Tao Lin
 PhD Candidate
 ECE Dept.
 Virginia Tech
 
 
----- Original Message -----
From:=20 Mona
Sent: Monday, July 07, 2003 = 12:22=20 PM
Subject: Re: [manet] About = changing=20 bandwidth

Dear Fathi,
 
I have tried to change this value in ns2. However = it seems=20 if I changed it, all the wireless link bandwidths will = change.
I want to have different wireless link bandwidths = between=20 mobile nodes. Do you have any idea how I can make this scenario? =
Any comment would be appreciated.
 
Kind Regards, Mona
 
 
Date: Mon, 07 Jul 2003 11:59:45 = +0200
From:=20 Fethi Filali <Fethi.Filali@sophia.inria.fr>
Organization: INRIA Sophia-Antipolis (http://www.inria.fr)
To: skame <skame@net.ie.niigata-u.ac.jp>
CC:=20 manet@ietf.org, syoshida@net.ie.niigata-u.ac.jp
Subject: Re:=20 [manet] About changing bandwidth

skmae,

The default rate = in ns2=20 seems to be 1Mb.

See file ns-2.26/tcl/lan/mac.tcl , u can find = the=20 line:

   Mac/802_11 set dataRate_ 1Mb   ;# = both=20 control and data pkts

the tcl variable dataRate_ is binded to = the c++=20 variable dataRate_ in
the mac-802_11.cc file

you can change = the=20 default value in mac.tcl and recompiling = ns.

Fethi.

skame=20 wrote:
> Hi,all.
>
> I want to know the way of = changing=20 bandwidth.
> The defalut bandwidth in ns2 is 2[Mb/s].
> I = suppose=20 802.11b in maclayer.
> Now bandwidth in 802.11b is = 11[Mb/s].
> So=20 I want to change the bandwidth from 2[Mb/s] to 11[Mb/s].
> = Please tell=20 me how to change bandwidth.
>
> Thank you.
> = skame
>=20
> _______________________________________________
> manet = mailing=20 list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>




-----------------------------------------------------------
M= ona=20 Ghassemian, PhD student
Centre for Telecommunications = Research
Kings=20 College London
Strand, London WC2R 2LS
UK
TEL: +44 20 7848=20 2596
FAX: +44 20 7848 2664
Mona.Ghassemian@kcl.ac.ukTehran@ieee.org
------=_NextPart_000_003A_01C34481.C8B85760-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 7 12:49:57 2003 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 MAA03342 for ; Mon, 7 Jul 2003 12:49:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZZBC-0004fa-8h for manet-archive@odin.ietf.org; Mon, 07 Jul 2003 12:49:30 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67GnUiJ017944 for manet-archive@odin.ietf.org; Mon, 7 Jul 2003 12:49:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZZBC-0004fL-5b for manet-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 12:49: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 MAA03301 for ; Mon, 7 Jul 2003 12:49:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZZBA-0006eQ-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 12:49:28 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZZB9-0006eN-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 12:49:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZZAj-0004Ya-PE; Mon, 07 Jul 2003 12:49:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZZAW-0004YB-50 for manet@optimus.ietf.org; Mon, 07 Jul 2003 12:48: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 MAA03235 for ; Mon, 7 Jul 2003 12:48:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZZAU-0006d5-00 for manet@ietf.org; Mon, 07 Jul 2003 12:48:46 -0400 Received: from avsmtp.unitn.it ([193.205.206.51] helo=rav2.unitn.it) by ietf-mx with esmtp (Exim 4.12) id 19ZZAT-0006bp-00 for manet@ietf.org; Mon, 07 Jul 2003 12:48:45 -0400 Received: from science.unitn.it (alpha.science.unitn.it [193.205.194.23]) by rav2.unitn.it (8.12.9/8.12.5) with ESMTP id h67GmEbH021836 for ; Mon, 7 Jul 2003 18:48:14 +0200 Received: from brunato (brunato.science.unitn.it [193.205.213.112]) by science.unitn.it (8.9.3/8.9.3) with SMTP id SAA26409 for ; Mon, 7 Jul 2003 18:48:14 +0200 (MET DST) Message-ID: <005b01c344a8$103243f0$70d5cdc1@science.unitn.it> From: "Mauro Brunato" To: Date: Mon, 7 Jul 2003 18:51:51 +0200 Organization: =?iso-8859-1?Q?Universit=E0_di_Trento?= 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.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-RAVMilter-Version: 8.4.3(snapshot 20030212) (rav2) X-Spam-Score: -100 () USER_IN_WHITELIST X-Scanned-By: MIMEDefang 2.32 (www . roaringpenguin . com / mimedefang) Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by rav2.unitn.it id h67GmEbH021836 Content-Transfer-Encoding: quoted-printable Subject: [manet] CFP: WONS2004, Madonna di Campiglio, Italy Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 This is intended as a one-time posting. Please accept my apologies if you receive multiple copies. Mauro Brunato brunato@dit.unitn.it =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CALL FOR PAPERS WONS 2004 First International Working Conference on Wireless On-demand Network Systems (sponsorship by IFIP WG 6.3 and 6.8 is pending for approval) http://dit.unitn.it/wons/ wons@dit.unitn.it Madonna di Campiglio (Italy) January 21-23, 2004 Wireless LANs are enjoying a growing interest at all levels: research, application, business. The explosive growth of IEEE802.11b (Wi-Fi), the ongoing change of spectrum management policies and the technology boost making wireless wideband a reality are bringing high bandwidth wireless connectivity to the masses. Connectivity and networking built "on-demand"= , where and when they are needed in an evolutionary and incremental fashion with limited investments, is spawning new research and business opportunities, offering unprecedented possibilities to support working communities and ubiquitous, cooperative computing. Many aspects of the current wireless LANs growth resemble the rapid, and = in part anarchic and unexpected, evolution of the wired Internet. The road i= s traced and enthusiasm is mounting but many challenges have to be solved before providing seamless communication, reliable quality, secure high bandwidth connectivity, and useful services. The conference will concentrate on new research issues open in the "wirel= ess Internet" context, including design, modelling and performance evaluation= , pricing and profitability models, QoS models and practical implementation. Sound experimental evaluation of new techniques will also be considered. The meeting will take place in one of the finest winter resorts of the Al= ps, Madonna di Campiglio, in the Trentino region. The cozy atmosphere of the conference hotel, facing one of the most spectacular panoramas in the Alp= s, will facilitate concentration and creativity. The schedule of the meeting will consist of presentations in the morning = and in the afternoon/evening. A pause after lunch will allow social activitie= s and informal interaction among the participants. Topics comprise, but are not limited to: - Wireless access to the Internet - Modelling and performance evaluation of wireless LANs - Quality of service and pricing ("charging for quality") - Traffic and user activity models - Service differentiation mechanisms - Virtual operators in WiFi networks - Pervasive / ubiquitous computing - Location and context-awareness - Wireless LANs design - Management, authentication, authorization and accounting - On-Demand, Ad-Hoc Networks ---------------------------------------------------------- Keynote speech: "Ad Hoc Wireless Networks: Protocols and Applications" Mario Gerla, Computer Science Department, UCLA ---------------------------------------------------------- Conference Proceedings will be published by Springer in the series "Lecture Notes in Computer Science". Extended versions of the best papers will be considered for publication on a special issue of Kluwer/ACM Mobile Networks and Applications (MONET). A Best Paper Award will be assigned at the conference. ---------------------------------------------------------- Important deadlines: - August 1st, 2003 (Hard Deadline): Electronic Full Paper Submission - September 30, 2003: Acceptance Notification - October 15, 2003: Final Version Due ---------------------------------------------------------- General Chair: Roberto Battiti, University of Trento, Italy Local Organization Chairs: Sandro Pera, University of Trento, Italy Alessandro Villani, University of Trento, Italy Publicity Chairs: Mauro Brunato, University of Trento, Italy Tutorials and Sponsorships Chairs: Paolo Simonetti, Provincia Autonoma di Trento, Italy Program Committee Chairs: Marco Conti, CNR Pisa, Italy Renato Lo Cigno, University of Trento, Italy Technical Program Committee: Arup Acharya, IBM T.J. Watson Research, USA Ian Akyildiz, Georgia Institute of Technology, Atlanta, USA Eitan Altman, INRIA, Sophia Antipolis, France Roberto Battiti, University of Trento, Italy Hendrik Berndt, DoCoMo Communications Laboratories Europe Alan Albert Bertossi, University of Bologna, Italy Giuseppe Bianchi, University of Palermo, Italy Ernst Biersack, Eurecom, Sophia Antipolis, France Maurizio Bonuccelli, University of Pisa, Italy Dragan Boscovic, Motorola Research Center of Paris, France Andrew T. Campbell, Columbia University, USA Carla Fabiana Chiasserini, Politecnico di Torino, Italy Imrich Chlamtac, University of Trento, Italy A. Chockalingam, IIS, Bangalore, India Sunghyun Choi, Seoul National University, Korea Marco Conti, CNR of Pisa, Italy Szab=F3 Csaba, BME, Budapest, Hungary Sajal K. Das, The University of Texas at Arlington, USA Christos Douligeris, University of Piraeus, Greece Domenico Ferrari, Universit=E0 Cattolica of Piacenza, Italy Mario Gerla, UCLA, USA Silvia Giordano, SUPSI of Lugano, Switzerland Enrico Gregori, CNR of Pisa, Italy Parviz Kermani, IBM - T.J. Watson Research Center, USA Demetres D. Kouvatsos, University of Bradford, UK Kin K. Leung, Bell Labs, Lucent Technologies, USA Bo Li, University of Science and Technology of Hong Kong, China Renato Lo Cigno, University of Trento, Italy Gerald Q. Maguire Jr., KTH, Sweden Petri H. M=E4h=F6nen, RWTH Aachen, Germany Michela Meo, Politecnico di Torino, Italy Sergio Palazzo, University of Catania, Italy Bj=F6rn Pehrson, KTH, Sweden Gian Paolo Rossi, University of Milano, Italy M. Yahya "Medy" Sanadidi, UCLA, USA Puneet Sharma, Hewlett Packard Labs, USA Ioannis Stavrakakis, University of Athens, Greece Heinrich J. St=FCttgen, NEC Europe Ltd., Germany Salvatore Tucci, University of Roma Tor Vergata, Italy Bernhard Walke, Aachen University of Technology, Germany Menzo Wentink, Intersil, The Netherlands Adam Wolisz, TU Berlin, Germany Hidetoshi Yokota, KDDI R&D Laboratories, Japan Michele Zorzi, University of Ferrara, Italy _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 7 16:00:50 2003 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 QAA12330 for ; Mon, 7 Jul 2003 16:00: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 19Zc9u-00010i-UX for manet-archive@odin.ietf.org; Mon, 07 Jul 2003 16:00:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h67K0Mkm003884 for manet-archive@odin.ietf.org; Mon, 7 Jul 2003 16:00:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zc9u-00010Z-Qb for manet-web-archive@optimus.ietf.org; Mon, 07 Jul 2003 16:00: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 QAA12281 for ; Mon, 7 Jul 2003 16:00:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zc9t-0001vG-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 16:00:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Zc9s-0001vD-00 for manet-web-archive@ietf.org; Mon, 07 Jul 2003 16:00:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zc9a-0000to-91; Mon, 07 Jul 2003 16:00:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Zc8l-0000sm-T6 for manet@optimus.ietf.org; Mon, 07 Jul 2003 15:59:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12222; Mon, 7 Jul 2003 15:59:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Zc8k-0001uP-00; Mon, 07 Jul 2003 15:59:10 -0400 Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 19Zc8j-0001uG-00; Mon, 07 Jul 2003 15:59:09 -0400 Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2/8.11.2) with ESMTP id h67Jx6L28601; Mon, 7 Jul 2003 12:59:06 -0700 (PDT) Message-Id: <200307071959.h67Jx6L28601@gamma.isi.edu> To: IETF-Announce: ; Cc: rfc-editor@rfc-editor.org, manet@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Mon, 07 Jul 2003 12:59:06 -0700 Subject: [manet] RFC 3561 on Ad hoc On-Demand Distance Vector (AODV) 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: , --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3561 Title: Ad hoc On-Demand Distance Vector (AODV) Routing Author(s): C. Perkins, E. Belding-Royer, S. Das Status: Experimental Date: July 2003 Mailbox: Charles.Perkins@nokia.com, ebelding@cs.ucsb.edu, sdas@ececs.uc.edu Pages: 37 Characters: 90356 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-manet-aodv-13.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3561.txt The Ad hoc On-Demand Distance Vector (AODV) routing protocol is intended for use by mobile nodes in an ad hoc network. It offers quick adaptation to dynamic link conditions, low processing and memory overhead, low network utilization, and determines unicast routes to destinations within the ad hoc network. It uses destination sequence numbers to ensure loop freedom at all times (even in the face of anomalous delivery of routing control messages), avoiding problems (such as "counting to infinity") associated with classical distance vector protocols. This document is a product of the Mobile Ad-hoc Networks Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <030707125735.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3561 --OtherAccess Content-Type: Message/External-body; name="rfc3561.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <030707125735.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 8 05:07:43 2003 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 FAA15188 for ; Tue, 8 Jul 2003 05:07:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZoRP-0006QV-Kt for manet-archive@odin.ietf.org; Tue, 08 Jul 2003 05:07:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6897Fio024699 for manet-archive@odin.ietf.org; Tue, 8 Jul 2003 05:07:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZoRP-0006QE-H0 for manet-web-archive@optimus.ietf.org; Tue, 08 Jul 2003 05:07: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 FAA15175 for ; Tue, 8 Jul 2003 05:07:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZoRM-00002H-00 for manet-web-archive@ietf.org; Tue, 08 Jul 2003 05:07:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZoRL-00002D-00 for manet-web-archive@ietf.org; Tue, 08 Jul 2003 05:07:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZoRC-0006Nu-CS; Tue, 08 Jul 2003 05:07:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZoQI-0006Ml-8G for manet@optimus.ietf.org; Tue, 08 Jul 2003 05:06: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 FAA15156 for ; Tue, 8 Jul 2003 05:06:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZoQF-00001r-00 for manet@ietf.org; Tue, 08 Jul 2003 05:06:03 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19ZoQD-00001X-00 for manet@ietf.org; Tue, 08 Jul 2003 05:06:02 -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 h689HW916889; Tue, 8 Jul 2003 18:17:33 +0900 (KST) Message-ID: <001701c3452f$c67dd2a0$c470fe81@etri.re.kr> From: "Jaehoon Jeong" To: "Jean-Marie ORSET" Cc: "MANET WG" , "autonet" References: <9E664A0522ABD711827B00D0B7A8AC4A373891@cms3.etri.re.kr><20030704110130.0b71f038.jean-marie.orset@int-evry.fr><009101c34290$bf613ad0$c470fe81@etri.re.kr> <20030707183238.299531ae.jean-marie.orset@int-evry.fr> Subject: Re: [Re] [manet] Re: Ad Hoc IP Address Autoconfiguration Date: Tue, 8 Jul 2003 18:03:18 +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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 SGksIEplYW4tTWFyaWUuDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQpGcm9tOiAi SmVhbi1NYXJpZSBPUlNFVCIgPGplYW4tbWFyaWUub3JzZXRAaW50LWV2cnkuZnI+DQpUbzogIkph ZWhvb24gSmVvbmciIDxwYXVsQGV0cmkucmUua3I+DQpTZW50OiBUdWVzZGF5LCBKdWx5IDA4LCAy MDAzIDE6MzIgQU0NClN1YmplY3Q6IFJlOiBbUmVdIFttYW5ldF0gUmU6IEFkIEhvYyBJUCBBZGRy ZXNzIEF1dG9jb25maWd1cmF0aW9uDQoNCg0KPiANCj4gTGUgU2F0LCA1IEp1bCAyMDAzIDA5OjU5 OjUzICswOTAwDQo+IEphZWhvb24gSmVvbmcgYSDpY3JpdDoNCj4gDQo+ID4gSSBhZ3JlZSB3aXRo IHlvdSB0aGF0IHRoZSBwdWJsaWMgY3J5cHRvZ3JhcGh5IGlzIHZlcnkgZXhwZW5zaXZlLCBlc3Bl Y2lhbGx5IGluIE1BTkVULg0KPiA+IEluIG15IHNjaGVtZSwgYSBrZXkgaXMgdXNlZCBmb3IgaWRl bnRpZnlpbmcgdGhlIGFkZHJlc3MgZHVwbGljYXRpb24uIA0KPiA+IFNvLCBrZXkncyB1bmlxdWVu ZXNzIGlzIGltcG9ydGFudC4NCj4gPiBJbiBvcmRlciB0byBndWFyYW50ZWUgdGhlIHVuaXF1ZW5l c3Mgb2YgcHVibGljIGtleSwgDQo+ID4gV2Ugc2hvdWxkIHVzZSBhIGNlcnRpZmljYXRlIGZvciBh IHB1YmxpYyBrZXk/DQo+ID4gSG93IGFib3V0Pw0KPiANCj4gWWVzLCBhIGNlcnRpZmljYXRlIHNl ZW1zIHRvIGJlIGVzc2VudGlhbCB3aGlsZSB1c2luZyBwdWJsaWMga2V5IGNyeXB0b2dyYXBoeS4N Cj4gSW4gZmFjdCwgdGhlIHByb2JsZW0gaXMgd2hvIHdpbGwgYmUgdXNlZCB0byBjZXJ0aWZpY2F0 ZSB0aGUga2V5LCBzaW5jZSB3ZSBjYW4gbm90IGVtcGx5IGNlbnRyYWxpemVkIGNlcnRpZmljYXRp b24gYXV0aG90aXR5PyBaaG91IGFuZCBIYWFzIGRpZCB3cml0ZSBhIHZlcnkgZ29vZCBwYXBlciBv biB0aGUgZGlzdHJpYnV0aW9uIG9mIHRydXN0IGluIE1hbmV0LiBUaGUgc2NoZW1lcyBjb3VsZA0K PiBiZSB1c2VkIGNvbXBsZW1lbnRhcnkuDQoNCiAgIENvdWxkIHlvdSB0ZWxsIG1lIHRoZSBVUkwg b2YgdGhlIHBhcGVyPw0KDQo+IEhvd2V2ZXIsIGV2ZW4gaWYgaXQgaXMgaW1wb3J0YW50IHRvIGd1 YXJhbnRlZSB0aGUgbm9uIGFkZHJlc3MgZHVwbGljYXRpb24NCj4gSSdtIG5vdCBzdXJlIHB1Ymxp YyBrZXkgY3J5cHRvZ3JhcGh5IGNvdWxkIGJlIHVzZWQgdG8gc2lnbiBlYWNoIHBhY2tldC4NCj4N CiAgIFRoYXQgd2lsbCBuZWVkIG1vcmUgZGlzY3Vzc2lvbiwgSSB0aGluay4NCiAgIEFueXdheSwg SSBob3BlICB0aGlzIG1hbmV0IHdnIG1lZXRpbmcgc3RhcnRzIHRvIGRpc2N1c3MgYWQgaG9jIGFk ZHJlc3MgYXV0b2NvbmZpZ3VyYXRpb24uDQogICBUaGFua3MuDQoNCiAgIC9KYWVob29uDQoNCj4g Q29yZGlhbGx5LCBKZWFuLU1hcmllIE9yc2V0DQo+IA== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 8 12:23:45 2003 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 MAA29408 for ; Tue, 8 Jul 2003 12:23: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 19ZvFN-00048L-Ni for manet-archive@odin.ietf.org; Tue, 08 Jul 2003 12:23:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h68GNHsC015885 for manet-archive@odin.ietf.org; Tue, 8 Jul 2003 12:23:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZvFN-000488-Jw for manet-web-archive@optimus.ietf.org; Tue, 08 Jul 2003 12:23: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 MAA29396 for ; Tue, 8 Jul 2003 12:23:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZvFM-0003J9-00 for manet-web-archive@ietf.org; Tue, 08 Jul 2003 12:23:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ZvFL-0003J6-00 for manet-web-archive@ietf.org; Tue, 08 Jul 2003 12:23:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ZvF7-00046v-KU; Tue, 08 Jul 2003 12: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 19ZvEm-00046b-Hv for manet@optimus.ietf.org; Tue, 08 Jul 2003 12:22: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 MAA29374 for ; Tue, 8 Jul 2003 12:22:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ZvEl-0003J0-00 for manet@ietf.org; Tue, 08 Jul 2003 12:22:39 -0400 Received: from reserv2.univ-lille1.fr ([193.49.225.90] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19ZvEk-0003Ix-00 for manet@ietf.org; Tue, 08 Jul 2003 12:22:38 -0400 Received: from malonne.lifl.fr (malonne.lifl.fr [134.206.10.29]) by reserv2.univ-lille1.fr (8.12.9/jtpda-5.3.1) with ESMTP id h68GMYFg005247 for ; Tue, 8 Jul 2003 18:22:34 +0200 Received: from KRIEK (kriek.lifl.fr [134.206.11.16]) by malonne.lifl.fr with ESMTP id h68GMXO26515 for ; Tue, 8 Jul 2003 18:22:33 +0200 (MEST) From: "David Simplot" To: Date: Tue, 8 Jul 2003 18:23:49 +0200 Organization: IRCICA/LIFL, Univ. Lille 1 Message-ID: <004701c3456d$502a7f20$100bce86@lifl.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-MailScanner: Found to be clean Content-Transfer-Encoding: quoted-printable Subject: [manet] 2nd CFP WWAN 2004, Tokyo, Japan, March 23-26, 2004 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Please accept our apologies in case you receive this information from multiple sources.=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CALL FOR PAPERS WWAN 2004 International Workshop on Wireless Ad Hoc Networking http://www.lifl.fr/RD2P/WWAN2004 to be held in conjunction with The 24th International Conference on Distributed Computing Systems (ICDCS-2004) Tokyo, Japan, March 23-26, 2004 http://www.cis.ohio-state.edu/icdcs04 http://www.icdcs2004.org Wireless networks and mobile computing research has until recently concentrated on single-hop networks (network nodes communicating directly to a fixed infrastructure), such as cellular or satellite systems. Ad hoc networking covers multi-hop scenarios (network nodes communicating via other network nodes) such as conference, hospital, battlefield, rescue, monitoring scenarios. Wireless ad-hoc networks are formed by a set of hosts that communicate with each other over a wireless channel. Each node has the ability to communicate directly with another node in its physical neighborhood. They operate in a self-organized and decentralized manner and message communication takes place via multi-hop spreading. A packet is sent to its target node through a set of intermediate nodes that act as routers. Particular ad hoc network systems include packet radio networks, sensor networks, personal communication systems, rooftop networks, and wireless local area networks. This workshop covers the area of ad hoc networking, from physical issues up to applications aspects. In particular, it will cover physical, data link, network and transport layers, as well as applications, security, simulation and power management issues in sensor, local area, personal, and mobile ad hoc networks. It is the goal of this workshop to review ad hoc protocols and models and to reflect the latest in the state of the art in ad hoc networks. It seeks to provide up to date information on research and development activities in rapidly growing area of ad hoc networks. Topics of Interest We are seeking papers that describe original and unpublished contributions addressing various aspects of ad hoc networking. Possible topics of interest include, but are not limited to: - Applications and history of ad hoc networks,=20 - Physical layer of ad hoc networks,=20 - Pervasive and wearable computing,=20 - IEEE 801.11 and Bluetooth based medium access control,=20 - Methods and tools for ad hoc networks simulation,=20 - Analytical, mobility and validation models for ad hoc networks,=20 - Hybrid networks and wireless internet,=20 - Security in ad hoc networks,=20 - Data management issues, query processing, data delivery,=20 - Routing, broadcasting and multicasting in ad hoc networks,=20 - Energy-efficient protocols for ad hoc networks,=20 - Quality of service in medium access control and routing,=20 - Topology construction and maintenance in ad hoc networks.=20 Paper Submission Submit a full paper of about 6 pages (IEEE Computer Society proceedings Manuscripts: two column, single-spaced), including figures and references, using 10 font size, and number each page. Accepted papers will be published by IEEE Computer Society Press, as proceedings of the ICDCS'2004 workshops. You can use the IEEE Computer Society Press Proceedings Author Guidelines (http://computer.org/cspress/instruct.htm). Prepare your paper in Postscript or PDF file (Adobe format), paper title, authors' names, affiliations, postal address, phone, fax, and e-mail address of the authors, about 200-250 word abstract, and five keywords. Send by mail your submission to both co-chairs (David.Simplot@lifl.fr and ivan@site.uottawa.ca). Important Dates Manuscript Submission: September 1, 2003=20 Acceptance Notification: October 31, 2003=20 Final Manuscript Due: December 20, 2003=20 Program Co-Chairs Dr. David Simplot IRCICA/LIFL, Univ. Lille 1, France David.Simplot@lifl.fr=20 Dr. Ivan Stojmenovic SITE, University of Ottawa, Canada ivan@site.uottawa.ca=20 Program Committee Michel Barbeau, Carleton University, Ottawa, Canada=20 Stefano Basagni, Northeastern University, Boston, USA=20 Ana Cavalli, INT Evry, France=20 Marco Conti, IIT Institute, Pisa, Italy=20 Piet Demeester, University of Gent, Belgium=20 Serge Fdida, University of Paris, France=20 Laura Feeney, SICS, Kista, Sweden=20 Afonso Ferreira, INRIA Sophia Antipolis, France=20 Matthias Frank, University of Bonn, Germany=20 Jennifer Hou, University of Illinois, USA=20 Philippe Jacquet, INRIA Rocquencourt, France=20 Keqin Li, State University of New York, USA=20 Xiang-Yang Li, Illinois Institute of Technology, USA=20 Jelena Misic, University of Manitoba, Winnipeg, Canada=20 Stephan Olariu, Old Dominion University, Norfolk, USA=20 Symeon Papavassiliou, University Heights, Newark, USA=20 Tarek N. Saadawi, CCNY New York, USA=20 Loren Schwiebert, Wayne University, Detroit, USA=20 Krishna Sivalingam, University of Maryland Baltimore County, USA=20 Ketil St=F8len, SINTEF Oslo, Norway=20 Vassilis Tsaoussidis, Demokritos University of Greece, Greece=20 St=E9phane Ub=E9da, INSA Lyon, France=20 Takashi Watanabe, Shizuoka University, Japan=20 Fr=E9d=E9ric Weis, University of Rennes, France=20 Jie Wu, Florida Atlantic University, USA=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 12:04:44 2003 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 MAA07629 for ; Wed, 9 Jul 2003 12:04: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 19aHQX-00088F-Ku for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 12:04:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69G4HPa031255 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 12:04:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aHQX-000882-G0 for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 12:04: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 MAA07581 for ; Wed, 9 Jul 2003 12:04:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aHQW-00006P-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 12:04:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aHQV-00006L-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 12:04:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aHQJ-00082a-Kl; Wed, 09 Jul 2003 12:04:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aHPl-0007zM-03 for manet@optimus.ietf.org; Wed, 09 Jul 2003 12:03:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07557 for ; Wed, 9 Jul 2003 12:03:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aHPj-000062-00 for manet@ietf.org; Wed, 09 Jul 2003 12:03:27 -0400 Received: from crystal.bbn.com ([128.89.80.29]) by ietf-mx with esmtp (Exim 4.12) id 19aHPj-00005j-00 for manet@ietf.org; Wed, 09 Jul 2003 12:03:27 -0400 Received: from crystal.bbn.com (localhost.bbn.com [127.0.0.1]) by crystal.bbn.com (Postfix) with ESMTP id 558791D14D; Wed, 9 Jul 2003 12:08:35 -0400 (EDT) To: manet@ietf.org Cc: ramanath@bbn.com Date: Wed, 09 Jul 2003 12:08:35 -0400 From: Ram Ramanathan Message-Id: <20030709160835.558791D14D@crystal.bbn.com> Subject: [manet] Carrier sense threshold/range control Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 looking for pointers to research on the control of carrier sensing range in lieu of using RTS/CTS to address the hidden node problem? To elaborate, the threshold for when carrier is declared to be "sensed" can be adjusted in many radios. Using this facility, one could possibly make the "carrier sense range" approximately twice the "communication range" (successful packet reception), and detect hidden nodes. This is by no means a new idea, and I vaguely recally some mention of it on this list. Of course, there are a number of factors that make the problem far more complex than the simple statement above indicates, and it is not immediately clear whether it will be effective at all. I am looking for papers, tech reports, or any publicly available material (non-proprietary) on this issue. Many thanks in advance, -Ram. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 12:18:12 2003 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 MAA08326 for ; Wed, 9 Jul 2003 12:18:12 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aHdZ-0001s8-A6 for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 12:17:45 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69GHjTF007190 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 12:17:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aHdZ-0001rt-6d for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 12:17:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08296 for ; Wed, 9 Jul 2003 12:17:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aHdX-0000JD-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 12:17:43 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aHdX-0000JA-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 12:17:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aHct-0001ir-Cd; Wed, 09 Jul 2003 12:17:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aHcp-0001iP-8p for manet@optimus.ietf.org; Wed, 09 Jul 2003 12:16: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 MAA08263 for ; Wed, 9 Jul 2003 12:16:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aHcn-0000Iv-00 for manet@ietf.org; Wed, 09 Jul 2003 12:16:57 -0400 Received: from gateway.scalable-networks.com ([63.205.33.202] helo=mithrandir.scalable-networks.com) by ietf-mx with smtp (Exim 4.12) id 19aHcm-0000In-00 for manet@ietf.org; Wed, 09 Jul 2003 12:16:56 -0400 Received: (qmail 5786 invoked from network); 9 Jul 2003 16:21:04 -0000 Received: from web.lan.scalable-solutions.com (HELO cs.ucla.edu) (mineo@192.168.0.1) by mithrandir.lan.scalable.networks.com with SMTP; 9 Jul 2003 16:21:04 -0000 Message-ID: <3F0C3FD6.4050203@cs.ucla.edu> Date: Wed, 09 Jul 2003 09:16:22 -0700 From: Mineo Takai 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: Ram Ramanathan CC: manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control References: <20030709160835.558791D14D@crystal.bbn.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello Ram, This issue was discussed in my part of a tutorial on "MAC protocols for MANET" (by Nitin Vaidya, Rajive Bagrodia and Mineo Takai) in MobiHoc 2001. Some of the slides seem to have corrupted, but you can take a look at Slides 31 through 34 of http://www.scalable-networks.com/pdf/mobihocpreso.pdf. I will try regenerating the slides and ask them to update. Regards, Mineo Ram Ramanathan wrote: > I am looking for pointers to research on the control of carrier sensing > range in lieu of using RTS/CTS to address the hidden node problem? > > To elaborate, the threshold for when carrier is declared to be "sensed" > can be adjusted in many radios. Using this facility, one could possibly > make the "carrier sense range" approximately twice the "communication range" > (successful packet reception), and detect hidden nodes. > > This is by no means a new idea, and I vaguely recally some mention of > it on this list. Of course, there are a number of factors that make the > problem far more complex than the simple statement above indicates, and > it is not immediately clear whether it will be effective at all. > > I am looking for papers, tech reports, or any publicly available material > (non-proprietary) on this issue. > > Many thanks in advance, > > -Ram. > > _______________________________________________ > 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 Jul 9 13:05:11 2003 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 NAA10334 for ; Wed, 9 Jul 2003 13:05:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aIN2-00052P-7F for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 13:04:45 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69H4iPP019364 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 13:04:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aIN2-00052F-4F for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 13:04: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 NAA10274 for ; Wed, 9 Jul 2003 13:04:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aIN0-0000nx-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 13:04:42 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aIMz-0000nu-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 13:04:41 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aIML-0004uN-MI; Wed, 09 Jul 2003 13: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 19aILO-0004tK-79 for manet@optimus.ietf.org; Wed, 09 Jul 2003 13:03: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 NAA10194 for ; Wed, 9 Jul 2003 13:02:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aILM-0000mO-00 for manet@ietf.org; Wed, 09 Jul 2003 13:03:00 -0400 Received: from gateway.scalable-networks.com ([63.205.33.202] helo=mithrandir.scalable-networks.com) by ietf-mx with smtp (Exim 4.12) id 19aILL-0000mL-00 for manet@ietf.org; Wed, 09 Jul 2003 13:02:59 -0400 Received: (qmail 3982 invoked from network); 9 Jul 2003 17:07:06 -0000 Received: from web.lan.scalable-solutions.com (HELO cs.ucla.edu) (mineo@192.168.0.1) by mithrandir.lan.scalable.networks.com with SMTP; 9 Jul 2003 17:07:06 -0000 Message-ID: <3F0C4AA0.1030501@cs.ucla.edu> Date: Wed, 09 Jul 2003 10:02:24 -0700 From: Mineo Takai 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: Ram Ramanathan CC: manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control References: <20030709160835.558791D14D@crystal.bbn.com> <3F0C3FD6.4050203@cs.ucla.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 (I forgot to comment on this in my previous message other than giving a pointer..) It is possible to avoid many hidden terminal cases by setting the sensing range more than twice the communication range, though there are some caveats. We can set/adjust the CS threshold, but not the pathloss that is to be determined by the environment. The CS range is a function of the CS threshold and pathloss (and TX power, antenna gains etc.), so the radio can hardly know what the resulting CS range is for a given CS threshold value. We can make each radio very sensitive by setting the CS threshold sufficiently low, but that would severely limit the network capacity as each radio becomes too conservative for signal transmission. Moreover, hidden terminal problems may show up regardless of the CS threshold due to irregular pathloss values. Imagine Nodes A, B and C are placed in an equal distance from each other (triangular topology), but Nodes B and C are obstructed by a wall that completely shuts down the communication link between them (pathloss equal to infinity). This clearly creates a hidden terminal problem at Node A regardless of the CS threshold. (RTS/CTS should still work in this situation.) Finally, other factors (fading, noise sources nearby, cumulative interference, interference/noise estimation errors etc.) make the CS mechanism less than perfect. I'm not saying physical carrier sense is useless (In fact, I think it's very useful). Virtual carrier sense (RTS/CTS) is not a perfect solution either and comes with big overheads. Mineo Mineo Takai wrote: > Hello Ram, > > This issue was discussed in my part of a tutorial on "MAC protocols for > MANET" (by Nitin Vaidya, Rajive Bagrodia and Mineo Takai) in MobiHoc > 2001. Some of the slides seem to have corrupted, but you can take a look > at Slides 31 through 34 of > http://www.scalable-networks.com/pdf/mobihocpreso.pdf. I will try > regenerating the slides and ask them to update. > > Regards, > > Mineo > > Ram Ramanathan wrote: > >> I am looking for pointers to research on the control of carrier >> sensing range in lieu of using RTS/CTS to address the hidden node >> problem? >> >> To elaborate, the threshold for when carrier is declared to be >> "sensed" can be adjusted in many radios. Using this facility, one >> could possibly >> make the "carrier sense range" approximately twice the "communication >> range" >> (successful packet reception), and detect hidden nodes. >> >> This is by no means a new idea, and I vaguely recally some mention of >> it on this list. Of course, there are a number of factors that make >> the problem far more complex than the simple statement above >> indicates, and >> it is not immediately clear whether it will be effective at all. >> >> I am looking for papers, tech reports, or any publicly available material >> (non-proprietary) on this issue. >> >> Many thanks in advance, >> >> -Ram. >> >> _______________________________________________ >> 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 Jul 9 13:40:26 2003 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 NAA11607 for ; Wed, 9 Jul 2003 13:40:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aIv8-0007E1-9S for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 13:39:58 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69HdwPg027772 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 13:39:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aIv8-0007Dr-4i for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 13:39:58 -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 NAA11573 for ; Wed, 9 Jul 2003 13:39:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aIuE-0006yr-DG; Wed, 09 Jul 2003 13:39:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aItQ-0006y0-4R for manet@optimus.ietf.org; Wed, 09 Jul 2003 13:38: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 NAA11537 for ; Wed, 9 Jul 2003 13:38:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aItN-000194-00 for manet@ietf.org; Wed, 09 Jul 2003 13:38:09 -0400 Received: from fmr05.intel.com ([134.134.136.6] helo=hermes.jf.intel.com) by ietf-mx with esmtp (Exim 4.12) id 19aItN-00018r-00 for manet@ietf.org; Wed, 09 Jul 2003 13:38:09 -0400 Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6]) by hermes.jf.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 h69HZV829015 for ; Wed, 9 Jul 2003 17:35:31 GMT Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by petasus.jf.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 h69HWpm25439 for ; Wed, 9 Jul 2003 17:32:51 GMT Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56]) by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2003070910485724124 ; Wed, 09 Jul 2003 10:48:57 -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); Wed, 9 Jul 2003 10:37:35 -0700 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Subject: RE: [manet] Carrier sense threshold/range control Date: Wed, 9 Jul 2003 10:37:34 -0700 Message-ID: Thread-Topic: [manet] Carrier sense threshold/range control Thread-Index: AcNGPIWp17etAiQbSbG5DzwZgJnMgwAAmqBQ From: "Yang, Lily L" To: "Mineo Takai" , "Ram Ramanathan" Cc: X-OriginalArrivalTime: 09 Jul 2003 17:37:35.0693 (UTC) FILETIME=[C8C857D0:01C34640] 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 Is this threshold commonly adjustable in the driver for most 802.11 = cards? I agree with Mineo that this threshold by itself may not be = adaquate for the hidden node problem. I would rather want to adjust the = threshold to maximize the network capacity. As Mineo pointed out, when = it is set too conservatively (which I think is the case), it causes the = nodes to backoff unnecessarily and hence sacrifice spatial reuse = potential and network capacity ultimately.=20 > -----Original Message----- > From: Mineo Takai [mailto:mineo@cs.ucla.edu] > Sent: Wednesday, July 09, 2003 10:02 AM > To: Ram Ramanathan > Cc: manet@ietf.org > Subject: Re: [manet] Carrier sense threshold/range control >=20 >=20 > (I forgot to comment on this in my previous message other=20 > than giving a pointer..) >=20 > It is possible to avoid many hidden terminal cases by setting=20 > the sensing range=20 > more than twice the communication range, though there are=20 > some caveats. We can=20 > set/adjust the CS threshold, but not the pathloss that is to=20 > be determined by=20 > the environment. The CS range is a function of the CS=20 > threshold and pathloss=20 > (and TX power, antenna gains etc.), so the radio can hardly=20 > know what the=20 > resulting CS range is for a given CS threshold value. We can=20 > make each radio=20 > very sensitive by setting the CS threshold sufficiently low,=20 > but that would=20 > severely limit the network capacity as each radio becomes too=20 > conservative for=20 > signal transmission. Moreover, hidden terminal problems may=20 > show up regardless=20 > of the CS threshold due to irregular pathloss values. Imagine=20 > Nodes A, B and C=20 > are placed in an equal distance from each other (triangular=20 > topology), but Nodes=20 > B and C are obstructed by a wall that completely shuts down=20 > the communication=20 > link between them (pathloss equal to infinity). This clearly=20 > creates a hidden=20 > terminal problem at Node A regardless of the CS threshold.=20 > (RTS/CTS should still=20 > work in this situation.) Finally, other factors (fading,=20 > noise sources nearby,=20 > cumulative interference, interference/noise estimation errors=20 > etc.) make the CS=20 > mechanism less than perfect. >=20 > I'm not saying physical carrier sense is useless (In fact, I=20 > think it's very=20 > useful). Virtual carrier sense (RTS/CTS) is not a perfect=20 > solution either and=20 > comes with big overheads. >=20 > Mineo >=20 > Mineo Takai wrote: > > Hello Ram, > >=20 > > This issue was discussed in my part of a tutorial on "MAC=20 > protocols for=20 > > MANET" (by Nitin Vaidya, Rajive Bagrodia and Mineo Takai)=20 > in MobiHoc=20 > > 2001. Some of the slides seem to have corrupted, but you=20 > can take a look=20 > > at Slides 31 through 34 of=20 > > http://www.scalable-networks.com/pdf/mobihocpreso.pdf. I will try=20 > > regenerating the slides and ask them to update. > >=20 > > Regards, > >=20 > > Mineo > >=20 > > Ram Ramanathan wrote: > >=20 > >> I am looking for pointers to research on the control of carrier=20 > >> sensing range in lieu of using RTS/CTS to address the hidden node=20 > >> problem? > >> > >> To elaborate, the threshold for when carrier is declared to be=20 > >> "sensed" can be adjusted in many radios. Using this facility, one=20 > >> could possibly > >> make the "carrier sense range" approximately twice the=20 > "communication=20 > >> range" > >> (successful packet reception), and detect hidden nodes. > >> > >> This is by no means a new idea, and I vaguely recally some=20 > mention of > >> it on this list. Of course, there are a number of factors=20 > that make=20 > >> the problem far more complex than the simple statement above=20 > >> indicates, and > >> it is not immediately clear whether it will be effective at all. > >> > >> I am looking for papers, tech reports, or any publicly=20 > available material > >> (non-proprietary) on this issue. > >> > >> Many thanks in advance, > >> > >> -Ram. > >> > >> _______________________________________________ > >> manet mailing list > >> manet@ietf.org > >> https://www1.ietf.org/mailman/listinfo/manet > >=20 > >=20 >=20 >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 15:33:49 2003 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 PAA17240 for ; Wed, 9 Jul 2003 15:33:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aKgq-0006L4-M2 for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 15:33:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69JXKUs024365 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 15:33:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aKgq-0006Ku-GP for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 15:33: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 PAA17224 for ; Wed, 9 Jul 2003 15:33:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aKgp-0002Jm-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 15:33:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aKgo-0002Jj-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 15:33:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aKgW-0006Ek-S6; Wed, 09 Jul 2003 15:33:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aKfd-00068F-Eb for manet@optimus.ietf.org; Wed, 09 Jul 2003 15:32: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 PAA17148 for ; Wed, 9 Jul 2003 15:32:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aKfb-0002If-00 for manet@ietf.org; Wed, 09 Jul 2003 15:32:03 -0400 Received: from crystal.bbn.com ([128.89.80.29]) by ietf-mx with esmtp (Exim 4.12) id 19aKfb-0002IO-00 for manet@ietf.org; Wed, 09 Jul 2003 15:32:03 -0400 Received: from crystal.bbn.com (localhost.bbn.com [127.0.0.1]) by crystal.bbn.com (Postfix) with ESMTP id 3E26E1D14D; Wed, 9 Jul 2003 15:37:06 -0400 (EDT) To: Mineo Takai Cc: Ram Ramanathan , manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control In-reply-to: Your message of "Wed, 09 Jul 2003 10:02:24 PDT." <3F0C4AA0.1030501@cs.ucla.edu> Date: Wed, 09 Jul 2003 15:37:06 -0400 From: Ram Ramanathan Message-Id: <20030709193706.3E26E1D14D@crystal.bbn.com> Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , > Date: Wed, 09 Jul 2003 10:02:24 -0700 > From: Mineo Takai > 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: Ram Ramanathan > Cc: manet@ietf.org > Subject: Re: [manet] Carrier sense threshold/range control > References: <20030709160835.558791D14D@crystal.bbn.com> <3F0C3FD6.4050203@cs.ucla.edu> > Content-Type: text/plain; charset=us-ascii; format=flowed > Content-Transfer-Encoding: 7bit > X-Spam-Status: NO > X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) > X-Scanned-By: MIMEDefang 2.19 (www . roaringpenguin . com / mimedefang) > .. SNIP.. > I'm not saying physical carrier sense is useless (In fact, I think it's very > useful). Virtual carrier sense (RTS/CTS) is not a perfect solution either and > comes with big overheads. > > Mineo Precisely. RTS/CTS also has the exposed terminal problem which is akin to being over-conservative on the sensing threshold (although not quite as bad). From your slides it seems like they are kind of competitive even if CS range is less than twice Comm range. So if I have two crummy mechanisms, why not choose the simpler one:) I am not arguing a case here. Just wanted to know if someone has done a detailed comparision. Your tutorial comes closest, but is there a paper? -Ram. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 15:54:49 2003 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 PAA18334 for ; Wed, 9 Jul 2003 15:54:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aL1A-0007dw-Sw for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 15:54:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69JsKhg029374 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 15:54:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aL1A-0007dh-PK for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 15:54:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18316 for ; Wed, 9 Jul 2003 15:54:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aL19-0002Y7-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 15:54:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aL18-0002Y4-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 15:54:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aL0s-0007Zf-1V; Wed, 09 Jul 2003 15: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 19aKzu-0007Yf-GC for manet@optimus.ietf.org; Wed, 09 Jul 2003 15:53:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18271 for ; Wed, 9 Jul 2003 15:52:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aKzs-0002X9-00 for manet@ietf.org; Wed, 09 Jul 2003 15:53:00 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 19aKzo-0002X3-00 for manet@ietf.org; Wed, 09 Jul 2003 15:52:56 -0400 Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id D14331E4030; Wed, 9 Jul 2003 16:04:12 -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 h69Jqtg03733; Wed, 9 Jul 2003 15:52:55 -0400 Date: Wed, 9 Jul 2003 15:51:43 -0400 (EDT) From: "haas@ece.cornell.edu" To: Ram Ramanathan Cc: Mineo Takai , manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control In-Reply-To: <20030709193706.3E26E1D14D@crystal.bbn.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 Ram, Actually, that's not entirely correct - the RTS/CTS dialogue will *in principle* solve both the hidden- and the exposed-terminal problems. The issue is that in practical situations it may fail, more specifically when some of the control messages (RTS or CTS) are lost due to transmission errors, mobility, etc. There are a few papers relevant here. The first is the original MACA paper by Phil Karn that discusses the use of RTS/CTS instead of CS. The next is the MACAW paper that solves some residual problems for an indoor IR network (fairness, etc). Finally, there is our Dual Busy Tone Multiple Access (DBTMA) paper: Zygmunt J. Haas and Jing Deng, "Dual Busy Tone Multiple Access (DBTMA) - A Multiple Access Control for Ad Hoc Networks," IEEE Transactions on Communications, vol. 50, no. 6, June 2002, pp. 975-985 which you can dowload from our web page at: http://wnl.ece.cornell.edu/wnlprojects.html and which contains the references to the MACA and the MACAW papers. Best, 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 Act WNL web page: http://wnl.ece.cornell.edu ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- On Wed, 9 Jul 2003, Ram Ramanathan wrote: > > > Date: Wed, 09 Jul 2003 10:02:24 -0700 > > From: Mineo Takai > > 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: Ram Ramanathan > > Cc: manet@ietf.org > > Subject: Re: [manet] Carrier sense threshold/range control > > References: <20030709160835.558791D14D@crystal.bbn.com> <3F0C3FD6.4050203@cs.ucla.edu> > > Content-Type: text/plain; charset=us-ascii; format=flowed > > Content-Transfer-Encoding: 7bit > > X-Spam-Status: NO > > X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) > > X-Scanned-By: MIMEDefang 2.19 (www . roaringpenguin . com / mimedefang) > > > > .. SNIP.. > > > > I'm not saying physical carrier sense is useless (In fact, I think it's very > > useful). Virtual carrier sense (RTS/CTS) is not a perfect solution either and > > comes with big overheads. > > > > Mineo > > > Precisely. RTS/CTS also has the exposed terminal problem which is akin > to being over-conservative on the sensing threshold (although not quite > as bad). From your slides it seems like they are kind of competitive even > if CS range is less than twice Comm range. > > So if I have two crummy mechanisms, why not choose the simpler one:) > > I am not arguing a case here. Just wanted to know if someone has done > a detailed comparision. Your tutorial comes closest, but is there a paper? > > -Ram. > > > _______________________________________________ > 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 Jul 9 16:40:55 2003 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 QAA20898 for ; Wed, 9 Jul 2003 16:40:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aLjk-0001om-2W for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 16:40:28 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69KeOs1006984 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 16:40:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aLjj-0001oZ-Vn for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 16:40: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 QAA20866 for ; Wed, 9 Jul 2003 16:40:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aLji-00038U-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 16:40:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aLjh-00038R-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 16:40:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aLjP-0001iX-62; Wed, 09 Jul 2003 16:40:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aLiR-0001eW-9i for manet@optimus.ietf.org; Wed, 09 Jul 2003 16:39: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 QAA20839 for ; Wed, 9 Jul 2003 16:38:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aLiO-00037r-00 for manet@ietf.org; Wed, 09 Jul 2003 16:39:00 -0400 Received: from pit.erg.sri.com ([128.18.100.28]) by ietf-mx with esmtp (Exim 4.12) id 19aLiN-00037O-00 for manet@ietf.org; Wed, 09 Jul 2003 16:38:59 -0400 Received: from pit.erg.sri.com (localhost [127.0.0.1]) by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id NAA27054; Wed, 9 Jul 2003 13:34:24 -0700 (PDT) Message-Id: <200307092034.NAA27054@pit.erg.sri.com> To: "haas@ece.cornell.edu" cc: Ram Ramanathan , Mineo Takai , manet@ietf.org Reply-To: ogier@erg.sri.com From: ogier@erg.sri.com Subject: Re: [manet] Carrier sense threshold/range control In-reply-to: Your message of "Wed, 09 Jul 2003 15:51:43 EDT." Date: Wed, 09 Jul 2003 13:34:24 -0700 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , > Hi Ram, > > Actually, that's not entirely correct - the RTS/CTS dialogue will *in > principle* solve both the hidden- and the exposed-terminal problems. The > issue is that in practical situations it may fail, more specifically when > some of the control messages (RTS or CTS) are lost due to transmission > errors, mobility, etc. The problem with exposed terminals is that a node does not transmit even when it should (the opposite of the hidden terminal problem). RTS/CTS and CS both have the exposed terminal problem. Here is an illustration of the exposed terminal problem: http://pcl.cs.ucla.edu/slides/workshop99/Ken-pw99/sld009.htm Richard > > There are a few papers relevant here. The first is the original MACA paper > by Phil Karn that discusses the use of RTS/CTS instead of CS. The next is > the MACAW paper that solves some residual problems for an indoor IR network > (fairness, etc). Finally, there is our Dual Busy Tone Multiple Access > (DBTMA) paper: > > Zygmunt J. Haas and Jing Deng, "Dual Busy Tone Multiple Access (DBTMA) > - A Multiple Access Control for Ad Hoc Networks," IEEE Transactions on > Communications, vol. 50, no. 6, June 2002, pp. 975-985 > > which you can dowload from our web page at: > http://wnl.ece.cornell.edu/wnlprojects.html > and which contains the references to the MACA and the MACAW papers. > > Best, > > 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 > Act WNL web page: http://wnl.ece.cornell.edu > ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- > > > > On Wed, 9 Jul 2003, Ram Ramanathan wrote: > > > > > > Date: Wed, 09 Jul 2003 10:02:24 -0700 > > > From: Mineo Takai > > > User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/2 0030208 Netscape/7.02 > > > X-Accept-Language: en-us, en > > > MIME-Version: 1.0 > > > To: Ram Ramanathan > > > Cc: manet@ietf.org > > > Subject: Re: [manet] Carrier sense threshold/range control > > > References: <20030709160835.558791D14D@crystal.bbn.com> <3F0C3FD6.4050203@cs. ucla.edu> > > > Content-Type: text/plain; charset=us-ascii; format=flowed > > > Content-Transfer-Encoding: 7bit > > > X-Spam-Status: NO > > > X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) > > > X-Scanned-By: MIMEDefang 2.19 (www . roaringpenguin . com / mimedefang) > > > > > > > .. SNIP.. > > > > > > > I'm not saying physical carrier sense is useless (In fact, I think it's very > > > useful). Virtual carrier sense (RTS/CTS) is not a perfect solution either and > > > comes with big overheads. > > > > > > Mineo > > > > > > Precisely. RTS/CTS also has the exposed terminal problem which is akin > > to being over-conservative on the sensing threshold (although not quite > > as bad). From your slides it seems like they are kind of competitive even > > if CS range is less than twice Comm range. > > > > So if I have two crummy mechanisms, why not choose the simpler one:) > > > > I am not arguing a case here. Just wanted to know if someone has done > > a detailed comparision. Your tutorial comes closest, but is there a paper? > > > > -Ram. > > > > > > _______________________________________________ > > 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 Wed Jul 9 16:48:36 2003 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 QAA21349 for ; Wed, 9 Jul 2003 16:48:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aLrF-0003AA-DB for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 16:48:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69Km9Zs012098 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 16:48:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aLrF-00038K-4Z for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 16:48: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 QAA21322 for ; Wed, 9 Jul 2003 16:48:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aLrD-0003Gg-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 16:48:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aLrC-0003Gd-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 16:48:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aLr8-00033h-Kb; Wed, 09 Jul 2003 16:48:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aLqE-00032k-Kg for manet@optimus.ietf.org; Wed, 09 Jul 2003 16:47: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 QAA21294 for ; Wed, 9 Jul 2003 16:47:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aLqC-0003Fy-00 for manet@ietf.org; Wed, 09 Jul 2003 16:47:04 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 19aLqB-0003Fv-00 for manet@ietf.org; Wed, 09 Jul 2003 16:47:04 -0400 Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 117AC1E4030; Wed, 9 Jul 2003 16:58:21 -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 h69Kl3g05434; Wed, 9 Jul 2003 16:47:03 -0400 Date: Wed, 9 Jul 2003 16:45:50 -0400 (EDT) From: "haas@ece.cornell.edu" To: ogier@erg.sri.com Cc: Ram Ramanathan , Mineo Takai , manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control In-Reply-To: <200307092034.NAA27054@pit.erg.sri.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 Richard, On Wed, 9 Jul 2003 ogier@erg.sri.com wrote: > > Actually, that's not entirely correct - the RTS/CTS dialogue will *in > > principle* solve both the hidden- and the exposed-terminal problems. The > > issue is that in practical situations it may fail, more specifically when > > some of the control messages (RTS or CTS) are lost due to transmission > > errors, mobility, etc. > > The problem with exposed terminals is that a node does not transmit > even when it should (the opposite of the hidden terminal problem). > RTS/CTS and CS both have the exposed terminal problem. > Here is an illustration of the exposed terminal problem: > http://pcl.cs.ucla.edu/slides/workshop99/Ken-pw99/sld009.htm Yes, CS has the exposed terminal problem, but not RTS/CTS. In the slide that you have referenced, B transmits to A and C wants to transmit to D. When B send the RTS, it (temporarily) disables C from transmitting (for the duration of the RTS/CTS dialogue *only*). When A replies with CTS, this CTS is NOT heard by C (it is out of range), thus this CTS does not disable C from issuing RTS to D and (after this RTS/CTS dialogue concludes) transmit to D. The bottom line, B can send to A while C sends to D; i.e., no exposed terminal exists here. All this is in the original paper by Phil Karn on MACA. However, RTS/CTS dialogue will fail to solve the hidden-terminal problem due to issues such as transmission errors, propagation delay, mobility, etc. Zygmunt. ==-=-==== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Prof. Zygmunt J. Haas http://people.ece.cornell.edu/haas Wireless Networks Laboratory http://wnl.ece.cornell.edu School of Electrical Engineering Cornell University tel: +1-607-255-3454 323 Frank Rhodes Hall fax: +1-607-255-9072 Ithaca, NY 14853 e-mail: haas@ece.cornell.edu U.S.A WNL web page: http://wnl.ece.cornell.edu ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 17:34:56 2003 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 RAA23200 for ; Wed, 9 Jul 2003 17:34:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMa0-0007PZ-Ow for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 17:34:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69LYOjQ028488 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 17:34:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMa0-0007PP-Ff for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 17: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 RAA23183 for ; Wed, 9 Jul 2003 17:34:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aMZy-0003mc-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 17:34:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aMZx-0003mZ-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 17:34:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMZd-0007Ir-MB; Wed, 09 Jul 2003 17:34:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMYl-0007IL-V7 for manet@optimus.ietf.org; Wed, 09 Jul 2003 17:33: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 RAA23169 for ; Wed, 9 Jul 2003 17:33:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aMYj-0003mG-00 for manet@ietf.org; Wed, 09 Jul 2003 17:33:05 -0400 Received: from mailer.cacs.louisiana.edu ([130.70.72.22]) by ietf-mx with esmtp (Exim 4.12) id 19aMYi-0003mD-00 for manet@ietf.org; Wed, 09 Jul 2003 17:33:04 -0400 Received: from swamp450.cacs.louisiana.edu (swamp450.cacs.louisiana.edu [130.70.75.99]) by mailer.cacs.louisiana.edu (8.11.3/8.11.3) with ESMTP id h69LP1r26276; Wed, 9 Jul 2003 16:25:01 -0500 (CDT) Date: Wed, 9 Jul 2003 16:25:01 -0500 (CDT) From: "Dmitri D. Perkins" To: "haas@ece.cornell.edu" cc: ogier@erg.sri.com, Ram Ramanathan , Mineo Takai , Subject: Re: [manet] Carrier sense threshold/range control 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: , Dr. Haas, Using the illustration referenced and assuming an RTS/CTS/DATA/ACK transmission scenario, the RTS must disable all nodes within range of B (since B must also recieve an ACK from A). Using the same illustration, if C is allowed transmit to D while B is transmitting to A, how will be B receive and ACK from A? It may now send C's transmission will like interfere. Thus, the duration field of the RTS message must forced neigboring nodes to remain silent long enough for the sender (node B) to receive a CTS from node A + send a data frame to node A + recv an ACK from node A. The RTS duration field will also need to account for DIFS and SIFS (interframe spacing). Now, if no ACK (an unreliable MAC) are used C should be allowed to transmit, but performance will suffer due to wireless channel effects. Thanks, Dmitri Perkins ================================================== Dr. Dmitri D. Perkins, Assistant Professor The Center for Advanced Computer Studies University of Louisiana at Lafayette P.O. Box 44330, Lafayette, LA 70504-4330 office: (337)482-6732 fax: (337)482-5791 http://www.cacs.louisiana.edu/~perkins ================================================== On Wed, 9 Jul 2003, haas@ece.cornell.edu wrote: > Hi Richard, > > On Wed, 9 Jul 2003 ogier@erg.sri.com wrote: > > > Actually, that's not entirely correct - the RTS/CTS dialogue will *in > > > principle* solve both the hidden- and the exposed-terminal problems. The > > > issue is that in practical situations it may fail, more specifically when > > > some of the control messages (RTS or CTS) are lost due to transmission > > > errors, mobility, etc. > > > > The problem with exposed terminals is that a node does not transmit > > even when it should (the opposite of the hidden terminal problem). > > RTS/CTS and CS both have the exposed terminal problem. > > Here is an illustration of the exposed terminal problem: > > http://pcl.cs.ucla.edu/slides/workshop99/Ken-pw99/sld009.htm > > Yes, CS has the exposed terminal problem, but not RTS/CTS. In the slide > that you have referenced, B transmits to A and C wants to transmit to D. > When B send the RTS, it (temporarily) disables C from transmitting (for > the duration of the RTS/CTS dialogue *only*). When A replies with CTS, > this CTS is NOT heard by C (it is out of range), thus this CTS does not > disable C from issuing RTS to D and (after this RTS/CTS dialogue > concludes) transmit to D. > > The bottom line, B can send to A while C sends to D; i.e., no exposed > terminal exists here. > > All this is in the original paper by Phil Karn on MACA. > > However, RTS/CTS dialogue will fail to solve the hidden-terminal problem > due to issues such as transmission errors, propagation delay, mobility, etc. > > Zygmunt. > ==-=-==== > ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- > Prof. Zygmunt J. Haas http://people.ece.cornell.edu/haas > Wireless Networks Laboratory http://wnl.ece.cornell.edu > School of Electrical Engineering > Cornell University tel: +1-607-255-3454 > 323 Frank Rhodes Hall fax: +1-607-255-9072 > Ithaca, NY 14853 e-mail: haas@ece.cornell.edu > U.S.A > WNL web page: http://wnl.ece.cornell.edu > ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- > > > > _______________________________________________ > 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 Jul 9 17:38:43 2003 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 RAA23407 for ; Wed, 9 Jul 2003 17:38:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMdk-00084H-JP for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 17:38:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69LcG0s031002 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 17:38:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMdk-00083x-1e for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 17:38: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 RAA23376 for ; Wed, 9 Jul 2003 17:38:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aMdf-0003r8-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 17:38:11 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aMde-0003r5-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 17:38:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMdV-0007x5-Qv; Wed, 09 Jul 2003 17:38:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMdA-0007s2-HZ for manet@optimus.ietf.org; Wed, 09 Jul 2003 17:37: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 RAA23353 for ; Wed, 9 Jul 2003 17:37:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aMd8-0003qc-00 for manet@ietf.org; Wed, 09 Jul 2003 17:37:38 -0400 Received: from smtpproxy2.mitre.org ([192.80.55.70]) by ietf-mx with esmtp (Exim 4.12) id 19aMd7-0003qZ-00 for manet@ietf.org; Wed, 09 Jul 2003 17:37:37 -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 h69LbR6r023390; Wed, 9 Jul 2003 17:37:27 -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 h69LbQOD014648; Wed, 9 Jul 2003 17:37:26 -0400 (EDT) Received: from m29103-pc.mitre.org (128.29.55.52) by mailhub1.mitre.org with SMTP id 3284237; Wed, 09 Jul 2003 17:37:22 -0400 Message-ID: <3F0C8B10.F86A1785@mitre.org> Date: Wed, 09 Jul 2003 17:37:20 -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: "haas@ece.cornell.edu" CC: ogier@erg.sri.com, Ram Ramanathan , Mineo Takai , manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control 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 "haas@ece.cornell.edu" wrote: > Hi Richard, > > On Wed, 9 Jul 2003 ogier@erg.sri.com wrote: > > > Actually, that's not entirely correct - the RTS/CTS dialogue will *in > > > principle* solve both the hidden- and the exposed-terminal problems. The > > > issue is that in practical situations it may fail, more specifically when > > > some of the control messages (RTS or CTS) are lost due to transmission > > > errors, mobility, etc. > > > > The problem with exposed terminals is that a node does not transmit > > even when it should (the opposite of the hidden terminal problem). > > RTS/CTS and CS both have the exposed terminal problem. > > Here is an illustration of the exposed terminal problem: > > http://pcl.cs.ucla.edu/slides/workshop99/Ken-pw99/sld009.htm > > Yes, CS has the exposed terminal problem, but not RTS/CTS. In the slide > that you have referenced, B transmits to A and C wants to transmit to D. > When B send the RTS, it (temporarily) disables C from transmitting (for > the duration of the RTS/CTS dialogue *only*). When A replies with CTS, > this CTS is NOT heard by C (it is out of range), thus this CTS does not > disable C from issuing RTS to D and (after this RTS/CTS dialogue > concludes) transmit to D. But won't C have to wait for a DIFS after the RTS/CTS NAV resulting in enough time for B to start sending its packet prior to C sending an RTS. C will have to defer again. The classic example of an exposed node is the node on a mountain that can hear two disjoint sections of a network on either side of the mountain. Call the set of nodes on one side of the mountain Network A and the nodes on the opposite side Network B. Nodes in Network A cannot hear Network B and vise versa. The exposed node hears both. The exposed node is at a disadvantage in gaining access and in receiving packets. In order for this node to transmit or receive both sides must be silent. The latter is not as obvious. If a node in network A sends an RTS to the exposed node and a transmission is already occurring in Network B, the exposed node cannot respond with a CTS since this may interfere with the reception in Network B. Thus the exposed node defers from responding. The node that sent the RTS to the exposed node chalks it up as a failure and retries. It will be pure chance that the node in network A will initiate a transmission to the exposed node during a period when Network B is silent. Certainly if Network B is silent and the exposed node receives the RTS from a node in Network A then the exposed node's CTS will silence Network B. Geography is not the only thing that can expose a node. Disjoint packet flows in an ad hoc network may also cause a node that hears both to be effectively exposed. The RTS/CTS handshake does nothing to prevent this exposure and exacerbates the problem because of the virtual sensing requirement. > > > The bottom line, B can send to A while C sends to D; i.e., no exposed > terminal exists here. > > All this is in the original paper by Phil Karn on MACA. > > However, RTS/CTS dialogue will fail to solve the hidden-terminal problem > due to issues such as transmission errors, propagation delay, mobility, etc. > > Zygmunt. > ==-=-==== > ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- > Prof. Zygmunt J. Haas http://people.ece.cornell.edu/haas > Wireless Networks Laboratory http://wnl.ece.cornell.edu > School of Electrical Engineering > Cornell University tel: +1-607-255-3454 > 323 Frank Rhodes Hall fax: +1-607-255-9072 > Ithaca, NY 14853 e-mail: haas@ece.cornell.edu > U.S.A > WNL web page: http://wnl.ece.cornell.edu > ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- > > _______________________________________________ > 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 Jul 9 17:41:37 2003 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 RAA23655 for ; Wed, 9 Jul 2003 17:41:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMgY-00008C-R0 for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 17:41:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69LfAZO000502 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 17:41:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMgY-000081-N5 for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 17:41: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 RAA23617 for ; Wed, 9 Jul 2003 17:41:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aMgW-0003w9-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 17:41:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aMgV-0003w6-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 17:41:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMgP-0008Vz-01; Wed, 09 Jul 2003 17:41:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aMgF-0008VF-Bb for manet@optimus.ietf.org; Wed, 09 Jul 2003 17:40: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 RAA23585 for ; Wed, 9 Jul 2003 17:40:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aMgC-0003vd-00 for manet@ietf.org; Wed, 09 Jul 2003 17:40:48 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 19aMgB-0003vX-00 for manet@ietf.org; Wed, 09 Jul 2003 17:40:48 -0400 Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 95FD71E4030; Wed, 9 Jul 2003 17:52:05 -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 h69Lelg06762; Wed, 9 Jul 2003 17:40:47 -0400 Date: Wed, 9 Jul 2003 17:39:34 -0400 (EDT) From: "haas@ece.cornell.edu" To: "Dmitri D. Perkins" Cc: ogier@erg.sri.com, Ram Ramanathan , Mineo Takai , manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control 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 Dmitri, On Wed, 9 Jul 2003, Dmitri D. Perkins wrote: > Using the illustration referenced and assuming an RTS/CTS/DATA/ACK > transmission scenario, the RTS must disable all nodes within range of > B (since B must also recieve an ACK from A). Using the same illustration, > if C is allowed transmit to D while B is transmitting to A, how will be > B receive and ACK from A? It may now send C's transmission will like > interfere. Please note that I referred to the RTS/CTS dialogue only, and not to the RTS/CTS/DATA/ACK exchange. In the former, there is no need for RTS to disable the nodes around the transmitter for more than the duration of the RTS/CTS exchange only. Thus, while B transmits DATA to A, C is not disabled and can transmit to A. You are correct in saying that RTS/CTS/DATA/ACK dialogue requires to disable nodes around both, the transmitter and the receiver, just to cover the ACK going back to the transmitter. But this is not the case in "pure" RTS/CTS dialogue, where the ACK can be sent on higher layer than the MAC. Hopes this clarifies the issue. 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 ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 18:05:47 2003 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 SAA24850 for ; Wed, 9 Jul 2003 18:05: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 19aN3w-00021E-Ay for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 18:05:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69M5KeD007760 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 18:05:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aN3w-000215-6u for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 18:05: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 SAA24790 for ; Wed, 9 Jul 2003 18:05:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aN3t-0004DB-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:05:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aN3t-0004D8-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:05:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aN3d-0001tu-HI; Wed, 09 Jul 2003 18:05:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aN34-0001pN-Rg for manet@optimus.ietf.org; Wed, 09 Jul 2003 18:04: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 SAA24666 for ; Wed, 9 Jul 2003 18:04:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aN32-0004CQ-00 for manet@ietf.org; Wed, 09 Jul 2003 18:04:24 -0400 Received: from amber.crhc.uiuc.edu ([130.126.143.254]) by ietf-mx with esmtp (Exim 4.12) id 19aN30-0004Bx-00 for manet@ietf.org; Wed, 09 Jul 2003 18:04:23 -0400 Received: from godel.crhc.uiuc.edu (godel.crhc.uiuc.edu [130.126.142.150]) by amber.crhc.uiuc.edu (8.12.9/8.12.9) with ESMTP id h69M3u5x022241 for ; Wed, 9 Jul 2003 17:03:56 -0500 (CDT) Received: from localhost (nhv@localhost) by godel.crhc.uiuc.edu (8.11.6/8.11.6) with ESMTP id h69M3oq05591 for ; Wed, 9 Jul 2003 17:03:50 -0500 X-Authentication-Warning: godel.crhc.uiuc.edu: nhv owned process doing -bs Date: Wed, 9 Jul 2003 17:03:50 -0500 (CDT) From: "Nitin H. Vaidya" To: MANET mailing list In-Reply-To: <20030709213400.28070.58574.Mailman@www1.ietf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Re: Carrier sense threshold/range control Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Reading manet mails in digest mode .... so comments on several messages lumped together. . >>From: Ram Ramanathan . >> . >>To elaborate, the threshold for when carrier is declared to be "sensed" . >>can be adjusted in many radios. Using this facility, one could possibly . >>make the "carrier sense range" approximately twice the "communication range" . >>(successful packet reception), and detect hidden nodes. If I recall correctly, the paper on Wavelan (the first Wavelan) that appeared in Bell Labs journal (AT&T journal, or whatever it was called at the time), shows a picture that matches with your discussion above. I think they chose a carrier sense range twice that of the transmission range -- it seems that the Bell Labs Tehcnical Journal has disappeared from the web, so I cannot find the paper (which was written by Bruce Tuch). . >>From: "haas@ece.cornell.edu" . >> . >>Actually, that's not entirely correct - the RTS/CTS dialogue will *in . >>principle* solve both the hidden- and the exposed-terminal problems. The It will solve the hidden terminal problem if the nodes that interfere with the reception at a host R are also the nodes that reliably receive the transmission of CTS from host R -- this may not the case. . >>From: "Dmitri D. Perkins" . >> . >>Dr. Haas, . >> . >>Using the illustration referenced and assuming an RTS/CTS/DATA/ACK . >>transmission scenario, the RTS must disable all nodes within range of . >>B (since B must also recieve an ACK from A). Using the same illustration, . >>if C is allowed transmit to D while B is transmitting to A, how will be . >>B receive and ACK from A? It may now send C's transmission will like . >>interfere. . >> . >>Thus, the duration field of the RTS message must forced neigboring nodes . >>to remain silent long enough for the sender (node B) to receive a CTS from . >>node A + send a data frame to node A + recv an ACK from node A. The RTS . >>duration field will also need to account for DIFS and SIFS (interframe . >>spacing). . >> . >>Now, if no ACK (an unreliable MAC) are used C should be allowed to . >>transmit, but performance will suffer due to wireless channel effects. Zygmunt is refering to MACA I think, whereas you might be refering to 802.11. Both are right, of course, Incidentally, 802.11 is conservative in the manner in which collisions with ACKs are prevented (neighbors of the senders only need disable transmissions during the ACK reception at the sender, but 802.11 disables them for the entire transaction -- that simplifies NAV maintenance). - nitin _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 18:10:35 2003 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 SAA25454 for ; Wed, 9 Jul 2003 18:10: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 19aN8b-0002cY-2I for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 18:10:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69MA94W010056 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 18:10:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aN8a-0002c7-G3 for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 18:10: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 SAA25408 for ; Wed, 9 Jul 2003 18:10:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aN8X-0004I5-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:10:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aN8X-0004I2-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:10:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aN8T-0002at-OF; Wed, 09 Jul 2003 18: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 19aN8N-0002aI-Mp for manet@optimus.ietf.org; Wed, 09 Jul 2003 18: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 SAA25383 for ; Wed, 9 Jul 2003 18:09:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aN8K-0004Hm-00 for manet@ietf.org; Wed, 09 Jul 2003 18:09:53 -0400 Received: from tiquini.ece.arizona.edu ([128.196.29.23]) by ietf-mx with esmtp (Exim 4.12) id 19aN8J-0004Hj-00 for manet@ietf.org; Wed, 09 Jul 2003 18:09:52 -0400 Received: from tiquini (tiquini [128.196.29.23]) by tiquini.ece.arizona.edu (8.12.9/8.12.9) with ESMTP id h69M9KI2009351; Wed, 9 Jul 2003 15:09:21 -0700 (MST) Received: from DHCP-140.ece.arizona.edu ([150.135.222.140]) by tiquini.ece.arizona.edu (MailMonitor for SMTP v1.2.2 ) ; Wed, 9 Jul 2003 15:09:20 -0700 (MST) Message-ID: <004701c34666$d06e1670$8cde8796@arizonaalaa> Reply-To: "Alaa Muqattash" From: "Alaa Muqattash" To: , "Dmitri D. Perkins" Cc: , "Ram Ramanathan" , "Mineo Takai" , References: Subject: Re: [manet] Carrier sense threshold/range control Date: Wed, 9 Jul 2003 15:09:49 -0700 Organization: The University of Arizona MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Prof Haas, So the "pure" RTS/CTS dialogue, where the ACK can be sent on higher layer than the MAC is *end-to-end* reliability mechanism. A more efficient method is to use ACK in *each hop* transmission. This would require the MAC layer to send back the ACK (and not any upper layer), thus, the RTS must silence nodes in the vicinity of the transmitter. The question is: Would the advantage MAC reliability (each hop ACK)offset the disadvantage of reserving the floor around the transmitter? Best regards, Alaa Muqattash ================================================= Alaa Muqattash Ph.D. Student & Research Assistant Broadband Networking Laboratory Dept. of Electrical & Computer Engineering The University of Arizona Rm. 109, ECE Bldg. Tucson AZ 85721 Tel : (520) 626-9249 Fax : (520) 621-3862 Email : alaa@ece.arizona.edu Web: http://www.ece.arizona.edu/~alaa/ "Imagination is more important than knowledge" Albert Einstein ================================================= ----- Original Message ----- From: To: "Dmitri D. Perkins" Cc: ; "Ram Ramanathan" ; "Mineo Takai" ; Sent: Wednesday, July 09, 2003 2:39 PM Subject: Re: [manet] Carrier sense threshold/range control > Hi Dmitri, > > On Wed, 9 Jul 2003, Dmitri D. Perkins wrote: > > Using the illustration referenced and assuming an RTS/CTS/DATA/ACK > > transmission scenario, the RTS must disable all nodes within range of > > B (since B must also recieve an ACK from A). Using the same illustration, > > if C is allowed transmit to D while B is transmitting to A, how will be > > B receive and ACK from A? It may now send C's transmission will like > > interfere. > > Please note that I referred to the RTS/CTS dialogue only, and not to the > RTS/CTS/DATA/ACK exchange. In the former, there is no need for RTS to disable > the nodes around the transmitter for more than the duration of the RTS/CTS > exchange only. Thus, while B transmits DATA to A, C is not disabled and > can transmit to A. > > You are correct in saying that RTS/CTS/DATA/ACK dialogue requires to > disable nodes around both, the transmitter and the receiver, just to cover > the ACK going back to the transmitter. But this is not the case in "pure" > RTS/CTS dialogue, where the ACK can be sent on higher layer than the MAC. > > Hopes this clarifies the issue. > > 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 > ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- > > > > _______________________________________________ > 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 Jul 9 18:18:43 2003 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 SAA26453 for ; Wed, 9 Jul 2003 18:18:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNGT-0003Lm-SP for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 18:18:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69MIHC8012872 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 18:18:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNGT-0003LX-Nr for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 18:18: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 SAA26415 for ; Wed, 9 Jul 2003 18:18:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNGQ-0004QN-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:18:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aNGQ-0004QK-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:18:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNGD-0003Eb-Hj; Wed, 09 Jul 2003 18:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNG7-0003DW-60 for manet@optimus.ietf.org; Wed, 09 Jul 2003 18:17: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 SAA26387 for ; Wed, 9 Jul 2003 18:17:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNG4-0004Pk-00 for manet@ietf.org; Wed, 09 Jul 2003 18:17:52 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 19aNG3-0004Ph-00 for manet@ietf.org; Wed, 09 Jul 2003 18:17:51 -0400 Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 0F0521E4030; Wed, 9 Jul 2003 18:29:10 -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 h69MHpg07613; Wed, 9 Jul 2003 18:17:51 -0400 Date: Wed, 9 Jul 2003 18:16:39 -0400 (EDT) From: "haas@ece.cornell.edu" To: Alaa Muqattash Cc: manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control In-Reply-To: <004701c34666$d06e1670$8cde8796@arizonaalaa> 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 Alaa, On Wed, 9 Jul 2003, Alaa Muqattash wrote: > The question is: Would the > advantage MAC reliability (each hop ACK)offset the disadvantage of reserving > the floor around the transmitter? There is no simple answer to your question - it depends on the various parameters of the system, such as the success prob of a single hop, the (end-to-end) path length, etc. Zygmunt. ==-=-==== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Prof. Zygmunt J. Haas http://people.ece.cornell.edu/haas Wireless Networks Laboratory http://wnl.ece.cornell.edu School of Electrical Engineering Cornell University tel: +1-607-255-3454 323 Frank Rhodes Hall fax: +1-607-255-9072 Ithaca, NY 14853 e-mail: haas@ece.cornell.edu U.S.A WNL web page: http://wnl.ece.cornell.edu ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 18:20:48 2003 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 SAA26596 for ; Wed, 9 Jul 2003 18:20:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNIU-0003fZ-Mi for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 18:20:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69MKM3b014102 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 18:20:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNIU-0003fN-J1 for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 18:20:22 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26581 for ; Wed, 9 Jul 2003 18:20:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNIR-0004Tq-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:20:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aNIR-0004Tn-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:20:19 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNIA-0003Ye-N6; Wed, 09 Jul 2003 18: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 19aNHc-0003X7-Fl for manet@optimus.ietf.org; Wed, 09 Jul 2003 18:19: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 SAA26537 for ; Wed, 9 Jul 2003 18:19:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNHZ-0004T6-00 for manet@ietf.org; Wed, 09 Jul 2003 18:19:25 -0400 Received: from mailer.cacs.louisiana.edu ([130.70.72.22]) by ietf-mx with esmtp (Exim 4.12) id 19aNHY-0004T3-00 for manet@ietf.org; Wed, 09 Jul 2003 18:19:24 -0400 Received: from swamp450.cacs.louisiana.edu (swamp450.cacs.louisiana.edu [130.70.75.99]) by mailer.cacs.louisiana.edu (8.11.3/8.11.3) with ESMTP id h69MJMr27072; Wed, 9 Jul 2003 17:19:23 -0500 (CDT) Date: Wed, 9 Jul 2003 17:19:22 -0500 (CDT) From: "Dmitri D. Perkins" To: "Nitin H. Vaidya" cc: MANET mailing list Subject: Re: [manet] Re: Carrier sense threshold/range control 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: , ================================================== Dr. Dmitri D. Perkins, Assistant Professor The Center for Advanced Computer Studies University of Louisiana at Lafayette P.O. Box 44330, Lafayette, LA 70504-4330 office: (337)482-6732 fax: (337)482-5791 http://www.cacs.louisiana.edu/~perkins ================================================== On Wed, 9 Jul 2003, Nitin H. Vaidya wrote: > > Reading manet mails in digest mode .... so comments on several > messages lumped together. > > . >>From: Ram Ramanathan > . >> > . >>To elaborate, the threshold for when carrier is declared to be "sensed" > . >>can be adjusted in many radios. Using this facility, one could possibly > . >>make the "carrier sense range" approximately twice the "communication range" > . >>(successful packet reception), and detect hidden nodes. > > If I recall correctly, the paper on Wavelan (the first Wavelan) that > appeared in Bell Labs journal (AT&T journal, or whatever it was called > at the time), shows a picture that matches with your discussion above. > I think they chose a carrier sense range twice that of the transmission > range -- it seems that the Bell Labs Tehcnical Journal has disappeared > from the web, so I cannot find the paper (which was written by Bruce > Tuch). > > . >>From: "haas@ece.cornell.edu" > . >> > . >>Actually, that's not entirely correct - the RTS/CTS dialogue will *in > . >>principle* solve both the hidden- and the exposed-terminal problems. The > > It will solve the hidden terminal problem if the nodes that > interfere with the reception at a host R are also the nodes > that reliably receive the transmission of CTS from host R -- this > may not the case. > > . >>From: "Dmitri D. Perkins" > . >> > . >>Dr. Haas, > . >> > . >>Using the illustration referenced and assuming an RTS/CTS/DATA/ACK > . >>transmission scenario, the RTS must disable all nodes within range of > . >>B (since B must also recieve an ACK from A). Using the same illustration, > . >>if C is allowed transmit to D while B is transmitting to A, how will be > . >>B receive and ACK from A? It may now send C's transmission will like > . >>interfere. > . >> > . >>Thus, the duration field of the RTS message must forced neigboring nodes > . >>to remain silent long enough for the sender (node B) to receive a CTS from > . >>node A + send a data frame to node A + recv an ACK from node A. The RTS > . >>duration field will also need to account for DIFS and SIFS (interframe > . >>spacing). > . >> > . >>Now, if no ACK (an unreliable MAC) are used C should be allowed to > . >>transmit, but performance will suffer due to wireless channel effects. > > Zygmunt is refering to MACA I think, whereas you might be refering > to 802.11. Both are right, of course, Incidentally, 802.11 is > conservative in the manner in which collisions with ACKs are prevented > (neighbors of the senders only need disable transmissions during the > ACK reception at the sender, but 802.11 disables them for the entire > transaction -- that simplifies NAV maintenance). > > - nitin > > > _______________________________________________ > 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 Jul 9 18:23:34 2003 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 SAA26712 for ; Wed, 9 Jul 2003 18:23: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 19aNLA-0003xR-Ol for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 18:23:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69MN8bB015209 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 18:23:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNLA-0003xE-Lt for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 18:23: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 SAA26706 for ; Wed, 9 Jul 2003 18:23:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNL7-0004Wt-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:23:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aNL7-0004Wq-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:23:05 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNL3-0003tS-UE; Wed, 09 Jul 2003 18: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 19aNKo-0003sO-TM for manet@optimus.ietf.org; Wed, 09 Jul 2003 18:22: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 SAA26691 for ; Wed, 9 Jul 2003 18:22:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNKl-0004WY-00 for manet@ietf.org; Wed, 09 Jul 2003 18:22:43 -0400 Received: from mta02.alltel.net ([166.102.165.144] helo=mta02-srv.alltel.net) by ietf-mx with esmtp (Exim 4.12) id 19aNKl-0004WV-00 for manet@ietf.org; Wed, 09 Jul 2003 18:22:43 -0400 Received: from BLUETRONIX001 ([162.40.170.227]) by mta02-srv.alltel.net with SMTP id <20030709222241.LRYJ1656.mta02-srv.alltel.net@BLUETRONIX001> for ; Wed, 9 Jul 2003 17:22:41 -0500 Message-ID: <016f01c34668$9c2465c0$72d6fea9@BLUETRONIX001> From: "mark j heiferling" To: References: <20030707160003.2950.43085.Mailman@www1.ietf.org> Date: Wed, 9 Jul 2003 18:22:40 -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 Subject: [manet] Re: manet digest, Vol 1 #481 - 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: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit martin you're ware of this mailing list right? ----- Original Message ----- From: To: Sent: Monday, July 07, 2003 12:00 PM Subject: manet digest, Vol 1 #481 - 4 msgs > Send manet mailing list submissions to > manet@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www1.ietf.org/mailman/listinfo/manet > or, via email, send a message with subject or body 'help' to > manet-request@ietf.org > > You can reach the person managing the list at > manet-admin@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of manet digest..." > > > Today's Topics: > > 1. About changing bandwidth (skame) > 2. Re: About changing bandwidth (Fethi Filali) > 3. (no subject) (Karun Verma) > 4. CFP:: First International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2004) (Atsushi Inoue) > > --__--__-- > > Message: 1 > Date: Mon, 7 Jul 2003 18:18:54 +0900 > From: skame > To: manet@ietf.org > Cc: syoshida@net.ie.niigata-u.ac.jp > Subject: [manet] About changing bandwidth > > Hi,all. > > I want to know the way of changing bandwidth. > The defalut bandwidth in ns2 is 2[Mb/s]. > I suppose 802.11b in maclayer. > Now bandwidth in 802.11b is 11[Mb/s]. > So I want to change the bandwidth from 2[Mb/s] to 11[Mb/s]. > Please tell me how to change bandwidth. > > Thank you. > skame > > > --__--__-- > > Message: 2 > Date: Mon, 07 Jul 2003 11:59:45 +0200 > From: Fethi Filali > Organization: INRIA Sophia-Antipolis (http://www.inria.fr) > To: skame > CC: manet@ietf.org, syoshida@net.ie.niigata-u.ac.jp > Subject: Re: [manet] About changing bandwidth > > skmae, > > The default rate in ns2 seems to be 1Mb. > > See file ns-2.26/tcl/lan/mac.tcl , u can find the line: > > Mac/802_11 set dataRate_ 1Mb ;# both control and data pkts > > the tcl variable dataRate_ is binded to the c++ variable dataRate_ in > the mac-802_11.cc file > > you can change the default value in mac.tcl and recompiling ns. > > Fethi. > > skame wrote: > > Hi,all. > > > > I want to know the way of changing bandwidth. > > The defalut bandwidth in ns2 is 2[Mb/s]. > > I suppose 802.11b in maclayer. > > Now bandwidth in 802.11b is 11[Mb/s]. > > So I want to change the bandwidth from 2[Mb/s] to 11[Mb/s]. > > Please tell me how to change bandwidth. > > > > Thank you. > > skame > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > --__--__-- > > Message: 3 > From: "Karun Verma" > To: manet@ietf.org > Date: Mon, 07 Jul 2003 16:30:15 +0530 > Subject: [manet] (no subject) > >
>
>

Hello,

>

I want to have some information on SLURP and GLS in Wireless Adhoc networks. Please provide me some links.

>

Karun  

See you

>

Watch Hallmark. Enjoy cool movies. Win hot prizes! > > > --__--__-- > > Message: 4 > To: nemo@nal.motlabs.com, manet@ietf.org, mobile-ip@sunroof.eng.sun.com, > pana@research.telcordia.com > Cc: inoue@isl.rdc.toshiba.co.jp > Date: Mon, 07 Jul 2003 20:15:21 +0900 > From: Atsushi Inoue > Subject: [manet] CFP:: First International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2004) > > (Apologies if you receive multiple copies) > CALL FOR PAPERS > =============== > First International Conference > on Mobile Computing and Ubiquitous Networking (ICMU 2004) > > January 8 and 9, 2004 > NTT DoCoMo R&D Center, Yokosuka Rsearch Park, Yokosuka, JAPAN > http://www.ipsj.or.jp/sig/mbl/icmu2004/ > > Deadline for submissions: August 1 2003 > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Co-sponsored by IPSJ SIG-MBL (Informaiton Processing Society > of Japan, Special Interest Group of Mobile Computing and > Ubiquitous Networking) and IPSJ SG-BCC (Study Group of > Broadcast Communicaiton and Computing) > > Scope: > ~~~~~~ > Mobile computing aims at ubiquitous user access to computer > application. To make it possible, networking technology which enables > Internet access anytime and everywhere, i.e. ubiquitous networking is > necessary. It is obvious that with the accelerating trends towards > mobile networks, ad-hoc networks, and wireless networks, mobile > computing and ubiquitous networking will play an important role in > future network. This conference is aimed at providing researchers and > practitioners in this hot research area a forum for discussion and > collaboration. Authors are invited to submit papers addressing, but > not limited to, the following topics: > > - Applications and services for mobile computing > - Network architectures, protocols, or service models for ubiquitous > networking > - Network management for ubiquitous networking > - Data management for mobile computing > - Security in mobile computing and ubiquitous networking > - Wireless and mobile communications > - Nomadic computing > - Ad-hoc networks > - Mobile Internetworking > - Performance evaluation for mobile computing and ubiquitous > networking systems > - Broadcast communication > > Submission Instructions: > ~~~~~~~~~~~~~~~~~~~~~~~~ > Papers are solicited as full papers of no more than 6 pages, each of > which will be subject to a full review process. Submission should > already follow the author guidelines as specified in the web site > below. An electronic, PDF-based submission of papers is mandatory. > > Please check Submission Guideline > (http://www.ipsj.or.jp/sig/mbl/icmu2004/guide.html) for further > submission instructions. > > Important Dates: > ~~~~~~~~~~~~~~~~ > - Deadline for submissions August 1, 2003 > - Notification of acceptance October 1, 2003 > - Camera ready due November 1, 2003 > - Conference January 8-9, 2004 > > > Location and Date: > ~~~~~~~~~~~~~~~~~~ > The location of the NTT DoCoMo R&D Center is in the heart of Yokosuka > Research Park(YRP) where a lot of wireless communication related > research institutes are established. YRP is really the heart of > wireless communications research in Japan. Japanese old city Kamakura, > a famous historic city, is 30 minutes by train. Beginning of the year > is one of the best seasons for visiting Japan. > > You can also get PDF version of Call for Papers > from http://www.ipsj.or.jp/sig/mbl/icmu2004/cfp-icmu2004.pdf > > > > Atsushi Inoue # Phone: +81-44-549-2065 > Communication Platform Lab. # Fax: +81-44-520-1806 > TOSHIBA R&D Center # inoue@isl.rdc.toshiba.co.jp > > > > > > > > --__--__-- > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > > End of manet Digest > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 18:43:47 2003 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 SAA27274 for ; Wed, 9 Jul 2003 18:43: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 19aNei-00051L-CD for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 18:43:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69MhKuF019293 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 18:43:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNei-000516-8l for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 18:43: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 SAA27262 for ; Wed, 9 Jul 2003 18:43:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNef-0004hQ-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:43:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aNee-0004hN-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:43:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNeQ-0004zi-1O; Wed, 09 Jul 2003 18:43:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNeF-0004zU-EL for manet@optimus.ietf.org; Wed, 09 Jul 2003 18:42: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 SAA27251 for ; Wed, 9 Jul 2003 18:42:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNeC-0004h8-00 for manet@ietf.org; Wed, 09 Jul 2003 18:42:48 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 19aNeB-0004h5-00 for manet@ietf.org; Wed, 09 Jul 2003 18:42:47 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id BD134201D; Wed, 9 Jul 2003 16:42:45 -0600 (MDT) From: "John Mullen" To: "'Alaa Muqattash'" Cc: Subject: RE: [manet] Carrier sense threshold/range control Date: Wed, 9 Jul 2003 16:42:45 -0600 Message-ID: <000101c3466b$6a73e110$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: <004701c34666$d06e1670$8cde8796@arizonaalaa> 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 Alaa, The advantage of the link-by-link ACK is primarily that intermediate nodes can flush the packet from their buffers as soon as they know it has been sent on. Without it, a lot of buffer space can be needlessly tied up. In many cases, and explicit ACK is not needed. Say we have A-B-C and A sends a packet to B intended for C. If B receives the packet and sends it to C, in most cases, A will be able to overhear B's transmission and be able to deduce that B has received the packet. An explicit ACK would be needed for the B-C link because C would not retransmit, so B will set the ACK flag in its transmission. On the other hand, if C would send an end-to-end ACK back to A anyways, B would not need to set the flag. An ACK would also be needed if A did not hear enough of the retransmitted packet to know it is B's relay. Usually, A waits for a timeout and either resends with a request for an explicit ACK. In most cases, however, this is unnecessary, saving the need to ACK. John Mullen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Alaa Muqattash Sent: Wednesday, July 09, 2003 3:10 PM To: haas@ece.cornell.edu; Dmitri D. Perkins Cc: ogier@erg.sri.com; Ram Ramanathan; Mineo Takai; manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control Prof Haas, So the "pure" RTS/CTS dialogue, where the ACK can be sent on higher layer than the MAC is *end-to-end* reliability mechanism. A more efficient method is to use ACK in *each hop* transmission. This would require the MAC layer to send back the ACK (and not any upper layer), thus, the RTS must silence nodes in the vicinity of the transmitter. The question is: Would the advantage MAC reliability (each hop ACK)offset the disadvantage of reserving the floor around the transmitter? Best regards, Alaa Muqattash ================================================= Alaa Muqattash Ph.D. Student & Research Assistant Broadband Networking Laboratory Dept. of Electrical & Computer Engineering The University of Arizona Rm. 109, ECE Bldg. Tucson AZ 85721 Tel : (520) 626-9249 Fax : (520) 621-3862 Email : alaa@ece.arizona.edu Web: http://www.ece.arizona.edu/~alaa/ "Imagination is more important than knowledge" Albert Einstein ================================================= ----- Original Message ----- From: To: "Dmitri D. Perkins" Cc: ; "Ram Ramanathan" ; "Mineo Takai" ; Sent: Wednesday, July 09, 2003 2:39 PM Subject: Re: [manet] Carrier sense threshold/range control > Hi Dmitri, > > On Wed, 9 Jul 2003, Dmitri D. Perkins wrote: > > Using the illustration referenced and assuming an RTS/CTS/DATA/ACK > > transmission scenario, the RTS must disable all nodes within range > > of B (since B must also recieve an ACK from A). Using the same illustration, > > if C is allowed transmit to D while B is transmitting to A, how will > > be B receive and ACK from A? It may now send C's transmission will > > like interfere. > > Please note that I referred to the RTS/CTS dialogue only, and not to > the RTS/CTS/DATA/ACK exchange. In the former, there is no need for RTS > to disable > the nodes around the transmitter for more than the duration of the > RTS/CTS exchange only. Thus, while B transmits DATA to A, C is not > disabled and can transmit to A. > > You are correct in saying that RTS/CTS/DATA/ACK dialogue requires to > disable nodes around both, the transmitter and the receiver, just to > cover the ACK going back to the transmitter. But this is not the case > in "pure" RTS/CTS dialogue, where the ACK can be sent on higher layer > than the MAC. > > Hopes this clarifies the issue. > > 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 > ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- ~- > > > > _______________________________________________ > 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 Wed Jul 9 18:44:29 2003 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 SAA27322 for ; Wed, 9 Jul 2003 18:44:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNfQ-0005Eg-19 for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 18:44:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69Mi3ap020116 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 18:44:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNfP-0005EN-Rw for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 18:44: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 SAA27293 for ; Wed, 9 Jul 2003 18:43:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNfM-0004i8-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:44:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aNfM-0004i5-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:44:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNfO-000582-7m; Wed, 09 Jul 2003 18:44:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNf8-00056n-LG for manet@optimus.ietf.org; Wed, 09 Jul 2003 18:43: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 SAA27272 for ; Wed, 9 Jul 2003 18:43:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNf5-0004hl-00 for manet@ietf.org; Wed, 09 Jul 2003 18:43:43 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 19aNf4-0004hi-00 for manet@ietf.org; Wed, 09 Jul 2003 18:43:42 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id B591F201D for ; Wed, 9 Jul 2003 16:43:42 -0600 (MDT) From: "John Mullen" To: Subject: RE: [manet] Carrier sense threshold/range control Date: Wed, 9 Jul 2003 16:43:42 -0600 Message-ID: <000201c3466b$8c6fad80$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 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 Zygmunt, Well, there is still a problem or two with RTS/CTS alone. Say, as in the illustration, B wishes to send to A. Terminal B sends a RTS, which C hears. However, C never hears the CTS from A because A is too far away. What are C's choices if it wishes to send to D? One is to hold off for a random period of time, just in case A intends to send a CTS. If A doesn't send a CTS, then C has missed an opportunity to send. On the other hand, if C sends its RTS, it may cause a data collision at B. Assuming C cannot hear A, it is not possible for C to know. Of course, once B starts to transmit, the risk of a collision at B is not a problem, but now C would not be able to hear a CTS from D due to interference from B. In theory, C can send to D without causing a problem, but in practice, unless the timing is just right, C will not know that. Unless terminals have perfect knowledge of the local topology and exactly what each of their neighbors are doing, it will not be possible to eliminate both the hidden and exposed terminal problems entirely. It should also be borne in mind that one can include in RTS and CTS an estimate of the duration of the channel's use so terminals that can hear will know how long to wait before trying to seize the channel. Carrier sensing, while useful, does not have this capability. An interesting approach is in the paper "Floor Acquisition Multiple Access (FAMA) for Packet-Radio Networks," available at http://citeseer.nj.nec.com/fullmer95floor.html In FAMA, time slots are reserved for RTS and CTS so data and control packets do not collide. Furthermore, the authors contend that data packets will never collide. The trade-off, of course, is the number of time slots to reserve for signaling. I'm not that current on MAC protocols and there may be more recent papers. John Mullen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of haas@ece.cornell.edu Sent: Wednesday, July 09, 2003 2:40 PM To: Dmitri D. Perkins Cc: ogier@erg.sri.com; Ram Ramanathan; Mineo Takai; manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control Hi Dmitri, On Wed, 9 Jul 2003, Dmitri D. Perkins wrote: > Using the illustration referenced and assuming an RTS/CTS/DATA/ACK > transmission scenario, the RTS must disable all nodes within range of > B (since B must also recieve an ACK from A). Using the same > illustration, if C is allowed transmit to D while B is transmitting to > A, how will be B receive and ACK from A? It may now send C's > transmission will like interfere. Please note that I referred to the RTS/CTS dialogue only, and not to the RTS/CTS/DATA/ACK exchange. In the former, there is no need for RTS to disable the nodes around the transmitter for more than the duration of the RTS/CTS exchange only. Thus, while B transmits DATA to A, C is not disabled and can transmit to A. You are correct in saying that RTS/CTS/DATA/ACK dialogue requires to disable nodes around both, the transmitter and the receiver, just to cover the ACK going back to the transmitter. But this is not the case in "pure" RTS/CTS dialogue, where the ACK can be sent on higher layer than the MAC. Hopes this clarifies the issue. 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 ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- ~- _______________________________________________ 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 Jul 9 18:47:46 2003 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 SAA27545 for ; Wed, 9 Jul 2003 18:47: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 19aNib-0005pq-8S for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 18:47:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69MlL2m022431 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 18:47:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNia-0005pi-FS for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 18:47: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 SAA27519 for ; Wed, 9 Jul 2003 18:47:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNiX-0004mz-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:47:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aNiW-0004mw-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:47:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNiI-0005fi-HO; Wed, 09 Jul 2003 18:47:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNhR-0005eR-7Y for manet@optimus.ietf.org; Wed, 09 Jul 2003 18:46: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 SAA27483 for ; Wed, 9 Jul 2003 18:46:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNhO-0004lk-00 for manet@ietf.org; Wed, 09 Jul 2003 18:46:06 -0400 Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx with esmtp (Exim 4.12) id 19aNhN-0004lh-00 for manet@ietf.org; Wed, 09 Jul 2003 18:46:05 -0400 Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 448D61E4030; Wed, 9 Jul 2003 18:57:24 -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 h69Mk5g08300; Wed, 9 Jul 2003 18:46:05 -0400 Date: Wed, 9 Jul 2003 18:44:53 -0400 (EDT) From: "haas@ece.cornell.edu" To: John Mullen Cc: manet@ietf.org Subject: RE: [manet] Carrier sense threshold/range control 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 John, > Say, as in the illustration, B wishes to send to A. Terminal B sends a > RTS, which C hears. However, C never hears the CTS from A because A is > too far away. What are C's choices if it wishes to send to D? One is > to hold off for a random period of time, just in case A intends to send > a CTS. If A doesn't send a CTS, then C has missed an opportunity to > send. On the other hand, if C sends its RTS, it may cause a data > collision at B. Assuming C cannot hear A, it is not possible for C to > know. The MACA algorithm that I was referring to allows RTS to "reserve" the channel for the duration of the RTS/CTS exchange only. Thus C will be disabled for the duration of that time only. There is no need for C to guess - if it did not hear CTS by the end of this period, it is free to access the channel. Again, the correctness of the MACA protocol depends on its theoretical assumptions that there are no transmission errors, etc ... i.e., if a RTS or CTS packet is sent, it is reliably received by all the nodes in the vicinity of the respective transmitter. > Of course, once B starts to transmit, the risk of a collision at B is > not a problem, but now C would not be able to hear a CTS from D due to > interference from B. In theory, C can send to D without causing a > problem, but in practice, unless the timing is just right, C will not > know that. Correct. This issue (and few others) were addressed in the MACAW paper. My statement was that under some theoretical assumptions, MACA provides for both hidden- and exposed-terminal problems. In practice, as I have stated, this is incorrect. This is why other schemes came in to fill in the gap, the FAMA, as you have mentioned, and the DBTMA, as I have. Cheers ... (I am off the line - have to do some work today ...(;-)). 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 ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 18:54:51 2003 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 SAA27740 for ; Wed, 9 Jul 2003 18:54:51 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNpR-0006Ip-NN for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 18:54:25 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69MsP9h024222 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 18:54:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNpR-0006Ib-Jx for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 18:54: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 SAA27724 for ; Wed, 9 Jul 2003 18:54:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNpO-0004rV-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:54:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aNpN-0004rS-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 18:54:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNp4-0006Bz-7d; Wed, 09 Jul 2003 18: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 19aNoX-0006At-1R for manet@optimus.ietf.org; Wed, 09 Jul 2003 18:53:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27708 for ; Wed, 9 Jul 2003 18:53:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNoU-0004qr-00 for manet@ietf.org; Wed, 09 Jul 2003 18:53:26 -0400 Received: from mailer.cacs.louisiana.edu ([130.70.72.22]) by ietf-mx with esmtp (Exim 4.12) id 19aNoS-0004qo-00 for manet@ietf.org; Wed, 09 Jul 2003 18:53:25 -0400 Received: from swamp450.cacs.louisiana.edu (swamp450.cacs.louisiana.edu [130.70.75.99]) by mailer.cacs.louisiana.edu (8.11.3/8.11.3) with ESMTP id h69MrMr27419; Wed, 9 Jul 2003 17:53:22 -0500 (CDT) Date: Wed, 9 Jul 2003 17:53:22 -0500 (CDT) From: "Dmitri D. Perkins" To: "Nitin H. Vaidya" cc: MANET mailing list Subject: Re: [manet] Re: Carrier sense threshold/range control 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: , Sorry about the previous mail... Question...Referencing the previous illustration (A<-----B C------>D), is there any work showing the benefit versus overhead or complexity for the following scenario: 1. allow node C to transmit to D while B is transmitting a data frame to A 2. force C to keep silent just in time for B to receive the ACK from A. This MAY result in better channel utilization but SHOULD require a more complex access/NAV scheme. Any thoughts... BTW... Regarding the use of end-to-end ACKs versus MAC-layer ACKs, if we compare the performance of TCP over CS/RTS/CTS/DATA/ACK versus CS/RTS/CTS/DATA versus CS/DATA, TCP over CS/RTS/CTS/DATA/ACK will typically perform better. I believe Gerla's group at UCLA has published some work on this issue. Of course, one cause of the decreased throughput when using TCP is the use of slow-start when a packet loss occurs. Any thoughts... Thanks, Dmitri On Wed, 9 Jul 2003, Dmitri D. Perkins wrote: > > > > ================================================== > Dr. Dmitri D. Perkins, Assistant Professor > The Center for Advanced Computer Studies > University of Louisiana at Lafayette > P.O. Box 44330, Lafayette, LA 70504-4330 > > office: (337)482-6732 fax: (337)482-5791 > http://www.cacs.louisiana.edu/~perkins > ================================================== > > On Wed, 9 Jul 2003, Nitin H. Vaidya wrote: > > > > > Reading manet mails in digest mode .... so comments on several > > messages lumped together. > > > > . >>From: Ram Ramanathan > > . >> > > . >>To elaborate, the threshold for when carrier is declared to be "sensed" > > . >>can be adjusted in many radios. Using this facility, one could possibly > > . >>make the "carrier sense range" approximately twice the "communication range" > > . >>(successful packet reception), and detect hidden nodes. > > > > If I recall correctly, the paper on Wavelan (the first Wavelan) that > > appeared in Bell Labs journal (AT&T journal, or whatever it was called > > at the time), shows a picture that matches with your discussion above. > > I think they chose a carrier sense range twice that of the transmission > > range -- it seems that the Bell Labs Tehcnical Journal has disappeared > > from the web, so I cannot find the paper (which was written by Bruce > > Tuch). > > > > . >>From: "haas@ece.cornell.edu" > > . >> > > . >>Actually, that's not entirely correct - the RTS/CTS dialogue will *in > > . >>principle* solve both the hidden- and the exposed-terminal problems. The > > > > It will solve the hidden terminal problem if the nodes that > > interfere with the reception at a host R are also the nodes > > that reliably receive the transmission of CTS from host R -- this > > may not the case. > > > > . >>From: "Dmitri D. Perkins" > > . >> > > . >>Dr. Haas, > > . >> > > . >>Using the illustration referenced and assuming an RTS/CTS/DATA/ACK > > . >>transmission scenario, the RTS must disable all nodes within range of > > . >>B (since B must also recieve an ACK from A). Using the same illustration, > > . >>if C is allowed transmit to D while B is transmitting to A, how will be > > . >>B receive and ACK from A? It may now send C's transmission will like > > . >>interfere. > > . >> > > . >>Thus, the duration field of the RTS message must forced neigboring nodes > > . >>to remain silent long enough for the sender (node B) to receive a CTS from > > . >>node A + send a data frame to node A + recv an ACK from node A. The RTS > > . >>duration field will also need to account for DIFS and SIFS (interframe > > . >>spacing). > > . >> > > . >>Now, if no ACK (an unreliable MAC) are used C should be allowed to > > . >>transmit, but performance will suffer due to wireless channel effects. > > > > Zygmunt is refering to MACA I think, whereas you might be refering > > to 802.11. Both are right, of course, Incidentally, 802.11 is > > conservative in the manner in which collisions with ACKs are prevented > > (neighbors of the senders only need disable transmissions during the > > ACK reception at the sender, but 802.11 disables them for the entire > > transaction -- that simplifies NAV maintenance). > > > > - nitin > > > > > > _______________________________________________ > > 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 Jul 9 19:01:38 2003 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 TAA28052 for ; Wed, 9 Jul 2003 19:01:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNw0-0006t3-P0 for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 19:01:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69N1Cfw026473 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 19:01:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNw0-0006su-Lk for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 19:01: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 TAA28026 for ; Wed, 9 Jul 2003 19:01:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNvx-0004xT-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 19:01:09 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aNvw-0004xQ-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 19:01:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNvq-0006md-BP; Wed, 09 Jul 2003 19:01:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aNvd-0006lw-AD for manet@optimus.ietf.org; Wed, 09 Jul 2003 19:00: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 TAA27995 for ; Wed, 9 Jul 2003 19:00:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aNva-0004xA-00 for manet@ietf.org; Wed, 09 Jul 2003 19:00:46 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 19aNvY-0004x6-00 for manet@ietf.org; Wed, 09 Jul 2003 19:00:44 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id 661B02020; Wed, 9 Jul 2003 17:00:44 -0600 (MDT) From: "John Mullen" To: Cc: Subject: RE: [manet] Carrier sense threshold/range control Date: Wed, 9 Jul 2003 17:00:44 -0600 Message-ID: <000901c3466d$ed5de880$67f57b80@IEngr.ad.nmsu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Zygmunt, (For when you get back :-) In my little example, I was referring to protocol design choices. The protocol would, of course, remove any ambiguity from C's little mind. My point was that if you use a hold-off, as in MACA, you have the exposed terminal problem and if you do not, you now have a hidden terminal problem, of sorts. (C may know B is there, but doesn't know that A is sending). Since you must do one or the other, you cannot eliminate both problems entirely. As for the realities of noise and random fluctuations. Well, that is what makes this whole thing interesting. A couple of years ago, I was on the committee of a Ph.D. student studying protocols for outer space transmission. He worked quite a while in an error free environment. I and other members of the committee urged him to include the noise before drawing too many conclusions, but he was a depth-first-search kind of guy. Finally, he put in the noise. I remember him showing me the effect. It was quite remarkable, as I expected. His carefully analyzed order of performance among the protocols was completely trashed by the effects of noise. :-) John Mullen p.s. thanks for the link. (Is this an ACK?) -----Original Message----- From: haas@ece.cornell.edu [mailto:haas@ece.cornell.edu] Sent: Wednesday, July 09, 2003 3:42 PM To: John Mullen Cc: Zygmunt Haas Subject: RE: [manet] Carrier sense threshold/range control Hi John, > Say, as in the illustration, B wishes to send to A. Terminal B sends > a RTS, which C hears. However, C never hears the CTS from A because A > is too far away. What are C's choices if it wishes to send to D? One > is to hold off for a random period of time, just in case A intends to > send a CTS. If A doesn't send a CTS, then C has missed an opportunity > to send. On the other hand, if C sends its RTS, it may cause a data > collision at B. Assuming C cannot hear A, it is not possible for C to > know. The MACA algorithm that I was referring to allows RTS to "reserve" the channel for the duration of the RTS/CTS exchange only. Thus C will be disabled for the duration of that time only. There is no need for C to guess - if it did not hear CTS by the end of this period, it is free to access the channel. Again, the correctness of the MACA protocol depends on its theoretical assumptions that there are no transmission errors, etc ... i.e., if a RTS or CTS packet is sent, it is reliably received by all the nodes in the vicinity of the respective transmitter. > Of course, once B starts to transmit, the risk of a collision at B is > not a problem, but now C would not be able to hear a CTS from D due to > interference from B. In theory, C can send to D without causing a > problem, but in practice, unless the timing is just right, C will not > know that. Correct. This issue (and few others) were addressed in the MACAW paper. My statement was that under some theoretical assumptions, MACA provides for both hidden- and exposed-terminal problems. In practice, as I have stated, this is incorrect. This is why other schemes came in to fill in the gap, the FAMA, as you have mentioned, and the DBTMA, as I have. Cheers ... (I am off the line - have to do some work today ...(;-)). 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 ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- ~- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 19:10:42 2003 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 TAA28288 for ; Wed, 9 Jul 2003 19:10:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aO4m-0007fg-V4 for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 19:10:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69NAGKs029482 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 19:10:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aO4m-0007fR-Qz for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 19:10: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 TAA28261 for ; Wed, 9 Jul 2003 19:10:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aO4j-000528-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 19:10:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aO4j-000525-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 19:10:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aO4Y-0007Yu-9E; Wed, 09 Jul 2003 19: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 19aO4D-0007YR-4H for manet@optimus.ietf.org; Wed, 09 Jul 2003 19: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 TAA28254 for ; Wed, 9 Jul 2003 19:09:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aO49-00051n-00 for manet@ietf.org; Wed, 09 Jul 2003 19:09:37 -0400 Received: from amber.crhc.uiuc.edu ([130.126.143.254]) by ietf-mx with esmtp (Exim 4.12) id 19aO48-00051Z-00 for manet@ietf.org; Wed, 09 Jul 2003 19:09:37 -0400 Received: from godel.crhc.uiuc.edu (godel.crhc.uiuc.edu [130.126.142.150]) by amber.crhc.uiuc.edu (8.12.9/8.12.9) with ESMTP id h69N995x026510; Wed, 9 Jul 2003 18:09:10 -0500 (CDT) Received: from localhost (nhv@localhost) by godel.crhc.uiuc.edu (8.11.6/8.11.6) with ESMTP id h69N94905701; Wed, 9 Jul 2003 18:09:04 -0500 X-Authentication-Warning: godel.crhc.uiuc.edu: nhv owned process doing -bs Date: Wed, 9 Jul 2003 18:09:04 -0500 (CDT) From: "Nitin H. Vaidya" To: "Dmitri D. Perkins" cc: MANET mailing list In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Re: Carrier sense threshold/range control Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Wed, 9 Jul 2003, Dmitri D. Perkins wrote: . >>Question...Referencing the previous illustration (A<-----B C------>D), . >>is there any work showing the benefit versus overhead or complexity for . >>the following scenario: . >> . >>1. allow node C to transmit to D while B is transmitting a data frame to A . >>2. force C to keep silent just in time for B to receive the ACK from A. . >> . >>This MAY result in better channel utilization but SHOULD require a more . >>complex access/NAV scheme. Any thoughts... In the above scenario, C needs to sneak in its DATA (and perhaps RTS) packet between the reception of CTS and ACK node B. This may not be feasible (depends on packet sizes). The gains could be much more interesting in the scenario below, which simply reverses directions of the data transmissions (provided that A does not pose too much interference at C, and D at B). A --------> B C <----------- D - nitin _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 19:30:51 2003 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 TAA28943 for ; Wed, 9 Jul 2003 19:30:51 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOOG-000197-Rz for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 19:30:24 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69NUOMe004406 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 19:30:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOOG-00018z-Op for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 19:30: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 TAA28916 for ; Wed, 9 Jul 2003 19:30:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aOOF-0005DQ-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 19:30:23 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aOOE-0005DN-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 19:30:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aONu-00012A-Cx; Wed, 09 Jul 2003 19: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 19aONY-00011f-OS for manet@optimus.ietf.org; Wed, 09 Jul 2003 19:29: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 TAA28894 for ; Wed, 9 Jul 2003 19:29:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aONX-0005Ci-00 for manet@ietf.org; Wed, 09 Jul 2003 19:29:39 -0400 Received: from tiquini.ece.arizona.edu ([128.196.29.23]) by ietf-mx with esmtp (Exim 4.12) id 19aONW-0005Cf-00 for manet@ietf.org; Wed, 09 Jul 2003 19:29:38 -0400 Received: from tiquini (tiquini [128.196.29.23]) by tiquini.ece.arizona.edu (8.12.9/8.12.9) with ESMTP id h69NTQI2018020; Wed, 9 Jul 2003 16:29:26 -0700 (MST) Received: from DHCP-140.ece.arizona.edu ([150.135.222.140]) by tiquini.ece.arizona.edu (MailMonitor for SMTP v1.2.2 ) ; Wed, 9 Jul 2003 16:29:26 -0700 (MST) Message-ID: <007c01c34672$00d08ef0$8cde8796@arizonaalaa> Reply-To: "Alaa Muqattash" From: "Alaa Muqattash" To: "Nitin H. Vaidya" Cc: "MANET mailing list" References: Subject: Re: [manet] Re: Carrier sense threshold/range control Date: Wed, 9 Jul 2003 16:29:54 -0700 Organization: The University of Arizona MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit ----- Original Message ----- From: "Nitin H. Vaidya" To: "Dmitri D. Perkins" Cc: "MANET mailing list" Sent: Wednesday, July 09, 2003 4:09 PM Subject: [manet] Re: Carrier sense threshold/range control > The gains could be much more interesting in the scenario below, which > simply reverses directions of the data transmissions (provided that > A does not pose too much interference at C, and D at B). > > A --------> B C <----------- D > > - nitin This is exactly what PCMA and PCDC do (see reference below); they allow nodes to access the channel simultaneously only if the interference is *not high enough* to cause collisions at the receivers. However, note that they use two channels and are not compatible with the 802.11 approach. Jeffrey P. Monks, Vaduvur Bharghavan, and Wen-mei Hwu, "A Power Controlled Multiple Access (PCMA) Protocol for Wireless Packet Networks," IEEE INFOCOM 2001, Anchorage, Alaska, April, 2001 Alaa Muqattash and Marwan Krunz "Power Controlled Dual Channel (PCDC) Medium Access Protocol for Wireless Ad Hoc Networks," in the Proceedings of the IEEE INFOCOM'03 Conference, San Francisco, April 2003. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 19:41:42 2003 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 TAA29221 for ; Wed, 9 Jul 2003 19:41:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOYl-0001oQ-QK for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 19:41:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69NfFBv006960 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 19:41:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOYl-0001oB-DT for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 19:41: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 TAA29190 for ; Wed, 9 Jul 2003 19:41:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aOYj-0005IP-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 19:41:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aOYj-0005IM-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 19:41:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOYX-0001k4-2G; Wed, 09 Jul 2003 19:41:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOXy-0001jd-IG for manet@optimus.ietf.org; Wed, 09 Jul 2003 19:40: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 TAA29156 for ; Wed, 9 Jul 2003 19:40:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aOXw-0005Hs-00 for manet@ietf.org; Wed, 09 Jul 2003 19:40:24 -0400 Received: from amber.crhc.uiuc.edu ([130.126.143.254]) by ietf-mx with esmtp (Exim 4.12) id 19aOXv-0005HC-00 for manet@ietf.org; Wed, 09 Jul 2003 19:40:24 -0400 Received: from godel.crhc.uiuc.edu (godel.crhc.uiuc.edu [130.126.142.150]) by amber.crhc.uiuc.edu (8.12.9/8.12.9) with ESMTP id h69Ndx5x028170; Wed, 9 Jul 2003 18:39:59 -0500 (CDT) Received: from localhost (nhv@localhost) by godel.crhc.uiuc.edu (8.11.6/8.11.6) with ESMTP id h69Ndrr05743; Wed, 9 Jul 2003 18:39:53 -0500 X-Authentication-Warning: godel.crhc.uiuc.edu: nhv owned process doing -bs Date: Wed, 9 Jul 2003 18:39:53 -0500 (CDT) From: "Nitin H. Vaidya" To: Alaa Muqattash cc: MANET mailing list Subject: Re: [manet] Re: Carrier sense threshold/range control In-Reply-To: <007c01c34672$00d08ef0$8cde8796@arizonaalaa> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Wed, 9 Jul 2003, Alaa Muqattash wrote: . >>----- Original Message ----- . >> . >>> The gains could be much more interesting in the scenario below, which . >>> simply reverses directions of the data transmissions (provided that . >>> A does not pose too much interference at C, and D at B). . >>> . >>> A --------> B C <----------- D . >>> . >>> - nitin . >> . >> . >>This is exactly what PCMA and PCDC do (see reference below); they allow Not quite the same as PCMA ... since the basic RTS/CTS mechanisms do not explicitly look at SNR, unlike PCMA. In any case, I think I got the example wrong in that it may not be any more interesting than the example with the flows in opposite directions. If B and C above were closer though, one could conceive a bit smarter MAC -- for instance, if C hears the RTS received by B from A, then C can overlap its RTS with the CTS it expects B to send to A. Too complex for this time of the day ... - nitin _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 19:57:08 2003 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 TAA29668 for ; Wed, 9 Jul 2003 19:57:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOnY-0002iQ-2X for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 19:56:40 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h69NuWOL010436 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 19:56:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOnX-0002iF-Sm for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 19:56: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 TAA29627 for ; Wed, 9 Jul 2003 19:56:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aOnV-0005Ro-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 19:56:29 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aOnV-0005Rl-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 19:56:29 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOn4-0002aZ-81; Wed, 09 Jul 2003 19:56:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aOmr-0002Zs-NI for manet@optimus.ietf.org; Wed, 09 Jul 2003 19:55: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 TAA29620 for ; Wed, 9 Jul 2003 19:55:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aOmp-0005Ra-00 for manet@ietf.org; Wed, 09 Jul 2003 19:55:47 -0400 Received: from ftpbox.mot.com ([129.188.136.101]) by ietf-mx with esmtp (Exim 4.12) id 19aOmo-0005RX-00 for manet@ietf.org; Wed, 09 Jul 2003 19:55:46 -0400 Received: from az33exr03.mot.com (pobox3.mot.com [10.64.251.242]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h69Ntjsn004583 for ; Wed, 9 Jul 2003 16:55:46 -0700 (MST) Received: from homer.arc.corp.mot.com (homer.arc.corp.mot.com [10.238.80.38]) by az33exr03.mot.com (Motorola/az33exr03) with ESMTP id h69NtbvQ016589 for ; Wed, 9 Jul 2003 18:55:43 -0500 Received: from arc.corp.mot.com (kwchin.arc.corp.mot.com [10.238.80.134]) by homer.arc.corp.mot.com (8.12.9/8.12.9) with ESMTP id h69NtZe7008027; Thu, 10 Jul 2003 09:55:35 +1000 (EST) Message-ID: <3F0CAB76.F06DB6A9@arc.corp.mot.com> Date: Thu, 10 Jul 2003 09:55:34 +1000 From: Kwan-Wu Chin Organization: Motorola Lab. Australia X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: manet@ietf.org, lwapp@frascone.com Content-Type: multipart/mixed; boundary="------------40868B81585F3330EE22E634" Subject: [manet] CFP: IEEE Percom'2004 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --------------40868B81585F3330EE22E634 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------40868B81585F3330EE22E634 Content-Type: text/plain; charset=us-ascii; name="CFP.txt" Content-Disposition: inline; filename="CFP.txt" Content-Transfer-Encoding: 7bit -------------------------------------------------------------------------------- *** OUR SINCERE APOLOGIES IF YOU RECEIVE MULTIPLE COPIES OF THIS CFP *** -------------------------------------------------------------------------------- CONFERENCE ANNOUNCEMENT AND CALL FOR PAPERS AND WORKSHOPS Second IEEE International Conference on Pervasive Computing and Communications PerCom 2004 (http//www.percom.org) March 14-17, 2004 Orlando, FLORIDA -------------------------------------------------------------------------------- **** Paper Submission Deadline --- September 1, 2003 **** **** Workshop Proposals Deadline --- June 1, 2003 **** Sponsored by The IEEE Computer Society and The University of Texas at Arlington Cosponsored by the IEEE TCCC and the IEEE TCPP -------------------------------------------------------------------------------- IEEE PerCom 2004 will be the second annual conference on the emerging area of pervasive computing and communications aimed at providing an exciting platform and paradigm for all the time, everywhere services. This emergence is a natural outcome of the tremendous advances in wireless networks, mobile computing, sensor networks, distributed computing, and agent technologies. PerCom 2004 will provide a high profile, leading edge forum for researchers and engineers alike to present their latest research in the field of pervasive computing and communications. As in PerCom 2003, the Mark Weiser Best Paper Award will be given to the best paper judged by the award subcommittee. Also, as in PerCom 2003, a special issue of a leading journal will be published out of the selected papers. Proposals to organize Workshops are also invited. PerCom 2004 will also feature industry exhibits and demonstrations. -------------------------------------------------------------------------------- Feature Topics: ---------------- Contributions are solicited in all areas and topics pertaining to pervasive computing research and applications. These include, but are not limited to, the following topics: * Pervasive computing architectures * Intelligent environments * Wearable computers * Smart devices and smart spaces * Location-dependent / personalized applications * Service discovery mechanisms * Agent technologies * Sensors and actuators * Positioning and tracking technologies * Identification and authentication technologies * Integration of wired and wireless networks * Personal area networks * Enabling technologies such as Bluetooth, 802.11 and 802.15 * Software coordination models * Mobile / wireless computing systems and services * Context based and implicit computing * Speech processing / advanced computer vision * User interfaces and interaction models * Wireless/mobile service management and delivery * Ad hoc networking protocols and service discovery * Resource management in pervasive computing platforms * Security and privacy issues for pervasive computing systems -------------------------------------------------------------------------------- Submission Guidelines: ---------------------------------- Submitted papers must be unpublished and not currently under consideration elsewhere for publication. Only electronic submissions (PS or PDF) will be considered. Page limit is 12 pages (single column, 11 pt fonts and 1.5 line spaced, excluding references, figures and tables). Detailed procedure will be available at http://www.percom.org. All submitted papers will undergo a rigorous review process managed by the technical program committee. IEEE Computer Society Press will publish the conference proceedings. Papers of particular merit will be considered for a special issue of a journal. For organizing a workshop at PerCom'2004, please contact the Workshop Chairs. A separate proceedings of workshop papers will be published by the IEEE Computer Society Press. ###################################################### IMPORTANT DATES: Paper Submission: September 1, 2003 Workshop Proposal: June 1, 2003 Demonstration Proposal: October 31, 2003 Acceptance Notification: November 15, 2003 Camera Ready Manuscripts: December 10, 2003 Conference Dates: March 14-17, 2004 ###################################################### --------------------------------------------------------------------------------- Program Chair: Anand Tripathi University of Minnesota, Twin Cities Email: tripathi@cs.umn.edu Vice Program Committee Chairs: Liviu Iftode University of Maryland, College Park Klara Nahrstedt University of Illinois at Urbana Champaign Paddy Nixon University of Strathclyde, UK Technical Program Committee: ---------------------------- Jean Bacon, Cambridge University, UK B.R. Badrinath, Rutgers University, USA Stefano Basagni, Northeastern University, USA Bharat Bhargava, Purdue University, USA Vinny Cahill, Trinity College Dublin, Ireland Andrew Campbell, Columbia University, USA Roy Campbell, University of Illinois at Urbana-Champaign, USA Matthew Chalmers, Glasgow University, UK Marco Conti, Council of National Research, Italy Diane Cook, University of Texas at Arlington, USA Antonio Corradi, University of Bologna, Italy Kieran Delaney, NMRC, Ireland Armando Fox, Stanford University, USA Dave Garlan, Carnegie Mellon University, USA Amir Herzberg, Bar-Ilan University, Israel Lars Holmquist, Viktoria Institute, Sweden Viktor K. Prasanna, University of Southern California, USA Robin Kravets, University of Illinois at Urbana-Champaign, USA Hui Lei, IBM T.J. Watson Research Center, USA Diana Marculescu, Carnegie Mellon University, USA Dave Marples, Telecordia, USA Phil McKinley, Michigan State University, USA Lionel Ni, Hong Kong University of Science and Technology, Hong Kong Sotiris Nikoletseas, Patras University, Greece Chiara Petrioli, Rome University `La Sapienza', Italy Gopal Pingali, IBM T.J. Watson Research Center, USA Ravi Prakash, University of Texas at Dallas, USA Kishore Ramachandran, Georgia Institute of Technology, USA Ichiro Satoh, National Institute of Informatics, Tokyo, Japan Steve Shafer, Microsoft Research, USA Mukesh Singhal, University of Kentucky, USA Dave Snowdon, Xerox Research Europe, France Maarten van Steen, Vrije Universiteit, The Netherlands Roy Want, Intel Research, USA Zhi-Li Zhang, University of Minnesota, Minneapolis, USA Taieb Znati, University of Pittsburgh and NSF, USA ------------------------------------------------------------ Organizing Committee: ------------------------- General Chair: Sajal K. Das, University of Texas at Arlington, USA General Vice Chair: Mohan Kumar, University of Texas at Arlington, USA Steering Committee Chair: Behrooz A. Shirazi, University of Texas at Arlington, USA Keynote Lecture Chair: Roy Want, Intel Research, Santa Clara, USA Panel Chair: Chatschik Bisdikian, IBM T.J. Watson Research, USA Workshop Chairs: Hui Lei, IBM Research and Francis Lau, University of Hong Kong Education Workshop Chair: Scott Midkiff, Virginia Tech, USA NIST-Industry Workshop Chair: Vince Stanford, National Institute of Standards and Technology (NIST), USA Industry Liaison: Sumi Helal, University of Florida at Gainesville, USA Demonstration and Exhibit Chairs: Gopal Pingali, IBM T.J. Watson Research Center, USA Chistian Becker, University of Stuttgart, Germany Publicity Chairs: Diana Marculescu, Carnegie Mellon University, USA Kwan-Wu Chin, Motorola Australia, Sydney, Australia Sotirios Terzis, University of Strathclyde, UK Registration Chair: Gergely Zaruba, University of Texas at Arlington, USA Finance Chair: David Levine, University of Texas at Arlington, USA Local Arrangements : Ratan Guha (Chair) University of Central Florida, USA Mostafa Bassiouni, University of Central Florida, USA Mainak Chatterjee, University of Central Florida, USA Damla Turgut, University of Central Florida, USA --------------------------------------------------------------------------------- --------------40868B81585F3330EE22E634-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 9 22:57:58 2003 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 WAA03066 for ; Wed, 9 Jul 2003 22:57:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aRci-0004tN-8U for manet-archive@odin.ietf.org; Wed, 09 Jul 2003 22:57:32 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6A2vWx3018804 for manet-archive@odin.ietf.org; Wed, 9 Jul 2003 22:57:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aRci-0004tD-4n for manet-web-archive@optimus.ietf.org; Wed, 09 Jul 2003 22:57: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 WAA03050 for ; Wed, 9 Jul 2003 22:57:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aRce-0006LG-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 22:57:28 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aRce-0006LD-00 for manet-web-archive@ietf.org; Wed, 09 Jul 2003 22:57:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aRcE-0004s1-4K; Wed, 09 Jul 2003 22:57:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aRc8-0004rk-KO for manet@optimus.ietf.org; Wed, 09 Jul 2003 22:56: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 WAA03044 for ; Wed, 9 Jul 2003 22:56:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aRc5-0006L5-00 for manet@ietf.org; Wed, 09 Jul 2003 22:56:53 -0400 Received: from x86unx3.comp.nus.edu.sg ([137.132.90.3]) by ietf-mx with esmtp (Exim 4.12) id 19aRc3-0006L0-00 for manet@ietf.org; Wed, 09 Jul 2003 22:56:52 -0400 Received: from e500b.comp.nus.edu.sg (e500b.comp.nus.edu.sg [137.132.90.26]) by x86unx3.comp.nus.edu.sg (8.9.1/8.9.1) with SMTP id KAA02343 for ; Thu, 10 Jul 2003 10:56:44 +0800 (GMT-8) From: Er Inn Inn Received: from se11.comp.nus.edu.sg(137.132.80.19) by e500b.comp.nus.edu.sg via csmap id 7018; Thu, 10 Jul 2003 10:56:23 +0800 (SGT) Received: (from http@localhost) by se11.comp.nus.edu.sg (8.12.2+Sun/8.12.5) id h6A2uN1K027658; Thu, 10 Jul 2003 10:56:23 +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 172.18.178.140) (SquirrelMail authenticated user erinninn) by mysoc.nus.edu.sg with HTTP; Thu, 10 Jul 2003 10:56:23 +0800 (SGT) Message-ID: <1074.137.132.80.35.1057805783.squirrel@mysoc.nus.edu.sg> Date: Thu, 10 Jul 2003 10:56:23 +0800 (SGT) Subject: Re: R: [manet] Problem installing tk8.3.2 To: In-Reply-To: <9620749A0C40FB49B72994B11B077C5DAD2ECD@EXC2K01A.cselt.it> References: <9620749A0C40FB49B72994B11B077C5DAD2ECD@EXC2K01A.cselt.it> 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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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, What do you mean by "maybe you've already done it"? However, I will try to do as you advised... thanks a lot! regards, inn inn > maybe you've already done it: install all rpms whose name contain the > word Xfree86 (or something like that). good luck, > --Patrick Stupar > > -----Messaggio originale----- > Da: Er Inn Inn [mailto:erinninn@comp.nus.edu.sg] > Inviato: Wednesday, July 09, 2003 3:08 PM > A: manet@ietf.org > Oggetto: [manet] Problem installing tk8.3.2 > > > Hi guys, > > I have downloaded tk8.3.2.tar.gz and tried to install it in my > machine. However, I met the following problem when I tried to > configure tk8.3.2: > > checking for X... (cached) no > checking for X11 header files... couldn't find any! > checking for X11 libraries... checking for XCreateWindow in -lXwindow... > (cached) no > couldn't find any! Using -lX11. > > And when I tried to make the files, the following error appeared: > ... > ... > {standard input}: Assembler messages: > {standard input}:661: Error: symbol `dy' is already defined > {standard input}:667: Error: symbol `dx' is already defined > {standard input}:714: Error: symbol `q' is already defined > {standard input}:720: Error: symbol `p' is already defined > {standard input}:726: Error: symbol `q' is already defined > {standard input}:732: Error: symbol `q' is already defined > make: *** [tk3d.o] Error 1 > > I guess the problem is with the X11 header files and libraries > that > I failed to find... But I don't know how to solve this problem. > Forget to mention that my system is running on Redhat Linux 9.0. > X11R6 folder is under /usr. There is a symbolic link named X11 in > /usr/lib. Really need help badly! Thanks in advance! > > > regards, > inn inn > > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > > ===================================================================CONFIDENTIALITY > NOTICE This message and its attachments are addressed solely to the > persons above and may contain confidential information. If you have > received the message in error, be informed that any use of the content > hereof is prohibited. Please return it immediately to the sender and > delete the message. Should you have any questions, please contact us by > replying to MailAdmin@tilab.com. Thank you > =================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 10 01:52:17 2003 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 BAA06462 for ; Thu, 10 Jul 2003 01:52:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aULN-0006uR-9Z for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 01:51:50 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6A5pnwO026560 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 01:51:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aULM-0006uJ-Vd for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 01:51: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 BAA06438 for ; Thu, 10 Jul 2003 01:51:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aULJ-0007GV-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 01:51:45 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aULI-0007GS-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 01:51:44 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aUKc-0006qC-Oy; Thu, 10 Jul 2003 01:51:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aUK7-0006ps-0R for manet@optimus.ietf.org; Thu, 10 Jul 2003 01:50: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 BAA06373 for ; Thu, 10 Jul 2003 01:50:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aUK3-0007Fh-00 for manet@ietf.org; Thu, 10 Jul 2003 01:50:27 -0400 Received: from den.erg.sri.com ([128.18.100.23]) by ietf-mx with esmtp (Exim 4.12) id 19aUK2-0007FR-00 for manet@ietf.org; Thu, 10 Jul 2003 01:50:26 -0400 Received: from den.erg.sri.com (localhost [127.0.0.1]) by den.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id WAA26387; Wed, 9 Jul 2003 22:49:23 -0700 (PDT) Message-Id: <200307100549.WAA26387@den.erg.sri.com> To: "John Mullen" cc: haas@ece.cornell.edu, manet@ietf.org Reply-To: ogier@erg.sri.com From: ogier@erg.sri.com Subject: Re: [manet] Carrier sense threshold/range control In-reply-to: Your message of "Wed, 09 Jul 2003 17:00:44 MDT." <000901c3466d$ed5de880$67f57b80@IEngr.ad.nmsu.edu> Date: Wed, 09 Jul 2003 22:49:23 -0700 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , John and Zygmunt, > Hi Zygmunt, > > (For when you get back :-) > > In my little example, I was referring to protocol design choices. The > protocol would, of course, remove any ambiguity from C's little mind. > My point was that if you use a hold-off, as in MACA, you have the > exposed terminal problem and if you do not, you now have a hidden > terminal problem, of sorts. (C may know B is there, but doesn't know > that A is sending). Since you must do one or the other, you cannot > eliminate both problems entirely. In fact, you cannot eliminate the exposed terminal problem completely, since (as you pointed out), if C sends an RTS to D while B is sending data to A, then C will not hear the resulting CTS from D. Therefore, it seems to me that even "pure" RTS/CTS does not solve the exposed terminal problem even in ideal conditions. I looked at the MACAW paper (Bhargavan et al.) today to see if it solves the exposed terminal problem, and it actually has a mechanism (Data-Sending packet) that *prevents* C from sending anything while B is sending data to A. Richard > > As for the realities of noise and random fluctuations. Well, that is > what makes this whole thing interesting. A couple of years ago, I was > on the committee of a Ph.D. student studying protocols for outer space > transmission. He worked quite a while in an error free environment. I > and other members of the committee urged him to include the noise before > drawing too many conclusions, but he was a depth-first-search kind of > guy. Finally, he put in the noise. I remember him showing me the > effect. It was quite remarkable, as I expected. His carefully analyzed > order of performance among the protocols was completely trashed by the > effects of noise. > > :-) > > John Mullen > p.s. thanks for the link. > (Is this an ACK?) > > -----Original Message----- > From: haas@ece.cornell.edu [mailto:haas@ece.cornell.edu] > Sent: Wednesday, July 09, 2003 3:42 PM > To: John Mullen > Cc: Zygmunt Haas > Subject: RE: [manet] Carrier sense threshold/range control > > > Hi John, > > > Say, as in the illustration, B wishes to send to A. Terminal B sends > > a RTS, which C hears. However, C never hears the CTS from A because A > > > is too far away. What are C's choices if it wishes to send to D? One > > > is to hold off for a random period of time, just in case A intends to > > send a CTS. If A doesn't send a CTS, then C has missed an opportunity > > > to send. On the other hand, if C sends its RTS, it may cause a data > > collision at B. Assuming C cannot hear A, it is not possible for C to > > > know. > > The MACA algorithm that I was referring to allows RTS to "reserve" the > channel for the duration of the RTS/CTS exchange only. Thus C will be > disabled for the duration of that time only. There is no need for C to > guess - if it did not hear CTS by the end of this period, it is free to > access the channel. > > Again, the correctness of the MACA protocol depends on its theoretical > assumptions that there are no transmission errors, etc ... i.e., if a > RTS or CTS packet is sent, it is reliably received by all the nodes in > the > vicinity of the respective transmitter. > > > Of course, once B starts to transmit, the risk of a collision at B is > > not a problem, but now C would not be able to hear a CTS from D due to > > > interference from B. In theory, C can send to D without causing a > > problem, but in practice, unless the timing is just right, C will not > > know that. > > Correct. This issue (and few others) were addressed in the MACAW paper. > > My statement was that under some theoretical assumptions, MACA provides > for both hidden- and exposed-terminal problems. In practice, as I have > stated, this is incorrect. This is why other schemes came in to fill in > the gap, the FAMA, as you have mentioned, and the DBTMA, as I have. > > Cheers ... (I am off the line - have to do some work today ...(;-)). > > 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 > ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- > ~- > > > _______________________________________________ > 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 Jul 10 02:56:45 2003 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 CAA20095 for ; Thu, 10 Jul 2003 02:56: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 19aVLn-0004G2-R6 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 02:56:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6A6uJnT016273 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 02:56:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aVLm-0004EJ-Af for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 02:56: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 CAA20065 for ; Thu, 10 Jul 2003 02:56:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aVLi-0007ic-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 02:56:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aVLh-0007iZ-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 02:56:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aVLW-0004AN-CY; Thu, 10 Jul 2003 02:56:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aVKc-00049A-Dt for manet@optimus.ietf.org; Thu, 10 Jul 2003 02:55: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 CAA20036 for ; Thu, 10 Jul 2003 02:55:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aVKY-0007iU-00 for manet@ietf.org; Thu, 10 Jul 2003 02:55:02 -0400 Received: from mail11.ntu.edu.sg ([155.69.5.163]) by ietf-mx with esmtp (Exim 4.12) id 19aVKX-0007iI-00 for manet@ietf.org; Thu, 10 Jul 2003 02:55:01 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mail11.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Thu, 10 Jul 2003 14:29:12 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Carrier sense threshold/range control Date: Thu, 10 Jul 2003 14:29:12 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D7F3@mail01.student.main.ntu.edu.sg> Thread-Topic: [manet] Carrier sense threshold/range control Thread-Index: AcNGp6ITGCWvrMccRRuzBnVGMqFMJAABHJLw From: "#LI ZHIFEI#" To: X-OriginalArrivalTime: 10 Jul 2003 06:29:12.0890 (UTC) FILETIME=[940FF9A0:01C346AC] 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 It seems that the RTS/CTS handshake in single channel cannot elimate the = hidden-terminal and esposed-terminal problem.=20 But the DBTMAC seems to solve these two problems completely with two = additional busy tone channel (rather than send the control frames in the = same data channel). -----Original Message----- From: ogier@erg.sri.com [mailto:ogier@erg.sri.com] Sent: dijous, 10 / juliol / 2003 13:49 To: John Mullen Cc: haas@ece.cornell.edu; manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control=20 John and Zygmunt, > Hi Zygmunt, >=20 > (For when you get back :-) >=20 > In my little example, I was referring to protocol design choices. The > protocol would, of course, remove any ambiguity from C's little mind. > My point was that if you use a hold-off, as in MACA, you have the > exposed terminal problem and if you do not, you now have a hidden > terminal problem, of sorts. (C may know B is there, but doesn't know > that A is sending). Since you must do one or the other, you cannot > eliminate both problems entirely. In fact, you cannot eliminate the exposed terminal problem completely, since (as you pointed out), if C sends an RTS to D while B is sending=20 data to A, then C will not hear the resulting CTS from D. Therefore, it seems to me that even "pure" RTS/CTS does not solve the exposed terminal problem even in ideal conditions. I looked at the MACAW paper (Bhargavan et al.) today to see if=20 it solves the exposed terminal problem, and it actually has a mechanism (Data-Sending packet) that *prevents* C from sending anything while B is sending data to A. Richard >=20 > As for the realities of noise and random fluctuations. Well, that is > what makes this whole thing interesting. A couple of years ago, I was > on the committee of a Ph.D. student studying protocols for outer space > transmission. He worked quite a while in an error free environment. = I > and other members of the committee urged him to include the noise = before > drawing too many conclusions, but he was a depth-first-search kind of > guy. Finally, he put in the noise. I remember him showing me the > effect. It was quite remarkable, as I expected. His carefully = analyzed > order of performance among the protocols was completely trashed by the > effects of noise. >=20 > :-) >=20 > John Mullen > p.s. thanks for the link. > (Is this an ACK?) >=20 > -----Original Message----- > From: haas@ece.cornell.edu [mailto:haas@ece.cornell.edu]=20 > Sent: Wednesday, July 09, 2003 3:42 PM > To: John Mullen > Cc: Zygmunt Haas > Subject: RE: [manet] Carrier sense threshold/range control=20 >=20 >=20 > Hi John, >=20 > > Say, as in the illustration, B wishes to send to A. Terminal B = sends=20 > > a RTS, which C hears. However, C never hears the CTS from A because = A >=20 > > is too far away. What are C's choices if it wishes to send to D? = One >=20 > > is to hold off for a random period of time, just in case A intends = to=20 > > send a CTS. If A doesn't send a CTS, then C has missed an = opportunity >=20 > > to send. On the other hand, if C sends its RTS, it may cause a data = > > collision at B. Assuming C cannot hear A, it is not possible for C = to >=20 > > know. >=20 > The MACA algorithm that I was referring to allows RTS to "reserve" the > channel for the duration of the RTS/CTS exchange only. Thus C will be > disabled for the duration of that time only. There is no need for C to > guess - if it did not hear CTS by the end of this period, it is free = to > access the channel. >=20 > Again, the correctness of the MACA protocol depends on its theoretical > assumptions that there are no transmission errors, etc ... i.e., if a > RTS or CTS packet is sent, it is reliably received by all the nodes in > the=20 > vicinity of the respective transmitter. >=20 > > Of course, once B starts to transmit, the risk of a collision at B = is=20 > > not a problem, but now C would not be able to hear a CTS from D due = to >=20 > > interference from B. In theory, C can send to D without causing a=20 > > problem, but in practice, unless the timing is just right, C will = not=20 > > know that. >=20 > Correct. This issue (and few others) were addressed in the MACAW = paper. >=20 > My statement was that under some theoretical assumptions, MACA = provides > for both hidden- and exposed-terminal problems. In practice, as I have > stated, this is incorrect. This is why other schemes came in to fill = in > the gap, the FAMA, as you have mentioned, and the DBTMA, as I have. >=20 > Cheers ... (I am off the line - have to do some work today ...(;-)). >=20 > Zygmunt. > =3D=3D=3D--=3D=3D=3D=3D=3D > = ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- > ~- > Prof. Zygmunt J. Haas > http://people.ece.cornell.edu/haas=20 > Wireless Networks Laboratory http://wnl.ece.cornell.edu > School of Electrical Engineering =20 > 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 =20 > WNL web page: http://wnl.ece.cornell.edu > = ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- > ~- >=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 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 10 09:51:41 2003 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 JAA02102 for ; Thu, 10 Jul 2003 09:51:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19abpL-0001CZ-SO for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 09:51:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6ADpFLG004615 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 09:51:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19abpL-0001CM-PQ for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 09:51: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 JAA02081 for ; Thu, 10 Jul 2003 09:51:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19abpJ-0002zX-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 09:51:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19abpJ-0002zU-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 09:51:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19abp7-0001BA-6R; Thu, 10 Jul 2003 09:51:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19abol-0001As-JH for manet@optimus.ietf.org; Thu, 10 Jul 2003 09:50: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 JAA02073 for ; Thu, 10 Jul 2003 09:50:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aboj-0002zJ-00 for manet@ietf.org; Thu, 10 Jul 2003 09:50:37 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 19aboi-0002zF-00 for manet@ietf.org; Thu, 10 Jul 2003 09:50:36 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id A44242005 for ; Thu, 10 Jul 2003 07:50:35 -0600 (MDT) From: "John Mullen" To: Subject: RE: [manet] Carrier sense threshold/range control Date: Thu, 10 Jul 2003 07:50:36 -0600 Message-ID: <000301c346ea$3d7e12f0$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 In-Reply-To: <3D565922795545468AE3E3DA2881BEA90186D7F3@mail01.student.main.ntu.edu.sg> Importance: Normal 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 Li, What you say is correct, but only to a point and with a reservation. First of all, although you can avoid collisions on the data channel, I don't think you can avoid them completely on the busy tone channels. The more significant problem is that you are reserving part of your available spectrum for signaling. Whether this is done with a separate radio channel or with time division on a single channel, you are allowing only a fraction of the allotted band for data. Thus, you need to determine how much of the channel(s) need to be reserved for signaling. This would be a design matter and probably a tuning parameter, since the distribution of message lengths would determine the optimal signaling/data ratio. This is not to say that such a thing is a bad idea, just that if not done properly, it could be an inefficient use of the available spectrum. John Mullen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of #LI ZHIFEI# Sent: Wednesday, July 09, 2003 11:29 PM To: manet@ietf.org Subject: RE: [manet] Carrier sense threshold/range control It seems that the RTS/CTS handshake in single channel cannot elimate the hidden-terminal and esposed-terminal problem. But the DBTMAC seems to solve these two problems completely with two additional busy tone channel (rather than send the control frames in the same data channel). _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 10 10:04:42 2003 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 KAA02775 for ; Thu, 10 Jul 2003 10:04:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ac1w-0002Xp-W2 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 10:04:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AE4Gix009770 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 10:04:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ac1w-0002XK-Rk for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 10:04: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 KAA02691 for ; Thu, 10 Jul 2003 10:04:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ac1u-00038O-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 10:04:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ac1u-00038L-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 10:04:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ac1h-0002I0-BQ; Thu, 10 Jul 2003 10: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 19ac1S-0002Dn-MM for manet@optimus.ietf.org; Thu, 10 Jul 2003 10: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 KAA02553 for ; Thu, 10 Jul 2003 10:03:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ac1Q-00037a-00 for manet@ietf.org; Thu, 10 Jul 2003 10:03:44 -0400 Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu) by ietf-mx with esmtp (Exim 4.12) id 19ac1P-00037W-00 for manet@ietf.org; Thu, 10 Jul 2003 10:03:44 -0400 Received: by mail.eecis.udel.edu (Postfix, from userid 62) id 5B43432974; Thu, 10 Jul 2003 10:03:39 -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 9A2973292E for ; Thu, 10 Jul 2003 10:03:38 -0400 (EDT) Date: Thu, 10 Jul 2003 10:03:38 -0400 (EDT) From: Chien-Chung Shen X-X-Sender: To: Subject: RE: [manet] Carrier sense threshold/range control Message-ID: X-Spam-Status: No, hits=-1.8 required=6.0 tests=DEPT_RCVD,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: , Greetings, We have paper that compared (omnidirectional) 802.11, MACA, and DBTMA, and their directional versions (with directional antenna) published in IEEE Globecom, 2002. Zhuochuan Huang and Chien-Chung Shen A Comparison Study of Omnidirectional and Directional MAC Protocols for Ad hoc Networks Thanks. Chien-Chung _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 10 10:32:47 2003 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 KAA04738 for ; Thu, 10 Jul 2003 10:32: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 19acT4-0004cQ-LE for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 10:32:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AEWIhE017754 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 10:32:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acT4-0004cH-EK for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 10:32: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 KAA04695 for ; Thu, 10 Jul 2003 10:32:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19acT2-0003LI-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 10:32:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19acT1-0003LF-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 10:32:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acSo-0004UD-36; Thu, 10 Jul 2003 10: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 19acSY-0004RW-NP for manet@optimus.ietf.org; Thu, 10 Jul 2003 10:31: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 KAA04680 for ; Thu, 10 Jul 2003 10:31:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19acSW-0003L1-00 for manet@ietf.org; Thu, 10 Jul 2003 10:31:44 -0400 Received: from mail11.ntu.edu.sg ([155.69.5.163]) by ietf-mx with esmtp (Exim 4.12) id 19acSV-0003Kb-00 for manet@ietf.org; Thu, 10 Jul 2003 10:31:43 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mail11.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Thu, 10 Jul 2003 22:06:21 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Carrier sense threshold/range control Date: Thu, 10 Jul 2003 22:06:21 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D80B@mail01.student.main.ntu.edu.sg> Thread-Topic: [manet] Carrier sense threshold/range control Thread-Index: AcNG6oTVkPpqt/KkSdi/KBfSurVf2QAAad7A From: "#LI ZHIFEI#" To: "John Mullen" Cc: X-OriginalArrivalTime: 10 Jul 2003 14:06:21.0560 (UTC) FILETIME=[70D2DF80:01C346EC] 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 >What you say is correct, but only to a point and with a reservation. >First of all, although you can avoid collisions on the data channel, I >don't think you can avoid them completely on the busy tone channels. As for my understanding, in the busy channels, other potentailly = interfering nodes need not interpret the content but just sensing the = existence of busy carrier. So what do you mean for the collisions on the busy channel?=20 >The more significant problem is that you are reserving part of your >available spectrum for signaling. Whether this is done with a separate >radio channel or with time division on a single channel, you are >allowing only a fraction of the allotted band for data. Thus, you need >to determine how much of the channel(s) need to be reserved for >signaling. This would be a design matter and probably a tuning >parameter, since the distribution of message lengths would determine = the >optimal signaling/data ratio. >This is not to say that such a thing is a bad idea, just that if not >done properly, it could be an inefficient use of the available = spectrum. I accept your viewpoint without any doubt. In addition to the issue = about the spectrum efficience, complexity may be another issue by = introducing multiple channels. =20 Best regards Li zhifei -----Original Message----- From: John Mullen [mailto:jomullen@nmsu.edu] Sent: dijous, 10 / juliol / 2003 21:51 To: manet@ietf.org Subject: RE: [manet] Carrier sense threshold/range control=20 Hi Li, What you say is correct, but only to a point and with a reservation. First of all, although you can avoid collisions on the data channel, I don't think you can avoid them completely on the busy tone channels. The more significant problem is that you are reserving part of your available spectrum for signaling. Whether this is done with a separate radio channel or with time division on a single channel, you are allowing only a fraction of the allotted band for data. Thus, you need to determine how much of the channel(s) need to be reserved for signaling. This would be a design matter and probably a tuning parameter, since the distribution of message lengths would determine the optimal signaling/data ratio. This is not to say that such a thing is a bad idea, just that if not done properly, it could be an inefficient use of the available spectrum. John Mullen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of #LI ZHIFEI# Sent: Wednesday, July 09, 2003 11:29 PM To: manet@ietf.org Subject: RE: [manet] Carrier sense threshold/range control=20 It seems that the RTS/CTS handshake in single channel cannot elimate the hidden-terminal and esposed-terminal problem.=20 But the DBTMAC seems to solve these two problems completely with two additional busy tone channel (rather than send the control frames in the same data channel). _______________________________________________ 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 Jul 10 10:33:38 2003 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 KAA04813 for ; Thu, 10 Jul 2003 10:33:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acTx-0004sU-Qm for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 10:33:13 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AEXD1n018751 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 10:33:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acTx-0004sM-Kq for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 10:33: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 KAA04766 for ; Thu, 10 Jul 2003 10:33:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19acTv-0003MJ-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 10:33:11 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19acTu-0003MG-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 10:33:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acTl-0004lz-FR; Thu, 10 Jul 2003 10:33:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acTB-0004ca-Rn for manet@optimus.ietf.org; Thu, 10 Jul 2003 10:32: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 KAA04705 for ; Thu, 10 Jul 2003 10:32:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19acT9-0003LV-00 for manet@ietf.org; Thu, 10 Jul 2003 10:32:23 -0400 Received: from mbox1.ntu.edu.sg ([155.69.5.171]) by ietf-mx with esmtp (Exim 4.12) id 19acT8-0003L5-00 for manet@ietf.org; Thu, 10 Jul 2003 10:32:23 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Thu, 10 Jul 2003 22:08:29 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Carrier sense threshold/range control Date: Thu, 10 Jul 2003 22:08:29 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D80C@mail01.student.main.ntu.edu.sg> Thread-Topic: RE: [manet] Carrier sense threshold/range control Thread-Index: AcNG7LxMEbX5dYqITN+0Y2HDoUvmew== From: "#LI ZHIFEI#" To: X-OriginalArrivalTime: 10 Jul 2003 14:08:29.0622 (UTC) FILETIME=[BD279560:01C346EC] 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, Ram In my view, even the Carrier Sensing Range (SR) is two times of the = Transmission Range (TR ), the hidden-termianl problem is still there. This can be illustrated as the following two topologies: Topology 1: Topology 2: A -> B <- C A -> B C<- = D (note that the distance between two neighboring nodes are equal to the = transmission range, i.e., one hop) The first topology is tipycally used to illustrate the well-known = hidden-terminal problem, but with an implicit assumption, i.e., SR=3DTR. If SR=3D2*TR, the hidden-terminal problem seems not exist any more in = this topology as the nodes A and C can sense the transmission of each = other. However, even SR=3D2*TR, the problem will arise in the second topology. = Specically, when node A starts to transmit to node B, since node D is out of the SR of node A, it cannot detect the transmission. = Therefore, node D may also start to transmit to node C, resulting in = collision (or capture). In such case, we can say that nodes A and D are hidden terminal of each = other. We do find the similarities of the performance between the two = cases:=20 topology 1 when SR=3DTR; and topology 2 when SR=3D2*TR When SR>TR, another problem is that how a node should defer its = transmission when it detects a SR frame. This is not an easy job since = the node cannot=20 interpret the content of the SR frame. In the IEEE 802.11, whenever a = node detects a SR frame, it will defer by a fixed EFIS value. However, = our results show this fixed value will cause many problems, e.g., unfairness. Moreover, = the capture ability will also greatly affect the performace when SR>TR. For a detailed descrition of these issues, please refer to the attached = references: Zhifei Li, Sukumar Nandi, Anil K. Gupta,=20 "Improving Fairness in IEEE 802.11 based MANETs using Enhanced Carrier = Sensing", submitted to conference, April 2003 http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf Zhifei Li, Sukumar Nandi, Anil K. Gupta,=20 "Study of IEEE 802.11 Fairness and its Interaction with Routing = Mechanism", accepted by IEEE MWCN 2003 Singapore, May 2003 http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf Though the above papers mainly focus on the the fairness issue when = SR>TR, the descirtion should also apply to the analysis of the channel = utilization. I hope that they will relate to your work and help you. Best regards=20 Li ZhiFei=20 PhD candidate, =20 Center For Multimedia And Network Technology School Of Computer Engineering Nanyang Technological University N4-b2c-08, Nanyang Avenue Singapore 639798 tel:(65)67906579=20 website: =20 -----Original Message----- From: Ram Ramanathan [mailto:ramanath@bbn.com] Sent: dijous, 10 / juliol / 2003 00:09 To: manet@ietf.org Cc: ramanath@bbn.com Subject: [manet] Carrier sense threshold/range control I am looking for pointers to research on the control of carrier sensing=20 range in lieu of using RTS/CTS to address the hidden node problem? To elaborate, the threshold for when carrier is declared to be "sensed"=20 can be adjusted in many radios. Using this facility, one could possibly make the "carrier sense range" approximately twice the "communication = range" (successful packet reception), and detect hidden nodes. This is by no means a new idea, and I vaguely recally some mention of it on this list. Of course, there are a number of factors that make the=20 problem far more complex than the simple statement above indicates, and it is not immediately clear whether it will be effective at all. I am looking for papers, tech reports, or any publicly available = material (non-proprietary) on this issue. Many thanks in advance, -Ram. _______________________________________________ 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 Jul 10 11:03:42 2003 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 LAA06088 for ; Thu, 10 Jul 2003 11:03:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acx3-0007OZ-4o for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 11:03:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AF3HxO028421 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 11:03:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acx3-0007OK-1X for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 11:03: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 LAA06055 for ; Thu, 10 Jul 2003 11:03:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19acx0-0003gd-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 11:03:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19acwz-0003ga-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 11:03:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acwn-0007NB-HA; Thu, 10 Jul 2003 11:03:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19acvz-0007KG-4s for manet@optimus.ietf.org; Thu, 10 Jul 2003 11:02: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 LAA06032 for ; Thu, 10 Jul 2003 11:02:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19acvw-0003g1-00 for manet@ietf.org; Thu, 10 Jul 2003 11:02:08 -0400 Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx with esmtp (Exim 4.12) id 19acvv-0003fx-00 for manet@ietf.org; Thu, 10 Jul 2003 11:02:07 -0400 Received: from zidane.cc.vt.edu (IDENT:mirapoint@evil-zidane [10.1.1.13]) by lennier.cc.vt.edu (8.12.8/8.12.8) with ESMTP id h6AF23CT287683; Thu, 10 Jul 2003 11:02:03 -0400 (EDT) Received: from zathras (zathras.cc.vt.edu [198.82.162.117]) by zidane.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BPX51044; Thu, 10 Jul 2003 11:02:01 -0400 (EDT) X-WebMail-UserID: vdham Date: Thu, 10 Jul 2003 11:02:00 -0400 From: Vikram Dham To: #LI ZHIFEI# , manet X-EXP32-SerialNo: 00002964 Subject: RE: [manet] Carrier sense threshold/range control Message-ID: <3F14CB8E@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 Hello Zhifei Li, Though topology 2 also may have scenarios with hidden terminal, but in a wireless network, probability (distance between nodes > 2SR) =< probability (distance between nodes > SR ). Though we may not be elminating all the hidden terminals but we may decrease the probability of occurence of hidden terminals by extending sensing range to 2SR. Regards Vikram Dham >===== Original Message From #LI ZHIFEI# ===== >Hi, Ram > >In my view, even the Carrier Sensing Range (SR) is two times of the Transmission Range (TR ), the hidden-termianl problem is still there. >This can be illustrated as the following two topologies: > >Topology 1: Topology 2: > >A -> B <- C A -> B C<- D > >(note that the distance between two neighboring nodes are equal to the transmission range, i.e., one hop) > >The first topology is tipycally used to illustrate the well-known hidden-terminal problem, but with an implicit assumption, i.e., SR=TR. >If SR=2*TR, the hidden-terminal problem seems not exist any more in this topology as the nodes A and C can sense the transmission of each other. > >However, even SR=2*TR, the problem will arise in the second topology. Specically, when node A starts to transmit to node B, since node D >is out of the SR of node A, it cannot detect the transmission. Therefore, node D may also start to transmit to node C, resulting in collision (or capture). >In such case, we can say that nodes A and D are hidden terminal of each other. We do find the similarities of the performance between the two cases: >topology 1 when SR=TR; and topology 2 when SR=2*TR > > >When SR>TR, another problem is that how a node should defer its transmission when it detects a SR frame. This is not an easy job since the node cannot >interpret the content of the SR frame. In the IEEE 802.11, whenever a node detects a SR frame, it will defer by a fixed EFIS value. However, our results show >this fixed value will cause many problems, e.g., unfairness. Moreover, the capture ability will also greatly affect the performace when SR>TR. >For a detailed descrition of these issues, please refer to the attached references: > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, >"Improving Fairness in IEEE 802.11 based MANETs using Enhanced Carrier Sensing", submitted to conference, April 2003 >http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, >"Study of IEEE 802.11 Fairness and its Interaction with Routing Mechanism", accepted by IEEE MWCN 2003 Singapore, May 2003 >http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf > > >Though the above papers mainly focus on the the fairness issue when SR>TR, the descirtion should also apply to the analysis of the channel utilization. >I hope that they will relate to your work and help you. > > >Best regards >Li ZhiFei >PhD candidate, >Center For Multimedia And Network Technology >School Of Computer Engineering >Nanyang Technological University >N4-b2c-08, Nanyang Avenue >Singapore 639798 >tel:(65)67906579 >website: > > >-----Original Message----- >From: Ram Ramanathan [mailto:ramanath@bbn.com] >Sent: dijous, 10 / juliol / 2003 00:09 >To: manet@ietf.org >Cc: ramanath@bbn.com >Subject: [manet] Carrier sense threshold/range control > > > >I am looking for pointers to research on the control of carrier sensing >range in lieu of using RTS/CTS to address the hidden node problem? > >To elaborate, the threshold for when carrier is declared to be "sensed" >can be adjusted in many radios. Using this facility, one could possibly >make the "carrier sense range" approximately twice the "communication range" >(successful packet reception), and detect hidden nodes. > >This is by no means a new idea, and I vaguely recally some mention of >it on this list. Of course, there are a number of factors that make the >problem far more complex than the simple statement above indicates, and >it is not immediately clear whether it will be effective at all. > >I am looking for papers, tech reports, or any publicly available material >(non-proprietary) on this issue. > >Many thanks in advance, > >-Ram. > >_______________________________________________ >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 Thu Jul 10 12:42:01 2003 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 MAA11157 for ; Thu, 10 Jul 2003 12:42:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aeU9-0000Ix-T9 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 12:41:35 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AGfXbi001167 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 12:41:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aeU9-0000Ik-Q2 for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 12:41: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 MAA11151 for ; Thu, 10 Jul 2003 12:41:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aeU8-0004tv-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 12:41:32 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aeU7-0004tr-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 12:41:31 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aeTd-0000DK-0b; Thu, 10 Jul 2003 12:41:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aeSi-00006s-Qw for manet@optimus.ietf.org; Thu, 10 Jul 2003 12:40: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 MAA11136 for ; Thu, 10 Jul 2003 12:39:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aeSh-0004tf-00 for manet@ietf.org; Thu, 10 Jul 2003 12:40:03 -0400 Received: from tyto.ciens.ucv.ve ([150.185.72.7]) by ietf-mx with esmtp (Exim 4.12) id 19aeSQ-0004ss-00 for manet@ietf.org; Thu, 10 Jul 2003 12:40:02 -0400 Received: from dircompucv2.tyto.ciens.ucv.ve (dircompucv.ciens.ucv.ve [150.185.75.85]) by tyto.ciens.ucv.ve (8.11.6/8.11.6) with ESMTP id h6AGWEh10347 for ; Thu, 10 Jul 2003 12:32:14 -0400 Message-Id: <5.0.0.25.0.20030710123750.0211e070@tyto.ciens.ucv.ve> X-Sender: asalazar@tyto.ciens.ucv.ve (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Thu, 10 Jul 2003 12:42:42 -0400 To: manet@ietf.org From: Alejandro salazar Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_1991493265==_.ALT" Subject: [manet] !about of delay end to end! Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=====================_1991493265==_.ALT Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Hi all I am interesting in calculating the average delay end to end to evaluate two routing protocols, and I'm going to use the following "simple" definition[esimtesis].: 1/S*(sum (ri-si)) 1<=3Di<=3DS where: S=3DNumber of successfully received packets. i=3DUnique packet identifier. ri=3DTime at which a packet with unique i identifier is received. si=3DTime at which a packet with unique identifier i is sent. However, I would like to know if there exist some research, paper or someones experience that could provide me with a finer measurement for my objective. Thank you very much for your advances. PD : Reference: [esimtesis] Selebi, Celebi. =93Performance Evaluation Of Wireless Multi-Hop= =20 Ad-Hoc Network Routing Protocols=94 Boc gazi=E7i University, 1998. page= 67,83. Serverside12 Alejandro Salazar Student's Computer Science School of Computer Sciences Sciences Faculty Central University of Venezuela email: asalazar@tyto.ciens.ucv.ve --=====================_1991493265==_.ALT Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all

I am interesting in calculating the average delay end to end
to evaluate
two routing protocols, and
I'm going to use the following "simple" definition[esimtesis].:

1/S*(sum (ri-si))
1<=3Di<=3DS
where:
S=3DNumber of successfully received packets.
i=3DUnique packet identifier.
ri=3DTime at which a packet with unique i identifier is received.
si=3DTime at which a packet with unique identifier i is sent.

However, I would like to know if there exist some
research, paper or someones experience that could
provide me with a finer measurement for my objective.

Thank you very much for your advances.

PD :
Reference:
[esimtesis] Selebi, Celebi. =93Performance Evaluation Of Wireless Multi-Hop Ad-Hoc Network Routing Protocols=94 Boc gazi=E7i University, 1998. page 67,83.
Serverside12

Alejandro Salazar
Student's Computer Science
School of Computer Sciences
Sciences Faculty
Central University of Venezuela
email: asalazar@tyto.ciens.ucv.ve

--=====================_1991493265==_.ALT-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 10 14:06:54 2003 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 OAA14805 for ; Thu, 10 Jul 2003 14:06:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19afoK-0008UX-5c for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 14:06:28 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AI6Sv1032635 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 14:06:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19afoK-0008UI-2R for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 14:06:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14797 for ; Thu, 10 Jul 2003 14:06:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19afoH-0005mV-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 14:06:25 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19afoH-0005mS-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 14:06:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19afnt-0008T1-KT; Thu, 10 Jul 2003 14:06:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19afmy-0008Sa-PS for manet@optimus.ietf.org; Thu, 10 Jul 2003 14: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 OAA14769 for ; Thu, 10 Jul 2003 14:05:00 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19afmw-0005mK-00 for manet@ietf.org; Thu, 10 Jul 2003 14:05:02 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 19afmv-0005mH-00 for manet@ietf.org; Thu, 10 Jul 2003 14:05:01 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id DC3B42028; Thu, 10 Jul 2003 12:05:00 -0600 (MDT) From: "John Mullen" To: "'#LI ZHIFEI#'" Cc: Subject: RE: [manet] Carrier sense threshold/range control Date: Thu, 10 Jul 2003 12:05:00 -0600 Message-ID: <000101c3470d$c7ccf1b0$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: <3D565922795545468AE3E3DA2881BEA90186D80B@mail01.student.main.ntu.edu.sg> 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 Li, I'm not entirely sure how you use the busy tone channels, so my statement may not be correct. However, a fundamental problem is in how a terminal gets the right to use a channel. If terminals transmit RTSs as the need arises, there is always a chance that those of different terminals will collide with each other. This contention will have to occur somewhere, whether on the signaling channel or the data channel. So, wherever this signaling occurs is where the problem will be. Another problem is the short, but significant, transmission delay. A terminal may sense that the busy channel is idle and begin to transmit, unaware that another terminal has made the same decision. Because the carriers takes a finite, though brief, time to reach the other terminal and there is inherent delay in the sensing and control processes, by the time the carrier could be sensed, the terminal will already be sending. Later, John Mullen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of #LI ZHIFEI# Sent: Thursday, July 10, 2003 7:06 AM To: John Mullen Cc: manet@ietf.org Subject: RE: [manet] Carrier sense threshold/range control >What you say is correct, but only to a point and with a reservation. >First of all, although you can avoid collisions on the data channel, I >don't think you can avoid them completely on the busy tone channels. As for my understanding, in the busy channels, other potentailly interfering nodes need not interpret the content but just sensing the existence of busy carrier. So what do you mean for the collisions on the busy channel? >The more significant problem is that you are reserving part of your >available spectrum for signaling. Whether this is done with a separate >radio channel or with time division on a single channel, you are >allowing only a fraction of the allotted band for data. Thus, you need >to determine how much of the channel(s) need to be reserved for >signaling. This would be a design matter and probably a tuning >parameter, since the distribution of message lengths would determine >the optimal signaling/data ratio. >This is not to say that such a thing is a bad idea, just that if not >done properly, it could be an inefficient use of the available >spectrum. I accept your viewpoint without any doubt. In addition to the issue about the spectrum efficience, complexity may be another issue by introducing multiple channels. Best regards Li zhifei _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 10 14:17:48 2003 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 OAA15201 for ; Thu, 10 Jul 2003 14:17:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19afys-0001Gs-EO for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 14:17:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AIHMtc004880 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 14:17:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19afyr-0001Gd-SV for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 14:17: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 OAA15161 for ; Thu, 10 Jul 2003 14:17:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19afyp-0005uX-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 14:17:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19afyo-0005uU-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 14:17:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19afyX-0000zO-5u; Thu, 10 Jul 2003 14:17:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19afyS-0000z1-N5 for manet@optimus.ietf.org; Thu, 10 Jul 2003 14:16: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 OAA15137 for ; Thu, 10 Jul 2003 14:16:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19afyQ-0005tb-00 for manet@ietf.org; Thu, 10 Jul 2003 14:16:54 -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 19afyP-0005tX-00 for manet@ietf.org; Thu, 10 Jul 2003 14:16:53 -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 h6AIGpg06000 for ; Thu, 10 Jul 2003 13:16:51 -0500 (CDT) Received: from localhost (b0l4549@localhost) by unix.cs.tamu.edu (8.10.2+Sun/8.10.2) with ESMTP id h6AIGpI05658 for ; Thu, 10 Jul 2003 13:16:51 -0500 (CDT) X-Authentication-Warning: unix.cs.tamu.edu: b0l4549 owned process doing -bs Date: Thu, 10 Jul 2003 13:16:51 -0500 (CDT) From: Bin Lu To: manet@ietf.org In-Reply-To: <5.0.0.25.0.20030710123750.0211e070@tyto.ciens.ucv.ve> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] QoS-AODV simulation? Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi all, If my memory serves me right, someone posted a message on this list that they did some simulation on QoS-AODV. I'm thinking to use the code in my simulation on QoS security for MANETs, but can't find the message... If there has been such code published, can somebody point me to it, or give me a hint where I can find it? I'd appreciate it very much! Bin Lu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 10 15:46:00 2003 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 PAA19055 for ; Thu, 10 Jul 2003 15:45:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ahMB-0000WR-1f for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 15:45:33 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AJjVns002008 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 15:45:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ahMA-0000WJ-V8 for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 15:45: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 PAA19030 for ; Thu, 10 Jul 2003 15:45:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ahM9-0006cI-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 15:45:29 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ahM8-0006cF-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 15:45:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ahLh-0000MF-FV; Thu, 10 Jul 2003 15:45:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ahLG-0000Lg-8l for manet@optimus.ietf.org; Thu, 10 Jul 2003 15:44: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 PAA19012 for ; Thu, 10 Jul 2003 15:44:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ahLE-0006bt-00 for manet@ietf.org; Thu, 10 Jul 2003 15:44:32 -0400 Received: from ecs.syr.edu ([128.230.208.14] helo=erebus.ecs.syr.edu) by ietf-mx with esmtp (Exim 4.12) id 19ahLE-0006bq-00 for manet@ietf.org; Thu, 10 Jul 2003 15:44:32 -0400 Received: from boreas.ecs.syr.edu (boreas.ecs.syr.edu [128.230.208.55]) by erebus.ecs.syr.edu (8.11.7+Sun/8.10.2) with ESMTP id h6AJiVK06279; Thu, 10 Jul 2003 15:44:31 -0400 (EDT) Date: Thu, 10 Jul 2003 15:44:31 -0400 (EDT) From: Jing Deng To: "Nitin H. Vaidya" cc: MANET mailing list Subject: Re: [manet] Re: Carrier sense threshold/range control 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: , Prof. Vaidya, In the first scenario, node C may not be able to sneak in its RTS and DATA packet transmissions even if their lengths are short enough. The problem is that it won't be able to receive node D's CTS reply correctly. Thus, if the RTS/CTS/DATA handshakes are implemented on a single channel (and assuming the same transmission ranges), the exposed terminals should never try to send their RTS requests. So node C may have only one choice: keep silent while node B is sending. If an ACK packet is to be transmitted back to node B (the DATA packet sender), node C may want to be quiet for a little bit longer. It will be another story if out-of-band signaling or multiple channels are in use. Jing ----------------------------------------------------------- Dr. Jing Deng http://www.cis.syr.edu/~jdeng01 2-191 CST, CASE Center Email: jdeng01@ecs.syr.edu Dept. of EECS Phone: (315) 443-3029 Syracuse University Fax: (315) 443-4745 Syracuse, NY 13244 --------------------------- @_@ --------------------------- On Wed, 9 Jul 2003, Nitin H. Vaidya wrote: > > > On Wed, 9 Jul 2003, Dmitri D. Perkins wrote: > > . >>Question...Referencing the previous illustration (A<-----B C------>D), > . >>is there any work showing the benefit versus overhead or complexity for > . >>the following scenario: > . >> > . >>1. allow node C to transmit to D while B is transmitting a data frame to A > . >>2. force C to keep silent just in time for B to receive the ACK from A. > . >> > . >>This MAY result in better channel utilization but SHOULD require a more > . >>complex access/NAV scheme. Any thoughts... > > In the above scenario, C needs to sneak in its DATA (and perhaps RTS) > packet between the reception of CTS and ACK node B. This may not > be feasible (depends on packet sizes). > > The gains could be much more interesting in the scenario below, which > simply reverses directions of the data transmissions (provided that > A does not pose too much interference at C, and D at B). > > A --------> B C <----------- D > > - nitin > > > > _______________________________________________ > 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 Jul 10 16:40:01 2003 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 QAA20841 for ; Thu, 10 Jul 2003 16:40:01 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aiCO-00069e-Hh for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 16:39:36 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AKdSuj023655 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 16:39:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aiCN-00069S-W9 for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 16:39: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 QAA20835 for ; Thu, 10 Jul 2003 16:39:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aiCL-00076Y-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 16:39:25 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aiCL-00076V-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 16:39:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aiBx-00062s-PY; Thu, 10 Jul 2003 16: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 19aiBS-00062H-3e for manet@optimus.ietf.org; Thu, 10 Jul 2003 16:38: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 QAA20818 for ; Thu, 10 Jul 2003 16:38:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aiBO-000764-00 for manet@ietf.org; Thu, 10 Jul 2003 16:38:26 -0400 Received: from wasp.ece.queensu.ca ([130.15.22.4]) by ietf-mx with esmtp (Exim 4.12) id 19aiBN-00075v-00 for manet@ietf.org; Thu, 10 Jul 2003 16:38:26 -0400 Received: from acer7k2wrwolsy ([24.226.47.100]) by wasp.ECE.QUEENSU.CA with Microsoft SMTPSVC(5.0.2195.5329); Thu, 10 Jul 2003 16:38:53 -0400 From: "Chi-Hsiang Yeh" To: "'John Mullen'" , "'#LI ZHIFEI#'" Cc: , Subject: RE: [manet] Carrier sense threshold/range control Date: Thu, 10 Jul 2003 16:37:55 -0400 Message-ID: <000701c34723$27eac2b0$642fe218@acer7k2wrwolsy> 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: <000101c3470d$c7ccf1b0$67f57b80@IEngr.ad.nmsu.edu> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 10 Jul 2003 20:38:53.0281 (UTC) FILETIME=[46BE4D10:01C34723] Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, John, > Hi Li, > > I'm not entirely sure how you use the busy tone channels, so > my statement may not be correct. However, a fundamental > problem is in how a terminal gets the right to use a channel. > If terminals transmit RTSs as the need arises, there is > always a chance that those of different terminals will > collide with each other. This contention will have to occur > somewhere, whether on the signaling channel or the data > channel. So, wherever this signaling occurs is where the > problem will be. What you said is correct in that contention will occur somewhere. But DBTMA uses busy tone and such busy tone does not have the collision problem (as Zhifei pointed out). Using this and other properties, data packet transmissions are collision-free in DBTMA even when some RTS/CTS messages are collided, "under certain assumptions" (e.g., when the following Problems (1-3) do not exist). We have another protocol (that does not require busy tone) where data packets and RTS/CTS control messages are both collision-free, under certain assumptions. See You, T., C.-H. Yeh, and H. Hassanein, "A new class of collision-prevention MAC protocols for ad hoc wireless networks," ICC, May 2003. When there are two separate channels for data packets and control messages, the hidden terminal problem and the exposed terminal problem can both be solved easily and simultaneously, but only theoretically. In practice, due to the following problems DBTMA and our protocol are not really collision-free, and most previous MAC protocols (including DBTMA and our ICC'03 protocol) still suffer from some forms of hidden/exposed terminal problems: (1) The propagation properties of the control channel and data channel may be different. As a result, a node that receives a CTS message actually may not collide the associated reception (and thus a form of the exposed terminal problem exists). Moreover, a node that did not receive a CTS message may actually collide the associated reception (and thus a form of the hidden terminal problem exists). No matter how you adjust the power levels of the control channel and busy tone, one or both of the problems exist. (2) In most papers it is assumed that transmission radius (TR) = interference radius (IR). When IR > TR, then a node with distance between TR and IR will collide a reception. This problem might be fixed when you have separate channels -- by sending RTS/CTS messages with a radius at least IR or at an appropriate power level. (3) Assume that (1) and (2) are not problems. Then two or more nodes that did not receive a CTS message may still collide the associated reception due to their "additive interference" (and thus a form of the hidden terminal problem exists). This problem is more difficult to solve than Problem (2). PCMA might "solve" this problem, but it suffers from Problem (1) and overhead/complexity/hardware cost. (4) When two or more nearby nodes transmit busy tone simultaneously, the strength received at a node is increased. So a node that should not have received any busy tone may actually detect such "additive busy tone" and defer its transmissions (and thus a form of the exposed terminal problem exists). Note that the above problems are not the hidden terminal problem and the exposed terminal problem identified in the Tobagi and Kleinrock paper (in IEEE Trans. Communications, 1975). They have some similarity in principle, but are not exactly the same problems. It's not impossible to solve all these problems, but the resultant protocol will not necessarily outperform existing protocols due to its overhead, and the resultant hardware may be more expensive. Chihsiang ___________________________________________________________ Chi-Hsiang Yeh (Mr./Dr./Prof.) Dept. of Electrical & Computer Eng. Queen's University Kingston, Ontario, K7L 3N6 Canada phone: +1 613-533-6368 fax: +1 613-533-6615 e-mail: chi-hsiang.yeh@ece.queensu.ca , yeh@ee.queensu.ca URL: http://www.ece.queensu.ca/hpages/faculty/yeh/ ___________________________________________________________ > Another problem is the short, but significant, transmission > delay. A terminal may sense that the busy channel is idle > and begin to transmit, unaware that another terminal has made > the same decision. Because the carriers takes a finite, > though brief, time to reach the other terminal and there is > inherent delay in the sensing and control processes, by the > time the carrier could be sensed, the terminal will already > be sending. > > > Later, > John Mullen > > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On > Behalf Of #LI ZHIFEI# > Sent: Thursday, July 10, 2003 7:06 AM > To: John Mullen > Cc: manet@ietf.org > Subject: RE: [manet] Carrier sense threshold/range control > > > > > >What you say is correct, but only to a point and with a reservation. > >First of all, although you can avoid collisions on the data > channel, I > >don't think you can avoid them completely on the busy tone channels. > > As for my understanding, in the busy channels, other > potentailly interfering nodes need not interpret the content > but just sensing the existence of busy carrier. So what do > you mean for the collisions on the busy channel? > > > >The more significant problem is that you are reserving part of your > >available spectrum for signaling. Whether this is done with > a separate > > >radio channel or with time division on a single channel, you are > >allowing only a fraction of the allotted band for data. > Thus, you need > > >to determine how much of the channel(s) need to be reserved for > >signaling. This would be a design matter and probably a tuning > >parameter, since the distribution of message lengths would determine > >the optimal signaling/data ratio. > > >This is not to say that such a thing is a bad idea, just that if not > >done properly, it could be an inefficient use of the available > >spectrum. > > I accept your viewpoint without any doubt. In addition to the > issue about the spectrum efficience, complexity may be > another issue by introducing multiple channels. > > > Best regards > > Li zhifei > > > > _______________________________________________ > 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 Jul 10 17:00:15 2003 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 RAA21381 for ; Thu, 10 Jul 2003 17:00:15 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aiW6-0007fk-Hb for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 16:59:50 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AKxo3n029492 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 16:59:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aiW6-0007fb-DE for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 16:59: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 QAA21261 for ; Thu, 10 Jul 2003 16:59:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aiW4-0007DH-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 16:59:48 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aiW3-0007DE-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 16:59:47 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aiVJ-0007Xm-7G; Thu, 10 Jul 2003 16: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 19aiUY-0007X0-C5 for manet@optimus.ietf.org; Thu, 10 Jul 2003 16:58: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 QAA21214 for ; Thu, 10 Jul 2003 16:58:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aiUU-0007CV-00 for manet@ietf.org; Thu, 10 Jul 2003 16:58:10 -0400 Received: from ecs.syr.edu ([128.230.208.14] helo=erebus.ecs.syr.edu) by ietf-mx with esmtp (Exim 4.12) id 19aiUU-0007CI-00 for manet@ietf.org; Thu, 10 Jul 2003 16:58:10 -0400 Received: from boreas.ecs.syr.edu (boreas.ecs.syr.edu [128.230.208.55]) by erebus.ecs.syr.edu (8.11.7+Sun/8.10.2) with ESMTP id h6AKw2K18130; Thu, 10 Jul 2003 16:58:04 -0400 (EDT) Date: Thu, 10 Jul 2003 16:58:02 -0400 (EDT) From: Jing Deng To: John Mullen cc: "'#LI ZHIFEI#'" , Subject: RE: [manet] Carrier sense threshold/range control In-Reply-To: <000101c3470d$c7ccf1b0$67f57b80@IEngr.ad.nmsu.edu> 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: , Dr. Mullen, I agree with you. It will be very difficult to eliminate collisions when distributed nodes (such as those in MANETs) are competing for a single shared channel. Due to signal propagation delays, carrier sensing delays, and processing delays, collisions will still exist even if carrier sensing technique is used (as you have assumed). However, if we use the busy tone or signaling channels properly, data packet collisions can be avoided. Only channel requests (RTS packets) are subject to possible collisions. Since the RTS packets are of much shorter length, performance gain of throughput can still be achieved. In what ratio the single channel is split affects the performance of the MAC scheme significantly (as you pointed out in your earlier post), especially when the RTS/CTS dialogues are to be transmitted on the control channel. We have found some interesting results and shown them in the following paper: J. Deng, Y. S. Han, and Z. J. Haas, "Analyzing Split Channel Medium Access Control Schemes with ALOHA Reservation," ADHOC-NOW '03, Montreal, Canada, October 8-10, 2003. (to appear) I will be happy to share it with anyone who is interested. Cheers, Jing ----------------------------------------------------------- Dr. Jing Deng http://www.cis.syr.edu/~jdeng01 2-191 CST, CASE Center Email: jdeng01@ecs.syr.edu Dept. of EECS Phone: (315) 443-3029 Syracuse University Fax: (315) 443-4745 Syracuse, NY 13244 --------------------------- @_@ --------------------------- On Thu, 10 Jul 2003, John Mullen wrote: > Hi Li, > > I'm not entirely sure how you use the busy tone channels, so my > statement may not be correct. However, a fundamental problem is in how > a terminal gets the right to use a channel. If terminals transmit RTSs > as the need arises, there is always a chance that those of different > terminals will collide with each other. This contention will have to > occur somewhere, whether on the signaling channel or the data channel. > So, wherever this signaling occurs is where the problem will be. > > Another problem is the short, but significant, transmission delay. A > terminal may sense that the busy channel is idle and begin to transmit, > unaware that another terminal has made the same decision. Because the > carriers takes a finite, though brief, time to reach the other terminal > and there is inherent delay in the sensing and control processes, by the > time the carrier could be sensed, the terminal will already be sending. > > > Later, > John Mullen > > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of > #LI ZHIFEI# > Sent: Thursday, July 10, 2003 7:06 AM > To: John Mullen > Cc: manet@ietf.org > Subject: RE: [manet] Carrier sense threshold/range control > > > > > >What you say is correct, but only to a point and with a reservation. > >First of all, although you can avoid collisions on the data channel, I > >don't think you can avoid them completely on the busy tone channels. > > As for my understanding, in the busy channels, other potentailly > interfering nodes need not interpret the content but just sensing the > existence of busy carrier. So what do you mean for the collisions on the > busy channel? > > > >The more significant problem is that you are reserving part of your > >available spectrum for signaling. Whether this is done with a separate > > >radio channel or with time division on a single channel, you are > >allowing only a fraction of the allotted band for data. Thus, you need > > >to determine how much of the channel(s) need to be reserved for > >signaling. This would be a design matter and probably a tuning > >parameter, since the distribution of message lengths would determine > >the optimal signaling/data ratio. > > >This is not to say that such a thing is a bad idea, just that if not > >done properly, it could be an inefficient use of the available > >spectrum. > > I accept your viewpoint without any doubt. In addition to the issue > about the spectrum efficience, complexity may be another issue by > introducing multiple channels. > > > Best regards > > Li zhifei > > > > _______________________________________________ > 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 Jul 10 17:26:46 2003 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 RAA22630 for ; Thu, 10 Jul 2003 17:26: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 19aivk-0002Pe-7g for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 17:26:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6ALQKwh009274 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 17:26:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aivk-0002PV-3Y for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 17:26: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 RAA22570 for ; Thu, 10 Jul 2003 17:26:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aivh-0007WZ-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 17:26:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aivh-0007WW-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 17:26:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aivS-0002LR-EV; Thu, 10 Jul 2003 17: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 19aiux-0002Kj-Ds for manet@optimus.ietf.org; Thu, 10 Jul 2003 17:25: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 RAA22552 for ; Thu, 10 Jul 2003 17:25:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aiuv-0007Vq-00 for manet@ietf.org; Thu, 10 Jul 2003 17:25:29 -0400 Received: from wasp.ece.queensu.ca ([130.15.22.4]) by ietf-mx with esmtp (Exim 4.12) id 19aiuu-0007Vn-00 for manet@ietf.org; Thu, 10 Jul 2003 17:25:28 -0400 Received: from acer7k2wrwolsy ([24.226.47.100]) by wasp.ECE.QUEENSU.CA with Microsoft SMTPSVC(5.0.2195.5329); Thu, 10 Jul 2003 17:26:01 -0400 From: "Chi-Hsiang Yeh" To: "'Nitin H. Vaidya'" , "'Alaa Muqattash'" Cc: "'MANET mailing list'" Subject: RE: [manet] Re: Carrier sense threshold/range control Date: Thu, 10 Jul 2003 17:25:08 -0400 Message-ID: <000901c34729$c02dbcc0$642fe218@acer7k2wrwolsy> 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: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 10 Jul 2003 21:26:01.0796 (UTC) FILETIME=[DCAB7040:01C34729] 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, Nitin, > On Wed, 9 Jul 2003, Alaa Muqattash wrote: > > . >>----- Original Message ----- > . >> > . >>> The gains could be much more interesting in the > scenario below, which . >>> simply reverses directions of > the data transmissions (provided that . >>> A does not pose > too much interference at C, and D at B). . >>> > . >>> A --------> B C <----------- D > . >>> > . >>> - nitin > . >> > . >> > . >>This is exactly what PCMA and PCDC do (see reference > below); they allow > > Not quite the same as PCMA ... since the basic RTS/CTS > mechanisms do not explicitly look at SNR, unlike PCMA. > > In any case, I think I got the example wrong in that it may > not be any more interesting than the example with the flows > in opposite directions. If B and C above were closer though, > one could conceive a bit smarter MAC -- for instance, if C > hears the RTS received by B from A, then C can overlap its > RTS with the CTS it expects B to send to A. Too complex for > this time of the day ... Could you explain your strategy (and the assumed scenario) more clearly? If C sends RTS then C is a transmitter and what you said is neither the above "A->B C<-D" scenario nor the "A<-B C->D" scenario (in Dmitri's mail). If C sends CTS and uses MACA/BI-type of mechanisms, the resultant strategy still has fundamental problems besides its complexity... Chihsiang _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 10 21:56:41 2003 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 VAA29918 for ; Thu, 10 Jul 2003 21:56:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19an8x-0005na-EV for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 21:56:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B1uFZY022284 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 21:56:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19an8x-0005nL-AD for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 21:56:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA29869 for ; Thu, 10 Jul 2003 21:56:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19an8u-0001Db-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 21:56:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19an8t-0001DY-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 21:56:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19an8k-0005by-9n; Thu, 10 Jul 2003 21:56:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19an82-0005bH-I3 for manet@optimus.ietf.org; Thu, 10 Jul 2003 21:55: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 VAA29865 for ; Thu, 10 Jul 2003 21:55:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19an7z-0001DT-00 for manet@ietf.org; Thu, 10 Jul 2003 21:55:15 -0400 Received: from [131.227.76.5] (helo=prue.eim.surrey.ac.uk ident=exim) by ietf-mx with esmtp (Exim 4.12) id 19an7z-0001DQ-00 for manet@ietf.org; Thu, 10 Jul 2003 21:55:15 -0400 Received: from romeo.ee.surrey.ac.uk ([131.227.76.30] helo=eim.surrey.ac.uk ident=www) by prue.eim.surrey.ac.uk with smtp (Exim 3.33 #4) id 19an7r-0001j1-00 for manet@ietf.org; Fri, 11 Jul 2003 02:55:07 +0100 Received: from open-net.ee.surrey.ac.uk ([131.227.76.238]) (SquirrelMail authenticated user eem1tk) by secure.eps.surrey.ac.uk with HTTP; Fri, 11 Jul 2003 02:55:07 +0100 (BST) Message-ID: <32782.131.227.76.238.1057888507.squirrel@secure.eps.surrey.ac.uk> Date: Fri, 11 Jul 2003 02:55:07 +0100 (BST) From: "Teng Kang" To: X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.9) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=-105.4 required=5.5 tests=BAYES_01,USER_IN_WHITELIST version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-Scanner: exiscan *19an7r-0001j1-00*i4DiXJ7SY82* (SECM, UniS) Content-Transfer-Encoding: 8bit Subject: [manet] Simulation under Glomosim2.03 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Dear all: Currently I am testing 802.11, which includes both PCF and DCF modes, under Glomosim 2.03. As I set the terrain-range greater than 300, the statics information is always incorrect and the running duratin of the simulation is abnormally short. Do you meet such kind of situation before and how to fix this kind of problem? Many thanks for your help in advance! Best Regards kangteng _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 10 22:15:46 2003 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 WAA00405 for ; Thu, 10 Jul 2003 22:15: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 19anRR-0007Uo-8R for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 22:15:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B2FLjk028808 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 22:15:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19anRR-0007UZ-4V for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 22:15: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 WAA00394 for ; Thu, 10 Jul 2003 22:15:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19anRN-0001Lk-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 22:15:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19anRM-0001Ld-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 22:15:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19anR7-0007O5-DB; Thu, 10 Jul 2003 22: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 19anQS-0007NH-Q0 for manet@optimus.ietf.org; Thu, 10 Jul 2003 22:14: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 WAA00386 for ; Thu, 10 Jul 2003 22:14:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19anQP-0001LS-00 for manet@ietf.org; Thu, 10 Jul 2003 22:14:17 -0400 Received: from mbox1.ntu.edu.sg ([155.69.5.171]) by ietf-mx with esmtp (Exim 4.12) id 19anQO-0001LK-00 for manet@ietf.org; Thu, 10 Jul 2003 22:14:17 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Fri, 11 Jul 2003 10:12:24 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Re: Carrier sense threshold/range control Date: Fri, 11 Jul 2003 10:12:24 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D819@mail01.student.main.ntu.edu.sg> Thread-Topic: [manet] Re: Carrier sense threshold/range control Thread-Index: AcNGc/Z4s+/0vBLeSxGNG3Nlp38WYAA3IUTg From: "#LI ZHIFEI#" To: "Nitin H. Vaidya" Cc: X-OriginalArrivalTime: 11 Jul 2003 02:12:24.0306 (UTC) FILETIME=[DE3E6520:01C34751] 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, prof. Nitin > If B and C above were closer though, one could conceive >a bit smarter MAC -- for instance, if C hears the RTS received >by B from A, then C can overlap its RTS with the CTS it expects B to >send to A. Too complex for this time of the day ... The problem for me is as follows: If node C can overhear the transmission of the RTS from node A to node = B, then, any transmission from=20 node C will interfere the frame reception at node A. Of course, we hold = the symmetry assumption.=20 So how could the transmission of RTS (from C) and the transmission of = CTS (from B ) can overlap? li zhifei -----Original Message----- From: Nitin H. Vaidya [mailto:nhv@crhc.uiuc.edu] Sent: dijous, 10 / juliol / 2003 07:40 To: Alaa Muqattash Cc: MANET mailing list Subject: Re: [manet] Re: Carrier sense threshold/range control On Wed, 9 Jul 2003, Alaa Muqattash wrote: . >>----- Original Message ----- . >> . >>> The gains could be much more interesting in the scenario below, = which . >>> simply reverses directions of the data transmissions (provided = that . >>> A does not pose too much interference at C, and D at B). . >>> . >>> A --------> B C <----------- D . >>> . >>> - nitin . >> . >> . >>This is exactly what PCMA and PCDC do (see reference below); they = allow Not quite the same as PCMA ... since the basic RTS/CTS mechanisms do not explicitly look at SNR, unlike PCMA. In any case, I think I got the example wrong in that it may not be any more interesting than the example with the flows in opposite directions. If B and C above were closer though, one could conceive a bit smarter MAC -- for instance, if C hears the RTS received by B from A, then C can overlap its RTS with the CTS it expects B to send to A. Too complex for this time of the day ... - nitin _______________________________________________ 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 Jul 10 22:36:43 2003 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 WAA01018 for ; Thu, 10 Jul 2003 22:36:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19anli-0000R6-Qh for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 22:36:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B2aIDM001674 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 22:36:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19anli-0000Qv-BE for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 22:36: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 WAA01012 for ; Thu, 10 Jul 2003 22:36:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19anlf-0001VX-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 22:36:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19anle-0001VU-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 22:36:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19anlR-0000KO-UK; Thu, 10 Jul 2003 22: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 19anl6-0000Jd-FO for manet@optimus.ietf.org; Thu, 10 Jul 2003 22:35:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00996 for ; Thu, 10 Jul 2003 22:35:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19anl3-0001V6-00 for manet@ietf.org; Thu, 10 Jul 2003 22:35:37 -0400 Received: from mbox1.ntu.edu.sg ([155.69.5.171]) by ietf-mx with esmtp (Exim 4.12) id 19anl2-0001Uk-00 for manet@ietf.org; Thu, 10 Jul 2003 22:35:36 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Fri, 11 Jul 2003 10:32:17 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Carrier sense threshold/range control Date: Fri, 11 Jul 2003 10:32:17 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D81D@mail01.student.main.ntu.edu.sg> Thread-Topic: [manet] Carrier sense threshold/range control Thread-Index: AcNHJffpKwCsfLxtQ4OooEwO1KL6FAALX7ug From: "#LI ZHIFEI#" To: X-OriginalArrivalTime: 11 Jul 2003 02:32:17.0370 (UTC) FILETIME=[A55D83A0:01C34754] 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 Yes, the objective of the handshaking (RTS/CTS/Data/ACK) is mainly to = protect the Data frame, which is normmally long. Therefore, the collision of short RTSs will not affect the channel = utilization too much. However, it will result in major problems if we consider fairness. As for the CTS, since its reception will enable the = transmission of Data, we should also preventing it from colliding. I think that is the main idea in DBTMA, i.e., protecting CTS and Data. -----Original Message----- From: Jing Deng [mailto:jdeng01@ecs.syr.edu] Sent: divendres, 11 / juliol / 2003 04:58 To: John Mullen Cc: #LI ZHIFEI#; manet@ietf.org Subject: RE: [manet] Carrier sense threshold/range control=20 Dr. Mullen, I agree with you. It will be very difficult to eliminate collisions when distributed nodes (such as those in MANETs) are competing for a single shared channel. Due to signal propagation delays, carrier sensing = delays, and processing delays, collisions will still exist even if carrier = sensing technique is used (as you have assumed). However, if we use the busy tone or signaling channels properly, data packet collisions can be avoided. Only channel requests (RTS packets) = are subject to possible collisions. Since the RTS packets are of much = shorter length, performance gain of throughput can still be achieved. In what ratio the single channel is split affects the performance of the MAC scheme significantly (as you pointed out in your earlier post), especially when the RTS/CTS dialogues are to be transmitted on the = control channel. We have found some interesting results and shown them in the following paper: J. Deng, Y. S. Han, and Z. J. Haas, "Analyzing Split Channel Medium = Access Control Schemes with ALOHA Reservation," ADHOC-NOW '03, Montreal, = Canada, October 8-10, 2003. (to appear) I will be happy to share it with anyone who is interested. Cheers, Jing ----------------------------------------------------------- Dr. Jing Deng http://www.cis.syr.edu/~jdeng01 2-191 CST, CASE Center Email: jdeng01@ecs.syr.edu Dept. of EECS Phone: (315) 443-3029 Syracuse University Fax: (315) 443-4745 Syracuse, NY 13244 --------------------------- @_@ --------------------------- On Thu, 10 Jul 2003, John Mullen wrote: > Hi Li, > > I'm not entirely sure how you use the busy tone channels, so my > statement may not be correct. However, a fundamental problem is in = how > a terminal gets the right to use a channel. If terminals transmit = RTSs > as the need arises, there is always a chance that those of different > terminals will collide with each other. This contention will have to > occur somewhere, whether on the signaling channel or the data channel. > So, wherever this signaling occurs is where the problem will be. > > Another problem is the short, but significant, transmission delay. A > terminal may sense that the busy channel is idle and begin to = transmit, > unaware that another terminal has made the same decision. Because the > carriers takes a finite, though brief, time to reach the other = terminal > and there is inherent delay in the sensing and control processes, by = the > time the carrier could be sensed, the terminal will already be = sending. > > > Later, > John Mullen > > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of > #LI ZHIFEI# > Sent: Thursday, July 10, 2003 7:06 AM > To: John Mullen > Cc: manet@ietf.org > Subject: RE: [manet] Carrier sense threshold/range control > > > > > >What you say is correct, but only to a point and with a reservation. > >First of all, although you can avoid collisions on the data channel, = I > >don't think you can avoid them completely on the busy tone channels. > > As for my understanding, in the busy channels, other potentailly > interfering nodes need not interpret the content but just sensing the > existence of busy carrier. So what do you mean for the collisions on = the > busy channel? > > > >The more significant problem is that you are reserving part of your > >available spectrum for signaling. Whether this is done with a = separate > > >radio channel or with time division on a single channel, you are > >allowing only a fraction of the allotted band for data. Thus, you = need > > >to determine how much of the channel(s) need to be reserved for > >signaling. This would be a design matter and probably a tuning > >parameter, since the distribution of message lengths would determine > >the optimal signaling/data ratio. > > >This is not to say that such a thing is a bad idea, just that if not > >done properly, it could be an inefficient use of the available > >spectrum. > > I accept your viewpoint without any doubt. In addition to the issue > about the spectrum efficience, complexity may be another issue by > introducing multiple channels. > > > Best regards > > Li zhifei > > > > _______________________________________________ > 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 Jul 10 22:58:46 2003 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 WAA01447 for ; Thu, 10 Jul 2003 22:58: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 19ao74-0002Uu-0C for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 22:58:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B2wLYx009600 for manet-archive@odin.ietf.org; Thu, 10 Jul 2003 22:58:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ao73-0002Ul-P4 for manet-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 22:58: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 WAA01434 for ; Thu, 10 Jul 2003 22:58:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ao70-0001by-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 22:58:18 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ao6z-0001bv-00 for manet-web-archive@ietf.org; Thu, 10 Jul 2003 22:58:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ao6j-0002TY-7S; Thu, 10 Jul 2003 22:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ao6Z-0002TH-3T for manet@optimus.ietf.org; Thu, 10 Jul 2003 22:57: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 WAA01430 for ; Thu, 10 Jul 2003 22:57:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ao6V-0001bs-00 for manet@ietf.org; Thu, 10 Jul 2003 22:57:47 -0400 Received: from mail11.ntu.edu.sg ([155.69.5.163]) by ietf-mx with esmtp (Exim 4.12) id 19ao6U-0001bo-00 for manet@ietf.org; Thu, 10 Jul 2003 22:57:47 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mail11.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Fri, 11 Jul 2003 10:54:51 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Carrier sense threshold/range control Date: Fri, 11 Jul 2003 10:54:51 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D824@mail01.student.main.ntu.edu.sg> Thread-Topic: [manet] Carrier sense threshold/range control Thread-Index: AcNG9NlrIY7GNsrMQzKR4vMBzAFKdgAYRt+A From: "#LI ZHIFEI#" To: , "Vikram Dham" X-OriginalArrivalTime: 11 Jul 2003 02:54:51.0572 (UTC) FILETIME=[CC885740:01C34757] 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 >>probability (distance between nodes > 2SR) =3D< probability (distance = between=20 >>nodes > SR ). =20 If you mean that (distance between nodes > 2TR) =3D< probability = (distance between=20 nodes > TR ), this may not be the case in the multi-hop wireless ad hoc = networks.=20 Of course, your statement should be held in the WLAN or single-hop ad = hoc networks. > Though we may not be elminating all the hidden terminals but we may = decrease=20 >the probability of occurence of hidden terminals by extending sensing = range to=20 >2SR. ???? >2TR The objective of elminating the hidden terminal problem is to reduce = collisions and thus=20 increase the channel utilization. However, if you increase the sensing = range, the interfering range is=20 also increased and thus the spatial reuse is greatly reduced. Of course, = if capture is enabled, it may be a different story. However, with capture, fairness becomse worse (which is = my main concern).=20 Moreover, as I have mentioned, when the sensing range (SR) is made = greater than transmission range (TR),=20 how long a node should defer its transmission when it detects a SR frame = is a very difficult job as=20 the node cannot interpret the conent of a SR frame. Li zhifei -----Original Message----- From: Vikram Dham [mailto:vdham@vt.edu] Sent: dijous, 10 / juliol / 2003 23:02 To: #LI ZHIFEI#; manet Subject: RE: [manet] Carrier sense threshold/range control Hello Zhifei Li, Though topology 2 also may have scenarios with hidden terminal, but in a = wireless network, probability (distance between nodes > 2SR) =3D< probability (distance = between=20 nodes > SR ). Though we may not be elminating all the hidden terminals but we may = decrease=20 the probability of occurence of hidden terminals by extending sensing = range to=20 2SR. Regards Vikram Dham >=3D=3D=3D=3D=3D Original Message From #LI ZHIFEI# = =3D=3D=3D=3D=3D >Hi, Ram > >In my view, even the Carrier Sensing Range (SR) is two times of the=20 Transmission Range (TR ), the hidden-termianl problem is still there. >This can be illustrated as the following two topologies: > >Topology 1: Topology 2: > >A -> B <- C A -> B C<- = D > >(note that the distance between two neighboring nodes are equal to the=20 transmission range, i.e., one hop) > >The first topology is tipycally used to illustrate the well-known=20 hidden-terminal problem, but with an implicit assumption, i.e., SR=3DTR. >If SR=3D2*TR, the hidden-terminal problem seems not exist any more in = this=20 topology as the nodes A and C can sense the transmission of each other. > >However, even SR=3D2*TR, the problem will arise in the second topology. = Specically, when node A starts to transmit to node B, since node D >is out of the SR of node A, it cannot detect the transmission. = Therefore,=20 node D may also start to transmit to node C, resulting in collision (or=20 capture). >In such case, we can say that nodes A and D are hidden terminal of each = other. We do find the similarities of the performance between the two = cases: >topology 1 when SR=3DTR; and topology 2 when SR=3D2*TR > > >When SR>TR, another problem is that how a node should defer its = transmission=20 when it detects a SR frame. This is not an easy job since the node = cannot >interpret the content of the SR frame. In the IEEE 802.11, whenever a = node=20 detects a SR frame, it will defer by a fixed EFIS value. However, our = results=20 show >this fixed value will cause many problems, e.g., unfairness. Moreover, = the=20 capture ability will also greatly affect the performace when SR>TR. >For a detailed descrition of these issues, please refer to the attached = references: > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, >"Improving Fairness in IEEE 802.11 based MANETs using Enhanced Carrier=20 Sensing", submitted to conference, April 2003 >http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, >"Study of IEEE 802.11 Fairness and its Interaction with Routing = Mechanism",=20 accepted by IEEE MWCN 2003 Singapore, May 2003 >http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf > > >Though the above papers mainly focus on the the fairness issue when = SR>TR,=20 the descirtion should also apply to the analysis of the channel = utilization. >I hope that they will relate to your work and help you. > > >Best regards >Li ZhiFei >PhD candidate, >Center For Multimedia And Network Technology >School Of Computer Engineering >Nanyang Technological University >N4-b2c-08, Nanyang Avenue >Singapore 639798 >tel:(65)67906579 >website: > > >-----Original Message----- >From: Ram Ramanathan [mailto:ramanath@bbn.com] >Sent: dijous, 10 / juliol / 2003 00:09 >To: manet@ietf.org >Cc: ramanath@bbn.com >Subject: [manet] Carrier sense threshold/range control > > > >I am looking for pointers to research on the control of carrier sensing >range in lieu of using RTS/CTS to address the hidden node problem? > >To elaborate, the threshold for when carrier is declared to be "sensed" >can be adjusted in many radios. Using this facility, one could possibly >make the "carrier sense range" approximately twice the "communication = range" >(successful packet reception), and detect hidden nodes. > >This is by no means a new idea, and I vaguely recally some mention of >it on this list. Of course, there are a number of factors that make the >problem far more complex than the simple statement above indicates, and >it is not immediately clear whether it will be effective at all. > >I am looking for papers, tech reports, or any publicly available = material >(non-proprietary) on this issue. > >Many thanks in advance, > >-Ram. > >_______________________________________________ >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 exim@www1.ietf.org Fri Jul 11 00:10:54 2003 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 AAA03275 for ; Fri, 11 Jul 2003 00:10:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19apEm-0007q9-7F for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 00:10:28 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B4AOV5030132 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 00:10:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19apEm-0007pv-0Z for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 00:10: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 AAA03256 for ; Fri, 11 Jul 2003 00:10:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19apEj-00025f-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 00:10:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19apEj-00025c-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 00:10:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19apEP-0007ly-Nr; Fri, 11 Jul 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 19apDl-0007lS-O4 for manet@optimus.ietf.org; Fri, 11 Jul 2003 00:09: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 AAA03244 for ; Fri, 11 Jul 2003 00:09:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19apDj-00025K-00 for manet@ietf.org; Fri, 11 Jul 2003 00:09:19 -0400 Received: from wasp.ece.queensu.ca ([130.15.19.4]) by ietf-mx with esmtp (Exim 4.12) id 19apDi-00025H-00 for manet@ietf.org; Fri, 11 Jul 2003 00:09:18 -0400 Received: from acer7k2wrwolsy ([24.226.47.100]) by wasp.ECE.QUEENSU.CA with Microsoft SMTPSVC(5.0.2195.5329); Fri, 11 Jul 2003 00:09:49 -0400 From: "Chi-Hsiang Yeh" To: "'#LI ZHIFEI#'" , Cc: "'Vikram Dham'" Subject: RE: [manet] Carrier sense threshold/range control Date: Fri, 11 Jul 2003 00:08:47 -0400 Message-ID: <001401c34762$23baaef0$642fe218@acer7k2wrwolsy> 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: <3D565922795545468AE3E3DA2881BEA90186D824@mail01.student.main.ntu.edu.sg> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 11 Jul 2003 04:09:49.0234 (UTC) FILETIME=[45591920:01C34762] 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, Zhifei, > > Though we may not be elminating all the hidden terminals but we may > >decrease > >the probability of occurence of hidden terminals by > extending sensing range to > >2SR. ???? >2TR > > The objective of elminating the hidden terminal problem is to > reduce collisions and thus > increase the channel utilization. However, if you increase > the sensing range, the interfering range is > also increased and thus the spatial reuse is greatly reduced. This is not true. Besides SR and TR, there is another parameter "interference range (IR)", which is not necessarily equal to SR. By lowering the threshold for sensing, increasing SR does not affect IR. Instead, IR is increased when the associated transmission power level is increased. Also, when SR >= IR + TR, topology 2 (in your previous e-mail) and other topologies without obstacles would not suffer from the hidden terminal problem (without considering collisions of control messages and propagation characteristics/delays etc. of course). Chihsiang > Of course, if capture is enabled, it may be a different > story. However, with capture, fairness becomse worse (which > is my main concern). > Moreover, as I have mentioned, when the sensing range (SR) is > made greater than transmission range (TR), > how long a node should defer its transmission when it detects > a SR frame is a very difficult job as > the node cannot interpret the conent of a SR frame. > > > > Li zhifei > > > -----Original Message----- > From: Vikram Dham [mailto:vdham@vt.edu] > Sent: dijous, 10 / juliol / 2003 23:02 > To: #LI ZHIFEI#; manet > Subject: RE: [manet] Carrier sense threshold/range control > > > Hello Zhifei Li, > > Though topology 2 also may have scenarios with hidden > terminal, but in a > wireless network, > > probability (distance between nodes > 2SR) =< probability > (distance between > nodes > SR ). > > Though we may not be elminating all the hidden terminals but > we may decrease > the probability of occurence of hidden terminals by extending > sensing range to > 2SR. > > Regards > > Vikram Dham > >===== Original Message From #LI ZHIFEI# > >===== Hi, Ram > > > >In my view, even the Carrier Sensing Range (SR) is two times of the > Transmission Range (TR ), the hidden-termianl problem is still there. > >This can be illustrated as the following two topologies: > > > >Topology 1: Topology 2: > > > >A -> B <- C A -> B C<- D > > > >(note that the distance between two neighboring nodes are > equal to the > transmission range, i.e., one hop) > > > >The first topology is tipycally used to illustrate the well-known > hidden-terminal problem, but with an implicit assumption, i.e., SR=TR. > >If SR=2*TR, the hidden-terminal problem seems not exist any more in > >this > topology as the nodes A and C can sense the transmission of > each other. > > > >However, even SR=2*TR, the problem will arise in the second topology. > Specically, when node A starts to transmit to node B, since node D > >is out of the SR of node A, it cannot detect the transmission. > >Therefore, > node D may also start to transmit to node C, resulting in > collision (or > capture). > >In such case, we can say that nodes A and D are hidden > terminal of each > other. We do find the similarities of the performance between > the two cases: > >topology 1 when SR=TR; and topology 2 when SR=2*TR > > > > > >When SR>TR, another problem is that how a node should defer its > >transmission > when it detects a SR frame. This is not an easy job since the > node cannot > >interpret the content of the SR frame. In the IEEE 802.11, > whenever a > >node > detects a SR frame, it will defer by a fixed EFIS value. > However, our results > show > >this fixed value will cause many problems, e.g., unfairness. > Moreover, > >the > capture ability will also greatly affect the performace when SR>TR. > >For a detailed descrition of these issues, please refer to > the attached > references: > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > >"Improving Fairness in IEEE 802.11 based MANETs using > Enhanced Carrier > Sensing", submitted to conference, April 2003 > >http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > >"Study of IEEE 802.11 Fairness and its Interaction with Routing > >Mechanism", > accepted by IEEE MWCN 2003 Singapore, May 2003 > >http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf > > > > > >Though the above papers mainly focus on the the fairness issue when > >SR>TR, > the descirtion should also apply to the analysis of the > channel utilization. > >I hope that they will relate to your work and help you. > > > > > >Best regards > >Li ZhiFei > >PhD candidate, > >Center For Multimedia And Network Technology > >School Of Computer Engineering > >Nanyang Technological University > >N4-b2c-08, Nanyang Avenue > >Singapore 639798 > >tel:(65)67906579 > >website: > > > > > >-----Original Message----- > >From: Ram Ramanathan [mailto:ramanath@bbn.com] > >Sent: dijous, 10 / juliol / 2003 00:09 > >To: manet@ietf.org > >Cc: ramanath@bbn.com > >Subject: [manet] Carrier sense threshold/range control > > > > > > > >I am looking for pointers to research on the control of > carrier sensing > >range in lieu of using RTS/CTS to address the hidden node problem? > > > >To elaborate, the threshold for when carrier is declared to > be "sensed" > >can be adjusted in many radios. Using this facility, one > could possibly > >make the "carrier sense range" approximately twice the > "communication > >range" (successful packet reception), and detect hidden nodes. > > > >This is by no means a new idea, and I vaguely recally some > mention of > >it on this list. Of course, there are a number of factors > that make the > >problem far more complex than the simple statement above > indicates, and > >it is not immediately clear whether it will be effective at all. > > > >I am looking for papers, tech reports, or any publicly available > >material > >(non-proprietary) on this issue. > > > >Many thanks in advance, > > > >-Ram. > > > >_______________________________________________ > >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 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 11 00:40:39 2003 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 AAA03879 for ; Fri, 11 Jul 2003 00:40:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aphd-0001ri-QR for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 00:40:14 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B4eDMr007163 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 00:40:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aphd-0001rS-6R for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 00:40: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 AAA03864 for ; Fri, 11 Jul 2003 00:40:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19apha-0002Dq-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 00:40:10 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19apha-0002Dn-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 00:40:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aphR-0001gC-V3; Fri, 11 Jul 2003 00:40:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19apgb-0001ZD-PC for manet@optimus.ietf.org; Fri, 11 Jul 2003 00:39: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 AAA03860 for ; Fri, 11 Jul 2003 00:39:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19apgZ-0002Dj-00 for manet@ietf.org; Fri, 11 Jul 2003 00:39:07 -0400 Received: from law15-f112.law15.hotmail.com ([64.4.23.112] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19apgY-0002Dg-00 for manet@ietf.org; Fri, 11 Jul 2003 00:39:06 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 10 Jul 2003 21:38:22 -0700 Received: from 62.135.24.123 by lw15fd.law15.hotmail.msn.com with HTTP; Fri, 11 Jul 2003 04:38:22 GMT X-Originating-IP: [62.135.24.123] X-Originating-Email: [reh_elmayet@hotmail.com] From: "reham elmayet" To: manet@ietf.org Date: Fri, 11 Jul 2003 04:38:22 +0000 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 11 Jul 2003 04:38:22.0733 (UTC) FILETIME=[42AC4BD0:01C34766] 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,
please, can I get the ns2 source code for LAR and DREAM ad hoc routing protocols?
please help me
thank you,
regarards,
Reham Elmayet

MSN 8 helps ELIMINATE E-MAIL VIRUSES. Get 2 months FREE*. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 11 02:53:47 2003 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 CAA18541 for ; Fri, 11 Jul 2003 02:53: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 19armO-0003VJ-G4 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 02:53:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B6rGUh013468 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 02:53:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19armN-0003V7-Vz for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 02: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 CAA18533 for ; Fri, 11 Jul 2003 02:53:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19armK-0002vk-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 02:53:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19armJ-0002vh-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 02:53:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19armA-0003To-Dx; Fri, 11 Jul 2003 02:53:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19arlG-0003Sj-GH for manet@optimus.ietf.org; Fri, 11 Jul 2003 02:52: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 CAA18525 for ; Fri, 11 Jul 2003 02:52:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19arlC-0002vS-00 for manet@ietf.org; Fri, 11 Jul 2003 02:52:02 -0400 Received: from [130.15.22.4] (helo=wasp.ECE.QUEENSU.CA) by ietf-mx with esmtp (Exim 4.12) id 19arlB-0002vP-00 for manet@ietf.org; Fri, 11 Jul 2003 02:52:01 -0400 Received: from acer7k2wrwolsy ([24.226.47.100]) by wasp.ECE.QUEENSU.CA with Microsoft SMTPSVC(5.0.2195.5329); Fri, 11 Jul 2003 02:52:36 -0400 From: "Chi-Hsiang Yeh" To: "'#LI ZHIFEI#'" , "'Nitin H. Vaidya'" Cc: Subject: RE: [manet] Re: Carrier sense threshold/range control Date: Fri, 11 Jul 2003 02:51:41 -0400 Message-ID: <001701c34778$e5ab4400$642fe218@acer7k2wrwolsy> 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: <3D565922795545468AE3E3DA2881BEA90186D819@mail01.student.main.ntu.edu.sg> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 11 Jul 2003 06:52:36.0250 (UTC) FILETIME=[02F177A0:01C34779] 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 > -----Original Message----- > From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On > Behalf Of #LI ZHIFEI# > Sent: Thursday, July 10, 2003 10:12 PM > To: Nitin H. Vaidya > Cc: manet@ietf.org > Subject: RE: [manet] Re: Carrier sense threshold/range control > > > hi, prof. Nitin > > > > If B and C above were closer though, one could conceive > >a bit smarter MAC -- for instance, if C hears the RTS received by B > >from A, then C can overlap its RTS with the CTS it expects B > to send to > >A. Too complex for this time of the day ... > > The problem for me is as follows: > > If node C can overhear the transmission of the RTS from node > A to node B, then, any transmission from > node C will interfere the frame reception at node A. Of > course, we hold the symmetry assumption. > > So how could the transmission of RTS (from C) and the > transmission of CTS (from B ) can overlap? Another problem: When C is close to B and C is really a transmitter (rather than being mistaken due to typos in the original e-mail), the data reception at B will be collided by the data transmission from C even if the above dialogues work due to capture. Chihsiang > > > li zhifei > > > > -----Original Message----- > From: Nitin H. Vaidya [mailto:nhv@crhc.uiuc.edu] > Sent: dijous, 10 / juliol / 2003 07:40 > To: Alaa Muqattash > Cc: MANET mailing list > Subject: Re: [manet] Re: Carrier sense threshold/range control > > > > On Wed, 9 Jul 2003, Alaa Muqattash wrote: > > . >>----- Original Message ----- > . >> > . >>> The gains could be much more interesting in the > scenario below, which . >>> simply reverses directions of > the data transmissions (provided that . >>> A does not pose > too much interference at C, and D at B). . >>> > . >>> A --------> B C <----------- D > . >>> > . >>> - nitin > . >> > . >> > . >>This is exactly what PCMA and PCDC do (see reference > below); they allow > > Not quite the same as PCMA ... since the basic RTS/CTS > mechanisms do not explicitly look at SNR, unlike PCMA. > > In any case, I think I got the example wrong in that it may > not be any more interesting than the example with the flows > in opposite directions. If B and C above were closer though, > one could conceive a bit smarter MAC -- for instance, if C > hears the RTS received by B from A, then C can overlap its > RTS with the CTS it expects B to send to A. Too complex for > this time of the day ... > > - nitin > > > _______________________________________________ > 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 Fri Jul 11 04:15:02 2003 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 EAA20332 for ; Fri, 11 Jul 2003 04:15:01 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19at2z-0001hi-Ke for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 04:14:34 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B8ESo1006543 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 04:14:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19at2x-0001hS-D4 for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 04:14: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 EAA20321 for ; Fri, 11 Jul 2003 04:14:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19at2u-0003Ny-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 04:14:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19at2u-0003Nv-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 04:14:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19at2X-0001g6-PP; Fri, 11 Jul 2003 04:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19at1r-0001f8-K8 for manet@optimus.ietf.org; Fri, 11 Jul 2003 04:13: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 EAA20315 for ; Fri, 11 Jul 2003 04:13:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19at1o-0003Na-00 for manet@ietf.org; Fri, 11 Jul 2003 04:13:16 -0400 Received: from mbox1.ntu.edu.sg ([155.69.5.171]) by ietf-mx with esmtp (Exim 4.12) id 19at1n-0003NU-00 for manet@ietf.org; Fri, 11 Jul 2003 04:13:15 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Fri, 11 Jul 2003 16:12:30 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Carrier sense threshold/range control Date: Fri, 11 Jul 2003 16:12:30 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D842@mail01.student.main.ntu.edu.sg> Thread-Topic: [manet] Carrier sense threshold/range control Thread-Index: AcNHYjPY7LQ4sw/cT/+Bk01y/iWrNwAFdD3g From: "#LI ZHIFEI#" To: "Chi-Hsiang Yeh" , X-OriginalArrivalTime: 11 Jul 2003 08:12:30.0914 (UTC) FILETIME=[2CC92220:01C34784] 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 Is there any formal definition about the "interference range"? The definition of "interference range" in the following paper is some = confusing to me. How effective is the IEEE 802.11 RTS/CTS handshake in ad hoc networks?=20 Kaixin Xu; Gerla, M.; Sang Bae;=20 Global Telecommunications Conference, 2002. GLOBECOM '02. IEEE , Volume: = 1 , Nov 17-21, 2002=20 Page(s): 72 -76 However, I do believe that when SR is increased, the spatial reuse in = multi-hop networks will be substantially reduced, which is also pointed = out in the above paper. Best regards=20 Li ZhiFei=20 PhD candidate, =20 Center For Multimedia And Network Technology School Of Computer Engineering Nanyang Technological University N4-b2c-08, Nanyang Avenue Singapore 639798 tel:(65)67906579=20 website: =20 -----Original Message----- From: Chi-Hsiang Yeh [mailto:chi-hsiang.yeh@ece.queensu.ca] Sent: divendres, 11 / juliol / 2003 12:09 To: #LI ZHIFEI#; manet@ietf.org Cc: 'Vikram Dham' Subject: RE: [manet] Carrier sense threshold/range control Hi, Zhifei, > > Though we may not be elminating all the hidden terminals but we may=20 > >decrease > >the probability of occurence of hidden terminals by=20 > extending sensing range to=20 > >2SR. ???? >2TR > > The objective of elminating the hidden terminal problem is to=20 > reduce collisions and thus=20 > increase the channel utilization. However, if you increase=20 > the sensing range, the interfering range is=20 > also increased and thus the spatial reuse is greatly reduced.=20 This is not true. Besides SR and TR, there is another parameter "interference range (IR)", which is not necessarily equal to SR. By lowering the threshold for sensing, increasing SR does not affect IR. Instead, IR is increased when the associated transmission power level is increased. Also, when SR >=3D IR + TR, topology 2 (in your previous e-mail) and = other topologies without obstacles would not suffer from the hidden terminal problem (without considering collisions of control messages and propagation characteristics/delays etc. of course). Chihsiang > Of course, if capture is enabled, it may be a different=20 > story. However, with capture, fairness becomse worse (which=20 > is my main concern).=20 > Moreover, as I have mentioned, when the sensing range (SR) is=20 > made greater than transmission range (TR),=20 > how long a node should defer its transmission when it detects=20 > a SR frame is a very difficult job as=20 > the node cannot interpret the conent of a SR frame. >=20 >=20 >=20 > Li zhifei >=20 >=20 > -----Original Message----- > From: Vikram Dham [mailto:vdham@vt.edu] > Sent: dijous, 10 / juliol / 2003 23:02 > To: #LI ZHIFEI#; manet > Subject: RE: [manet] Carrier sense threshold/range control >=20 >=20 > Hello Zhifei Li, >=20 > Though topology 2 also may have scenarios with hidden=20 > terminal, but in a=20 > wireless network, >=20 > probability (distance between nodes > 2SR) =3D< probability=20 > (distance between=20 > nodes > SR ). >=20 > Though we may not be elminating all the hidden terminals but=20 > we may decrease=20 > the probability of occurence of hidden terminals by extending=20 > sensing range to=20 > 2SR. >=20 > Regards >=20 > Vikram Dham > >=3D=3D=3D=3D=3D Original Message From #LI ZHIFEI# = =20 > >=3D=3D=3D=3D=3D Hi, Ram > > > >In my view, even the Carrier Sensing Range (SR) is two times of the > Transmission Range (TR ), the hidden-termianl problem is still there. > >This can be illustrated as the following two topologies: > > > >Topology 1: Topology 2: > > > >A -> B <- C A -> B C<- D > > > >(note that the distance between two neighboring nodes are=20 > equal to the > transmission range, i.e., one hop) > > > >The first topology is tipycally used to illustrate the well-known > hidden-terminal problem, but with an implicit assumption, i.e., = SR=3DTR. > >If SR=3D2*TR, the hidden-terminal problem seems not exist any more in = > >this > topology as the nodes A and C can sense the transmission of=20 > each other. > > > >However, even SR=3D2*TR, the problem will arise in the second = topology. > Specically, when node A starts to transmit to node B, since node D > >is out of the SR of node A, it cannot detect the transmission.=20 > >Therefore, > node D may also start to transmit to node C, resulting in=20 > collision (or=20 > capture). > >In such case, we can say that nodes A and D are hidden=20 > terminal of each > other. We do find the similarities of the performance between=20 > the two cases: > >topology 1 when SR=3DTR; and topology 2 when SR=3D2*TR > > > > > >When SR>TR, another problem is that how a node should defer its=20 > >transmission > when it detects a SR frame. This is not an easy job since the=20 > node cannot > >interpret the content of the SR frame. In the IEEE 802.11,=20 > whenever a=20 > >node > detects a SR frame, it will defer by a fixed EFIS value.=20 > However, our results=20 > show > >this fixed value will cause many problems, e.g., unfairness.=20 > Moreover,=20 > >the > capture ability will also greatly affect the performace when SR>TR. > >For a detailed descrition of these issues, please refer to=20 > the attached > references: > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > >"Improving Fairness in IEEE 802.11 based MANETs using=20 > Enhanced Carrier > Sensing", submitted to conference, April 2003 > >http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > >"Study of IEEE 802.11 Fairness and its Interaction with Routing=20 > >Mechanism", > accepted by IEEE MWCN 2003 Singapore, May 2003 > >http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf > > > > > >Though the above papers mainly focus on the the fairness issue when=20 > >SR>TR, > the descirtion should also apply to the analysis of the=20 > channel utilization. > >I hope that they will relate to your work and help you. > > > > > >Best regards > >Li ZhiFei > >PhD candidate, > >Center For Multimedia And Network Technology > >School Of Computer Engineering > >Nanyang Technological University > >N4-b2c-08, Nanyang Avenue > >Singapore 639798 > >tel:(65)67906579 > >website: > > > > > >-----Original Message----- > >From: Ram Ramanathan [mailto:ramanath@bbn.com] > >Sent: dijous, 10 / juliol / 2003 00:09 > >To: manet@ietf.org > >Cc: ramanath@bbn.com > >Subject: [manet] Carrier sense threshold/range control > > > > > > > >I am looking for pointers to research on the control of=20 > carrier sensing=20 > >range in lieu of using RTS/CTS to address the hidden node problem? > > > >To elaborate, the threshold for when carrier is declared to=20 > be "sensed"=20 > >can be adjusted in many radios. Using this facility, one=20 > could possibly=20 > >make the "carrier sense range" approximately twice the=20 > "communication=20 > >range" (successful packet reception), and detect hidden nodes. > > > >This is by no means a new idea, and I vaguely recally some=20 > mention of=20 > >it on this list. Of course, there are a number of factors=20 > that make the=20 > >problem far more complex than the simple statement above=20 > indicates, and=20 > >it is not immediately clear whether it will be effective at all. > > > >I am looking for papers, tech reports, or any publicly available=20 > >material > >(non-proprietary) on this issue. > > > >Many thanks in advance, > > > >-Ram. > > > >_______________________________________________ > >manet mailing list > >manet@ietf.org > >https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > > >_______________________________________________ > >manet mailing list > >manet@ietf.org > >https://www1.ietf.org/mailman/listinfo/manet >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 11 04:46:54 2003 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 EAA21281 for ; Fri, 11 Jul 2003 04:46:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19atXv-0004Pl-Tg for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 04:46:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B8kRct016970 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 04:46:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19atXt-0004PZ-Uk for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 04:46: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 EAA21269 for ; Fri, 11 Jul 2003 04:46:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19atXr-0003fu-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 04:46:23 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19atXq-0003fr-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 04:46:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19atXV-0004Is-NW; Fri, 11 Jul 2003 04:46:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19atXA-0004Ia-KA for manet@optimus.ietf.org; Fri, 11 Jul 2003 04: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 EAA21260 for ; Fri, 11 Jul 2003 04:45:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19atX7-0003fY-00 for manet@ietf.org; Fri, 11 Jul 2003 04:45:37 -0400 Received: from mbox1.ntu.edu.sg ([155.69.5.171]) by ietf-mx with esmtp (Exim 4.12) id 19atX6-0003fL-00 for manet@ietf.org; Fri, 11 Jul 2003 04:45:36 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Fri, 11 Jul 2003 16:44:33 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Carrier sense threshold/range control Date: Fri, 11 Jul 2003 16:44:33 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D847@mail01.student.main.ntu.edu.sg> Thread-Topic: [manet] Carrier sense threshold/range control Thread-Index: AcNHYjPY7LQ4sw/cT/+Bk01y/iWrNwAJSTtQ From: "#LI ZHIFEI#" To: "Chi-Hsiang Yeh" Cc: X-OriginalArrivalTime: 11 Jul 2003 08:44:33.0543 (UTC) FILETIME=[A6C30970:01C34788] 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 >Also, when SR >=3D IR + TR, topology 2 (in your previous e-mail) and = other >topologies without obstacles would not suffer from the hidden terminal >problem (without considering collisions of control messages and >propagation characteristics/delays etc. of course). That is true but at the cost of capacity. Moreover, if SR >=3D IR + TR, = it seems that the RTS/CTS do not have much meaning=20 any more. However, as pointed out by some work, whether the SR can be = set to greater than (IR + TR) depends upon the antenna's sensitivity. -----Original Message----- From: Chi-Hsiang Yeh [mailto:chi-hsiang.yeh@ece.queensu.ca] Sent: divendres, 11 / juliol / 2003 12:09 To: #LI ZHIFEI#; manet@ietf.org Cc: 'Vikram Dham' Subject: RE: [manet] Carrier sense threshold/range control Hi, Zhifei, > > Though we may not be elminating all the hidden terminals but we may=20 > >decrease > >the probability of occurence of hidden terminals by=20 > extending sensing range to=20 > >2SR. ???? >2TR > > The objective of elminating the hidden terminal problem is to=20 > reduce collisions and thus=20 > increase the channel utilization. However, if you increase=20 > the sensing range, the interfering range is=20 > also increased and thus the spatial reuse is greatly reduced.=20 This is not true. Besides SR and TR, there is another parameter "interference range (IR)", which is not necessarily equal to SR. By lowering the threshold for sensing, increasing SR does not affect IR. Instead, IR is increased when the associated transmission power level is increased. Also, when SR >=3D IR + TR, topology 2 (in your previous e-mail) and = other topologies without obstacles would not suffer from the hidden terminal problem (without considering collisions of control messages and propagation characteristics/delays etc. of course). Chihsiang > Of course, if capture is enabled, it may be a different=20 > story. However, with capture, fairness becomse worse (which=20 > is my main concern).=20 > Moreover, as I have mentioned, when the sensing range (SR) is=20 > made greater than transmission range (TR),=20 > how long a node should defer its transmission when it detects=20 > a SR frame is a very difficult job as=20 > the node cannot interpret the conent of a SR frame. >=20 >=20 >=20 > Li zhifei >=20 >=20 > -----Original Message----- > From: Vikram Dham [mailto:vdham@vt.edu] > Sent: dijous, 10 / juliol / 2003 23:02 > To: #LI ZHIFEI#; manet > Subject: RE: [manet] Carrier sense threshold/range control >=20 >=20 > Hello Zhifei Li, >=20 > Though topology 2 also may have scenarios with hidden=20 > terminal, but in a=20 > wireless network, >=20 > probability (distance between nodes > 2SR) =3D< probability=20 > (distance between=20 > nodes > SR ). >=20 > Though we may not be elminating all the hidden terminals but=20 > we may decrease=20 > the probability of occurence of hidden terminals by extending=20 > sensing range to=20 > 2SR. >=20 > Regards >=20 > Vikram Dham > >=3D=3D=3D=3D=3D Original Message From #LI ZHIFEI# = =20 > >=3D=3D=3D=3D=3D Hi, Ram > > > >In my view, even the Carrier Sensing Range (SR) is two times of the > Transmission Range (TR ), the hidden-termianl problem is still there. > >This can be illustrated as the following two topologies: > > > >Topology 1: Topology 2: > > > >A -> B <- C A -> B C<- D > > > >(note that the distance between two neighboring nodes are=20 > equal to the > transmission range, i.e., one hop) > > > >The first topology is tipycally used to illustrate the well-known > hidden-terminal problem, but with an implicit assumption, i.e., = SR=3DTR. > >If SR=3D2*TR, the hidden-terminal problem seems not exist any more in = > >this > topology as the nodes A and C can sense the transmission of=20 > each other. > > > >However, even SR=3D2*TR, the problem will arise in the second = topology. > Specically, when node A starts to transmit to node B, since node D > >is out of the SR of node A, it cannot detect the transmission.=20 > >Therefore, > node D may also start to transmit to node C, resulting in=20 > collision (or=20 > capture). > >In such case, we can say that nodes A and D are hidden=20 > terminal of each > other. We do find the similarities of the performance between=20 > the two cases: > >topology 1 when SR=3DTR; and topology 2 when SR=3D2*TR > > > > > >When SR>TR, another problem is that how a node should defer its=20 > >transmission > when it detects a SR frame. This is not an easy job since the=20 > node cannot > >interpret the content of the SR frame. In the IEEE 802.11,=20 > whenever a=20 > >node > detects a SR frame, it will defer by a fixed EFIS value.=20 > However, our results=20 > show > >this fixed value will cause many problems, e.g., unfairness.=20 > Moreover,=20 > >the > capture ability will also greatly affect the performace when SR>TR. > >For a detailed descrition of these issues, please refer to=20 > the attached > references: > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > >"Improving Fairness in IEEE 802.11 based MANETs using=20 > Enhanced Carrier > Sensing", submitted to conference, April 2003 > >http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > >"Study of IEEE 802.11 Fairness and its Interaction with Routing=20 > >Mechanism", > accepted by IEEE MWCN 2003 Singapore, May 2003 > >http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf > > > > > >Though the above papers mainly focus on the the fairness issue when=20 > >SR>TR, > the descirtion should also apply to the analysis of the=20 > channel utilization. > >I hope that they will relate to your work and help you. > > > > > >Best regards > >Li ZhiFei > >PhD candidate, > >Center For Multimedia And Network Technology > >School Of Computer Engineering > >Nanyang Technological University > >N4-b2c-08, Nanyang Avenue > >Singapore 639798 > >tel:(65)67906579 > >website: > > > > > >-----Original Message----- > >From: Ram Ramanathan [mailto:ramanath@bbn.com] > >Sent: dijous, 10 / juliol / 2003 00:09 > >To: manet@ietf.org > >Cc: ramanath@bbn.com > >Subject: [manet] Carrier sense threshold/range control > > > > > > > >I am looking for pointers to research on the control of=20 > carrier sensing=20 > >range in lieu of using RTS/CTS to address the hidden node problem? > > > >To elaborate, the threshold for when carrier is declared to=20 > be "sensed"=20 > >can be adjusted in many radios. Using this facility, one=20 > could possibly=20 > >make the "carrier sense range" approximately twice the=20 > "communication=20 > >range" (successful packet reception), and detect hidden nodes. > > > >This is by no means a new idea, and I vaguely recally some=20 > mention of=20 > >it on this list. Of course, there are a number of factors=20 > that make the=20 > >problem far more complex than the simple statement above=20 > indicates, and=20 > >it is not immediately clear whether it will be effective at all. > > > >I am looking for papers, tech reports, or any publicly available=20 > >material > >(non-proprietary) on this issue. > > > >Many thanks in advance, > > > >-Ram. > > > >_______________________________________________ > >manet mailing list > >manet@ietf.org > >https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > > >_______________________________________________ > >manet mailing list > >manet@ietf.org > >https://www1.ietf.org/mailman/listinfo/manet >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 11 06:06:47 2003 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 GAA23552 for ; Fri, 11 Jul 2003 06:06: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 19aunA-0002W2-AW for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 06:06:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BA6G8X009664 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 06:06:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aunA-0002Vn-6Y for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 06:06: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 GAA23520 for ; Fri, 11 Jul 2003 06:06:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aun6-0004Im-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 06:06:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aun5-0004Ij-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 06:06:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aumw-0002QZ-Ce; Fri, 11 Jul 2003 06:06:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aumu-0002Pz-MO for manet@optimus.ietf.org; Fri, 11 Jul 2003 06: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 GAA23511 for ; Fri, 11 Jul 2003 06:05:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aumr-0004IS-00 for manet@ietf.org; Fri, 11 Jul 2003 06:05:57 -0400 Received: from mailhost.iitb.ac.in ([203.197.74.142]) by ietf-mx with smtp (Exim 4.12) id 19aump-0004IP-00 for manet@ietf.org; Fri, 11 Jul 2003 06:05:56 -0400 Received: (qmail 23164 invoked from network); 11 Jul 2003 10:05:48 -0000 Received: from newsmtp.iitb.ac.in (144.16.108.201) by mailhost.iitb.ac.in with SMTP; 11 Jul 2003 10:05:48 -0000 Received: (qmail 11286 invoked by uid 512); 11 Jul 2003 10:05:48 -0000 Received: from leena@it.iitb.ac.in by newsmtp by uid 509 with qmail-scanner-1.15 (clamscan: 0.54. Clear:. Processed in 0.231707 secs); 11 Jul 2003 10:05:48 -0000 Received: from gaia.it.iitb.ac.in (HELO gaia) ([10.129.100.81]) (envelope-sender ) by smtp.iitb.ac.in (qmail-ldap-1.03) with SMTP for ; 11 Jul 2003 10:05:48 -0000 From: "Leena Chandran-Wadia" To: Cc: Date: Fri, 11 Jul 2003 15:41:12 +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 V6.00.2600.0000 Importance: Normal Content-Transfer-Encoding: 7bit Subject: [manet] Re: Carrier sense threshold/range control Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Dear Dr. Perkins, On Wed, 9 Jul 2003, Dmitri D. Perkins wrote: >Question...Referencing the previous illustration (A<-----B C------>D), >is there any work showing the benefit versus overhead or complexity for >the following scenario: > >1. allow node C to transmit to D while B is transmitting a data frame to A >2. force C to keep silent just in time for B to receive the ACK from A. > >This MAY result in better channel utilization but SHOULD require a more >complex access/NAV scheme. Any thoughts... We have tried 1. and 2. on 802.11 ad hoc networks. As mentioned by Nitin Vaidya, packet sizes become important if one wants to allow parallel transmission. C can indeed transmit to D while B is sending data to A, provided it has a packet small enough so that it can finish transmission and be silent in time for B to receive the ACK from A. Also, the transmission from C to D must not use RTS/CTS. C can even receive an ACK from D provided the end of transmission of its data is aligned with that of B. We have implemented this in GloMoSim - turns out to be not too complex. The details are available in a paper just accepted to ICCCN http://www.it.iitb.ac.in/~sri/papers/expnode-ic3n03.pdf The camera ready version of this paper is due on August 1st. If you and others on the list can offer comments/criticisms, we would be glad to try and incorporate them - at least the ones we can handle in the next 2 weeks...We can also make the implementation available if somone wants to experiment with it. There is also another effort in this direction. The authors have a much more complex algorithm, called MACA-P, which involves negotiations between pairs of transmitting nodes. There is an IBM research report (RC 22528) somewhere in cyberspace. The paper was presented at IEEE PerCom 2003. Thanks, Leena ------------------------ Dr. Leena Chandran-Wadia Infosys Research Fellow Kanwal Rekhi School of Information Technology IIT-Bombay, Powai Mumbai - 400 076 mailto:leena@it.iitb.ac.in -------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 11 07:54:45 2003 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 HAA26103 for ; Fri, 11 Jul 2003 07:54: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 19awTg-0002vX-DU for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 07:54:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BBsG2Q011245 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 07:54:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19awTg-0002vI-92 for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 07:54: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 HAA26079 for ; Fri, 11 Jul 2003 07:54:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19awTf-0004zt-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 07:54:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19awTe-0004zq-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 07:54:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19awTS-0002on-G9; Fri, 11 Jul 2003 07: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 19awSx-0002oQ-1m for manet@optimus.ietf.org; Fri, 11 Jul 2003 07:53: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 HAA26006 for ; Fri, 11 Jul 2003 07:53:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19awSw-0004zi-00 for manet@ietf.org; Fri, 11 Jul 2003 07:53:30 -0400 Received: from mailhub02-skge0.unibe.ch ([130.92.9.53] helo=mailhub02.unibe.ch) by ietf-mx with esmtp (Exim 4.12) id 19awSv-0004zV-00 for manet@ietf.org; Fri, 11 Jul 2003 07:53:29 -0400 Received: from localhost (localhost [127.0.0.1]) by mailhub02.unibe.ch (Postfix) with ESMTP id AFE48764C7 for ; Fri, 11 Jul 2003 13:52:58 +0200 (MEST) Received: from mailhub02.unibe.ch ([127.0.0.1]) by localhost (mailhub02 [127.0.0.1:10024]) (amavisd-new) with LMTP id 29300-01-6 for ; Fri, 11 Jul 2003 13:52:58 +0200 (MEST) Received: from asterix.unibe.ch (asterix.unibe.ch [130.92.64.4]) by mailhub02.unibe.ch (Postfix) with ESMTP id C127E764C9 for ; Fri, 11 Jul 2003 13:52:57 +0200 (MEST) Received: from sagnix.unibe.ch (sagnix [130.92.64.6]) by asterix.unibe.ch (8.11.6+Sun/8.11.6) with ESMTP id h6BBqvK08744 for ; Fri, 11 Jul 2003 13:52:57 +0200 (MET DST) Received: from sagnix (sagnix [130.92.64.6]) by sagnix.unibe.ch (8.11.6+Sun/8.11.6) with SMTP id h6BBqvl19826 for ; Fri, 11 Jul 2003 13:52:57 +0200 (MEST) Message-Id: <200307111152.h6BBqvl19826@sagnix.unibe.ch> Date: Fri, 11 Jul 2003 13:52:57 +0200 (MEST) From: Markus Waelchli Reply-To: Markus Waelchli To: manet@ietf.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: oSWA4qX20SPHSul8C0z6vw== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.6_06 SunOS 5.8 sun4u sparc X-Virus-checked: by University of Berne Subject: [manet] GPSR or GFG 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: , Hi dear users I am looking for an Implementation of GPSR or GFG for GlomoSim or Qualnet. It could also be another position-based routing algorithm, if someone has already written one. I use GlomoSim version 2.02 Thanks markus Markus Waelchli Institute of Computer Science and Applied Mathematics Univeristy of Bern waelchli@iam.unibe.ch http://www.iam.unibe.ch/~waelchli _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 11 10:24:45 2003 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 KAA01356 for ; Fri, 11 Jul 2003 10:24: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 19ayot-0006DZ-7L for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 10:24:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BEOJjt023895 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 10:24:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ayos-0006DK-Iv for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 10:24: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 KAA01333 for ; Fri, 11 Jul 2003 10:24:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ayoq-0005yo-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 10:24:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ayop-0005yl-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 10:24:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ayob-0005zj-Cb; Fri, 11 Jul 2003 10:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ayoT-0005zS-M9 for manet@optimus.ietf.org; Fri, 11 Jul 2003 10:23:53 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01329 for ; Fri, 11 Jul 2003 10:23:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ayoR-0005yc-00 for manet@ietf.org; Fri, 11 Jul 2003 10:23:51 -0400 Received: from web20106.mail.yahoo.com ([216.136.226.43]) by ietf-mx with smtp (Exim 4.12) id 19ayoQ-0005yZ-00 for manet@ietf.org; Fri, 11 Jul 2003 10:23:50 -0400 Message-ID: <20030711142349.85439.qmail@web20106.mail.yahoo.com> Received: from [146.186.29.49] by web20106.mail.yahoo.com via HTTP; Fri, 11 Jul 2003 07:23:49 PDT Date: Fri, 11 Jul 2003 07:23:49 -0700 (PDT) From: Siddharth Ray To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] Glomosim Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Markus, Well, I wanted to clarify something about glomosim. I have heard that glomosim is not supported and hence, there are a lot of bugs in it. The papers which I have gone through in ACM etc, none of them have used glomosim for simulation. I have a friend in UCBerkely who says that glomosim can be used when people are just starting to learn simulation but cannot be really used for some serious simulations. Can anybody clarify this for me. Thanks, Siddharth ===== "Keep me away from the wisdom which does not cry, the philosophy which does not laugh and the greatness which does not bow before children." - Kahlil Gibran MS, Department of Computer Sc. & Engg, Pond Lab, State College, PA - 16802, USA. http://www.cse.psu.edu/~sray __________________________________ 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 Fri Jul 11 12:37:47 2003 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 MAA05272 for ; Fri, 11 Jul 2003 12:37: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 19b0tX-0000OH-FP for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 12:37:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BGbFvG001502 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 12:37:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b0tV-0000Nf-Tb for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 12:37: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 MAA05263 for ; Fri, 11 Jul 2003 12:37:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b0tU-0006zv-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 12:37:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19b0tT-0006zs-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 12:37:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b0tK-0000JE-3r; Fri, 11 Jul 2003 12:37:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b0t2-0000Hw-MD for manet@optimus.ietf.org; Fri, 11 Jul 2003 12:36: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 MAA05257 for ; Fri, 11 Jul 2003 12:36:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b0t1-0006zj-00 for manet@ietf.org; Fri, 11 Jul 2003 12:36:43 -0400 Received: from [130.15.22.4] (helo=wasp.ECE.QUEENSU.CA) by ietf-mx with esmtp (Exim 4.12) id 19b0t0-0006zg-00 for manet@ietf.org; Fri, 11 Jul 2003 12:36:42 -0400 Received: from acer7k2wrwolsy ([24.226.47.100]) by wasp.ECE.QUEENSU.CA with Microsoft SMTPSVC(5.0.2195.5329); Fri, 11 Jul 2003 12:37:14 -0400 From: "Chi-Hsiang Yeh" To: "'#LI ZHIFEI#'" Cc: Subject: RE: [manet] Carrier sense threshold/range control Date: Fri, 11 Jul 2003 12:36:16 -0400 Message-ID: <002a01c347ca$90911920$642fe218@acer7k2wrwolsy> 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: <3D565922795545468AE3E3DA2881BEA90186D847@mail01.student.main.ntu.edu.sg> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 11 Jul 2003 16:37:14.0750 (UTC) FILETIME=[AF5BC9E0:01C347CA] 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 > -----Original Message----- > From: #LI ZHIFEI# [mailto:zhifeili@pmail.ntu.edu.sg] > Sent: Friday, July 11, 2003 4:45 AM > To: Chi-Hsiang Yeh > Cc: manet@ietf.org > Subject: RE: [manet] Carrier sense threshold/range control > > > >Also, when SR >= IR + TR, topology 2 (in your previous e-mail) and > >other topologies without obstacles would not suffer from the hidden > >terminal problem (without considering collisions of control messages > >and propagation characteristics/delays etc. of course). > > That is true but at the cost of capacity. Moreover, if SR >= > IR + TR, it seems that the RTS/CTS do not have much meaning > any more. You are right, for free space. For indoor environments, strategies using large SR alone do not work well due to obstacles. If anyone has or know experiements on this issue (indoor + large SR), I'll appreciate it if you could give me a pointer. > However, as pointed out by some work, whether the > SR can be set to greater than (IR + TR) depends upon the > antenna's sensitivity. You are right. And it also depends on path loss etc. There is always a limit on SR, and in reality it may not be easy to know these parameter values directly or to make SR=IR+TR. Chihsiang > > > > -----Original Message----- > From: Chi-Hsiang Yeh [mailto:chi-hsiang.yeh@ece.queensu.ca] > Sent: divendres, 11 / juliol / 2003 12:09 > To: #LI ZHIFEI#; manet@ietf.org > Cc: 'Vikram Dham' > Subject: RE: [manet] Carrier sense threshold/range control > > > Hi, Zhifei, > > > > Though we may not be elminating all the hidden terminals > but we may > > >decrease > > >the probability of occurence of hidden terminals by > > extending sensing range to > > >2SR. ???? >2TR > > > > The objective of elminating the hidden terminal problem is to > > reduce collisions and thus > > increase the channel utilization. However, if you increase > > the sensing range, the interfering range is > > also increased and thus the spatial reuse is greatly reduced. > > This is not true. Besides SR and TR, there is another > parameter "interference range (IR)", which is not necessarily > equal to SR. By lowering the threshold for sensing, > increasing SR does not affect IR. Instead, IR is increased > when the associated transmission power level is increased. > > Also, when SR >= IR + TR, topology 2 (in your previous > e-mail) and other topologies without obstacles would not > suffer from the hidden terminal problem (without considering > collisions of control messages and propagation > characteristics/delays etc. of course). > > Chihsiang > > > Of course, if capture is enabled, it may be a different > > story. However, with capture, fairness becomse worse (which > > is my main concern). > > Moreover, as I have mentioned, when the sensing range (SR) is > > made greater than transmission range (TR), > > how long a node should defer its transmission when it detects > > a SR frame is a very difficult job as > > the node cannot interpret the conent of a SR frame. > > > > > > > > Li zhifei > > > > > > -----Original Message----- > > From: Vikram Dham [mailto:vdham@vt.edu] > > Sent: dijous, 10 / juliol / 2003 23:02 > > To: #LI ZHIFEI#; manet > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > Hello Zhifei Li, > > > > Though topology 2 also may have scenarios with hidden > > terminal, but in a > > wireless network, > > > > probability (distance between nodes > 2SR) =< probability > > (distance between > > nodes > SR ). > > > > Though we may not be elminating all the hidden terminals but > > we may decrease > > the probability of occurence of hidden terminals by extending > > sensing range to > > 2SR. > > > > Regards > > > > Vikram Dham > > >===== Original Message From #LI ZHIFEI# > > >===== Hi, Ram > > > > > >In my view, even the Carrier Sensing Range (SR) is two times of the > > Transmission Range (TR ), the hidden-termianl problem is > still there. > > >This can be illustrated as the following two topologies: > > > > > >Topology 1: > Topology 2: > > > > > >A -> B <- C A -> B > C<- D > > > > > >(note that the distance between two neighboring nodes are > > equal to the > > transmission range, i.e., one hop) > > > > > >The first topology is tipycally used to illustrate the well-known > > hidden-terminal problem, but with an implicit assumption, > i.e., SR=TR. > > >If SR=2*TR, the hidden-terminal problem seems not exist any more in > > >this > > topology as the nodes A and C can sense the transmission of > > each other. > > > > > >However, even SR=2*TR, the problem will arise in the > second topology. > > Specically, when node A starts to transmit to node B, since node D > > >is out of the SR of node A, it cannot detect the transmission. > > >Therefore, > > node D may also start to transmit to node C, resulting in > > collision (or > > capture). > > >In such case, we can say that nodes A and D are hidden > > terminal of each > > other. We do find the similarities of the performance between > > the two cases: > > >topology 1 when SR=TR; and topology 2 when SR=2*TR > > > > > > > > >When SR>TR, another problem is that how a node should defer its > > >transmission > > when it detects a SR frame. This is not an easy job since the > > node cannot > > >interpret the content of the SR frame. In the IEEE 802.11, > > whenever a > > >node > > detects a SR frame, it will defer by a fixed EFIS value. > > However, our results > > show > > >this fixed value will cause many problems, e.g., unfairness. > > Moreover, > > >the > > capture ability will also greatly affect the performace when SR>TR. > > >For a detailed descrition of these issues, please refer to > > the attached > > references: > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > > >"Improving Fairness in IEEE 802.11 based MANETs using > > Enhanced Carrier > > Sensing", submitted to conference, April 2003 > > >http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf > > > > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > > >"Study of IEEE 802.11 Fairness and its Interaction with Routing > > >Mechanism", > > accepted by IEEE MWCN 2003 Singapore, May 2003 > > >http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf > > > > > > > > >Though the above papers mainly focus on the the fairness issue when > > >SR>TR, > > the descirtion should also apply to the analysis of the > > channel utilization. > > >I hope that they will relate to your work and help you. > > > > > > > > >Best regards > > >Li ZhiFei > > >PhD candidate, > > >Center For Multimedia And Network Technology > > >School Of Computer Engineering > > >Nanyang Technological University > > >N4-b2c-08, Nanyang Avenue > > >Singapore 639798 > > >tel:(65)67906579 > > >website: > > > > > > > > >-----Original Message----- > > >From: Ram Ramanathan [mailto:ramanath@bbn.com] > > >Sent: dijous, 10 / juliol / 2003 00:09 > > >To: manet@ietf.org > > >Cc: ramanath@bbn.com > > >Subject: [manet] Carrier sense threshold/range control > > > > > > > > > > > >I am looking for pointers to research on the control of > > carrier sensing > > >range in lieu of using RTS/CTS to address the hidden node problem? > > > > > >To elaborate, the threshold for when carrier is declared to > > be "sensed" > > >can be adjusted in many radios. Using this facility, one > > could possibly > > >make the "carrier sense range" approximately twice the > > "communication > > >range" (successful packet reception), and detect hidden nodes. > > > > > >This is by no means a new idea, and I vaguely recally some > > mention of > > >it on this list. Of course, there are a number of factors > > that make the > > >problem far more complex than the simple statement above > > indicates, and > > >it is not immediately clear whether it will be effective at all. > > > > > >I am looking for papers, tech reports, or any publicly available > > >material > > >(non-proprietary) on this issue. > > > > > >Many thanks in advance, > > > > > >-Ram. > > > > > >_______________________________________________ > > >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 > > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 11 13:10:47 2003 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 NAA06349 for ; Fri, 11 Jul 2003 13:10: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 19b1PZ-00035u-TE for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 13:10:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BHALWl011889 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 13:10:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b1PZ-00035g-Pc for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 13:10: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 NAA06340 for ; Fri, 11 Jul 2003 13:10:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b1PX-0007Iz-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 13:10:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19b1PX-0007Iv-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 13: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 19b1PG-0002px-M0; Fri, 11 Jul 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 19b1OW-0002ol-TS for manet@optimus.ietf.org; Fri, 11 Jul 2003 13: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 NAA06328 for ; Fri, 11 Jul 2003 13:09:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b1OU-0007IN-00 for manet@ietf.org; Fri, 11 Jul 2003 13:09:14 -0400 Received: from tiquini.ece.arizona.edu ([128.196.29.23]) by ietf-mx with esmtp (Exim 4.12) id 19b1OU-0007ID-00 for manet@ietf.org; Fri, 11 Jul 2003 13:09:14 -0400 Received: from tiquini (tiquini [128.196.29.23]) by tiquini.ece.arizona.edu (8.12.9/8.12.9) with ESMTP id h6BGrqI2002594; Fri, 11 Jul 2003 09:53:53 -0700 (MST) Received: from DHCP-140.ece.arizona.edu ([150.135.222.140]) by tiquini.ece.arizona.edu (MailMonitor for SMTP v1.2.2 ) ; Fri, 11 Jul 2003 09:53:32 -0700 (MST) Message-ID: <00d501c347cd$27f48570$8cde8796@arizonaalaa> Reply-To: "Alaa Muqattash" From: "Alaa Muqattash" To: "Chi-Hsiang Yeh" , "'#LI ZHIFEI#'" Cc: References: <002a01c347ca$90911920$642fe218@acer7k2wrwolsy> Subject: Re: [manet] Carrier sense threshold/range control Date: Fri, 11 Jul 2003 09:54:55 -0700 Organization: The University of Arizona MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Could you please explain what do you mean by the "interference range"? I don't think that this range is fixed. Instead, it depends on: 1- The transmission power 2- The channel gain between the transmitter & receiver 3- The minimum SNR threshold required for reliable communication For example, fixing all other parameters, if the required SNR is increased, then your interference range is increased. Any thoughts? regards, Alaa ----- Original Message ----- From: "Chi-Hsiang Yeh" To: "'#LI ZHIFEI#'" Cc: Sent: Friday, July 11, 2003 9:36 AM Subject: RE: [manet] Carrier sense threshold/range control > > -----Original Message----- > > From: #LI ZHIFEI# [mailto:zhifeili@pmail.ntu.edu.sg] > > Sent: Friday, July 11, 2003 4:45 AM > > To: Chi-Hsiang Yeh > > Cc: manet@ietf.org > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > >Also, when SR >= IR + TR, topology 2 (in your previous e-mail) and > > >other topologies without obstacles would not suffer from the hidden > > >terminal problem (without considering collisions of control messages > > >and propagation characteristics/delays etc. of course). > > > > That is true but at the cost of capacity. Moreover, if SR >= > > IR + TR, it seems that the RTS/CTS do not have much meaning > > any more. > > You are right, for free space. For indoor environments, strategies using > large SR alone do not work well due to obstacles. If anyone has or know > experiements on this issue (indoor + large SR), I'll appreciate it if > you could give me a pointer. > > > However, as pointed out by some work, whether the > > SR can be set to greater than (IR + TR) depends upon the > > antenna's sensitivity. > > You are right. And it also depends on path loss etc. There is always a > limit on SR, and in reality it may not be easy to know these parameter > values directly or to make SR=IR+TR. > > Chihsiang > > > > > > > > > > > -----Original Message----- > > From: Chi-Hsiang Yeh [mailto:chi-hsiang.yeh@ece.queensu.ca] > > Sent: divendres, 11 / juliol / 2003 12:09 > > To: #LI ZHIFEI#; manet@ietf.org > > Cc: 'Vikram Dham' > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > Hi, Zhifei, > > > > > > Though we may not be elminating all the hidden terminals > > but we may > > > >decrease > > > >the probability of occurence of hidden terminals by > > > extending sensing range to > > > >2SR. ???? >2TR > > > > > > The objective of elminating the hidden terminal problem is to > > > reduce collisions and thus > > > increase the channel utilization. However, if you increase > > > the sensing range, the interfering range is > > > also increased and thus the spatial reuse is greatly reduced. > > > > This is not true. Besides SR and TR, there is another > > parameter "interference range (IR)", which is not necessarily > > equal to SR. By lowering the threshold for sensing, > > increasing SR does not affect IR. Instead, IR is increased > > when the associated transmission power level is increased. > > > > Also, when SR >= IR + TR, topology 2 (in your previous > > e-mail) and other topologies without obstacles would not > > suffer from the hidden terminal problem (without considering > > collisions of control messages and propagation > > characteristics/delays etc. of course). > > > > Chihsiang > > > > > Of course, if capture is enabled, it may be a different > > > story. However, with capture, fairness becomse worse (which > > > is my main concern). > > > Moreover, as I have mentioned, when the sensing range (SR) is > > > made greater than transmission range (TR), > > > how long a node should defer its transmission when it detects > > > a SR frame is a very difficult job as > > > the node cannot interpret the conent of a SR frame. > > > > > > > > > > > > Li zhifei > > > > > > > > > -----Original Message----- > > > From: Vikram Dham [mailto:vdham@vt.edu] > > > Sent: dijous, 10 / juliol / 2003 23:02 > > > To: #LI ZHIFEI#; manet > > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > > > > Hello Zhifei Li, > > > > > > Though topology 2 also may have scenarios with hidden > > > terminal, but in a > > > wireless network, > > > > > > probability (distance between nodes > 2SR) =< probability > > > (distance between > > > nodes > SR ). > > > > > > Though we may not be elminating all the hidden terminals but > > > we may decrease > > > the probability of occurence of hidden terminals by extending > > > sensing range to > > > 2SR. > > > > > > Regards > > > > > > Vikram Dham > > > >===== Original Message From #LI ZHIFEI# > > > >===== Hi, Ram > > > > > > > >In my view, even the Carrier Sensing Range (SR) is two times of the > > > Transmission Range (TR ), the hidden-termianl problem is > > still there. > > > >This can be illustrated as the following two topologies: > > > > > > > >Topology 1: > > Topology 2: > > > > > > > >A -> B <- C A -> B > > C<- D > > > > > > > >(note that the distance between two neighboring nodes are > > > equal to the > > > transmission range, i.e., one hop) > > > > > > > >The first topology is tipycally used to illustrate the well-known > > > hidden-terminal problem, but with an implicit assumption, > > i.e., SR=TR. > > > >If SR=2*TR, the hidden-terminal problem seems not exist any more in > > > >this > > > topology as the nodes A and C can sense the transmission of > > > each other. > > > > > > > >However, even SR=2*TR, the problem will arise in the > > second topology. > > > Specically, when node A starts to transmit to node B, since node D > > > >is out of the SR of node A, it cannot detect the transmission. > > > >Therefore, > > > node D may also start to transmit to node C, resulting in > > > collision (or > > > capture). > > > >In such case, we can say that nodes A and D are hidden > > > terminal of each > > > other. We do find the similarities of the performance between > > > the two cases: > > > >topology 1 when SR=TR; and topology 2 when SR=2*TR > > > > > > > > > > > >When SR>TR, another problem is that how a node should defer its > > > >transmission > > > when it detects a SR frame. This is not an easy job since the > > > node cannot > > > >interpret the content of the SR frame. In the IEEE 802.11, > > > whenever a > > > >node > > > detects a SR frame, it will defer by a fixed EFIS value. > > > However, our results > > > show > > > >this fixed value will cause many problems, e.g., unfairness. > > > Moreover, > > > >the > > > capture ability will also greatly affect the performace when SR>TR. > > > >For a detailed descrition of these issues, please refer to > > > the attached > > > references: > > > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > > > >"Improving Fairness in IEEE 802.11 based MANETs using > > > Enhanced Carrier > > > Sensing", submitted to conference, April 2003 > > > >http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf > > > > > > > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > > > >"Study of IEEE 802.11 Fairness and its Interaction with Routing > > > >Mechanism", > > > accepted by IEEE MWCN 2003 Singapore, May 2003 > > > >http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf > > > > > > > > > > > >Though the above papers mainly focus on the the fairness issue when > > > >SR>TR, > > > the descirtion should also apply to the analysis of the > > > channel utilization. > > > >I hope that they will relate to your work and help you. > > > > > > > > > > > >Best regards > > > >Li ZhiFei > > > >PhD candidate, > > > >Center For Multimedia And Network Technology > > > >School Of Computer Engineering > > > >Nanyang Technological University > > > >N4-b2c-08, Nanyang Avenue > > > >Singapore 639798 > > > >tel:(65)67906579 > > > >website: > > > > > > > > > > > >-----Original Message----- > > > >From: Ram Ramanathan [mailto:ramanath@bbn.com] > > > >Sent: dijous, 10 / juliol / 2003 00:09 > > > >To: manet@ietf.org > > > >Cc: ramanath@bbn.com > > > >Subject: [manet] Carrier sense threshold/range control > > > > > > > > > > > > > > > >I am looking for pointers to research on the control of > > > carrier sensing > > > >range in lieu of using RTS/CTS to address the hidden node problem? > > > > > > > >To elaborate, the threshold for when carrier is declared to > > > be "sensed" > > > >can be adjusted in many radios. Using this facility, one > > > could possibly > > > >make the "carrier sense range" approximately twice the > > > "communication > > > >range" (successful packet reception), and detect hidden nodes. > > > > > > > >This is by no means a new idea, and I vaguely recally some > > > mention of > > > >it on this list. Of course, there are a number of factors > > > that make the > > > >problem far more complex than the simple statement above > > > indicates, and > > > >it is not immediately clear whether it will be effective at all. > > > > > > > >I am looking for papers, tech reports, or any publicly available > > > >material > > > >(non-proprietary) on this issue. > > > > > > > >Many thanks in advance, > > > > > > > >-Ram. > > > > > > > >_______________________________________________ > > > >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 > > > > > > > > > > > > > > > _______________________________________________ > 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 Jul 11 13:49:43 2003 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 NAA07945 for ; Fri, 11 Jul 2003 13:49:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b21E-0006U9-8w for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 13:49:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BHnG9q024895 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 13:49:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b21E-0006Sv-57 for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 13:49: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 NAA07915 for ; Fri, 11 Jul 2003 13:49:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b21B-00000h-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 13:49:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19b21B-00000e-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 13:49:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b20z-0006Rg-FG; Fri, 11 Jul 2003 13:49:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b20C-0006Oy-M6 for manet@optimus.ietf.org; Fri, 11 Jul 2003 13:48: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 NAA07901 for ; Fri, 11 Jul 2003 13:48:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b20A-0007nr-00 for manet@ietf.org; Fri, 11 Jul 2003 13:48:10 -0400 Received: from [131.227.76.5] (helo=prue.eim.surrey.ac.uk ident=exim) by ietf-mx with esmtp (Exim 4.12) id 19b209-0007no-00 for manet@ietf.org; Fri, 11 Jul 2003 13:48:09 -0400 Received: from romeo.ee.surrey.ac.uk ([131.227.76.30] helo=eim.surrey.ac.uk ident=www) by prue.eim.surrey.ac.uk with smtp (Exim 3.33 #4) id 19b1zw-0006Td-00 for manet@ietf.org; Fri, 11 Jul 2003 18:47:56 +0100 Received: from open-net.ee.surrey.ac.uk ([131.227.76.238]) (SquirrelMail authenticated user eem1tk) by secure.eps.surrey.ac.uk with HTTP; Fri, 11 Jul 2003 18:47:56 +0100 (BST) Message-ID: <3644.131.227.76.238.1057945676.squirrel@secure.eps.surrey.ac.uk> Date: Fri, 11 Jul 2003 18:47:56 +0100 (BST) From: "Teng Kang" To: X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.9) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=-105.4 required=5.5 tests=BAYES_01,USER_IN_WHITELIST version=2.55 X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) X-Scanner: exiscan *19b1zw-0006Td-00*BusmwY2XEKA* (SECM, UniS) Content-Transfer-Encoding: 8bit Subject: [manet] E-DCF and HCF Implementations in Glomosim Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Dear all users: I am a MSc student and doing my master project about QOS support in ad hoc. Since the time left for me to achieve the work is quite short, I want to find some helps from you. I want to know whether you have the code of E-DCF and HCF Implementations in Glomosim. I need such kinds of references to do my project. I hope my mail will not cost your too much time. Your reply is highly appreciated! Best regards kangteng _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 11 13:50:42 2003 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 NAA07987 for ; Fri, 11 Jul 2003 13:50:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b22A-0006mT-Oz for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 13:50:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BHoE4M026063 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 13:50:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b22A-0006mH-F8 for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 13:50: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 NAA07973 for ; Fri, 11 Jul 2003 13:50:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b228-00001o-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 13:50:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19b227-00001l-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 13:50:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b21y-0006fp-Fi; Fri, 11 Jul 2003 13:50:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b21m-0006bx-E9 for manet@optimus.ietf.org; Fri, 11 Jul 2003 13: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 NAA07943 for ; Fri, 11 Jul 2003 13:49:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b21e-000019-00 for manet@ietf.org; Fri, 11 Jul 2003 13:49:42 -0400 Received: from nestor.nmsu.edu ([128.123.34.146] helo=mail.nmsu.edu) by ietf-mx with esmtp (Exim 4.12) id 19b21c-000014-00 for manet@ietf.org; Fri, 11 Jul 2003 13:49:40 -0400 Received: from PCMullen2 (pc-mullen-2.NMSU.Edu [128.123.245.103]) by mail.nmsu.edu (Postfix) with ESMTP id E24382026; Fri, 11 Jul 2003 11:49:37 -0600 (MDT) From: "John Mullen" To: "'Alaa Muqattash'" Cc: Subject: RE: [manet] Carrier sense threshold/range control Date: Fri, 11 Jul 2003 11:49:37 -0600 Message-ID: <000201c347d4$cc123510$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 In-Reply-To: <00d501c347cd$27f48570$8cde8796@arizonaalaa> Importance: Normal 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 Alaa, As I use it, the IR is the distance at which a transmitted signal from a terminal interferes with that of another at the receiver. You are correct in that the distance is not fixed. If A is sending to B in the presence of a signal from C, whether or not B can successfully decode A's transmission depends on the signal strength from A, that from C, and the noise level at B. A simple approximation is to treat the transmission from C as noise and to look at the ratio of SN(A) / [SN(C)+N]. However, this is inexact. Because C's signal is actually a valid transmission, it would be more difficult for the receiver to ignore. (I'm assuming C is using the same channel, waveform, etc. as A and B). To illustrate, if you had a signal from C that was just marginally rejectable by B, reducing A's signal strength, by any means, e.g. antenna gain, distance, xmitter power, etc., would cause that signal to cause a data collision at B. On the other hand, if the signal from A increases, then that of C would become less and less significant. I think most people consider the IR to that which would cause interference at an extreme A-B range, but this is misleading in that when A&B are closer, the interference source can also be closer without causing difficulty. John Mullen -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Alaa Muqattash Sent: Friday, July 11, 2003 9:55 AM To: Chi-Hsiang Yeh; '#LI ZHIFEI#' Cc: manet@ietf.org Subject: Re: [manet] Carrier sense threshold/range control Could you please explain what do you mean by the "interference range"? I don't think that this range is fixed. Instead, it depends on: 1- The transmission power 2- The channel gain between the transmitter & receiver 3- The minimum SNR threshold required for reliable communication For example, fixing all other parameters, if the required SNR is increased, then your interference range is increased. Any thoughts? regards, Alaa ----- Original Message ----- From: "Chi-Hsiang Yeh" To: "'#LI ZHIFEI#'" Cc: Sent: Friday, July 11, 2003 9:36 AM Subject: RE: [manet] Carrier sense threshold/range control > > -----Original Message----- > > From: #LI ZHIFEI# [mailto:zhifeili@pmail.ntu.edu.sg] > > Sent: Friday, July 11, 2003 4:45 AM > > To: Chi-Hsiang Yeh > > Cc: manet@ietf.org > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > >Also, when SR >= IR + TR, topology 2 (in your previous e-mail) and > > >other topologies without obstacles would not suffer from the hidden > > >terminal problem (without considering collisions of control > > >messages and propagation characteristics/delays etc. of course). > > > > That is true but at the cost of capacity. Moreover, if SR >= IR + > > TR, it seems that the RTS/CTS do not have much meaning any more. > > You are right, for free space. For indoor environments, strategies > using large SR alone do not work well due to obstacles. If anyone has > or know experiements on this issue (indoor + large SR), I'll > appreciate it if you could give me a pointer. > > > However, as pointed out by some work, whether the > > SR can be set to greater than (IR + TR) depends upon the antenna's > > sensitivity. > > You are right. And it also depends on path loss etc. There is always a > limit on SR, and in reality it may not be easy to know these parameter > values directly or to make SR=IR+TR. > > Chihsiang > > > > > > > > > > > -----Original Message----- > > From: Chi-Hsiang Yeh [mailto:chi-hsiang.yeh@ece.queensu.ca] > > Sent: divendres, 11 / juliol / 2003 12:09 > > To: #LI ZHIFEI#; manet@ietf.org > > Cc: 'Vikram Dham' > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > Hi, Zhifei, > > > > > > Though we may not be elminating all the hidden terminals > > but we may > > > >decrease > > > >the probability of occurence of hidden terminals by > > > extending sensing range to > > > >2SR. ???? >2TR > > > > > > The objective of elminating the hidden terminal problem is to > > > reduce collisions and thus increase the channel utilization. > > > However, if you increase the sensing range, the interfering range > > > is also increased and thus the spatial reuse is greatly reduced. > > > > This is not true. Besides SR and TR, there is another parameter > > "interference range (IR)", which is not necessarily equal to SR. By > > lowering the threshold for sensing, increasing SR does not affect > > IR. Instead, IR is increased when the associated transmission power > > level is increased. > > > > Also, when SR >= IR + TR, topology 2 (in your previous > > e-mail) and other topologies without obstacles would not suffer from > > the hidden terminal problem (without considering collisions of > > control messages and propagation characteristics/delays etc. of > > course). > > > > Chihsiang > > > > > Of course, if capture is enabled, it may be a different story. > > > However, with capture, fairness becomse worse (which is my main > > > concern). Moreover, as I have mentioned, when the sensing range > > > (SR) is made greater than transmission range (TR), > > > how long a node should defer its transmission when it detects > > > a SR frame is a very difficult job as > > > the node cannot interpret the conent of a SR frame. > > > > > > > > > > > > Li zhifei > > > > > > > > > -----Original Message----- > > > From: Vikram Dham [mailto:vdham@vt.edu] > > > Sent: dijous, 10 / juliol / 2003 23:02 > > > To: #LI ZHIFEI#; manet > > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > > > > Hello Zhifei Li, > > > > > > Though topology 2 also may have scenarios with hidden terminal, > > > but in a wireless network, > > > > > > probability (distance between nodes > 2SR) =< probability > > > (distance between nodes > SR ). > > > > > > Though we may not be elminating all the hidden terminals but we > > > may decrease the probability of occurence of hidden terminals by > > > extending sensing range to > > > 2SR. > > > > > > Regards > > > > > > Vikram Dham > > > >===== Original Message From #LI ZHIFEI# > > > > ===== Hi, Ram > > > > > > > >In my view, even the Carrier Sensing Range (SR) is two times of > > > >the > > > Transmission Range (TR ), the hidden-termianl problem is > > still there. > > > >This can be illustrated as the following two topologies: > > > > > > > >Topology 1: > > Topology 2: > > > > > > > >A -> B <- C A -> B > > C<- D > > > > > > > >(note that the distance between two neighboring nodes are > > > equal to the > > > transmission range, i.e., one hop) > > > > > > > >The first topology is tipycally used to illustrate the well-known > > > hidden-terminal problem, but with an implicit assumption, > > i.e., SR=TR. > > > >If SR=2*TR, the hidden-terminal problem seems not exist any more > > > >in this > > > topology as the nodes A and C can sense the transmission of each > > > other. > > > > > > > >However, even SR=2*TR, the problem will arise in the > > second topology. > > > Specically, when node A starts to transmit to node B, since node D > > > >is out of the SR of node A, it cannot detect the transmission. > > > >Therefore, > > > node D may also start to transmit to node C, resulting in > > > collision (or capture). > > > >In such case, we can say that nodes A and D are hidden > > > terminal of each > > > other. We do find the similarities of the performance between the > > > two cases: > > > >topology 1 when SR=TR; and topology 2 when SR=2*TR > > > > > > > > > > > >When SR>TR, another problem is that how a node should defer its > > > >transmission > > > when it detects a SR frame. This is not an easy job since the node > > > cannot > > > >interpret the content of the SR frame. In the IEEE 802.11, > > > whenever a > > > >node > > > detects a SR frame, it will defer by a fixed EFIS value. However, > > > our results show > > > >this fixed value will cause many problems, e.g., unfairness. > > > Moreover, > > > >the > > > capture ability will also greatly affect the performace when > > > SR>TR. > > > >For a detailed descrition of these issues, please refer to > > > the attached > > > references: > > > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > > > >"Improving Fairness in IEEE 802.11 based MANETs using > > > Enhanced Carrier > > > Sensing", submitted to conference, April 2003 > > > >http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf > > > > > > > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > > > >"Study of IEEE 802.11 Fairness and its Interaction with Routing > > > >Mechanism", > > > accepted by IEEE MWCN 2003 Singapore, May 2003 > > > >http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf > > > > > > > > > > > >Though the above papers mainly focus on the the fairness issue > > > >when > > > >SR>TR, > > > the descirtion should also apply to the analysis of the channel > > > utilization. > > > >I hope that they will relate to your work and help you. > > > > > > > > > > > >Best regards > > > >Li ZhiFei > > > >PhD candidate, > > > >Center For Multimedia And Network Technology > > > >School Of Computer Engineering > > > >Nanyang Technological University > > > >N4-b2c-08, Nanyang Avenue > > > >Singapore 639798 > > > >tel:(65)67906579 > > > >website: > > > > > > > > > > > >-----Original Message----- > > > >From: Ram Ramanathan [mailto:ramanath@bbn.com] > > > >Sent: dijous, 10 / juliol / 2003 00:09 > > > >To: manet@ietf.org > > > >Cc: ramanath@bbn.com > > > >Subject: [manet] Carrier sense threshold/range control > > > > > > > > > > > > > > > >I am looking for pointers to research on the control of > > > carrier sensing > > > >range in lieu of using RTS/CTS to address the hidden node > > > >problem? > > > > > > > >To elaborate, the threshold for when carrier is declared to > > > be "sensed" > > > >can be adjusted in many radios. Using this facility, one > > > could possibly > > > >make the "carrier sense range" approximately twice the > > > "communication > > > >range" (successful packet reception), and detect hidden nodes. > > > > > > > >This is by no means a new idea, and I vaguely recally some > > > mention of > > > >it on this list. Of course, there are a number of factors > > > that make the > > > >problem far more complex than the simple statement above > > > indicates, and > > > >it is not immediately clear whether it will be effective at all. > > > > > > > >I am looking for papers, tech reports, or any publicly available > > > >material > > > >(non-proprietary) on this issue. > > > > > > > >Many thanks in advance, > > > > > > > >-Ram. > > > > > > > >_______________________________________________ > > > >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 > > > > > > > > > > > > > > > _______________________________________________ > 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 Fri Jul 11 15:22:56 2003 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 PAA12264 for ; Fri, 11 Jul 2003 15:22:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3TQ-0002ig-4M for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 15:22:28 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BJMSTp010450 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 15:22:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3TQ-0002iT-0Z for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 15:22: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 PAA12247 for ; Fri, 11 Jul 2003 15:22:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b3TL-0000uA-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 15:22:23 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19b3TL-0000u7-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 15:22:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3T0-0002e7-DH; Fri, 11 Jul 2003 15: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 19b3Sq-0002du-3f for manet@optimus.ietf.org; Fri, 11 Jul 2003 15:21: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 PAA12223 for ; Fri, 11 Jul 2003 15:21:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b3So-0000tv-00 for manet@ietf.org; Fri, 11 Jul 2003 15:21:50 -0400 Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu) by ietf-mx with esmtp (Exim 4.12) id 19b3So-0000ts-00 for manet@ietf.org; Fri, 11 Jul 2003 15:21:50 -0400 Received: by mail.eecis.udel.edu (Postfix, from userid 62) id 2553F3299E; Fri, 11 Jul 2003 15:21:50 -0400 (EDT) Received: from buckwheat.cis.udel.edu (buckwheat.cis.udel.edu [128.4.131.43]) by mail.eecis.udel.edu (Postfix) with ESMTP id 4DEBC32984; Fri, 11 Jul 2003 15:21:49 -0400 (EDT) Date: Fri, 11 Jul 2003 15:21:49 -0400 (EDT) From: Sonny Rajagopalan X-X-Sender: To: Siddharth Ray Cc: Subject: Re: [manet] Glomosim In-Reply-To: <20030711142349.85439.qmail@web20106.mail.yahoo.com> Message-ID: X-Spam-Status: No, hits=-4.2 required=6.0 tests=DEPT_RCVD,EMAIL_ATTRIBUTION,IN_REP_TO,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: , > glomosim for simulation. I have a friend in UCBerkely > who says that glomosim can be used when people are > just starting to learn simulation but cannot be really > used for some serious simulations. Can anybody clarify That is definitely untrue. GlomoSim can be, and indeed is being, used for very serious simulations. In my view, given a choice between the use of Glomosim and NS2, I would much rather use GlomoSim -- some people in the community feel NS-2's MAC layer and below are too simplistic. Cheers, Sonny. ---- >From the desk of Sonny Rajagopalan @ http://www.cis.udel.edu/~rajagopa ---- On Fri, 11 Jul 2003, Siddharth Ray wrote: > Hi Markus, > Well, I wanted to clarify something about glomosim. I > have heard that glomosim is not supported and hence, > there are a lot of bugs in it. The papers which I have > gone through in ACM etc, none of them have used > glomosim for simulation. I have a friend in UCBerkely > who says that glomosim can be used when people are > just starting to learn simulation but cannot be really > used for some serious simulations. Can anybody clarify > this for me. > Thanks, > Siddharth > > ===== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 11 15:29:47 2003 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 PAA12687 for ; Fri, 11 Jul 2003 15:29: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 19b3a0-0003Vu-M3 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 15:29:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BJTGvB013500 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 15:29:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3a0-0003Ve-CD for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 15:29: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 PAA12578 for ; Fri, 11 Jul 2003 15:29:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b3Zx-0000za-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 15:29:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19b3Zx-0000zX-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 15:29:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3Zm-0003Ov-Ku; Fri, 11 Jul 2003 15:29:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3Z8-0003Hq-Lx for manet@optimus.ietf.org; Fri, 11 Jul 2003 15: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 PAA12526 for ; Fri, 11 Jul 2003 15:28:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b3Z7-0000ya-00 for manet@ietf.org; Fri, 11 Jul 2003 15:28:21 -0400 Received: from hellmouth3.gatech.edu ([130.207.165.163] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19b3Z6-0000yX-00 for manet@ietf.org; Fri, 11 Jul 2003 15:28:20 -0400 Received: from hellmouth3.gatech.edu (localhost [127.0.0.1]) by hellmouth3.gatech.edu (Postfix) with SMTP id 5EC5E220FEE for ; Fri, 11 Jul 2003 15:28:20 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: from acmey.gatech.edu (acmey.prism.gatech.edu [130.207.171.27]) by hellmouth3.gatech.edu (Postfix) with ESMTP id 4573B220FEB for ; Fri, 11 Jul 2003 15:28:20 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: by acmey.gatech.edu (Postfix, from userid 21503) id 2E8C331F20; Fri, 11 Jul 2003 15:28:20 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by acmey.gatech.edu (Postfix) with ESMTP id 269F4330EE for ; Fri, 11 Jul 2003 15:28:20 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Date: Fri, 11 Jul 2003 15:28:20 -0400 (EDT) From: Young-Jun Lee X-X-Sender: To: Subject: [manet] Where to put on-demand routing protocol 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, In the INFOCOM paper 'Performance comparison of two on-demand routing protocols for ad hoc networks' (S. Das, C. Perkins, and E. Royer), the simulation model section says "The routing model sees all data packets transmitted or forwarded, and responds by invoking routing activities as appropriate". Does it mean that on-demand routing protocol like AODV is between L3 and L4, or somewhere else? Where exactly can on-demand protocols be in the protocol stack? Young _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 11 15:33:07 2003 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 PAA13292 for ; Fri, 11 Jul 2003 15:33:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3dE-0004cr-7f for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 15:32:38 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BJWa8N017775 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 15:32:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3dD-0004cc-Ud for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 15:32: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 PAA13222 for ; Fri, 11 Jul 2003 15:32:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b3dC-0001B9-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 15:32:34 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19b3dC-0001B6-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 15:32:34 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3cg-0004Cp-1K; Fri, 11 Jul 2003 15: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 19b3bo-0003yR-6S for manet@optimus.ietf.org; Fri, 11 Jul 2003 15:31: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 PAA12990 for ; Fri, 11 Jul 2003 15:31:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b3bm-000176-00 for manet@ietf.org; Fri, 11 Jul 2003 15:31:06 -0400 Received: from vitalstatistix.cs.uoregon.edu ([128.223.4.19] helo=cs.uoregon.edu ident=root) by ietf-mx with esmtp (Exim 4.12) id 19b3bk-00016j-00 for manet@ietf.org; Fri, 11 Jul 2003 15:31:05 -0400 Received: from virix.cs.uoregon.edu (manoj@virix.cs.uoregon.edu [128.223.4.133]) by cs.uoregon.edu (8.12.9/8.12.8) with ESMTP id h6BJV2BJ000632; Fri, 11 Jul 2003 12:31:02 -0700 (PDT) Date: Fri, 11 Jul 2003 12:31:02 -0700 (PDT) From: Manoj K Pandey To: Sonny Rajagopalan cc: Siddharth Ray , Subject: Re: [manet] Glomosim 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: , just to add to what Sonny said: the design of radio and mobility layers are really nice in glomosim. also, there are lot of publications based on glomosim simulations... you could go to citeseer and search glomosim... the list is pretty big... including papers from Infocom! and finally, it can be tuned for parallel simulation based on multiple partitioning of the field size [using the underlying parsec platform]. thnx manoj ****************************** Manoj Pandey, PhD student, #226, Deschutes, Computer and Information Science, University of Oregon, Phone# 541-346-1381 [Office], www.cs.uoregon.edu/~manoj ****************************** On Fri, 11 Jul 2003, Sonny Rajagopalan wrote: > > glomosim for simulation. I have a friend in UCBerkely > > who says that glomosim can be used when people are > > just starting to learn simulation but cannot be really > > used for some serious simulations. Can anybody clarify > > That is definitely untrue. GlomoSim can be, and indeed is being, used for > very serious simulations. In my view, given a choice between the use of > Glomosim and NS2, I would much rather use GlomoSim -- some people in the > community feel NS-2's MAC layer and below are too simplistic. > > Cheers, > Sonny. > ---- > >From the desk of Sonny Rajagopalan @ http://www.cis.udel.edu/~rajagopa > ---- > > On Fri, 11 Jul 2003, Siddharth Ray wrote: > > > Hi Markus, > > Well, I wanted to clarify something about glomosim. I > > have heard that glomosim is not supported and hence, > > there are a lot of bugs in it. The papers which I have > > gone through in ACM etc, none of them have used > > glomosim for simulation. I have a friend in UCBerkely > > who says that glomosim can be used when people are > > just starting to learn simulation but cannot be really > > used for some serious simulations. Can anybody clarify > > this for me. > > Thanks, > > Siddharth > > > > ===== > > > _______________________________________________ > 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 Jul 11 15:42:36 2003 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 PAA13938 for ; Fri, 11 Jul 2003 15:42:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3mS-0005zS-Of for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 15:42:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BJg8AV023021 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 15:42:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3mS-0005zE-Lp for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 15:42:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13916 for ; Fri, 11 Jul 2003 15:42:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b3mR-0001PM-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 15:42:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19b3mQ-0001PJ-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 15:42:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3mK-0005vP-IB; Fri, 11 Jul 2003 15:42:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b3la-0005qQ-GL for manet@optimus.ietf.org; Fri, 11 Jul 2003 15:41: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 PAA13850 for ; Fri, 11 Jul 2003 15:41:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b3lY-0001OE-00 for manet@ietf.org; Fri, 11 Jul 2003 15:41:12 -0400 Received: from hellmouth4.gatech.edu ([130.207.165.164] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19b3lY-0001Nt-00 for manet@ietf.org; Fri, 11 Jul 2003 15:41:12 -0400 Received: from hellmouth4.gatech.edu (localhost [127.0.0.1]) by hellmouth4.gatech.edu (Postfix) with SMTP id 89F6AA5B7 for ; Fri, 11 Jul 2003 15:40:42 -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 76577A48D for ; Fri, 11 Jul 2003 15:40:42 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: by acmey.gatech.edu (Postfix, from userid 21503) id 62AE231F20; Fri, 11 Jul 2003 15:40:42 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by acmey.gatech.edu (Postfix) with ESMTP id 58FC7330EE for ; Fri, 11 Jul 2003 15:40:42 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Date: Fri, 11 Jul 2003 15:40:42 -0400 (EDT) From: Young-Jun Lee X-X-Sender: To: Subject: Re: [manet] Glomosim 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: , What about the scalability? Is it reasonal to do simulation using Glomosim for a large scale ad hoc network with a size of a few hundred or one thousand? On Fri, 11 Jul 2003, Manoj K Pandey wrote: > just to add to what Sonny said: > the design of radio and mobility layers are really nice in glomosim. > > also, there are lot of publications based on glomosim simulations... > you could go to citeseer and search glomosim... the list > is pretty big... including papers from Infocom! > > and finally, it can be tuned for parallel simulation > based on multiple partitioning of the field size [using the underlying > parsec platform]. > > thnx > manoj > > ****************************** > Manoj Pandey, PhD student, > #226, Deschutes, Computer and Information Science, > University of Oregon, Phone# 541-346-1381 [Office], > www.cs.uoregon.edu/~manoj > ****************************** > > On Fri, 11 Jul 2003, Sonny Rajagopalan wrote: > > > > glomosim for simulation. I have a friend in UCBerkely > > > who says that glomosim can be used when people are > > > just starting to learn simulation but cannot be really > > > used for some serious simulations. Can anybody clarify > > > > That is definitely untrue. GlomoSim can be, and indeed is being, used for > > very serious simulations. In my view, given a choice between the use of > > Glomosim and NS2, I would much rather use GlomoSim -- some people in the > > community feel NS-2's MAC layer and below are too simplistic. > > > > Cheers, > > Sonny. > > ---- > > >From the desk of Sonny Rajagopalan @ http://www.cis.udel.edu/~rajagopa > > ---- > > > > On Fri, 11 Jul 2003, Siddharth Ray wrote: > > > > > Hi Markus, > > > Well, I wanted to clarify something about glomosim. I > > > have heard that glomosim is not supported and hence, > > > there are a lot of bugs in it. The papers which I have > > > gone through in ACM etc, none of them have used > > > glomosim for simulation. I have a friend in UCBerkely > > > who says that glomosim can be used when people are > > > just starting to learn simulation but cannot be really > > > used for some serious simulations. Can anybody clarify > > > this for me. > > > Thanks, > > > Siddharth > > > > > > ===== > > > > > > _______________________________________________ > > 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 Fri Jul 11 16:32:54 2003 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 QAA15628 for ; Fri, 11 Jul 2003 16:32:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b4Z8-00018q-1C for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 16:32:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BKWQsc004383 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 16:32:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b4Z7-00018c-Tg for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 16:32: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 QAA15612 for ; Fri, 11 Jul 2003 16:32:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b4Z5-0001vl-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 16:32:23 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19b4Z5-0001vi-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 16:32:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b4Yk-0000yu-JK; Fri, 11 Jul 2003 16: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 19b4YI-0000os-3s for manet@optimus.ietf.org; Fri, 11 Jul 2003 16:31: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 QAA15581 for ; Fri, 11 Jul 2003 16:31:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b4YG-0001uj-00 for manet@ietf.org; Fri, 11 Jul 2003 16:31:32 -0400 Received: from [130.15.22.4] (helo=wasp.ECE.QUEENSU.CA) by ietf-mx with esmtp (Exim 4.12) id 19b4YF-0001ug-00 for manet@ietf.org; Fri, 11 Jul 2003 16:31:31 -0400 Received: from acer7k2wrwolsy ([24.226.47.100]) by wasp.ECE.QUEENSU.CA with Microsoft SMTPSVC(5.0.2195.5329); Fri, 11 Jul 2003 16:32:03 -0400 From: "Chi-Hsiang Yeh" To: "'Alaa Muqattash'" , "'#LI ZHIFEI#'" Cc: Subject: RE: [manet] Carrier sense threshold/range control Date: Fri, 11 Jul 2003 16:31:04 -0400 Message-ID: <003801c347eb$5d0a7940$642fe218@acer7k2wrwolsy> 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: <00d501c347cd$27f48570$8cde8796@arizonaalaa> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 11 Jul 2003 20:32:03.0562 (UTC) FILETIME=[7CF1E4A0:01C347EB] 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, Alaa, The Globecom'02 paper of Xu, Gerla, and Bae defined interference range as "the range within which stations in receive mode will be "interfered with" by an unrelated transmitter and thus suffer a loss." This paper assumes that wireless stations are transmitting at a fixed power level, using the same modulation etc... I myself usually assume that there is a minimum interference threshold every receiver needs to be able to tolerate, where the resultant collision probability is sufficiently small when the cumulative interference is smaller than that threshold. If you have lower gain or need higher SINR, the associated transmitter needs to transmit at a power level that is sufficiently high. I call a related parameter "maximum interfered range". This value is fixed for a certain transmission, but different transmissions have different values. For a receiver, there is another parameter "maximum interfering range". My protocols need them to determine the power levels for transmitting RTS and CTS messages respectively. You may also look at J. L. Sobrinho and A. S. Krishnakumar, "Quality-of-Service in ad hoc carrier sense multiple access networks," IEEE Journal on Selected Areas in Communications, 17(8), August 1999, pp. 1353-1368. Regards, Chihsiang > -----Original Message----- > From: Alaa Muqattash [mailto:alaa@ece.arizona.edu] > Sent: Friday, July 11, 2003 12:55 PM > To: Chi-Hsiang Yeh; '#LI ZHIFEI#' > Cc: manet@ietf.org > Subject: Re: [manet] Carrier sense threshold/range control > > > Could you please explain what do you mean by the > "interference range"? I don't think that this range is fixed. > Instead, it depends on: > > 1- The transmission power > 2- The channel gain between the transmitter & receiver > 3- The minimum SNR threshold required for reliable communication > > For example, fixing all other parameters, if the required SNR > is increased, then your interference range is increased. > > Any thoughts? > > regards, > Alaa > ----- Original Message ----- > From: "Chi-Hsiang Yeh" > To: "'#LI ZHIFEI#'" > Cc: > Sent: Friday, July 11, 2003 9:36 AM > Subject: RE: [manet] Carrier sense threshold/range control > > > > > -----Original Message----- > > > From: #LI ZHIFEI# [mailto:zhifeili@pmail.ntu.edu.sg] > > > Sent: Friday, July 11, 2003 4:45 AM > > > To: Chi-Hsiang Yeh > > > Cc: manet@ietf.org > > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > > > > >Also, when SR >= IR + TR, topology 2 (in your previous > e-mail) and > > > >other topologies without obstacles would not suffer from > the hidden > > > >terminal problem (without considering collisions of control > > > >messages and propagation characteristics/delays etc. of course). > > > > > > That is true but at the cost of capacity. Moreover, if > SR >= IR + > > > TR, it seems that the RTS/CTS do not have much meaning any more. > > > > You are right, for free space. For indoor environments, strategies > > using large SR alone do not work well due to obstacles. If > anyone has > > or know experiements on this issue (indoor + large SR), I'll > > appreciate it if you could give me a pointer. > > > > > However, as pointed out by some work, whether the > > > SR can be set to greater than (IR + TR) depends upon the > antenna's > > > sensitivity. > > > > You are right. And it also depends on path loss etc. There > is always a > > limit on SR, and in reality it may not be easy to know > these parameter > > values directly or to make SR=IR+TR. > > > > Chihsiang > > > > > > > > > > > > > > > > > > -----Original Message----- > > > From: Chi-Hsiang Yeh [mailto:chi-hsiang.yeh@ece.queensu.ca] > > > Sent: divendres, 11 / juliol / 2003 12:09 > > > To: #LI ZHIFEI#; manet@ietf.org > > > Cc: 'Vikram Dham' > > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > > > > Hi, Zhifei, > > > > > > > > Though we may not be elminating all the hidden terminals > > > but we may > > > > >decrease > > > > >the probability of occurence of hidden terminals by > > > > extending sensing range to > > > > >2SR. ???? >2TR > > > > > > > > The objective of elminating the hidden terminal problem is to > > > > reduce collisions and thus increase the channel utilization. > > > > However, if you increase the sensing range, the > interfering range > > > > is also increased and thus the spatial reuse is greatly reduced. > > > > > > This is not true. Besides SR and TR, there is another parameter > > > "interference range (IR)", which is not necessarily equal > to SR. By > > > lowering the threshold for sensing, increasing SR does not affect > > > IR. Instead, IR is increased when the associated > transmission power > > > level is increased. > > > > > > Also, when SR >= IR + TR, topology 2 (in your previous > > > e-mail) and other topologies without obstacles would not > suffer from > > > the hidden terminal problem (without considering collisions of > > > control messages and propagation characteristics/delays etc. of > > > course). > > > > > > Chihsiang > > > > > > > Of course, if capture is enabled, it may be a different story. > > > > However, with capture, fairness becomse worse (which is my main > > > > concern). Moreover, as I have mentioned, when the sensing range > > > > (SR) is made greater than transmission range (TR), > > > > how long a node should defer its transmission when it detects > > > > a SR frame is a very difficult job as > > > > the node cannot interpret the conent of a SR frame. > > > > > > > > > > > > > > > > Li zhifei > > > > > > > > > > > > -----Original Message----- > > > > From: Vikram Dham [mailto:vdham@vt.edu] > > > > Sent: dijous, 10 / juliol / 2003 23:02 > > > > To: #LI ZHIFEI#; manet > > > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > > > > > > > Hello Zhifei Li, > > > > > > > > Though topology 2 also may have scenarios with hidden terminal, > > > > but in a wireless network, > > > > > > > > probability (distance between nodes > 2SR) =< probability > > > > (distance between nodes > SR ). > > > > > > > > Though we may not be elminating all the hidden > terminals but we > > > > may decrease the probability of occurence of hidden > terminals by > > > > extending sensing range to > > > > 2SR. > > > > > > > > Regards > > > > > > > > Vikram Dham > > > > >===== Original Message From #LI ZHIFEI# > > > > > ===== Hi, Ram > > > > > > > > > >In my view, even the Carrier Sensing Range (SR) is two > times of > > > > >the > > > > Transmission Range (TR ), the hidden-termianl problem is > > > still there. > > > > >This can be illustrated as the following two topologies: > > > > > > > > > >Topology 1: > > > Topology 2: > > > > > > > > > >A -> B <- C > A -> B > > > C<- D > > > > > > > > > >(note that the distance between two neighboring nodes are > > > > equal to the > > > > transmission range, i.e., one hop) > > > > > > > > > >The first topology is tipycally used to illustrate the > well-known > > > > hidden-terminal problem, but with an implicit assumption, > > > i.e., SR=TR. > > > > >If SR=2*TR, the hidden-terminal problem seems not > exist any more > > > > >in this > > > > topology as the nodes A and C can sense the > transmission of each > > > > other. > > > > > > > > > >However, even SR=2*TR, the problem will arise in the > > > second topology. > > > > Specically, when node A starts to transmit to node B, > since node D > > > > >is out of the SR of node A, it cannot detect the transmission. > > > > >Therefore, > > > > node D may also start to transmit to node C, resulting in > > > > collision (or capture). > > > > >In such case, we can say that nodes A and D are hidden > > > > terminal of each > > > > other. We do find the similarities of the performance > between the > > > > two cases: > > > > >topology 1 when SR=TR; and topology 2 when SR=2*TR > > > > > > > > > > > > > > >When SR>TR, another problem is that how a node should > defer its > > > > >transmission > > > > when it detects a SR frame. This is not an easy job > since the node > > > > cannot > > > > >interpret the content of the SR frame. In the IEEE 802.11, > > > > whenever a > > > > >node > > > > detects a SR frame, it will defer by a fixed EFIS > value. However, > > > > our results show > > > > >this fixed value will cause many problems, e.g., unfairness. > > > > Moreover, > > > > >the > > > > capture ability will also greatly affect the performace when > > > > SR>TR. > > > > >For a detailed descrition of these issues, please refer to > > > > the attached > > > > references: > > > > > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > > > > >"Improving Fairness in IEEE 802.11 based MANETs using > > > > Enhanced Carrier > > > > Sensing", submitted to conference, April 2003 > > > > >http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf > > > > > > > > > > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > > > > >"Study of IEEE 802.11 Fairness and its Interaction > with Routing > > > > >Mechanism", > > > > accepted by IEEE MWCN 2003 Singapore, May 2003 > > > > >http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf > > > > > > > > > > > > > > >Though the above papers mainly focus on the the fairness issue > > > > >when > > > > >SR>TR, > > > > the descirtion should also apply to the analysis of the channel > > > > utilization. > > > > >I hope that they will relate to your work and help you. > > > > > > > > > > > > > > >Best regards > > > > >Li ZhiFei > > > > >PhD candidate, > > > > >Center For Multimedia And Network Technology > > > > >School Of Computer Engineering > > > > >Nanyang Technological University > > > > >N4-b2c-08, Nanyang Avenue > > > > >Singapore 639798 > > > > >tel:(65)67906579 > > > > >website: > > > > > > > > > > > > > > >-----Original Message----- > > > > >From: Ram Ramanathan [mailto:ramanath@bbn.com] > > > > >Sent: dijous, 10 / juliol / 2003 00:09 > > > > >To: manet@ietf.org > > > > >Cc: ramanath@bbn.com > > > > >Subject: [manet] Carrier sense threshold/range control > > > > > > > > > > > > > > > > > > > >I am looking for pointers to research on the control of > > > > carrier sensing > > > > >range in lieu of using RTS/CTS to address the hidden node > > > > >problem? > > > > > > > > > >To elaborate, the threshold for when carrier is declared to > > > > be "sensed" > > > > >can be adjusted in many radios. Using this facility, one > > > > could possibly > > > > >make the "carrier sense range" approximately twice the > > > > "communication > > > > >range" (successful packet reception), and detect hidden nodes. > > > > > > > > > >This is by no means a new idea, and I vaguely recally some > > > > mention of > > > > >it on this list. Of course, there are a number of factors > > > > that make the > > > > >problem far more complex than the simple statement above > > > > indicates, and > > > > >it is not immediately clear whether it will be > effective at all. > > > > > > > > > >I am looking for papers, tech reports, or any publicly > available > > > > >material > > > > >(non-proprietary) on this issue. > > > > > > > > > >Many thanks in advance, > > > > > > > > > >-Ram. > > > > > > > > > >_______________________________________________ > > > > >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 > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > 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 Jul 11 16:55:56 2003 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 QAA16492 for ; Fri, 11 Jul 2003 16:55:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b4vR-0002fv-Mp for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 16:55:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BKtTjo010283 for manet-archive@odin.ietf.org; Fri, 11 Jul 2003 16:55:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b4vR-0002fm-Hh for manet-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 16:55:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16463 for ; Fri, 11 Jul 2003 16:55:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b4vK-0002Fg-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 16:55:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19b4vK-0002Fd-00 for manet-web-archive@ietf.org; Fri, 11 Jul 2003 16:55:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b4uz-0002Xb-QK; Fri, 11 Jul 2003 16:55:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19b4u2-0002W8-1A for manet@optimus.ietf.org; Fri, 11 Jul 2003 16: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 QAA16412 for ; Fri, 11 Jul 2003 16:53:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19b4tv-0002ED-00 for manet@ietf.org; Fri, 11 Jul 2003 16:53:55 -0400 Received: from wasp.ece.queensu.ca ([130.15.19.4]) by ietf-mx with esmtp (Exim 4.12) id 19b4tu-0002EA-00 for manet@ietf.org; Fri, 11 Jul 2003 16:53:54 -0400 Received: from acer7k2wrwolsy ([24.226.47.100]) by wasp.ECE.QUEENSU.CA with Microsoft SMTPSVC(5.0.2195.5329); Fri, 11 Jul 2003 16:54:27 -0400 From: "Chi-Hsiang Yeh" To: "'#LI ZHIFEI#'" , Subject: RE: [manet] Carrier sense threshold/range control Date: Fri, 11 Jul 2003 16:53:33 -0400 Message-ID: <003901c347ee$81357a60$642fe218@acer7k2wrwolsy> 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: <3D565922795545468AE3E3DA2881BEA90186D842@mail01.student.main.ntu.edu.sg> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-OriginalArrivalTime: 11 Jul 2003 20:54:27.0671 (UTC) FILETIME=[9E18A670:01C347EE] 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, Zhifei, > However, I do believe that when SR is increased, the spatial > reuse in multi-hop networks will be substantially reduced, > which is also pointed out in the above paper. You are right when SR is too large so that CSMA becomes too conservative (and the exposed terminal problem deteriorates). But such reduction in throughput is not caused by increase in IR (and in fact IR is not increased in such a case). SR >= IR + TR is just a condition to solve the hidden terminal problem in open space (as I was pointing out that this was possible when there were no obstacles). It is not necessarily a condition optimized for throughput, collision rate, or other metrics. Best regards, Chihsiang > -----Original Message----- > From: #LI ZHIFEI# [mailto:zhifeili@pmail.ntu.edu.sg] > Sent: Friday, July 11, 2003 4:13 AM > To: Chi-Hsiang Yeh; manet@ietf.org > Subject: RE: [manet] Carrier sense threshold/range control > > > Is there any formal definition about the "interference range"? > > The definition of "interference range" in the following > paper is some confusing to me. > > How effective is the IEEE 802.11 RTS/CTS handshake in ad hoc > networks? > Kaixin Xu; Gerla, M.; Sang Bae; > Global Telecommunications Conference, 2002. GLOBECOM '02. > IEEE , Volume: 1 , Nov 17-21, 2002 > Page(s): 72 -76 > > > However, I do believe that when SR is increased, the spatial > reuse in multi-hop networks will be substantially reduced, > which is also pointed out in the above paper. > > > Best regards > Li ZhiFei > PhD candidate, > Center For Multimedia And Network Technology > School Of Computer Engineering > Nanyang Technological University > N4-b2c-08, Nanyang Avenue > Singapore 639798 > tel:(65)67906579 > website: > > > > -----Original Message----- > From: Chi-Hsiang Yeh [mailto:chi-hsiang.yeh@ece.queensu.ca] > Sent: divendres, 11 / juliol / 2003 12:09 > To: #LI ZHIFEI#; manet@ietf.org > Cc: 'Vikram Dham' > Subject: RE: [manet] Carrier sense threshold/range control > > > Hi, Zhifei, > > > > Though we may not be elminating all the hidden terminals > but we may > > >decrease > > >the probability of occurence of hidden terminals by > > extending sensing range to > > >2SR. ???? >2TR > > > > The objective of elminating the hidden terminal problem is to > > reduce collisions and thus > > increase the channel utilization. However, if you increase > > the sensing range, the interfering range is > > also increased and thus the spatial reuse is greatly reduced. > > This is not true. Besides SR and TR, there is another > parameter "interference range (IR)", which is not necessarily > equal to SR. By lowering the threshold for sensing, > increasing SR does not affect IR. Instead, IR is increased > when the associated transmission power level is increased. > > Also, when SR >= IR + TR, topology 2 (in your previous > e-mail) and other topologies without obstacles would not > suffer from the hidden terminal problem (without considering > collisions of control messages and propagation > characteristics/delays etc. of course). > > Chihsiang > > > Of course, if capture is enabled, it may be a different > > story. However, with capture, fairness becomse worse (which > > is my main concern). > > Moreover, as I have mentioned, when the sensing range (SR) is > > made greater than transmission range (TR), > > how long a node should defer its transmission when it detects > > a SR frame is a very difficult job as > > the node cannot interpret the conent of a SR frame. > > > > > > > > Li zhifei > > > > > > -----Original Message----- > > From: Vikram Dham [mailto:vdham@vt.edu] > > Sent: dijous, 10 / juliol / 2003 23:02 > > To: #LI ZHIFEI#; manet > > Subject: RE: [manet] Carrier sense threshold/range control > > > > > > Hello Zhifei Li, > > > > Though topology 2 also may have scenarios with hidden > > terminal, but in a > > wireless network, > > > > probability (distance between nodes > 2SR) =< probability > > (distance between > > nodes > SR ). > > > > Though we may not be elminating all the hidden terminals but > > we may decrease > > the probability of occurence of hidden terminals by extending > > sensing range to > > 2SR. > > > > Regards > > > > Vikram Dham > > >===== Original Message From #LI ZHIFEI# > > >===== Hi, Ram > > > > > >In my view, even the Carrier Sensing Range (SR) is two times of the > > Transmission Range (TR ), the hidden-termianl problem is > still there. > > >This can be illustrated as the following two topologies: > > > > > >Topology 1: > Topology 2: > > > > > >A -> B <- C A -> B > C<- D > > > > > >(note that the distance between two neighboring nodes are > > equal to the > > transmission range, i.e., one hop) > > > > > >The first topology is tipycally used to illustrate the well-known > > hidden-terminal problem, but with an implicit assumption, > i.e., SR=TR. > > >If SR=2*TR, the hidden-terminal problem seems not exist any more in > > >this > > topology as the nodes A and C can sense the transmission of > > each other. > > > > > >However, even SR=2*TR, the problem will arise in the > second topology. > > Specically, when node A starts to transmit to node B, since node D > > >is out of the SR of node A, it cannot detect the transmission. > > >Therefore, > > node D may also start to transmit to node C, resulting in > > collision (or > > capture). > > >In such case, we can say that nodes A and D are hidden > > terminal of each > > other. We do find the similarities of the performance between > > the two cases: > > >topology 1 when SR=TR; and topology 2 when SR=2*TR > > > > > > > > >When SR>TR, another problem is that how a node should defer its > > >transmission > > when it detects a SR frame. This is not an easy job since the > > node cannot > > >interpret the content of the SR frame. In the IEEE 802.11, > > whenever a > > >node > > detects a SR frame, it will defer by a fixed EFIS value. > > However, our results > > show > > >this fixed value will cause many problems, e.g., unfairness. > > Moreover, > > >the > > capture ability will also greatly affect the performace when SR>TR. > > >For a detailed descrition of these issues, please refer to > > the attached > > references: > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > > >"Improving Fairness in IEEE 802.11 based MANETs using > > Enhanced Carrier > > Sensing", submitted to conference, April 2003 > > >http://www.ntu.edu.sg/home5/pg03802331/papers/ecs.pdf > > > > > > > > >Zhifei Li, Sukumar Nandi, Anil K. Gupta, > > >"Study of IEEE 802.11 Fairness and its Interaction with Routing > > >Mechanism", > > accepted by IEEE MWCN 2003 Singapore, May 2003 > > >http://www.ntu.edu.sg/home5/pg03802331/papers/mwcn03.pdf > > > > > > > > >Though the above papers mainly focus on the the fairness issue when > > >SR>TR, > > the descirtion should also apply to the analysis of the > > channel utilization. > > >I hope that they will relate to your work and help you. > > > > > > > > >Best regards > > >Li ZhiFei > > >PhD candidate, > > >Center For Multimedia And Network Technology > > >School Of Computer Engineering > > >Nanyang Technological University > > >N4-b2c-08, Nanyang Avenue > > >Singapore 639798 > > >tel:(65)67906579 > > >website: > > > > > > > > >-----Original Message----- > > >From: Ram Ramanathan [mailto:ramanath@bbn.com] > > >Sent: dijous, 10 / juliol / 2003 00:09 > > >To: manet@ietf.org > > >Cc: ramanath@bbn.com > > >Subject: [manet] Carrier sense threshold/range control > > > > > > > > > > > >I am looking for pointers to research on the control of > > carrier sensing > > >range in lieu of using RTS/CTS to address the hidden node problem? > > > > > >To elaborate, the threshold for when carrier is declared to > > be "sensed" > > >can be adjusted in many radios. Using this facility, one > > could possibly > > >make the "carrier sense range" approximately twice the > > "communication > > >range" (successful packet reception), and detect hidden nodes. > > > > > >This is by no means a new idea, and I vaguely recally some > > mention of > > >it on this list. Of course, there are a number of factors > > that make the > > >problem far more complex than the simple statement above > > indicates, and > > >it is not immediately clear whether it will be effective at all. > > > > > >I am looking for papers, tech reports, or any publicly available > > >material > > >(non-proprietary) on this issue. > > > > > >Many thanks in advance, > > > > > >-Ram. > > > > > >_______________________________________________ > > >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 > > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat Jul 12 00:30:06 2003 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 AAA07150 for ; Sat, 12 Jul 2003 00:30:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bC0y-0004qw-3u for manet-archive@odin.ietf.org; Sat, 12 Jul 2003 00:29:40 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6C4TeNx018648 for manet-archive@odin.ietf.org; Sat, 12 Jul 2003 00:29:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bC0y-0004qh-0h for manet-web-archive@optimus.ietf.org; Sat, 12 Jul 2003 00:29: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 AAA07120 for ; Sat, 12 Jul 2003 00:29:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19bC0v-0000H2-00 for manet-web-archive@ietf.org; Sat, 12 Jul 2003 00:29:37 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19bC0u-0000Gz-00 for manet-web-archive@ietf.org; Sat, 12 Jul 2003 00:29:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bC0M-0004pV-0A; Sat, 12 Jul 2003 00:29:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bC03-0004pE-TE for manet@optimus.ietf.org; Sat, 12 Jul 2003 00:28: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 AAA07062 for ; Sat, 12 Jul 2003 00:28:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19bC01-0000G4-00 for manet@ietf.org; Sat, 12 Jul 2003 00:28:41 -0400 Received: from web14703.mail.yahoo.com ([216.136.224.120]) by ietf-mx with smtp (Exim 4.12) id 19bC00-0000G1-00 for manet@ietf.org; Sat, 12 Jul 2003 00:28:40 -0400 Message-ID: <20030712042840.41117.qmail@web14703.mail.yahoo.com> Received: from [203.197.138.163] by web14703.mail.yahoo.com via HTTP; Fri, 11 Jul 2003 21:28:40 PDT Date: Fri, 11 Jul 2003 21:28:40 -0700 (PDT) From: panneer pandi To: AODV MailingList , Glomosim MailingList , Manet MailingList MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1588497349-1057984120=:41077" Subject: [manet] relay route reply Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-1588497349-1057984120=:41077 Content-Type: text/plain; charset=us-ascii Hello friends I am using Glomosim for my simulation. The routing protocol which i am using is AODV. I am not able to understand one concept, in relay route reply why do they check this condition if (destAddr == ANY_DEST) { NetworkIpSendRawGlomoMessage(node, newMsg, ANY_DEST, CONTROL, IPPROTO_AODV, 1); } because relay reply wonnt use ANY_DEST and why do they call, network ip send raw glomo message what is the purpose of it. It would be helpfull if you respond quickly. Thank's for all. --------------------------------- Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! --0-1588497349-1057984120=:41077 Content-Type: text/html; charset=us-ascii
Hello friends
 
 
          I am using Glomosim for my simulation. The routing protocol which i am using is AODV. I am not able to understand one concept, in relay route reply why do they check this condition 
if (destAddr == ANY_DEST)

    {

NetworkIpSendRawGlomoMessage(node, newMsg, ANY_DEST, CONTROL, IPPROTO_AODV, 1);

    }

 because relay reply wonnt use ANY_DEST and why do they call, network ip send raw glomo message what is the purpose of it.
 
 It would be helpfull if you respond quickly.
 
                                Thank's for all.

Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month! --0-1588497349-1057984120=:41077-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat Jul 12 00:36:48 2003 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 AAA07523 for ; Sat, 12 Jul 2003 00:36:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bC7P-0005j5-6w for manet-archive@odin.ietf.org; Sat, 12 Jul 2003 00:36:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6C4aJ7A022006 for manet-archive@odin.ietf.org; Sat, 12 Jul 2003 00:36:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bC7P-0005ir-2a for manet-web-archive@optimus.ietf.org; Sat, 12 Jul 2003 00:36: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 AAA07470 for ; Sat, 12 Jul 2003 00:36:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19bC7M-0000NW-00 for manet-web-archive@ietf.org; Sat, 12 Jul 2003 00:36:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19bC7L-0000NT-00 for manet-web-archive@ietf.org; Sat, 12 Jul 2003 00:36:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bC78-0005ZN-Q7; Sat, 12 Jul 2003 00: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 19bC6F-0005Or-Fb for manet@optimus.ietf.org; Sat, 12 Jul 2003 00:35: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 AAA07401 for ; Sat, 12 Jul 2003 00:35:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19bC6C-0000M8-00 for manet@ietf.org; Sat, 12 Jul 2003 00:35:04 -0400 Received: from x86unx3.comp.nus.edu.sg ([137.132.90.3]) by ietf-mx with esmtp (Exim 4.12) id 19bC6B-0000Lq-00 for manet@ietf.org; Sat, 12 Jul 2003 00:35:03 -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 MAA25897 for ; Sat, 12 Jul 2003 12:34:56 +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 13894; Sat, 12 Jul 2003 12:34:55 +0800 (SGT) Received: (from http@localhost) by se11.comp.nus.edu.sg (8.12.2+Sun/8.12.5) id h6C4YtoD014569; Sat, 12 Jul 2003 12:34:55 +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 172.18.179.81) (SquirrelMail authenticated user erinninn) by mysoc.nus.edu.sg with HTTP; Sat, 12 Jul 2003 12:34:55 +0800 (SGT) Message-ID: <40658.137.132.80.35.1057984495.squirrel@mysoc.nus.edu.sg> Date: Sat, 12 Jul 2003 12:34:55 +0800 (SGT) To: In-Reply-To: References: 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] Problem using setdest to generate scenario files Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 all, I have faced the following problem when I tried to generate scenario files using setdest function in NS. [root@soccf-cb-014 setdest]# ./setdest -n 20 -p 2.0 -s 10.0 -t 200 -x 500 -y 500 > scen-30-test bash: ./setdest: /usr/libexec/ld-elf.so.1: bad ELF interpreter: No such file or directory I think the problem may be related to the dynamic linker used by Redhat Linux 9 (the platform I am currently using). However, due to my limited knowledge on Redhat Linux 9, I don't know how to solve the above mentioned problem. Could anyone help? Thanks in advance! regards, inn inn _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sun Jul 13 19:20:54 2003 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 TAA08843 for ; Sun, 13 Jul 2003 19:20:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bq8p-0007rR-GI for manet-archive@odin.ietf.org; Sun, 13 Jul 2003 19:20:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6DNKRmK030212 for manet-archive@odin.ietf.org; Sun, 13 Jul 2003 19:20:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bq8p-0007rD-DD for manet-web-archive@optimus.ietf.org; Sun, 13 Jul 2003 19:20: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 TAA08838 for ; Sun, 13 Jul 2003 19:20:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19bq8j-0007lo-00 for manet-web-archive@ietf.org; Sun, 13 Jul 2003 19:20:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19bq8i-0007lk-00 for manet-web-archive@ietf.org; Sun, 13 Jul 2003 19:20:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bq8P-0007pu-Ox; Sun, 13 Jul 2003 19:20:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19bq7s-0007p8-T6 for manet@optimus.ietf.org; Sun, 13 Jul 2003 19:19:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08823 for ; Sun, 13 Jul 2003 19:19:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19bq7r-0007lJ-00 for manet@ietf.org; Sun, 13 Jul 2003 19:19:27 -0400 Received: from web10003.mail.yahoo.com ([216.136.130.39]) by ietf-mx with smtp (Exim 4.12) id 19bq7q-0007lG-00 for manet@ietf.org; Sun, 13 Jul 2003 19:19:26 -0400 Message-ID: <20030713231926.40336.qmail@web10003.mail.yahoo.com> Received: from [80.110.14.123] by web10003.mail.yahoo.com via HTTP; Sun, 13 Jul 2003 16:19:26 PDT Date: Sun, 13 Jul 2003 16:19:26 -0700 (PDT) From: Jaehoon Jeong To: corson@flarion.com, macker@itd.nrl.navy.mil Cc: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] About agenda in Vienna meeting Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 manet chairs, I would like to know what manet agenda is. When would you let us know it? Also, I am wondering if Ad Hoc IP Address Autoconfiguration will be discussed as wg issue. Thanks. Regards, Jaehoon __________________________________ 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 Sun Jul 13 23:46:54 2003 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 XAA12937 for ; Sun, 13 Jul 2003 23:46:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19buIF-0008Uv-8i for manet-archive@odin.ietf.org; Sun, 13 Jul 2003 23:46:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6E3kRJ2032659 for manet-archive@odin.ietf.org; Sun, 13 Jul 2003 23:46:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19buIF-0008Ug-4P for manet-web-archive@optimus.ietf.org; Sun, 13 Jul 2003 23:46: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 XAA12930 for ; Sun, 13 Jul 2003 23:46:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19buIC-000152-00 for manet-web-archive@ietf.org; Sun, 13 Jul 2003 23:46:25 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19buIC-00014z-00 for manet-web-archive@ietf.org; Sun, 13 Jul 2003 23:46:24 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19buHp-0008TM-Kj; Sun, 13 Jul 2003 23:46:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19buGt-0008Sp-Ht for manet@optimus.ietf.org; Sun, 13 Jul 2003 23: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 XAA12864 for ; Sun, 13 Jul 2003 23:44:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19buGm-00014a-00 for manet@ietf.org; Sun, 13 Jul 2003 23:44:56 -0400 Received: from mbox1.ntu.edu.sg ([155.69.5.171]) by ietf-mx with esmtp (Exim 4.12) id 19buGl-00014F-00 for manet@ietf.org; Sun, 13 Jul 2003 23:44:55 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Mon, 14 Jul 2003 11:37:57 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 14 Jul 2003 11:37:56 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D88E@mail01.student.main.ntu.edu.sg> Thread-Topic: how to detect the type of sensing range frame Thread-Index: AcNJuVAe8fw7veEDQfaSA1+rIhYeKw== From: "#LI ZHIFEI#" To: X-OriginalArrivalTime: 14 Jul 2003 03:37:57.0218 (UTC) FILETIME=[50EFDC20:01C349B9] Content-Transfer-Encoding: quoted-printable Subject: [manet] how to detect the type of sensing range frame Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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, In the IEEE 802.11, when the sensing range (SR) is assumed to be greater = than the transmission range,=20 is there any methods for a node that detects an SR frame to identify the = type (i.e., RTS/CTS/Data/ACK) of this frame? Note that the node cannot interpret the content of the SR frame. Best regards=20 Li ZhiFei=20 PhD candidate, =20 Center For Multimedia And Network Technology School Of Computer Engineering Nanyang Technological University N4-b2c-08, Nanyang Avenue Singapore 639798 tel:(65)67906579=20 website: =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 14 04:18:05 2003 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 EAA01188 for ; Mon, 14 Jul 2003 04:18:04 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19byWf-0002IO-25 for manet-archive@odin.ietf.org; Mon, 14 Jul 2003 04:17:37 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6E8HZct008815 for manet-archive@odin.ietf.org; Mon, 14 Jul 2003 04:17:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19byWb-0002I5-MB for manet-web-archive@optimus.ietf.org; Mon, 14 Jul 2003 04:17: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 EAA01175 for ; Mon, 14 Jul 2003 04:17:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19byWY-0002eU-00 for manet-web-archive@ietf.org; Mon, 14 Jul 2003 04:17:31 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19byWY-0002eR-00 for manet-web-archive@ietf.org; Mon, 14 Jul 2003 04:17:30 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19byW8-0002GP-JK; Mon, 14 Jul 2003 04:17:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19byVD-0002Ff-1i for manet@optimus.ietf.org; Mon, 14 Jul 2003 04:16: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 EAA01103 for ; Mon, 14 Jul 2003 04:16:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19byVA-0002e0-00 for manet@ietf.org; Mon, 14 Jul 2003 04:16:04 -0400 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 19byV9-0002dd-00 for manet@ietf.org; Mon, 14 Jul 2003 04:16:03 -0400 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2653.19) id <35CFG7FY>; Mon, 14 Jul 2003 04:15:28 -0400 Message-ID: <748C6D0A58C0F94CA63C198B6674697A0192C6B7@ftmail.lab.flarion.com> From: Corson Scott To: "'manet@ietf.org'" Date: Mon, 14 Jul 2003 04:15:25 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [manet] Draft MANET 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: , Folks, Here's what I have so far as a draft agenda: ************ Manet Agenda, Wednesday, 15:30-17:30 Agenda Bashing (5 min) Updates of Current Drafts OLSR update, T. Clausen, U. Aalborg (20 min) TBRPF update, R. Ogier, SRI (20 min.) AODV update, C. Perkins, Nokia (20 min.) Recent Drafts Ad Hoc IP Address Autoconfiguration, draft-jeong-adhoc-ip-addr-autoconf-00.txt, Jaehoon Jeong, ETRI (15 min.) draft-engelstad-manet-name-resolution-00.txt , P. Englestad, Telenor (15 min.) Open Discussion (*) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 14 12:49:56 2003 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 MAA03760 for ; Mon, 14 Jul 2003 12:49:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19c6W1-0000tK-PC for manet-archive@odin.ietf.org; Mon, 14 Jul 2003 12:49:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6EGnTuU003420 for manet-archive@odin.ietf.org; Mon, 14 Jul 2003 12:49:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19c6W1-0000t4-Ig for manet-web-archive@optimus.ietf.org; Mon, 14 Jul 2003 12:49:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03700 for ; Mon, 14 Jul 2003 12:49:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19c6Vz-0002o2-00 for manet-web-archive@ietf.org; Mon, 14 Jul 2003 12:49:27 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19c6Vz-0002nz-00 for manet-web-archive@ietf.org; Mon, 14 Jul 2003 12:49:27 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19c6VZ-0000rV-JH; Mon, 14 Jul 2003 12:49:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19c6VF-0000qw-VO for manet@optimus.ietf.org; Mon, 14 Jul 2003 12:48: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 MAA03621 for ; Mon, 14 Jul 2003 12:48:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19c6VD-0002mr-00 for manet@ietf.org; Mon, 14 Jul 2003 12:48:39 -0400 Received: from nn2.excitenetwork.com ([207.159.120.56] helo=xmxpita.excite.com) by ietf-mx with esmtp (Exim 4.12) id 19c6VD-0002mC-00 for manet@ietf.org; Mon, 14 Jul 2003 12:48:39 -0400 Received: by xmxpita.excite.com (Postfix, from userid 110) id 93E53299E8; Mon, 14 Jul 2003 12:48:00 -0400 (EDT) To: manet@ietf.org Received: from [128.163.173.55] by xprdmailfe21.nwk.excite.com via HTTP; Mon, 14 Jul 2003 12:48:00 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = 3fb9e8fae3e11de0bf79149ac2ee686d Reply-To: jw2000@excite.com From: "Jack Wang" MIME-Version: 1.0 X-Sender: jw2000@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20030714164800.93E53299E8@xmxpita.excite.com> Date: Mon, 14 Jul 2003 12:48:00 -0400 (EDT) Content-Transfer-Encoding: 7bit Subject: [manet] location management Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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: Are there any published works about "location tracking for ad hoc networks"? Thanks a lot. Jack _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 14 14:17:39 2003 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 OAA10705 for ; Mon, 14 Jul 2003 14:17:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19c7su-0006xs-6D for manet-archive@odin.ietf.org; Mon, 14 Jul 2003 14:17:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6EIHCmx026771 for manet-archive@odin.ietf.org; Mon, 14 Jul 2003 14:17:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19c7st-0006xi-3V for manet-web-archive@optimus.ietf.org; Mon, 14 Jul 2003 14:17: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 OAA10640 for ; Mon, 14 Jul 2003 14:17:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19c7sq-0004Z1-00 for manet-web-archive@ietf.org; Mon, 14 Jul 2003 14:17:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19c7sq-0004Yy-00 for manet-web-archive@ietf.org; Mon, 14 Jul 2003 14:17:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19c7sj-0006wQ-R3; Mon, 14 Jul 2003 14:17:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19c7s5-0006vu-Gc for manet@optimus.ietf.org; Mon, 14 Jul 2003 14:16:21 -0400 Received: from gehenna.ece.cornell.edu (gehenna.ece.cornell.edu [128.84.95.235]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10462 for ; Mon, 14 Jul 2003 14:16:18 -0400 (EDT) Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 855E41E4050; Mon, 14 Jul 2003 14:28:34 -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 h6EIGIg01395; Mon, 14 Jul 2003 14:16:18 -0400 Date: Mon, 14 Jul 2003 14:15:05 -0400 (EDT) From: "haas@ece.cornell.edu" To: Jack Wang Cc: manet@ietf.org Subject: Re: [manet] location management In-Reply-To: <20030714164800.93E53299E8@xmxpita.excite.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 Jack, Try the following: 1. Z.J. Haas and B. Liang, "Ad Hoc Location Management Using Quorum Systems,"ACM/IEEE Transactions on Networking, April 1999 2. B. Liang and Z.J. Haas, "Virtual Backbone Generation and Maintenance in Ad Hoc Network Mobility Management," IEEE INFOCOM'2000, Tel Aviv, Israel, March 26-30, 2000 3. Z.J. Haas and B. Liang, "Ad-Hoc Mobility Management with Randomized Database Groups," IEEE ICC'99, Vancouver, BC, Canada, June 6-10, 1999 2. J. Li, Z.J. Haas, and B. Liang, ``Performance Analysis of Random Database Group Scheme for Mobility Management in Ad hoc Network,'' IEEE International Conference on Communications (ICC) 2003, Anchorage, Alaska, May 11-15, 2003 Zygmunt. ==-=-===== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Prof. Zygmunt J. Haas http://people.ece.cornell.edu/haas Wireless Networks Laboratory http://wnl.ece.cornell.edu School of Electrical Engineering Cornell University tel: +1-607-255-3454 323 Frank Rhodes Hall fax: +1-607-255-9072 Ithaca, NY 14853 e-mail: haas@ece.cornell.edu U.S.A WNL web page: http://wnl.ece.cornell.edu ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- On Mon, 14 Jul 2003, Jack Wang wrote: > > Hi all: > > Are there any published works about "location tracking for ad hoc networks"? > > Thanks a lot. > > Jack > > > > > _______________________________________________ > Join Excite! - http://www.excite.com > The most personalized portal on the Web! > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 14 19:42:40 2003 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 TAA06950 for ; Mon, 14 Jul 2003 19:42:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cCxS-0004cr-1l for manet-archive@odin.ietf.org; Mon, 14 Jul 2003 19:42:14 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6ENgENq017775 for manet-archive@odin.ietf.org; Mon, 14 Jul 2003 19:42:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cCxR-0004cc-TE for manet-web-archive@optimus.ietf.org; Mon, 14 Jul 2003 19:42: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 TAA06883 for ; Mon, 14 Jul 2003 19:42:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cCxQ-0002d7-00 for manet-web-archive@ietf.org; Mon, 14 Jul 2003 19:42:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cCxP-0002d3-00 for manet-web-archive@ietf.org; Mon, 14 Jul 2003 19:42:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cCxG-0004bR-5x; Mon, 14 Jul 2003 19:42:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cCwU-0004b5-H0 for manet@optimus.ietf.org; Mon, 14 Jul 2003 19:41: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 TAA06750 for ; Mon, 14 Jul 2003 19:41:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cCwS-0002bC-00 for manet@ietf.org; Mon, 14 Jul 2003 19:41:12 -0400 Received: from law15-f89.law15.hotmail.com ([64.4.23.89] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19cCwS-0002aJ-00 for manet@ietf.org; Mon, 14 Jul 2003 19:41:12 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 14 Jul 2003 16:40:42 -0700 Received: from 62.135.24.142 by lw15fd.law15.hotmail.msn.com with HTTP; Mon, 14 Jul 2003 23:40:42 GMT X-Originating-IP: [62.135.24.142] X-Originating-Email: [reh_elmayet@hotmail.com] From: "reham elmayet" To: manet@ietf.org Date: Mon, 14 Jul 2003 23:40:42 +0000 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 14 Jul 2003 23:40:42.0569 (UTC) FILETIME=[56D68B90:01C34A61] 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 the maximum size allowed to configure the ad hoc invironment, maximum number of  nodes, maximum speed allowed for the mobile node and maximum delay allowed. Also, I want to know if there is a relationship between the movement model and IEEE 802.11 standard and all of these parameters .
Regards,
Reham Elmayet

MSN 8 helps ELIMINATE E-MAIL VIRUSES. Get 2 months FREE*. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 15 01:34:48 2003 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 BAA06614 for ; Tue, 15 Jul 2003 01:34: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 19cISD-0001g1-46 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 01:34:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6F5YLFm006439 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 01:34:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cISC-0001fm-T6 for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 01:34: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 BAA06554 for ; Tue, 15 Jul 2003 01:34:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cIS9-0002Oj-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 01:34:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cIS9-0002Og-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 01:34:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cIRt-0001eV-HY; Tue, 15 Jul 2003 01:34:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cIRi-0001eF-MN for manet@optimus.ietf.org; Tue, 15 Jul 2003 01:33: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 BAA06489 for ; Tue, 15 Jul 2003 01:33:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cIRf-0002Nw-00 for manet@ietf.org; Tue, 15 Jul 2003 01:33:47 -0400 Received: from web8107.mail.in.yahoo.com ([203.199.70.121]) by ietf-mx with smtp (Exim 4.12) id 19cIRe-0002Mu-00 for manet@ietf.org; Tue, 15 Jul 2003 01:33:46 -0400 Message-ID: <20030715053316.96141.qmail@web8107.mail.in.yahoo.com> Received: from [202.141.69.161] by web8107.mail.in.yahoo.com via HTTP; Tue, 15 Jul 2003 06:33:16 BST Date: Tue, 15 Jul 2003 06:33:16 +0100 (BST) From: =?iso-8859-1?q?Ash=20Mohammad=20Abbas?= Subject: Re: [manet] Where to put on-demand routing protocol To: Young-Jun Lee , manet@ietf.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-224475774-1058247196=:94171" 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: , --0-224475774-1058247196=:94171 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sir, Irrespective of the fact that a protocol is on-demand or pro-active, a routing protocol will remain layer-3( Network Layer of OSI model) protocol. After a route has been established, ofcourse, the protocol might be used to send data packets. With best regards, Ash Mohammad Abbas http://www.cse.iitd.ernet.in/~abbas Young-Jun Lee <gte393q@mail.gatech.edu> wrote: All, In the INFOCOM paper 'Performance comparison of two on-demand routing protocols for ad hoc networks' (S. Das, C. Perkins, and E. Royer), the simulation model section says "The routing model sees all data packets transmitted or forwarded, and responds by invoking routing activities as appropriate". Does it mean that on-demand routing protocol like AODV is between L3 and L4, or somewhere else? Where exactly can on-demand protocols be in the protocol stack? Young _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet SMS using the Yahoo! Messenger;Download latest version. --0-224475774-1058247196=:94171 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit

Sir,

Irrespective of the fact that a protocol is on-demand or pro-active, a routing protocol will remain layer-3( Network Layer of OSI model) protocol. After a route has been established, ofcourse, the protocol might be used to send data packets.

With best regards,

Ash Mohammad Abbas

http://www.cse.iitd.ernet.in/~abbas

  Young-Jun Lee &lt;gte393q@mail.gatech.edu&gt; wrote:

All,

In the INFOCOM paper 'Performance comparison of two on-demand routing
protocols for ad hoc networks' (S. Das, C. Perkins, and E. Royer),
the simulation model section says

"The routing model sees all data packets transmitted or forwarded, and
responds by invoking routing activities as appropriate".

Does it mean that on-demand routing protocol like AODV is between L3
and L4, or somewhere else?
Where exactly can on-demand protocols be in the protocol stack?

Young


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

Yahoo! India Mobile SMS using the Yahoo! Messenger; Download latest version. --0-224475774-1058247196=:94171-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 15 03:24:39 2003 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 DAA28494 for ; Tue, 15 Jul 2003 03:24:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cKAV-0002T4-Aq for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 03:24:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6F7OBEt009482 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 03:24:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cKAU-0002Sr-7J for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 03:24: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 DAA28479 for ; Tue, 15 Jul 2003 03:24:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cKAR-0004wG-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 03:24:08 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cKAR-0004wD-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 03:24:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cKAL-0002Om-R5; Tue, 15 Jul 2003 03:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cK9T-0002LB-4h for manet@optimus.ietf.org; Tue, 15 Jul 2003 03:23: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 DAA28446 for ; Tue, 15 Jul 2003 03:23:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cK9Q-0004vu-00 for manet@ietf.org; Tue, 15 Jul 2003 03:23:04 -0400 Received: from marfik.cc.upv.es ([158.42.2.61] helo=marfik.upv.es) by ietf-mx with esmtp (Exim 4.12) id 19cK9P-0004vr-00 for manet@ietf.org; Tue, 15 Jul 2003 03:23:04 -0400 Received: from pop.upv.es (maia.cc.upv.es [158.42.4.11]) by marfik.upv.es (8.11.6/8.11.6) with ESMTP id h6F7Mvx26044; Tue, 15 Jul 2003 09:22:57 +0200 Received: from mx2.upv.es (mx2.cc.upv.es [158.42.249.55]) by pop.upv.es (8.11.3/8.11.3) with ESMTP id h6F7Mvt16245; Tue, 15 Jul 2003 09:22:57 +0200 (METDST) Received: from nao.disca.upv.es (nao.disca.upv.es [158.42.53.70]) by mx2.upv.es (8.12.9/8.12.9) with ESMTP id h6F7OAoE032257; Tue, 15 Jul 2003 09:24:11 +0200 Received: from ieee.org (msanchez2.disca.upv.es [158.42.53.165]) by nao.disca.upv.es (Postfix on SuSE eMail Server 2.0) with ESMTP id E20741FE8B; Tue, 15 Jul 2003 09:22:40 +0200 (CEST) Message-ID: <3F13AC5C.9050504@ieee.org> Date: Tue, 15 Jul 2003 09:25:16 +0200 From: =?ISO-8859-1?Q?Miguel_S=E1nchez?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030626 X-Accept-Language: en-us, en MIME-Version: 1.0 To: #LI ZHIFEI# Cc: manet@ietf.org Subject: Re: [manet] how to detect the type of sensing range frame References: <3D565922795545468AE3E3DA2881BEA90186D88E@mail01.student.main.ntu.edu.sg> In-Reply-To: <3D565922795545468AE3E3DA2881BEA90186D88E@mail01.student.main.ntu.edu.sg> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by marfik.upv.es id h6F7Mvx26044 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 Li, While not sure you can get this info from the device driver, it seems that frame length analysis, when possible, it would allow you to learn if your interferer is sending RTS/CTS, data or ACK. However, if you have multiple interferers then this idea could not be applied. Best, Miguel S=E1nchez Polytechnic University of Valencia, Spain #LI ZHIFEI# wrote: >Hi, > >In the IEEE 802.11, when the sensing range (SR) is assumed to be greater= than the transmission range,=20 >is there any methods for a node that detects an SR frame to identify the= type (i.e., RTS/CTS/Data/ACK) of this frame? >Note that the node cannot interpret the content of the SR frame. > >Best regards=20 >Li ZhiFei=20 >PhD candidate, =20 >Center For Multimedia And Network Technology >School Of Computer Engineering >Nanyang Technological University >N4-b2c-08, Nanyang Avenue >Singapore 639798 >tel:(65)67906579=20 >website: =20 > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > =20 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 15 03:32:48 2003 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 DAA28807 for ; Tue, 15 Jul 2003 03:32:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cKIP-00030m-La for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 03:32:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6F7WLa4011566 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 03: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 19cKIP-00030T-Aa for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 03: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 DAA28760 for ; Tue, 15 Jul 2003 03:32:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cKIM-00051U-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 03:32:18 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cKID-00051K-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 03:32:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cKI5-0002ql-SU; Tue, 15 Jul 2003 03: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 19cKHa-0002pV-L9 for manet@optimus.ietf.org; Tue, 15 Jul 2003 03:31: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 DAA28678 for ; Tue, 15 Jul 2003 03:31:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cKHY-000509-00 for manet@ietf.org; Tue, 15 Jul 2003 03:31:28 -0400 Received: from mbox1.ntu.edu.sg ([155.69.5.171]) by ietf-mx with esmtp (Exim 4.12) id 19cKHX-0004zR-00 for manet@ietf.org; Tue, 15 Jul 2003 03:31:27 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mbox1.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Tue, 15 Jul 2003 15:29:47 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] how to detect the type of sensing range frame Date: Tue, 15 Jul 2003 15:29:47 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D8D4@mail01.student.main.ntu.edu.sg> Thread-Topic: [manet] how to detect the type of sensing range frame Thread-Index: AcNKofJQZWhspJAiRES3YJvP9MEujgAAE63w From: "#LI ZHIFEI#" To: =?iso-8859-1?Q?Miguel_S=E1nchez?= Cc: X-OriginalArrivalTime: 15 Jul 2003 07:29:47.0919 (UTC) FILETIME=[DEC621F0:01C34AA2] 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 Thank you for your response.=20 But I am still not clear about the method your mentioned (i.e., "frame = length analysis") . Could you please explain it more clearly or give me=20 some links/examples. We can simply assume that there is only one = interferer. Best regards Li zhifei -----Original Message----- From: Miguel S=A8=A2nchez [mailto:misan@ieee.org] Sent: dimarts, 15 / juliol / 2003 15:25 To: #LI ZHIFEI# Cc: manet@ietf.org Subject: Re: [manet] how to detect the type of sensing range frame Hi Li, While not sure you can get this info from the device driver, it seems that frame length analysis, when possible, it would allow you to learn if your interferer is sending RTS/CTS, data or ACK. However, if you have multiple interferers then this idea could not be applied. Best, Miguel S=E1nchez Polytechnic University of Valencia, Spain #LI ZHIFEI# wrote: >Hi, > >In the IEEE 802.11, when the sensing range (SR) is assumed to be = greater than the transmission range,=20 >is there any methods for a node that detects an SR frame to identify = the type (i.e., RTS/CTS/Data/ACK) of this frame? >Note that the node cannot interpret the content of the SR frame. > >Best regards=20 >Li ZhiFei=20 >PhD candidate, =20 >Center For Multimedia And Network Technology >School Of Computer Engineering >Nanyang Technological University >N4-b2c-08, Nanyang Avenue >Singapore 639798 >tel:(65)67906579=20 >website: =20 > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > =20 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 15 04:07:56 2003 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 EAA02320 for ; Tue, 15 Jul 2003 04:07:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cKqO-00058c-2B for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 04:07:30 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6F87Rcq019721 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 04:07:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cKqM-00057s-OR for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 04:07: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 EAA02255 for ; Tue, 15 Jul 2003 04:07:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cKqK-0005qg-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 04:07:24 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cKqJ-0005qd-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 04:07:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cKpy-0004t2-J9; Tue, 15 Jul 2003 04:07:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cKp5-0004lz-AO for manet@optimus.ietf.org; Tue, 15 Jul 2003 04:06: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 EAA02139 for ; Tue, 15 Jul 2003 04:06:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cKp2-0005p4-00 for manet@ietf.org; Tue, 15 Jul 2003 04:06:04 -0400 Received: from marfik.cc.upv.es ([158.42.2.61] helo=marfik.upv.es) by ietf-mx with esmtp (Exim 4.12) id 19cKp1-0005p0-00 for manet@ietf.org; Tue, 15 Jul 2003 04:06:03 -0400 Received: from pop.upv.es (maia.cc.upv.es [158.42.4.11]) by marfik.upv.es (8.11.6/8.11.6) with ESMTP id h6F85lx31538; Tue, 15 Jul 2003 10:05:47 +0200 Received: from mx2.upv.es (mx2.cc.upv.es [158.42.249.55]) by pop.upv.es (8.11.3/8.11.3) with ESMTP id h6F85kt00920; Tue, 15 Jul 2003 10:05:46 +0200 (METDST) Received: from nao.disca.upv.es (nao.disca.upv.es [158.42.53.70]) by mx2.upv.es (8.12.9/8.12.9) with ESMTP id h6F872oE013435; Tue, 15 Jul 2003 10:07:02 +0200 Received: from ieee.org (msanchez2.disca.upv.es [158.42.53.165]) by nao.disca.upv.es (Postfix on SuSE eMail Server 2.0) with ESMTP id 55F711FE8B; Tue, 15 Jul 2003 10:05:32 +0200 (CEST) Message-ID: <3F13B668.7000708@ieee.org> Date: Tue, 15 Jul 2003 10:08:08 +0200 From: =?ISO-8859-1?Q?Miguel_S=E1nchez?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030626 X-Accept-Language: en-us, en MIME-Version: 1.0 To: #LI ZHIFEI# Cc: =?ISO-8859-1?Q?Miguel_S=E1nchez?= , manet@ietf.org Subject: Re: [manet] how to detect the type of sensing range frame References: <3D565922795545468AE3E3DA2881BEA90186D8D4@mail01.student.main.ntu.edu.sg> In-Reply-To: <3D565922795545468AE3E3DA2881BEA90186D8D4@mail01.student.main.ntu.edu.sg> X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by marfik.upv.es id h6F85lx31538 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 Li, What I mean is that given that RTS, CTS, data and ACK frames have different frame lengths (only data has a variable size), then by looking at the length of the "interference you cannot receive as a frame" you could figure out what kind of frame caused it (even when you cannot successfully decode it). Regards, Miguel S=E1nchez #LI ZHIFEI# wrote: >Thank you for your response.=20 > >But I am still not clear about the method your mentioned (i.e., "frame l= ength analysis") . Could you please explain it more clearly or give me=20 >some links/examples. We can simply assume that there is only one interf= erer. > >Best regards > >Li zhifei > >-----Original Message----- >From: Miguel S=A8=A2nchez [mailto:misan@ieee.org] >Sent: dimarts, 15 / juliol / 2003 15:25 >To: #LI ZHIFEI# >Cc: manet@ietf.org >Subject: Re: [manet] how to detect the type of sensing range frame > > >Hi Li, > >While not sure you can get this info from the device driver, it seems >that frame length analysis, when possible, it would allow you to learn >if your interferer is sending RTS/CTS, data or ACK. > >However, if you have multiple interferers then this idea could not be >applied. > >Best, > >Miguel S=E1nchez >Polytechnic University of Valencia, Spain > >#LI ZHIFEI# wrote: > > =20 > >>Hi, >> >>In the IEEE 802.11, when the sensing range (SR) is assumed to be greate= r than the transmission range,=20 >>is there any methods for a node that detects an SR frame to identify th= e type (i.e., RTS/CTS/Data/ACK) of this frame? >>Note that the node cannot interpret the content of the SR frame. >> >>Best regards=20 >>Li ZhiFei=20 >>PhD candidate, =20 >>Center For Multimedia And Network Technology >>School Of Computer Engineering >>Nanyang Technological University >>N4-b2c-08, Nanyang Avenue >>Singapore 639798 >>tel:(65)67906579=20 >>website: =20 >> >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> >>=20 >> >> =20 >> > > > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > =20 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 15 04:22:46 2003 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 EAA03533 for ; Tue, 15 Jul 2003 04:22: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 19cL4m-00065d-1v for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 04:22:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6F8MKXi023403 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 04:22:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cL4l-00065O-TD for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 04: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 EAA03467 for ; Tue, 15 Jul 2003 04:22:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cL4j-0006Aa-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 04:22:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cL4i-0006AX-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 04:22:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cL4W-0005yt-Bt; Tue, 15 Jul 2003 04:22:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cL44-0005xz-Bg for manet@optimus.ietf.org; Tue, 15 Jul 2003 04:21: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 EAA03404 for ; Tue, 15 Jul 2003 04:21:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cL40-00069L-00 for manet@ietf.org; Tue, 15 Jul 2003 04:21:32 -0400 Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx with esmtp (Exim 4.12) id 19cL3z-00069I-00 for manet@ietf.org; Tue, 15 Jul 2003 04:21:31 -0400 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id h6F8KDB1008418; Tue, 15 Jul 2003 04:21:22 -0400 (EDT) Received: from bibbiena.ece.neu.edu ([129.10.60.216]) by calvin.ece.neu.edu (SAVSMTP 3.0.0.44) with SMTP id M2003071504212111533 ; Tue, 15 Jul 2003 04:21:21 -0400 Received: from localhost (basagni@localhost) by bibbiena.ece.neu.edu (8.11.6+Sun/8.9.3) with ESMTP id h6F8LLs24475; Tue, 15 Jul 2003 04:21:21 -0400 (EDT) X-Authentication-Warning: bibbiena.ece.neu.edu: basagni owned process doing -bs Date: Tue, 15 Jul 2003 04:21:21 -0400 (EDT) From: Stefano Basagni X-X-Sender: basagni@bibbiena To: Jack Wang cc: manet@ietf.org Subject: Re: [manet] location management In-Reply-To: <20030714164800.93E53299E8@xmxpita.excite.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 Jeck, you can also have a look to the following paper. Cheers, St. @inproceedings{ICC01, author = {Basagni, S. and Turgut, D. and Das, S. K.}, title = {Mobility-Adaptive Protocols for Managing Large Ad Hoc Networks}, booktitle = {Proceedings of the IEEE International Conference on Communications, ICC 2001}, volume = {5}, pages = {1539--1543}, address = {Helsinki, Finland}, month = {June 11--14}, year = {2001}, } -- Stefano Basagni, Ph.D. Assistant Professor of Computer Engineering Dept. of Electrical and Computer Engineering 312 Dana Research Center Northeastern University 360 Huntington Ave. Boston, MA 02115 Tel. 617 373 3061, Fax 617 373 8970 E-mail: basagni@ece.neu.edu *** http://www.ece.neu.edu/faculty/basagni/ *** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 15 04:28:50 2003 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 EAA04053 for ; Tue, 15 Jul 2003 04:28: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 19cLAa-0006fJ-1p for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 04:28:24 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6F8SKAJ025615 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 04:28:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cLAZ-0006f4-Se for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 04:28: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 EAA04017 for ; Tue, 15 Jul 2003 04:28:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cLAX-0006JO-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 04:28:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cLAW-0006JL-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 04:28:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cLAK-0006W4-Kn; Tue, 15 Jul 2003 04:28:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cL9k-0006Uz-Ig for manet@optimus.ietf.org; Tue, 15 Jul 2003 04:27: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 EAA03950 for ; Tue, 15 Jul 2003 04:27:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cL9h-0006Ic-00 for manet@ietf.org; Tue, 15 Jul 2003 04:27:25 -0400 Received: from mail11.ntu.edu.sg ([155.69.5.163]) by ietf-mx with esmtp (Exim 4.12) id 19cL9g-0006Hq-00 for manet@ietf.org; Tue, 15 Jul 2003 04:27:25 -0400 Received: from mail01.student.main.ntu.edu.sg ([155.69.5.165]) by mail11.ntu.edu.sg with Microsoft SMTPSVC(5.0.2195.5576); Tue, 15 Jul 2003 16:26:53 +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="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] how to detect the type of sensing range frame Date: Tue, 15 Jul 2003 16:26:53 +0800 Message-ID: <3D565922795545468AE3E3DA2881BEA90186D8D8@mail01.student.main.ntu.edu.sg> Thread-Topic: [manet] how to detect the type of sensing range frame Thread-Index: AcNKp/w0Z9mBPJGISwWF0eKMwCMrGAAAEnOQ From: "#LI ZHIFEI#" To: =?iso-8859-1?Q?Miguel_S=E1nchez?= Cc: X-OriginalArrivalTime: 15 Jul 2003 08:26:53.0938 (UTC) FILETIME=[D8D72520:01C34AAA] 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, Actually, I have used the method you mentioned in one of my papers. But = it may not be physically implemented. The reason is as follows: In the IEEE 802.11, when a node is in the sensing range of the = transmitter who is transmitting a frame (e.g., RTS), the node may not = even=20 correctly demodulate the PLCP header (physical layer), which includes = the information about the transmission rate and the MAC frame length.=20 Therefore, based on the length of time duration that the inteference is = keeping on, we cannot identify the frame type even though the length (in = bytes) of these frames are unique.=20 Do you find anybody else or any papers use this method? If yes, please = let me know, thank you very much. Best Regards Li zhifei=20 -----Original Message----- From: Miguel S=A8=A2nchez [mailto:misan@ieee.org] Sent: dimarts, 15 / juliol / 2003 16:08 To: #LI ZHIFEI# Cc: Miguel S=A8=A2nchez; manet@ietf.org Subject: Re: [manet] how to detect the type of sensing range frame Hi Li, What I mean is that given that RTS, CTS, data and ACK frames have different frame lengths (only data has a variable size), then by looking at the length of the "interference you cannot receive as a frame" you could figure out what kind of frame caused it (even when you cannot successfully decode it). Regards, Miguel S=E1nchez #LI ZHIFEI# wrote: >Thank you for your response.=20 > >But I am still not clear about the method your mentioned (i.e., "frame = length analysis") . Could you please explain it more clearly or give me=20 >some links/examples. We can simply assume that there is only one = interferer. > >Best regards > >Li zhifei > >-----Original Message----- >From: Miguel S=A8=A2nchez [mailto:misan@ieee.org] >Sent: dimarts, 15 / juliol / 2003 15:25 >To: #LI ZHIFEI# >Cc: manet@ietf.org >Subject: Re: [manet] how to detect the type of sensing range frame > > >Hi Li, > >While not sure you can get this info from the device driver, it seems >that frame length analysis, when possible, it would allow you to learn >if your interferer is sending RTS/CTS, data or ACK. > >However, if you have multiple interferers then this idea could not be >applied. > >Best, > >Miguel S=E1nchez >Polytechnic University of Valencia, Spain > >#LI ZHIFEI# wrote: > > =20 > >>Hi, >> >>In the IEEE 802.11, when the sensing range (SR) is assumed to be = greater than the transmission range,=20 >>is there any methods for a node that detects an SR frame to identify = the type (i.e., RTS/CTS/Data/ACK) of this frame? >>Note that the node cannot interpret the content of the SR frame. >> >>Best regards=20 >>Li ZhiFei=20 >>PhD candidate, =20 >>Center For Multimedia And Network Technology >>School Of Computer Engineering >>Nanyang Technological University >>N4-b2c-08, Nanyang Avenue >>Singapore 639798 >>tel:(65)67906579=20 >>website: =20 >> >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> >>=20 >> >> =20 >> > > > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > =20 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 15 06:13:28 2003 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 GAA12270 for ; Tue, 15 Jul 2003 06:13:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cMnv-0004vK-JK for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 06:13:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6FAD3Io018922 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 06:13:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cMnv-0004v7-GY for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 06:13: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 GAA12258 for ; Tue, 15 Jul 2003 06:12:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cMnm-0000JS-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 06:12:54 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cMnM-0000Ih-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 06:12:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cMk1-0004ay-Ng; Tue, 15 Jul 2003 06:09:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cMj4-0004Zf-4E for manet@optimus.ietf.org; Tue, 15 Jul 2003 06: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 GAA12132 for ; Tue, 15 Jul 2003 06:07:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cMiu-0000IV-00 for manet@ietf.org; Tue, 15 Jul 2003 06:07:52 -0400 Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81]) by ietf-mx with esmtp (Exim 4.12) id 19cMiU-0000I1-00 for manet@ietf.org; Tue, 15 Jul 2003 06:07:26 -0400 Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5] helo=irams1.ira.uka.de) by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10 (Debian)) id 19cMe1-0003p2-00; Tue, 15 Jul 2003 12:02:49 +0200 Received: from i72tribble.tm.uni-karlsruhe.de ([141.3.70.72] helo=tribble ident=weniger) by irams1.ira.uka.de with esmtp (Exim 3.30 #7 (Debian)) id 19cMe1-0003UV-00; Tue, 15 Jul 2003 12:02:49 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Kilian Weniger Organization: University of Karlsruhe To: "Jaehoon Jeong" Subject: Re: [manet] Ad Hoc IP Address Autoconfiguration Date: Tue, 15 Jul 2003 12:02:49 +0200 User-Agent: KMail/1.4.3 References: <9E664A0522ABD711827B00D0B7A8AC4A373891@cms3.etri.re.kr> <20030707183238.299531ae.jean-marie.orset@int-evry.fr> <001701c3452f$c67dd2a0$c470fe81@etri.re.kr> In-Reply-To: <001701c3452f$c67dd2a0$c470fe81@etri.re.kr> Cc: "MANET WG" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200307151202.49110.weniger@tm.uka.de> 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 Jaehoon, we are also working on Duplicate Address Detection in mobile ad hoc netwo= rks.=20 In our approach, which is called "Passive Duplicate Address Detection" (P= DAD)=20 and which was presented at IEEE WCNC, New Orleans, March 2003 (K.Weniger,= =20 "Passive Duplicate Address Detection in Mobile Ad Hoc Networks"), all nod= es=20 continuously monitor the routing protocol traffic and seeks for anomalies= in=20 order to find duplicate addresses in the network. Thus, PDAD supports net= work=20 partitioning and merging as Weak DAD does. One advantage of our approach is, that it does not consume any additional= =20 protocol overhead (as WDAD does: one keys for each address). Another=20 advantage is, that the routing protocol message format does not need to b= e=20 modified (as it is for WDAD). Thus, it is even possible to use existing=20 routing protocol implementations, e.g. by implementing PDAD as a linux=20 netfilter module (we are currently working on that). We have done detailed simulations using PDAD with FSR and OLSR. For each = of=20 these protocols, a combination of schemes was able to resolve all conflic= ts.=20 The results will be published soon. Since the publication mentioned above= =20 only discusses proactive link state routing protocols, support for reacti= ve=20 routing protocols is another issue we are currently working on. Summarizing, PDAD could also be an option for your draft, in addition or = as an=20 alternative to WDAD. Regards, Kilian Weniger Am Dienstag, 8. Juli 2003 11:03 schrieb Jaehoon Jeong: > Hi, Jean-Marie. >=20 > ----- Original Message -----=20 > From: "Jean-Marie ORSET" > To: "Jaehoon Jeong" > Sent: Tuesday, July 08, 2003 1:32 AM > Subject: Re: [Re] [manet] Re: Ad Hoc IP Address Autoconfiguration >=20 >=20 > > >=20 > > Le Sat, 5 Jul 2003 09:59:53 +0900 > > Jaehoon Jeong a =E9crit: > >=20 > > > > > I agree with you that the public cryptography is very expensive, > > > especially in MANET.=0D In my scheme, a key is used for identifying= the > > > address duplication. So, key's uniqueness is important. > > > In order to guarantee the uniqueness of public key,=20 > > > We should use a certificate for a public key? > > > How about? > > > >=20 > > Yes, a certificate seems to be essential while using public key > > cryptography.=0D In fact, the problem is who will be used to certific= ate > > the key, since we can not emply centralized certification authotity? = Zhou > > and Haas did write a very good paper on the distribution of trust in > > Manet. The schemes could be used complementary. > >=20 > Could you tell me the URL of the paper? >=20 > > > However, even if it is important to guarantee the non address > > duplication=0D I'm not sure public key cryptography could be used to = sign > > each packet.=20 > > That will need more discussion, I think. > Anyway, I hope this manet wg meeting starts to discuss ad hoc addre= ss > autoconfiguration.=0D Thanks. >=20 > /Jaehoon >=20 > > > Cordially, Jean-Marie Orset --=20 Dipl.-Ing. Kilian Weniger=09 Institute of Telematics, Universitaet Karlsruhe (TH) Zirkel 2, 76128 Karlsruhe, Germany Phone: +49 721 608 6415, Fax: +49 721 388097 Email: weniger@tm.uka.de, HP: http://www.tm.uka.de/~weniger _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 15 06:27:29 2003 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 GAA12918 for ; Tue, 15 Jul 2003 06:27:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cN1T-0005dF-Mz for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 06:27:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6FAR3Ln021643 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 06:27:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cN1S-0005d0-TW for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 06:27:02 -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 GAA12879 for ; Tue, 15 Jul 2003 06:26:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cN0V-0005PE-Db; Tue, 15 Jul 2003 06:26:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cN0D-0005OJ-0O for manet@optimus.ietf.org; Tue, 15 Jul 2003 06:25: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 GAA12789 for ; Tue, 15 Jul 2003 06:25:38 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cN03-0000QM-00 for manet@ietf.org; Tue, 15 Jul 2003 06:25:35 -0400 Received: from venus.uos.ac.kr ([210.125.183.202]) by ietf-mx with esmtp (Exim 4.12) id 19cMzV-0000Ph-00 for manet@ietf.org; Tue, 15 Jul 2003 06:25:01 -0400 Received: from aodv2 ([203.249.110.191]) by venus.uos.ac.kr (8.12.3/8.12.3/Debian -4) with ESMTP id h6FANSM7003042; Tue, 15 Jul 2003 19:23:28 +0900 From: "Youngmin Kim" To: "'Ash Mohammad Abbas'" , "Manet" Subject: RE: [manet] Where to put on-demand routing protocol Date: Tue, 15 Jul 2003 19:23:29 +0900 Message-ID: <000001c34abb$2296e500$bf6ef9cb@aodv2> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C34B06.927E8D00" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <20030715053316.96141.qmail@web8107.mail.in.yahoo.com> 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_01C34B06.927E8D00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I know that forwarding is separated from routing in wired network. Then.. why is not so in adhoc network? Thanks.. -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Ash Mohammad Abbas Sent: Tuesday, July 15, 2003 2:33 PM To: Young-Jun Lee; manet@ietf.org Subject: Re: [manet] Where to put on-demand routing protocol Sir, Irrespective of the fact that a protocol is on-demand or pro-active, a routing protocol will remain layer-3( Network Layer of OSI model) protocol. After a route has been established, ofcourse, the protocol might be used to send data packets. With best regards, Ash Mohammad Abbas http://www.cse.iitd.ernet.in/~abbas Young-Jun Lee <gte393q@mail.gatech.edu> wrote: All, In the INFOCOM paper 'Performance comparison of two on-demand routing protocols for ad hoc networks' (S. Das, C. Perkins, and E. Royer), the simulation model section says "The routing model sees all data packets transmitted or forwarded, and responds by invoking routing activities as appropriate". Does it mean that on-demand routing protocol like AODV is between L3 and L4, or somewhere else? Where exactly can on-demand protocols be in the protocol stack? Young _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet Yahoo! India Mobile SMS using the Yahoo! Messenger; Download latest version. ------=_NextPart_000_0001_01C34B06.927E8D00 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I know that forwarding is = separated from routing in wired network.

Then.. why is not so in adhoc network? =

 

Thanks..

 

 

-----Original Message-----
From: = manet-admin@ietf.org [mailto:manet-admin@ietf.org] On = Behalf Of Ash Mohammad Abbas
Sent: = Tuesday, July 15, = 2003 2:33 = PM
To: Young-Jun Lee; = manet@ietf.org
Subject: Re: [manet] = Where to put on-demand routing protocol

 

Sir,

Irrespective of the fact that a protocol is on-demand or pro-active, a routing = protocol will remain layer-3( Network Layer of OSI model) protocol. After a route has = been established, ofcourse, the protocol might be used to send data = packets.

With best regards,

Ash Mohammad Abbas

http://www.cse.iitd.ernet.in= /~abbas

  Young-Jun Lee &lt;gte393q@mail.gatech.edu&gt; wrote: =

All,

In the INFOCOM paper 'Performance comparison of two on-demand = routing
protocols for ad hoc networks' (S. Das, C. Perkins, and E. = Royer),
the simulation model section says

"The routing model sees all data packets transmitted or forwarded, = and
responds by invoking routing activities as appropriate".

Does it mean that on-demand routing protocol like AODV is between L3
and L4, or somewhere else?
Where exactly can on-demand protocols be in the protocol stack?

Young


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

3D"Yahoo!SMS = using the Yahoo! Messenger; Download latest = version.

------=_NextPart_000_0001_01C34B06.927E8D00-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 15 08:38:25 2003 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 IAA16422 for ; Tue, 15 Jul 2003 08:38:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cP4A-0003TV-Eq for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 08:37:58 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6FCbwwu013353 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 08:37:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cP4A-0003TH-BV for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 08: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 IAA16405 for ; Tue, 15 Jul 2003 08:37:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cP44-0001VH-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 08:37:52 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cP3e-0001V6-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 08:37:26 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cP3F-00039c-6F; Tue, 15 Jul 2003 08:37:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cP2o-00037O-4d for manet@optimus.ietf.org; Tue, 15 Jul 2003 08:36: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 IAA16367 for ; Tue, 15 Jul 2003 08:36:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cP2h-0001UX-00 for manet@ietf.org; Tue, 15 Jul 2003 08:36:27 -0400 Received: from web10002.mail.yahoo.com ([216.136.130.38]) by ietf-mx with smtp (Exim 4.12) id 19cP2G-0001UN-00 for manet@ietf.org; Tue, 15 Jul 2003 08:36:00 -0400 Message-ID: <20030715123530.29196.qmail@web10002.mail.yahoo.com> Received: from [81.160.243.20] by web10002.mail.yahoo.com via HTTP; Tue, 15 Jul 2003 05:35:30 PDT Date: Tue, 15 Jul 2003 05:35:30 -0700 (PDT) From: Jaehoon Jeong Subject: Re: [manet] Ad Hoc IP Address Autoconfiguration To: Kilian Weniger Cc: MANET WG In-Reply-To: <200307151202.49110.weniger@tm.uka.de> 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 Kilian, I welcome your suggestion. Would you show me the link of your paper? After reading your paper, I am going to think over how to include your idea in my draft. In tomorrow manet meeting, the most important is that Ad Hoc IP Addressing should be selected as a new manet item. I only reinitiates the issue after Charlie. I need many comments from manet guys including you and Charlie. I would like to make a good ad hoc address autoconfiguration scheme with others. Thanks. /Jaehoon Paul --- Kilian Weniger wrote: > Hi Jaehoon, > > we are also working on Duplicate Address Detection > in mobile ad hoc networks. > > In our approach, which is called "Passive Duplicate > Address Detection" (PDAD) > and which was presented at IEEE WCNC, New Orleans, > March 2003 (K.Weniger, > "Passive Duplicate Address Detection in Mobile Ad > Hoc Networks"), all nodes > continuously monitor the routing protocol traffic > and seeks for anomalies in > order to find duplicate addresses in the network. > Thus, PDAD supports network > partitioning and merging as Weak DAD does. > > One advantage of our approach is, that it does not > consume any additional > protocol overhead (as WDAD does: one keys for each > address). Another > advantage is, that the routing protocol message > format does not need to be > modified (as it is for WDAD). Thus, it is even > possible to use existing > routing protocol implementations, e.g. by > implementing PDAD as a linux > netfilter module (we are currently working on that). > > We have done detailed simulations using PDAD with > FSR and OLSR. For each of > these protocols, a combination of schemes was able > to resolve all conflicts. > The results will be published soon. Since the > publication mentioned above > only discusses proactive link state routing > protocols, support for reactive > routing protocols is another issue we are currently > working on. > > Summarizing, PDAD could also be an option for your > draft, in addition or as an > alternative to WDAD. > > > Regards, > > Kilian Weniger > > > Am Dienstag, 8. Juli 2003 11:03 schrieb Jaehoon > Jeong: > > Hi, Jean-Marie. > > > > ----- Original Message ----- > > From: "Jean-Marie ORSET" > > > To: "Jaehoon Jeong" > > Sent: Tuesday, July 08, 2003 1:32 AM > > Subject: Re: [Re] [manet] Re: Ad Hoc IP Address > Autoconfiguration > > > > > > > > > > > > Le Sat, 5 Jul 2003 09:59:53 +0900 > > > Jaehoon Jeong a ?rit: > > > > > > > > > > I agree with you that the public cryptography > is very expensive, > > > > especially in MANET. In my scheme, a key is > used for identifying the > > > > address duplication. So, key's uniqueness is > important. > > > > In order to guarantee the uniqueness of public > key, > > > > We should use a certificate for a public key? > > > > How about? > > > > > > > > > Yes, a certificate seems to be essential while > using public key > > > cryptography. In fact, the problem is who will > be used to certificate > > > the key, since we can not emply centralized > certification authotity? Zhou > > > and Haas did write a very good paper on the > distribution of trust in > > > Manet. The schemes could be used complementary. > > > > > > Could you tell me the URL of the paper? > > > > > > > However, even if it is important to guarantee > the non address > > > duplication I'm not sure public key > cryptography could be used to sign > > > each packet. > > > > That will need more discussion, I think. > > Anyway, I hope this manet wg meeting starts to > discuss ad hoc address > > autoconfiguration. Thanks. > > > > /Jaehoon > > > > > > > Cordially, Jean-Marie Orset > > -- > Dipl.-Ing. Kilian Weniger > Institute of Telematics, Universitaet Karlsruhe (TH) > Zirkel 2, 76128 Karlsruhe, Germany > Phone: +49 721 608 6415, Fax: +49 721 388097 > Email: weniger@tm.uka.de, HP: > http://www.tm.uka.de/~weniger > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet __________________________________ 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 Jul 15 09:44:08 2003 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 JAA18357 for ; Tue, 15 Jul 2003 09:44:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQ5m-0006jh-4d for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 09:43:42 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6FDhgrT025887 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 09:43:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQ5l-0006jS-Vl for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 09:43:41 -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 JAA18342 for ; Tue, 15 Jul 2003 09:43:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQ57-0006Xv-RS; Tue, 15 Jul 2003 09:43:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQ4d-0006XE-5s for manet@optimus.ietf.org; Tue, 15 Jul 2003 09:42: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 JAA18324 for ; Tue, 15 Jul 2003 09:42:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cQ4b-00020C-00 for manet@ietf.org; Tue, 15 Jul 2003 09:42:29 -0400 Received: from web10002.mail.yahoo.com ([216.136.130.38]) by ietf-mx with smtp (Exim 4.12) id 19cQ4P-0001zP-00 for manet@ietf.org; Tue, 15 Jul 2003 09:42:18 -0400 Message-ID: <20030715134046.44708.qmail@web10002.mail.yahoo.com> Received: from [81.160.98.35] by web10002.mail.yahoo.com via HTTP; Tue, 15 Jul 2003 06:40:46 PDT Date: Tue, 15 Jul 2003 06:40:46 -0700 (PDT) From: Jaehoon Jeong To: jean-marie.orset@int-evry.fr Cc: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] Re: [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: , Hi Jean-Marie, >Hi Jaehoon. >Forgive me to still disturb you but there is >something that I don't understand in your draft. That's ok. :-) >At page 8, step (f), you propose the node which >receives a routing packet whose virtual address >are the same that in its cache, send an AERR message. >However, i don't understand how they could be >different. You are right. The sentence should be corrected as follows; whose virtual address are the same that in its cache -> ^^^^^^^^^^^^^^^ ~ IP address are the same ~ >If a node send a packet to another. The intermediary >nodes will write its adress in their cache or routing >table. If the node sends some packet again to the >same node, intermediary nodes will have to forward >packets with the same virtual adress as in their >table since it is the same node which did send them. > According to the above modification, I think, your wonder can be solved. Is there something missing? /Jaehoon Paul (Paul is my baptismal name :-) >Could you please explain me? > >Cordially, jean-Marie Orset > __________________________________ 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 Jul 15 10:25:07 2003 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 KAA21382 for ; Tue, 15 Jul 2003 10:25:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQjN-0000O4-Tf for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 10:24:42 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6FEObe0001487 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 10:24:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQjN-0000Nu-OU for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 10:24: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 KAA21353 for ; Tue, 15 Jul 2003 10:24:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQin-0000BX-B0; Tue, 15 Jul 2003 10:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cQhv-000064-4P for manet@optimus.ietf.org; Tue, 15 Jul 2003 10:23: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 KAA21285 for ; Tue, 15 Jul 2003 10:23:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cQhs-0002No-00 for manet@ietf.org; Tue, 15 Jul 2003 10:23:04 -0400 Received: from web10005.mail.yahoo.com ([216.136.130.41]) by ietf-mx with smtp (Exim 4.12) id 19cQhh-0002Nb-00 for manet@ietf.org; Tue, 15 Jul 2003 10:22:54 -0400 Message-ID: <20030715141553.21211.qmail@web10005.mail.yahoo.com> Received: from [81.160.98.35] by web10005.mail.yahoo.com via HTTP; Tue, 15 Jul 2003 07:15:53 PDT Date: Tue, 15 Jul 2003 07:15:53 -0700 (PDT) From: Jaehoon Jeong Subject: Re: [manet] Ad Hoc IP Address Autoconfiguration To: Kilian Weniger Cc: manet@ietf.org In-Reply-To: <200307151457.08221.weniger@tm.uka.de> 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: , Thanks. /Jaehoon --- Kilian Weniger wrote: > Hi Jaehoon, > > you can find the paper at > > http://www.tm.uka.de/~weniger/passive_dad_lsr_wcnc03.pdf > > > Regards, > > Kilian Weniger > > > Am Dienstag, 15. Juli 2003 14:35 schrieb Jaehoon > Jeong: > > Hi Kilian, > > I welcome your suggestion. > > Would you show me the link of your paper? > > After reading your paper, I am going to think over > how > > to include your idea in my draft. > > In tomorrow manet meeting, the most important is > that > > Ad Hoc IP Addressing should be selected as a new > manet > > item. I only reinitiates the issue after Charlie. > I > > need many comments from manet guys including you > and > > Charlie. > > I would like to make a good ad hoc address > > autoconfiguration scheme with others. > > Thanks. > > > > /Jaehoon Paul > > > > --- Kilian Weniger wrote: > > > Hi Jaehoon, > > > > > > we are also working on Duplicate Address > Detection > > > in mobile ad hoc networks. > > > > > > In our approach, which is called "Passive > Duplicate > > > Address Detection" (PDAD) > > > and which was presented at IEEE WCNC, New > Orleans, > > > March 2003 (K.Weniger, > > > "Passive Duplicate Address Detection in Mobile > Ad > > > Hoc Networks"), all nodes > > > continuously monitor the routing protocol > traffic > > > and seeks for anomalies in > > > order to find duplicate addresses in the > network. > > > Thus, PDAD supports network > > > partitioning and merging as Weak DAD does. > > > > > > One advantage of our approach is, that it does > not > > > consume any additional > > > protocol overhead (as WDAD does: one keys for > each > > > address). Another > > > advantage is, that the routing protocol message > > > format does not need to be > > > modified (as it is for WDAD). Thus, it is even > > > possible to use existing > > > routing protocol implementations, e.g. by > > > implementing PDAD as a linux > > > netfilter module (we are currently working on > that). > > > > > > We have done detailed simulations using PDAD > with > > > FSR and OLSR. For each of > > > these protocols, a combination of schemes was > able > > > to resolve all conflicts. > > > The results will be published soon. Since the > > > publication mentioned above > > > only discusses proactive link state routing > > > protocols, support for reactive > > > routing protocols is another issue we are > currently > > > working on. > > > > > > Summarizing, PDAD could also be an option for > your > > > draft, in addition or as an > > > alternative to WDAD. > > > > > > > > > Regards, > > > > > > Kilian Weniger > > > > > > > > > Am Dienstag, 8. Juli 2003 11:03 schrieb Jaehoon > > > > > > Jeong: > > > > Hi, Jean-Marie. > > > > > > > > ----- Original Message ----- > > > > From: "Jean-Marie ORSET" > > > > > > > > > > > > > To: "Jaehoon Jeong" > > > > Sent: Tuesday, July 08, 2003 1:32 AM > > > > Subject: Re: [Re] [manet] Re: Ad Hoc IP > Address > > > > > > Autoconfiguration > > > > > > > > Le Sat, 5 Jul 2003 09:59:53 +0900 > > > > > > > > > > Jaehoon Jeong a ?rit: > > > > > > I agree with you that the public > cryptography > > > > > > is very expensive, > > > > > > > > > especially in MANET. > > > > In my scheme, a key is > > > > > used for identifying the > > > > > > > > > address duplication. So, key's uniqueness > is > > > > > > important. > > > > > > > > > In order to guarantee the uniqueness of > public > > > > > > key, > > > > > > > > > We should use a certificate for a public > key? > > > > > > How about? > > > > > > > > > > Yes, a certificate seems to be essential > while > > > > > > using public key > > > > > > > > cryptography. > > > > In fact, the problem is who will > > > > > be used to certificate > > > > > > > > the key, since we can not emply centralized > > > > > > certification authotity? Zhou > > > > > > > > and Haas did write a very good paper on the > > > > > > distribution of trust in > > > > > > > > Manet. The schemes could be used > complementary. > > > > > > > > Could you tell me the URL of the paper? > > > > > > > > > However, even if it is important to > guarantee > > > > > > the non address > > > > > > > > duplication > > > > I'm not sure public key > > > > > cryptography could be used to sign > > > > > > > > each packet. > > > > > > > > That will need more discussion, I think. > > > > Anyway, I hope this manet wg meeting > starts to > > > > > > discuss ad hoc address > > > > > > > autoconfiguration. > > > > Thanks. > > > > > > /Jaehoon > > > > > > > > > Cordially, Jean-Marie Orset > > > > > > -- > > > Dipl.-Ing. Kilian Weniger > > > Institute of Telematics, Universitaet Karlsruhe > (TH) > > > Zirkel 2, 76128 Karlsruhe, Germany > > > Phone: +49 721 608 6415, Fax: +49 721 388097 > === message truncated === __________________________________ 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 Jul 15 11:13:49 2003 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 LAA23573 for ; Tue, 15 Jul 2003 11:13:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRUY-00030I-8F for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 11:13:23 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6FFDMT0011540 for manet-archive@odin.ietf.org; Tue, 15 Jul 2003 11:13:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRUY-000303-3q for manet-web-archive@optimus.ietf.org; Tue, 15 Jul 2003 11:13: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 LAA23567 for ; Tue, 15 Jul 2003 11:13:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cRUU-0002nM-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 11:13:18 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cRUO-0002nJ-00 for manet-web-archive@ietf.org; Tue, 15 Jul 2003 11:13:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRUC-0002wG-FE; Tue, 15 Jul 2003 11:13:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cRTg-0002s0-V9 for manet@optimus.ietf.org; Tue, 15 Jul 2003 11:12: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 LAA23541 for ; Tue, 15 Jul 2003 11:12:24 -0400 (EDT) From: jm.orset@free.fr Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cRTg-0002mx-00 for manet@ietf.org; Tue, 15 Jul 2003 11:12:28 -0400 Received: from postfix3-1.free.fr ([213.228.0.44]) by ietf-mx with esmtp (Exim 4.12) id 19cRSS-0002ml-00 for manet@ietf.org; Tue, 15 Jul 2003 11:11:12 -0400 Received: from imptest1-2.proxad.net (impt1-2.free.fr [213.228.0.144]) by postfix3-1.free.fr (Postfix) with ESMTP id ADF23C272 for ; Tue, 15 Jul 2003 17:10:10 +0200 (CEST) Received: by imptest1-2.proxad.net (Postfix, from userid 33) id A2D55BD8C; Tue, 15 Jul 2003 17:10:10 +0200 (MEST) Received: from 157.159.100.240 ([157.159.100.240]) by impt1-2.free.fr (IMP) with HTTP for ; Tue, 15 Jul 2003 17:10:10 +0200 Message-ID: <1058281810.3f14195285f2a@impt1-2.free.fr> Date: Tue, 15 Jul 2003 17:10:10 +0200 To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 User-Agent: Internet Messaging Program (IMP) 3.2.1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA23542 Subject: [manet] (no subject) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Le Tue, 15 Jul 2003 06:40:46 -0700 (PDT) Jaehoon Jeong a =E9crit: > You are right. The sentence should be corrected as > follows; > whose virtual address are the same that in its cache > -> ^^^^^^^^^^^^^^^ > ~ IP address are the same ~ > =20 Yes! But in this case, I have still a problem. Let suppose a node leaves sudently the network. Its IP address can be re-aloted to another node. However the key this nod= e will choose will probably be different from the key that will be associated with its address in routing table of= other nodes, because those routing table or cache will not have been updated si= nce the node is not aware of the re-alocation of the adress. Consequently, if a node leaves the network sudently, I think its address = can not be re-used. Is this right? Thank you for your preceding answer. Cordially, Jean-Marie Orset _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 16 00:51:55 2003 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 AAA17286 for ; Wed, 16 Jul 2003 00:51:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ceGI-0004q7-I6 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 00:51:30 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6G4pU3G018600 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 00:51:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ceGI-0004pv-CR for manet-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 00:51: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 AAA17277 for ; Wed, 16 Jul 2003 00:51:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ceGF-0002Hz-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 00:51:27 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ceGA-0002Hs-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 00:51:22 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ceFq-0004jl-Cv; Wed, 16 Jul 2003 00:51:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ceFI-0004jS-C5 for manet@optimus.ietf.org; Wed, 16 Jul 2003 00:50: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 AAA17247 for ; Wed, 16 Jul 2003 00:50:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ceFF-0002Go-00 for manet@ietf.org; Wed, 16 Jul 2003 00:50:25 -0400 Received: from web8103.mail.in.yahoo.com ([203.199.70.30]) by ietf-mx with smtp (Exim 4.12) id 19ceF4-0002GA-00 for manet@ietf.org; Wed, 16 Jul 2003 00:50:14 -0400 Message-ID: <20030716044923.22861.qmail@web8103.mail.in.yahoo.com> Received: from [202.141.69.66] by web8103.mail.in.yahoo.com via HTTP; Wed, 16 Jul 2003 05:49:23 BST Date: Wed, 16 Jul 2003 05:49:23 +0100 (BST) From: =?iso-8859-1?q?Ash=20Mohammad=20Abbas?= Subject: Re: [manet] (no subject) To: jm.orset@free.fr, manet@ietf.org In-Reply-To: <1058281810.3f14195285f2a@impt1-2.free.fr> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1403018692-1058330963=:22829" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-1403018692-1058330963=:22829 Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id AAA17248 Content-Transfer-Encoding: quoted-printable If a node leaves suddenly, we should not worry about the reuse of its IP = address. The incoming node should be assignrd an IP address, which is not= currenly in use by other (remaining) active nodes. Let the incoming node= chhose a different key ( or the same key which is left by the leaving no= de ). This will be a simpler solution. I aggree that some of the IP addre= sses may not be used. Can we not have number of IP addresses more than nu= mber of participating nodes. If not in IPv4, then IPv6 addresses ( there = is a huge amount of addresses ). Wish you best, Ash Mohammad Abbas http://www.cse.iitd.ernet.in/~abbas=20 jm.orset@free.fr wrote: Le Tue, 15 Jul 2003 06:40:46 -0700 (PDT) Jaehoon Jeong a =E9crit: > You are right. The sentence should be corrected as > follows; > whose virtual address are the same that in its cache > -> ^^^^^^^^^^^^^^^ > ~ IP address are the same ~ >=20 Yes! But in this case, I have still a problem. Let suppose a node leaves sudently the network. Its IP address can be re-aloted to another node. However the key this nod= e will choose will probably be different from the key that will be associated with its address in routing table of= other nodes, because those routing table or cache will not have been updated si= nce the node is not aware of the re-alocation of the adress. Consequently, if a node leaves the network sudently, I think its address = can not be re-used. Is this right? Thank you for your preceding answer. Cordially, Jean-Marie Orset _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet SMS using the Yahoo! Messenger;Download latest version. --0-1403018692-1058330963=:22829 Content-Type: text/html; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id AAA17248 Content-Transfer-Encoding: quoted-printable
If a node leaves suddenly, we should not worry about the reuse of it= s IP address. The incoming node should be assignrd an IP address, which i= s not currenly in use by other (remaining) active nodes. Let the incoming= node chhose a different key ( or the same key which is left by the leavi= ng node ). This will be a simpler solution. I aggree that some of&nb= sp;the IP addresses may not be used. Can we not have numbe= r of IP addresses more than number of participating nodes. If not in IPv4= , then IPv6 addresses ( there is a huge amount of addresses ).
Wish you best,
Ash Mohammad Abbas
http://www.cse.iitd.= ernet.in/~abbas 

jm.orset@free.fr wrote:


Le Tue, 15 Jul 2003 06:40:46 -0700 = (PDT)
Jaehoon Jeong a =E9crit:

> You are right. The sentence= should be corrected as
> follows;
> whose virtual address ar= e the same that in its cache
> -> ^^^^^^^^^^^^^^^
> ~ IP a= ddress are the same ~
>

Yes! But in this case, I have still= a problem. Let suppose a node leaves
sudently the network.
Its IP = address can be re-aloted to another node. However the key this node will<= BR>choose will probably be different
from the key that will be associa= ted with its address in routing table of other
nodes, because those ro= uting table or cache will not have been updated since the
node is not = aware of the re-alocation of the adress.
Consequently, if a node leave= s the network sudently, I think its address can not
be re-used.
Is this right?
Thank you for your preceding answer.

Cordially, Jean-Marie Orset

______________________= _________________________
manet mailing list
manet@ietf.org
http= s://www1.ietf.org/mailman/listinfo/manet

3D"Yahoo! SMS using the Yahoo!=20 Messenger; Download latest versio= n. --0-1403018692-1058330963=:22829-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 16 01:44:52 2003 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 BAA18970 for ; Wed, 16 Jul 2003 01:44: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 19cf5V-0007Mu-LZ for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 01:44:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6G5iPOf028318 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 01:44:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cf5U-0007Mf-S0 for manet-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 01:44: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 BAA18959 for ; Wed, 16 Jul 2003 01:44:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cf5R-0002zs-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 01:44:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cf5L-0002zp-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 01:44:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cf57-0007Lb-S7; Wed, 16 Jul 2003 01:44:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cf4S-0007Kq-8z for manet@optimus.ietf.org; Wed, 16 Jul 2003 01:43: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 BAA18924 for ; Wed, 16 Jul 2003 01:43:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cf4P-0002xK-00 for manet@ietf.org; Wed, 16 Jul 2003 01:43:17 -0400 Received: from venus.uos.ac.kr ([210.125.183.202]) by ietf-mx with esmtp (Exim 4.12) id 19cf42-0002wQ-00 for manet@ietf.org; Wed, 16 Jul 2003 01:42:54 -0400 Received: from aodv2 ([203.249.110.191]) by venus.uos.ac.kr (8.12.3/8.12.3/Debian -4) with ESMTP id h6G5ekM7007598; Wed, 16 Jul 2003 14:40:47 +0900 From: "Youngmin Kim" To: "'Ash Mohammad Abbas'" , "Manet" Subject: RE: [manet] Where to put on-demand routing protocol Date: Wed, 16 Jul 2003 14:40:48 +0900 Message-ID: <000401c34b5c$cfe74320$bf6ef9cb@aodv2> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C34BA8.3FCEEB20" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <20030716043448.49427.qmail@web8104.in.yahoo.com> 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_0005_01C34BA8.3FCEEB20 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit My question was not accuracy!! Forwarding : forwarding to next hop, to send packets for destination, Routing ==> Routing protocol : making a routing table I know that forwarding is separated from routing protocol in wired network. Then.. why is not so in adhoc network? Thanks.. -----Original Message----- From: Ash Mohammad Abbas [mailto:abbas_iitd2001@yahoo.co.in] Sent: Wednesday, July 16, 2003 1:35 PM To: Youngmin Kim Cc: manet-admin@ietf.org Subject: RE: [manet] Where to put on-demand routing protocol Exactly! In ad hoc networks, there is a different scenario. In wired networks there are separate nodes for forwarding, which are called routers as opposed to ad hoc environment in which the participating nodes have agreed to forward the packets of other nodes. In other words, every participating node double as routers. Therfore, there is no separate forwarding in ad hoc networks. Youngmin Kim wrote: I know that forwarding is separated from routing in wired network. Then.. why is not so in adhoc network? Thanks.. -----Original Message----- From: manet-admin@ietf.org [mailto:manet-admin@ietf.org] On Behalf Of Ash Mohammad Abbas Sent: Tuesday, July 15, 2003 2:33 PM To: Young-Jun Lee; manet@ietf.org Subject: Re: [manet] Where to put on-demand routing protocol Sir, Irrespective of the fact that a protocol is on-demand or pro-active, a routing protocol will remain layer-3( Network Layer of OSI model) protocol. After a route has been established, ofcourse, the protocol might be used to send data packets. With best regards, Ash Mohammad Abbas http://www.cse.iitd.ernet.in/~abbas Young-Jun Lee <gte393q@mail.gatech.edu> wrote: All, In the INFOCOM paper 'Performance comparison of two on-demand routing protocols for ad hoc networks' (S. Das, C. Perkins, and E. Royer), the simulation model section says "The routing model sees all data packets transmitted or forwarded, and responds by invoking routing activities as appropriate". Does it mean that on-demand routing protocol like AODV is between L3 and L4, or somewhere else? Where exactly can on-demand protocols be in the protocol stack? Young _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet Yahoo! India Mobile SMS using the Yahoo! Messenger; Download latest version. Yahoo! India Mobile SMS using the Yahoo! Messenger; Download latest version. ------=_NextPart_000_0005_01C34BA8.3FCEEB20 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

My question was not = accuracy!!

 

Forwarding = : forwarding to next hop, to send packets for destination, =

Routing è Routing protocol : making a = routing table

 

 

I know that forwarding<= /b> is separated from routing protocol in wired = network.

Then.. why is not so in adhoc network? =

 

 

Thanks..

 

 

-----Original Message-----
From: Ash Mohammad Abbas [mailto:abbas_iitd2001@yahoo.co.in]
Sent: Wednesday, July 16, = 2003 1:35 = PM
To: Youngmin Kim
Cc: = manet-admin@ietf.org
Subject: RE: [manet] Where to put on-demand routing protocol

 

Exactly!

In ad hoc networks, there is a different scenario. In wired networks there are separate nodes for forwarding, which are called routers as opposed to ad = hoc environment in which the participating nodes have agreed to forward the = packets of other nodes. In other words, every participating node double as = routers. Therfore, there is no separate forwarding in ad hoc networks.

Youngmin Kim <blhole@venus.uos.ac.kr> wrote: =

I know that forwarding is separated from routing in wired = network.

Then.. why is not so in adhoc network? =

 

Thanks..

 

 

-----Original Message-----
From: = manet-admin@ietf.org [mailto:manet-admin@ietf.org] On = Behalf Of Ash Mohammad Abbas
Sent: = Tuesday, July 15, 2003 = 2:33 PM
To: Young-Jun Lee; = manet@ietf.org
Subject: Re: [manet] = Where to put on-demand routing protocol

 

Sir,

Irrespective of the fact that a protocol is on-demand or pro-active, a routing = protocol will remain layer-3( Network Layer of OSI model) protocol. After a route has = been established, ofcourse, the protocol might be used to send data = packets.

With best regards,

Ash Mohammad Abbas

http://www.cse.iitd.ernet.in= /~abbas

  Young-Jun Lee &lt;gte393q@mail.gatech.edu&gt; wrote: =

All,

In the INFOCOM paper 'Performance comparison of two on-demand = routing
protocols for ad hoc networks' = (S. Das, = C. Perkins, and E. Royer),
the simulation model section says

"The routing model sees all data packets transmitted or forwarded, = and
responds by invoking routing activities as appropriate".

Does it mean that on-demand routing protocol like AODV is between L3
and L4, or somewhere else?
Where exactly can on-demand protocols be in the protocol stack?

Young


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

3D"Yahoo!SMS = using the Yahoo! Messenger; Download latest = version.

3D"Yahoo!SMS = using the Yahoo! Messenger; Download latest = version.

------=_NextPart_000_0005_01C34BA8.3FCEEB20-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 16 02:13:03 2003 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 CAA01250 for ; Wed, 16 Jul 2003 02:13: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 19cfWm-0001BZ-Dm for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 02:12:36 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6G6CaPa004553 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 02:12:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cfWk-0001BE-Dx for manet-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 02:12: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 CAA01179 for ; Wed, 16 Jul 2003 02:12:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cfWg-0003Cu-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 02:12:30 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cfWb-0003Cr-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 02:12:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cfWE-00011u-SA; Wed, 16 Jul 2003 02:12:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cfVQ-0000ov-JA for manet@optimus.ietf.org; Wed, 16 Jul 2003 02:11: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 CAA00754 for ; Wed, 16 Jul 2003 02:11:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cfVN-0003CF-00 for manet@ietf.org; Wed, 16 Jul 2003 02:11:09 -0400 Received: from web10010.mail.yahoo.com ([216.136.128.121]) by ietf-mx with smtp (Exim 4.12) id 19cfVC-0003Br-00 for manet@ietf.org; Wed, 16 Jul 2003 02:10:58 -0400 Message-ID: <20030716061025.48588.qmail@web10010.mail.yahoo.com> Received: from [80.110.14.123] by web10010.mail.yahoo.com via HTTP; Tue, 15 Jul 2003 23:10:25 PDT Date: Tue, 15 Jul 2003 23:10:25 -0700 (PDT) From: Jaehoon Jeong Subject: Re: [manet] Ad Hoc IP Address Autoconfiguration To: Ash Mohammad Abbas Cc: manet@ietf.org In-Reply-To: <20030716044923.22861.qmail@web8103.mail.in.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --- Ash Mohammad Abbas wrote: > If a node leaves suddenly, we should not worry about > the reuse of its IP address. The incoming node > should be assignrd an IP address, which is not > currenly in use by other (remaining) active nodes. > Let the incoming node choose a different key ( or > the same key which is left by the leaving node ). > This will be a simpler solution. I aggree that some > of the IP addresses may not be used. Can we not have > number of IP addresses more than number of > participating nodes. If not in IPv4, then IPv6 > addresses ( there is a huge amount of addresses ). IMHO, For IPv4, it is valuable to consider the reuse of IP addresses further. Thanks for your opinion. /Jaehoon Paul > Wish you best, > Ash Mohammad Abbas > http://www.cse.iitd.ernet.in/~abbas > > jm.orset@free.fr wrote: > > > Le Tue, 15 Jul 2003 06:40:46 -0700 (PDT) > Jaehoon Jeong a ?rit: > > > You are right. The sentence should be corrected as > > follows; > > whose virtual address are the same that in its > cache > > -> ^^^^^^^^^^^^^^^ > > ~ IP address are the same ~ > > > > Yes! But in this case, I have still a problem. Let > suppose a node leaves > sudently the network. > Its IP address can be re-aloted to another node. > However the key this node will > choose will probably be different > from the key that will be associated with its > address in routing table of other > nodes, because those routing table or cache will not > have been updated since the > node is not aware of the re-alocation of the adress. > Consequently, if a node leaves the network sudently, > I think its address can not > be re-used. > > Is this right? > Thank you for your preceding answer. > > Cordially, Jean-Marie Orset > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > SMS using the Yahoo! Messenger;Download latest version. __________________________________ 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 Wed Jul 16 07:08:59 2003 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 HAA25452 for ; Wed, 16 Jul 2003 07:08:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ck93-0002Za-Hz for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 07:08:33 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GB8P2e009886 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 07:08:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ck93-0002ZN-Bi for manet-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 07:08: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 HAA25415 for ; Wed, 16 Jul 2003 07:08:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ck8z-0005ut-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 07:08:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ck8t-0005uq-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 07:08:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ck8f-0002ON-KC; Wed, 16 Jul 2003 07:08:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ck7r-0002B4-6j for manet@optimus.ietf.org; Wed, 16 Jul 2003 07:07: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 HAA25363 for ; Wed, 16 Jul 2003 07:07:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ck7n-0005uA-00 for manet@ietf.org; Wed, 16 Jul 2003 07:07:07 -0400 Received: from web10006.mail.yahoo.com ([216.136.130.42]) by ietf-mx with smtp (Exim 4.12) id 19ck7c-0005tj-00 for manet@ietf.org; Wed, 16 Jul 2003 07:06:56 -0400 Message-ID: <20030716110613.74548.qmail@web10006.mail.yahoo.com> Received: from [81.160.98.35] by web10006.mail.yahoo.com via HTTP; Wed, 16 Jul 2003 04:06:13 PDT Date: Wed, 16 Jul 2003 04:06:13 -0700 (PDT) From: Jaehoon Jeong To: manet@ietf.org Cc: khj@etri.re.kr, kipark@etri.re.kr, pjs@etri.re.kr MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] Presentation material about 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: , Hello MANET members! I send my presentation material for you to prepare to discuss MANET address autoconfiguration today. You can find it in the following links; http://www.adhoc.6ants.net/~paul/data/ietf57-manet-adhoc-ip-addr-autoconf-00.ppt http://www.adhoc.6ants.net/~paul/data/ietf57-manet-adhoc-ip-addr-autoconf-00.pdf /Jaehoon Paul __________________________________ 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 Wed Jul 16 14:20:33 2003 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 OAA11227 for ; Wed, 16 Jul 2003 14:20:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cqso-0003pB-GX for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 14:20:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GIK6qL014695 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 14:20:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cqso-0003ow-1H for manet-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 14:20: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 OAA11205 for ; Wed, 16 Jul 2003 14:20:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cqsg-0001uD-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 14:19:58 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cqsG-0001tu-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 14:19:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cqrl-0003OA-Nw; Wed, 16 Jul 2003 14:19:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cqqo-0003Iv-KO for manet@optimus.ietf.org; Wed, 16 Jul 2003 14:18: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 OAA11107 for ; Wed, 16 Jul 2003 14:17:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cqqh-0001sx-00 for manet@ietf.org; Wed, 16 Jul 2003 14:17:55 -0400 Received: from web10003.mail.yahoo.com ([216.136.130.39]) by ietf-mx with smtp (Exim 4.12) id 19cqqH-0001so-00 for manet@ietf.org; Wed, 16 Jul 2003 14:17:29 -0400 Message-ID: <20030716181702.18283.qmail@web10003.mail.yahoo.com> Received: from [81.160.243.20] by web10003.mail.yahoo.com via HTTP; Wed, 16 Jul 2003 11:17:02 PDT Date: Wed, 16 Jul 2003 11:17:02 -0700 (PDT) From: Jaehoon Jeong To: manet@ietf.org Cc: khj@etri.re.kr, kipark@etri.re.kr, pjs@etri.re.kr In-Reply-To: <20030716110613.74548.qmail@web10006.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] About Presentation about 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: , Hi MANET members. In this meeting, I brought ad hoc addressing issue to MANET wg again. I presented a stateless address autoconfiguration scheme, using strong DAD and weak DAD. As I know, some people seem to have suggested to make a requirement document about Ad Hoc IP Address Autoconfiguration, which introduces the need of ad hoc address autoconfiguration and analyzes stateless and stateful approaches. After writing the document, I think, for each approach we can develope mechanism drafts as informational RFCs. I would like to write the requirement draft. Is there any other volunteers? /Jaehoon Paul __________________________________ 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 Wed Jul 16 17:55:44 2003 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 RAA19205 for ; Wed, 16 Jul 2003 17:55: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 19cuF5-0008SY-L7 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 17:55:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GLtJGW032514 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 17:55:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cuF5-0008SL-Hv for manet-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 17:55: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 RAA19162 for ; Wed, 16 Jul 2003 17:55:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cuF2-0003vD-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 17:55:16 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19cuEx-0003vA-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 17:55:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cuEm-0008OI-VQ; Wed, 16 Jul 2003 17:55:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cuDz-0008Jg-PG for manet@optimus.ietf.org; Wed, 16 Jul 2003 17:54: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 RAA19068 for ; Wed, 16 Jul 2003 17:54:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cuDx-0003uG-00 for manet@ietf.org; Wed, 16 Jul 2003 17:54:09 -0400 Received: from jive.softhome.net ([66.54.152.27]) by ietf-mx with smtp (Exim 4.12) id 19cuDm-0003tj-00 for manet@ietf.org; Wed, 16 Jul 2003 17:53:58 -0400 Received: (qmail 3534 invoked by uid 417); 16 Jul 2003 21:52:10 -0000 Received: from shunt-smtp-out-0 (HELO softhome.net) (172.16.3.12) by shunt-smtp-out-0 with SMTP; 16 Jul 2003 21:52:10 -0000 Received: from dream ([202.88.168.95]) (AUTH: LOGIN jigar.doshi@softhome.net) by softhome.net with esmtp; Wed, 16 Jul 2003 15:52:06 -0600 From: "Jigar Doshi" To: manet@ietf.org Date: Thu, 17 Jul 2003 03:21:37 +0530 Organization: Doshi Housing Message-ID: <000001c34be4$81bfc040$5fa858ca@dream> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C34C12.9B77FC40" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [manet] FW: Performance Comparisons Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_01C34C12.9B77FC40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I am looking for papers on performance comparisons between adhoc routing protocols. Is there any such papers available other than the seminal Josh Broch David A. Maltz David B. Johnson et all A performance comparison of Multi-Hop Wireless Ad Hoc Network Routing Protocols. In particular has anyone compared the performance of hybrid routing schemes in adhoc networks? Thank You, Jigar Doshi ------=_NextPart_000_0001_01C34C12.9B77FC40 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

I am looking for papers on performance comparisons = between adhoc routing protocols.

Is there any such papers available other than the seminal Josh Broch = David A. Maltz David B. Johnson et all A performance comparison of Multi-Hop = Wireless Ad Hoc Network Routing Protocols. 

 

In particular has anyone compared the performance of = hybrid routing schemes in adhoc networks?

 

Thank You,

Jigar Doshi

 

 

------=_NextPart_000_0001_01C34C12.9B77FC40-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 16 18:05:13 2003 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 SAA19871 for ; Wed, 16 Jul 2003 18:05:13 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cuOG-0000uO-FO for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 18:04:48 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GM4moA003486 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 18:04:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cuOG-0000u9-BL for manet-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 18:04: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 SAA19777 for ; Wed, 16 Jul 2003 18:04:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cuNV-0000do-5w; Wed, 16 Jul 2003 18: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 19cuMW-0000Ql-Jk for manet@optimus.ietf.org; Wed, 16 Jul 2003 18:03: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 SAA19559 for ; Wed, 16 Jul 2003 18:02:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19cuMT-00040X-00 for manet@ietf.org; Wed, 16 Jul 2003 18:02:57 -0400 Received: from hellmouth5.gatech.edu ([130.207.165.165] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19cuMJ-000404-00 for manet@ietf.org; Wed, 16 Jul 2003 18:02:47 -0400 Received: from hellmouth5.gatech.edu (localhost [127.0.0.1]) by hellmouth5.gatech.edu (Postfix) with SMTP id D93561D19EB; Wed, 16 Jul 2003 18:01:03 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: from acmex.gatech.edu (acmex.prism.gatech.edu [130.207.171.14]) by hellmouth5.gatech.edu (Postfix) with ESMTP id BF9A11D19B6; Wed, 16 Jul 2003 18:01:03 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: by acmex.gatech.edu (Postfix, from userid 21503) id 839ED1DFA8; Wed, 16 Jul 2003 18:01:03 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by acmex.gatech.edu (Postfix) with ESMTP id 7C58D1F176; Wed, 16 Jul 2003 18:01:03 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Date: Wed, 16 Jul 2003 18:01:03 -0400 (EDT) From: Young-Jun Lee X-X-Sender: To: Jigar Doshi Cc: Subject: Re: [manet] FW: Performance Comparisons In-Reply-To: <000001c34be4$81bfc040$5fa858ca@dream> 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: , P. Johansson et al., ``Scenario-based performance analysis of routing protocols for mobile ad-hoc networks,'' ACM MOBICOM 1999. S. Das et al., ``Performance comparison of two on-demand routing protocols for ad hoc netwoks,'' IEEE INFOCOM 2000. On Thu, 17 Jul 2003, Jigar Doshi wrote: > Hi, > > I am looking for papers on performance comparisons between adhoc routing > protocols. > > Is there any such papers available other than the seminal Josh Broch > David A. Maltz David B. Johnson et all A performance comparison of > Multi-Hop Wireless Ad Hoc Network Routing Protocols. > > > > In particular has anyone compared the performance of hybrid routing > schemes in adhoc networks? > > > > Thank You, > > Jigar Doshi > > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 16 18:18:11 2003 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 SAA21134 for ; Wed, 16 Jul 2003 18:18:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cuap-000236-5J for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 18:17:47 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6GMHldS007870 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 18:17:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cuap-00022r-1U for manet-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 18:17: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 SAA21114 for ; Wed, 16 Jul 2003 18:17:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cua5-0001nl-Nl; Wed, 16 Jul 2003 18:17:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19cuZE-0001nK-Su for manet@optimus.ietf.org; Wed, 16 Jul 2003 18:16:09 -0400 Received: from che.ojctech.com (che.ojctech.com [209.254.133.74]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20997 for ; Wed, 16 Jul 2003 18:16:02 -0400 (EDT) Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id h6GMB5Rn018802 for ; Wed, 16 Jul 2003 17:11:05 -0500 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id h6GMB5LA018800 for manet@ietf.org; Wed, 16 Jul 2003 17:11:05 -0500 Date: Wed, 16 Jul 2003 17:11:05 -0500 From: David Young To: manet@ietf.org Message-ID: <20030716221105.GG14625@che.ojctech.com> Mail-Followup-To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: [manet] HSLS reference 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: , Is there a reference implementation of a Hazy-Sighted Link State routing daemon in open source? 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 Wed Jul 16 23:43:51 2003 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 XAA29726 for ; Wed, 16 Jul 2003 23:43:51 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19czfy-0001tx-5k for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 23:43:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6H3hQO9007303 for manet-archive@odin.ietf.org; Wed, 16 Jul 2003 23:43:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19czfy-0001ti-1L for manet-web-archive@optimus.ietf.org; Wed, 16 Jul 2003 23:43: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 XAA29683 for ; Wed, 16 Jul 2003 23:43:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19czfv-00078n-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 23:43:23 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19czfq-00078e-00 for manet-web-archive@ietf.org; Wed, 16 Jul 2003 23:43:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19czfZ-0001fu-8K; Wed, 16 Jul 2003 23:43:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19czee-0001fR-Dd for manet@optimus.ietf.org; Wed, 16 Jul 2003 23:42: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 XAA29616 for ; Wed, 16 Jul 2003 23:41:59 -0400 (EDT) From: atin@eden.rutgers.edu Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19czec-000775-00 for manet@ietf.org; Wed, 16 Jul 2003 23:42:02 -0400 Received: from nbcs-av.rutgers.edu ([128.6.72.254] helo=nbcs-av3.rutgers.edu) by ietf-mx with smtp (Exim 4.12) id 19czeR-000765-00 for manet@ietf.org; Wed, 16 Jul 2003 23:41:51 -0400 Received: from narnia7.rutgers.edu(165.230.180.177) by nbcs-av3.rutgers.edu via csmap id 8563; Wed, 16 Jul 2003 23:35:16 -0400 (EDT) Received: from azrael1.rutgers.edu (services.rutgers.edu [128.6.72.240]) by eden.rutgers.edu (Postfix) with SMTP id 2F3304001C for ; Wed, 16 Jul 2003 23:40:41 -0400 (EDT) To: manet@ietf.org Date: Wed, 16 Jul 2003 23:40:41 -0400 (EDT) X-Real-Sender: atin@eden.rutgers.edu X-Mailer: Postman 1.12 Message-ID: <3446461662atin@eden.rutgers.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable Subject: [manet] Multiple channel support in ns2 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 All, The standard ns2 package does not support multiple overlapping=20 channels. I need to simulate an ad hoc network which requires the=20 same. I'd really appreciate if I can get some pointers to any work=20 done in this area. Thanks, Atin Kumar Rutgers University _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 17 00:50:40 2003 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 AAA01949 for ; Thu, 17 Jul 2003 00:50:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d0id-0005Ej-MF for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 00:50:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6H4oFQp020130 for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 00:50:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d0id-0005Eb-Id for manet-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 00:50: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 AAA01937 for ; Thu, 17 Jul 2003 00:50:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19d0ia-0000Mz-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 00:50:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19d0iV-0000Mw-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 00:50:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19d0iP-000588-H8; Thu, 17 Jul 2003 00: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 19d0i0-00057h-Jr for manet@optimus.ietf.org; Thu, 17 Jul 2003 00:49: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 AAA01923 for ; Thu, 17 Jul 2003 00:49:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19d0hy-0000MJ-00 for manet@ietf.org; Thu, 17 Jul 2003 00:49:34 -0400 Received: from web8104.mail.in.yahoo.com ([203.199.70.104] helo=web8104.in.yahoo.com) by ietf-mx with smtp (Exim 4.12) id 19d0hm-0000LZ-00 for manet@ietf.org; Thu, 17 Jul 2003 00:49:23 -0400 Message-ID: <20030717044821.66119.qmail@web8104.in.yahoo.com> Received: from [202.141.69.57] by web8104.mail.in.yahoo.com via HTTP; Thu, 17 Jul 2003 05:48:21 BST Date: Thu, 17 Jul 2003 05:48:21 +0100 (BST) From: =?iso-8859-1?q?Ash=20Mohammad=20Abbas?= Subject: Re: [manet] FW: Performance Comparisons To: Jigar Doshi , manet@ietf.org In-Reply-To: <000001c34be4$81bfc040$5fa858ca@dream> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-176854743-1058417301=:65500" 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: , --0-176854743-1058417301=:65500 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit You may also look at 1) "Performance Comparison of Ad hoc Routing Protocols with Multicasing" by Ajay Agarwal, Ash Mohammad Abbas, Rajeev Shorey, Bijendra Nath Jain, Proc. of HPC-Asia 2002. 2) " Performance Comparison of On-demand Ad hoc Routing Protocols in a Sparse Mode Multicast Environment" by Ash Mohammad Abbas, Ajay Agarwal, Rajeev Shorey, Bijendra Nath Jain, Proc. of IEE/IFIP/TC6 Intenational Syposium on Telecommunications" ( to be held in August 2003). With best regards, Ash Mohammad Abbas http://www.cse.iitd.ernet.in/~abbas Jigar Doshi wrote: Hi, I am looking for papers on performance comparisons between adhoc routing protocols. Is there any such papers available other than the seminal Josh Broch David A. Maltz David B. Johnson et all A performance comparison of Multi-Hop Wireless Ad Hoc Network Routing Protocols. In particular has anyone compared the performance of hybrid routing schemes in adhoc networks? Thank You, Jigar Doshi SMS using the Yahoo! Messenger;Download latest version. --0-176854743-1058417301=:65500 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
You may also look at 
1) "Performance Comparison of Ad hoc Routing Protocols with Multicasing" by Ajay Agarwal, Ash Mohammad Abbas, Rajeev Shorey, Bijendra Nath Jain, Proc. of HPC-Asia 2002.
2) " Performance Comparison of On-demand Ad hoc Routing Protocols in a Sparse Mode Multicast Environment" by Ash Mohammad Abbas, Ajay Agarwal, Rajeev Shorey, Bijendra Nath Jain, Proc. of IEE/IFIP/TC6 Intenational Syposium on Telecommunications" ( to be held in August 2003).
With best regards,
Ash Mohammad Abbas

Jigar Doshi <jigar.doshi@softhome.net> wrote:

Hi,

I am looking for papers on performance comparisons between adhoc routing protocols.

Is there any such papers available other than the seminal Josh Broch David A. Maltz David B. Johnson et all A performance comparison of Multi-Hop Wireless Ad Hoc Network Routing Protocols. 

 

In particular has anyone compared the performance of hybrid routing schemes in adhoc networks?

 

Thank You,

Jigar Doshi

 

 

Yahoo! India Mobile SMS using the Yahoo! Messenger; Download latest version. --0-176854743-1058417301=:65500-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 17 10:47:02 2003 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 KAA09749 for ; Thu, 17 Jul 2003 10:47: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 19dA1k-0005LE-QM for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 10:46:37 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HEkaXf020526 for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 10:46:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dA1k-0005Kz-JQ for manet-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 10: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 KAA09717 for ; Thu, 17 Jul 2003 10:46:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dA1i-0006tC-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 10:46:34 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dA1c-0006t2-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 10:46:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dA1B-0005Jk-Qp; Thu, 17 Jul 2003 10:46:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dA0o-0005JN-8f for manet@optimus.ietf.org; Thu, 17 Jul 2003 10:45: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 KAA09684 for ; Thu, 17 Jul 2003 10:45:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dA0l-0006sQ-00 for manet@ietf.org; Thu, 17 Jul 2003 10:45:35 -0400 Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com) by ietf-mx with esmtp (Exim 4.12) id 19dA0a-0006rx-00 for manet@ietf.org; Thu, 17 Jul 2003 10:45:25 -0400 Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59) id ; Thu, 17 Jul 2003 10:43:48 -0400 Message-ID: <748C6D0A58C0F94CA63C198B6674697A0192C91B@ftmail.lab.flarion.com> From: Corson Scott To: "'manet@ietf.org'" Date: Thu, 17 Jul 2003 04:16:36 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain Subject: [manet] Presentations 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: , Folks, Would those that presented slides please forward me a copy for the Proceedings if you have not already done so. Thx. -Scott _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 17 10:56:46 2003 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 KAA10326 for ; Thu, 17 Jul 2003 10:56: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 19dABB-0005w3-8g for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 10:56:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HEuLrn022809 for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 10:56:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dABB-0005vo-4Z for manet-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 10:56: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 KAA10278 for ; Thu, 17 Jul 2003 10:56:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dAB8-0006yN-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 10:56:18 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dAB3-0006yK-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 10:56:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAAs-0005pS-4f; Thu, 17 Jul 2003 10:56:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAAP-0005oe-EB for manet@optimus.ietf.org; Thu, 17 Jul 2003 10:55: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 KAA10219 for ; Thu, 17 Jul 2003 10:55:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dAAM-0006xg-00 for manet@ietf.org; Thu, 17 Jul 2003 10:55:31 -0400 Received: from tardis.ee.ethz.ch ([129.132.2.217] helo=ntardis.ee.ethz.ch ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19dAAC-0006wQ-00 for manet@ietf.org; Thu, 17 Jul 2003 10:55:20 -0400 Received: from localhost (localhost [127.0.0.1]) by ntardis.ee.ethz.ch (Postfix) with ESMTP id 2DE58D9338 for ; Thu, 17 Jul 2003 16:53:39 +0200 (MEST) Received: from ntardis.ee.ethz.ch ([127.0.0.1]) by localhost (ntardis [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17402-06 for ; Thu, 17 Jul 2003 16:53:39 +0200 (MEST) Received: from tik.ee.ethz.ch (pc-3692.ethz.ch [129.132.66.106]) by ntardis.ee.ethz.ch (Postfix) with ESMTP id EE1A9D930B for ; Thu, 17 Jul 2003 16:53:38 +0200 (MEST) Message-ID: <3F16B871.8070200@tik.ee.ethz.ch> Date: Thu, 17 Jul 2003 16:53:37 +0200 From: Vincent Lenders User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030704 Debian/1.4-1 X-Accept-Language: en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at ee.ethz.ch Content-Transfer-Encoding: 7bit Subject: [manet] How to add a new routing protocol to Glomosim Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi I want to implement my own routing protocol in Glomosim. Is there a any documentation for this. I did not find any usefull documentation for the APIs of Glomosim. Thanx Vincent _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 17 11:00:08 2003 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 LAA10528 for ; Thu, 17 Jul 2003 11:00:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAEQ-0006UP-Tf for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 10:59:42 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HExgWR024939 for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 10:59:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAEQ-0006UA-Pi for manet-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 10:59:42 -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 KAA10494 for ; Thu, 17 Jul 2003 10:59:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dADm-0006D8-Da; Thu, 17 Jul 2003 10: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 19dACs-0006Ax-Tg for manet@optimus.ietf.org; Thu, 17 Jul 2003 10:58: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 KAA10407 for ; Thu, 17 Jul 2003 10:58:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dACq-0006zJ-00 for manet@ietf.org; Thu, 17 Jul 2003 10:58:04 -0400 Received: from hadar.cse.buffalo.edu ([128.205.32.1] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19dACf-0006xy-00 for manet@ietf.org; Thu, 17 Jul 2003 10:57:53 -0400 Received: from hadar.cse.Buffalo.EDU (ab42@localhost [127.0.0.1]) by hadar.cse.Buffalo.EDU (8.12.9/8.12.9) with ESMTP id h6HEtaBd016580 for ; Thu, 17 Jul 2003 10:55:36 -0400 (EDT) Received: (from ab42@localhost) by hadar.cse.Buffalo.EDU (8.12.9/8.12.9/Submit) id h6HEtZgk016578; Thu, 17 Jul 2003 10:55:35 -0400 (EDT) Date: Thu, 17 Jul 2003 10:55:35 -0400 (EDT) From: Aruna Balasubramanian To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Key management Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi all, I am a student in the University at Buffalo and am working on security for wireless networks. I have developed a key management protocol but i am not sure how I can test it. Even if i do use GlomoSim to simulate the protocol, how do i test its usefulness in terms of security Could someone please help Thank you Aruna _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 17 11:17:55 2003 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 LAA11306 for ; Thu, 17 Jul 2003 11:17:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAVb-0007zG-UE for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 11:17:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HFHRVt030698 for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 11:17:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAVb-0007z3-Nq for manet-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 11:17: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 LAA11288 for ; Thu, 17 Jul 2003 11:17:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dAVa-00079R-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 11:17:26 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dAVV-00079O-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 11:17:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAVB-0007nb-QF; Thu, 17 Jul 2003 11:17:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAV1-0007nK-25 for manet@optimus.ietf.org; Thu, 17 Jul 2003 11:16: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 LAA11272 for ; Thu, 17 Jul 2003 11:16:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dAV0-00078y-00 for manet@ietf.org; Thu, 17 Jul 2003 11:16:50 -0400 Received: from web10006.mail.yahoo.com ([216.136.130.42]) by ietf-mx with smtp (Exim 4.12) id 19dAUp-00078a-00 for manet@ietf.org; Thu, 17 Jul 2003 11:16:39 -0400 Message-ID: <20030717151618.5485.qmail@web10006.mail.yahoo.com> Received: from [81.160.243.20] by web10006.mail.yahoo.com via HTTP; Thu, 17 Jul 2003 08:16:18 PDT Date: Thu, 17 Jul 2003 08:16:18 -0700 (PDT) From: Jaehoon Jeong Subject: RE: [manet] About Presentation about Ad Hoc IP Address Autoconfiguration To: "Yang, Lily L" Cc: manet@ietf.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Lily, --- "Yang, Lily L" wrote: > Hi, Jaehoon -- > I had a conflict with MANET and so wasn't able to > hear your > presentation. I want to ask you one thing: What > about the scenario when > the mesh is connected to the internet? Do you think > autoconfig still > valuable and feasible since now the IP address has > to be globally > unique? To clarify your question, do you mean autoconfig as stateless autoconf? If so, my answer is yes. When considering Internet connectivity, Internet Gateway or DHCP server should assign an IP address to a manet node that wish to communicate with a correspondent node in the Internet. Therefore, either stateful or stateless autoconfiguration is necessary. However, we should also consider address autoconfiguration in case that Internet Gateway is inaccessible. It is general MANET, I think. In this environment, local-scoped address autoconfiguration, either stateless or stateful, is also necessary for the MANET separated from the Internet. /Jaehoon Paul > Lily > > -----Original Message----- > From: Jaehoon Jeong [mailto:jaehoon_paul@yahoo.com] > Sent: Wednesday, July 16, 2003 11:17 AM > To: manet@ietf.org > Cc: khj@etri.re.kr; kipark@etri.re.kr; > pjs@etri.re.kr > Subject: [manet] About Presentation about Ad Hoc IP > Address > Autoconfiguration > > Hi MANET members. > In this meeting, I brought ad hoc addressing issue > to > MANET wg again. I presented a stateless address > autoconfiguration scheme, using strong DAD and weak > DAD. > As I know, some people seem to have suggested to > make > a requirement document about Ad Hoc IP Address > Autoconfiguration, which introduces the need of ad > hoc > address autoconfiguration and analyzes stateless and > stateful approaches. After writing the document, I > think, for each approach we can develope mechanism > drafts as informational RFCs. I would like to write > the requirement draft. Is there any other > volunteers? > > /Jaehoon Paul > > __________________________________ > 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 __________________________________ 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 Thu Jul 17 11:30:53 2003 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 LAA11572 for ; Thu, 17 Jul 2003 11:30:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAiA-0008S8-WD for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 11:30:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HFUQNa032493 for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 11:30:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAiA-0008Rw-RZ for manet-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 11:30: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 LAA11541 for ; Thu, 17 Jul 2003 11:30:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dAi9-0007Dc-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 11:30:25 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dAi4-0007DZ-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 11:30:20 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAhl-0008LM-QD; Thu, 17 Jul 2003 11:30:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dAhQ-0008Ky-0U for manet@optimus.ietf.org; Thu, 17 Jul 2003 11:29: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 LAA11521 for ; Thu, 17 Jul 2003 11:29:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dAhO-0007DB-00 for manet@ietf.org; Thu, 17 Jul 2003 11:29:39 -0400 Received: from mail11.ntu.edu.sg ([155.69.5.163]) by ietf-mx with esmtp (Exim 4.12) id 19dAhE-0007Cp-00 for manet@ietf.org; Thu, 17 Jul 2003 11:29:28 -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); Thu, 17 Jul 2003 23:08:01 +0800 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 Subject: RE: [manet] Key management Date: Thu, 17 Jul 2003 23:07:52 +0800 Message-ID: <295CB338B611594582D82D9F26AEF70636587A@mail02.student.main.ntu.edu.sg> Thread-Topic: [manet] Key management Thread-Index: AcNMdE2QhL7ZcBVkQPyaM5Bqr3qZMAAAFndg From: "#ZHOU ZHI#" To: "Aruna Balasubramanian" Cc: X-OriginalArrivalTime: 17 Jul 2003 15:08:01.0892 (UTC) FILETIME=[3748FA40:01C34C75] 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 Aruna, Could you explain a little bit about your protocol? What security service it provides? I mean PKI, key agreement, or others? -----Original Message----- From: Aruna Balasubramanian [mailto:ab42@cse.Buffalo.EDU]=20 Sent: Thursday, July 17, 2003 22:56 To: manet@ietf.org Subject: [manet] Key management Importance: High Hi all, I am a student in the University at Buffalo and am working on security for wireless networks. I have developed a key management protocol but i am not sure how I can test it. Even if i do use GlomoSim to simulate the protocol, how do i test its usefulness in terms of security Could someone please help Thank you Aruna _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 17 13:00:58 2003 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 NAA13777 for ; Thu, 17 Jul 2003 13:00:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dC7M-0004wm-UD for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 13:00:33 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HH0W0u019010 for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 13:00:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dC7M-0004wX-MC for manet-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 13:00: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 NAA13769 for ; Thu, 17 Jul 2003 13:00:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dC7K-0007iP-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 13:00:30 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dC7F-0007iM-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 13:00:25 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dC6s-0004q4-8U; Thu, 17 Jul 2003 13:00:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dC64-0004pK-Sz for manet@optimus.ietf.org; Thu, 17 Jul 2003 12:59: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 MAA13729 for ; Thu, 17 Jul 2003 12:59:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dC63-0007hg-00 for manet@ietf.org; Thu, 17 Jul 2003 12:59:11 -0400 Received: from jive.softhome.net ([66.54.152.27]) by ietf-mx with smtp (Exim 4.12) id 19dC5s-0007hX-00 for manet@ietf.org; Thu, 17 Jul 2003 12:59:00 -0400 Received: (qmail 21997 invoked by uid 417); 17 Jul 2003 16:58:27 -0000 Received: from shunt-smtp-out-0 (HELO softhome.net) (172.16.3.12) by shunt-smtp-out-0 with SMTP; 17 Jul 2003 16:58:27 -0000 Received: from dream ([202.88.168.95]) (AUTH: LOGIN jigar.doshi@softhome.net) by softhome.net with esmtp; Thu, 17 Jul 2003 10:58:21 -0600 From: "Jigar Doshi" To: "'Krishnaswamy, Padma'" Cc: manet@ietf.org Subject: RE: [manet] FW: Performance Comparisons Date: Thu, 17 Jul 2003 22:27:47 +0530 Organization: Doshi Housing Message-ID: <000801c34c84$a0a2e550$5fa858ca@dream> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01C34CB2.BA5B2150" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <8A443FA5598F9545A4583F9D3BECE43F01C6B3CC@mcl-its-exs01> Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_01C34CB2.BA5B2150 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hybrid routing protocols = reactive + proactive like ZRp , SHARP etc. -----Original Message----- From: Krishnaswamy, Padma [mailto:PADMA.KRISHNASWAMY@saic.com] Sent: Thursday, July 17, 2003 9:03 PM To: Jigar Doshi Subject: RE: [manet] FW: Performance Comparisons Jigar Im curious about what you mean by hybrid routing schemes- did you mean layer 2 and layer 3 routing operating simultaneously, or is the hybrid nature based on something else- reactive + proactive for instance? thanks Padma Krishnaswamy -----Original Message----- From: Jigar Doshi [mailto:jigar.doshi@softhome.net] Sent: Wednesday, July 16, 2003 5:52 PM To: manet@ietf.org Subject: [manet] FW: Performance Comparisons Hi, I am looking for papers on performance comparisons between adhoc routing protocols. Is there any such papers available other than the seminal Josh Broch David A. Maltz David B. Johnson et all A performance comparison of Multi-Hop Wireless Ad Hoc Network Routing Protocols. In particular has anyone compared the performance of hybrid routing schemes in adhoc networks? Thank You, Jigar Doshi ------=_NextPart_000_0009_01C34CB2.BA5B2150 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hybrid routing protocols =3D = reactive + proactive like ZRp , SHARP etc.

 

-----Original = Message-----
From: Krishnaswamy, Padma [mailto:PADMA.KRISHNASWAMY@saic.com]
Sent: Thursday, July 17, = 2003 9:03 PM
To: Jigar Doshi
Subject: RE: [manet] FW: Performance Comparisons

 

Jigar

Im curious about = what you mean by hybrid routing schemes- did you mean layer 2 and layer 3 routing operating simultaneously, or is the hybrid nature based on something = else- reactive + proactive for instance?

 

thanks

Padma = Krishnaswamy

-----Original Message-----
From: Jigar Doshi [mailto:jigar.doshi@softhome.net]
Sent: Wednesday, July 16, = 2003 5:52 PM
To: manet@ietf.org
Subject: [manet] FW: = Performance Comparisons

Hi,

I am looking for papers on performance comparisons between adhoc routing = protocols.

Is there any such papers = available other than the seminal Josh Broch = David A. Maltz David B. Johnson et all A performance comparison of Multi-Hop = Wireless Ad Hoc Network Routing Protocols. 

 

In particular has anyone = compared the performance of hybrid routing schemes in adhoc = networks?

 

Thank = You,

Jigar Doshi =

 

 

------=_NextPart_000_0009_01C34CB2.BA5B2150-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 17 19:50:52 2003 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 TAA27484 for ; Thu, 17 Jul 2003 19:50: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 19dIW0-0005nj-Fz for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 19:50:24 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6HNoO1o022293 for manet-archive@odin.ietf.org; Thu, 17 Jul 2003 19:50:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dIW0-0005nU-BD for manet-web-archive@optimus.ietf.org; Thu, 17 Jul 2003 19:50: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 TAA27460 for ; Thu, 17 Jul 2003 19:50:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dIVy-0002Ti-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 19:50:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dIVs-0002Tf-00 for manet-web-archive@ietf.org; Thu, 17 Jul 2003 19:50:16 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dIVe-0005if-CP; Thu, 17 Jul 2003 19:50:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dIVN-0005iI-EW for manet@optimus.ietf.org; Thu, 17 Jul 2003 19:49: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 TAA27440 for ; Thu, 17 Jul 2003 19:49:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dIVL-0002TW-00 for manet@ietf.org; Thu, 17 Jul 2003 19:49:43 -0400 Received: from pedigree.cs.ubc.ca ([142.103.6.50]) by ietf-mx with esmtp (Exim 4.12) id 19dIVA-0002Sl-00 for manet@ietf.org; Thu, 17 Jul 2003 19:49:32 -0400 Received: from doraemon.cs.ubc.ca (IDENT:2JpERtwmzHsmW06SBOh5/3H0/vY4ObKW@doraemon.cs.ubc.ca [142.103.10.79]) by pedigree.cs.ubc.ca (8.12.9/8.11.4) with ESMTP id h6HNlUJt012430 for ; Thu, 17 Jul 2003 16:47:30 -0700 (PDT) Date: Thu, 17 Jul 2003 16:47:32 -0700 (PDT) From: Suprio Ray To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Mobility Model implementations for GlomoSim Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, For GlomoSim, the available mobility models (that I know) are Random Drunk/Walk and Random Waypoint. I would like to know if there are implementations of other Mobility Models available for GlomoSim for instance Gauss-Markov Model, Boundless Model, Nomadic Community Model etc. Thanks in advance for your information. Regards, Suprio ---------------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 18 00:27:43 2003 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 AAA03593 for ; Fri, 18 Jul 2003 00:27:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dMpy-0006bu-Ac for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 00:27:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I4RIRR025404 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 00:27:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dMpy-0006bf-6T for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 00:27: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 AAA03576 for ; Fri, 18 Jul 2003 00:27:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dMpv-0004Th-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 00:27:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dMpq-0004Te-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 00:27:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dMph-0006aV-4V; Fri, 18 Jul 2003 00:27:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dMpV-0006Yk-AV for manet@optimus.ietf.org; Fri, 18 Jul 2003 00:26: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 AAA03554 for ; Fri, 18 Jul 2003 00:26:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dMpS-0004TF-00 for manet@ietf.org; Fri, 18 Jul 2003 00:26:46 -0400 Received: from web41906.mail.yahoo.com ([66.218.93.157]) by ietf-mx with smtp (Exim 4.12) id 19dMpH-0004SG-00 for manet@ietf.org; Fri, 18 Jul 2003 00:26:35 -0400 Message-ID: <20030718042441.58834.qmail@web41906.mail.yahoo.com> Received: from [137.148.143.44] by web41906.mail.yahoo.com via HTTP; Thu, 17 Jul 2003 21:24:41 PDT Date: Thu, 17 Jul 2003 21:24:41 -0700 (PDT) From: Shiv Mehra To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-188765895-1058502281=:58104" Subject: [manet] AodvUU-ns2 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-188765895-1058502281=:58104 Content-Type: text/plain; charset=us-ascii Hello friends, Does the AODVUU ns2 patch support multiple interfaces? Best regards, Shiv --------------------------------- Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. --0-188765895-1058502281=:58104 Content-Type: text/html; charset=us-ascii
Hello friends,
Does the AODVUU ns2 patch support multiple interfaces?
Best regards,
Shiv

Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo. --0-188765895-1058502281=:58104-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 18 04:12:57 2003 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 EAA22016 for ; Fri, 18 Jul 2003 04:12:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dQLt-0000vL-Cg for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 04:12:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I8CTTB003489 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 04:12:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dQLp-0000tK-Tu for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 04:12: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 EAA21952 for ; Fri, 18 Jul 2003 04:12:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dQLm-0006Lh-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 04:12:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dQLh-0006Le-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 04:12:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dQLT-0000rL-D4; Fri, 18 Jul 2003 04:12:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dQKY-0000mI-P6 for manet@optimus.ietf.org; Fri, 18 Jul 2003 04:11:06 -0400 Received: from smtp.ietf57.telekom.at (smtp.ietf57.telekom.at [81.160.16.8]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21867 for ; Fri, 18 Jul 2003 04:11:02 -0400 (EDT) Received: from paul2 ([81.160.243.20]) by smtp.ietf57.telekom.at (8.11.7+Sun/8.10.2) with SMTP id h6I8A6k13500; Fri, 18 Jul 2003 10:10:06 +0200 (MEST) Message-ID: <005101c34cc9$83ce2ad0$14f3a051@etri.re.kr> From: "Jaehoon Jeong" To: Cc: "MANET WG" Date: Fri, 18 Jul 2003 10:11:27 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: base64 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: base64 Subject: [manet] Answer to a question in 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 RGVhciBDaGFybGVzIFBlcmtpbnMsDQoNCkluIG15IHRhbGsgb2YgdGhpcyBJRVRGIG1lZXRpbmcs IHlvdSBhc2tlZCBob3cgQUVSUiBtZXNzYWdlIGlzIGRlbGl2ZXJlZCANCmZyb20gb25lIG1vYmls ZSBub2RlIHRvIGFub3RoZXIgd2hpY2ggaGF2ZSBkdXBsaWNhdGUgYWRkcmVzc2VzIGR1cmluZyB3 ZWFrIERBRC4gDQpGb3IgZXhhbXBsZSwgbG9vayBhdCB0aGUgRmlnIDEsIHdoZXJlIE1BTkVUIHBh cnRpdGlvbiBjb25zaXN0IG9mIGZvdXIgbm9kZXMuDQoNCiAgICAgICBNTi0xIDwtLS0tLT4gTU4t MiA8LS0tLS0+IE1OLTMgPC0tLS0tPiBNTi00DQogKEEuQi5DLkQsIGtleS0xKSAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKEEuQi5DLkQsIGtleS00KQ0KICAgICAgICAg DQogIEZpZyAxLiBBZGRyZXNzIER1cGxpY2F0aW9uIGR1cmluZyBhZCBob2Mgcm91dGluZyAob3Ig V2VhayBEQUQpDQogDQpIb3cgZG9lcyBNTi00IGluZm9ybSBNTi0xIG9mIGFkZHJlc3MgZHVwbGlj YXRpb24gdGhyb3VnaCBBRVJSIG1lc3NhZ2UNCndoaWxlIE1OLTEgcGVyZm9ybXMgdGhlIHJvdXRl IGRpc2NvdmVyeShSUkVRKSBvZiBhIGRlc3RpbmF0aW9uIA0Kd2l0aCBpdHMgc291cmNlIGFkZHJl c3MgIkEuQi5DLkQiPw0KUlJFUSBjb250YWlucyBpdHMgc291cmNlIGFkZHJlc3MgYW5kIGtleS4N Ck1OLTQgcmVjZWl2ZXMgYW4gUlJFUSBmcm9tIE1OLTEgYW5kIGZpbmRzIG91dCBhZGRyZXNzIGR1 cGxpY2F0aW9uLA0KYmVjYXVzZSB0aGUgc291cmNlIGFkZHJlc3Mgb2YgUlJFUSBpcyB0aGUgc2Ft ZSBhcyBNTi00J3MgYnV0IHRoZSBrZXlzIGFyZSBkaWZmZXJlbnQuDQoNCkluIFdlYWsgREFELCB0 aGUgZm9yd2FyZGluZyBpcyBiYXNlZCBvbiB0aGUgcGFpciBvZiBJUCBhZGRyZXNzIGFuZCBrZXku IA0KTU4tMyBoYXMgdHdvIGhvc3Qgcm91dGVzIG9mIGFkZHJlc3MgIkEuQi5DLkQiIGluIHRoZSBt b21lbnQgdGhhdCBNTi0zIGZvcndhcmRzDQpNTi00J3MgQUVSUiBtZXNzYWdlIHRvd2FyZCBNTi0x IGxpa2UgVGFibGUgMS4NCg0KICBUYWJsZSAxLiBSb3V0aW5nIFRhYmxlIG9mIE1OLTMNCg0KICAg LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiAgfCAgICAg IERlc3QgICAgICAgfCBEZXN0IEtleSB8IE5leHQgSG9wIHwgRGlzdGFuY2UgfA0KICAgLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiAgfCAgIEEuQi5DLkQg ICB8ICAgIGtleS00ICAgIHwgICBNTi00ICAgIHwgICAgICAxICAgICAgfA0KICB8ICAgQS5CLkMu RCAgIHwgICAga2V5LTEgICAgfCAgIE1OLTIgICAgfCAgICAgIDIgICAgICB8IC0+IHByZWN1cnNv ciBmb3IgZm9yd2FyZGluZyBSUkVQIG1lc3NhZ2UNCiAgICAgICAuLi4uDQoNClRocm91Z2ggdGhl IGZvcndhcmRpbmcgYmFzZWQgb24gSVAgYWRkcmVzcyBhbmQga2V5LCB0aGUgQUVSUiBmcm9tIE1O LTQgd2lsbCBiZSBkZWxpdmVyZWQgdG8gTU4tMS4NClRoaXMgaXMgbXkgYW5zd2VyIDotKQ0KSXMg dGhlcmUgYW55IG1vcmUgcXVlc3Rpb24gYW5kIGNvbW1lbnRzPw0KDQpSZWdhcmRzLA0KSmFlaG9v biBQYXVsDQo= _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 18 04:39:54 2003 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 EAA23081 for ; Fri, 18 Jul 2003 04:39:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dQly-0002RJ-4R for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 04:39:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I8dPe2009370 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 04:39:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dQls-0002Nu-4N for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 04:39: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 EAA23045 for ; Fri, 18 Jul 2003 04:39:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dQlp-0006Wb-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 04:39:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dQlj-0006WY-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 04:39:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dQla-0002Jn-Pa; Fri, 18 Jul 2003 04:39:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dQl4-0002Iz-1N for manet@optimus.ietf.org; Fri, 18 Jul 2003 04:38: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 EAA22973 for ; Fri, 18 Jul 2003 04:38:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dQl0-0006VH-00 for manet@ietf.org; Fri, 18 Jul 2003 04:38:26 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19dQkp-0006Uf-00 for manet@ietf.org; Fri, 18 Jul 2003 04:38:15 -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 BAA15502; Fri, 18 Jul 2003 01:37:07 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h6I8b6d07282; Fri, 18 Jul 2003 01:37:06 -0700 X-mProtect: <200307180837> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (10.241.50.96, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdYZks0P; Fri, 18 Jul 2003 01:37:03 PDT Message-ID: <3F17B1B4.8010904@iprg.nokia.com> Date: Fri, 18 Jul 2003 01:37:08 -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: Jaehoon Jeong CC: MANET WG Subject: Re: [manet] Answer to a question in Ad Hoc IP Address Autoconfiguration References: <005101c34cc9$83ce2ad0$14f3a051@etri.re.kr> Content-Type: text/plain; charset=windows-1252; format=flowed 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 Hello Jaehoon Paul, Thanks for your explanation, now I understand. The solution places a requirement for a new field in the routing table -- namely, the inclusion of a "key" field. I guess there isn't any protection against accidental cases where the two contenders for A.B.C.D happen to select the same value for "key". That should be O.K. as long as (i) the key is _long_ (in bits), and (ii) the nodes are quite capable of producing truly random numbers. Also, I notice that the intermediate routing points also have to maintain the "key" value for the two endpoints, at least during address discovery. Regards, Charlie P. Jaehoon Jeong wrote: >Dear Charles Perkins, > >In my talk of this IETF meeting, you asked how AERR message is delivered >from one mobile node to another which have duplicate addresses during weak DAD. >For example, look at the Fig 1, where MANET partition consist of four nodes. > > MN-1 <-----> MN-2 <-----> MN-3 <-----> MN-4 > (A.B.C.D, key-1) (A.B.C.D, key-4) > > Fig 1. Address Duplication during ad hoc routing (or Weak DAD) > >How does MN-4 inform MN-1 of address duplication through AERR message >while MN-1 performs the route discovery(RREQ) of a destination >with its source address "A.B.C.D"? >RREQ contains its source address and key. >MN-4 receives an RREQ from MN-1 and finds out address duplication, >because the source address of RREQ is the same as MN-4's but the keys are different. > >In Weak DAD, the forwarding is based on the pair of IP address and key. >MN-3 has two host routes of address "A.B.C.D" in the moment that MN-3 forwards >MN-4's AERR message toward MN-1 like Table 1. > > Table 1. Routing Table of MN-3 > > ----------------------------------------------- > | Dest | Dest Key | Next Hop | Distance | > ----------------------------------------------- > | A.B.C.D | key-4 | MN-4 | 1 | > | A.B.C.D | key-1 | MN-2 | 2 | -> precursor for forwarding RREP message > .... > >Through the forwarding based on IP address and key, the AERR from MN-4 will be delivered to MN-1. >This is my answer :-) >Is there any more question and comments? > >Regards, >Jaehoon Paul >fjw-(% x% Kfjw-~'-?z+m&O 0Wx5h.fj)fj?e Kbz?)^ > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 18 05:50:47 2003 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 FAA25294 for ; Fri, 18 Jul 2003 05:50: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 19dRsY-0006Wi-Lb for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 05:50:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6I9oIdk025087 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 05:50:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dRsY-0006WY-HC for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 05:50: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 FAA25269 for ; Fri, 18 Jul 2003 05:50:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dRsU-0007Cz-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 05:50:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dRsP-0007Cw-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 05:50:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dRsI-0006VE-OX; Fri, 18 Jul 2003 05:50:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dRs4-0006TO-AP for manet@optimus.ietf.org; Fri, 18 Jul 2003 05:49: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 FAA25236 for ; Fri, 18 Jul 2003 05:49:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dRs0-0007CO-00 for manet@ietf.org; Fri, 18 Jul 2003 05:49:44 -0400 Received: from dpt-info.u-strasbg.fr ([130.79.44.193]) by ietf-mx with esmtp (Exim 4.12) id 19dRrp-0007C9-00 for manet@ietf.org; Fri, 18 Jul 2003 05:49:34 -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 h6I9n9nX025353 for ; Fri, 18 Jul 2003 11:49:09 +0200 Message-ID: <003d01c34d12$458d3ce0$ac5a4f82@ustrasbg.fr> From: "Christophe Jelger" To: "MANET WG" References: <005101c34cc9$83ce2ad0$14f3a051@etri.re.kr> Date: Fri, 18 Jul 2003 11:52:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" 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 h6I9n9nX025353 Content-Transfer-Encoding: quoted-printable 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: quoted-printable Content-Transfer-Encoding: quoted-printable Hi, I'm sorry I have not really followed all discussions around DAD in Adhoc networks and I've also not attended the IETF in Vienna, but I have a few questions about DAD in adhoc networks ... 1. Keeping in mind that IPv6 address collisions for stateless configurati= ons are extremely rare (from a probalistic point of you), I wonder what are t= he motivations for doing DAD in adhoc networks ... (actually the same questi= on could apply to wired networks, but I don't want to start a discussion on that) ;-) 2. DAD was designed to work on a link, it does not prevent nodes on different links to have the same address ... does it therefore make sense= to use DAD in a adhoc network, which is by essence a multi-hop network ? 3. If one wants to dissemate global prefix information in an adhoc networ= k, the usual RA technique cannot be used because nodes should forward packet= s sent to a link local address ... the point is : if we don't do it the nor= mal way and thus don't strictly follow IPv6 rules, can't we also consider to bypass DAD ? 4. By including complex mechanisms to perform DAD in adhoc networks, woul= d it not prevent routing protocols from being developed in a large scale an= d thus used ? Please do not misunderstand my point : I'm not saying DAD should not be used, I'm just trying to understand the pros and cons of using it in an adhoc environment. Comments on my thoughts are very welcome. Thanks, Christophe --------------------------------------------------------------- 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 Fri Jul 18 06:28:43 2003 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 GAA26044 for ; Fri, 18 Jul 2003 06:28:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dSTJ-0007yp-66 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 06:28:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6IASHOb030671 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 06:28:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dSTJ-0007yc-0v for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 06:28: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 GAA26021 for ; Fri, 18 Jul 2003 06:28:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dSTF-0007X0-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 06:28:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dST9-0007Wx-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 06:28:07 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dST3-0007s8-3Y; Fri, 18 Jul 2003 06: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 19dSSG-0007rm-9x for manet@optimus.ietf.org; Fri, 18 Jul 2003 06:27: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 GAA26013 for ; Fri, 18 Jul 2003 06:27:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dSS0-0007Wu-00 for manet@ietf.org; Fri, 18 Jul 2003 06:26:56 -0400 Received: from goliath.siemens.de ([192.35.17.28]) by ietf-mx with esmtp (Exim 4.12) id 19dSRp-0007Wr-00 for manet@ietf.org; Fri, 18 Jul 2003 06:26:45 -0400 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.11.7/8.11.7) with ESMTP id h6IAQa102003 for ; Fri, 18 Jul 2003 12:26:36 +0200 (MEST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail2.siemens.de (8.11.7/8.11.7) with ESMTP id h6IAQZq03995 for ; Fri, 18 Jul 2003 12:26:35 +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 h6IAQZe6015367 for ; Fri, 18 Jul 2003 12:26:35 +0200 (CEST) Received: from alpha (alpha [139.23.202.151]) by mail-y.mchp.siemens.de with SMTP id h6IAQYiO023295 for ; Fri, 18 Jul 2003 12:26:34 +0200 (MET DST) Date: Fri, 18 Jul 2003 12:26:34 +0200 (MET DST) From: Florian Schiel X-Sender: fschiel@alpha To: IETF MANET List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Question about multiple IPs Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 Folks, I noticed in the recent discussion, that it seems a mobile node in a MANET can only have one single IP. To my knowledge, there is nothing that stops us from assigning multiple IPs to a single interface of a device. At least in IPv6, an interface almost always has more than one IP, a link local one, and a global/site-local one. So what stops us from assigning a link-local IP together with a stateless autoconfigured MANET-IP and a global-scope IP statefully autoconfigured by a gateway? In IPv4 things should be similar. I hope I am not mistaken here... So long, 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 Fri Jul 18 07:38:36 2003 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 HAA27409 for ; Fri, 18 Jul 2003 07:38:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dTYt-0002Ox-An for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 07:38:07 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6IBc7bt009232 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 07:38:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dTYt-0002Op-4B for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 07:38: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 HAA27397 for ; Fri, 18 Jul 2003 07:38:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dTYs-0000Ci-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 07:38:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dTYm-0000Ce-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 07:38:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dTXq-00023l-46; Fri, 18 Jul 2003 07:37:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dTXK-000232-KJ for manet@optimus.ietf.org; Fri, 18 Jul 2003 07:36: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 HAA27377 for ; Fri, 18 Jul 2003 07:36:29 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dTXJ-0000CK-00 for manet@ietf.org; Fri, 18 Jul 2003 07:36:29 -0400 Received: from dpt-info.u-strasbg.fr ([130.79.44.193]) by ietf-mx with esmtp (Exim 4.12) id 19dTX9-0000CG-00 for manet@ietf.org; Fri, 18 Jul 2003 07:36:19 -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 h6IBZvnX026393 for ; Fri, 18 Jul 2003 13:35:57 +0200 Message-ID: <005d01c34d21$315db470$ac5a4f82@ustrasbg.fr> From: "Christophe Jelger" To: "IETF MANET List" References: Subject: Re: [manet] Question about multiple IPs Date: Fri, 18 Jul 2003 13:39:05 +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 There is indeed nothing that stops a node to have multiple addresses. You just have to be careful about how the routing protocol handles multiple addresses, and how in practise you can use these addresses. In particular, a few papers have proposed to have a site local address (MANET_PREFIX) to communicate within the adhoc network, and a global address for communications with the rst of the Internet. That's nice, but a communication has to be initiated with the address for this mechanism to work. If, for example, you use the name of a host whihc is in the adhoc network, and assuming there is a DNS system, how can the DNS "guess" which of the two addresses you want ? With the source address in the IPv6 header (either global or site ?) ? This is not so straight forward ... ;-) Christophe ----- Original Message ----- > > Hello Folks, > > I noticed in the recent discussion, that it seems a mobile node in > a MANET can only have one single IP. To my knowledge, there is nothing > that stops us from assigning multiple IPs to a single interface of > a device. > > At least in IPv6, an interface almost always has more than one IP, > a link local one, and a global/site-local one. > > So what stops us from assigning a link-local IP together with a stateless > autoconfigured MANET-IP and a global-scope IP statefully autoconfigured by > a gateway? > > In IPv4 things should be similar. > I hope I am not mistaken here... > > So long, > > 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 > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 18 08:42:50 2003 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 IAA28653 for ; Fri, 18 Jul 2003 08:42:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUZ3-0004Qc-Sn for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 08:42:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6ICgL06017016 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 08:42:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUZ3-0004QN-Oh for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 08:42: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 IAA28645 for ; Fri, 18 Jul 2003 08:42:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dUZ2-0000fP-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 08:42:20 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dUYw-0000fM-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 08:42:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUYj-0004MY-JW; Fri, 18 Jul 2003 08:42:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUYI-0004ML-GA for manet@optimus.ietf.org; Fri, 18 Jul 2003 08:41: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 IAA28635 for ; Fri, 18 Jul 2003 08:41:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dUYH-0000fJ-00 for manet@ietf.org; Fri, 18 Jul 2003 08:41:33 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19dUY6-0000es-00 for manet@ietf.org; Fri, 18 Jul 2003 08:41:22 -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 h6ICeGDi029351; Fri, 18 Jul 2003 08:40:16 -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 h6ICeEKP028011; Fri, 18 Jul 2003 08:40:16 -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 M2003071808401606605 ; Fri, 18 Jul 2003 08:40:16 -0400 Message-Id: <5.1.1.5.2.20030718083453.015077e8@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Fri, 18 Jul 2003 08:40:03 -0400 To: Florian Schiel , IETF MANET List From: Joe Macker Subject: Re: [manet] Question about multiple IPs In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 12:26 PM 7/18/2003 +0200, Florian Schiel wrote: >Hello Folks, > >I noticed in the recent discussion, that it seems a mobile node in >a MANET can only have one single IP. Where was that said? We already run IPv6 manet networks where this is not true. >At least in IPv6, an interface almost always has more than one IP, >a link local one, and a global/site-local one. Agreed. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 18 08:50:47 2003 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 IAA28817 for ; Fri, 18 Jul 2003 08:50: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 19dUgh-0004sL-JD for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 08:50:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6ICoFXe018735 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 08:50:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUgh-0004s6-Ej for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 08:50: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 IAA28809 for ; Fri, 18 Jul 2003 08:50:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dUgg-0000jA-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 08:50:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dUga-0000j7-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 08:50:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUgU-0004i1-5x; Fri, 18 Jul 2003 08:50:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUg7-0004hU-Gm for manet@optimus.ietf.org; Fri, 18 Jul 2003 08:49: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 IAA28789 for ; Fri, 18 Jul 2003 08:49:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dUg6-0000ij-00 for manet@ietf.org; Fri, 18 Jul 2003 08:49:38 -0400 Received: from smtp02.web.de ([217.72.192.151] helo=smtp.web.de) by ietf-mx with esmtp (Exim 4.12) id 19dUfv-0000iO-00 for manet@ietf.org; Fri, 18 Jul 2003 08:49:27 -0400 Received: from [80.131.155.154] (helo=navayo.local) by smtp.web.de with esmtp (WEB.DE 4.98 #244) id 19dUf4-0007Xb-00 for manet@ietf.org; Fri, 18 Jul 2003 14:48:34 +0200 From: Frank Dinies To: manet@ietf.org Subject: Re: [manet] Question about multiple IPs Date: Fri, 18 Jul 2003 14:48:27 +0200 User-Agent: KMail/1.5 References: <5.1.1.5.2.20030718083453.015077e8@pop.itd.nrl.navy.mil> In-Reply-To: <5.1.1.5.2.20030718083453.015077e8@pop.itd.nrl.navy.mil> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200307181448.28034.FrankDinies@web.de> Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, by the way, it is possible to have a NIC with more than one ip-address configured. Under linux this is possible with the ifconfig command. this is interessting for anycast purposes for example greeting Frank Am Freitag, 18. Juli 2003 14:40 schrieb Joe Macker: > At 12:26 PM 7/18/2003 +0200, Florian Schiel wrote: > >Hello Folks, > > > >I noticed in the recent discussion, that it seems a mobile node in > >a MANET can only have one single IP. > > Where was that said? > We already run IPv6 manet networks where this is not true. > > >At least in IPv6, an interface almost always has more than one IP, > >a link local one, and a global/site-local one. > > Agreed. > > > > _______________________________________________ > 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 Jul 18 09:00:48 2003 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 JAA29067 for ; Fri, 18 Jul 2003 09:00:48 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUqS-0005M8-Se for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 09:00:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6ID0KDr020589 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 09:00:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUqS-0005M0-ND for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 09:00: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 JAA29053 for ; Fri, 18 Jul 2003 09:00:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dUqR-0000pY-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 09:00:19 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dUqL-0000pV-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 09:00:13 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUqA-0005FK-0S; Fri, 18 Jul 2003 09:00:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dUpG-0005DU-D6 for manet@optimus.ietf.org; Fri, 18 Jul 2003 08:59: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 IAA29031 for ; Fri, 18 Jul 2003 08:59:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dUpE-0000pC-00 for manet@ietf.org; Fri, 18 Jul 2003 08:59:05 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19dUp4-0000og-00 for manet@ietf.org; Fri, 18 Jul 2003 08:58:54 -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 h6ICwJDi000213; Fri, 18 Jul 2003 08:58:19 -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 h6ICwDKP028430; Fri, 18 Jul 2003 08:58:18 -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 M2003071808581806687 ; Fri, 18 Jul 2003 08:58:18 -0400 Message-Id: <5.1.1.5.2.20030718085733.0340d2d8@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Fri, 18 Jul 2003 08:58:05 -0400 To: Frank Dinies , manet@ietf.org From: Joe Macker Subject: Re: [manet] Question about multiple IPs In-Reply-To: <200307181448.28034.FrankDinies@web.de> References: <5.1.1.5.2.20030718083453.015077e8@pop.itd.nrl.navy.mil> <5.1.1.5.2.20030718083453.015077e8@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 02:48 PM 7/18/2003 +0200, Frank Dinies wrote: >Hi, > >by the way, it is possible to have a NIC with more than one ip-address >configured. Under linux this is possible with the ifconfig command. this is >interessting for anycast purposes for example Agreed there is an important application for anycasting here. >greeting > >Frank > > >Am Freitag, 18. Juli 2003 14:40 schrieb Joe Macker: >> At 12:26 PM 7/18/2003 +0200, Florian Schiel wrote: >> >Hello Folks, >> > >> >I noticed in the recent discussion, that it seems a mobile node in >> >a MANET can only have one single IP. >> >> Where was that said? >> We already run IPv6 manet networks where this is not true. >> >> >At least in IPv6, an interface almost always has more than one IP, >> >a link local one, and a global/site-local one. >> >> Agreed. >> >> >> >> _______________________________________________ >> 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 Fri Jul 18 09:58:46 2003 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 JAA00470 for ; Fri, 18 Jul 2003 09:58: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 19dVkZ-0007OJ-S2 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 09:58:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6IDwJ1H028407 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 09:58:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dVkZ-0007O6-Oy for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 09:58: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 JAA00426 for ; Fri, 18 Jul 2003 09:58:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dVkX-00019J-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 09:58:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dVkS-00019G-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 09:58:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dVkH-0007IK-Ta; Fri, 18 Jul 2003 09:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dVji-0007Hg-7a for manet@optimus.ietf.org; Fri, 18 Jul 2003 09:57: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 JAA00393 for ; Fri, 18 Jul 2003 09:57:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dVjf-00018l-00 for manet@ietf.org; Fri, 18 Jul 2003 09:57:23 -0400 Received: from [133.11.236.3] (helo=saffron.mlab.t.u-tokyo.ac.jp) by ietf-mx with esmtp (Exim 4.12) id 19dVjU-00018C-00 for manet@ietf.org; Fri, 18 Jul 2003 09:57:12 -0400 Received: from saffron.mlab.t.u-tokyo.ac.jp (unknown [127.0.0.1]) by localhost (Postfix) with ESMTP id C58292CE9DE for ; Fri, 18 Jul 2003 22:56:07 +0900 (JST) Received: from MORI-T40.mlab.t.u-tokyo.ac.jp (unknown [133.11.236.3]) by saffron.mlab.t.u-tokyo.ac.jp (Postfix) with ESMTP id 40FD12CE9D6 for ; Fri, 18 Jul 2003 22:56:05 +0900 (JST) Message-Id: <5.1.1.9.2.20030718225547.04352b98@localhost> X-Sender: mori@localhost X-Mailer: QUALCOMM Windows Eudora Version 5.1-Jr4 Date: Fri, 18 Jul 2003 22:55:49 +0900 To: manet@ietf.org From: Hiroyuki Morikawa Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] MobiCom 2003 Call for Posters, Demos, and Exhibits Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 ACM MobiCom 2003, the Ninth Annual International Conference on Mobile Computing and Networking, will be held September 14-19, 2003, in beautiful, sunny San Diego, California. MobiCom is the premier international forum focusing on all areas of mobile computing and mobile and wireless networking at the link layer and above. Technical paper submission and selection for MobiCom 2003 is now complete, but it is not too late to present your work at the conference. MobiCom 2003 solicits posters for the Student Poster Session, as well as research demonstrations and product or service exhibits that showcase the state-of-the-art in mobile computing and networking systems. STUDENT POSTER SESSION MobiCom 2003 solicits student posters that present recent and on-going research by students on mobile computing and mobile and wireless networking topics. Presenting a poster at MobiCom is a great chance for students to obtain interesting and valuable feedback on their on-going work from a knowledgeable crowd at the conference. Poster proposals should be a maximum of 2 pages in length. Although posters don't need to describe completed work, the work should be advanced beyond the initial stages. The primary author of all poster submissions must be a student. Poster abstracts will not be published in the conference Proceedings but will be published on the web before the conference. Poster submissions will be reviewed. Authors of accepted papers at the conference must not submit a poster of the work presented in that paper. For more information on the MobiCom 2003 Student Poster Session and for detailed submission instructions, please see the Student Poster Session web page at http://www.sigmobile.org/mobicom/2003/posters.html The deadline for submitting a student poster is July 31, 2003. We will select approximately 20 of the most interesting and thought-provoking posters by August 18, 2003 and notify the contact author of each poster then. For questions about the MobiCom 2003 Student Poster Session or the poster submission and review process, please contact the Student Poster Session Co-Chairs Nigel Davies and James Kempf . DEMOS AND EXHIBITS If you are implementing a ground-breaking system in your research that you would like to demonstrate for your peers, please submit a proposal of no more than 3 pages to the Research Demo Chair, David Maltz , by July 25, 2003. Demo proposals should include a description of the demo, the equipment to be used, the demo layout and space required to set up the demo, and possible interactions (interoperability or interference) with other proposed demonstrations. The basic facilities available will be those typical of a hotel meeting room: power, table space, and poster easels. 100Base-T and 802.11 network connections may be arranged if required. For more information on submitting MobiCom 2003 demos, please see the Demos and Exhibits web page http://www.sigmobile.org/mobicom/2003/demos.html We are also planning an Expo at MobiCom 2003 featuring exhibits of the latest mobile computing products and services. If you are interested in exhibiting your product or service at MobiCom 2003, please see the Demos and Exhibits page of the MobiCom 2003 website for more information. Please also check our Corporate Supporters page for information on how to support the conference and receive a free Expo booth, web promotion, and complimentary registration for the conference. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 18 23:34:09 2003 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 XAA21942 for ; Fri, 18 Jul 2003 23:34:09 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19diTd-00073t-I9 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 23:33:41 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6J3XfBZ027139 for manet-archive@odin.ietf.org; Fri, 18 Jul 2003 23:33:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19diTc-00073e-2c for manet-web-archive@optimus.ietf.org; Fri, 18 Jul 2003 23:33: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 XAA21933 for ; Fri, 18 Jul 2003 23:33:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19diTZ-00065j-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 23:33:37 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19diTU-00065X-00 for manet-web-archive@ietf.org; Fri, 18 Jul 2003 23:33:32 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19diT2-0006zq-3N; Fri, 18 Jul 2003 23:33:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19diSH-0006za-Pq for manet@optimus.ietf.org; Fri, 18 Jul 2003 23:32: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 XAA21918 for ; Fri, 18 Jul 2003 23:32:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19diSE-000654-00 for manet@ietf.org; Fri, 18 Jul 2003 23:32:14 -0400 Received: from [202.108.44.181] (helo=sm181.163.com) by ietf-mx with esmtp (Exim 4.12) id 19diS4-00064x-00 for manet@ietf.org; Fri, 18 Jul 2003 23:32:04 -0400 Received: from localhost (localhost [127.0.0.1]) by sm181.163.com (Postfix) with SMTP id CD9131CB59231 for ; Sat, 19 Jul 2003 11:31:51 +0800 (CST) Received: from RavProxy (unknown [61.187.64.195]) by 192.168.1.181 (Coremail:163.com) with SMTP id 8k0AAKa7GD8MGUDD.1 for ; Sat, 19 Jul 2003 11:31:51 +0800 (CST) X-Originating-IP: [61.187.64.195] Message-ID: <002001c34da6$6e6cf490$7600a8c0@zyn> From: "Zhang Yanan" To: Date: Sat, 19 Jul 2003 11:32:50 +0800 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.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Transfer-Encoding: base64 Subject: [manet] realize WATCHDOG on 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: base64 Content-Transfer-Encoding: base64 SGF2ZSBhbnlvbmUgcmVhbGl6ZSAiV2F0aERvZyIgb24gRFNSIHVzaW5nIEdsb21vc2ltPz8NCg0K SSdtIHJlYWxseSB3YW50IHRvIGtub3cgaG93IHRvIHJlYWxpemUgaXQgIQ0KDQo= _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat Jul 19 01:14:59 2003 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 BAA23494 for ; Sat, 19 Jul 2003 01:14:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dk3E-0001Rc-16 for manet-archive@odin.ietf.org; Sat, 19 Jul 2003 01:14:32 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6J5EWZt005549 for manet-archive@odin.ietf.org; Sat, 19 Jul 2003 01:14:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dk3D-0001RQ-RV for manet-web-archive@optimus.ietf.org; Sat, 19 Jul 2003 01:14: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 BAA23491 for ; Sat, 19 Jul 2003 01:14:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dk3A-0006gX-00 for manet-web-archive@ietf.org; Sat, 19 Jul 2003 01:14:28 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dk35-0006gU-00 for manet-web-archive@ietf.org; Sat, 19 Jul 2003 01:14:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dk2j-0001Ne-Kf; Sat, 19 Jul 2003 01:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dk1n-0001Kg-AH for manet@optimus.ietf.org; Sat, 19 Jul 2003 01:13: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 BAA23482 for ; Sat, 19 Jul 2003 01:12:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dk1k-0006g2-00 for manet@ietf.org; Sat, 19 Jul 2003 01:13:00 -0400 Received: from ns.sait.samsung.co.kr ([202.20.142.13]) by ietf-mx with esmtp (Exim 4.12) id 19dk1Z-0006fV-00 for manet@ietf.org; Sat, 19 Jul 2003 01:12:49 -0400 Received: from mavpc (localhost [127.0.0.1]) by ns.sait.samsung.co.kr (8.12.9/8.12.1) with SMTP id h6J5BRb8021000; Sat, 19 Jul 2003 14:11:32 +0900 (KST) Message-ID: <002b01c34db4$45abb9c0$db2f024b@mavpc> From: "Jihoon Lee" To: "Christophe Jelger" , "MANET WG" References: <005101c34cc9$83ce2ad0$14f3a051@etri.re.kr> <003d01c34d12$458d3ce0$ac5a4f82@ustrasbg.fr> Subject: Re: [manet] Ad Hoc IP Address Autoconfiguration Date: Sat, 19 Jul 2003 14:11:50 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: base64 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: base64 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 SGkuIEplbGdlciBhbmQgbWFuZXQgbWVtYmVycy4NCg0KTXkgY29tbWVzIGFyZSBpbiBsaW5lLg0K DQoNCj4gDQo+IDIuIERBRCB3YXMgZGVzaWduZWQgdG8gd29yayBvbiBhIGxpbmssIGl0IGRvZXMg bm90IHByZXZlbnQgbm9kZXMgb24NCj4gZGlmZmVyZW50IGxpbmtzIHRvIGhhdmUgdGhlIHNhbWUg YWRkcmVzcyAuLi4gZG9lcyBpdCB0aGVyZWZvcmUgbWFrZSBzZW5zZSB0bw0KPiB1c2UgREFEIGlu IGEgYWRob2MgbmV0d29yaywgd2hpY2ggaXMgYnkgZXNzZW5jZSBhIG11bHRpLWhvcCBuZXR3b3Jr ID8NCg0KSVB2NiBEQUQgc2NoZW1lIGhhcyBvbi1saW5rIHJhbmdlLiBBcyB5b3Ugc2FpZCwgdGhl cmUgaXMsIGluIGVzc2VuY2UsIGEgZGlmZmVyZW5jZSBiZXR3ZWVuIG5vcm1hbCBJUHY2IERBRCBh bmQgREFEIGluIEFkIGhvYy4gREFEIGluIEFkIGhvYyBtZWFucyBhIHNjaGVtZSB0aGF0IGNhbiBk ZXRlY3QgYWRkcmVzcyBkdXBsaWNhdGlvbiBpbiBvbmUgYWQgaG9jIG5ldHdvcmsuIE9uZSBhZCBo b2MgbmV0d29yayBpcyBzaW1pbGFyIHRvIElQdjYgb24tbGluayBzdWJuZXQuIEVzcGVjaWFsbHkg aW4gYWQgaG9jIG5ldHdvcmtzLCB0aGVyZSBpcyBhIGNoYW5jZSBpbiBuZXR3b3JrIG1lcmdpbmcg KGFkIGhvYyBBICsgYWQgaG9jIEIpLiBJbiBtZXJnZWQgbmV0d29yaywgdGhlcmUgaXMgYSBiaWcg Y2hhbmNlIGluIHRoZSBleGlzdGVuY2Ugb2Ygc29tZSBub2RlcyB3aXRoIHRoZSBzYW1lIGFkZHJl c3MsIGVhY2ggb3RoZXIgcmFuZG9tbHkgZ2VuZXJhdGVkLiBBIGNvbGxpc2lvbiBhbW9uZyBzb21l IG5vZGVzIGlzIGluZXZpdGFibGUuDQoNCkluIHN1bW1hcnksIEkgdGhpbmsgREFEIGluIGFkIGhv YyBpcyBuZWVkZWQgdG8gZXNjYXBlIHBhY2tldCBtaXNyb3V0aW5ncyB0byB3cm9uZyBub2RlLiAN Cg0KDQpJbiBhZGRpdGlvbiwgSSB0aGluayB0aGF0IGZvciBlZmZpY2llbnQgREFEIHNoY2VtZSwg bmV0d29yayBjbHVzdGVyaW5nL3BhcnRpdGlvbmluZyBzY2hlbWUgbXVzdCBiZSB0b2dldGhlciBj b25zaWRlcmVkIA0KDQoNCg== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat Jul 19 12:16:50 2003 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 MAA17439 for ; Sat, 19 Jul 2003 12:16:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19duNk-0003cc-IN for manet-archive@odin.ietf.org; Sat, 19 Jul 2003 12:16:24 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6JGGOVd013919 for manet-archive@odin.ietf.org; Sat, 19 Jul 2003 12:16:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19duNk-0003cQ-Ae for manet-web-archive@optimus.ietf.org; Sat, 19 Jul 2003 12:16: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 MAA17436 for ; Sat, 19 Jul 2003 12:16:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19duNi-0002yz-00 for manet-web-archive@ietf.org; Sat, 19 Jul 2003 12:16:23 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19duNd-0002yw-00 for manet-web-archive@ietf.org; Sat, 19 Jul 2003 12:16:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19duNO-0003bF-Py; Sat, 19 Jul 2003 12:16:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19duMb-0003ax-GH for manet@optimus.ietf.org; Sat, 19 Jul 2003 12:15: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 MAA17430 for ; Sat, 19 Jul 2003 12:15:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19duMa-0002yh-00 for manet@ietf.org; Sat, 19 Jul 2003 12:15:12 -0400 Received: from web40006.mail.yahoo.com ([66.218.78.24]) by ietf-mx with smtp (Exim 4.12) id 19duMP-0002yT-00 for manet@ietf.org; Sat, 19 Jul 2003 12:15:01 -0400 Message-ID: <20030719161411.54722.qmail@web40006.mail.yahoo.com> Received: from [129.110.93.17] by web40006.mail.yahoo.com via HTTP; Sat, 19 Jul 2003 09:14:11 PDT Date: Sat, 19 Jul 2003 09:14:11 -0700 (PDT) From: ruchir sinha To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] Help!!...Glomosim installation on LINUX Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I am new to LINUX and Glomosim....and having problems with Glomosim Installation on LINUX.. I followed the following steps..... After unzipping and doing an untar ( which was successfully done) i did the following ------------------------------------------------------------------------------------------------------------------------------------------- bash-2.05b$ pwd /ruchir/glomosim-2.03/glomosim/main bash-2.05b$ setenv PCC_DIRECTORY /ruchir/glomosim-2.03/parsec/redhat-7.2 bash: setenv: command not found bash-2.05b$ As you can see i got this error message..... ------------------------------------------------------------------------------------------------------------------------------------------- I then searched on google and found the following information about setenv... Setenv is C shell. Red Hat defaults to the Bash > shell. > > The Bash equivalent of the C shell > > setenv VARIABLE value > > is > > export VARIABLE=value > > or > > VARIABLE=value; export VARIABLE > > the latter being more portable as it will also work > in the older Bourne > shell. Either will also work in the K shell. > > Both the csh setenv and the sh/bash/ksh export are > built in commands, so > they do not have associated binaries. The setenv man > page you found is, > as "karlp" pointed out, for the subroutine for use > in programs. Shell > builtins are documented in the man pages for the > shells themselves (e.g. > "man bash"). -------------------------------------------------------------------------------------------------------------------------------------------- So I tried export and this is what i got...... bash-2.05b$ pwd /ruchir bash-2.05b$ export PCC_DIRECTORY=/ruchir/glomosim-2.03/redhat-7.2 bash-2.05b$ pwd /ruchir bash-2.05b$ cd glomosim-2.03 bash-2.05b$ cd glomosim bash-2.05b$ cd main bash-2.05b$ pwd /ruchir/glomosim-2.03/glomosim/main bash-2.05b$ make pcc -g -O3 -I../include/ -I../transport -I../transport/tcp -I../application -I../mac -I../main -I../network -I../radio -clock longlong -lm -c ../main/glomo.pc make: pcc: Command not found make: *** [../main/glomo.o] Error 127 bash-2.05b$ -------------------------------------------------------------------------------------------------------------------------------------- I then copied the files parsecc and pcc from /ruchir/glomosim-2.03/glomosim/parsec/redhat-7.2 to /ruchir/glomosim-2.03/glomosim/main and tried a make again ( from main) but did not work( same error message as above.. Can anyone help me out...... Regards Ruchir __________________________________ 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 Sat Jul 19 12:52:44 2003 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 MAA17840 for ; Sat, 19 Jul 2003 12:52: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 19duwV-0004ht-3L for manet-archive@odin.ietf.org; Sat, 19 Jul 2003 12:52:19 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6JGqJ3g018087 for manet-archive@odin.ietf.org; Sat, 19 Jul 2003 12:52:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19duwV-0004he-03 for manet-web-archive@optimus.ietf.org; Sat, 19 Jul 2003 12:52: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 MAA17808 for ; Sat, 19 Jul 2003 12:52:13 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19duwT-00035i-00 for manet-web-archive@ietf.org; Sat, 19 Jul 2003 12:52:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19duwN-00035d-00 for manet-web-archive@ietf.org; Sat, 19 Jul 2003 12:52:11 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19duwD-0004bv-J3; Sat, 19 Jul 2003 12:52:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19duvr-0004bY-Ut for manet@optimus.ietf.org; Sat, 19 Jul 2003 12:51: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 MAA17799 for ; Sat, 19 Jul 2003 12:51:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19duvq-00035U-00 for manet@ietf.org; Sat, 19 Jul 2003 12:51:38 -0400 Received: from dyn110.mel1.homedsl.pacific.net.au ([203.100.244.110] helo=sun.etna.org) by ietf-mx with esmtp (Exim 4.12) id 19duve-00035P-00 for manet@ietf.org; Sat, 19 Jul 2003 12:51:27 -0400 Received: by sun.etna.org (Postfix, from userid 0) id 9850014D60; Sun, 20 Jul 2003 02:50:24 +1000 (EST) Subject: Re: [manet] Help!!...Glomosim installation on LINUX From: Anshul Gupta To: ruchir sinha Cc: manet@ietf.org In-Reply-To: <20030719161411.54722.qmail@web40006.mail.yahoo.com> References: <20030719161411.54722.qmail@web40006.mail.yahoo.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1058633423.3506.47.camel@sun.etna.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 20 Jul 2003 02:50:24 +1000 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 setenv works only in C shell. Do "export PCC_DIRECTORY=value" before you type any command. On Sun, 2003-07-20 at 02:14, ruchir sinha wrote: > Hi, > I am new to LINUX and Glomosim....and having > problems with Glomosim Installation on LINUX.. > I followed the following steps..... > > After unzipping and doing an untar ( which was > successfully done) i did the following > ------------------------------------------------------------------------------------------------------------------------------------------- > bash-2.05b$ pwd > /ruchir/glomosim-2.03/glomosim/main > bash-2.05b$ setenv PCC_DIRECTORY > /ruchir/glomosim-2.03/parsec/redhat-7.2 > bash: setenv: command not found > bash-2.05b$ > > As you can see i got this error message..... > ------------------------------------------------------------------------------------------------------------------------------------------- > I then searched on google and found the following > information about setenv... > > Setenv is C shell. Red Hat defaults to the Bash > > shell. > > > > The Bash equivalent of the C shell > > > > setenv VARIABLE value > > > > is > > > > export VARIABLE=value > > > > or > > > > VARIABLE=value; export VARIABLE > > > > the latter being more portable as it will also work > > in the older Bourne > > shell. Either will also work in the K shell. > > > > Both the csh setenv and the sh/bash/ksh export are > > built in commands, so > > they do not have associated binaries. The setenv man > > page you found is, > > as "karlp" pointed out, for the subroutine for use > > in programs. Shell > > builtins are documented in the man pages for the > > shells themselves (e.g. > > "man bash"). > -------------------------------------------------------------------------------------------------------------------------------------------- > So I tried export and this is what i got...... > > bash-2.05b$ pwd > /ruchir > bash-2.05b$ export > PCC_DIRECTORY=/ruchir/glomosim-2.03/redhat-7.2 > bash-2.05b$ pwd > /ruchir > bash-2.05b$ cd glomosim-2.03 > bash-2.05b$ cd glomosim > bash-2.05b$ cd main > bash-2.05b$ pwd > /ruchir/glomosim-2.03/glomosim/main > bash-2.05b$ make > pcc -g -O3 -I../include/ -I../transport > -I../transport/tcp -I../application -I../mac -I../main > -I../network -I../radio -clock longlong -lm -c > .../main/glomo.pc > make: pcc: Command not found > make: *** [../main/glomo.o] Error 127 > bash-2.05b$ > -------------------------------------------------------------------------------------------------------------------------------------- > > I then copied the files parsecc and pcc from > > /ruchir/glomosim-2.03/glomosim/parsec/redhat-7.2 to > /ruchir/glomosim-2.03/glomosim/main > > and tried a make again ( from main) but did not work( > same error message as above.. > > Can anyone help me out...... > > Regards > Ruchir > > __________________________________ > 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 -- Anshul Gupta _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat Jul 19 16:16:52 2003 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 QAA21889 for ; Sat, 19 Jul 2003 16:16: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 19dy7y-00018F-74 for manet-archive@odin.ietf.org; Sat, 19 Jul 2003 16:16:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6JKGM0Q004347 for manet-archive@odin.ietf.org; Sat, 19 Jul 2003 16:16:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dy7y-000182-0t for manet-web-archive@optimus.ietf.org; Sat, 19 Jul 2003 16:16: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 QAA21861 for ; Sat, 19 Jul 2003 16:16:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dy7w-00044r-00 for manet-web-archive@ietf.org; Sat, 19 Jul 2003 16:16:20 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19dy7q-00044o-00 for manet-web-archive@ietf.org; Sat, 19 Jul 2003 16:16:14 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dy7e-00014D-K1; Sat, 19 Jul 2003 16:16:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19dy6w-00013w-Is for manet@optimus.ietf.org; Sat, 19 Jul 2003 16:15: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 QAA21858 for ; Sat, 19 Jul 2003 16:15:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19dy6u-00044Q-00 for manet@ietf.org; Sat, 19 Jul 2003 16:15:16 -0400 Received: from cheviot3.ncl.ac.uk ([128.240.233.117] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19dy6k-00044A-00 for manet@ietf.org; Sat, 19 Jul 2003 16:15:06 -0400 Received: from ncl.ac.uk (msvpn-4.ncl.ac.uk [128.240.230.132]) by cheviot3.ncl.ac.uk (8.10.1/8.10.1) with ESMTP id h6JKEge30876; Sat, 19 Jul 2003 21:14:42 +0100 Date: Sat, 19 Jul 2003 21:11:24 +0100 Subject: Re: [manet] Mobility Model implementations for GlomoSim Content-Type: text/plain; delsp=yes; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: manet@ietf.org To: Suprio Ray From: Einar Vollset In-Reply-To: Message-Id: <2BCDA2A1-BA25-11D7-AA4E-000A9575BD30@ncl.ac.uk> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) X-Newcastle-MailScanner-Information: Please contact Postmaster@newcastle.ac.uk for more information 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 Suprio, I believe BonnMotion (http://web.informatik.uni-bonn.de/IV/Mitarbeiter/dewaal/BonnMotion/) provides a number of mobility models which can be "ported" both to ns-2 and Glomosim. It also provides a simple (but very usefull) statistics tool to analyze generated mobility scenarios. Cheers, Einar On Friday, Jul 18, 2003, at 00:47 Europe/London, Suprio Ray wrote: > > Hi, > For GlomoSim, the available mobility models (that I know) are Random > Drunk/Walk and Random Waypoint. > > I would like to know if there are implementations of other Mobility > Models > available for GlomoSim for instance Gauss-Markov Model, Boundless > Model, > Nomadic Community Model etc. > > Thanks in advance for your information. > > Regards, > Suprio > ----------------------------------------------------------------------- > ----- > > > _______________________________________________ > 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 Jul 21 16:21:02 2003 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 QAA09729 for ; Mon, 21 Jul 2003 16:21:01 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eh99-0004Rc-PI for manet-archive@odin.ietf.org; Mon, 21 Jul 2003 16:20:36 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6LKKZON017077 for manet-archive@odin.ietf.org; Mon, 21 Jul 2003 16:20:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eh99-0004RM-Hs for manet-web-archive@optimus.ietf.org; Mon, 21 Jul 2003 16:20: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 QAA09715 for ; Mon, 21 Jul 2003 16:20:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19eh97-000647-00 for manet-web-archive@ietf.org; Mon, 21 Jul 2003 16:20:33 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19eh92-000643-00 for manet-web-archive@ietf.org; Mon, 21 Jul 2003 16:20:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eh8b-0004N4-Kb; Mon, 21 Jul 2003 16:20:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eh8D-0004MU-5L for manet@optimus.ietf.org; Mon, 21 Jul 2003 16:19: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 QAA09692 for ; Mon, 21 Jul 2003 16:19:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19eh8A-00063d-00 for manet@ietf.org; Mon, 21 Jul 2003 16:19:34 -0400 Received: from mail.drexel.edu ([144.118.25.40]) by ietf-mx with esmtp (Exim 4.12) id 19eh7z-00063Y-00 for manet@ietf.org; Mon, 21 Jul 2003 16:19:23 -0400 Received: from webmail.drexel.edu (webmail.drexel.edu [144.118.25.20]) by mail.drexel.edu (Sun Internet Mail Server sims.4.0.2001.07.26.11.50.p9) with ESMTP id <0HIE00IGX5RKLO@mail.drexel.edu> for manet@ietf.org; Mon, 21 Jul 2003 16:18:56 -0400 (EDT) Date: Mon, 21 Jul 2003 16:18:56 -0400 From: Harpreet Arora To: manet@ietf.org Message-id: <3F1C8EA4@webmail.drexel.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: ha33 X-EXP32-SerialNo: 00003005 Content-Transfer-Encoding: 7BIT Subject: [manet] bandwidth calculation at a node Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT Hi, I have read a number of papers offering QoS solutions in MANETs. Most of them assume that nodes somehow have an idea of the available bandwidth in their neighborhood and either pass this information around or make admission control decisions based on this information. The SWAN model computes bandwidth at a node by tapping all packet transmissions within the neighborhood of the node within a certain period of time and updating the estimate of the bandwidth being used based on that information. However, this does not capture the scenario where two nodes are within interfering range of each other but not in reception range. Are there any papers in this regard? thanks, Harpreet S. Arora Research Assistant, ITCSL Drexel University Philadelphia, PA-19104 Ph: 215-895-6198 -------------------------------------------------------------------- Harpreet S. Arora Research Assistant, ITCSL Drexel University, Philadelphia, PA-19104 Ph. # 215-895-6198 http://www.pages.drexel.edu/~ha33 ---------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 22 00:46:42 2003 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 AAA19427 for ; Tue, 22 Jul 2003 00:46:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ep2X-00030A-Gr for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 00:46:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6M4kHDc011534 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 00:46:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ep2X-0002zx-E5 for manet-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 00:46: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 AAA19412 for ; Tue, 22 Jul 2003 00:46:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ep2U-0001Fw-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 00:46:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ep2P-0001Ft-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 00:46:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ep2I-0002u4-D4; Tue, 22 Jul 2003 00:46:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ep1L-0002ta-RA for manet@optimus.ietf.org; Tue, 22 Jul 2003 00: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 AAA19401 for ; Tue, 22 Jul 2003 00:44:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ep1J-0001FT-00 for manet@ietf.org; Tue, 22 Jul 2003 00:45:01 -0400 Received: from web8105.mail.in.yahoo.com ([203.199.70.105] helo=web8105.in.yahoo.com) by ietf-mx with smtp (Exim 4.12) id 19ep18-0001F2-00 for manet@ietf.org; Tue, 22 Jul 2003 00:44:50 -0400 Message-ID: <20030722044358.77773.qmail@web8105.in.yahoo.com> Received: from [202.141.69.19] by web8105.mail.in.yahoo.com via HTTP; Tue, 22 Jul 2003 05:43:58 BST Date: Tue, 22 Jul 2003 05:43:58 +0100 (BST) From: =?iso-8859-1?q?Ash=20Mohammad=20Abbas?= Subject: Re: [manet] bandwidth calculation at a node To: Harpreet Arora , manet@ietf.org In-Reply-To: <3F1C8EA4@webmail.drexel.edu> 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 Sir, As if I know, there was a whole symposium on inteference cancellation in IEEE VTC 2003 chaired by Husain Arsalan, from University of Florida, USA. I suggest, search their website, and if you have authorization to see IEEE Conference Proc., I think you may get some papers on your problem. Wish you best, Regards, Abbas http://www.cse.iitd.ernet.in/~abbas --- Harpreet Arora wrote: > Hi, > > I have read a number of papers offering QoS > solutions in MANETs. Most of them > assume that nodes somehow have an idea of the > available bandwidth in their > neighborhood and either pass this information around > or make admission control > decisions based on this information. The SWAN model > computes bandwidth at a > node by tapping all packet transmissions within the > neighborhood of the node > within a certain period of time and updating the > estimate of the bandwidth > being used based on that information. However, this > does not capture the > scenario where two nodes are within interfering > range of each other but not in > reception range. Are there any papers in this > regard? > > thanks, > Harpreet S. Arora > > Research Assistant, ITCSL > Drexel University > Philadelphia, PA-19104 > Ph: 215-895-6198 > > -------------------------------------------------------------------- > Harpreet S. Arora > Research Assistant, ITCSL > Drexel University, > Philadelphia, PA-19104 > Ph. # 215-895-6198 > http://www.pages.drexel.edu/~ha33 > ---------------------------------------------------------------------- > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet ________________________________________________________________________ Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 22 01:59:51 2003 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 BAA20460 for ; Tue, 22 Jul 2003 01:59: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 19eqBF-00059G-Q1 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 01:59:24 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6M5xLKA019787 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 01:59:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eqBF-000594-MG for manet-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 01:59: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 BAA20457 for ; Tue, 22 Jul 2003 01:59:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19eqBC-0001f9-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 01:59:18 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19eqB6-0001f6-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 01:59:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eqAv-00055H-Mw; Tue, 22 Jul 2003 01: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 19eqAr-00054i-CQ for manet@optimus.ietf.org; Tue, 22 Jul 2003 01: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 BAA20448 for ; Tue, 22 Jul 2003 01:58:53 -0400 (EDT) From: bsmanoj@cs.iitm.ernet.in Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19eqAo-0001f3-00 for manet@ietf.org; Tue, 22 Jul 2003 01:58:54 -0400 Received: from pri-dns.cs.iitm.ernet.in ([202.141.25.89] helo=cello.cs.iitm.ernet.in) by ietf-mx with esmtp (Exim 4.12) id 19eqAb-0001ez-00 for manet@ietf.org; Tue, 22 Jul 2003 01:58:42 -0400 Received: from rts.cs.iitm.ernet.in (rts.cs.iitm.ernet.in [10.6.6.3]) by cello.cs.iitm.ernet.in (8.12.5/8.12.5) with ESMTP id h6M6NREh010224; Tue, 22 Jul 2003 11:53:31 +0530 Received: from hpc.cs.iitm.ernet.in (IDENT:root@hpc.cs.iitm.ernet.in [10.6.6.2]) by rts.cs.iitm.ernet.in (8.9.3/8.8.7) with ESMTP id KAA17817; Tue, 22 Jul 2003 10:43:59 +0530 Received: from localhost (bsmanoj@localhost) by hpc.cs.iitm.ernet.in (8.11.2/8.11.2) with ESMTP id h6M5rTD28023; Tue, 22 Jul 2003 11:23:30 +0530 X-Authentication-Warning: hpc.cs.iitm.ernet.in: bsmanoj owned process doing -bs Date: Tue, 22 Jul 2003 11:23:29 +0530 (IST) cc: Harpreet Arora , Subject: Re: [manet] bandwidth calculation at a node In-Reply-To: <20030722044358.77773.qmail@web8105.in.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Arora, Instead of taking the number of transmissions for bandwidth calculation, One can try the channel's "idle time" during a time window under consideration. This can take in to account nodes presence in the interference range. bsmanoj > --- Harpreet Arora wrote: > Hi, > > > > I have read a number of papers offering QoS > > solutions in MANETs. Most of them > > assume that nodes somehow have an idea of the > > available bandwidth in their > > neighborhood and either pass this information around > > or make admission control > > decisions based on this information. The SWAN model > > computes bandwidth at a > > node by tapping all packet transmissions within the > > neighborhood of the node > > within a certain period of time and updating the > > estimate of the bandwidth > > being used based on that information. However, this > > does not capture the > > scenario where two nodes are within interfering > > range of each other but not in > > reception range. Are there any papers in this > > regard? > > > > thanks, > > Harpreet S. Arora > > > > Research Assistant, ITCSL > > Drexel University > > Philadelphia, PA-19104 > > Ph: 215-895-6198 > > > > > -------------------------------------------------------------------- > > Harpreet S. Arora > > Research Assistant, ITCSL > > Drexel University, > > Philadelphia, PA-19104 > > Ph. # 215-895-6198 > > http://www.pages.drexel.edu/~ha33 > > > ---------------------------------------------------------------------- > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > ________________________________________________________________________ > Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/ > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -- -bsm.. B.S.Manoj, Research Scholar, High Performance Computing and Networking Lab, CSE Dept., IIT Madras, India, Ph: 5330 (Internal calls only). -------------------------------------------------------------------------- It's lucky you're going so slowly, because you're going in the wrong direction. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 22 04:47:47 2003 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 EAA06104 for ; Tue, 22 Jul 2003 04:47: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 19esnm-0004XD-Sa for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 04:47:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6M8lIN6017430 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 04:47:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19esnm-0004X3-Le for manet-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 04:47: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 EAA06092 for ; Tue, 22 Jul 2003 04:47:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19esnj-0002gU-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 04:47:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19esne-0002gR-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 04:47:10 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19esnW-0004Sj-Oy; Tue, 22 Jul 2003 04:47:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eslW-0004LP-Ou for manet@optimus.ietf.org; Tue, 22 Jul 2003 04:44: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 EAA05968 for ; Tue, 22 Jul 2003 04:44:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19eslT-0002ei-00 for manet@ietf.org; Tue, 22 Jul 2003 04:44:55 -0400 Received: from smtp.eurecom.fr ([193.55.113.210]) by ietf-mx with esmtp (Exim 4.12) id 19eslI-0002dx-00 for manet@ietf.org; Tue, 22 Jul 2003 04:44:45 -0400 Received: from monza.eurecom.fr (localhost [127.0.0.1]) by smtp.eurecom.fr (8.12.1/8.12.1) with ESMTP id h6M8hYqh005004; Tue, 22 Jul 2003 10:43:36 +0200 (MEST) Received: from eurecom.fr (alloix.eurecom.fr [172.17.20.153]) by monza.eurecom.fr (Postfix) with ESMTP id EE1433C307; Tue, 22 Jul 2003 10:43:34 +0200 (MEST) Message-ID: <3F1CF936.9070803@eurecom.fr> Date: Tue, 22 Jul 2003 10:43:34 +0200 From: Lamia Romdhani Organization: Eurecom User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org, eroyer@alpha.ece.ucsb.edu, cperkins@iprg.nokia.com, idc@engineering.ucsb.edu Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [manet] AODV and packet delivery ratio Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi , I 'm doing some simulations on AODV protocol. I use ns-2.1b9a version that contains the same files of aodv code online in http://www.cs.sunysb.edu/~mahesh/aodv/ I get a low delivery fraction (%) with AODV when I use 20 or 30 node sources, about 55 % and 45 %, but with 10 sources I get 90 %. The causes are due to Drop IFQ and Drop route. However, in "Energy-Aware On-demand Routing for mobile Ad Hoc Networks"paper, the results are greater than 80% even for 20 or 30 sources. Is there any modifications that I should add in that code to get the same results. i'm waiting for any suggestions. Thank you. Lamia. PhD student. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 22 05:20:50 2003 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 FAA06787 for ; Tue, 22 Jul 2003 05:20: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 19etJo-0005lV-ED for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 05:20:24 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6M9KOjP022155 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 05:20:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19etJo-0005lG-B7 for manet-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 05:20: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 FAA06769 for ; Tue, 22 Jul 2003 05:20:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19etJl-0002rc-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 05:20:21 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19etJf-0002rZ-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 05:20:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19etJR-0005h9-Ly; Tue, 22 Jul 2003 05:20:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19etIX-0005gU-Hy for manet@optimus.ietf.org; Tue, 22 Jul 2003 05:19: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 FAA06765 for ; Tue, 22 Jul 2003 05:19:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19etIU-0002rM-00 for manet@ietf.org; Tue, 22 Jul 2003 05:19:02 -0400 Received: from concorde.inria.fr ([192.93.2.39]) by ietf-mx with esmtp (Exim 4.12) id 19etIE-0002rJ-00 for manet@ietf.org; Tue, 22 Jul 2003 05:18:46 -0400 Received: from zephyrin (byzantium.inria.fr [128.93.17.6]) by concorde.inria.fr (8.11.1/8.11.1) with SMTP id h6M9Hff11209; Tue, 22 Jul 2003 11:17:41 +0200 (MET DST) Message-ID: <001101c35032$d202eda0$1f175d80@inria.fr> From: "Philippe Jacquet" To: "Harpreet Arora" , References: <3F1C8EA4@webmail.drexel.edu> Subject: Re: [manet] bandwidth calculation at a node Date: Tue, 22 Jul 2003 11:22:49 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Content-Transfer-Encoding: 7bit Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hello, Harpreet, We have extended the available bandwidth calculation per node (or per link) up to an arbitrary number H_I of hops from the node. Interferences can extend much further than one hop. With IEEE 802.11 the interference range extend between two and three hops. However we prove in http://www.inria.fr/rrrt/rr-4876.html that the problem of finding a route that fits the bandwidth requirement of a new connection is NP hard in general as soon as H_I>0. We show example with slotted ad hoc TDMA networks. This result is in sharp contrast with wired network (H_I=0) where the finding of an optimal route is polynomial. Philippe ----- Original Message ----- From: Harpreet Arora To: Sent: Monday, July 21, 2003 10:18 PM Subject: [manet] bandwidth calculation at a node > Hi, > > I have read a number of papers offering QoS solutions in MANETs. Most of them > assume that nodes somehow have an idea of the available bandwidth in their > neighborhood and either pass this information around or make admission control > decisions based on this information. The SWAN model computes bandwidth at a > node by tapping all packet transmissions within the neighborhood of the node > within a certain period of time and updating the estimate of the bandwidth > being used based on that information. However, this does not capture the > scenario where two nodes are within interfering range of each other but not in > reception range. Are there any papers in this regard? > > thanks, > Harpreet S. Arora > > Research Assistant, ITCSL > Drexel University > Philadelphia, PA-19104 > Ph: 215-895-6198 > > -------------------------------------------------------------------- > Harpreet S. Arora > Research Assistant, ITCSL > Drexel University, > Philadelphia, PA-19104 > Ph. # 215-895-6198 > http://www.pages.drexel.edu/~ha33 > ---------------------------------------------------------------------- > > > _______________________________________________ > 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 Tue Jul 22 08:09:58 2003 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 IAA10709 for ; Tue, 22 Jul 2003 08:09:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19evxS-00047x-AR for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 08:09:30 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MC9UZw015861 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 08:09:30 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19evxS-00047k-7e for manet-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 08:09: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 IAA10694 for ; Tue, 22 Jul 2003 08:09:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19evxR-0003yC-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 08:09:29 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19evxL-0003y9-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 08:09:23 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19evmL-0003M5-LT; Tue, 22 Jul 2003 07:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19evlS-0003KF-LL for manet@optimus.ietf.org; Tue, 22 Jul 2003 07:57: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 HAA10447 for ; Tue, 22 Jul 2003 07:57:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19evlR-0003sf-00 for manet@ietf.org; Tue, 22 Jul 2003 07:57:05 -0400 Received: from web8105.mail.in.yahoo.com ([203.199.70.105] helo=web8105.in.yahoo.com) by ietf-mx with smtp (Exim 4.12) id 19evlG-0003sN-00 for manet@ietf.org; Tue, 22 Jul 2003 07:56:54 -0400 Message-ID: <20030722115542.38044.qmail@web8105.in.yahoo.com> Received: from [202.141.69.19] by web8105.mail.in.yahoo.com via HTTP; Tue, 22 Jul 2003 12:55:42 BST Date: Tue, 22 Jul 2003 12:55:42 +0100 (BST) From: =?iso-8859-1?q?Ash=20Mohammad=20Abbas?= Subject: Re: [manet] AODV and packet delivery ratio To: Lamia Romdhani , manet@ietf.org, eroyer@alpha.ece.ucsb.edu, cperkins@iprg.nokia.com, idc@engineering.ucsb.edu In-Reply-To: <3F1CF936.9070803@eurecom.fr> 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 This depends on how many runs you are having. If you keep no. of runs equal to 1, delivery ratio might be lower, but it may not a correct simulation result. For averaging purposes one should have around 10 runs for a single point. Wish you best, Abbas http://www.cse.iitd.ernet.in/~abbas --- Lamia Romdhani wrote: > Hi , > I 'm doing some simulations on AODV protocol. I use > ns-2.1b9a version > that contains the same files of aodv code online in > > http://www.cs.sunysb.edu/~mahesh/aodv/ > > I get a low delivery fraction (%) with AODV when I > use 20 or 30 node > sources, about 55 % > and 45 %, but with 10 sources I get 90 %. The > causes are due to Drop IFQ > and Drop route. > However, in "Energy-Aware On-demand Routing for > mobile Ad Hoc > Networks"paper, the results are greater than 80% > even for 20 or 30 sources. > Is there any modifications that I should add in > that code to get the > same results. > i'm waiting for any suggestions. > Thank you. > Lamia. > PhD student. > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet ________________________________________________________________________ Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 22 11:03:42 2003 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 LAA16632 for ; Tue, 22 Jul 2003 11:03:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eyfd-0002HM-Ay for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 11:03:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MF3HTU008756 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 11:03:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eyfd-0002H9-7n for manet-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 11:03: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 LAA16613 for ; Tue, 22 Jul 2003 11:03:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19eyfa-0005GF-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 11:03:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19eyfV-0005GC-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 11:03:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eyfN-0002G4-NM; Tue, 22 Jul 2003 11:03:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19eyeY-0002Fl-E4 for manet@optimus.ietf.org; Tue, 22 Jul 2003 11:02: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 LAA16551 for ; Tue, 22 Jul 2003 11:02:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19eyeV-0005Fu-00 for manet@ietf.org; Tue, 22 Jul 2003 11:02:07 -0400 Received: from smtp.eurecom.fr ([193.55.113.210]) by ietf-mx with esmtp (Exim 4.12) id 19eyeK-0005FI-00 for manet@ietf.org; Tue, 22 Jul 2003 11:01:57 -0400 Received: from monza.eurecom.fr (localhost [127.0.0.1]) by smtp.eurecom.fr (8.12.1/8.12.1) with ESMTP id h6MF0AG5015404; Tue, 22 Jul 2003 17:00:11 +0200 (MEST) Received: from eurecom.fr (alloix.eurecom.fr [172.17.20.153]) by monza.eurecom.fr (Postfix) with ESMTP id 129863C307; Tue, 22 Jul 2003 17:00:11 +0200 (MEST) Message-ID: <3F1D517A.8090403@eurecom.fr> Date: Tue, 22 Jul 2003 17:00:10 +0200 From: Lamia Romdhani Organization: Eurecom User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ash Mohammad Abbas Cc: manet@ietf.org, eroyer@alpha.ece.ucsb.edu, cperkins@iprg.nokia.com, idc@engineering.ucsb.edu Subject: Re: [manet] AODV and packet delivery ratio References: <20030722115542.38044.qmail@web8105.in.yahoo.com> Content-Type: multipart/alternative; boundary="------------010402060301060608000808" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------010402060301060608000808 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Thank you for your response, Of course the results that I have are the average of 10 runs. Ash Mohammad Abbas wrote: >This depends on how many runs you are having. If you >keep no. of runs equal to 1, delivery ratio might be >lower, but it may not a correct simulation result. For >averaging purposes one should have around 10 runs for >a single point. >Wish you best, >Abbas >http://www.cse.iitd.ernet.in/~abbas > > > > > > > > --- Lamia Romdhani wrote: > > >>Hi , >> I 'm doing some simulations on AODV protocol. I use >>ns-2.1b9a version >>that contains the same files of aodv code online in >> >> http://www.cs.sunysb.edu/~mahesh/aodv/ >> >> I get a low delivery fraction (%) with AODV when I >>use 20 or 30 node >> sources, about 55 % >> and 45 %, but with 10 sources I get 90 %. The >>causes are due to Drop IFQ >> and Drop route. >> However, in "Energy-Aware On-demand Routing for >>mobile Ad Hoc >> Networks"paper, the results are greater than 80% >>even for 20 or 30 sources. >> Is there any modifications that I should add in >>that code to get the >> same results. >> i'm waiting for any suggestions. >> Thank you. >> Lamia. >> PhD student. >> >> >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> > > >________________________________________________________________________ >Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/ > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > > --------------010402060301060608000808 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Thank you for your response,
Of course the results that I have are the average of 10 runs.

Ash Mohammad Abbas wrote:
This depends on how many runs you are having. If you
keep no. of runs equal to 1, delivery ratio might be
lower, but it may not a correct simulation result. For
averaging purposes one should have around 10 runs for
a single point.
Wish you best,
Abbas
http://www.cse.iitd.ernet.in/~abbas







 --- Lamia Romdhani <Lamia.Romdhani@eurecom.fr> wrote:
  
Hi ,
 I 'm doing some simulations on AODV protocol. I use
ns-2.1b9a version 
that contains the same files of aodv code online in
 
 http://www.cs.sunysb.edu/~mahesh/aodv/
 
 I get a low delivery fraction (%) with AODV when I
use 20 or 30 node 
 sources, about 55 %
 and 45 %, but with 10 sources I get 90 %. The
causes are due to Drop IFQ 
 and Drop route.
 However, in  "Energy-Aware On-demand Routing for
mobile Ad Hoc 
 Networks"paper, the results are greater than 80%
even for 20 or 30 sources.
 Is there any modifications that I should add in
that code to get the 
 same results.
 i'm waiting for  any suggestions.
 Thank you.
 Lamia.
 PhD student.



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


________________________________________________________________________
Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/

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

--------------010402060301060608000808-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 22 14:02:43 2003 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 OAA21045 for ; Tue, 22 Jul 2003 14:02:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f1Sq-0000x2-Ge for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 14:02:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MI2Gsg003650 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 14:02:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f1Sq-0000wn-CG for manet-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 14:02: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 OAA21035 for ; Tue, 22 Jul 2003 14:02:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f1So-0006Jx-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 14:02:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19f1Si-0006Ju-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 14:02:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f1Sc-0000sU-3i; Tue, 22 Jul 2003 14:02:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f1SM-0000sE-AY for manet@optimus.ietf.org; Tue, 22 Jul 2003 14:01: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 OAA21028 for ; Tue, 22 Jul 2003 14:01:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f1SJ-0006Jb-00 for manet@ietf.org; Tue, 22 Jul 2003 14:01:43 -0400 Received: from web41407.mail.yahoo.com ([66.218.93.73]) by ietf-mx with smtp (Exim 4.12) id 19f1S8-0006JB-00 for manet@ietf.org; Tue, 22 Jul 2003 14:01:33 -0400 Message-ID: <20030722180033.6155.qmail@web41407.mail.yahoo.com> Received: from [137.73.11.84] by web41407.mail.yahoo.com via HTTP; Tue, 22 Jul 2003 19:00:33 BST Date: Tue, 22 Jul 2003 19:00:33 +0100 (BST) From: =?iso-8859-1?q?karatam=20nagavenkata?= To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Transfer-Encoding: 8bit Subject: [manet] changing the default bandwidth Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 hai every one I am trying to change the default bandwidth between two wireless nodes.could any one know how to change the default bandwidth of 802.11. I tried changing /ns-allinone-2.1b9a/ns-2.1b9a/tcl/lan/mac.tcl but it does'nt work I appreciate if some one can help me regards swamy ________________________________________________________________________ Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 22 16:03:47 2003 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 QAA25224 for ; Tue, 22 Jul 2003 16:03: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 19f3M0-0006k6-0q for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 16:03:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6MK3JMM025914 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 16:03:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f3Lz-0006jt-Ty for manet-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 16: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 QAA25194 for ; Tue, 22 Jul 2003 16:03:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f3Ly-00074q-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 16:03:18 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19f3Ls-00074m-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 16:03:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f3Lh-0006i9-UN; Tue, 22 Jul 2003 16:03:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f3LT-0006ha-L9 for manet@optimus.ietf.org; Tue, 22 Jul 2003 16:02: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 QAA25174 for ; Tue, 22 Jul 2003 16:02:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f3LS-00074C-00 for manet@ietf.org; Tue, 22 Jul 2003 16:02:46 -0400 Received: from letters.cs.ucsb.edu ([128.111.41.13]) by ietf-mx with esmtp (Exim 4.12) id 19f3LG-000743-00 for manet@ietf.org; Tue, 22 Jul 2003 16:02:35 -0400 Received: from yosemite.cs.ucsb.edu (yosemite [128.111.40.103]) by letters.cs.ucsb.edu (8.11.7+Sun/8.11.6) with ESMTP id h6MJwAS23293; Tue, 22 Jul 2003 12:58:10 -0700 (PDT) Subject: Re: [manet] AODV and packet delivery ratio From: Elizabeth Belding-Royer To: Lamia Romdhani Cc: Ash Mohammad Abbas , manet@ietf.org, ebelding@cs.ucsb.edu, cperkins@iprg.nokia.com, idc@engineering.ucsb.edu In-Reply-To: <3F1D517A.8090403@eurecom.fr> References: <20030722115542.38044.qmail@web8105.in.yahoo.com> <3F1D517A.8090403@eurecom.fr> Content-Type: text/plain Message-Id: <1058903893.30566.3.camel@yosemite.cs.ucsb.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 22 Jul 2003 12:58:13 -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 I recommend you use the AODV-UU NS-2 code for simulating AODV. The code you are using is a bit outdated (though that doesn't really explain why your results are so poor). The AODV_UU code can be found on the AODV website: http://moment.cs.ucsb.edu/AODV Elizabeth On Tue, 2003-07-22 at 08:00, Lamia Romdhani wrote: > Thank you for your response, > Of course the results that I have are the average of 10 runs. > > Ash Mohammad Abbas wrote: > > This depends on how many runs you are having. If you > > keep no. of runs equal to 1, delivery ratio might be > > lower, but it may not a correct simulation result. For > > averaging purposes one should have around 10 runs for > > a single point. > > Wish you best, > > Abbas > > http://www.cse.iitd.ernet.in/~abbas > > > > > > > > > > > > > > > > --- Lamia Romdhani wrote: > > > > > Hi , > > > I 'm doing some simulations on AODV protocol. I use > > > ns-2.1b9a version > > > that contains the same files of aodv code online in > > > > > > http://www.cs.sunysb.edu/~mahesh/aodv/ > > > > > > I get a low delivery fraction (%) with AODV when I > > > use 20 or 30 node > > > sources, about 55 % > > > and 45 %, but with 10 sources I get 90 %. The > > > causes are due to Drop IFQ > > > and Drop route. > > > However, in "Energy-Aware On-demand Routing for > > > mobile Ad Hoc > > > Networks"paper, the results are greater than 80% > > > even for 20 or 30 sources. > > > Is there any modifications that I should add in > > > that code to get the > > > same results. > > > i'm waiting for any suggestions. > > > Thank you. > > > Lamia. > > > PhD student. > > > > > > > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > > ________________________________________________________________________ > > Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/ > > > > _______________________________________________ > > 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 Tue Jul 22 22:54:51 2003 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 WAA03795 for ; Tue, 22 Jul 2003 22:54:51 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f9lp-0002eb-U1 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 22:54:26 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6N2sPsD010198 for manet-archive@odin.ietf.org; Tue, 22 Jul 2003 22:54:25 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f9lo-0002eP-8V for manet-web-archive@optimus.ietf.org; Tue, 22 Jul 2003 22:54: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 WAA03752 for ; Tue, 22 Jul 2003 22:54:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f9lk-00017g-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 22:54:20 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19f9lf-00017d-00 for manet-web-archive@ietf.org; Tue, 22 Jul 2003 22:54:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19f9lS-0002ap-1f; Tue, 22 Jul 2003 22: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 19f9l8-0002aY-BK for manet@optimus.ietf.org; Tue, 22 Jul 2003 22:53: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 WAA03748 for ; Tue, 22 Jul 2003 22:53:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19f9l4-00017V-00 for manet@ietf.org; Tue, 22 Jul 2003 22:53:38 -0400 Received: from pec.etri.re.kr ([129.254.114.50]) by ietf-mx with esmtp (Exim 4.12) id 19f9kt-00017S-00 for manet@ietf.org; Tue, 22 Jul 2003 22:53:27 -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 h6N363S29026; Wed, 23 Jul 2003 12:06:03 +0900 (KST) Message-ID: <00d001c350c5$56d2c9a0$c470fe81@etri.re.kr> From: "Jaehoon Paul Jeong" To: "Charlie Perkins" Cc: "MANET WG" References: <005101c34cc9$83ce2ad0$14f3a051@etri.re.kr> <3F17B1B4.8010904@iprg.nokia.com> Subject: Re: [manet] Answer to a question in Ad Hoc IP Address Autoconfiguration Date: Wed, 23 Jul 2003 11:51:39 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" 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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 SGkgQ2hhcmxpZSBQLg0KDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIkNo YXJsaWUgUGVya2lucyIgPGNoYXJsaWVwQElQUkcubm9raWEuY29tPg0KVG86ICJKYWVob29uIEpl b25nIiA8cGF1bEBldHJpLnJlLmtyPg0KQ2M6ICJNQU5FVCBXRyIgPG1hbmV0QGlldGYub3JnPg0K U2VudDogRnJpZGF5LCBKdWx5IDE4LCAyMDAzIDU6MzcgUE0NClN1YmplY3Q6IFJlOiBbbWFuZXRd IEFuc3dlciB0byBhIHF1ZXN0aW9uIGluIEFkIEhvYyBJUCBBZGRyZXNzIEF1dG9jb25maWd1cmF0 aW9uDQoNCg0KPiANCj4gDQo+IEhlbGxvIEphZWhvb24gUGF1bCwNCj4gDQo+IFRoYW5rcyBmb3Ig eW91ciBleHBsYW5hdGlvbiwgbm93IEkgdW5kZXJzdGFuZC4NCj4gDQo+IFRoZSBzb2x1dGlvbiBw bGFjZXMgYSByZXF1aXJlbWVudCBmb3IgYSBuZXcgZmllbGQgaW4gdGhlDQo+IHJvdXRpbmcgdGFi bGUgLS0gbmFtZWx5LCB0aGUgaW5jbHVzaW9uIG9mIGEgImtleSIgZmllbGQuDQo+IA0KUmlnaHQu DQoNCj4gSSBndWVzcyB0aGVyZSBpc24ndCBhbnkgcHJvdGVjdGlvbiBhZ2FpbnN0IGFjY2lkZW50 YWwNCj4gY2FzZXMgd2hlcmUgdGhlIHR3byBjb250ZW5kZXJzIGZvciAgQS5CLkMuRCAgaGFwcGVu DQo+IHRvIHNlbGVjdCB0aGUgc2FtZSB2YWx1ZSBmb3IgImtleSIuICBUaGF0IHNob3VsZCBiZSBP LksuDQo+IGFzIGxvbmcgYXMgKGkpIHRoZSBrZXkgaXMgX2xvbmdfIChpbiBiaXRzKSwgIGFuZCAo aWkpIHRoZQ0KPiBub2RlcyBhcmUgcXVpdGUgY2FwYWJsZSBvZiBwcm9kdWNpbmcgdHJ1bHkgcmFu ZG9tDQo+IG51bWJlcnMuICANCkN1cnJlbnRseSwgdGhlcmUgaXMgbm8gcHJvdGVjdGlvbiBhZ2Fp bnQgdGhlIHNpbXVsdGFuZW91cyBjb25mbGljdCBvZiBhZGRyZXNzIGFuZCBrZXkuDQpJIGFzc3Vt ZWQgdGhlIHBvc3NpYmlsaXR5IG9mIHRoYXQgY2FzZSBpcyB2ZXJ5IGxvdyBhcyB5b3Ugc3VnZ2Vz dGVkLg0KDQo+IEFsc28sIEkgbm90aWNlIHRoYXQgdGhlIGludGVybWVkaWF0ZSByb3V0aW5nDQo+ IHBvaW50cyBhbHNvIGhhdmUgdG8gbWFpbnRhaW4gdGhlICJrZXkiIHZhbHVlIGZvciB0aGUNCj4g dHdvIGVuZHBvaW50cywgYXQgbGVhc3QgZHVyaW5nIGFkZHJlc3MgZGlzY292ZXJ5Lg0KPiANClll cy4gDQpJIGFtIHRoaW5raW5nIG92ZXIgYW5vdGhlciB3YXkgdG8gcmVwbGFjZSBXZWFrIERBRCwg d2hpY2ggZG9lcyBub3QgdXNlIGFkZGl0aW9uYWwga2V5IA0KZm9yIGFkZHJlc3MgZHVwbGljYXRp b24gZGV0ZWN0aW9uLiANCkkgYW0gaW52ZXN0aWdhdGluZyB3aGV0aGVyICJPcmlnaW5hdG9yIFNl cXVlbmNlIE51bWJlciIgb2YgUlJFUSBjYW4gYmUgdXNlZCBpbnN0ZWFkIG9mIGtleSBvciBub3Qu DQpIb3cgYWJvdXQ/DQoNCi9KYWVob29uIFBhdWwNCg0KPiBSZWdhcmRzLA0KPiBDaGFybGllIFAu DQo+IA0KPiANCj4gSmFlaG9vbiBKZW9uZyB3cm90ZToNCj4gDQo+ID5EZWFyIENoYXJsZXMgUGVy a2lucywNCj4gPg0KPiA+SW4gbXkgdGFsayBvZiB0aGlzIElFVEYgbWVldGluZywgeW91IGFza2Vk IGhvdyBBRVJSIG1lc3NhZ2UgaXMgZGVsaXZlcmVkIA0KPiA+ZnJvbSBvbmUgbW9iaWxlIG5vZGUg dG8gYW5vdGhlciB3aGljaCBoYXZlIGR1cGxpY2F0ZSBhZGRyZXNzZXMgZHVyaW5nIHdlYWsgREFE LiANCj4gPkZvciBleGFtcGxlLCBsb29rIGF0IHRoZSBGaWcgMSwgd2hlcmUgTUFORVQgcGFydGl0 aW9uIGNvbnNpc3Qgb2YgZm91ciBub2Rlcy4NCj4gPg0KPiA+ICAgICAgIE1OLTEgPC0tLS0tPiBN Ti0yIDwtLS0tLT4gTU4tMyA8LS0tLS0+IE1OLTQNCj4gPiAoQS5CLkMuRCwga2V5LTEpICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAoQS5CLkMuRCwga2V5LTQpDQo+ID4g ICAgICAgICANCj4gPiAgRmlnIDEuIEFkZHJlc3MgRHVwbGljYXRpb24gZHVyaW5nIGFkIGhvYyBy b3V0aW5nIChvciBXZWFrIERBRCkNCj4gPiANCj4gPkhvdyBkb2VzIE1OLTQgaW5mb3JtIE1OLTEg b2YgYWRkcmVzcyBkdXBsaWNhdGlvbiB0aHJvdWdoIEFFUlIgbWVzc2FnZQ0KPiA+d2hpbGUgTU4t MSBwZXJmb3JtcyB0aGUgcm91dGUgZGlzY292ZXJ5KFJSRVEpIG9mIGEgZGVzdGluYXRpb24gDQo+ ID53aXRoIGl0cyBzb3VyY2UgYWRkcmVzcyAiQS5CLkMuRCI/DQo+ID5SUkVRIGNvbnRhaW5zIGl0 cyBzb3VyY2UgYWRkcmVzcyBhbmQga2V5Lg0KPiA+TU4tNCByZWNlaXZlcyBhbiBSUkVRIGZyb20g TU4tMSBhbmQgZmluZHMgb3V0IGFkZHJlc3MgZHVwbGljYXRpb24sDQo+ID5iZWNhdXNlIHRoZSBz b3VyY2UgYWRkcmVzcyBvZiBSUkVRIGlzIHRoZSBzYW1lIGFzIE1OLTQncyBidXQgdGhlIGtleXMg YXJlIGRpZmZlcmVudC4NCj4gPg0KPiA+SW4gV2VhayBEQUQsIHRoZSBmb3J3YXJkaW5nIGlzIGJh c2VkIG9uIHRoZSBwYWlyIG9mIElQIGFkZHJlc3MgYW5kIGtleS4gDQo+ID5NTi0zIGhhcyB0d28g aG9zdCByb3V0ZXMgb2YgYWRkcmVzcyAiQS5CLkMuRCIgaW4gdGhlIG1vbWVudCB0aGF0IE1OLTMg Zm9yd2FyZHMNCj4gPk1OLTQncyBBRVJSIG1lc3NhZ2UgdG93YXJkIE1OLTEgbGlrZSBUYWJsZSAx Lg0KPiA+DQo+ID4gIFRhYmxlIDEuIFJvdXRpbmcgVGFibGUgb2YgTU4tMw0KPiA+DQo+ID4gICAt LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+ICB8ICAg ICAgRGVzdCAgICAgICB8IERlc3QgS2V5IHwgTmV4dCBIb3AgfCBEaXN0YW5jZSB8DQo+ID4gICAt LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiA+ICB8ICAg QS5CLkMuRCAgIHwgICAga2V5LTQgICAgfCAgIE1OLTQgICAgfCAgICAgIDEgICAgICB8DQo+ID4g IHwgICBBLkIuQy5EICAgfCAgICBrZXktMSAgICB8ICAgTU4tMiAgICB8ICAgICAgMiAgICAgIHwg LT4gcHJlY3Vyc29yIGZvciBmb3J3YXJkaW5nIFJSRVAgbWVzc2FnZQ0KPiA+ICAgICAgIC4uLi4N Cj4gPg0KPiA+VGhyb3VnaCB0aGUgZm9yd2FyZGluZyBiYXNlZCBvbiBJUCBhZGRyZXNzIGFuZCBr ZXksIHRoZSBBRVJSIGZyb20gTU4tNCB3aWxsIGJlIGRlbGl2ZXJlZCB0byBNTi0xLg0KPiA+VGhp cyBpcyBteSBhbnN3ZXIgOi0pDQo+ID5JcyB0aGVyZSBhbnkgbW9yZSBxdWVzdGlvbiBhbmQgY29t bWVudHM/DQo+ID4NCj4gPlJlZ2FyZHMsDQo+ID5KYWVob29uIFBhdWwNCj4gPn9/f39/f39/f39/ f39/f39/f39/f39/f39/f39/f39/f39/Zmp3LRkoJQ0KPiB4JQ0KPiBLZmp3LX4nLT96KwIbbSZP f38gMFd4HjV/aC4PZmopZmo/ZQ0KPiBLYh16PxkpXg0KPiA+ICANCj4gPg0KPiANCj4g _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 23 02:20:56 2003 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 CAA22677 for ; Wed, 23 Jul 2003 02:20:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fCzE-0001yZ-Ql for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 02:20:28 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6N6KSXg007581 for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 02:20:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fCzD-0001yC-LN for manet-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 02:20: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 CAA22134 for ; Wed, 23 Jul 2003 02:20:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fCz9-00028v-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 02:20:23 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fCz4-00028s-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 02:20:18 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fCyo-0001tR-AV; Wed, 23 Jul 2003 02: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 19fCyQ-0001sD-BO for manet@optimus.ietf.org; Wed, 23 Jul 2003 02:19: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 CAA21275 for ; Wed, 23 Jul 2003 02:19:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fCyM-00028d-00 for manet@ietf.org; Wed, 23 Jul 2003 02:19:34 -0400 Received: from web8107.mail.in.yahoo.com ([203.199.70.121]) by ietf-mx with smtp (Exim 4.12) id 19fCyB-00028M-00 for manet@ietf.org; Wed, 23 Jul 2003 02:19:23 -0400 Message-ID: <20030723061821.17302.qmail@web8107.mail.in.yahoo.com> Received: from [202.141.69.127] by web8107.mail.in.yahoo.com via HTTP; Wed, 23 Jul 2003 07:18:21 BST Date: Wed, 23 Jul 2003 07:18:21 +0100 (BST) From: =?iso-8859-1?q?Ash=20Mohammad=20Abbas?= Subject: Re: [manet] changing the default bandwidth To: karatam nagavenkata , manet@ietf.org In-Reply-To: <20030722180033.6155.qmail@web41407.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 I suggest you should change default bandwidth in the source code i.e., .cc file. Wish you best Abbas http://www.cse.iitd.ernet.in/~abbas --- karatam nagavenkata wrote: > hai every one > I am trying to change the default bandwidth between > two wireless nodes.could any one know how to change > the default bandwidth of 802.11. > I tried changing > /ns-allinone-2.1b9a/ns-2.1b9a/tcl/lan/mac.tcl > but it does'nt work > I appreciate if some one can help me > regards > swamy > > ________________________________________________________________________ > Want to chat instantly with your online friends? > Get the FREE Yahoo! > Messenger http://uk.messenger.yahoo.com/ > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet ________________________________________________________________________ Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 23 04:31:50 2003 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 EAA05863 for ; Wed, 23 Jul 2003 04:31: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 19fF1u-00084n-AJ for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 04:31:22 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6N8VLoZ031045 for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 04:31:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fF1s-00084e-OE for manet-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 04:31: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 EAA05850 for ; Wed, 23 Jul 2003 04:31:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fF1p-00036n-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 04:31:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fF1k-00036k-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 04:31:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fF1Z-00080l-3e; Wed, 23 Jul 2003 04:31:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fF0w-0007zq-R3 for manet@optimus.ietf.org; Wed, 23 Jul 2003 04:30: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 EAA05782 for ; Wed, 23 Jul 2003 04:30:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fF0u-000360-00 for manet@ietf.org; Wed, 23 Jul 2003 04:30:20 -0400 Received: from reserv1.univ-lille1.fr ([193.49.225.15] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19fF0i-00035g-00 for manet@ietf.org; Wed, 23 Jul 2003 04:30:09 -0400 Received: from malonne.lifl.fr (malonne.lifl.fr [134.206.10.29]) by reserv1.univ-lille1.fr (8.12.9/jtpda-5.3.1) with ESMTP id h6N8Th91017112 for ; Wed, 23 Jul 2003 10:29:43 +0200 Received: from KRIEK (kriek.lifl.fr [134.206.11.16]) by malonne.lifl.fr with ESMTP id h6N8Tgc05729 for ; Wed, 23 Jul 2003 10:29:42 +0200 (MEST) From: "David Simplot" To: Date: Wed, 23 Jul 2003 10:31:18 +0200 Organization: IRCICA/LIFL, Univ. Lille 1 Message-ID: <001001c350f4$ca14f800$100bce86@lifl.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-MailScanner: Found to be clean Content-Transfer-Encoding: quoted-printable Subject: [manet] CFP IEEE Network Magazine special issue on 'Ad hoc Networking: Data Communications & Topology Control' Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 Please accept our apologies in case you receive this information from multiple sources.=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Call for Papers IEEE Network Magazine Special Issue on 'AD HOC NETWORKING: DATA COMMUNICATIONS & TOPOLOGY CONTROL' http://www.comsoc.org/pubs/net/ntwrk/special.html IEEE Network seeks articles for a special issue on Ad Hoc Networking: Data Communications and Topology Control, to appear in July 2004. The guest editors for this special issue are David Simplot, Universit=E9 de Lille, France, and Ivan Stojmenovic, University of Ottawa, Canada. Purpose Wireless networks and mobile computing research has until recently concentrated on single-hop networks (network nodes communicating directly to a fixed infrastructure), such as cellular and satellite systems. Ad hoc networking covers multi-hop scenarios (network nodes communicating via other network nodes) such as conference, hospital, battlefield, rescue, and monitoring scenarios. Particular ad hoc network systems include packet radio networks, sensor networks, personal communication systems, rooftop networks, and wireless local area networks. Even multi-hop cellular networks may be a viable option when a huge number of cellular phones are concentrated on a small area such as stadium. This special issue will cover comprehensively the network layer in ad hoc networks, which deals with data communication and topology control problems. Data communication problems include routing, broadcasting, multicasting, geocasting, clustering, area monitoring, data and service access. Topology control problems include neighbor discovery, topology construction and maintenance, activity scheduling, position discovery, partition detection, location updates, and network management. The new approaches to ad hoc networks design emphasize cross-layering approach, and therefore the relevant issues arising from network layer problems will also be covered, such as power management, security, quality of service, performance evaluation, data link and transport layers. The goal of the special issue is to publish original research and review articles which should be comprehensive to all readers, regardless of their specialty. Manuscript submission Send papers as PDF file to both co-guest editors simplot@lifl.fr and ivan@site.uottawa.ca. It is recommended that submissions be limited to 4500 words, with the number of references limited to 10. Guidelines for authors can be found on the IEEE Network magazine Website at http://www.comsoc.org/pubs/net/ntwrk/authors.html . Important dates Manuscript Submission: November 30, 2003 Acceptance Notification: February 29, 2004 Final Manuscript Due: May 1, 2004 Publication: July/August 2004 Guest co-editors Dr. David Simplot IRCICA/LIFL, Univ. Lille 1, France David.Simplot@lifl.fr Dr. Ivan Stojmenovic SITE, University of Ottawa, Canada ivan@site.uottawa.ca _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 23 11:25:49 2003 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 LAA16761 for ; Wed, 23 Jul 2003 11:25:49 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLUX-0006vf-O9 for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 11:25:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6NFPLNF026632 for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 11:25:21 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLUX-0006vT-JW for manet-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 11:25: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 LAA16738 for ; Wed, 23 Jul 2003 11:25:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fLUW-0005Qu-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 11:25:20 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fLUR-0005Qr-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 11:25:15 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLUE-0006uF-50; Wed, 23 Jul 2003 11:25:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fLTX-0006tt-NZ for manet@optimus.ietf.org; Wed, 23 Jul 2003 11:24: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 LAA16727 for ; Wed, 23 Jul 2003 11:24:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fLTW-0005Qd-00 for manet@ietf.org; Wed, 23 Jul 2003 11:24:18 -0400 Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx with esmtp (Exim 4.12) id 19fLTM-0005Pt-00 for manet@ietf.org; Wed, 23 Jul 2003 11:24:08 -0400 Received: from zidane.cc.vt.edu (IDENT:mirapoint@evil-zidane [10.1.1.13]) by lennier.cc.vt.edu (8.12.8/8.12.8) with ESMTP id h6NFMfvt332794 for ; Wed, 23 Jul 2003 11:22:41 -0400 (EDT) Received: from tom ([198.70.228.75]) by zidane.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BRF92276 (AUTH talin); Wed, 23 Jul 2003 11:22:34 -0400 (EDT) Message-ID: <001b01c3512e$4016fe20$2502a8c0@tom> From: "Tao Lin" To: "manet" Cc: Date: Wed, 23 Jul 2003 11:22:37 -0400 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.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Transfer-Encoding: 7bit Subject: [manet] New Release of the MANET Emulation Tool Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sorry to bother others who are not interested. We have released version 2.0 of our MANET emulation tool, the dynamic switch, at http://sourceforge.net/projects/dynamic-switch. It is based on Red Hat 9.0 (2.4.20-8 kernel). The basic features are as follows. 1. Emulate MANET topology changes in a wired (Ethernet) test bed. The dynamic switch is designed to switch datagrams based on the incoming network interface. The switch does not check the IP or MAC address of datagrams. It forwards the datagrams to the proper outgoing network interface(s) based on a user-defined connectivity table. All end hosts (emulated mobile nodes) connect to the dynamic switch via cross-over cables. Users can control the connectivity among end hosts at the dynamic switch via input-commands or scripts. Note that there is no need for special configuration or emulation software at the end hosts and there is no restriction of the operating system and other software used at the end hosts. 2. Switch between normal Linux box and the dynamic switch. The software uses a loadable module, which means users can load this software and change the normal Linux box into a dynamic switch or unload the module and convert the dynamic switch back to a normal machine. There is also an option to set individual network cards back to normal mode. 3. Emulate limited bandwidth and packet loss. The dynamic switch can emulate bandwidth limitations using the leaky-token-bucket model. The dynamic switch can also emulate packet loss according to a specified packet drop rate using different probability distributions. 4. Requires only a single kernel recompilation. Users can update the number of network cards after the installation. The software will detect them when it is loaded. Please check the Install-howto and Readme first once you download it. Thanks! Tao Lin Ph.D Candidate Virginia Tech Lab for Advanced Networking (VT LAN) ECE Dept. Virginia Tech _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 23 12:45:41 2003 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 MAA19312 for ; Wed, 23 Jul 2003 12:45:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fMjr-0002pP-Fg for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 12:45:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6NGjFYW010865 for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 12:45:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fMjr-0002pA-Bs for manet-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 12:45: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 MAA19296 for ; Wed, 23 Jul 2003 12:45:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fMjp-00064J-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 12:45:13 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fMjk-00064G-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 12:45:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fMjd-0002lL-H7; Wed, 23 Jul 2003 12:45:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fMjC-0002l1-At for manet@optimus.ietf.org; Wed, 23 Jul 2003 12:44: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 MAA19291 for ; Wed, 23 Jul 2003 12:44:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fMjA-00063j-00 for manet@ietf.org; Wed, 23 Jul 2003 12:44:32 -0400 Received: from mta6.adelphia.net ([64.8.50.190]) by ietf-mx with esmtp (Exim 4.12) id 19fMj0-00063c-00 for manet@ietf.org; Wed, 23 Jul 2003 12:44:22 -0400 Received: from angel ([68.70.61.77]) by mta6.adelphia.net (InterMail vM.5.01.05.32 201-253-122-126-132-20030307) with SMTP id <20030723164331.IYSV20440.mta6.adelphia.net@angel> for ; Wed, 23 Jul 2003 12:43:31 -0400 From: "George Hadjichristofi" To: Date: Wed, 23 Jul 2003 12:43:02 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" 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) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 7bit Subject: [manet] routing protocols-- spoofed IP Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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, Are there any routing protocols that can detect or provide protection against spoofed IP addresses? Thanks George *********************************************************** George C. Hadjichristofi Graduate Student Bradley Department of Electrical and Computer Engineering Virginia Tech,Blacksburg,VA 24061,U.S.A TEL:(540)-951-8936 *********************************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 23 13:46:45 2003 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 NAA21027 for ; Wed, 23 Jul 2003 13:46: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 19fNgv-0005VU-JK for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 13:46:17 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6NHkHLM021162 for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 13:46:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fNgv-0005VE-Dc for manet-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 13:46: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 NAA20987 for ; Wed, 23 Jul 2003 13:46:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fNgt-0006Pz-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 13:46:15 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fNgn-0006Pw-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 13:46:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fNgf-0005R7-3o; Wed, 23 Jul 2003 13:46:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fNgZ-0005Qe-RJ for manet@optimus.ietf.org; Wed, 23 Jul 2003 13:45: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 NAA20970 for ; Wed, 23 Jul 2003 13:45:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fNgX-0006Pc-00 for manet@ietf.org; Wed, 23 Jul 2003 13:45:53 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx with esmtp (Exim 4.12) id 19fNgM-0006Ol-00 for manet@ietf.org; Wed, 23 Jul 2003 13:45:42 -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 h6NHipDi009822; Wed, 23 Jul 2003 13:44:51 -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 h6NHioKN003579; Wed, 23 Jul 2003 13:44:50 -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 M2003072313445029893 ; Wed, 23 Jul 2003 13:44:50 -0400 Message-Id: <5.1.1.5.2.20030723134226.03c6c248@pop.itd.nrl.navy.mil> X-Sender: macker@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 Date: Wed, 23 Jul 2003 13:44:46 -0400 To: "George Hadjichristofi" , From: Joe Macker Subject: Re: [manet] routing protocols-- spoofed IP In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , At 12:43 PM 7/23/2003 -0400, George Hadjichristofi wrote: >Hi, > >Are there any routing protocols that can detect or provide protection >against spoofed IP addresses? There are authentication methods one can think of applying to messaging. Hopefully ones that also protect against replay,etc. Is this what you mean? You might want to check the routing security working group which is working the more general problem of routing security. >Thanks >George > > >*********************************************************** >George C. Hadjichristofi >Graduate Student >Bradley Department of Electrical and Computer Engineering >Virginia Tech,Blacksburg,VA 24061,U.S.A >TEL:(540)-951-8936 >*********************************************************** > > >_______________________________________________ >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 Jul 23 15:11:03 2003 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 PAA24670 for ; Wed, 23 Jul 2003 15:11:03 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fP0W-0000v4-OP for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 15:10:37 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6NJAa50003530 for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 15:10:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fP0W-0000ur-LZ for manet-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 15:10: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 PAA24614 for ; Wed, 23 Jul 2003 15:10:32 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fP0T-00073T-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 15:10:33 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fP0O-00073Q-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 15:10:28 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fOzy-0000r1-49; Wed, 23 Jul 2003 15: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 19fOzJ-0000qK-Qx for manet@optimus.ietf.org; Wed, 23 Jul 2003 15:09: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 PAA24489 for ; Wed, 23 Jul 2003 15:09:17 -0400 (EDT) From: Claude.Castelluccia@inrialpes.fr Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fOzG-000732-00 for manet@ietf.org; Wed, 23 Jul 2003 15:09:18 -0400 Received: from mx-serv.inrialpes.fr ([194.199.18.100]) by ietf-mx with esmtp (Exim 4.12) id 19fOz5-00072A-00 for manet@ietf.org; Wed, 23 Jul 2003 15:09:07 -0400 Received: from imap-serv.inrialpes.fr (imap-serv.inrialpes.fr [194.199.18.72]) by mx-serv.inrialpes.fr (8.12.8/8.12.8) with ESMTP id h6NJ7HDv014486; Wed, 23 Jul 2003 21:07:17 +0200 (MEST) Received: (from nobody@localhost) by imap-serv.inrialpes.fr (8.11.6/8.11.3/ImagV2) id h6NJ7Ip22855; Wed, 23 Jul 2003 21:07:18 +0200 (MEST) X-Authentication-Warning: imap-serv.inrialpes.fr: nobody set sender to ccastel@inrialpes.fr using -f Received: from 128.200.38.88 ( [128.200.38.88]) as user ccastel@imap-serv.inrialpes.fr by imap-serv.inrialpes.fr with HTTP; Wed, 23 Jul 2003 21:07:18 +0200 Message-ID: <1058987238.3f1edce62fb8c@imap-serv.inrialpes.fr> Date: Wed, 23 Jul 2003 21:07:18 +0200 To: George Hadjichristofi Cc: manet@ietf.org Subject: Re: [manet] routing protocols-- spoofed IP References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 User-Agent: Internet Messaging Program (IMP) 3.1 X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: McAfee uvscan 4241 RBL+ ORBS Found to be clean Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mx-serv.inrialpes.fr id h6NJ7HDv014486 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 Quoting George Hadjichristofi : > Hi, >=20 > Are there any routing protocols that can detect or provide protection > against spoofed IP addresses? >=20 Hello, One solution is to use Crypto. Generated Addresses... CGA are currently being used to secure MIPv6 and ND. They can also be used in MANET to secure the routing protocol. We actually applied them to secure AODVv6 but they can actually be used with any protocols... You can read: =A8Protecting AODV against impersonation attacks=A8 http://portal.acm.org/citation.cfm?id=3D581313&coll=3Dportal&dl=3DACM&ret= =3D1#Fulltext hope this help... Claude. > Thanks > George >=20 >=20 > *********************************************************** > George C. Hadjichristofi > Graduate Student > Bradley Department of Electrical and Computer Engineering > Virginia Tech,Blacksburg,VA 24061,U.S.A > TEL:(540)-951-8936 > *********************************************************** >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 >=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 23 16:10:14 2003 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 QAA00674 for ; Wed, 23 Jul 2003 16:10:14 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fPvn-000469-1a for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 16:09:47 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6NK9l8h015747 for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 16:09:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fPvm-00045u-TM for manet-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 16:09:46 -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 QAA00650 for ; Wed, 23 Jul 2003 16:09:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fPv3-00041o-TA; Wed, 23 Jul 2003 16:09:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fPun-00041Y-Mi for manet@optimus.ietf.org; Wed, 23 Jul 2003 16:08: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 QAA00616 for ; Wed, 23 Jul 2003 16:08:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fPum-0000O3-00 for manet@ietf.org; Wed, 23 Jul 2003 16:08:44 -0400 Received: from mailhost.iprg.nokia.com ([205.226.5.12]) by ietf-mx with esmtp (Exim 4.12) id 19fPua-0000NT-00 for manet@ietf.org; Wed, 23 Jul 2003 16:08:32 -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 NAA14112; Wed, 23 Jul 2003 13:07:20 -0700 (PDT) Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id h6NK7Js31453; Wed, 23 Jul 2003 13:07:19 -0700 X-mProtect: <200307232007> Nokia Silicon Valley Messaging Protection Received: from UNKNOWN (205.226.2.67, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdBr2m5n; Wed, 23 Jul 2003 13:07:18 PDT Message-ID: <3F1EEC41.7050800@iprg.nokia.com> Date: Wed, 23 Jul 2003 13:12:49 -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: Claude.Castelluccia@inrialpes.fr CC: George Hadjichristofi , manet@ietf.org Subject: Re: [manet] routing protocols-- spoofed IP References: <1058987238.3f1edce62fb8c@imap-serv.inrialpes.fr> 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 Claude.Castelluccia@inrialpes.fr wrote: >One solution is to use Crypto. Generated Addresses... >CGA are currently being used to secure MIPv6 and ND. They > CGA is one alternative; see the IETF SEND wg for more info. >can also be used in MANET to secure the routing protocol. >We actually applied them to secure AODVv6 but they can actually be >used with any protocols... > Agreed; we touched on this briefly in the TBRPF spec. Fred ftemplin@iprg.nokia.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 23 20:24:57 2003 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 UAA08506 for ; Wed, 23 Jul 2003 20:24:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fTuH-0008Am-25 for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 20:24:29 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6O0OTWE031365 for manet-archive@odin.ietf.org; Wed, 23 Jul 2003 20:24:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fTuG-00089H-Rw for manet-web-archive@optimus.ietf.org; Wed, 23 Jul 2003 20:24: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 UAA08500 for ; Wed, 23 Jul 2003 20:24:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fTuE-0001x8-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 20:24:26 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fTu9-0001x2-00 for manet-web-archive@ietf.org; Wed, 23 Jul 2003 20:24:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fTtp-00086h-HW; Wed, 23 Jul 2003 20:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fTt9-00086O-Bi for manet@optimus.ietf.org; Wed, 23 Jul 2003 20:23: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 UAA08473 for ; Wed, 23 Jul 2003 20:23:16 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fTt7-0001wq-00 for manet@ietf.org; Wed, 23 Jul 2003 20:23:17 -0400 Received: from mail.drexel.edu ([144.118.25.40]) by ietf-mx with esmtp (Exim 4.12) id 19fTsw-0001wk-00 for manet@ietf.org; Wed, 23 Jul 2003 20:23:06 -0400 Received: from webmail.drexel.edu (webmail.drexel.edu [144.118.25.20]) by mail.drexel.edu (Sun Internet Mail Server sims.4.0.2001.07.26.11.50.p9) with ESMTP id <0HII002056DQ79@mail.drexel.edu> for manet@ietf.org; Wed, 23 Jul 2003 20:22:38 -0400 (EDT) Date: Wed, 23 Jul 2003 20:22:38 -0400 From: Harpreet Arora Subject: RE: [manet] bandwidth calculation at a node To: manet , Philippe Jacquet Message-id: <3F1F6791@webmail.drexel.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: ha33 X-EXP32-SerialNo: 00003005 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 Philippe. This is certainly useful. However, the paper assumes that a channel is divided into time slots and reservations are made by reserving time slots. I am trying to figure out if it is possible to make QoS assurances in an 802.11-DCF based network. In such a network, each node has to keep track of the amount of bandwidth which is being used by the neighboring nodes (nodes which are transmitting within the interference range of this node) before it can make any reservations or admission control decisions. Is there any work done which discusses how bandwidth can be calculated in this scenario? thanks, Harpreet >===== Original Message From Philippe Jacquet ===== >Hello, Harpreet, > >We have extended the available bandwidth calculation per node (or per link) >up to an arbitrary number H_I of hops from the node. Interferences can >extend much further than one hop. With IEEE 802.11 the interference range >extend between two and three hops. However we prove in >http://www.inria.fr/rrrt/rr-4876.html that the problem of finding a route >that fits the bandwidth requirement of a new connection is NP hard in >general as soon as H_I>0. We show example with slotted ad hoc TDMA networks. >This result is in sharp contrast with wired network (H_I=0) where the >finding of an optimal route is polynomial. > >Philippe > >----- Original Message ----- >From: Harpreet Arora >To: >Sent: Monday, July 21, 2003 10:18 PM >Subject: [manet] bandwidth calculation at a node > > >> Hi, >> >> I have read a number of papers offering QoS solutions in MANETs. Most of >them >> assume that nodes somehow have an idea of the available bandwidth in their >> neighborhood and either pass this information around or make admission >control >> decisions based on this information. The SWAN model computes bandwidth at >a >> node by tapping all packet transmissions within the neighborhood of the >node >> within a certain period of time and updating the estimate of the bandwidth >> being used based on that information. However, this does not capture the >> scenario where two nodes are within interfering range of each other but >not in >> reception range. Are there any papers in this regard? >> >> thanks, >> Harpreet S. Arora >> >> Research Assistant, ITCSL >> Drexel University >> Philadelphia, PA-19104 >> Ph: 215-895-6198 >> >> -------------------------------------------------------------------- >> Harpreet S. Arora >> Research Assistant, ITCSL >> Drexel University, >> Philadelphia, PA-19104 >> Ph. # 215-895-6198 >> http://www.pages.drexel.edu/~ha33 >> ---------------------------------------------------------------------- >> >> >> _______________________________________________ >> 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 -------------------------------------------------------------------- Harpreet S. Arora Research Assistant, ITCSL Drexel University, Philadelphia, PA-19104 Ph. # 215-895-6198 http://www.pages.drexel.edu/~ha33 ---------------------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 01:56:27 2003 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 BAA13697 for ; Thu, 24 Jul 2003 01:56:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fZ48-0003WL-5u for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 01:55:00 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6O5t03p013527 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 01:55:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fZ47-0003W6-N1 for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 01:54: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 BAA13675 for ; Thu, 24 Jul 2003 01:54:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fZ44-0003T8-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 01:54:56 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fZ3y-0003T5-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 01:54:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fZ3B-0003PV-OV; Thu, 24 Jul 2003 01:54:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fZ2f-0003Mj-VS for manet@optimus.ietf.org; Thu, 24 Jul 2003 01:53:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13663 for ; Thu, 24 Jul 2003 01:53:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fZ2c-0003Sr-00 for manet@ietf.org; Thu, 24 Jul 2003 01:53:26 -0400 Received: from web8106.mail.in.yahoo.com ([203.199.70.120]) by ietf-mx with smtp (Exim 4.12) id 19fZ2R-0003Sj-00 for manet@ietf.org; Thu, 24 Jul 2003 01:53:15 -0400 Message-ID: <20030724055204.78903.qmail@web8106.mail.in.yahoo.com> Received: from [202.141.70.188] by web8106.mail.in.yahoo.com via HTTP; Thu, 24 Jul 2003 06:52:04 BST Date: Thu, 24 Jul 2003 06:52:04 +0100 (BST) From: =?iso-8859-1?q?Ash=20Mohammad=20Abbas?= To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-163164334-1059025924=:78593" Content-Transfer-Encoding: 8bit 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: , --0-163164334-1059025924=:78593 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Can anybody tell me how to attach a routing header in NS-2? I have designed a new routing protocol. I want to run it as a stand alone protocol in itself for simulation results. What should I do. Please elaborate your reply a little bit. Abbas SMS using the Yahoo! Messenger;Download latest version. --0-163164334-1059025924=:78593 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Can anybody tell me how to attach a routing header in NS-2? I have designed a new routing protocol. I want to run it as a stand alone protocol in itself for simulation results. What should I do. Please elaborate your reply a little bit.
Abbas 

Yahoo! India Mobile SMS using the Yahoo! Messenger; Download latest version. --0-163164334-1059025924=:78593-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 04:05:32 2003 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 EAA28153 for ; Thu, 24 Jul 2003 04:05:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fb61-00033S-Or for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 04:05:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6O851Gr011729 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 04:05:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fb5w-000336-IC for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 04:05: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 EAA28129 for ; Thu, 24 Jul 2003 04:04:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fb5t-00049v-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 04:04:58 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fb5o-00049s-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 04:04:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fb4z-0002sk-K8; Thu, 24 Jul 2003 04: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 19fb4Q-0002rz-Uz for manet@optimus.ietf.org; Thu, 24 Jul 2003 04:03:27 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28104 for ; Thu, 24 Jul 2003 04:03:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fb4O-00049N-00 for manet@ietf.org; Thu, 24 Jul 2003 04:03:24 -0400 Received: from postfix.informatik.uni-bonn.de ([131.220.8.4]) by ietf-mx with esmtp (Exim 4.12) id 19fb4D-00048y-00 for manet@ietf.org; Thu, 24 Jul 2003 04:03:13 -0400 X-IAI-Env-From: : [131.220.6.147] Received: from cs.uni-bonn.de (bratislava.informatik.uni-bonn.de [131.220.6.147]) by postfix.informatik.uni-bonn.de (Postfix) with ESMTP id 4DACC5C818; Thu, 24 Jul 2003 10:02:24 +0200 (MEST) (envelope-from dewaal@cs.uni-bonn.de) (envelope-to VARIOUS) (2) (internal use: ta=0, tu=1, te=0, am=-, au=-) Message-ID: <3F1F9290.4030107@cs.uni-bonn.de> Date: Thu, 24 Jul 2003 10:02:24 +0200 From: Christian de Waal Organization: Computer Science IV, University of Bonn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Harpreet Arora , manet@ietf.org Subject: Re: [manet] bandwidth calculation at a node References: <3F1F6791@webmail.drexel.edu> In-Reply-To: <3F1F6791@webmail.drexel.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 Hi Harpreet, QoS assurances are not possible in 802.11 DCF networks. Period. To make assurances, you need something like a slotted MAC layer, because "simply" knowing the available bandwidth at the sending and at the receiving station is not enough: The stations also have to negotiate at what times the medium is free at _both_ stations. If half of the link bandwidth is available at both stations, but one station is blocked when the other is not and vice versa, then these stations cannot communicate unless some re-scheduling is performed. I can once again point you to our ASWN'03 paper which describes these difficulties in detail. http://web.informatik.uni-bonn.de/IV/Mitarbeiter/dewaal/aswn03.html Best regards, Christian Harpreet Arora wrote: > Thanks Philippe. This is certainly useful. However, the paper assumes that a > channel is divided into time slots and reservations are made by reserving > time slots. I am trying to figure out if it is possible to make QoS > assurances in an 802.11-DCF based network. In such a network, each node > has to keep track of the amount of bandwidth which is being used by the > neighboring nodes (nodes which are transmitting within the interference > range of this node) before it can make any reservations or admission > control decisions. Is there any work done which discusses how bandwidth can > be calculated in this scenario? > > thanks, > Harpreet -- ____________________________________________________________________ Christian de Waal University of Bonn Phone: +49 228 73-4548 Institute of Computer Science IV Fax: +49 228 73-4571 Roemerstr. 164 E-mail: dewaal@cs.uni-bonn.de 53117 Bonn, Germany http://www.cs.uni-bonn.de/IV/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 05:33:22 2003 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 FAA00371 for ; Thu, 24 Jul 2003 05:33:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fcT3-0007gA-3J for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 05:32:57 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6O9WvfS029514 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 05:32:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fcT3-0007fx-0J for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 05:32: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 FAA00353 for ; Thu, 24 Jul 2003 05:32:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fcSz-0004kd-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 05:32:53 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fcSu-0004kZ-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 05:32:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fcSA-0007WD-9v; Thu, 24 Jul 2003 05: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 19fcRA-0007T6-TH for manet@optimus.ietf.org; Thu, 24 Jul 2003 05:31: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 FAA00280 for ; Thu, 24 Jul 2003 05:30:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fcR7-0004jQ-00 for manet@ietf.org; Thu, 24 Jul 2003 05:30:57 -0400 Received: from inet-tsb.toshiba.co.jp ([202.33.96.40]) by ietf-mx with esmtp (Exim 4.12) id 19fcQw-0004jM-00 for manet@ietf.org; Thu, 24 Jul 2003 05:30:46 -0400 Received: from tsb-wall.toshiba.co.jp ([133.199.160.134]) by inet-tsb.toshiba.co.jp with ESMTP id h6O9UfVj024735 for ; Thu, 24 Jul 2003 18:30:42 +0900 (JST) Received: (from root@localhost) by tsb-wall.toshiba.co.jp id h6O9UgRD014518 for ; Thu, 24 Jul 2003 18:30:42 +0900 (JST) Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id UAA14516 ; Thu, 24 Jul 2003 18:30:41 +0900 Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp id SAA09676; Thu, 24 Jul 2003 18:30:41 +0900 (JST) Received: from m400.sitc.toshiba.co.jp by toshiba.co.jp id SAA06806; Thu, 24 Jul 2003 18:30:39 +0900 (JST) Received: from AYA ([133.196.175.144]) by m400.sitc.toshiba.co.jp (Mirapoint Messaging Server MOS 3.2.2-GA) with ESMTP id AAR34191; Thu, 24 Jul 2003 18:30:38 +0900 (JST) To: manet@ietf.org From: YAMADA Tatsuya Message-Id: <200307241828.BCC92371.EZN@sitc.toshiba.co.jp> X-Mailer: Winbiff [Version 2.42 PL2] X-Accept-Language: ja,en Date: Thu, 24 Jul 2003 18:30:38 +0900 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [manet] Q. about RFC3561 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 all, I have a question about RFC3561. Section 6.1. is written as below, >6.1. Maintaining Sequence Numbers (snip) > guarantee the loop-freedom of all routes towards that node. A > destination node increments its own sequence number in two > circumstances: > > - Immediately before a node originates a route discovery, it MUST > increment its own sequence number. This prevents conflicts with > previously established reverse routes towards the originator of a > RREQ. Does "a node" in first item mean "an originator" ? If so, it shold be written like that explicitly. If not so, could you tell me when a destination node has to originate a route discovery ? (When a destination node will reply a RREP, a route from a destination to an originator (and vice versa) has been already established, I think.) Or does "a node" mean both ? Best Regards, ---- YAMADA Tatsuya / mailto:tatsuya10.yamada@toshiba.co.jp Software Technology Group 2, Software Engineering Center, Toshiba Corp. Tel: +81-44-549-2404 / Fax: +81-44-549-5484 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 07:05:57 2003 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 HAA01951 for ; Thu, 24 Jul 2003 07:05:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fduf-0003vU-1o for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 07:05:33 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OB5Xoa015086 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 07:05:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fdue-0003vE-TG for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 07:05:32 -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 HAA01914 for ; Thu, 24 Jul 2003 07:05:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fdtC-0003Rs-TQ; Thu, 24 Jul 2003 07:04:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fdt3-0003RT-KF for manet@optimus.ietf.org; Thu, 24 Jul 2003 07:03: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 HAA01871 for ; Thu, 24 Jul 2003 07:03:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fdsz-0005C1-00 for manet@ietf.org; Thu, 24 Jul 2003 07:03:49 -0400 Received: from tounes103.gw.tn ([193.95.50.103]) by ietf-mx with esmtp (Exim 4.12) id 19fdsI-0005Bh-00 for manet@ietf.org; Thu, 24 Jul 2003 07:03:11 -0400 Received: from tounes-22.ati.tn (tounes-22.ati.tn [193.95.66.22]) by tounes.tngw.tn (8.8.8/8.8.8) with ESMTP id MAA28892 for ; Thu, 24 Jul 2003 12:02:08 -0100 (GMT) Received: from mail.rnu.tn ([193.95.67.6]) by tounes-22.ati.tn (8.12.8/8.12.8) with ESMTP id h6OA1Nfv012872 for ; Thu, 24 Jul 2003 12:01:23 +0200 (EET) Received: from gammar ([193.95.31.8]) by mail.rnu.tn (8.12.5/8.12.8) with SMTP id h6OBboMv007163 for ; Thu, 24 Jul 2003 12:38:04 +0100 Message-ID: <005201c351d1$b3c8ec90$081f5fc1@gammar> From: "Sonia METTALI GAMMAR" To: Date: Thu, 24 Jul 2003 11:51:46 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004C_01C351D9.F59B13C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Subject: [manet] Managing ADHOC Networks Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , C'est un message de format MIME en plusieurs parties. ------=_NextPart_000_004C_01C351D9.F59B13C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello is there some protocols used to manage adhoc network giving the topology = of the network and caraterising a node=20 Thanks for your help Sonia Gammar ------=_NextPart_000_004C_01C351D9.F59B13C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hello
is there some protocols used to manage = adhoc=20 network giving the topology of the network and caraterising a node =
Thanks for your help
Sonia = Gammar

------=_NextPart_000_004C_01C351D9.F59B13C0-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 07:31:27 2003 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 HAA02436 for ; Thu, 24 Jul 2003 07:31:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19feJI-0005e4-4M for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 07:31:00 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OBV0X3021685 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 07:31:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19feJH-0005da-QT for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 07:30: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 HAA02400 for ; Thu, 24 Jul 2003 07:30:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19feJG-0005Kp-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 07:30:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19feJB-0005Kl-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 07:30:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19feIM-00057p-A0; Thu, 24 Jul 2003 07: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 19feI7-00056R-6L for manet@optimus.ietf.org; Thu, 24 Jul 2003 07:29: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 HAA02369 for ; Thu, 24 Jul 2003 07:29:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19feI6-0005J2-00 for manet@ietf.org; Thu, 24 Jul 2003 07:29:46 -0400 Received: from law15-f104.law15.hotmail.com ([64.4.23.104] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19feHv-0005IY-00 for manet@ietf.org; Thu, 24 Jul 2003 07:29:36 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 24 Jul 2003 04:28:18 -0700 Received: from 62.135.35.7 by lw15fd.law15.hotmail.msn.com with HTTP; Thu, 24 Jul 2003 11:28:17 GMT X-Originating-IP: [62.135.35.7] X-Originating-Email: [reh_elmayet@hotmail.com] From: "reham elmayet" To: manet@ietf.org Date: Thu, 24 Jul 2003 11:28:17 +0000 Mime-Version: 1.0 Content-Type: text/html Message-ID: X-OriginalArrivalTime: 24 Jul 2003 11:28:18.0342 (UTC) FILETIME=[AE2B2460:01C351D6] Subject: [manet] MANET real time applications Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: ,
hi all,
I want to know what'sa the real time applications for MANETs.
Also, what's the points for research in this direction.
Regards,
Reham

MSN 8 helps ELIMINATE E-MAIL VIRUSES. Get 2 months FREE*. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 07:58:17 2003 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 HAA01952 for ; Thu, 24 Jul 2003 07:05:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fduf-0003vj-5H for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 07:05:33 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OB5Xsa015101 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 07:05:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fdue-0003vF-Vn for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 07:05:33 -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 HAA01915 for ; Thu, 24 Jul 2003 07:05:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fdtB-0003Ri-QR; Thu, 24 Jul 2003 07: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 19fdsX-0003Oh-3R for manet@optimus.ietf.org; Thu, 24 Jul 2003 07:03: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 HAA01860 for ; Thu, 24 Jul 2003 07:03:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fdsS-0005Bn-00 for manet@ietf.org; Thu, 24 Jul 2003 07:03:17 -0400 Received: from tounes103.gw.tn ([193.95.50.103]) by ietf-mx with esmtp (Exim 4.12) id 19fdsD-0005Bi-00 for manet@ietf.org; Thu, 24 Jul 2003 07:03:06 -0400 Received: from tounes-22.ati.tn (tounes-22.ati.tn [193.95.66.22]) by tounes.tngw.tn (8.8.8/8.8.8) with ESMTP id MAA29006 for ; Thu, 24 Jul 2003 12:02:16 -0100 (GMT) Received: from mail.rnu.tn ([193.95.67.6]) by tounes-22.ati.tn (8.12.8/8.12.8) with ESMTP id h6OA1Xfv012959 for ; Thu, 24 Jul 2003 12:01:33 +0200 (EET) Received: from gammar ([193.95.31.8]) by mail.rnu.tn (8.12.5/8.12.8) with SMTP id h6OBc8Mv007191 for ; Thu, 24 Jul 2003 12:38:17 +0100 Message-ID: <005d01c351d1$bf4068f0$081f5fc1@gammar> From: "Sonia METTALI GAMMAR" To: Date: Thu, 24 Jul 2003 11:52:38 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004F_01C351DA.147BE490" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Subject: [manet] performance evaluation of an extension 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: , C'est un message de format MIME en plusieurs parties. ------=_NextPart_000_004F_01C351DA.147BE490 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable hello; we have proposed an entension of OLSR protocol modifying the routing = table structure (we added some field) and the TC table structure. We = want to evaluate the performance of the new algorithm and to compare it = with OLSR by simulation. But we haven't find which parameters can be used to compare and to = caraterise our algorithm. i appreciate if someone have suggestions. Thanks =20 ------=_NextPart_000_004F_01C351DA.147BE490 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
hello;
we have proposed an entension of OLSR = protocol=20 modifying the routing table structure  (we added some field) and = the TC=20 table structure. We want to evaluate the performance of the new=20 algorithm and to compare it with OLSR by simulation.
But we haven't find = which parameters can be=20 used to compare and to caraterise our algorithm.
i appreciate if someone have=20 suggestions.
Thanks
 
------=_NextPart_000_004F_01C351DA.147BE490-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 08:18:17 2003 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 HAA02434 for ; Thu, 24 Jul 2003 07:31:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19feJI-0005e5-4P for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 07:31:00 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OBV0Fo021684 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 07:31:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19feJH-0005db-RU for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 07:30: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 HAA02402 for ; Thu, 24 Jul 2003 07:30:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19feJH-0005Ks-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 07:30:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19feJB-0005Km-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 07:30:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19feIK-00057W-UF; Thu, 24 Jul 2003 07:30:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19feHs-00056C-6E for manet@optimus.ietf.org; Thu, 24 Jul 2003 07:29: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 HAA02342 for ; Thu, 24 Jul 2003 07:29:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19feHr-0005Iq-00 for manet@ietf.org; Thu, 24 Jul 2003 07:29:31 -0400 Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu) by ietf-mx with esmtp (Exim 4.12) id 19feHg-0005Ik-00 for manet@ietf.org; Thu, 24 Jul 2003 07:29:20 -0400 Received: by mail.eecis.udel.edu (Postfix, from userid 62) id 0B1F5329A4; Thu, 24 Jul 2003 07:25:47 -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 403DA3299F; Thu, 24 Jul 2003 07:25:46 -0400 (EDT) Date: Thu, 24 Jul 2003 07:25:46 -0400 (EDT) From: Chien-Chung Shen X-X-Sender: To: Sonia METTALI GAMMAR Cc: Subject: Re: [manet] Managing ADHOC Networks In-Reply-To: <005201c351d1$b3c8ec90$081f5fc1@gammar> Message-ID: X-Spam-Status: No, hits=-4.2 required=6.0 tests=DEPT_RCVD,EMAIL_ATTRIBUTION,IN_REP_TO,SPAM_PHRASE_02_03, USER_AGENT_PINE version=2.43 X-Sanitizer: This message has been sanitized! X-Sanitizer-URL: http://mailtools.anomy.net/ X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm,v 1.64 2002/10/22 MIME-Version: 1.0 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset="US-ASCII" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , On Thu, 24 Jul 2003, Sonia METTALI GAMMAR wrote: > Hello > is there some protocols used to manage adhoc network giving the topology of the network and caraterising a node > Thanks for your help > Sonia Gammar Please check out @article{ author = "Wenli Chen and Suresh Singh and Nitin Jain", title = "{ANMP:Ad hoc network Network Management Protocol}", journal = "IEEE Journal on Selected Areas in Communications", month = "August", number = "8", pages = "1506", volume = "17", year = "1999" } @article{ author = "Chien-Chung Shen and Chavalit Srisathapornphat and Chaiporn Jaikaeo" , title = "{An Adaptive Management Architecture for Ad hoc Networks}", journal = "IEEE Communications", month = "February", number = "2", pages = "108--115", volume = "41", year = "2003" } _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 08:23:27 2003 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 IAA03721 for ; Thu, 24 Jul 2003 08:23:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ff7c-0000Dy-Jk for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 08:23:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OCN02p000854 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 08:23:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ff7c-0000Dg-Fy for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 08:23: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 IAA03672 for ; Thu, 24 Jul 2003 08:22:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ff7b-0005cs-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 08:22:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ff7V-0005cp-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 08:22:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ff6f-0008QR-Pu; Thu, 24 Jul 2003 08: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 19ff6O-0008Je-HZ for manet@optimus.ietf.org; Thu, 24 Jul 2003 08:21: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 IAA03644 for ; Thu, 24 Jul 2003 08:21:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ff6N-0005c7-00 for manet@ietf.org; Thu, 24 Jul 2003 08:21:43 -0400 Received: from hades.snrc.uow.edu.au ([130.130.10.100]) by ietf-mx with esmtp (Exim 4.12) id 19ff6C-0005bf-00 for manet@ietf.org; Thu, 24 Jul 2003 08:21:32 -0400 Received: from hades.snrc.uow.edu.au (IDENT:99@localhost [127.0.0.1]) by hades.snrc.uow.edu.au (8.12.9/8.12.4) with ESMTP id h6OCJrEY025516; Thu, 24 Jul 2003 22:19:53 +1000 Received: (from nobody@localhost) by hades.snrc.uow.edu.au (8.12.9/8.12.4/Submit) id h6OCJrJh025515; Thu, 24 Jul 2003 22:19:53 +1000 X-Authentication-Warning: hades.snrc.uow.edu.au: nobody set sender to justin@titr.uow.edu.au using -f Received: from 217.44.153.198 ( [217.44.153.198]) as user justin@imap.snrc.uow.edu.au by hades.snrc.uow.edu.au with HTTP; Thu, 24 Jul 2003 22:19:53 +1000 Message-ID: <1059049193.3f1fcee927302@hades.snrc.uow.edu.au> Date: Thu, 24 Jul 2003 22:19:53 +1000 From: Justin Lipman To: Sonia METTALI GAMMAR Cc: manet@ietf.org Subject: Re: [manet] Managing ADHOC Networks References: <005201c351d1$b3c8ec90$081f5fc1@gammar> In-Reply-To: <005201c351d1$b3c8ec90$081f5fc1@gammar> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 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 Sonia, I had a paper at Medhoc 2003 on information collection in ad hoc networks, which may be used as a basis for efficient topology discovery. J. Lipman, P. Boustead, J. Chicharo, J. Judge, "Resource Aware Information Collection (RAIC) in Ad hoc Networks". In proceedings 2nd Mediterranean Workshop on Ad-Hoc Networks, pp.161-168, June 2003. http://www.titr.uow.edu.au/~justin/raic_medhoc03.ps regards, Justin Quoting Sonia METTALI GAMMAR : > Hello > is there some protocols used to manage adhoc network giving the topology of > the network and caraterising a node > Thanks for your help > Sonia Gammar > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 08:24:42 2003 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 IAA03780 for ; Thu, 24 Jul 2003 08:24:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ff8p-0000UP-Dx for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 08:24:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OCOFjv001875 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 08:24:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ff8p-0000UA-8t for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 08:24:15 -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 IAA03769 for ; Thu, 24 Jul 2003 08:24:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ff7e-0000E9-8z; Thu, 24 Jul 2003 08:23:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ff77-00007K-Ke for manet@optimus.ietf.org; Thu, 24 Jul 2003 08:22:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03650 for ; Thu, 24 Jul 2003 08:22:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ff76-0005cI-00 for manet@ietf.org; Thu, 24 Jul 2003 08:22:28 -0400 Received: from web8005.mail.in.yahoo.com ([203.199.70.65]) by ietf-mx with smtp (Exim 4.12) id 19ff6v-0005bb-00 for manet@ietf.org; Thu, 24 Jul 2003 08:22:17 -0400 Message-ID: <20030724121955.59901.qmail@web8005.mail.in.yahoo.com> Received: from [202.62.76.47] by web8005.mail.in.yahoo.com via HTTP; Thu, 24 Jul 2003 13:19:55 BST Date: Thu, 24 Jul 2003 13:19:55 +0100 (BST) From: =?iso-8859-1?q?Jitesh=20Shah?= Subject: Re: [manet] MANET real time applications To: manet@ietf.org 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, I think such questions should not be addressed to this group. You may please refer to some basic Manet book or on internet for that matter. Regards Jitesh --- reham elmayet wrote: --------------------------------- hi all, I want to know what'sa the real time applications for MANETs. Also, what's the points for research in this direction. Regards, Reham ________________________________________________________________________ Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 09:08:16 2003 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 JAA04891 for ; Thu, 24 Jul 2003 09:08:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ffp0-0002wA-C3 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 09:07:50 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OD7oZR011276 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 09:07:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ffp0-0002vn-2x for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 09:07: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 JAA04873 for ; Thu, 24 Jul 2003 09:07:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ffoy-0005qn-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 09:07:48 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ffot-0005qk-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 09:07:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ffoE-0002UE-Ex; Thu, 24 Jul 2003 09:07:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ffnu-0002Sf-GD for manet@optimus.ietf.org; Thu, 24 Jul 2003 09:06: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 JAA04824 for ; Thu, 24 Jul 2003 09:06:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ffns-0005q2-00 for manet@ietf.org; Thu, 24 Jul 2003 09:06:40 -0400 Received: from [203.199.70.30] (helo=web8103.mail.in.yahoo.com) by ietf-mx with smtp (Exim 4.12) id 19ffnh-0005ob-00 for manet@ietf.org; Thu, 24 Jul 2003 09:06:30 -0400 Message-ID: <20030724130359.38185.qmail@web8103.mail.in.yahoo.com> Received: from [202.141.69.127] by web8103.mail.in.yahoo.com via HTTP; Thu, 24 Jul 2003 14:03:59 BST Date: Thu, 24 Jul 2003 14:03:59 +0100 (BST) From: =?iso-8859-1?q?Ash=20Mohammad=20Abbas?= Subject: Re: [manet] performance evaluation of an extension of OLSR To: Sonia METTALI GAMMAR , manet@ietf.org In-Reply-To: <005d01c351d1$bf4068f0$081f5fc1@gammar> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1804786082-1059051839=:33313" 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: , --0-1804786082-1059051839=:33313 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit If you have really done a good job as you think, I suggest, see papers on OLSR and figure out the parameters, and then you should compare your results with the results contained in those papers. Wish you best, Abbas http://www.cse.iitd.ernet.in/~abbas Sonia METTALI GAMMAR wrote: hello; we have proposed an entension of OLSR protocol modifying the routing table structure (we added some field) and the TC table structure. We want to evaluate the performance of the new algorithm and to compare it with OLSR by simulation. But we haven't find which parameters can be used to compare and to caraterise our algorithm. i appreciate if someone have suggestions. Thanks SMS using the Yahoo! Messenger;Download latest version. --0-1804786082-1059051839=:33313 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
If you have really done a good job as you think, I suggest, see
papers on OLSR and figure out the parameters, and then you should compare your results with the results contained in those papers.
Wish you best,
Abbas

Sonia METTALI GAMMAR <sonia.gammar@ensi.rnu.tn> wrote:
hello;
we have proposed an entension of OLSR protocol modifying the routing table structure  (we added some field) and the TC table structure. We want to evaluate the performance of the new algorithm and to compare it with OLSR by simulation.
But we haven't find which parameters can be used to compare and to caraterise our algorithm.
i appreciate if someone have suggestions.
Thanks
 

Yahoo! India Mobile SMS using the Yahoo! Messenger; Download latest version. --0-1804786082-1059051839=:33313-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 09:19:24 2003 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 JAA05204 for ; Thu, 24 Jul 2003 09:19:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ffzn-0003n6-2M for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 09:18:59 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6ODIxAC014566 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 09:18:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ffzm-0003mr-VK for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 09:18: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 JAA05201 for ; Thu, 24 Jul 2003 09:18:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ffzl-0005wZ-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 09:18:57 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ffzf-0005wW-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 09:18:51 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ffyr-0003d4-Lm; Thu, 24 Jul 2003 09:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ffxt-0003TO-F4 for manet@optimus.ietf.org; Thu, 24 Jul 2003 09: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 JAA05179 for ; Thu, 24 Jul 2003 09:16:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ffxr-0005vr-00 for manet@ietf.org; Thu, 24 Jul 2003 09:16:59 -0400 Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx with esmtp (Exim 4.12) id 19ffxh-0005vf-00 for manet@ietf.org; Thu, 24 Jul 2003 09:16:49 -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 h6ODGKvt084274; Thu, 24 Jul 2003 09:16:20 -0400 (EDT) Received: from LAPTOPPC (h80ad37c6.dhcp.vt.edu [128.173.55.198]) by dagger.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BRK06040; Thu, 24 Jul 2003 09:16:17 -0400 (EDT) Message-ID: <000f01c351e5$c274a1d0$c637ad80@LAPTOPPC> From: "Tao Lin" To: "Ash Mohammad Abbas" , "Sonia METTALI GAMMAR" , References: <20030724130359.38185.qmail@web8103.mail.in.yahoo.com> Subject: Re: [manet] performance evaluation of an extension of OLSR Date: Thu, 24 Jul 2003 09:16:13 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01C351C4.3A66C780" 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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_000A_01C351C4.3A66C780 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable You can set OLSR parameters using a olsr.cfg which contains all = parameters. The default parameters are defined in some header files = distributed with OLSR. Correct me if I am wrong. :) =20 Tao Lin PhD Candidate VT LAN ECE Dept.=20 Virginia Tech ----- Original Message -----=20 From: Ash Mohammad Abbas=20 To: Sonia METTALI GAMMAR ; manet@ietf.org=20 Sent: Thursday, July 24, 2003 9:03 AM Subject: Re: [manet] performance evaluation of an extension of OLSR If you have really done a good job as you think, I suggest, see papers on OLSR and figure out the parameters, and then you should = compare your results with the results contained in those papers. Wish you best, Abbas http://www.cse.iitd.ernet.in/~abbas Sonia METTALI GAMMAR wrote: hello; we have proposed an entension of OLSR protocol modifying the routing = table structure (we added some field) and the TC table structure. We = want to evaluate the performance of the new algorithm and to compare it = with OLSR by simulation. But we haven't find which parameters can be used to compare and to = caraterise our algorithm. i appreciate if someone have suggestions. Thanks SMS using the Yahoo! Messenger; Download latest version.=20 ------=_NextPart_000_000A_01C351C4.3A66C780 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

You can set OLSR parameters using = a olsr.cfg=20 which contains all parameters.  The default parameters are defined = in some=20 header files distributed with OLSR.  Correct me if I am wrong.=20 :)
 
 Tao Lin
 PhD Candidate
 VT LAN
 ECE Dept.
 Virginia Tech
 
----- Original Message -----
From:=20 Ash Mohammad Abbas =
Sent: Thursday, July 24, 2003 = 9:03=20 AM
Subject: Re: [manet] = performance=20 evaluation of an extension of OLSR

If you have really done a good job as you think, I suggest, = see
papers=20 on OLSR and figure out the parameters, and then you should compare = your=20 results with the results contained in those papers.
Wish you best,
Abbas
http://www.cse.iitd.ernet.in= /~abbas

Sonia METTALI GAMMAR <sonia.gammar@ensi.rnu.tn>= =20 wrote:
hello;
we have proposed an entension of = OLSR protocol=20 modifying the routing table structure  (we added some field) = and the TC=20 table structure. We want to evaluate the performance of the new=20 algorithm and to compare it with OLSR by = simulation.
But we haven't find = which parameters can=20 be used to compare and to caraterise our algorithm.
i appreciate if someone have=20 suggestions.
Thanks
 

3D"Yahoo! SMS using=20 the Yahoo! Messenger; = Download latest = version.=20

------=_NextPart_000_000A_01C351C4.3A66C780-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 09:43:38 2003 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 JAA06057 for ; Thu, 24 Jul 2003 09:43:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fgND-0005DE-VT for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 09:43:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6ODhBvc020030 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 09:43:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fgND-0005Cz-Qk for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 09:43: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 JAA06020 for ; Thu, 24 Jul 2003 09:43:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fgNB-00067W-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 09:43:10 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fgN6-00067T-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 09:43:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fgM5-0004xq-Sx; Thu, 24 Jul 2003 09:42:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fgLi-0004xJ-Sm for manet@optimus.ietf.org; Thu, 24 Jul 2003 09:41:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05946 for ; Thu, 24 Jul 2003 09:41:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fgLg-00066g-00 for manet@ietf.org; Thu, 24 Jul 2003 09:41:36 -0400 Received: from quadra.novaengr.com ([198.30.180.1]) by ietf-mx with esmtp (Exim 4.12) id 19fgLW-00066G-00 for manet@ietf.org; Thu, 24 Jul 2003 09:41:26 -0400 Received: by quadra.novaengr.com with Internet Mail Service (5.5.2653.19) id ; Thu, 24 Jul 2003 09:40:23 -0400 Message-ID: <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> From: Michael Rauf To: "'Jitesh Shah'" , manet@ietf.org Subject: RE: [manet] MANET real time applications Date: Thu, 24 Jul 2003 09:40:23 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 respectfully disagree as this is a General Discussion Group for MANET. I would also like to hear anyone's input to Reham's question. _________________________________ Michael Rauf Nova Engineering -----Original Message----- From: Jitesh Shah [mailto:jiteshshahin@yahoo.com] Sent: Thursday, July 24, 2003 8:20 AM To: manet@ietf.org Subject: Re: [manet] MANET real time applications Hi, I think such questions should not be addressed to this group. You may please refer to some basic Manet book or on internet for that matter. Regards Jitesh --- reham elmayet wrote: --------------------------------- hi all, I want to know what'sa the real time applications for MANETs. Also, what's the points for research in this direction. Regards, Reham ________________________________________________________________________ Send free SMS using the Yahoo! Messenger. Go to http://in.mobile.yahoo.com/new/pc/ _______________________________________________ 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 Jul 24 10:10:01 2003 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 KAA07734 for ; Thu, 24 Jul 2003 10:10:01 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fgmm-0007LD-2T for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 10:09:36 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OE9abp028214 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 10:09:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fgmk-0007Kw-GV for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 10:09:35 -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 KAA07642 for ; Thu, 24 Jul 2003 10:09:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fglF-00073P-BP; Thu, 24 Jul 2003 10:08:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fglA-000717-6x for manet@optimus.ietf.org; Thu, 24 Jul 2003 10:07: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 KAA07412 for ; Thu, 24 Jul 2003 10:07:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fgl7-0006GJ-00 for manet@ietf.org; Thu, 24 Jul 2003 10:07:53 -0400 Received: from nautique.ornl.gov ([160.91.64.128]) by ietf-mx with esmtp (Exim 4.12) id 19fgku-0006EQ-00 for manet@ietf.org; Thu, 24 Jul 2003 10:07:40 -0400 Received: from LOCALHOST (LOCALHOST [127.0.0.1]) by nautique.ornl.gov (Postfix) with ESMTP id 1DE194B5F; Thu, 24 Jul 2003 10:03:15 -0400 (EDT) Subject: RE: [manet] MANET real time applications From: Lawrence MacIntyre To: Michael Rauf Cc: "'Jitesh Shah'" , manet@ietf.org In-Reply-To: <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> References: <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-8Bfdv1qh6VsI6Yt/HM+B" Message-Id: <1059055394.11235.13.camel@nautique> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 24 Jul 2003 10:03:15 -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: , --=-8Bfdv1qh6VsI6Yt/HM+B Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I would say that the obvious real-time app for wireless is videoconferencing and the obvious research direction would be providing QOS. Another application would be wireless sensors and activators. On Thu, 2003-07-24 at 09:40, Michael Rauf wrote: > I respectfully disagree as this is a General Discussion Group for MANET. = I > would also like to hear anyone's input to Reham's question.=20 >=20 > _________________________________ > Michael Rauf =20 > Nova Engineering =20 >=20 >=20 > -----Original Message----- > From: Jitesh Shah [mailto:jiteshshahin@yahoo.com]=20 > Sent: Thursday, July 24, 2003 8:20 AM > To: manet@ietf.org > Subject: Re: [manet] MANET real time applications >=20 > Hi, >=20 > I think such questions should not be addressed to this > group. You may please refer to some basic Manet book > or on internet for that matter. >=20 > Regards > Jitesh >=20 > --- reham elmayet wrote:=20 > --------------------------------- > hi all, > I want to know what'sa the real time applications for > MANETs. > Also, what's the points for research in this > direction. > Regards, > Reham >=20 > ________________________________________________________________________ > Send free SMS using the Yahoo! Messenger. Go to > http://in.mobile.yahoo.com/new/pc/ >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet --=20 Lawrence MacIntyre 865.574.8696 lpz@ornl.gov Oak Ridge National Laboratory High Performance Information Infrastructure Technology Group --=-8Bfdv1qh6VsI6Yt/HM+B 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/H+ciCNjP8rawCW4RAlU1AKCLj0xwhr8vBJkYMHSs5Grjgml1PACfRtj9 QGjI/w5yaIMhTQHBNAU/v4g= =U7Ze -----END PGP SIGNATURE----- --=-8Bfdv1qh6VsI6Yt/HM+B-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 10:36:43 2003 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 KAA09220 for ; Thu, 24 Jul 2003 10:36:43 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fhCb-0000ud-I1 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 10:36:18 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OEaHdK003506 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 10:36:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fhCb-0000uT-F4 for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 10:36:17 -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 KAA09188 for ; Thu, 24 Jul 2003 10:36:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fhAQ-0000aP-4A; Thu, 24 Jul 2003 10:34:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fhAK-0000a9-Bg for manet@optimus.ietf.org; Thu, 24 Jul 2003 10:33: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 KAA09086 for ; Thu, 24 Jul 2003 10:33:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fhAI-0006Sh-00 for manet@ietf.org; Thu, 24 Jul 2003 10:33:54 -0400 Received: from tc-mail.insa-lyon.fr ([134.214.202.113]) by ietf-mx with esmtp (Exim 4.12) id 19fhA6-0006RZ-00 for manet@ietf.org; Thu, 24 Jul 2003 10:33:43 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by tc-mail.insa-lyon.fr (Postfix) with ESMTP id D960C139F0; Thu, 24 Jul 2003 16:26:54 +0200 (CEST) Received: from inrialpes.fr (ares-guerin-1.insa-lyon.fr [134.214.144.150]) by tc-mail.insa-lyon.fr (Postfix) with ESMTP id 3E6E2139DD; Thu, 24 Jul 2003 16:26:52 +0200 (CEST) Message-ID: <3F1FEB87.8060207@inrialpes.fr> Date: Thu, 24 Jul 2003 16:21:59 +0200 From: =?ISO-8859-1?Q?Isabelle_Gu=E9rin_Lassous?= 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: Harpreet Arora Cc: manet , Philippe Jacquet Subject: Re: [manet] bandwidth calculation at a node References: <3F1F6791@webmail.drexel.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Virus-Scanned: by AMaViS snapshot-20020300 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id KAA09087 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 Harpreet Arora wrote: >Thanks Philippe. This is certainly useful. However, the paper assumes th= at a >channel is divided into time slots and reservations are made by reservin= g >time slots. I am trying to figure out if it is possible to make QoS >assurances in an 802.11-DCF based network. In such a network, each no= de >has to keep track of the amount of bandwidth which is being used by the >neighboring nodes (nodes which are transmitting within the interference >range of this node) before it can make any reservations or admission >control decisions. Is there any work done which discusses how bandwidth = can >be calculated in this scenario? > >thanks, >Harpreet > > =20 > Hi Harpreet, We have designed a bandwidth reservation protocol (called BRuIT for=20 Bandwidth Reservation under InTerferences) for MANET that tries to=20 address the interference notion. You can find the first paper on the=20 subject at http://www.inria.fr/rrrt/rr-4308.html. The protocol is not=20 perfect, but it was a first step towards the integration of=20 interferences notion into QoS protocols for MANET. We have gone on=20 working on the subject since this paper, and we have now a more detailed=20 protocol. I hope a more complete paper will appear soon. Do not hesitate if you have some questions. Regards, Isabelle Gu=E9rin Lassous =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 11:11:46 2003 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 LAA10512 for ; Thu, 24 Jul 2003 11:11: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 19fhkX-0003hj-7S for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 11:11:21 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OFBLES014233 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 11: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 19fhkX-0003hU-3i for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 11: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 LAA10429 for ; Thu, 24 Jul 2003 11:11:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fhkU-0006ny-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 11:11:18 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fhkO-0006nv-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 11:11:12 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fhjF-0003Pr-Pj; Thu, 24 Jul 2003 11: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 19fhiU-0003H7-JF for manet@optimus.ietf.org; Thu, 24 Jul 2003 11:09: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 LAA10320 for ; Thu, 24 Jul 2003 11:09:08 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fhiR-0006mG-00 for manet@ietf.org; Thu, 24 Jul 2003 11:09:11 -0400 Received: from basie.internet2.edu ([207.75.164.22]) by ietf-mx with esmtp (Exim 4.12) id 19fhiG-0006ly-00 for manet@ietf.org; Thu, 24 Jul 2003 11:09:00 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by basie.internet2.edu (Postfix) with ESMTP id 2EF497B48D; Thu, 24 Jul 2003 11:08:11 -0400 (EDT) Received: from magic.internet2.edu (aa185.internet2.edu [207.75.164.185]) by basie.internet2.edu (Postfix) with ESMTP id 2130A7B48A; Thu, 24 Jul 2003 11:08:10 -0400 (EDT) Message-Id: <5.1.0.14.2.20030724110434.01a6c0a8@mail.internet2.edu> X-Sender: jzeeff@mail.internet2.edu X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 24 Jul 2003 11:07:51 -0400 To: Lawrence MacIntyre , Michael Rauf From: Jon Zeeff Subject: RE: [manet] MANET real time applications Cc: "'Jitesh Shah'" , manet@ietf.org In-Reply-To: <1059055394.11235.13.camel@nautique> References: <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> 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: , At 10:03 AM 7/24/2003 -0400, Lawrence MacIntyre wrote: >I would say that the obvious real-time app for wireless is >videoconferencing and the obvious research direction would be providing >QOS. I agree that real-time video is a demanding application and thus a good test case. Also that QOS (in it's broadest definition - ie, including multipath routing, fair queuing, non hop-count metric based routing, etc) is needed. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 12:26:33 2003 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 MAA12720 for ; Thu, 24 Jul 2003 12:26:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fiut-0006gz-Ha for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 12:26:08 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OGQ7gc025719 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 12:26:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fiut-0006gk-DI for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 12:26: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 MAA12675 for ; Thu, 24 Jul 2003 12:26:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fiur-0007Go-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 12:26:05 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fium-0007Gl-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 12:26:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fitp-0006Tx-NR; Thu, 24 Jul 2003 12:25:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fitB-0006TY-H5 for manet@optimus.ietf.org; Thu, 24 Jul 2003 12:24: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 MAA12525 for ; Thu, 24 Jul 2003 12:24:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fit9-0007Ft-00 for manet@ietf.org; Thu, 24 Jul 2003 12:24:19 -0400 Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69] helo=kanmx1.ca.alcatel.com) by ietf-mx with smtp (Exim 4.12) id 19fisz-0007FW-00 for manet@ietf.org; Thu, 24 Jul 2003 12:24:09 -0400 Received: (qmail 9181 invoked from network); 24 Jul 2003 16:34:06 -0000 Received: from unknown (HELO camail02.ca.alcatel.com) (138.120.105.122) by kanmx1.ca.alcatel.com with SMTP; 24 Jul 2003 16:34:06 -0000 Received: from alcatel.com ([138.120.62.49]) by camail02.ca.alcatel.com (Netscape Messaging Server 4.15) with ESMTP id HIJEV200.TCP; Thu, 24 Jul 2003 12:23:26 -0400 Message-ID: <3F2007FE.817E2A5A@alcatel.com> Date: Thu, 24 Jul 2003 12:23:26 -0400 From: "BRIAN McBride" X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Jon Zeeff CC: Lawrence MacIntyre , Michael Rauf , "'Jitesh Shah'" , manet@ietf.org Subject: Re: [manet] MANET real time applications References: <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> <5.1.0.14.2.20030724110434.01a6c0a8@mail.internet2.edu> Content-Type: multipart/mixed; boundary="------------466C60293AE7D2C4411D2F22" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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. --------------466C60293AE7D2C4411D2F22 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have been doing QoS (ATM, diffserv etc.) for quite sometime, but yet have to find a necessary application other than leased lines and simple "real time" vs non-real time. However it does make good research work. I am interested in understanding why QoS is important, separating research from standards development. Is there some work on the applications of ad-hoc networking someone could point me to as a starting point? I have my theories and the common ones I think, but do not know of any that require QoS other than pure fairness amongst all active users. Seems to me the nature of ad-hoc is all are fairly treated, to introduce bias would imply some central authority to manage the bias. I always considered ad-hoc in the context of free-roaming, independent, individuals in a network. Qos leads to guaranteed Qos that inevitably will lead to a claim that MPLS and TE must then be applied to mobile ad-hoc networking ;-). The obvious app for real-time to me is voice, but it is my choice of how I use the bits I am allocated in the network, the network just needs to offer me fair access to the bits. Thanks, Brian McBride Jon Zeeff wrote: > At 10:03 AM 7/24/2003 -0400, Lawrence MacIntyre wrote: > >I would say that the obvious real-time app for wireless is > >videoconferencing and the obvious research direction would be providing > >QOS. > > I agree that real-time video is a demanding application and thus a good > test case. Also that > QOS (in it's broadest definition - ie, including multipath routing, fair > queuing, non hop-count > metric based routing, etc) is needed. > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet --------------466C60293AE7D2C4411D2F22 Content-Type: text/x-vcard; charset=us-ascii; name="brian.mcbride.vcf" Content-Description: Card for Brian McBride Content-Disposition: attachment; filename="brian.mcbride.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:McBride;Brian tel;work:613-784-3010 x-mozilla-html:FALSE org:Alcatel;Research and Innovation adr:;;;Ottawa;;;Canada version:2.1 email;internet:Brian.Mcbride@alcatel.com title:Senior Researcher fn:Brian McBride end:vcard --------------466C60293AE7D2C4411D2F22-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 12:38:21 2003 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 MAA13555 for ; Thu, 24 Jul 2003 12:38:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fj6K-0007Z4-Iz for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 12:37:56 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OGbuqn029079 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 12:37:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fj6K-0007Yw-Fh for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 12: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 MAA13527 for ; Thu, 24 Jul 2003 12:37:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fj6F-0007Nm-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 12:37:51 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fj69-0007Ni-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 12:37:45 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fj5R-00075s-3t; Thu, 24 Jul 2003 12:37:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fj5G-000756-89 for manet@optimus.ietf.org; Thu, 24 Jul 2003 12:36: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 MAA13490 for ; Thu, 24 Jul 2003 12:36:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fj5E-0007N0-00 for manet@ietf.org; Thu, 24 Jul 2003 12:36:48 -0400 Received: from cs.sfu.ca ([142.58.111.1] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19fj54-0007Mu-00 for manet@ietf.org; Thu, 24 Jul 2003 12:36:38 -0400 Received: from css.css.sfu.ca (daemon@css [199.60.1.20]) by cs.sfu.ca (8.12.9/8.12.9) with ESMTP id h6OGaDSk008235; Thu, 24 Jul 2003 09:36:13 -0700 (PDT) Received: from localhost (yzchen@localhost) by css.css.sfu.ca (8.11.6/8.11.6) with ESMTP id h6OGaDY27217; Thu, 24 Jul 2003 09:36:13 -0700 (PDT) X-Authentication-Warning: css.css.sfu.ca: yzchen owned process doing -bs Date: Thu, 24 Jul 2003 09:36:13 -0700 (PDT) From: Yuanzhu Peter Chen X-X-Sender: yzchen@css.css.sfu.ca To: Sonia METTALI GAMMAR cc: manet@ietf.org Subject: Re: [manet] Managing ADHOC Networks 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: , Hello Sonia, Here are some works on clustering using graphs domination and variants: @inproceedings{wu-li-cds-1999, author = {Jie Wu and Hailan Li}, title = {On Calculating Connected Dominating Set for Efficient Routing in Ad Hoc Wireless Networks}, booktitle = {DIAL M'99}, year = {1999} } @inproceedings{das-MCDS, author = {Bevan Das and Vaduvur Bharghavan}, title = {Routing in Ad-Hoc Networks Using Minimum Connected Dominating Sets}, booktitle = {IEEE International Conference on Communications (ICC'97)}, year = {1997} } @inproceedings{clustering_overhead_infocom01, author = {John Sucec and Ivan Marsic}, title = {Clustering Overhead for Hierarchical Routing in Mobile Ad hoc Networks}, booktitle = {Proceedings of INFOCOM}, year = {2002} } @article{zonal_wcds_chen_liestman_2003, author = {Yuanzhu Peter Chen and Arthur L. Liestman}, title = {A Zonal Algorithm for Clustering Ad Hoc Networks}, journal = {International Journal of Foundations of Computer Science}, pages = {305-322}, number = {2}, volume = {14}, year = {2003} } Have a good day! Cheers, Yuanzhu Peter Chen Simon Fraser University ------------------------------------------------ "I have not powered down. I have just rebooted." Quoting Sonia METTALI GAMMAR : > Hello > is there some protocols used to manage adhoc network giving the topology of > the network and caraterising a node > Thanks for your help > Sonia Gammar > > > _______________________________________________ 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 Jul 24 12:52:27 2003 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 MAA13964 for ; Thu, 24 Jul 2003 12:52:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjJw-0008BR-RQ for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 12:52:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OGq00N031456 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 12:52:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjJw-0008BH-DJ for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 12: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 MAA13946 for ; Thu, 24 Jul 2003 12:51:54 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fjJu-0007So-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 12:51:58 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fjJp-0007Sl-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 12:51:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjJ0-0007wM-IA; Thu, 24 Jul 2003 12:51:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjIq-0007w0-00 for manet@optimus.ietf.org; Thu, 24 Jul 2003 12:50: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 MAA13921 for ; Thu, 24 Jul 2003 12:50:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fjIo-0007S3-00 for manet@ietf.org; Thu, 24 Jul 2003 12:50:50 -0400 Received: from letters.cs.ucsb.edu ([128.111.41.13]) by ietf-mx with esmtp (Exim 4.12) id 19fjId-0007Rv-00 for manet@ietf.org; Thu, 24 Jul 2003 12:50:39 -0400 Received: from kenai.cs.ucsb.edu (badlands.cs.ucsb.edu [128.111.40.116]) by letters.cs.ucsb.edu (8.11.7+Sun/8.11.6) with ESMTP id h6OGo6S07060; Thu, 24 Jul 2003 09:50:07 -0700 (PDT) From: Ian Chakeres MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16160.3631.416864.743074@gargle.gargle.HOWL> Date: Thu, 24 Jul 2003 09:49:51 -0700 To: YAMADA Tatsuya Cc: MANET Mailing List Subject: RE:[manet] Q. about RFC3561 In-Reply-To: <200307241828.BCC92371.EZN@sitc.toshiba.co.jp> References: <200307241828.BCC92371.EZN@sitc.toshiba.co.jp> X-Mailer: VM 7.15 under Emacs 21.3.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 This paragraph is not describing management of routing table entries but each nodes own "destination sequence number". In AODV each node maintains it's own destination sequence number therefore specifying originator or destination is slightly redundant (but correct in the context of each bullet) in this paragraph. I'll try to make it more clear in future drafts. Does this re-write remove the confusion? guarantee the loop-freedom of all routes towards that node. A node increments its own sequence number in two circumstances: - Immediately before a originating node starts a route discovery, it MUST increment its own sequence number. This prevents conflicts with previously established reverse routes towards the originator of a RREQ. - Immediately before a destination node issues a route reply in response to a RREQ, it MUST update its own sequence number to the maximum of its current sequence number and the destination sequence number in the RREQ packet. Ian Chakeres >YAMADA Tatsuya wrote: >Hello all, > >I have a question about RFC3561. Section 6.1. is written as below, > >>6.1. Maintaining Sequence Numbers >(snip) >> guarantee the loop-freedom of all routes towards that node. A >> destination node increments its own sequence number in two >> circumstances: >> >> - Immediately before a node originates a route discovery, it MUST >> increment its own sequence number. This prevents conflicts with >> previously established reverse routes towards the originator of a >> RREQ. > >Does "a node" in first item mean "an originator" ? > >If so, it shold be written like that explicitly. > >If not so, could you tell me when a destination node has to originate a >route discovery ? >(When a destination node will reply a RREP, a route from a destination to >an originator (and vice versa) has been already established, I think.) > > >Or does "a node" mean both ? > > >Best Regards, > >---- >YAMADA Tatsuya / mailto:tatsuya10.yamada@toshiba.co.jp >Software Technology Group 2, Software Engineering Center, Toshiba Corp. >Tel: +81-44-549-2404 / Fax: +81-44-549-5484 > >_______________________________________________ >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 Jul 24 13:00:06 2003 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 NAA14525 for ; Thu, 24 Jul 2003 13:00:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjRL-0000NM-5w for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 12:59:41 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OGxdRR001443 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 12:59:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjRK-0000NB-T1 for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 12:59:38 -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 MAA14322 for ; Thu, 24 Jul 2003 12:59:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjPl-0008KE-9N; Thu, 24 Jul 2003 12:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjOx-0008Hu-7d for manet@optimus.ietf.org; Thu, 24 Jul 2003 12:57: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 MAA14057 for ; Thu, 24 Jul 2003 12:57:05 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fjOs-0007Ve-00 for manet@ietf.org; Thu, 24 Jul 2003 12:57:06 -0400 Received: from slb-smtpout-01.boeing.com ([130.76.64.48]) by ietf-mx with esmtp (Exim 4.12) id 19fjOg-0007Um-00 for manet@ietf.org; Thu, 24 Jul 2003 12:56:54 -0400 Received: from slb-av-02.boeing.com ([129.172.13.7]) by slb-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id JAA05762; Thu, 24 Jul 2003 09:55:48 -0700 (PDT) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by slb-av-02.boeing.com (8.9.3p2/8.9.2/MBS-AV-02) with ESMTP id JAA17755; Thu, 24 Jul 2003 09:56:27 -0700 (PDT) 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 h6OGtZD08392; Thu, 24 Jul 2003 09:55:35 -0700 (PDT) Received: from XCH-NE-02.ne.nos.boeing.com ([128.225.80.202]) by xch-nebh-01.ne.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.2966); Thu, 24 Jul 2003 12:55:05 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] MANET real time applications Date: Thu, 24 Jul 2003 12:55:05 -0400 Message-ID: Thread-Topic: [manet] MANET real time applications Thread-Index: AcNSAFTIgWv1n+W/R8qAG8gD02tY2wAAhK0Q From: "Manfredi, Albert E" To: "BRIAN McBride" Cc: X-OriginalArrivalTime: 24 Jul 2003 16:55:05.0712 (UTC) FILETIME=[55125F00:01C35204] 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 BRIAN McBride wrote: > I have been doing QoS (ATM, diffserv etc.) for quite=20 > sometime, but yet have > to find a necessary application other than leased lines and=20 > simple "real > time" vs non-real time. However it does make good research work. I don't disagree with the skepticism entirely, but voice telephony and = even one-way streaming media over non QoS guaranteed nets are proof = enough that something is needed that ain't usually there. The problem with voice telephony over non-QoS IP nets is obvious. What = typically happens, especially over long distances, is unacceptable = delay, caused by the essential large buffers, and frequent drop-outs. = Far, far worse than voice calls used to be over satellite links. One way streaming media sessions are also frequently affected by buffer = starvation and session drop-outs. I usually listen to streaming media = during my lunch hour, over a broadband network of course, and the idea = that in principle large buffers can easily accommodate non-interactive = streaming traffic is simply not always the case. These services are = *not* ready for prime time. > Qos leads to guaranteed Qos that inevitably will lead to a=20 > claim that MPLS > and TE must then be applied to mobile ad-hoc networking ;-). Yup. Sounds unlikely, I agree. > The obvious app for real-time to me is voice, but it is my=20 > choice of how I > use the bits I am allocated in the network, the network just=20 > needs to offer > me fair access to the bits. But that's not enough. Bert _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 13:00:41 2003 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 NAA14739 for ; Thu, 24 Jul 2003 13:00:41 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjRw-0000Sj-Dp for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 13:00:16 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OH0GAK001771 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 13:00:16 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjRw-0000SU-A3 for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 13:00:16 -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 NAA14550 for ; Thu, 24 Jul 2003 13:00:09 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fjQj-00006v-UG; Thu, 24 Jul 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 19fjQ4-0008Pt-Pl for manet@optimus.ietf.org; Thu, 24 Jul 2003 12:58: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 MAA14163 for ; Thu, 24 Jul 2003 12:58:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fjQ2-0007Wg-00 for manet@ietf.org; Thu, 24 Jul 2003 12:58:18 -0400 Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx with esmtp (Exim 4.12) id 19fjPr-0007WI-00 for manet@ietf.org; Thu, 24 Jul 2003 12:58:07 -0400 Received: from zidane.cc.vt.edu (IDENT:mirapoint@evil-zidane [10.1.1.13]) by lennier.cc.vt.edu (8.12.8/8.12.8) with ESMTP id h6OGv2vt145055; Thu, 24 Jul 2003 12:57:02 -0400 (EDT) Received: from tom ([198.70.228.115]) by zidane.cc.vt.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id BRJ80769 (AUTH talin); Thu, 24 Jul 2003 12:57:01 -0400 (EDT) Message-ID: <002301c35204$9cfbcb80$2502a8c0@tom> From: "Tao Lin" To: "Yuanzhu Peter Chen" , "Sonia METTALI GAMMAR" Cc: References: Subject: Re: [manet] Managing ADHOC Networks Date: Thu, 24 Jul 2003 12:57:05 -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 We have one paper using minimal dominating sets in MANETs. @inproceedings{TAO-MCDS, author = {Tao Lin, Scott F. Midkiff, and Jahng S. Park}, title = {Approximation Algorithms for Minimal Connected Dominating Sets and Application with Routing protocol in Wireless Ad Hoc Network}, booktitle = {IEEE International Performance Computing and Communications Conference(IPCCC'03)}, pages = {157-164}, year = {2003} } Thanks, Tao Lin PhD Candidate VT LAN ECE Dept. Virginia Tech ----- Original Message ----- From: "Yuanzhu Peter Chen" To: "Sonia METTALI GAMMAR" Cc: Sent: Thursday, July 24, 2003 12:36 PM Subject: Re: [manet] Managing ADHOC Networks > Hello Sonia, > > Here are some works on clustering using graphs domination and > variants: > > @inproceedings{wu-li-cds-1999, > author = {Jie Wu and Hailan Li}, > title = {On Calculating Connected Dominating Set for Efficient Routing > in Ad Hoc Wireless Networks}, > booktitle = {DIAL M'99}, > year = {1999} } > > @inproceedings{das-MCDS, > author = {Bevan Das and Vaduvur Bharghavan}, > title = {Routing in Ad-Hoc Networks Using Minimum Connected Dominating > Sets}, > booktitle = {IEEE International Conference on Communications (ICC'97)}, > year = {1997} } > > @inproceedings{clustering_overhead_infocom01, > author = {John Sucec and Ivan Marsic}, > title = {Clustering Overhead for Hierarchical Routing in Mobile Ad hoc > Networks}, > booktitle = {Proceedings of INFOCOM}, > year = {2002} } > > @article{zonal_wcds_chen_liestman_2003, > author = {Yuanzhu Peter Chen and Arthur L. Liestman}, > title = {A Zonal Algorithm for Clustering Ad Hoc Networks}, > journal = {International Journal of Foundations of Computer Science}, > pages = {305-322}, > number = {2}, > volume = {14}, > year = {2003} } > > Have a good day! > > Cheers, > Yuanzhu Peter Chen > Simon Fraser University > ------------------------------------------------ > "I have not powered down. I have just rebooted." > > Quoting Sonia METTALI GAMMAR : > > > Hello > > is there some protocols used to manage adhoc network giving the topology of > > the network and caraterising a node > > Thanks for your help > > Sonia Gammar > > > > > > > > > > _______________________________________________ > 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 Thu Jul 24 13:48:27 2003 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 NAA18043 for ; Thu, 24 Jul 2003 13:48:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fkC9-0002fZ-76 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 13:48:01 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OHm1TL010255 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 13:48:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fkC9-0002fK-3H for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 13:48: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 NAA18010 for ; Thu, 24 Jul 2003 13:47:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fkC6-0000Px-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 13:47:58 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fkC1-0000Pu-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 13:47:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fkBB-0002VJ-Md; Thu, 24 Jul 2003 13:47:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fkAv-0002V4-6g for manet@optimus.ietf.org; Thu, 24 Jul 2003 13:46:45 -0400 Received: from [140.32.132.66] (capella.nps.navy.mil [131.120.254.83]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17920 for ; Thu, 24 Jul 2003 13:46:40 -0400 (EDT) Received: from no.name.available by [140.32.132.66] via smtpd (for [132.151.1.176]) with ESMTP; Thu, 24 Jul 2003 10:41:33 -0700 Received: from ro178-66.ro.nps.navy.mil (ro178-66.ro.nps.navy.mil [131.120.178.66]) by capella.nps.navy.mil (8.12.9/8.12.9) with ESMTP id h6OHkRxK025483; Thu, 24 Jul 2003 10:46:29 -0700 (PDT) Subject: Re: [manet] MANET real time applications From: Rex Buddenberg To: BRIAN McBride Cc: Jon Zeeff , Lawrence MacIntyre , Michael Rauf , "'Jitesh Shah'" , manet@ietf.org In-Reply-To: <3F2007FE.817E2A5A@alcatel.com> References: <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> <5.1.0.14.2.20030724110434.01a6c0a8@mail.internet2.edu> <3F2007FE.817E2A5A@alcatel.com> Content-Type: text/plain Message-Id: <1059068537.3748.15.camel@ro178-66.ro.nps.navy.mil> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 24 Jul 2003 10:42:17 -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 Brian, There are lots of applications where, in the macro, we have legitimate needs to make some pigs more equal than others. But ... TANSTAFL. Consider these parameters as metrics of qos: - bandwidth efficiency - latency - jitter - interactivity - determinism At layer 3, IP optimizes bandwidth efficiency and trades all the other parameters to get it. Somehow that usually gets warped into 'not real time' is discussion. QoS control, at least within the MANET context, means changing the layer 3 handling to optimize one or more of the other parameters. But always at the expense of bandwidth efficiency. Diff-serv, RSVP, MPLS are all methods to change this optimization default in some way. At layer 2, we have two qos models. Ethernet (CSMA/CD) and it's offspring in 802.11, optimize interactivity (and min latency comes along with it) and does so at the expense of bandwidth efficiency. By contrast, token MACs optimize bandwidth efficiency, throw in determinism and do it at the expense of the other three parameters. Oh, TANSAFL? There aint no such thing as free lunch. On Thu, 2003-07-24 at 09:23, BRIAN McBride wrote: > I have been doing QoS (ATM, diffserv etc.) for quite sometime, but yet have > to find a necessary application other than leased lines and simple "real > time" vs non-real time. However it does make good research work. > > I am interested in understanding why QoS is important, separating research > from standards development. Is there some work on the applications of > ad-hoc networking someone could point me to as a starting point? > > I have my theories and the common ones I think, but do not know of any that > require QoS other than pure fairness amongst all active users. Seems to me > the nature of ad-hoc is all are fairly treated, to introduce bias would > imply some central authority to manage the bias. I always considered ad-hoc > in the context of free-roaming, independent, individuals in a network. > > Qos leads to guaranteed Qos that inevitably will lead to a claim that MPLS > and TE must then be applied to mobile ad-hoc networking ;-). > > The obvious app for real-time to me is voice, but it is my choice of how I > use the bits I am allocated in the network, the network just needs to offer > me fair access to the bits. > > Thanks, > Brian McBride > > Jon Zeeff wrote: > > > At 10:03 AM 7/24/2003 -0400, Lawrence MacIntyre wrote: > > >I would say that the obvious real-time app for wireless is > > >videoconferencing and the obvious research direction would be providing > > >QOS. > > > > I agree that real-time video is a demanding application and thus a good > > test case. Also that > > QOS (in it's broadest definition - ie, including multipath routing, fair > > queuing, non hop-count > > metric based routing, etc) is needed. > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet -- b _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 24 14:54:45 2003 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 OAA21443 for ; Thu, 24 Jul 2003 14:54: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 19flEH-00066t-NQ for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 14:54:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OIsHXL023483 for manet-archive@odin.ietf.org; Thu, 24 Jul 2003 14:54:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19flEG-00066g-3m for manet-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 14:54: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 OAA21402 for ; Thu, 24 Jul 2003 14:54:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19flEC-0000vy-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 14:54:12 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19flE6-0000vv-00 for manet-web-archive@ietf.org; Thu, 24 Jul 2003 14:54:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19flC6-0005xj-Db; Thu, 24 Jul 2003 14:52:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19flBw-0005xA-Fm for manet@optimus.ietf.org; Thu, 24 Jul 2003 14:51: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 OAA21310 for ; Thu, 24 Jul 2003 14:51:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19flBt-0000tx-00 for manet@ietf.org; Thu, 24 Jul 2003 14:51:49 -0400 Received: from dahlia.noc.ucla.edu ([169.232.46.11]) by ietf-mx with esmtp (Exim 4.12) id 19flBf-0000tO-00 for manet@ietf.org; Thu, 24 Jul 2003 14:51:36 -0400 Received: from manthosm50 (Panther.CS.UCLA.EDU [131.179.128.25]) by dahlia.noc.ucla.edu (8.12.8p1/8.12.8) with SMTP id h6OInnhE006579; Thu, 24 Jul 2003 11:49:50 -0700 Message-ID: <00d701c35214$04262c60$0100007f@manthosm50> From: "Dr Manthos Kazantzidis" To: "Christian de Waal" , "Harpreet Arora" , References: <3F1F6791@webmail.drexel.edu> <3F1F9290.4030107@cs.uni-bonn.de> Subject: Re: [manet] bandwidth calculation at a node Date: Thu, 24 Jul 2003 11:26:02 -0700 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 Hi Harpreet and Christian, While I agree with the email, I wanted to add that there is an issue of available bandwidth definition and measurement method. For example if there is a local measurement that takes into account the MAC mechanisms then one can say that the available bandwidth can be predicted at some value - of course this does not imply when you sent a packet it will be received but just that under some scheduling (similar to such of the past if you will) if no additional flows enter the link etc the available bandwidth will be that. At End-to-end versus Explicit Feedback Measurement in 802.11 Networks -ISCC02 downloadable from http://www.cs.ucla.edu/~kazantz/ I am attempting a per-neighbour measurement of available bandwidth using the ACK times. I am considering the neighbour and neighbour's neighborhood by combining a source, destination specific throughput measurement (which indirectly depends on 802.11 timers) with the node utilization. If the paper is not very clear I can post additional slides and some results that show that -in simulation- works very well for multimedia adaptation, if interested. Regards, Manthos PS: I have not read that paper but will do. ----- Original Message ----- From: "Christian de Waal" To: "Harpreet Arora" ; Sent: Thursday, July 24, 2003 1:02 AM Subject: Re: [manet] bandwidth calculation at a node > Hi Harpreet, > > QoS assurances are not possible in 802.11 DCF networks. Period. To make > assurances, you need something like a slotted MAC layer, because > "simply" knowing the available bandwidth at the sending and at the > receiving station is not enough: The stations also have to negotiate at > what times the medium is free at _both_ stations. If half of the link > bandwidth is available at both stations, but one station is blocked when > the other is not and vice versa, then these stations cannot communicate > unless some re-scheduling is performed. > > I can once again point you to our ASWN'03 paper which describes these > difficulties in detail. > > http://web.informatik.uni-bonn.de/IV/Mitarbeiter/dewaal/aswn03.html > > Best regards, > Christian > > > Harpreet Arora wrote: > > > Thanks Philippe. This is certainly useful. However, the paper assumes that a > > channel is divided into time slots and reservations are made by reserving > > time slots. I am trying to figure out if it is possible to make QoS > > assurances in an 802.11-DCF based network. In such a network, each node > > has to keep track of the amount of bandwidth which is being used by the > > neighboring nodes (nodes which are transmitting within the interference > > range of this node) before it can make any reservations or admission > > control decisions. Is there any work done which discusses how bandwidth can > > be calculated in this scenario? > > > > thanks, > > Harpreet > > > -- > ____________________________________________________________________ > Christian de Waal > > University of Bonn Phone: +49 228 73-4548 > Institute of Computer Science IV Fax: +49 228 73-4571 > Roemerstr. 164 E-mail: dewaal@cs.uni-bonn.de > 53117 Bonn, Germany http://www.cs.uni-bonn.de/IV/ > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 25 08:14:37 2003 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 IAA02930 for ; Fri, 25 Jul 2003 08:14:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g1Sb-0000i3-RE for manet-archive@odin.ietf.org; Fri, 25 Jul 2003 08:14:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6PCE98c002724 for manet-archive@odin.ietf.org; Fri, 25 Jul 2003 08:14:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g1Sa-0000hr-5i for manet-web-archive@optimus.ietf.org; Fri, 25 Jul 2003 08:14: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 IAA02922 for ; Fri, 25 Jul 2003 08:14:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g1SZ-0007ZX-00 for manet-web-archive@ietf.org; Fri, 25 Jul 2003 08:14:07 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19g1ST-0007ZU-00 for manet-web-archive@ietf.org; Fri, 25 Jul 2003 08:14:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g1RV-0000Z1-Ua; Fri, 25 Jul 2003 08: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 19g1R8-0000Yg-Rs for manet@optimus.ietf.org; Fri, 25 Jul 2003 08:12: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 IAA02901 for ; Fri, 25 Jul 2003 08:12:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g1R7-0007Z0-00 for manet@ietf.org; Fri, 25 Jul 2003 08:12:37 -0400 Received: from mail.zrz.tu-berlin.de ([130.149.4.15]) by ietf-mx with esmtp (Exim 4.12) id 19g1Qx-0007Yn-00 for manet@ietf.org; Fri, 25 Jul 2003 08:12:27 -0400 Received: from localhost ([127.0.0.1] helo=mail.zrz.TU-Berlin.DE) by mail.zrz.tu-berlin.de with esmtp (exim-4.20-2) for id 19g1Q1-0008H5-L7; Fri, 25 Jul 2003 14:11:29 +0200 Received: from mail.zrz.TU-Berlin.DE ([130.149.4.15]) by mail.zrz.TU-Berlin.DE (MailMonitor for SMTP v1.2.2 ) ; Fri, 25 Jul 2003 14:11:29 +0200 (CEST) Received: from ftmail.ee.tu-berlin.de ([130.149.49.250]) by mail.zrz.tu-berlin.de with esmtp (exim-4.20-2) for id 19g1Q0-0008Eh-MC; Fri, 25 Jul 2003 14:11:28 +0200 Received: from almathea (mail@almathea.tkn.TU-Berlin.DE [130.149.49.56]) by ftmail.ee.tu-berlin.de (8.11.3/8.11.3) with ESMTP id h6PCBSB31222 for ; Fri, 25 Jul 2003 14:11:28 +0200 Received: from karl by almathea with local (Exim 3.35 #1 (Debian)) id 19g1Q0-0003KM-00 for ; Fri, 25 Jul 2003 14:11:28 +0200 To: manet@ietf.org Message-Id: From: Holger Karl Date: Fri, 25 Jul 2003 14:11:28 +0200 X-Virus-Scanned: Sophos MailMonitor on mail.zrz.tu-berlin.de; Fri, 25 Jul 2003 14:11:29 +0200 Subject: [manet] Call for Papers: WiOpt'04 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Apologies if you receive multiple copies of this call! ---------------------------------------------------------------------- Note: The submission deadline is 5th of November, 2003. *************************************************** ******** CALL FOR PAPERS ******** *************************************************** * * * WiOpt '04 * * * * 2nd Workshop on Modeling and Optimization * * in Mobile, Ad Hoc and Wireless Networks * * * * March 24 - 26, 2004, Cambridge, UK * * * * * *************************************************** Workshop Website: http://www.cl.cam.ac.uk/Research/SRG/wiopt04/ This workshop is intended to bring together leading researchers from both academia and industry to present both foundations and practical methods and tools for modeling and optimisation of mobile and ad hoc networks. The workshop will bring together researchers studying optimisation issues of mobile networks from both the network performance and the mobile networking perspectives: * Mobile Network Optimisation: Applications and Algorithms * Performance characterisation and optimisation of mobile/wireless networks and systems * Protocol design (MAC, Routing) for optimal mobile network utilisation * Tools for network optimisation * Energy efficiency in mobile networks * Security and co-operation models for mobile networks * Pricing and incentives in mobile and ad hoc networks. Papers to be presented at WiOpt'04 will be selected based on extended abstracts of up to 8 pages, double-spaced, 12 point font size. The submission should not exceed 3000 words including tables and figures, each of which count as 250 words. Authors of accepted presentations will have the opportunity to publish either the extended abstract or the full paper in a proceedings volume. Full papers will further be considered for publication in a special issue of the high-level journals MONET and Performance Evaluation. Plenary Speakers: Bruce Hajek (University of Illinois at Urbana-Champaign, USA) Ian Akyildiz (Georgia Institute of Technology, USA) IMPORTANT DATES: Submission of extended abstract: Nov. 5, 2003. Notification of acceptance: Jan. 15, 2003. Camera ready copy: Feb. 15, 2003. (Further details on the workshop website, http://www.cl.cam.ac.uk/Research/SRG/wiopt04/) General chairman: Imrich Chlamtac Vice General Chair: Roger Whitaker Program Co-Chairs: Marco Conti and Tamer Basar Program committee of the conference (to be extended): Eitan Altman, Venkat Anantharam, Konstantin Avrachenkov, Andrew Campbell, A. Chockalingam, Jon Crowcroft, Silvia Giordano, Stephen V. Hanly, Jean-Pierre Hubaux, Peter Key, P. R. Kumar, Peter Marbach, Philippe Nain, Sven Östring, Yoshikuni Onozato, Ramesh Rao, Ness Shroff, Violet Syrotiuk, Thierry Turletti, Jeff Wieselthier Local Arrangements Co-Chair: Sven Östring and Julian Chesterfield Publicity Chair: Holger Karl Sponsors: The workshop is co-sponsored by * Univ. of Cambridge, * IIT (Istituto di Informatica e Telematica) * Intel * Microsoft (IEEE and ACM sponsorships are pending.) _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 25 10:50:21 2003 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 KAA08186 for ; Fri, 25 Jul 2003 10:50:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g3tM-0007Jm-8b for manet-archive@odin.ietf.org; Fri, 25 Jul 2003 10:49:56 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6PEnu01028126 for manet-archive@odin.ietf.org; Fri, 25 Jul 2003 10:49:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g3tM-0007JZ-4R for manet-web-archive@optimus.ietf.org; Fri, 25 Jul 2003 10: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 KAA08171 for ; Fri, 25 Jul 2003 10:49:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g3tJ-0000q2-00 for manet-web-archive@ietf.org; Fri, 25 Jul 2003 10:49:53 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19g3tE-0000pz-00 for manet-web-archive@ietf.org; Fri, 25 Jul 2003 10:49:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g3sT-00079b-4t; Fri, 25 Jul 2003 10:49:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g3rj-00075X-OK for manet@optimus.ietf.org; Fri, 25 Jul 2003 10: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 KAA08077 for ; Fri, 25 Jul 2003 10:48:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g3rh-0000oM-00 for manet@ietf.org; Fri, 25 Jul 2003 10:48:13 -0400 Received: from smtp1.libero.it ([193.70.192.51]) by ietf-mx with esmtp (Exim 4.12) id 19g3rW-0000o2-00 for manet@ietf.org; Fri, 25 Jul 2003 10:48:02 -0400 Received: from tnmac109 (151.25.43.128) by smtp1.libero.it (7.0.012) id 3ECB938A014AB6A0 for manet@ietf.org; Fri, 25 Jul 2003 16:44:21 +0200 Message-ID: <010801c352ba$c891d120$802b1997@science.unitn.it> From: "Mauro Brunato" To: Date: Fri, 25 Jul 2003 16:14:01 +0200 Organization: =?iso-8859-1?Q?Universit=E0_di_Trento?= 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: Quoted-Printable Content-Transfer-Encoding: Quoted-Printable Subject: [manet] Reminder: WONS2004 deadline (Aug 1st) is approaching Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-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 [Just a quick reminder with the sincere hope that you don't receive more than one copy] Only 7 days are left for submissions to WONS 2004, the First Working Conference on Wireless On-demand Network Systems, to be held at Madonna di Campiglio (Italy) on January 2004. Please find more information on the Conference website: http://dit.unitn.it/wons/ Best regards, Mauro. -- Mauro Brunato WONS 2004 Publicity Chair Universit=E0 di Trento, Italy http://dit.unitn.it/~brunato/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 25 12:06:10 2003 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 MAA10526 for ; Fri, 25 Jul 2003 12:06:10 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g54j-0003k2-28 for manet-archive@odin.ietf.org; Fri, 25 Jul 2003 12:05:45 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6PG5jtQ014381 for manet-archive@odin.ietf.org; Fri, 25 Jul 2003 12:05:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g54i-0003js-Vf for manet-web-archive@optimus.ietf.org; Fri, 25 Jul 2003 12:05: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 MAA10474 for ; Fri, 25 Jul 2003 12:05:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g54h-0001V4-00 for manet-web-archive@ietf.org; Fri, 25 Jul 2003 12:05:43 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19g54h-0001V1-00 for manet-web-archive@ietf.org; Fri, 25 Jul 2003 12:05:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g541-0003ZT-Vg; Fri, 25 Jul 2003 12:05:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g53B-0003YO-JS for manet@optimus.ietf.org; Fri, 25 Jul 2003 12:04: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 MAA10402 for ; Fri, 25 Jul 2003 12:04:04 -0400 (EDT) From: mei-ling.bow@philips.com Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g53A-0001U4-00 for manet@ietf.org; Fri, 25 Jul 2003 12:04:08 -0400 Received: from gw-nl6.philips.com ([212.153.235.103]) by ietf-mx with esmtp (Exim 4.12) id 19g539-0001U1-00 for manet@ietf.org; Fri, 25 Jul 2003 12:04:07 -0400 Received: from smtpscan-nl3.philips.com (smtpscan-nl3.philips.com [130.139.36.23]) by gw-nl6.philips.com (Postfix) with ESMTP id 966465D07F for ; Fri, 25 Jul 2003 18:04:06 +0200 (MET DST) Received: from smtpscan-nl3.philips.com (localhost [127.0.0.1]) by localhost.philips.com (Postfix) with ESMTP id 229B619C4D for ; Fri, 25 Jul 2003 18:04:06 +0200 (MEST) Received: from smtprelay-nl2.philips.com (smtprelay-eur2.philips.com [130.139.36.35]) by smtpscan-nl3.philips.com (Postfix) with ESMTP id ADF7E19C4A for ; Fri, 25 Jul 2003 18:04:05 +0200 (MEST) Received: from hbg001soh.diamond.philips.com (e1soh01.diamond.philips.com [130.143.165.45]) by smtprelay-nl2.philips.com (8.9.3-p1/8.8.5-1.2.2m-19990317) with ESMTP id SAA19093 for ; Fri, 25 Jul 2003 18:04:05 +0200 (MEST) To: manet@ietf.org X-Mailer: Lotus Notes Release 5.0.9a January 7, 2002 Message-ID: Date: Fri, 25 Jul 2003 18:02:48 +0200 X-MIMETrack: Serialize by Router on hbg001soh/H/SERVER/PHILIPS(Release 5.0.11 |July 24, 2002) at 25/07/2003 18:05:13 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Subject: [manet] NIST/AODV Problem Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi, I have installed the NIST/AODV implementation for OPNET, however each time I run the simulation, I get either a segmentation violation or a bus error. Has anyone encountered this problem, or is there something I need to set in the simulation preferences or environment? Any help would be appreciated, Regards, Mei-Ling <<< Program Fault >>> * Time: 17:00:11 Fri Jul 25 2003 * Product: modeler * Program: op_runsim (Version 8.0.C PL7 Build 1252) * System: SunOS eniac 5.6 Generic_105181-30 sun4u * Package: process (aodv_routing) at module (top.sn.mobile_node_0.aodv_routing) * Function: aodv_routing () [Handle_Breakage enter execs] * Error: program abort -- bus error T (272.55), EV (293234), MOD (top.sn.mobile_node_0.aodv_routing), PROC (aodv_routing) * Function call stack: (builds down) ------------------------------------------------------------ Call Block Count Line# Function ------------------------------------------------------------ 0) 1 125 m3_main (argc, argv) 1) 1 519 sim_main (prog_name, argc, argv, dynamic_sim, def_net_name, num_procs, ...) 2) 1 937 sim_ev_loop () 3) 107074 481 sim_obj_qps_intrpt (simev_ptr) 4) 24888 3576 aodv_routing () [Handle_Breakage enter execs] ------------------------------------------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Fri Jul 25 12:31:13 2003 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 MAA11297 for ; Fri, 25 Jul 2003 12:31:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g5St-0005PT-Ls for manet-archive@odin.ietf.org; Fri, 25 Jul 2003 12:30:43 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6PGUh3I020791 for manet-archive@odin.ietf.org; Fri, 25 Jul 2003 12:30:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g5Se-0005PA-Hs for manet-web-archive@optimus.ietf.org; Fri, 25 Jul 2003 12:30: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 MAA11122 for ; Fri, 25 Jul 2003 12:26:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g5Ox-0001gB-00 for manet-web-archive@ietf.org; Fri, 25 Jul 2003 12:26:39 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19g5Ow-0001g7-00 for manet-web-archive@ietf.org; Fri, 25 Jul 2003 12:26:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g5OL-0004yS-Ae; Fri, 25 Jul 2003 12:26:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g5Nh-0004xo-S5 for manet@optimus.ietf.org; Fri, 25 Jul 2003 12:25: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 MAA11087 for ; Fri, 25 Jul 2003 12:24:56 -0400 (EDT) From: ha33@drexel.edu Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g5NM-0001f9-00 for manet@ietf.org; Fri, 25 Jul 2003 12:25:00 -0400 Received: from mail.drexel.edu ([144.118.25.40]) by ietf-mx with esmtp (Exim 4.12) id 19g5NL-0001f6-00 for manet@ietf.org; Fri, 25 Jul 2003 12:24:59 -0400 Received: from shim2.irt.drexel.edu (shim2.irt.drexel.edu [144.118.25.82]) by mail.drexel.edu (Sun Internet Mail Server sims.4.0.2001.07.26.11.50.p9) with ESMTP id <0HIL0067G9LHHM@mail.drexel.edu> for manet@ietf.org; Fri, 25 Jul 2003 12:24:53 -0400 (EDT) Received: from conversion-daemon.shim2.irt.drexel.edu by shim2.irt.drexel.edu (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0HIL00D019IX7K@shim2.irt.drexel.edu> for manet@ietf.org; Fri, 25 Jul 2003 12:24:53 -0400 (EDT) Received: from glue.irt.drexel.edu (glue.irt.drexel.edu [144.118.25.22]) by shim2.irt.drexel.edu (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0HIL00DCA9LGWH@shim2.irt.drexel.edu> for manet@ietf.org; Fri, 25 Jul 2003 12:24:52 -0400 (EDT) Received: from drexel.edu ([192.168.5.137]) by glue.irt.drexel.edu (8.11.3/8.11.3) with ESMTP id h6PGOq007455 for ; Fri, 25 Jul 2003 12:24:52 -0400 (EDT) Received: from [192.168.5.136] by mail2.prvt.drexel.edu (mshttpd); Fri, 25 Jul 2003 12:24:47 -0400 Date: Fri, 25 Jul 2003 12:24:47 -0400 Subject: Re: [manet] MANET real time applications To: manet@ietf.org Message-id: <1ece31e88c.1e88c1ece3@drexel.edu> MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 1.17 (built Jun 23 2003) Content-type: text/plain; charset=us-ascii Content-language: en Content-disposition: inline Content-transfer-encoding: 7BIT X-Accept-Language: en Priority: 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 Brian, I have been studying QoS for MANETs for quite some time now. I feel that QoS is essentially important for MANETs because of the kinds of applications that are projected from them. Most common among them are in the defence sector and disaster relief operations (comemrcial applications are also being developed like an ad hoc network of a group of cars). This implies that MANETs are going to be widely used for voice communications (between soldiers and rescue workers etc). Here, best effort delivery would not work. Simulations show that one new flow can easily influence the existing flows in terms of their end-to-end latency, packet delivery ratio etc. Also in situtations like war some flows WILL be more important that others and it is necessary that nodes are aware of such differentiation. Current TCP/IP model and MAC 802.11 which aim at being fair to all participating nodes wont work here. I think this is sufficient reason to consider QoS as an important aspect of ad hoc networks. regards, Harpreet ----- Original Message ----- From: BRIAN McBride Date: Thursday, July 24, 2003 12:23 pm Subject: Re: [manet] MANET real time applications > I have been doing QoS (ATM, diffserv etc.) for quite sometime, but > yet have > to find a necessary application other than leased lines and simple > "realtime" vs non-real time. However it does make good research work. > > I am interested in understanding why QoS is important, separating > researchfrom standards development. Is there some work on the > applications of > ad-hoc networking someone could point me to as a starting point? > > I have my theories and the common ones I think, but do not know of > any that > require QoS other than pure fairness amongst all active users. > Seems to me > the nature of ad-hoc is all are fairly treated, to introduce bias > wouldimply some central authority to manage the bias. I always > considered ad-hoc > in the context of free-roaming, independent, individuals in a network. > > Qos leads to guaranteed Qos that inevitably will lead to a claim > that MPLS > and TE must then be applied to mobile ad-hoc networking ;-). > > The obvious app for real-time to me is voice, but it is my choice > of how I > use the bits I am allocated in the network, the network just needs > to offer > me fair access to the bits. > > Thanks, > Brian McBride > > Jon Zeeff wrote: > > > At 10:03 AM 7/24/2003 -0400, Lawrence MacIntyre wrote: > > >I would say that the obvious real-time app for wireless is > > >videoconferencing and the obvious research direction would be > providing> >QOS. > > > > I agree that real-time video is a demanding application and thus > a good > > test case. Also that > > QOS (in it's broadest definition - ie, including multipath > routing, fair > > queuing, non hop-count > > metric based routing, etc) is needed. > > > > _______________________________________________ > > 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 Jul 25 14:13:38 2003 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 OAA14122 for ; Fri, 25 Jul 2003 14:13:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g744-0002Su-Ey for manet-archive@odin.ietf.org; Fri, 25 Jul 2003 14:13:12 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6PIDClO009475 for manet-archive@odin.ietf.org; Fri, 25 Jul 2003 14:13:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g744-0002Sk-B0 for manet-web-archive@optimus.ietf.org; Fri, 25 Jul 2003 14:13: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 OAA14109 for ; Fri, 25 Jul 2003 14:13:07 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g741-0002N4-00 for manet-web-archive@ietf.org; Fri, 25 Jul 2003 14:13:09 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19g741-0002N1-00 for manet-web-archive@ietf.org; Fri, 25 Jul 2003 14:13:09 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19g72v-0002LM-Cc; Fri, 25 Jul 2003 14: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 19g722-0002Kq-8e for manet@optimus.ietf.org; Fri, 25 Jul 2003 14:11: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 OAA14061 for ; Fri, 25 Jul 2003 14:11:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19g71z-0002Mk-00 for manet@ietf.org; Fri, 25 Jul 2003 14:11:03 -0400 Received: from mailserver1.opnet.com ([12.145.55.23]) by ietf-mx with esmtp (Exim 4.12) id 19g71z-0002Mg-00 for manet@ietf.org; Fri, 25 Jul 2003 14:11:03 -0400 Received: from wtn11055.opnet.com (wtn11055.opnet.com [172.16.11.55]) by mailserver1.opnet.com (8.12.9/8.12.8) with ESMTP id h6PIAsA9002117; Fri, 25 Jul 2003 14:10:54 -0400 (EDT) Message-Id: <5.1.0.14.2.20030725133231.0439e510@mailserver.opnet.com> X-Sender: jlee@mailserver.opnet.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 25 Jul 2003 14:10:54 -0400 To: mei-ling.bow@philips.com, manet@ietf.org From: Jay J Lee Subject: Re: [manet] NIST/AODV Problem In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-MailScanner: Not scanned: Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hmm, looks like a problem due to the difference in the version of Modeler the model was created and the version you are using to run them. You should contact the OPNET technical support. They will not be able to debug this problem for you since it is a contributed model but they will certainly help you on debugging process models in general. BTW, I believe several MANET models will be released as a part of OPNET standard model library soon. I am not sure if AODV will be one of them thou. Hope this helps, - Jay At 06:02 PM 7/25/2003 +0200, mei-ling.bow@philips.com wrote: >Hi, > >I have installed the NIST/AODV implementation for OPNET, however each time >I run the simulation, I get either a segmentation violation or a bus >error. Has anyone encountered this problem, or is there something I need >to set in the simulation preferences >or environment? > >Any help would be appreciated, > >Regards, >Mei-Ling > ><<< Program Fault >>> >* Time: 17:00:11 Fri Jul 25 2003 >* Product: modeler >* Program: op_runsim (Version 8.0.C PL7 Build 1252) >* System: SunOS eniac 5.6 Generic_105181-30 sun4u >* Package: process (aodv_routing) at module >(top.sn.mobile_node_0.aodv_routing) >* Function: aodv_routing () [Handle_Breakage enter execs] >* Error: program abort -- bus error > T (272.55), EV (293234), MOD > (top.sn.mobile_node_0.aodv_routing), PROC (aodv_routing) >* Function call stack: (builds down) >------------------------------------------------------------ >Call Block Count Line# Function >------------------------------------------------------------ >0) 1 125 m3_main (argc, argv) >1) 1 519 sim_main (prog_name, argc, argv, dynamic_sim, >def_net_name, num_procs, ...) >2) 1 937 sim_ev_loop () >3) 107074 481 sim_obj_qps_intrpt (simev_ptr) >4) 24888 3576 aodv_routing () [Handle_Breakage enter execs] >------------------------------------------------------------ > > > > >_______________________________________________ >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 Sat Jul 26 00:29:27 2003 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 AAA10902 for ; Sat, 26 Jul 2003 00:29:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19gGfv-0004CP-Tz for manet-archive@odin.ietf.org; Sat, 26 Jul 2003 00:29:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6Q4Stqb016139 for manet-archive@odin.ietf.org; Sat, 26 Jul 2003 00: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 19gGfu-0004CE-DX for manet-web-archive@optimus.ietf.org; Sat, 26 Jul 2003 00:28: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 AAA10877 for ; Sat, 26 Jul 2003 00:28:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19gGfr-0002fO-00 for manet-web-archive@ietf.org; Sat, 26 Jul 2003 00:28:51 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19gGfr-0002fL-00 for manet-web-archive@ietf.org; Sat, 26 Jul 2003 00:28:51 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19gGf3-00049s-V2; Sat, 26 Jul 2003 00: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 19gGeb-00049I-Rb for manet@optimus.ietf.org; Sat, 26 Jul 2003 00:27: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 AAA10834 for ; Sat, 26 Jul 2003 00:27:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19gGeY-0002e3-00 for manet@ietf.org; Sat, 26 Jul 2003 00:27:30 -0400 Received: from exstudent9.city.unisa.edu.au ([130.220.84.78]) by ietf-mx with esmtp (Exim 4.12) id 19gGeW-0002df-00 for manet@ietf.org; Sat, 26 Jul 2003 00:27:30 -0400 Received: by exstudent9.city.unisa.edu.au with Internet Mail Service (5.5.2656.59) id ; Sat, 26 Jul 2003 13:57:25 +0930 Message-ID: From: "Liaw, Yong Shyang - LIAYS001" To: "'Jay J Lee'" , mei-ling.bow@philips.com, manet@ietf.org Subject: RE: [manet] NIST/AODV Problem Date: Sat, 26 Jul 2003 13:57:26 +0930 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , As jay point out, the version of the model you use may need a particular version of Opnet. Check which version of Opnet the model is developed for and try to run on that version of Opnet. This is one bad thing about Opnet. > -----Original Message----- > From: Jay J Lee [mailto:jlee@opnet.com] > Sent: Saturday, 26 July 2003 3:41 > To: mei-ling.bow@philips.com; manet@ietf.org > Subject: Re: [manet] NIST/AODV Problem > > > Hmm, looks like a problem due to the difference in the > version of Modeler > the model was created and the version you are using to run them. You > should contact the OPNET technical support. They will not be > able to debug > this problem for you since it is a contributed model but they will > certainly help you on debugging process models in general. > BTW, I believe several MANET models will be released as a > part of OPNET > standard model library soon. I am not sure if AODV will be > one of them thou. > > Hope this helps, - Jay > > At 06:02 PM 7/25/2003 +0200, mei-ling.bow@philips.com wrote: > >Hi, > > > >I have installed the NIST/AODV implementation for OPNET, > however each time > >I run the simulation, I get either a segmentation violation or a bus > >error. Has anyone encountered this problem, or is there > something I need > >to set in the simulation preferences > >or environment? > > > >Any help would be appreciated, > > > >Regards, > >Mei-Ling > > > ><<< Program Fault >>> > >* Time: 17:00:11 Fri Jul 25 2003 > >* Product: modeler > >* Program: op_runsim (Version 8.0.C PL7 Build 1252) > >* System: SunOS eniac 5.6 Generic_105181-30 sun4u > >* Package: process (aodv_routing) at module > >(top.sn.mobile_node_0.aodv_routing) > >* Function: aodv_routing () [Handle_Breakage enter execs] > >* Error: program abort -- bus error > > T (272.55), EV (293234), MOD > > (top.sn.mobile_node_0.aodv_routing), PROC (aodv_routing) > >* Function call stack: (builds down) > >------------------------------------------------------------ > >Call Block Count Line# Function > >------------------------------------------------------------ > >0) 1 125 m3_main (argc, argv) > >1) 1 519 sim_main (prog_name, argc, argv, dynamic_sim, > >def_net_name, num_procs, ...) > >2) 1 937 sim_ev_loop () > >3) 107074 481 sim_obj_qps_intrpt (simev_ptr) > >4) 24888 3576 aodv_routing () [Handle_Breakage enter execs] > >------------------------------------------------------------ > > > > > > > > > >_______________________________________________ > >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 Sat Jul 26 03:08:06 2003 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 DAA27402 for ; Sat, 26 Jul 2003 03:08:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19gJ9Z-00051P-AG for manet-archive@odin.ietf.org; Sat, 26 Jul 2003 03:07:41 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6Q77fQY019302 for manet-archive@odin.ietf.org; Sat, 26 Jul 2003 03:07:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19gJ9Z-00051F-11 for manet-web-archive@optimus.ietf.org; Sat, 26 Jul 2003 03:07: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 DAA27365 for ; Sat, 26 Jul 2003 03:07:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19gJ9V-0004Qn-00 for manet-web-archive@ietf.org; Sat, 26 Jul 2003 03:07:37 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19gJ9U-0004Qk-00 for manet-web-archive@ietf.org; Sat, 26 Jul 2003 03:07:36 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19gJ8x-0004pL-GI; Sat, 26 Jul 2003 03:07:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19gJ8P-0004ky-CB for manet@optimus.ietf.org; Sat, 26 Jul 2003 03:06:29 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27333 for ; Sat, 26 Jul 2003 03:06:24 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19gJ8L-0004Pf-00 for manet@ietf.org; Sat, 26 Jul 2003 03:06:25 -0400 Received: from inet-tsb.toshiba.co.jp ([202.33.96.40]) by ietf-mx with esmtp (Exim 4.12) id 19gJ8K-0004Pc-00 for manet@ietf.org; Sat, 26 Jul 2003 03:06:24 -0400 Received: from tsb-wall.toshiba.co.jp ([133.199.160.134]) by inet-tsb.toshiba.co.jp with ESMTP id h6Q76OVj002617 for ; Sat, 26 Jul 2003 16:06:24 +0900 (JST) Received: (from root@localhost) by tsb-wall.toshiba.co.jp id h6Q76Or7021312 for ; Sat, 26 Jul 2003 16:06:24 +0900 (JST) Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id SAA21310 ; Sat, 26 Jul 2003 16:06:24 +0900 Received: from mx2.toshiba.co.jp by tis2.tis.toshiba.co.jp id QAA24421; Sat, 26 Jul 2003 16:06:23 +0900 (JST) Received: from m400.sitc.toshiba.co.jp by toshiba.co.jp id QAA23020; Sat, 26 Jul 2003 16:06:22 +0900 (JST) Received: from AYA ([133.196.175.144]) by m400.sitc.toshiba.co.jp (Mirapoint Messaging Server MOS 3.2.2-GA) with ESMTP id AAR40788; Sat, 26 Jul 2003 16:06:21 +0900 (JST) To: manet@ietf.org Subject: Re: [manet] Q. about RFC3561 From: YAMADA Tatsuya References: <200307241828.BCC92371.EZN@sitc.toshiba.co.jp> <16160.3631.416864.743074@gargle.gargle.HOWL> In-Reply-To: <16160.3631.416864.743074@gargle.gargle.HOWL> Message-Id: <200307261605.DEB82904.EZN@sitc.toshiba.co.jp> X-Mailer: Winbiff [Version 2.42 PL2] X-Accept-Language: ja,en Date: Sat, 26 Jul 2003 16:06:21 +0900 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: , Hello, Thank you for your reply. Added word and your comment solve my misunderstanding. I think that it is better to rewrite it as described below in a next version draft. Best regards, > This paragraph is not describing management of routing table entries > but each nodes own "destination sequence number". In AODV each node > maintains it's own destination sequence number therefore specifying > originator or destination is slightly redundant (but correct in the > context of each bullet) in this paragraph. I'll try to make it more > clear in future drafts. > > Does this re-write remove the confusion? > > guarantee the loop-freedom of all routes towards that node. A node > increments its own sequence number in two circumstances: > > - Immediately before a originating node starts a route discovery, it > MUST increment its own sequence number. This prevents conflicts > with previously established reverse routes towards the > originator of a RREQ. > > - Immediately before a destination node issues a route reply in > response to a RREQ, it MUST update its own sequence number to the > maximum of its current sequence number and the destination > sequence number in the RREQ packet. > > Ian Chakeres ---- YAMADA Tatsuya / mailto:tatsuya10.yamada@toshiba.co.jp Software Technology Group 2, Software Engineering Center, Toshiba Corp. Tel: +81-44-549-2404 / Fax: +81-44-549-5484 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Sat Jul 26 14:16:46 2003 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 OAA14433 for ; Sat, 26 Jul 2003 14:16: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 19gTae-0007ok-C3 for manet-archive@odin.ietf.org; Sat, 26 Jul 2003 14:16:20 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6QIGKLv030046 for manet-archive@odin.ietf.org; Sat, 26 Jul 2003 14:16:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19gTae-0007oX-9J for manet-web-archive@optimus.ietf.org; Sat, 26 Jul 2003 14:16: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 OAA14427 for ; Sat, 26 Jul 2003 14:16:15 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19gTab-00040J-00 for manet-web-archive@ietf.org; Sat, 26 Jul 2003 14:16:17 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19gTab-00040F-00 for manet-web-archive@ietf.org; Sat, 26 Jul 2003 14:16:17 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19gTZO-0007k3-Bd; Sat, 26 Jul 2003 14:15:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19gTZ7-0007j2-Am for manet@optimus.ietf.org; Sat, 26 Jul 2003 14:14: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 OAA14415 for ; Sat, 26 Jul 2003 14:14:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19gTZ4-0003zk-00 for manet@ietf.org; Sat, 26 Jul 2003 14:14:42 -0400 Received: from h008.c000.snv.cp.net ([209.228.32.72] helo=c000.snv.cp.net) by ietf-mx with smtp (Exim 4.12) id 19gTZ4-0003zh-00 for manet@ietf.org; Sat, 26 Jul 2003 14:14:42 -0400 Received: (cpmta 15599 invoked from network); 26 Jul 2003 11:14:41 -0700 Received: from 12.221.64.123 (HELO cs.uiuc.edu) by smtp.carter.net (209.228.32.72) with SMTP; 26 Jul 2003 11:14:41 -0700 X-Sent: 26 Jul 2003 18:14:41 GMT Message-ID: <3F22C308.3060903@cs.uiuc.edu> Date: Sat, 26 Jul 2003 13:06:00 -0500 From: Casey Carter User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 X-Accept-Language: en-us, en MIME-Version: 1.0 To: idc@cs.ucsb.edu CC: YAMADA Tatsuya , MANET Mailing List Subject: Re: [manet] Q. about RFC3561 References: <200307241828.BCC92371.EZN@sitc.toshiba.co.jp> <16160.3631.416864.743074@gargle.gargle.HOWL> In-Reply-To: <16160.3631.416864.743074@gargle.gargle.HOWL> 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 Ian Chakeres wrote: >This paragraph is not describing management of routing table entries >but each nodes own "destination sequence number". In AODV each node >maintains it's own destination sequence number therefore specifying >originator or destination is slightly redundant (but correct in the >context of each bullet) in this paragraph. I'll try to make it more >clear in future drafts. > >Does this re-write remove the confusion? > > guarantee the loop-freedom of all routes towards that node. A node > increments its own sequence number in two circumstances: > > - Immediately before a originating node starts a route discovery, it > MUST increment its own sequence number. This prevents conflicts > with previously established reverse routes towards the > originator of a RREQ. > > - Immediately before a destination node issues a route reply in > response to a RREQ, it MUST update its own sequence number to the > maximum of its current sequence number and the destination > sequence number in the RREQ packet. > > Doesn't this text (from Section 6.1) conflict with: 6.6.1. Route Reply Generation by the Destination If the generating node is the destination itself, it MUST increment its own sequence number by one if the sequence number in the RREQ packet is equal to that incremented value. Otherwise, the destination does not change its sequence number before generating the RREP message. The destination node places its (perhaps newly incremented) sequence number into the Destination Sequence Number field of the RREP, and enters the value zero in the Hop Count field of the RREP. Is there an internal inconsistency in the document, or am I missing something? -- Casey Carter Casey@Carter.net ccarter@cs.uiuc.edu AIM: cartec69 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 28 03:38:25 2003 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 DAA21503 for ; Mon, 28 Jul 2003 03:38:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h2Zx-0002eb-4Q for manet-archive@odin.ietf.org; Mon, 28 Jul 2003 03:37:57 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6S7bvc2010198 for manet-archive@odin.ietf.org; Mon, 28 Jul 2003 03:37:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h2Zw-0002eP-Oq for manet-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 03: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 DAA21483 for ; Mon, 28 Jul 2003 03:37:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19h2Zu-0005z9-00 for manet-web-archive@ietf.org; Mon, 28 Jul 2003 03:37:54 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19h2Zt-0005z5-00 for manet-web-archive@ietf.org; Mon, 28 Jul 2003 03:37:53 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h2Z3-0002MD-Ig; Mon, 28 Jul 2003 03:37:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h2Ym-0002Kw-Cp for manet@optimus.ietf.org; Mon, 28 Jul 2003 03:36: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 DAA21451 for ; Mon, 28 Jul 2003 03:36:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19h2Yj-0005xy-00 for manet@ietf.org; Mon, 28 Jul 2003 03:36:41 -0400 Received: from odin.unik.no ([193.156.96.7]) by ietf-mx with esmtp (Exim 4.12) id 19h2Yi-0005xg-00 for manet@ietf.org; Mon, 28 Jul 2003 03:36:40 -0400 Received: from freya.unik.no ([193.156.96.215]) by odin.unik.no with esmtp (Exim 3.36 #12) id 19h2Y1-0007na-00; Mon, 28 Jul 2003 09:35:57 +0200 Received: from [193.156.97.98] (helo=unik.no) by freya.unik.no with esmtp (Exim 3.36 #12) id 19h2Y1-0006TD-00; Mon, 28 Jul 2003 09:35:57 +0200 Message-ID: <3F24D2DA.5030408@unik.no> Date: Mon, 28 Jul 2003 09:38:02 +0200 From: Frank Li User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dr Manthos Kazantzidis CC: manet@ietf.org Subject: Re: [manet] bandwidth calculation at a node References: <3F1F6791@webmail.drexel.edu> <3F1F9290.4030107@cs.uni-bonn.de> <00d701c35214$04262c60$0100007f@manthosm50> Content-Type: multipart/alternative; boundary="------------010006080002010500070909" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --------------010006080002010500070909 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hello Manthos, We recently built an ns2 model similar to your ISCC'02 paper, trying to measure the available bandwidth (throughput) using probe packets. There are three nodes within the transmission range, one receiver plus two senders. The first sender is transmitting ordinary CBR traffic to the receiver while the other one sends regularly probe packets to the same receiver. The probe packets were sent at quite low bitrate to avoid 'stealing' much bandwidth from CBR traffic when the load is heavy. We measure the packet throughput by packet_length/(T_ack - T_send) and the measured throughput is the average value from, say, 30 probe packets. The preliminary results show that the measured throughput is almost the same as the maximum throughput when there is no CBR traffic. But as the load from ordinary source inceases, the results become more and more unrealiable, especially when the channel is saturated. For instance, when the offered CBR load > maximum throughput, the probing node can still obtain quite high 'available' bandwidth. However, the measured throughput roughly reflects the channel congestion status. So I basically feel that this probing-based method may not act as an accurate measurement for available bandwidth, but only as an indicator for channel condition. You claimed in sec. 3.1 of your paper that 'our measurement is very accurate under low load conditions'. How about the case when the load is heavy? Could you please post more results? BR, Frank Dr Manthos Kazantzidis wrote: >Hi Harpreet and Christian, > > While I agree with the email, I wanted to add that there >is an issue of available bandwidth definition and measurement >method. For example if there is a local measurement >that takes into account the MAC mechanisms then one >can say that the available bandwidth can be predicted at some >value - of course this does not imply when you sent a packet >it will be received but just that under some scheduling (similar to such of >the past >if you will) if no additional flows enter the link etc the available >bandwidth will be that. > >At > >End-to-end versus Explicit Feedback Measurement in 802.11 Networks -ISCC02 > >downloadable from http://www.cs.ucla.edu/~kazantz/ > >I am attempting a per-neighbour measurement of available bandwidth >using the ACK times. > >I am considering the neighbour and neighbour's neighborhood by combining >a source, destination specific throughput measurement >(which indirectly depends on 802.11 timers) with the node utilization. >If the paper is not very clear I can post additional slides and some >results that show that -in simulation- works very well for multimedia >adaptation, if interested. > >Regards, >Manthos > >PS: I have not read that paper but will do. > >----- Original Message ----- >From: "Christian de Waal" >To: "Harpreet Arora" ; >Sent: Thursday, July 24, 2003 1:02 AM >Subject: Re: [manet] bandwidth calculation at a node > > > > >>Hi Harpreet, >> >>QoS assurances are not possible in 802.11 DCF networks. Period. To make >>assurances, you need something like a slotted MAC layer, because >>"simply" knowing the available bandwidth at the sending and at the >>receiving station is not enough: The stations also have to negotiate at >>what times the medium is free at _both_ stations. If half of the link >>bandwidth is available at both stations, but one station is blocked when >>the other is not and vice versa, then these stations cannot communicate >>unless some re-scheduling is performed. >> >>I can once again point you to our ASWN'03 paper which describes these >>difficulties in detail. >> >>http://web.informatik.uni-bonn.de/IV/Mitarbeiter/dewaal/aswn03.html >> >>Best regards, >>Christian >> >> >>Harpreet Arora wrote: >> >> >> >>>Thanks Philippe. This is certainly useful. However, the paper assumes >>> >>> >that a > > >>>channel is divided into time slots and reservations are made by >>> >>> >reserving > > >>>time slots. I am trying to figure out if it is possible to make QoS >>>assurances in an 802.11-DCF based network. In such a network, each >>> >>> >node > > >>>has to keep track of the amount of bandwidth which is being used by the >>>neighboring nodes (nodes which are transmitting within the interference >>>range of this node) before it can make any reservations or admission >>>control decisions. Is there any work done which discusses how bandwidth >>> >>> >can > > >>>be calculated in this scenario? >>> >>>thanks, >>>Harpreet >>> >>> >>-- >>____________________________________________________________________ >>Christian de Waal >> >>University of Bonn Phone: +49 228 73-4548 >>Institute of Computer Science IV Fax: +49 228 73-4571 >>Roemerstr. 164 E-mail: dewaal@cs.uni-bonn.de >>53117 Bonn, Germany http://www.cs.uni-bonn.de/IV/ >> >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > --------------010006080002010500070909 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Manthos,

We recently built an ns2 model  similar to your ISCC'02 paper,  trying to measure the available bandwidth (throughput) using probe packets. There are three nodes within the transmission range, one receiver plus two senders. The first sender is transmitting ordinary CBR traffic to the receiver while the other one sends regularly probe packets to the same receiver. The probe packets were sent at quite low bitrate to avoid 'stealing' much bandwidth  from  CBR traffic when the load is heavy. We measure the packet throughput by packet_length/(T_ack - T_send) and the measured throughput is the average value from, say, 30 probe packets.

The preliminary results show that the measured throughput is almost the same as the maximum throughput when there is no CBR traffic. But as the load from ordinary source inceases, the results become more and more unrealiable, especially when the channel is saturated.  For instance, when the offered CBR load > maximum throughput,  the probing node can still obtain quite high 'available' bandwidth. However, the measured throughput roughly reflects the channel congestion status.

So I basically feel that this probing-based method may not act as an accurate measurement for available bandwidth, but only as an indicator for channel condition. You claimed in sec. 3.1 of your paper that 'our measurement is very accurate under low load conditions'. How about the case when the load is heavy? Could you please post more results?

BR,
Frank



Dr Manthos Kazantzidis wrote:
Hi Harpreet and Christian,

 While I agree with the email, I wanted to add that there
is an issue of available bandwidth definition and measurement
method. For example if there is a local measurement
that takes into account the MAC mechanisms then one
can say that the available bandwidth can be predicted at some
value - of course this does not imply when you sent a packet
it will be received but just that under some scheduling (similar to such of
the past
if you will) if no additional flows enter the link etc the available
bandwidth will be that.

At

End-to-end versus Explicit Feedback Measurement in 802.11 Networks -ISCC02

downloadable from http://www.cs.ucla.edu/~kazantz/

I am attempting a per-neighbour measurement of available bandwidth
using the ACK times.

I am considering the neighbour and neighbour's neighborhood by combining
a source, destination specific throughput measurement
(which indirectly depends on 802.11 timers) with the node utilization.
If the paper is not very clear I can post additional slides and some
results that show that -in simulation- works very well for multimedia
adaptation, if interested.

Regards,
Manthos

PS: I have not read that paper but will do.

----- Original Message ----- 
From: "Christian de Waal" <dewaal@cs.uni-bonn.de>
To: "Harpreet Arora" <ha33@drexel.edu>; <manet@ietf.org>
Sent: Thursday, July 24, 2003 1:02 AM
Subject: Re: [manet] bandwidth calculation at a node


  
Hi Harpreet,

QoS assurances are not possible in 802.11 DCF networks. Period. To make
assurances, you need something like a slotted MAC layer, because
"simply" knowing the available bandwidth at the sending and at the
receiving station is not enough: The stations also have to negotiate at
what times the medium is free at _both_ stations. If half of the link
bandwidth is available at both stations, but one station is blocked when
the other is not and vice versa, then these stations cannot communicate
unless some re-scheduling is performed.

I can once again point you to our ASWN'03 paper which describes these
difficulties in detail.

http://web.informatik.uni-bonn.de/IV/Mitarbeiter/dewaal/aswn03.html

Best regards,
Christian


Harpreet Arora wrote:

    
Thanks Philippe. This is certainly useful. However, the paper assumes
      
that a
  
channel is divided into time slots and reservations are made by
      
reserving
  
time slots. I am trying to figure out if it is possible to make QoS
assurances in an 802.11-DCF   based network.  In such a network, each
      
node
  
has to keep track of the amount of bandwidth which is being used by the
neighboring nodes (nodes which are transmitting within the interference
range of  this node) before it can make any reservations or admission
control decisions. Is there any work done which discusses how bandwidth
      
can
  
be calculated in this scenario?

thanks,
Harpreet
      
-- 
____________________________________________________________________
Christian de Waal

University of Bonn                            Phone: +49 228 73-4548
Institute of Computer Science IV                Fax: +49 228 73-4571
Roemerstr. 164                         E-mail: dewaal@cs.uni-bonn.de
53117 Bonn, Germany                    http://www.cs.uni-bonn.de/IV/


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


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


--------------010006080002010500070909-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 28 03:42:06 2003 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 DAA21745 for ; Mon, 28 Jul 2003 03:42:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h2dW-0003D1-3Q for manet-archive@odin.ietf.org; Mon, 28 Jul 2003 03:41:38 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6S7fcwj012329 for manet-archive@odin.ietf.org; Mon, 28 Jul 2003 03:41:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h2dV-0003Ci-VT for manet-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 03:41:38 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21708 for ; Mon, 28 Jul 2003 03:41:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19h2dT-000663-00 for manet-web-archive@ietf.org; Mon, 28 Jul 2003 03:41:35 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19h2dS-000660-00 for manet-web-archive@ietf.org; Mon, 28 Jul 2003 03:41:34 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h2cw-0002xy-CM; Mon, 28 Jul 2003 03: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 19h2cD-0002wY-VU for manet@optimus.ietf.org; Mon, 28 Jul 2003 03:40: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 DAA21583 for ; Mon, 28 Jul 2003 03:40:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19h2cB-00062L-00 for manet@ietf.org; Mon, 28 Jul 2003 03:40:15 -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 19h2cA-00062B-00 for manet@ietf.org; Mon, 28 Jul 2003 03:40:14 -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 h6S7e9NQ025200; Mon, 28 Jul 2003 09:40:09 +0200 (MEST) Message-ID: <3F24D354.3000207@informatik.uni-ulm.de> Date: Mon, 28 Jul 2003 09:40:04 +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: Aruna Balasubramanian CC: manet@ietf.org Subject: Re: [manet] Key management References: In-Reply-To: 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-dmv.com-Metrics: gemini 1181; 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 Aruna Balasubramanian wrote: > I am a student in the University at Buffalo and am working on security > for wireless networks. > I have developed a key management protocol but i am not sure how I can > test it. Even if i do use GlomoSim to simulate the protocol, how do i test > its usefulness in terms of security > Could someone please help There are a number of formal methods that _TRY_ to verify the correctness of authentication protocolls etc. One of the basic mechanisms is the BAN logic. See @article{ burrows90logic, author = "Michael Burrows and Mart{\'i}n Abadi and Roger M. Needham", title = "{A Logic of Authentication}", journal = "ACM Transactions on Computer Systems", volume = "8", number = "1", pages = "18--36", year = "1990" } for details. There are a number of derived or similar mechanisms like GAN, Abadi-Tuttle etc. One could also use verification tools like the NRL analyzer. Simulations will only give you information on runtime properties of your protocol, like overhead etc. To actually proof the correctness is a complex and hard job. 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/ <--- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 28 05:01:32 2003 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 FAA24587 for ; Mon, 28 Jul 2003 05:01:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h3sQ-0005xz-6V for manet-archive@odin.ietf.org; Mon, 28 Jul 2003 05:01:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6S9167s022935 for manet-archive@odin.ietf.org; Mon, 28 Jul 2003 05:01:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h3sP-0005xq-Vg for manet-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 05:01: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 FAA24548 for ; Mon, 28 Jul 2003 05:01:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19h3sM-0007VL-00 for manet-web-archive@ietf.org; Mon, 28 Jul 2003 05:01:02 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19h3sM-0007VI-00 for manet-web-archive@ietf.org; Mon, 28 Jul 2003 05:01:02 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h3rO-0005pQ-Kj; Mon, 28 Jul 2003 05:00:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19h3qu-0005ob-ID for manet@optimus.ietf.org; Mon, 28 Jul 2003 04:59: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 EAA24500 for ; Mon, 28 Jul 2003 04:59:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19h3qr-0007U2-00 for manet@ietf.org; Mon, 28 Jul 2003 04:59:29 -0400 Received: from periwinkle.noc.ucla.edu ([169.232.47.11]) by ietf-mx with esmtp (Exim 4.12) id 19h3qq-0007Tz-00 for manet@ietf.org; Mon, 28 Jul 2003 04:59:28 -0400 Received: from manthosm50 (Panther.CS.UCLA.EDU [131.179.128.25]) by periwinkle.noc.ucla.edu (8.12.8/8.12.8) with SMTP id h6S8xMQh026640; Mon, 28 Jul 2003 01:59:23 -0700 Message-ID: <020c01c354e6$3042a0b0$0f02000a@manthosm50> From: "Dr Manthos Kazantzidis" To: "Frank Li" Cc: References: <3F1F6791@webmail.drexel.edu> <3F1F9290.4030107@cs.uni-bonn.de> <00d701c35214$04262c60$0100007f@manthosm50> <3F24D2DA.5030408@unik.no> Subject: Re: [manet] bandwidth calculation at a node Date: Mon, 28 Jul 2003 01:56:47 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0209_01C354AB.80CDAF10" 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 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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_0209_01C354AB.80CDAF10 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Frank, My suggestions are: 1- Check that your CBR source does not create any synchronization effect in the simulation. If so, you cannot measure accurately (that would not happen in a real scenario). Use a source (can be CBR viewed=20 at a larger interval) that has a random=20 packet interarrival time for example. 2- As the congestion increases your sample variance increases and you would need more samples to=20 find the available bandwidth. Some samples will be at maximum throughput since they will only be affected by a small carrier sense interval if they do not coincide with a CBR traffic packet.=20 3- Take into account lost packets as well in case you do not. I believe that measurement proposed is very accurate bc it indirectly takes into account MAC collision avoidance=20 timers that 'sense' the neighborhood contention . I hope this helps Manthos ----- Original Message -----=20 From: Frank Li=20 To: Dr Manthos Kazantzidis=20 Cc: manet@ietf.org=20 Sent: Monday, July 28, 2003 12:38 AM Subject: Re: [manet] bandwidth calculation at a node Hello Manthos, We recently built an ns2 model similar to your ISCC'02 paper, trying = to measure the available bandwidth (throughput) using probe packets. = There are three nodes within the transmission range, one receiver plus = two senders. The first sender is transmitting ordinary CBR traffic to = the receiver while the other one sends regularly probe packets to the = same receiver. The probe packets were sent at quite low bitrate to avoid = 'stealing' much bandwidth from CBR traffic when the load is heavy. We = measure the packet throughput by packet_length/(T_ack - T_send) and the = measured throughput is the average value from, say, 30 probe packets.=20 The preliminary results show that the measured throughput is almost = the same as the maximum throughput when there is no CBR traffic. But as = the load from ordinary source inceases, the results become more and more = unrealiable, especially when the channel is saturated. For instance, = when the offered CBR load > maximum throughput, the probing node can = still obtain quite high 'available' bandwidth. However, the measured = throughput roughly reflects the channel congestion status.=20 So I basically feel that this probing-based method may not act as an = accurate measurement for available bandwidth, but only as an indicator = for channel condition. You claimed in sec. 3.1 of your paper that 'our = measurement is very accurate under low load conditions'. How about the = case when the load is heavy? Could you please post more results?=20 BR, Frank Dr Manthos Kazantzidis wrote: Hi Harpreet and Christian, While I agree with the email, I wanted to add that there is an issue of available bandwidth definition and measurement method. For example if there is a local measurement that takes into account the MAC mechanisms then one can say that the available bandwidth can be predicted at some value - of course this does not imply when you sent a packet it will be received but just that under some scheduling (similar to such = of the past if you will) if no additional flows enter the link etc the available bandwidth will be that. At End-to-end versus Explicit Feedback Measurement in 802.11 Networks = -ISCC02 downloadable from http://www.cs.ucla.edu/~kazantz/ I am attempting a per-neighbour measurement of available bandwidth using the ACK times. I am considering the neighbour and neighbour's neighborhood by combining a source, destination specific throughput measurement (which indirectly depends on 802.11 timers) with the node utilization. If the paper is not very clear I can post additional slides and some results that show that -in simulation- works very well for multimedia adaptation, if interested. Regards, Manthos PS: I have not read that paper but will do. ----- Original Message -----=20 From: "Christian de Waal" To: "Harpreet Arora" ; Sent: Thursday, July 24, 2003 1:02 AM Subject: Re: [manet] bandwidth calculation at a node Hi Harpreet, QoS assurances are not possible in 802.11 DCF networks. Period. To make assurances, you need something like a slotted MAC layer, because "simply" knowing the available bandwidth at the sending and at the receiving station is not enough: The stations also have to negotiate at what times the medium is free at _both_ stations. If half of the link bandwidth is available at both stations, but one station is blocked when the other is not and vice versa, then these stations cannot communicate unless some re-scheduling is performed. I can once again point you to our ASWN'03 paper which describes these difficulties in detail. http://web.informatik.uni-bonn.de/IV/Mitarbeiter/dewaal/aswn03.html Best regards, Christian Harpreet Arora wrote: Thanks Philippe. This is certainly useful. However, the paper = assumes that a channel is divided into time slots and reservations are made by reserving time slots. I am trying to figure out if it is possible to make QoS assurances in an 802.11-DCF based network. In such a network, each node has to keep track of the amount of bandwidth which is being used by = the neighboring nodes (nodes which are transmitting within the interference range of this node) before it can make any reservations or admission control decisions. Is there any work done which discusses how bandwidth can be calculated in this scenario? thanks, Harpreet --=20 ____________________________________________________________________ Christian de Waal University of Bonn Phone: +49 228 73-4548 Institute of Computer Science IV Fax: +49 228 73-4571 Roemerstr. 164 E-mail: dewaal@cs.uni-bonn.de 53117 Bonn, Germany http://www.cs.uni-bonn.de/IV/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet =20 ------=_NextPart_000_0209_01C354AB.80CDAF10 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Dear Frank,
 
My suggestions are:
 
1- Check that your CBR source does not = create
any synchronization effect in the simulation. If=20 so,
you cannot measure accurately (that would not=20 happen
in a real scenario). Use a source (can be CBR viewed =
at a larger interval) that has = a random=20
packet interarrival time for example.
 
2-  As the congestion increases your sample=20 variance
increases and you would need more samples to =
find the available bandwidth. Some samples will be=20 at
maximum throughput since they will only be=20 affected
by a small carrier sense interval if they do not=20 coincide
with a CBR traffic packet.
 
3- Take into account lost packets as well in case = you do=20 not.
 
I believe that measurement proposed is very accurate = bc
it indirectly takes into account MAC collision = avoidance=20
timers that 'sense' the neighborhood contention = .
 
I hope this helps
 
Manthos
 
----- Original Message -----
From:=20 Frank = Li
Sent: Monday, July 28, 2003 = 12:38=20 AM
Subject: Re: [manet] bandwidth=20 calculation at a node

Hello=20 Manthos,

We recently built an ns2 model  similar to your = ISCC'02=20 paper,  trying to measure the available bandwidth (throughput) = using=20 probe packets. There are three nodes within the transmission range, = one=20 receiver plus two senders. The first sender is transmitting ordinary = CBR=20 traffic to the receiver while the other one sends regularly probe = packets to=20 the same receiver. The probe packets were sent at quite low bitrate to = avoid=20 'stealing' much bandwidth  from  CBR traffic when the load = is heavy.=20 We measure the packet throughput by packet_length/(T_ack - T_send) and = the=20 measured throughput is the average value from, say, 30 probe packets.=20

The preliminary results show that the measured throughput is = almost=20 the same as the maximum throughput when there is no CBR traffic. But = as the=20 load from ordinary source inceases, the results become more and more=20 unrealiable, especially when the channel is saturated.  For = instance,=20 when the offered CBR load > maximum throughput,  the probing = node can=20 still obtain quite high 'available' bandwidth. However, the measured=20 throughput roughly reflects the channel congestion status.

So = I=20 basically feel that this probing-based method may not act as an = accurate=20 measurement for available bandwidth, but only as an indicator for = channel=20 condition. You claimed in sec. 3.1 of your paper that 'our measurement = is very=20 accurate under low load conditions'. How about the case when the load = is=20 heavy? Could you please post more results?=20

BR,
Frank



Dr Manthos Kazantzidis wrote:
Hi Harpreet and Christian,

 While I agree with the email, I wanted to add that there
is an issue of available bandwidth definition and measurement
method. For example if there is a local measurement
that takes into account the MAC mechanisms then one
can say that the available bandwidth can be predicted at some
value - of course this does not imply when you sent a packet
it will be received but just that under some scheduling (similar to such =
of
the past
if you will) if no additional flows enter the link etc the available
bandwidth will be that.

At

End-to-end versus Explicit Feedback Measurement in 802.11 Networks =
-ISCC02

downloadable from http://www.cs.ucla.edu/~kazantz=
/

I am attempting a per-neighbour measurement of available bandwidth
using the ACK times.

I am considering the neighbour and neighbour's neighborhood by combining
a source, destination specific throughput measurement
(which indirectly depends on 802.11 timers) with the node utilization.
If the paper is not very clear I can post additional slides and some
results that show that -in simulation- works very well for multimedia
adaptation, if interested.

Regards,
Manthos

PS: I have not read that paper but will do.

----- Original Message -----=20
From: "Christian de Waal" <dewaal@cs.uni-bonn.de>
To: "Harpreet Arora" <ha33@drexel.edu>; <manet@ietf.org>
Sent: Thursday, July 24, 2003 1:02 AM
Subject: Re: [manet] bandwidth calculation at a node


  
Hi Harpreet,

QoS assurances are not possible in 802.11 DCF networks. Period. To make
assurances, you need something like a slotted MAC layer, because
"simply" knowing the available bandwidth at the sending and at the
receiving station is not enough: The stations also have to negotiate at
what times the medium is free at _both_ stations. If half of the link
bandwidth is available at both stations, but one station is blocked when
the other is not and vice versa, then these stations cannot communicate
unless some re-scheduling is performed.

I can once again point you to our ASWN'03 paper which describes these
difficulties in detail.

http://web.informatik.uni-bonn.de/IV/Mitarbeiter/dewaal/aswn03.html

Best regards,
Christian


Harpreet Arora wrote:

    
Thanks Philippe. This is =
certainly useful. However, the paper assumes
      
that a
  
channel is divided into =
time slots and reservations are made by
      
reserving
  
time slots. I am trying =
to figure out if it is possible to make QoS
assurances in an 802.11-DCF   based network.  In such a network, each
      
node
  
has to keep track of the =
amount of bandwidth which is being used by the
neighboring nodes (nodes which are transmitting within the interference
range of  this node) before it can make any reservations or admission
control decisions. Is there any work done which discusses how bandwidth
      
can
  
be calculated in this =
scenario?

thanks,
Harpreet
      
--=20
____________________________________________________________________
Christian de Waal

University of Bonn                            Phone: +49 228 73-4548
Institute of Computer Science IV                Fax: +49 228 73-4571
Roemerstr. 164                         E-mail: dewaal@cs.uni-bonn.de
53117 Bonn, Germany                    http://www.cs.uni-bonn.de/IV/


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


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


------=_NextPart_000_0209_01C354AB.80CDAF10-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 28 11:40:19 2003 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 LAA07879 for ; Mon, 28 Jul 2003 11:40:19 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hA6J-0003AW-MJ for manet-archive@odin.ietf.org; Mon, 28 Jul 2003 11:39:52 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6SFdpf1012174 for manet-archive@odin.ietf.org; Mon, 28 Jul 2003 11:39:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hA6J-0003AH-IB for manet-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 11:39: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 LAA07865 for ; Mon, 28 Jul 2003 11:39:47 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hA6I-0004KO-00 for manet-web-archive@ietf.org; Mon, 28 Jul 2003 11:39:50 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hA6H-0004KL-00 for manet-web-archive@ietf.org; Mon, 28 Jul 2003 11:39:49 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hA5V-00033X-7W; Mon, 28 Jul 2003 11: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 19hA4k-00033D-8i for manet@optimus.ietf.org; Mon, 28 Jul 2003 11:38: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 LAA07755 for ; Mon, 28 Jul 2003 11:38:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hA4i-0004IT-00 for manet@ietf.org; Mon, 28 Jul 2003 11:38:12 -0400 Received: from thoth.sbs.de ([192.35.17.2]) by ietf-mx with esmtp (Exim 4.12) id 19hA4h-0004IO-00 for manet@ietf.org; Mon, 28 Jul 2003 11:38:12 -0400 Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by thoth.sbs.de (8.11.7/8.11.7) with ESMTP id h6SFc8Z00186; Mon, 28 Jul 2003 17:38:09 +0200 (MEST) Received: from mchp9daa.mch.sbs.de (mchp9daa.mch.sbs.de [139.25.137.99]) by mail2.siemens.de (8.11.7/8.11.7) with ESMTP id h6SFc8R19688; Mon, 28 Jul 2003 17:38:08 +0200 (MEST) Received: by mchp9daa.mch.sbs.de with Internet Mail Service (5.5.2653.19) id ; Mon, 28 Jul 2003 17:38:07 +0200 Message-ID: <12D31B803B18D4119958009027FD42B8042539E9@mchp952a.mch.sbs.de> From: Bahr Michael To: idc@cs.ucsb.edu Cc: MANET Mailing List Subject: AW: [manet] Q. about RFC3561 Date: Mon, 28 Jul 2003 17:38:06 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 Ian, I think the text is still a little bit confusing, considering that your comment is not in the RFC. Without your comment, it is not really = clear, whether the node in the paragraph before the bullets is the same as the originating node of the first bullet and the destination node in the = second bullet. How about the following wording? guarantee the loop-freedom of all routes towards that node. A node increments its own sequence number in two circumstances: - Immediately before a node originates a route discovery, it MUST increment its own sequence number. This prevents conflicts with previously established reverse routes towards the originator of a RREQ. - Immediately before a node, being the destination node, issues a = route reply in response to a RREQ, it MUST update its own sequence number to the maximum of its current sequence number and the destination sequence number in the RREQ packet. (The first bullet is actually the original text from RFC 3561.) Best regards, Michael Bahr --=20 Michael Bahr Siemens Corporate Technology Munich, Germany > -----Urspr=FCngliche Nachricht----- > Von: Ian Chakeres [mailto:idc@engineering.ucsb.edu] > Gesendet am: Donnerstag, 24. Juli 2003 18:50 > An: YAMADA Tatsuya > Cc: MANET Mailing List > Betreff: RE:[manet] Q. about RFC3561 >=20 >=20 > This paragraph is not describing management of routing table entries > but each nodes own "destination sequence number". In AODV each node > maintains it's own destination sequence number therefore specifying > originator or destination is slightly redundant (but correct in the > context of each bullet) in this paragraph. I'll try to make it more > clear in future drafts. >=20 > Does this re-write remove the confusion? >=20 > guarantee the loop-freedom of all routes towards that node. A = node > increments its own sequence number in two circumstances: >=20 > - Immediately before a originating node starts a route=20 > discovery, it > MUST increment its own sequence number. This prevents = conflicts > with previously established reverse routes towards the > originator of a RREQ. >=20 > - Immediately before a destination node issues a route reply in > response to a RREQ, it MUST update its own sequence number to = the > maximum of its current sequence number and the destination > sequence number in the RREQ packet. >=20 > Ian Chakeres >=20 > >YAMADA Tatsuya wrote: > >Hello all, > > > >I have a question about RFC3561. Section 6.1. is written as below, > > > >>6.1. Maintaining Sequence Numbers > >(snip) > >> guarantee the loop-freedom of all routes towards that node. A > >> destination node increments its own sequence number in two > >> circumstances: > >> > >> - Immediately before a node originates a route=20 > discovery, it MUST > >> increment its own sequence number. This prevents=20 > conflicts with > >> previously established reverse routes towards the=20 > originator of a > >> RREQ. > > > >Does "a node" in first item mean "an originator" ? > > > >If so, it shold be written like that explicitly. > > > >If not so, could you tell me when a destination node has to=20 > originate a=20 > >route discovery ? > >(When a destination node will reply a RREP, a route from a=20 > destination to=20 > >an originator (and vice versa) has been already established,=20 > I think.) > > > > > >Or does "a node" mean both ? > > > > > >Best Regards, > > > >---- > >YAMADA Tatsuya / mailto:tatsuya10.yamada@toshiba.co.jp > >Software Technology Group 2, Software Engineering Center,=20 > Toshiba Corp. > >Tel: +81-44-549-2404 / Fax: +81-44-549-5484 > > > >_______________________________________________ > >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 >=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Mon Jul 28 16:16:53 2003 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 QAA19657 for ; Mon, 28 Jul 2003 16:16:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hEPz-0001I0-4s for manet-archive@odin.ietf.org; Mon, 28 Jul 2003 16:16:27 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6SKGRUi004952 for manet-archive@odin.ietf.org; Mon, 28 Jul 2003 16:16:27 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hEPz-0001Hn-0n for manet-web-archive@optimus.ietf.org; Mon, 28 Jul 2003 16:16: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 QAA19604 for ; Mon, 28 Jul 2003 16:15:49 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hEPP-0007Ya-00 for manet-web-archive@ietf.org; Mon, 28 Jul 2003 16:15:51 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hEPO-0007YX-00 for manet-web-archive@ietf.org; Mon, 28 Jul 2003 16:15:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hEOc-00013u-Aw; Mon, 28 Jul 2003 16:15:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hENo-0000y0-5f for manet@optimus.ietf.org; Mon, 28 Jul 2003 16:14: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 QAA19571 for ; Mon, 28 Jul 2003 16:14:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hENk-0007Xj-00 for manet@ietf.org; Mon, 28 Jul 2003 16:14:08 -0400 Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69] helo=kanmx1.ca.alcatel.com) by ietf-mx with smtp (Exim 4.12) id 19hENk-0007Xg-00 for manet@ietf.org; Mon, 28 Jul 2003 16:14:08 -0400 Received: (qmail 29652 invoked from network); 28 Jul 2003 20:24:51 -0000 Received: from unknown (HELO camail02.ca.alcatel.com) (138.120.105.122) by kanmx1.ca.alcatel.com with SMTP; 28 Jul 2003 20:24:51 -0000 Received: from alcatel.com ([138.120.62.49]) by camail02.ca.alcatel.com (Netscape Messaging Server 4.15) with ESMTP id HIR47G00.H71 for ; Mon, 28 Jul 2003 16:14:05 -0400 Message-ID: <3F25840C.839695B@alcatel.com> Date: Mon, 28 Jul 2003 16:14:04 -0400 From: "BRIAN McBride" X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: manet@ietf.org Subject: Re: [manet] MANET real time applications References: <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> <09624AD44E416B4D8BF29194221BA492088EC9@quadra.novaengr.com> <5.1.0.14.2.20030724110434.01a6c0a8@mail.internet2.edu> <3F2007FE.817E2A5A@alcatel.com> <01bf01c352c8$e96e6990$2b081981@explore> Content-Type: multipart/mixed; boundary="------------A86DFC40A6A533CEE1BF7FF7" Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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. --------------A86DFC40A6A533CEE1BF7FF7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Harpreet, Rex, Albert Thanks, I did not mean to sound skeptical, just wanted to understand which applications people are considering QoS for. I favour ad-hoc for a communal, hostile and decentralized network of fairly simple devices, ie not mobile IP. As such only fair access to the medium is expected and nodes are assumed to be misbehaving. My skepticism is limited to enforcing any global QoS policies in an ad-hoc network using connection-like methods. I am doing a study to show how a well connected network of simple devices can achieve good QoS without reservation of bandwidth for a decentralized, dynamic and hostile network. Good QoS, even for voice and video, does not require reservation. I agree there are flows that are more important and current TCP/IP and MAC do not work. However I believe flow importance can only be defined in a host to host manner, rather than globally, in a hostile wireless network. This is different than the current networking where it is difficult for a device to tap into your fibre/wire and do bad things. The problem with TCP is that the end stations, not the intermediaries, define the fairness, therefore the network is exposed to malicious end stations. IMHO a simple distributed mechanism all intermediaries enforce is required to achieve any QoS in an ad-hoc network. This does not require any reservation mechanisms however. Brian "Harpreet S. Arora" wrote: > Hi Brian, > > I have been studying QoS for MANETs for quite some time now. I feel that QoS > is essentially important for MANETs because of the kinds of applications > that are projected from them. Most common among them are in the defence > sector and disaster relief operations (comemrcial applications are also > being developed like an ad hoc network of a group of cars). This implies > that MANETs are going to be used widely for voice communications (between > soldiers and rescue workers etc). Here, best effort delivery would not work. > Simulations show that one new flow can easily influence the existing flows > in terms of their end-to-end latency, packet delivery ratio etc. Also in > situtations like war some flows WILL be more important that others and it is > necessary that nodes are aware of such differentiation. Current TCP/IP model > and MAC 802.11 which aim at being fair to all participating nodes wont work > here. I think this is sufficient reason to consider QoS as an important > aspect of ad hoc networks. > > regards, > Harpreet > > ----- Original Message ----- > From: "BRIAN McBride" > To: "Jon Zeeff" > Cc: "Lawrence MacIntyre" ; "Michael Rauf" > ; "'Jitesh Shah'" ; > > Sent: Thursday, July 24, 2003 12:23 PM > Subject: Re: [manet] MANET real time applications > > > I have been doing QoS (ATM, diffserv etc.) for quite sometime, but yet > have > > to find a necessary application other than leased lines and simple "real > > time" vs non-real time. However it does make good research work. > > > > I am interested in understanding why QoS is important, separating research > > from standards development. Is there some work on the applications of > > ad-hoc networking someone could point me to as a starting point? > > > > I have my theories and the common ones I think, but do not know of any > that > > require QoS other than pure fairness amongst all active users. Seems to > me > > the nature of ad-hoc is all are fairly treated, to introduce bias would > > imply some central authority to manage the bias. I always considered > ad-hoc > > in the context of free-roaming, independent, individuals in a network. > > > > Qos leads to guaranteed Qos that inevitably will lead to a claim that MPLS > > and TE must then be applied to mobile ad-hoc networking ;-). > > > > The obvious app for real-time to me is voice, but it is my choice of how I > > use the bits I am allocated in the network, the network just needs to > offer > > me fair access to the bits. > > > > Thanks, > > Brian McBride > > > > Jon Zeeff wrote: > > > > > At 10:03 AM 7/24/2003 -0400, Lawrence MacIntyre wrote: > > > >I would say that the obvious real-time app for wireless is > > > >videoconferencing and the obvious research direction would be providing > > > >QOS. > > > > > > I agree that real-time video is a demanding application and thus a good > > > test case. Also that > > > QOS (in it's broadest definition - ie, including multipath routing, fair > > > queuing, non hop-count > > > metric based routing, etc) is needed. > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > -- Cheers, Brian M "It is not worth an intelligent man's time to be in the majority. By definition, there are already enough people to do that." G. H. Hardy (1877 - 1947) --------------A86DFC40A6A533CEE1BF7FF7 Content-Type: text/x-vcard; charset=us-ascii; name="brian.mcbride.vcf" Content-Description: Card for Brian McBride Content-Disposition: attachment; filename="brian.mcbride.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:McBride;Brian tel;work:613-784-3010 x-mozilla-html:FALSE org:Alcatel;Research and Innovation adr:;;;Ottawa;;;Canada version:2.1 email;internet:Brian.Mcbride@alcatel.com title:Senior Researcher fn:Brian McBride end:vcard --------------A86DFC40A6A533CEE1BF7FF7-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 29 00:54:27 2003 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 AAA00294 for ; Tue, 29 Jul 2003 00:54:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hMUm-0002bs-0u for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 00:53:56 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6T4rtCP010028 for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 00:53:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hMUl-0002bf-Tr for manet-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 00:53: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 AAA00276 for ; Tue, 29 Jul 2003 00:53:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hMUi-0002az-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 00:53:52 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hMUi-0002aw-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 00:53:52 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hMTu-0002X4-0X; Tue, 29 Jul 2003 00:53:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hMTK-0002Wg-Lu for manet@optimus.ietf.org; Tue, 29 Jul 2003 00:52: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 AAA00259 for ; Tue, 29 Jul 2003 00:52:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hMTH-0002aa-00 for manet@ietf.org; Tue, 29 Jul 2003 00:52:23 -0400 Received: from web8103.mail.in.yahoo.com ([203.199.70.30]) by ietf-mx with smtp (Exim 4.12) id 19hMTG-0002aN-00 for manet@ietf.org; Tue, 29 Jul 2003 00:52:22 -0400 Message-ID: <20030729045150.537.qmail@web8103.mail.in.yahoo.com> Received: from [202.141.69.7] by web8103.mail.in.yahoo.com via HTTP; Tue, 29 Jul 2003 05:51:50 BST Date: Tue, 29 Jul 2003 05:51:50 +0100 (BST) From: =?iso-8859-1?q?Ash=20Mohammad=20Abbas?= Subject: Re: [manet] MANET real time applications To: BRIAN McBride , manet@ietf.org In-Reply-To: <3F25840C.839695B@alcatel.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1632516709-1059454310=:265" 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: , --0-1632516709-1059454310=:265 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Dear BRIAN McBride My suggestion is, continue your good work, if you deem so. Different people will have different arguments and suggestions, and it's natural. When your work is complete, let peer researchers in your area analyze your work. I mean, after completion, you may send your work to reputed conferences and/or journals, where your work might be reviewed by the experts in the field. Either your work will be accepted or at least you will receive their comments. In the light of those you can further continue your work. As I told, in research, views are different. After my work, somebody may come forward and say " These ... were the omissions in Mr. Abbas work..., and these are our solutions regarding these omissions." What is the harm in this. I should be happy, that people did spent thier valuable time in finding my mistakes and ommissions, and are coming with better solutions than me. It should be a thing of great pride for me. So, one should continue his work and let others analyze ! it. After all, it's also one kind of view by a researcher like me. With best wishes, Abbas http://www.cse.iitd.ernet.in/~abbas BRIAN McBride <Brian.Mcbride@alcatel.com> wrote: Harpreet, Rex, Albert Thanks, I did not mean to sound skeptical, just wanted to understand which applications people are considering QoS for. I favour ad-hoc for a communal, hostile and decentralized network of fairly simple devices, ie not mobile IP. As such only fair access to the medium is expected and nodes are assumed to be misbehaving. My skepticism is limited to enforcing any global QoS policies in an ad-hoc network using connection-like methods. I am doing a study to show how a well connected network of simple devices can achieve good QoS without reservation of bandwidth for a decentralized, dynamic and hostile network. Good QoS, even for voice and video, does not require reservation. I agree there are flows that are more important and current TCP/IP and MAC do not work. However I believe flow importance can only be defined in a host to host manner, rather than globally, in a hostile wireless network. This is different than the current networking where it is difficult for a device to tap into your fibre/wire and do bad things. The problem with TCP is that the end stations, not the intermediaries, define the fairness, therefore the network is exposed to malicious end stations. IMHO a simple distributed mechanism all intermediaries enforce is required to achieve any QoS in an ad-hoc network. This does not require any reservation mechanisms however. Brian "Harpreet S. Arora" wrote: > Hi Brian, > > I have been studying QoS for MANETs for quite some time now. I feel that QoS > is essentially important for MANETs because of the kinds of applications > that are projected from them. Most common among them are in the defence > sector and disaster relief operations (comemrcial applications are also > being developed like an ad hoc network of a group of cars). This implies > that MANETs are going to be used widely for voice communications (between > soldiers and rescue workers etc). Here, best effort delivery would not work. > Simulations show that one new flow can easily influence the existing flows > in terms of their end-to-end latency, packet delivery ratio etc. Also in > situtations like war some flows WILL be more important that others and it is > necessary that nodes are aware of such differentiation. Current TCP/IP model > and MAC 802.11 which aim at being fair to all participating nodes wont work > here. I think this is sufficient reason to consider QoS as an important > aspect of ad hoc networks. > > regards, > Harpreet > > ----- Original Message ----- > From: "BRIAN McBride" > To: "Jon Zeeff" > Cc: "Lawrence MacIntyre" ; "Michael Rauf" > ; "'Jitesh Shah'" ; > > Sent: Thursday, July 24, 2003 12:23 PM > Subject: Re: [manet] MANET real time applications > > > I have been doing QoS (ATM, diffserv etc.) for quite sometime, but yet > have > > to find a necessary application other than leased lines and simple "real > > time" vs non-real time. However it does make good research work. > > > > I am interested in understanding why QoS is important, separating research > > from standards development. Is there some work on the applications of > > ad-hoc networking someone could point me to as a starting point? > > > > I have my theories and the common ones I think, but do not know of any > that > > require QoS other than pure fairness amongst all active users. Seems to > me > > the nature of ad-hoc is all are fairly treated, to introduce bias would > > imply some central authority to manage the bias. I always considered > ad-hoc > > in the context of free-roaming, independent, individuals in a network. > > > > Qos leads to guaranteed Qos that inevitably will lead to a claim that MPLS > > and TE must then be applied to mobile ad-hoc networking ;-). > > > > The obvious app for real-time to me is voice, but it is my choice of how I > > use the bits I am allocated in the network, the network just needs to > offer > > me fair access to the bits. > > > > Thanks, > > Brian McBride > > > > Jon Zeeff wrote: > > > > > At 10:03 AM 7/24/2003 -0400, Lawrence MacIntyre wrote: > > > >I would say that the obvious real-time app for wireless is > > > >videoconferencing and the obvious research direction would be providing > > > >QOS. > > > > > > I agree that real-time video is a demanding application and thus a good > > > test case. Also that > > > QOS (in it's broadest definition - ie, including multipath routing, fair > > > queuing, non hop-count > > > metric based routing, etc) is needed. > > > > > > _______________________________________________ > > > manet mailing list > > > manet@ietf.org > > > https://www1.ietf.org/mailman/listinfo/manet > > -- Cheers, Brian M "It is not worth an intelligent man's time to be in the majority. By definition, there are already enough people to do that." G. H. Hardy (1877 - 1947) begin:vcard n:McBride;Brian tel;work:613-784-3010 x-mozilla-html:FALSE org:Alcatel;Research and Innovation adr:;;;Ottawa;;;Canada version:2.1 email;internet:Brian.Mcbride@alcatel.com title:Senior Researcher fn:Brian McBride end:vcard SMS using the Yahoo! Messenger;Download latest version. --0-1632516709-1059454310=:265 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit

Dear BRIAN McBride

My suggestion is, continue your good work, if you deem so. Different people will have different arguments and suggestions, and it's natural. When your work is complete, let peer researchers in your area analyze your work. I mean, after completion, you may send your work to reputed conferences and/or journals, where your work might be reviewed by the experts in the field. Either your work will be accepted or at least you will receive their comments. In the light of those you can further continue your work. As I told, in research, views are different. After my work, somebody may come forward and say " These ...  were the omissions in Mr. Abbas work..., and these are our solutions regarding these omissions."  What is the harm in this. I should be happy, that people did spent thier valuable time in finding my mistakes and ommissions, and are coming with better solutions than me. It should be a thing of great pride for me. So, one should continue his work ! and let others analyze it.

After all, it's also one kind of view by a researcher like me.

With best wishes,

Abbas

http://www.cse.iitd.ernet.in/~abbas

 

 

  BRIAN McBride &lt;Brian.Mcbride@alcatel.com&gt; wrote:

Harpreet, Rex, Albert

Thanks, I did not mean to sound skeptical, just wanted to understand which
applications people are considering QoS for. I favour ad-hoc for a communal,
hostile and decentralized network of fairly simple devices, ie not mobile IP.
As such only fair access to the medium is expected and nodes are assumed to be
misbehaving. My skepticism is limited to enforcing any global QoS policies in
an ad-hoc network using connection-like methods.

I am doing a study to show how a well connected network of simple devices can
achieve good QoS without reservation of bandwidth for a decentralized, dynamic
and hostile network. Good QoS, even for voice and video, does not require
reservation.

I agree there are flows that are more important and current TCP/IP and MAC do
not work. However I believe flow importance can only be defined in a host to
host manner, rather than globally, in a hostile wireless network. This is
different than the current networking where it is difficult for a device to tap
into your fibre/wire and do bad things.

The problem with TCP is that the end stations, not the intermediaries, define
the fairness, therefore the network is exposed to malicious end stations. IMHO
a simple distributed mechanism all intermediaries enforce is required to achieve
any QoS in an ad-hoc network. This does not require any reservation mechanisms
however.

Brian

"Harpreet S. Arora" wrote:

> Hi Brian,
>
> I have been studying QoS for MANETs for quite some time now. I feel that QoS
> is essentially important for MANETs because of the kinds of applications
> that are projected from them. Most common among them are in the defence
> sector and disaster relief operations (comemrcial applications are also
> being developed like an ad! hoc network of a group of cars). This implies
> that MANETs are going to be used widely for voice communications (between
> soldiers and rescue workers etc). Here, best effort delivery would not work.
> Simulations show that one new flow can easily influence the existing flows
> in terms of their end-to-end latency, packet delivery ratio etc. Also in
> situtations like war some flows WILL be more important that others and it is
> necessary that nodes are aware of such differentiation. Current TCP/IP model
> and MAC 802.11 which aim at being fair to all participating nodes wont work
> here. I think this is sufficient reason to consider QoS as an important
> aspect of ad hoc networks.
>
> regards,
> Harpreet
>
> ----- Original Message -----
> From: "BRIAN McBride"
> To: "Jon Zeeff"
> Cc: "Lawrence MacIntyre" ; "Mich! ael Rauf"
> ; "'Jitesh Shah'" ;
>
> Sent: Thursday, July 24, 2003 12:23 PM
> Subject: Re: [manet] MANET real time applications
>
> > I have been doing QoS (ATM, diffserv etc.) for quite sometime, but yet
> have
> > to find a necessary application other than leased lines and simple "real
> > time" vs non-real time. However it does make good research work.
> >
> > I am interested in understanding why QoS is important, separating research
> > from standards development. Is there some work on the applications of
> > ad-hoc networking someone could point me to as a starting point?
> >
> > I have my theories and the common ones I think, but do not know of any
> that
> > require QoS other than pure fairness amongst all active users. Seems to
> me
> > the nature of ad-hoc is all ar! e fairly treated, to introduce bias would
> > imply some central authority to manage the bias. I always considered
> ad-hoc
> > in the context of free-roaming, independent, individuals in a network.
> >
> > Qos leads to guaranteed Qos that inevitably will lead to a claim that MPLS
> > and TE must then be applied to mobile ad-hoc networking ;-).
> >
> > The obvious app for real-time to me is voice, but it is my choice of how I
> > use the bits I am allocated in the network, the network just needs to
> offer
> > me fair access to the bits.
> >
> > Thanks,
> > Brian McBride
> >
> > Jon Zeeff wrote:
> >
> > > At 10:03 AM 7/24/2003 -0400, Lawrence MacIntyre wrote:
> > > >I would say that the obvious real-time app for wireless is
> > > >videoconferencing and the obvious research direction would be providing
> > > >QOS.
> > >
> > > I agree that real-time video is a demanding application and thus a good
> > > test case. Also that
> > > QOS (in it's broadest definition - ie, including multipath routing, fair
> > > queuing, non hop-count
> > > metric based routing, etc) is needed.
> > >
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> >

--
Cheers,
Brian M

"It is not worth an intelligent man's time to be in the majority. By definition,
there are already enough people to do that." G. H. Hardy (1877 - 1947)

begin:vcard
n:McBride;Brian
tel;work:613-784-3010
x-mozilla-html:FALSE
org:Alcatel;Research and Innovation
adr:;;;Ottawa;;;Canada
version:2.1
email;internet:Brian.Mcbride@alcatel.com
title:Senior Researcher
fn:Brian McBride
end:vcard

Yahoo! India Mobile SMS using the Yahoo! Messenger; Download latest version. --0-1632516709-1059454310=:265-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 29 06:01:12 2003 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 GAA17282 for ; Tue, 29 Jul 2003 06:01:12 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hRHk-0004sD-9T for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 06:00:48 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6TA0mLq018729 for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 06:00:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hRHk-0004s0-4E for manet-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 06:00: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 GAA17258 for ; Tue, 29 Jul 2003 06:00:41 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hRHg-0003rg-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 06:00:44 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hRHf-0003rc-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 06:00:43 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hRH0-0004mi-J5; Tue, 29 Jul 2003 06:00:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hRGQ-0004lu-89 for manet@optimus.ietf.org; Tue, 29 Jul 2003 05:59:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17236 for ; Tue, 29 Jul 2003 05:59:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hRGM-0003rR-00 for manet@ietf.org; Tue, 29 Jul 2003 05:59:22 -0400 Received: from smtp0.libero.it ([193.70.192.33]) by ietf-mx with esmtp (Exim 4.12) id 19hRGM-0003rO-00 for manet@ietf.org; Tue, 29 Jul 2003 05:59:22 -0400 Received: from libero.it (193.70.192.63) by smtp0.libero.it (7.0.019) id 3F1D5F7C000AA4F6 for manet@ietf.org; Tue, 29 Jul 2003 11:58:52 +0200 Date: Tue, 29 Jul 2003 11:58:52 +0200 Message-Id: Subject: [MANET] [DSR] linux implementation 802.11b MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable From: "spagoni\@inwind\.it" To: "manet" X-XaM3-API-Version: 4.1 (B6) X-type: 0 X-SenderIP: 80.180.163.73 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, my name is Carlo and i'm going to develop my thesis in manet envir= onment. I must build a real testbed in ad hoc environment with DSR routi= ng protocol, anyone know where can i find an implementation of DSR routi= ng protocol for linux with support to 802.11b? Thanks....and sorry for= my bad english Carlo _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 29 08:46:16 2003 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 IAA21205 for ; Tue, 29 Jul 2003 08:46:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hTrS-0001aJ-M5 for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 08:45:50 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6TCjoBk006085 for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 08:45:50 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hTrS-0001a4-GV for manet-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 08:45: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 IAA21165 for ; Tue, 29 Jul 2003 08:45:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hTrR-00056Y-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 08:45:49 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hTrQ-00056V-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 08:45:48 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hTqf-0001OK-FJ; Tue, 29 Jul 2003 08:45:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hTq4-0001Na-PZ for manet@optimus.ietf.org; Tue, 29 Jul 2003 08:44: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 IAA21092 for ; Tue, 29 Jul 2003 08:44:20 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hTq3-00054P-00 for manet@ietf.org; Tue, 29 Jul 2003 08:44:23 -0400 Received: from web40906.mail.yahoo.com ([66.218.78.203]) by ietf-mx with smtp (Exim 4.12) id 19hTq2-00054D-00 for manet@ietf.org; Tue, 29 Jul 2003 08:44:22 -0400 Message-ID: <20030729124352.9723.qmail@web40906.mail.yahoo.com> Received: from [158.94.71.65] by web40906.mail.yahoo.com via HTTP; Tue, 29 Jul 2003 05:43:52 PDT Date: Tue, 29 Jul 2003 05:43:52 -0700 (PDT) From: Hari Sivaramakrishnan To: manet@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1157410463-1059482632=:6873" Subject: [manet] query Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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-1157410463-1059482632=:6873 Content-Type: text/plain; charset=us-ascii hi all, with specific reference to the paper " performance compairson of three ad-hoc routing protocols" by - Hing jiang, how do i view the statistics(ie: pause time vs controld overhead) of the scenarios in the paper using qualnet developer???? i m a beginner so please guide me suitably. regards, Hari --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-1157410463-1059482632=:6873 Content-Type: text/html; charset=us-ascii

hi all,
 
   with specific reference to the paper " performance compairson of three ad-hoc routing protocols" by - Hing jiang, how do i view the statistics(ie: pause time vs controld overhead) of the scenarios in the paper using qualnet developer???? i m a beginner so please guide me suitably.
 
regards,
Hari


Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software --0-1157410463-1059482632=:6873-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 29 11:42:16 2003 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 LAA26768 for ; Tue, 29 Jul 2003 11:42:16 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hWbk-0007ix-Kb for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 11:41:51 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6TFfmeu029685 for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 11:41:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hWbk-0007ii-Fr for manet-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 11:41: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 LAA26741 for ; Tue, 29 Jul 2003 11:41:43 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hWbj-0006en-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 11:41:47 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hWbi-0006ek-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 11:41:46 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hWaz-0007YR-It; Tue, 29 Jul 2003 11:41:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hWa8-0007Xf-W5 for manet@optimus.ietf.org; Tue, 29 Jul 2003 11:40: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 LAA26652 for ; Tue, 29 Jul 2003 11:40:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hWa5-0006dr-00 for manet@ietf.org; Tue, 29 Jul 2003 11:40:05 -0400 Received: from ponypub.arc.nasa.gov ([128.102.31.43]) by ietf-mx with esmtp (Exim 4.12) id 19hWa5-0006db-00 for manet@ietf.org; Tue, 29 Jul 2003 11:40:05 -0400 Received: from nren-194.arc.nasa.gov ([128.102.196.194] verified) by ponypub.arc.nasa.gov (CommuniGate Pro SMTP 4.0.6) with ESMTP id 1522497; Tue, 29 Jul 2003 08:39:34 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Jerry Toung Reply-To: jtoung@arc.nasa.gov To: "spagoni\@inwind\.it" , "manet" Subject: Re: [MANET] [DSR] linux implementation 802.11b Date: Tue, 29 Jul 2003 08:37:55 -0700 User-Agent: KMail/1.4.3 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200307290837.56005.jtoung@arc.nasa.gov> 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 Good morning Carlo, I'm not sure there is one available. Last I heard back in March was that = there=20 was a Linux implementation from University of Queensland.=20 Jerry. On Tuesday 29 July 2003 02:58 am, spagoni@inwind.it wrote: > Hi, > > my name is Carlo and i'm going to develop my thesis in manet environmen= t. > I must build a real testbed in ad hoc environment with DSR routing > protocol, anyone know where can i find an implementation of DSR routing > protocol for linux with support to 802.11b? > > Thanks....and sorry for my bad english > > > Carlo > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet --=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 29 12:16:21 2003 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 MAA27852 for ; Tue, 29 Jul 2003 12:16:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hX8m-0001GD-CJ for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 12:15:56 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6TGFuhq004846 for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 12:15:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hX8m-0001G5-8N for manet-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 12:15:56 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27805 for ; Tue, 29 Jul 2003 12:15:50 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hX8k-0006wu-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 12:15:54 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hX8k-0006wr-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 12:15:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hX7t-00010J-UC; Tue, 29 Jul 2003 12: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 19hX7n-000100-8Q for manet@optimus.ietf.org; Tue, 29 Jul 2003 12:14:55 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27687; Tue, 29 Jul 2003 12:14:49 -0400 (EDT) Message-Id: <200307291614.MAA27687@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: manet@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Tue, 29 Jul 2003 12:14:48 -0400 Subject: [manet] I-D ACTION:draft-ietf-manet-tbrpf-10.txt Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF. Title : Topology Dissemination Based on Reverse-Path Forwarding (TBRPF) Author(s) : R. Ogier, M. Lewis, F. Templin Filename : draft-ietf-manet-tbrpf-10.txt Pages : 47 Date : 2003-7-29 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-10.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-manet-tbrpf-10.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-manet-tbrpf-10.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-7-29122710.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-manet-tbrpf-10.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-manet-tbrpf-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-29122710.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 29 12:24:03 2003 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 MAA28229 for ; Tue, 29 Jul 2003 12:24:03 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hXGE-0001qH-TO for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 12:23:39 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6TGNcx1007075 for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 12:23:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hXGD-0001px-DQ for manet-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 12:23: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 MAA28196 for ; Tue, 29 Jul 2003 12:23:31 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hXGB-000743-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 12:23:35 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hXGB-00073y-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 12:23:35 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hXFe-0001aY-7F; Tue, 29 Jul 2003 12:23:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hXEi-0001Zf-Tk for manet@optimus.ietf.org; Tue, 29 Jul 2003 12:22: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 MAA28148 for ; Tue, 29 Jul 2003 12:21:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hXEh-00072K-00 for manet@ietf.org; Tue, 29 Jul 2003 12:22:03 -0400 Received: from farley4.colorado.edu ([128.138.129.105]) by ietf-mx with esmtp (Exim 4.12) id 19hXEg-00072H-00 for manet@ietf.org; Tue, 29 Jul 2003 12:22:02 -0400 Received: (from nobody@localhost) by farley4.Colorado.EDU (8.12.9/8.12.8/ITS-6.0/webmail) id h6TGM1qo002557; Tue, 29 Jul 2003 10:22:01 -0600 (MDT) From: Shweta.Bhandare@colorado.edu Received: from eternal.vericept.com (eternal.vericept.com [65.100.174.33]) by webmail.colorado.edu (IMP) with HTTP for ; Tue, 29 Jul 2003 10:22:01 -0600 Message-ID: <1059495721.3f269f299c65c@webmail.colorado.edu> Date: Tue, 29 Jul 2003 10:22:01 -0600 To: "spagoni@inwind.it" Cc: manet Subject: Re: [MANET] [DSR] linux implementation 802.11b References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2-cvs 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 Carlo, We at University of COlorado at Boulder have a Linux implementation of DSR (userlevel) and the source code can be found at http://pecolab.colorado.edu Thanks, Shweta. Quoting "spagoni@inwind.it" : > Hi, > > my name is Carlo and i'm going to develop my thesis in manet environment. > I must build a real testbed in ad hoc environment with DSR routing protocol, > anyone know where can i find an implementation of DSR routing protocol for > linux with support to 802.11b? > > Thanks....and sorry for my bad english > > > Carlo > > > _______________________________________________ > 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 Tue Jul 29 16:45:24 2003 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 QAA08539 for ; Tue, 29 Jul 2003 16:45:23 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hbL8-0004aN-Nt for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 16:44:58 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6TKiwH9017621 for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 16:44:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hbL8-0004a8-Ku for manet-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 16:44:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08496 for ; Tue, 29 Jul 2003 16:44:51 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hbL5-0001eg-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 16:44:55 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hbL4-0001ed-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 16:44:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hbKD-0004Sv-OG; Tue, 29 Jul 2003 16:44:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hbJq-0004Ry-RT for manet@optimus.ietf.org; Tue, 29 Jul 2003 16:43: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 QAA08467 for ; Tue, 29 Jul 2003 16:43:33 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hbJm-0001dw-00 for manet@ietf.org; Tue, 29 Jul 2003 16:43:34 -0400 Received: from smtp2.libero.it ([193.70.192.52]) by ietf-mx with esmtp (Exim 4.12) id 19hbJl-0001de-00 for manet@ietf.org; Tue, 29 Jul 2003 16:43:33 -0400 Received: from libero.it (193.70.192.48) by smtp2.libero.it (7.0.012) id 3E9BEBBA00A420B7 for manet@ietf.org; Tue, 29 Jul 2003 22:43:06 +0200 Date: Tue, 29 Jul 2003 22:43:02 +0200 Message-Id: MIME-Version: 1.0 X-Sensitivity: 3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable From: "spagoni\@inwind\.it" To: "manet manet" X-XaM3-API-Version: 4.1 (B6) X-type: 0 X-SenderIP: 80.180.163.73 Content-Transfer-Encoding: quoted-printable Subject: [manet] (no subject) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable ...thanks all.... >Hello Carlo, >Would you be interested in AODV inst= ead? >Regards, >Charlie P. ..thank for answering me but i'm not in= teresting because someone else is already developing this protocol in my = team. >Hi Carlo, >Here's one you can use.. >http://pecolab.col= orado.edu/DSR.html >Regards >Sheetal ..thanks man...but i alread= y found this implementation and i had problems to recompile kernel in my = debian woody with last kernel version any suggestion for me? >Hi = Carlo, >We at University of COlorado at Boulder have a Linux implementat= ion of DSR >(userlevel) and the source code can be found at http://peco= lab.colorado.edu >Thanks, >Shweta. thank you ... see above the r= eply to Sheetal >Good morning Carlo, >I'm not sure there is one ava= ilable. Last I heard back in March was that there >was a Linux implemen= tation from University of Queensland. >Jerry. thank you Jerry....i s= aw that implementation but it isn't good because maybe only for 802.11 an= d i must do my with 802.11b >University of Colorado did a DSR vari= ant recently. >So ... do a grep on the listserv archive? The NRL websit= e usually has >an current archive >Pete Sholander thank you ... see = above the reply to Sheetal _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Tue Jul 29 17:54:10 2003 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 RAA11128 for ; Tue, 29 Jul 2003 17:54:10 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hcPi-0008Mv-QB for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 17:53:46 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6TLrkk2032163 for manet-archive@odin.ietf.org; Tue, 29 Jul 2003 17:53:46 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hcPi-0008Mg-25 for manet-web-archive@optimus.ietf.org; Tue, 29 Jul 2003 17:53: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 RAA11087 for ; Tue, 29 Jul 2003 17:53:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hcPf-0002F3-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 17:53:43 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hcPe-0002Ez-00 for manet-web-archive@ietf.org; Tue, 29 Jul 2003 17:53:42 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hcOz-0008Cp-T9; Tue, 29 Jul 2003 17:53:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hcOq-0008CT-4u for manet@optimus.ietf.org; Tue, 29 Jul 2003 17:52: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 RAA11043 for ; Tue, 29 Jul 2003 17:52:45 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hcOn-0002E3-00 for manet@ietf.org; Tue, 29 Jul 2003 17:52:49 -0400 Received: from hellmouth4.gatech.edu ([130.207.165.164] ident=postfix) by ietf-mx with esmtp (Exim 4.12) id 19hcOm-0002Dx-00 for manet@ietf.org; Tue, 29 Jul 2003 17:52:48 -0400 Received: from hellmouth4.gatech.edu (localhost [127.0.0.1]) by hellmouth4.gatech.edu (Postfix) with SMTP id 94B54A56E for ; Tue, 29 Jul 2003 17:52:43 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: from acmex.gatech.edu (acmex.prism.gatech.edu [130.207.171.14]) by hellmouth4.gatech.edu (Postfix) with ESMTP id 7F1A4A549 for ; Tue, 29 Jul 2003 17:52:43 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Received: by acmex.gatech.edu (Postfix, from userid 21503) id 66F211DFA8; Tue, 29 Jul 2003 17:52:43 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by acmex.gatech.edu (Postfix) with ESMTP id 5E9D41F176 for ; Tue, 29 Jul 2003 17:52:43 -0400 (EDT) (envelope-from gte393q@mail.gatech.edu) Date: Tue, 29 Jul 2003 17:52:43 -0400 (EDT) From: Young-Jun Lee X-X-Sender: To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [manet] Request table and ID FIFO cache of 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: , Hello all, I'm trying to implement DSR protocol in a simulation tool. While reading the DSR draft (draft-ietf-manet-dsr-08.txt), I found the request table structure a little bit confusing. In Page 28 of the draft, it says route request table records information about route request, i.e. using ID fifo cache. Does this mean that this ID fifo cache is a field of request table entry? Or, is the ID fifo cache a separate data structure? I checked the DSR model in ns-2 and the DSR linux implementation by univ. Colorado, but both do not have any data structure like ID fifo cache. I'd appreciate it if anybody gives me some hints on this. Thanks. Young _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 30 05:29:36 2003 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 FAA24967 for ; Wed, 30 Jul 2003 05:29:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hnGV-00027f-Ih for manet-archive@odin.ietf.org; Wed, 30 Jul 2003 05:29:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6U9Sxa4008155 for manet-archive@odin.ietf.org; Wed, 30 Jul 2003 05:28:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hnGV-00027S-CU for manet-web-archive@optimus.ietf.org; Wed, 30 Jul 2003 05:28: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 FAA24923 for ; Wed, 30 Jul 2003 05:28:53 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hnGR-0006IC-00 for manet-web-archive@ietf.org; Wed, 30 Jul 2003 05:28:55 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19hnGQ-0006I9-00 for manet-web-archive@ietf.org; Wed, 30 Jul 2003 05:28:54 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19hnFZ-0001vh-PK; Wed, 30 Jul 2003 05: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 19hnFE-0001vR-UT for manet@optimus.ietf.org; Wed, 30 Jul 2003 05:27: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 FAA24889 for ; Wed, 30 Jul 2003 05:27:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19hnFA-0006HY-00 for manet@ietf.org; Wed, 30 Jul 2003 05:27:36 -0400 Received: from inet-tsb.toshiba.co.jp ([202.33.96.40]) by ietf-mx with esmtp (Exim 4.12) id 19hnF9-0006HU-00 for manet@ietf.org; Wed, 30 Jul 2003 05:27:35 -0400 Received: from tsb-wall.toshiba.co.jp ([133.199.160.134]) by inet-tsb.toshiba.co.jp with ESMTP id h6U9RHVj024030; Wed, 30 Jul 2003 18:27:17 +0900 (JST) Received: (from root@localhost) by tsb-wall.toshiba.co.jp id h6U9RHXd029465; Wed, 30 Jul 2003 18:27:17 +0900 (JST) Received: from tis2 [133.199.160.66] by tsb-wall.toshiba.co.jp with SMTP id UAA29458 ; Wed, 30 Jul 2003 18:27:17 +0900 Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp id SAA06312; Wed, 30 Jul 2003 18:27:16 +0900 (JST) Received: from isl.rdc.toshiba.co.jp by toshiba.co.jp id SAA07520; Wed, 30 Jul 2003 18:27:15 +0900 (JST) Received: from localhost (inoue@flowerpark [133.196.16.25]) by isl.rdc.toshiba.co.jp (8.11.7/8.11.6/1.4) with ESMTP id h6U9REb29524; Wed, 30 Jul 2003 18:27:14 +0900 (JST) To: nemo@nal.motlabs.com, manet@ietf.org, mobile-ip@sunroof.eng.sun.com, pana@research.telcordia.com Cc: inoue@isl.rdc.toshiba.co.jp In-Reply-To: Your message of "Mon, 07 Jul 2003 20:15:21 +0900" <20030707201521A.inoue@isl.rdc.toshiba.co.jp> References: <20030707201521A.inoue@isl.rdc.toshiba.co.jp> X-Mailer: Mew version 1.93 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20030730182713V.inoue@isl.rdc.toshiba.co.jp> Date: Wed, 30 Jul 2003 18:27:13 +0900 From: Atsushi Inoue X-Dispatcher: imput version 980905(IM100) Lines: 90 Content-Transfer-Encoding: 7bit Subject: [manet] CFP:: First International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2004) Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit The deadline of submission (August 1st) is approaching. -- inoue (Apologies if you receive multiple copies) CALL FOR PAPERS =============== First International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2004) January 8 and 9, 2004 NTT DoCoMo R&D Center, Yokosuka Rsearch Park, Yokosuka, JAPAN http://www.ipsj.or.jp/sig/mbl/icmu2004/ Deadline for submissions: August 1 2003 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Co-sponsored by IPSJ SIG-MBL (Informaiton Processing Society of Japan, Special Interest Group of Mobile Computing and Ubiquitous Networking) and IPSJ SG-BCC (Study Group of Broadcast Communicaiton and Computing) Scope: ~~~~~~ Mobile computing aims at ubiquitous user access to computer application. To make it possible, networking technology which enables Internet access anytime and everywhere, i.e. ubiquitous networking is necessary. It is obvious that with the accelerating trends towards mobile networks, ad-hoc networks, and wireless networks, mobile computing and ubiquitous networking will play an important role in future network. This conference is aimed at providing researchers and practitioners in this hot research area a forum for discussion and collaboration. Authors are invited to submit papers addressing, but not limited to, the following topics: - Applications and services for mobile computing - Network architectures, protocols, or service models for ubiquitous networking - Network management for ubiquitous networking - Data management for mobile computing - Security in mobile computing and ubiquitous networking - Wireless and mobile communications - Nomadic computing - Ad-hoc networks - Mobile Internetworking - Performance evaluation for mobile computing and ubiquitous networking systems - Broadcast communication Submission Instructions: ~~~~~~~~~~~~~~~~~~~~~~~~ Papers are solicited as full papers of no more than 6 pages, each of which will be subject to a full review process. Submission should already follow the author guidelines as specified in the web site below. An electronic, PDF-based submission of papers is mandatory. Please check Submission Guideline (http://www.ipsj.or.jp/sig/mbl/icmu2004/guide.html) for further submission instructions. Important Dates: ~~~~~~~~~~~~~~~~ - Deadline for submissions August 1, 2003 - Notification of acceptance October 1, 2003 - Camera ready due November 1, 2003 - Conference January 8-9, 2004 Location and Date: ~~~~~~~~~~~~~~~~~~ The location of the NTT DoCoMo R&D Center is in the heart of Yokosuka Research Park(YRP) where a lot of wireless communication related research institutes are established. YRP is really the heart of wireless communications research in Japan. Japanese old city Kamakura, a famous historic city, is 30 minutes by train. Beginning of the year is one of the best seasons for visiting Japan. You can also get PDF version of Call for Papers from http://www.ipsj.or.jp/sig/mbl/icmu2004/cfp-icmu2004.pdf Atsushi Inoue # Phone: +81-44-549-2065 Communication Platform Lab. # Fax: +81-44-520-1806 TOSHIBA R&D Center # inoue@isl.rdc.toshiba.co.jp _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 30 21:13:18 2003 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 VAA25729 for ; Wed, 30 Jul 2003 21:13:18 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i1zx-0005Vz-I4 for manet-archive@odin.ietf.org; Wed, 30 Jul 2003 21:12:53 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6V1CrjH021195 for manet-archive@odin.ietf.org; Wed, 30 Jul 2003 21:12:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i1zx-0005Vm-FF for manet-web-archive@optimus.ietf.org; Wed, 30 Jul 2003 21:12: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 VAA25702 for ; Wed, 30 Jul 2003 21:12:48 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19i1zu-00064u-00 for manet-web-archive@ietf.org; Wed, 30 Jul 2003 21:12:50 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19i1zu-00064q-00 for manet-web-archive@ietf.org; Wed, 30 Jul 2003 21:12:50 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i1z8-0005PZ-4r; Wed, 30 Jul 2003 21:12:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i1yW-0005NE-4m for manet@optimus.ietf.org; Wed, 30 Jul 2003 21: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 VAA25653 for ; Wed, 30 Jul 2003 21:11:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19i1yT-00064C-00 for manet@ietf.org; Wed, 30 Jul 2003 21:11:21 -0400 Received: from [203.254.224.25] (helo=mailout2.samsung.com) by ietf-mx with esmtp (Exim 4.12) id 19i1yS-00063m-00 for manet@ietf.org; Wed, 30 Jul 2003 21:11:20 -0400 Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) id <0HIV006017A05R@mailout2.samsung.com> for manet@ietf.org; Thu, 31 Jul 2003 10:10:48 +0900 (KST) Received: from ep_mmp1 (localhost [127.0.0.1]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) with ESMTP id <0HIV003H379ZC5@mailout2.samsung.com> for manet@ietf.org; Thu, 31 Jul 2003 10:10:48 +0900 (KST) Received: from Shubhranshu ([75.2.47.220]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTPA id <0HIV009KH79ZFS@mmp1.samsung.com> for manet@ietf.org; Thu, 31 Jul 2003 10:10:47 +0900 (KST) Date: Thu, 31 Jul 2003 10:10:51 -0800 From: Shubhranshu Subject: Re: [manet] I-D ACTION:draft-ietf-manet-tbrpf-10.txt To: manet@ietf.org Reply-to: Shubhranshu Message-id: <00fc01c3578f$13d14ed0$dc2f024b@Shubhranshu> Organization: Samsung MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Mailer: Microsoft Outlook Express 6.00.2800.1106 Content-type: text/plain; charset=x-user-defined Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <200307291614.MAA27687@ietf.org> 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, In section 5.2 , second paragraph -- " The part of T that a node reports to neighbors is called the "reported subtree" and is denoted RT... " Which part of T ? Thanks Shubhranshu ----- Original Message ----- From: To: Cc: Sent: Tuesday, July 29, 2003 8:14 AM Subject: [manet] I-D ACTION:draft-ietf-manet-tbrpf-10.txt > 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-10.txt > Pages : 47 > Date : 2003-7-29 > > 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-10.txt > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Wed Jul 30 23:19:50 2003 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 XAA27825 for ; Wed, 30 Jul 2003 23:19: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 19i3yO-0000mj-9f for manet-archive@odin.ietf.org; Wed, 30 Jul 2003 23:19:24 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6V3JOoB003011 for manet-archive@odin.ietf.org; Wed, 30 Jul 2003 23:19:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i3yN-0000mU-QH for manet-web-archive@optimus.ietf.org; Wed, 30 Jul 2003 23:19: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 XAA27813 for ; Wed, 30 Jul 2003 23:19:18 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19i3yL-0006e4-00 for manet-web-archive@ietf.org; Wed, 30 Jul 2003 23:19:22 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19i3yL-0006e1-00 for manet-web-archive@ietf.org; Wed, 30 Jul 2003 23:19:21 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i3x4-0000WV-Fx; Wed, 30 Jul 2003 23: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 19i3wO-0000Vy-BH for manet@optimus.ietf.org; Wed, 30 Jul 2003 23:17: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 XAA27744 for ; Wed, 30 Jul 2003 23:17:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19i3wM-0006bu-00 for manet@ietf.org; Wed, 30 Jul 2003 23:17:18 -0400 Received: from den.erg.sri.com ([128.18.100.23]) by ietf-mx with esmtp (Exim 4.12) id 19i3wL-0006bl-00 for manet@ietf.org; Wed, 30 Jul 2003 23:17:17 -0400 Received: from den.erg.sri.com (localhost [127.0.0.1]) by den.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id UAA06205; Wed, 30 Jul 2003 20:16:44 -0700 (PDT) Message-Id: <200307310316.UAA06205@den.erg.sri.com> To: Shubhranshu cc: manet@ietf.org Reply-To: ogier@erg.sri.com From: ogier@erg.sri.com Subject: Re: [manet] I-D ACTION:draft-ietf-manet-tbrpf-10.txt In-reply-to: Your message of "Thu, 31 Jul 2003 10:10:51 -0800." <00fc01c3578f$13d14ed0$dc2f024b@Shubhranshu> Date: Wed, 30 Jul 2003 20:16:44 -0700 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , > Hi, > > In section 5.2 , second paragraph -- " The part > of T that a node reports to neighbors is called the > "reported subtree" and is denoted RT... " > > Which part of T ? > > Thanks > Shubhranshu Hi Shubhranshu, The answer can be found two paragraphs later (in Section 5.2 - Overview of the Routing Module) where RT and RN are described, and in more detail in Section 8.4.4 - Updating the Reported Node Set. Regards, Richard _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 31 01:15:06 2003 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 BAA29877 for ; Thu, 31 Jul 2003 01:15:06 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i5lv-0003u1-8l for manet-archive@odin.ietf.org; Thu, 31 Jul 2003 01:14:39 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6V5Ed19014995 for manet-archive@odin.ietf.org; Thu, 31 Jul 2003 01:14:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i5lv-0003tm-3V for manet-web-archive@optimus.ietf.org; Thu, 31 Jul 2003 01:14: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 BAA29861 for ; Thu, 31 Jul 2003 01:14:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19i5ls-0007Ig-00 for manet-web-archive@ietf.org; Thu, 31 Jul 2003 01:14:36 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19i5lr-0007Id-00 for manet-web-archive@ietf.org; Thu, 31 Jul 2003 01:14:35 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i5lJ-0003kB-I6; Thu, 31 Jul 2003 01:14:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i5kY-0003je-Pq for manet@optimus.ietf.org; Thu, 31 Jul 2003 01:13: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 BAA29833 for ; Thu, 31 Jul 2003 01:13:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19i5kV-0007Hq-00 for manet@ietf.org; Thu, 31 Jul 2003 01:13:11 -0400 Received: from [203.254.224.25] (helo=mailout2.samsung.com) by ietf-mx with esmtp (Exim 4.12) id 19i5kU-0007Hd-00 for manet@ietf.org; Thu, 31 Jul 2003 01:13:11 -0400 Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) id <0HIV00F01IH02T@mailout2.samsung.com> for manet@ietf.org; Thu, 31 Jul 2003 14:12:36 +0900 (KST) Received: from ep_mmp1 (localhost [127.0.0.1]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.05 (built Nov 6 2002)) with ESMTP id <0HIV00392IGZCM@mailout2.samsung.com> for manet@ietf.org; Thu, 31 Jul 2003 14:12:36 +0900 (KST) Received: from Shubhranshu ([75.2.47.220]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTPA id <0HIV009I5IGZBQ@mmp1.samsung.com> for manet@ietf.org; Thu, 31 Jul 2003 14:12:35 +0900 (KST) Date: Thu, 31 Jul 2003 14:12:38 -0800 From: Shubhranshu Subject: Re: [manet] I-D ACTION:draft-ietf-manet-tbrpf-10.txt To: ogier@erg.sri.com Cc: manet@ietf.org Reply-to: Shubhranshu Message-id: <016501c357b0$da9c1ab0$dc2f024b@Shubhranshu> Organization: Samsung MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Mailer: Microsoft Outlook Express 6.00.2800.1106 Content-type: text/plain; charset=x-user-defined Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <200307310316.UAA06205@den.erg.sri.com> Content-Transfer-Encoding: 7BIT Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7BIT Content-Transfer-Encoding: 7BIT Hi Richard, Thanks One more quick question : In section 8.4.4, third paragraph --- " .... shortest paths, up to 2 hops, from each neighbor to each other neighbor, using only neighbors (or node i itself) as an intermediate node,...." I feel that it should be ".....to each other neighbor, using only *node i itself* as an intermediate node ..." If not then I am afraid i could not exactly understand how node i determines that one of its neighbors may select i to be its next hop on its shortest path to j. Regards Shubhranshu ----- Original Message ----- From: To: "Shubhranshu" Cc: Sent: Wednesday, July 30, 2003 7:16 PM Subject: Re: [manet] I-D ACTION:draft-ietf-manet-tbrpf-10.txt > > Hi, > > > > In section 5.2 , second paragraph -- " The part > > of T that a node reports to neighbors is called the > > "reported subtree" and is denoted RT... " > > > > Which part of T ? > > > > Thanks > > Shubhranshu > > Hi Shubhranshu, > > The answer can be found two paragraphs later (in Section 5.2 - Overview > of the Routing Module) where RT and RN are described, and in more detail > in Section 8.4.4 - Updating the Reported Node Set. > > Regards, > Richard > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 31 06:24:07 2003 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 GAA19311 for ; Thu, 31 Jul 2003 06:24:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iAb0-0000z6-CK for manet-archive@odin.ietf.org; Thu, 31 Jul 2003 06:23:43 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6VANgTE003778 for manet-archive@odin.ietf.org; Thu, 31 Jul 2003 06:23:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iAb0-0000yr-87 for manet-web-archive@optimus.ietf.org; Thu, 31 Jul 2003 06:23: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 GAA19286 for ; Thu, 31 Jul 2003 06:23:36 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19iAaw-0001pW-00 for manet-web-archive@ietf.org; Thu, 31 Jul 2003 06:23:38 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19iAav-0001pT-00 for manet-web-archive@ietf.org; Thu, 31 Jul 2003 06:23:37 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iAaM-0000rj-2t; Thu, 31 Jul 2003 06:23:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iAZb-0000qd-0m for manet@optimus.ietf.org; Thu, 31 Jul 2003 06:22: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 GAA19229 for ; Thu, 31 Jul 2003 06:22:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19iAZX-0001nV-00 for manet@ietf.org; Thu, 31 Jul 2003 06:22:11 -0400 Received: from mephisto.inf.tu-dresden.de ([141.76.40.3]) by ietf-mx with esmtp (Exim 4.12) id 19iAZW-0001nR-00 for manet@ietf.org; Thu, 31 Jul 2003 06:22:10 -0400 Received: from acer.rn.inf.tu-dresden.de (acer.inf.tu-dresden.de [141.76.44.88]) by mephisto.inf.tu-dresden.de (8.8.7/8.8.7) with ESMTP id MAA25218; Thu, 31 Jul 2003 12:22:08 +0200 (MET DST) Message-Id: <5.1.0.14.0.20030731121716.032eddc8@harmless.inf.tu-dresden.de> X-Sender: gikaru@harmless.inf.tu-dresden.de X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 31 Jul 2003 12:22:20 +0200 To: ns-users@ISI.EDU From: gikaru Cc: manet@ietf.org Mime-Version: 1.0 Content-Type: multipart/mixed; x-avg-checked=avg-ok-6AFA4F16; boundary="=======4BE622FA=======" Subject: [manet] Implementations of LAR and GPSR Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , --=======4BE622FA======= Content-Type: text/plain; x-avg-checked=avg-ok-6AFA4F16; charset=us-ascii; format=flowed Content-Transfer-Encoding: 8bit Hello, Has anyone implemented LAR and/or GPSR in ns-2b9 or closer version. I need to do some comparison of their performances on routing overheads. If anyone has done the implementation, i wish to have a look. Thanks Gikaru --=======4BE622FA======= Content-Type: text/plain; charset=us-ascii; x-avg=cert; x-avg-checked=avg-ok-6AFA4F16 Content-Disposition: inline --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.504 / Virus Database: 302 - Release Date: 24.07.2003 --=======4BE622FA=======-- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 31 16:05:11 2003 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 QAA12310 for ; Thu, 31 Jul 2003 16:05:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iJfI-00034t-Aw for manet-archive@odin.ietf.org; Thu, 31 Jul 2003 16:04:45 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6VK4ipu011830 for manet-archive@odin.ietf.org; Thu, 31 Jul 2003 16:04:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iJfI-00034j-72 for manet-web-archive@optimus.ietf.org; Thu, 31 Jul 2003 16:04: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 QAA12268 for ; Thu, 31 Jul 2003 16:04:40 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19iJfG-0007EY-00 for manet-web-archive@ietf.org; Thu, 31 Jul 2003 16:04:42 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19iJfF-0007EV-00 for manet-web-archive@ietf.org; Thu, 31 Jul 2003 16:04:41 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iJec-0002xF-9G; Thu, 31 Jul 2003 16:04:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iJeT-0002wp-8m for manet@optimus.ietf.org; Thu, 31 Jul 2003 16:03: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 QAA12233 for ; Thu, 31 Jul 2003 16:03:46 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19iJeP-0007Dp-00 for manet@ietf.org; Thu, 31 Jul 2003 16:03:49 -0400 Received: from pit.erg.sri.com ([128.18.100.28]) by ietf-mx with esmtp (Exim 4.12) id 19iJeO-0007DX-00 for manet@ietf.org; Thu, 31 Jul 2003 16:03:48 -0400 Received: from pit.erg.sri.com (localhost [127.0.0.1]) by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id NAA11976; Thu, 31 Jul 2003 13:03:14 -0700 (PDT) Message-Id: <200307312003.NAA11976@pit.erg.sri.com> To: Shubhranshu cc: ogier@erg.sri.com, manet@ietf.org Reply-To: ogier@erg.sri.com From: ogier@erg.sri.com Subject: Re: [manet] I-D ACTION:draft-ietf-manet-tbrpf-10.txt In-reply-to: Your message of "Thu, 31 Jul 2003 14:12:38 -0800." <016501c357b0$da9c1ab0$dc2f024b@Shubhranshu> Date: Thu, 31 Jul 2003 13:03:13 -0700 Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Mobile Ad-hoc Networks List-Post: List-Help: List-Subscribe: , Hi Shubhranshu, > Hi Richard, > Thanks > One more quick question : > In section 8.4.4, third paragraph --- " .... node i computes shortest > paths, up to 2 hops, from each neighbor to each other > neighbor, using only neighbors (or node i itself) as an intermediate node,... ." > > I feel that it should be ".....to each other neighbor, using only > *node i itself* as an intermediate node ..." > If not then I am afraid i could not exactly understand how > node i determines that one of its neighbors > may select i to be its next hop on its shortest path to j. For reference, here is the paragraph in the draft: "A node first determines which of its neighbors belong to RN. Node i includes a neighbor j in RN if and only if node i determines that one of its neighbors may select i to be its next hop on its shortest path to j. To make this determination, node i computes the shortest paths, up to 2 hops, from each neighbor to each other neighbor, using only neighbors (or node i itself) as an intermediate node, and using relay priority and router ID to break ties." Maybe this rewrite will make it clearer: To determine which neighbors are in RN, node i computes shortest paths, up to 2 hops, from each neighbor k to each other neighbor j, allowing only neighbors of node i (or node i itself) to be the intermediate node, and using relay priority and router ID to break ties. (If the intermediate node happens to be node i, then node j is included in RN.) The procedure Update_RN() defined in the same section makes this precise. Note also that node i knows the local links reported by each neighbor, i.e., it knows the full topology for its 2-hop neighborhood, which allows it to compute the 2-hop shortest paths mentioned above. The following paragraph from the draft helps to understand the analogy between neighbors in RN and MPR selectors: "We note that neighbors in RN are analogous to multipoint relay (MPR) selectors [9]. Thus, if node i selects neighbor j to be in RN, then node i effectively selects itself to be an MPR of node j. This is quite different from [9], in which a node does not select itself to be an MPR, but selects a subset of its neighbors to be MPRs." Regards, Richard > > Regards > Shubhranshu > > > > > ----- Original Message ----- > From: > To: "Shubhranshu" > Cc: > Sent: Wednesday, July 30, 2003 7:16 PM > Subject: Re: [manet] I-D ACTION:draft-ietf-manet-tbrpf-10.txt > > > > > Hi, > > > > > > In section 5.2 , second paragraph -- " The part > > > of T that a node reports to neighbors is called the > > > "reported subtree" and is denoted RT... " > > > > > > Which part of T ? > > > > > > Thanks > > > Shubhranshu > > > > Hi Shubhranshu, > > > > The answer can be found two paragraphs later (in Section 5.2 - Overview > > of the Routing Module) where RT and RN are described, and in more detail > > in Section 8.4.4 - Updating the Reported Node Set. > > > > Regards, > > Richard > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From exim@www1.ietf.org Thu Jul 31 18:56:08 2003 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 SAA18016 for ; Thu, 31 Jul 2003 18:56:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iMKk-00012r-4M for manet-archive@odin.ietf.org; Thu, 31 Jul 2003 18:55:44 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6VMtg82004011 for manet-archive@odin.ietf.org; Thu, 31 Jul 2003 18:55:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iMKj-00012c-Ud for manet-web-archive@optimus.ietf.org; Thu, 31 Jul 2003 18:55: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 SAA17962 for ; Thu, 31 Jul 2003 18:55:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19iMKg-0000XP-00 for manet-web-archive@ietf.org; Thu, 31 Jul 2003 18:55:38 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19iMKg-0000XM-00 for manet-web-archive@ietf.org; Thu, 31 Jul 2003 18:55:38 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iMK5-0000vi-Mt; Thu, 31 Jul 2003 18:55:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19iMJD-0000uw-DE for manet@optimus.ietf.org; Thu, 31 Jul 2003 18: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 SAA17936 for ; Thu, 31 Jul 2003 18:54:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19iMJA-0000WS-00 for manet@ietf.org; Thu, 31 Jul 2003 18:54:04 -0400 Received: from strix.ciens.ucv.ve ([150.185.72.253]) by ietf-mx with esmtp (Exim 4.12) id 19iMJ9-0000WL-00 for manet@ietf.org; Thu, 31 Jul 2003 18:54:03 -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 h6VNTdGM002145; Thu, 31 Jul 2003 19:29:39 -0400 Received: from localhost (dcobos@localhost) by strix.ciens.ucv.ve (8.12.5/8.12.5/Submit) with ESMTP id h6VNTcFE002141; Thu, 31 Jul 2003 19:29:38 -0400 Date: Thu, 31 Jul 2003 19:29:38 -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 validation test of AODV-UU!! Sender: manet-admin@ietf.org Errors-To: manet-admin@ietf.org X-BeenThere: manet@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 all I've decided to use the AODV implementation developed in the AODV-UU project. I am really interested in getting to know if there exist any validation tests on the AODV-UU implementations for NS-2. If that is the case, are they available? Thank you very much for your feedbacks. -- ***************************************************** * * * 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