From manet-bounces@ietf.org Mon Nov 1 04:48:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09330 for ; Mon, 1 Nov 2004 04:48:18 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COZ2L-0002nX-Qy for manet-web-archive@ietf.org; Mon, 01 Nov 2004 05:03:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COYcg-0002lD-FX; Mon, 01 Nov 2004 04:37:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COYVa-0001wh-Id for manet@megatron.ietf.org; Mon, 01 Nov 2004 04:29:50 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08302 for ; Mon, 1 Nov 2004 04:29:49 -0500 (EST) Received: from dns1.tilab.com ([163.162.42.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COYkS-0002RV-H3 for manet@ietf.org; Mon, 01 Nov 2004 04:45:13 -0500 Received: from iowa2k01a.cselt.it ([163.162.242.201]) by dns1.cselt.it (PMDF V6.0-025 #38895) with ESMTP id <0I6H0000XU9KST@dns1.cselt.it> for manet@ietf.org; Mon, 01 Nov 2004 10:27:20 +0100 (MET) Received: from EXC01A.cselt.it ([163.162.4.198]) by iowa2k01a.cselt.it with Microsoft SMTPSVC(6.0.3790.211); Mon, 01 Nov 2004 10:31:16 +0100 Date: Mon, 01 Nov 2004 10:29:15 +0100 From: Ruffino Simone To: manet@ietf.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Importance: normal Priority: normal Thread-Topic: New draft on connectivity scenarios and autoconfiguration issues thread-index: AcS/9UDy/KQyh2MkQbO6Hu2F0vMh6w== Content-Class: urn:content-classes:message X-OriginalArrivalTime: 01 Nov 2004 09:31:16.0140 (UTC) FILETIME=[891BA6C0:01C4BFF5] X-Spam-Score: 0.0 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Content-Transfer-Encoding: quoted-printable Subject: [manet] New draft on connectivity scenarios and autoconfiguration issues X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Content-Transfer-Encoding: quoted-printable Hi to all, a new draft was submitted as individual submission, titled "Autoconfiguration in a MANET: connectivity scenarios and technical issues".=20 Goal of the draft is to describe the scenarios, in which a MANET can be connected to an external network (by means of either wired of wireless links) and to list some of the technical issues, which are related to autoconfiguration and global connectivity, that arise in such scenarios. Comments welcome and appreciated ! Thanks in advance, Simone Ruffino > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title: Autoconfiguration in a MANET: connectivity scenarios and=20 > technical issues > Author(s): S. Ruffino, et al. > Filename: draft-ruffino-manet-autoconf-scenarios-00.txt > Pages: 26 > Date: 2004-10-19 > > MANET interconnection with external networks enables a number of > usage scenarios, but generates also a number of technical issues, > mainly related with node autoconfiguration and global connectivity. > This Internet Draft aims at characterizing global connectivity > scenarios and listing technical issues related to IP address > autoconfiguration which are implied by such scenarios and should be > addressed by a generic solution. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ruffino-manet-autoconf-scenari os-00.txt > > Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia = S.p.A. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 send an e_mail to=20 MailAdmin@tilab.com. Thank you =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From mailman-bounces@ietf.org Mon Nov 1 06:23:11 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18196 for ; Mon, 1 Nov 2004 06:23:11 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COaWD-0004ir-0x for manet-web-archive@ietf.org; Mon, 01 Nov 2004 06:38:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COZNs-0007E7-41 for manet-web-archive@ietf.org; Mon, 01 Nov 2004 05:25:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: manet-web-archive@ietf.org X-No-Archive: yes Message-ID: Date: Mon, 01 Nov 2004 05:09:05 -0500 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@ietf.org. Thanks! Passwords for manet-web-archive@ietf.org: List Password // URL ---- -------- manet@ietf.org pKoU https://www1.ietf.org/mailman/options/manet/manet-web-archive%40ietf.org From manet-bounces@ietf.org Mon Nov 1 08:21:33 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29693 for ; Mon, 1 Nov 2004 08:21:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COcMl-0006xY-VE for manet-web-archive@ietf.org; Mon, 01 Nov 2004 08:37:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COZe2-0003wO-OV; Mon, 01 Nov 2004 05:42:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COZ2U-0006IA-Bp for manet@megatron.ietf.org; Mon, 01 Nov 2004 05:03:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10541 for ; Mon, 1 Nov 2004 05:03:49 -0500 (EST) Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COZHM-0003B7-Jj for manet@ietf.org; Mon, 01 Nov 2004 05:19:13 -0500 Received: from [192.168.2.19] (lina23.tts.lth.se [130.235.18.83]) by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id LAA27586; Mon, 1 Nov 2004 11:02:50 +0100 (MET) Message-ID: <418617C5.5060909@telecom.lth.se> Date: Mon, 01 Nov 2004 12:02:29 +0100 From: Ali Hamidian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: herb@cnds.jhu.edu Subject: Re: [manet] Another questions about MAC protocols References: <003c01c4be8e$f82b3070$6801a8c0@amd2100> In-Reply-To: <003c01c4be8e$f82b3070$6801a8c0@amd2100> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org, "'Yau P'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: 7bit What Herb says is correct of course, but AODV will retransmit the broadcasted RREQ message if no RREP is received. After some number of retries AODV will give up. See the AODV RFC for more details. Hope it helps Ali Herbert Rubens wrote: >This is no ACK or retransmission of broadcast packets, only unicast >packets. So the RREQ will have no retransmissions by the lower layer but >the RREP will since it is unicast back to the source. > >Hope this helps. > >-Herb > > > >-----Original Message----- >From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf >Of Yau P >Sent: Saturday, October 30, 2004 10:20 AM >To: manet@ietf.org >Subject: [manet] Another questions about MAC protocols > >Dear all, > >I was wondering if you help me answer a simple question. Assuming that >802.11 or some other similar MAC protocol is being used, and the ad hoc >network in question is using AODV - does the broadcast of a RREQ undergo >the >same reliable delivery as with unicast packets (i.e. I think it is >three >attempts before 802.11 gives up)? > >Many thanks for your time in advance, >Po > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 1 10:44:29 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22294 for ; Mon, 1 Nov 2004 10:44:29 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COeb6-0001XE-6r for manet-web-archive@ietf.org; Mon, 01 Nov 2004 10:59:56 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COcd0-0002wm-8d; Mon, 01 Nov 2004 08:53:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COZiz-0008MC-KK for manet@megatron.ietf.org; Mon, 01 Nov 2004 05:47:45 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14782 for ; Mon, 1 Nov 2004 05:47:44 -0500 (EST) Received: from oola.is.scarlet.be ([193.74.71.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COZxp-00046O-Aq for manet@ietf.org; Mon, 01 Nov 2004 06:03:09 -0500 Received: from (u81-11-142-183.adsl.scarlet.be [81.11.142.183]) by oola.is.scarlet.be with ESMTP id iA1AlVG21155 for ; Mon, 1 Nov 2004 11:47:31 +0100 From: Bart Braem To: manet@ietf.org Subject: Re: [manet] AODV: previous hop for RREP Date: Mon, 1 Nov 2004 11:47:31 +0100 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411011147.31553.bart.braem@ua.ac.be> X-Spam-Score: 0.1 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: 7bit > Well basicaly, it means that when you receive a RREP, you just forward it > as it would be expected: sending it in the direction of the node which > originated the RREQ. You have a route to that node, because that route > has been reated when you received the RREQ (in the old AODV drafts > terminology: the reverse route (the route that goes from the destination > till the originator that is created when RREQ is being forwarded). > > But you don't send it to the originator node directly. You just > forward it to the next hop of the route to the originator. > And that next hop will do the same. And so on, till it > reaches the node that originated the RREQ. Okay I understand the principle. So that previous hop mentioned in the first paragraph is the next node which will send the RREP to the originator of the RREQ. But what happens when no valid route to the previous hop is found? It says "If needed, a route is created for the previous hop, but without a valid sequence number." I can create a new route table entry but then the RREP is stuck with me... A little bit further: "... the node consults its route table entry for the originating node to determine the next hop for the RREP packet, and then forwards the RREP towards the originator using the information in that route table entry." So a route to the next hop of presumed? Thanks for your help Bart _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 1 11:49:11 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01561 for ; Mon, 1 Nov 2004 11:49:10 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COfbf-0003rc-Tv for manet-web-archive@ietf.org; Mon, 01 Nov 2004 12:04:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COf3G-0006Wq-WB; Mon, 01 Nov 2004 11:29:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COeVh-0000cG-EE for manet@megatron.ietf.org; Mon, 01 Nov 2004 10:54:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23946 for ; Mon, 1 Nov 2004 10:54:20 -0500 (EST) From: McLanahan.Stevens@gd-ais.com Received: from mnblin01.mnb.gd-ais.com ([206.11.149.28] ident=firewall-user) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COekc-0001oF-HC for manet@ietf.org; Mon, 01 Nov 2004 11:09:47 -0500 Received: from blcex01.ad.gd-ais.com (blcex01.mnb.gd-ais.com [160.207.2.51]) by mnblin01.mnb.gd-ais.com (8.12.11/8.12.10) with ESMTP id iA1FsHfo010511 for ; Mon, 1 Nov 2004 09:54:17 -0600 Received: by blcex01.mnb.gd-ais.com with Internet Mail Service (5.5.2657.72) id ; Mon, 1 Nov 2004 09:54:17 -0600 Message-ID: <6806E1D3EF34D3408250BFDA3D465AB706AC6B64@blcex01.mnb.gd-ais.com> To: manet@ietf.org Subject: RE: [manet] New draft on connectivity scenarios and autoconfigura tion issues Date: Mon, 1 Nov 2004 09:54:14 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.3 (/) X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196 First of all some comments (nothing personal of course). Overall I think this will help to serve as an architectural starting point, a 10,000 foot view if you will. It does need to be cleaned up from an editorial perspective (grammar and spelling errors mostly). Since the group probably does not want to read my spelling nitpicks, I will leave those in a private follow up email. Besides, I'm an engineer, not an English professor. Technical Discussion -------------------- Section 2. Node: Do we want to tie ourselves to IPv4/IPv6 as a node definition. Perhaps IP-Based would be best here. After all, we never know if someone will come up with some sort of IPvWireless in the distant future. Section 3.2.1 Surveillance networks: I do not think the generalization that nodes will remain stationary is a good one. Surveillance (or preferably called Sensor networks), can have a dynamic nature to them depending on the application. Take, for example, a gas monitoring van (often used by gas companies) with several sensors on it. The van is in constant motion throughout the network. Perhaps a 3rd case should be added here. In addition a "Heavyweight" node scenario should probably be added where each node can act as a gateway/router if necessary. Section 4.1 I think a scenario needs to be addressed in this section that discusses the transient/isolated MANET issue. Take for example a MANET that periodically comes into contact with a gateway. That MANET will transition between an isolated MANET and a connected MANET. The potential for this happening in a mobile environment is high. Section 4.1.3 Volatile network scenario: What happens when the MANET is volatile? Let's take this case into consideration... 2 MANETs join with say x nodes that have the same address. The MANETs separate into two different networks with one MANET getting several of the duplicate addresses. Capability will have to exist in each MANET "sub-network" to broker network addresses. Section 4.2.4 Multiple Gateway routing and addressing issues (first paragraph): Isn't this issue solved by the various ad-hoc routing protocols out there. Do we really need this to be part of a dynamic configuration protocol? Section 4.2.4 Paragraph 3 It is desirable that traffic follows the same path uplink and downlink within the MANET: this is because the uplink path towards the default gateway is guaranteed to be optimal by routing the protocol. The follow up statement doesn't really prove anything. Just because an uplink path is optimal, doesn't always mean the downlink is. Take for example mobile nodes that have different transmit power levels, antenna heights, etc... Section 4.2.9 Paragraph 2. Expand on this. More discussion on source routing would be nice :) Section 5 Nodes with specific functionalities: It might be good to distribute the services across the MANET network. Or better yet, actually have "back-up" services. Nodes should have the capability to "jump in" if connectivity is lost. Section 6. I think something needs to be considered here. There are potential security issues that could arise (such as malicious nodes on a network). Perhaps a discussion on dynamic network configuration security would be good. I'm sure I will get some comments on some these points (after all, the morning coffee is only now kicking in so my mind is not fully revved up yet :)) but I just thought I would share some thoughts. -Mac Stevens --------------------------------------------- McLanahan Stevens Sr. Software Engineer General Dynamics Advanced Information Systems -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]On Behalf Of Ruffino Simone Sent: Monday, November 01, 2004 3:29 AM To: manet@ietf.org Subject: [manet] New draft on connectivity scenarios and autoconfiguration issues Hi to all, a new draft was submitted as individual submission, titled "Autoconfiguration in a MANET: connectivity scenarios and technical issues". Goal of the draft is to describe the scenarios, in which a MANET can be connected to an external network (by means of either wired of wireless links) and to list some of the technical issues, which are related to autoconfiguration and global connectivity, that arise in such scenarios. Comments welcome and appreciated ! Thanks in advance, Simone Ruffino > A New Internet-Draft is available from the on-line Internet-Drafts directories. > > > Title: Autoconfiguration in a MANET: connectivity scenarios and > technical issues > Author(s): S. Ruffino, et al. > Filename: draft-ruffino-manet-autoconf-scenarios-00.txt > Pages: 26 > Date: 2004-10-19 > > MANET interconnection with external networks enables a number of > usage scenarios, but generates also a number of technical issues, > mainly related with node autoconfiguration and global connectivity. > This Internet Draft aims at characterizing global connectivity > scenarios and listing technical issues related to IP address > autoconfiguration which are implied by such scenarios and should be > addressed by a generic solution. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ruffino-manet-autoconf-scenari os-00.txt > > Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia S.p.A. ==================================================================== 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 send an e_mail to MailAdmin@tilab.com. Thank you ==================================================================== _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 1 12:55:10 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09576 for ; Mon, 1 Nov 2004 12:55:10 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COgdb-0005q7-Ar for manet-web-archive@ietf.org; Mon, 01 Nov 2004 13:10:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COg30-0007f3-Bc; Mon, 01 Nov 2004 12:32:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COfih-0002rk-2e for manet@megatron.ietf.org; Mon, 01 Nov 2004 12:11:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04991 for ; Mon, 1 Nov 2004 12:11:49 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.200]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COfxc-0004cn-IO for manet@ietf.org; Mon, 01 Nov 2004 12:27:17 -0500 Received: by rproxy.gmail.com with SMTP id 77so256061rnl for ; Mon, 01 Nov 2004 09:11:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=A6wPCOaWn5NwG3zn/UfiIQZ3L0f8wUgfnz6/r8Km9hqIsVBgJbOZscsfEMG/8YyGPx7f3PKavh14y1j8wOQnbsKVeYf+Bgh5HF/GzpsGOMuBUuEvYrpglt3DCoxT4v0C7/fCw8auZTpsMU/EcI+HEGs25W9NZpeiIINZjncozI0= Received: by 10.38.150.54 with SMTP id x54mr845320rnd; Mon, 01 Nov 2004 09:11:36 -0800 (PST) Received: by 10.38.15.65 with HTTP; Mon, 1 Nov 2004 09:11:36 -0800 (PST) Message-ID: <78e4c4dc041101091179b71a2e@mail.gmail.com> Date: Mon, 1 Nov 2004 09:11:36 -0800 From: Pankaj Godbole To: Luke Klein-Berndt Subject: Re: [manet] AODV kernel module problem In-Reply-To: <030401c4c023$c141a670$33320681@campus.nist.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <78e4c4dc041029194821c4b9f4@mail.gmail.com> <030401c4c023$c141a670$33320681@campus.nist.gov> X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pankaj Godbole List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Content-Transfer-Encoding: 7bit Thanks Luke, The module is working now. The reason for the error was that I was passing the wrong interface to $use_dev in start.sh. Regards, Pankaj. On Mon, 1 Nov 2004 10:02:07 -0500, Luke Klein-Berndt wrote: > Hi Pankaj, > I think what might be happening is that additional error > messages are being generated by Kernel AODV. I would check the kernel > log to see if there are any messages there. I would also make sure the > interface you specify in the start.sh is properly configured and has an > IP address. > > Try: "insmod kernel_aodv.o use_dev=wlan0(or the interface you wish to > use)" > > Also if you would like to use modprobe, make sure you do "make install" > to place the module into the correct directory. > > Hope this helps, send me an email if it doesn't. > > -Luke Klein-Berndt > > > > > -----Original Message----- > > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] > > On Behalf Of Pankaj Godbole > > Sent: Friday, October 29, 2004 10:49 PM > > To: manet@ietf.org > > Subject: [manet] AODV kernel module problem > > > > > > Hi All, > > > > Has anybody tried to install and run the AODV kernel module > > from NIST ( kernel-aodv_v2.2.2)? I have successfully compiled > > this module, but when I try to run the script: start.sh, it > > returns an error saying > > "init_module: Operation not permitted" or "modprobe: Can't > > locate module" > > > > I have checked the paths to the module and also tried > > modifying the start.sh script but to no avail. If anyone has > > had success with this could you please guide me as to where I > > could be going wrong? > > > > Thanks in advance. > > Pankaj. > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 1 16:54:13 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08766 for ; Mon, 1 Nov 2004 16:54:13 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COkMx-0005AV-8c for manet-web-archive@ietf.org; Mon, 01 Nov 2004 17:09:44 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COjdI-00088T-1V; Mon, 01 Nov 2004 16:22:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COiwt-0001oi-Vn for manet@megatron.ietf.org; Mon, 01 Nov 2004 15:38:44 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28362 for ; Mon, 1 Nov 2004 15:38:40 -0500 (EST) Received: from bay23-f36.bay23.hotmail.com ([64.4.22.86] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COjBh-0002GV-4R for manet@ietf.org; Mon, 01 Nov 2004 15:54:12 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 1 Nov 2004 12:38:00 -0800 Received: from 142.137.26.200 by by23fd.bay23.hotmail.msn.com with HTTP; Mon, 01 Nov 2004 20:37:53 GMT X-Originating-IP: [142.137.26.200] X-Originating-Email: [kais_mnif@hotmail.com] X-Sender: kais_mnif@hotmail.com From: "Kais Mnif" To: manet@ietf.org Date: Mon, 01 Nov 2004 20:37:53 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 01 Nov 2004 20:38:00.0813 (UTC) FILETIME=[ADC051D0:01C4C052] X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Subject: [manet] how to build a benchmark for experimentation for ad hoc network X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Dear patriots In our educational laboratory, we like to build an ad hoc network for experimentation we just starting, we like to know if someone can help us to choose hardware (product such as switchs routers wireless cards etc. ) and software ! we anticipate to use Linux as an operating system. Any suggestion and help will be appreciated _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 1 18:05:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17302 for ; Mon, 1 Nov 2004 18:05:18 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COlTm-0007hs-8q for manet-web-archive@ietf.org; Mon, 01 Nov 2004 18:20:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COkpk-0001kl-6M; Mon, 01 Nov 2004 17:39:28 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COkh8-0003HI-Ao for manet@megatron.ietf.org; Mon, 01 Nov 2004 17:30:34 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13836 for ; Mon, 1 Nov 2004 17:30:32 -0500 (EST) Received: from ms-smtp-02-lbl.southeast.rr.com ([24.25.9.101] helo=ms-smtp-02-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COkw7-0006lh-27 for manet@ietf.org; Mon, 01 Nov 2004 17:46:03 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-02-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iA1MUK4R025941; Mon, 1 Nov 2004 17:30:23 -0500 (EST) From: "Christopher P. Rigano" To: "'Daniel Henkel'" , Subject: RE: [manet] Are there protocols that are like SIP or H.323 that couldprovide session or peer-peer sceesions in MANETS for Voice or Multimedia? Date: Mon, 1 Nov 2004 17:30:13 -0500 Message-ID: <000001c4c062$5b34c710$0600a8c0@CPQ73745201364> 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.2627 Importance: Normal In-Reply-To: <104146498433.20041030091307@gmx.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.1 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Content-Transfer-Encoding: quoted-printable Greetings Daniel, In your MANET architecture, do all the nodes act as Location Services, Proxies, User Agent Clients (UACs) and User Agent Server (UASs)? Thanks and regards, Chris -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Daniel Henkel Sent: Saturday, October 30, 2004 11:13 AM To: manet@ietf.org Subject: Re: [manet] Are there protocols that are like SIP or H.323 that couldprovide session or peer-peer sceesions in MANETS for Voice or Multimedia? Hi Christopher, We have successfully used SIP to initiate VoIP sessions over several hops in our testbed. Using Linphone on both laptops and iPAQs we were able to have very reliable communication with our DSR implementation. You can possibly use a much more stripped down version of SIP and achieve same results if footprint is an issue; try oSIP: http://www.gnu.org/software/osip/osip.html Regards, Daniel Henkel University of Colorado at Boulder http://AUGNet.colorado.edu ---- Original Message ---- From: Christopher P. Rigano To: Subject: [manet] Are there protocols that are like SIP or H.323 that could provide session or peer-peer sceesions in MANETS for Voice or Multimedia? Friday, October 29, 2004, 1:59:34 PM, you wrote: CPR> =A0 =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 2 00:54:00 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29273 for ; Tue, 2 Nov 2004 00:54:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COrrM-0008Qr-Cc for manet-web-archive@ietf.org; Tue, 02 Nov 2004 01:09:36 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COrZv-0003G1-St; Tue, 02 Nov 2004 00:51:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COrYj-0002dS-Hv for manet@megatron.ietf.org; Tue, 02 Nov 2004 00:50:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28929 for ; Tue, 2 Nov 2004 00:50:19 -0500 (EST) Received: from outbound04.telus.net ([199.185.220.223] helo=priv-edtnes51.telusplanet.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COrnm-0008LD-Jv for manet@ietf.org; Tue, 02 Nov 2004 01:05:55 -0500 Received: from JooHan ([154.20.57.100]) by priv-edtnes51.telusplanet.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP id <20041102054949.UHDX8263.priv-edtnes51.telusplanet.net@JooHan> for ; Mon, 1 Nov 2004 22:49:49 -0700 Message-ID: <00ea01c4c09f$c09c7a70$6439149a@JooHan> From: "Joo-Han Song" To: "Manet" Date: Mon, 1 Nov 2004 21:49:42 -0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.5 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Subject: [manet] layer of manet routing? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0021776250==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 This is a multi-part message in MIME format. --===============0021776250== Content-Type: multipart/alternative; boundary="----=_NextPart_000_00E7_01C4C05C.B20B3660" This is a multi-part message in MIME format. ------=_NextPart_000_00E7_01C4C05C.B20B3660 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable Hi all, Is there anyone who can clarify the layer of manet routing in real=20 implememtation? In many real papers, they are implemented as an application daemon. Does that mean the manet routing header should be included in the=20 application layer header? Another question is about routing header of AODV. In AODV's both RREQ or = RREP messages, I can find a destination address field. Since the IP = header=20 has the same field, I am wondering why we need to keep the same = destination=20 address field in both IP and AODV header. Regards, JH=20 ------=_NextPart_000_00E7_01C4C05C.B20B3660 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable Hi all,

Is there anyone who can clarify = the layer=20 of manet routing in real
implememtation?
In many real papers, = they are=20 implemented as an application daemon.
Does that mean the manet = routing header=20 should be included in the
application layer header?

Another = question=20 is about routing header of AODV. In AODV's both RREQ or
RREP = messages, I can=20 find a destination address field. Since the IP header
has the same = field, I=20 am wondering why we need to keep the same destination
address field = in both=20 IP and AODV header.

Regards,

JH
------=_NextPart_000_00E7_01C4C05C.B20B3660-- --===============0021776250== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0021776250==-- From manet-bounces@ietf.org Tue Nov 2 01:30:27 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02425 for ; Tue, 2 Nov 2004 01:30:27 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COsQb-0000kd-Rj for manet-web-archive@ietf.org; Tue, 02 Nov 2004 01:46:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COs7h-0000hq-QT; Tue, 02 Nov 2004 01:26:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COs1x-00065q-Ij for manet@megatron.ietf.org; Tue, 02 Nov 2004 01:20:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01842 for ; Tue, 2 Nov 2004 01:20:32 -0500 (EST) Received: from avas3.olemiss.edu ([130.74.120.13]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COsGw-0000YP-B1 for manet@ietf.org; Tue, 02 Nov 2004 01:36:07 -0500 Received: from sunset.backbone.olemiss.edu (sunset [172.16.1.8]) by avas3.olemiss.edu (8.12.11/8.12.11) with ESMTP id iA26KKC7032587; Tue, 2 Nov 2004 00:20:20 -0600 (envelope-from srgopal@olemiss.edu) Received: from olemiss.edu (webmail.olemiss.edu [172.16.1.11]) by sunset.backbone.olemiss.edu (8.12.10+Sun/8.12.9) with ESMTP id iA26KJes008788; Tue, 2 Nov 2004 00:20:20 -0600 (CST) From: "srgopal" To: "Christopher P. Rigano" , manet@ietf.org Subject: RE: [manet] Are there protocols that are like SIP or H.323 that couldprovide session or peer-peer sceesions in MANETS for Voice or Multimedia? X-Mailer: Quality Web Email v3.1e, http://netwinsite.com/refw.htm Date: Tue, 02 Nov 2004 00:20:19 -0600 Message-id: <41872723.374.4f92.1979108565@olemiss.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.0.0, Antispam-Data: 2004.11.1.6 X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: srgopal@olemiss.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Content-Transfer-Encoding: quoted-printable Dear Daniel and christopher, Are you saying that this SIP protocol can be used to generate VoIP packets like packet voice in Mobile Ad Hoc networks to see the performance of Ad Hoc networks when supporting VoIp and/or multimedia? I mean can it be used with ns-2 simulator and see its affect on ad hoc network performance. Please clarify this. If not, how can one generate packet voice while simulating Ad Hoc network using ns-2 simulator? I would appreciate your time and patience in this regard. Regards, Raja. > Greetings Daniel, > In your MANET architecture, do all the nodes act as > Location Services, Proxies, User Agent Clients (UACs) and > User Agent Server (UASs)? > > Thanks and regards, > > Chris > > -----Original Message----- > From: manet-bounces@ietf.org > [mailto:manet-bounces@ietf.org] On Behalf Of Daniel Henkel > Sent: Saturday, October 30, 2004 11:13 AM > To: manet@ietf.org > Subject: Re: [manet] Are there protocols that are like SIP > or H.323 that couldprovide session or peer-peer sceesions > in MANETS for Voice or Multimedia? > > Hi Christopher, > > We have successfully used SIP to initiate VoIP sessions > over several hops in our testbed. Using Linphone on both > laptops and iPAQs we were able to have very reliable > communication with our DSR implementation. You can > possibly use a much more stripped down version of SIP and > achieve same results if footprint is an issue; try oSIP: > http://www.gnu.org/software/osip/osip.html > > Regards, > Daniel Henkel > University of Colorado at Boulder > http://AUGNet.colorado.edu > > > ---- Original Message ---- > From: Christopher P. Rigano > To: > Subject: [manet] Are there protocols that are like SIP or > H.323 that could provide session or peer-peer sceesions in > MANETS for Voice or Multimedia? > > Friday, October 29, 2004, 1:59:34 PM, you wrote: > > CPR> =a0 > > > > > > > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 2 08:06:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16620 for ; Tue, 2 Nov 2004 08:06:08 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COyba-0000ru-MM for manet-web-archive@ietf.org; Tue, 02 Nov 2004 08:21:46 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COyF6-0003ss-P1; Tue, 02 Nov 2004 07:58:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COy64-0000YK-Ji for manet@megatron.ietf.org; Tue, 02 Nov 2004 07:49:12 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14911 for ; Tue, 2 Nov 2004 07:49:11 -0500 (EST) Received: from mail.crc.ca ([142.92.39.129]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COyL7-0000RP-Gc for manet@ietf.org; Tue, 02 Nov 2004 08:04:49 -0500 Received: from ROGER (roger.dgrc.crc.ca [142.92.38.14]) by mail.crc.ca (8.12.11/8.12.11) with SMTP id iA2Cbv49012400 for ; Tue, 2 Nov 2004 07:37:57 -0500 Message-Id: <200411021237.iA2Cbv49012400@mail.crc.ca> X-Sender: lli@mail.crc.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Tue, 02 Nov 2004 07:58:52 -0500 To: manet@ietf.org From: Li Li Subject: RE: [manet] Are there protocols that are like SIP or H.323 thatcouldprovide session or peer-peer sceesions in MANETS for Voiceor Multimedia? In-Reply-To: <41872723.374.4f92.1979108565@olemiss.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Scanned-By: MIMEDefang 2.44 X-Spam-Score: 1.9 (+) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 We did the SIP over MANET simulation using OPNET, generating SIP voice packets over an OLSR MANET to evaluate service performance. It should be possible with ns-2 simulator. You can find our work and paper at http://www.crc.ca/en/html/manetsensor/home/research_area/support li li At 12:20 AM 11/2/2004 -0600, srgopal wrote: >Dear Daniel and christopher, > >Are you saying that this SIP protocol can be used to >generate VoIP packets like packet voice in Mobile Ad Hoc >networks to see the performance of Ad Hoc networks when >supporting VoIp and/or multimedia? I mean can it be used >with ns-2 simulator and see its affect on ad hoc network >performance. Please clarify this. If not, how can one >generate packet voice while simulating Ad Hoc network using >ns-2 simulator? > >I would appreciate your time and patience in this regard. > >Regards, >Raja. > > > >> Greetings Daniel, >> In your MANET architecture, do all the nodes act as >> Location Services, Proxies, User Agent Clients (UACs) and >> User Agent Server (UASs)? >> >> Thanks and regards, >> >> Chris >> >> -----Original Message----- >> From: manet-bounces@ietf.org >> [mailto:manet-bounces@ietf.org] On Behalf Of Daniel Henkel >> Sent: Saturday, October 30, 2004 11:13 AM >> To: manet@ietf.org >> Subject: Re: [manet] Are there protocols that are like SIP >> or H.323 that couldprovide session or peer-peer sceesions >> in MANETS for Voice or Multimedia? >> >> Hi Christopher, >> >> We have successfully used SIP to initiate VoIP sessions >> over several hops in our testbed. Using Linphone on both >> laptops and iPAQs we were able to have very reliable >> communication with our DSR implementation. You can >> possibly use a much more stripped down version of SIP and >> achieve same results if footprint is an issue; try oSIP: >> http://www.gnu.org/software/osip/osip.html >> >> Regards, >> Daniel Henkel >> University of Colorado at Boulder >> http://AUGNet.colorado.edu >> >> >> ---- Original Message ---- >> From: Christopher P. Rigano >> To: >> Subject: [manet] Are there protocols that are like SIP or >> H.323 that could provide session or peer-peer sceesions in >> MANETS for Voice or Multimedia? >> >> Friday, October 29, 2004, 1:59:34 PM, you wrote: >> >> CPR> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> manet mailing 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 > Li Li, Ph.D Communications Research Centre, Industry Canada 3701 Carling avenue P.O. box 11490 Station H, Ottawa, Ontario, Canada K2H 8S2 Tel: (613) 990-5246 Email: li.li@crc.ca _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 2 09:02:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21498 for ; Tue, 2 Nov 2004 09:02:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COzUB-0002GE-TI for manet-web-archive@ietf.org; Tue, 02 Nov 2004 09:18:12 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COz71-0002a6-7f; Tue, 02 Nov 2004 08:54:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1COz5q-0001YR-5c for manet@megatron.ietf.org; Tue, 02 Nov 2004 08:53:02 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20843 for ; Tue, 2 Nov 2004 08:53:00 -0500 (EST) Received: from mailhub01-skge0.unibe.ch ([130.92.9.52] helo=mailhub01.unibe.ch) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1COzKw-00021W-5U for manet@ietf.org; Tue, 02 Nov 2004 09:08:39 -0500 Received: from localhost (scanhub02.unibe.ch [130.92.254.66]) by mailhub01.unibe.ch (Postfix) with ESMTP id 2BDD825BAEE for ; Tue, 2 Nov 2004 14:52:18 +0100 (MET) Received: from mailhub01.unibe.ch ([130.92.9.52]) by localhost (scanhub02.unibe.ch [130.92.254.66]) (amavisd-new, port 10024) with LMTP id 24542-03-83 for ; Tue, 2 Nov 2004 14:52:12 +0100 (CET) Received: from asterix.unibe.ch (asterix.unibe.ch [130.92.64.4]) by mailhub01.unibe.ch (Postfix) with ESMTP id 092EB25BB81 for ; Tue, 2 Nov 2004 14:52:16 +0100 (MET) Received: from [130.92.65.230] (kirok [130.92.65.230]) by asterix.unibe.ch (8.11.7p1+Sun/8.11.7) with ESMTP id iA2DqF118355 for ; Tue, 2 Nov 2004 14:52:15 +0100 (MET) Message-ID: <41879103.6030709@iam.unibe.ch> Date: Tue, 02 Nov 2004 14:52:03 +0100 From: =?windows-1252?Q?Marc_Heissenb=FCttel?= Organization: Inst. of CS, Universtity of Bern, Switzerland User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=windows-1252; format=flowed X-Virus-checked: by University of Berne Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: quoted-printable Subject: [manet] Energy Consumption of Sensor Nodes X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: quoted-printable Hi to all, does anybody have information about the typical energy consumption of=20 RF interface in ad-hoc or sensor network nodes. More specifically about=20 the ratio between sending / receiving / idle listening / sleep.=20 Obviously this is specific to the networking context, but I would be=20 just interested about some typical ratios that are achievable,=20 espeically for sensor network nodes. I am aware that several papers reported typical ratios for WLAN cards to=20 be in the order of 2 / 1.5 / 1 / 0.05 for send/recv/idle/sleep. Other papers such as "Wake on Wireless" or "PicoRadio" reported improved=20 ratios. Thanks Marc --=20 Marc Heissenb=FCttel Computer Networks and Distributed Systems Institute of Computer Science and Applied Mathematics University of Bern Neubr=FCckstrasse 10 CH-3012 Bern Switzerland Tel: +41 31 631 86 91 (direct) Tel: +41 31 631 89 57 (Secretary) Fax: +41 31 631 32 61 Email: heissen@iam.unibe.ch http://www.iam.unibe.ch _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 2 15:37:11 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09114 for ; Tue, 2 Nov 2004 15:37:11 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP5e9-0004qO-6T for manet-web-archive@ietf.org; Tue, 02 Nov 2004 15:52:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CP5D6-0001sg-Kw; Tue, 02 Nov 2004 15:24:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CP4zK-0007G9-12 for manet@megatron.ietf.org; Tue, 02 Nov 2004 15:10:43 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05424 for ; Tue, 2 Nov 2004 15:10:40 -0500 (EST) Received: from morse.colorado.edu ([198.11.21.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP5EU-0003zn-C9 for manet@ietf.org; Tue, 02 Nov 2004 15:26:22 -0500 Received: from morse.Colorado.EDU (localhost [127.0.0.1]) by morse.Colorado.EDU (8.12.10/8.12.10/UnixOps+Hesiod) with ESMTP id iA2KA67G004916; Tue, 2 Nov 2004 13:10:06 -0700 (MST) Received: from localhost (timxb@localhost) by morse.Colorado.EDU (8.12.10/8.12.8/Submit) with ESMTP id iA2KA5Sa004913; Tue, 2 Nov 2004 13:10:05 -0700 (MST) Date: Tue, 2 Nov 2004 13:10:05 -0700 (MST) From: Brown Tim To: =?windows-1252?Q?Marc_Heissenb=FCttel?= Subject: Re: [manet] Energy Consumption of Sensor Nodes In-Reply-To: <41879103.6030709@iam.unibe.ch> Message-ID: References: <41879103.6030709@iam.unibe.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=windows-1252 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Content-Transfer-Encoding: QUOTED-PRINTABLE Many cards have these numbers in their spec sheets. In particular Orinoco has this data. =09Regards, =09=09Tim On Tue, 2 Nov 2004, [windows-1252] Marc Heissenb=FCttel wrote: > > Hi to all, > > does anybody have information about the typical energy consumption of > RF interface in ad-hoc or sensor network nodes. More specifically about > the ratio between sending / receiving / idle listening / sleep. > Obviously this is specific to the networking context, but I would be > just interested about some typical ratios that are achievable, > espeically for sensor network nodes. > > I am aware that several papers reported typical ratios for WLAN cards to > be in the order of 2 / 1.5 / 1 / 0.05 for send/recv/idle/sleep. > > Other papers such as "Wake on Wireless" or "PicoRadio" reported improved > ratios. > > Thanks > > Marc > > > > -- > Marc Heissenb=FCttel > Computer Networks and Distributed Systems > Institute of Computer Science and Applied Mathematics > University of Bern > Neubr=FCckstrasse 10 > CH-3012 Bern > Switzerland > > Tel: +41 31 631 86 91 (direct) > Tel: +41 31 631 89 57 (Secretary) > Fax: +41 31 631 32 61 > Email: heissen@iam.unibe.ch > http://www.iam.unibe.ch > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > Timothy X Brown Interdisciplinary Telecommunications Electrical and Computer Engineering ECOT 256 Campus Box 530 University of Colorado Boulder, CO 80309 Tel: (303) 492-1630 Fax: (303) 492-1112 http://ece.colorado.edu/~timxb _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 2 16:01:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11359 for ; Tue, 2 Nov 2004 16:01:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP61u-0005d3-Gz for manet-web-archive@ietf.org; Tue, 02 Nov 2004 16:17:27 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CP5YY-0002B8-GA; Tue, 02 Nov 2004 15:47:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CP5Hc-0005rd-LJ for manet@megatron.ietf.org; Tue, 02 Nov 2004 15:29:36 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08114 for ; Tue, 2 Nov 2004 15:29:35 -0500 (EST) Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP5Wm-0004Yl-Sw for manet@ietf.org; Tue, 02 Nov 2004 15:45:18 -0500 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 iA2KTWeA168641 for ; Tue, 2 Nov 2004 15:29:32 -0500 (EST) Received: from angel (69-161-5-229.chvlva.adelphia.net [69.161.5.229]) by dagger.cc.vt.edu (MOS 3.4.8-GR) with ESMTP id BYJ27968 (AUTH ghadjich@127.0.0.1:1109); Tue, 2 Nov 2004 15:29:30 -0500 (EST) From: "George Hadjichristofi" To: Date: Tue, 2 Nov 2004 15:25:12 -0500 Message-ID: <000901c4c11a$10f68b80$ca00a8c0@angel> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.6 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Subject: [manet] distribution- bonnmotion vs. setdest X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ghadjich@vt.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1328931678==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc This is a multi-part message in MIME format. --===============1328931678== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01C4C0F0.28208380" This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C4C0F0.28208380 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear All, I was wondering whether there is any difference in the distribution of RandomWayPoint model mobility scenarios generated with bonnmotion vs. the RandomWayPoint model mobility scenarios generated with setdest in ns2? (partitions, average node degree,...) I am assuming that the parameters used are the same - speed, radio range, number of nodes, area .... Thank you, George ------=_NextPart_000_000A_01C4C0F0.28208380 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Dear=20 All,
 
I was = wondering=20 whether there is any difference in the distribution of RandomWayPoint=20 model mobility scenarios generated with bonnmotion vs. the = RandomWayPoint=20 model mobility scenarios generated with setdest in ns2? (partitions, = average=20 node degree,...)
 
I am = assuming that=20 the parameters used are the same - speed, radio range, number of nodes, = area=20 ....
 
Thank=20 you,
George
------=_NextPart_000_000A_01C4C0F0.28208380-- --===============1328931678== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1328931678==-- From manet-bounces@ietf.org Tue Nov 2 16:16:03 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13040 for ; Tue, 2 Nov 2004 16:16:03 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP6Fm-00066C-QJ for manet-web-archive@ietf.org; Tue, 02 Nov 2004 16:31:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CP5bQ-0004in-GI; Tue, 02 Nov 2004 15:50:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CP5SO-0005zp-0Q for manet@megatron.ietf.org; Tue, 02 Nov 2004 15:40:44 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09449 for ; Tue, 2 Nov 2004 15:40:42 -0500 (EST) Received: from fruitcake.icsi.berkeley.edu ([192.150.186.11]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP5hY-0004vF-4h for manet@ietf.org; Tue, 02 Nov 2004 15:56:25 -0500 Received: from Gezgin (dhcp98.icir.org [192.150.187.98]) by fruitcake.ICSI.Berkeley.EDU (8.12.10/8.12.9) with ESMTP id iA2KeaN2018338 for ; Tue, 2 Nov 2004 12:40:39 -0800 (PST) Message-Id: <200411022040.iA2KeaN2018338@fruitcake.ICSI.Berkeley.EDU> From: "Mesut Guenes" To: Date: Tue, 2 Nov 2004 12:40:32 -0800 Organization: ICSI MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcTBHDIwNyXuWfuqT5abJbO/lFZJNA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: quoted-printable Subject: [manet] AODV and DSR trace file curiosity X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: guenes@ICSI.Berkeley.EDU List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Content-Transfer-Encoding: quoted-printable Hi folks, I noticed a difference in trace files of AODV and DSR. Somehow AODV generates one line less than AODV for each data packet. In the following you see snippets from trace files based on simulation = runs with 3 nodes and chain topology: 0 - 1 - 2 Both AODV and DSR generate 2 events at the agent layer. At the routing layer AODV has 4 events, and DSR 5 events. AODV: s -t 3.000000 -Hs 0 -Hd -2 -Ni 0 -Nl AGT -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 64 -If 0 -Ii 1 -Iv 32 -Pn 0 -Pi 1 -Pf 0 -Po 0 r -t 3.000000 -Hs 0 -Hd -2 -Ni 0 -Nl RTR -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 64 -If 0 -Ii 1 -Iv 32 -Pn 0 -Pi 1 -Pf 0 -Po 0 s -t 3.000000 -Hs 0 -Hd 1 -Ni 0 -Nl RTR -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 84 -If 0 -Ii 1 -Iv 30 -Pn 0 -Pi 1 -Pf 0 -Po 0 r -t 3.002106 -Hs 1 -Hd 1 -Ni 1 -Nl RTR -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 84 -If 0 -Ii 1 -Iv 30 -Pn 0 -Pi 1 -Pf 1 -Po 0 f -t 3.002106 -Hs 1 -Hd 2 -Ni 1 -Nl RTR -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 84 -If 0 -Ii 1 -Iv 29 -Pn 0 -Pi 1 -Pf 1 -Po 0 r -t 3.004396 -Hs 2 -Hd 2 -Ni 2 -Nl AGT -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 84 -If 0 -Ii 1 -Iv 29 -Pn 0 -Pi 1 -Pf 2 -Po 0 DSR: s -t 3.000000 -Hs 0 -Hd -2 -Ni 0 -Nl AGT -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 64 -If 0 -Ii 5 -Iv 32 -Pn 0 -Pi 1 -Pf 0 -Po 0 r -t 3.000000 -Hs 0 -Hd -2 -Ni 0 -Nl RTR -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 64 -If 0 -Ii 5 -Iv 32 -Pn 0 -Pi 1 -Pf 0 -Po 0 s -t 3.000000 -Hs 0 -Hd 1 -Ni 0 -Nl RTR -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 104 -If 0 -Ii 5 -Iv 32 -Pn 0 -Pi 1 -Pf 0 -Po 0 r -t 3.002506 -Hs 1 -Hd 1 -Ni 1 -Nl RTR -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 104 -If 0 -Ii 5 -Iv 32 -Pn 0 -Pi 1 -Pf 1 -Po 0 f -t 3.002506 -Hs 1 -Hd 2 -Ni 1 -Nl RTR -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 104 -If 0 -Ii 5 -Iv 31 -Pn 0 -Pi 1 -Pf 1 -Po 0 r -t 3.005236 -Hs 2 -Hd 2 -Ni 2 -Nl RTR -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 104 -If 0 -Ii 5 -Iv 31 -Pn 0 -Pi 1 -Pf 2 -Po 0 r -t 3.005236 -Hs 2 -Hd 2 -Ni 2 -Nl AGT -Nw --- -Is 0.0 -Id 2.0 = -It cbr -Il 64 -If 0 -Ii 5 -Iv 31 -Pn 0 -Pi 1 -Pf 2 -Po 0 Especially, the last routing layer event of DSR looks somehow curios, = or? On the other hand the you find '-Pf 2' in both routing techniques at the agent layer, but the packet was forwarded only 1 times, or not? Does someone has an explanation? Regards Mesut G=FCnes _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 2 16:49:40 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19475 for ; Tue, 2 Nov 2004 16:49:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP6mJ-0007SG-Os for manet-web-archive@ietf.org; Tue, 02 Nov 2004 17:05:24 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CP63g-0001VM-OL; Tue, 02 Nov 2004 16:19:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CP5hi-0000bU-KS for manet@megatron.ietf.org; Tue, 02 Nov 2004 15:56:34 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10893 for ; Tue, 2 Nov 2004 15:56:33 -0500 (EST) Received: from universe.uohyd.ernet.in ([202.41.85.90]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CP5ws-0005VI-KJ for manet@ietf.org; Tue, 02 Nov 2004 16:12:16 -0500 Received: from ailab.uohyd.ernet.in (ailab.uohyd.ernet.in [202.41.85.117]) by universe.uohyd.ernet.in (8.9.0/8.9.0) with ESMTP id CAA15027; Wed, 3 Nov 2004 02:23:56 -0500 (GMT) Received: from ailab.uohyd.ernet.in (ailab [127.0.0.1]) by ailab.uohyd.ernet.in (8.12.8/8.12.8) with ESMTP id iA2KtBtm007024; Wed, 3 Nov 2004 02:25:11 +0530 Received: (from apache@localhost) by ailab.uohyd.ernet.in (8.12.8/8.12.8/Submit) id iA2Kt4rG007022; Wed, 3 Nov 2004 01:55:04 +0500 X-Authentication-Warning: ailab.uohyd.ernet.in: apache set sender to shahriar@ailab.uohyd.ernet.in using -f Received: from 172.16.1.2 (proxying for 172.16.2.28) (SquirrelMail authenticated user shahriar) by 172.16.17.2 with HTTP; Wed, 3 Nov 2004 01:55:04 +0500 (MVT) Message-ID: <60583.172.16.1.2.1099428904.squirrel@172.16.17.2> Date: Wed, 3 Nov 2004 01:55:04 +0500 (MVT) From: "Shahriar Shamil Uulu" To: , X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.10) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 8bit Subject: [manet] How to get ad-hoc secure routing protocols source codes X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: shahriar@ailab.uohyd.ernet.in List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 8bit Dear Members, I would like to know from where i can get the source codes of ad hoc security routing protocols like(i.e. Security aware ad hoc routing, SRP, ARAN,Watchdog and pathrate,ARIADNE,SAODV, SPRP) implemented on ns-2. If any body anything regarding this issue please help me. Any help will be apperciated. Thank you. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 3 02:37:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07050 for ; Wed, 3 Nov 2004 02:37:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPFwu-0004Xj-Hn for manet-web-archive@ietf.org; Wed, 03 Nov 2004 02:52:56 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPFfA-0000y2-VW; Wed, 03 Nov 2004 02:34:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPFVL-0004ad-5v for manet@megatron.ietf.org; Wed, 03 Nov 2004 02:24:27 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29794 for ; Wed, 3 Nov 2004 02:24:25 -0500 (EST) Received: from outbound01.telus.net ([199.185.220.220] helo=priv-edtnes57.telusplanet.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPFkb-0004Js-U6 for manet@ietf.org; Wed, 03 Nov 2004 02:40:14 -0500 Received: from JooHan ([154.20.57.100]) by priv-edtnes57.telusplanet.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with SMTP id <20041103072347.XMRQ22740.priv-edtnes57.telusplanet.net@JooHan> for ; Wed, 3 Nov 2004 00:23:47 -0700 Message-ID: <010c01c4c176$07b2b330$4cdf5289@JooHan> From: "Joo-Han Song" To: "Manet" Date: Tue, 2 Nov 2004 23:23:34 -0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.2 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Subject: [manet] how ARP is working in MANET? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1905513670==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe This is a multi-part message in MIME format. --===============1905513670== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0109_01C4C132.F9138C70" This is a multi-part message in MIME format. ------=_NextPart_000_0109_01C4C132.F9138C70 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable Hi, I am wondering how Address Resolution Protocol is working is MANET? Should ARP message be broadcasted in multihops or one hop? JH ------=_NextPart_000_0109_01C4C132.F9138C70 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable
Hi,
 
I am wondering how Address Resolution = Protocol is=20 working is MANET?
Should ARP message be broadcasted in = multihops or=20 one hop?
 
JH
------=_NextPart_000_0109_01C4C132.F9138C70-- --===============1905513670== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1905513670==-- From manet-bounces@ietf.org Wed Nov 3 04:56:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16515 for ; Wed, 3 Nov 2004 04:56:50 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPI87-0007ex-VW for manet-web-archive@ietf.org; Wed, 03 Nov 2004 05:12:41 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPHWt-0000KS-3W; Wed, 03 Nov 2004 04:34:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPHQa-0005Kp-4S for manet@megatron.ietf.org; Wed, 03 Nov 2004 04:27:41 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14752 for ; Wed, 3 Nov 2004 04:27:38 -0500 (EST) Received: from bay16-f35.bay16.hotmail.com ([65.54.186.85] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPHfr-00071d-AJ for manet@ietf.org; Wed, 03 Nov 2004 04:43:28 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 3 Nov 2004 01:27:01 -0800 Received: from 61.187.54.10 by by16fd.bay16.hotmail.msn.com with HTTP; Wed, 03 Nov 2004 09:26:51 GMT X-Originating-IP: [61.187.54.10] X-Originating-Email: [zongmng@hotmail.com] X-Sender: zongmng@hotmail.com From: "Zong Ming" To: liqiming@comp.nus.edu.sg Date: Wed, 03 Nov 2004 17:26:51 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed Message-ID: X-OriginalArrivalTime: 03 Nov 2004 09:27:01.0121 (UTC) FILETIME=[45EE5710:01C4C187] X-Spam-Score: 2.2 (++) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA14752 Cc: manet@ietf.org Subject: [manet] cbrp problem X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 2.2 (++) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: quoted-printable hello, I simulate cbrp in ns-allinone2.15b and trace=20 CBRP_Agent::no_of_clusters_.I found sometimes no_of_clusters_ was a=20 negative.Have you met this problem too? Zong Ming _________________________________________________________________ =C3=E2=B7=D1=CF=C2=D4=D8 MSN Explorer: http://explorer.msn.com/lccn/ =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 3 07:37:25 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02561 for ; Wed, 3 Nov 2004 07:37:25 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPKdY-00038p-HN for manet-web-archive@ietf.org; Wed, 03 Nov 2004 07:53:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPKEw-0007Jq-IX; Wed, 03 Nov 2004 07:27:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPK7D-0005bN-Hf for manet@megatron.ietf.org; Wed, 03 Nov 2004 07:19:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01021 for ; Wed, 3 Nov 2004 07:19:48 -0500 (EST) Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPKMX-0002kv-3l for manet@ietf.org; Wed, 03 Nov 2004 07:35:41 -0500 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 iA3CJoeA045601; Wed, 3 Nov 2004 07:19:50 -0500 (EST) Received: from qwertyuiop2003 (sun.irean.vt.edu [128.173.52.26]) by vivi.cc.vt.edu (MOS 3.4.8-GR) with SMTP id BXX75558; Wed, 3 Nov 2004 07:19:48 -0500 (EST) Message-ID: <002501c4c19f$688f9e60$6401a8c0@qwertyuiop2003> From: "Tao Lin" To: References: <3819AE3ED40E734BBC1ABF0259B2E1F82227C8@MBOX22.stu.nus.edu.sg> Subject: Re: [manet] how ARP is working in MANET? Date: Wed, 3 Nov 2004 07:19:31 -0500 Organization: Virginia Tech MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" 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 X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit Cc: joohans@telus.net X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tao Lin List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7bit One hop only. > Hi, > > I am wondering how Address Resolution Protocol is working is MANET? > Should ARP message be broadcasted in multihops or one hop? > > JH _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 3 07:52:37 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04079 for ; Wed, 3 Nov 2004 07:52:37 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPKsG-0003iA-Ck for manet-web-archive@ietf.org; Wed, 03 Nov 2004 08:08:29 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPKUF-0002Tm-0h; Wed, 03 Nov 2004 07:43:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPKSf-0001qX-6R for manet@megatron.ietf.org; Wed, 03 Nov 2004 07:42:02 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03312 for ; Wed, 3 Nov 2004 07:41:59 -0500 (EST) Received: from mx1.iit.cnr.it ([146.48.98.40] helo=mx.iit.cnr.it) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPKhx-0003Hc-Fk for manet@ietf.org; Wed, 03 Nov 2004 07:57:50 -0500 Received: from localhost (mx.iit.cnr.it [127.0.0.1]) by mx.iit.cnr.it (Postfix) with ESMTP id 5778A2EE44 for ; Wed, 3 Nov 2004 13:41:25 +0100 (CET) Received: from mx.iit.cnr.it ([127.0.0.1]) by localhost (mx.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23556-08 for ; Wed, 3 Nov 2004 13:41:21 +0100 (CET) Received: from delmastro1 (delmastrof.iit.cnr.it [146.48.98.74]) by mx.iit.cnr.it (Postfix) with ESMTP id 8DDC82EE48 for ; Wed, 3 Nov 2004 13:41:20 +0100 (CET) Message-ID: <00ac01c4c1a2$6eaa8c30$51d9fea9@delmastro1> From: "Franca Delmastro" To: Date: Wed, 3 Nov 2004 13:41:24 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by Content Checker at iit.cnr.it X-Spam-Score: 0.7 (/) X-Scan-Signature: 4863a9796402a44fdb52482f353618fe Subject: [manet] [WoWMoM 2005] Cfp: Submission Deadline EXTENDED to November 20 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0071154399==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.7 (/) X-Scan-Signature: 398dc098b38497efe55f044562a219e7 This is a multi-part message in MIME format. --===============0071154399== Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A9_01C4C1AA.CF9AB440" This is a multi-part message in MIME format. ------=_NextPart_000_00A9_01C4C1AA.CF9AB440 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -------------------------------------------------------------------------= We apologize in advance if you receive multiple copies of this CFP. ************************************************************* CALL FOR PAPERS WoWMoM 2005 IEEE International Symposium on a World of Wireless, Mobile and Multimedia Networks http://cnd.iit.cnr.it/wowmom2005 Taormina, Italy, June 13-16, 2005 Sponsored by The IEEE Computer Society The University of Texas at Arlington Technical sponsored by IEEE TCCC **** Submission Deadline --- November 10, 2004 **** Extended to November 20, 2004 ************************************************************** Technology evolution is driving toward a world of wireless, mobile, and multimedia pervasive communications where users can seamlessly and ubiquitously accomplish their tasks, access information or communicate with other users all the anytime, everywhere, and from any device. Technologies include, among others, IEEE 802.11, 802.15, 802.16, Mobile IP, micro-mobility protocols, IP paging, wireless IP QOS, mobile ad hoc and sensor networks, and cellular networks. In addition to these, new and emerging technologies (e.g., UWB) need to be taken into account. The resulting networking environment will constitute the fourth generation wireless networks. 4G will integrate different types of wireless networks with wire-line backbone network seamlessly, and provide the convergence of voice, multimedia and data traffic over a single IP based core network. WoWMoM 2005 technical program committee is soliciting papers addressing the research challenges toward a world of wireless, mobile, and multimedia pervasive communications. Two types of contributions will be accepted: FULL PAPERS: Full Papers must present original, previously unpublished, complete works, validated by experimentation, simulation, or analysis. Practical experiences and experimental efforts are welcome. POSITION PAPERS: Papers in this category must be visionary, innovative and forward-looking. They must offer new perspectives opening future research directions, rather than by presenting mature work with quantitative results. Only a limited number of slots will be available for position papers that will be reviewed primarily for relevance and originality. Topics of interest for WOWMOM 2005 include, but are not limited to: - System prototypes and experiences - Software technologies and systems - QoS for real-time voice and video in wireless networks - Interactive broadband television, gaming, and video distribution - Middleware support for QoS provision - Caching and content management in WLANs and WMANs - Differentiated service in wireless multimedia networks - IP-based multimedia services over wireless networks - Networking services for ambient intelligent and pervasive environments - Multicasting and broadcasting problems and solutions - Handoff and mobility management - Seamless internetworking - IP-based mobile networks - Location mechanism and services - Wireless BAN, PAN, LAN, and MAN - Ad hoc and sensor networks - Vehicular wireless networks - Access technologies - Third and fourth generation systems - Energy-efficient protocols and power management - Wireless security and authentication - Pricing and billing - Modeling and Performance evaluation PAPER SUBMISSION AND PUBLICATION =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 Papers should neither have been published elsewhere nor currently under review by another conference or journal. Guidelines on paper submission and formatting will be provided on the website. Accepted papers will appear in the symposium proceedings published by IEEE. IMPORTANT DATES =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Full papers due: November 10, 2004 Extended to: November 20, 2004 Notification: January 20, 2005 Camera Ready due: February 15, 2005 ORGANIZING COMMITTEE =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D GENERAL Co-Chairs: Giuseppe Anastasi, University of Pisa, Italy Sajal K. Das, The University of Texas at Arlington, USA PROGRAM Co-Chairs: Marco Conti, IIT-CNR, Italy Dipankar Raychaudhuri WINLAB/Rutgers University, USA FINANCE & REGISTRATION Chair: Yonghe Liu, The University of Texas at Arlington, USA PUBLICITY Co-Chairs: Mainak Chatterjee, Univ. Central Florida, USA Sunghyun Choi, Seoul National University, Korea Franca Delmastro, IIT-CNR, Italy PUBLICATION Co-Chairs: Eleonora Borgia, IIT-CNR, Italy Luciana Pelusi, IIT-CNR, Italy SPONSORSHIP Chair Alessandro Genco, University of Palermo, Italy LOCAL ARRANGEMENTS Chair: Antonio Puliafito, University of Messina, Italy WEB DESIGNER & MANAGER: Patrizia Andronico, IIT-CNR, Italy STEERING COMMITTEE =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Marco Conti, IIT-CNR, Italy Sajal K. Das, The University of Texas at Arlington, USA (chair) Dipankar Raychaudhuri WINLAB/Rutgers University, USA Satish K. Tripathi, SUNY Buffalo, USA PROGRAM COMMITTEE =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Arup Acharya, IBM T.J. Watson Research, USA Dharma P. Agrawal, University of Cincinnati, USA Kevin C. Almeroth, University of California at Santa Barbara, USA Christian Becker, University of Stuttgart, Germany Giuseppe Bianchi, University of Rome "Tor Vergata", Italy Chris Blondia, University of Antwerp, Belgium Azzedine Boukerche, University of Ottawa, Canada Jiannong Cao, Hong Kong Polytechnic University, Hong Kong Chua Kee Chaing, National University of Singapore, Republic of Singapore Rajarathnam Chandramouili, Stevens Institute of Technology, USA Mainak Chatterjee, University of Central Florida, USA Carla-Fabiana Chiasserini, Polytechnic of Turin, Italy A. Chockalingam, Indian Institute of Science, Banglore, India Sunghyun Choi, Seoul National University, Korea Antonio Corradi, University of Bologna, Italy Antony Ephremides, University of Maryland, USA Gabor Fodor, Ericsson, Sweden Luigi Fratta, Polytechnic of Milan, Italy Marco Gruteser, Rutgers University, USA Paul J.M. Havinga, University of Twente, The Netherlands Kazuo Imai, NTT DoCoMo, Japan Holger Karl, Universtit=E4t Paderborn, Germany Anurag Kumar, Indian Inst of Science, Bangalore, India Mohan Kumar, The University of Texas at Arlington, USA P. R. Kumar, University of Illinois, USA Masahiro Kuroda, National Institute of Info. and Com. Tech., Japan Luciano Lenzini, University of Pisa, Italy K. Ben Letaief, Hong Kong Univ. Science & Technology, Hong Kong Victor Leung, The University of British Columbia, Canada Yonghe Liu, Univ. Texas at Arlington, USA Giri Mandyam, Nokia Research Center, USA Martin Mauve, University of Dusseldorf, Germany Archan Misra, IBM T.J. Watson Research, USA Refik Molva, Institut Eurecom, France Giacomo Morabito, University of Catania, Italy Hiroyuki Morikawa, , University of Tokyo, Japan Stephan Olariu, Old Dominion University, USA Maximilian Ott, Semandex Networks, USA Michael Paterakis, Technical University of Crete, Greece George C. Polyzos, Athens University of Economics and Business, Greece Antonio Puliafito, University of Messina, Italy Jochen H. Schiller, Freie Universit=E4t Berlin, Germany Henning Schulzrinne, Columbia University, USA Rajeev Shorey, IBM India Research Lab, India Ivan Stojmenovic, University of Ottawa, Canada Violet R. Syrotiuk, Arizona State University, USA Wade Trappe, Rutgers University, USA Ooi Wei Tsang, National University of Singapore, Singapore Christian Tschudin, Basel University, Switzerland Thierry Turletti, INRIA France Andras Valko, Ericsson, Hungary Bernard Walke, Aachen University of Technology, Germany Xingwei Wang, Northeastern Univ, China Jie Wu, Florida Atlantic University, USA Gergely Zaruba, The University of Texas at Arlington, USA Roger Zimmerman, University of Southern California, USA ************************************************************ Franca Delmastro Pervasive Computing & Networking Lab. (PerLab) IIT- National Research Council via G. Moruzzi,1 56124 Pisa, Italy ******************************************************** ------=_NextPart_000_00A9_01C4C1AA.CF9AB440 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
----------------------------------------------------------------= ---------

We apologize in advance if you = receive multiple=20 copies of this=20 CFP.
*************************************************************

          &nbs= p;         &nbs= p;  =20 CALL FOR PAPERS

          &nbs= p;         &nbs= p;    =20 WoWMoM 2005
         IEEE=20 International Symposium on a World of=20 Wireless,
          =        =20 Mobile and Multimedia=20 Networks

         &nb= sp;      =20 http://cnd.iit.cnr.it/wowmom2005
      &= nbsp;        =20 Taormina, Italy, June 13-16,=20 2005

          &= nbsp;         &= nbsp;    =20 Sponsored=20 by
           <= SPAN>       =20 The IEEE Computer=20 Society
          &n= bsp; =20 The University of Texas at=20 Arlington
          =    =20 Technical sponsored by IEEE=20 TCCC

        **** Submission = Deadline=20 --- November 10, 2004 ****
          &nbs= p;            = ; =20  Extended to November 20,=20 2004
**********************************************************= ****


Technology=20 evolution is driving toward a world of wireless,
mobile, and = multimedia=20 pervasive communications where users can
seamlessly and ubiquitously=20 accomplish their tasks, access information
or communicate with other = users=20 all the anytime, everywhere, and from
any device. Technologies = include, among=20 others, IEEE 802.11,
802.15, 802.16, Mobile IP, micro-mobility = protocols, IP=20 paging,
wireless IP QOS, mobile ad hoc and sensor networks, and=20 cellular
networks.
In addition to these, new and emerging = technologies=20 (e.g., UWB) need to
be taken into account.  The resulting = networking=20 environment will
constitute the fourth generation wireless networks. = 4G will=20 integrate
different types of wireless networks with wire-line = backbone=20 network
seamlessly, and provide the convergence of voice, multimedia=20 and
data traffic over a single IP based core network.  WoWMoM = 2005=20 technical
program committee is soliciting papers addressing the=20 research
challenges
toward a world of wireless, mobile, and = multimedia=20 pervasive
communications.
Two types of contributions will be=20 accepted:

FULL PAPERS: Full Papers must present original, = previously=20 unpublished,
complete works, validated by experimentation, = simulation, or=20 analysis.
Practical experiences and experimental efforts are=20 welcome.

POSITION PAPERS: Papers in this category must be = visionary,=20 innovative
and forward-looking. They must offer new perspectives = opening=20 future
research directions, rather than by presenting mature work=20 with
quantitative results. Only a limited number of slots will be=20 available
for
position papers that will be reviewed primarily for=20 relevance and
originality.

Topics of interest for WOWMOM 2005 = include,=20 but are not limited to:
- System prototypes and experiences
- = Software=20 technologies and systems
- QoS for real-time voice and video in = wireless=20 networks
- Interactive broadband television, gaming, and video=20 distribution
- Middleware support for QoS provision
- Caching and = content=20 management in WLANs and WMANs
- Differentiated service in wireless = multimedia=20 networks
- IP-based multimedia services over wireless networks
-=20 Networking services for ambient intelligent and pervasive = environments
-=20 Multicasting and broadcasting problems and solutions
- Handoff and = mobility=20 management
- Seamless internetworking
- IP-based mobile=20 networks
- Location mechanism and = services
- Wireless=20 BAN, PAN, LAN, and MAN
- Ad hoc and sensor networks
- Vehicular = wireless=20 networks
- Access technologies
- Third and fourth generation = systems
-=20 Energy-efficient protocols and power management
- Wireless security = and=20 authentication
- Pricing and billing
- Modeling and Performance=20 evaluation

PAPER SUBMISSION AND=20 PUBLICATION
=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
Papers should neither have been = published=20 elsewhere nor currently
under review by another conference or = journal. =20 Guidelines on paper
submission and formatting will be = provided on=20 the website.
Accepted papers will appear in the symposium proceedings = published by
IEEE.


IMPORTANT = DATES
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Full=20 papers due:        November 10,=20 2004
Extended to:     = November 20,=20 2004
Notification:        &nb= sp; =20 January 20, 2005
Camera Ready = due:      =20 February 15, 2005


ORGANIZING COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=
GENERAL=20 Co-Chairs:
        Giuseppe = Anastasi,=20 University of Pisa, Italy
        = Sajal K.=20 Das, The University of Texas at Arlington, USA

PROGRAM=20 Co-Chairs:
        Marco Conti, = IIT-CNR,=20 Italy
        Dipankar = Raychaudhuri=20 WINLAB/Rutgers University, USA


FINANCE & REGISTRATION=20 Chair:
         Yonghe Liu, = The=20 University of Texas at Arlington, USA
PUBLICITY=20 Co-Chairs:
         Mainak=20 Chatterjee, Univ. Central Florida,=20 USA
         Sunghyun Choi, = Seoul=20 National University, Korea
        =20 Franca Delmastro, IIT-CNR, Italy


PUBLICATION Co-Chairs:
        =20 Eleonora Borgia, IIT-CNR, Italy
        =20 Luciana Pelusi, IIT-CNR, Italy


SPONSORSHIP Chair
        Alessandro = Genco,=20 University of Palermo, Italy


LOCAL ARRANGEMENTS=20 Chair:
        Antonio Puliafito,=20 University of Messina, Italy


WEB DESIGNER &=20 MANAGER:
        Patrizia = Andronico,=20 IIT-CNR, Italy



STEERING=20 COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Ma= rco Conti, IIT-CNR, Italy
Sajal K. Das,=20 The University of Texas at Arlington, USA (chair)
Dipankar = Raychaudhuri=20 WINLAB/Rutgers University, USA
Satish K. Tripathi, SUNY Buffalo,=20 USA


PROGRAM = COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Arup = Acharya, IBM T.J.=20 Watson Research, USA
Dharma P. Agrawal, University of Cincinnati,=20 USA
Kevin C. Almeroth, University of California at Santa Barbara,=20 USA
Christian Becker, University of Stuttgart, Germany
Giuseppe = Bianchi,=20 University of Rome "Tor Vergata", Italy
Chris Blondia, University of = Antwerp,=20 Belgium
Azzedine  Boukerche, University of Ottawa, = Canada
Jiannong=20 Cao, Hong Kong Polytechnic University, Hong Kong
Chua Kee Chaing, = National=20 University of Singapore, Republic of Singapore
Rajarathnam = Chandramouili,=20 Stevens Institute of Technology, USA
Mainak Chatterjee, University of = Central=20 Florida, USA
Carla-Fabiana Chiasserini, Polytechnic of Turin, = Italy
A.=20 Chockalingam, Indian Institute of Science, Banglore, India
Sunghyun = Choi,=20 Seoul National University, Korea
Antonio Corradi, University of = Bologna,=20 Italy
Antony Ephremides, University of Maryland, USA
Gabor Fodor,=20 Ericsson, Sweden
Luigi Fratta, Polytechnic of Milan, Italy
Marco = Gruteser,=20 Rutgers University, USA
Paul J.M. Havinga, University of Twente, The=20 Netherlands
Kazuo Imai, NTT DoCoMo, Japan
Holger Karl, Universtit=E4t = Paderborn,=20 Germany
Anurag Kumar, Indian Inst of = Science, Bangalore,=20 India
Mohan Kumar, The University of Texas at Arlington, USA
P. R. = Kumar,=20 University of Illinois, USA
Masahiro Kuroda, National Institute of = Info. and=20 Com. Tech., Japan
Luciano Lenzini, University of Pisa, Italy
K. = Ben=20 Letaief, Hong Kong Univ. Science & Technology, Hong Kong
Victor = Leung,=20 The University of British Columbia, Canada
Yonghe Liu, Univ. Texas at = Arlington,=20 USA
Giri Mandyam, Nokia Research Center, = USA
Martin Mauve, University of Dusseldorf, Germany
Archan Misra, = IBM T.J.=20 Watson Research, USA
Refik Molva, Institut Eurecom, France
Giacomo = Morabito, University of Catania, Italy
Hiroyuki Morikawa, , = University of=20 Tokyo, Japan
Stephan Olariu, Old Dominion University, = USA
Maximilian Ott,=20 Semandex Networks, USA
Michael Paterakis, Technical University of = Crete,=20 Greece
George C. Polyzos, Athens University of Economics and = Business,=20 Greece
Antonio Puliafito, University of Messina, Italy
Jochen H. = Schiller,=20 Freie Universit=E4t Berlin, Germany
Henning Schulzrinne, Columbia = University,=20 USA
Rajeev Shorey, IBM India Research Lab, India
Ivan Stojmenovic, = University of Ottawa, Canada
Violet R. Syrotiuk, Arizona State = University,=20 USA
Wade Trappe, Rutgers University, USA
Ooi Wei Tsang, National=20 University of Singapore, Singapore
Christian Tschudin, Basel = University,=20 Switzerland
Thierry Turletti, INRIA France
Andras Valko, Ericsson, = Hungary
Bernard Walke, Aachen University of Technology, = Germany
Xingwei=20 Wang, Northeastern Univ, China
Jie Wu, Florida Atlantic University,=20 USA
Gergely Zaruba, The University of = Texas at=20 Arlington, USA
Roger Zimmerman, University of = Southern=20 California, USA
 
************************************************************
= Franca=20 Delmastro
Pervasive Computing & Networking Lab. = (PerLab)
 
IIT- National Research = Council
via G.=20 Moruzzi,1
56124 Pisa,=20 Italy
********************************************************<= /DIV> ------=_NextPart_000_00A9_01C4C1AA.CF9AB440-- --===============0071154399== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0071154399==-- From manet-bounces@ietf.org Wed Nov 3 10:55:58 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21397 for ; Wed, 3 Nov 2004 10:55:57 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPNji-0008NM-Oj for manet-web-archive@ietf.org; Wed, 03 Nov 2004 11:11:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPNPi-0005Zb-ME; Wed, 03 Nov 2004 10:51:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPNKO-0004f2-Od for manet@megatron.ietf.org; Wed, 03 Nov 2004 10:45:41 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20806 for ; Wed, 3 Nov 2004 10:45:37 -0500 (EST) Received: from xizor.is.scarlet.be ([193.74.71.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPNZi-0008Aw-8j for manet@ietf.org; Wed, 03 Nov 2004 11:01:31 -0500 Received: from (u212-239-152-89.adsl.scarlet.be [212.239.152.89]) by xizor.is.scarlet.be with ESMTP id iA3FjQ516166 for ; Wed, 3 Nov 2004 16:45:27 +0100 From: Bart Braem To: manet@ietf.org Date: Wed, 3 Nov 2004 16:45:27 +0100 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411031645.27190.bart.braem@ua.ac.be> X-Spam-Score: 0.2 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit Subject: [manet] AODV: small RFC question X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7bit Hello, Just to be certain: in chapter 6.2 is the third case in which a route can be updated the case in which the *new* sequence number is unknown? Otherwise I don't now how to interpret 6.5: "without a valid sequence number (see section 6.2)". Thanks for your help, Bart _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 4 01:21:24 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02581 for ; Thu, 4 Nov 2004 01:21:24 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPbFJ-0002le-0G for manet-web-archive@ietf.org; Thu, 04 Nov 2004 01:37:24 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPauC-0006b3-Uf; Thu, 04 Nov 2004 01:15:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPalw-0004eC-Sz for manet@megatron.ietf.org; Thu, 04 Nov 2004 01:07:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01667 for ; Thu, 4 Nov 2004 01:07:00 -0500 (EST) Received: from ziz.its.uow.edu.au ([130.130.68.16]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPb1P-0002V3-Dq for manet@ietf.org; Thu, 04 Nov 2004 01:23:00 -0500 Received: from febris.its.uow.edu.au ([130.130.68.100]) by ziz.its.uow.edu.au with esmtp (Exim 4.34) id 1CPals-00074g-IP; Thu, 04 Nov 2004 17:06:56 +1100 Received: from mirapoint.uow.edu.au (mirapoint.uow.edu.au [130.130.68.27]) by febris.its.uow.edu.au (MOS 3.5.5-GR) with ESMTP id AFX13907; Thu, 4 Nov 2004 17:06:55 +1100 (EST) Received: from 69.197.226.58 by mirapoint.uow.edu.au (MOS 3.5.3-GR) with HTTP/1.1; Thu, 4 Nov 2004 17:06:55 +1100 Date: Thu, 4 Nov 2004 17:06:55 +1100 From: Lan Nguyen To: manet@ietf.org X-Mailer: Mirapoint Webmail Direct 3.5.3-GR MIME-Version: 1.0 Message-Id: <90a655e1.99d1bb59.8254300@mirapoint.uow.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.9 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit Subject: [manet] AMRIS glomosim source code X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7bit Hi, Anyone knows where to get the AMRIS glomosim/qualnet patch/source code ? Lan ---- Grad Student, York University http://www.cs.yorku.ca/~lan _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 4 02:54:13 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA23406 for ; Thu, 4 Nov 2004 02:54:13 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPchC-0004gW-Na for manet-web-archive@ietf.org; Thu, 04 Nov 2004 03:10:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPcMe-0002Yt-4r; Thu, 04 Nov 2004 02:49:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPcEm-000204-9m for manet@megatron.ietf.org; Thu, 04 Nov 2004 02:40:54 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22549 for ; Thu, 4 Nov 2004 02:40:51 -0500 (EST) Received: from jpnmailout02.yamato.ibm.com ([203.141.80.82]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPcUB-0004P2-2r for manet@ietf.org; Thu, 04 Nov 2004 02:56:52 -0500 Received: from e19f2n15.jp.ibm.com (d19relay01.sagamino.japan.ibm.com [203.141.80.90] (may be forged)) by jpnmailout02.yamato.ibm.com (8.12.11/8.12.11) with ESMTP id iA47e9KD012842 for ; Thu, 4 Nov 2004 16:40:09 +0900 Received: from D19ML114.sagamino.japan.ibm.com (d19av04.sagamino.japan.ibm.com [9.189.5.112]) by e19f2n15.jp.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iA47e9Ek144590 for ; Thu, 4 Nov 2004 16:40:09 +0900 In-Reply-To: <200411031300.iA3D0rMJ077674@jpnmailin02.yamato.ibm.com> To: manet@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.2CF2 July 23, 2003 From: Akihiko Mizutani Message-ID: Date: Thu, 4 Nov 2004 16:40:07 +0900 X-MIMETrack: Serialize by Router on D19ML114/19/M/IBM(Release 6.51HF338 | June 21, 2004) at 2004/11/04 16:40:09, Serialize complete at 2004/11/04 16:40:09 X-Spam-Score: 0.0 (/) X-Scan-Signature: f460acdc4aacf7fc5e6f9bd32f8fd8c6 Subject: [manet] IPSJ ICMU2005: Call for Papers -- Submission deadline extended -- X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2010879994==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 031b5f42d6d2cd097710e6b68613cb36 This is a multipart message in MIME format. --===============2010879994== Content-Type: multipart/alternative; boundary="=_alternative 002A245B49256F42_=" This is a multipart message in MIME format. --=_alternative 002A245B49256F42_= Content-Type: text/plain; charset="ISO-2022-JP" ======================================================================== CALL FOR PAPERS Second International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2005) April 13 through 15, 2005 Osaka University Convention Center, Osaka, Japan http://www.ipsj.or.jp/sig/mbl/icmu2005/ IMPORTANT DATES Deadline for submissions: November 15, 2004 ****** Extended to: December 1, 2004 ******* Notification of acceptance: January 15, 2005 Camera ready due: February 15, 2005 Sponsored by IPSJ SIG-MBL (Information Processing Society of Japan, Special Interest Group of Mobile Computing and Ubiquitous Networking) IPSJ SIG-BCC (Study Group of Broadcast Communication and Computing) Supported by IPSJ SIG-ITS (Special Interest Group of Intelligent Transport Systems) IPSJ SIG-UBI (Ubiquitous Computing System) Telecommunications Advancement Foundation. ------------------------------------------------------------------------------- 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 management for ubiquitous networking * Data management for mobile computing * Wireless and mobile communications * Performance evaluation for mobile computing and ubiquitous networking systems * Broadcast communication * Network architectures, protocols, or service models for ubiquitous networking * Security in mobile computing and ubiquitous networking * Nomadic computing * Mobile Internetworking * Ad hoc networks * Sensor networks * Location-based Service 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 the web site of the conference http://www.ishilab.net/icmu2005/ http://www.ipsj.or.jp/sig/mbl/icmu2005/ for further submission instructions. Important Dates ~~~~~~~~~~~~~~~ Deadline for submissions: November 15, 2004 ********** Extended to: December 1, 2004 ********* Notification of acceptance: January 15, 2005 Camera ready due: February 15, 2005 After the conference, a selected number of papers will be published as special issues in IPSJ journal. Committees ~~~~~~~~~~ General Chair Yasuo Hirata (KDDI R&D Laboratories, Japan) Executive Committee Co-Chairs: Tadanori Mizuno (Shizuoka University, Japan) Osamu Takahashi (Future University-Hakodate, Japan) Technical Program Committee Chair: Takashi Watanabe (Shizuoka University, Japan) Publication Chair Hidetoshi Yokota (KDDI R&D Laboratories, Japan) Publicity Chair Akihiko Mizutani (IBM Japan, Japan) Local Arrangement Masahiko Tsukamoto (Kobe University, Japan) Treasurer Hirozumi Yamaguchi (Osaka University, Japan) Technical Program Committee Mohammed Atiquzzaman (University of Oklahoma, USA) Masaki Bandai (Shizuoka University, Japan) Po-Jen Chuang (Tamkang University, Taiwan) Xiuzhen Cheng (George Washington University, USA) Nobutsugu Fujino (Fujitsu Laboratories, Japan) Jeong Hye Han (Cheongju National University of Education, Korea) Chung-Ming Huang (National Cheng Kung University, Taiwan) Tetsuo Ideguchi (Aichi Prefectural University, Japan) Fumiyuki Iizuka (Fujitsu Laboratories, Japan) Akino Inoue (Matsushita Electric Industrial, Japan) Masugi Inoue (National Institute of Information and CommunicationsTechnology, Japan) Susumu Ishihara (Shizuoka University, Japan) Masahiro Ishiyama (Toshiba Corporation, Japan) Tomoko Itao (NTT, Japan) Shuichi Karino (NEC, Japan) Nobuo Kawaguchi (Nagoya University, Japan) Dong Yoon Kim (Ajou University, Korea) Cheeha Kim (Pohang University of Science and Technology, Korea) Kane Kim (University of California at Irvine, USA) Gen Kitagata (Tohoku University, Japan) Peter Langendoerfer (IHP Microelectronics, Germany) Mitsuji Matshumoto(Waseda University, Japan) Masateru Minami (Shibaura Institute of Technology, Japan) Akihiko Mizutani (IBM Japan, Japan) Eigo Mori (Nokia Japan, Japan) Hiroyuki Morikawa (University of Tokyo, Japan) Yasuto Nakanishi (Tokyo University of Agriculture and Technology, Japan) Junya Nakata (Japan Advanced Institute of Science and Technology, Japan $B!K(B Masahiro Nishi (Hiroshima City University, Japan) Akiyoshi Ogawa (Vodafone, Japan) Ken Ohta (NTT DoCoMo, Japan) Minoru Okada (Nara Institute of Science and Technology, Japan) Kouji Okamura (Kyushu University, Japan) Ryouji Ono (Mitsubishi Electric, Japan) Yuko Onoe (NTT DoCoMo, Japan) Antonio Pescape (University of Napoli, Italy) Keizo Saisho (Kagawa University, Japan) Ichiro Satoh (National Institute of Informatics, Japan) Winston Seah (Institute for Infocomm Research, Singapore) Hiroshi Shigeno (Keio University, Japan) Akio Shinohara (NTT, Japan) Biplab Sikdar (Rensselaer Polytechnic Institute, USA) Tatsuya Suda (University of California at Irvine$B!$(BUSA) Shinta Sugimoto (Nippon Ericsson, Japan) Keisuke Suwa (Musashi Institute of Technology, Japan) Kastumi Takahashi (NTT, Japan) Osamu Takahashi (Future University-Hakodate, Japan) Kazunori Takashio (Keio University, Japan) Takamichi Tateoka (University of Electro-Communications, Japan) Chai-Keong Toh (Queen Mary University of London, UK) Msahiko Tsukamoto (Kobe University, Japan) Hirozumi Yamaguchi (Osaka University, Japan) Hirofumi Yamaki (Kyoto University, Japan) Miki Yamamoto (Osaka University, Japan) Nagatsugu Yamanouchi (Toho University, Japan) Masashi Yano (Hitachi Ltd., Japan) Takashi Yoshino (Wakayama University, Japan) --=_alternative 002A245B49256F42_= Content-Type: text/html; charset="ISO-2022-JP"
========================================================================
                           CALL FOR PAPERS

                Second International Conference on
       Mobile Computing and Ubiquitous Networking (ICMU 2005)

                    April 13 through 15, 2005
          Osaka University Convention Center, Osaka, Japan
             http://www.ipsj.or.jp/sig/mbl/icmu2005/

                         IMPORTANT DATES

           Deadline for submissions: November 15, 2004
                  ****** Extended to: December 1, 2004 *******
            Notification of acceptance: January 15, 2005
            Camera ready due: February 15, 2005

Sponsored by

 IPSJ SIG-MBL (Information Processing Society of Japan, Special Interest
               Group of Mobile Computing and Ubiquitous Networking)
IPSJ SIG-BCC (Study Group of Broadcast Communication and Computing)

Supported by

 IPSJ SIG-ITS (Special Interest Group of Intelligent Transport Systems)
IPSJ SIG-UBI (Ubiquitous Computing System)
 Telecommunications Advancement Foundation.
<Please forgive us if you receive this information from multiple sources>
-------------------------------------------------------------------------------

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 management for ubiquitous networking
* Data management for mobile computing
* Wireless and mobile communications
* Performance evaluation for mobile computing and
 ubiquitous networking systems
* Broadcast communication
* Network architectures, protocols, or service models
 for ubiquitous networking
* Security in mobile computing and ubiquitous networking
* Nomadic computing
* Mobile Internetworking
* Ad hoc networks
* Sensor networks
* Location-based Service


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 the web site of the conference

http://www.ishilab.net/icmu2005/
http://www.ipsj.or.jp/sig/mbl/icmu2005/
for further submission instructions.

Important Dates
~~~~~~~~~~~~~~~
Deadline for submissions: November 15, 2004
  ********** Extended to: December 1, 2004 *********
Notification of acceptance: January 15, 2005
Camera ready due: February 15, 2005


After the conference, a selected number of papers will be published
as special issues in IPSJ journal.


Committees
~~~~~~~~~~
General Chair
Yasuo Hirata (KDDI R&D Laboratories, Japan)

Executive Committee Co-Chairs:
Tadanori Mizuno (Shizuoka University, Japan)
Osamu Takahashi (Future University-Hakodate, Japan)

Technical Program Committee Chair:
Takashi Watanabe (Shizuoka University, Japan)

Publication Chair
Hidetoshi Yokota (KDDI R&D Laboratories, Japan)

Publicity Chair
Akihiko Mizutani (IBM Japan, Japan)

Local Arrangement
Masahiko Tsukamoto (Kobe University, Japan)

Treasurer
Hirozumi Yamaguchi (Osaka University, Japan)

Technical Program Committee
Mohammed Atiquzzaman (University of Oklahoma, USA)
Masaki Bandai (Shizuoka University, Japan)
Po-Jen Chuang (Tamkang University, Taiwan)
Xiuzhen Cheng (George Washington University, USA)
 Nobutsugu Fujino (Fujitsu Laboratories, Japan)
Jeong Hye Han (Cheongju National University of Education, Korea)
Chung-Ming Huang (National Cheng Kung University, Taiwan)
Tetsuo Ideguchi (Aichi Prefectural University, Japan)
Fumiyuki Iizuka (Fujitsu Laboratories, Japan)
Akino Inoue (Matsushita Electric Industrial, Japan)
Masugi Inoue (National Institute of Information and CommunicationsTechnology, Japan)
Susumu Ishihara (Shizuoka University, Japan)
Masahiro Ishiyama (Toshiba Corporation, Japan)
Tomoko Itao (NTT, Japan)
Shuichi Karino (NEC, Japan)
Nobuo Kawaguchi (Nagoya University, Japan)
Dong Yoon Kim (Ajou University, Korea)
Cheeha Kim (Pohang University of Science and Technology, Korea)
Kane Kim (University of California at Irvine, USA)
 Gen Kitagata (Tohoku University, Japan)
Peter Langendoerfer (IHP Microelectronics, Germany)
Mitsuji Matshumoto(Waseda University, Japan)
Masateru Minami (Shibaura Institute of Technology, Japan)
Akihiko Mizutani (IBM Japan, Japan)
Eigo Mori (Nokia Japan, Japan)
Hiroyuki Morikawa (University of Tokyo, Japan)
Yasuto Nakanishi (Tokyo University of Agriculture and Technology,  Japan)
Junya Nakata  (Japan Advanced Institute of Science and Technology, Japan$B!K(B
Masahiro Nishi (Hiroshima City University, Japan)
Akiyoshi Ogawa (Vodafone, Japan)
Ken Ohta (NTT DoCoMo, Japan)
Minoru Okada (Nara Institute of Science and Technology, Japan)
Kouji Okamura (Kyushu University, Japan)
Ryouji Ono (Mitsubishi Electric, Japan)
Yuko Onoe (NTT DoCoMo, Japan)
Antonio Pescape (University of Napoli, Italy)
Keizo Saisho (Kagawa University, Japan)
Ichiro Satoh (National Institute of Informatics, Japan)
Winston Seah (Institute for Infocomm Research, Singapore)
Hiroshi Shigeno (Keio University, Japan)
Akio Shinohara (NTT, Japan)
Biplab Sikdar (Rensselaer Polytechnic Institute, USA)
Tatsuya Suda (University of California at Irvine$B!$(BUSA)
Shinta Sugimoto (Nippon Ericsson, Japan)
Keisuke Suwa (Musashi Institute of Technology, Japan)
Kastumi Takahashi (NTT, Japan)
 Osamu Takahashi (Future University-Hakodate, Japan)
Kazunori Takashio (Keio University, Japan)
Takamichi Tateoka (University of Electro-Communications, Japan)
Chai-Keong Toh (Queen Mary University of London, UK)
Msahiko Tsukamoto (Kobe University, Japan)
Hirozumi Yamaguchi (Osaka University, Japan)
Hirofumi Yamaki (Kyoto University, Japan)
Miki Yamamoto (Osaka University, Japan)
Nagatsugu Yamanouchi (Toho University, Japan)
Masashi Yano (Hitachi Ltd., Japan)
Takashi Yoshino (Wakayama University, Japan)
 --=_alternative 002A245B49256F42_=-- --===============2010879994== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2010879994==-- From manet-bounces@ietf.org Thu Nov 4 05:32:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06727 for ; Thu, 4 Nov 2004 05:32:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPfAN-0008WJ-Fu for manet-web-archive@ietf.org; Thu, 04 Nov 2004 05:48:32 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPeoH-0000Zj-GG; Thu, 04 Nov 2004 05:25:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPeYL-0006lu-3Z for manet@megatron.ietf.org; Thu, 04 Nov 2004 05:09:13 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05027 for ; Thu, 4 Nov 2004 05:09:10 -0500 (EST) Received: from web25203.mail.ukl.yahoo.com ([217.12.10.63]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CPenm-00080B-FN for manet@ietf.org; Thu, 04 Nov 2004 05:25:13 -0500 Received: (qmail 85969 invoked by uid 60001); 4 Nov 2004 10:08:37 -0000 Message-ID: <20041104100837.85967.qmail@web25203.mail.ukl.yahoo.com> Received: from [194.145.62.45] by web25203.mail.ukl.yahoo.com via HTTP; Thu, 04 Nov 2004 10:08:37 GMT Date: Thu, 4 Nov 2004 10:08:37 +0000 (GMT) From: =?iso-8859-1?q?V=EDtor=20Jesus?= To: ns-users@ISI.EDU, manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA05027 Subject: [manet] DSR: only getting 1 route out of 2 possible X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: quoted-printable Hi all, I have this very simple script (ns-2.27) with a fixed (nodes don't move) adhoc running DSR. Imagine source and destination, with two possible routes (2 branches). The only difference is that one branch has one more hop. When I look for RREP, I get only one route (shortest). The only way I get the 2nd one, is by forcing some traffic (ftp) in the inner nodes of the non-used branch. Even so, if I stop traffic, soon the route is taken out of the cache. I understand DSR using the sortest one but I was expecting to see the alternate one. Has anyone a simple explanation for this? Thanks in advance. --V=EDtor =09 =09 =09 ___________________________________________________________ALL-NEW Yahoo!= Messenger - all new features - even more fun! http://uk.messenger.yahoo.= com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 4 08:42:11 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20124 for ; Thu, 4 Nov 2004 08:42:11 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPi80-0004Et-7b for manet-web-archive@ietf.org; Thu, 04 Nov 2004 08:58:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPhoP-0001j2-Vz; Thu, 04 Nov 2004 08:38:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPhlM-0000fV-LH for manet@megatron.ietf.org; Thu, 04 Nov 2004 08:34:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19413 for ; Thu, 4 Nov 2004 08:34:51 -0500 (EST) Received: from web60006.mail.yahoo.com ([216.109.116.229]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CPi0q-00043D-M9 for manet@ietf.org; Thu, 04 Nov 2004 08:50:56 -0500 Message-ID: <20041104133418.7064.qmail@web60006.mail.yahoo.com> Received: from [202.141.142.23] by web60006.mail.yahoo.com via HTTP; Thu, 04 Nov 2004 05:34:17 PST Date: Thu, 4 Nov 2004 05:34:17 -0800 (PST) From: Shahriar Shamil Uulu To: manet@ietf.org, ns-users@ISI.EDU MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Subject: [manet] Where i can get ad-hoc secure routing protocols source codes X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1654323355==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa --===============1654323355== Content-Type: multipart/alternative; boundary="0-978546527-1099575257=:6165" --0-978546527-1099575257=:6165 Content-Type: text/plain; charset=us-ascii Dear Users, I would like to know from where i can get the source codes of ad hoc security routing protocols like(i.e. Security aware ad hoc routing, SRP, ARAN,Watchdog and pathrate,ARIADNE,SAODV, SPRP) implemented on any open source freely available network simulator . I am doing analysis of performance on existing security routing protocols, so if you have some i idea or you have a source code please let me know about that. Any help will be apperciated. Thank you. --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com/a --0-978546527-1099575257=:6165 Content-Type: text/html; charset=us-ascii
Dear Users,
I would like to know from where i can get the source codes of ad hoc
security routing protocols like(i.e. Security aware ad hoc routing, SRP,
ARAN,Watchdog and pathrate,ARIADNE,SAODV, SPRP) implemented on any
open source freely available network simulator . I am doing analysis of
performance on existing security routing protocols, so if you have some i
idea  or you have a source code please let me know about that.
Any help will be apperciated.
Thank you.

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com; Thu, 4 Nov 2004 10:32:12 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPjqR-000745-Rf for manet-web-archive@ietf.org; Thu, 04 Nov 2004 10:48:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPjS3-0004wG-FU; Thu, 04 Nov 2004 10:23:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPjCc-0005yG-NZ for manet@megatron.ietf.org; Thu, 04 Nov 2004 10:07:08 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27793 for ; Thu, 4 Nov 2004 10:07:02 -0500 (EST) Received: from netopia.knu.ac.kr ([155.230.90.33] helo=localhost.localdomain) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPjS7-0006P7-QK for manet@ietf.org; Thu, 04 Nov 2004 10:23:08 -0500 Received: from netopiahm (mari.knu.ac.kr [155.230.90.188]) (authenticated) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id iA4FYM421729 for ; Fri, 5 Nov 2004 00:34:22 +0900 Message-ID: <000801c4c27f$eceff340$bc5ae69b@netopiahm> From: "Jae-Min Son" To: References: <200411031739.iA3HdQ415425@localhost.localdomain> Date: Fri, 5 Nov 2004 00:06:56 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea Content-Transfer-Encoding: 7bit Subject: [manet] [Help] Size of control packet in senseor netwokr X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 7bit Dear All, I have a question. I wish I know the size of "Control Packet" in sensor network. Thank you for reading.. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 4 11:39:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07871 for ; Thu, 4 Nov 2004 11:39:59 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPku5-0000Fj-Tn for manet-web-archive@ietf.org; Thu, 04 Nov 2004 11:56:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPkWj-0003hr-9i; Thu, 04 Nov 2004 11:31:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPkO0-00023j-0a for manet@megatron.ietf.org; Thu, 04 Nov 2004 11:22:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06359 for ; Thu, 4 Nov 2004 11:22:54 -0500 (EST) Received: from netopia.knu.ac.kr ([155.230.90.33] helo=localhost.localdomain) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPkdY-0008Iu-Ce for manet@ietf.org; Thu, 04 Nov 2004 11:39:01 -0500 Received: from netopiahm (mari.knu.ac.kr [155.230.90.188]) (authenticated) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id iA4GoH422069 for ; Fri, 5 Nov 2004 01:50:17 +0900 Message-ID: <000e01c4c28a$86374120$bc5ae69b@netopiahm> From: "Jae-Min Son" To: Date: Fri, 5 Nov 2004 01:22:48 +0900 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.5 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Subject: [manet] Control Packet Size in Sensor Network X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0272793515==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 This is a multi-part message in MIME format. --===============0272793515== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C4C2D5.F5E33FB0" This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C4C2D5.F5E33FB0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable Dear All, I have a question. I wish I know the size of "Control Packet" in sensor network. Thank you for reading.. ------=_NextPart_000_000B_01C4C2D5.F5E33FB0 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: quoted-printable
Dear All,

I have a question.
I wish I = know the=20 size of "Control Packet" in sensor network.

Thank you for=20 reading..
------=_NextPart_000_000B_01C4C2D5.F5E33FB0-- --===============0272793515== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0272793515==-- From manet-bounces@ietf.org Thu Nov 4 11:50:17 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09064 for ; Thu, 4 Nov 2004 11:50:17 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPl43-0000ab-Ag for manet-web-archive@ietf.org; Thu, 04 Nov 2004 12:06:24 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPkgi-0001q8-OZ; Thu, 04 Nov 2004 11:42:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPkZx-0007dp-4H for manet@megatron.ietf.org; Thu, 04 Nov 2004 11:35:17 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07456 for ; Thu, 4 Nov 2004 11:35:14 -0500 (EST) Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPkpV-00007q-Hy for manet@ietf.org; Thu, 04 Nov 2004 11:51:21 -0500 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.12.10+Sun/8.12.8) with SMTP id iA4GYjTQ008498 for ; Thu, 4 Nov 2004 11:34:45 -0500 (EST) Received: from [132.250.92.22] ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.0.4.64) with SMTP id M2004110411344406976 for ; Thu, 04 Nov 2004 11:34:44 -0500 Message-ID: <418A5A66.4050503@nrl.navy.mil> Date: Thu, 04 Nov 2004 11:35:50 -0500 From: Joe Macker User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Subject: [manet] Focus for next DC MANET meeting X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit The DC MANET meeting is presently Nov. 10, Wed afternoon 1300-1500. Unfortunately this got moved and now collides with NEMO. As a heads up, I am still discussing charter update details with the ADs. We should be wrapping this up soon. In meantime, here is the intended scope for the upcomging meeting. The main discussion for the upcoming meeting will be on the following routing area work items. These are intended to be proposed standard track work items - common framework for a proactive MANET protocol - common framework for a reactive MANET protocol - common framework for a simplified MANET multicast forwarding protocol Other related MANET items may need to be handled via BOF,etc exploration..or discussed more with the ADs and WG chairs. -Joe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 4 12:08:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11787 for ; Thu, 4 Nov 2004 12:08:08 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPlLK-0001DZ-Nx for manet-web-archive@ietf.org; Thu, 04 Nov 2004 12:24:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPklL-0002Sp-Fb; Thu, 04 Nov 2004 11:47:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPkdM-00013x-Um for manet@megatron.ietf.org; Thu, 04 Nov 2004 11:38:48 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07791 for ; Thu, 4 Nov 2004 11:38:46 -0500 (EST) Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPksv-0000DN-LJ for manet@ietf.org; Thu, 04 Nov 2004 11:54:53 -0500 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.12.10+Sun/8.12.8) with SMTP id iA4GcHTQ008682 for ; Thu, 4 Nov 2004 11:38:18 -0500 (EST) Received: from [132.250.92.22] ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.0.4.64) with SMTP id M2004110411381707006 for ; Thu, 04 Nov 2004 11:38:17 -0500 Message-ID: <418A5B3A.80501@nrl.navy.mil> Date: Thu, 04 Nov 2004 11:39:22 -0500 From: Joe Macker User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Content-Transfer-Encoding: 7bit Subject: [manet] Focus for next DC MANET meeting X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Content-Transfer-Encoding: 7bit > The DC MANET meeting is presently Nov. 10, Wed afternoon 1300-1500. > Unfortunately this got moved and now collides with NEMO. We may be able to resolve this conflict. Please pay attention for last minute agenda updates. -Joe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 4 15:02:49 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27780 for ; Thu, 4 Nov 2004 15:02:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPo4O-0005Py-8R for manet-web-archive@ietf.org; Thu, 04 Nov 2004 15:18:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPnhO-0008DL-IV; Thu, 04 Nov 2004 14:55:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPnY4-0006XD-00 for manet@megatron.ietf.org; Thu, 04 Nov 2004 14:45:32 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26564 for ; Thu, 4 Nov 2004 14:45:30 -0500 (EST) Received: from web13204.mail.yahoo.com ([216.136.174.189]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CPnnT-00055n-6D for manet@ietf.org; Thu, 04 Nov 2004 15:01:38 -0500 Received: (qmail 58671 invoked by uid 60001); 4 Nov 2004 19:18:09 -0000 Message-ID: <20041104191805.58639.qmail@web13204.mail.yahoo.com> Received: from [156.26.108.50] by web13204.mail.yahoo.com via HTTP; Thu, 04 Nov 2004 11:18:05 PST Date: Thu, 4 Nov 2004 11:18:05 -0800 (PST) From: sumanth sarma Subject: Re: [manet] Where i can get ad-hoc secure routing protocols source codes To: Shahriar Shamil Uulu , manet@ietf.org, ns-users@ISI.EDU In-Reply-To: <20041104133418.7064.qmail@web60006.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Hi, you can find them in monarch projects website. ss --- Shahriar Shamil Uulu wrote: > Dear Users, > I would like to know from where i can get the source > codes of ad hoc > security routing protocols like(i.e. Security aware > ad hoc routing, SRP, > ARAN,Watchdog and pathrate,ARIADNE,SAODV, SPRP) > implemented on any > open source freely available network simulator . I > am doing analysis of > performance on existing security routing protocols, > so if you have some i > idea or you have a source code please let me know > about that. > Any help will be apperciated. > Thank you. > > > > > --------------------------------- > Do you Yahoo!? > Check out the new Yahoo! Front Page. www.yahoo.com/a> _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 4 17:56:36 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18862 for ; Thu, 4 Nov 2004 17:56:36 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPqma-0001xA-Cj for manet-web-archive@ietf.org; Thu, 04 Nov 2004 18:12:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPqQZ-0000OH-EW; Thu, 04 Nov 2004 17:49:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPqCg-0004kl-KO for manet@megatron.ietf.org; Thu, 04 Nov 2004 17:35:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15977 for ; Thu, 4 Nov 2004 17:35:35 -0500 (EST) Received: from web90110.mail.scd.yahoo.com ([66.218.94.81]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CPqSH-0001Fb-2T for manet@ietf.org; Thu, 04 Nov 2004 17:51:46 -0500 Received: (qmail 12251 invoked by uid 60001); 4 Nov 2004 22:35:05 -0000 Message-ID: <20041104223505.12245.qmail@web90110.mail.scd.yahoo.com> Received: from [203.208.193.230] by web90110.mail.scd.yahoo.com via HTTP; Thu, 04 Nov 2004 14:35:05 PST Date: Thu, 4 Nov 2004 14:35:05 -0800 (PST) From: Parag Goswami To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Subject: [manet] linking Ad Hoc and WiMax ? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1897722900==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.0 (+) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 --===============1897722900== Content-Type: multipart/alternative; boundary="0-380559651-1099607705=:11178" --0-380559651-1099607705=:11178 Content-Type: text/plain; charset=us-ascii Hi friends, Well there is one query that I have relating to providing internet access to mobile nodes. The situation is like : Suppose we have setup an ad hoc network which detects a new mobile node automatically based on context information and is also auto configured. Now suppose we need to provide internet access to one of the mobile node in this system. So can we provide an internet access to this node through WiMax infrastructure ? And if not than why not and how is it possible to link this ad hoc network with the World Wide Web. Best Regards, Parag Goswami http://www.geocities.com/paragboom2k --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com/a --0-380559651-1099607705=:11178 Content-Type: text/html; charset=us-ascii
Hi friends,
Well there is one query that I have relating to providing internet access to mobile nodes.
 
The situation is like :
Suppose we have setup an ad hoc network which detects a new mobile node automatically based on context information and is also auto configured. Now suppose we need to provide internet access to one of the mobile node in this system.
So can we provide an internet access to this node through WiMax infrastructure ?
And if not than why not and how is it possible to link this ad hoc network with the World Wide Web.
 
Best Regards,
Parag Goswami

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com; Thu, 4 Nov 2004 18:44:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPrX2-0002we-AR for manet-web-archive@ietf.org; Thu, 04 Nov 2004 19:00:44 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPr5W-0007t3-5t; Thu, 04 Nov 2004 18:32:18 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPr3T-00077Z-Qs for manet@megatron.ietf.org; Thu, 04 Nov 2004 18:30:11 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22785 for ; Thu, 4 Nov 2004 18:30:08 -0500 (EST) From: angiez@cs.sfu.ca Received: from rm-rstar.sfu.ca ([142.58.120.21] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPrJ5-0002fl-JD for manet@ietf.org; Thu, 04 Nov 2004 18:46:20 -0500 Received: from cultus.sfu.ca (cultus.sfu.ca [142.58.101.5]) by rm-rstar.sfu.ca (8.12.10/8.12.5/SFU-5.0H) with ESMTP id iA4NU2O2020706 for ; Thu, 4 Nov 2004 15:30:03 -0800 (PST) Message-Id: <200411042330.iA4NU2O2020706@rm-rstar.sfu.ca> Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary X-Mailer: SFUwebmail 2.70 X-Sender: angiez@cs.sfu.ca To: manet@ietf.org MIME-Version: 1.0 Subject: [manet] How to specify the speed of a mobile node in NS2? Date: Thu, 04 Nov 2004 15:30:02 -0800 X-Virus-Scanned: by antibody.sfu.ca running antivirus scanner X-Spam-Score: 0.3 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: binary X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: angiez@cs.sfu.ca List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: binary Hi friends, I wonder if anybody know how to specify the speed and moving direction of a mobile node in NS2? Thanks in advance, Angie Zhang _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 4 20:48:20 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03518 for ; Thu, 4 Nov 2004 20:48:20 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPtSp-0005XO-Hi for manet-web-archive@ietf.org; Thu, 04 Nov 2004 21:04:31 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPt54-00062C-KV; Thu, 04 Nov 2004 20:39:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPt2U-0005Q7-Up for manet@megatron.ietf.org; Thu, 04 Nov 2004 20:37:18 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02599 for ; Thu, 4 Nov 2004 20:37:17 -0500 (EST) Received: from web50604.mail.yahoo.com ([206.190.38.91]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CPtHx-0005HS-FP for manet@ietf.org; Thu, 04 Nov 2004 20:53:28 -0500 Received: (qmail 46311 invoked by uid 60001); 5 Nov 2004 01:36:36 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=bM3f1aZzug/K5rVXvq7RC9PU4Tl3H5Tcrr3dvxmCKEQxZfuvL1jYRjvy0DmzfqbZ0wMJVlsqcxzHtkd2/IOb7JtxKprDUoylHZOwiBP2r7hJcTUErCxtr6hPA2pmKp+bFM+6AnLYiwvc3ytdcBAzVVz7Zg/uhXKcQ8VnxyvfV40= ; Message-ID: <20041105013636.46307.qmail@web50604.mail.yahoo.com> Received: from [130.74.176.55] by web50604.mail.yahoo.com via HTTP; Thu, 04 Nov 2004 17:36:36 PST Date: Thu, 4 Nov 2004 17:36:36 -0800 (PST) From: Raja Sombhotla To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Subject: [manet] Query reg. MANET simulation supporting packet voice X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0934528340==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.3 (+) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 --===============0934528340== Content-Type: multipart/alternative; boundary="0-915872625-1099618596=:45647" --0-915872625-1099618596=:45647 Content-Type: text/plain; charset=us-ascii Dear all, Can any one please tell me what is the optimum selection of call arrival rate and call duration time in the simulation of an Ad Hoc network supporting packet voice. On what factors does the selection of these parameters depend?Also what is the optimum number of nodes to be considered in the ad hoc network for such scenario? Kindly reply at your earliest. Thanks in advance. Regards, Raja. --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com/a --0-915872625-1099618596=:45647 Content-Type: text/html; charset=us-ascii
Dear all,
 
Can any one please tell me what is the optimum selection of call arrival rate and call duration time in the simulation of an Ad Hoc network supporting packet voice. On what factors does the selection of these parameters depend?Also what is the optimum number of nodes to be considered in the ad hoc network for such scenario?
 
Kindly reply at your earliest. Thanks in advance.
 
Regards,
Raja.

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com; Fri, 5 Nov 2004 03:43:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPzwC-0004tD-6v for manet-web-archive@ietf.org; Fri, 05 Nov 2004 03:59:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPzX9-0006NP-HY; Fri, 05 Nov 2004 03:33:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPzVV-00063Y-GK for manet@megatron.ietf.org; Fri, 05 Nov 2004 03:31:41 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15918 for ; Fri, 5 Nov 2004 03:31:39 -0500 (EST) Received: from plinius.intec.ugent.be ([157.193.122.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPzl9-0004jc-01 for manet@ietf.org; Fri, 05 Nov 2004 03:47:54 -0500 Received: from localhost (localhost [127.0.0.1]) by plinius.intec.ugent.be (Postfix) with ESMTP id 2CD92BD20 for ; Fri, 5 Nov 2004 09:31:33 +0100 (CET) Received: from [157.193.122.223] (martialis.intec.ugent.be [157.193.122.223]) by plinius.intec.ugent.be (Postfix) with ESMTP id A7908BD57 for ; Fri, 5 Nov 2004 09:31:32 +0100 (CET) Message-ID: <418B3A49.8000600@intec.ugent.be> Date: Fri, 05 Nov 2004 09:31:05 +0100 From: Gerry Holderbeke User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS snapshot-20020222 X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7bit Subject: [manet] Glomosim in real-time X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7bit Hi Everyone, Does anyone of you has any experience in making discrete-event simulators, for example Glomosim or others, run in real time ? Any information is welcome ! Thanks in advance, Gerry INTEC, Information Technology University of Ghent Belgium _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 05:07:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24445 for ; Fri, 5 Nov 2004 05:07:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ1GC-0006r0-FQ for manet-web-archive@ietf.org; Fri, 05 Nov 2004 05:24:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ0Sc-0005ui-VJ; Fri, 05 Nov 2004 04:32:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ0RJ-0005el-1h for manet@megatron.ietf.org; Fri, 05 Nov 2004 04:31:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19868 for ; Fri, 5 Nov 2004 04:31:22 -0500 (EST) Received: from smtp8.clb.oleane.net ([213.56.31.28]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ0h0-0005sz-Mh for manet@ietf.org; Fri, 05 Nov 2004 04:47:39 -0500 Received: from Pavillonquatre (upperside.rain.fr [194.206.151.59] (may be forged)) by smtp8.clb.oleane.net with ESMTP id iA59UnMm022241 for ; Fri, 5 Nov 2004 10:30:49 +0100 Message-Id: <200411050930.iA59UnMm022241@smtp8.clb.oleane.net> From: "Gunther Palmer" To: Date: Fri, 5 Nov 2004 10:30:46 +0100 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTDGiEacf2JhXFESPO3rWWIFY7gfg== X-Spam-Score: 0.1 (/) X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f Subject: [manet] WiMAX Summit: Call for proposals X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2042190683==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 2a76bcd37b1c8a21336eb0a1ea6bbf48 This is a multi-part message in MIME format. --===============2042190683== Content-Type: multipart/alternative; boundary="----=_NextPart_000_00F2_01C4C322.836427E0" This is a multi-part message in MIME format. ------=_NextPart_000_00F2_01C4C322.836427E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit . What is the business model for WiMAX? . What do we learn from earlier deployments? . What about the future extensions of the standard? . How is addressed the interoperability challenge? These questions, among others, will be addressed during the second edition of the WiMAX Summit, next April 5-8 2005, by distinguished experts and key players in the field. The call for proposal dead line has been extended to November 30. Details at: http://www.upperside.fr/wimax05/wimax2005intro.htm ------=_NextPart_000_00F2_01C4C322.836427E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

• = What is the business model for WiMAX?
• = What do we learn from earlier deployments?
• = What about the future extensions of the standard?
• = How is addressed the interoperability challenge?

These questions, among others, will be addressed during the second = edition of the WiMAX Summit, next April 5-8 2005, by distinguished = experts and key players in the field.

 

The call for proposal dead line has been = extended to November 30.

 

Details at:

http://www.upperside.fr/wimax05/wimax2005intro.htm

 

------=_NextPart_000_00F2_01C4C322.836427E0-- --===============2042190683== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2042190683==-- From manet-bounces@ietf.org Fri Nov 5 05:22:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26407 for ; Fri, 5 Nov 2004 05:22:43 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ1Uh-0007Mt-GE for manet-web-archive@ietf.org; Fri, 05 Nov 2004 05:39:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ17n-00048X-PH; Fri, 05 Nov 2004 05:15:20 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ0Xj-0006aE-9Z for manet@megatron.ietf.org; Fri, 05 Nov 2004 04:38:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20510 for ; Fri, 5 Nov 2004 04:37:46 -0500 (EST) Received: from smtp1.bae.co.uk ([20.133.0.6]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ0nB-000613-Gn for manet@ietf.org; Fri, 05 Nov 2004 04:54:02 -0500 Received: from ngbaux (ngbaux.msd.bae.co.uk [141.245.68.234]) by smtp1.bae.co.uk (Switch-2.2.8/Switch-2.2.8) with ESMTP id iA59b6U11647 for ; Fri, 5 Nov 2004 09:37:06 GMT Received: from glkas0106.GREENLNK.NET ([141.245.68.243]) by ngbaux.net.bae.co.uk (PMDF V5.2-33 #44998) with ESMTP id <0I6P008FU9C5YL@ngbaux.net.bae.co.uk> for manet@ietf.org; Fri, 5 Nov 2004 09:36:05 +0000 (GMT) Received: from glkms0001.GREENLNK.NET ([10.15.184.1]) by glkas0106.GREENLNK.NET with InterScan Messaging Security Suite; Fri, 05 Nov 2004 09:37:07 +0000 Received: from glkms0008.GREENLNK.NET ([10.15.184.8]) by glkms0001.GREENLNK.NET with Microsoft SMTPSVC(5.0.2195.5329); Fri, 05 Nov 2004 09:37:07 +0000 Date: Fri, 05 Nov 2004 09:37:06 +0000 From: "Dearlove, Christopher (UK)" Subject: RE: [manet] Focus for next DC MANET meeting To: manet@ietf.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6556.0 Content-type: text/plain; charset="iso-8859-1" Content-transfer-encoding: quoted-printable Thread-Topic: [manet] Focus for next DC MANET meeting Thread-Index: AcTCkNd5oWZ24HPjQzOwjVrqd8aOXAAii6jQ content-class: urn:content-classes:message X-OriginalArrivalTime: 05 Nov 2004 09:37:07.0335 (UTC) FILETIME=[0416C170:01C4C31B] X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: quoted-printable Cc: Joe Macker X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: quoted-printable > We may be able to resolve this conflict. Please pay attention=0D > for last minute agenda updates. Please don't change the day - some of us have made plans accordingly. (Selfishly, I could handle a change to Tuesday, but not Thursday, but I presume others will be the other way round.) =0D ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 06:53:14 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03796 for ; Fri, 5 Nov 2004 06:53:13 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ2uE-0000tx-Nm for manet-web-archive@ietf.org; Fri, 05 Nov 2004 07:09:32 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ2cq-0008Lt-Tc; Fri, 05 Nov 2004 06:51:28 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ2YF-0007NJ-KU for manet@megatron.ietf.org; Fri, 05 Nov 2004 06:46:43 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03331 for ; Fri, 5 Nov 2004 06:46:40 -0500 (EST) Received: from web25203.mail.ukl.yahoo.com ([217.12.10.63]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CQ2nn-0000ll-Jj for manet@ietf.org; Fri, 05 Nov 2004 07:02:59 -0500 Received: (qmail 5232 invoked by uid 60001); 5 Nov 2004 11:46:00 -0000 Message-ID: <20041105114600.5224.qmail@web25203.mail.ukl.yahoo.com> Received: from [194.145.62.46] by web25203.mail.ukl.yahoo.com via HTTP; Fri, 05 Nov 2004 11:46:00 GMT Date: Fri, 5 Nov 2004 11:46:00 +0000 (GMT) From: =?iso-8859-1?q?V=EDtor=20Jesus?= To: roneel z , ns-users@ISI.EDU, manet@ietf.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Spam-Score: 0.7 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA03331 Subject: [manet] RE: [ns] DSR: only getting 1 route out of 2 possible X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.7 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Content-Transfer-Encoding: quoted-printable Thanks for your help but I didn't state my problem as clear as I should. The problem is not why DSR chooses which route. It is why the 2nd route doesn't appear via RREP. Anyway, I solved it, though I still have some doubts on exactly what happened. But it was related to the distance between the nodes (some MAC effects I was not counting on when placing the nodes). Thanks again, --v=EDtor --- roneel z wrote:=20 > You answered your question. >=20 > "I understand DSR using the shortest one". >=20 > Try sending more data from your source than the link > from your intermediate=20 > node to the destination could handle. That way it > might opt to use alternate=20 > route. >=20 > Best of luck >=20 > _________________________________________________________________ > Express yourself instantly with MSN Messenger! > Download today - it's FREE!=20 > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ >=20 > =20 =09 ___________________________________________________________=20 How much free photo storage do you get? Store your holiday=20 snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 08:31:39 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11904 for ; Fri, 5 Nov 2004 08:31:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ4RZ-00037f-CX for manet-web-archive@ietf.org; Fri, 05 Nov 2004 08:47:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ45u-0006A1-FS; Fri, 05 Nov 2004 08:25:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ423-0005Yg-Bm for manet@megatron.ietf.org; Fri, 05 Nov 2004 08:21:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11017 for ; Fri, 5 Nov 2004 08:21:33 -0500 (EST) Received: from main.gmane.org ([80.91.229.2]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ4Ha-0002sx-6W for manet@ietf.org; Fri, 05 Nov 2004 08:37:50 -0500 Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CQ41n-0001eP-00 for ; Fri, 05 Nov 2004 14:21:19 +0100 Received: from p50883011.dip0.t-ipconnect.de ([80.136.48.17]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 05 Nov 2004 14:21:19 +0100 Received: from news+200406 by p50883011.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 05 Nov 2004 14:21:19 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: manet@ietf.org From: Spiro Trikaliotis Date: Fri, 5 Nov 2004 13:30:24 +0100 Lines: 18 Message-ID: References: <418B3A49.8000600@intec.ugent.be> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: p50883011.dip0.t-ipconnect.de User-Agent: slrn/0.9.8.1 (Debian) X-Spam-Score: 1.1 (+) X-Scan-Signature: d6b246023072368de71562c0ab503126 Subject: [manet] Re: Glomosim in real-time X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Hello, Gerry Holderbeke wrote: > Does anyone of you has any experience in making discrete-event > simulators, for example Glomosim or others, run in real time ? Any > information is welcome ! For ns2, you can find an implementation at http://www-ivs.cs.uni-magdeburg.de/EuK/forschung/projekte/nse/index.shtml HTH, Spiro. -- Spiro R. Trikaliotis University of Magdeburg, IVS.EUK, P.O.Box 4120, 39016 Magdeburg, Germany _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 10:36:31 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22052 for ; Fri, 5 Nov 2004 10:36:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ6OQ-0005hC-OY for manet-web-archive@ietf.org; Fri, 05 Nov 2004 10:52:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ63C-0007T2-Lx; Fri, 05 Nov 2004 10:30:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ61H-0006tH-Lm for manet@megatron.ietf.org; Fri, 05 Nov 2004 10:28:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21443 for ; Fri, 5 Nov 2004 10:28:53 -0500 (EST) Received: from mail.cs.umn.edu ([128.101.35.202] ident=postfix) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ6H2-0005XG-CD for manet@ietf.org; Fri, 05 Nov 2004 10:45:12 -0500 Received: from localhost (localhost [127.0.0.1]) by augustus.cs.umn.edu (Postfix) with ESMTP id CC3C35C39F; Fri, 5 Nov 2004 09:28:46 -0600 (CST) Received: from mail.cs.umn.edu ([127.0.0.1]) by localhost (augustus [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 13071-01-10; Fri, 5 Nov 2004 09:28:45 -0600 (CST) Received: from paulnb (fw-dtc.cs.umn.edu [128.101.189.210]) by mail.cs.umn.edu (Postfix) with SMTP id 592425C395; Fri, 5 Nov 2004 09:28:45 -0600 (CST) Message-ID: <002301c4c3a8$90ba3160$c88310ac@paulnb> From: "Jaehoon Jeong" To: "Joe Macker" , References: <418A5A66.4050503@nrl.navy.mil> Subject: Re: [manet] Focus for next DC MANET meeting Date: Fri, 5 Nov 2004 21:30:22 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at cs.umn.edu X-Spam-Score: 4.1 (++++) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Cc: autonet , ??? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1558431791==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 4.1 (++++) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 --===============1558431791== Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 SGkgSm9lLA0KDQpBcyB5b3Uga25vdywgbWFueSBwZW9wbGUgd2FudCBNQU5FVCBhZGRyZXNzIGF1 dG9jb25mIHRvIGJlIHN0YW5kYXJkaXplZCBpbiB0aGUgSUVURi4NCkVUUkkgaGFzIGFscmVhZHkg aW1wbGVtZW50ZWQgTUFORVQgYWRkcmVzcyBhdXRvY29uZiBiYXNlZCBvbiBteSBkcmFmdDoNCmh0 dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWplb25nLW1hbmV0LWFvZHYt YWRkci1hdXRvY29uZi0wMS50eHQNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRz L2RyYWZ0LWplb25nLWFkaG9jLWlwLWFkZHItYXV0b2NvbmYtMDMudHh0DQpodHRwOi8vd3d3Lmll dGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1qZW9uZy1tYW5ldC1hZGRyLWF1dG9jb25mLXJl cXRzLTAzLnR4dA0KDQpBbHNvLCByZWNlbnRseSwgUHJvZi4gS2lsaWFuIFdlbmlnZXIgYW5ub3Vu Y2VkIHRoZSBpbXBsZW1lbnRhdGlvbiBvZiBQYXNzaXZlIERBRDoNCmh0dHA6Ly9wYWNtYW4tYXV0 b2NvbmYuc291cmNlZm9yZ2UubmV0DQpodHRwOi8vc291cmNlZm9yZ2UubmV0L3Byb2plY3RzL3Bh Y21hbi1hdXRvY29uZi8NCg0KU2luY2UgTUFORVQgYWRkcmVzc2luZyBpcyBwcmVyZXF1aXNpdGUg Zm9yIE1BTkVUIHJvdXRpbmcsIEkgdGhpbmsgaXQgY2FuIGJlIGhhbmRsZWQgYXQgb3VyIE1BTkVU IHdnLg0KRmlyc3QsIHdlIGNhbiBtYWtlIHRoZSByZXF1aXJlbWVudHMgZm9yIE1BTkVUIGFkZHJl c3MgYXV0b2NvbmYgYXMgSW5mb3JtYXRpb25hbCBSRkMuDQpBZnRlciB0aGF0LCBpZiBhIHNpbXBs ZSBNQU5FVCBhdXRvY29uZiBzY2hlbWUgZ2V0cyBhIGNvbnNlbnN1cywgd2UgY2FuIG1ha2UgaXQg YXMgYW5vdGhlciBJbmZvcm1hdGlvbiBSRkMuDQoNCkkgd291bGQgbGlrZSB0byBhc2sgeW91IHRv IGRpc2N1c3MgaXQgd2l0aCBBRHMuDQoNClRoYW5rcy4NCg0KUmVnYXJkcywNCg0KUGF1bA0KDQo9 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT0NCkphZWhvb24gUGF1bCBKZW9uZywNClBoLkQuIFN0dWRlbnQsDQpEZXBh cnRtZW50IG9mIENvbXB1dGVyIFNjaWVuY2UNClVuaXZlcnNpdHkgb2YgTWlubmVzb3RhIGF0IFR3 aW4gQ2l0aWVzDQpFbWFpbDogamplb25nQGNzLnVtbi5lZHUNCkhvbWVwYWdlOiBodHRwOi8vd3d3 LmNzLnVtbi5lZHUvfmpqZW9uZy8NClBob25lOiArMS02MTItNjI0LTYyMDgoT2ZmaWNlKSwgNjUx LTU4Ny03Nzc0KENlbGwpDQoNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206 ICJKb2UgTWFja2VyIiA8am9zZXBoLm1hY2tlckBucmwubmF2eS5taWw+DQpUbzogPG1hbmV0QGll dGYub3JnPg0KU2VudDogVGh1cnNkYXksIE5vdmVtYmVyIDA0LCAyMDA0IDExOjM1IEFNDQpTdWJq ZWN0OiBbbWFuZXRdIEZvY3VzIGZvciBuZXh0IERDIE1BTkVUIG1lZXRpbmcNCg0KDQo+IFRoZSBE QyBNQU5FVCBtZWV0aW5nIGlzIHByZXNlbnRseSBOb3YuIDEwLCBXZWQgYWZ0ZXJub29uIDEzMDAt MTUwMC4NCj4gVW5mb3J0dW5hdGVseSB0aGlzIGdvdCBtb3ZlZCBhbmQgbm93IGNvbGxpZGVzIHdp dGggTkVNTy4NCj4gDQo+IEFzIGEgaGVhZHMgdXAsIEkgYW0gc3RpbGwgZGlzY3Vzc2luZyBjaGFy dGVyIHVwZGF0ZSBkZXRhaWxzIHdpdGggdGhlIEFEcy4NCj4gV2Ugc2hvdWxkIGJlIHdyYXBwaW5n IHRoaXMgdXAgc29vbi4gSW4gbWVhbnRpbWUsIGhlcmUgaXMgdGhlIGludGVuZGVkIHNjb3BlIGZv ciB0aGUgdXBjb21naW5nIG1lZXRpbmcuDQo+IA0KPiBUaGUgbWFpbiBkaXNjdXNzaW9uIGZvciB0 aGUgdXBjb21pbmcgbWVldGluZyB3aWxsIGJlIG9uIHRoZSBmb2xsb3dpbmcgcm91dGluZyBhcmVh IHdvcmsgaXRlbXMuDQo+IFRoZXNlIGFyZSBpbnRlbmRlZCB0byBiZSBwcm9wb3NlZCBzdGFuZGFy ZCB0cmFjayB3b3JrIGl0ZW1zDQo+IA0KPiAtIGNvbW1vbiBmcmFtZXdvcmsgZm9yIGEgcHJvYWN0 aXZlIE1BTkVUIHByb3RvY29sDQo+IC0gY29tbW9uIGZyYW1ld29yayBmb3IgYSByZWFjdGl2ZSBN QU5FVCBwcm90b2NvbA0KPiAtIGNvbW1vbiBmcmFtZXdvcmsgZm9yIGEgc2ltcGxpZmllZCBNQU5F VCBtdWx0aWNhc3QgZm9yd2FyZGluZyBwcm90b2NvbA0KPiANCj4gT3RoZXIgcmVsYXRlZCBNQU5F VCBpdGVtcyBtYXkgbmVlZCB0byBiZSBoYW5kbGVkIHZpYSBCT0YsZXRjIGV4cGxvcmF0aW9uLi5v ciBkaXNjdXNzZWQgbW9yZSB3aXRoIHRoZSBBRHMgYW5kIFdHIGNoYWlycy4NCj4gDQo+IC1Kb2UN Cj4gDQo+IA0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Xw0KPiBtYW5ldCBtYWlsaW5nIGxpc3QNCj4gbWFuZXRAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cx LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWFuZXQNCj4gDQo+IA== --===============1558431791== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1558431791==-- From manet-bounces@ietf.org Fri Nov 5 10:55:56 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23457 for ; Fri, 5 Nov 2004 10:55:56 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ6hE-00067z-02 for manet-web-archive@ietf.org; Fri, 05 Nov 2004 11:12:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ6NX-0007eo-0x; Fri, 05 Nov 2004 10:51:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ6ND-0007Sv-Nn for manet@megatron.ietf.org; Fri, 05 Nov 2004 10:51:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23147 for ; Fri, 5 Nov 2004 10:51:33 -0500 (EST) Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CQ6cv-00062Z-CE for manet@ietf.org; Fri, 05 Nov 2004 11:07:52 -0500 Received: (qmail 20341 invoked for bounce); 5 Nov 2004 15:51:33 -0000 Received: from unknown (HELO dpt-info.u-strasbg.fr) (jelger@unknown) by unknown with RC4-MD5 encrypted SMTP; 5 Nov 2004 15:51:33 -0000 Message-ID: <418BA0C8.3010309@dpt-info.u-strasbg.fr> Date: Fri, 05 Nov 2004 16:48:24 +0100 From: Christophe Jelger User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031030 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jaehoon Jeong Subject: Re: [manet] Focus for next DC MANET meeting References: <418A5A66.4050503@nrl.navy.mil> <002301c4c3a8$90ba3160$c88310ac@paulnb> In-Reply-To: <002301c4c3a8$90ba3160$c88310ac@paulnb> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org, Joe Macker , autonet , ??? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: 7bit Hello, There is also our implementations based on prefix continuity for ad hoc networks connected to the Internet via gateway nodes. http://www-r2.u-strasbg.fr/~frey/safari/autoconf.html Regards, Christophe Jaehoon Jeong wrote: >Hi Joe, > >As you know, many people want MANET address autoconf to be standardized in the IETF. >ETRI has already implemented MANET address autoconf based on my draft: >http://www.ietf.org/internet-drafts/draft-jeong-manet-aodv-addr-autoconf-01.txt >http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-03.txt >http://www.ietf.org/internet-drafts/draft-jeong-manet-addr-autoconf-reqts-03.txt > >Also, recently, Prof. Kilian Weniger announced the implementation of Passive DAD: >http://pacman-autoconf.sourceforge.net >http://sourceforge.net/projects/pacman-autoconf/ > >Since MANET addressing is prerequisite for MANET routing, I think it can be handled at our MANET wg. >First, we can make the requirements for MANET address autoconf as Informational RFC. >After that, if a simple MANET autoconf scheme gets a consensus, we can make it as another Information RFC. > >I would like to ask you to discuss it with ADs. > >Thanks. > >Regards, > >Paul > >======================================================================== >Jaehoon Paul Jeong, >Ph.D. Student, >Department of Computer Science >University of Minnesota at Twin Cities >Email: jjeong@cs.umn.edu >Homepage: http://www.cs.umn.edu/~jjeong/ >Phone: +1-612-624-6208(Office), 651-587-7774(Cell) > > >----- Original Message ----- >From: "Joe Macker" >To: >Sent: Thursday, November 04, 2004 11:35 AM >Subject: [manet] Focus for next DC MANET meeting > > > > >>The DC MANET meeting is presently Nov. 10, Wed afternoon 1300-1500. >>Unfortunately this got moved and now collides with NEMO. >> >>As a heads up, I am still discussing charter update details with the ADs. >>We should be wrapping this up soon. In meantime, here is the intended scope for the upcomging meeting. >> >>The main discussion for the upcoming meeting will be on the following routing area work items. >>These are intended to be proposed standard track work items >> >>- common framework for a proactive MANET protocol >>- common framework for a reactive MANET protocol >>- common framework for a simplified MANET multicast forwarding protocol >> >>Other related MANET items may need to be handled via BOF,etc exploration..or discussed more with the ADs and WG chairs. >> >>-Joe >> >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 11:00:34 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23795 for ; Fri, 5 Nov 2004 11:00:34 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ6li-0006Eb-1k for manet-web-archive@ietf.org; Fri, 05 Nov 2004 11:16:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ6UM-0000Xs-3f; Fri, 05 Nov 2004 10:58:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ6O7-0007g4-3T for manet@megatron.ietf.org; Fri, 05 Nov 2004 10:52:31 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23205 for ; Fri, 5 Nov 2004 10:52:28 -0500 (EST) Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CQ6ds-00064C-9y for manet@ietf.org; Fri, 05 Nov 2004 11:08:48 -0500 Received: (qmail 20371 invoked for bounce); 5 Nov 2004 15:52:40 -0000 Received: from unknown (HELO dpt-info.u-strasbg.fr) (jelger@unknown) by unknown with RC4-MD5 encrypted SMTP; 5 Nov 2004 15:52:40 -0000 Message-ID: <418BA10A.3050409@dpt-info.u-strasbg.fr> Date: Fri, 05 Nov 2004 16:49:30 +0100 From: Christophe Jelger User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031030 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jaehoon Jeong Subject: Re: [manet] Focus for next DC MANET meeting References: <418A5A66.4050503@nrl.navy.mil> <002301c4c3a8$90ba3160$c88310ac@paulnb> In-Reply-To: <002301c4c3a8$90ba3160$c88310ac@paulnb> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org, Joe Macker , autonet , ??? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: 7bit Hello, There is also our implementations based on prefix continuity for ad hoc networks connected to the Internet via gateway nodes. http://www-r2.u-strasbg.fr/~frey/safari/autoconf.html Regards, Christophe Jaehoon Jeong wrote: >Hi Joe, > >As you know, many people want MANET address autoconf to be standardized in the IETF. >ETRI has already implemented MANET address autoconf based on my draft: >http://www.ietf.org/internet-drafts/draft-jeong-manet-aodv-addr-autoconf-01.txt >http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-03.txt >http://www.ietf.org/internet-drafts/draft-jeong-manet-addr-autoconf-reqts-03.txt > >Also, recently, Prof. Kilian Weniger announced the implementation of Passive DAD: >http://pacman-autoconf.sourceforge.net >http://sourceforge.net/projects/pacman-autoconf/ > >Since MANET addressing is prerequisite for MANET routing, I think it can be handled at our MANET wg. >First, we can make the requirements for MANET address autoconf as Informational RFC. >After that, if a simple MANET autoconf scheme gets a consensus, we can make it as another Information RFC. > >I would like to ask you to discuss it with ADs. > >Thanks. > >Regards, > >Paul > >======================================================================== >Jaehoon Paul Jeong, >Ph.D. Student, >Department of Computer Science >University of Minnesota at Twin Cities >Email: jjeong@cs.umn.edu >Homepage: http://www.cs.umn.edu/~jjeong/ >Phone: +1-612-624-6208(Office), 651-587-7774(Cell) > > >----- Original Message ----- >From: "Joe Macker" >To: >Sent: Thursday, November 04, 2004 11:35 AM >Subject: [manet] Focus for next DC MANET meeting > > > > >>The DC MANET meeting is presently Nov. 10, Wed afternoon 1300-1500. >>Unfortunately this got moved and now collides with NEMO. >> >>As a heads up, I am still discussing charter update details with the ADs. >>We should be wrapping this up soon. In meantime, here is the intended scope for the upcomging meeting. >> >>The main discussion for the upcoming meeting will be on the following routing area work items. >>These are intended to be proposed standard track work items >> >>- common framework for a proactive MANET protocol >>- common framework for a reactive MANET protocol >>- common framework for a simplified MANET multicast forwarding protocol >> >>Other related MANET items may need to be handled via BOF,etc exploration..or discussed more with the ADs and WG chairs. >> >>-Joe >> >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 11:57:49 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28389 for ; Fri, 5 Nov 2004 11:57:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ7f6-0007Sr-Sh for manet-web-archive@ietf.org; Fri, 05 Nov 2004 12:14:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ7Gk-0000fw-FZ; Fri, 05 Nov 2004 11:48:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ7CJ-00005i-IH for manet@megatron.ietf.org; Fri, 05 Nov 2004 11:44:23 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27358 for ; Fri, 5 Nov 2004 11:44:20 -0500 (EST) Received: from dns1.tilab.com ([163.162.42.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ7S3-0007BV-Fb for manet@ietf.org; Fri, 05 Nov 2004 12:00:41 -0500 Received: from iowa2k01a.cselt.it ([163.162.242.201]) by dns1.cselt.it (PMDF V6.0-025 #38895) with ESMTP id <0I6P00M0GT1L8W@dns1.cselt.it> for manet@ietf.org; Fri, 05 Nov 2004 17:41:46 +0100 (MET) Received: from EXC01A.cselt.it ([163.162.4.198]) by iowa2k01a.cselt.it with Microsoft SMTPSVC(6.0.3790.211); Fri, 05 Nov 2004 17:45:44 +0100 Date: Fri, 05 Nov 2004 17:43:43 +0100 From: Ruffino Simone Subject: RE: [manet] New draft on connectivity scenarios and autoconfigura tion issues To: McLanahan.Stevens@gd-ais.com Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Importance: normal Priority: normal Thread-Topic: [manet] New draft on connectivity scenarios and autoconfigura tion issues Thread-Index: AcTAMxOnWILfA0eBTvezfeyEgHEpMACR+CNw Content-class: urn:content-classes:message X-OriginalArrivalTime: 05 Nov 2004 16:45:44.0000 (UTC) FILETIME=[E46A6C00:01C4C356] X-Spam-Score: 0.0 (/) X-Scan-Signature: 17bdfcaea25d1444baef0e24abc38874 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2b2ad76aced9b1d558e34a970a85c027 Content-Transfer-Encoding: quoted-printable Dear Mac Stevens, Thanks a lot for your review. A lot of useful and interesting = observations. See below for inline comments (on your comments).=20 Will you attend IETF meeting next week ? Best Regards, Simone > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf = Of > McLanahan.Stevens@gd-ais.com > Sent: luned=EC 1 novembre 2004 16.54 > To: manet@ietf.org > Subject: RE: [manet] New draft on connectivity scenarios and = autoconfigura > tion issues >=20 > First of all some comments (nothing personal of course). >=20 > Overall I think this will help to serve as an architectural starting = point, > a 10,000 foot view if you will.=20 [Ruff] Yes, it is a starting point, aimed at defining both reference = scenarios and problem statement. As a matter of fact, we don't think = that our draft is a complete problem statement, which, in our opinion, = should be addressed in a future version of the draft (or maybe in a = different one).=20 > It does need to be cleaned up from an > editorial perspective (grammar and spelling errors mostly). Since the > group probably does not want to read my spelling nitpicks, I will = leave > those in a private follow up email. Besides, I'm an engineer, not an > English professor. [Ruff] Sorry for that. Next version will be polished.... :) >=20 > Technical Discussion > -------------------- >=20 > Section 2. Node: Do we want to tie ourselves to IPv4/IPv6 as a node > definition. Perhaps IP-Based would be best here. After all, we never = know > if someone will come up with some sort of IPvWireless in the distant > future. >=20 > Section 3.2.1 Surveillance networks: I do not think the generalization > that nodes will remain stationary is a good one. Surveillance (or > preferably called Sensor networks), can have a dynamic nature to them > depending on the application. Take, for example, a gas monitoring van > (often used by gas companies) with several sensors on it. The van is = in > constant motion throughout the network. Perhaps a 3rd case should be = added > here. In addition a "Heavyweight" node scenario should probably be = added > where each node can act as a gateway/router if necessary. >=20 [Ruff] We were not aware of applications of this kind. For sure this = could bring to a new scenario, or maybe we could expand one of the = already described scenarios. > Section 4.1 I think a scenario needs to be addressed in this section = that > discusses the transient/isolated MANET issue. Take for example a MANET > that periodically comes into contact with a gateway. That MANET will > transition between an isolated MANET and a connected MANET. The = potential > for this happening in a mobile environment is high. >=20 [Ruff] From our point of view, this could be an addition to sec. 3.2 = "MANET connected to an external network". Actually, the loss of = connectivity of the gateway can be classified to the scenario addressed = in 3.2.2 "Mobile Gateways" =20 > Section 4.1.3 Volatile network scenario: What happens when the MANET = is > volatile? Let's take this case into consideration... 2 MANETs join = with > say x nodes that have the same address. The MANETs separate into two > different networks with one MANET getting several of the duplicate > addresses. Capability will have to exist in each MANET "sub-network" = to > broker network addresses. [Ruff] Maybe I don't get your point here, but I think this is an issue a = DAD mechanism must solve as soon as the two MANETs join for the first = time. If this is the case, when the 2 MANETs separate there are no = duplicate addresses. >=20 > Section 4.2.4 Multiple Gateway routing and addressing issues (first > paragraph): Isn't this issue solved by the various ad-hoc routing > protocols out there. Do we really need this to be part of a dynamic > configuration protocol? [Ruff] Yes, this is not an issue, it's a feature! For example, proactive = routing protocols already handle it. We meant to give emphasis to the = benefits this feature can bring. >=20 > Section 4.2.4 Paragraph 3 It is desirable that traffic follows the = same > path uplink and downlink within the MANET: this is because the uplink = path > towards the default gateway is guaranteed to be optimal by routing the > protocol. > The follow up statement doesn't really prove anything. Just because an > uplink path is optimal, doesn't always mean the downlink is. Take for > example mobile nodes that have different transmit power levels, = antenna > heights, etc... >=20 [Ruff] OK, we based our statement considering only hop-count metric. If = different kinds of metric are available, then you're right. > Section 4.2.9 Paragraph 2. Expand on this. More discussion on source > routing would be nice :) >=20 > Section 5 Nodes with specific functionalities: It might be good to > distribute the services across the MANET network. Or better yet, = actually > have "back-up" services. Nodes should have the capability to "jump in" = if > connectivity is lost. >=20 > Section 6. I think something needs to be considered here. There are > potential security issues that could arise (such as malicious nodes on = a > network). Perhaps a discussion on dynamic network configuration = security > would be good. >=20 [Ruff] Yes, I agree, a security consideration section could be helpful. = Let me say that a malicious node located within a MANET can do many many = other bad things, e.g. to the routing protocols...really too many to = enumerate here. >=20 >=20 > I'm sure I will get some comments on some these points (after all, the > morning coffee is only now kicking in so my mind is not fully revved = up > yet :)) but I just thought I would share some thoughts. >=20 > -Mac Stevens >=20 > --------------------------------------------- > McLanahan Stevens > Sr. Software Engineer > General Dynamics Advanced Information Systems >=20 >=20 >=20 >=20 > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]On Behalf = Of > Ruffino Simone > Sent: Monday, November 01, 2004 3:29 AM > To: manet@ietf.org > Subject: [manet] New draft on connectivity scenarios and > autoconfiguration issues >=20 >=20 > Hi to all, >=20 > a new draft was submitted as individual submission, titled > "Autoconfiguration in a MANET: connectivity scenarios and technical > issues". >=20 > Goal of the draft is to describe the scenarios, in which a MANET can = be > connected to an external network (by means of either wired of wireless > links) and to list some of the technical issues, which are related to > autoconfiguration and global connectivity, that arise in such = scenarios. >=20 >=20 > Comments welcome and appreciated ! >=20 > Thanks in advance, > Simone Ruffino >=20 >=20 > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > > > > > > Title: Autoconfiguration in a MANET: connectivity scenarios and > > technical issues > > Author(s): S. Ruffino, et al. > > Filename: draft-ruffino-manet-autoconf-scenarios-00.txt > > Pages: 26 > > Date: 2004-10-19 > > > > MANET interconnection with external networks enables a number of > > usage scenarios, but generates also a number of technical issues, > > mainly related with node autoconfiguration and global = connectivity. > > This Internet Draft aims at characterizing global connectivity > > scenarios and listing technical issues related to IP address > > autoconfiguration which are implied by such scenarios and should = be > > addressed by a generic solution. > > > > A URL for this Internet-Draft is: > > > = http://www.ietf.org/internet-drafts/draft-ruffino-manet-autoconf-scenari > os-00.txt > > Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia = S.p.A. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 send an e_mail to=20 MailAdmin@tilab.com. Thank you =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 12:34:54 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01063 for ; Fri, 5 Nov 2004 12:34:54 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ8F1-0008CY-0I for manet-web-archive@ietf.org; Fri, 05 Nov 2004 12:51:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ7rr-0000dy-EF; Fri, 05 Nov 2004 12:27:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ7Xh-00036Q-N9 for manet@megatron.ietf.org; Fri, 05 Nov 2004 12:06:29 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29160 for ; Fri, 5 Nov 2004 12:06:26 -0500 (EST) Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CQ7nS-0007eG-GO for manet@ietf.org; Fri, 05 Nov 2004 12:22:47 -0500 Received: (qmail 29274 invoked by uid 65534); 5 Nov 2004 17:05:48 -0000 Received: from unknown (EHLO 127.0.0.1) (67.176.36.236) by mail.gmx.net (mp025) with SMTP; 05 Nov 2004 18:05:48 +0100 X-Authenticated: #309278 Date: Fri, 5 Nov 2004 10:05:05 -0700 From: Daniel Henkel X-Mailer: The Bat! (v2.00.6) Business X-Priority: 3 (Normal) Message-ID: <7168728999.20041105100505@gmx.com> To: manet@ietf.org Subject: RE: [manet] Are there protocols that are like SIP or H.323 ... In-Reply-To: <1099498645.41890495e7361@webmail.colorado.edu> References: <635810552.20041103080341@gmx.com> <1099498645.41890495e7361@webmail.colorado.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Henkel List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: 7bit Chris, So far, we have only implemented clients that talk to each other directly without any lookup services or gateways in between. It would, however, be possible to have a UAS, like www.asterisk.org, running on the gateway routing call requests and calls. Regards, - Daniel. University of Colorado at Boulder http://AUGNet.colordo.edu SD> Date: Mon, 1 Nov 2004 17:30:13 -0500 SD> From: SD> Subject: RE: [manet] Are there protocols that are like SIP or H.323 SD> that couldprovide session or peer-peer sceesions in MANETS for SD> Voice SD> or Multimedia? SD> To: "'Daniel Henkel'" , SD> Message-ID: <000001c4c062$5b34c710$0600a8c0@CPQ73745201364> SD> Content-Type: text/plain; charset="iso-8859-1" SD> Greetings Daniel, SD> In your MANET architecture, do all the nodes act as Location Services, SD> Proxies, User Agent Clients (UACs) and User Agent Server (UASs)? SD> Thanks and regards, SD> Chris SD> -- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 12:40:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01681 for ; Fri, 5 Nov 2004 12:40:59 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ8Kt-0008LY-P2 for manet-web-archive@ietf.org; Fri, 05 Nov 2004 12:57:20 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ7s7-0000nK-H4; Fri, 05 Nov 2004 12:27:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ7dm-0004eC-1r for manet@megatron.ietf.org; Fri, 05 Nov 2004 12:12:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29522 for ; Fri, 5 Nov 2004 12:12:42 -0500 (EST) Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ7tU-0007mB-8z for manet@ietf.org; Fri, 05 Nov 2004 12:29:03 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id iA5GiKB25518; Fri, 5 Nov 2004 08:44:20 -0800 X-mProtect: <200411051644> Nokia Silicon Valley Messaging Protection Received: from danira-pool049160.americas.nokia.com (10.241.49.160, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdMz9LvK; Fri, 05 Nov 2004 08:44:18 PST Message-ID: <418BB44B.8010603@iprg.nokia.com> Date: Fri, 05 Nov 2004 09:11:39 -0800 From: "Charles E. Perkins" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jaehoon Jeong Subject: Re: [manet] Focus for next DC MANET meeting References: <418A5A66.4050503@nrl.navy.mil> <002301c4c3a8$90ba3160$c88310ac@paulnb> In-Reply-To: <002301c4c3a8$90ba3160$c88310ac@paulnb> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 Content-Transfer-Encoding: 7bit Hello Jaehoon, As you probably know, we also have had drafts for autoconfiguration of addresses in ad hoc networks. These drafts have not been resubmitted recently, because the working group has not had autoconfiguration on its charter. Nevertheless, the specification is good and compatible with on-demand routing protocols. If the working group decides to charter new work on this activity, I would like our previous drafts to be considered for adoption by the working group. Alternatively, it might make sense to investigate some combined approach. Regards, Charlie P. Jaehoon Jeong wrote: >Hi Joe, > >As you know, many people want MANET address autoconf to be standardized in the IETF. >ETRI has already implemented MANET address autoconf based on my draft: >http://www.ietf.org/internet-drafts/draft-jeong-manet-aodv-addr-autoconf-01.txt >http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-03.txt >http://www.ietf.org/internet-drafts/draft-jeong-manet-addr-autoconf-reqts-03.txt > >Also, recently, Prof. Kilian Weniger announced the implementation of Passive DAD: >http://pacman-autoconf.sourceforge.net >http://sourceforge.net/projects/pacman-autoconf/ > >Since MANET addressing is prerequisite for MANET routing, I think it can be handled at our MANET wg. >First, we can make the requirements for MANET address autoconf as Informational RFC. >After that, if a simple MANET autoconf scheme gets a consensus, we can make it as another Information RFC. > >I would like to ask you to discuss it with ADs. > >Thanks. > >Regards, > >Paul > >======================================================================== >Jaehoon Paul Jeong, >Ph.D. Student, >Department of Computer Science >University of Minnesota at Twin Cities >Email: jjeong@cs.umn.edu >Homepage: http://www.cs.umn.edu/~jjeong/ >Phone: +1-612-624-6208(Office), 651-587-7774(Cell) > > >----- Original Message ----- >From: "Joe Macker" >To: >Sent: Thursday, November 04, 2004 11:35 AM >Subject: [manet] Focus for next DC MANET meeting > > > > >>The DC MANET meeting is presently Nov. 10, Wed afternoon 1300-1500. >>Unfortunately this got moved and now collides with NEMO. >> >>As a heads up, I am still discussing charter update details with the ADs. >>We should be wrapping this up soon. In meantime, here is the intended scope for the upcomging meeting. >> >>The main discussion for the upcoming meeting will be on the following routing area work items. >>These are intended to be proposed standard track work items >> >>- common framework for a proactive MANET protocol >>- common framework for a reactive MANET protocol >>- common framework for a simplified MANET multicast forwarding protocol >> >>Other related MANET items may need to be handled via BOF,etc exploration..or discussed more with the ADs and WG chairs. >> >>-Joe >> >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>manet mailing list >>manet@ietf.org >>https://www1.ietf.org/mailman/listinfo/manet >> >> _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 13:05:33 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03744 for ; Fri, 5 Nov 2004 13:05:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ8ig-0000Vq-M4 for manet-web-archive@ietf.org; Fri, 05 Nov 2004 13:21:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ8NO-0007xJ-8w; Fri, 05 Nov 2004 12:59:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ8JJ-0006et-V6 for manet@megatron.ietf.org; Fri, 05 Nov 2004 12:55:41 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03018 for ; Fri, 5 Nov 2004 12:55:38 -0500 (EST) Received: from mail.cs.umn.edu ([128.101.34.202] ident=postfix) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ8Z1-0000IU-N9 for manet@ietf.org; Fri, 05 Nov 2004 13:12:00 -0500 Received: from localhost (localhost [127.0.0.1]) by augustus.cs.umn.edu (Postfix) with ESMTP id 43AF85C3A0; Fri, 5 Nov 2004 11:55:36 -0600 (CST) Received: from mail.cs.umn.edu ([127.0.0.1]) by localhost (augustus [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20878-01-8; Fri, 5 Nov 2004 11:55:34 -0600 (CST) Received: from paulnb (fw-dtc.cs.umn.edu [128.101.189.210]) by mail.cs.umn.edu (Postfix) with SMTP id A34665C359; Fri, 5 Nov 2004 11:55:34 -0600 (CST) Message-ID: <00e901c4c3bd$13340cb0$c88310ac@paulnb> From: "Jaehoon Jeong" To: "Charles E. Perkins" References: <418A5A66.4050503@nrl.navy.mil> <002301c4c3a8$90ba3160$c88310ac@paulnb> <418BB44B.8010603@iprg.nokia.com> Subject: Re: [manet] Focus for next DC MANET meeting Date: Fri, 5 Nov 2004 23:57:11 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at cs.umn.edu X-Spam-Score: 4.1 (++++) X-Scan-Signature: 25620135586de10c627e3628c432b04a Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1353147340==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 4.1 (++++) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 --===============1353147340== Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 SGkgQ2hhcmxpZSwNCg0KSWYgTUFORVQgY2hhaXJzIGRlY2lkZSB0byB3b3JrIG9uIHRoaXMgYWN0 aXZpdHksIEkgdGhpbmsgdGhhdCB5b3VyIHByZXZpb3VzIGRyYWZ0cw0KY2FuIGJlIHVzZWQgYXMg YmFzZSBkb2N1bWVudHMuDQpGb3IgZGV2ZWxvcGluZyBzcGVjaWZpYyBtYWNoYW5pc20gZHJhZnQo cyksIHdlIHNlZW0gdG8gaGF2ZSB0byByZWFjaCBhIGNvbnNlbnN1cyBvbg0KdGhlIHJlcXVpcmVt ZW50cyBvZiBNQU5FVCBhZGRyZXNzIGF1dG9jb25mLg0KSSBhcHByZWNpYXRlIHlvdXIgcHJldmlv dXMgd29yay4NCg0KVGhhbmtzLg0KDQpKYWVob29uDQoNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2Fn ZSAtLS0tLSANCkZyb206ICJDaGFybGVzIEUuIFBlcmtpbnMiIDxjaGFybGllcEBpcHJnLm5va2lh LmNvbT4NClRvOiAiSmFlaG9vbiBKZW9uZyIgPGpqZW9uZ0Bjcy51bW4uZWR1Pg0KQ2M6IDxtYW5l dEBpZXRmLm9yZz4NClNlbnQ6IEZyaWRheSwgTm92ZW1iZXIgMDUsIDIwMDQgMTI6MTEgUE0NClN1 YmplY3Q6IFJlOiBbbWFuZXRdIEZvY3VzIGZvciBuZXh0IERDIE1BTkVUIG1lZXRpbmcNCg0KDQo+ IA0KPiBIZWxsbyBKYWVob29uLA0KPiANCj4gQXMgeW91IHByb2JhYmx5IGtub3csIHdlIGFsc28g aGF2ZSBoYWQgZHJhZnRzIGZvciBhdXRvY29uZmlndXJhdGlvbg0KPiBvZiBhZGRyZXNzZXMgaW4g YWQgaG9jIG5ldHdvcmtzLiAgVGhlc2UgZHJhZnRzIGhhdmUgbm90IGJlZW4gcmVzdWJtaXR0ZWQN Cj4gcmVjZW50bHksIGJlY2F1c2UgdGhlIHdvcmtpbmcgZ3JvdXAgaGFzIG5vdCBoYWQgYXV0b2Nv bmZpZ3VyYXRpb24gb24NCj4gaXRzIGNoYXJ0ZXIuICBOZXZlcnRoZWxlc3MsIHRoZSBzcGVjaWZp Y2F0aW9uIGlzIGdvb2QgYW5kIGNvbXBhdGlibGUgd2l0aA0KPiBvbi1kZW1hbmQgcm91dGluZyBw cm90b2NvbHMuICBJZiB0aGUgd29ya2luZyBncm91cCBkZWNpZGVzIHRvIGNoYXJ0ZXINCj4gbmV3 IHdvcmsgb24gdGhpcyBhY3Rpdml0eSwgSSB3b3VsZCBsaWtlIG91ciBwcmV2aW91cyBkcmFmdHMg dG8gYmUNCj4gY29uc2lkZXJlZCBmb3IgYWRvcHRpb24gYnkgdGhlIHdvcmtpbmcgZ3JvdXAuICBB bHRlcm5hdGl2ZWx5LCBpdCBtaWdodA0KPiBtYWtlIHNlbnNlIHRvIGludmVzdGlnYXRlIHNvbWUg Y29tYmluZWQgYXBwcm9hY2guDQo+IA0KPiBSZWdhcmRzLA0KPiBDaGFybGllIFAuDQo+IA0KPiAN Cj4gSmFlaG9vbiBKZW9uZyB3cm90ZToNCj4gDQo+ID5IaSBKb2UsDQo+ID4NCj4gPkFzIHlvdSBr bm93LCBtYW55IHBlb3BsZSB3YW50IE1BTkVUIGFkZHJlc3MgYXV0b2NvbmYgdG8gYmUgc3RhbmRh cmRpemVkIGluIHRoZSBJRVRGLg0KPiA+RVRSSSBoYXMgYWxyZWFkeSBpbXBsZW1lbnRlZCBNQU5F VCBhZGRyZXNzIGF1dG9jb25mIGJhc2VkIG9uIG15IGRyYWZ0Og0KPiA+aHR0cDovL3d3dy5pZXRm Lm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtamVvbmctbWFuZXQtYW9kdi1hZGRyLWF1dG9jb25m LTAxLnR4dA0KPiA+aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtamVv bmctYWRob2MtaXAtYWRkci1hdXRvY29uZi0wMy50eHQNCj4gPmh0dHA6Ly93d3cuaWV0Zi5vcmcv aW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWplb25nLW1hbmV0LWFkZHItYXV0b2NvbmYtcmVxdHMtMDMu dHh0DQo+ID4NCj4gPkFsc28sIHJlY2VudGx5LCBQcm9mLiBLaWxpYW4gV2VuaWdlciBhbm5vdW5j ZWQgdGhlIGltcGxlbWVudGF0aW9uIG9mIFBhc3NpdmUgREFEOg0KPiA+aHR0cDovL3BhY21hbi1h dXRvY29uZi5zb3VyY2Vmb3JnZS5uZXQNCj4gPmh0dHA6Ly9zb3VyY2Vmb3JnZS5uZXQvcHJvamVj dHMvcGFjbWFuLWF1dG9jb25mLw0KPiA+DQo+ID5TaW5jZSBNQU5FVCBhZGRyZXNzaW5nIGlzIHBy ZXJlcXVpc2l0ZSBmb3IgTUFORVQgcm91dGluZywgSSB0aGluayBpdCBjYW4gYmUgaGFuZGxlZCBh dCBvdXIgTUFORVQgd2cuDQo+ID5GaXJzdCwgd2UgY2FuIG1ha2UgdGhlIHJlcXVpcmVtZW50cyBm b3IgTUFORVQgYWRkcmVzcyBhdXRvY29uZiBhcyBJbmZvcm1hdGlvbmFsIFJGQy4NCj4gPkFmdGVy IHRoYXQsIGlmIGEgc2ltcGxlIE1BTkVUIGF1dG9jb25mIHNjaGVtZSBnZXRzIGEgY29uc2Vuc3Vz LCB3ZSBjYW4gbWFrZSBpdCBhcyBhbm90aGVyIEluZm9ybWF0aW9uIFJGQy4NCj4gPg0KPiA+SSB3 b3VsZCBsaWtlIHRvIGFzayB5b3UgdG8gZGlzY3VzcyBpdCB3aXRoIEFEcy4NCj4gPg0KPiA+VGhh bmtzLg0KPiA+DQo+ID5SZWdhcmRzLA0KPiA+DQo+ID5QYXVsDQo+ID4NCj4gPj09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PQ0KPiA+SmFlaG9vbiBQYXVsIEplb25nLA0KPiA+UGguRC4gU3R1ZGVudCwNCj4gPkRlcGFy dG1lbnQgb2YgQ29tcHV0ZXIgU2NpZW5jZQ0KPiA+VW5pdmVyc2l0eSBvZiBNaW5uZXNvdGEgYXQg VHdpbiBDaXRpZXMNCj4gPkVtYWlsOiBqamVvbmdAY3MudW1uLmVkdQ0KPiA+SG9tZXBhZ2U6IGh0 dHA6Ly93d3cuY3MudW1uLmVkdS9+amplb25nLw0KPiA+UGhvbmU6ICsxLTYxMi02MjQtNjIwOChP ZmZpY2UpLCA2NTEtNTg3LTc3NzQoQ2VsbCkNCj4gPg0KPiA+DQo+ID4tLS0tLSBPcmlnaW5hbCBN ZXNzYWdlIC0tLS0tIA0KPiA+RnJvbTogIkpvZSBNYWNrZXIiIDxqb3NlcGgubWFja2VyQG5ybC5u YXZ5Lm1pbD4NCj4gPlRvOiA8bWFuZXRAaWV0Zi5vcmc+DQo+ID5TZW50OiBUaHVyc2RheSwgTm92 ZW1iZXIgMDQsIDIwMDQgMTE6MzUgQU0NCj4gPlN1YmplY3Q6IFttYW5ldF0gRm9jdXMgZm9yIG5l eHQgREMgTUFORVQgbWVldGluZw0KPiA+DQo+ID4NCj4gPiAgDQo+ID4NCj4gPj5UaGUgREMgTUFO RVQgbWVldGluZyBpcyBwcmVzZW50bHkgTm92LiAxMCwgV2VkIGFmdGVybm9vbiAxMzAwLTE1MDAu DQo+ID4+VW5mb3J0dW5hdGVseSB0aGlzIGdvdCBtb3ZlZCBhbmQgbm93IGNvbGxpZGVzIHdpdGgg TkVNTy4NCj4gPj4NCj4gPj5BcyBhIGhlYWRzIHVwLCBJIGFtIHN0aWxsIGRpc2N1c3NpbmcgY2hh cnRlciB1cGRhdGUgZGV0YWlscyB3aXRoIHRoZSBBRHMuDQo+ID4+V2Ugc2hvdWxkIGJlIHdyYXBw aW5nIHRoaXMgdXAgc29vbi4gSW4gbWVhbnRpbWUsIGhlcmUgaXMgdGhlIGludGVuZGVkIHNjb3Bl IGZvciB0aGUgdXBjb21naW5nIG1lZXRpbmcuDQo+ID4+DQo+ID4+VGhlIG1haW4gZGlzY3Vzc2lv biBmb3IgdGhlIHVwY29taW5nIG1lZXRpbmcgd2lsbCBiZSBvbiB0aGUgZm9sbG93aW5nIHJvdXRp bmcgYXJlYSB3b3JrIGl0ZW1zLg0KPiA+PlRoZXNlIGFyZSBpbnRlbmRlZCB0byBiZSBwcm9wb3Nl ZCBzdGFuZGFyZCB0cmFjayB3b3JrIGl0ZW1zDQo+ID4+DQo+ID4+LSBjb21tb24gZnJhbWV3b3Jr IGZvciBhIHByb2FjdGl2ZSBNQU5FVCBwcm90b2NvbA0KPiA+Pi0gY29tbW9uIGZyYW1ld29yayBm b3IgYSByZWFjdGl2ZSBNQU5FVCBwcm90b2NvbA0KPiA+Pi0gY29tbW9uIGZyYW1ld29yayBmb3Ig YSBzaW1wbGlmaWVkIE1BTkVUIG11bHRpY2FzdCBmb3J3YXJkaW5nIHByb3RvY29sDQo+ID4+DQo+ ID4+T3RoZXIgcmVsYXRlZCBNQU5FVCBpdGVtcyBtYXkgbmVlZCB0byBiZSBoYW5kbGVkIHZpYSBC T0YsZXRjIGV4cGxvcmF0aW9uLi5vciBkaXNjdXNzZWQgbW9yZSB3aXRoIHRoZSBBRHMgYW5kIFdH IGNoYWlycy4NCj4gPj4NCj4gPj4tSm9lDQo+ID4+DQo+ID4+DQo+ID4+X19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPj5tYW5ldCBtYWlsaW5nIGxpc3QN Cj4gPj5tYW5ldEBpZXRmLm9yZw0KPiA+Pmh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xp c3RpbmZvL21hbmV0DQo+ID4+DQo+ID4+ICAgIA0KPiA+Pg0KPiA+Pi0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K PiA+Pg0KPiA+Pl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f DQo+ID4+bWFuZXQgbWFpbGluZyBsaXN0DQo+ID4+bWFuZXRAaWV0Zi5vcmcNCj4gPj5odHRwczov L3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tYW5ldA0KPiA+PiAgICANCj4gPj4NCj4g DQo+IA0KPiA= --===============1353147340== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1353147340==-- From manet-bounces@ietf.org Fri Nov 5 13:42:39 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06231 for ; Fri, 5 Nov 2004 13:42:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ9Ia-0001BL-QQ for manet-web-archive@ietf.org; Fri, 05 Nov 2004 13:59:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ8xJ-00064v-3t; Fri, 05 Nov 2004 13:37:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ8kL-0003lG-Ee for manet@megatron.ietf.org; Fri, 05 Nov 2004 13:23:39 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05011 for ; Fri, 5 Nov 2004 13:23:34 -0500 (EST) Received: from reserv5.univ-lille1.fr ([193.49.225.19] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ907-0000qM-Mr for manet@ietf.org; Fri, 05 Nov 2004 13:39:56 -0500 Received: from kriek (kriek.lifl.fr [134.206.11.16]) by reserv5.univ-lille1.fr (8.13.1/jtpda-5.3.1) with ESMTP id iA5ILGwR019600 ; Fri, 5 Nov 2004 19:21:16 +0100 From: "David Simplot-Ryl" To: , , , Date: Fri, 5 Nov 2004 19:21:46 +0100 Message-ID: <010601c4c364$56da0090$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.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-USTL-MailScanner-Information: Please contact the ISP for more information X-USTL-MailScanner: Found to be clean X-MailScanner-From: david.simplot@lifl.fr X-Spam-Score: 0.0 (/) X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a Content-Transfer-Encoding: quoted-printable Subject: [manet] Last CFP WWAN 2005, Columbus, Ohio, USA, 6-9 June, 2005 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985 Content-Transfer-Encoding: quoted-printable Please accept our apologies in case you receive this information from multiple sources. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D LAST CALL FOR PAPERS WWAN 2005 2nd International Workshop on Wireless Ad Hoc Networking http://www.lifl.fr/RD2P/WWAN2005 to be held in conjunction with The 25th IEEE International Conference on Distributed Computing Systems (ICDCS-2005) Columbus, Ohio, USA, June 6-9, 2005 http://www.cis.ohio-state.edu/icdcs05 ---------------------------------------------------------------------- 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 or satellite systems. Wireless ad hoc networking covers multi-hop scenarios (network nodes communicating via other network nodes) such as conference, hospital, battlefield, rescue, and 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 the rapidly growing area of ad hoc networks. The first edition of WWAN held last year during ICDCS-2004 (Tokyo, Japan) was organized by David Simplot-Ryl and Ivan Stojmenovic. In response to the Call for Papers, 42 papers from 20 different countries had been submitted. Based on three review reports per paper, they was classified as accept, reject or discuss. For those papers in the discuss list, additional opinions were sought. As a result, a total of 21 papers were selected for presentation at WWAN 2004 and were organized in 7 sessions. Website of this prior workshop: http://www.lifl.fr/RD2P/WWAN2004 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 802.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. 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'2005 workshops. You can use the IEEE Computer Society Press Proceedings Author Guidelines (http://computer.org/cspress/instruct.htm). Prepare your paper in PDF file only (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: November 12, 2004=20 Acceptance Notification: January 21, 2005=20 Final Manuscript Due: March 1, 2005=20 Program Co-Chairs Dr. David Simplot IRCICA/LIFL, Univ. Lille 1, INRIA Futurs, 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 Serge Fdida, University of Paris, France=20 Laura Marie Feeney, SICS, Kista, Sweden=20 Afonso Ferreira, CNRS, France & COST Office, Brussels, Belgium=20 Eric Fleury, CITI Lyon, France=20 Matthias Frank, University of Bonn, Germany=20 Jennifer Hou, University of Illinois, USA=20 Keqin Li, State University of New York, USA=20 Xiang-Yang Li, Illinois Institute of Technology, USA=20 Soung-Chang Liew, The Chinese University of Hong Kong, Hong Kong=20 St=E9phane Maag, INT Evry, France=20 Jelena Misic, University of Manitoba, Winnipeg, Canada=20 Ingrid Moerman, University of Gent, Belgium=20 Amiya Nayak, SITE, University of Ottawa, Canada=20 Stephan Olariu, Old Dominion University, Norfolk, USA=20 Symeon Papavassiliou, University Heights, Newark, USA=20 Pedro Ruiz, University of Murcia, Spain=20 Loren Schwiebert, Wayne University, Detroit, USA=20 Krishna Sivalingam, University of Maryland Baltimore County, USA=20 Ketil St=F8len, SINTEF and University of Oslo, Norway=20 Takashi Watanabe, Shizuoka University, Japan=20 Fr=E9d=E9ric Weis, University of Rennes, France=20 Jie Wu, Florida Atlantic University, USA _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 13:44:46 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06417 for ; Fri, 5 Nov 2004 13:44:46 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ9Kc-0001FV-9p for manet-web-archive@ietf.org; Fri, 05 Nov 2004 14:01:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ90v-0006xR-H0; Fri, 05 Nov 2004 13:40:45 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ8qC-00050k-9G for manet@megatron.ietf.org; Fri, 05 Nov 2004 13:29:42 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05302 for ; Fri, 5 Nov 2004 13:29:37 -0500 (EST) Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ95w-0000wY-2B for manet@ietf.org; Fri, 05 Nov 2004 13:45:59 -0500 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.12.10+Sun/8.12.8) with SMTP id iA5ISqTS027597; Fri, 5 Nov 2004 13:28:54 -0500 (EST) Received: from [132.250.92.22] ([132.250.92.22]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.0.4.64) with SMTP id M2004110513285215387 ; Fri, 05 Nov 2004 13:28:52 -0500 Message-ID: <418BC6AA.5050903@nrl.navy.mil> Date: Fri, 05 Nov 2004 13:30:02 -0500 From: Joe Macker User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jaehoon Jeong Subject: Re: [manet] Focus for next DC MANET meeting References: <418A5A66.4050503@nrl.navy.mil> <002301c4c3a8$90ba3160$c88310ac@paulnb> In-Reply-To: <002301c4c3a8$90ba3160$c88310ac@paulnb> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Content-Transfer-Encoding: 7bit Cc: Alex Zinin , Bill Fenner , manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 7bit Jaehoon Jeong wrote: > Hi Joe, > > As you know, many people want MANET address autoconf to be standardized in the IETF. > ETRI has already implemented MANET address autoconf based on my draft: > http://www.ietf.org/internet-drafts/draft-jeong-manet-aodv-addr-autoconf-01.txt > http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf-03.txt > http://www.ietf.org/internet-drafts/draft-jeong-manet-addr-autoconf-reqts-03.txt > > Also, recently, Prof. Kilian Weniger announced the implementation of Passive DAD: > http://pacman-autoconf.sourceforge.net > http://sourceforge.net/projects/pacman-autoconf/ > > Since MANET addressing is prerequisite for MANET routing, I think it can be handled at our MANET wg. > First, we can make the requirements for MANET address autoconf as Informational RFC. > After that, if a simple MANET autoconf scheme gets a consensus, we can make it as another Information RFC. > > I would like to ask you to discuss it with ADs. > I assure you I have been discussing this with the ADs and there has been some resistance to expanding MANET WG scope in this area. I am cc'ing them so they have your input. I would agree that even in addition to the above work, there are many others that implement autoconf approaches and have shown them to work. We may wish to plan an MANET autoconf BOF for the next IETF. Secondly, since MANET (in the WB context) is just IP routing it can be applied in many different scenarios with many ways of performing address management. I would encourage you to promote this not a requirements discussion but perhaps a best known practices formulation exercise with some applicability discussion. -Joe _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 14:06:26 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08140 for ; Fri, 5 Nov 2004 14:06:26 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ9fW-0001hV-W6 for manet-web-archive@ietf.org; Fri, 05 Nov 2004 14:22:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ9LB-00025u-0n; Fri, 05 Nov 2004 14:01:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQ96K-0008NX-W8 for manet@megatron.ietf.org; Fri, 05 Nov 2004 13:46:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06525 for ; Fri, 5 Nov 2004 13:46:19 -0500 (EST) Received: from dns1.tilab.com ([163.162.42.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQ9Lw-0001Gq-Q3 for manet@ietf.org; Fri, 05 Nov 2004 14:02:40 -0500 Received: from iowa2k01a.cselt.it ([163.162.242.201]) by dns1.cselt.it (PMDF V6.0-025 #38895) with ESMTP id <0I6P00387YOQS3@dns1.cselt.it> for manet@ietf.org; Fri, 05 Nov 2004 19:43:38 +0100 (MET) Received: from EXC01A.cselt.it ([163.162.4.198]) by iowa2k01a.cselt.it with Microsoft SMTPSVC(6.0.3790.211); Fri, 05 Nov 2004 19:47:36 +0100 Date: Fri, 05 Nov 2004 19:45:36 +0100 From: Ruffino Simone Subject: RE: [manet] Focus for next DC MANET meeting To: Jaehoon Jeong Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Importance: normal Priority: normal Thread-Topic: [manet] Focus for next DC MANET meeting Thread-Index: AcTDYoYQC82Kx66SRRysfV7dpqG61wAADVgw Content-class: urn:content-classes:message X-OriginalArrivalTime: 05 Nov 2004 18:47:36.0515 (UTC) FILETIME=[EB03A930:01C4C367] X-Spam-Score: 0.0 (/) X-Scan-Signature: 140baa79ca42e6b0e2b4504291346186 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a492040269d440726bfd84680622cee7 Content-Transfer-Encoding: quoted-printable Hi Jaehoon, Here's our recently published draft : http://www.ietf.org/internet-drafts/draft-ruffino-manet-autoconf-scenari os-00.txt The goal of this draft is to describe the scenarios in which autoconfiguration problem arises, mainly focusing on MANET connected to external networks. You can find today's deployment scenarios and more "futuristic" ones. In the draft we also introduce the problem statement for autoconfiguration topic, related to such scenarios. In fact, we think that any discussion on requirements should start from a general problem statement, to avoid deriving requirements suited to a limited set of applications/scenarios. I'd really appreciate your feedback on it.=20 Thanks Regards, Simone > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of > Jaehoon Jeong > Sent: sabato 6 novembre 2004 5.57 > To: Charles E. Perkins > Cc: manet@ietf.org > Subject: Re: [manet] Focus for next DC MANET meeting >=20 > Hi Charlie, >=20 > If MANET chairs decide to work on this activity, I think that your > previous drafts > can be used as base documents. > For developing specific machanism draft(s), we seem to have to reach a > consensus on > the requirements of MANET address autoconf. > I appreciate your previous work. >=20 > Thanks. >=20 > Jaehoon >=20 >=20 > ----- Original Message ----- > From: "Charles E. Perkins" > To: "Jaehoon Jeong" > Cc: > Sent: Friday, November 05, 2004 12:11 PM > Subject: Re: [manet] Focus for next DC MANET meeting >=20 >=20 > > > > Hello Jaehoon, > > > > As you probably know, we also have had drafts for autoconfiguration > > of addresses in ad hoc networks. These drafts have not been resubmitted > > recently, because the working group has not had autoconfiguration on > > its charter. Nevertheless, the specification is good and compatible > with > > on-demand routing protocols. If the working group decides to charter > > new work on this activity, I would like our previous drafts to be > > considered for adoption by the working group. Alternatively, it might > > make sense to investigate some combined approach. > > > > Regards, > > Charlie P. > > > > > > Jaehoon Jeong wrote: > > > > >Hi Joe, > > > > > >As you know, many people want MANET address autoconf to be standardized > in the IETF. > > >ETRI has already implemented MANET address autoconf based on my draft: > > >http://www.ietf.org/internet-drafts/draft-jeong-manet-aodv-addr- > autoconf-01.txt > > >http://www.ietf.org/internet-drafts/draft-jeong-adhoc-ip-addr-autoconf- > 03.txt > > >http://www.ietf.org/internet-drafts/draft-jeong-manet-addr-autoconf- > reqts-03.txt > > > > > >Also, recently, Prof. Kilian Weniger announced the implementation of > Passive DAD: > > >http://pacman-autoconf.sourceforge.net > > >http://sourceforge.net/projects/pacman-autoconf/ > > > > > >Since MANET addressing is prerequisite for MANET routing, I think it > can be handled at our MANET wg. > > >First, we can make the requirements for MANET address autoconf as > Informational RFC. > > >After that, if a simple MANET autoconf scheme gets a consensus, we can > make it as another Information RFC. > > > > > >I would like to ask you to discuss it with ADs. > > > > > >Thanks. > > > > > >Regards, > > > > > >Paul > > > > > > >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D > > >Jaehoon Paul Jeong, > > >Ph.D. Student, > > >Department of Computer Science > > >University of Minnesota at Twin Cities > > >Email: jjeong@cs.umn.edu > > >Homepage: http://www.cs.umn.edu/~jjeong/ > > >Phone: +1-612-624-6208(Office), 651-587-7774(Cell) > > > > > > > > >----- Original Message ----- > > >From: "Joe Macker" > > >To: > > >Sent: Thursday, November 04, 2004 11:35 AM > > >Subject: [manet] Focus for next DC MANET meeting > > > > > > > > > > > > > > >>The DC MANET meeting is presently Nov. 10, Wed afternoon 1300-1500. > > >>Unfortunately this got moved and now collides with NEMO. > > >> > > >>As a heads up, I am still discussing charter update details with the > ADs. > > >>We should be wrapping this up soon. In meantime, here is the intended > scope for the upcomging meeting. > > >> > > >>The main discussion for the upcoming meeting will be on the following > routing area work items. > > >>These are intended to be proposed standard track work items > > >> > > >>- common framework for a proactive MANET protocol > > >>- common framework for a reactive MANET protocol > > >>- common framework for a simplified MANET multicast forwarding > protocol > > >> > > >>Other related MANET items may need to be handled via BOF,etc > exploration..or discussed more with the ADs and WG chairs. > > >> > > >>-Joe > > >> > > >> > > >>_______________________________________________ > > >>manet mailing list > > >>manet@ietf.org > > >>https://www1.ietf.org/mailman/listinfo/manet > > >> > > >> > > >> > > >>---------------------------------------------------------------------- > -- > > >> > > >>_______________________________________________ > > >>manet mailing list > > >>manet@ietf.org > > >>https://www1.ietf.org/mailman/listinfo/manet > > >> > > >> > > > > > > Gruppo Telecom Italia - Direzione e coordinamento di Telecom Italia = S.p.A. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 send an e_mail to=20 MailAdmin@tilab.com. Thank you =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 5 17:48:19 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27209 for ; Fri, 5 Nov 2004 17:48:19 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQCsY-0006lV-Rw for manet-web-archive@ietf.org; Fri, 05 Nov 2004 17:48:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQCoo-0004gc-DP; Fri, 05 Nov 2004 17:44:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQClm-0003mL-8F for manet@megatron.ietf.org; Fri, 05 Nov 2004 17:41:22 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26700 for ; Fri, 5 Nov 2004 17:41:19 -0500 (EST) Received: from mail.cs.umn.edu ([128.101.32.202] ident=postfix) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQClm-0006cK-Fh for manet@ietf.org; Fri, 05 Nov 2004 17:41:22 -0500 Received: from localhost (localhost [127.0.0.1]) by augustus.cs.umn.edu (Postfix) with ESMTP id F0E715C397; Fri, 5 Nov 2004 16:41:20 -0600 (CST) Received: from mail.cs.umn.edu ([127.0.0.1]) by localhost (augustus [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29330-01-3; Fri, 5 Nov 2004 16:41:19 -0600 (CST) Received: from paulnb (fw-dtc.cs.umn.edu [128.101.189.210]) by mail.cs.umn.edu (Postfix) with SMTP id 0DEE95C383; Fri, 5 Nov 2004 16:41:18 -0600 (CST) Message-ID: <013a01c4c380$66188650$c88310ac@paulnb> From: "Jaehoon Jeong" To: "Joe Macker" References: <418A5A66.4050503@nrl.navy.mil> <002301c4c3a8$90ba3160$c88310ac@paulnb> <418BC6AA.5050903@nrl.navy.mil> Subject: Re: [manet] Focus for next DC MANET meeting Date: Fri, 5 Nov 2004 16:42:50 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at cs.umn.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Cc: Bill Fenner , Alex Zinin , manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0933015809==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a --===============0933015809== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 VGhhbmtzIGZvciB5b3VyIHdvcmsuIDotKQ0KDQpJIGhvcGUgdG8gc2VlIHRoZSBkaXJlY3Rpb24g b2YgTUFORVQgYXV0b2NvbmYgYXQgdGhpcyBtZWV0aW5nOg0KYSBuZXcgaXRlbSBhdCBNQU5FVCB3 ZyBvciB0aGUgZGV2ZWxvcG1lbnQgdGhyb3VnaCBNQU5FVCBBdXRvY29uZiBCb2YuDQoNCkphZWhv b24NCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJKb2UgTWFja2VyIiA8 am9zZXBoLm1hY2tlckBucmwubmF2eS5taWw+DQpUbzogIkphZWhvb24gSmVvbmciIDxqamVvbmdA Y3MudW1uLmVkdT4NCkNjOiA8bWFuZXRAaWV0Zi5vcmc+OyAiQWxleCBaaW5pbiIgPHppbmluQHBz Zy5jb20+OyAiQmlsbCBGZW5uZXIiIDxmZW5uZXJAcmVzZWFyY2guYXR0LmNvbT4NClNlbnQ6IEZy aWRheSwgTm92ZW1iZXIgMDUsIDIwMDQgMTozMCBQTQ0KU3ViamVjdDogUmU6IFttYW5ldF0gRm9j dXMgZm9yIG5leHQgREMgTUFORVQgbWVldGluZw0KDQoNCj4gSmFlaG9vbiBKZW9uZyB3cm90ZToN Cj4gPiBIaSBKb2UsDQo+ID4gDQo+ID4gQXMgeW91IGtub3csIG1hbnkgcGVvcGxlIHdhbnQgTUFO RVQgYWRkcmVzcyBhdXRvY29uZiB0byBiZSBzdGFuZGFyZGl6ZWQgaW4gdGhlIElFVEYuDQo+ID4g RVRSSSBoYXMgYWxyZWFkeSBpbXBsZW1lbnRlZCBNQU5FVCBhZGRyZXNzIGF1dG9jb25mIGJhc2Vk IG9uIG15IGRyYWZ0Og0KPiA+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2Ry YWZ0LWplb25nLW1hbmV0LWFvZHYtYWRkci1hdXRvY29uZi0wMS50eHQNCj4gPiBodHRwOi8vd3d3 LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1qZW9uZy1hZGhvYy1pcC1hZGRyLWF1dG9j b25mLTAzLnR4dA0KPiA+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0 LWplb25nLW1hbmV0LWFkZHItYXV0b2NvbmYtcmVxdHMtMDMudHh0DQo+ID4gDQo+ID4gQWxzbywg cmVjZW50bHksIFByb2YuIEtpbGlhbiBXZW5pZ2VyIGFubm91bmNlZCB0aGUgaW1wbGVtZW50YXRp b24gb2YgUGFzc2l2ZSBEQUQ6DQo+ID4gaHR0cDovL3BhY21hbi1hdXRvY29uZi5zb3VyY2Vmb3Jn ZS5uZXQNCj4gPiBodHRwOi8vc291cmNlZm9yZ2UubmV0L3Byb2plY3RzL3BhY21hbi1hdXRvY29u Zi8NCj4gPiANCj4gPiBTaW5jZSBNQU5FVCBhZGRyZXNzaW5nIGlzIHByZXJlcXVpc2l0ZSBmb3Ig TUFORVQgcm91dGluZywgSSB0aGluayBpdCBjYW4gYmUgaGFuZGxlZCBhdCBvdXIgTUFORVQgd2cu DQo+ID4gRmlyc3QsIHdlIGNhbiBtYWtlIHRoZSByZXF1aXJlbWVudHMgZm9yIE1BTkVUIGFkZHJl c3MgYXV0b2NvbmYgYXMgSW5mb3JtYXRpb25hbCBSRkMuDQo+ID4gQWZ0ZXIgdGhhdCwgaWYgYSBz aW1wbGUgTUFORVQgYXV0b2NvbmYgc2NoZW1lIGdldHMgYSBjb25zZW5zdXMsIHdlIGNhbiBtYWtl IGl0IGFzIGFub3RoZXIgSW5mb3JtYXRpb24gUkZDLg0KPiA+IA0KPiA+IEkgd291bGQgbGlrZSB0 byBhc2sgeW91IHRvIGRpc2N1c3MgaXQgd2l0aCBBRHMuDQo+ID4gDQo+IA0KPiBJIGFzc3VyZSB5 b3UgSSBoYXZlIGJlZW4gZGlzY3Vzc2luZyB0aGlzIHdpdGggdGhlIEFEcyBhbmQgdGhlcmUgaGFz IGJlZW4gc29tZSByZXNpc3RhbmNlIHRvIGV4cGFuZGluZyBNQU5FVCBXRyBzY29wZSBpbiB0aGlz IGFyZWEuDQo+IEkgYW0gY2MnaW5nIHRoZW0gc28gdGhleSBoYXZlIHlvdXIgaW5wdXQuDQo+IA0K PiBJIHdvdWxkIGFncmVlIHRoYXQgZXZlbiBpbiBhZGRpdGlvbiB0byB0aGUgYWJvdmUgd29yaywg dGhlcmUgYXJlIG1hbnkgb3RoZXJzIHRoYXQgaW1wbGVtZW50IGF1dG9jb25mIGFwcHJvYWNoZXMg YW5kIGhhdmUgc2hvd24gdGhlbSB0byB3b3JrLiBXZSBtYXkgd2lzaCB0byBwbGFuIGFuIE1BTkVU IGF1dG9jb25mIEJPRiBmb3IgdGhlIG5leHQgSUVURi4NCj4gDQo+IFNlY29uZGx5LCBzaW5jZSBN QU5FVCAoaW4gdGhlIFdCIGNvbnRleHQpIGlzIGp1c3QgSVAgcm91dGluZyBpdCBjYW4gYmUgYXBw bGllZCBpbiBtYW55IGRpZmZlcmVudCBzY2VuYXJpb3Mgd2l0aCBtYW55IHdheXMgb2YgcGVyZm9y bWluZyBhZGRyZXNzIG1hbmFnZW1lbnQuIEkgd291bGQgZW5jb3VyYWdlIHlvdSB0byBwcm9tb3Rl IHRoaXMgbm90IGEgcmVxdWlyZW1lbnRzIGRpc2N1c3Npb24gYnV0IHBlcmhhcHMgYSBiZXN0IGtu b3duIHByYWN0aWNlcyBmb3JtdWxhdGlvbiBleGVyY2lzZSB3aXRoIHNvbWUgYXBwbGljYWJpbGl0 eSBkaXNjdXNzaW9uLg0KPiANCj4gLUpvZQ0KPiANCj4g --===============0933015809== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0933015809==-- From manet-bounces@ietf.org Sat Nov 6 11:56:41 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20607 for ; Sat, 6 Nov 2004 11:56:41 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQTry-0001zh-MA for manet-web-archive@ietf.org; Sat, 06 Nov 2004 11:56:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQToM-0008Lc-P1; Sat, 06 Nov 2004 11:53:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQTkl-0007su-VC for manet@megatron.ietf.org; Sat, 06 Nov 2004 11:49:28 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20224 for ; Sat, 6 Nov 2004 11:49:25 -0500 (EST) Received: from web90105.mail.scd.yahoo.com ([66.218.94.76]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CQTku-0001rO-TZ for manet@ietf.org; Sat, 06 Nov 2004 11:49:38 -0500 Received: (qmail 88507 invoked by uid 60001); 6 Nov 2004 16:48:55 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=ezU3caPFCJ89KuGTwqKE0sWXn4qFh3XyOnB3GXG3AGH9qCuAeM03jZBoZ8Ux/4qWFXRvBJ1GFcyrEG4LU0tN1LNL6UYNLuF92LVKHuoVctLBrLnY/PfylN2XjgtO5Os9i08Cd841Y+5Xzq6CL63geKk1FkttOa/exXQDV8H35ag= ; Message-ID: <20041106164854.88505.qmail@web90105.mail.scd.yahoo.com> Received: from [203.208.193.230] by web90105.mail.scd.yahoo.com via HTTP; Sat, 06 Nov 2004 08:48:54 PST Date: Sat, 6 Nov 2004 08:48:54 -0800 (PST) From: Parag Goswami To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Subject: [manet] about autoconfiguration ? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1764008064==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da --===============1764008064== Content-Type: multipart/alternative; boundary="0-341062767-1099759734=:88244" --0-341062767-1099759734=:88244 Content-Type: text/plain; charset=us-ascii Hi all, This is Parag Goswami an undergraduate student of Computer science ane Engineering.Well my question is that suppose we have ad hoc network in which all nodes are connected through access points and these access points are connected to a main Gateway. This gateway may also a part of some bigger system.Now if a new node (mobile) enters the system. Now this new node has to be connected through all the other nodes on this system through access points and the gateway.All nodes contact each other through a message passsing protocol. My question is : 1. Does all the nodes in the network has a particular IP before this node enters the system ? 2. If the above holds true that once this new node is detected and enters the system then do we need any autoconfiguration mechanism for IP of nodes in the system or How this configuration is done ? Look forward to hear from you guys. Thanks for the time. Best Regards, Parag Goswami http://www.geocities.com/paragboom2k --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --0-341062767-1099759734=:88244 Content-Type: text/html; charset=us-ascii
Hi all,
This is Parag Goswami an undergraduate student of Computer science ane Engineering.Well my question is that suppose we have ad hoc network in which all nodes are connected through access points and these access points are connected to a main Gateway. This gateway may also a part of some bigger system.Now if a new node  (mobile) enters the system. Now this new node has to be connected through all the other nodes on this system through access points and the gateway.All nodes contact each other through a message passsing protocol. My question is :
 
1. Does all the nodes in the network has a particular IP before this node enters 
    the system ?
    
2. If the above holds true that once this new node is detected and enters the
    system then do we need any autoconfiguration mechanism for IP of nodes in
    the system or How this configuration is done ?
 
Look forward to hear from you guys.
Thanks for the time.
 
Best Regards,
Parag Goswami

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com --0-341062767-1099759734=:88244-- --===============1764008064== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1764008064==-- From manet-bounces@ietf.org Sat Nov 6 12:46:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23803 for ; Sat, 6 Nov 2004 12:46:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQUeK-00031S-5Y for manet-web-archive@ietf.org; Sat, 06 Nov 2004 12:46:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQUZf-0000hv-B9; Sat, 06 Nov 2004 12:42:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQUSr-0007li-3f for manet@megatron.ietf.org; Sat, 06 Nov 2004 12:35:01 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22858 for ; Sat, 6 Nov 2004 12:34:58 -0500 (EST) Received: from web20921.mail.yahoo.com ([216.136.224.135]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CQUT0-0002kB-Ea for manet@ietf.org; Sat, 06 Nov 2004 12:35:11 -0500 Received: (qmail 36330 invoked by uid 60001); 6 Nov 2004 17:34:57 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=BTgGUt7XY+YwCMStgP/qi5FkM5GKHBgZVkbz3G/uv3R+9vRB83n54KFCXsnRBik+CPons0KlLH2cAa5FHJTWb+rkINBFQJXBFYlVHKJZElEBjsDKeHauNeLdLqBmaTfWIQQJpyKiAxDN/gjwIYwyYBdy0aow9+YgB0bbqktJ6WQ= ; Message-ID: <20041106173457.36327.qmail@web20921.mail.yahoo.com> Received: from [203.208.193.230] by web20921.mail.yahoo.com via HTTP; Sat, 06 Nov 2004 09:34:57 PST Date: Sat, 6 Nov 2004 09:34:57 -0800 (PST) From: Praveen Choudary To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Subject: [manet] research X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0042900908==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 --===============0042900908== Content-Type: multipart/alternative; boundary="0-1543830629-1099762497=:36152" --0-1543830629-1099762497=:36152 Content-Type: text/plain; charset=us-ascii Hi, I want to know, if there are any publications which try to group nodes clusters using GPS. I mean, suppose if the node is in a particular region, it will be in one cluster. As the node keeps on moving, it continuously checks if it is in the region. Once, it crosses the region boundary, it will know that is in different cluster. I have seen this concept in one publication previously, but I am not able to recollect the Publication. This is very important for my research. I request the members of this group, to give me some references in this direction. Looking forward for your reply, Praveen. --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --0-1543830629-1099762497=:36152 Content-Type: text/html; charset=us-ascii
Hi,
 I want to know, if there are any publications which try to group nodes clusters using GPS. I mean, suppose if the node is in a particular region, it will be in one cluster. As the node keeps on moving, it continuously checks if it is in the region. Once, it crosses the region boundary, it will know that is in different cluster. I have seen this concept in one publication previously, but I am not able to recollect the Publication. This is very important for my research.
 
I request the members of this group, to give me some references in this direction.
 
Looking forward for your reply,
Praveen.

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com --0-1543830629-1099762497=:36152-- --===============0042900908== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0042900908==-- From manet-bounces@ietf.org Sat Nov 6 12:50:11 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24049 for ; Sat, 6 Nov 2004 12:50:11 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQUhk-000361-Mg for manet-web-archive@ietf.org; Sat, 06 Nov 2004 12:50:25 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQUZh-0000io-0m; Sat, 06 Nov 2004 12:42:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQUSx-0007mj-Uu for manet@megatron.ietf.org; Sat, 06 Nov 2004 12:35:08 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22877 for ; Sat, 6 Nov 2004 12:35:04 -0500 (EST) Received: from web20926.mail.yahoo.com ([216.136.224.143]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CQUT7-0002kf-Bn for manet@ietf.org; Sat, 06 Nov 2004 12:35:18 -0500 Received: (qmail 49604 invoked by uid 60001); 6 Nov 2004 17:35:05 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=LILMLACNXnfPtp1zZky/mnDJ8i16alWz62W9Rf5NAS3dLrGQQfFXv41jEfbLZJtyJaXoZrLEEAeMKx2BrzeWdS2n8ImvWH4Pw5cvwrp3zZ6c0tpeAvSwvKwjPWojLBeqYUBshhxzSBeDQvRs/8WdTxnl4LDDZeM/58DwKjGbPcM= ; Message-ID: <20041106173505.49602.qmail@web20926.mail.yahoo.com> Received: from [203.208.193.230] by web20926.mail.yahoo.com via HTTP; Sat, 06 Nov 2004 09:35:05 PST Date: Sat, 6 Nov 2004 09:35:05 -0800 (PST) From: Praveen Choudary To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Subject: [manet] research X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1815897571==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 --===============1815897571== Content-Type: multipart/alternative; boundary="0-728971154-1099762505=:49487" --0-728971154-1099762505=:49487 Content-Type: text/plain; charset=us-ascii Hi, I want to know, if there are any publications which try to group nodes clusters using GPS. I mean, suppose if the node is in a particular region, it will be in one cluster. As the node keeps on moving, it continuously checks if it is in the region. Once, it crosses the region boundary, it will know that is in different cluster. I have seen this concept in one publication previously, but I am not able to recollect the Publication. This is very important for my research. I request the members of this group, to give me some references in this direction. Looking forward for your reply, Praveen. --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --0-728971154-1099762505=:49487 Content-Type: text/html; charset=us-ascii
Hi,
 I want to know, if there are any publications which try to group nodes clusters using GPS. I mean, suppose if the node is in a particular region, it will be in one cluster. As the node keeps on moving, it continuously checks if it is in the region. Once, it crosses the region boundary, it will know that is in different cluster. I have seen this concept in one publication previously, but I am not able to recollect the Publication. This is very important for my research.
 
I request the members of this group, to give me some references in this direction.
 
Looking forward for your reply,
Praveen.

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com --0-728971154-1099762505=:49487-- --===============1815897571== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1815897571==-- From manet-bounces@ietf.org Sat Nov 6 21:45:24 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27849 for ; Sat, 6 Nov 2004 21:45:24 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQd3m-0004ck-9A for manet-web-archive@ietf.org; Sat, 06 Nov 2004 21:45:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQcwI-0000aN-Mk; Sat, 06 Nov 2004 21:37:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQcsd-0007hV-CJ for manet@megatron.ietf.org; Sat, 06 Nov 2004 21:34:11 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27202 for ; Sat, 6 Nov 2004 21:34:09 -0500 (EST) From: erinninn@comp.nus.edu.sg Received: from x86unx3.comp.nus.edu.sg ([137.132.80.24]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQcsr-0004Np-Fs for manet@ietf.org; Sat, 06 Nov 2004 21:34:26 -0500 Received: from e500d.comp.nus.edu.sg (e500d.comp.nus.edu.sg [137.132.90.69]) by x86unx3.comp.nus.edu.sg (8.9.1-20030924/8.9.1) with SMTP id KAA00639; Sun, 7 Nov 2004 10:33:33 +0800 (GMT-8) Received: from se11.comp.nus.edu.sg(137.132.80.19) by e500d.comp.nus.edu.sg via csmap id cf834308_3065_11d9_9cbc_0030482985c3_18007; Sun, 07 Nov 2004 10:36:21 +0800 (SGT) Received: (from http@localhost) by se11.comp.nus.edu.sg (8.12.10+Sun/8.12.5) id iA72XWRZ014001; Sun, 7 Nov 2004 10:33:32 +0800 (SGT) X-Authentication-Warning: se11.comp.nus.edu.sg: http set sender to erinninn@comp.nus.edu.sg using -f Received: from cm55.sigma98.maxonline.com.sg ([218.212.98.55]) (proxying for 218.212.220.127) (SquirrelMail authenticated user erinninn); by mysoc.nus.edu.sg with HTTP; Sun, 7 Nov 2004 10:33:32 +0800 (SGT) Message-ID: <26820.218.212.98.55.1099794812.squirrel@218.212.98.55> In-Reply-To: <20041106173505.49602.qmail@web20926.mail.yahoo.com> References: <20041106173505.49602.qmail@web20926.mail.yahoo.com> Date: Sun, 7 Nov 2004 10:33:32 +0800 (SGT) Subject: Re: [manet] research To: "Praveen Choudary" User-Agent: SquirrelMail/1.4.3 X-Mailer: SquirrelMail/1.4.3 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: 0.3 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: 8bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 8bit Hi, Our group works on the project which is a clustering algorithm that group nodes based on the moving pattern but not on GPS information. Just refer you to the link.. hope it helps. http://www.comp.nus.edu.sg/~erinninn/mobdhop.pdf regards inn inn > Hi, > I want to know, if there are any publications which try to group nodes > clusters using GPS. I mean, suppose if the node is in a particular > region, it will be in one cluster. As the node keeps on moving, it > continuously checks if it is in the region. Once, it crosses the region > boundary, it will know that is in different cluster. I have seen this > concept in one publication previously, but I am not able to recollect the > Publication. This is very important for my research. > > I request the members of this group, to give me some references in this > direction. > > Looking forward for your reply, > Praveen. > > > --------------------------------- > Do you Yahoo!? > Check out the new Yahoo! Front Page. > www.yahoo.com_______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Nov 7 07:45:26 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15498 for ; Sun, 7 Nov 2004 07:45:26 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQmQW-000239-V6 for manet-web-archive@ietf.org; Sun, 07 Nov 2004 07:45:49 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQmIl-0006yg-Nw; Sun, 07 Nov 2004 07:37:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQmIf-0006tJ-5b for manet@megatron.ietf.org; Sun, 07 Nov 2004 07:37:41 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15190 for ; Sun, 7 Nov 2004 07:37:39 -0500 (EST) From: mehrana@uow.edu.au Received: from ziz.its.uow.edu.au ([130.130.68.16]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQmIy-0001w3-Vc for manet@ietf.org; Sun, 07 Nov 2004 07:38:01 -0500 Received: from febris.its.uow.edu.au ([130.130.68.100]) by ziz.its.uow.edu.au with esmtp (Exim 4.34) id 1CQmIZ-0005u8-Op; Sun, 07 Nov 2004 23:37:35 +1100 Received: from mirapoint.uow.edu.au (mirapoint.uow.edu.au [130.130.68.27]) by febris.its.uow.edu.au (MOS 3.5.5-GR) with ESMTP id AGI27545; Sun, 7 Nov 2004 23:37:31 +1100 (EST) Received: from 130.130.37.6 by mirapoint.uow.edu.au (MOS 3.5.3-GR) with HTTP/1.1; Sun, 7 Nov 2004 23:37:31 +1100 Date: Sun, 7 Nov 2004 23:37:31 +1100 Subject: Re: [manet] research To: Praveen Choudary X-Mailer: Mirapoint Webmail Direct 3.5.3-GR MIME-Version: 1.0 Message-Id: <5f07a9f9.9b80ffc9.81ba400@mirapoint.uow.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.3 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Content-Transfer-Encoding: 7bit Hi Praveen, The following references presents some of the work with performed in designing a GPS-based clustering alogorithms and routing. M.Abolhasan, T.A.Wysocki, and E.Dutkiewicz: "Scalable Routing Strategies For Dynamic Zone-based MANETS", Proc. of IEEE GLOBECOM 2002, Taipei, Taiwan, R.O.C., November 17-21, 2002. M. Abolhasan and T.A. Wysocki:"Highly Scalable Routing Strategies: DZTR routing protocol", In an edited volume by the Kluwer Academic Publishers, pp. 1-18, 2004. Regards, Mehran ---- Original message ---- >Date: Sat, 6 Nov 2004 09:35:05 -0800 (PST) >From: Praveen Choudary >Subject: [manet] research >To: manet@ietf.org > > Hi, > I want to know, if there are any publications which > try to group nodes clusters using GPS. I mean, > suppose if the node is in a particular region, it > will be in one cluster. As the node keeps on moving, > it continuously checks if it is in the region. Once, > it crosses the region boundary, it will know that is > in different cluster. I have seen this concept in > one publication previously, but I am not able to > recollect the Publication. This is very important > for my research. > > I request the members of this group, to give me some > references in this direction. > > Looking forward for your reply, > Praveen. > > ------------------------------------------------ > > Do you Yahoo!? > Check out the new Yahoo! Front Page. www.yahoo.com >________________ >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet Mehran Abolhasan B.E Computer, PhD Research Fellow Telecommunications and IT Research Institute (TITR) University of Wollongong, Northfields Ave, NSW 2522, Australia Phone: +61 2 4221 3347 Fax: +61 2 4221 3277 www.titr.uow.edu.au/~mehran Email 1: mehrana@uow.edu.au Email 2: mehran@titr.uow.edu.au _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Nov 7 08:23:15 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18077 for ; Sun, 7 Nov 2004 08:23:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQn17-00033Z-Sj for manet-web-archive@ietf.org; Sun, 07 Nov 2004 08:23:38 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQmuz-00073C-IX; Sun, 07 Nov 2004 08:17:17 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQmsE-0006at-4z for manet@megatron.ietf.org; Sun, 07 Nov 2004 08:14:26 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17427 for ; Sun, 7 Nov 2004 08:14:24 -0500 (EST) Received: from smtp.acd.net ([207.179.64.154]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQmsY-0002rW-Of for manet@ietf.org; Sun, 07 Nov 2004 08:14:47 -0500 Received: from DrEvil ([207.179.88.194]) by smtp.acd.net with Microsoft SMTPSVC(5.0.2195.6713); Sun, 7 Nov 2004 08:15:32 -0500 From: "Alex Terrazas" To: Date: Sun, 7 Nov 2004 08:13:55 -0500 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcTEy6H+BD9+ClV+R9KxRI6Cq9lbIQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Message-ID: X-OriginalArrivalTime: 07 Nov 2004 13:15:32.0223 (UTC) FILETIME=[DC0978F0:01C4C4CB] X-Spam-Score: 0.9 (/) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 Subject: [manet] MANETs in wireless behavior mod X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1836618511==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48 This is a multi-part message in MIME format. --===============1836618511== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0000_01C4C4A1.B9D68900" This is a multi-part message in MIME format. ------=_NextPart_000_0000_01C4C4A1.B9D68900 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi-- I am a psychologist and neuroscientist who is using MANETs to measure behavior and give reinforcement in the form of points. The points can be traded in for access to electronic media--computer games, TV, Internet, cell phone minutes, etc.--think of it as behavioral pay-per-view. Measurement of behavior occurs through a network of automated (usually) sensors. I can see that my use of Bluetooth is rudimentary at present. I would like to take advantage of more sophisticated approaches. In general, what I am doing can be called behavioral economics. I call the idea 'wireless walden' after the psychologist B.F. Skinner. I intend to use the technology to treat physical inactivity, over eating, attention deficit disorder, and several other behavioral problems. I have a small company (3 employees total). I am applying for grants to test the many aspects of this approach. Here are some items I would like feedback on: 1) What would be a good journal or conference to describe the application? 2) What are the potential strategies for organizing the MANETs for this application. I realize I have not given a great deal of info. If anyone would be willing to provide some direction, I could give you a phone call or we can discuss this on the forum. Most often the sensors are automated--I have a prototype sensor that detects the stretch of your belly, for example. I have a lot of accelerometer-based designs--like a leaf rake that gives points. I have Hall effect sensors. The application domain is pretty much endless--unless everyone starts behaving themselves! 3) Anybody know of grant opportunities in this area? I have been going after NIH so far but wouldn't mind expanding. It has been interesting following some of the discussions on this forum. Thanks-- Alex ------=_NextPart_000_0000_01C4C4A1.B9D68900 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
Hi--
 
I am a = psychologist=20 and neuroscientist who is using MANETs to measure behavior and give=20 reinforcement in the form of points.  The points can be traded in = for=20 access to electronic media--computer games, TV, Internet, cell phone = minutes,=20 etc.--think of it as behavioral pay-per-view.  Measurement of = behavior=20 occurs through a network of automated (usually) sensors.  I = can see=20 that my use of Bluetooth is rudimentary at present.  I would like = to take=20 advantage of more sophisticated approaches.
 
In = general, what I=20 am doing can be called behavioral economics.  I call the idea = 'wireless=20 walden' after the psychologist B.F. Skinner.  I intend to use the=20 technology to treat physical inactivity, over eating, attention deficit=20 disorder, and several other behavioral problems.  I have a small = company (3=20 employees total).  I am applying for grants to test the = many=20 aspects of this approach.
 
Here=20 are some items I would like feedback on:
 
1)=20 What would be a good journal or conference to describe the = application? =20
 
2)=20 What are the potential strategies for organizing the MANETs for this=20 application.  I realize I have not given a great deal of = info.  If=20 anyone would be willing to provide some direction, I could give you a = phone call=20 or we can discuss this on the forum.  Most often the sensors are=20 automated--I have a prototype sensor that detects the stretch of your = belly, for=20 example.  I have a lot of accelerometer-based designs--like a leaf = rake=20 that gives points.  I have Hall effect sensors.  The = application=20 domain is pretty much endless--unless everyone starts behaving = themselves! =20
 
3)=20 Anybody know of grant opportunities in this area?  I have been = going after=20 NIH so far but wouldn't mind expanding.
 
It=20 has been interesting following some of the discussions on this = forum. =20
 
Thanks--
 
Alex
------=_NextPart_000_0000_01C4C4A1.B9D68900-- --===============1836618511== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1836618511==-- From manet-bounces@ietf.org Sun Nov 7 19:59:46 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17658 for ; Sun, 7 Nov 2004 19:59:46 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CQxtJ-0001Im-SX for manet-web-archive@ietf.org; Sun, 07 Nov 2004 20:00:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQxmK-0005j7-4A; Sun, 07 Nov 2004 19:53:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CQxi1-0005Ex-Cb for manet@megatron.ietf.org; Sun, 07 Nov 2004 19:48:37 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16768 for ; Sun, 7 Nov 2004 19:48:33 -0500 (EST) Received: from web60003.mail.yahoo.com ([216.109.116.226]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CQxiR-00013j-GF for manet@ietf.org; Sun, 07 Nov 2004 19:49:04 -0500 Message-ID: <20041108004803.71299.qmail@web60003.mail.yahoo.com> Received: from [202.141.142.23] by web60003.mail.yahoo.com via HTTP; Sun, 07 Nov 2004 16:48:03 PST Date: Sun, 7 Nov 2004 16:48:03 -0800 (PST) From: Shahriar Shamil Uulu To: ns-users@ISI.EDU, manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Subject: [manet] Questions regarding ... X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1219897162==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 --===============1219897162== Content-Type: multipart/alternative; boundary="0-843013316-1099874883=:70018" --0-843013316-1099874883=:70018 Content-Type: text/plain; charset=us-ascii Hi everybody, I have two questions: 1. Where i can find a good manual for ns2, in fact i am having one mostly times i am getting confused in it. 2. From where i can download Glomosim, i tried to download it from Glomosim website but it said that i am having problem with my IP. If any one could answer my questions it would be greatly apperciated. Thank you ... --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --0-843013316-1099874883=:70018 Content-Type: text/html; charset=us-ascii
Hi everybody,
I have two questions:
1. Where i can find a good manual for ns2, in fact i am having one mostly times i am getting confused in it.
2. From where i can download Glomosim,  i tried to download it from Glomosim website but it said that i am having problem with my IP.
If any one could answer my questions it would be greatly apperciated.
Thank you ...

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com --0-843013316-1099874883=:70018-- --===============1219897162== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1219897162==-- From manet-bounces@ietf.org Mon Nov 8 01:04:06 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10930 for ; Mon, 8 Nov 2004 01:04:06 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CR2dp-0007Nv-Dl for manet-web-archive@ietf.org; Mon, 08 Nov 2004 01:04:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CR2Zd-0000Xu-49; Mon, 08 Nov 2004 01:00:17 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CR2Xw-00006w-Ax for manet@megatron.ietf.org; Mon, 08 Nov 2004 00:58:32 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA10281 for ; Mon, 8 Nov 2004 00:58:28 -0500 (EST) Received: from web50606.mail.yahoo.com ([206.190.38.93]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CR2YF-0007DO-Vn for manet@ietf.org; Mon, 08 Nov 2004 00:59:02 -0500 Received: (qmail 70055 invoked by uid 60001); 8 Nov 2004 05:57:50 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=A0BpXGj4gBWNepaNZN3ZuhN7DLWJB82niF0KrVbhMcJNJLVOlHW7i9wngrB3A1Hwe0lwJJ3/HTB3DwWH66UpSt7gVhzDzfKxBuoe/Z/5aDVPrSTGLHgJUnA3DPfy4sHrb+lpY8x/HJ/Mzu5kN7311mKtYADZG0D17rlqUXc4OAY= ; Message-ID: <20041108055750.70052.qmail@web50606.mail.yahoo.com> Received: from [130.74.176.55] by web50606.mail.yahoo.com via HTTP; Sun, 07 Nov 2004 21:57:50 PST Date: Sun, 7 Nov 2004 21:57:50 -0800 (PST) From: Raja Sombhotla Subject: RE: [manet] Are there protocols that are like SIP or H.323 thatcouldprovide session or peer-peer sceesions in MANETS for Voiceor Multimedia? To: Li Li , manet@ietf.org In-Reply-To: <200411021237.iA2Cbv49012400@mail.crc.ca> MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1768588318==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576 --===============1768588318== Content-Type: multipart/alternative; boundary="0-306698763-1099893470=:69096" --0-306698763-1099893470=:69096 Content-Type: text/plain; charset=us-ascii Dear all, First of all thank you very much for answering my questions. Li Li, in your paper why have you considered the interarrival time is exponentially distributed with a mean value of 600 sec and the call duration time is also exponentially distributed with a mean value of 180 sec? What is the criteria for choosing these parameters in a mobile ad hoc network simulation evaluating the service carrying capacity? Li Li wrote: We did the SIP over MANET simulation using OPNET, generating SIP voice packets over an OLSR MANET to evaluate service performance. It should be possible with ns-2 simulator. You can find our work and paper at http://www.crc.ca/en/html/manetsensor/home/research_area/support li li At 12:20 AM 11/2/2004 -0600, srgopal wrote: >Dear Daniel and christopher, > >Are you saying that this SIP protocol can be used to >generate VoIP packets like packet voice in Mobile Ad Hoc >networks to see the performance of Ad Hoc networks when >supporting VoIp and/or multimedia? I mean can it be used >with ns-2 simulator and see its affect on ad hoc network >performance. Please clarify this. If not, how can one >generate packet voice while simulating Ad Hoc network using >ns-2 simulator? > >I would appreciate your time and patience in this regard. > >Regards, >Raja. > > > >> Greetings Daniel, >> In your MANET architecture, do all the nodes act as >> Location Services, Proxies, User Agent Clients (UACs) and >> User Agent Server (UASs)? >> >> Thanks and regards, >> >> Chris >> >> -----Original Message----- >> From: manet-bounces@ietf.org >> [mailto:manet-bounces@ietf.org] On Behalf Of Daniel Henkel >> Sent: Saturday, October 30, 2004 11:13 AM >> To: manet@ietf.org >> Subject: Re: [manet] Are there protocols that are like SIP >> or H.323 that couldprovide session or peer-peer sceesions >> in MANETS for Voice or Multimedia? >> >> Hi Christopher, >> >> We have successfully used SIP to initiate VoIP sessions >> over several hops in our testbed. Using Linphone on both >> laptops and iPAQs we were able to have very reliable >> communication with our DSR implementation. You can >> possibly use a much more stripped down version of SIP and >> achieve same results if footprint is an issue; try oSIP: >> http://www.gnu.org/software/osip/osip.html >> >> Regards, >> Daniel Henkel >> University of Colorado at Boulder >> http://AUGNet.colorado.edu >> >> >> ---- Original Message ---- >> From: Christopher P. Rigano >> To: >> Subject: [manet] Are there protocols that are like SIP or >> H.323 that could provide session or peer-peer sceesions in >> MANETS for Voice or Multimedia? >> >> Friday, October 29, 2004, 1:59:34 PM, you wrote: >> >> CPR> >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> manet mailing 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 > Li Li, Ph.D Communications Research Centre, Industry Canada 3701 Carling avenue P.O. box 11490 Station H, Ottawa, Ontario, Canada K2H 8S2 Tel: (613) 990-5246 Email: li.li@crc.ca _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --0-306698763-1099893470=:69096 Content-Type: text/html; charset=us-ascii
Dear all,
 
First of all thank you very much for answering my questions.
 
Li Li, in your paper why have you considered the interarrival time is exponentially distributed with a mean value of 600 sec and the call duration time is also exponentially distributed with a mean value of 180 sec? What is the criteria for choosing these parameters in a mobile ad hoc network simulation evaluating the service carrying capacity?

Li Li <li.li@crc.ca> wrote:
We did the SIP over MANET simulation using OPNET, generating SIP voice
packets over an OLSR MANET to evaluate service performance. It should be
possible with ns-2 simulator.

You can find our work and paper at
http://www.crc.ca/en/html/manetsensor/home/research_area/support

li li

At 12:20 AM 11/2/2004 -0600, srgopal wrote:
>Dear Daniel and christopher,
>
>Are you saying that this SIP protocol can be used to
>generate VoIP packets like packet voice in Mobile Ad Hoc
>networks to see the performance of Ad Hoc networks when
>supporting VoIp and/or multimedia? I mean can it be used
>with ns-2 simulator and see its affect on ad hoc network
>performance. Please clarify this. If not, how can one
>generate packet voice while simulating Ad Hoc network using
>ns-2 simulator?
>
>I would appreciate your time and patience in this regard.
>
>Regards,
>Raja.
>
>
>
>> Greetings Daniel,
>> In your MANET architecture, do all the nodes act as
>> Location Services, Proxies, User Agent Clients (UACs) and
>> User Agent Server (UASs)?
>>
>> Thanks and regards,
>>
>> Chris
>>
>> -----Original Message-----
>> From: manet-bounces@ietf.org
>> [mailto:manet-bounces@ietf.org] On Behalf Of Daniel Henkel
>> Sent: Saturday, October 30, 2004 11:13 AM
>> To: manet@ietf.org
>> Subject: Re: [manet] Are there protocols that are like SIP
>> or H.323 that couldprovide session or peer-peer sceesions
>> in MANETS for Voice or Multimedia?
>>
>> Hi Christopher,
>>
>> We have successfully used SIP to initiate VoIP sessions
>> over several hops in our testbed.! Using Linphone on both
>> laptops and iPAQs we were able to have very reliable
>> communication with our DSR implementation. You can
>> possibly use a much more stripped down version of SIP and
>> achieve same results if footprint is an issue; try oSIP:
>> http://www.gnu.org/software/osip/osip.html
>>
>> Regards,
>> Daniel Henkel
>> University of Colorado at Boulder
>> http://AUGNet.colorado.edu
>>
>>
>> ---- Original Message ----
>> From: Christopher P. Rigano
>> To:
>> Subject: [manet] Are there protocols that are like SIP or
>> H.323 that could provide session or peer-peer sceesions in
>> MANETS for Voice or Multimedia?
>>
>> Friday, October 29, 2004, 1:59:34 PM, you wrote:
>>
>> CPR>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> manet mailing 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
>
Li Li, Ph.D
Communications Research Centre, Industry Canada
3701 Carling avenue
P.O. box 11490
Station H, Ottawa,
Ontario, Canada K2H 8S2
Tel: (613) 990-5246
Email: li.li@crc.ca


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

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com --0-306698763-1099893470=:69096-- --===============1768588318== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1768588318==-- From manet-bounces@ietf.org Mon Nov 8 05:13:58 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17165 for ; Mon, 8 Nov 2004 05:13:58 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CR6Xg-00049X-HW for manet-web-archive@ietf.org; Mon, 08 Nov 2004 05:14:33 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CR6Rh-0006CP-DY; Mon, 08 Nov 2004 05:08:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CR6CU-0004E5-1y for manet@megatron.ietf.org; Mon, 08 Nov 2004 04:52:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15720 for ; Mon, 8 Nov 2004 04:52:35 -0500 (EST) Received: from web53904.mail.yahoo.com ([206.190.36.214]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CR6Cy-0003j3-SO for manet@ietf.org; Mon, 08 Nov 2004 04:53:10 -0500 Message-ID: <20041108095204.75756.qmail@web53904.mail.yahoo.com> Received: from [81.31.160.4] by web53904.mail.yahoo.com via HTTP; Mon, 08 Nov 2004 01:52:04 PST Date: Mon, 8 Nov 2004 01:52:04 -0800 (PST) From: Ehsan Ataie To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 3.0 (+++) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Subject: [manet] DSR in GloMoSim X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 3.0 (+++) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab hi my friends, does anybody know where i can find a DSR implementation in GloMoSim simulator? i appreciate any help; best regards, Ehsan __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 8 12:01:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01429 for ; Mon, 8 Nov 2004 12:01:04 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRCtg-00077p-9B for manet-web-archive@ietf.org; Mon, 08 Nov 2004 12:01:43 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRCW6-0005FI-Gu; Mon, 08 Nov 2004 11:37:18 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRCQV-0003ml-Bg for manet@megatron.ietf.org; Mon, 08 Nov 2004 11:31:31 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27510 for ; Mon, 8 Nov 2004 11:31:28 -0500 (EST) Received: from wproxy.gmail.com ([64.233.184.206]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRCR4-00064m-3R for manet@ietf.org; Mon, 08 Nov 2004 11:32:06 -0500 Received: by wproxy.gmail.com with SMTP id 66so234267wri for ; Mon, 08 Nov 2004 08:30:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=hF/dK5frInXIjbZL1AzG4x/4s4zvgAiIr9N5B/qHJQQ1AP3ubSTT6t5TExArvuMTEx6/qg0pzC56DCrxAQ5NIYDloqtAEWcwFhyW3/58vQCqS4Li1tT758pB8W4/sgs8O4V+KzuJr26hJSXW9+7GRypkSFvkQlopB6As9yxJ/hw= Received: by 10.54.41.27 with SMTP id o27mr182062wro; Mon, 08 Nov 2004 08:30:56 -0800 (PST) Received: by 10.54.50.61 with HTTP; Mon, 8 Nov 2004 08:30:56 -0800 (PST) Message-ID: <4176419a041108083057e991cd@mail.gmail.com> Date: Mon, 8 Nov 2004 13:30:56 -0300 From: Marcos Ferreyra To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Content-Transfer-Encoding: 7bit Subject: [manet] how can I simulate multicast in ad hoc WLANs? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marcos Ferreyra List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Hi everyone, Does NS (ns-allinone-2.27) support multicast traffic in ad hoc WLANs? If it does please tell me how, give me a link, whatever! else can you please suggest an alternative simulator? Marcos _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 8 12:38:34 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05233 for ; Mon, 8 Nov 2004 12:38:34 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRDU2-00086T-1A for manet-web-archive@ietf.org; Mon, 08 Nov 2004 12:39:14 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRDHb-0006jg-UH; Mon, 08 Nov 2004 12:26:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRCzk-00017V-1O for manet@megatron.ietf.org; Mon, 08 Nov 2004 12:07:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02170 for ; Mon, 8 Nov 2004 12:07:53 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.196]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRD0J-0007Jv-TV for manet@ietf.org; Mon, 08 Nov 2004 12:08:32 -0500 Received: by rproxy.gmail.com with SMTP id a36so321111rnf for ; Mon, 08 Nov 2004 09:07:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=GT0PDlaE3USoAzSQXd+M3y8pBzLDQYPdDh7yPOSlbyvXtV3ynpyNxM1K2opHOOqL/6TLqPK9ZQX8dkAMhS6xZhVNeY2cnztKA4c8rAoRgFiMxPV4yQOEjmjkEcEoRujgzR2aSymx0y2waitct3HMrPzsHl/PSpEuNArRum5KwoQ= Received: by 10.38.15.25 with SMTP id 25mr695484rno; Mon, 08 Nov 2004 09:07:53 -0800 (PST) Received: by 10.38.164.19 with HTTP; Mon, 8 Nov 2004 09:07:53 -0800 (PST) Message-ID: Date: Mon, 8 Nov 2004 18:07:53 +0100 From: Jinshan Liu To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 20f22c03b5c66958bff5ef54fcda6e48 Content-Transfer-Encoding: quoted-printable Subject: [manet] CFP -- iTrust 2005, third international Conference on Trust Management X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jinshan Liu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92 Content-Transfer-Encoding: quoted-printable CFP -- iTrust 2005 international conference on Trust management Sincere apologies if you receive multiple copies of this CFP. ------------------------------------------------------------------- Last Call for Papers 3rd International Conference on Trust Management (iTrust'2005) 23-26 May 2005, INRIA-Rocquencourt, France Submission of papers: Nov. 25th, 2004 http://www-rocq.inria.fr/arles/events/iTrust2005/ The iTrust international Conference looks at trust from multidisciplinary= =20 perspectives: economic, legal, pyschology, philosophy, sociology as well=20 as information technology.=20 Building upon the work of the IST iTrust working group=20 (http://www.itrust.uoc.gr) and the success of the two previous iTrust=20 International conferences (http://www.trustmanagement.cclrc.ac.uk/), the ai= ms=20 of iTrust'2005 are to attract a critical mass of experts from industry,=20 government and academia with a keen interest in the area of trust managemen= t.=20 The objectives of the Conference are:=20 - To facilitate the cross-disciplinary investigation of fundamental=20 issues underpinning computational trust models by bringing together=20 expertise from technology oriented sciences, law, philosophy and social= =20 sciences.=20 - To facilitate the emergence of widely acceptable trust management process= es=20 or dynamic open systems and applications.=20 - To facilitate the development of new paradigms in the area of dynamic=20 open systems which effectively utilise computational trust models.=20 - To facilitate the integration of new trust management paradigms and=20 emerging architectures for Grid computing and Virtual Organisations.=20 - To help the incorporation of trust management elements in existing standa= rds. =20 Topics of Interest: Full technical papers contributing to the issue of trust management are=20 solicited in the relevant areas, including but not limited to:=20 - The legal notion of trust in computer science and engineering - Requirements and methodologies to ensure that the user can trust the=20 functioning of software systems - Trust management frameworks for secure collaborations in dynamic Virtual= =20 Organisations=20 - Design of trust based architectures and decision-making mechanisms for=20 e-community and e-service interactions - Trust specification, analysis and reasoning - Dynamics of trust dispositions and relations=20 - Realisation of prototypes of software architectures and applications - Trust elements in contract negotiation, execution monitoring, re-negotiat= ion=20 and arbitration - Legal contribution to trust in technological infrastructures and=20 interactions: the on-line identification of subjects, the evaluation of= =20 their reliability, the data protection, privacy,=20 confidentiality, security, commercial transactions, the resolution of=20 disputes, software agents, the access to source code - The conditions for the reliance in the artefact and the machine - Trust in the interaction and cooperation "mediated" through computer and= =20 network, and the balance between control and intervention.=20 - Research of on-line trust, the trust of the consumer towards the web site= =20 of the distribution company - Analysis of the relationship between trust and such notions as confidence= ,=20 distrust, diffidence, expectation, risk and reliance. Important Dates:=20 Papers:=20 Submission of papers: November 25, 2004=20 Notification of paper acceptance: January 14, 2005 Submission of final camera ready version: February 25, 2005 How to Submit: Submissions must be original and must not have been submitted for publicati= on=20 elsewhere. =20 The proceedings of the Conference will be published by Springer in the=20 Lecture Notes in Computer Science series. Submissions must be in English=20 and authors should ensure that papers are formatted according to=20 the LNCS format (see author's instructions given on the Conference Web site= ).=20 Full technical papers should not exceed 15 pages in the abovementioned=20 format.=20 Submissions should be made through the Conference Web Site. =20 Organization: General Chair:=20 Valerie Issarny (INRIA) Programme Co-Chairs: Peter Herrmann, University of Dortmund, Germany Simon Shiu, Hewlett Packard, UK Conference Committee: Demonstration Chair: Nikolaos Georgantas, INRIA, France Panel Chair: Paul Kearney, BTexact, UK Tutorial Chair: Yuecel Karabulut, SAP AG, Germany Publicity Chair: Jinshan Liu, INRIA, France Local Arrangement: Dominique Potherat, INRIA, France Programme Committee: =20 Eliza Bertino, University of Milano, Italy Jon Bing, NRCCL-University of Oslo, Norway Jeremy Bryans, University of Newcastle, UK Cristiano Castelfranchi, CNR, Italy David Chadwick, University of Salford, UK Andrew Charlesworth, University of Bristol, UK David Crocker, Brandenburg InternetWorking, USA Mark Roger Dibben, University of St. Andrews, UK Theo Dimitrakos, CCLRC, UK Rino Falcone, CNR, Italy Peter Herrmann, University of Dortmund, Germany Valerie Issarny, INRIA, France Keith Jeffery, CCLRC, UK Christian Jensen, DTU, Denmark Andrew Jones, King's College, UK Audun Josang, DSTC, Australia Yuecel Karabulut, SAP AG, Germany Paul Kearney, BTexact, UK Graham Klyne, Nine by Nine, UK Heiko Krumm, University of Dortmund, Germany Ninghui Li, Stanford University, USA Peter Linington, University of Kent at Canterbury, UK Stephane Lo Presti, University of Southampton, UK Fabio Martinelli, CNR, Italy Fabio Massacci, Universit=E0 di Trento, Italy Erich Neuhold, Darmstadt University of Technology and Fraunhofer IPSI, Germ= any Christos Nikolaou, University of Crete, Greece Paddy Nixon, University of Strathclyde, UK Stefan Poslad, Queen Mary Colledge, UK Jens Riegelsberger, University of Newcastle, UK Peter Ryan, University of Newcastle, UK Babak Sadighi, SICS, Sweden Simon Shiu, Hewlett Packard, UK Morris Sloman, Imperial College, UK Ketil Stoelen, SINTEF & University of Oslo, Norway Yao-Hua Tan, Free University of Amsterdam, Holland Sotirios Terzis, University of Strathclyde, UK Dimitris Tsigos, Virtual Trip Ltd, Greece Stavroula Tsinorema, University of Crete, Greece Andrew Twigg, University of Cambridge, UK Emily Weitzenboeck, NRCCL-University of Oslo, Norway Marianne Winslett, University of Illinois at Urbana-Champaign, USA _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 8 13:04:02 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07544 for ; Mon, 8 Nov 2004 13:04:02 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRDsf-0000J2-2s for manet-web-archive@ietf.org; Mon, 08 Nov 2004 13:04:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRDn8-0004VS-8s; Mon, 08 Nov 2004 12:58:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRDef-0003Ri-NE for manet@megatron.ietf.org; Mon, 08 Nov 2004 12:50:13 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06619 for ; Mon, 8 Nov 2004 12:50:09 -0500 (EST) Received: from mail.icu.ac.kr ([210.107.128.19] helo=icu.ac.kr) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRDfD-0008Rr-Rh for manet@ietf.org; Mon, 08 Nov 2004 12:50:48 -0500 Received: from doggy (Debian-exim@v85-109.icu.ac.kr [220.69.185.109]) by icu.ac.kr (8.12.10/8.12.8) with ESMTP id iA8HfAj7003790; Tue, 9 Nov 2004 02:41:10 +0900 (KST) Received: from newcat by doggy with local (Exim 4.34) id 1CRDfc-00055n-5m; Tue, 09 Nov 2004 02:51:12 +0900 Date: Tue, 9 Nov 2004 02:51:12 +0900 From: YangWoo Ko To: Marcos Ferreyra Subject: Re: [manet] how can I simulate multicast in ad hoc WLANs? Message-ID: <20041108175112.GA19564@doggy> References: <4176419a041108083057e991cd@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4176419a041108083057e991cd@mail.gmail.com> User-Agent: Mutt/1.5.6+20040907i X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Dear Marcos, I don't know what options are available with 2.27 version. I usually used maodv implementaion with 2.26 verion, You can get it from the following URL. http://www.sce.carleton.ca/wmc/code.html Or you can also find odmrp impelmentation with older versions of ns. Good luck On Tue, Nov 09, 2004 at 02:00:11AM +0900, Marcos Ferreyra wrote: > > Hi everyone, > > Does NS (ns-allinone-2.27) support multicast traffic in ad hoc WLANs? > If it does > please tell me how, give me a link, whatever! > else > can you please suggest an alternative simulator? > > > Marcos > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > -- /*------------------------------------------------ The ones doing their job, doing what they were meant to do, are invisible. -- Matrix Reloaded Ko, YangWoo / Searcher / newcat@icu.ac.kr ------------------------------------------------*/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 8 14:08:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15299 for ; Mon, 8 Nov 2004 14:08:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CREt0-00026Q-B7 for manet-web-archive@ietf.org; Mon, 08 Nov 2004 14:09:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CREbT-0007ZD-3j; Mon, 08 Nov 2004 13:50:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CREMO-0004EO-9k for manet@megatron.ietf.org; Mon, 08 Nov 2004 13:35:24 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10567 for ; Mon, 8 Nov 2004 13:35:20 -0500 (EST) Received: from web50408.mail.yahoo.com ([206.190.38.73]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CREMy-000164-5F for manet@ietf.org; Mon, 08 Nov 2004 13:36:01 -0500 Message-ID: <20041108183451.86442.qmail@web50408.mail.yahoo.com> Received: from [200.231.0.66] by web50408.mail.yahoo.com via HTTP; Mon, 08 Nov 2004 10:34:51 PST Date: Mon, 8 Nov 2004 10:34:51 -0800 (PST) From: Guild Jackson To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Subject: [manet] ad hoc with SIP VoIP protocol X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Hi all, I would like to know how is the process to make a SIP registration in an Ad Hoc network that uses SIP VoIP protocol to create sessions between the terminals. Is there a REGISTRAR server that can register this SIP addresses? Thanks in advance and best regards Guild Jackson __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 8 14:45:36 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19804 for ; Mon, 8 Nov 2004 14:45:36 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRFSw-0003JY-Oj for manet-web-archive@ietf.org; Mon, 08 Nov 2004 14:46:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRF4i-0008B8-Br; Mon, 08 Nov 2004 14:21:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRF1X-0006nW-GN for manet@megatron.ietf.org; Mon, 08 Nov 2004 14:17:55 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16591 for ; Mon, 8 Nov 2004 14:17:53 -0500 (EST) Received: from simon.cs.cornell.edu ([128.84.154.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRF28-0002Rb-EV for manet@ietf.org; Mon, 08 Nov 2004 14:18:32 -0500 Received: from sundial.cs.cornell.edu (sundial.cs.cornell.edu [128.84.96.115]) by simon.cs.cornell.edu (8.11.7-20031020/8.11.7/R-3.17) with ESMTP id iA8JHrF07874; Mon, 8 Nov 2004 14:17:53 -0500 (EST) Received: from kwalsh4158.cs.cornell.edu (dhcp98-214.cs.cornell.edu [128.84.98.214]) by sundial.cs.cornell.edu (8.11.7-20031020/8.11.7/M-3.21) with ESMTP id iA8JHqq11540; Mon, 8 Nov 2004 14:17:53 -0500 (EST) Message-Id: <5.2.1.1.0.20041108140939.00ab0ef8@popsrv.cs.cornell.edu> X-Sender: kwalsh@popsrv.cs.cornell.edu X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Mon, 08 Nov 2004 14:17:39 -0500 To: Marcos Ferreyra , manet@ietf.org From: Kevin Walsh Subject: Re: [manet] how can I simulate multicast in ad hoc WLANs? In-Reply-To: <4176419a041108083057e991cd@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Along with the suggestion of maodv, I would add that you should be able to run maodv under the SNS simulator, available at: http://www.cs.cornell.edu/People/egs/sns/ SNS is fully compatible with sns-allinone-2.1b9a (it is an extension of the ns2 simulator, and shares most of the code base), but is quite a bit faster, and can simulate much larger wireless networks. Regards, Kevin W. At 01:30 PM 11/8/2004 -0300, Marcos Ferreyra wrote: >Hi everyone, > >Does NS (ns-allinone-2.27) support multicast traffic in ad hoc WLANs? >If it does > please tell me how, give me a link, whatever! >else > can you please suggest an alternative simulator? > > >Marcos > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 8 15:05:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22910 for ; Mon, 8 Nov 2004 15:05:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRFmP-0003wz-Ds for manet-web-archive@ietf.org; Mon, 08 Nov 2004 15:06:24 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRFVT-0006Gp-6c; Mon, 08 Nov 2004 14:48:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRFBB-0000o2-LJ for manet@megatron.ietf.org; Mon, 08 Nov 2004 14:27:53 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17631 for ; Mon, 8 Nov 2004 14:27:51 -0500 (EST) Received: from wproxy.gmail.com ([64.233.184.197]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRFBl-0002kJ-Tf for manet@ietf.org; Mon, 08 Nov 2004 14:28:31 -0500 Received: by wproxy.gmail.com with SMTP id 66so258653wri for ; Mon, 08 Nov 2004 11:27:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=f/RaWHq04ePjQ0F7IMeMoZSlqXJgjQ4ToeQ4+x7mucQhyJa37VAhtxMgRWvSxyoOhn66f9wbvtBgWozH1tAhn1olDO80Dv1BUF2CN3+O0eQgiv26Vw9RrerzIpaN4L4QutHXUmz7VnvxFQgnd6GbzrLqY3KzexNL3yzhzDjdsjI= Received: by 10.54.31.63 with SMTP id e63mr10280wre; Mon, 08 Nov 2004 11:27:07 -0800 (PST) Received: by 10.54.50.61 with HTTP; Mon, 8 Nov 2004 11:27:07 -0800 (PST) Message-ID: <4176419a041108112772f0c3@mail.gmail.com> Date: Mon, 8 Nov 2004 16:27:07 -0300 From: Marcos Ferreyra To: YangWoo Ko Subject: Re: [manet] how can I simulate multicast in ad hoc WLANs? In-Reply-To: <20041108175112.GA19564@doggy> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4176419a041108083057e991cd@mail.gmail.com> <20041108175112.GA19564@doggy> X-Spam-Score: 0.0 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marcos Ferreyra List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Content-Transfer-Encoding: 7bit Hi > I don't know what options are available with 2.27 version. I usually > used maodv implementaion with 2.26 verion, You can get it from the > following URL. > > http://www.sce.carleton.ca/wmc/code.html > Or you can also find odmrp impelmentation with older versions of ns. Hmm, what I want is to get srm (or at least rtp) running in an ad hoc WLAN. I am not talking about multihop routing in ad hoc nets. I guess I did not make the correct question. I am sorry. Anyway, would any of these multicast routing protocols make srm work on ad hoc nets? When I use mobilenodes and srm I get: $ns wsrm.tcl num_nodes is set 1 INITIALIZE THE LIST xListHead Starting Simulation... channel.cc:sendUp - Calc highestAntennaZ_ and distCST_ highestAntennaZ_ = 1.5, distCST_ = 550.0 SORTING LISTS ...DONE! ns: _o19 new-group 0 -2147483648 -1 cache-miss: can't read "protocols_(-1)": no such variable while executing "$protocols_($iface) upcall $code $source $group $iface" (procedure "_o20" line 9) (mrtObject upcall line 9) invoked from within "$mrtObject_ upcall $code $src $group $iface" (procedure "_o14" line 3) (Node new-group line 3) invoked from within "$node_ new-group $src $group $iface $code" (procedure "_o19" line 3) (Classifier/Multicast new-group line 3) invoked from within "_o19 new-group 0 -2147483648 -1 cache-miss" I grepped for "protocols_" and found many entries in ns-2.27/tcl/mcast/McastProto.tcl, but nowhere else. I have found at least 6 other posts since 2001 reporting the same or very similar problems. Any ideas? Would maodv or odrmp solve this problem? > > Hi everyone, > > > > Does NS (ns-allinone-2.27) support multicast traffic in ad hoc WLANs? > > If it does > > please tell me how, give me a link, whatever! > > else > > can you please suggest an alternative simulator? > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 8 15:22:29 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25709 for ; Mon, 8 Nov 2004 15:22:29 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRG2e-0004Ri-Ii for manet-web-archive@ietf.org; Mon, 08 Nov 2004 15:23:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRFnB-0007us-Dc; Mon, 08 Nov 2004 15:07:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRFWM-0006Mc-Nb for manet@megatron.ietf.org; Mon, 08 Nov 2004 14:49:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20621 for ; Mon, 8 Nov 2004 14:49:44 -0500 (EST) Received: from mail.icu.ac.kr ([210.107.128.19] helo=icu.ac.kr) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRFWw-0003Sq-3v for manet@ietf.org; Mon, 08 Nov 2004 14:50:24 -0500 Received: from doggy (Debian-exim@v85-109.icu.ac.kr [220.69.185.109]) by icu.ac.kr (8.12.10/8.12.8) with ESMTP id iA8JeOj7021930; Tue, 9 Nov 2004 04:40:24 +0900 (KST) Received: from newcat by doggy with local (Exim 4.34) id 1CRFX0-0005FK-Db; Tue, 09 Nov 2004 04:50:26 +0900 Date: Tue, 9 Nov 2004 04:50:26 +0900 From: YangWoo Ko To: Marcos Ferreyra Subject: Re: [manet] how can I simulate multicast in ad hoc WLANs? Message-ID: <20041108195026.GA20155@doggy> References: <4176419a041108083057e991cd@mail.gmail.com> <20041108175112.GA19564@doggy> <4176419a041108112772f0c3@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4176419a041108112772f0c3@mail.gmail.com> User-Agent: Mutt/1.5.6+20040907i X-Spam-Score: 0.0 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 On Tue, Nov 09, 2004 at 04:18:54AM +0900, Marcos Ferreyra wrote: > > Hi > > > I don't know what options are available with 2.27 version. I usually > > used maodv implementaion with 2.26 verion, You can get it from the > > following URL. > > > > http://www.sce.carleton.ca/wmc/code.html > > Or you can also find odmrp impelmentation with older versions of ns. > > Hmm, what I want is to get srm (or at least rtp) running in an ad > hoc WLAN. I am not talking about multihop routing in ad hoc nets. > I guess I did not make the correct question. I am sorry. Anyway, > would any of these multicast routing protocols make srm work > on ad hoc nets? Yes. If my memory is not wrong, I ran a few ad hoc networking simulations with srm + maodv patch + ns 2.26. > When I use mobilenodes and srm I get: > > $ns wsrm.tcl > num_nodes is set 1 > INITIALIZE THE LIST xListHead > Starting Simulation... > channel.cc:sendUp - Calc highestAntennaZ_ and distCST_ > highestAntennaZ_ = 1.5, distCST_ = 550.0 > SORTING LISTS ...DONE! > ns: _o19 new-group 0 -2147483648 -1 cache-miss: can't read > "protocols_(-1)": no such variable > while executing > "$protocols_($iface) upcall $code $source $group $iface" > (procedure "_o20" line 9) > (mrtObject upcall line 9) > invoked from within > "$mrtObject_ upcall $code $src $group $iface" > (procedure "_o14" line 3) > (Node new-group line 3) > invoked from within > "$node_ new-group $src $group $iface $code" > (procedure "_o19" line 3) > (Classifier/Multicast new-group line 3) > invoked from within > "_o19 new-group 0 -2147483648 -1 cache-miss" > > > I grepped for "protocols_" and found many entries in > ns-2.27/tcl/mcast/McastProto.tcl, but nowhere else. > > I have found at least 6 other posts since 2001 reporting the > same or very similar problems. Any ideas? Would maodv or > odrmp solve this problem? > > > > Hi everyone, > > > > > > Does NS (ns-allinone-2.27) support multicast traffic in ad hoc WLANs? > > > If it does > > > please tell me how, give me a link, whatever! > > > else > > > can you please suggest an alternative simulator? > > > > > -- /*------------------------------------------------ The ones doing their job, doing what they were meant to do, are invisible. -- Matrix Reloaded Ko, YangWoo / Searcher / newcat@icu.ac.kr ------------------------------------------------*/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 8 16:58:46 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07432 for ; Mon, 8 Nov 2004 16:58:46 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRHXq-0007JE-LC for manet-web-archive@ietf.org; Mon, 08 Nov 2004 16:59:27 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRHO8-0007yZ-VL; Mon, 08 Nov 2004 16:49:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRHDw-0005Ea-6u for manet@megatron.ietf.org; Mon, 08 Nov 2004 16:38:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05244 for ; Mon, 8 Nov 2004 16:38:49 -0500 (EST) Received: from wproxy.gmail.com ([64.233.184.199]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRHEU-0006eh-87 for manet@ietf.org; Mon, 08 Nov 2004 16:39:30 -0500 Received: by wproxy.gmail.com with SMTP id 66so275722wri for ; Mon, 08 Nov 2004 13:37:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=LNkswNZ8qZfKJD+abnh+KDyB4Ahn2cSMenXj9pd/07vw+7t7eO+sNv0rEdQSfFTuDDbHr58E6zs40T6s3Lc5pAApCNDoPTuN1QxVmZc9CPu7RSli29ZuE6oBptr2tLNZieZwZCo/8dkGlYCzL/4j3P6MJVvpeFZToF3SkDsSRVY= Received: by 10.54.31.63 with SMTP id e63mr20618wre; Mon, 08 Nov 2004 13:37:40 -0800 (PST) Received: by 10.54.50.61 with HTTP; Mon, 8 Nov 2004 13:37:40 -0800 (PST) Message-ID: <4176419a04110813377464ee4d@mail.gmail.com> Date: Mon, 8 Nov 2004 18:37:40 -0300 From: Marcos Ferreyra To: manet@ietf.org Subject: Re: [manet] how can I simulate multicast in ad hoc WLANs? In-Reply-To: <20041108195026.GA20155@doggy> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4176419a041108083057e991cd@mail.gmail.com> <20041108175112.GA19564@doggy> <4176419a041108112772f0c3@mail.gmail.com> <20041108195026.GA20155@doggy> X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marcos Ferreyra List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Content-Transfer-Encoding: 7bit > > > I don't know what options are available with 2.27 version. I usually > > > used maodv implementaion with 2.26 verion, You can get it from the > > > following URL. > > > > > > http://www.sce.carleton.ca/wmc/code.html > > > Or you can also find odmrp impelmentation with older versions of ns. > > > > Hmm, what I want is to get srm (or at least rtp) running in an ad > > hoc WLAN. I am not talking about multihop routing in ad hoc nets. > > I guess I did not make the correct question. I am sorry. Anyway, > > would any of these multicast routing protocols make srm work > > on ad hoc nets? > > Yes. If my memory is not wrong, I ran a few ad hoc networking > simulations with srm + maodv patch + ns 2.26. Well, well, this is Bach to my years. I will try right now. If you happen to find that piece of code, and wish to share it, please let me know. Thank you very much for your time. > > When I use mobilenodes and srm I get: > > > > $ns wsrm.tcl > > num_nodes is set 1 > > INITIALIZE THE LIST xListHead > > Starting Simulation... > > channel.cc:sendUp - Calc highestAntennaZ_ and distCST_ > > highestAntennaZ_ = 1.5, distCST_ = 550.0 > > SORTING LISTS ...DONE! > > ns: _o19 new-group 0 -2147483648 -1 cache-miss: can't read > > "protocols_(-1)": no such variable > > while executing > > "$protocols_($iface) upcall $code $source $group $iface" > > (procedure "_o20" line 9) > > (mrtObject upcall line 9) > > invoked from within > > "$mrtObject_ upcall $code $src $group $iface" > > (procedure "_o14" line 3) > > (Node new-group line 3) > > invoked from within > > "$node_ new-group $src $group $iface $code" > > (procedure "_o19" line 3) > > (Classifier/Multicast new-group line 3) > > invoked from within > > "_o19 new-group 0 -2147483648 -1 cache-miss" > > > > > > I grepped for "protocols_" and found many entries in > > ns-2.27/tcl/mcast/McastProto.tcl, but nowhere else. > > > > I have found at least 6 other posts since 2001 reporting the > > same or very similar problems. Any ideas? Would maodv or > > odrmp solve this problem? > > > > > > Hi everyone, > > > > > > > > Does NS (ns-allinone-2.27) support multicast traffic in ad hoc WLANs? > > > > If it does > > > > please tell me how, give me a link, whatever! > > > > else > > > > can you please suggest an alternative simulator? _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 8 21:44:48 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05670 for ; Mon, 8 Nov 2004 21:44:48 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRM0h-0005z5-D1 for manet-web-archive@ietf.org; Mon, 08 Nov 2004 21:45:31 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRLit-00025Z-N5; Mon, 08 Nov 2004 21:27:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRLej-0008OL-SJ for manet@megatron.ietf.org; Mon, 08 Nov 2004 21:22:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03854 for ; Mon, 8 Nov 2004 21:22:47 -0500 (EST) Received: from [203.199.83.247] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRLfD-0005ZG-OE for manet@ietf.org; Mon, 08 Nov 2004 21:23:30 -0500 Received: (qmail 30962 invoked by uid 510); 9 Nov 2004 02:22:03 -0000 Date: 9 Nov 2004 02:22:03 -0000 Message-ID: <20041109022203.30961.qmail@mailweb34.rediffmail.com> Received: from unknown (203.208.193.230) by rediffmail.com via HTTP; 09 nov 2004 02:22:03 -0000 MIME-Version: 1.0 From: "gokina " To: manet@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Subject: [manet] Research in WSN X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gokina List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1389161633==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 This is a multipart mime message --===============1389161633== Content-type: multipart/alternative; boundary="Next_1099966923---0-203.199.83.247-30957" This is a multipart mime message --Next_1099966923---0-203.199.83.247-30957 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0AHi,
=0A I want to discuss one particular topic in Wi= reless Sensor Networks. Several routing protocols have been proposed. Total= ly independent of this, several researchers have also focussed on developin= g energy efficient MAC protocols for sensor networks. To be more clear, the= routing protocols assume 802.11 based MAC protocol. I want to know, if any= research has been done in this direction. I am thinking if we can provide = smooth integration of currently incompatible MAC protocols and routing prot= ocols.
=0A
=0A Kindly let me know, if anybody in this group is workin= g in this direction. I request the members to give me some references in th= is direction.
=0A
=0ALooking forward for your suggestions,
=0AGoki= na.=0A

=0A

=0A=0A --Next_1099966923---0-203.199.83.247-30957 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0=0AHi,=0A I want to discuss one particular topic in Wireless Sensor Net= works. Several routing protocols have been proposed. Totally independent of= this, several researchers have also focussed on developing energy efficien= t MAC protocols for sensor networks. To be more clear, the routing protocol= s assume 802.11 based MAC protocol. I want to know, if any research has bee= n done in this direction. I am thinking if we can provide smooth integratio= n of currently incompatible MAC protocols and routing protocols.=0A=0A Kind= ly let me know, if anybody in this group is working in this direction. I re= quest the members to give me some references in this direction.=0A=0ALookin= g forward for your suggestions,=0AGokina. --Next_1099966923---0-203.199.83.247-30957-- --===============1389161633== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1389161633==-- From manet-bounces@ietf.org Mon Nov 8 21:48:31 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05988 for ; Mon, 8 Nov 2004 21:48:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRM4H-00064L-TH for manet-web-archive@ietf.org; Mon, 08 Nov 2004 21:49:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRM1M-0006oG-Bz; Mon, 08 Nov 2004 21:46:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRLkH-0002IZ-Px for manet@megatron.ietf.org; Mon, 08 Nov 2004 21:28:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04542 for ; Mon, 8 Nov 2004 21:28:31 -0500 (EST) Received: from [202.30.0.18] (helo=mail.ajou.ac.kr) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRLkv-0005fu-Na for manet@ietf.org; Mon, 08 Nov 2004 21:29:14 -0500 Received: from seodang.ajou.ac.kr ([202.30.0.9]) by maru (Crinity Message Backbone-2.6.23.1) with SMTP ID 441 for ; Tue, 9 Nov 2004 10:43:36 +0900 (KST) Message-ID: <01a501c4c5fd$9e402c20$bbcb6bd2@ajoudayhakyu> From: Faisal Adeem Siddiqui To: manet@ietf.org Date: Tue, 9 Nov 2004 10:44:14 +0900 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 0.5 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Subject: [manet] End-to-End Mobility in MANETs X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1328537454==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c This is a multi-part message in MIME format. --===============1328537454== Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A2_01C4C649.0E20A830" This is a multi-part message in MIME format. ------=_NextPart_000_01A2_01C4C649.0E20A830 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi everyone, I've seen papers on mobility management between MANET nodes and internet = connected nodes (can be of other MANET) but these schemes are based on = MIPv6. I want to know if there are publications on end-to-end mobility = management in MANETs ?=20 Thanks in advance. Faysal. ------=_NextPart_000_01A2_01C4C649.0E20A830 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi everyone,
I've seen papers on mobility = management=20 between MANET nodes and internet connected nodes (can be of other = MANET)=20 but these schemes are based on MIPv6. I want to know if there are = publications=20 on end-to-end mobility management in MANETs ?
 
Thanks in = advance.
Faysal.
------=_NextPart_000_01A2_01C4C649.0E20A830-- --===============1328537454== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1328537454==-- From manet-bounces@ietf.org Tue Nov 9 04:04:54 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02736 for ; Tue, 9 Nov 2004 04:04:54 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRRwZ-0005mU-Rw for manet-web-archive@ietf.org; Tue, 09 Nov 2004 04:05:41 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRRic-0007qg-M5; Tue, 09 Nov 2004 03:51:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRRf6-0007DK-FL for manet@megatron.ietf.org; Tue, 09 Nov 2004 03:47:36 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01225 for ; Tue, 9 Nov 2004 03:47:34 -0500 (EST) Received: from web53906.mail.yahoo.com ([206.190.36.216]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRRff-0005FI-Fp for manet@ietf.org; Tue, 09 Nov 2004 03:48:21 -0500 Received: (qmail 3280 invoked by uid 60001); 9 Nov 2004 08:46:55 -0000 Message-ID: <20041109084655.3278.qmail@web53906.mail.yahoo.com> Received: from [81.31.160.4] by web53906.mail.yahoo.com via HTTP; Tue, 09 Nov 2004 00:46:55 PST Date: Tue, 9 Nov 2004 00:46:55 -0800 (PST) From: Ehsan Ataie To: ns-users@ISI.EDU MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 3.0 (+++) X-Scan-Signature: d6b246023072368de71562c0ab503126 Cc: manet@ietf.org Subject: [manet] link lenght and link optimization X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 3.0 (+++) X-Scan-Signature: 93238566e09e6e262849b4f805833007 hi, is there any way for calculating link optimization with ns2 in an ad hoc routing protocol? in other words, i want to know the lenght of a link between a source and its destination in e.g. DSR protocol and also the lenght of the optimized link between those nodes. thanks in advanced. Ehsan __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 9 04:21:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04094 for ; Tue, 9 Nov 2004 04:21:50 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRSCz-00069X-Bd for manet-web-archive@ietf.org; Tue, 09 Nov 2004 04:22:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRS4j-0003fc-Hc; Tue, 09 Nov 2004 04:14:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRS3Y-0003W5-2k for manet@megatron.ietf.org; Tue, 09 Nov 2004 04:12:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03490 for ; Tue, 9 Nov 2004 04:12:49 -0500 (EST) Received: from [203.200.31.190] (helo=juke.msrit.edu) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRS46-0005xU-0M for manet@ietf.org; Tue, 09 Nov 2004 04:13:36 -0500 Received: (qmail 21675 invoked by uid 89); 9 Nov 2004 09:18:09 -0000 Message-ID: <20041109091809.21674.qmail@juke.msrit.edu> From: "Shekhar H M P" To: manet@ietf.org Date: Tue, 09 Nov 2004 14:48:09 +0530 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8" Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Content-Transfer-Encoding: 7bit Subject: [manet] DSR & RED Problems in ns-2.26 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Content-Transfer-Encoding: 7bit Dear All, We have problems in wireless ad hoc network simulation with the following in ns-2.26: * DSR is not working and it gives segmentation error when tcl script is run * Also, RED is not working. What to do? Kindly reply.... With Regards, Shekhar H M P Assistant Professor, Wireless Networking Laboratory, Department of Computer Science & Engg., M S Ramaiah Institute of Technology, Banglore - 560 054, INDIA. Alternate E-mail: shekhar_hmp@yahoo.com Ph: 91+ 80 2360 0822 Ext. 143. Mobile No.: 98450 16280 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 9 06:31:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13710 for ; Tue, 9 Nov 2004 06:31:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRUE5-0000G9-Oa for manet-web-archive@ietf.org; Tue, 09 Nov 2004 06:31:56 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRUA0-0003Aw-RD; Tue, 09 Nov 2004 06:27:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRU6p-0002vo-Go for manet@megatron.ietf.org; Tue, 09 Nov 2004 06:24:23 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13301 for ; Tue, 9 Nov 2004 06:24:20 -0500 (EST) Received: from smtp.andrew.cmu.edu ([128.2.10.82]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRU7Z-00009G-4W for manet@ietf.org; Tue, 09 Nov 2004 06:25:09 -0500 Received: from [192.168.2.101] (h-67-101-138-182.phlapafg.dynamic.covad.net [67.101.138.182]) (user=dmaltz mech=KERBEROS_V4 (0 bits)) by smtp.andrew.cmu.edu (8.12.10/8.12.10) with ESMTP id iA9BOM5h005644; Tue, 9 Nov 2004 06:24:22 -0500 Date: Tue, 09 Nov 2004 06:24:54 -0500 From: Dave Maltz To: Ehsan Ataie , ns-users@ISI.EDU Subject: Re: [manet] link lenght and link optimization Message-ID: <291763393.1099981494@[192.168.2.101]> In-Reply-To: <20041109084655.3278.qmail@web53906.mail.yahoo.com> References: <20041109084655.3278.qmail@web53906.mail.yahoo.com> Originator-Info: login-token=Mulberry:018N+03FRMFUg2ZANTO18rS0M8Kwh2SkEeQiFR8E8nZQ==; token_authority=postmaster@andrew.cmu.edu X-Mailer: Mulberry/3.0.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.2 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: 7bit --On Tuesday, November 09, 2004 12:46 AM -0800 Ehsan Ataie wrote: > is there any way for calculating link optimization > with ns2 in an ad hoc routing protocol? in other > words, i want to know the lenght of a link between a > source and its destination in e.g. DSR protocol and > also the lenght of the optimized link between those > nodes. If you created your mobility traces using setdest, then the trace file probably already contains "god" information, which gives the shortest number of hops between two nodes at that point in time. If your trace conforms to the expected format, you can use calcdest to add god information to a trace constructed using other means (e.g., another program such as ad-hockey) You can then compare the number of hops a packet took with the shortest number of hops that existed at that time. Caveats: 1) the "shortest number of hops" is calculated assuming the successful transmission range is a perfect circle of some pre-set radius. This is a simplification of both the real world and how the simulator calculates successful receptions. 2) in a congested network, packets can be stuck in interface queues long enough that the nodes move substantially between when a packet is originated and when it is finally received at its destination. This can cause packets to appear to take *less* than the shortest number of hops. Cheers, -dam _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 9 09:21:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00868 for ; Tue, 9 Nov 2004 09:21:57 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRWtR-0004nO-SQ for manet-web-archive@ietf.org; Tue, 09 Nov 2004 09:22:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRWhr-0001aq-Lp; Tue, 09 Nov 2004 09:10:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRWar-00027X-HN for manet@megatron.ietf.org; Tue, 09 Nov 2004 09:03:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28621 for ; Tue, 9 Nov 2004 09:03:31 -0500 (EST) Received: from [203.199.83.135] (helo=rediffmail.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRWbY-0004Go-S8 for manet@ietf.org; Tue, 09 Nov 2004 09:04:20 -0500 Received: (qmail 19656 invoked by uid 510); 9 Nov 2004 14:02:55 -0000 Date: 9 Nov 2004 14:02:55 -0000 Message-ID: <20041109140255.19655.qmail@webmail45.rediffmail.com> Received: from unknown (203.208.193.230) by rediffmail.com via HTTP; 09 nov 2004 14:02:55 -0000 MIME-Version: 1.0 From: "gokina " To: manet@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Subject: [manet] Research Project X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gokina List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0409610590==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 This is a multipart mime message --===============0409610590== Content-type: multipart/alternative; boundary="Next_1100008975---0-203.199.83.135-19645" This is a multipart mime message --Next_1100008975---0-203.199.83.135-19645 Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable =A0=0AHi,=0A My research interests are in Mobile Ad-hoc Networks, Sensor N= etworks and Peer-to-Peer Networks. I got a good understanding of the resear= ch work done in my areas of inteerest. I want to demonstrate, my capability= of research by doing a research project.=0A=0AIf research is all about und= erstanding the publications, finding out the deficiencies of the existing i= deas, and developing new ideas showing an improvement over the existing ide= as, then I have the capabiity to do that. Definitely, there are some open c= hallenging problems. I have the capability to understand the publications a= nd analyze them. I want to do a survey on some topic in my areas of interes= t and make a significant contribution in the project.=0A=0AI want to know, = if it is possible for anyone in this group to consider my request. I am con= fident, I can contribute beyond your expectation in the project.=0A=0AWaiti= ng for your reply,=0AGokina. =0A --Next_1100008975---0-203.199.83.135-19645 Content-type: text/html; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable

=0A 
=0AHi,
=0A My research interests are in Mobile Ad-hoc N= etworks, Sensor Networks and Peer-to-Peer Networks. I got a good understand= ing of the research work done in my areas of inteerest. I want to demonstra= te, my capability of research by doing a research project.
=0A
=0AIf = research is all about understanding the publications, finding out the defic= iencies of the existing ideas, and developing new ideas showing an improvem= ent over the existing ideas, then I have the capabiity to do that. Definite= ly, there are some open challenging problems. I have the capability to unde= rstand the publications and analyze them. I want to do a survey on some top= ic in my areas of interest and make a significant contribution in the proje= ct.
=0A
=0AI want to know, if it is possible for anyone in this group= to consider my request. I am confident, I can contribute beyond your expec= tation in the project.
=0A
=0AWaiting for your reply,
=0AGokina. <= BR>=0A=0A

=0A

=0A=0A --Next_1100008975---0-203.199.83.135-19645-- --===============0409610590== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0409610590==-- From manet-bounces@ietf.org Tue Nov 9 09:58:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04571 for ; Tue, 9 Nov 2004 09:58:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRXSx-0005g6-9z for manet-web-archive@ietf.org; Tue, 09 Nov 2004 09:59:28 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRXKe-0003Ot-FH; Tue, 09 Nov 2004 09:50:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRXDH-0001c6-Aa for manet@megatron.ietf.org; Tue, 09 Nov 2004 09:43:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02969 for ; Tue, 9 Nov 2004 09:43:13 -0500 (EST) Received: from ms-smtp-03-lbl.southeast.rr.com ([24.25.9.102] helo=ms-smtp-03-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRXE2-0005JF-KW for manet@ietf.org; Tue, 09 Nov 2004 09:44:02 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-03-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iA9Eh0kc026433; Tue, 9 Nov 2004 09:43:05 -0500 (EST) From: "Christopher P. Rigano" To: "'Faisal Adeem Siddiqui'" , Subject: RE: [manet] End-to-End Mobility in MANETs Date: Tue, 9 Nov 2004 09:42:56 -0500 Message-ID: <000001c4c66a$675a4a20$0600a8c0@CPQ73745201364> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal In-Reply-To: <01a501c4c5fd$9e402c20$bbcb6bd2@ajoudayhakyu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.7 (/) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1668379976==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.0 (+) X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 This is a multi-part message in MIME format. --===============1668379976== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C4C640.7E844220" This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C4C640.7E844220 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings, My interestes are similar, but focous on the capability to maintain a connection/media stream when a node moves fro one MANET to another. Is this acomplished through a combination of proactive and on demand routing? thanks and regards, Chris -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Faisal Adeem Siddiqui Sent: Monday, November 08, 2004 8:44 PM To: manet@ietf.org Subject: [manet] End-to-End Mobility in MANETs Hi everyone, I've seen papers on mobility management between MANET nodes and internet connected nodes (can be of other MANET) but these schemes are based on MIPv6. I want to know if there are publications on end-to-end mobility management in MANETs ? Thanks in advance. Faysal. ------=_NextPart_000_0001_01C4C640.7E844220 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Greetings,
 
My=20 interestes are similar, but focous on the capability to maintain a=20 connection/media stream when a node moves fro one MANET to another. Is = this=20 acomplished through a combination of proactive and on demand=20 routing?
 
thanks=20 and regards,
 
Chris
-----Original Message-----
From:=20 manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of = Faisal Adeem Siddiqui
Sent: Monday, November 08, 2004 = 8:44=20 PM
To: manet@ietf.org
Subject: [manet] End-to-End = Mobility=20 in MANETs

Hi everyone,
I've seen papers on = mobility management=20 between MANET nodes and internet connected nodes (can be of other = MANET)=20 but these schemes are based on MIPv6. I want to know if there are = publications=20 on end-to-end mobility management in MANETs ?
 
Thanks in = advance.
Faysal.
------=_NextPart_000_0001_01C4C640.7E844220-- --===============1668379976== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1668379976==-- From manet-bounces@ietf.org Tue Nov 9 10:05:16 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05659 for ; Tue, 9 Nov 2004 10:05:16 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRXZN-0005t4-Jf for manet-web-archive@ietf.org; Tue, 09 Nov 2004 10:06:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRXTD-0005LK-9E; Tue, 09 Nov 2004 09:59:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRXMK-00043L-Td for manet@megatron.ietf.org; Tue, 09 Nov 2004 09:52:36 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03974 for ; Tue, 9 Nov 2004 09:52:34 -0500 (EST) Received: from dcs-server2.cs.uiuc.edu ([128.174.252.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRXN6-0005Y0-CZ for manet@ietf.org; Tue, 09 Nov 2004 09:53:24 -0500 Received: from brooklyn (brooklyn.cs.uiuc.edu [128.174.244.80]) (authenticated bits=0) by dcs-server2.cs.uiuc.edu (8.12.10/8.12.10) with ESMTP id iA9EqYhh028000 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 9 Nov 2004 08:52:35 -0600 (CST) Message-Id: <200411091452.iA9EqYhh028000@dcs-server2.cs.uiuc.edu> From: "Robin Kravets" To: Date: Tue, 9 Nov 2004 08:50:29 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcTGa3Sk90PsxNAaSRiNMGYvxE7P3Q== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab Content-Transfer-Encoding: quoted-printable Subject: [manet] ACM MobiHoc 2005 - Call For Papers X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c Content-Transfer-Encoding: quoted-printable We apologize in advance if you receive multiple copies of this CFP. ---------------------------------------------------------------------- Call for Papers MobiHoc 2005=20 6th ACM International Symposium on=20 Mobile Ad Hoc Networking and Computing=20 May 25-28, 2005 Urbana-Champaign, Illinois, USA=20 http://www.sigmobile.org/mobihoc/2005/=20 Sponsored by ACM SIGMOBILE=20 ACM MobiHoc is the premier international meeting dedicated to addressing challenges emerging from wireless ad hoc networking and computing. Due = to the growing interest in the field this year's symposium will have an expanded format that will include a highly selective, dual-track = technical program for the first time, as well as hands-on research demonstrations, keynote, panel, and tutorials. We invite paper, poster, and demonstration submissions on mobile ad hoc networks, wireless sensor networks, and ad hoc computing systems, with = the focus being on issues at and above the MAC layer. Areas of interest = include, but are not limited to: Applications, operating system, and middleware support=20 Analysis and design of transport, network, and MAC protocols=20 Energy-efficient algorithms =20 Location discovery and management techniques=20 Network scaling and limits=20 Measurements and practical experience from experimental systems and = testbeds Cross layer design=20 Network resilience, fault-tolerance, and reliability=20 Security and defense issues=20 In-network processing, aggregation and data dissemination=20 Distributed actuation, control, and coordination Modeling, performance evaluation, and QoS issues=20 PAPERS: Papers must report new results substantiated by experimentation, = simulation, or analysis. All submissions will be handled electronically and must be = in PDF format. Papers must not exceed 12 pages (US letter size, 8.5 =F011 = inches) including text, figures and references. The font size must be at least = 10 points. Accepted papers will be published in the symposium proceedings. = All submitted papers are judged based on their quality through double -blind reviewing, where the identities of the authors are withheld from the reviewers. Authors' names must not appear in the paper or in the PDF = file. Submitted papers must not be currently under review for any other publication. Detailed instructions on paper submission and formatting = are available here. Please direct any questions about the paper submission process to the Program Co-Chairs Andrew T. Campbell , and Roger Wattenhofer . POSTERS: Posters presenting early work and preliminary results are solicited. The poster session will provide an excellent opportunity for initial = feedback on early research results. Poster descriptions, of no more than 3 pages, = using font size 10 on 8.5x11in size paper, should be submitted to the Poster Co-Chairs Songwu Lu and Saswati Sarkar before April 1, 2005. Please include the words "Poster Abstract:" to precede the title on the cover page. A selected = subset of poster abstracts will be published in ACM Mobile Computing and Communications Review.=20 DEMOS: Technical demonstration of experimental ad hoc networking and computing systems are solicited. One-page demo descriptions, including a list of = any required supporting equipment, should be sent to the Demo Chair Scott R. Graham before March 1, 2005. TUTORIALS: Proposals for tutorials are solicited. Evaluation of proposals will be = based on the expertise and experience of the instructors, and on the relevance = of the subject matter. Potential instructors are requested to submit a = tutorial proposal of at most 5 pages, including a biographical sketch, to the Tutorial Co-Chairs Bhaskar Krishnamachari and Richard = J. La before Jan. 15, 2005. PANELS: Panels are solicited that examine innovative, controversial, or = otherwise provocative issues of interest. Panel proposals should not exceed 2 = pages, including biographical sketches of the panelists. Potential panel = organizers should contact the General Chair P. R. Kumar before December 15, 2004. =20 IMPORTANT DATES: Paper Registration Deadline: =20 December 13, 2004 (5PM US EST)=20 =20 Paper Submission Deadline: December 20, 2004 (5PM US EST) =20 Notification of Acceptance: March 27, 2005 =20 Camera-Ready Version Due: April 10, 2005 =20 For more information contact the General Chair or consult the symposium webpage. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 9 20:18:26 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06694 for ; Tue, 9 Nov 2004 20:18:26 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRh8r-0003rP-CZ for manet-web-archive@ietf.org; Tue, 09 Nov 2004 20:19:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRh10-0008Dw-C6; Tue, 09 Nov 2004 20:11:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRh04-00086U-5h for manet@megatron.ietf.org; Tue, 09 Nov 2004 20:10:16 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06086 for ; Tue, 9 Nov 2004 20:10:14 -0500 (EST) Received: from gateway.scalable-networks.com ([63.205.33.202] helo=mithrandir.scalable-networks.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRh0s-0003is-6e for manet@ietf.org; Tue, 09 Nov 2004 20:11:09 -0500 Received: (qmail 11864 invoked by uid 1046); 10 Nov 2004 01:13:46 -0000 Received: from mineo@cs.ucla.edu by mithrandir by uid 2850 with qmail-scanner-1.20 (clamscan: 0.67. Clear:RC:0(68.127.37.105):. Processed in 0.034529 secs); 10 Nov 2004 01:13:46 -0000 Received: from adsl-68-127-37-105.dsl.irvnca.pacbell.net (HELO ?127.0.0.1?) (sssmail@68.127.37.105) by mithrandir.scalable-networks.com with SMTP; 10 Nov 2004 01:13:46 -0000 Message-ID: <41916A5F.6010102@cs.ucla.edu> Date: Tue, 09 Nov 2004 17:09:51 -0800 From: Mineo Takai User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, ja MIME-Version: 1.0 To: Gerry Holderbeke Subject: Re: [manet] Glomosim in real-time References: <418B3A49.8000600@intec.ugent.be> In-Reply-To: <418B3A49.8000600@intec.ugent.be> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.1 (+) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 7bit Hello Gerry, You might find one of our papers interesting: "MAYA: Integrating Hybrid Network Modeling to the Physical World," Junlan Zhou, Zhengrong Ji, Mineo Takai, and Rajive Bagrodia. ACM Transactions on Modeling and Computer Simulation, v.14 n.2 p.149-169, April 2004. http://pcl.cs.ucla.edu/papers/files/tomacs-04.pdf The paper describes how we run discrete-event simulators like GloMoSim in real time, or in other words, how we synchronize them with real networks in order to allow packet exchanges between simulated and operational physical networks without timing errors. Best, Mineo Gerry Holderbeke wrote: > Hi Everyone, > > Does anyone of you has any experience in making discrete-event > simulators, for example Glomosim or others, run in real time ? Any > information is welcome ! > > Thanks in advance, > Gerry > > > INTEC, Information Technology > University of Ghent > Belgium > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 10 02:17:19 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA18826 for ; Wed, 10 Nov 2004 02:17:18 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRmkC-0002Jr-St for manet-web-archive@ietf.org; Wed, 10 Nov 2004 02:18:17 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRmg2-0000sq-8t; Wed, 10 Nov 2004 02:13:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRmdw-0008TW-Qk for manet@megatron.ietf.org; Wed, 10 Nov 2004 02:11:48 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA13962 for ; Wed, 10 Nov 2004 02:11:47 -0500 (EST) Received: from web14707.mail.yahoo.com ([216.136.224.124]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRmeq-0002Ch-2F for manet@ietf.org; Wed, 10 Nov 2004 02:12:45 -0500 Received: (qmail 67884 invoked by uid 60001); 10 Nov 2004 07:11:45 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=py2o1NPSLQZieCDj/Eb3GpzUpTZe3h0g3PFDqX5WPXX94U8Af7h/z+1cIbqtfToz5Fo1PmCroU5DMNsW7mVI6ixqXBBo1kjyHWSTMWMTGri2wsLKPgxzgQXe7MKSxey79ll6kxBAjDeMTzwRnXZXyZUmgY7axghIWuZoYRPR404= ; Message-ID: <20041110071145.67882.qmail@web14707.mail.yahoo.com> Received: from [217.29.240.34] by web14707.mail.yahoo.com via HTTP; Tue, 09 Nov 2004 23:11:45 PST Date: Tue, 9 Nov 2004 23:11:45 -0800 (PST) From: mazen alhasan To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 2.2 (++) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Subject: [manet] request X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0992942957==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 2.2 (++) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 --===============0992942957== Content-Type: multipart/alternative; boundary="0-1704722692-1100070705=:60809" --0-1704722692-1100070705=:60809 Content-Type: text/plain; charset=us-ascii hi every one,i want glomosim simulater --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --0-1704722692-1100070705=:60809 Content-Type: text/html; charset=us-ascii
hi every one,i want glomosim simulater

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com --0-1704722692-1100070705=:60809-- --===============0992942957== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0992942957==-- From manet-bounces@ietf.org Wed Nov 10 09:08:49 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09838 for ; Wed, 10 Nov 2004 09:08:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRtAU-0002jC-0t for manet-web-archive@ietf.org; Wed, 10 Nov 2004 09:09:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRt2z-00056r-12; Wed, 10 Nov 2004 09:02:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRsuQ-0003kV-1n for manet@megatron.ietf.org; Wed, 10 Nov 2004 08:53:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08402 for ; Wed, 10 Nov 2004 08:53:12 -0500 (EST) Received: from web60002.mail.yahoo.com ([216.109.116.225]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRsvN-0002ML-0o for manet@ietf.org; Wed, 10 Nov 2004 08:54:14 -0500 Received: (qmail 76008 invoked by uid 60001); 10 Nov 2004 13:52:41 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=EC8RM8th8SAXoM+/HARBvDczxx1wQHXZvQeHwKmp5YypfQI71uOqwtK1z86EKMGcq2b0d884ZaA8+J3JqRGSw7S7RQtAZU1uUSVOhZBphr2AvcPK9icohlSs5Mg87J2rTLqVOyxysp9/4GgWCFIFbbM0761tSwbPpJSDBgYfJQc= ; Message-ID: <20041110135240.76006.qmail@web60002.mail.yahoo.com> Received: from [202.141.142.23] by web60002.mail.yahoo.com via HTTP; Wed, 10 Nov 2004 05:52:40 PST Date: Wed, 10 Nov 2004 05:52:40 -0800 (PST) From: Shahriar Shamil Uulu To: manet@ietf.org, ns-users@ISI.EDU MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Subject: [manet] Generating Selfishness in manet X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Hi Everybody, I would like to test a "Selfishness" problem in Mobile Ad hoc networks. Does anybody know how i can do that. Please help me, any help will be apperciated. Thank you in advance ===== Shahriar Shamil Uulu Hyderabad Central University M.Tech(Computer Science) email:shamilsons@yahoo.com website: http://shamilson.narod.ru __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 10 10:48:00 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22472 for ; Wed, 10 Nov 2004 10:48:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRuiV-0005RA-D5 for manet-web-archive@ietf.org; Wed, 10 Nov 2004 10:49:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRudH-0006sF-BL; Wed, 10 Nov 2004 10:43:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRuSe-0004Zu-A3 for manet@megatron.ietf.org; Wed, 10 Nov 2004 10:32:40 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20646 for ; Wed, 10 Nov 2004 10:32:37 -0500 (EST) Received: from web20923.mail.yahoo.com ([216.136.224.137]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRuTb-000542-Mf for manet@irtf.org; Wed, 10 Nov 2004 10:33:41 -0500 Received: (qmail 87648 invoked by uid 60001); 10 Nov 2004 15:32:36 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=CVm7882+usJU6lqxVncdBh84dymBaLFOOYPyaooBf6yXptKYle+6KGrE98whAWr34jqAJq2iikF/+BTkXi1iZN16KZGplkZ0IDnMJHCMLG+LnkEdck3hjmvIdiTxpgBOtUZ6cfYFaN1mejHtjcf9Gt9aXxQo9opeARYT1CqnGrI= ; Message-ID: <20041110153236.87646.qmail@web20923.mail.yahoo.com> Received: from [203.208.193.230] by web20923.mail.yahoo.com via HTTP; Wed, 10 Nov 2004 07:32:36 PST Date: Wed, 10 Nov 2004 07:32:36 -0800 (PST) From: Praveen Choudary To: manet@irtf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Subject: [manet] MAC protocol in WSN X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0590644917==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c --===============0590644917== Content-Type: multipart/alternative; boundary="0-197739241-1100100756=:87361" --0-197739241-1100100756=:87361 Content-Type: text/plain; charset=us-ascii Hi, I am Praveen, final year undergraduate ( Computer Science & Engineering) from Indian School of Mines, India. I have one doubt related to MAC protocol in Sensor Networks. I want the members to have a look at this publication " C. Lu, B. Blum, T. Abdelzaher, J. Stankovic, and T. He, "RAP: A Real-Time Communication Architecture for Large-Scale Wireless Sensor Networks", Proceedings of IEEE Real-Time and Embedded Technology and Applications Symposium (RTAS 2002), San Jose, CA, USA, September 2002". In this publication, the point in my interest is " MAC protocol should provide distributed prioritization on packets from different nodes". Extensions of the IEEE 802.11 wireless LAN protocol have been investigated to provide distributed prioritization. S-MAC is better than 802.11 for Wireless Sensor Networks. I want to know, can we suggest any modification for S-MAC (or any other sensor MAC), so that it can be used with the kind of routing protocol given in the reference. I hope this extension can be useful to other related routing protocols. I am doing research on my own. I request the members of this group who are working in this area to give their comments. Kindly, let me know if I am thinking in the right direction. Looking forward for your reply, Sincerely, Praveen. --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --0-197739241-1100100756=:87361 Content-Type: text/html; charset=us-ascii
Hi,
 I am Praveen, final year undergraduate ( Computer Science & Engineering) from Indian School of Mines, India. I have one doubt related to MAC protocol in Sensor Networks.
 
I want the members to have a look at this publication
 
 " C. Lu, B. Blum, T. Abdelzaher, J. Stankovic, and T. He, "RAP: A Real-Time Communication Architecture for Large-Scale Wireless Sensor Networks", Proceedings of IEEE Real-Time and Embedded Technology and Applications Symposium (RTAS 2002), San Jose, CA, USA, September 2002".
 
In this publication, the point in my interest is " MAC protocol should provide distributed prioritization on packets from different nodes". Extensions of the IEEE 802.11 wireless LAN protocol have been investigated to provide distributed prioritization.
 
S-MAC is better than 802.11 for Wireless Sensor Networks. I want to know, can we suggest any modification for S-MAC (or any other sensor MAC), so that it can be used with the kind of routing protocol given in the reference. I hope this extension can be useful to other related routing protocols.
 
I am doing research on my own. I request the members of this group who are working in this area to give their comments. Kindly, let me know if I am thinking in the right direction.
 
Looking forward for your reply,
Sincerely,
Praveen.

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com --0-197739241-1100100756=:87361-- --===============0590644917== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0590644917==-- From manet-bounces@ietf.org Wed Nov 10 11:52:16 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29936 for ; Wed, 10 Nov 2004 11:52:16 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRvii-0007Gi-2d for manet-web-archive@ietf.org; Wed, 10 Nov 2004 11:53:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRvZZ-0006fQ-7e; Wed, 10 Nov 2004 11:43:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRvXa-0006Er-EL for manet@megatron.ietf.org; Wed, 10 Nov 2004 11:41:50 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28664 for ; Wed, 10 Nov 2004 11:41:47 -0500 (EST) Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRvYZ-0006xD-Gt for manet@ietf.org; Wed, 10 Nov 2004 11:42:52 -0500 Received: from [192.168.2.19] (lina23.tts.lth.se [130.235.18.83]) by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id RAA16925 for ; Wed, 10 Nov 2004 17:41:03 +0100 (MET) Message-ID: <41924483.6070405@telecom.lth.se> Date: Wed, 10 Nov 2004 17:40:35 +0100 From: Ali Hamidian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit Subject: [manet] reliable broadcast frames in 802.11 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7bit Hi, I wonder if there is any work on reliable broadcast messages at the MAC layer, e.g. a proposed extension/enhancement to 802.11. With reliable I mean that the sender of a broadcast MAC frame can be sure that all its neighbors receive the broadcast MAC frame. Regards Ali _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 10 14:17:58 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15462 for ; Wed, 10 Nov 2004 14:17:58 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRxzf-0002Sc-AA for manet-web-archive@ietf.org; Wed, 10 Nov 2004 14:19:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRxrJ-0002SD-Ui; Wed, 10 Nov 2004 14:10:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRxls-0000i8-LD for manet@megatron.ietf.org; Wed, 10 Nov 2004 14:04:44 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13870 for ; Wed, 10 Nov 2004 14:04:43 -0500 (EST) Received: from web25810.mail.ukl.yahoo.com ([217.12.10.195]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CRxmd-00022w-AB for manet@ietf.org; Wed, 10 Nov 2004 14:05:47 -0500 Received: (qmail 60305 invoked by uid 60001); 10 Nov 2004 19:03:56 -0000 Message-ID: <20041110190356.60300.qmail@web25810.mail.ukl.yahoo.com> Received: from [194.145.62.45] by web25810.mail.ukl.yahoo.com via HTTP; Wed, 10 Nov 2004 19:03:56 GMT Date: Wed, 10 Nov 2004 19:03:56 +0000 (GMT) From: =?iso-8859-1?q?V=EDtor=20Jesus?= Subject: Re: [manet] Generating Selfishness in manet To: Shahriar Shamil Uulu In-Reply-To: <20041110135240.76006.qmail@web60002.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id OAA13870 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Content-Transfer-Encoding: quoted-printable Depending on what you mean by a selfish node, you could modify the ns-2 code so that some nodes *don't* forward packets. That's a selfish greedy node for me. Hope it helps. --v=EDtor --- Shahriar Shamil Uulu wrote:=20 > Hi Everybody, > I would like to test a "Selfishness" problem in > Mobile > Ad hoc networks. Does anybody know how i can do > that. > Please help me, any help will be apperciated. > Thank you in advance =20 >=20 > =3D=3D=3D=3D=3D > Shahriar Shamil Uulu=20 > Hyderabad Central University=20 > M.Tech(Computer Science) > email:shamilsons@yahoo.com > website: http://shamilson.narod.ru >=20 > =20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > =09 > __________________________________=20 > Do you Yahoo!?=20 > Check out the new Yahoo! Front Page.=20 > www.yahoo.com=20 > =20 >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > =20 =09 =09 =09 ___________________________________________________________=20 ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.me= ssenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 10 16:15:31 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04274 for ; Wed, 10 Nov 2004 16:15:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRzp1-0007XQ-Gp for manet-web-archive@ietf.org; Wed, 10 Nov 2004 16:16:38 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRzZ1-0002ih-Tb; Wed, 10 Nov 2004 15:59:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRzMi-0000jz-Rn for manet@megatron.ietf.org; Wed, 10 Nov 2004 15:46:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28438 for ; Wed, 10 Nov 2004 15:46:50 -0500 (EST) Received: from [210.125.184.35] (helo=smf.uos.ac.kr) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRzLx-0005Ue-8k for manet@ietf.org; Wed, 10 Nov 2004 15:47:56 -0500 Received: from external ([203.249.110.25]) by smf.uos.ac.kr (1.0) id iAAKeOH00100; Thu, 11 Nov 2004 05:40:24 +0900 X-SMF-UNIQ9EDA4EDC67F1B84C606C3D35C8DEF05D: iAAKeOH00100 Received: from venus.uos.ac.kr (localhost [127.0.0.1]) by venus.uos.ac.kr (8.12.3/8.12.3/Debian -4) with ESMTP id iAAKhQD1028350; Thu, 11 Nov 2004 05:43:26 +0900 From: "=?EUC-KR?Q?=BE=C8=BB=F3=C7=F6?=" To: manet@ietf.org;macker@itd.nrl.navy.mil;;;; Subject: [manet] draft on duplicate packet detection Date: Thu, 11 Nov 2004 05:43:26 +0900 Message-Id: <20041110204119.M39955@venus.uos.ac.kr> X-Mailer: Open WebMail 1.90 20030212 X-OriginatingIP: 130.129.131.115 (ahn) MIME-Version: 1.0 Content-Type: text/plain; charset=euc-kr X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Hi! This is Sanghyun Ahn from University of Seoul, Korea. At the MANET session of the 61st meeting, I've mentioned about the draft I have submitted in last July. The title of the draft is as follows: Multicast Ad hoc On-Demand Distance Vector Routing for IP version 6 (MAODV6) http://www.ietf.org/internet-drafts/draft-jeong-manet-maodv6-00.txt The draft is about detecting duplicate multicast data packets which can occur during multicast data forwarding. In that draft, we defined two related problems and proposed solutions for them. Also, we've implemented the proposed mechanisms last year. Regards, Sanghyun Ahn University of Seoul _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 10 16:26:56 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06255 for ; Wed, 10 Nov 2004 16:26:56 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS00Z-0007wY-0i for manet-web-archive@ietf.org; Wed, 10 Nov 2004 16:28:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRztx-000584-Pe; Wed, 10 Nov 2004 16:21:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRzgd-0006qA-OO for manet@megatron.ietf.org; Wed, 10 Nov 2004 16:07:27 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02860 for ; Wed, 10 Nov 2004 16:07:25 -0500 (EST) Received: from smtp2.adtran.com ([66.0.238.13] helo=adtran.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRzhf-0007HB-EI for manet@ietf.org; Wed, 10 Nov 2004 16:08:31 -0500 Received: from ([172.22.48.6]) by smtp2.adtran.com with ESMTP id 133020030.2205906; Wed, 10 Nov 2004 15:06:52 -0600 Received: by srv-exchange2.adtran.com with Internet Mail Service (5.5.2657.72) id ; Wed, 10 Nov 2004 15:06:52 -0600 Message-ID: <39B01E2189D99F4B8C9612462DB3922A153B95BB@srv-exchange.adtran.com> From: DANIEL BYRNE To: manet@ietf.org Date: Wed, 10 Nov 2004 15:10:28 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d62ab47271805379d7172ee693a45db Subject: [manet] LAN Card X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de I'm looking for a LAN card that I can use for MANET research. Specifically I'm looking for a card that has an open source driver with source code, and a card that uses a chipset whose datasheet doesn't require an NDA, your firstborn, and an Act of Congress to get a hold of. Thanks in advance, Daniel Byrne _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 10 17:04:07 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09835 for ; Wed, 10 Nov 2004 17:04:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS0aX-0000KM-TE for manet-web-archive@ietf.org; Wed, 10 Nov 2004 17:05:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CS0Pu-0003gJ-7B; Wed, 10 Nov 2004 16:54:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CS0Fq-0006vh-1w for manet@megatron.ietf.org; Wed, 10 Nov 2004 16:43:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08120 for ; Wed, 10 Nov 2004 16:43:47 -0500 (EST) Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS0Gp-0008Hm-2O for manet@ietf.org; Wed, 10 Nov 2004 16:44:54 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id iAALFO418763; Wed, 10 Nov 2004 13:15:24 -0800 X-mProtect: <200411102115> Nokia Silicon Valley Messaging Protection Received: from danira-pool049160.americas.nokia.com (10.241.49.160, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdp6PaTd; Wed, 10 Nov 2004 13:15:23 PST Message-ID: <41928B62.3040509@iprg.nokia.com> Date: Wed, 10 Nov 2004 13:42:58 -0800 From: "Charles E. Perkins" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mobile Ad Hoc IETF working group Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7bit Cc: Herbert Rubens , David Holmer Subject: [manet] Pointer to pulse work X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Hello folks, Here is a pointer to some of the work that I mentioned this afternoon in the [manet] working group: http://www.cnds.jhu.edu/research/networks/archipelago/ Plus, I';ve CC:d two researchers who have developed the protocol. I reckon they can answer detailed questions. Regards, Charlie P. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 10 17:05:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10005 for ; Wed, 10 Nov 2004 17:05:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS0br-0000NP-If for manet-web-archive@ietf.org; Wed, 10 Nov 2004 17:06:35 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CS0QC-0003qw-Qn; Wed, 10 Nov 2004 16:54:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CS0Km-0000eP-Tc for manet@megatron.ietf.org; Wed, 10 Nov 2004 16:48:57 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08507 for ; Wed, 10 Nov 2004 16:48:54 -0500 (EST) Received: from che.ojctech.com ([209.254.158.42]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CS0Ln-0008O2-Ql for manet@ietf.org; Wed, 10 Nov 2004 16:50:01 -0500 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id iAALm7u6026627; Wed, 10 Nov 2004 15:48:07 -0600 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id iAALllje026613; Wed, 10 Nov 2004 15:47:47 -0600 Date: Wed, 10 Nov 2004 15:47:47 -0600 From: David Young To: DANIEL BYRNE Subject: Re: [manet] LAN Card Message-ID: <20041110214746.GZ17288@che.ojctech.com> Mail-Followup-To: DANIEL BYRNE , manet@ietf.org References: <39B01E2189D99F4B8C9612462DB3922A153B95BB@srv-exchange.adtran.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <39B01E2189D99F4B8C9612462DB3922A153B95BB@srv-exchange.adtran.com> User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 On Wed, Nov 10, 2004 at 03:10:28PM -0600, DANIEL BYRNE wrote: > I'm looking for a LAN card that I can use for MANET research. > Specifically I'm looking for a card that has an open source driver with > source code, and a card that uses a chipset whose datasheet doesn't > require an NDA, your firstborn, and an Act of Congress to get a hold of. Look at what is available for ADMtek ADM8211, Realtek RTL8180, Ralink RT2500, and Atheros 5xxx. Dave -- David Young OJC Technologies dyoung@ojctech.com Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 11 03:56:31 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14585 for ; Thu, 11 Nov 2004 03:56:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSAlz-0004IW-CB for manet-web-archive@ietf.org; Thu, 11 Nov 2004 03:57:43 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSAiK-0004UA-8K; Thu, 11 Nov 2004 03:53:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSAhp-0004Na-3s for manet@megatron.ietf.org; Thu, 11 Nov 2004 03:53:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14183 for ; Thu, 11 Nov 2004 03:53:23 -0500 (EST) Received: from mailgw5.vtt.fi ([130.188.1.19]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSAit-0004DE-UY for manet@ietf.org; Thu, 11 Nov 2004 03:54:35 -0500 Received: from elemail.ele.vtt.fi (localhost [127.0.0.1]) by mailgw5.vtt.fi (8.12.11/8.12.11) with ESMTP id iAB8p89C013393 for ; Thu, 11 Nov 2004 10:51:09 +0200 (EET) Received: from OULKV10435.elemail.ele.vtt.fi (tko1135.tko.vtt.fi [130.188.91.135]) by elemail.ele.vtt.fi (8.9.1a/8.9.1) with ESMTP id KAA18707 for ; Thu, 11 Nov 2004 10:52:46 +0200 (EET) Message-Id: <5.1.0.14.2.20041111104831.00bb97f8@elemail.ele.vtt.fi> X-Sender: elexkar@elemail.ele.vtt.fi X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 11 Nov 2004 10:52:46 +0200 To: manet@ietf.org From: Kaarina Karppinen In-Reply-To: <20041110153236.87646.qmail@web20923.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Subject: [manet] JiST/SWANS GUI? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Hi, does anyone know if there is a graphical useer interface for JiST/SWANS? I've heard that there would be one available but haven't found the code. Has someone used JiST/SWANS simulation for simulating security of MANETs? Brgds, Kaarina student of University of Oulu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 11 13:33:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10650 for ; Thu, 11 Nov 2004 13:33:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSJmU-0000v4-Kv for manet-web-archive@ietf.org; Thu, 11 Nov 2004 13:34:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSJfv-0005S6-Fn; Thu, 11 Nov 2004 13:28:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSJcO-0004NS-Ap for manet@megatron.ietf.org; Thu, 11 Nov 2004 13:24:24 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09928 for ; Thu, 11 Nov 2004 13:24:21 -0500 (EST) Received: from web60003.mail.yahoo.com ([216.109.116.226]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CSJda-0000jk-Ni for manet@ietf.org; Thu, 11 Nov 2004 13:25:39 -0500 Received: (qmail 9164 invoked by uid 60001); 11 Nov 2004 18:23:52 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=2v2Z9Dm7xj0TCOrxQrCLpdxTTnVoNItosTUotMxgAjnYwKI3QdvLE35gvbXtHWUOg6nRl5M31n4UmMIX2pWMWn/+uWpm+eGoIr43gV3coDyTBaTG8ne7mA/kihYk7lRco3hsKneS9QdMdVgdvO+2DZydeVurSPqAynRocDvfvJI= ; Message-ID: <20041111182352.9162.qmail@web60003.mail.yahoo.com> Received: from [202.141.142.23] by web60003.mail.yahoo.com via HTTP; Thu, 11 Nov 2004 10:23:52 PST Date: Thu, 11 Nov 2004 10:23:52 -0800 (PST) From: Shahriar Shamil Uulu To: manet@ietf.org, ns-users@ISI.EDU MIME-Version: 1.0 X-Spam-Score: 0.8 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Subject: [manet] About SAODV X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1064135744==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a --===============1064135744== Content-Type: multipart/alternative; boundary="0-1751705081-1100197432=:7985" --0-1751705081-1100197432=:7985 Content-Type: text/plain; charset=us-ascii Hi All, I would like to ask is there anybody who konws where i can get a source code for SAODV protocol implemented on ns2 or other free available network simulator. Any help will be greatly apperciated. Thanking you in advance Shahriar Shamil Uulu Hyderabad Central University M.Tech(Computer Science) email:shamilsons@yahoo.com website: http://shamilson.narod.ru --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --0-1751705081-1100197432=:7985 Content-Type: text/html; charset=us-ascii
Hi All,
I would like to ask is there anybody who konws where i can get a source code for SAODV protocol implemented on ns2 or other free available network simulator. Any help will be greatly apperciated.
Thanking you in advance


Shahriar Shamil Uulu
Hyderabad Central University
M.Tech(Computer Science)
email:shamilsons@yahoo.com
website: http://shamilson.narod.ru
 

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com --0-1751705081-1100197432=:7985-- --===============1064135744== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1064135744==-- From manet-bounces@ietf.org Fri Nov 12 01:53:07 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19335 for ; Fri, 12 Nov 2004 01:53:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSVKJ-0000fU-4R for manet-web-archive@ietf.org; Fri, 12 Nov 2004 01:54:31 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSVE9-0002xy-Ns; Fri, 12 Nov 2004 01:48:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSVAG-0002IZ-H2 for manet@megatron.ietf.org; Fri, 12 Nov 2004 01:44:08 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA18883 for ; Fri, 12 Nov 2004 01:44:01 -0500 (EST) Received: from web20923.mail.yahoo.com ([216.136.224.137]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CSVBS-0000Wp-UT for manet@ietf.org; Fri, 12 Nov 2004 01:45:24 -0500 Received: (qmail 37588 invoked by uid 60001); 12 Nov 2004 06:43:55 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=16fO6eJdG/BI8IkIN+FLGHA9o0CGlpBsB7levBFp2lcxnYFyueTu+r9meZ0kzTzwc+jBw6pd0LUiuNI2jH4CWbK6mA33dXUFwoiXnDuJaTXxI5MF14N8TzGeVkrRc1CpDubpAVAsbpCJEnj4OXewuS5Q9CNJPPwPev6zrVaMRkE= ; Message-ID: <20041112064355.37586.qmail@web20923.mail.yahoo.com> Received: from [203.208.193.230] by web20923.mail.yahoo.com via HTTP; Thu, 11 Nov 2004 22:43:55 PST Date: Thu, 11 Nov 2004 22:43:55 -0800 (PST) From: Praveen Choudary To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Subject: [manet] Research in WSN X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1361750030==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 --===============1361750030== Content-Type: multipart/alternative; boundary="0-819292825-1100241835=:37577" --0-819292825-1100241835=:37577 Content-Type: text/plain; charset=us-ascii Hi, I am interested in the problem, where the nodes in Sensor Network are grouped into cluster. I have read some publications in this area. I feel that the publications either assume that the nodes are either completely stationary or completely mobile. I want to consider a situation in which there are stationary sensor nodes Let us call these as lower-level sensors which only sense and disseminate data. There are more powerful mobile nodes which aggregate data in addition to forwarding it. I am sure that the mobile nodes should have less energy constraints then static sensor nodes. That is there is a combination of stationary and mobile nodes. Now I want to organize the nodes into clusters. The stationary nodes in the cluster are fixed and will act as members. The mobile nodes which are more powerful, act as group leaders. I have one Idea, in my mind for this network. I want to make sure, if there are any publications that exactly duplicates the situation in my interest. The answer for this question is very important for my research. I request the members to give soe suggestions so that I can proceed further. Waiting for your reply, Praveen. --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --0-819292825-1100241835=:37577 Content-Type: text/html; charset=us-ascii
Hi,
 I am interested in the problem, where the nodes in Sensor Network are grouped into cluster. I have read some publications in this area. I feel that the publications either assume that the nodes are either completely stationary or completely mobile.
 
 I want to consider a situation in which there are stationary sensor nodes  Let us call these as lower-level sensors which only sense and disseminate data. There are more powerful mobile nodes which aggregate data in addition to forwarding it. I am sure that the mobile nodes should have less energy constraints then static sensor nodes. That is there is a combination of stationary and mobile nodes.
 
Now I want to organize the nodes into clusters. The stationary nodes in the cluster are fixed and will act as members. The mobile nodes which are more powerful, act as group leaders. I have one Idea, in my mind for this network. I want to make sure, if there are any publications that exactly duplicates the situation in my interest.
 
The answer for this question is very important for my research. I request the members to give soe suggestions so that I can proceed further.
 
Waiting for your reply,
Praveen.

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com --0-819292825-1100241835=:37577-- --===============1361750030== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1361750030==-- From manet-bounces@ietf.org Fri Nov 12 04:56:35 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15685 for ; Fri, 12 Nov 2004 04:56:34 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSYBt-0003sr-2u for manet-web-archive@ietf.org; Fri, 12 Nov 2004 04:58:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSY8M-000311-Hw; Fri, 12 Nov 2004 04:54:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSY2n-000255-QO for manet@megatron.ietf.org; Fri, 12 Nov 2004 04:48:39 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15135 for ; Fri, 12 Nov 2004 04:48:12 -0500 (EST) Received: from web25806.mail.ukl.yahoo.com ([217.12.10.191]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CSY3l-0003k7-2m for manet@ietf.org; Fri, 12 Nov 2004 04:49:38 -0500 Received: (qmail 98534 invoked by uid 60001); 12 Nov 2004 09:47:41 -0000 Message-ID: <20041112094741.98532.qmail@web25806.mail.ukl.yahoo.com> Received: from [194.145.62.45] by web25806.mail.ukl.yahoo.com via HTTP; Fri, 12 Nov 2004 09:47:41 GMT Date: Fri, 12 Nov 2004 09:47:41 +0000 (GMT) From: =?iso-8859-1?q?V=EDtor=20Jesus?= To: takhoa@rice.edu, kaz In-Reply-To: <1100192441.9488.21.camel@rodenbach> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA15135 Cc: ns-users@ISI.EDU, manet@ietf.org Subject: [manet] Re: [ns] DSR: flow route changing without movements X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Content-Transfer-Encoding: quoted-printable Khoa, kaz, I got exactly the same effect as Kaz has.=20 The channel contention is a strong issue (very clear and complete explanation from Khoa) but, in my experience, ns-2 also has a very unrealistic propagation model. I've been using TwoRay model. If you simulate a "fixed" adhoc in ns-2, if you keep all nodes appart some distance D, and if you slightly change D (say, 150m + 1m), you get drastic changes in packet loss and the nodes where the losses occur (from traces). Such small variation resulting in such major effects seems more like a propagation issue, very typical of a TwoRay model.=20 As I see it, it looks like interference pattern is changing at the "rate" of the wavelength used which is about 10cm for GHz band. That is what I would expect from a simple TwoRay model. --V=EDtor JS --- Khoa To wrote:=20 >=20 > If you are sending lots of packets, the wireless > channel could get > saturated. This leads to route errors when the node > cannot send out a > packet to the neighbor (due to contention in the > wireless channel). >=20 > When this happens, DSR assumes that the link is > broken, and proceeds to > discover a new path to the destination. >=20 > If you are using fixed nodes, you could tell DSR not > to respond to > transmission failure by not responding to any > packets that come through > the DSR::xmitFailed() function (i.e. free those > packets, don't initiate > a new route discovery process). The problem with > this is that DSR would > be come a static routing protocol and cannot respond > to and change in > the topology, but it will discover the initial > topology and stick with > that. >=20 > Khoa. >=20 > On Thu, 2004-11-11 at 10:25, kaz wrote: > > Hi everybody, > >=20 > > I have a quite strange problem: I'm using fixed > nodes. I mean, which are=20 > > not moving. However, I have quite a lot of route > error: about 6000 route=20 > > error pkt for 35000 cbr pkt sent and a 900s > simulation. And my flow=20 > > routes are changing all the time. So, I was > wondering if there were an=20 > > explanation for this. > >=20 > > regards > >=20 >=20 > =20 =09 =09 =09 ___________________________________________________________=20 ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.me= ssenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 12 05:59:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19539 for ; Fri, 12 Nov 2004 05:59:04 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSZAN-0004zj-Ee for manet-web-archive@ietf.org; Fri, 12 Nov 2004 06:00:31 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSZ4D-0003RZ-RG; Fri, 12 Nov 2004 05:54:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSZ3U-0003LJ-OW for manet@megatron.ietf.org; Fri, 12 Nov 2004 05:53:24 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA19263 for ; Fri, 12 Nov 2004 05:53:21 -0500 (EST) Received: from web25810.mail.ukl.yahoo.com ([217.12.10.195]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CSZ4o-0004tj-C4 for manet@ietf.org; Fri, 12 Nov 2004 05:54:48 -0500 Received: (qmail 1880 invoked by uid 60001); 12 Nov 2004 10:52:50 -0000 Message-ID: <20041112105250.1878.qmail@web25810.mail.ukl.yahoo.com> Received: from [194.145.62.46] by web25810.mail.ukl.yahoo.com via HTTP; Fri, 12 Nov 2004 10:52:50 GMT Date: Fri, 12 Nov 2004 10:52:50 +0000 (GMT) From: =?iso-8859-1?q?V=EDtor=20Jesus?= Subject: Re: [manet] Generating Selfishness in manet ... PLEASE HELP ME To: Shahriar Shamil Uulu In-Reply-To: <20041111183238.15922.qmail@web60004.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA19263 Cc: ns-users@ISI.EDU, manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: quoted-printable In DSR (I'm more familiar to DSR than AODV, so I'll use it here), it is very simple to do that but some understanding of the code is needed. The recv() function (DSRAgent.cc) is the starting point. From there, all packets that arrive (either from MAC or upper layers) are processed. I suggest you to implement a filter on that method (or derived ones) so that, according to some rule you specify, some packets are forwarded to next hop or not. --V=EDtor=20 --- Shahriar Shamil Uulu wrote:=20 > Hi Vitor Jesus, > This exactly what i want to do as you mentioned. The > node or the group of nodes must silently drop the > packets, at the end of the simulation i want to > analyze and show that how many packets has been > dropped by selfish node. Most probably i am planning > to do it with AODV or DSR protocols in ns2 .So if > you have any idea how to do that please give me some > guidelines.It would be most apperciated. SORRY FOR > 2nd COPY=20 > Thank you in advance >=20 >=20 >=20 > Shahriar Shamil Uulu=20 > Hyderabad Central University=20 > M.Tech(Computer Science) > email:shamilsons@yahoo.com > website: http://shamilson.narod.ru >=20 > =20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > =09 > --------------------------------- > Do you Yahoo!? > Check out the new Yahoo! Front Page. www.yahoo.com=20 =09 =09 =09 ___________________________________________________________=20 ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.me= ssenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 12 06:58:13 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23197 for ; Fri, 12 Nov 2004 06:58:13 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSa5d-00063O-9G for manet-web-archive@ietf.org; Fri, 12 Nov 2004 06:59:41 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSa28-0004O4-TQ; Fri, 12 Nov 2004 06:56:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSa1E-0004I9-5W for manet@megatron.ietf.org; Fri, 12 Nov 2004 06:55:08 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22967 for ; Fri, 12 Nov 2004 06:55:05 -0500 (EST) Received: from stamps.cs.ucsb.edu ([128.111.41.14]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSa2a-00060B-NE for manet@ietf.org; Fri, 12 Nov 2004 06:56:33 -0500 Received: from [127.0.0.1] (moment.cs.ucsb.edu [128.111.40.94]) by stamps.cs.ucsb.edu (8.12.11/8.12.11) with ESMTP id iACBsxaW014736; Fri, 12 Nov 2004 03:55:03 -0800 Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Ian Chakeres Date: Fri, 12 Nov 2004 06:55:02 -0500 To: "'manet'" X-Mailer: Apple Mail (2.619) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (stamps.cs.ucsb.edu [128.111.41.14]); Fri, 12 Nov 2004 03:55:03 -0800 (PST) X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on stamps.cs.ucsb.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53 Content-Transfer-Encoding: 7bit Subject: [manet] Minutes from IETF61 MANET WG Meeting X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 17e5edc4dfd335965c1d21372171c01c Content-Transfer-Encoding: 7bit Presentations will be published to http://www.ietf.org/proceedings/directory.html shortly. Ian Chakeres ----------------------------------------------------------- MANET Minutes 11/10/04 Note Taker: Krishna Ramachandran MANET draft agenda: See slides Joe Macker (JM) * Charter Revision update: See slides Speaker: Joe Macker Comments: Samita Chakrabarti - Does it make sense to define the application target in the charter? Joe Macker - The goal is to design a light-weight but not necessarily an optimal routing solution. Constraints such as power saving need to be considered design. Mechanisms will be built in to support various policies such as energy saving, etc. Will post charter text on ML. * DyMO: See slides Speaker: Ian Chakeres (IC) Comments: Charlie Perkins (CP) - I Like path accumulation. We have to think about how to capture path info in smaller MTUs. Justin Dean - Aggregate path accumulation information may be able to enable no reverse routes on RREQ processing. Will post more information to the list. IC - I like path accumulation. The question is whether it should be required or not. * Manet Proactive Routing Protocol (see slides) Speaker: Thomas Clausen (TC) Comments: JM - Doing full-state flooding might be sensible for some n/w configurations. TC - Yes. I am not precluding it from the spec, but I mentioned optimized partial topology dissemination because of all the work and the community consensus on this thus far. CP - It is important that some nodes that implement only the base spec don't bog down the remaining nodes that support an extension that achieves some optimization. Don't ignore important optimizations because they are extensions. JM - Document the design rationale when writing the spec. TC - Is there a process for documenting the design rationale? Brian Adamson - Specify 3 things in the doc: core baseline spec, extensions to typically include in an implementation, and finally some extensions that could be implemented in the future. JM - The process of a design rationale should be open to the WG. Alex Zinin (AZ) - Bring the design choices to the ML. Maybe write an information document on the design choices. TC - Do we have to include all MAYs in the standard track document? AZ - Typically MAYs are included for interoperability purposes. But there are no hard and fast rules. Phillip Chimento - How about features that need to be used but are not present because the base spec doesn't support? JM - Prioritize the known features to be deployed. IC - Solutions for the interaction of unknown options are a common problem. If you know a solution please post it to the list. Otherwise we will do our best. CP - Base protocol should not require to be designed for the majority of the cases. Things like expanding ring search, etc are known to be help optimize network operation. Should they be included? JM - Base spec should satisfy many cases but cannot necessarily say that they satisfy the majority of cases. CP - We plan to get the base doc out first. Then soon after, publish another doc with extensions, and then do this iteratively. Pedro - Internet gatewaying results. (Please query for more information.) JM - There are definitely some trade offs and different approaches for proactive vs reactive. More information would be helpful. AZ - Focus on core functionality. Consider the implementation requirement before putting a feature into the core spec. If some feature is not going to be implemented, don't put it into the spec. Rob Frye - Agreement with whats already been said about the core-extension design rationale. * Simplified Multicast Forwarding for MANET (see slides) Speaker: Joe Macker Comments: Tom Henderson - Will there be a specific MANET multicast address for delivery of packet to all manet nodes? JM - CP will address this. There might be some IANA assigned IPs. Tom Anderson - Will multicast scoping be required? JM - There are other ways to do scoping. So not necessarily in the base spec. Phil Chimento - Is the phy layer assumed to be 802.11? Does it matter? JM - It matters but we chose 802.11 mac for availability of hardware. Herbert Dens - Broadcast is done at the lower rate. This could eliminate higher throughput routes that the connected dominating set doesn't consider because it is formed using broadcast. JM - This is a problem in MANET. Unknown - Their implementation experience with MAODV might be relevant. JM - Post the publication to the ML. Justin Dean - Implementation specific issue about IP to Mac address mapping. Li Li - Is the forwarding mechanism per packet or precomputed? JM - Precomputed. * Simplified Manet Multicast Routing Protocol (SMURF) (Slides) Speaker: Charlie Perkins Comments: Tom Henderson - Can we do things like cross-layer optimization in the multicast forwarding algorithm? CP - Might be ambitious to include initially but definitely worthwhile considering. JM - Is there consensus that multicast work is useful? Does anyone have any negative feedback about this charter item? Luke Klein-Berndt - Yes. It will be very useful for work we are doing at NIST. Unknown - Yes. Even for sensors. Li Li - Very useful for our work. * First OLSR Interop Report (Slides) Speaker: Thomas Clausen Announcements: Unknown - Immediately following MANET is a BOF on IPv6 over IEEE 802.15.4. CP - Pulsing power conserving solution: Consider such solutions as part of the design process. Will post reference to the list. * MANET AutoConf (see slides) Speaker: Emmanuel Baccelli Comments: JM - Too many solutions in the basket. Need to explore more. Possibly also explore collaboration with other groups. Not necessarily a routing area issue. AZ - Start discussion on ML. Request for a BOF after some consensus is reached. Paal Engelstad - If autoconf is going to be a BOF, include service discovery also. JM - Time is up, please thrash it out on the ML. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 12 07:07:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23742 for ; Fri, 12 Nov 2004 07:07:57 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSaF0-0006Er-Qk for manet-web-archive@ietf.org; Fri, 12 Nov 2004 07:09:26 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSaAq-0005eS-9N; Fri, 12 Nov 2004 07:05:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSa5E-0004l1-09 for manet@megatron.ietf.org; Fri, 12 Nov 2004 06:59:16 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23268 for ; Fri, 12 Nov 2004 06:59:12 -0500 (EST) Received: from stamps.cs.ucsb.edu ([128.111.41.14]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSa6a-00064k-Ky for manet@ietf.org; Fri, 12 Nov 2004 07:00:41 -0500 Received: from [127.0.0.1] (moment.cs.ucsb.edu [128.111.40.94]) by stamps.cs.ucsb.edu (8.12.11/8.12.11) with ESMTP id iACBxCC0014842; Fri, 12 Nov 2004 03:59:13 -0800 Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <462F6BE0-34A2-11D9-B99A-000A95C1BC0A@cs.ucsb.edu> Content-Transfer-Encoding: 7bit From: Ian Chakeres Date: Fri, 12 Nov 2004 06:59:15 -0500 To: "'manet'" X-Mailer: Apple Mail (2.619) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (stamps.cs.ucsb.edu [128.111.41.14]); Fri, 12 Nov 2004 03:59:13 -0800 (PST) X-Virus-Scanned: clamd / ClamAV version 0.71, clamav-milter version 0.71 X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on stamps.cs.ucsb.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7bit Subject: [manet] Path Accumulation in DyMO X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7bit At the MANET meeting I presented DyMO (Dynamic MANET On-demand Routing Protocol). My slides from the presentation are available at http://moment.cs.ucsb.edu/~idc/pub/chakeres_ietf61_presentation.pdf. There was a short discussion about using path accumulation in the base specification. Most people expressed their feelings that path accumulation is useful for additional route information dissemination. I believe there was consensus to not include path accumulation in the core spec though it should definitely be included as an optimization. If you disagree, lets discuss it more on the list. Thanks. Ian Chakeres _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Nov 13 12:50:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19960 for ; Sat, 13 Nov 2004 12:50:23 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CT24D-0002Pa-9s for manet-web-archive@ietf.org; Sat, 13 Nov 2004 12:52:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CT1sq-00006E-GZ; Sat, 13 Nov 2004 12:40:20 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CT1rt-0008K0-0T for manet@megatron.ietf.org; Sat, 13 Nov 2004 12:39:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19529 for ; Sat, 13 Nov 2004 12:39:18 -0500 (EST) Received: from web20923.mail.yahoo.com ([216.136.224.137]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CT1tU-0001vH-FG for manet@irtf.org; Sat, 13 Nov 2004 12:41:01 -0500 Received: (qmail 21560 invoked by uid 60001); 13 Nov 2004 17:39:15 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=ZEB6UC17qBk5NIomfqhysuzyYYTaqvDumsZoscm+azVDrcfZI6oJiOfejwfU+kP+nj0BFgGVQaToDSZokpmN+xMZ7KBTKAXjNQguQztoztrsUWOrqOVzRBZQnQfodQneyRm7SuA0awVatUoaWkM8EOJnW8WYX8wJw1GKzgBRgWk= ; Message-ID: <20041113173915.21558.qmail@web20923.mail.yahoo.com> Received: from [203.208.193.230] by web20923.mail.yahoo.com via HTTP; Sat, 13 Nov 2004 09:39:15 PST Date: Sat, 13 Nov 2004 09:39:15 -0800 (PST) From: Praveen Choudary To: manet@irtf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Subject: [manet] Sensor MAC X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1293725407==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 --===============1293725407== Content-Type: multipart/alternative; boundary="0-109385900-1100367555=:20177" --0-109385900-1100367555=:20177 Content-Type: text/plain; charset=us-ascii Hi, I want to modify S-MAC so that it can be used with energy efficient routing protocols which address QOS issues in sensor networks. If anybody has come across publications that address the "Integration of MAC and routing protocols for QOS traffic in Sensor Networks", kindly give me some references. If possible suggest some modifications of S-MAC or atleast give me some hints so that I can think in the right direction and proceed further. Your hints or suggestions can help me make a meaningful contribution to the research in this area. Looking forward for your reply, Praveen. --------------------------------- Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com --0-109385900-1100367555=:20177 Content-Type: text/html; charset=us-ascii
Hi,
 I want to modify S-MAC so that it can be used with energy efficient routing protocols which address QOS issues in sensor networks.
 
If anybody has come across publications that address the "Integration of MAC and routing protocols for QOS traffic in Sensor Networks", kindly give me some references. If possible suggest some modifications of S-MAC or atleast give me some hints so that I can think in the right direction and proceed further.
 
Your hints or suggestions can help me make a meaningful contribution to the research in this area.
Looking forward for your reply,
Praveen.

Do you Yahoo!?
Check out the new Yahoo! Front Page. www.yahoo.com --0-109385900-1100367555=:20177-- --===============1293725407== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1293725407==-- From manet-bounces@ietf.org Sat Nov 13 17:19:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04921 for ; Sat, 13 Nov 2004 17:19:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CT6Gs-0005nb-Uk for manet-web-archive@ietf.org; Sat, 13 Nov 2004 17:21:30 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CT64M-0007Y7-7e; Sat, 13 Nov 2004 17:08:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CT5vb-0005wz-FZ for manet@megatron.ietf.org; Sat, 13 Nov 2004 16:59:27 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03135 for ; Sat, 13 Nov 2004 16:59:24 -0500 (EST) Received: from ms-smtp-01-lbl.southeast.rr.com ([24.25.9.100] helo=ms-smtp-01-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CT5xF-0004k4-Nr for manet@ietf.org; Sat, 13 Nov 2004 17:01:10 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-01-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iADLxLKj025197 for ; Sat, 13 Nov 2004 16:59:23 -0500 (EST) From: "Christopher P. Rigano" To: Date: Sat, 13 Nov 2004 16:59:21 -0500 Message-ID: <000901c4c9cc$07d4bb70$0300a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.2 (/) X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff Subject: [manet] RE: uppper layers used with MANETs are they just TCP/UDP IP? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0655369442==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 501044f827b673024f6a4cb1d46e67d2 This is a multi-part message in MIME format. --===============0655369442== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000A_01C4C9A2.1EFEB370" This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C4C9A2.1EFEB370 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings all, I understand that MANETs exist "on top of "a physical and link/MAC layer. MANETs to a great extent are topology or layer 3 (network). What protocols are currently used to run "on top of" MANETs are they mostly TCP/UDP with IP addresses as nodes? What variants then are used? What other protocols provide transport and session capabilities? Thanks and regards, Christopher ------=_NextPart_000_000A_01C4C9A2.1EFEB370 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings all,

 

I understand that MANETs exist “on top of = “a physical and link/MAC layer. MANETs to a great extent are topology or = layer 3 (network). What protocols are currently used to run “on top of” MANETs = are they mostly TCP/UDP with IP addresses as nodes? What variants then are = used? What other protocols provide transport and session capabilities? =

 

Thanks and regards,

 

Christopher

------=_NextPart_000_000A_01C4C9A2.1EFEB370-- --===============0655369442== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0655369442==-- From manet-bounces@ietf.org Sun Nov 14 17:19:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16151 for ; Sun, 14 Nov 2004 17:19:50 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTSkm-00035E-Mz for manet-web-archive@ietf.org; Sun, 14 Nov 2004 17:21:48 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTScm-0005bw-CQ; Sun, 14 Nov 2004 17:13:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTSaY-0005Iq-0A for manet@megatron.ietf.org; Sun, 14 Nov 2004 17:11:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15568 for ; Sun, 14 Nov 2004 17:11:11 -0500 (EST) Received: from xdsl-3173.wroclaw.dialog.net.pl ([81.168.156.101] helo=192.168.0.1) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CTScN-0002ep-IX for manet@ietf.org; Sun, 14 Nov 2004 17:13:10 -0500 Message-ID: <008f01c4ca96$c9837fc0$659ca851@saddamlennon> From: "Grzegorz Jablonski" To: References: <5.1.0.14.2.20041111104831.00bb97f8@elemail.ele.vtt.fi> Subject: Re: [manet] JiST/SWANS GUI? Date: Sun, 14 Nov 2004 23:10:44 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.3 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 7bit I've used SWANS to simulate some location-aware algorithms. There's no GUI as far as I know, but you can write your own - it shouldn't be difficult if you have some java skills. Anyway, be careful, there's some bugs in SWANS's implementation of 802.11 MAC layer - it would deadlock for me sometimes under high network load. Apart from this, it's a great simulator and I can't wait until it gets better. Cheers Greg ----- Original Message ----- From: "Kaarina Karppinen" To: Sent: Thursday, November 11, 2004 9:52 AM Subject: [manet] JiST/SWANS GUI? > Hi, > > does anyone know if there is a graphical useer interface for JiST/SWANS? > I've heard that there would be one available but haven't found the code. > > Has someone used JiST/SWANS simulation for simulating security of MANETs? > > Brgds, > > Kaarina > student of University of Oulu > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Nov 14 22:47:21 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06008 for ; Sun, 14 Nov 2004 22:47:21 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTXrm-0005zs-FC for manet-web-archive@ietf.org; Sun, 14 Nov 2004 22:49:22 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTXn0-0007xG-KA; Sun, 14 Nov 2004 22:44:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTXhg-0007aa-T3 for manet@megatron.ietf.org; Sun, 14 Nov 2004 22:38:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05593 for ; Sun, 14 Nov 2004 22:38:54 -0500 (EST) Received: from ms-smtp-01-lbl.southeast.rr.com ([24.25.9.100] helo=ms-smtp-01-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTXjY-0005sN-J9 for manet@ietf.org; Sun, 14 Nov 2004 22:40:55 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-01-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iAF3cmKj014433 for ; Sun, 14 Nov 2004 22:38:49 -0500 (EST) From: "Christopher P. Rigano" To: Date: Sun, 14 Nov 2004 22:38:46 -0500 Message-ID: <000b01c4cac4$9ce21700$0300a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.0 (/) X-Scan-Signature: 25eb6223a37c19d53ede858176b14339 Subject: [manet] 802.16a, e and 802.20 OPNET Modules X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0587911520==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 93df555cbdbcdae9621e5b95d44b301e This is a multi-part message in MIME format. --===============0587911520== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01C4CA9A.B40C0F00" This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C4CA9A.B40C0F00 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings, Does anyone know if there are 802.16a, e and 802.20 OPNET Modules available? I want to try and simulate MANETs over them. Thank and regards, Chris ------=_NextPart_000_000C_01C4CA9A.B40C0F00 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings,

 

Does anyone know if there are 802.16a, e and 802.20 = OPNET Modules available? I want to try and simulate MANETs over them. =

 

Thank and regards,

 

Chris

------=_NextPart_000_000C_01C4CA9A.B40C0F00-- --===============0587911520== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0587911520==-- From manet-bounces@ietf.org Mon Nov 15 01:08:56 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13998 for ; Mon, 15 Nov 2004 01:08:56 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTa4m-0008LR-RY for manet-web-archive@ietf.org; Mon, 15 Nov 2004 01:10:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTZzz-0006gw-VN; Mon, 15 Nov 2004 01:05:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTZz9-0006dF-Pa for manet@megatron.ietf.org; Mon, 15 Nov 2004 01:05:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13915 for ; Mon, 15 Nov 2004 01:05:06 -0500 (EST) Received: from web13205.mail.yahoo.com ([216.136.174.190]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CTa14-0008Ig-Ks for manet@ietf.org; Mon, 15 Nov 2004 01:07:08 -0500 Received: (qmail 77894 invoked by uid 60001); 15 Nov 2004 06:05:04 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=LZtd5l1kJtVhfiF0JVAHnKgAz+rbIKioPabwwg2KurJPiagMxNk3UqZ0FIsYSSNKJnOQSnf13qeQMvvIMfDDm6QcHAch5gAM5G9Iz2xmyWFK+aXvpHHMt0Mw+T8mS9Xoiz5BAfiwO37GOEIllFFdThsTOHeoA8twc4ZhPDbOy4c= ; Message-ID: <20041115060503.77888.qmail@web13205.mail.yahoo.com> Received: from [156.26.36.223] by web13205.mail.yahoo.com via HTTP; Sun, 14 Nov 2004 22:05:03 PST Date: Sun, 14 Nov 2004 22:05:03 -0800 (PST) From: sumanth sarma To: ns-users@ISI.EDU, manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Subject: [manet] anyone worked on VoIP module in ns2??.. X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Hello, anyone worked on voice over IP applications in ns2?..Please do let me know about that. Thanks Sumanth __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 15 08:52:40 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25196 for ; Mon, 15 Nov 2004 08:52:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CThJe-0007OK-2X for manet-web-archive@ietf.org; Mon, 15 Nov 2004 08:54:46 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CThCN-0001wz-0E; Mon, 15 Nov 2004 08:47:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CThAk-0001j1-P9 for manet@megatron.ietf.org; Mon, 15 Nov 2004 08:45:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24826 for ; Mon, 15 Nov 2004 08:45:33 -0500 (EST) From: haas@ece.cornell.edu Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CThCi-0007Hn-6u for manet@ietf.org; Mon, 15 Nov 2004 08:47:39 -0500 Received: from zeno.ece.cornell.edu (zeno.ece.cornell.edu [128.84.81.136]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 34DF01E8029; Mon, 15 Nov 2004 08:45:28 -0500 (EST) Date: Mon, 15 Nov 2004 08:48:16 -0500 (EST) To: manet@ietf.org Subject: Re: [manet] JiST/SWANS GUI? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.3 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: Zygmunt Haas , rimon@acm.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Dear Kaarina, > does anyone know if there is a graphical useer interface for > JiST/SWANS? I've heard that there would be one available but haven't > found the code. The official release does not currently contain a graphical interface. That said, at least two groups that we know of have built their own (very nice) small GUIs, particular to their experiments. It is not difficult. Within your simulation code you intersperse events that update the GUI model. It's very similar to a logging statement, except you send some kind of object which describes the change. The GUI view simply looks at this model as it changes and updates the screen. And, since you are working Java you have all of the portable Swing libraries at your disposal. In general, it is difficult to create a general-purpose GUI. They are often very task specific, so you would have to build one to show the things you are a particularly interested in, whether it be a view of the network operations or of aggregate statistics over time that are particular to your protocol, etc. > Has someone used JiST/SWANS simulation for simulating security of > MANETs? Security is not something that you typically prove or disprove through simulation. If you are referring to the measurement of the overhead imposed by or performance of various secure or fault tolerant protocols, then this is no different from simulating any other network protocol within SWANS. Best regards, Rimon Barr Zygmunt Haas. ===--==-====== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- 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(at)ece(dot)cornell(dot)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 manet-bounces@ietf.org Mon Nov 15 09:08:45 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26136 for ; Mon, 15 Nov 2004 09:08:45 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CThZA-0007hK-V5 for manet-web-archive@ietf.org; Mon, 15 Nov 2004 09:10:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CThR4-0003fe-O2; Mon, 15 Nov 2004 09:02:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CThNT-0003HZ-Sx for manet@megatron.ietf.org; Mon, 15 Nov 2004 08:58:43 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25563 for ; Mon, 15 Nov 2004 08:58:42 -0500 (EST) From: haas@ece.cornell.edu Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CThPT-0007Vb-Ft for manet@ietf.org; Mon, 15 Nov 2004 09:00:48 -0500 Received: from zeno.ece.cornell.edu (zeno.ece.cornell.edu [128.84.81.136]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id 14DC61E8029; Mon, 15 Nov 2004 08:58:42 -0500 (EST) Date: Mon, 15 Nov 2004 09:01:30 -0500 (EST) To: manet@ietf.org, ans-research@www1.ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.3 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: Zygmunt Haas , rimon@acm.org Subject: [manet] v1.0.2 of JiST/SWANS has been released X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Hi Everyone, For those of you interested in the JiST/SWANS simulator, we have released v1.0.2. Below is the change log. The source code is available online at: http://jist.ece.cornell.edu v1.0.2 - change log: - swans.Rewriter: inhibit method signature changes to methods outside the SWANS or application codebase (reported by Gabi Kliot) - RadioNoiseAdditive: properly initialize total power to background noise - RadioNoiseIndep: consider background noise (reported by Einar Vollset), reducing the effective transmission range when using default radio parameters - renamed/added/cleaned up some examples in driver directory - NetIp: promisc mode packets processed like any other packet - fix: in RadioNoiseIndep (line 137) due to Gabi Kliot: only set mode to idle if signals==0 - change jist/swans/misc/makefile to ignore performance-enhancing native library compilation errors - fix: NullPointerException in classloader -> ClassNotFoundException - fix: data flow analysis modified to ignore JSR return addresses - fix: jump target lost during rewrite when immediatelly before blocking call (reported by Einar Vollset) All the best, Rimon Barr and Zygmunt Haas. ===-==-=======--=-== ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- 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(at)ece(dot)cornell(dot)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 manet-bounces@ietf.org Mon Nov 15 09:36:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28044 for ; Mon, 15 Nov 2004 09:36:23 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CThzy-0008Iq-H3 for manet-web-archive@ietf.org; Mon, 15 Nov 2004 09:38:30 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CThuI-0008JK-BY; Mon, 15 Nov 2004 09:32:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CThrr-0007nD-IB for manet@megatron.ietf.org; Mon, 15 Nov 2004 09:30:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27598 for ; Mon, 15 Nov 2004 09:30:05 -0500 (EST) Message-Id: <200411151430.JAA27598@ietf.org> Received: from mail.gmx.net ([213.165.64.20]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CThtr-00088W-PO for manet@ietf.org; Mon, 15 Nov 2004 09:32:12 -0500 Received: (qmail 8963 invoked by uid 65534); 15 Nov 2004 14:29:29 -0000 Received: from unknown (EHLO NicoBare) (192.166.62.145) by mail.gmx.net (mp019) with SMTP; 15 Nov 2004 15:29:29 +0100 X-Authenticated: #15262315 From: "Nico Bayer" To: Date: Mon, 15 Nov 2004 15:29:34 +0100 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTLH4c9iikCrZExRSKxHo4uUmt2Sw== X-Spam-Score: 0.1 (/) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f Subject: [manet] 802.16 implementation for NS2 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2054644659==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365 This is a multi-part message in MIME format. --===============2054644659== Content-Type: multipart/alternative; boundary="----=_NextPart_000_007C_01C4CB27.E9D21980" This is a multi-part message in MIME format. ------=_NextPart_000_007C_01C4CB27.E9D21980 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hello, I want to do some simulations with 802.16 (a and e). Does anyone know if there are implementations for NS2 available? Thank you in advance. Kind Regards, Nico Bayer ------=_NextPart_000_007C_01C4CB27.E9D21980 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

I want to do some simulations with 802.16 (a and e). = Does anyone know if there are implementations for NS2 = available?

Thank you in advance.

 

Kind Regards, Nico Bayer

------=_NextPart_000_007C_01C4CB27.E9D21980-- --===============2054644659== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2054644659==-- From manet-bounces@ietf.org Mon Nov 15 12:21:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12098 for ; Mon, 15 Nov 2004 12:21:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTkZp-00038N-OA for manet-web-archive@ietf.org; Mon, 15 Nov 2004 12:23:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTkR9-0001sD-Uv; Mon, 15 Nov 2004 12:14:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTkFe-0007tv-IA for manet@megatron.ietf.org; Mon, 15 Nov 2004 12:02:50 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10970 for ; Mon, 15 Nov 2004 12:02:47 -0500 (EST) Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTkHg-0002pv-5V for manet@ietf.org; Mon, 15 Nov 2004 12:04:57 -0500 Received: from [192.168.2.19] (lina23.tts.lth.se [130.235.18.83]) by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id SAA09436 for ; Mon, 15 Nov 2004 18:02:00 +0100 (MET) Message-ID: <4198E0E9.7070606@telecom.lth.se> Date: Mon, 15 Nov 2004 18:01:29 +0100 From: Ali Hamidian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit Subject: [manet] broadcasting in 802.11 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Hi, Using 802.11, no control frames are used for broadcast packets, so they are "unreliable" and a station never knows if a broadcast message was received by its neighbors or not. Now my question is: How can a station broadcast a message and be sure that all its neighbors received the message? Is there any suggestions for extending 802.11 so that broadcast messages become "reliable"? Kind regards Ali _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 16 00:15:42 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04245 for ; Tue, 16 Nov 2004 00:15:42 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTvj4-0003dE-Km for manet-web-archive@ietf.org; Tue, 16 Nov 2004 00:17:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTveE-0003Lp-Ae; Tue, 16 Nov 2004 00:12:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTvdG-00033j-9y for manet@megatron.ietf.org; Tue, 16 Nov 2004 00:11:58 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04004 for ; Tue, 16 Nov 2004 00:11:56 -0500 (EST) Received: from avas3.olemiss.edu ([130.74.120.13]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTvfP-0003Z1-HK for manet@ietf.org; Tue, 16 Nov 2004 00:14:11 -0500 Received: from sunset.backbone.olemiss.edu (sunset [172.16.1.8]) by avas3.olemiss.edu (8.12.11/8.12.11) with ESMTP id iAG5BKvf027191 for ; Mon, 15 Nov 2004 23:11:20 -0600 (envelope-from srgopal@olemiss.edu) Received: from olemiss.edu (webmail.olemiss.edu [172.16.1.11]) by sunset.backbone.olemiss.edu (8.12.10+Sun/8.12.9) with ESMTP id iAG5BKiI012066 for ; Mon, 15 Nov 2004 23:11:20 -0600 (CST) From: "srgopal" To: manet@ietf.org X-Mailer: Quality Web Email v3.1e, http://netwinsite.com/refw.htm Date: Mon, 15 Nov 2004 23:11:20 -0600 Message-id: <41998bf8.a9.44e4.705901203@olemiss.edu> X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2004.11.15.5 X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [manet] Mathematicval distribution of real-time voice transmission! X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: srgopal@olemiss.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Dear all, Can anyone please tell me what mathematical (probability) distribution does real-time voice transmissions follow? I am trying to simulate mobile ad hoc networks for packet voice transmissions and analyze the call carrying capacity of the network. I guess that the talk spurt and the silence periods in a call follow exponential distribution? Isn't it? So for generation of voice packets i am planning to generate packets whereby my generator follow an exponential on/off distribution. Will this emulate real-time packet voice transmission? And also advice upon how to choose the call arrival rate and call duration rates? Please answer my questions. If anybody is working in similar areas please refer any previous work or publications. Thanks in advance. Regards, Raja. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 16 03:20:55 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03236 for ; Tue, 16 Nov 2004 03:20:55 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTycJ-0007Gf-4o for manet-web-archive@ietf.org; Tue, 16 Nov 2004 03:23:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTyVs-00018g-AA; Tue, 16 Nov 2004 03:16:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTyNc-0008G9-K5 for manet@megatron.ietf.org; Tue, 16 Nov 2004 03:08:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01979 for ; Tue, 16 Nov 2004 03:07:59 -0500 (EST) From: Raphael-a.MASSIN@fr.thalesgroup.com Received: from gwout.thalesgroup.com ([195.101.39.227]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTyPm-0006wN-Gf for manet@ietf.org; Tue, 16 Nov 2004 03:10:14 -0500 Received: from thalescan.corp.thales (200.3.2.3) by GWOUT.thalesgroup.com (NPlex 6.5.026) id 4196E019000C9A27 for manet@ietf.org; Tue, 16 Nov 2004 09:07:14 +0100 Received: from hiplex.tsbh.thales ([10.33.19.4]) by thalescan with InterScan Messaging Security Suite; Tue, 16 Nov 2004 09:06:26 +0100 Received: from hiplex.tsbh.thales (10.33.21.5) by hiplex.tsbh.thales (NPlex 6.5.026) id 4198ECC500003777 for manet@ietf.org; Tue, 16 Nov 2004 09:06:26 +0100 Received: from complex.tcfr.thales ([202.3.3.26]) by hiplex with InterScan Messaging Security Suite; Tue, 16 Nov 2004 09:06:25 +0100 Received: from complex.tcfr.thales (202.3.3.26) by complex.tcfr.thales (NPlex 6.5.026) id 4180F16800075B95 for manet@ietf.org; Tue, 16 Nov 2004 09:05:38 +0100 Received: from NODALNET.clb.tcfr.thales ([146.11.5.4]) by complex with InterScan Messaging Security Suite; Tue, 16 Nov 2004 09:05:38 +0100 Received: by NODALNET.clb.tcfr.thales with Internet Mail Service (5.5.2653.19) id ; Tue, 16 Nov 2004 09:06:25 +0100 Message-ID: <1BECC1DBB19ACE41AD81FA2E9B53750C0224EA76@khephren.clb.tcfr.thales> To: srgopal@olemiss.edu Subject: RE: [manet] Mathematicval distribution of real-time voice transmi ssion! Date: Tue, 16 Nov 2004 09:06:29 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Score: 0.3 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Hi Raja, Heve a look at the paper "Modelling Approach for VoIP Traffic Aggregations for Transferring Tele-traffic Trunks in a QoS enabled IP-Backbone Environment", from Jorn Seger. Here the Gamma distribution is mentionned for length of spurts and the Weibull distribution for length of silence. Raphael -----Message d'origine----- De : srgopal [mailto:srgopal@olemiss.edu] Envoye : mardi 16 novembre 2004 06:11 A : manet@ietf.org Objet : [manet] Mathematicval distribution of real-time voice transmission! Dear all, Can anyone please tell me what mathematical (probability) distribution does real-time voice transmissions follow? I am trying to simulate mobile ad hoc networks for packet voice transmissions and analyze the call carrying capacity of the network. I guess that the talk spurt and the silence periods in a call follow exponential distribution? Isn't it? So for generation of voice packets i am planning to generate packets whereby my generator follow an exponential on/off distribution. Will this emulate real-time packet voice transmission? And also advice upon how to choose the call arrival rate and call duration rates? Please answer my questions. If anybody is working in similar areas please refer any previous work or publications. Thanks in advance. Regards, Raja. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 16 05:42:00 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13029 for ; Tue, 16 Nov 2004 05:42:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU0or-0001by-1r for manet-web-archive@ietf.org; Tue, 16 Nov 2004 05:44:17 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU0f3-000166-A1; Tue, 16 Nov 2004 05:34:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU0YM-00004s-Jv for manet@megatron.ietf.org; Tue, 16 Nov 2004 05:27:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12161 for ; Tue, 16 Nov 2004 05:27:12 -0500 (EST) Received: from mx1.iit.cnr.it ([146.48.98.40] helo=mx.iit.cnr.it) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU0aU-0001LK-Og for manet@ietf.org; Tue, 16 Nov 2004 05:29:30 -0500 Received: from localhost (mx.iit.cnr.it [127.0.0.1]) by mx.iit.cnr.it (Postfix) with ESMTP id 286C22EE62 for ; Tue, 16 Nov 2004 11:26:36 +0100 (CET) Received: from mx.iit.cnr.it ([127.0.0.1]) by localhost (mx.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26232-13 for ; Tue, 16 Nov 2004 11:26:25 +0100 (CET) Received: from delmastro1 (delmastrof.iit.cnr.it [146.48.98.74]) by mx.iit.cnr.it (Postfix) with ESMTP id ABE492EE8E for ; Tue, 16 Nov 2004 11:26:24 +0100 (CET) Message-ID: <012e01c4cbc6$beab7f90$4a623092@delmastro1> From: "Franca Delmastro" To: Date: Tue, 16 Nov 2004 11:26:30 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by Content Checker at iit.cnr.it X-Spam-Score: 0.7 (/) X-Scan-Signature: d4673ea769cc9931269061744af205ce Subject: [manet] [WoWMoM 2005] Last Cfp: Submission Deadline November 20 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0406818922==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.7 (/) X-Scan-Signature: 7f3077fcbbd2d4a1504dfa044ebcf773 This is a multi-part message in MIME format. --===============0406818922== Content-Type: multipart/alternative; boundary="----=_NextPart_000_012B_01C4CBCF.1EDF5C80" This is a multi-part message in MIME format. ------=_NextPart_000_012B_01C4CBCF.1EDF5C80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ----- Original Message -----=20 From: Franca Delmastro=20 To: Franca Delmastro=20 Sent: Tuesday, November 16, 2004 9:17 AM Subject: [WoWMoM 2005] Last Cfp: Submission Deadline November 20 -------------------------------------------------------------------------= We apologize in advance if you receive multiple copies of this CFP. ************************************************************* CALL FOR PAPERS WoWMoM 2005 IEEE International Symposium on a World of Wireless, Mobile and Multimedia Networks http://cnd.iit.cnr.it/wowmom2005 Taormina, Italy, June 13-16, 2005 Sponsored by The IEEE Computer Society The University of Texas at Arlington Technical sponsored by IEEE TCCC **** Submission Deadline --- November 10, 2004 **** Extended to November 20, 2004 ************************************************************** Technology evolution is driving toward a world of wireless, mobile, and multimedia pervasive communications where users can seamlessly and ubiquitously accomplish their tasks, access information or communicate with other users all the anytime, everywhere, and from any device. Technologies include, among others, IEEE 802.11, 802.15, 802.16, Mobile IP, micro-mobility protocols, IP paging, wireless IP QOS, mobile ad hoc and sensor networks, and cellular networks. In addition to these, new and emerging technologies (e.g., UWB) need to be taken into account. The resulting networking environment will constitute the fourth generation wireless networks. 4G will integrate different types of wireless networks with wire-line backbone network seamlessly, and provide the convergence of voice, multimedia and data traffic over a single IP based core network. WoWMoM 2005 technical program committee is soliciting papers addressing the research challenges toward a world of wireless, mobile, and multimedia pervasive communications. Two types of contributions will be accepted: FULL PAPERS: Full Papers must present original, previously unpublished, complete works, validated by experimentation, simulation, or analysis. Practical experiences and experimental efforts are welcome. POSITION PAPERS: Papers in this category must be visionary, innovative and forward-looking. They must offer new perspectives opening future research directions, rather than by presenting mature work with quantitative results. Only a limited number of slots will be available for position papers that will be reviewed primarily for relevance and originality. Topics of interest for WOWMOM 2005 include, but are not limited to: - System prototypes and experiences - Software technologies and systems - QoS for real-time voice and video in wireless networks - Interactive broadband television, gaming, and video distribution - Middleware support for QoS provision - Caching and content management in WLANs and WMANs - Differentiated service in wireless multimedia networks - IP-based multimedia services over wireless networks - Networking services for ambient intelligent and pervasive environments - Multicasting and broadcasting problems and solutions - Handoff and mobility management - Seamless internetworking - IP-based mobile networks - Location mechanism and services - Wireless BAN, PAN, LAN, and MAN - Ad hoc and sensor networks - Vehicular wireless networks - Access technologies - Third and fourth generation systems - Energy-efficient protocols and power management - Wireless security and authentication - Pricing and billing - Modeling and Performance evaluation PAPER SUBMISSION AND PUBLICATION =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 Papers should neither have been published elsewhere nor currently under review by another conference or journal. Guidelines on paper submission and formatting will be provided on the website. Accepted papers will appear in the symposium proceedings published by IEEE. IMPORTANT DATES =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Full papers due: November 10, 2004 Extended to: November 20, 2004 Notification: January 20, 2005 Camera Ready due: February 15, 2005 ORGANIZING COMMITTEE =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D GENERAL Co-Chairs: Giuseppe Anastasi, University of Pisa, Italy Sajal K. Das, The University of Texas at Arlington, USA PROGRAM Co-Chairs: Marco Conti, IIT-CNR, Italy Dipankar Raychaudhuri WINLAB/Rutgers University, USA FINANCE & REGISTRATION Chair: Yonghe Liu, The University of Texas at Arlington, USA PUBLICITY Co-Chairs: Mainak Chatterjee, Univ. Central Florida, USA Sunghyun Choi, Seoul National University, Korea Franca Delmastro, IIT-CNR, Italy PUBLICATION Co-Chairs: Eleonora Borgia, IIT-CNR, Italy Luciana Pelusi, IIT-CNR, Italy SPONSORSHIP Chair Alessandro Genco, University of Palermo, Italy LOCAL ARRANGEMENTS Chair: Antonio Puliafito, University of Messina, Italy WEB DESIGNER & MANAGER: Patrizia Andronico, IIT-CNR, Italy STEERING COMMITTEE =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Marco Conti, IIT-CNR, Italy Sajal K. Das, The University of Texas at Arlington, USA (chair) Dipankar Raychaudhuri WINLAB/Rutgers University, USA Satish K. Tripathi, SUNY Buffalo, USA PROGRAM COMMITTEE =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Arup Acharya, IBM T.J. Watson Research, USA Dharma P. Agrawal, University of Cincinnati, USA Kevin C. Almeroth, University of California at Santa Barbara, USA Christian Becker, University of Stuttgart, Germany Giuseppe Bianchi, University of Rome "Tor Vergata", Italy Chris Blondia, University of Antwerp, Belgium Azzedine Boukerche, University of Ottawa, Canada Jiannong Cao, Hong Kong Polytechnic University, Hong Kong Chua Kee Chaing, National University of Singapore, Republic of Singapore Rajarathnam Chandramouili, Stevens Institute of Technology, USA Mainak Chatterjee, University of Central Florida, USA Carla-Fabiana Chiasserini, Polytechnic of Turin, Italy A. Chockalingam, Indian Institute of Science, Banglore, India Sunghyun Choi, Seoul National University, Korea Antonio Corradi, University of Bologna, Italy Antony Ephremides, University of Maryland, USA Gabor Fodor, Ericsson, Sweden Luigi Fratta, Polytechnic of Milan, Italy Marco Gruteser, Rutgers University, USA Paul J.M. Havinga, University of Twente, The Netherlands Kazuo Imai, NTT DoCoMo, Japan Holger Karl, Universtit=E4t Paderborn, Germany Anurag Kumar, Indian Inst of Science, Bangalore, India Mohan Kumar, The University of Texas at Arlington, USA P. R. Kumar, University of Illinois, USA Masahiro Kuroda, National Institute of Info. and Com. Tech., Japan Luciano Lenzini, University of Pisa, Italy K. Ben Letaief, Hong Kong Univ. Science & Technology, Hong Kong Victor Leung, The University of British Columbia, Canada Yonghe Liu, Univ. Texas at Arlington, USA Giri Mandyam, Nokia Research Center, USA Martin Mauve, University of Dusseldorf, Germany Archan Misra, IBM T.J. Watson Research, USA Refik Molva, Institut Eurecom, France Giacomo Morabito, University of Catania, Italy Hiroyuki Morikawa, , University of Tokyo, Japan Stephan Olariu, Old Dominion University, USA Maximilian Ott, Semandex Networks, USA Michael Paterakis, Technical University of Crete, Greece George C. Polyzos, Athens University of Economics and Business, Greece Antonio Puliafito, University of Messina, Italy Jochen H. Schiller, Freie Universit=E4t Berlin, Germany Henning Schulzrinne, Columbia University, USA Rajeev Shorey, IBM India Research Lab, India Ivan Stojmenovic, University of Ottawa, Canada Violet R. Syrotiuk, Arizona State University, USA Wade Trappe, Rutgers University, USA Ooi Wei Tsang, National University of Singapore, Singapore Christian Tschudin, Basel University, Switzerland Thierry Turletti, INRIA France Andras Valko, Ericsson, Hungary Bernard Walke, Aachen University of Technology, Germany Xingwei Wang, Northeastern Univ, China Jie Wu, Florida Atlantic University, USA Gergely Zaruba, The University of Texas at Arlington, USA Roger Zimmerman, University of Southern California, USA ************************************************************ Franca Delmastro Pervasive Computing & Networking Lab. (PerLab) IIT- National Research Council via G. Moruzzi,1 56124 Pisa, Italy ******************************************************** ------=_NextPart_000_012B_01C4CBCF.1EDF5C80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
----- Original Message -----=20
From: Franca Delmastro
Sent: Tuesday, November 16, 2004 9:17 AM
Subject: [WoWMoM 2005] Last Cfp: Submission Deadline = November=20 20

 
----------------------------------------------------------------= ---------

We apologize in advance if you = receive multiple=20 copies of this=20 CFP.
*************************************************************

          &nbs= p;         &nbs= p;  =20 CALL FOR PAPERS

          &nbs= p;         &nbs= p;    =20 WoWMoM 2005
         IEEE=20 International Symposium on a World of=20 Wireless,
          =        =20 Mobile and Multimedia=20 Networks

         &nb= sp;      =20 http://cnd.iit.cnr.it/wowmom2005
      &= nbsp;        =20 Taormina, Italy, June 13-16,=20 2005

          &= nbsp;         &= nbsp;    =20 Sponsored=20 by
           <= SPAN>       =20 The IEEE Computer=20 Society
          &n= bsp; =20 The University of Texas at=20 Arlington
          =    =20 Technical sponsored by IEEE=20 TCCC

        **** Submission = Deadline=20 --- November 10, 2004 ****
          &nbs= p;            = ; =20  Extended to November 20,=20 2004
**********************************************************= ****


Technology=20 evolution is driving toward a world of wireless,
mobile, and = multimedia=20 pervasive communications where users can
seamlessly and ubiquitously=20 accomplish their tasks, access information
or communicate with other = users=20 all the anytime, everywhere, and from
any device. Technologies = include, among=20 others, IEEE 802.11,
802.15, 802.16, Mobile IP, micro-mobility = protocols, IP=20 paging,
wireless IP QOS, mobile ad hoc and sensor networks, and=20 cellular
networks.
In addition to these, new and emerging = technologies=20 (e.g., UWB) need to
be taken into account.  The resulting = networking=20 environment will
constitute the fourth generation wireless networks. = 4G will=20 integrate
different types of wireless networks with wire-line = backbone=20 network
seamlessly, and provide the convergence of voice, multimedia=20 and
data traffic over a single IP based core network.  WoWMoM = 2005=20 technical
program committee is soliciting papers addressing the=20 research
challenges
toward a world of wireless, mobile, and = multimedia=20 pervasive
communications.
Two types of contributions will be=20 accepted:

FULL PAPERS: Full Papers must present original, = previously=20 unpublished,
complete works, validated by experimentation, = simulation, or=20 analysis.
Practical experiences and experimental efforts are=20 welcome.

POSITION PAPERS: Papers in this category must be = visionary,=20 innovative
and forward-looking. They must offer new perspectives = opening=20 future
research directions, rather than by presenting mature work=20 with
quantitative results. Only a limited number of slots will be=20 available
for
position papers that will be reviewed primarily for=20 relevance and
originality.

Topics of interest for WOWMOM 2005 = include,=20 but are not limited to:
- System prototypes and experiences
- = Software=20 technologies and systems
- QoS for real-time voice and video in = wireless=20 networks
- Interactive broadband television, gaming, and video=20 distribution
- Middleware support for QoS provision
- Caching and = content=20 management in WLANs and WMANs
- Differentiated service in wireless = multimedia=20 networks
- IP-based multimedia services over wireless networks
-=20 Networking services for ambient intelligent and pervasive = environments
-=20 Multicasting and broadcasting problems and solutions
- Handoff and = mobility=20 management
- Seamless internetworking
- IP-based mobile=20 networks
- Location mechanism and = services
- Wireless=20 BAN, PAN, LAN, and MAN
- Ad hoc and sensor networks
- Vehicular = wireless=20 networks
- Access technologies
- Third and fourth generation = systems
-=20 Energy-efficient protocols and power management
- Wireless security = and=20 authentication
- Pricing and billing
- Modeling and Performance=20 evaluation

PAPER SUBMISSION AND=20 PUBLICATION
=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
Papers should neither have been = published=20 elsewhere nor currently
under review by another conference or = journal. =20 Guidelines on paper
submission and formatting will be = provided on=20 the website.
Accepted papers will appear in the symposium proceedings = published by
IEEE.


IMPORTANT = DATES
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Full=20 papers due:        November 10,=20 2004
Extended to:     = November 20,=20 2004
Notification:        &nb= sp; =20 January 20, 2005
Camera Ready = due:      =20 February 15, 2005


ORGANIZING COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=
GENERAL=20 Co-Chairs:
        Giuseppe = Anastasi,=20 University of Pisa, Italy
        = Sajal K.=20 Das, The University of Texas at Arlington, USA

PROGRAM=20 Co-Chairs:
        Marco Conti, = IIT-CNR,=20 Italy
        Dipankar = Raychaudhuri=20 WINLAB/Rutgers University, USA


FINANCE & REGISTRATION=20 Chair:
         Yonghe Liu, = The=20 University of Texas at Arlington, USA
PUBLICITY=20 Co-Chairs:
         Mainak=20 Chatterjee, Univ. Central Florida,=20 USA
         Sunghyun Choi, = Seoul=20 National University, Korea
        =20 Franca Delmastro, IIT-CNR, Italy


PUBLICATION Co-Chairs:
        =20 Eleonora Borgia, IIT-CNR, Italy
        =20 Luciana Pelusi, IIT-CNR, Italy


SPONSORSHIP Chair
        Alessandro = Genco,=20 University of Palermo, Italy


LOCAL ARRANGEMENTS=20 Chair:
        Antonio Puliafito,=20 University of Messina, Italy


WEB DESIGNER &=20 MANAGER:
        Patrizia = Andronico,=20 IIT-CNR, Italy



STEERING=20 COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Ma= rco Conti, IIT-CNR, Italy
Sajal K. Das,=20 The University of Texas at Arlington, USA (chair)
Dipankar = Raychaudhuri=20 WINLAB/Rutgers University, USA
Satish K. Tripathi, SUNY Buffalo,=20 USA


PROGRAM = COMMITTEE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Arup = Acharya, IBM T.J.=20 Watson Research, USA
Dharma P. Agrawal, University of Cincinnati,=20 USA
Kevin C. Almeroth, University of California at Santa Barbara,=20 USA
Christian Becker, University of Stuttgart, Germany
Giuseppe = Bianchi,=20 University of Rome "Tor Vergata", Italy
Chris Blondia, University of = Antwerp,=20 Belgium
Azzedine  Boukerche, University of Ottawa, = Canada
Jiannong=20 Cao, Hong Kong Polytechnic University, Hong Kong
Chua Kee Chaing, = National=20 University of Singapore, Republic of Singapore
Rajarathnam = Chandramouili,=20 Stevens Institute of Technology, USA
Mainak Chatterjee, University of = Central=20 Florida, USA
Carla-Fabiana Chiasserini, Polytechnic of Turin, = Italy
A.=20 Chockalingam, Indian Institute of Science, Banglore, India
Sunghyun = Choi,=20 Seoul National University, Korea
Antonio Corradi, University of = Bologna,=20 Italy
Antony Ephremides, University of Maryland, USA
Gabor Fodor,=20 Ericsson, Sweden
Luigi Fratta, Polytechnic of Milan, Italy
Marco = Gruteser,=20 Rutgers University, USA
Paul J.M. Havinga, University of Twente, The=20 Netherlands
Kazuo Imai, NTT DoCoMo, Japan
Holger Karl, Universtit=E4t = Paderborn,=20 Germany
Anurag Kumar, Indian Inst of = Science, Bangalore,=20 India
Mohan Kumar, The University of Texas at Arlington, USA
P. R. = Kumar,=20 University of Illinois, USA
Masahiro Kuroda, National Institute of = Info. and=20 Com. Tech., Japan
Luciano Lenzini, University of Pisa, Italy
K. = Ben=20 Letaief, Hong Kong Univ. Science & Technology, Hong Kong
Victor = Leung,=20 The University of British Columbia, Canada
Yonghe Liu, Univ. Texas at = Arlington,=20 USA
Giri Mandyam, Nokia Research Center, = USA
Martin Mauve, University of Dusseldorf, Germany
Archan Misra, = IBM T.J.=20 Watson Research, USA
Refik Molva, Institut Eurecom, France
Giacomo = Morabito, University of Catania, Italy
Hiroyuki Morikawa, , = University of=20 Tokyo, Japan
Stephan Olariu, Old Dominion University, = USA
Maximilian Ott,=20 Semandex Networks, USA
Michael Paterakis, Technical University of = Crete,=20 Greece
George C. Polyzos, Athens University of Economics and = Business,=20 Greece
Antonio Puliafito, University of Messina, Italy
Jochen H. = Schiller,=20 Freie Universit=E4t Berlin, Germany
Henning Schulzrinne, Columbia = University,=20 USA
Rajeev Shorey, IBM India Research Lab, India
Ivan Stojmenovic, = University of Ottawa, Canada
Violet R. Syrotiuk, Arizona State = University,=20 USA
Wade Trappe, Rutgers University, USA
Ooi Wei Tsang, National=20 University of Singapore, Singapore
Christian Tschudin, Basel = University,=20 Switzerland
Thierry Turletti, INRIA France
Andras Valko, Ericsson, = Hungary
Bernard Walke, Aachen University of Technology, = Germany
Xingwei=20 Wang, Northeastern Univ, China
Jie Wu, Florida Atlantic University,=20 USA
Gergely Zaruba, The University of = Texas at=20 Arlington, USA
Roger Zimmerman, University of = Southern=20 California, USA
 
************************************************************
= Franca=20 Delmastro
Pervasive Computing & Networking Lab. = (PerLab)
 
IIT- National Research = Council
via G.=20 Moruzzi,1
56124 Pisa,=20 Italy
********************************************************<= /DIV> ------=_NextPart_000_012B_01C4CBCF.1EDF5C80-- --===============0406818922== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0406818922==-- From manet-bounces@ietf.org Tue Nov 16 09:56:54 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04348 for ; Tue, 16 Nov 2004 09:56:54 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU4nZ-0007Hi-VZ for manet-web-archive@ietf.org; Tue, 16 Nov 2004 09:59:14 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU4ds-00074H-E7; Tue, 16 Nov 2004 09:49:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU4W9-00061B-2m for manet@megatron.ietf.org; Tue, 16 Nov 2004 09:41:13 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03196 for ; Tue, 16 Nov 2004 09:41:11 -0500 (EST) Received: from ms-smtp-02-lbl.southeast.rr.com ([24.25.9.101] helo=ms-smtp-02-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU4YC-0006t6-Qo for manet@ietf.org; Tue, 16 Nov 2004 09:43:31 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-02-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iAGEew4R020527 for ; Tue, 16 Nov 2004 09:40:59 -0500 (EST) From: "Christopher P. Rigano" To: Subject: RE: [manet] RE: uppper layers used with MANETs are they just TCP/UDP IP? Date: Tue, 16 Nov 2004 09:40:58 -0500 Message-ID: <003a01c4cbea$493c4950$0300a8c0@CPQ73745201364> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal In-reply-to: <000901c4c9cc$07d4bb70$0300a8c0@CPQ73745201364> X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.2 (/) X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1022403381==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: a4a24b484706be629f915bfb1a3e4771 This is a multi-part message in MIME format. --===============1022403381== Content-Type: multipart/alternative; boundary="----=_NextPart_000_003B_01C4CBC0.60664150" This is a multi-part message in MIME format. ------=_NextPart_000_003B_01C4CBC0.60664150 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings all, I understand that MANETs exist "on top of "a physical and link/MAC layer. MANETs to a great extent are topology or layer 3 (network). What protocols are currently used to run "on top of" MANETs are they mostly TCP/UDP with IP addresses as nodes? What variants then are used? What other protocols provide transport and session capabilities? Thanks and regards, Christopher ------=_NextPart_000_003B_01C4CBC0.60664150 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

 

Greetings = all,

 

I understand that MANETs = exist “on top of “a physical and link/MAC layer. MANETs to a great = extent are topology or layer 3 (network). What protocols are currently used to = run “on top of” MANETs are they mostly TCP/UDP with IP addresses = as nodes? What variants then are used? What other protocols provide = transport and session capabilities?

 

Thanks and = regards,

 

Christopher

------=_NextPart_000_003B_01C4CBC0.60664150-- --===============1022403381== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1022403381==-- From manet-bounces@ietf.org Tue Nov 16 09:59:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04585 for ; Tue, 16 Nov 2004 09:59:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU4q7-0007Mw-El for manet-web-archive@ietf.org; Tue, 16 Nov 2004 10:01:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU4dt-00074m-SP; Tue, 16 Nov 2004 09:49:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU4WK-00065n-Cl for manet@megatron.ietf.org; Tue, 16 Nov 2004 09:41:24 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03212 for ; Tue, 16 Nov 2004 09:41:23 -0500 (EST) Received: from ms-smtp-04-lbl.southeast.rr.com ([24.25.9.103] helo=ms-smtp-04-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU4YY-0006tt-7G for manet@ietf.org; Tue, 16 Nov 2004 09:43:42 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-04-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iAGEfJCh019499; Tue, 16 Nov 2004 09:41:21 -0500 (EST) From: "Christopher P. Rigano" To: "'Christopher P. Rigano'" , Subject: RE: [manet] 802.16a, e and 802.20 OPNET Modules Date: Tue, 16 Nov 2004 09:41:20 -0500 Message-ID: <003f01c4cbea$565037a0$0300a8c0@CPQ73745201364> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal In-reply-to: <000b01c4cac4$9ce21700$0300a8c0@CPQ73745201364> X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 1.3 (+) X-Scan-Signature: 311e798ce51dbeacf5cdfcc8e9fda21b X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1811859608==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: e367d58950869b6582535ddf5a673488 This is a multi-part message in MIME format. --===============1811859608== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0040_01C4CBC0.6D7A2FA0" This is a multi-part message in MIME format. ------=_NextPart_000_0040_01C4CBC0.6D7A2FA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings, Does anyone know if there are 802.16a, e and 802.20 OPNET Modules available? I want to try and simulate MANETs over them. Thank and regards, Chris ------=_NextPart_000_0040_01C4CBC0.6D7A2FA0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

 

 

Greetings, =

 

Does anyone know if there = are 802.16a, e and 802.20 OPNET Modules available? I want to try and = simulate MANETs over them.

 

Thank and = regards,

 

Chris

------=_NextPart_000_0040_01C4CBC0.6D7A2FA0-- --===============1811859608== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1811859608==-- From manet-bounces@ietf.org Tue Nov 16 10:08:34 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05805 for ; Tue, 16 Nov 2004 10:08:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU4yq-0007d3-Gs for manet-web-archive@ietf.org; Tue, 16 Nov 2004 10:10:53 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU4t7-0003d1-Ok; Tue, 16 Nov 2004 10:04:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU4fJ-0007D5-NX for manet@megatron.ietf.org; Tue, 16 Nov 2004 09:50:41 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03878 for ; Tue, 16 Nov 2004 09:50:40 -0500 (EST) Received: from ms-smtp-03-lbl.southeast.rr.com ([24.25.9.102] helo=ms-smtp-03-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU4hW-00076s-NY for manet@ietf.org; Tue, 16 Nov 2004 09:52:59 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-03-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iAGEoZkc023580; Tue, 16 Nov 2004 09:50:37 -0500 (EST) From: "Christopher P. Rigano" To: , Date: Tue, 16 Nov 2004 09:50:35 -0500 Message-ID: <004401c4cbeb$a15853d0$0300a8c0@CPQ73745201364> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal In-reply-to: <20041116123022.1F49034006@mx2.su.se> X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.1 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Content-Transfer-Encoding: 7bit Subject: [manet] continuing SIP bearer in Mobile environments X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit I am doing some research with MANETs and Wireless using SIP to establish video streams in Mpeg4. Are there any ways to maintain packet flow when crossing cells/domains other than MIP? How about the via field? Any ideas? Thanks mates! Chris _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 16 13:21:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26713 for ; Tue, 16 Nov 2004 13:21:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU7zZ-00044B-IB for manet-web-archive@ietf.org; Tue, 16 Nov 2004 13:23:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU7ri-0000n2-7E; Tue, 16 Nov 2004 13:15:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU7iB-0007U5-HY for manet@megatron.ietf.org; Tue, 16 Nov 2004 13:05:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25421 for ; Tue, 16 Nov 2004 13:05:49 -0500 (EST) Received: from smtp02.ya.com ([62.151.11.161] helo=smtp.ya.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU7kF-0003i8-Rz for manet@ietf.org; Tue, 16 Nov 2004 13:08:11 -0500 Received: from [62.151.11.36] (helo=ispwebmail02) by smtp.ya.com with smtp id 1CU7ht-00079y-00; Tue, 16 Nov 2004 19:05:33 +0100 Date: Tue, 16 Nov 2004 19:05:33 +0100 From: "llasax@ya.com " To: "manet@ietf.org" Xmailer: Mixmail Server 3.0 X-Priority: 3 MIME-Version: 1.0 Content-type: text/plain Content-Transfer-Encoding: quoted-printable Message-Id: X-Spam-Score: 0.8 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Content-Transfer-Encoding: quoted-printable Subject: [manet] Kernel changes with multirouting X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: llasax@ya.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: quoted-printable I'm woking with AODV_UU implementation trying to add QoS in a route. I would need to know if somebody knows how to add in the Linux kernel routing table multiple routes to the same destination. Thanks!!! Emma Gispert _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 16 14:28:30 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02515 for ; Tue, 16 Nov 2004 14:28:29 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU92R-0005cz-BA for manet-web-archive@ietf.org; Tue, 16 Nov 2004 14:30:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU8rx-00037z-IT; Tue, 16 Nov 2004 14:20:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU8oy-0002kv-3Y for manet@megatron.ietf.org; Tue, 16 Nov 2004 14:16:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01309 for ; Tue, 16 Nov 2004 14:16:54 -0500 (EST) Received: from stl-smtpout-01.boeing.com ([130.76.96.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU8rD-0005Lb-V2 for manet@ietf.org; Tue, 16 Nov 2004 14:19:16 -0500 Received: from stl-av-01.boeing.com ([192.76.190.6]) by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id NAA29519; Tue, 16 Nov 2004 13:16:23 -0600 (CST) Received: from XCH-NWBH-02.nw.nos.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id iAGJGNN18829; Tue, 16 Nov 2004 13:16:23 -0600 (CST) Received: from XCH-NW-09.nw.nos.boeing.com ([192.42.226.84]) by XCH-NWBH-02.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 16 Nov 2004 11:16:21 -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.6603.0 Subject: RE: [manet] Kernel changes with multirouting Date: Tue, 16 Nov 2004 11:16:21 -0800 Message-ID: <2B3DC5CC87DC754E8EF8B9271F91AA270427A8A9@xch-nw-09.nw.nos.boeing.com> Thread-Topic: [manet] Kernel changes with multirouting Thread-Index: AcTMChfXJB/D4cEJT5S5pfpx6h4tJwABpHtA From: "Ahrenholz, Jeffrey M" To: , X-OriginalArrivalTime: 16 Nov 2004 19:16:21.0948 (UTC) FILETIME=[C1FF17C0:01C4CC10] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: quoted-printable Emma, If you are using the rtnetlink socket interface in your Linux program, you can set the rtm_tos or rtm_table fields of your route message (struct rtmsg) when you send your add/delete messages to the kernel. (See the file /usr/include/linux/rtnetlink.h) You can also do this using the "ip route" command. =20 -Jeff > -----Original Message----- > From: llasax@ya.com [mailto:llasax@ya.com]=20 > Sent: Tuesday, November 16, 2004 10:06 AM > To: manet@ietf.org > Subject: [manet] Kernel changes with multirouting >=20 >=20 >=20 > I'm woking with AODV_UU implementation trying to add QoS in a=20 > route. > I would need to know if somebody knows how to add in the=20 > Linux kernel routing table multiple routes to the same=20 > destination. >=20 > Thanks!!! Emma Gispert > =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 manet-bounces@ietf.org Tue Nov 16 15:02:24 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06045 for ; Tue, 16 Nov 2004 15:02:24 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU9ZF-0006Ws-RL for manet-web-archive@ietf.org; Tue, 16 Nov 2004 15:04:46 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU9Ny-0000UX-5l; Tue, 16 Nov 2004 14:53:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU9FT-0006xV-G7 for manet@megatron.ietf.org; Tue, 16 Nov 2004 14:44:19 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04407 for ; Tue, 16 Nov 2004 14:44:17 -0500 (EST) Received: from animal.inescn.pt ([192.35.246.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU9HW-000667-CD for manet@ietf.org; Tue, 16 Nov 2004 14:46:39 -0500 Received: from localhost (localhost [127.0.0.1]) by animal.inescn.pt (8.12.10/8.12.11/19) with ESMTP id iAGJhmUI026122; Tue, 16 Nov 2004 19:43:48 GMT Received: from bart.inescn.pt (root@bart.inescn.pt [192.35.246.9]) by animal.inescn.pt (8.12.10/8.12.10/7) with ESMTP id iAGJgq9s025985; Tue, 16 Nov 2004 19:42:52 GMT Received: from [194.117.24.133] (woodstock.inescn.pt [194.117.24.133]) by bart.inescn.pt (8.12.5/INESCP-V2.12) with ESMTP id iAGJgpxx029905; Tue, 16 Nov 2004 19:42:52 GMT Message-ID: <419A5903.9020908@inescporto.pt> Date: Tue, 16 Nov 2004 14:46:11 -0500 From: Filipe Abrantes User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: llasax@ya.com, manet@ietf.org Subject: Re: [manet] Kernel changes with multirouting References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at inescporto.pt X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 7bit Hi Emma, Please take a look at: http://www.lartc.org/howto/lartc.rpdb.multiple-links.html#AEN298 , specially 4.2.2 section. Best Regards Filipe llasax@ya.com wrote: > I'm woking with AODV_UU implementation trying to add QoS in a > route. > I would need to know if somebody knows how to add in the > Linux kernel routing table multiple routes to the same > destination. > > Thanks!!! Emma Gispert > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > -- Filipe Lameiro Abrantes INESC Porto Campus da FEUP Rua Dr. Roberto Frias, 378 4200-465 Porto Portugal Phone: +351 22 209 4266 E-mail: fla@inescporto.pt Web: http://yang.inescporto.pt/~fabrantes/homepage _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 16 15:47:53 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11499 for ; Tue, 16 Nov 2004 15:47:53 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUAHH-0007al-P9 for manet-web-archive@ietf.org; Tue, 16 Nov 2004 15:50:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUABk-0003LN-MX; Tue, 16 Nov 2004 15:44:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUAA2-0002d7-VU for manet@megatron.ietf.org; Tue, 16 Nov 2004 15:42:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11042 for ; Tue, 16 Nov 2004 15:42:45 -0500 (EST) From: voberoi@mtu.edu Received: from mailoff.mtu.edu ([141.219.70.111]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUACI-0007V2-Jp for manet@ietf.org; Tue, 16 Nov 2004 15:45:08 -0500 Received: from node5.services.dcsint.mtu.edu (node5.mtu.edu [141.219.69.5]) by mailoff.mtu.edu (8.11.7p1+Sun/8.11.4) with ESMTP id iAGKghH12143 for ; Tue, 16 Nov 2004 15:42:43 -0500 (EST) Received: from node34.edge.dcsint.mtu.edu (node34.mtu.edu [141.219.69.34]) by node5.services.dcsint.mtu.edu (8.12.10/8.12.8) with ESMTP id iAGKggiv005991 for ; Tue, 16 Nov 2004 15:42:43 -0500 Received: from mail.mtu.edu (campus4.mtu.edu [141.219.70.7]) by node34.edge.dcsint.mtu.edu (8.12.11/8.12.11) with ESMTP id iAGKggwD026559 for ; Tue, 16 Nov 2004 15:42:42 -0500 (envelope-from voberoi@mtu.edu) Received: from node6.services.dcsint.mtu.edu (node6.mtu.edu [141.219.69.6]) by mail.mtu.edu (8.11.7p1+Sun/8.11.6) with ESMTP id iAGKgf426332 for ; Tue, 16 Nov 2004 15:42:41 -0500 (EST) Received: from huskymail.mtu.edu (node72.mtu.edu [141.219.69.72]) by node6.services.dcsint.mtu.edu (8.12.10/8.12.3/auth_ssl.mc v1.0) with SMTP id iAGKgfwT016429 for ; Tue, 16 Nov 2004 15:42:41 -0500 Received: from 141.219.193.31 (SquirrelMail authenticated user voberoi) by huskymail.mtu.edu with HTTP; Tue, 16 Nov 2004 15:42:41 -0500 (EST) Message-ID: <2507.141.219.193.31.1100637761.squirrel@huskymail.mtu.edu> Date: Tue, 16 Nov 2004 15:42:41 -0500 (EST) To: manet@ietf.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.0.0, Antispam-Data: 2004.11.16.3 X-PerlMx-Spam: Gauge=X, Probability=10%, Report='PRIORITY_NO_NAME 0.716, NO_REAL_NAME 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_PRIORITY 0, __MIME_VERSION 0, __SANE_MSGID 0' X-Spam-Score: 1.1 (+) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 8bit Subject: [manet] single versus dual channel for MAC X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 8bit Hi, Iam presently studying some of the MAC protocols proposed for wireless ad hoc networks. Some of them make use of a separate signalling channel for RTS/ CTS packets and also send a busy tone over the same channel and they send data over another channel. One such protocol is PAMAS. I wanted to know what is the additional complexity and cost of having this separate channel and whehter this approach is better than having a single channel? Thankyou Your help is really appreciated. Vikram Oberoi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 16 17:56:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05831 for ; Tue, 16 Nov 2004 17:56:18 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUCHa-00069n-Lk for manet-web-archive@ietf.org; Tue, 16 Nov 2004 17:58:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUC3K-0008Fd-OW; Tue, 16 Nov 2004 17:43:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUBtg-0001Ki-Mr for manet@megatron.ietf.org; Tue, 16 Nov 2004 17:34:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02748 for ; Tue, 16 Nov 2004 17:33:58 -0500 (EST) Received: from web50910.mail.yahoo.com ([206.190.39.38]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CUBvx-0005GT-I6 for manet@ietf.org; Tue, 16 Nov 2004 17:36:23 -0500 Received: (qmail 52128 invoked by uid 60001); 16 Nov 2004 22:33:28 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=V8o+ddx3vr9Yi+pPzucWwnNV4imSKR8cTJxtmJr/Schk2EJR/G0Ee651Lah3iyNPQuEZ9Wbm7I52SFYgW7MAR61lc7nWC8MO9sSnKb94wEUFlRjJYfSyiaar9w3V/Z0mV+l0OhJ4I+em1tnX3aAqz3g9h19jehLMnVCkHCjiU/k= ; Message-ID: <20041116223328.52126.qmail@web50910.mail.yahoo.com> Received: from [193.63.148.178] by web50910.mail.yahoo.com via HTTP; Tue, 16 Nov 2004 14:33:28 PST Date: Tue, 16 Nov 2004 14:33:28 -0800 (PST) From: chitra balakrishnan To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Subject: [manet] ZRP problem X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2034226148==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 --===============2034226148== Content-Type: multipart/alternative; boundary="0-1138590802-1100644408=:52089" --0-1138590802-1100644408=:52089 Content-Type: text/plain; charset=us-ascii Hi, I 'm trying to study ZRP , have used the implementation by prashant inamti on ns-2.1b9 , the demo3_rad3.tcl is giving errors. Simulation ends very abruptly at _14_ [0.175208] | checking outer route expirations. | None expired. (null) - invalid packet type (undefined) Can anyone help me on this. I havent been able to run any TCL script using ZRP on this. Is there a different version of ZRP implementation available . --Chitra __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-1138590802-1100644408=:52089 Content-Type: text/html; charset=us-ascii
Hi,
   I 'm trying to study ZRP , have used the implementation by prashant inamti on ns-2.1b9 , the demo3_rad3.tcl is giving errors.  Simulation ends very abruptly
 at
_14_ [0.175208] | checking outer route expirations. | None expired. (null) - invalid packet type (undefined)
 
 
Can anyone  help me on this. I havent been able to run any TCL script using ZRP on this.  Is there a different version of ZRP implementation available .
 
 
--Chitra
 
 

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-1138590802-1100644408=:52089-- --===============2034226148== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2034226148==-- From manet-bounces@ietf.org Wed Nov 17 05:23:00 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08947 for ; Wed, 17 Nov 2004 05:23:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUN0F-00050F-9g for manet-web-archive@ietf.org; Wed, 17 Nov 2004 05:25:31 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUMmt-0002sX-Pw; Wed, 17 Nov 2004 05:11:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUMiq-000258-5j for manet@megatron.ietf.org; Wed, 17 Nov 2004 05:07:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07553 for ; Wed, 17 Nov 2004 05:07:29 -0500 (EST) Received: from web90107.mail.scd.yahoo.com ([66.218.94.78]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CUMlD-0004eE-0a for manet@ietf.org; Wed, 17 Nov 2004 05:10:00 -0500 Received: (qmail 7057 invoked by uid 60001); 17 Nov 2004 10:06:59 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=Fq25Yw16wHz411ZmiOGskZdJ5NK7NsQ5WFZcAXbtFjGObrR3fNbnXek+Z8hntmDrZ3QySX0p0HGR2N3t99Trd/FiWvmSdRFSfetlRtS0LN99t8qzwKyqIchcxmtK9hAko5bqlfE2pgzA1jte8mfOAzM18+XwCIjYOBCTxkEIGAI= ; Message-ID: <20041117100658.7055.qmail@web90107.mail.scd.yahoo.com> Received: from [203.208.193.230] by web90107.mail.scd.yahoo.com via HTTP; Wed, 17 Nov 2004 02:06:58 PST Date: Wed, 17 Nov 2004 02:06:58 -0800 (PST) From: Parag Goswami To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Subject: [manet] need help on tools..... X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0074030930==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 --===============0074030930== Content-Type: multipart/alternative; boundary="0-1508718585-1100686018=:3372" --0-1508718585-1100686018=:3372 Content-Type: text/plain; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA07553 Content-Transfer-Encoding: quoted-printable Hi all, I am an undergraduate student of Computer science and engineering.I need = help on the various tools that can be used for the simulation purpose in = my project. Please explain me these tools NS-2 and OPNET. I have to choos= e one from these two tools for my simulation purpose.Please provide infor= mation about : 1. Which one is better? 2. How do they work both OPNET and NS-2 ? =20 Look further to recieve soon response. =20 Best Regards, Parag Goswami http://www.geocities.com/paragboom2k =09 --------------------------------- Do you Yahoo!? The all-new My Yahoo! =96 Get yours free! =20 --0-1508718585-1100686018=:3372 Content-Type: text/html; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA07553 Content-Transfer-Encoding: quoted-printable

Hi all,
I am an undergraduate student of Computer science and engineering.I = need help on the various tools that can be used for the simulation purpos= e in my project. Please explain me these tools NS-2 and OPNET. I have to = choose one from these two tools for my simulation purpose.Please provide = information about :
1. Which one is better?
2. How do they work both OPNET and NS-2 ?
 
Look further to recieve soon response.
 
Best Regards,
Parag Goswami

=09

Do you Yahoo!?
=20 The all-new My Yahoo! =96 Get yours f= ree!=20 =20 =20 =20 --0-1508718585-1100686018=:3372-- --===============0074030930== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0074030930==-- From manet-bounces@ietf.org Wed Nov 17 05:59:46 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12161 for ; Wed, 17 Nov 2004 05:59:46 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUNZp-0005n4-Qr for manet-web-archive@ietf.org; Wed, 17 Nov 2004 06:02:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUNTe-0004ED-KO; Wed, 17 Nov 2004 05:55:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUNPl-0003lp-HI for manet@megatron.ietf.org; Wed, 17 Nov 2004 05:51:53 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11436 for ; Wed, 17 Nov 2004 05:51:50 -0500 (EST) From: Hakim.Badis@lri.fr Received: from ext.lri.fr ([129.175.15.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUNS6-0005aS-CG for manet@ietf.org; Wed, 17 Nov 2004 05:54:22 -0500 Received: from localhost (localhost [127.0.0.1]) by ext.lri.fr (Postfix) with ESMTP id AFD3F19E79A; Wed, 17 Nov 2004 11:51:05 +0100 (CET) Received: from ext.lri.fr ([127.0.0.1]) by localhost (ext.lri.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16680-07; Wed, 17 Nov 2004 11:51:05 +0100 (CET) Received: from www.lri.fr (newww [129.175.15.10]) by ext.lri.fr (Postfix) with ESMTP id 8E26D19E791; Wed, 17 Nov 2004 11:51:05 +0100 (CET) Received: from afontenayssb-152-1-14-142.w82-121.abo.wanadoo.fr ([82.121.108.142]) (SquirrelMail authenticated user badis); by www.lri.fr with HTTP; Wed, 17 Nov 2004 11:51:05 +0100 (CET) Message-ID: <3488.82.121.108.142.1100688665.squirrel@www.lri.fr> In-Reply-To: <20041117100658.7055.qmail@web90107.mail.scd.yahoo.com> References: <20041117100658.7055.qmail@web90107.mail.scd.yahoo.com> Date: Wed, 17 Nov 2004 11:51:05 +0100 (CET) Subject: Re: [manet] need help on tools..... To: "Parag Goswami" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at lri.fr X-Spam-Score: 0.4 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA11436 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: quoted-printable Hi Parag, Simulation tools (OPNET, NS-2, GloMoSim, etc.) comparaison is not easy. I= n our team, we use OPNET 10.0 Modeler and we have obtained many good results. You can refere for example to this paper "OPNET Modeler and Ns-2= : Comparing the Accuracy of Network Simulator for Packet-Level Analysis using a Network Testbed". Hakim. > Hi all, > I am an undergraduate student of Computer science and engineering.I nee= d > help on the various tools that can be used for the simulation purpose i= n > my project. Please explain me these tools NS-2 and OPNET. I have to cho= ose > one from these two tools for my simulation purpose.Please provide > information about : > 1. Which one is better? > 2. How do they work both OPNET and NS-2 ? > > Look further to recieve soon response. > > Best Regards, > Parag Goswami > http://www.geocities.com/paragboom2k > > > --------------------------------- > Do you Yahoo!? > The all-new My Yahoo! =96 Get yours free! > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 17 12:38:29 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23195 for ; Wed, 17 Nov 2004 12:38:29 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUTna-0007Ij-8Z for manet-web-archive@ietf.org; Wed, 17 Nov 2004 12:41:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUTXz-0007VT-5l; Wed, 17 Nov 2004 12:24:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUTFo-0001Nz-RY for manet@megatron.ietf.org; Wed, 17 Nov 2004 12:06:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19873 for ; Wed, 17 Nov 2004 12:05:57 -0500 (EST) Received: from kurla.upf.edu ([193.145.39.26]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUTI6-0006OI-H6 for manet@ietf.org; Wed, 17 Nov 2004 12:08:32 -0500 Received: from kurla.upf.edu (localhost [127.0.0.1]) by kurla.upf.edu (8.12.10/8.12.10) with ESMTP id iAHH5IrJ026492 for ; Wed, 17 Nov 2004 18:05:18 +0100 Received: from [193.145.45.186] (efpc396.upf.es [193.145.45.186])by kurla.upf.edu (8.12.10/8.12.10) with ESMTP id iAHH5HiC026487for ; Wed, 17 Nov 2004 18:05:17 +0100 Message-ID: <419B84AE.9000909@upf.edu> Date: Wed, 17 Nov 2004 18:04:46 +0100 From: Manel Guerrero User-Agent: Mozilla Thunderbird 0.8 (X11/20041102) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-imss-version: 2.8 X-imss-result: Passed X-imss-approveListMatch: *@upf.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: 7bit Subject: [manet] New SAODV draft: draft-guerrero-manet-saodv-02.txt X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7bit Hi everybody :) The new SAODV draft is available at: http://www.ietf.org/internet-drafts/draft-guerrero-manet-saodv-02.txt At the end of the draft there is a section with what has changed from previous versions. Of course, feedback is more than welcome. Thanks to Moritz Killat and Varaporn Pangboonyanon for the corrections and improvements and suggestions to the previous draft. Regards, Manel _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 17 14:43:17 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04567 for ; Wed, 17 Nov 2004 14:43:17 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUVkV-0001WX-Bn for manet-web-archive@ietf.org; Wed, 17 Nov 2004 14:45:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUVXK-0007QL-Ek; Wed, 17 Nov 2004 14:32:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUVQZ-0005pu-9p for manet@megatron.ietf.org; Wed, 17 Nov 2004 14:25:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01944 for ; Wed, 17 Nov 2004 14:25:13 -0500 (EST) Received: from simmts5.bellnexxia.net ([206.47.199.163] helo=simmts5-srv.bellnexxia.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUVT1-00017b-GD for manet@ietf.org; Wed, 17 Nov 2004 14:27:48 -0500 Received: from [156.34.93.40] by simmts5-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20041117192438.CCVR1614.simmts5-srv.bellnexxia.net@[156.34.93.40]> for ; Wed, 17 Nov 2004 14:24:38 -0500 Message-Id: <6.0.3.0.0.20041117152116.02f0eeb0@imap.dal.ca> X-Sender: artimym@imap.dal.ca X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0 Date: Wed, 17 Nov 2004 15:24:31 -0400 To: manet@ietf.org From: "Maen M. Artimy" In-Reply-To: <200411171716.iAHHGwuI019667@KIL-MX-2.UCIS.Dal.Ca> References: <200411171716.iAHHGwuI019667@KIL-MX-2.UCIS.Dal.Ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.1 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Subject: [manet] Dynamic Range Assignment X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 >Hi, I would like to know if there any major work has been done in establishing network connectivity using dynamic/variable transmission range. Thanks. Maen Maen Artimy Dalhousie University http://is2.dal.ca/~artimym _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 17 15:16:21 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08000 for ; Wed, 17 Nov 2004 15:16:21 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUWGW-0002J3-QO for manet-web-archive@ietf.org; Wed, 17 Nov 2004 15:18:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUW9P-0007Fu-Vg; Wed, 17 Nov 2004 15:11:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUW2A-0001k4-0c for manet@megatron.ietf.org; Wed, 17 Nov 2004 15:04:06 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06215 for ; Wed, 17 Nov 2004 15:04:03 -0500 (EST) Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUW4c-00020F-S4 for manet@ietf.org; Wed, 17 Nov 2004 15:06:39 -0500 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.12.10+Sun/8.12.8) with SMTP id iAHK3Qsb018052; Wed, 17 Nov 2004 15:03:32 -0500 (EST) Received: from D313NV11.itd.nrl.navy.mil ([132.250.93.60]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.0.4.64) with SMTP id M2004111715033125385 ; Wed, 17 Nov 2004 15:03:31 -0500 Message-Id: <5.2.0.9.2.20041117151004.0347fc70@pop.itd.nrl.navy.mil> X-Sender: jdean@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 17 Nov 2004 15:14:46 -0500 To: "Kais Mnif" , manet@ietf.org From: Justin Dean Subject: Re: [manet] how to build a benchmark for experimentation for ad hoc network In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 If you are looking to go cheap you might want to check out our mobile network emulator. (MNE) it uses predetermined movement patterns, mac filtering, along with a back channel to emulate a movement scenario. The software is free at pf.itd.nrl.navy.mil MNE. We use laptop computers with a wired backchannel and a wireless card each. But you might even be able to use the linux linksys box, which would be cheaper in terms of hardware ~50 bucks a piece but limited in software because of resorces. Justin Dean At 08:37 PM 11/1/2004 +0000, Kais Mnif wrote: >Dear patriots > >In our educational laboratory, we like to build an ad hoc network for >experimentation >we just starting, we like to know if someone can help us to choose >hardware (product such as switchs routers wireless cards etc. ) and >software ! we anticipate to use Linux as an operating system. > >Any suggestion and help will be appreciated > > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 17 15:31:34 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09488 for ; Wed, 17 Nov 2004 15:31:34 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUWVD-0002cg-8f for manet-web-archive@ietf.org; Wed, 17 Nov 2004 15:34:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUWIj-0004bE-Jy; Wed, 17 Nov 2004 15:21:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUWDy-0000sV-CX for manet@megatron.ietf.org; Wed, 17 Nov 2004 15:16:18 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07987 for ; Wed, 17 Nov 2004 15:16:16 -0500 (EST) Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUWGS-0002IN-01 for manet@ietf.org; Wed, 17 Nov 2004 15:18:52 -0500 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.12.10+Sun/8.12.8) with SMTP id iAHKFesZ018654; Wed, 17 Nov 2004 15:15:45 -0500 (EST) Received: from D313NV11.itd.nrl.navy.mil ([132.250.93.60]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.0.4.64) with SMTP id M2004111715154425477 ; Wed, 17 Nov 2004 15:15:44 -0500 Message-Id: <5.2.0.9.2.20041117152205.034dbb58@pop.itd.nrl.navy.mil> X-Sender: jdean@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 17 Nov 2004 15:26:58 -0500 To: Ian Chakeres , "'manet'" From: Justin Dean Subject: Re: [manet] Path Accumulation in DyMO In-Reply-To: <462F6BE0-34A2-11D9-B99A-000A95C1BC0A@cs.ucsb.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 I don't know that I agree or if I disagree. I see tradeoffs in complexity no matter which method is used. With accumulation the problem of large packet headers, without storing state. Although I am leaning towards not having it in the base specification because it seems to me easier to optionally add accumulation than it would be to take it away. Justin Dean At 06:59 AM 11/12/2004 -0500, Ian Chakeres wrote: >At the MANET meeting I presented DyMO (Dynamic MANET On-demand Routing >Protocol). My slides from the presentation are available at >http://moment.cs.ucsb.edu/~idc/pub/chakeres_ietf61_presentation.pdf. > >There was a short discussion about using path accumulation in the base >specification. Most people expressed their feelings that path >accumulation is useful for additional route information dissemination. I >believe there was consensus to not include path accumulation in the core >spec though it should definitely be included as an optimization. >If you disagree, lets discuss it more on the list. > >Thanks. >Ian Chakeres > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 17 15:35:39 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09772 for ; Wed, 17 Nov 2004 15:35:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUWZC-0002iZ-Hw for manet-web-archive@ietf.org; Wed, 17 Nov 2004 15:38:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUWUC-0003Gu-D5; Wed, 17 Nov 2004 15:33:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUWIl-0004bz-OV for manet@megatron.ietf.org; Wed, 17 Nov 2004 15:21:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08621 for ; Wed, 17 Nov 2004 15:21:13 -0500 (EST) Received: from davinci.coe.neu.edu ([129.10.32.95]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUWLF-0002PV-68 for manet@ietf.org; Wed, 17 Nov 2004 15:23:49 -0500 Received: from Wright.coe.neu.edu (Wright.coe.neu.edu [129.10.32.88]) by DaVinci.coe.neu.edu (8.12.10/8.12.10) with SMTP id iAHKLDFw021798 for ; Wed, 17 Nov 2004 15:21:13 -0500 (EST) Received: from wright.coe.neu.edu ([129.10.32.84]) by Wright.coe.neu.edu (SMSSMTP 4.0.0.59) with SMTP id M2004111715211220307 for ; Wed, 17 Nov 2004 15:21:12 -0500 Received: from Euclid.coe.neu.edu (Euclid.coe.neu.edu [129.10.32.93]) by wright.coe.neu.edu (8.12.11/8.12.11) with ESMTP id iAHKLCjX010071 for ; Wed, 17 Nov 2004 15:21:12 -0500 (EST) Received: (from www@localhost) by Euclid.coe.neu.edu (8.12.10/8.12.10/Submit) id iAHKLCXF021411 for manet@ietf.org; Wed, 17 Nov 2004 15:21:12 -0500 (EST) X-Authentication-Warning: Euclid.coe.neu.edu: www set sender to nshah@coe.neu.edu using -f Received: from 129.10.64.189 ([129.10.64.189]) by www.coe.neu.edu (IMP) with HTTP for ; Wed, 17 Nov 2004 15:21:12 -0500 Message-ID: <1100722872.419bb2b8d4691@www.coe.neu.edu> Date: Wed, 17 Nov 2004 15:21:12 -0500 From: Nishit Shah 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.3 X-Originating-IP: 129.10.64.189 X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 8bit Subject: [manet] Simulating Ad Hoc Localization X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Content-Transfer-Encoding: 8bit Hi All I am developing a range-based localization technique for ad hoc wireless sensor networks. I want to validate it w.r.t. some performance metrics. However i am looking for some answers: 1. Is there a simulator that simulates the TOA, TDOA, AOA techniques taking into account the error involved therein? 2. Are there any tutorials that demonstrate how to simulate localization algorithms? Any help will be appreciated. Thank you. -- Nishit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 17 16:49:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22362 for ; Wed, 17 Nov 2004 16:49:57 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUXj8-0006VE-TE for manet-web-archive@ietf.org; Wed, 17 Nov 2004 16:52:35 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUXJb-0000qV-Sv; Wed, 17 Nov 2004 16:26:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUWnz-00054g-3F for manet@megatron.ietf.org; Wed, 17 Nov 2004 15:53:31 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11272 for ; Wed, 17 Nov 2004 15:53:28 -0500 (EST) Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUWqS-00035W-SI for manet@ietf.org; Wed, 17 Nov 2004 15:56:05 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id iAHKOJr19145; Wed, 17 Nov 2004 12:24:19 -0800 X-mProtect: <200411172024> Nokia Silicon Valley Messaging Protection Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com") by darkstar.iprg.nokia.com smtpdxB0svk; Wed, 17 Nov 2004 12:24:17 PST Message-ID: <419BBA92.1D9DBB63@iprg.nokia.com> Date: Wed, 17 Nov 2004 12:54:42 -0800 From: "Charles E.Perkins" Organization: Nokia Research Center X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Justin Dean Subject: Re: [manet] Path Accumulation in DyMO References: <5.2.0.9.2.20041117152205.034dbb58@pop.itd.nrl.navy.mil> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Content-Transfer-Encoding: 7bit Cc: Ian Chakeres , "'manet'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Content-Transfer-Encoding: 7bit Hello Justin, It seems to me that the path accumulation feature is potentially quite valuable, and that therefore we should encourage it to be part of any reactive routing specification. Whether or not it should be mandated is a tough question, because one can argue both sides of the debate by invoking the goal of simplicity. On the one hand, not having path accumulation in a node certainly makes the implementation of that node simpler. Unfortunately, it makes implementation in the other nodes more complicated, if those other nodes wish to provide and use the path accumulation information. If not all nodes comply, then adjacency cannot be inferred for the nodes in the accumulated list. In order to account for this, the data structure used for reporting the path accumulation data may have to be expanded somewhat. So, over time as more and more nodes implement the path accumulation feature, I think that the results of noncompliance by some nodes would be: - an increase in the overall complexity of the network - an increase in the amount of data per node reported, because of the expanded data structures required - a reduction in the effectiveness of the algorithm - consequently an increase in the number of route discoveries, - because of that an increase in congestion I don't have any good data right now about the magnitude of these likely effects. Furthermore, I would not let my intuitions about the need for path accumulation stand in the way of promulgating a standard for a reactive routing protocol. But, if I can get the data to quantify the abovementioned effects, then it would probably make sense for us to weigh the performance implications when we are engineering the protocol. Regards, Charlie P. Justin Dean wrote: > > I don't know that I agree or if I disagree. I see tradeoffs in complexity > no matter which method is used. With accumulation the problem of large > packet headers, without storing state. Although I am leaning towards not > having it in the base specification because it seems to me easier to > optionally add accumulation than it would be to take it away. > > Justin Dean > > At 06:59 AM 11/12/2004 -0500, Ian Chakeres wrote: > >At the MANET meeting I presented DyMO (Dynamic MANET On-demand Routing > >Protocol). My slides from the presentation are available at > >http://moment.cs.ucsb.edu/~idc/pub/chakeres_ietf61_presentation.pdf. > > > >There was a short discussion about using path accumulation in the base > >specification. Most people expressed their feelings that path > >accumulation is useful for additional route information dissemination. I > >believe there was consensus to not include path accumulation in the core > >spec though it should definitely be included as an optimization. > >If you disagree, lets discuss it more on the list. > > > >Thanks. > >Ian Chakeres > > > > > >_______________________________________________ > >manet mailing list > >manet@ietf.org > >https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 17 17:47:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27981 for ; Wed, 17 Nov 2004 17:47:50 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUYdA-0008Bw-HL for manet-web-archive@ietf.org; Wed, 17 Nov 2004 17:50:28 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUYN8-0001yW-71; Wed, 17 Nov 2004 17:33:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUYCg-0006oe-Vx for manet@megatron.ietf.org; Wed, 17 Nov 2004 17:23:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25698 for ; Wed, 17 Nov 2004 17:23:04 -0500 (EST) Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUYFA-0007ZS-OP for manet@ietf.org; Wed, 17 Nov 2004 17:25:42 -0500 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id iAHMN4Rh014952 for ; Wed, 17 Nov 2004 17:23:04 -0500 (EST) Received: from ECE.NEU.EDU ([129.10.60.216]) by calvin.ece.neu.edu (SAVSMTP 3.1.0.29) with SMTP id M2004111717230310592 for ; Wed, 17 Nov 2004 17:23:03 -0500 Received: from localhost (basagni@localhost) by ECE.NEU.EDU (8.12.8/8.12.5/Submit) with ESMTP id iAHMN4ER013472 for ; Wed, 17 Nov 2004 17:23:04 -0500 Date: Wed, 17 Nov 2004 17:23:04 -0500 (EST) From: Stefano Basagni To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.6 (/) X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede Subject: [manet] IEEE SECON 2005 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 We apologize if you receive multiple copies of this CfP ************************************************************* Preliminary Announcement and Call for Papers *** IEEE SECON 2005 *** Second Annual IEEE Communications Society Conference on Sensor and Ad Hoc Communications and Networks Santa Clara, California, USA September 26-29, 2005 Paper Submission Deadline: April 6, 2005 http://www.ieee-secon.org/2005 ************************************************************ Building on the success of last year's inaugural conference, this new IEEE Communications Society conference will provide a forum to exchange ideas, techniques, and applications, discuss best practices, raise awareness and share experiences among researchers, practitioners, standard developers and policy makers in the field of sensor and ad hoc networks and systems. The conference will be organized to provide for a degree of collegiality and continuity in the discussions of the various topics among participants from the industrial, governmental and academic sectors. Original technical papers that address the communications, networking, systems and algorithmic aspects of ad hoc and sensor networks, as well as those that describe practical deployment and implementation experiences, are solicited for presentation at the conference and publication in the conference proceedings. Papers presenting novel contributions in such disciplines as communications, networking protocols and architectures, algorithms, embedded systems, middleware and information management, and novel applications are solicited. PAPERS: Full papers describing original, previously unpublished research work, experimental efforts, practical experiences, and industrial and commercial developments in sensor and ad hoc communications and networks. Papers with a deep focus on a specific discipline or stimulated by the synergistic interaction of diverse disciplines are encouraged. Particular topics of interest include, but are not limited to: * New architectures, protocols and access control to support communication, localization, time synchronization, routing and data dissemination in heterogeneous, large-scale distributed, ad hoc networks and sensor networks * Novel algorithms and theories for management, supervisory control and monitoring of distributed ad hoc networks, and techniques for the interpretation and use of sensor data in decision-making processes * Modeling and performance evaluation of large-scale distributed and ad hoc sensor networks, practical implementations, and real-work experiences * Theories and models on fundamental information and communication aspects of wireless ad hoc and sensor networks * Mechanisms for authenticated, secure communication and data dissemination in sensor and ad hoc networks * Integration of sensors into engineered systems, including novel techniques for sensor renewable power sources, mechanisms for on-sensor self-calibration and self-testing and efficient schemes to maximize accuracy and minimize false alarms * Chip-based systems incorporating multiple sensors, computation, actuation, and wireless interfaces * Software platforms, middleware and tools for ad hoc and sensor network applications development, deployment and management TUTORIALS and PANELS: Proposals for tutorials and panels on current topics in the field of ad hoc and sensor networking and applications are solicited. Panels related to the commercial application and development of sensors and ad hoc networks are especially encouraged. DEMOS and EXPO: Demonstrations that showcases the practical implementations, industrial and commercial developments, and new applications for ad hoc and sensor networks are solicited. SUBMISSION INSTRUCTIONS: All paper submissions will be handled electronically through the EDAS system. Details regarding the paper format and the submission process will be posted at the conference web site. IMPORTANT DATES: April 6, 2005 Paper submission deadline May 1, 2005 Tutorial/Panel/Demo proposals deadline June 13, 2005 Notifications July 8, 2005 Camera-ready due date TPC Co-Chairs: Elizabeth Belding-Royer ebelding@cs.ucsb.edu Marwan Krunz krunz@ece.arizona.edu Thyaga Nandagopal thyaga@lucent.com General Chair: J.J. Garcia-Luna-Aceves jj@soe.ucsc.edu -- Stefano Basagni, Ph.D. Assistant Professor of Computer Engineering Dept. of Electrical and Computer Engineering 312 Dana Research Center Northeastern University 360 Huntington Ave. Boston, MA 02115 Tel. 617 373 3061, Fax 617 373 8970 E-mail: basagni@ece.neu.edu *** http://www.ece.neu.edu/faculty/basagni/ *** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 17 22:57:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23429 for ; Wed, 17 Nov 2004 22:57:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUdT0-0006NS-Mf for manet-web-archive@ietf.org; Wed, 17 Nov 2004 23:00:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUdLd-0005tM-Q2; Wed, 17 Nov 2004 22:52:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUdK1-0005gP-Lh for manet@megatron.ietf.org; Wed, 17 Nov 2004 22:51:01 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23084 for ; Wed, 17 Nov 2004 22:50:59 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.202]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUdMY-0006Gh-Ej for manet@ietf.org; Wed, 17 Nov 2004 22:53:39 -0500 Received: by rproxy.gmail.com with SMTP id a36so984808rnf for ; Wed, 17 Nov 2004 19:50:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Y2RSF4FlJ/tQxseQ60Eh8r2jOJD5oV5IMGXvCPItmcJykH9/bOGVmnUsXO+vhs2wuQuu5pVI65k4bdV92rZYVSSv1IwYfIzn2Iekdx+4jOh/e4UYT2bRDXBldAhIv4JjCvarbDIp+nAhcTupt5QYLi736V6WuZoTfEBuWqaS67s= Received: by 10.38.83.67 with SMTP id g67mr367638rnb; Wed, 17 Nov 2004 19:50:55 -0800 (PST) Received: by 10.38.15.80 with HTTP; Wed, 17 Nov 2004 19:50:55 -0800 (PST) Message-ID: <78e4c4dc0411171950761c181c@mail.gmail.com> Date: Wed, 17 Nov 2004 19:50:55 -0800 From: Pankaj Godbole To: Parag Goswami Subject: Re: [manet] need help on tools..... In-Reply-To: <20041117100658.7055.qmail@web90107.mail.scd.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable References: <20041117100658.7055.qmail@web90107.mail.scd.yahoo.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Pankaj Godbole List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Content-Transfer-Encoding: quoted-printable Hi Parag, If you haven't already done so, you could take a look at this paper which compares the performance of the three popular simulators: NS-2, Glomosim and OPNET in simulating a simple flooding algorithm. http://lsewww.epfl.ch/Documents/acrobat/CSA02b.pdf Regards, Pankaj Godbole. On Wed, 17 Nov 2004 02:06:58 -0800 (PST), Parag Goswami wrote: >=20 > Hi all,=20 > I am an undergraduate student of Computer science and engineering.I need > help on the various tools that can be used for the simulation purpose in = my > project. Please explain me these tools NS-2 and OPNET. I have to choose o= ne > from these two tools for my simulation purpose.Please provide information > about :=20 > 1. Which one is better?=20 > 2. How do they work both OPNET and NS-2 ?=20 > =20 > Look further to recieve soon response.=20 > =20 > Best Regards,=20 > Parag Goswami=20 > http://www.geocities.com/paragboom2k >=20 > ________________________________ > Do you Yahoo!? > The all-new My Yahoo! =E2=80=93 Get yours free!=20 >=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 manet-bounces@ietf.org Thu Nov 18 08:09:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22332 for ; Thu, 18 Nov 2004 08:09:59 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUm5c-0000qj-4x for manet-web-archive@ietf.org; Thu, 18 Nov 2004 08:12:44 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUlyO-0002f9-Ds; Thu, 18 Nov 2004 08:05:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUluF-0001Uu-Mp for manet@megatron.ietf.org; Thu, 18 Nov 2004 08:00:59 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21478 for ; Thu, 18 Nov 2004 08:00:58 -0500 (EST) Received: from mailout2.samsung.com ([203.254.224.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUlwr-0000aU-Mt for manet@ietf.org; Thu, 18 Nov 2004 08:03:42 -0500 Received: from custom-daemon.mailout2.samsung.com by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I7D00309LGPLO@mailout2.samsung.com> for manet@ietf.org; Thu, 18 Nov 2004 22:00:25 +0900 (KST) Received: from ep_mmp1 (mailout2.samsung.com [203.254.224.25]) by mailout2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I7D0014DLGKCY@mailout2.samsung.com> for manet@ietf.org; Thu, 18 Nov 2004 22:00:20 +0900 (KST) Received: from Shubhranshu ([75.2.91.24]) by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA id <0I7D00IZ6LGKOY@mmp1.samsung.com> for manet@ietf.org; Thu, 18 Nov 2004 22:00:20 +0900 (KST) Date: Thu, 18 Nov 2004 22:00:20 +0900 From: Shubhranshu To: manet@ietf.org Message-id: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Organization: Samsung Electronics MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook Express 6.00.2800.1409 Content-type: text/plain; charset=ks_c_5601-1987 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7BIT Subject: [manet] manet autoconf. X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: 7BIT Hi all, MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, there are other issues fundamental to ad hoc network operation and deployment such as address auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and need to standardize solutions for these auto-configuration related issues within IETF. This was then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be the best place to solve these issues. There was some sort of consensus to move forward with this work. Several independent publications and implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up a mailing list of those interested in these topics and willing to contribute. There should be consensus on problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, depending on the development on this mailing list. Regards, Shubhranshu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 08:19:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22968 for ; Thu, 18 Nov 2004 08:19:43 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUmEy-000122-LC for manet-web-archive@ietf.org; Thu, 18 Nov 2004 08:22:28 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmAQ-0005jR-U8; Thu, 18 Nov 2004 08:17:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUm1n-0003Vq-Ms for manet@megatron.ietf.org; Thu, 18 Nov 2004 08:08:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22222 for ; Thu, 18 Nov 2004 08:08:46 -0500 (EST) Received: from outbound.mailhop.org ([63.208.196.171] ident=mailnull) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUm4D-0000pG-9I for manet@ietf.org; Thu, 18 Nov 2004 08:11:30 -0500 Received: from [192.70.34.42] (helo=[192.168.0.192]) by outbound.mailhop.org with esmtpsa (SSLv3:RC4-MD5:128) (Exim 4.42) id 1CUm1X-000PMQ-A2; Thu, 18 Nov 2004 08:08:32 -0500 Mime-Version: 1.0 X-Mailer: SnapperMail 2.0.5.01 by Snapperfish, www.snappermail.com To: Ian Chakeres Subject: Re: [manet] Path Accumulation in DyMO Message-ID: <8497-SnapperMsgD302CB11BDC24FFA@192.168.0.192> In-Reply-To: <462F6BE0-34A2-11D9-B99A-000A95C1BC0A@cs.ucsb.edu> References: Message-ID: From: Thomas Heide Clausen Date: Thu, 18 Nov 2004 14:11 +0100 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mail-Handler: MailHop Outbound by DynDNS.org X-Originating-IP: 192.70.34.42 X-Report-Abuse-To: abuse@dyndns.org (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: voop X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: 7bit Ian, I am still of the general opinion that leaving an option unspecified is a bad thing, assuming that it's an option which (i) a plurality of deployments might use and (ii) where different approaches/implementations might impair interoperability. What's the general observations on (i) and (ii) regarding path-accumulation? --thomas ___ Sent with SnapperMail www.snappermail.com ...... Original Message ....... On Fri, 12 Nov 2004 06:59:15 -0500 Ian Chakeres wrote: >At the MANET meeting I presented DyMO (Dynamic MANET On-demand Routing >Protocol). My slides from the presentation are available at >http://moment.cs.ucsb.edu/~idc/pub/chakeres_ietf61_presentation.pdf. > >There was a short discussion about using path accumulation in the base >specification. Most people expressed their feelings that path >accumulation is useful for additional route information dissemination. >I believe there was consensus to not include path accumulation in the >core spec though it should definitely be included as an optimization. >If you disagree, lets discuss it more on the list. > >Thanks. >Ian Chakeres > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 08:32:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23914 for ; Thu, 18 Nov 2004 08:32:23 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUmRI-0001G1-KV for manet-web-archive@ietf.org; Thu, 18 Nov 2004 08:35:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmAg-0005s6-I2; Thu, 18 Nov 2004 08:17:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUm94-0005KK-0r for manet@megatron.ietf.org; Thu, 18 Nov 2004 08:16:18 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22760 for ; Thu, 18 Nov 2004 08:16:16 -0500 (EST) Received: from smtp4.na.baesystems.com ([63.164.202.13]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUmBg-0000xb-Q6 for manet@ietf.org; Thu, 18 Nov 2004 08:19:01 -0500 Received: from BLUMS0022.bluelnk.net (blums0022.na.baesystems.com [10.40.96.145]) by smtp4.na.baesystems.com (8.12.10/8.12.10) with ESMTP id iAIDG8M1025417 for ; Thu, 18 Nov 2004 08:16:08 -0500 (EST) Received: from blums0002.bluelnk.net (blums0002.na.baesystems.com [10.40.96.102]) by smtp1.na.baesystems.com (8.12.10/8.12.10) with ESMTP id iAIDG5Ie029339; Thu, 18 Nov 2004 08:16:07 -0500 (EST) Received: from BLUMS0005.bluelnk.net ([10.40.96.105]) by blums0002.bluelnk.net with Microsoft SMTPSVC(5.0.2195.5329); Thu, 18 Nov 2004 08:16:16 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] manet autoconf. Date: Thu, 18 Nov 2004 08:16:16 -0500 Message-ID: Thread-Topic: [manet] manet autoconf. Thread-Index: AcTNcCqDbVd8DJXqQvCBK4HCbUJzjwAAIi/w From: "Frye, Robert J (US SSA)" To: "Shubhranshu" , X-OriginalArrivalTime: 18 Nov 2004 13:16:16.0921 (UTC) FILETIME=[C9391890:01C4CD70] X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: quoted-printable Count me in. Rob Frye BAE SYSTEMS CNIR 11487 Sunset Hills Road Reston, VA 20190 (v)703-668-4520 (m)571-331-2846 (e)robert.frye@baesystems.com =20 -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Shubhranshu Sent: Thursday, November 18, 2004 8:00 AM To: manet@ietf.org Subject: [manet] manet autoconf. Hi all, MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However,=20 there are other issues fundamental to ad hoc network operation and deployment such as address=20 auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic=20 forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji=20 Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and need to standardize solutions for these auto-configuration related issues within IETF. This was=20 then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be the best place to solve these issues. There was some sort of consensus to move forward with this work. Several independent publications and=20 implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up=20 a mailing list of those interested in these topics and willing to contribute. There should be consensus on problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting,=20 depending on the development on this mailing list. Regards, Shubhranshu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 08:56:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25818 for ; Thu, 18 Nov 2004 08:56:43 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUmop-0001nr-Ev for manet-web-archive@ietf.org; Thu, 18 Nov 2004 08:59:28 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmZQ-0003PW-Or; Thu, 18 Nov 2004 08:43:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmXG-0002fN-Oz for manet@megatron.ietf.org; Thu, 18 Nov 2004 08:41:19 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24576 for ; Thu, 18 Nov 2004 08:41:16 -0500 (EST) Received: from web20926.mail.yahoo.com ([216.136.224.143]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CUmZq-0001RY-N8 for manet@ietf.org; Thu, 18 Nov 2004 08:44:02 -0500 Received: (qmail 24299 invoked by uid 60001); 18 Nov 2004 13:41:13 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=KB44E7oaaTXtz2m5wP6mrvoSrDdqLByUxDVq5p1xPuRlykCrDhiEEVkrm0pJZ8noDpWFC8K/B67wqCgM58tr1zqZA4xL+K794XxXQqiVn0cmUMNUXAEOEUMZJ71zN5YhqEtf2MUWCX0XhTvDfY76m9llJX0fi5fZYQk12LbGkHE= ; Message-ID: <20041118134113.24297.qmail@web20926.mail.yahoo.com> Received: from [203.208.193.230] by web20926.mail.yahoo.com via HTTP; Thu, 18 Nov 2004 05:41:13 PST Date: Thu, 18 Nov 2004 05:41:13 -0800 (PST) From: Praveen Choudary To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.9 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Subject: [manet] Research X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Hi, Kindly let me know if anybody in this group is doing research in routing and MAC rpotocols of Sensor Networks. I am mainly interested in QOS issues in Sensor Networks. I have some ideas and if anybody is working in this area, I request them to help me so that I can make a meaningful contribution to the research in this direction. Looking forward for your reply, Praveen. __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 09:13:15 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26741 for ; Thu, 18 Nov 2004 09:13:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUn4p-00026Y-Ov for manet-web-archive@ietf.org; Thu, 18 Nov 2004 09:16:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmly-0006W7-4i; Thu, 18 Nov 2004 08:56:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmYv-0003Hj-V3 for manet@megatron.ietf.org; Thu, 18 Nov 2004 08:43:01 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24748 for ; Thu, 18 Nov 2004 08:43:00 -0500 (EST) Received: from web20926.mail.yahoo.com ([216.136.224.143]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CUmbX-0001Uf-LW for manet@ietf.org; Thu, 18 Nov 2004 08:45:45 -0500 Received: (qmail 24522 invoked by uid 60001); 18 Nov 2004 13:42:58 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=nOah7dHRnR+359ZXN+lGsjMgQwE4HFBAqpRJKYUNr9+BS7FIz/8au5EMiH4y7bUtp/2ykZ0HyMc+i5XoPmgaUUXfU6RADr4FZNOMnBquzCCYOolmW9npaMcPNcC8rqEWhz7hfiQ9Wgt+NFlG1acRtCHrYeMaFyxNOaQQyyH/epM= ; Message-ID: <20041118134258.24520.qmail@web20926.mail.yahoo.com> Received: from [203.208.193.230] by web20926.mail.yahoo.com via HTTP; Thu, 18 Nov 2004 05:42:58 PST Date: Thu, 18 Nov 2004 05:42:58 -0800 (PST) From: Praveen Choudary To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.9 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [manet] Research X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Hi, Kindly let me know if anybody in this group is doing research in routing and MAC rpotocols of Wireless Sensor Networks. I am mainly interested in QOS issues in Sensor Networks. I have some potential ideas and if anybody is working in this area, I request them to help me so that I can make a meaningful contribution to the research in this direction and demonstrate my research capability. Looking forward for your reply, Praveen. __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 09:19:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27341 for ; Thu, 18 Nov 2004 09:19:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUnAw-0002HD-6k for manet-web-archive@ietf.org; Thu, 18 Nov 2004 09:22:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUn3i-0002rO-8q; Thu, 18 Nov 2004 09:14:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmml-0006tW-NN for manet@megatron.ietf.org; Thu, 18 Nov 2004 08:57:20 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25887 for ; Thu, 18 Nov 2004 08:57:17 -0500 (EST) Received: from nez-perce.inria.fr ([192.93.2.78]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUmpO-0001o7-He for manet@ietf.org; Thu, 18 Nov 2004 09:00:03 -0500 Received: from inria.fr (darguina.inria.fr [128.93.17.1]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id iAIDulps017433; Thu, 18 Nov 2004 14:56:47 +0100 Message-ID: <419CA731.7050405@inria.fr> Date: Thu, 18 Nov 2004 14:44:17 +0100 From: saadi boudjit 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: Shubhranshu Subject: Re: [manet] manet autoconf. References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Miltered: at nez-perce with ID 419CAA1F.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit Hi Shubhranshu, I think that this mailing list is a good idea and I would like to be part of it. Saadi. HIPERCOM Project INRIA - France >Hi all, > >MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, >there are other issues fundamental to ad hoc network operation and deployment such as address >auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic >forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji >Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and >need to standardize solutions for these auto-configuration related issues within IETF. This was >then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be >the best place to solve these issues. > >There was some sort of consensus to move forward with this work. Several independent publications and >implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up >a mailing list of those interested in these topics and willing to contribute. There should be consensus on >problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would >like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, >depending on the development on this mailing list. > >Regards, >Shubhranshu > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 09:26:41 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27945 for ; Thu, 18 Nov 2004 09:26:41 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUnHq-0002Sf-1C for manet-web-archive@ietf.org; Thu, 18 Nov 2004 09:29:27 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUn7w-00050P-Gp; Thu, 18 Nov 2004 09:19:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUmwB-0000Qz-IH for manet@megatron.ietf.org; Thu, 18 Nov 2004 09:07:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26517 for ; Thu, 18 Nov 2004 09:07:01 -0500 (EST) Received: from clarinet.u-strasbg.fr ([130.79.90.157]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CUmyo-00021G-Hp for manet@ietf.org; Thu, 18 Nov 2004 09:09:47 -0500 Received: (qmail 17137 invoked for bounce); 18 Nov 2004 14:07:08 -0000 Received: from unknown (HELO unibas.ch) (jelger@unknown) by unknown with RC4-MD5 encrypted SMTP; 18 Nov 2004 14:07:08 -0000 Message-ID: <419CABCC.5080406@unibas.ch> Date: Thu, 18 Nov 2004 15:03:56 +0100 From: Christophe Jelger Organization: University of Basel User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031030 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Shubhranshu Subject: Re: [manet] manet autoconf. References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Content-Transfer-Encoding: 7bit Hi Shubhranshu, Please add me to the list. Regards, Christophe Dr. Christophe Jelger Computer Networks Group University of Basel Switzerland Shubhranshu wrote: >Hi all, > >MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, >there are other issues fundamental to ad hoc network operation and deployment such as address >auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic >forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji >Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and >need to standardize solutions for these auto-configuration related issues within IETF. This was >then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be >the best place to solve these issues. > >There was some sort of consensus to move forward with this work. Several independent publications and >implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up >a mailing list of those interested in these topics and willing to contribute. There should be consensus on >problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would >like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, >depending on the development on this mailing list. > >Regards, >Shubhranshu > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 09:41:15 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29182 for ; Thu, 18 Nov 2004 09:41:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUnVw-0002nn-RU for manet-web-archive@ietf.org; Thu, 18 Nov 2004 09:44:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUnOQ-0001SI-E6; Thu, 18 Nov 2004 09:36:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUnJd-00006B-H0 for manet@megatron.ietf.org; Thu, 18 Nov 2004 09:31:17 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28314 for ; Thu, 18 Nov 2004 09:31:15 -0500 (EST) Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUnMD-0002Yp-Go for manet@ietf.org; Thu, 18 Nov 2004 09:34:01 -0500 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.12.10+Sun/8.12.8) with SMTP id iAIEUcsX018049; Thu, 18 Nov 2004 09:30:38 -0500 (EST) Received: from D313NV11.itd.nrl.navy.mil ([132.250.93.60]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.0.4.64) with SMTP id M2004111809303630047 ; Thu, 18 Nov 2004 09:30:36 -0500 Message-Id: <5.2.0.9.2.20041118091625.034d4928@pop.itd.nrl.navy.mil> X-Sender: jdean@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Thu, 18 Nov 2004 09:41:52 -0500 To: "Charles E.Perkins" From: Justin Dean Subject: Re: [manet] Path Accumulation in DyMO In-Reply-To: <419BBA92.1D9DBB63@iprg.nokia.com> References: <5.2.0.9.2.20041117152205.034dbb58@pop.itd.nrl.navy.mil> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Cc: Ian Chakeres , "'manet'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813 I tend to agree with your intuition about the complexity that arises when some nodes implement path accumulation and others don't. And I guess my general feeling of things is that IF the option to not have path accumulation is a desired goal, for whatever reason, then it would seem to be easier to add a form of path accumulation on top of a network which does not do path accumulation than it would be to take it away from a network. On the other hand having the extra link state information disseminated throughout the network on route requests can lead, down the line, to some nice proactive options. I also wanted to elaborate one something you said. "If not all nodes comply, then adjacency cannot be inferred for the nodes in the accumulated list." Correct but virtual adjacency can be inferred and with a metric inclusive path accumulation method a "longer" path can be added to the packet when it re-enters the network doing path accumulation. I am still on the fence with this issue and either way is doable depending on how the spec is written. Justin Dean At 12:54 PM 11/17/2004 -0800, Charles E.Perkins wrote: >Hello Justin, > >It seems to me that the path accumulation feature is potentially >quite valuable, and that therefore we should encourage it to be >part of any reactive routing specification. Whether or not it >should be mandated is a tough question, because one can argue >both sides of the debate by invoking the goal of simplicity. > >On the one hand, not having path accumulation in a node certainly >makes the implementation of that node simpler. Unfortunately, it >makes implementation in the other nodes more complicated, if >those other nodes wish to provide and use the path accumulation >information. If not all nodes comply, then adjacency cannot be >inferred for the nodes in the accumulated list. In order to >account for this, the data structure used for reporting the path >accumulation data may have to be expanded somewhat. > >So, over time as more and more nodes implement the path >accumulation feature, I think that the results of noncompliance >by some nodes would be: >- an increase in the overall complexity of the network >- an increase in the amount of data per node reported, because > of the expanded data structures required >- a reduction in the effectiveness of the algorithm >- consequently an increase in the number of route discoveries, >- because of that an increase in congestion > >I don't have any good data right now about the magnitude >of these likely effects. Furthermore, I would not let my >intuitions about the need for path accumulation stand in the >way of promulgating a standard for a reactive routing protocol. >But, if I can get the data to quantify the abovementioned >effects, then it would probably make sense for us to weigh >the performance implications when we are engineering the >protocol. > >Regards, >Charlie P. > > > > >Justin Dean wrote: > > > > I don't know that I agree or if I disagree. I see tradeoffs in complexity > > no matter which method is used. With accumulation the problem of large > > packet headers, without storing state. Although I am leaning towards not > > having it in the base specification because it seems to me easier to > > optionally add accumulation than it would be to take it away. > > > > Justin Dean > > > > At 06:59 AM 11/12/2004 -0500, Ian Chakeres wrote: > > >At the MANET meeting I presented DyMO (Dynamic MANET On-demand Routing > > >Protocol). My slides from the presentation are available at > > >http://moment.cs.ucsb.edu/~idc/pub/chakeres_ietf61_presentation.pdf. > > > > > >There was a short discussion about using path accumulation in the base > > >specification. Most people expressed their feelings that path > > >accumulation is useful for additional route information dissemination. I > > >believe there was consensus to not include path accumulation in the core > > >spec though it should definitely be included as an optimization. > > >If you disagree, lets discuss it more on the list. > > > > > >Thanks. > > >Ian Chakeres > > > > > > > > >_______________________________________________ > > >manet mailing list > > >manet@ietf.org > > >https://www1.ietf.org/mailman/listinfo/manet > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 10:03:05 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00536 for ; Thu, 18 Nov 2004 10:03:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUnr5-0003Fe-P0 for manet-web-archive@ietf.org; Thu, 18 Nov 2004 10:05:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUnib-0006O0-76; Thu, 18 Nov 2004 09:57:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUnff-0005JN-LP for manet@megatron.ietf.org; Thu, 18 Nov 2004 09:54:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29922 for ; Thu, 18 Nov 2004 09:54:01 -0500 (EST) Received: from kurla.upf.edu ([193.145.39.26]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUni9-00032m-6B for manet@ietf.org; Thu, 18 Nov 2004 09:56:47 -0500 Received: from kurla.upf.edu (localhost [127.0.0.1]) by kurla.upf.edu (8.12.10/8.12.10) with ESMTP id iAIErLRi023287 for ; Thu, 18 Nov 2004 15:53:21 +0100 Received: from [193.145.45.186] (efpc396.upf.es [193.145.45.186])by kurla.upf.edu (8.12.10/8.12.10) with ESMTP id iAIErKe2023281; Thu, 18 Nov 2004 15:53:20 +0100 Message-ID: <419CB75F.6040503@upf.edu> Date: Thu, 18 Nov 2004 15:53:19 +0100 From: Manel Guerrero User-Agent: Mozilla Thunderbird 0.8 (X11/20041102) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Shubhranshu Subject: Re: [manet] manet autoconf. References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit X-imss-version: 2.8 X-imss-result: Passed X-imss-approveListMatch: *@upf.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 7bit Hi :) I'm interested on these topics, so I would also like to be in that mailing list. BTW, in the saodv draft there is a section (14.4. SAODV Key Management) where there is an address auto-configuration proposal that links the public key of a node with its IP address (something very important to achieve security). Regards, Manel Shubhranshu wrote: > Hi all, > > MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, > there are other issues fundamental to ad hoc network operation and deployment such as address > auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic > forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji > Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and > need to standardize solutions for these auto-configuration related issues within IETF. This was > then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be > the best place to solve these issues. > > There was some sort of consensus to move forward with this work. Several independent publications and > implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up > a mailing list of those interested in these topics and willing to contribute. There should be consensus on > problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would > like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, > depending on the development on this mailing list. > > Regards, > Shubhranshu > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 11:25:41 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08379 for ; Thu, 18 Nov 2004 11:25:41 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUp91-00058D-Kz for manet-web-archive@ietf.org; Thu, 18 Nov 2004 11:28:28 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUow5-0007Be-UW; Thu, 18 Nov 2004 11:15:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUorj-0005jP-2S for manet@megatron.ietf.org; Thu, 18 Nov 2004 11:10:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06776 for ; Thu, 18 Nov 2004 11:10:32 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.193]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUouN-0004i4-5m for manet@ietf.org; Thu, 18 Nov 2004 11:13:19 -0500 Received: by rproxy.gmail.com with SMTP id a36so1035139rnf for ; Thu, 18 Nov 2004 08:10:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=iXFAL60Oyc9rR+ao0SWwVRJeaqcnRFQ7XC3APnYcVaE5fmvCSgrGrZBYHDfgO+2aZ6P4EqciSSYRfFcz+GkZ2S4hR/YWNm8JzmsGjzXZDniMI0icZxONkXZFbpuQSaOQ580j9JoO562x3pNE+5tJK30ux/nACUTxjS4hTtRYikQ= Received: by 10.38.82.31 with SMTP id f31mr38403rnb; Thu, 18 Nov 2004 08:10:26 -0800 (PST) Received: by 10.38.66.42 with HTTP; Thu, 18 Nov 2004 08:10:26 -0800 (PST) Message-ID: Date: Thu, 18 Nov 2004 11:10:26 -0500 From: Marshall Eubanks To: Shubhranshu Subject: Re: [manet] manet autoconf. In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marshall Eubanks List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: 7bit Hello; Please add me to the list. Can you provide me with I-D's or RFC numbers for the "simplified multicast forwarding protocols" ? Regards Marshall Eubanks On Thu, 18 Nov 2004 22:00:20 +0900, Shubhranshu wrote: > Hi all, > > MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, > there are other issues fundamental to ad hoc network operation and deployment such as address > auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic > forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji > Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and > need to standardize solutions for these auto-configuration related issues within IETF. This was > then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be > the best place to solve these issues. > > There was some sort of consensus to move forward with this work. Several independent publications and > implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up > a mailing list of those interested in these topics and willing to contribute. There should be consensus on > problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would > like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, > depending on the development on this mailing list. > > Regards, > Shubhranshu > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 12:21:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13517 for ; Thu, 18 Nov 2004 12:21:23 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUq0x-0006Vp-Lf for manet-web-archive@ietf.org; Thu, 18 Nov 2004 12:24:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUpiI-0004N6-3B; Thu, 18 Nov 2004 12:04:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUpVE-0000q2-8y for manet@megatron.ietf.org; Thu, 18 Nov 2004 11:51:24 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10888 for ; Thu, 18 Nov 2004 11:51:21 -0500 (EST) Received: from mail.cs.umn.edu ([128.101.35.202] ident=postfix) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUpXs-0005lc-Sh for manet@ietf.org; Thu, 18 Nov 2004 11:54:09 -0500 Received: from localhost (localhost [127.0.0.1]) by augustus.cs.umn.edu (Postfix) with ESMTP id A99AF5C390; Thu, 18 Nov 2004 10:51:22 -0600 (CST) Received: from mail.cs.umn.edu ([127.0.0.1]) by localhost (augustus [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 24330-01-2; Thu, 18 Nov 2004 10:51:21 -0600 (CST) Received: from paulnb (fw-dtc.cs.umn.edu [128.101.189.210]) by mail.cs.umn.edu (Postfix) with SMTP id 4054E5C37F; Thu, 18 Nov 2004 10:51:21 -0600 (CST) Message-ID: <000c01c4cd86$ae974f00$c88310ac@paulnb> From: "Jaehoon Jeong" To: "Shubhranshu" , References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Subject: Re: [manet] manet autoconf. Date: Thu, 18 Nov 2004 10:53:00 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at cs.umn.edu X-Spam-Score: 1.1 (+) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0517007964==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 --===============0517007964== Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 SGkgU2h1YmhyYW5zaHUsDQoNClBsZWFzZSBjb3VudCBpbiBtZSwgdG9vLg0KSSBob3BlIHdlIGNh biBjb250cmlidXRlIHRvIHRoZSBkZXZlbG9wbWVudCBvZiBNQU5FVCBhdXRvY29uZiBtZWNoYW5p c20uDQoNClRoYW5rcyBmb3IgeW91ciB3b3JrLg0KDQpSZWdhcmRzLA0KUGF1bA0KDQo9PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT0NCkphZWhvb24gUGF1bCBKZW9uZywNClBoLkQuIFN0dWRlbnQsDQpEZXBhcnRtZW50 IG9mIENvbXB1dGVyIFNjaWVuY2UNClVuaXZlcnNpdHkgb2YgTWlubmVzb3RhIGF0IFR3aW4gQ2l0 aWVzDQpFbWFpbDogamplb25nQGNzLnVtbi5lZHUNCkhvbWVwYWdlOiBodHRwOi8vd3d3LmNzLnVt bi5lZHUvfmpqZW9uZy8NClBob25lOiArMS02MTItNjI0LTYyMDgoT2ZmaWNlKSwgNjUxLTU4Ny03 Nzc0KENlbGwpDQoNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJTaHVi aHJhbnNodSIgPHNodWJocmFuc2h1QHNhbXN1bmcuY29tPg0KVG86IDxtYW5ldEBpZXRmLm9yZz4N ClNlbnQ6IFRodXJzZGF5LCBOb3ZlbWJlciAxOCwgMjAwNCA4OjAwIEFNDQpTdWJqZWN0OiBbbWFu ZXRdIG1hbmV0IGF1dG9jb25mLg0KDQoNCj4gSGkgYWxsLA0KPiANCj4gTUFORVQgV0cgaXMgZGV2 ZWxvcGluZyBwcm9hY3RpdmUsIHJlYWN0aXZlIGFuZCBzaW1wbGlmaWVkIG11bHRpY2FzdCBmb3J3 YXJkaW5nIHByb3RvY29scy4gSG93ZXZlciwgDQo+IHRoZXJlIGFyZSBvdGhlciBpc3N1ZXMgZnVu ZGFtZW50YWwgdG8gYWQgaG9jIG5ldHdvcmsgb3BlcmF0aW9uIGFuZCBkZXBsb3ltZW50IHN1Y2gg YXMgYWRkcmVzcyANCj4gYXV0by1jb25maWd1cmF0aW9uLCBEQUQsIGdhdGV3YXkgZGlzY292ZXJ5 IGFuZCBzZWxlY3Rpb24gZm9yIGdsb2JhbCBwcmVmaXggYWxsb2NhdGlvbiBhbmQgdHJhZmZpYyAN Cj4gZm9yd2FyZGluZywgZXRjLiBEdXJpbmcgNjFzdCBJRVRGIG1lZXRpbmcsIFRob21hcyBDbGF1 c2VuLCBSdWZmaW5vIFNpbW9uLCBDaGFybGVzIFBlcmtpbnMsIFJ5dWppIA0KPiBXYWtpa2F3YSwg TGkgTGksIEVtbWFudWVsIEJhY2NlbGxpLCBteXNlbGYgYW5kIGZldyBvdGhlcnMgZGlzY3Vzc2Vk IGFib3V0IHRoZSBpbXBvcnRhbmNlIGFuZA0KPiBuZWVkIHRvIHN0YW5kYXJkaXplIHNvbHV0aW9u cyBmb3IgdGhlc2UgYXV0by1jb25maWd1cmF0aW9uIHJlbGF0ZWQgaXNzdWVzIHdpdGhpbiBJRVRG LiBUaGlzIHdhcyANCj4gdGhlbiBwcmVzZW50ZWQgYnkgU2ltb24gaW4gdGhlIE1BTkVUIFdHIG1l ZXRpbmcuIEl0IGlzIHVuZGVyc3Rvb2QgdGhhdCBNQU5FVCBXRyBtYXkgbm90IGJlDQo+IHRoZSBi ZXN0IHBsYWNlIHRvIHNvbHZlIHRoZXNlIGlzc3Vlcy4NCj4gDQo+IFRoZXJlIHdhcyBzb21lIHNv cnQgb2YgY29uc2Vuc3VzIHRvIG1vdmUgZm9yd2FyZCB3aXRoIHRoaXMgd29yay4gU2V2ZXJhbCBp bmRlcGVuZGVudCBwdWJsaWNhdGlvbnMgYW5kIA0KPiBpbXBsZW1lbnRhdGlvbnMgYXJlIGF2YWls YWJsZS4gQXMgc3VnZ2VzdGVkIGJ5IEpvZSBNYWNrZXIsIEFsZXggWmluaW4gYW5kIG90aGVycywg d2UgYXJlIGdvaW5nIHRvIHNldCB1cCANCj4gYSBtYWlsaW5nIGxpc3Qgb2YgdGhvc2UgaW50ZXJl c3RlZCBpbiB0aGVzZSB0b3BpY3MgYW5kIHdpbGxpbmcgdG8gY29udHJpYnV0ZS4gVGhlcmUgc2hv dWxkIGJlIGNvbnNlbnN1cyBvbg0KPiBwcm9ibGVtIHN0YXRlbWVudCwgcG9zc2libGUgYXBwcm9h Y2gsIGV4aXN0aW5nIHNvbHV0aW9ucywgbWlsZXN0b25lcywgZXRjLiBTbywgbGV0IG1lIGtub3cg aWYgeW91IHdvdWxkDQo+IGxpa2UgdG8gYmUgcGFydCBvZiB0aGUgbWFpbGluZyBsaXN0LiBXZSBh cmUgcGxhbm5pbmcgdG8gZ28gZm9yIEJPRi9iYXItQk9GIGF0IHRoZSBuZXh0IElFVEYgbWVldGlu ZywgDQo+IGRlcGVuZGluZyBvbiB0aGUgZGV2ZWxvcG1lbnQgb24gdGhpcyBtYWlsaW5nIGxpc3Qu DQo+IA0KPiBSZWdhcmRzLA0KPiBTaHViaHJhbnNodQ0KPiANCj4gDQo+IF9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IG1hbmV0IG1haWxpbmcgbGlzdA0K PiBtYW5ldEBpZXRmLm9yZw0KPiBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m by9tYW5ldA0KPiANCj4g --===============0517007964== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0517007964==-- From manet-bounces@ietf.org Thu Nov 18 12:37:12 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14805 for ; Thu, 18 Nov 2004 12:37:12 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUqGG-0006u9-II for manet-web-archive@ietf.org; Thu, 18 Nov 2004 12:40:00 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUq28-00046Q-TI; Thu, 18 Nov 2004 12:25:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUpoh-0006Io-VE for manet@megatron.ietf.org; Thu, 18 Nov 2004 12:11:32 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12549 for ; Thu, 18 Nov 2004 12:11:29 -0500 (EST) Received: from che.ojctech.com ([209.254.158.42]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUprM-0006FM-I7 for manet@ietf.org; Thu, 18 Nov 2004 12:14:17 -0500 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id iAIHB0u6024777 for ; Thu, 18 Nov 2004 11:11:00 -0600 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id iAIHAxie024775 for manet@ietf.org; Thu, 18 Nov 2004 11:10:59 -0600 Date: Thu, 18 Nov 2004 11:10:59 -0600 From: David Young To: manet@ietf.org Subject: Re: [manet] manet autoconf. Message-ID: <20041118171059.GK17288@che.ojctech.com> Mail-Followup-To: manet@ietf.org References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 On Thu, Nov 18, 2004 at 10:00:20PM +0900, Shubhranshu wrote: > There was some sort of consensus to move forward with this work. Several > independent publications and implementations are available. As > suggested by Joe Macker, Alex Zinin and others, we are going to set > up a mailing list of those interested in these topics and willing to > contribute. There should be consensus on problem statement, possible > approach, existing solutions, milestones, etc. So, let me know if you > would like to be part of the mailing list. We are planning to go for > BOF/bar-BOF at the next IETF meeting, depending on the development on > this mailing list. I will participate. Dave -- David Young OJC Technologies dyoung@ojctech.com Urbana, IL * (217) 278-3933 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 12:40:45 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15135 for ; Thu, 18 Nov 2004 12:40:45 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUqJh-0006zC-ER for manet-web-archive@ietf.org; Thu, 18 Nov 2004 12:43:33 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUq2E-00049p-SL; Thu, 18 Nov 2004 12:25:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUptO-0000OP-VC for manet@megatron.ietf.org; Thu, 18 Nov 2004 12:16:23 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13074 for ; Thu, 18 Nov 2004 12:16:20 -0500 (EST) Received: from animal.inescn.pt ([192.35.246.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUpvu-0006ND-Ll for manet@ietf.org; Thu, 18 Nov 2004 12:19:09 -0500 Received: from localhost (localhost [127.0.0.1]) by animal.inescn.pt (8.12.10/8.12.11/19) with ESMTP id iAIHFxUI021801; Thu, 18 Nov 2004 17:15:59 GMT Received: from bart.inescn.pt (root@bart.inescn.pt [192.35.246.9]) by animal.inescn.pt (8.12.10/8.12.10/7) with ESMTP id iAIHFo9s021789; Thu, 18 Nov 2004 17:15:50 GMT Received: from osteolito.inescn.pt (osteolito.inescn.pt [194.117.24.81]) by bart.inescn.pt (8.12.5/INESCP-V2.12) with ESMTP id iAIHFlxx012248; Thu, 18 Nov 2004 17:15:48 GMT To: "Marshall Eubanks" , Shubhranshu Subject: Re: [manet] manet autoconf. References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Message-ID: Date: Thu, 18 Nov 2004 17:16:39 -0000 From: "Rui Campos" Organization: INESC Porto Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Opera M2/7.54 (Win32, build 3865) X-Virus-Scanned: by amavisd-new at inescporto.pt X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Content-Transfer-Encoding: 8bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Content-Transfer-Encoding: 8bit Hi all, I am interested in those topics as well. Please, add me to the list! Thanks! BR, Rui Campos On Thu, 18 Nov 2004 11:10:26 -0500, Marshall Eubanks wrote: > Hello; > > Please add me to the list. > > Can you provide me with I-D's or RFC numbers for the "simplified > multicast forwarding protocols" ? > > Regards > Marshall Eubanks > > > On Thu, 18 Nov 2004 22:00:20 +0900, Shubhranshu > wrote: >> Hi all, >> >> MANET WG is developing proactive, reactive and simplified multicast >> forwarding protocols. However, >> there are other issues fundamental to ad hoc network operation and >> deployment such as address >> auto-configuration, DAD, gateway discovery and selection for global >> prefix allocation and traffic >> forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino >> Simon, Charles Perkins, Ryuji >> Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed >> about the importance and >> need to standardize solutions for these auto-configuration related >> issues within IETF. This was >> then presented by Simon in the MANET WG meeting. It is understood that >> MANET WG may not be >> the best place to solve these issues. >> >> There was some sort of consensus to move forward with this work. >> Several independent publications and >> implementations are available. As suggested by Joe Macker, Alex Zinin >> and others, we are going to set up >> a mailing list of those interested in these topics and willing to >> contribute. There should be consensus on >> problem statement, possible approach, existing solutions, milestones, >> etc. So, let me know if you would >> like to be part of the mailing list. We are planning to go for >> BOF/bar-BOF at the next IETF meeting, >> depending on the development on this mailing list. >> >> Regards, >> Shubhranshu >> >> _______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www1.ietf.org/mailman/listinfo/manet >> > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet -- Using Opera's revolutionary e-mail client: http://www.opera.com/m2/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 13:12:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17986 for ; Thu, 18 Nov 2004 13:12:08 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUqo5-0007tG-FD for manet-web-archive@ietf.org; Thu, 18 Nov 2004 13:14:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUqat-00066h-Dm; Thu, 18 Nov 2004 13:01:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUqQC-0003Pi-Cs for manet@megatron.ietf.org; Thu, 18 Nov 2004 12:50:16 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16132 for ; Thu, 18 Nov 2004 12:50:12 -0500 (EST) Received: from animal.inescn.pt ([192.35.246.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUqSp-0007Ij-DA for manet@ietf.org; Thu, 18 Nov 2004 12:53:01 -0500 Received: from localhost (localhost [127.0.0.1]) by animal.inescn.pt (8.12.10/8.12.11/19) with ESMTP id iAIHo5UI025526; Thu, 18 Nov 2004 17:50:05 GMT Received: from yang.inescn.pt (yang.inescn.pt [194.117.24.169]) by animal.inescn.pt (8.12.10/8.12.10/7) with ESMTP id iAIHnv9s025497; Thu, 18 Nov 2004 17:49:57 GMT Received: from nicles (nicles.inescn.pt [194.117.24.79]) by yang.inescn.pt (Postfix) with ESMTP id 649BC6FEA1; Thu, 18 Nov 2004 17:49:57 +0000 (WET) From: =?iso-8859-1?Q?T=E2nia_Pinto_Cal=E7ada?= To: "'Shubhranshu'" , Subject: RE: [manet] manet autoconf. Date: Thu, 18 Nov 2004 17:49:57 -0000 Organization: INESC Porto Message-ID: <008201c4cd97$04c52040$451975c2@inescn.pt> 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, Build 10.0.2627 In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Virus-Scanned: by amavisd-new at inescporto.pt X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tcalcada@inescporto.pt List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Content-Transfer-Encoding: 7bit Hello, I am working on this subject, so would like to be part of this mailing list. Tania Calcada tcalcada@inescporto.pt > De: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] Em > nome de Shubhranshu > Enviada: quinta-feira, 18 de Novembro de 2004 13:00 > Para: manet@ietf.org > Assunto: [manet] manet autoconf. > > > Hi all, > > MANET WG is developing proactive, reactive and simplified > multicast forwarding protocols. However, > there are other issues fundamental to ad hoc network > operation and deployment such as address > auto-configuration, DAD, gateway discovery and selection for > global prefix allocation and traffic > forwarding, etc. During 61st IETF meeting, Thomas Clausen, > Ruffino Simon, Charles Perkins, Ryuji > Wakikawa, Li Li, Emmanuel Baccelli, myself and few others > discussed about the importance and need to standardize > solutions for these auto-configuration related issues within > IETF. This was > then presented by Simon in the MANET WG meeting. It is > understood that MANET WG may not be the best place to solve > these issues. > > There was some sort of consensus to move forward with this > work. Several independent publications and > implementations are available. As suggested by Joe Macker, > Alex Zinin and others, we are going to set up > a mailing list of those interested in these topics and > willing to contribute. There should be consensus on problem > statement, possible approach, existing solutions, milestones, > etc. So, let me know if you would like to be part of the > mailing list. We are planning to go for BOF/bar-BOF at the > next IETF meeting, > depending on the development on this mailing list. > > Regards, > Shubhranshu > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 13:16:39 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18335 for ; Thu, 18 Nov 2004 13:16:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUqsR-000805-UD for manet-web-archive@ietf.org; Thu, 18 Nov 2004 13:19:29 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUqgt-0007g9-PB; Thu, 18 Nov 2004 13:07:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUqSt-0003yp-Me for manet@megatron.ietf.org; Thu, 18 Nov 2004 12:53:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16284 for ; Thu, 18 Nov 2004 12:52:59 -0500 (EST) Received: from aplexpony.dom1.jhuapl.edu ([128.244.198.131]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUqVY-0007Lt-Cy for manet@ietf.org; Thu, 18 Nov 2004 12:55:48 -0500 Received: from APLESLIBERTY.dom1.jhuapl.edu ([128.244.198.134]) by APLEXPONY.dom1.jhuapl.edu with Microsoft SMTPSVC(6.0.3790.0); Thu, 18 Nov 2004 12:52:27 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] manet autoconf. Date: Thu, 18 Nov 2004 12:52:27 -0500 Message-ID: <0F5AC32D8E455545AD0349BA8400A3CA1B0472@aplesliberty.dom1.jhuapl.edu> Thread-Topic: [manet] manet autoconf. Thread-Index: AcTNld09zE1/KcmXRxC9PN7g3XFlzQAATgQQ From: "Farrag, Osama" To: X-OriginalArrivalTime: 18 Nov 2004 17:52:27.0745 (UTC) FILETIME=[5E342D10:01C4CD97] X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87 Content-Transfer-Encoding: quoted-printable Please include me in the auto-config. Mailing list, I am interested. Johns Hopkins University/APL Osama Farrag =20 -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Rui Campos Sent: Thursday, November 18, 2004 12:17 PM To: Marshall Eubanks; Shubhranshu Cc: manet@ietf.org Subject: Re: [manet] manet autoconf. Hi all, I am interested in those topics as well. Please, add me to the list! =20 Thanks! BR, Rui Campos On Thu, 18 Nov 2004 11:10:26 -0500, Marshall Eubanks =20 wrote: > Hello; > > Please add me to the list. > > Can you provide me with I-D's or RFC numbers for the "simplified > multicast forwarding protocols" ? > > Regards > Marshall Eubanks > > > On Thu, 18 Nov 2004 22:00:20 +0900, Shubhranshu =20 > wrote: >> Hi all, >> >> MANET WG is developing proactive, reactive and simplified multicast =20 >> forwarding protocols. However, >> there are other issues fundamental to ad hoc network operation and =20 >> deployment such as address >> auto-configuration, DAD, gateway discovery and selection for global =20 >> prefix allocation and traffic >> forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino =20 >> Simon, Charles Perkins, Ryuji >> Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed =20 >> about the importance and >> need to standardize solutions for these auto-configuration related =20 >> issues within IETF. This was >> then presented by Simon in the MANET WG meeting. It is understood that =20 >> MANET WG may not be >> the best place to solve these issues. >> >> There was some sort of consensus to move forward with this work. =20 >> Several independent publications and >> implementations are available. As suggested by Joe Macker, Alex Zinin >> and others, we are going to set up >> a mailing list of those interested in these topics and willing to =20 >> contribute. There should be consensus on >> problem statement, possible approach, existing solutions, milestones, >> etc. So, let me know if you would >> like to be part of the mailing list. We are planning to go for =20 >> BOF/bar-BOF at the next IETF meeting, >> depending on the development on this mailing list. >> >> Regards, >> Shubhranshu >> >> _______________________________________________ >> manet mailing 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 Using Opera's revolutionary e-mail client: http://www.opera.com/m2/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 13:21:32 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18730 for ; Thu, 18 Nov 2004 13:21:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUqxA-000883-KM for manet-web-archive@ietf.org; Thu, 18 Nov 2004 13:24:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUqn6-000137-KG; Thu, 18 Nov 2004 13:13:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUqca-0006k3-Rg for manet@megatron.ietf.org; Thu, 18 Nov 2004 13:03:05 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17067 for ; Thu, 18 Nov 2004 13:03:01 -0500 (EST) From: Abhiram.Kampe-1@ou.edu Received: from mail.zero.ou.edu ([129.15.0.75] helo=fourlom.ou.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUqfG-0007c1-88 for manet@ietf.org; Thu, 18 Nov 2004 13:05:50 -0500 Received: from ou.edu ([192.168.11.58]) by fourlom.ou.edu (Sun Java System Messaging Server 6.1 HotFix 0.01 (built Jun 24 2004)) with ESMTP id <0I7D00EWYZG61RD0@fourlom.ou.edu> for manet@ietf.org; Thu, 18 Nov 2004 12:02:30 -0600 (CST) Received: from [129.15.0.75] (Forwarded-For: [68.0.64.173]) by han.ou.edu (mshttpd); Thu, 18 Nov 2004 12:07:19 -0600 Date: Thu, 18 Nov 2004 12:07:19 -0600 Subject: Re: [manet] manet autoconf. To: Shubhranshu Message-id: MIME-version: 1.0 X-Mailer: Sun Java(tm) System Messenger Express 6.1 HotFix 0.01 (built Jun 24 2004) Content-type: text/plain; charset=us-ascii Content-language: en Content-transfer-encoding: 7BIT Content-disposition: inline X-Accept-Language: en Priority: normal X-Spam-Score: 0.4 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7BIT Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7BIT Hi Shubhranshu, Please add me to the list. Thanks Abhiram. Abhiram Kampe Graduate Research Assitant University of Oklahoma USA _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 13:47:37 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA20671 for ; Thu, 18 Nov 2004 13:47:37 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUrMP-0000F8-0g for manet-web-archive@ietf.org; Thu, 18 Nov 2004 13:50:25 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUrF2-0007Yi-Nh; Thu, 18 Nov 2004 13:42:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUqxl-0004If-C6 for manet@megatron.ietf.org; Thu, 18 Nov 2004 13:24:57 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18995 for ; Thu, 18 Nov 2004 13:24:53 -0500 (EST) Received: from mailout1.samsung.com ([203.254.224.24]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUr0Q-0008Cv-9E for manet@ietf.org; Thu, 18 Nov 2004 13:27:43 -0500 Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) id <0I7E005010GNYL@mailout1.samsung.com> for manet@ietf.org; Fri, 19 Nov 2004 03:24:23 +0900 (KST) Received: from ep_ms3_bk (mailout1.samsung.com [203.254.224.24]) by mailout1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0I7E0017O0GN5O@mailout1.samsung.com> for manet@ietf.org; Fri, 19 Nov 2004 03:24:23 +0900 (KST) Received: from localhost (ms3.samsung.com [203.254.225.112]) by ms3.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with SMTP id <0I7E00HTK0GMUV@ms3.samsung.com> for manet@ietf.org; Fri, 19 Nov 2004 03:24:23 +0900 (KST) Date: Thu, 18 Nov 2004 18:24:46 +0000 (GMT) From: Daniel Park Subject: Re: [manet] manet autoconf. X-Sender: =?euc-kr?B?U2Ftc3VuZyBFbGVjdHJvbmljc6HnTW9iaQ==?= =?euc-kr?B?bGUgUGxhdGZvcm0gTGFioedFbmdpbmVlcg==?= To: SINGH SHUBHRANSHU Message-id: <0I7E00HTN0GNUV@ms3.samsung.com> MIME-version: 1.0 X-Priority: 3 Msgkey: 20041118182421899@soohong.park X-MTR: 20041118182421899@soohong.park X-EPLocale: en_US.euc-kr X-EPWebmail-Msg-Type: personal X-EPWebmail-Reply-Demand: 0 X-Generator: NamoMIME 1.1.0.17 X-Spam-Score: 2.5 (++) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Cc: "manet@ietf.org " X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: soohong.park@samsung.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0760701981==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 2.4 (++) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b --===============0760701981== Content-type: text/html; charset=euc-kr Content-Transfer-Encoding: base64 PEhUTUw+PEhFQUQ+CjxNRVRBIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9J3RleHQv aHRtbDsgY2hhcnNldD1ldWMta3InPgo8dGl0bGU+U2Ftc3VuZyBFbnRlcnByaXNlIFBvcnRhbCBt eVNpbmdsZTwvdGl0bGU+CjxzdHlsZT4gUCwgdGQsIGxpIHtmb250LWZhbWlseTqxvLiyw7wsIGFy aWFsOyBmb250LXNpemU6OXB0OyBtYXJnaW4tdG9wOjVweDttYXJnaW4tYm90dG9tOjVweDt9PC9z dHlsZT4KPC9IRUFEPjxCT0RZPjxwPlNpbmdoLiB1cG9uIGNvbXBsZXRpbmcgYSBtYWlsaW5nIGxp c3QsIHBsZWFzZSBmb3J3YXJkIGl0Jm5ic3A7dG8gDQp0aGlzIGxpc3Qgb25jZSBtb3JlLCANCjxw PnRoZW4gdGhvc2Ugd2hvIG5lZWQgdG8gam9pbiBpdCB3aWxsIGVhc2lseSByZWdpc3RlciB0aGUg bmFtZSBpbiB0aGUmbmJzcDthdXRvbWF0aWMgDQptYW5uZXIuPGJyPjwvcD4NCjxwPiZuYnNwOzwv cD4NCjxwPlRoYW5rcyB5b3VyIGVmZm9ydCBpbiBhZHZhbmNlLjxicj48YnI+RGFuaWVsPGJyPjxi cj4tLS0tLS0tIDxiPk9yaWdpbmFsIE1lc3NhZ2U8L2I+IC0tLS0tLS08YnI+PGI+U2VuZGVyPC9i PiA6IFNJTkdIIFNIVUJIUkFOU0hVJmx0O3NodWJocmFuc2h1QHNhbXN1bmcuY29tJmd0OyBBc3Np c3RhbnQ/UmVzZWFyY2g/U3RhZmYvQ29tbXVuaWNhdGlvbiAmYW1wOyBOZXR3b3JrIExhYi9TYW1z dW5nIEFkdmFuY2VkIEluc3RpdHV0ZSBvZiBUZWNobm9sb2d5PGJyPjxiPkRhdGU8L2I+ICAgOiBO b3YgMTgsIDIwMDQgMjI6MDA8YnI+PGI+VGl0bGU8L2I+ICA6IFttYW5ldF0gbWFuZXQgYXV0b2Nv bmYuPGJyPkhpJm5ic3A7YWxsLA0KPGJyPg0KPGJyPk1BTkVUJm5ic3A7V0cmbmJzcDtpcyZuYnNw O2RldmVsb3BpbmcmbmJzcDtwcm9hY3RpdmUsJm5ic3A7cmVhY3RpdmUmbmJzcDthbmQmbmJzcDtz aW1wbGlmaWVkJm5ic3A7bXVsdGljYXN0Jm5ic3A7Zm9yd2FyZGluZyZuYnNwO3Byb3RvY29scy4m bmJzcDtIb3dldmVyLCZuYnNwOw0KPGJyPnRoZXJlJm5ic3A7YXJlJm5ic3A7b3RoZXImbmJzcDtp c3N1ZXMmbmJzcDtmdW5kYW1lbnRhbCZuYnNwO3RvJm5ic3A7YWQmbmJzcDtob2MmbmJzcDtuZXR3 b3JrJm5ic3A7b3BlcmF0aW9uJm5ic3A7YW5kJm5ic3A7ZGVwbG95bWVudCZuYnNwO3N1Y2gmbmJz cDthcyZuYnNwO2FkZHJlc3MmbmJzcDsNCjxicj5hdXRvLWNvbmZpZ3VyYXRpb24sJm5ic3A7REFE LCZuYnNwO2dhdGV3YXkmbmJzcDtkaXNjb3ZlcnkmbmJzcDthbmQmbmJzcDtzZWxlY3Rpb24mbmJz cDtmb3ImbmJzcDtnbG9iYWwmbmJzcDtwcmVmaXgmbmJzcDthbGxvY2F0aW9uJm5ic3A7YW5kJm5i c3A7dHJhZmZpYyZuYnNwOw0KPGJyPmZvcndhcmRpbmcsJm5ic3A7ZXRjLiZuYnNwO0R1cmluZyZu YnNwOzYxc3QmbmJzcDtJRVRGJm5ic3A7bWVldGluZywmbmJzcDtUaG9tYXMmbmJzcDtDbGF1c2Vu LCZuYnNwO1J1ZmZpbm8mbmJzcDtTaW1vbiwmbmJzcDtDaGFybGVzJm5ic3A7UGVya2lucywmbmJz cDtSeXVqaSZuYnNwOw0KPGJyPldha2lrYXdhLCZuYnNwO0xpJm5ic3A7TGksJm5ic3A7RW1tYW51 ZWwmbmJzcDtCYWNjZWxsaSwmbmJzcDtteXNlbGYmbmJzcDthbmQmbmJzcDtmZXcmbmJzcDtvdGhl cnMmbmJzcDtkaXNjdXNzZWQmbmJzcDthYm91dCZuYnNwO3RoZSZuYnNwO2ltcG9ydGFuY2UmbmJz cDthbmQNCjxicj5uZWVkJm5ic3A7dG8mbmJzcDtzdGFuZGFyZGl6ZSZuYnNwO3NvbHV0aW9ucyZu YnNwO2ZvciZuYnNwO3RoZXNlJm5ic3A7YXV0by1jb25maWd1cmF0aW9uJm5ic3A7cmVsYXRlZCZu YnNwO2lzc3VlcyZuYnNwO3dpdGhpbiZuYnNwO0lFVEYuJm5ic3A7VGhpcyZuYnNwO3dhcyZuYnNw Ow0KPGJyPnRoZW4mbmJzcDtwcmVzZW50ZWQmbmJzcDtieSZuYnNwO1NpbW9uJm5ic3A7aW4mbmJz cDt0aGUmbmJzcDtNQU5FVCZuYnNwO1dHJm5ic3A7bWVldGluZy4mbmJzcDtJdCZuYnNwO2lzJm5i c3A7dW5kZXJzdG9vZCZuYnNwO3RoYXQmbmJzcDtNQU5FVCZuYnNwO1dHJm5ic3A7bWF5Jm5ic3A7 bm90Jm5ic3A7YmUNCjxicj50aGUmbmJzcDtiZXN0Jm5ic3A7cGxhY2UmbmJzcDt0byZuYnNwO3Nv bHZlJm5ic3A7dGhlc2UmbmJzcDtpc3N1ZXMuDQo8YnI+DQo8YnI+VGhlcmUmbmJzcDt3YXMmbmJz cDtzb21lJm5ic3A7c29ydCZuYnNwO29mJm5ic3A7Y29uc2Vuc3VzJm5ic3A7dG8mbmJzcDttb3Zl Jm5ic3A7Zm9yd2FyZCZuYnNwO3dpdGgmbmJzcDt0aGlzJm5ic3A7d29yay4mbmJzcDtTZXZlcmFs Jm5ic3A7aW5kZXBlbmRlbnQmbmJzcDtwdWJsaWNhdGlvbnMmbmJzcDthbmQmbmJzcDsNCjxicj5p bXBsZW1lbnRhdGlvbnMmbmJzcDthcmUmbmJzcDthdmFpbGFibGUuJm5ic3A7QXMmbmJzcDtzdWdn ZXN0ZWQmbmJzcDtieSZuYnNwO0pvZSZuYnNwO01hY2tlciwmbmJzcDtBbGV4Jm5ic3A7WmluaW4m bmJzcDthbmQmbmJzcDtvdGhlcnMsJm5ic3A7d2UmbmJzcDthcmUmbmJzcDtnb2luZyZuYnNwO3Rv Jm5ic3A7c2V0Jm5ic3A7dXAmbmJzcDsNCjxicj5hJm5ic3A7bWFpbGluZyZuYnNwO2xpc3QmbmJz cDtvZiZuYnNwO3Rob3NlJm5ic3A7aW50ZXJlc3RlZCZuYnNwO2luJm5ic3A7dGhlc2UmbmJzcDt0 b3BpY3MmbmJzcDthbmQmbmJzcDt3aWxsaW5nJm5ic3A7dG8mbmJzcDtjb250cmlidXRlLiZuYnNw O1RoZXJlJm5ic3A7c2hvdWxkJm5ic3A7YmUmbmJzcDtjb25zZW5zdXMmbmJzcDtvbg0KPGJyPnBy b2JsZW0mbmJzcDtzdGF0ZW1lbnQsJm5ic3A7cG9zc2libGUmbmJzcDthcHByb2FjaCwmbmJzcDtl eGlzdGluZyZuYnNwO3NvbHV0aW9ucywmbmJzcDttaWxlc3RvbmVzLCZuYnNwO2V0Yy4mbmJzcDtT bywmbmJzcDtsZXQmbmJzcDttZSZuYnNwO2tub3cmbmJzcDtpZiZuYnNwO3lvdSZuYnNwO3dvdWxk DQo8YnI+bGlrZSZuYnNwO3RvJm5ic3A7YmUmbmJzcDtwYXJ0Jm5ic3A7b2YmbmJzcDt0aGUmbmJz cDttYWlsaW5nJm5ic3A7bGlzdC4mbmJzcDtXZSZuYnNwO2FyZSZuYnNwO3BsYW5uaW5nJm5ic3A7 dG8mbmJzcDtnbyZuYnNwO2ZvciZuYnNwO0JPRi9iYXItQk9GJm5ic3A7YXQmbmJzcDt0aGUmbmJz cDtuZXh0Jm5ic3A7SUVURiZuYnNwO21lZXRpbmcsJm5ic3A7DQo8YnI+ZGVwZW5kaW5nJm5ic3A7 b24mbmJzcDt0aGUmbmJzcDtkZXZlbG9wbWVudCZuYnNwO29uJm5ic3A7dGhpcyZuYnNwO21haWxp bmcmbmJzcDtsaXN0Lg0KPGJyPg0KPGJyPlJlZ2FyZHMsDQo8YnI+U2h1YmhyYW5zaHUNCjxicj4N Cjxicj4NCjxicj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Xw0KPGJyPm1hbmV0Jm5ic3A7bWFpbGluZyZuYnNwO2xpc3QNCjxicj5tYW5ldEBpZXRmLm9yZw0K PGJyPmh0dHBzOi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21hbmV0DQo8YnI+DQo8 YnI+DQo8YnI+PGJyPjxicj4mbmJzcDsNCjwvcD4NCjxwPiZuYnNwOzwvcD4NCjxwPiZuYnNwOzwv cD4NCjxwPiZuYnNwOzwvcD4NCjxwPiZuYnNwOzwvcD4NCjxwPlJlZ2FyZHMNCg0KICAgDQo8L3A+ DQo8cD4mbmJzcDs8L3A+DQo8cD5EYW5pZWwgKFNvb2hvbmcgRGFuaWVsIFBhcmspDQo8L3A+DQo8 cD5Nb2JpbGUgUGxhdGZvcm0gTGFib3JhdG9yeS4gU0FNU1VORyBFbGVjdHJvbmljczwvcD4NCjxw PiZuYnNwOzwvcD4NCjxwPiZuYnNwOzwvcD48YnI+PC9CT0RZPjwvSFRNTD4= --===============0760701981== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0760701981==-- From manet-bounces@ietf.org Thu Nov 18 13:52:27 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21211 for ; Thu, 18 Nov 2004 13:52:27 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUrR4-0000NE-H2 for manet-web-archive@ietf.org; Thu, 18 Nov 2004 13:55:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUrFh-0007yX-Ak; Thu, 18 Nov 2004 13:43:29 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUr1T-0004lv-5e for manet@megatron.ietf.org; Thu, 18 Nov 2004 13:28:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19286 for ; Thu, 18 Nov 2004 13:28:43 -0500 (EST) Received: from mailout3.samsung.com ([203.254.224.33]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUr47-0008H8-Md for manet@ietf.org; Thu, 18 Nov 2004 13:31:33 -0500 Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I7E000010N13B@mailout3.samsung.com> for manet@ietf.org; Fri, 19 Nov 2004 03:28:13 +0900 (KST) Received: from ep_ms3_bk (mailout3.samsung.com [203.254.224.33]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I7E000NW0N1L3@mailout3.samsung.com> for manet@ietf.org; Fri, 19 Nov 2004 03:28:13 +0900 (KST) Received: from localhost (ms3.samsung.com [203.254.225.112]) by ms3.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with SMTP id <0I7E0050E0N140@ms3.samsung.com> for manet@ietf.org; Fri, 19 Nov 2004 03:28:13 +0900 (KST) Date: Thu, 18 Nov 2004 18:28:36 +0000 (GMT) From: Daniel Park Subject: Re: Re: [manet] manet autoconf. X-Sender: =?windows-1252?B?U2Ftc3VuZyBFbGVjdHJvbmljcz9Nb2Jp?= =?windows-1252?B?bGUgUGxhdGZvcm0gTGFiP0VuZ2luZWVy?= Message-id: <0I7E0050H0N140@ms3.samsung.com> MIME-version: 1.0 X-Priority: 3 Msgkey: 20041118182811128@soohong.park X-MTR: 20041118182811128@soohong.park X-EPLocale: en_US.windows-1252 X-EPWebmail-Msg-Type: personal X-EPWebmail-Reply-Demand: 0 X-Generator: NamoMIME 1.1.0.17 X-Spam-Score: 1.4 (+) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: SINGH SHUBHRANSHU , "manet@ietf.org " X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: soohong.park@samsung.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1088285904==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.6 (+) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 --===============1088285904== Content-type: text/html; charset=windows-1252 Content-Transfer-Encoding: 7BIT Samsung Enterprise Portal mySingle

Singh. upon completing a mailing list, please forward it to this list once more,

then those who need to join it will easily register the name in the automatic manner.

It will avoid flooding the all same response "please add me..."

 

Thanks your effort in advance.

Daniel (Soohong Daniel Park)

Mobile Platform Laboratory. SAMSUNG Electronics

 

 


--===============1088285904== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1088285904==-- From manet-bounces@ietf.org Thu Nov 18 15:21:40 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02618 for ; Thu, 18 Nov 2004 15:21:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUspO-0002jk-Lc for manet-web-archive@ietf.org; Thu, 18 Nov 2004 15:24:29 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUsfm-0006ov-Pi; Thu, 18 Nov 2004 15:14:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUsZc-00034n-0G for manet@megatron.ietf.org; Thu, 18 Nov 2004 15:08:08 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00131 for ; Thu, 18 Nov 2004 15:08:05 -0500 (EST) Received: from smtp108.mail.sc5.yahoo.com ([66.163.170.6]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CUscH-0002Iu-4I for manet@ietf.org; Thu, 18 Nov 2004 15:10:54 -0500 Received: from unknown (HELO ?192.168.200.2?) (fjrm4@83.44.49.216 with plain) by smtp108.mail.sc5.yahoo.com with SMTP; 18 Nov 2004 20:08:04 -0000 From: "Francisco J. Ros" To: manet@ietf.org Subject: Re: [manet] manet autoconf. Date: Thu, 18 Nov 2004 21:08:17 +0100 User-Agent: KMail/1.6.1 References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200411182108.17901.fjrm@dif.um.es> X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: quoted-printable Cc: Shubhranshu X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: quoted-printable I'd also like joining the list. Thanks, =46rancisco J. Ros El Jueves, 18 de Noviembre de 2004 14:00, Shubhranshu escribi=F3: > Hi all, > > MANET WG is developing proactive, reactive and simplified multicast > forwarding protocols. However, there are other issues fundamental to ad h= oc > network operation and deployment such as address auto-configuration, DAD, > gateway discovery and selection for global prefix allocation and traffic > forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, > Charles Perkins, Ryuji Wakikawa, Li Li, Emmanuel Baccelli, myself and few > others discussed about the importance and need to standardize solutions f= or > these auto-configuration related issues within IETF. This was then > presented by Simon in the MANET WG meeting. It is understood that MANET WG > may not be the best place to solve these issues. > > There was some sort of consensus to move forward with this work. Several > independent publications and implementations are available. As suggested = by > Joe Macker, Alex Zinin and others, we are going to set up a mailing list = of > those interested in these topics and willing to contribute. There should = be > consensus on problem statement, possible approach, existing solutions, > milestones, etc. So, let me know if you would like to be part of the > mailing list. We are planning to go for BOF/bar-BOF at the next IETF > meeting, depending on the development on this mailing list. > > Regards, > Shubhranshu > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 16:38:31 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18768 for ; Thu, 18 Nov 2004 16:38:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUu1p-0007ZK-0m for manet-web-archive@ietf.org; Thu, 18 Nov 2004 16:41:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUtfC-0004dS-9G; Thu, 18 Nov 2004 16:17:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUt0h-0003JW-7o for manet@megatron.ietf.org; Thu, 18 Nov 2004 15:36:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04548 for ; Thu, 18 Nov 2004 15:36:04 -0500 (EST) Received: from mmlab.snu.ac.kr ([147.46.114.112]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUt3N-0003Dt-4N for manet@ietf.org; Thu, 18 Nov 2004 15:38:54 -0500 Received: from MMLABFOMULA ([147.46.216.59]) by mmlab.snu.ac.kr (8.12.10/8.12.10) with ESMTP id iAIKcI9M048505; Fri, 19 Nov 2004 05:38:18 +0900 (KST) (envelope-from fomula@mmlab.snu.ac.kr) Message-Id: <200411182038.iAIKcI9M048505@mmlab.snu.ac.kr> From: "Nakjung Choi" To: "'Shubhranshu'" , Subject: RE: [manet] manet autoconf. Date: Fri, 19 Nov 2004 05:35:53 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Thread-Index: AcTNcJHWyR9DOSMFRty7OFpTy4VSNQAPQe1Q X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Content-Transfer-Encoding: 7bit Hi Shubhranshu, Please add me to the mailing list, too. Thanks, Choi. ======================================================================== Nakjung Choi, Ph.D. Student, School of Computer Science & Engineering Seoul National University Email: fomula@mmlab.snu.ac.kr Homepage: http://mmlab.snu.ac.kr/~fomula/ Phone: +82-2-876-7170 (Office) -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Shubhranshu Sent: Thursday, November 18, 2004 10:00 PM To: manet@ietf.org Subject: [manet] manet autoconf. Hi all, MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, there are other issues fundamental to ad hoc network operation and deployment such as address auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and need to standardize solutions for these auto-configuration related issues within IETF. This was then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be the best place to solve these issues. There was some sort of consensus to move forward with this work. Several independent publications and implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up a mailing list of those interested in these topics and willing to contribute. There should be consensus on problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, depending on the development on this mailing list. Regards, Shubhranshu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 17:08:35 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23666 for ; Thu, 18 Nov 2004 17:08:35 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUuUw-0000Ml-2q for manet-web-archive@ietf.org; Thu, 18 Nov 2004 17:11:26 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUuFw-0003da-3K; Thu, 18 Nov 2004 16:55:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUu2n-0006J4-Ke for manet@megatron.ietf.org; Thu, 18 Nov 2004 16:42:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19924 for ; Thu, 18 Nov 2004 16:42:19 -0500 (EST) Received: from fed1rmmtao10.cox.net ([68.230.241.29]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUu5U-0007pA-Th for manet@ietf.org; Thu, 18 Nov 2004 16:45:09 -0500 Received: from [192.168.0.11] (really [68.6.77.43]) by fed1rmmtao10.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041118214149.KTMV18545.fed1rmmtao10.cox.net@[192.168.0.11]>; Thu, 18 Nov 2004 16:41:49 -0500 In-Reply-To: <8497-SnapperMsgD302CB11BDC24FFA@192.168.0.192> References: Message-ID: <8497-SnapperMsgD302CB11BDC24FFA@192.168.0.192> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1CC461A4-39A1-11D9-830D-000A95C1BC0A@cs.ucsb.edu> Content-Transfer-Encoding: 7bit From: Ian Chakeres Subject: Re: [manet] Path Accumulation in DyMO Date: Thu, 18 Nov 2004 12:33:31 -0800 To: "Charles E. Perkins" , Thomas Heide Clausen , "'manet'" , Justin Dean X-Mailer: Apple Mail (2.619) X-Spam-Score: 0.1 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a Content-Transfer-Encoding: 7bit First I want to issue a query to the list. Does anyone think we should use path accumulation to alleviate creating a reverse route to the source during RREQ propagation? I'd like to get consensus that this is a non-issue. Given that we don't perform path accumulation for the reason of not storing the reverse route during RREQ propagation, I think there are a large number of possibilities for disseminating additional information. For example, we could include each node on the path, and their sequence number. Alternatively we could create a more modular option that allows us to include only some nodes on the path. Or even more versatile a method to disseminate routes that are not on the RREQ/RREP path (i.e. gateways). It could even carry additional information, hop count, metric, security information, etc... Given all these choices I would prefer to leave this as an open issue pending experimentation, instead of attempting to specify the "way" to do it in the base spec. Obviously we could do both, specify one way and allow additional options for others. I'm open to that option also. Does anyone have a feeling as to what if any technique should be included in the base specification but not mandated? What information should be disseminated? Thanks. Ian Chakeres On Nov 18, 2004, at 5:11 AM, Thomas Heide Clausen wrote: > Ian, > > I am still of the general opinion that leaving an option unspecified > is a > bad thing, assuming that it's an option which (i) a plurality of > deployments might use and (ii) where different > approaches/implementations > might impair interoperability. > > What's the general observations on (i) and (ii) regarding > path-accumulation? > > --thomas > ___ > Sent with SnapperMail > www.snappermail.com > > ...... Original Message ....... > On Fri, 12 Nov 2004 06:59:15 -0500 Ian Chakeres > wrote: >> At the MANET meeting I presented DyMO (Dynamic MANET On-demand Routing >> Protocol). My slides from the presentation are available at >> http://moment.cs.ucsb.edu/~idc/pub/chakeres_ietf61_presentation.pdf. >> >> There was a short discussion about using path accumulation in the base >> specification. Most people expressed their feelings that path >> accumulation is useful for additional route information dissemination. >> I believe there was consensus to not include path accumulation in the >> core spec though it should definitely be included as an optimization. >> If you disagree, lets discuss it more on the list. >> >> Thanks. >> Ian Chakeres >> >> >> _______________________________________________ >> manet mailing list >> manet@ietf.org >> https://www1.ietf.org/mailman/listinfo/manet >> _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 18:13:19 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01176 for ; Thu, 18 Nov 2004 18:13:18 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUvVa-00021d-66 for manet-web-archive@ietf.org; Thu, 18 Nov 2004 18:16:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUvMi-00038M-Pj; Thu, 18 Nov 2004 18:07:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUvEw-0007JN-04 for manet@megatron.ietf.org; Thu, 18 Nov 2004 17:58:58 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29194 for ; Thu, 18 Nov 2004 17:58:54 -0500 (EST) Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUvHd-0001iY-SI for manet@ietf.org; Thu, 18 Nov 2004 18:01:46 -0500 Received: from xdsl-3173.wroclaw.dialog.net.pl ([81.168.156.101] helo=192.168.0.1) by mx2.foretec.com with smtp (Exim 4.24) id 1CUvEu-0000pq-Lo for manet@ietf.org; Thu, 18 Nov 2004 17:58:56 -0500 Message-ID: <003a01c4cdc2$231d2a80$659ca851@saddamlennon> From: "Grzegorz Jablonski" To: "manet" References: <4198E0E9.7070606@telecom.lth.se> Subject: Re: [manet] broadcasting in 802.11 Date: Thu, 18 Nov 2004 23:58:36 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.3 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: 7bit > Hi, > > Using 802.11, no control frames are used for broadcast packets, so they > are "unreliable" and a station never knows if a broadcast message was > received by its neighbors or not. Now my question is: How can a station > broadcast a message and be sure that all its neighbors received the > message? > > Is there any suggestions for extending 802.11 so that broadcast messages > become "reliable"? > > Kind regards > Ali I think this is technically impossible. Sender can wait for an acknowledgement from all it neighbours, but how will it know taht the information he's got about neighbours is correct? I may be wrong, but as far as I know wireless node may only have approximated and usually slightly outdated information about his neighbours. Therefore you can never make sure that all neighbours have received your message. The approximated information can as well be enough for your needs. Greg > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 18:14:54 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01377 for ; Thu, 18 Nov 2004 18:14:54 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUvX7-000245-St for manet-web-archive@ietf.org; Thu, 18 Nov 2004 18:17:46 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUvNK-0003Xo-VD; Thu, 18 Nov 2004 18:07:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUvHg-0008EF-Bc for manet@megatron.ietf.org; Thu, 18 Nov 2004 18:01:48 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29405 for ; Thu, 18 Nov 2004 18:01:45 -0500 (EST) Received: from po0.glue.umd.edu ([128.8.70.17]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUvKO-0001lm-7b for manet@ietf.org; Thu, 18 Nov 2004 18:04:36 -0500 Received: from z.glue.umd.edu (IDENT:sendmail@z.glue.umd.edu [128.8.10.71]) by po0.glue.umd.edu (8.12.10/8.12.10) with ESMTP id iAIN1hGs004407; Thu, 18 Nov 2004 18:01:43 -0500 (EST) Received: from localhost (kerk@localhost) by z.glue.umd.edu (8.12.10/8.12.10) with ESMTP id iAIN1g88006711; Thu, 18 Nov 2004 18:01:43 -0500 (EST) X-Authentication-Warning: z.glue.umd.edu: kerk owned process doing -bs Date: Thu, 18 Nov 2004 18:01:42 -0500 (EST) From: Kyriakos Manousakis To: Shubhranshu Subject: Re: [manet] manet autoconf. In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Hi Shubhrashu, i am also interested in the auto-configuration issue. Could you please add me to the list? Thanks Kyriakos On Thu, 18 Nov 2004, Shubhranshu wrote: > Hi all, > > MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, > there are other issues fundamental to ad hoc network operation and deployment such as address > auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic > forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji > Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and > need to standardize solutions for these auto-configuration related issues within IETF. This was > then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be > the best place to solve these issues. > > There was some sort of consensus to move forward with this work. Several independent publications and > implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up > a mailing list of those interested in these topics and willing to contribute. There should be consensus on > problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would > like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, > depending on the development on this mailing list. > > Regards, > Shubhranshu > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > ________________________________________________________ -------------------------------------------------------- KYRIAKOS MANOUSAKIS Graduate Research Assistant Center for Satellite and Hybrid Communication Networks University of MD, College Park URL:http://www.isr.umd.edu/~kerk ________________________________________________________ -------------------------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 18:18:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02138 for ; Thu, 18 Nov 2004 18:18:50 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUvak-0002BO-UZ for manet-web-archive@ietf.org; Thu, 18 Nov 2004 18:21:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUvNO-0003aA-UM; Thu, 18 Nov 2004 18:07:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUvLi-0002Wx-GE for manet@megatron.ietf.org; Thu, 18 Nov 2004 18:05:58 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29774 for ; Thu, 18 Nov 2004 18:05:54 -0500 (EST) Received: from [202.20.142.15] (helo=sm.sait.samsung.co.kr) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUvOE-0001q5-F6 for manet@ietf.org; Thu, 18 Nov 2004 18:08:46 -0500 Received: from sm.sait.samsung.co.kr (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 0DF60E5D51; Fri, 19 Nov 2004 08:04:22 +0900 (KST) Received: from 127.0.0.1 by 127.0.0.1(smtpfilter) with ESMTP; Fri, 19 Nov 2004 08:04:21 +0900 (KST) Received: from LocalHost (unknown [75.2.93.47]) by sm.sait.samsung.co.kr (Postfix) with SMTP id:738DBE5B05; Fri, 19 Nov 2004 08:04:21 +0900 (KST) Message-ID: <004201c4cdc3$0f32f0d0$2f5d024b@LocalHost> From: "Jihoon Lee" To: "Shubhranshu" , References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Subject: Re: [manet] manet autoconf. Date: Fri, 19 Nov 2004 08:05:12 +0900 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 1.1 (+) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0085688671==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 --===============0085688671== Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 SGkuIFNodWJocmFuc2h1DQoNClBsZWFzZSBhZGQgbWUgdG8gdGhlIGxpc3QuDQpUaGFua3MgaW4g YWR2YW5jZS4NCg0KDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tIA0KRnJvbTogIlNodWJo cmFuc2h1IiA8c2h1YmhyYW5zaHVAc2Ftc3VuZy5jb20+DQpUbzogPG1hbmV0QGlldGYub3JnPg0K U2VudDogVGh1cnNkYXksIE5vdmVtYmVyIDE4LCAyMDA0IDEwOjAwIFBNDQpTdWJqZWN0OiBbbWFu ZXRdIG1hbmV0IGF1dG9jb25mLg0KDQoNCj4gSGkgYWxsLA0KPiANCj4gTUFORVQgV0cgaXMgZGV2 ZWxvcGluZyBwcm9hY3RpdmUsIHJlYWN0aXZlIGFuZCBzaW1wbGlmaWVkIG11bHRpY2FzdCBmb3J3 YXJkaW5nIHByb3RvY29scy4gSG93ZXZlciwgDQo+IHRoZXJlIGFyZSBvdGhlciBpc3N1ZXMgZnVu ZGFtZW50YWwgdG8gYWQgaG9jIG5ldHdvcmsgb3BlcmF0aW9uIGFuZCBkZXBsb3ltZW50IHN1Y2gg YXMgYWRkcmVzcyANCj4gYXV0by1jb25maWd1cmF0aW9uLCBEQUQsIGdhdGV3YXkgZGlzY292ZXJ5 IGFuZCBzZWxlY3Rpb24gZm9yIGdsb2JhbCBwcmVmaXggYWxsb2NhdGlvbiBhbmQgdHJhZmZpYyAN Cj4gZm9yd2FyZGluZywgZXRjLiBEdXJpbmcgNjFzdCBJRVRGIG1lZXRpbmcsIFRob21hcyBDbGF1 c2VuLCBSdWZmaW5vIFNpbW9uLCBDaGFybGVzIFBlcmtpbnMsIFJ5dWppIA0KPiBXYWtpa2F3YSwg TGkgTGksIEVtbWFudWVsIEJhY2NlbGxpLCBteXNlbGYgYW5kIGZldyBvdGhlcnMgZGlzY3Vzc2Vk IGFib3V0IHRoZSBpbXBvcnRhbmNlIGFuZA0KPiBuZWVkIHRvIHN0YW5kYXJkaXplIHNvbHV0aW9u cyBmb3IgdGhlc2UgYXV0by1jb25maWd1cmF0aW9uIHJlbGF0ZWQgaXNzdWVzIHdpdGhpbiBJRVRG LiBUaGlzIHdhcyANCj4gdGhlbiBwcmVzZW50ZWQgYnkgU2ltb24gaW4gdGhlIE1BTkVUIFdHIG1l ZXRpbmcuIEl0IGlzIHVuZGVyc3Rvb2QgdGhhdCBNQU5FVCBXRyBtYXkgbm90IGJlDQo+IHRoZSBi ZXN0IHBsYWNlIHRvIHNvbHZlIHRoZXNlIGlzc3Vlcy4NCj4gDQo+IFRoZXJlIHdhcyBzb21lIHNv cnQgb2YgY29uc2Vuc3VzIHRvIG1vdmUgZm9yd2FyZCB3aXRoIHRoaXMgd29yay4gU2V2ZXJhbCBp bmRlcGVuZGVudCBwdWJsaWNhdGlvbnMgYW5kIA0KPiBpbXBsZW1lbnRhdGlvbnMgYXJlIGF2YWls YWJsZS4gQXMgc3VnZ2VzdGVkIGJ5IEpvZSBNYWNrZXIsIEFsZXggWmluaW4gYW5kIG90aGVycywg d2UgYXJlIGdvaW5nIHRvIHNldCB1cCANCj4gYSBtYWlsaW5nIGxpc3Qgb2YgdGhvc2UgaW50ZXJl c3RlZCBpbiB0aGVzZSB0b3BpY3MgYW5kIHdpbGxpbmcgdG8gY29udHJpYnV0ZS4gVGhlcmUgc2hv dWxkIGJlIGNvbnNlbnN1cyBvbg0KPiBwcm9ibGVtIHN0YXRlbWVudCwgcG9zc2libGUgYXBwcm9h Y2gsIGV4aXN0aW5nIHNvbHV0aW9ucywgbWlsZXN0b25lcywgZXRjLiBTbywgbGV0IG1lIGtub3cg aWYgeW91IHdvdWxkDQo+IGxpa2UgdG8gYmUgcGFydCBvZiB0aGUgbWFpbGluZyBsaXN0LiBXZSBh cmUgcGxhbm5pbmcgdG8gZ28gZm9yIEJPRi9iYXItQk9GIGF0IHRoZSBuZXh0IElFVEYgbWVldGlu ZywgDQo+IGRlcGVuZGluZyBvbiB0aGUgZGV2ZWxvcG1lbnQgb24gdGhpcyBtYWlsaW5nIGxpc3Qu DQo+IA0KPiBSZWdhcmRzLA0KPiBTaHViaHJhbnNodQ0KPiANCj4gDQo+IF9fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IG1hbmV0IG1haWxpbmcgbGlzdA0K PiBtYW5ldEBpZXRmLm9yZw0KPiBodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m by9tYW5ldA0KPiANCj4= --===============0085688671== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0085688671==-- From manet-bounces@ietf.org Thu Nov 18 21:38:31 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19787 for ; Thu, 18 Nov 2004 21:38:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUyiB-0006ls-IZ for manet-web-archive@ietf.org; Thu, 18 Nov 2004 21:41:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUyYI-0001VD-Ce; Thu, 18 Nov 2004 21:31:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUyW3-0000oa-Mi for manet@megatron.ietf.org; Thu, 18 Nov 2004 21:28:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18861 for ; Thu, 18 Nov 2004 21:28:49 -0500 (EST) Received: from osdp-gw.osdp.is.tsukuba.ac.jp ([130.158.83.245] helo=rasheen.osdp.cs.tsukuba.ac.jp) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUyYm-0006Wg-MD for manet@ietf.org; Thu, 18 Nov 2004 21:31:41 -0500 Received: from alcyone (lrd.osdp.is.tsukuba.ac.jp [130.158.83.81]) by rasheen.osdp.cs.tsukuba.ac.jp (8.13.1/8.13.1) with ESMTP id iAJ2SDpt083838; Fri, 19 Nov 2004 11:28:13 +0900 (JST) (envelope-from lrd@osdp.is.tsukuba.ac.jp) From: "LiRuidong" To: "'Shubhranshu'" Subject: RE: [manet] manet autoconf. Date: Fri, 19 Nov 2004 11:28:09 +0900 Message-ID: <001801c4cddf$6a8b4650$51539e82@alcyone> 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: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2739.300 Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit Dear Shubhranshu: Could you add me to the list? I am interested in MANET auto-configuration. Best regards, Li -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Shubhranshu Sent: Thursday, November 18, 2004 10:00 PM To: manet@ietf.org Subject: [manet] manet autoconf. Hi all, MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, there are other issues fundamental to ad hoc network operation and deployment such as address auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and need to standardize solutions for these auto-configuration related issues within IETF. This was then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be the best place to solve these issues. There was some sort of consensus to move forward with this work. Several independent publications and implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up a mailing list of those interested in these topics and willing to contribute. There should be consensus on problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, depending on the development on this mailing list. Regards, Shubhranshu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 23:36:26 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29594 for ; Thu, 18 Nov 2004 23:36:26 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV0YK-0000v1-D8 for manet-web-archive@ietf.org; Thu, 18 Nov 2004 23:39:20 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV0SM-0006Iv-UQ; Thu, 18 Nov 2004 23:33:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV0MV-0004Bm-HN for manet@megatron.ietf.org; Thu, 18 Nov 2004 23:27:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28698 for ; Thu, 18 Nov 2004 23:27:04 -0500 (EST) Received: from web53003.mail.yahoo.com ([206.190.39.193]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CV0PE-0000hr-UN for manet@ietf.org; Thu, 18 Nov 2004 23:29:58 -0500 Received: (qmail 64031 invoked by uid 60001); 19 Nov 2004 04:26:34 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=swnxEDfnm9CgtmtaS/MzskEzrQhu01+bKn+XsZs8riHcir7KUtmKjjSlCccCxQo8HIuAjpFza1Pajm17PcQ7enSWA7wwP8yWIPFRzqy0ItV2W1CYTadMxYtkp6kKGW39UEZPBbGzdcd/gagetzLHRcPxkrhhNv+2rdsqDEKKUd8= ; Message-ID: <20041119042634.64029.qmail@web53003.mail.yahoo.com> Received: from [155.69.5.235] by web53003.mail.yahoo.com via HTTP; Thu, 18 Nov 2004 20:26:34 PST Date: Thu, 18 Nov 2004 20:26:34 -0800 (PST) From: Gayathri Subject: Re: [manet] manet autoconf. To: Shubhranshu In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Dear Shubhranshu: Could you add me to the list? I am interested in MANET auto-configuration. Thanking you Best regards, Gayathri Venkataraman --- Shubhranshu wrote: > Hi all, > > MANET WG is developing proactive, reactive and > simplified multicast forwarding protocols. However, > there are other issues fundamental to ad hoc network > operation and deployment such as address > auto-configuration, DAD, gateway discovery and > selection for global prefix allocation and traffic > forwarding, etc. During 61st IETF meeting, Thomas > Clausen, Ruffino Simon, Charles Perkins, Ryuji > Wakikawa, Li Li, Emmanuel Baccelli, myself and few > others discussed about the importance and > need to standardize solutions for these > auto-configuration related issues within IETF. This > was > then presented by Simon in the MANET WG meeting. It > is understood that MANET WG may not be > the best place to solve these issues. > > There was some sort of consensus to move forward > with this work. Several independent publications and > > implementations are available. As suggested by Joe > Macker, Alex Zinin and others, we are going to set > up > a mailing list of those interested in these topics > and willing to contribute. There should be consensus > on > problem statement, possible approach, existing > solutions, milestones, etc. So, let me know if you > would > like to be part of the mailing list. We are planning > to go for BOF/bar-BOF at the next IETF meeting, > depending on the development on this mailing list. > > Regards, > Shubhranshu > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 18 23:45:09 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00551 for ; Thu, 18 Nov 2004 23:45:09 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV0gl-00017s-HJ for manet-web-archive@ietf.org; Thu, 18 Nov 2004 23:48:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV0SS-0006KI-Cp; Thu, 18 Nov 2004 23:33:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV0OT-0004gG-4M for manet@megatron.ietf.org; Thu, 18 Nov 2004 23:29:09 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28872 for ; Thu, 18 Nov 2004 23:29:06 -0500 (EST) Received: from web53001.mail.yahoo.com ([206.190.39.191]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CV0RC-0000k8-4i for manet@ietf.org; Thu, 18 Nov 2004 23:32:00 -0500 Received: (qmail 16937 invoked by uid 60001); 19 Nov 2004 04:28:31 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=lGprDgzQhVBliKE1bEZFIucQai8c07A8yOqSqepjg2GAzMYT40DyjdEkUO/Aj6nuT44p808sqlhHTA3Pu1zETywi9Ku6sdgDl3o1mya2kxdwrNOOrvvZu4PylpuN5yKckY88yB+l4H08/YFZpG0ivkP0hfoGYjsvaTK8Y8vIFqw= ; Message-ID: <20041119042829.16924.qmail@web53001.mail.yahoo.com> Received: from [155.69.5.235] by web53001.mail.yahoo.com via HTTP; Thu, 18 Nov 2004 20:28:29 PST Date: Thu, 18 Nov 2004 20:28:29 -0800 (PST) From: Gayathri Subject: Re: [manet] manet autoconf. To: Shubhranshu In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 hi !!! Please add me on to the list. I apologize if you have received more than one copy of this message Gayathri --- Shubhranshu wrote: > Hi all, > > MANET WG is developing proactive, reactive and > simplified multicast forwarding protocols. However, > there are other issues fundamental to ad hoc network > operation and deployment such as address > auto-configuration, DAD, gateway discovery and > selection for global prefix allocation and traffic > forwarding, etc. During 61st IETF meeting, Thomas > Clausen, Ruffino Simon, Charles Perkins, Ryuji > Wakikawa, Li Li, Emmanuel Baccelli, myself and few > others discussed about the importance and > need to standardize solutions for these > auto-configuration related issues within IETF. This > was > then presented by Simon in the MANET WG meeting. It > is understood that MANET WG may not be > the best place to solve these issues. > > There was some sort of consensus to move forward > with this work. Several independent publications and > > implementations are available. As suggested by Joe > Macker, Alex Zinin and others, we are going to set > up > a mailing list of those interested in these topics > and willing to contribute. There should be consensus > on > problem statement, possible approach, existing > solutions, milestones, etc. So, let me know if you > would > like to be part of the mailing list. We are planning > to go for BOF/bar-BOF at the next IETF meeting, > depending on the development on this mailing list. > > Regards, > Shubhranshu > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 02:09:21 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA19138 for ; Fri, 19 Nov 2004 02:09:21 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV2wJ-0004Dj-3H for manet-web-archive@ietf.org; Fri, 19 Nov 2004 02:12:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV2p9-0001Nr-6e; Fri, 19 Nov 2004 02:04:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV2nu-0000sN-E6 for manet@megatron.ietf.org; Fri, 19 Nov 2004 02:03:34 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14708 for ; Fri, 19 Nov 2004 02:03:33 -0500 (EST) Received: from bay14-f32.bay14.hotmail.com ([64.4.49.32] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV2qf-000471-9z for manet@ietf.org; Fri, 19 Nov 2004 02:06:27 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 18 Nov 2004 23:03:00 -0800 Message-ID: Received: from 130.158.83.80 by by14fd.bay14.hotmail.msn.com with HTTP; Fri, 19 Nov 2004 07:02:19 GMT X-Originating-IP: [130.158.83.80] X-Originating-Email: [tanakaatomu@hotmail.com] X-Sender: tanakaatomu@hotmail.com From: "tanaka atomu" To: manet@ietf.org Date: Fri, 19 Nov 2004 16:02:19 +0900 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp; format=flowed X-OriginalArrivalTime: 19 Nov 2004 07:03:00.0786 (UTC) FILETIME=[CE7FD920:01C4CE05] X-Spam-Score: 0.8 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: [manet] Is it reasonable to use static topology in MAC protocol design for MANET X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Hi, all: Recently i am working on the MAC protocol for MANETs. I have read some papers in this filed, and found that in the most of the simulations they carried out, the topology is static, that is, all the nodes will not move during the simulation. This may be contrast with the most critical future of MANET: All the nodes move frequently and rapidly. Thus i am wondering: 1)Is it reasonable to use the static toplogy in the simulation for MANETs when simulating MAC protocol? 2)If it is reasonable to use static toplogy for MAC protocols of MANETs, will there be some different results occuring between simulating the static topology and simulating the dynamic toplogy? That is, the results obtained when simulating static topology are different from that of dynamic topology. Is it reasonable? Thanks in advance. Tanaka _________________________________________________________________ $B3Z$7$$3(J8;z$G%3%3%mEA$o$k%a%C%;%s%8%c!<(B http://messenger.msn.co.jp/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 02:21:45 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27790 for ; Fri, 19 Nov 2004 02:21:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV38I-0004V4-IT for manet-web-archive@ietf.org; Fri, 19 Nov 2004 02:24:38 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV334-0006On-CQ; Fri, 19 Nov 2004 02:19:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV31e-0005hy-0h for manet@megatron.ietf.org; Fri, 19 Nov 2004 02:17:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26191 for ; Fri, 19 Nov 2004 02:17:45 -0500 (EST) Received: from web50601.mail.yahoo.com ([206.190.38.88]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CV34G-0004Of-9Z for manet@ietf.org; Fri, 19 Nov 2004 02:20:38 -0500 Received: (qmail 66676 invoked by uid 60001); 19 Nov 2004 07:17:04 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=qvW33VBbIikSf5c/RyzPpp4lVT+30SdXxOrfaXcmrPjMuD2HsC9E/hrReJZKKNmNW5i5QsC4JE0LKO1HZzp3va7WHnzPNymefKVW4UE/HCXNAtdBT9Pbi9KDip4c2oE/icrgPA2TWa3O8x6bi7D/1xJCHxhVqQ29QbSAFxMEe+c= ; Message-ID: <20041119071704.66673.qmail@web50601.mail.yahoo.com> Received: from [130.74.176.55] by web50601.mail.yahoo.com via HTTP; Thu, 18 Nov 2004 23:17:04 PST Date: Thu, 18 Nov 2004 23:17:04 -0800 (PST) From: Raja Sombhotla Subject: Re: [manet] manet autoconf. To: Shubhranshu , manet@ietf.org In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1498474898==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813 --===============1498474898== Content-Type: multipart/alternative; boundary="0-788609318-1100848624=:66402" --0-788609318-1100848624=:66402 Content-Type: text/plain; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id CAA26191 Content-Transfer-Encoding: quoted-printable Hi, Please add me in the list. =20 Regards, Raja. Shubhranshu wrote: Hi all, MANET WG is developing proactive, reactive and simplified multicast forwa= rding protocols. However,=20 there are other issues fundamental to ad hoc network operation and deploy= ment such as address=20 auto-configuration, DAD, gateway discovery and selection for global prefi= x allocation and traffic=20 forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon,= Charles Perkins, Ryuji=20 Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about= the importance and need to standardize solutions for these auto-configuration related issues= within IETF. This was=20 then presented by Simon in the MANET WG meeting. It is understood that MA= NET WG may not be the best place to solve these issues. There was some sort of consensus to move forward with this work. Several = independent publications and=20 implementations are available. As suggested by Joe Macker, Alex Zinin and= others, we are going to set up=20 a mailing list of those interested in these topics and willing to contrib= ute. There should be consensus on problem statement, possible approach, existing solutions, milestones, etc= . So, let me know if you would like to be part of the mailing list. We are planning to go for BOF/bar-BO= F at the next IETF meeting,=20 depending on the development on this mailing list. Regards, Shubhranshu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet =09 --------------------------------- Do you Yahoo!? Discover all that=92s new in My Yahoo! --0-788609318-1100848624=:66402 Content-Type: text/html; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id CAA26191 Content-Transfer-Encoding: quoted-printable
Hi,
Please add me in the list.
 
Regards,
Raja.

Shubhranshu <shubhranshu@samsung.com> wrote:
Hi all,

MANET WG is developing pro= active, reactive and simplified multicast forwarding protocols. However, =
there are other issues fundamental to ad hoc network operation and de= ployment such as address
auto-configuration, DAD, gateway discovery a= nd selection for global prefix allocation and traffic
forwarding, etc= . During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkin= s, Ryuji
Wakikawa, Li Li, Emmanuel Baccelli, myself and few others di= scussed about the importance and
need to standardize solutions for the= se auto-configuration related issues within IETF. This was
then prese= nted by Simon in the MANET WG meeting. It is understood that MANET WG may= not be
the best place to solve these issues.

There was some so= rt of consensus to move forward with this work. Several independent publi= cations and
implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up <= BR>a mailing list of those interested in these topics and willing to cont= ribute. There should be consensus on
problem statement, possible appro= ach, existing solutions, milestones, etc. So, let me know if you wouldlike to be part of the mailing list. We are planning to go for BOF/bar-B= OF at the next IETF meeting,
depending on the development on this mai= ling list.

Regards,
Shubhranshu


____________________= ___________________________
manet mailing list
manet@ietf.org
ht= tps://www1.ietf.org/mailman/listinfo/manet

Do you Yahoo!?
=20 Discover all that=92s new in My Yahoo! --0-788609318-1100848624=:66402-- --===============1498474898== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1498474898==-- From manet-bounces@ietf.org Fri Nov 19 04:20:29 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA08160 for ; Fri, 19 Nov 2004 04:20:29 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV4zF-0007BI-2X for manet-web-archive@ietf.org; Fri, 19 Nov 2004 04:23:25 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV4tR-00088q-UR; Fri, 19 Nov 2004 04:17:25 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV4rL-0007hr-Cb for manet@megatron.ietf.org; Fri, 19 Nov 2004 04:15:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07919 for ; Fri, 19 Nov 2004 04:15:13 -0500 (EST) Received: from swing.cefriel.it ([131.175.53.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV4u8-00076C-G7 for manet@ietf.org; Fri, 19 Nov 2004 04:18:09 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] Is it reasonable to use static topology in MAC protocoldesign for MANET Date: Fri, 19 Nov 2004 10:15:27 +0100 Message-ID: <9F1223587A755D47805AECAB7ECAF5D901843812@swing.cefriel.it> Thread-Topic: [manet] Is it reasonable to use static topology in MAC protocoldesign for MANET Thread-Index: AcTOBw4wKJRksEvqTBqjyJznZChnNwADvOIw From: "Giorgio Mulas" To: "tanaka atomu" , X-Spam-Score: 0.0 (/) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Content-Transfer-Encoding: quoted-printable Hi, 1) IMHO the answer is no, because "M" in MANET stands for Mobile.=20 2) Another important issue that should be studied in depth is choosing = realistic mobility models in simulations.... Giorgio =09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .=09 =09 =09 =09 Giorgio Mulas | Researcher=09 =09 CEFRIEL =A8C Politecnico di Milano ICT Center of Excellence For Research, Innovation, Education & = industrial Labs partnership=20 Via Fucini, 2 =A1=A4 20133 Milano (Italy) =09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . = . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .=09 [p. +39 02 23954 265 =A1=A4 f. +39 02 23954 465 =A1=A4 e. = giorgio.mulas@cefriel.it =A1=A4 w. http://www.cefriel.it/~mulas =09 -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf = Of tanaka atomu Sent: venerd=A8=AC 19 novembre 2004 8.02 To: manet@ietf.org Subject: [manet] Is it reasonable to use static topology in MAC = protocoldesign for MANET Hi, all: Recently i am working on the MAC protocol for MANETs. I have read = some=20 papers in this filed, and found that in the most of the simulations they = carried out, the topology is static, that is, all the nodes will not = move=20 during the simulation. This may be contrast with the most critical = future=20 of MANET: All the nodes move frequently and rapidly. Thus i am = wondering: 1)Is it reasonable to use the static toplogy in the simulation for = MANETs=20 when simulating MAC protocol? 2)If it is reasonable to use static toplogy for MAC protocols of MANETs, = will there be some different results occuring between simulating the = static=20 topology and simulating the dynamic toplogy? That is, the results = obtained=20 when simulating static topology are different from that of dynamic=20 topology. Is it reasonable? Thanks in advance. Tanaka _________________________________________________________________ =98S=A4=B7=A4=A4=BD}=CE=C4=D7=D6=A4=C7=A5=B3=A5=B3=A5=ED=81=BB=A4=EF=A4=EB= =A5=E1=A5=C3=A5=BB=A5=F3=A5=B8=A5=E3=A9` http://messenger.msn.co.jp/=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 04:42:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA10126 for ; Fri, 19 Nov 2004 04:42:59 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV5L0-0007ff-Jt for manet-web-archive@ietf.org; Fri, 19 Nov 2004 04:45:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV5Ea-0004fg-Cx; Fri, 19 Nov 2004 04:39:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV5CJ-0003r8-32 for manet@megatron.ietf.org; Fri, 19 Nov 2004 04:37:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09667 for ; Fri, 19 Nov 2004 04:36:52 -0500 (EST) Received: from bells.cs.ucl.ac.uk ([128.16.5.31]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CV5F5-0007Xu-5J for manet@ietf.org; Fri, 19 Nov 2004 04:39:48 -0500 Received: from mozzarella.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Fri, 19 Nov 2004 09:36:34 +0000 Message-ID: <419DBEBA.4060909@cs.ucl.ac.uk> Date: Fri, 19 Nov 2004 09:36:58 +0000 From: Mirco Musolesi User-Agent: Mozilla Thunderbird 0.6 (X11/20040519) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Giorgio Mulas Subject: Re: [manet] Is it reasonable to use static topology in MAC protocoldesign for MANET References: <9F1223587A755D47805AECAB7ECAF5D901843812@swing.cefriel.it> In-Reply-To: <9F1223587A755D47805AECAB7ECAF5D901843812@swing.cefriel.it> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: 7bit Cc: manet X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Content-Transfer-Encoding: 7bit Hi all, > 2) Another important issue that should be studied in depth is choosing realistic mobility models in simulations.... Probably you may be interested in our current work about the design of mobility models for mobile ad hoc networks research founded on social networks theory: http://www.cs.ucl.ac.uk/research/mobile/mobilitymodelsproject.html Best regards, Mirco -- Mirco Musolesi Department of Computer Science University College London Gower Street London WC1E 6BT United Kingdom Email: m.musolesi@cs.ucl.ac.uk Phone: +44 20 7679 3645 Fax: +44 20 7387 1397 Web: http://www.cs.ucl.ac.uk/staff/m.musolesi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 06:18:13 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17460 for ; Fri, 19 Nov 2004 06:18:13 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV6pC-0001D8-IH for manet-web-archive@ietf.org; Fri, 19 Nov 2004 06:21:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV6hP-0005nF-2B; Fri, 19 Nov 2004 06:13:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV6en-0004l9-3N for manet@megatron.ietf.org; Fri, 19 Nov 2004 06:10:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16778 for ; Fri, 19 Nov 2004 06:10:22 -0500 (EST) Received: from smtpproxy1.mitre.org ([192.160.51.76] helo=smtp-bedford.mitre.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV6hb-00012N-IK for manet@ietf.org; Fri, 19 Nov 2004 06:13:19 -0500 Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (8.11.6/8.11.6) with SMTP id iAJBANu11893 for ; Fri, 19 Nov 2004 06:10:23 -0500 Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-bedford.mitre.org (Postfix) with ESMTP id A3C17BF01 for ; Fri, 19 Nov 2004 06:10:23 -0500 (EST) Received: from MAILHUB2 (mailhub2.mitre.org [129.83.221.18]) by smtp-bedford.mitre.org (8.11.6/8.11.6) with ESMTP id iAJBAN211850; Fri, 19 Nov 2004 06:10:23 -0500 Message-Id: <200411191110.iAJBAN211850@smtp-bedford.mitre.org> Received: from unity-w-157-27.mitre.org (128.29.157.27) by mailhub2.mitre.org with SMTP id 6080665; Fri, 19 Nov 2004 06:10:18 -0500 From: "John Stine" To: "'tanaka atomu'" , Subject: RE: [manet] Is it reasonable to use static topology in MAC protocol design for MANET Date: Fri, 19 Nov 2004 06:10:13 -0500 Organization: The MITRE Corporation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-reply-to: Thread-index: AcTOBs0j6JRlaEf3T4us8saQNwoxdAAITqTw X-Spam-Score: 0.8 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 25620135586de10c627e3628c432b04a Content-Transfer-Encoding: 7bit Tanaka, It will depend on the MAC protocol and whether mobility will have an affect on its performance. If the MAC does not react to topology changes, (i.e. track state of the network for its operation), then what purpose does modeling mobility serve? It is likely to confound the performance of the routing protocol with that of the access protocol. Examples of MAC protocols that are sensitive to mobility are scheduling access mechanisms, access mechanisms that use clustering, and access mechanisms that track power requirements, interference constraints, directionality, etc. Examples of access mechanisms that are not sensitive to mobility are most random access techniques, e.g. aloha, csma, and 802.11. I personally much rather read a paper on a MAC protocol that uses static topologies to benchmark the MAC's performance according to node density and traffic load and then describes how mobility would affect that performance without regard to routing. I do not want to see results that allow the poor choice of a next hop destination by a routing protocol to affect the results. An example of an issue where mobility might be of interest in studying a MAC protocol is to see the effect of access delay, i.e. the routing protocol makes a good routing decision but the delay from the time that the packet was forwarded to the MAC and the packet was transmitted allowed the topology to change. To study the MAC protocols contribution to this problem might involve implementing a "perfect" router and parameterizing mobility to identify how much mobility causes the problem. In the end, the problem will be most sensitive to load and node density since this is what causes access delay. John -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of tanaka atomu Sent: Friday, November 19, 2004 2:02 AM To: manet@ietf.org Subject: [manet] Is it reasonable to use static topology in MAC protocol design for MANET Hi, all: Recently i am working on the MAC protocol for MANETs. I have read some papers in this filed, and found that in the most of the simulations they carried out, the topology is static, that is, all the nodes will not move during the simulation. This may be contrast with the most critical future of MANET: All the nodes move frequently and rapidly. Thus i am wondering: 1)Is it reasonable to use the static toplogy in the simulation for MANETs when simulating MAC protocol? 2)If it is reasonable to use static toplogy for MAC protocols of MANETs, will there be some different results occuring between simulating the static topology and simulating the dynamic toplogy? That is, the results obtained when simulating static topology are different from that of dynamic topology. Is it reasonable? Thanks in advance. Tanaka _________________________________________________________________ $B3Z$7$$3(J8;z$G%3%3%mEA$o$k%a%C%;%s%8%c!<(B http://messenger.msn.co.jp/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 06:41:31 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19503 for ; Fri, 19 Nov 2004 06:41:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV7Bk-0001fn-IO for manet-web-archive@ietf.org; Fri, 19 Nov 2004 06:44:29 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV73q-0002ru-Jx; Fri, 19 Nov 2004 06:36:18 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV6zy-0002Rf-NB for manet@megatron.ietf.org; Fri, 19 Nov 2004 06:32:19 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18592 for ; Fri, 19 Nov 2004 06:32:16 -0500 (EST) Received: from monet.knu.ac.kr ([155.230.29.236]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV72c-0001UG-LS for manet@ietf.org; Fri, 19 Nov 2004 06:35:13 -0500 Received: from monetwvf2cws5q ([155.230.29.237]) by monet.knu.ac.kr (8.12.9/8.12.9) with ESMTP id iAJBW4kD004954; Fri, 19 Nov 2004 20:32:04 +0900 From: =?ks_c_5601-1987?B?waTIq8G+?= To: "'Shubhranshu'" Subject: RE: [manet] manet autoconf. Date: Fri, 19 Nov 2004 20:31:57 +0900 Message-ID: <000001c4ce2b$63c1d720$ed1de69b@monetwvf2cws5q> MIME-Version: 1.0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: 7bit Hi Shubhranshu, Please add me to the mailing list, too. Thanks. -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Shubhranshu Sent: Thursday, November 18, 2004 10:00 PM To: manet@ietf.org Subject: [manet] manet autoconf. Hi all, MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, there are other issues fundamental to ad hoc network operation and deployment such as address auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and need to standardize solutions for these auto-configuration related issues within IETF. This was then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be the best place to solve these issues. There was some sort of consensus to move forward with this work. Several independent publications and implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up a mailing list of those interested in these topics and willing to contribute. There should be consensus on problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, depending on the development on this mailing list. Regards, Shubhranshu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 06:55:45 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20892 for ; Fri, 19 Nov 2004 06:55:45 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV7PW-0001yh-MJ for manet-web-archive@ietf.org; Fri, 19 Nov 2004 06:58:43 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV7HD-0005i8-W2; Fri, 19 Nov 2004 06:50:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV7Cl-0004Tz-01 for manet@megatron.ietf.org; Fri, 19 Nov 2004 06:45:31 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19866 for ; Fri, 19 Nov 2004 06:45:28 -0500 (EST) Received: from outbound.kcl.ac.uk ([137.73.2.214]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV7FP-0001je-FT for manet@ietf.org; Fri, 19 Nov 2004 06:48:26 -0500 Received: from smtpredi.kcl.ac.uk ([137.73.66.123] helo=redwood) by outbound.kcl.ac.uk outbound with esmtp (TLSv1:DHE-RSA-AES256-SHA:256) id 1CV7Ak-0001rP-TJ for manet@ietf.org; Fri, 19 Nov 2004 11:43:26 +0000 Received: from [137.73.11.140] (helo=ronandesktop) by redwood smtpred with esmtp id 1CV7AV-0003I9-Qr for manet@ietf.org; Fri, 19 Nov 2004 11:43:12 +0000 From: "ronan de renesse" To: Subject: RE: [manet] Is it reasonable to use static topology in MAC protocoldesign for MANET Date: Fri, 19 Nov 2004 11:43:12 -0000 Message-ID: <001601c4ce2c$f2e281b0$6564a8c0@ronandesktop> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-KCLSpamScore: 0 X-KCLRealSpamScore: 0.0 X-KCLZStatus: 0 X-KCL-MailScanner: Found to be clean X-MailScanner-From: ronan.de_renesse@kcl.ac.uk X-Spam-Score: 0.0 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c Content-Transfer-Encoding: 7bit Hi, Maybe this paper could help you: http://www.tkn.tu-berlin.de/tkn/publications/papers/carlson_paper1.pdf It's about a MAC reservation protocol called DARE taking mobility into account in MANETs. Regards, Ronan -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of tanaka atomu Sent: 19 November 2004 07:02 To: manet@ietf.org Subject: [manet] Is it reasonable to use static topology in MAC protocoldesign for MANET Hi, all: Recently i am working on the MAC protocol for MANETs. I have read some papers in this filed, and found that in the most of the simulations they carried out, the topology is static, that is, all the nodes will not move during the simulation. This may be contrast with the most critical future of MANET: All the nodes move frequently and rapidly. Thus i am wondering: 1)Is it reasonable to use the static toplogy in the simulation for MANETs when simulating MAC protocol? 2)If it is reasonable to use static toplogy for MAC protocols of MANETs, will there be some different results occuring between simulating the static topology and simulating the dynamic toplogy? That is, the results obtained when simulating static topology are different from that of dynamic topology. Is it reasonable? Thanks in advance. Tanaka _________________________________________________________________ $B3Z$7$$3(J8;z$G%3%3%mEA$o$k%a%C%;%s%8%c!<(B http://messenger.msn.co.jp/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 07:10:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22179 for ; Fri, 19 Nov 2004 07:10:59 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV7eH-0002Jt-MO for manet-web-archive@ietf.org; Fri, 19 Nov 2004 07:13:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV7Up-0000Rt-8U; Fri, 19 Nov 2004 07:04:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV7Rt-0008B5-RS for manet@megatron.ietf.org; Fri, 19 Nov 2004 07:01:10 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21400 for ; Fri, 19 Nov 2004 07:01:06 -0500 (EST) Message-Id: <200411191201.HAA21400@ietf.org> Received: from pop.gmx.net ([213.165.64.20] helo=mail.gmx.net) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CV7UY-00025q-GZ for manet@ietf.org; Fri, 19 Nov 2004 07:04:04 -0500 Received: (qmail 13225 invoked by uid 65534); 19 Nov 2004 12:00:26 -0000 Received: from unknown (EHLO NicoBare) (192.166.62.145) by mail.gmx.net (mp009) with SMTP; 19 Nov 2004 13:00:26 +0100 X-Authenticated: #15262315 From: "Nico Bayer" To: "'Shubhranshu'" , Subject: AW: [manet] manet autoconf. Date: Fri, 19 Nov 2004 13:00:41 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTNcEMod4GjJroVSqmL1WWSPV4cGAAvwrBQ X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Content-Transfer-Encoding: quoted-printable Hi Shubhranshu, Please add me to the mailing list, too. Thank you in advance. Regards, Nico -----Urspr=FCngliche Nachricht----- Von: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] Im Auftrag = von Shubhranshu Gesendet: Donnerstag, 18. November 2004 14:00 An: manet@ietf.org Betreff: [manet] manet autoconf. Hi all, MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However,=20 there are other issues fundamental to ad hoc network operation and deployment such as address=20 auto-configuration, DAD, gateway discovery and selection for global = prefix allocation and traffic=20 forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino = Simon, Charles Perkins, Ryuji=20 Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed = about the importance and need to standardize solutions for these auto-configuration related = issues within IETF. This was=20 then presented by Simon in the MANET WG meeting. It is understood that = MANET WG may not be the best place to solve these issues. There was some sort of consensus to move forward with this work. Several independent publications and=20 implementations are available. As suggested by Joe Macker, Alex Zinin = and others, we are going to set up=20 a mailing list of those interested in these topics and willing to contribute. There should be consensus on problem statement, possible approach, existing solutions, milestones, = etc. So, let me know if you would like to be part of the mailing list. We are planning to go for = BOF/bar-BOF at the next IETF meeting,=20 depending on the development on this mailing list. Regards, Shubhranshu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 08:26:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29767 for ; Fri, 19 Nov 2004 08:26:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV8pZ-0004Hh-5Z for manet-web-archive@ietf.org; Fri, 19 Nov 2004 08:29:41 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV8kx-0000og-MZ; Fri, 19 Nov 2004 08:24:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV8c6-0007iM-Bl for manet@megatron.ietf.org; Fri, 19 Nov 2004 08:15:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28886 for ; Fri, 19 Nov 2004 08:15:45 -0500 (EST) Received: from concorde.inria.fr ([192.93.2.39]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV8ev-00042l-Q2 for manet@ietf.org; Fri, 19 Nov 2004 08:18:42 -0500 Received: from inria.fr (ruspina.inria.fr [128.93.17.52]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id iAJDFDHY015756; Fri, 19 Nov 2004 14:15:14 +0100 Message-ID: <419DF1E1.4110C51@inria.fr> Date: Fri, 19 Nov 2004 14:15:13 +0100 From: Anis LAOUITI X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: Shubhranshu Subject: Re: [manet] manet autoconf. References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Miltered: at concorde with ID 419DF1E1.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Content-Transfer-Encoding: 7bit Hi Shubhranshu, I'm interested in this topic also, please add my address to this new list Anis Shubhranshu wrote: > Hi all, > > MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, > there are other issues fundamental to ad hoc network operation and deployment such as address > auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic > forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji > Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and > need to standardize solutions for these auto-configuration related issues within IETF. This was > then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be > the best place to solve these issues. > > There was some sort of consensus to move forward with this work. Several independent publications and > implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up > a mailing list of those interested in these topics and willing to contribute. There should be consensus on > problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would > like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, > depending on the development on this mailing list. > > Regards, > Shubhranshu > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 08:58:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02766 for ; Fri, 19 Nov 2004 08:58:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV9KH-00050h-ST for manet-web-archive@ietf.org; Fri, 19 Nov 2004 09:01:26 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV9DJ-0007YR-Fs; Fri, 19 Nov 2004 08:54:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV97h-0005tg-U3 for manet@megatron.ietf.org; Fri, 19 Nov 2004 08:48:26 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01967 for ; Fri, 19 Nov 2004 08:48:24 -0500 (EST) Received: from tx5.mail.ox.ac.uk ([163.1.2.169]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV9AX-0004lJ-31 for manet@ietf.org; Fri, 19 Nov 2004 08:51:21 -0500 Received: from scan5.mail.ox.ac.uk ([163.1.2.177] helo=localhost) by tx5.mail.ox.ac.uk with esmtp (Exim 4.42) id 1CV977-0006Zd-Hg for manet@ietf.org; Fri, 19 Nov 2004 13:47:49 +0000 Received: from rx5.mail.ox.ac.uk ([163.1.2.168]) by localhost (scan5.mail.ox.ac.uk [163.1.2.177]) (amavisd-new, port 25) with ESMTP id 25261-01 for ; Fri, 19 Nov 2004 13:47:49 +0000 (GMT) Received: from smtp0.herald.ox.ac.uk ([163.1.0.246]) by rx5.mail.ox.ac.uk with esmtp (Exim 4.42) id 1CV977-0006ZZ-HC for manet@ietf.org; Fri, 19 Nov 2004 13:47:49 +0000 Received: from webmail223.herald.ox.ac.uk ([163.1.0.223]) by smtp0.herald.ox.ac.uk with esmtp (Exim 3.35 #1) id 1CV977-0000VO-3y for manet@ietf.org; Fri, 19 Nov 2004 13:47:49 +0000 Received: by webmail223.herald.ox.ac.uk (Postfix, from userid 101) id 5D31C2A0EC; Fri, 19 Nov 2004 13:47:48 +0000 (GMT) Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: binary MIME-Version: 1.0 X-Mailer: MIME-tools 5.411 (Entity 5.404) From: Alexander Casson Date: Fri, 19 Nov 2004 13:47:48 +0000 (GMT) To: manet@ietf.org Message-Id: <20041119134748.5D31C2A0EC@webmail223.herald.ox.ac.uk> X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Content-Transfer-Encoding: binary Subject: [manet] Link cluster topologies with a wired backbone X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Content-Transfer-Encoding: binary Hi all. I'm looking at ad hoc networks in hospital environments. We need to have a server to store all of the data as we can't just have it floating round where it could potentially get lost. The natural structure that suggests itself is a cluster on with the central sever in the middle, such as I've tried to show below: Cluster | | | |---------Cluster | | Server-----Cluster | | | | | Cluster Doing some reading this is somewhat similar the "Near Term Digital Radio Network" (NTDR) structure. In this, however, the clusterheads are chosen dynamically to be the optimum nodes available. These then up their transmission power to form the inter-cluster back bone. In the hospital, however, a limited wired network is already present. What would be good is to have fixed terminals on the end of this and then ad hoc out beyond that. Has anybody looked in to such a situation and could point me in the direction of some literature describing it? Thanks in advance, Alex ~~~~~~~~~~~~~~~~~~~~~~ Alex Casson Lincoln College _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 09:49:15 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07214 for ; Fri, 19 Nov 2004 09:49:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVA7R-0006C8-PI for manet-web-archive@ietf.org; Fri, 19 Nov 2004 09:52:13 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV9x0-0002JB-3e; Fri, 19 Nov 2004 09:41:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CV9qt-000163-Dm for manet@megatron.ietf.org; Fri, 19 Nov 2004 09:35:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05846 for ; Fri, 19 Nov 2004 09:35:05 -0500 (EST) Received: from satchmo.cs.engr.uky.edu ([128.163.146.23]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV9tj-0005qV-Kc for manet@ietf.org; Fri, 19 Nov 2004 09:38:03 -0500 Received: from cs.uky.edu (lily.cs.engr.uky.edu [128.163.146.76]) by satchmo.cs.engr.uky.edu (8.12.9/8.12.9) with ESMTP id iAJEYwwS004246 for ; Fri, 19 Nov 2004 09:34:58 -0500 (EST) Received: from localhost (venkata@localhost) by cs.uky.edu (8.12.9/8.12.9/Submit) with ESMTP id iAJEYwnw020198 for ; Fri, 19 Nov 2004 09:34:58 -0500 Date: Fri, 19 Nov 2004 09:34:58 -0500 (EST) From: "Venkata C. Giruka" To: manet@ietf.org Subject: Re: [manet] manet autoconf. In-Reply-To: <200411191202.iAJC1xwS028620@satchmo.cs.engr.uky.edu> Message-ID: References: <200411191202.iAJC1xwS028620@satchmo.cs.engr.uky.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-CSUKY-MailScanner-Information: Contact for more information X-CSUKY-MailScanner: Found to be clean X-MailScanner-From: venkata@cs.uky.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Hi, Please add me to the list. Thanks -Venkata > > Hi all, > > > > MANET WG is developing proactive, reactive and > > simplified multicast forwarding protocols. However, > > there are other issues fundamental to ad hoc network > > operation and deployment such as address > > auto-configuration, DAD, gateway discovery and > > selection for global prefix allocation and traffic > > forwarding, etc. During 61st IETF meeting, Thomas > > Clausen, Ruffino Simon, Charles Perkins, Ryuji > > Wakikawa, Li Li, Emmanuel Baccelli, myself and few > > others discussed about the importance and > > need to standardize solutions for these > > auto-configuration related issues within IETF. This > > was > > then presented by Simon in the MANET WG meeting. It > > is understood that MANET WG may not be > > the best place to solve these issues. > > > > There was some sort of consensus to move forward > > with this work. Several independent publications and > > > > implementations are available. As suggested by Joe > > Macker, Alex Zinin and others, we are going to set > > up > > a mailing list of those interested in these topics > > and willing to contribute. There should be consensus > > on > > problem statement, possible approach, existing > > solutions, milestones, etc. So, let me know if you > > would > > like to be part of the mailing list. We are planning > > to go for BOF/bar-BOF at the next IETF meeting, > > depending on the development on this mailing list. > > > > Regards, > > Shubhranshu > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 10:29:33 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12040 for ; Fri, 19 Nov 2004 10:29:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVAkS-00077J-1X for manet-web-archive@ietf.org; Fri, 19 Nov 2004 10:32:32 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVAVD-00069Q-Kx; Fri, 19 Nov 2004 10:16:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVATA-0005QW-6U for manet@megatron.ietf.org; Fri, 19 Nov 2004 10:14:40 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10105 for ; Fri, 19 Nov 2004 10:14:38 -0500 (EST) From: haas@ece.cornell.edu Received: from gehenna.ece.cornell.edu ([128.84.95.235]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVAW0-0006m2-NZ for manet@ietf.org; Fri, 19 Nov 2004 10:17:37 -0500 Received: from zeno.ece.cornell.edu (zeno.ece.cornell.edu [128.84.81.136]) by gehenna.ece.cornell.edu (Postfix) with ESMTP id AFA591E801D; Fri, 19 Nov 2004 10:14:38 -0500 (EST) Date: Fri, 19 Nov 2004 10:17:27 -0500 (EST) To: manet@ietf.org Subject: Re: [manet] JiST/SWANS GUI? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.3 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Cc: Zygmunt Haas , rimon@acm.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c > Date: Sun, 14 Nov 2004 23:10:44 +0100 > From: Grzegorz Jablonski > To: manet@ietf.org > Subject: Re: [manet] JiST/SWANS GUI? > > I've used SWANS to simulate some location-aware algorithms. There's no > GUI as far as I know, but you can write your own - it shouldn't be > difficult if you have some java skills. Agreed. > Anyway, be careful, there's some bugs in SWANS's implementation of > 802.11 MAC layer - it would deadlock for me sometimes under high > network load. Apart from this, it's a great simulator and I can't wait > until it gets better. As is the case with the vast majority of 802.11 implementations, the SWANS implementation is incomplete. 802.11 is a very complex protocol. Currently, the broadcast function works just fine, and that's what we use thus far in our research work. Unicasts (i.e. RTS/CTS and backoff) have been partially implemented, but not sufficiently tested. We, too, have noticed the "lock-up" problem under heavy load. The state machine probably has a minor bug. The current implementation also, like ns2 and GloMoSim (to the best of our knowledge), does not provide support for the base station and associated client functionality defined in the specification. We will continue building components based on our research needs, and are happy to release them to the community. And, we would be happy to serve as an exchange point for contributions from others. Feel free to send in patches or new components. Rimon Barr and Zygmunt Haas. ===--======= ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- 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(at)ece(dot)cornell(dot)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 manet-bounces@ietf.org Fri Nov 19 10:53:35 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14272 for ; Fri, 19 Nov 2004 10:53:35 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVB7i-0007fJ-Ka for manet-web-archive@ietf.org; Fri, 19 Nov 2004 10:56:34 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVAwx-0005Sy-QI; Fri, 19 Nov 2004 10:45:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVArM-0004AX-Rr for manet@megatron.ietf.org; Fri, 19 Nov 2004 10:39:41 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13056 for ; Fri, 19 Nov 2004 10:39:38 -0500 (EST) Received: from morse.colorado.edu ([198.11.21.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVAuD-0007LS-Dh for manet@ietf.org; Fri, 19 Nov 2004 10:42:38 -0500 Received: from morse.Colorado.EDU (localhost [127.0.0.1]) by morse.Colorado.EDU (8.12.10/8.12.10/UnixOps+Hesiod) with ESMTP id iAJFdZ7G016606; Fri, 19 Nov 2004 08:39:35 -0700 (MST) Received: from localhost (timxb@localhost) by morse.Colorado.EDU (8.12.10/8.12.8/Submit) with ESMTP id iAJFdZud016603; Fri, 19 Nov 2004 08:39:35 -0700 (MST) Date: Fri, 19 Nov 2004 08:39:35 -0700 (MST) From: Brown Tim To: John Stine Subject: RE: [manet] Is it reasonable to use static topology in MAC protocol design for MANET In-Reply-To: <200411191110.iAJBAN211850@smtp-bedford.mitre.org> Message-ID: References: <200411191110.iAJBAN211850@smtp-bedford.mitre.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-2022-jp Content-Transfer-Encoding: QUOTED-PRINTABLE X-Spam-Score: 0.0 (/) X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 Content-Transfer-Encoding: QUOTED-PRINTABLE I would go a bit further than John. It is more than whether or not the MAC protocol is affected by mobility. It also depends on whether the MAC protocol is trying to solve mobility problems. For instance, a MAC protocol with an embedded lightweight HELLO mechanism to keep track of neighbors for the higher layers is much more interesting in a mobile environment than a static environment. Many 802.11 implementations have adaptive ACK timeouts to solve the problem that nodes can move further or closer. And, of course, every radio is sensitive to doppler shifts at high enough speed. Some mechanisms may try to treat these issues specifically and so testing in a mobile environment is imperative. =09Regards, =09=09Tim On Fri, 19 Nov 2004, John Stine wrote: > Tanaka, > > =09It will depend on the MAC protocol and whether mobility will have an > affect on its performance. If the MAC does not react to topology changes= , > (i.e. track state of the network for its operation), then what purpose do= es > modeling mobility serve? It is likely to confound the performance of the > routing protocol with that of the access protocol. Examples of MAC > protocols that are sensitive to mobility are scheduling access mechanisms= , > access mechanisms that use clustering, and access mechanisms that track > power requirements, interference constraints, directionality, etc. Examp= les > of access mechanisms that are not sensitive to mobility are most random > access techniques, e.g. aloha, csma, and 802.11. I personally much rathe= r > read a paper on a MAC protocol that uses static topologies to benchmark t= he > MAC's performance according to node density and traffic load and then > describes how mobility would affect that performance without regard to > routing. I do not want to see results that allow the poor choice of a ne= xt > hop destination by a routing protocol to affect the results. An example = of > an issue where mobility might be of interest in studying a MAC protocol i= s > to see the effect of access delay, i.e. the routing protocol makes a good > routing decision but the delay from the time that the packet was forwarde= d > to the MAC and the packet was transmitted allowed the topology to change. > To study the MAC protocols contribution to this problem might involve > implementing a "perfect" router and parameterizing mobility to identify h= ow > much mobility causes the problem. In the end, the problem will be most > sensitive to load and node density since this is what causes access delay= =2E > > John > > > -----Original Message----- > From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of > tanaka atomu > Sent: Friday, November 19, 2004 2:02 AM > To: manet@ietf.org > Subject: [manet] Is it reasonable to use static topology in MAC protocol > design for MANET > > Hi, all: > > Recently i am working on the MAC protocol for MANETs. I have read some > papers in this filed, and found that in the most of the simulations they > carried out, the topology is static, that is, all the nodes will not move > during the simulation. This may be contrast with the most critical future > of MANET: All the nodes move frequently and rapidly. Thus i am wondering: > > 1)Is it reasonable to use the static toplogy in the simulation for MANETs > when simulating MAC protocol? > > 2)If it is reasonable to use static toplogy for MAC protocols of MANETs, > will there be some different results occuring between simulating the stat= ic > topology and simulating the dynamic toplogy? That is, the results obtain= ed > when simulating static topology are different from that of dynamic > topology. Is it reasonable? > > Thanks in advance. > > Tanaka > > _________________________________________________________________ > =B3=DA=A4=B7=A4=A4=B3=A8=CA=B8=BB=FA=A4=C7=A5=B3=A5=B3=A5=ED=C5=C1=A4=EF= =A4=EB=A5=E1=A5=C3=A5=BB=A5=F3=A5=B8=A5=E3=A1=BC http://messenger.msn.co.jp= / > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > Timothy X Brown Interdisciplinary Telecommunications Electrical and Computer Engineering ECOT 256 Campus Box 530 University of Colorado Boulder, CO 80309 Tel: (303) 492-1630 Fax: (303) 492-1112 http://ece.colorado.edu/~timxb _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 11:07:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15788 for ; Fri, 19 Nov 2004 11:07:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVBLJ-00082W-Hu for manet-web-archive@ietf.org; Fri, 19 Nov 2004 11:10:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVBCk-00015O-5I; Fri, 19 Nov 2004 11:01:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVB57-0007Cj-0Q for manet@megatron.ietf.org; Fri, 19 Nov 2004 10:53:53 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14332 for ; Fri, 19 Nov 2004 10:53:50 -0500 (EST) Received: from mail.crc.ca ([142.92.39.129]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVB7w-0007e4-4C for manet@ietf.org; Fri, 19 Nov 2004 10:56:50 -0500 Received: from ROGER (roger.dgrc.crc.ca [142.92.38.14]) by mail.crc.ca (8.12.11/8.12.11) with SMTP id iAJGq1A7032343; Fri, 19 Nov 2004 11:52:01 -0500 Message-Id: <200411191652.iAJGq1A7032343@mail.crc.ca> X-Sender: lli@mail.crc.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 19 Nov 2004 11:03:49 -0500 To: Ian Chakeres , "Charles E. Perkins" , Thomas Heide Clausen , "'manet'" , Justin Dean From: Li Li Subject: Re: [manet] Path Accumulation in DyMO In-Reply-To: <1CC461A4-39A1-11D9-830D-000A95C1BC0A@cs.ucsb.edu> References: <8497-SnapperMsgD302CB11BDC24FFA@192.168.0.192> <8497-SnapperMsgD302CB11BDC24FFA@192.168.0.192> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Scanned-By: MIMEDefang 2.44 X-Spam-Score: 1.9 (+) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 At 12:33 PM 11/18/2004 -0800, Ian Chakeres wrote: >First I want to issue a query to the list. Does anyone think we should >use path accumulation to alleviate creating a reverse route to the >source during RREQ propagation? I'd like to get consensus that this is >a non-issue. > >Given that we don't perform path accumulation for the reason of not >storing the reverse route during RREQ propagation, I think there are a >large number of possibilities for disseminating additional information. >For example, we could include each node on the path, and their sequence >number. Correct me if I'm wrong. I think this is an option doing the path accumulation, to know the reverse path. As Justin pointed out in his earlier email that we may use the RREQ and RRES to carry the path instead of storing the state. RRES can pop off the used address to cut short the header along the way. Carrying the path may not bring much complexity in implementation but would result in a longer header to take more bandwidth. Don't know if someone has some data to compare the bandwidth taken by the longer header vs. taken by the messages needed to get a reverse path? I somehow favor carrying the path. Used it in other protocols before and felt it very handy. I think path accumulation is very valuable to be included in the protocol. Thanks, li li _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 11:21:58 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17287 for ; Fri, 19 Nov 2004 11:21:58 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVBZB-0008NE-EB for manet-web-archive@ietf.org; Fri, 19 Nov 2004 11:24:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVBOI-0004GN-2x; Fri, 19 Nov 2004 11:13:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVBNL-0003wT-15 for manet@megatron.ietf.org; Fri, 19 Nov 2004 11:12:43 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16501 for ; Fri, 19 Nov 2004 11:12:40 -0500 (EST) Received: from mail.ece.gatech.edu ([199.77.227.200]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVBQA-0008BK-QT for manet@ietf.org; Fri, 19 Nov 2004 11:15:40 -0500 Received: from localhost (bigzilla.ece.gatech.edu [130.207.225.103]) by mail.ece.gatech.edu (8.12.10/8.12.10) with ESMTP id iAJGCdg8013159 for ; Fri, 19 Nov 2004 11:12:39 -0500 (EST) Received: from mail.ece.gatech.edu ([199.77.227.200]) by localhost (bigzilla.ece.gatech.edu [130.207.225.103]) (amavisd-new, port 10024) with LMTP id 09903-05 for ; Fri, 19 Nov 2004 11:12:36 -0500 (EST) Received: from ece.gatech.edu (pascal.ece.gatech.edu [199.77.145.86]) (authenticated bits=0) by mail.ece.gatech.edu (8.12.10/8.12.10) with ESMTP id iAJGCYid013153 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Fri, 19 Nov 2004 11:12:35 -0500 (EST) Message-ID: <419E247B.7020505@ece.gatech.edu> Date: Fri, 19 Nov 2004 11:51:07 -0500 From: Yujie Zhu User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at ece.gatech.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit Subject: [manet] A graph growth problem X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 7bit Hi all: I'm looking into a graph growth problem described as follows: Consider a large scale sensor network with nodes uniformly distributed in a finite field. A shortest path tree is generated from sink located at the center of the field to all other sensor nodes. Is there any analytical formula that characterizes the number of nodes at j hops from the sink on the shortest path tree(defined as Q(j))? For infinite random graph and k-ary trees, Q(j) increases exponentially, but I'm not sure if this is true for finite networks with uniform node distribution. From a simple simulation it seems that Q(j) increases in a superlinear fashion within a certain hops, then decrease dramatically. Does anybody aware of any existing solution to this problem? Thanks in advance, Yujie Zhu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 13:08:03 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27472 for ; Fri, 19 Nov 2004 13:08:03 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVDDs-0002fF-JN for manet-web-archive@ietf.org; Fri, 19 Nov 2004 13:11:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVCwE-0007oy-0X; Fri, 19 Nov 2004 12:52:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVCuJ-00072D-PM for manet@megatron.ietf.org; Fri, 19 Nov 2004 12:50:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26196 for ; Fri, 19 Nov 2004 12:50:48 -0500 (EST) Received: from smtp.andrew.cmu.edu ([128.2.10.83]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVCxB-0002J9-QF for manet@ietf.org; Fri, 19 Nov 2004 12:53:50 -0500 Received: from DMALTZ.WV.CS.cmu.edu (DMALTZ.WV.CS.cmu.edu [128.237.237.32]) (user=dmaltz mech=KERBEROS_V4 (0 bits)) by smtp.andrew.cmu.edu (8.12.10/8.12.10) with ESMTP id iAJHomWJ030558; Fri, 19 Nov 2004 12:50:49 -0500 Date: Fri, 19 Nov 2004 12:52:03 -0500 From: Dave Maltz To: Grzegorz Jablonski , manet Subject: Re: [manet] broadcasting in 802.11 Message-ID: <56955487.1100868723@DMALTZ.WV.CS.cmu.edu> In-Reply-To: <003a01c4cdc2$231d2a80$659ca851@saddamlennon> References: <4198E0E9.7070606@telecom.lth.se> <003a01c4cdc2$231d2a80$659ca851@saddamlennon> Originator-Info: login-token=Mulberry:01822dh1fa/vM58uz+Pu0U9kbKFLN52Coh0Ar8890QEA==; token_authority=postmaster@andrew.cmu.edu X-Mailer: Mulberry/3.0.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: 7bit --On Thursday, November 18, 2004 11:58 PM +0100 Grzegorz Jablonski wrote: >> Is there any suggestions for extending 802.11 so that broadcast messages >> become "reliable"? > I think this is technically impossible. > Sender can wait for an acknowledgement from all it neighbours, but how > will it know taht the information he's got about neighbours is correct? I > may be wrong, but as far as I know wireless node may only have > approximated and usually slightly outdated information about his > neighbours. Therefore you can never make sure that all neighbours have > received your message. The approximated information can as well be enough > for your needs. While not perfect and fairly expensive in overhead, the IMEP protocol will approximate reliable broadcast for you. It's implemented in the Monarch extensions to ns-2 (and I recall Scott and/or Joe did an implementation as well). There's also a trick that can help with reliability, if you're willing to keep your nodes in promiscuous listen mode and use a header flag or some convention to indicated broadcast packets. The transmitting node must know the MAC address of any single neighbor (which it might learn via promiscuous listening). The transmitting node then unicasts the "broadcast" packet to the neighbor, causing 802.11 to cover the packet with an RTS/CTS exchange. If the other nodes are in promiscuous listen, they will overhear the packet, see the flag or convention, realize the packet is really intended as a broadcast, and pass it up the stack. Cheers, -dam _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 13:16:25 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28267 for ; Fri, 19 Nov 2004 13:16:25 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVDLy-0002rY-O0 for manet-web-archive@ietf.org; Fri, 19 Nov 2004 13:19:26 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVDGS-0004AE-TK; Fri, 19 Nov 2004 13:13:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVDDK-0003O1-KR for manet@megatron.ietf.org; Fri, 19 Nov 2004 13:10:30 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27825 for ; Fri, 19 Nov 2004 13:10:27 -0500 (EST) Received: from wizard.cse.nd.edu ([129.74.152.2] helo=cse.nd.edu) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVDGC-0002jy-6B for manet@ietf.org; Fri, 19 Nov 2004 13:13:28 -0500 Received: from cse.nd.edu (cse.nd.edu [129.74.152.2]) by cse.nd.edu (8.12.10/8.12.10) with ESMTP id iAJIAOTX006372 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 19 Nov 2004 13:10:25 -0500 (EST) Received: (from surendar@localhost) by cse.nd.edu (8.12.10/8.12.10/Submit) id iAJIAOHm006370 for manet@ietf.org; Fri, 19 Nov 2004 13:10:24 -0500 (EST) Date: Fri, 19 Nov 2004 13:10:24 -0500 (EST) From: Surendar Chandra Message-Id: <200411191810.iAJIAOHm006370@cse.nd.edu> To: manet@ietf.org X-GRUMPY-MTA-Date: Fri, 19 Nov 2004 13:10:26 -0500 (EST) X-CSE-Virus-Scan: engine v4.3.20; dat v4409 X-Scanned-By: MIMEDefang 2.40 X-Spam-Score: 0.0 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Subject: [manet] Participation: Trusted Internet Workshop (TIW 04) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8 We apologize if you received multiple copies of this Call for Participation. Please feel free to distribute it to those who might be interested. ****************************************************************** CALL FOR PARTICIPATION Third Annual Trusted Internet Workshop (TIW) 2004 Dec. 22, 2004, Bangalore, India Held in conjunction with Intl. Conf. on High-Performance Computing (HiPC) 2004 Preliminary Technical Program URLs: http://www.ee.iastate.edu/~gmani/tiw-2004 http://www.hipc.org Note: Selected Papers will appear in a special issue of the Journal of High Speed Networks. ****************************************************************** Welcome and Keynote Talk: (9:00 - 9:45 am) Keynote Speaker: Dr. Biswanath Mukherjee, University of California, Davis Title: TBA ****************************************************************** SESSION 1: Adhoc Networks Performance and Security (9:45 - 10:40 am) ****************************************************************** RTCP: An Adaptive Rate Based TCP for Ad hoc Wireless Networks B. Venkata Ramana, B. S. Manoj, and C. Siva Ram Murthy (IIT Madras, India) A Novel Architecture for Secure Group Communication in Wireless Ad-hoc Networks with Application-Level Multicast R. Mukkamala and M. Moharrum (Old Dominion University, USA), and M. Eltoweissy (Virginia Tech, USA) Key Management and Delayed Verification for Ad Hoc Networks Manel Guerrero Zapata (Universitat Pompeu Fabra, Spain) Reliable Multicast Transport in Ad hoc Networks Feng Mei-yu, Cheng Sheng, Zhang Xu, and Ding Wei (Beijing Univ. of Posts and Telecom, Beijing, China) (SHORT paper) ****************************************************************** Session 2: Wireless Sensor Networks Security (11 am - 11:50 pm) ****************************************************************** Distributed Cluster Monitoring in Wireless Sensor Networks for Reliable Data Delivery Uttara Korad and Krishna M. Sivalingam (University of Maryland, Baltimore County, USA) Using Routing Data for Information Authentication in Sensor Networks Vijay Bhuse, Ajay Gupta, Mark Terwilliger, Zijiang Yang, and Zill-E-Huma Kamal (Western Michigan University, USA) Elliptic Curve Cryptography in Wireless Protocol Junaid Majeed (Hamdard University, Karachi, Pakistan) ****************************************************************** Session 3: Networks and Architecture Security (12 - 1 pm) ****************************************************************** Dynamic Cuttings: Packet Classification with Network Traffic Statistics Yaxuan Qi, and Jun Li (Tsinghua University, Beijing, China) SPEE: A Secure Program Execution Environment Tool Using Static and Dynamic Code Verification Olga Gelbart, Bhagirath Narahari, and Rahul Simha (The George Washington University, USA) SCIT-DNS: Critical Infrastructure Protection through Secure DNS Server Dynamic Updates, Yih Huang, David Arsenault, and Arun Sood (George Mason University, USA) Virtualized Credential Management in Inter-domain Grid System Kai Mosebach, Lech Damian Alves, and Anirban Chakrabarti (Infosys Technologies Ltd., Bangalore, India) (SHORT paper) On Encryption by Microprocessors Vipul Goyal (OSP Global, Mumbai, India) (SHORT paper) ****************************************************************** _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 13:51:55 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01414 for ; Fri, 19 Nov 2004 13:51:55 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVDuI-0003du-94 for manet-web-archive@ietf.org; Fri, 19 Nov 2004 13:54:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVDcN-0001NE-9y; Fri, 19 Nov 2004 13:36:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVDbZ-00017F-P2 for manet@megatron.ietf.org; Fri, 19 Nov 2004 13:35:34 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00166 for ; Fri, 19 Nov 2004 13:35:32 -0500 (EST) Received: from mail.crc.ca ([142.92.39.129]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVDeR-0003LK-Tp for manet@ietf.org; Fri, 19 Nov 2004 13:38:32 -0500 Received: from ROGER (roger.dgrc.crc.ca [142.92.38.14]) by mail.crc.ca (8.12.11/8.12.11) with SMTP id iAJJXeR0025806; Fri, 19 Nov 2004 14:33:40 -0500 Message-Id: <200411191933.iAJJXeR0025806@mail.crc.ca> X-Sender: lli@mail.crc.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Fri, 19 Nov 2004 13:45:30 -0500 To: Ian Chakeres , "Charles E. Perkins" , Thomas Heide Clausen , "'manet'" , Justin Dean From: Li Li Subject: Re: [manet] Path Accumulation in DyMO In-Reply-To: <1CC461A4-39A1-11D9-830D-000A95C1BC0A@cs.ucsb.edu> References: <8497-SnapperMsgD302CB11BDC24FFA@192.168.0.192> <8497-SnapperMsgD302CB11BDC24FFA@192.168.0.192> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Scanned-By: MIMEDefang 2.44 X-Spam-Score: 1.9 (+) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 At 12:33 PM 11/18/2004 -0800, Ian Chakeres wrote: > Alternatively we could create a more modular option that allows >us to include only some nodes on the path. Or even more versatile a >method to disseminate routes that are not on the RREQ/RREP path (i.e. >gateways). It could even carry additional information, hop count, >metric, security information, etc... > If including only some nodes not every node, then the format/structure and the procedure may be more complex than every node is included? Is this for the purpose that nodes can have an option of not supporting the feature? Using RREQ/RREP etc. to disseminate all kinds of information should be optional based on which feature it is for, if the feature is optional or mandatory. I feel path accumulation for routing more valuable than some of the others. Also saodv draft has proposed some security information for the security requirements. li li Li Li, Ph.D Communications Research Centre, Industry Canada 3701 Carling avenue P.O. box 11490 Station H, Ottawa, Ontario, Canada K2H 8S2 Tel: (613) 990-5246 Email: li.li@crc.ca _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 14:32:39 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04954 for ; Fri, 19 Nov 2004 14:32:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVEXk-0004dD-Dr for manet-web-archive@ietf.org; Fri, 19 Nov 2004 14:35:40 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVERr-0005UJ-WD; Fri, 19 Nov 2004 14:29:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVEM5-0004IJ-Nk for manet@megatron.ietf.org; Fri, 19 Nov 2004 14:23:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04195 for ; Fri, 19 Nov 2004 14:23:36 -0500 (EST) Received: from smtp.ucla.edu ([169.232.47.138]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVEOy-0004QN-Hy for manet@ietf.org; Fri, 19 Nov 2004 14:26:37 -0500 Received: from mail.ucla.edu (mail.ucla.edu [169.232.48.135]) by smtp.ucla.edu (8.13.1/8.13.1) with ESMTP id iAJJNY1O006764; Fri, 19 Nov 2004 11:23:34 -0800 Received: from LauraD5590W31 (rubin-d1.ee.ucla.edu [128.97.89.172]) (authenticated bits=0) by mail.ucla.edu (8.13.1/8.13.1) with ESMTP id iAJJNPKh024854; Fri, 19 Nov 2004 11:23:34 -0800 From: "Huei-jiun Ju \(Laura\)" To: "'Shubhranshu'" , Subject: RE: [manet] manet autoconf. Date: Fri, 19 Nov 2004 11:23:26 -0800 Message-ID: <001601c4ce6d$417acae0$ac596180@LauraD5590W31> 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.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal In-Reply-To: <200411191201.HAA21400@ietf.org> X-Probable-Spam: no X-Spam-Hits: 0 X-Scanned-By: smtp.ucla.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Content-Transfer-Encoding: quoted-printable Hi Shubhranshu, Please add me to the mailing list, too. Thank you in advance. --- Huei-jiun Ju (Laura) Autonomous Intelligent Networked Systems group, Electrical Engineering dept, UCLA -----Urspr=FCngliche Nachricht----- Von: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] Im Auftrag von Shubhranshu Gesendet: Donnerstag, 18. November 2004 14:00 An: manet@ietf.org Betreff: [manet] manet autoconf. Hi all, MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However,=20 there are other issues fundamental to ad hoc network operation and deployment such as address=20 auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic=20 forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji=20 Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and need to standardize solutions for these auto-configuration related issues within IETF. This was=20 then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be the best place to solve these issues. There was some sort of consensus to move forward with this work. Several independent publications and=20 implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up=20 a mailing list of those interested in these topics and willing to contribute. There should be consensus on problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting,=20 depending on the development on this mailing list. Regards, Shubhranshu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 14:52:06 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06737 for ; Fri, 19 Nov 2004 14:52:06 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVEqY-00055q-LQ for manet-web-archive@ietf.org; Fri, 19 Nov 2004 14:55:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVEXs-0007AW-3X; Fri, 19 Nov 2004 14:35:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVEVn-0006Wp-0a for manet@megatron.ietf.org; Fri, 19 Nov 2004 14:33:39 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05086 for ; Fri, 19 Nov 2004 14:33:37 -0500 (EST) Received: from as.itesm.mx ([200.34.200.251]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVEYf-0004el-Uh for manet@ietf.org; Fri, 19 Nov 2004 14:36:38 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-Ironport-AV: i="3.87,100,1099288800"; d="scan'208"; a="30453538:sNHT14106968" Received: from lp4 (10.49.146.170) by itesm.mx (6.7.019) id 4145DDA900431A66; Fri, 19 Nov 2004 13:33:32 -0600 From: "Francisco A. Gonzalez Horta" To: "Shubhranshu" , Subject: RE: [manet] manet autoconf. Date: Fri, 19 Nov 2004 13:35:32 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="ks_c_5601-1987" 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) In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit Hello Shubhranshu, Please add me to the manet autoconf list. Regards, Francisco Gonzalez > -----Mensaje original----- > De: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]En > nombre de Shubhranshu > Enviado el: Jueves, 18 de Noviembre de 2004 07:00 a.m. > Para: manet@ietf.org > Asunto: [manet] manet autoconf. > > > Hi all, > > MANET WG is developing proactive, reactive and simplified > multicast forwarding protocols. However, > there are other issues fundamental to ad hoc network operation > and deployment such as address > auto-configuration, DAD, gateway discovery and selection for > global prefix allocation and traffic > forwarding, etc. During 61st IETF meeting, Thomas Clausen, > Ruffino Simon, Charles Perkins, Ryuji > Wakikawa, Li Li, Emmanuel Baccelli, myself and few others > discussed about the importance and > need to standardize solutions for these auto-configuration > related issues within IETF. This was > then presented by Simon in the MANET WG meeting. It is understood > that MANET WG may not be > the best place to solve these issues. > > There was some sort of consensus to move forward with this work. > Several independent publications and > implementations are available. As suggested by Joe Macker, Alex > Zinin and others, we are going to set up > a mailing list of those interested in these topics and willing to > contribute. There should be consensus on > problem statement, possible approach, existing solutions, > milestones, etc. So, let me know if you would > like to be part of the mailing list. We are planning to go for > BOF/bar-BOF at the next IETF meeting, > depending on the development on this mailing list. > > Regards, > Shubhranshu > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 15:16:02 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09223 for ; Fri, 19 Nov 2004 15:16:02 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVFDj-0005e0-Oc for manet-web-archive@ietf.org; Fri, 19 Nov 2004 15:19:04 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVF3F-0005tp-1O; Fri, 19 Nov 2004 15:08:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVEzc-0002GT-0H for manet@megatron.ietf.org; Fri, 19 Nov 2004 15:04:28 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07937 for ; Fri, 19 Nov 2004 15:04:25 -0500 (EST) Received: from darkstar.iprg.nokia.com ([205.226.5.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVF2U-0005QH-Ed for manet@ietf.org; Fri, 19 Nov 2004 15:07:27 -0500 Received: (from root@localhost) by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id iAJJZk215040; Fri, 19 Nov 2004 11:35:46 -0800 X-mProtect: <200411191935> Nokia Silicon Valley Messaging Protection Received: from mvdhcp141115.americas.nokia.com (172.18.141.115, claiming to be "[172.18.141.115]") by darkstar.iprg.nokia.com smtpdn7VZpC; Fri, 19 Nov 2004 11:35:44 PST Message-ID: <419E4FED.1080204@iprg.nokia.com> Date: Fri, 19 Nov 2004 11:56:29 -0800 From: Charlie P Organization: NOKIA User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Luke Klein-Berndt Subject: Re: [manet] Path Accumulation in DyMO References: <00d901c4ce6b$82e82150$33320681@campus.nist.gov> In-Reply-To: <00d901c4ce6b$82e82150$33320681@campus.nist.gov> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9 Content-Transfer-Encoding: 7bit Cc: "'manet'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26 Content-Transfer-Encoding: 7bit Hello Luke, Luke Klein-Berndt wrote: >Right now it is clear that having Path Accumulation information would be >valuable, but it isn't completely clear how it can be best used right >now. There are some scenarios were the might be gains from having the >additional destinations along a route, but there are some scenarios, >such as high mobility, where those additional destinations could be >stale leading to short lived routes. > > The reason for standardizing is to maximize interoperability, and here we can see clear benefits from mandating path accumulation: - simpler data structure overall - probably less congestion under a majority of the circumstances - enables simpler computation at each node wishing to use the data - decrease substantially the need for reverse route maintenance and timeout. But, note that the code for those operations is still needed. It just doesn't need to be exercised very often. - etc., as mentioned in other emails. Consider the implementation complexity. Roughly speaking, it boils down to copying a list and extending it by (sizeof IP_address). That's not too bad. Plus, a conformant IP stack already has to perform a more difficult similar task in order to implement the source routing options for IPv4 and the analogous header for IPv6. I don't see implementation as a difficulty unless you also wanted to fudge the IP header processing itself (eek!!). Maybe more serious is the limitation on message size which would be imposed by a goal to avoid fragmentation. For IPv4, this doesn't seem to be too serious unless we are dealing with large node populations. In fact, I think there is a solution that does not add very much code on top of what is already required, but there's no need to discuss that until we decide one way or the other. If the decision turns out to rest on code complexity, then I'll formulate another message about such a potential solution. If you believe the above, then the bottom line is that if we do NOT mandate path accumulation, you _still_ don't get any extra sleep. And who knows, maybe we would all lose sleep over failure to do the right thing (just kidding!). Overall, I am much in favor of mandating path accumulation, but not at the risk of deraiiling the specification effort. Regards, Charlie P. >If the standard is going to be deployed I don't think we should add a >feature because it could be interesting, we should add it because it >provides known gains. The is especially true if it takes away from an >existing feature like simplicity. > >Here is what I would do: Leave path accumlation of the Standard for >DyMO. Carfully define the extension section of DyMO, so that it can >handle things like Path Accumulation Extensions. It is also important to >define how DyMO should handle extensions it doesn't know, ie probably >just ignoring them. This would it easier for industry to create DyMO >Standard based products. Exstensibility would also allow researchers to >create extensions like Path Accumulation or newer un-thought-of >improverment with existing products. > >I definitely think that we should either have every node use Path >Accumulation or not. Otherwise the value of Path Accumulation gets >deluted and the algorithm for building a route gets less fun. > >Basically I am lazy would rather not implement things that are not going >to improve functionality. We have all done a lot of research in this >field, and if we don't have a clear reason for including something in >the standard, it might not belong... but as per my previous sentence, I >would also make my life easier :) > >- Luke Klein-Berndt > > > > > >>-----Original Message----- >>From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] >>On Behalf Of Ian Chakeres >>Sent: Thursday, November 18, 2004 3:34 PM >>To: Charles E. Perkins; Thomas Heide Clausen; 'manet'; Justin Dean >>Subject: Re: [manet] Path Accumulation in DyMO >> >> >>First I want to issue a query to the list. Does anyone think >>we should >>use path accumulation to alleviate creating a reverse route to the >>source during RREQ propagation? I'd like to get consensus >>that this is >>a non-issue. >> >>Given that we don't perform path accumulation for the reason of not >>storing the reverse route during RREQ propagation, I think >>there are a >>large number of possibilities for disseminating additional >>information. >>For example, we could include each node on the path, and >>their sequence >>number. Alternatively we could create a more modular option >>that allows >>us to include only some nodes on the path. Or even more versatile a >>method to disseminate routes that are not on the RREQ/RREP path (i.e. >>gateways). It could even carry additional information, hop count, >>metric, security information, etc... >> >>Given all these choices I would prefer to leave this as an open issue >>pending experimentation, instead of attempting to specify the >>"way" to >>do it in the base spec. Obviously we could do both, specify one way >>and allow additional options for others. I'm open to that >>option also. >> >>Does anyone have a feeling as to what if any technique should be >>included in the base specification but not mandated? What information >>should be disseminated? >> >>Thanks. >>Ian Chakeres >> >>On Nov 18, 2004, at 5:11 AM, Thomas Heide Clausen wrote: >> >> >>>Ian, >>> >>>I am still of the general opinion that leaving an option unspecified >>>is a >>>bad thing, assuming that it's an option which (i) a plurality of >>>deployments might use and (ii) where different >>>approaches/implementations >>>might impair interoperability. >>> >>>What's the general observations on (i) and (ii) regarding >>>path-accumulation? >>> >>>--thomas >>>___ >>>Sent with SnapperMail >>>www.snappermail.com >>> >>>...... Original Message ....... >>>On Fri, 12 Nov 2004 06:59:15 -0500 Ian Chakeres >>>wrote: >>> >>> >>>>At the MANET meeting I presented DyMO (Dynamic MANET On-demand >>>>Routing Protocol). My slides from the presentation are >>>> >>>> >>available at >> >> >>http://moment.cs.ucsb.edu/~idc/pub/chakeres_ietf61_presentatio >> >> >n.pdf. > > >>>There was a short discussion about using path accumulation in the >>>base specification. Most people expressed their feelings that path >>>accumulation is useful for additional route information >>>dissemination. I believe there was consensus to not include path >>>accumulation in the core spec though it should definitely be included >>> >>> > > > >>>as an optimization. If you disagree, lets discuss it more on the >>>list. >>> >>>Thanks. >>>Ian Chakeres >>> >>> >>>_______________________________________________ >>>manet mailing list >>>manet@ietf.org >>>https://www1.ietf.org/mailman/listinfo/manet >>> >>> >>> > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 15:42:36 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13793 for ; Fri, 19 Nov 2004 15:42:36 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVFdR-0006m1-OP for manet-web-archive@ietf.org; Fri, 19 Nov 2004 15:45:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVFQ6-0005fF-Bn; Fri, 19 Nov 2004 15:31:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVF9S-0001MP-Vi for manet@megatron.ietf.org; Fri, 19 Nov 2004 15:14:39 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09078 for ; Fri, 19 Nov 2004 15:14:37 -0500 (EST) Received: from mailer.nec-labs.com ([138.15.108.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVFCM-0005by-I9 for manet@ietf.org; Fri, 19 Nov 2004 15:17:38 -0500 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.6487.1 Subject: RE: [manet] manet autoconf. Date: Fri, 19 Nov 2004 15:14:05 -0500 Message-ID: <951A499AA688EF47A898B45F25BD8EE801579F57@mailer.nec-labs.com> Thread-Topic: [manet] manet autoconf. Thread-Index: AcTN8Z2J65dk0puIQwW81POlXI6mlgAgpE5Q From: "Kyungtae Kim" To: "Gayathri" , "Shubhranshu" X-Spam-Score: 0.0 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Content-Transfer-Encoding: quoted-printable Dear Shubhranshu, Could you add me to the list? I am interested in MANET auto-configuration.=20 Thanking you Best regards, Kyungtae Kim -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Gayathri Sent: Thursday, November 18, 2004 11:27 PM To: Shubhranshu Cc: manet@ietf.org Subject: Re: [manet] manet autoconf. Dear Shubhranshu: Could you add me to the list? I am interested in MANET auto-configuration.=20 Thanking you Best regards, Gayathri Venkataraman=20 --- Shubhranshu wrote: > Hi all, >=20 > MANET WG is developing proactive, reactive and > simplified multicast forwarding protocols. However,=20 > there are other issues fundamental to ad hoc network > operation and deployment such as address=20 > auto-configuration, DAD, gateway discovery and > selection for global prefix allocation and traffic=20 > forwarding, etc. During 61st IETF meeting, Thomas > Clausen, Ruffino Simon, Charles Perkins, Ryuji=20 > Wakikawa, Li Li, Emmanuel Baccelli, myself and few > others discussed about the importance and > need to standardize solutions for these > auto-configuration related issues within IETF. This > was=20 > then presented by Simon in the MANET WG meeting. It > is understood that MANET WG may not be > the best place to solve these issues. >=20 > There was some sort of consensus to move forward > with this work. Several independent publications and >=20 > implementations are available. As suggested by Joe > Macker, Alex Zinin and others, we are going to set > up=20 > a mailing list of those interested in these topics > and willing to contribute. There should be consensus > on > problem statement, possible approach, existing > solutions, milestones, etc. So, let me know if you > would > like to be part of the mailing list. We are planning > to go for BOF/bar-BOF at the next IETF meeting,=20 > depending on the development on this mailing list. >=20 > Regards, > Shubhranshu >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around=20 http://mail.yahoo.com=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 16:55:23 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28519 for ; Fri, 19 Nov 2004 16:55:22 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVGlt-0003ER-6k for manet-web-archive@ietf.org; Fri, 19 Nov 2004 16:58:25 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVGO2-0006nh-HM; Fri, 19 Nov 2004 16:33:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVFsf-0000HQ-5t for manet@megatron.ietf.org; Fri, 19 Nov 2004 16:01:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA17619 for ; Fri, 19 Nov 2004 16:01:16 -0500 (EST) Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVFvW-000868-71 for manet@ietf.org; Fri, 19 Nov 2004 16:04:18 -0500 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.12.10+Sun/8.12.8) with SMTP id iAJL02sX025520; Fri, 19 Nov 2004 16:00:03 -0500 (EST) Received: from D313NV11.itd.nrl.navy.mil ([132.250.93.60]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.0.4.64) with SMTP id M2004111916000107906 ; Fri, 19 Nov 2004 16:00:01 -0500 Message-Id: <5.2.0.9.2.20041119153535.034e9b30@pop.itd.nrl.navy.mil> X-Sender: jdean@pop.itd.nrl.navy.mil X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 19 Nov 2004 16:11:17 -0500 To: Charlie P , Luke Klein-Berndt From: Justin Dean Subject: Re: [manet] Path Accumulation in DyMO In-Reply-To: <419E4FED.1080204@iprg.nokia.com> References: <00d901c4ce6b$82e82150$33320681@campus.nist.gov> <00d901c4ce6b$82e82150$33320681@campus.nist.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: a4a24b484706be629f915bfb1a3e4771 Cc: "'manet'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b84f8c8fba0e1389e5eb998b64078964 One big issue that may be some cause for concern when using path accumulation is security. By allowing packet modification a single compromised node can cause quite a bit of havoc throughout the network. I am not saying that it can not be done only that it seems to me to be inherently less secure than not having accumulation. As a routing person path accumulation is the way to go because of the reasons Charlie mentioned as well as others. Looking at it in terms of security/deployment person no path accumulation should be safer. Because I am more of a routing person I want path accumulation; there is just so much more information to work with by using it. As for Ian's question of what should be included in the base specification. I would propose a modular information field, which could be turned on using some bytes in the header. The actual information field containing a type field and a value field. (with a bit reserved in the type field for continuation, ie next 32 bits is another value field not an address) Other than defining the fields I don't think anything further should be included in base specification. Let types be defined by later options specifications. I also think default mode of operation should just be addresses. The above idea along with storing link information could be used to compress packets which are in danger of becoming too large. By removing a bunch of path information recording it locally and putting in a value field with the corresponding hop count between end points that were not removed. On return trip the information could be added back into the packet. Justin Dean At 11:56 AM 11/19/2004 -0800, Charlie P wrote: >Hello Luke, > >Luke Klein-Berndt wrote: > >>Right now it is clear that having Path Accumulation information would be >>valuable, but it isn't completely clear how it can be best used right >>now. There are some scenarios were the might be gains from having the >>additional destinations along a route, but there are some scenarios, >>such as high mobility, where those additional destinations could be >>stale leading to short lived routes. >> >The reason for standardizing is to maximize interoperability, and >here we can see clear benefits from mandating path accumulation: >- simpler data structure overall >- probably less congestion under a majority of the circumstances >- enables simpler computation at each node wishing to use the data >- decrease substantially the need for reverse route maintenance > and timeout. But, note that the code for those operations is > still needed. It just doesn't need to be exercised very often. >- etc., as mentioned in other emails. > >Consider the implementation complexity. Roughly speaking, it boils >down to copying a list and extending it by (sizeof IP_address). >That's not too bad. Plus, a conformant IP stack already has to >perform a more difficult similar task in order to implement the >source routing options for IPv4 and the analogous header for >IPv6. I don't see implementation as a difficulty unless you also >wanted to fudge the IP header processing itself (eek!!). > >Maybe more serious is the limitation on message size which >would be imposed by a goal to avoid fragmentation. For IPv4, >this doesn't seem to be too serious unless we are dealing with >large node populations. In fact, I think there is a solution that >does not add very much code on top of what is already required, >but there's no need to discuss that until we decide one way or >the other. If the decision turns out to rest on code complexity, >then I'll formulate another message about such a potential >solution. > >If you believe the above, then the bottom line is that if we >do NOT mandate path accumulation, you _still_ don't get >any extra sleep. And who knows, maybe we would all >lose sleep over failure to do the right thing (just kidding!). > >Overall, I am much in favor of mandating path accumulation, >but not at the risk of deraiiling the specification effort. > >Regards, >Charlie P. > > >>If the standard is going to be deployed I don't think we should add a >>feature because it could be interesting, we should add it because it >>provides known gains. The is especially true if it takes away from an >>existing feature like simplicity. >> >>Here is what I would do: Leave path accumlation of the Standard for >>DyMO. Carfully define the extension section of DyMO, so that it can >>handle things like Path Accumulation Extensions. It is also important to >>define how DyMO should handle extensions it doesn't know, ie probably >>just ignoring them. This would it easier for industry to create DyMO >>Standard based products. Exstensibility would also allow researchers to >>create extensions like Path Accumulation or newer un-thought-of >>improverment with existing products. >>I definitely think that we should either have every node use Path >>Accumulation or not. Otherwise the value of Path Accumulation gets >>deluted and the algorithm for building a route gets less fun. >> >>Basically I am lazy would rather not implement things that are not going >>to improve functionality. We have all done a lot of research in this >>field, and if we don't have a clear reason for including something in >>the standard, it might not belong... but as per my previous sentence, I >>would also make my life easier :) >>- Luke Klein-Berndt >> >> >> >> >> >>>-----Original Message----- >>>From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf >>>Of Ian Chakeres >>>Sent: Thursday, November 18, 2004 3:34 PM >>>To: Charles E. Perkins; Thomas Heide Clausen; 'manet'; Justin Dean >>>Subject: Re: [manet] Path Accumulation in DyMO >>> >>> >>>First I want to issue a query to the list. Does anyone think we should >>>use path accumulation to alleviate creating a reverse route to the >>>source during RREQ propagation? I'd like to get consensus that this is a >>>non-issue. >>> >>>Given that we don't perform path accumulation for the reason of not >>>storing the reverse route during RREQ propagation, I think there are a >>>large number of possibilities for disseminating additional information. >>>For example, we could include each node on the path, and their sequence >>>number. Alternatively we could create a more modular option that allows >>>us to include only some nodes on the path. Or even more versatile a >>>method to disseminate routes that are not on the RREQ/RREP path (i.e. >>>gateways). It could even carry additional information, hop count, >>>metric, security information, etc... >>> >>>Given all these choices I would prefer to leave this as an open issue >>>pending experimentation, instead of attempting to specify the "way" to >>>do it in the base spec. Obviously we could do both, specify one way and >>>allow additional options for others. I'm open to that option also. >>> >>>Does anyone have a feeling as to what if any technique should be >>>included in the base specification but not mandated? What information >>>should be disseminated? >>> >>>Thanks. >>>Ian Chakeres >>> >>>On Nov 18, 2004, at 5:11 AM, Thomas Heide Clausen wrote: >>> >>> >>>>Ian, >>>> >>>>I am still of the general opinion that leaving an option unspecified >>>>is a >>>>bad thing, assuming that it's an option which (i) a plurality of >>>>deployments might use and (ii) where different approaches/implementations >>>>might impair interoperability. >>>> >>>>What's the general observations on (i) and (ii) regarding >>>>path-accumulation? >>>> >>>>--thomas >>>>___ >>>>Sent with SnapperMail >>>>www.snappermail.com >>>> >>>>...... Original Message ....... >>>>On Fri, 12 Nov 2004 06:59:15 -0500 Ian Chakeres >>>>wrote: >>>> >>>> >>>>>At the MANET meeting I presented DyMO (Dynamic MANET On-demand Routing >>>>>Protocol). My slides from the presentation are >>>available at >>> >>>http://moment.cs.ucsb.edu/~idc/pub/chakeres_ietf61_presentatio >>> >>n.pdf. >> >> >>>>There was a short discussion about using path accumulation in the base >>>>specification. Most people expressed their feelings that path >>>>accumulation is useful for additional route information dissemination. >>>>I believe there was consensus to not include path accumulation in the >>>>core spec though it should definitely be included >>>> >> >> >> >>>>as an optimization. If you disagree, lets discuss it more on the list. >>>> >>>>Thanks. >>>>Ian Chakeres >>>> >>>> >>>>_______________________________________________ >>>>manet mailing 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 manet-bounces@ietf.org Fri Nov 19 17:00:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29315 for ; Fri, 19 Nov 2004 17:00:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVGr4-0003TP-Tw for manet-web-archive@ietf.org; Fri, 19 Nov 2004 17:03:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVGWr-0007h1-Ae; Fri, 19 Nov 2004 16:42:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVGGt-00019A-4o for manet@megatron.ietf.org; Fri, 19 Nov 2004 16:26:23 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24570 for ; Fri, 19 Nov 2004 16:26:22 -0500 (EST) Received: from rimp1.nist.gov ([129.6.16.226] helo=smtp.nist.gov) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVGJo-0001zp-FG for manet@ietf.org; Fri, 19 Nov 2004 16:29:24 -0500 Received: from gwialo (camelot.antd.nist.gov [129.6.50.51]) by smtp.nist.gov (8.12.10/8.12.10) with ESMTP id iAJLQI2x015280; Fri, 19 Nov 2004 16:26:18 -0500 From: "Luke Klein-Berndt" To: "'Charlie P'" Subject: RE: [manet] Path Accumulation in DyMO Date: Fri, 19 Nov 2004 16:26:18 -0500 Message-ID: <00de01c4ce7e$68978c60$33320681@campus.nist.gov> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal In-Reply-To: <419E4FED.1080204@iprg.nokia.com> X-NIST-MailScanner: Found to be clean X-MailScanner-From: luke.klein-berndt@nist.gov X-Spam-Score: 0.0 (/) X-Scan-Signature: 3f3e54d3c03ed638c06aa9fa6861237e Content-Transfer-Encoding: 7bit Cc: "'manet'" X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cdeeb24e6b743a852c396a4af0e53c8f Content-Transfer-Encoding: 7bit Hi Charlie, I think my basic feeling is that we should either mandate Path Accumulation for all nodes or not include it. Making it optional, where only some nodes would add themselves to the list, would make it more complex to implement and take away from some of its usefulness. To me it seems like performance wise they would be roughly equal on average, and since they are about the same to implement, I think either method would work. I do agree that Path Accumulation does have advantages. One of them is that it delivers more information, of course more information does mean that the packets are bigger. If stratigies for handling routes that are too large for a packet was kept simple or put in another document, I would be for path accumulation. It might also turn out that you don't want to be building routes that are too long to fit inside a packet. There might end up being a relation between maximum packet size and the maximum length of a reliable route. I am happy with either method. I think the Path Accumulation should be used for building routes instead of an option used to gathering more information. My main concern is just keeping the base standard straight forward and relativly easy to follow. The less conditional cases the better! -Luke Klein-Berndt > -----Original Message----- > From: Charlie P [mailto:charliep@iprg.nokia.com] > Sent: Friday, November 19, 2004 2:56 PM > To: Luke Klein-Berndt > Cc: 'manet' > Subject: Re: [manet] Path Accumulation in DyMO > > > > Hello Luke, > > Luke Klein-Berndt wrote: > > >Right now it is clear that having Path Accumulation > information would > >be valuable, but it isn't completely clear how it can be best used > >right now. There are some scenarios were the might be gains > from having > >the additional destinations along a route, but there are some > >scenarios, such as high mobility, where those additional > destinations > >could be stale leading to short lived routes. > > > > > The reason for standardizing is to maximize interoperability, > and here we can see clear benefits from mandating path accumulation: > - simpler data structure overall > - probably less congestion under a majority of the circumstances > - enables simpler computation at each node wishing to use the data > - decrease substantially the need for reverse route maintenance > and timeout. But, note that the code for those operations is > stil needed. It just doesn't need to be exercised very often. > - etc., as mentioned in other emails. > > Consider the implementation complexity. Roughly speaking, it > boils down to copying a list and extending it by (sizeof > IP_address). That's not too bad. Plus, a conformant IP stack > already has to perform a more difficult similar task in order > to implement the source routing options for IPv4 and the > analogous header for IPv6. I don't see implementation as a > difficulty unless you also wanted to fudge the IP header > processing itself (eek!!). > > Maybe more serious is the limitation on message size which > would be imposed by a goal to avoid fragmentation. For IPv4, > this doesn't seem to be too serious unless we are dealing > with large node populations. In fact, I think there is a > solution that does not add very much code on top of what is > already required, but there's no need to discuss that until > we decide one way or the other. If the decision turns out to > rest on code complexity, then I'll formulate another message > about such a potential solution. > > If you believe the above, then the bottom line is that if we > do NOT mandate path accumulation, you _still_ don't get > any extra sleep. And who knows, maybe we would all > lose sleep over failure to do the right thing (just kidding!). > > Overall, I am much in favor of mandating path accumulation, > but not at the risk of deraiiling the specification effort. > > Regards, > Charlie P. > > > >If the standard is going to be deployed I don't think we > should add a > >feature because it could be interesting, we should add it because it > >provides known gains. The is especially true if it takes > away from an > >existing feature like simplicity. > > > >Here is what I would do: Leave path accumlation of the Standard for > >DyMO. Carfully define the extension section of DyMO, so that it can > >handle things like Path Accumulation Extensions. It is also > important > >to define how DyMO should handle extensions it doesn't know, ie > >probably just ignoring them. This would it easier for industry to > >create DyMO Standard based products. Exstensibility would also allow > >researchers to create extensions like Path Accumulation or newer > >un-thought-of improverment with existing products. > > > >I definitely think that we should either have every node use Path > >Accumulation or not. Otherwise the value of Path Accumulation gets > >deluted and the algorithm for building a route gets less fun. > > > >Basically I am lazy would rather not implement things that are not > >going to improve functionality. We have all done a lot of > research in > >this field, and if we don't have a clear reason for > including something > >in the standard, it might not belong... but as per my previous > >sentence, I would also make my life easier :) > > > >- Luke Klein-Berndt > > > > > > > > > > > >>-----Original Message----- > >>From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] > >>On Behalf Of Ian Chakeres > >>Sent: Thursday, November 18, 2004 3:34 PM > >>To: Charles E. Perkins; Thomas Heide Clausen; 'manet'; Justin Dean > >>Subject: Re: [manet] Path Accumulation in DyMO > >> > >> > >>First I want to issue a query to the list. Does anyone think > >>we should > >>use path accumulation to alleviate creating a reverse route to the > >>source during RREQ propagation? I'd like to get consensus > >>that this is > >>a non-issue. > >> > >>Given that we don't perform path accumulation for the reason of not > >>storing the reverse route during RREQ propagation, I think > >>there are a > >>large number of possibilities for disseminating additional > >>information. > >>For example, we could include each node on the path, and > >>their sequence > >>number. Alternatively we could create a more modular option > >>that allows > >>us to include only some nodes on the path. Or even more versatile a > >>method to disseminate routes that are not on the RREQ/RREP > path (i.e. > >>gateways). It could even carry additional information, hop count, > >>metric, security information, etc... > >> > >>Given all these choices I would prefer to leave this as an > open issue > >>pending experimentation, instead of attempting to specify the > >>"way" to > >>do it in the base spec. Obviously we could do both, > specify one way > >>and allow additional options for others. I'm open to that > >>option also. > >> > >>Does anyone have a feeling as to what if any technique should be > >>included in the base specification but not mandated? What > information > >>should be disseminated? > >> > >>Thanks. > >>Ian Chakeres > >> > >>On Nov 18, 2004, at 5:11 AM, Thomas Heide Clausen wrote: > >> > >> > >>>Ian, > >>> > >>>I am still of the general opinion that leaving an option > unspecified > >>>is a bad thing, assuming that it's an option which (i) a > plurality of > >>>deployments might use and (ii) where different > >>>approaches/implementations > >>>might impair interoperability. > >>> > >>>What's the general observations on (i) and (ii) regarding > >>>path-accumulation? > >>> > >>>--thomas > >>>___ > >>>Sent with SnapperMail > >>>www.snappermail.com > >>> > >>>...... Original Message ....... > >>>On Fri, 12 Nov 2004 06:59:15 -0500 Ian Chakeres > >>>wrote: > >>> > >>> > >>>>At the MANET meeting I presented DyMO (Dynamic MANET On-demand > >>>>Routing Protocol). My slides from the presentation are > >>>> > >>>> > >>available at > >> > >> > >>http://moment.cs.ucsb.edu/~idc/pub/chakeres_ietf61_presentatio > >> > >> > >n.pdf. > > > > > >>>There was a short discussion about using path accumulation in the > >>>base specification. Most people expressed their feelings > that path > >>>accumulation is useful for additional route information > >>>dissemination. I believe there was consensus to not include path > >>>accumulation in the core spec though it should definitely > be included > >>> > >>> > > > > > > > >>>as an optimization. If you disagree, lets discuss it more on the > >>>list. > >>> > >>>Thanks. > >>>Ian Chakeres > >>> > >>> > >>>_______________________________________________ > >>>manet mailing list > >>>manet@ietf.org > >>>https://www1.ietf.org/mailman/listinfo/manet > >>> > >>> > >>> > > > > > >_______________________________________________ > >manet mailing list > >manet@ietf.org > >https://www1.ietf.org/mailman/listinfo/manet > > > > > > > > > > > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 19 21:03:39 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18015 for ; Fri, 19 Nov 2004 21:03:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVKe9-0008JA-RS for manet-web-archive@ietf.org; Fri, 19 Nov 2004 21:06:44 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVKY5-0000JQ-W5; Fri, 19 Nov 2004 21:00:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVKPn-0007DU-Ud for manet@megatron.ietf.org; Fri, 19 Nov 2004 20:51:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17092 for ; Fri, 19 Nov 2004 20:51:50 -0500 (EST) Received: from [203.232.32.5] (helo=phenix.dyu.ac.kr) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVKSi-000826-Q2 for manet@ietf.org; Fri, 19 Nov 2004 20:54:54 -0500 Received: from skyhigh ([192.168.5.245]) by phenix.dyu.ac.kr (8.11.1/8.11.1) with SMTP id iAK1b5A01592; Sat, 20 Nov 2004 10:37:06 +0900 (KST) Message-ID: <009f01c4cea3$6c9287f0$f505a8c0@skyhigh> From: "Young-Dong Kim" To: "Shubhranshu" , References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Subject: Re: [manet] manet autoconf. Date: Sat, 20 Nov 2004 10:49:04 +0900 Organization: Dong Yang University MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 1.1 (+) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Young-Dong Kim List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1695082230==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.1 (+) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 --===============1695082230== Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 RGVhciBTaHViaHJhbnNodSwNCg0KSSBoYXZlIGEgbG90IG9mIGludGVyZXN0IGluIHRob3NlIHRv cGljcy4gDQpQbGVhc2UsIGFkZCBtZSB0byB0aGUgbGlzdCwgdG9vLiAgDQoNClRoYW5rIHlvdSwg c28gbXVjaC4gDQoNCkJlc3QgcmVnYXJkcywNCllvdW5nLURvbmcgS2ltDQoNCi0tLS0tIE9yaWdp bmFsIE1lc3NhZ2UgLS0tLS0gDQpGcm9tOiAiU2h1YmhyYW5zaHUiIDxzaHViaHJhbnNodUBzYW1z dW5nLmNvbT4NClRvOiA8bWFuZXRAaWV0Zi5vcmc+DQpTZW50OiBUaHVyc2RheSwgTm92ZW1iZXIg MTgsIDIwMDQgMTA6MDAgUE0NClN1YmplY3Q6IFttYW5ldF0gbWFuZXQgYXV0b2NvbmYuDQoNCg0K PiBIaSBhbGwsDQo+IA0KPiBNQU5FVCBXRyBpcyBkZXZlbG9waW5nIHByb2FjdGl2ZSwgcmVhY3Rp dmUgYW5kIHNpbXBsaWZpZWQgbXVsdGljYXN0IGZvcndhcmRpbmcgcHJvdG9jb2xzLiBIb3dldmVy LCANCj4gdGhlcmUgYXJlIG90aGVyIGlzc3VlcyBmdW5kYW1lbnRhbCB0byBhZCBob2MgbmV0d29y ayBvcGVyYXRpb24gYW5kIGRlcGxveW1lbnQgc3VjaCBhcyBhZGRyZXNzIA0KPiBhdXRvLWNvbmZp Z3VyYXRpb24sIERBRCwgZ2F0ZXdheSBkaXNjb3ZlcnkgYW5kIHNlbGVjdGlvbiBmb3IgZ2xvYmFs IHByZWZpeCBhbGxvY2F0aW9uIGFuZCB0cmFmZmljIA0KPiBmb3J3YXJkaW5nLCBldGMuIER1cmlu ZyA2MXN0IElFVEYgbWVldGluZywgVGhvbWFzIENsYXVzZW4sIFJ1ZmZpbm8gU2ltb24sIENoYXJs ZXMgUGVya2lucywgUnl1amkgDQo+IFdha2lrYXdhLCBMaSBMaSwgRW1tYW51ZWwgQmFjY2VsbGks IG15c2VsZiBhbmQgZmV3IG90aGVycyBkaXNjdXNzZWQgYWJvdXQgdGhlIGltcG9ydGFuY2UgYW5k DQo+IG5lZWQgdG8gc3RhbmRhcmRpemUgc29sdXRpb25zIGZvciB0aGVzZSBhdXRvLWNvbmZpZ3Vy YXRpb24gcmVsYXRlZCBpc3N1ZXMgd2l0aGluIElFVEYuIFRoaXMgd2FzIA0KPiB0aGVuIHByZXNl bnRlZCBieSBTaW1vbiBpbiB0aGUgTUFORVQgV0cgbWVldGluZy4gSXQgaXMgdW5kZXJzdG9vZCB0 aGF0IE1BTkVUIFdHIG1heSBub3QgYmUNCj4gdGhlIGJlc3QgcGxhY2UgdG8gc29sdmUgdGhlc2Ug aXNzdWVzLg0KPiANCj4gVGhlcmUgd2FzIHNvbWUgc29ydCBvZiBjb25zZW5zdXMgdG8gbW92ZSBm b3J3YXJkIHdpdGggdGhpcyB3b3JrLiBTZXZlcmFsIGluZGVwZW5kZW50IHB1YmxpY2F0aW9ucyBh bmQgDQo+IGltcGxlbWVudGF0aW9ucyBhcmUgYXZhaWxhYmxlLiBBcyBzdWdnZXN0ZWQgYnkgSm9l IE1hY2tlciwgQWxleCBaaW5pbiBhbmQgb3RoZXJzLCB3ZSBhcmUgZ29pbmcgdG8gc2V0IHVwIA0K PiBhIG1haWxpbmcgbGlzdCBvZiB0aG9zZSBpbnRlcmVzdGVkIGluIHRoZXNlIHRvcGljcyBhbmQg d2lsbGluZyB0byBjb250cmlidXRlLiBUaGVyZSBzaG91bGQgYmUgY29uc2Vuc3VzIG9uDQo+IHBy b2JsZW0gc3RhdGVtZW50LCBwb3NzaWJsZSBhcHByb2FjaCwgZXhpc3Rpbmcgc29sdXRpb25zLCBt aWxlc3RvbmVzLCBldGMuIFNvLCBsZXQgbWUga25vdyBpZiB5b3Ugd291bGQNCj4gbGlrZSB0byBi ZSBwYXJ0IG9mIHRoZSBtYWlsaW5nIGxpc3QuIFdlIGFyZSBwbGFubmluZyB0byBnbyBmb3IgQk9G L2Jhci1CT0YgYXQgdGhlIG5leHQgSUVURiBtZWV0aW5nLCANCj4gZGVwZW5kaW5nIG9uIHRoZSBk ZXZlbG9wbWVudCBvbiB0aGlzIG1haWxpbmcgbGlzdC4NCj4gDQo+IFJlZ2FyZHMsDQo+IFNodWJo cmFuc2h1DQo+IA0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX18NCj4gbWFuZXQgbWFpbGluZyBsaXN0DQo+IG1hbmV0QGlldGYub3JnDQo+IGh0dHBz Oi8vd3d3MS5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21hbmV0DQo+IA0KPiA= --===============1695082230== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1695082230==-- From manet-bounces@ietf.org Fri Nov 19 22:37:53 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25305 for ; Fri, 19 Nov 2004 22:37:52 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVM7O-0001lv-O9 for manet-web-archive@ietf.org; Fri, 19 Nov 2004 22:40:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVLxq-0006AO-LJ; Fri, 19 Nov 2004 22:31:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVLv3-0005Mn-JX for manet@megatron.ietf.org; Fri, 19 Nov 2004 22:28:13 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24449 for ; Fri, 19 Nov 2004 22:28:11 -0500 (EST) Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVLxz-0001Z4-W8 for manet@ietf.org; Fri, 19 Nov 2004 22:31:17 -0500 Received: from dagger.cc.vt.edu (IDENT:mirapoint@evil-dagger.cc.vt.edu [10.1.1.11]) by lennier.cc.vt.edu (8.12.11/8.12.11) with ESMTP id iAK3PTwg029522 for ; Fri, 19 Nov 2004 22:25:29 -0500 Received: from angel (69-161-5-229.chvlva.adelphia.net [69.161.5.229]) by dagger.cc.vt.edu (MOS 3.4.8-GR) with ESMTP id CBO27411 (AUTH ghadjich@127.0.0.1:1109); Fri, 19 Nov 2004 22:27:38 -0500 (EST) From: "George Hadjichristofi" To: Date: Fri, 19 Nov 2004 22:22:51 -0500 Message-ID: <03a801c4ceb0$37f6bea0$ca00a8c0@angel> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal X-Spam-Score: 0.2 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Subject: [manet] most widely used routing protocols? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ghadjich@vt.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0971095707==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.6 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 This is a multi-part message in MIME format. --===============0971095707== Content-Type: multipart/alternative; boundary="----=_NextPart_000_03A9_01C4CE86.4F20B6A0" This is a multi-part message in MIME format. ------=_NextPart_000_03A9_01C4CE86.4F20B6A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear All, I was wondering which are the most widely used proactive and reactive protocols for MANETs? Also, how much is OLSR used? Thank you, George ------=_NextPart_000_03A9_01C4CE86.4F20B6A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
Dear=20 All,
 
I was = wondering=20 which are the most widely used proactive and reactive protocols for=20 MANETs?
 
Also, how much=20 is OLSR  used?
Thank=20 you,
George
 
------=_NextPart_000_03A9_01C4CE86.4F20B6A0-- --===============0971095707== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0971095707==-- From manet-bounces@ietf.org Sat Nov 20 01:47:05 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA09464 for ; Sat, 20 Nov 2004 01:47:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVP4V-0005eQ-GE for manet-web-archive@ietf.org; Sat, 20 Nov 2004 01:50:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVOwM-0001cL-Fw; Sat, 20 Nov 2004 01:41:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVOrQ-00087T-0s for manet@megatron.ietf.org; Sat, 20 Nov 2004 01:36:40 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08789 for ; Sat, 20 Nov 2004 01:36:38 -0500 (EST) Received: from web51607.mail.yahoo.com ([206.190.38.212]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CVOuN-0005Sq-Q4 for manet@ietf.org; Sat, 20 Nov 2004 01:39:45 -0500 Received: (qmail 24308 invoked by uid 60001); 20 Nov 2004 06:36:07 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=Qp7YA4Qguw4X4vOgrdbql1o98wLVYaVj5sJQkH/ZHTxgGi2JuW1e2YQm4IkKUnEScQsCeawOF/LAWUZCaGbBRC/iy5xT75eRDzq25XMhFXEcQRXoXcncaLorSgZ0eKEGahnrGegcO2N2u6lWPyv/iwywNAVKvc5fbNHGILt0CFc= ; Message-ID: <20041120063607.24306.qmail@web51607.mail.yahoo.com> Received: from [161.246.1.34] by web51607.mail.yahoo.com via HTTP; Fri, 19 Nov 2004 22:36:07 PST Date: Fri, 19 Nov 2004 22:36:07 -0800 (PST) From: TAING Nguon To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.9 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Subject: [manet] NS-2 and TLC document X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Dear members, I am new to NS2 and tlc. Could anyone provide me document about Ns2 and tcl? thanks in advace. Regards, Nguon __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Nov 20 02:33:55 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27320 for ; Sat, 20 Nov 2004 02:33:54 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVPnq-0006YP-0h for manet-web-archive@ietf.org; Sat, 20 Nov 2004 02:37:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVPgz-0005AX-OK; Sat, 20 Nov 2004 02:29:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVPbk-0002Z7-Bj for manet@megatron.ietf.org; Sat, 20 Nov 2004 02:24:32 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26343 for ; Sat, 20 Nov 2004 02:24:30 -0500 (EST) Received: from mailout3.samsung.com ([203.254.224.33]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVPej-0006Mv-Hg for manet@ietf.org; Sat, 20 Nov 2004 02:27:38 -0500 Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) id <0I7G00E01V7YFI@mailout3.samsung.com> for manet@ietf.org; Sat, 20 Nov 2004 16:23:58 +0900 (KST) Received: from ep_mmp2 (mailout3.samsung.com [203.254.224.33]) by mailout3.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0I7G00013V7YYC@mailout3.samsung.com> for manet@ietf.org; Sat, 20 Nov 2004 16:23:58 +0900 (KST) Received: from Shubhranshu ([75.2.91.24]) by mmp2.samsung.com (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTPA id <0I7G00KP5V7WO6@mmp2.samsung.com> for manet@ietf.org; Sat, 20 Nov 2004 16:23:56 +0900 (KST) Date: Sat, 20 Nov 2004 16:23:56 +0900 From: Shubhranshu To: manet@ietf.org Message-id: <055701c4ced1$e5438270$185b024b@Shubhranshu> Organization: Samsung Electronics MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Mailer: Microsoft Outlook Express 6.00.2800.1409 Content-type: text/plain; charset=ks_c_5601-1987 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> <009f01c4cea3$6c9287f0$f505a8c0@skyhigh> X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: 7BIT Subject: [manet] manet autoconf. --> Plz send e-mail to shubhranshu@samsung.com X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 7BIT Plz send e-mail to shubhranshu@samsung.com and not to the entire list. Thanks, ----- Original Message ----- From: "Shubhranshu" To: Sent: Thursday, November 18, 2004 10:00 PM Subject: [manet] manet autoconf. > Hi all, > > MANET WG is developing proactive, reactive and simplified multicast forwarding protocols. However, > there are other issues fundamental to ad hoc network operation and deployment such as address > auto-configuration, DAD, gateway discovery and selection for global prefix allocation and traffic > forwarding, etc. During 61st IETF meeting, Thomas Clausen, Ruffino Simon, Charles Perkins, Ryuji > Wakikawa, Li Li, Emmanuel Baccelli, myself and few others discussed about the importance and > need to standardize solutions for these auto-configuration related issues within IETF. This was > then presented by Simon in the MANET WG meeting. It is understood that MANET WG may not be > the best place to solve these issues. > > There was some sort of consensus to move forward with this work. Several independent publications and > implementations are available. As suggested by Joe Macker, Alex Zinin and others, we are going to set up > a mailing list of those interested in these topics and willing to contribute. There should be consensus on > problem statement, possible approach, existing solutions, milestones, etc. So, let me know if you would > like to be part of the mailing list. We are planning to go for BOF/bar-BOF at the next IETF meeting, > depending on the development on this mailing list. > > Regards, > Shubhranshu > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Nov 20 04:46:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06735 for ; Sat, 20 Nov 2004 04:46:43 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVRsP-0000dT-7r for manet-web-archive@ietf.org; Sat, 20 Nov 2004 04:49:53 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVRmm-0006a3-9N; Sat, 20 Nov 2004 04:44:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVRiA-0005rU-Bo for manet@megatron.ietf.org; Sat, 20 Nov 2004 04:39:18 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06127 for ; Sat, 20 Nov 2004 04:39:15 -0500 (EST) Received: from mx2sophos.cqu.edu.au ([138.77.5.126]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVRlA-0000Tg-B5 for manet@ietf.org; Sat, 20 Nov 2004 04:42:25 -0500 Received: from neutron.staff.ad.cqu.edu.au ([138.77.34.42] helo=ROKEMAIL.staff.ad.cqu.edu.au) by mx2sophos.cqu.edu.au with esmtp (Exim 4.43) id 1CVRi1-0005LE-4w; Sat, 20 Nov 2004 19:39:09 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] NS-2 and TLC document Date: Sat, 20 Nov 2004 19:39:08 +1000 Message-ID: Thread-Topic: [manet] NS-2 and TLC document Thread-Index: AcTOzV6bzCReLlp4Qz+iE2BIrTgCmgAFz2CA From: "Amoakoh Gyasi-Agyei" To: "TAING Nguon" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: quoted-printable Hi, The website below may be of some help to you. Cheers http://www.idsia.ch/~andrea/simtools.html -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of TAING Nguon Sent: Saturday, November 20, 2004 4:36 PM To: manet@ietf.org Subject: [manet] NS-2 and TLC document Dear members, I am new to NS2 and tlc. Could anyone provide me document about Ns2 and tcl? thanks in advace. Regards, Nguon =09 __________________________________=20 Do you Yahoo!?=20 The all-new My Yahoo! - Get yours free!=20 http://my.yahoo.com=20 =20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Nov 20 06:22:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13633 for ; Sat, 20 Nov 2004 06:22:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVTNE-0002VV-6D for manet-web-archive@ietf.org; Sat, 20 Nov 2004 06:25:49 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVTB4-0003vG-2i; Sat, 20 Nov 2004 06:13:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVT75-0002ho-E6 for manet@megatron.ietf.org; Sat, 20 Nov 2004 06:09:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12829 for ; Sat, 20 Nov 2004 06:09:04 -0500 (EST) Received: from web25101.mail.ukl.yahoo.com ([217.12.10.49]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CVTA5-0002Gi-ST for manet@ietf.org; Sat, 20 Nov 2004 06:12:15 -0500 Received: (qmail 29688 invoked by uid 60001); 20 Nov 2004 11:08:35 -0000 Message-ID: <20041120110834.29686.qmail@web25101.mail.ukl.yahoo.com> Received: from [193.95.41.228] by web25101.mail.ukl.yahoo.com via HTTP; Sat, 20 Nov 2004 12:08:34 CET Date: Sat, 20 Nov 2004 12:08:34 +0100 (CET) From: Gadri Moez To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.6 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Subject: [manet] Test X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0657185295==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.6 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca --===============0657185295== Content-Type: multipart/alternative; boundary="0-547432379-1100948914=:29349" --0-547432379-1100948914=:29349 Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA12829 Content-Transfer-Encoding: quoted-printable test =09 --------------------------------- Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo de stockage ! Cr=E9ez votre Yahoo! Mail Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveau= t=E9s pour dialoguer instantan=E9ment avec vos amis.T=E9l=E9chargez GRATU= ITEMENT ici ! --0-547432379-1100948914=:29349 Content-Type: text/html; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA12829 Content-Transfer-Encoding: quoted-printable
test

Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo= de stockage !
Cr=E9ez votre Yahoo! Mail

Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveaut=E9s pour dialoguer instantan=E9ment a= vec vos amis. T=E9l=E9chargez GRATUITEMENT ici ! --0-547432379-1100948914=:29349-- --===============0657185295== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0657185295==-- From manet-bounces@ietf.org Sat Nov 20 06:33:22 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14401 for ; Sat, 20 Nov 2004 06:33:22 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVTXd-0002jE-0k for manet-web-archive@ietf.org; Sat, 20 Nov 2004 06:36:33 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVTLq-00073X-T1; Sat, 20 Nov 2004 06:24:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVTEH-0005Gx-Om for manet@megatron.ietf.org; Sat, 20 Nov 2004 06:16:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13301 for ; Sat, 20 Nov 2004 06:16:30 -0500 (EST) Received: from web25105.mail.ukl.yahoo.com ([217.12.10.53]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CVTHI-0002Og-3P for manet@ietf.org; Sat, 20 Nov 2004 06:19:41 -0500 Received: (qmail 33242 invoked by uid 60001); 20 Nov 2004 11:16:01 -0000 Message-ID: <20041120111600.33240.qmail@web25105.mail.ukl.yahoo.com> Received: from [193.95.41.228] by web25105.mail.ukl.yahoo.com via HTTP; Sat, 20 Nov 2004 12:16:00 CET Date: Sat, 20 Nov 2004 12:16:00 +0100 (CET) From: Gadri Moez To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.3 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Subject: [manet] Cooperative Caching X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0023833256==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 --===============0023833256== Content-Type: multipart/alternative; boundary="0-2072452609-1100949360=:32330" --0-2072452609-1100949360=:32330 Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA13301 Content-Transfer-Encoding: quoted-printable Hi, I=92m interested to cooperative caching in on demand mobile ad hoc networ= ks. Obviously, the performances offered by such approach. If there=92s an= y document speaking about this subject, please send it to me. Thanks. =09 --------------------------------- Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo de stockage ! Cr=E9ez votre Yahoo! Mail Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveau= t=E9s pour dialoguer instantan=E9ment avec vos amis.T=E9l=E9chargez GRATU= ITEMENT ici ! --0-2072452609-1100949360=:32330 Content-Type: text/html; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA13301 Content-Transfer-Encoding: quoted-printable

Hi,

I=92m interested to cooperative caching in on demand mobile ad hoc n= etworks. Obviously, the performances offered by such approach. If there=92= s any document speaking about this subject, please send it to me.<= /FONT>

Thanks.

Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo= de stockage !
Cr=E9ez votre Yahoo! Mail

Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveaut=E9s pour dialoguer instantan=E9ment a= vec vos amis. T=E9l=E9chargez GRATUITEMENT ici ! --0-2072452609-1100949360=:32330-- --===============0023833256== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0023833256==-- From manet-bounces@ietf.org Sat Nov 20 06:43:33 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15115 for ; Sat, 20 Nov 2004 06:43:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVThU-0002wD-1I for manet-web-archive@ietf.org; Sat, 20 Nov 2004 06:46:44 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVTYK-0000l7-S9; Sat, 20 Nov 2004 06:37:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVTNP-0007M5-Jf for manet@megatron.ietf.org; Sat, 20 Nov 2004 06:25:59 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13950 for ; Sat, 20 Nov 2004 06:25:56 -0500 (EST) Received: from web25110.mail.ukl.yahoo.com ([217.12.10.58]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CVTQP-0002a5-86 for manet@ietf.org; Sat, 20 Nov 2004 06:29:07 -0500 Received: (qmail 21848 invoked by uid 60001); 20 Nov 2004 11:25:26 -0000 Message-ID: <20041120112526.21846.qmail@web25110.mail.ukl.yahoo.com> Received: from [193.95.41.228] by web25110.mail.ukl.yahoo.com via HTTP; Sat, 20 Nov 2004 12:25:26 CET Date: Sat, 20 Nov 2004 12:25:26 +0100 (CET) From: Gadri Moez To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.6 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Subject: [manet] cooperative caching X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1043117526==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 --===============1043117526== Content-Type: multipart/alternative; boundary="0-638175997-1100949926=:21818" --0-638175997-1100949926=:21818 Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA13950 Content-Transfer-Encoding: quoted-printable Hi, I=92m interested to cooperative caching in on demand mobile ad hoc networ= ks. Obviously, the performances offered by such approach. If there=92s an= y document speaking about this subject, please send it to me. Thanks. =09 --------------------------------- Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo de stockage ! Cr=E9ez votre Yahoo! Mail Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveau= t=E9s pour dialoguer instantan=E9ment avec vos amis.T=E9l=E9chargez GRATU= ITEMENT ici ! --0-638175997-1100949926=:21818 Content-Type: text/html; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id GAA13950 Content-Transfer-Encoding: quoted-printable

Hi,

I=92m interested to cooperative caching in on demand mobile ad hoc n= etworks. Obviously, the performances offered by such approach. If there=92= s any document speaking about this subject, please send it to me. Thanks.=

Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo= de stockage !
Cr=E9ez votre Yahoo! Mail

Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveaut=E9s pour dialoguer instantan=E9ment a= vec vos amis. T=E9l=E9chargez GRATUITEMENT ici ! --0-638175997-1100949926=:21818-- --===============1043117526== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1043117526==-- From manet-bounces@ietf.org Sat Nov 20 11:04:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03406 for ; Sat, 20 Nov 2004 11:04:43 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVXmG-00085o-4h for manet-web-archive@ietf.org; Sat, 20 Nov 2004 11:07:56 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVXbD-0007GM-F7; Sat, 20 Nov 2004 10:56:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVXWQ-0006SG-TE for manet@megatron.ietf.org; Sat, 20 Nov 2004 10:51:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02501 for ; Sat, 20 Nov 2004 10:51:31 -0500 (EST) Received: from vega.otenet.gr ([195.170.0.32] ident=OTEnet-mail-system) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVXZR-0007os-0h for manet@ietf.org; Sat, 20 Nov 2004 10:54:44 -0500 Received: from [212.205.247.132] (athe530-e132.otenet.gr [212.205.247.132]) by vega.otenet.gr (8.13.1/8.13.1/Debian-16.Otenet-1) with ESMTP id iAKFpPXd009346; Sat, 20 Nov 2004 17:51:26 +0200 Message-ID: <419F6809.6060005@aueb.gr> Date: Sat, 20 Nov 2004 17:51:37 +0200 From: Sergios Soursos User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gadri Moez Subject: Re: [manet] Cooperative Caching References: <20041120111600.33240.qmail@web25105.mail.ukl.yahoo.com> In-Reply-To: <20041120111600.33240.qmail@web25105.mail.ukl.yahoo.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by vega.otenet.gr id iAKFpPXd009346 X-Spam-Score: 2.9 (++) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sergios Soursos List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 2.9 (++) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Content-Transfer-Encoding: quoted-printable u can find an interesting paper at the following url: http://www.cse.psu.edu/~gcao/paper/yin/infocom04.pdf to be true, i haven't found any more papers on this subject ;-) sergios Gadri Moez wrote: > Hi, >=20 > I=92m interested to cooperative caching in on demand mobile ad hoc=20 > networks. Obviously, the performances offered by such approach. If=20 > there=92s any document speaking about this subject, please send it to m= e. >=20 > Thanks. >=20 > -----------------------------------------------------------------------= - > Cr=E9ez gratuitement votre Yahoo! Mail avec *100 Mo de stockage !* > Cr=E9ez votre Yahoo! Mail=20 > >=20 > *Le nouveau Yahoo! Messenger est arriv=E9 !* D=E9couvrez toutes les=20 > nouveaut=E9s pour dialoguer instantan=E9ment avec vos amis. T=E9l=E9cha= rgez=20 > GRATUITEMENT ici !=20 > =20 >=20 >=20 >=20 > -----------------------------------------------------------------------= - >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Nov 21 00:16:10 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA26551 for ; Sun, 21 Nov 2004 00:16:10 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVk8I-0006HS-BO for manet-web-archive@ietf.org; Sun, 21 Nov 2004 00:19:30 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVk2E-0005xL-Ea; Sun, 21 Nov 2004 00:13:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVjse-0003nL-GC for manet@megatron.ietf.org; Sun, 21 Nov 2004 00:03:20 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25572 for ; Sun, 21 Nov 2004 00:03:17 -0500 (EST) From: erinninn@comp.nus.edu.sg Received: from x86unx3.comp.nus.edu.sg ([137.132.80.24]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVjvo-00062G-Ey for manet@ietf.org; Sun, 21 Nov 2004 00:06:37 -0500 Received: from e500d.comp.nus.edu.sg (e500d.comp.nus.edu.sg [137.132.90.69]) by x86unx3.comp.nus.edu.sg (8.9.1-20030924/8.9.1) with SMTP id NAA09510; Sun, 21 Nov 2004 13:02:43 +0800 (GMT-8) Received: from se11.comp.nus.edu.sg(137.132.80.19) by e500d.comp.nus.edu.sg via csmap id 181f8d72_3b7b_11d9_8fb7_0030482985c3_18921; Sun, 21 Nov 2004 13:06:25 +0800 (SGT) Received: (from http@localhost) by se11.comp.nus.edu.sg (8.12.10+Sun/8.12.5) id iAL52guf011576; Sun, 21 Nov 2004 13:02:42 +0800 (SGT) X-Authentication-Warning: se11.comp.nus.edu.sg: http set sender to erinninn@comp.nus.edu.sg using -f Received: from cm89.sigma222.maxonline.com.sg ([218.212.222.89]) (proxying for 218.212.222.89) (SquirrelMail authenticated user erinninn); by mysoc.nus.edu.sg with HTTP; Sun, 21 Nov 2004 13:02:42 +0800 (SGT) Message-ID: <3508.218.212.222.89.1101013362.squirrel@218.212.222.89> In-Reply-To: <20041120112526.21846.qmail@web25110.mail.ukl.yahoo.com> References: <20041120112526.21846.qmail@web25110.mail.ukl.yahoo.com> Date: Sun, 21 Nov 2004 13:02:42 +0800 (SGT) Subject: Re: [manet] cooperative caching To: "Gadri Moez" User-Agent: SquirrelMail/1.4.3 X-Mailer: SquirrelMail/1.4.3 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by se11.comp.nus.edu.sg id iAL52guf011576 X-Spam-Score: 0.3 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: quoted-printable Hi I wonder will this paper help? Alvin Valera, Winston Khoon Guan Seah, S. V. Rao: Cooperative Packet Caching and Shortest Multipath Routing in Mobile Ad hoc Networks. INFOCOM 2003 regards inn inn > Hi, > > I=92m interested to cooperative caching in on demand mobile ad hoc netw= orks. > Obviously, the performances offered by such approach. If there=92s any > document speaking about this subject, please send it to me. Thanks. > > > > --------------------------------- > Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo de stockage ! > Cr=E9ez votre Yahoo! Mail > > Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouve= aut=E9s > pour dialoguer instantan=E9ment avec vos amis.T=E9l=E9chargez GRATUITEM= ENT ici > !_______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Nov 21 12:38:29 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08605 for ; Sun, 21 Nov 2004 12:38:29 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVvil-0007jL-BI for manet-web-archive@ietf.org; Sun, 21 Nov 2004 12:41:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVvce-0004qi-Nt; Sun, 21 Nov 2004 12:35:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVvbX-0004Xa-Ux for manet@megatron.ietf.org; Sun, 21 Nov 2004 12:34:28 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08411 for ; Sun, 21 Nov 2004 12:34:25 -0500 (EST) Received: from ms-smtp-01-lbl.southeast.rr.com ([24.25.9.100] helo=ms-smtp-01-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CVveo-0007eh-Nk for manet@ietf.org; Sun, 21 Nov 2004 12:37:52 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-01-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iALHYIKj016861; Sun, 21 Nov 2004 12:34:20 -0500 (EST) From: "Christopher P. Rigano" To: "'Christopher P. Rigano'" , , Date: Sun, 21 Nov 2004 12:34:02 -0500 Message-ID: <006a01c4cff0$54037570$0300a8c0@CPQ73745201364> 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.2900.2180 In-reply-to: <004401c4cbeb$a15853d0$0300a8c0@CPQ73745201364> X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.1 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: 7bit Subject: [manet] RE: [Sipforum-discussion] continuing SIP bearer in Mobile environments X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7bit I am doing some research with MANETs and Wireless using SIP to establish video streams in Mpeg4. Are there any ways to maintain packet flow when crossing cells/domains other than MIP? How about the via field? Any ideas? Thanks mates! Chris ------ To unsubscribe from the Sipforum-discussion mailing list visit https://mbox.su.se/mailman/listinfo/sipforum-discussion _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Nov 21 17:15:55 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28284 for ; Sun, 21 Nov 2004 17:15:55 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW03G-0004VN-M6 for manet-web-archive@ietf.org; Sun, 21 Nov 2004 17:19:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVzxG-0001Ot-5u; Sun, 21 Nov 2004 17:13:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CVzws-0001En-IF for manet@megatron.ietf.org; Sun, 21 Nov 2004 17:12:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28094 for ; Sun, 21 Nov 2004 17:12:44 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.193]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW00B-0004Si-TQ for manet@ietf.org; Sun, 21 Nov 2004 17:16:13 -0500 Received: by rproxy.gmail.com with SMTP id r35so188717rna for ; Sun, 21 Nov 2004 14:12:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=AaRpxVlYPCnEr1cC6u+HTV0g9wixbe/F10kYHIt90d4/abntKb6R03W9Sfi9xAxFYD0N7dQISTDLgO04J1SUaoBNqw1Okbq8kkiTjz8X+l5waMEnAfBPSFuYTNsm9lnP5VzqrSdaQLijbjwh4Sqd3Sc94xYI85w7tEV4ljLAr4g= Received: by 10.38.13.70 with SMTP id 70mr578387rnm; Sun, 21 Nov 2004 14:12:44 -0800 (PST) Received: by 10.39.1.55 with HTTP; Sun, 21 Nov 2004 14:12:44 -0800 (PST) Message-ID: <496ed12904112114129349df1@mail.gmail.com> Date: Sun, 21 Nov 2004 17:12:44 -0500 From: Prithwish Basu To: manet@ietf.org In-Reply-To: <496ed1290411211402795d15b1@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <6.0.0.22.2.20041121163941.01eadeb8@localhost> <496ed1290411211402795d15b1@mail.gmail.com> X-Spam-Score: 0.9 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: 7bit Subject: [manet] MobiQuitous 2005 - Call for Workshop Proposals X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Prithwish Basu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: 7bit Our sincere apologies if you receive multiple copies of this mailing! ************************************************************ *** MOBIQUITOUS 2005: CALL FOR WORKSHOP PROPOSALS *** ************************************************************ Dear Colleagues, We are already actively preparing for MobiQuitous 2005 (to be held in San Diego, CA in July 2005), the Second Annual International Conference on Mobile Ubiquitous Systems: Networking and Services. We are planning to host 4 workshops on the day following the main conference. Please visit http://mobiquitous.org for details about MQ05. We are kindly soliciting proposals for workshops to be held in conjunction with MQ05. We hope that you can contribute by proposing to organize a workshop on one of the many emerging, specific themes and topics in the field of networking and services for mobile and ubiquitous systems. The pdf version can be downloaded from the following URL: http://mobiquitous.org/workshop.html Workshop proposals should be submitted via e-mail to the Workshops co-chairs (Stefano Basagni: basagni@ece.neu.edu, and Prithwish Basu: pbasu@bbn.com) by December 17 2004. Best regards, Stefano and Prithwish _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Nov 21 19:10:21 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07346 for ; Sun, 21 Nov 2004 19:10:21 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW1q3-0006g4-Fg for manet-web-archive@ietf.org; Sun, 21 Nov 2004 19:13:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CW1id-0000Lh-BW; Sun, 21 Nov 2004 19:06:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CW1hv-0000DG-JV for manet@megatron.ietf.org; Sun, 21 Nov 2004 19:05:27 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07033 for ; Sun, 21 Nov 2004 19:05:24 -0500 (EST) Received: from aragorn.bbn.com ([128.33.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW1lG-0006Zq-0T for manet@ietf.org; Sun, 21 Nov 2004 19:08:55 -0500 Received: from bbn.com (central.bbn.com [128.89.96.49]) by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id iAM04nje026755; Sun, 21 Nov 2004 19:04:49 -0500 (EST) Message-Id: <200411220004.iAM04nje026755@aragorn.bbn.com> To: Gadri Moez Subject: Re: [manet] cooperative caching Date: Sun, 21 Nov 2004 19:04:47 -0500 From: Mitchell Tasman X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Gadri, Although less directly relevant to your query than the paper Sergio cites below, you may find the following to be of interest: http://www.sigmobile.org/phd/9495/theses/tasman.pdf Mitch Sergio Soursos wrote: > u can find an interesting paper at the following url: > http://www.cse.psu.edu/~gcao/paper/yin/infocom04.pdf > to be true, i haven't found any more papers on this subject ;-) > sergios In reply to Gadri Moez's query: >> Hi, >> >> I'm interested to cooperative caching in on demand mobile ad hoc >> networks. Obviously, the performances offered by such approach. If >> there's any document speaking about this subject, please send it to me. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Nov 21 19:43:21 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10760 for ; Sun, 21 Nov 2004 19:43:21 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW2Lz-0007Pt-Ru for manet-web-archive@ietf.org; Sun, 21 Nov 2004 19:46:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CW2Fi-0006En-Uf; Sun, 21 Nov 2004 19:40:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CW2Ez-00065V-Dc for manet@megatron.ietf.org; Sun, 21 Nov 2004 19:39:37 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10119 for ; Sun, 21 Nov 2004 19:39:34 -0500 (EST) Message-Id: <200411220039.TAA10119@ietf.org> Received: from ocean.ise.eng.osaka-u.ac.jp ([133.1.172.134]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CW2IK-0007GA-8G for manet@ietf.org; Sun, 21 Nov 2004 19:43:05 -0500 Received: (qmail 14454 invoked from network); 22 Nov 2004 09:38:38 +0900 Received: from unknown (HELO localhost) (127.0.0.1) by 0 with SMTP; 22 Nov 2004 09:38:38 +0900 Date: Mon, 22 Nov 2004 09:38:34 +0900 From: Takahiro Hara X-Mailer: EdMax Ver2.85.5F MIME-Version: 1.0 To: moezadhoc@yahoo.fr Subject: Fwd: Re: [manet] cooperative caching Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit Hi Gadri, Some of my works may be relevant to your query. Related publicatios are listed below: --takahiro --------------------------------------------------- T. Hara: "Effective Replica Allocation in Ad Hoc Networks for Improving Data Accessibility", Proc. of IEEE Infocom 2001, Anchorage, Alaska, U.S.A., Vol.3, pp.1568-1576 (Apr. 2001). T. Hara: "Cooperative Caching by Mobile Clients in Push-based Information Systems", Proc. of ACM Int'l Conf. on Information and Knowledge Management (ACM CIKM'02), McLean, VA, U.S.A., pp.186-193 (Nov. 2002). T. Hara: "Replica Allocation Methods in Ad Hoc Networks with Data Update", ACM-Kluwer Journal on Mobile Networks and Applications (MONET), Vol.8, No.4, pp.343-354 (Aug. 2003). H. Hayashi, T. Hara, and S. Nishio: "Cache Invalidation for Updated Data in Ad Hoc Networks", Proc. of Int'l Conf. on Cooperative Information Systems (CoopIS'03), Sicily, Italy, pp.516-535 (Nov. 2003). T. Hara, N. Murakami, and S. Nishio: "Replica Allocation for Correlated Data Items in Ad-Hoc Sensor Networks", ACM SIGMOD Record, Vol.33, No.1, pp.38-43 (Mar. 2004). H. Hayashi, T. Hara, and S. Nishio: "Replica Allocation Considering Data Update Intervals in Ad Hoc Networks", Proc. of IFIP/IEEE Int'l Conf. on Mobile and Wireless Communication Networks (MWCN 2004), Paris, France, pp.131-142 (Oct. 2004). Mitchell Tasman wrote: > > Subject: Re: [manet] cooperative caching > Date: Sun, 21 Nov 2004 19:04:47 -0500 > From: Mitchell Tasman > To: Gadri Moez > Cc: manet@ietf.org > > Gadri, > > Although less directly relevant to your query than the paper Sergio > cites below, you may find the following to be of interest: > > http://www.sigmobile.org/phd/9495/theses/tasman.pdf > > Mitch > > Sergio Soursos wrote: > > u can find an interesting paper at the following url: > > http://www.cse.psu.edu/~gcao/paper/yin/infocom04.pdf > > to be true, i haven't found any more papers on this subject ;-) > > sergios > > In reply to Gadri Moez's query: > >> Hi, > >> > >> I'm interested to cooperative caching in on demand mobile ad hoc > >> networks. Obviously, the performances offered by such approach. If > >> there's any document speaking about this subject, please send it to me. > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 22 00:19:21 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA03159 for ; Mon, 22 Nov 2004 00:19:21 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW6f8-0004MQ-9q for manet-web-archive@ietf.org; Mon, 22 Nov 2004 00:22:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CW6ZC-00075V-Si; Mon, 22 Nov 2004 00:16:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CW6Vv-0006DK-Ky for manet@megatron.ietf.org; Mon, 22 Nov 2004 00:13:23 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02461 for ; Mon, 22 Nov 2004 00:13:21 -0500 (EST) Received: from mail.icu.ac.kr ([210.107.128.19] helo=icu.ac.kr) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW6ZI-0004DX-VT for manet@ietf.org; Mon, 22 Nov 2004 00:16:54 -0500 Received: from doggy (Debian-exim@v85-109.icu.ac.kr [220.69.185.109]) by icu.ac.kr (8.12.10/8.12.8) with ESMTP id iAM54Lj7022274 for ; Mon, 22 Nov 2004 14:04:22 +0900 (KST) Received: from newcat by doggy with local (Exim 4.34) id 1CW6X9-0006iS-3A for manet@ietf.org; Mon, 22 Nov 2004 14:14:39 +0900 Date: Mon, 22 Nov 2004 14:14:34 +0900 From: YangWoo Ko To: manet@ietf.org Message-ID: <20041122051434.GB25652@doggy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6+20040907i X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Subject: [manet] MILCOM 2004 paper? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c I have failed to find an electronic copy of the Joe Macker's MILCOM 2004 paper mentioned at last IETF meeting. Can somebody give me a pointer? Or should I wait it be avaiable through IEEExplorer? -- /*------------------------------------------------ The ones doing their job, doing what they were meant to do, are invisible. -- Matrix Reloaded Ko, YangWoo / Searcher / newcat@icu.ac.kr ------------------------------------------------*/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 22 01:04:20 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05772 for ; Mon, 22 Nov 2004 01:04:20 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW7Mc-000579-Ta for manet-web-archive@ietf.org; Mon, 22 Nov 2004 01:07:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CW7HU-0004yB-V3; Mon, 22 Nov 2004 01:02:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CW7DK-0004QI-EY for manet@megatron.ietf.org; Mon, 22 Nov 2004 00:58:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05476 for ; Mon, 22 Nov 2004 00:58:11 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.199]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW7Gh-00050p-Vs for manet@ietf.org; Mon, 22 Nov 2004 01:01:45 -0500 Received: by rproxy.gmail.com with SMTP id b11so222059rne for ; Sun, 21 Nov 2004 21:58:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=fJ4sbjiYdQO7JlRFOUEd10UnI7xaJK3SsNV4/07EAiojObJib8pO/IkXusYVJk0UTZYxAu3jvBn/S5AXBVYAbU0bTPGNm87/bOIyqlc61r9HwuHnr/tksbZ2jhK8LAgrfM189D8xSv3OtlKwsSpQ4CZp7+39PxKIZihQzk8Fb6Q= Received: by 10.38.59.47 with SMTP id h47mr702859rna; Sun, 21 Nov 2004 21:58:12 -0800 (PST) Received: by 10.38.59.13 with HTTP; Sun, 21 Nov 2004 21:58:12 -0800 (PST) Message-ID: <7b595408041121215843df401@mail.gmail.com> Date: Mon, 22 Nov 2004 10:58:12 +0500 From: "M. U. Saleem" To: Shubhranshu , manet@ietf.org Subject: Re: [manet] manet autoconf. In-Reply-To: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <01d601c4cd6e$8f695c80$185b024b@Shubhranshu> X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "M. U. Saleem" List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Hello, I am working on this subject, so would like to be part of this mailing list. -- M. Usman Saleem Software Engineer, NRL, COMSATS IT Center, ATD, Pk. http://nrl.ciit.net.pk http://usman.saleems.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 22 02:56:35 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28478 for ; Mon, 22 Nov 2004 02:56:35 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW97H-0007Da-WD for manet-web-archive@ietf.org; Mon, 22 Nov 2004 03:00:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CW8zr-0007A3-8U; Mon, 22 Nov 2004 02:52:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CW8xM-0006it-01 for manet@megatron.ietf.org; Mon, 22 Nov 2004 02:49:52 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27640 for ; Mon, 22 Nov 2004 02:49:50 -0500 (EST) Received: from csiges9.insa-lyon.fr ([134.214.79.200] helo=mail.insa-lyon.fr) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CW90k-00071r-DO for manet@ietf.org; Mon, 22 Nov 2004 02:53:23 -0500 Received: from localhost (localhost [127.0.0.1]) by mail.insa-lyon.fr (Postfix) with ESMTP id D4E3F4FFF1 for ; Mon, 22 Nov 2004 08:49:01 +0100 (CET) Received: from mail.insa-lyon.fr ([127.0.0.1]) by localhost (csiges9.insa-lyon.fr [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 11553-01-6 for ; Mon, 22 Nov 2004 08:48:47 +0100 (CET) Received: from inrialpes.fr (ares-guerin-1.insa-lyon.fr [134.214.144.150]) by mail.insa-lyon.fr (Postfix) with ESMTP id 6D3294FD67 for ; Mon, 22 Nov 2004 08:48:47 +0100 (CET) Message-ID: <41A199A7.9010407@inrialpes.fr> Date: Mon, 22 Nov 2004 08:47:51 +0100 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: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new at insa-lyon.fr X-Spam-Score: 0.0 (/) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 Content-Transfer-Encoding: quoted-printable Subject: [manet] 1st CFP - Med-Hoc-Net 2005 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433 Content-Transfer-Encoding: quoted-printable 4th Mediterranean Workshop on Ad-Hoc Networks MED-HOC-NET 2005 Ile de Porquerolles, June 21-24, 2005 ------------------------------------------------------------ *First Call for papers* The fourth Med-Hoc-Net 2005 is a major annual international workshop in=20 the Mediterrnean region. It brings together researchers, technologists and visionaries=20 from academia, research labs, and industry, engineers and students to exchange, discuss and=20 share their experiences, new ideas and research about theoretical and practical aspects of ad-hoc = networking. Med-Hoc-Net 2005 will include presentations of theoretical and experimental achievements, innovative ad-hoc systems, prototyping efforts, case studies, and advancements in technology directly affecting ad-hoc networking and communications infrastructures. The papers solicited in Med-Hoc-Net 2005 cover a variety of topics=20 including but not limited to: - Implementations, testbeds, and prototypes, - Performance evaluation of ad-hoc network protocols through simulations,= analysis, and measurements, - Metrology, Ad-Hoc network measurement Tools, - MAC protocols, scheduling, and radio resource sharing in ad hoc networks, - Power management and control, - Topology control, - Self-organization and network reconfiguration, - Unicast and multicast routing algorithms and protocols, - Energy-efficient communications in ad-hoc networks, - Transport layer protocols for multi-hop networks, - Resource discovery and management, - Protocols for QoS support in ad-hoc networks, - Call admission and traffic shaping policies for ad-hoc networks, - Multimedia location services, - Security in ad-hoc networks, - Fault tolerance and error recovery, - Algorithmic challenges in ad-hoc networks, - Large scale ad-hoc networks, - Interconnection between ad hoc and wired networks, - Sensor networks: applications and protocols. After Sardinia (Italy), Mahdia (Tunisia) and Bodrum (Turkey), this year the workshop will take place in another beautiful spot on the Mediterranean Sea: Ile de Porquerolles (France). Steering Committee: Farouk Kamoun (ENSI, Tunisia) Mario Gerla (UCLA, USA) Guy Pujolle (LIP6, France) Khaldoun Al Agha (LRI, France) Giovanni Pau (UCLA, USA) =20 Program Chair: Isabelle Gu=E9rin Lassous (INRIA, France) Program Committee: Ian F. AKYILDIZ (Georgia Institute of Technology, USA) Khaldoun AL AGHA (LRI, France) Christian BECKER (University of Stuttgart, Germany) Brahim BENSAOU (Hong Kong University of science and technology, Hong Kong= ) Bharat K BHARGAVA (Purdue University, USA) Azzedine BOUKERCHE (University of Ottawa, Canada) Andrew T. CAMPBELL (Columbia University, USA) Rachel CARDELL-OLIVER (University of Western Australia, Australia) E. CAYIRCI (Istanbul Technical University, Turkey) Andrea CLEMENTI (University Roma II, Italy) Marco CONTI (CNR, Italy) Laurie CUTHBERT (University of London, UK) Bertrand.DUCOURTHIAL (UTC, France) Mario GERLA (UCLA, USA) Silvia GIORDANO (University of Applied Science, Switzerland) Stephen HAILES (University College London, UK) Farouk KAMOUN (ENSI, Tunisia) P. R. KUMAR (University of Illinois, Urbana-Champaign, USA) Pietro MANZONI (Universidad Politecnica de Valencia, Spain) Pasc ale MINET (INRIA, France) Sotiris NIKOLETSEAS (CTI/Univ. of Patras, Greece)=20 Giovanni PAU (UCLA, USA) Guy PUJOLLE (LIP6, France) Laurent REYNAUD (FT R&D, France) Christian PREHOFER (DoCoMo Euro-Labs, Germany) David SYMPLOT-RYL (University of Lille, France) Isabela SIQUEIRA (Federal University of Minas Gerais, Brazil) Patrick THIRAN (EPFL, Switzerland) Stavros TOUMPIS (Vienna Telecommunications Research Center, Austria) Christian TSCHUDIN (University of Basel, Switzerland) Guillaume VIVIER (Motorola, France)=20 Stefan WEBER (Trinity College Dublin, Ireland) Vincent W.S. WONG (University of British Columbia, Canada) Hiroyuki YOMO (Aalborg University, Danemark) Franco ZAMBONELLI (Universita' di Modena e Reggio Emilia, Italy) =20 Authors are invited to submit electronically original contributions in=20 the conference themes and related topics. Papers should not be longer than 12 pages. All=20 submitted papers will be reviewed and evaluated on the basis of relevance, originality, technical = quality and clarity. Accepted papers will be included in the conference proceedings. The=20 official workshop oral and written language is English. Details regarding the paper format and the submission process will be posted at the conference web site. Paper Submission Deadlines Full Paper Electronic Submission : 11 March 2005 Notification of acceptance/Rejection : 15 April 2005 Camera ready submission of full papers: 13 May 2005 ------------------------------------------------------------------------ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 09:17:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13013 for ; Tue, 23 Nov 2004 09:17:43 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWbXx-0006lw-NY for manet-web-archive@ietf.org; Tue, 23 Nov 2004 09:21:33 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWbLq-0003P8-TW; Tue, 23 Nov 2004 09:09:02 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWbIn-0002ok-RG for manet@megatron.ietf.org; Tue, 23 Nov 2004 09:05:54 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12304 for ; Tue, 23 Nov 2004 09:05:51 -0500 (EST) Received: from mn-2.atm.tut.fi ([130.230.52.147] helo=mn-2) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWbMS-0005Ag-Jw for manet@ietf.org; Tue, 23 Nov 2004 09:09:41 -0500 Received: from mark by mn-2 with local (Exim 3.36 #1 (Debian)) id 1CWbH2-0001Yw-00; Tue, 23 Nov 2004 16:04:04 +0200 From: Mark Borst To: manet@ietf.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 23 Nov 2004 16:04:02 +0200 Message-Id: <1101218642.5129.17.camel@mn-2> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 7bit Cc: sami.peltotalo@cs.tut.fi, jani.peltotalo@cs.tut.fi Subject: [manet] Multicast: MAODV and ODMRP X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: 7bit Hallo all We have been doing some research on multicasting in MANETs. Apparently multicasting is not in the charter of the MANET group, but we could not find any other group that has information on it, so we ask here anyway. The first question is: is there any other place, except the MANET group, that discusses MANETs and multicasting issues? It seems that MAODV and ODMRP are the most important multicasting protocols for MANETs at the moment. However, we cannot find sufficient information about them. On ODMRP we found the old draft-ietf-manet-odmrp-04, and the later draft-yi-manet-odmrp-00, both expired. Furthermore we found some papers on the protocol, but those didn't contain sufficient information for us, just as the drafts. They completely skip the matter of mesh creation (it just creates a lot of trees, that are further independent) and link failure recovery. Or if they are sufficiently specified, we cannot find the description of it. We are aware that people have simulated it, which implies they found sufficient information to solve these questions. Could you shine some light on this matter? Another question, of more general nature, is: can you give some comments on multicasting versus broadcasting/flooding? It seems that flooding is actually a good alternative to multicasting under certain scenarios, so is multicasting then still viable? Thanks, -- Mark Borst Researcher Network and Protocols Group Tampere University of Technology, Finland _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 10:07:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18431 for ; Tue, 23 Nov 2004 10:07:04 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWcJi-0004f9-Rc for manet-web-archive@ietf.org; Tue, 23 Nov 2004 10:10:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWc8Y-0006lx-MB; Tue, 23 Nov 2004 09:59:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWbw0-0003rA-P5 for manet@megatron.ietf.org; Tue, 23 Nov 2004 09:46:24 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15714 for ; Tue, 23 Nov 2004 09:46:22 -0500 (EST) Received: from sunup.cs.cornell.edu ([128.84.96.116]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWbzf-00022B-QZ for manet@ietf.org; Tue, 23 Nov 2004 09:50:13 -0500 Received: from sundial.cs.cornell.edu (sundial.cs.cornell.edu [128.84.96.115]) by sunup.cs.cornell.edu (8.11.7-20031020/8.11.7/R-3.17) with ESMTP id iANEkMG19664; Tue, 23 Nov 2004 09:46:22 -0500 (EST) Received: from kwalsh4158.cs.cornell.edu (dhcp98-214.cs.cornell.edu [128.84.98.214]) by sundial.cs.cornell.edu (8.11.7-20031020/8.11.7/M-3.21) with ESMTP id iANEkLb10152; Tue, 23 Nov 2004 09:46:21 -0500 (EST) Message-Id: <5.2.1.1.0.20041123094320.03be2ae8@popsrv.cs.cornell.edu> X-Sender: kwalsh@popsrv.cs.cornell.edu X-Mailer: QUALCOMM Windows Eudora Version 5.2.1 Date: Tue, 23 Nov 2004 09:46:19 -0500 To: Parag Goswami From: Kevin Walsh Subject: Re: [manet] need help on tools..... In-Reply-To: <78e4c4dc0411171950761c181c@mail.gmail.com> References: <20041117100658.7055.qmail@web90107.mail.scd.yahoo.com> <20041117100658.7055.qmail@web90107.mail.scd.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Content-Transfer-Encoding: quoted-printable If you are considering using NS-2, you might be interested in SNS, a=20 modified version of NS-2 that runs quite a bit faster than the ordinary=20 ns-2, and can simulate much larger networks. You can get more information=20 and download the software at http://www.cs.cornell.edu/People/egs/sns/. Good Luck, Kevin W. At 07:50 PM 11/17/2004 -0800, Pankaj Godbole wrote: >Hi Parag, > >If you haven't already done so, you could take a look at this paper >which compares the performance of the three popular simulators: NS-2, >Glomosim and OPNET in simulating a simple flooding algorithm. >http://lsewww.epfl.ch/Documents/acrobat/CSA02b.pdf > >Regards, >Pankaj Godbole. > > >On Wed, 17 Nov 2004 02:06:58 -0800 (PST), Parag Goswami > wrote: > > > > Hi all, > > I am an undergraduate student of Computer science and engineering.I need > > help on the various tools that can be used for the simulation purpose in= my > > project. Please explain me these tools NS-2 and OPNET. I have to choose= one > > from these two tools for my simulation purpose.Please provide= information > > about : > > 1. Which one is better? > > 2. How do they work both OPNET and NS-2 ? > > > > Look further to recieve soon response. > > > > Best Regards, > > Parag Goswami > > http://www.geocities.com/paragboom2k > > > > ________________________________ > > Do you Yahoo!? > > The all-new My Yahoo! =AD Get yours free! > > > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > > > > > > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 10:42:02 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22685 for ; Tue, 23 Nov 2004 10:42:02 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWcrY-0001IK-SV for manet-web-archive@ietf.org; Tue, 23 Nov 2004 10:45:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWcjP-0004Ak-0N; Tue, 23 Nov 2004 10:37:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWcV1-0001EQ-QV for manet@megatron.ietf.org; Tue, 23 Nov 2004 10:22:36 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20649 for ; Tue, 23 Nov 2004 10:22:33 -0500 (EST) Received: from cheviot5.ncl.ac.uk ([128.240.233.122] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWcYi-0006y8-15 for manet@ietf.org; Tue, 23 Nov 2004 10:26:24 -0500 Received: from [128.240.149.114] (deerbook.ncl.ac.uk [128.240.149.114]) by cheviot5.ncl.ac.uk (8.12.11/8.12.10) with ESMTP id iANFLZJ1009711; Tue, 23 Nov 2004 15:21:35 GMT In-Reply-To: <1101218642.5129.17.camel@mn-2> References: <1101218642.5129.17.camel@mn-2> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <5C5E0E3E-3D63-11D9-B16C-000A9575BD30@ncl.ac.uk> Content-Transfer-Encoding: 7bit From: Einar Vollset Subject: Re: [manet] Multicast: MAODV and ODMRP Date: Tue, 23 Nov 2004 15:21:34 +0000 To: Mark Borst X-Mailer: Apple Mail (2.619) X-Newcastle-MailScanner-Information: Please contact Postmaster@newcastle.ac.uk for more information X-Newcastle-MailScanner: Found to be clean X-Newcastle-MailScanner-From: einar.vollset@ncl.ac.uk X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Content-Transfer-Encoding: 7bit Cc: sami.peltotalo@cs.tut.fi, manet@ietf.org, jani.peltotalo@cs.tut.fi X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2 Content-Transfer-Encoding: 7bit > Another question, of more general nature, is: can you give some > comments > on multicasting versus broadcasting/flooding? It seems that flooding is > actually a good alternative to multicasting under certain scenarios, so > is multicasting then still viable? Broadcasting is not the same as flooding. Broadcasting is a communication primitive (1-ALL), where as flooding is a (simple) mechanism (re-transmit immediately after the first time I receive a packet) which attempts to provide the broadcast primitive. In fact, as broadcasting is a special case of multicasting (make the group contain ALL nodes in the system and you've got broadcasting), you could use any multicasting protocol to do broadcast. I guess the question you're really asking is if it's worth constructing routing structures (such as ODMRP's mesh or MAODV's tree) when a simple flooding approach does quite well? I think there is much to be said for attempting to lower the transmission overhead associated with simple flooding, though as you observe, there are cases when flooding does as well as a routing structure based approach, both in terms of overhead and number of successful recipients (typically high mobility scenarios) That being said, flooding is not a panacea when it comes to ensuring a broadcast is _reliable_. A simple example of when flooding fails to achieve this is when the network is transiently partitioned at the time the flooding is initiated (an extreme version of when such partitioning is considered "normal" is what the guys working on delay tolerant networking (DTNs) are interested in: http://www.dtnrg.org/ (IRTF DTN group)) There is also some work attempting to provide more optimized protocols than flooding (higher reception rate, lower overheads), e.g. - I. Stojmenovic, M. Seddigh, J. Zunic, "Dominating sets and neighbor elimination based broadcasting algorithms in wireless networks" - J. Lipman, P. Boustead, and J. Chicharo, "Reliable optimized flooding in ad hoc networks" - W. Lou and J. Wu, "Double Covered Broadcast (DCB): A simple reliable broadcast algorithm in manets" or the probabilistic approaches, e.g.: - J. Luo, P.T. Eugster, and J.-P. Hubaux, "Route Driven Gossip: Probabilistic reliable multicast in ad-hoc networks" - R. Chandra, V. Ramasubramanian, K. P. Birman, "Anonymous Gossip: Improving Multicast Reliability in Mobile Ad-Hoc Networks" - D. Cooper, I. Mitrani and P. Ezhilchelvan, "High Coverage Broadcasting for Mobile Ad-hoc Networks" However, if you want to absolutely, positively 100% ensure that all nodes in a group get a given message, you have to turn to deterministically reliable protocols instead. E.g. : - T. Gopalsamy, M. Singhal, D.Panda, and P. Sadayapan, "A reliable multicast algorithm for mobile ad-hoc networks" - K. Tang, K. Obraczka, S.J. Lee and M. Gerla: " Reliable, congestion controlled multicast transport in multimedia multihop networks" - E. Pagani and G.P. Rossi," Reliable Broadcast in Mobile Multihop Packets Networks" ..which is my current research interest. That was a more general answer to a more general question.. :-) Cheers, Einar ---------------------------------------- Einar Vollset PhD Student School of Computing Science University of Newcastle, UK http://vollset.org ----------------------------------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 10:52:49 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA24079 for ; Tue, 23 Nov 2004 10:52:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWd1z-0002vH-O0 for manet-web-archive@ietf.org; Tue, 23 Nov 2004 10:56:41 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWcn8-000525-Gg; Tue, 23 Nov 2004 10:41:18 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWcin-0003xF-Ll for manet@megatron.ietf.org; Tue, 23 Nov 2004 10:36:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22050 for ; Tue, 23 Nov 2004 10:36:46 -0500 (EST) Received: from web88009.mail.re2.yahoo.com ([206.190.37.196]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CWcmT-0000U5-Er for manet@ietf.org; Tue, 23 Nov 2004 10:40:37 -0500 Message-ID: <20041123153611.43273.qmail@web88009.mail.re2.yahoo.com> Received: from [66.185.84.77] by web88009.mail.re2.yahoo.com via HTTP; Tue, 23 Nov 2004 10:36:11 EST Date: Tue, 23 Nov 2004 10:36:11 -0500 (EST) From: jixiu Han To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: [manet] Broadcast simulation X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2041430306==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 --===============2041430306== Content-Type: multipart/alternative; boundary="0-417691963-1101224171=:42888" --0-417691963-1101224171=:42888 Content-Type: text/plain; charset=us-ascii Hi Folks, Does someone know how to send broadcast message in MANET, for example use DSR as the routing protocol? Regards, sally --0-417691963-1101224171=:42888 Content-Type: text/html; charset=us-ascii
Hi Folks,
 
Does someone know how to send broadcast message in MANET, for example use DSR as the routing protocol?
 
 
Regards,
 
sally
--0-417691963-1101224171=:42888-- --===============2041430306== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2041430306==-- From manet-bounces@ietf.org Tue Nov 23 11:44:02 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28815 for ; Tue, 23 Nov 2004 11:44:02 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWdpZ-0001QL-49 for manet-web-archive@ietf.org; Tue, 23 Nov 2004 11:47:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWdYl-0001qJ-4i; Tue, 23 Nov 2004 11:30:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWdVF-0000e5-47 for manet@megatron.ietf.org; Tue, 23 Nov 2004 11:26:53 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27248 for ; Tue, 23 Nov 2004 11:26:50 -0500 (EST) Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWdYv-0007TZ-8A for manet@ietf.org; Tue, 23 Nov 2004 11:30:42 -0500 Received: from smtp.um.es (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id EF4CE31512; Tue, 23 Nov 2004 17:26:14 +0100 (CET) Received: from correo.um.es (zape.um.es [155.54.212.102]) by smtp.um.es (Postfix) with ESMTP id C64B93147C; Tue, 23 Nov 2004 17:26:14 +0100 (CET) Received: from dif.um.es (dibulibu.um.es [155.54.1.250]) by correo.um.es (Postfix) with ESMTP id 21B9C5CC9; Tue, 23 Nov 2004 17:26:12 +0100 (MET) Message-ID: <41A3652D.1080603@dif.um.es> Date: Tue, 23 Nov 2004 17:28:29 +0100 From: "Pedro M. Ruiz" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030821 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Einar Vollset Subject: Re: [manet] Multicast: MAODV and ODMRP References: <1101218642.5129.17.camel@mn-2> <5C5E0E3E-3D63-11D9-B16C-000A9575BD30@ncl.ac.uk> In-Reply-To: <5C5E0E3E-3D63-11D9-B16C-000A9575BD30@ncl.ac.uk> X-Enigmail-Version: 0.76.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2 Content-Transfer-Encoding: 7bit Cc: sami.peltotalo@cs.tut.fi, manet@ietf.org, jani.peltotalo@cs.tut.fi X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 Content-Transfer-Encoding: 7bit Definitely a very good general answer... please let me add a very concrete appendix ;-) Regarding the viability of multicasting, you may find interesting the following paper which proposes enhancements to the mesh creation algorithm in ODMRP to lower the transmission overhead while maintining a high packet delivery ratio. You will see how it is possible to have high PDRs with high mobility at much lower data-overhead than flooding. Pedro M. Ruiz, Antonio F. Gomez-Skarmeta, "Mobility-Aware Mesh Construction Algorithm for Low Data-Overhead Multicast Ad Hoc Routing", to appear in Journal of Communications and Networks, Vol. 6, no. 4, December, 2004. Please, let me know if you need further information. The paper will be shortly available in my website: http://ants.dif.um.es/staff/pedrom/publications.html --Pedro Einar Vollset wrote: >> Another question, of more general nature, is: can you give some comments >> on multicasting versus broadcasting/flooding? It seems that flooding is >> actually a good alternative to multicasting under certain scenarios, so >> is multicasting then still viable? > > > Broadcasting is not the same as flooding. Broadcasting is a > communication primitive > (1-ALL), where as flooding is a (simple) mechanism (re-transmit > immediately after > the first time I receive a packet) which attempts to provide the > broadcast primitive. > > In fact, as broadcasting is a special case of multicasting (make the > group contain ALL > nodes in the system and you've got broadcasting), you could use any > multicasting > protocol to do broadcast. > > I guess the question you're really asking is if it's worth > constructing routing structures > (such as ODMRP's mesh or MAODV's tree) when a simple flooding approach > does > quite well? > I think there is much to be said for attempting to lower the > transmission overhead associated > with simple flooding, though as you observe, there are cases when > flooding does as > well as a routing structure based approach, both in terms of overhead > and number of > successful recipients (typically high mobility scenarios) > > That being said, flooding is not a panacea when it comes to ensuring a > broadcast is > _reliable_. A simple example of when flooding fails to achieve this is > when the network > is transiently partitioned at the time the flooding is initiated (an > extreme version of when > such partitioning is considered "normal" is what the guys working on > delay tolerant > networking (DTNs) are interested in: http://www.dtnrg.org/ (IRTF DTN > group)) > > There is also some work attempting to provide more optimized protocols > than flooding > (higher reception rate, lower overheads), e.g. > - I. Stojmenovic, M. Seddigh, J. Zunic, "Dominating sets and neighbor > elimination based broadcasting algorithms in wireless networks" > - J. Lipman, P. Boustead, and J. Chicharo, "Reliable optimized > flooding in ad hoc networks" > - W. Lou and J. Wu, "Double Covered Broadcast (DCB): A simple reliable > broadcast algorithm in manets" > > > or the probabilistic approaches, e.g.: > - J. Luo, P.T. Eugster, and J.-P. Hubaux, "Route Driven Gossip: > Probabilistic reliable multicast in ad-hoc networks" > - R. Chandra, V. Ramasubramanian, K. P. Birman, "Anonymous Gossip: > Improving Multicast Reliability in Mobile Ad-Hoc Networks" > - D. Cooper, I. Mitrani and P. Ezhilchelvan, "High Coverage > Broadcasting for Mobile Ad-hoc Networks" > > > However, if you want to absolutely, positively 100% ensure that all > nodes in a group get a given > message, you have to turn to deterministically reliable protocols > instead. E.g. : > > - T. Gopalsamy, M. Singhal, D.Panda, and P. Sadayapan, "A reliable > multicast algorithm for mobile ad-hoc networks" > - K. Tang, K. Obraczka, S.J. Lee and M. Gerla: " Reliable, congestion > controlled multicast transport in multimedia multihop networks" > - E. Pagani and G.P. Rossi," Reliable Broadcast in Mobile Multihop > Packets Networks" > > ..which is my current research interest. > > > That was a more general answer to a more general question.. :-) > > Cheers, > > Einar > > > ---------------------------------------- > Einar Vollset > PhD Student > School of Computing Science > University of Newcastle, UK > http://vollset.org > ----------------------------------------- > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 11:49:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29221 for ; Tue, 23 Nov 2004 11:49:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWduq-0001ss-Uo for manet-web-archive@ietf.org; Tue, 23 Nov 2004 11:53:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWdir-0004bo-6N; Tue, 23 Nov 2004 11:40:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWdY0-0001f8-De for manet@megatron.ietf.org; Tue, 23 Nov 2004 11:29:44 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27719 for ; Tue, 23 Nov 2004 11:29:41 -0500 (EST) Received: from pony1pub.arc.nasa.gov ([128.102.31.41]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWdbe-0007uM-51 for manet@ietf.org; Tue, 23 Nov 2004 11:33:33 -0500 Received: from mrcrab.nas.nasa.gov ([129.99.139.47] verified) by pony1pub.arc.nasa.gov (CommuniGate Pro SMTP 4.1.8) with ESMTP id 15179552 for manet@ietf.org; Tue, 23 Nov 2004 08:29:06 -0800 From: Jerry Toung To: manet@ietf.org Date: Tue, 23 Nov 2004 08:28:55 -0800 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411230828.55350.jtoung@arc.nasa.gov> X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit Subject: [manet] data link protocol for manet X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jtoung@arc.nasa.gov List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Good morning list, we are looking at other L2 protocols to implement and test. Beside 802.11 that everybody use with RF, what else is available? open source or publication. 802.11 is complicated for what we're doing in that it specifies both PHY and MAC layer. MAC layer only is enough. What's the simplest alternative to 802.11? thanks a lot. Jerry _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 14:07:22 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09244 for ; Tue, 23 Nov 2004 14:07:22 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWg4I-0003GZ-V8 for manet-web-archive@ietf.org; Tue, 23 Nov 2004 14:11:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWfuN-0004N1-Av; Tue, 23 Nov 2004 14:00:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWfqF-0003lt-A4 for manet@megatron.ietf.org; Tue, 23 Nov 2004 13:56:43 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08640 for ; Tue, 23 Nov 2004 13:56:41 -0500 (EST) Received: from smtp.andrew.cmu.edu ([128.2.10.81]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWftv-00025S-M9 for manet@ietf.org; Tue, 23 Nov 2004 14:00:34 -0500 Received: from DMALTZ.WV.CS.cmu.edu (DMALTZ.WV.CS.cmu.edu [128.237.240.184]) (user=dmaltz mech=KERBEROS_V4 (0 bits)) by smtp.andrew.cmu.edu (8.12.10/8.12.10) with ESMTP id iANIueEM003646; Tue, 23 Nov 2004 13:56:40 -0500 Date: Tue, 23 Nov 2004 13:56:44 -0500 From: Dave Maltz To: jtoung@arc.nasa.gov, manet@ietf.org Subject: Re: [manet] data link protocol for manet Message-ID: <185733560.1101218204@DMALTZ.WV.CS.cmu.edu> In-Reply-To: <200411230828.55350.jtoung@arc.nasa.gov> References: <200411230828.55350.jtoung@arc.nasa.gov> Originator-Info: login-token=Mulberry:01T5uLcLMI7NyVINrnmhsC36L4ApzVBhh9/vjlTwv++Q==; token_authority=postmaster@andrew.cmu.edu X-Mailer: Mulberry/3.0.2 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Content-Transfer-Encoding: 7bit --On Tuesday, November 23, 2004 8:28 AM -0800 Jerry Toung wrote: > we are looking at other L2 protocols to implement and test. > What's the simplest alternative to 802.11? CSMA/CA with ethernet framing is probably as simple as you can get (and it works pretty well!) We built the first version of the Monarch testbed using the original 900 MHz WaveLAN product from Lucent, which used pure CSMA/CA for floor control. Don't know if you can still find the hardware for sale in a store, but it's probably out there. I had a student write a CSMA/CA MAC module for ns-2. I don't recall which versions of the Monarch extensions it's in, or if it's been integrated into the mainline ns-2 distribution. The very first DSR tests were run using IBM diffuse infrared cards. I forget what the MAC was for those cards. Cheers, -dam _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 14:22:05 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10362 for ; Tue, 23 Nov 2004 14:22:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWgIX-0005EH-7x for manet-web-archive@ietf.org; Tue, 23 Nov 2004 14:25:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWg9H-0007YZ-TN; Tue, 23 Nov 2004 14:16:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWg5m-00070N-GN for manet@megatron.ietf.org; Tue, 23 Nov 2004 14:12:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09581 for ; Tue, 23 Nov 2004 14:12:44 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.193]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWg9U-00042T-VY for manet@ietf.org; Tue, 23 Nov 2004 14:16:37 -0500 Received: by rproxy.gmail.com with SMTP id a36so8102rnf for ; Tue, 23 Nov 2004 11:12:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=PDrYOOYCjwpdhSayxpnsaRdALTEidbMoCugaVSg9IY7Ccojv/IjHTx20sbr1lYNoO9gVBQFcGPYJiCpBDxbjgm/LFHqHixkk02ea+QvAMJbIpPMZVUz0/cRlfs5Jo5oWOlYvTvSpsdDNBdS5n8A32ZnUfvReEH6tCsk2xbCvtBw= Received: by 10.38.171.55 with SMTP id t55mr265402rne; Tue, 23 Nov 2004 11:12:45 -0800 (PST) Received: by 10.38.66.34 with HTTP; Tue, 23 Nov 2004 11:12:45 -0800 (PST) Message-ID: Date: Tue, 23 Nov 2004 14:12:45 -0500 From: Marshall Eubanks To: Mark Borst Subject: Re: [manet] Multicast: MAODV and ODMRP In-Reply-To: <1101218642.5129.17.camel@mn-2> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <1101218642.5129.17.camel@mn-2> X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Content-Transfer-Encoding: 7bit Cc: sami.peltotalo@cs.tut.fi, manet@ietf.org, jani.peltotalo@cs.tut.fi X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marshall Eubanks List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Content-Transfer-Encoding: 7bit Dear Mark; On Tue, 23 Nov 2004 16:04:02 +0200, Mark Borst wrote: > Hallo all > > We have been doing some research on multicasting in MANETs. Apparently > multicasting is not in the charter of the MANET group, but we could not > find any other group that has information on it, so we ask here anyway. > > The first question is: is there any other place, except the MANET group, > that discusses MANETs and multicasting issues? > MANET type networks have not been discussed in any depth in of the standard multicast WG (such as MBoneD), and as far as I can tell there is little knowledge of what's going on Ad Hoc networking in that community. If multicasting is a serious issue in Manet, I would suggest that the next MBoneD WG meeting in Minneapolis include some Manet presentations. This was done with MPLS LSP's with the idea of informing the community and limiting the amount of wheel re-creation. Regards Marshall Eubanks > It seems that MAODV and ODMRP are the most important multicasting > protocols for MANETs at the moment. However, we cannot find sufficient > information about them. > > On ODMRP we found the old draft-ietf-manet-odmrp-04, and the later > draft-yi-manet-odmrp-00, both expired. Furthermore we found some papers > on the protocol, but those didn't contain sufficient information for us, > just as the drafts. They completely skip the matter of mesh creation (it > just creates a lot of trees, that are further independent) and link > failure recovery. Or if they are sufficiently specified, we cannot find > the description of it. We are aware that people have simulated it, which > implies they found sufficient information to solve these questions. > Could you shine some light on this matter? > > Another question, of more general nature, is: can you give some comments > on multicasting versus broadcasting/flooding? It seems that flooding is > actually a good alternative to multicasting under certain scenarios, so > is multicasting then still viable? > > Thanks, > > -- > Mark Borst > Researcher > Network and Protocols Group > Tampere University of Technology, Finland > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 15:13:53 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18201 for ; Tue, 23 Nov 2004 15:13:53 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWh6f-0004Bz-Ny for manet-web-archive@ietf.org; Tue, 23 Nov 2004 15:17:46 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWguz-0005zm-OV; Tue, 23 Nov 2004 15:05:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWgiR-0006FV-Ba for manet@megatron.ietf.org; Tue, 23 Nov 2004 14:52:43 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13306 for ; Tue, 23 Nov 2004 14:52:41 -0500 (EST) Received: from pony1pub.arc.nasa.gov ([128.102.31.41]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWgm9-0000mj-Mk for manet@ietf.org; Tue, 23 Nov 2004 14:56:34 -0500 Received: from mrcrab.nas.nasa.gov ([129.99.139.47] verified) by pony1pub.arc.nasa.gov (CommuniGate Pro SMTP 4.1.8) with ESMTP id 15187693; Tue, 23 Nov 2004 11:52:08 -0800 From: Jerry Toung To: Dave Maltz , manet@ietf.org Subject: Re: [manet] data link protocol for manet Date: Tue, 23 Nov 2004 11:52:05 -0800 User-Agent: KMail/1.5.4 References: <200411230828.55350.jtoung@arc.nasa.gov> <185733560.1101218204@DMALTZ.WV.CS.cmu.edu> In-Reply-To: <185733560.1101218204@DMALTZ.WV.CS.cmu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411231152.05213.jtoung@arc.nasa.gov> X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: 7bit X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jtoung@arc.nasa.gov List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 7bit Thank you Dave, good info. That's what I was looking for. I will also look into getting that csma/ca implementation for ns-2. Jerry On Tuesday 23 November 2004 10:56 am, Dave Maltz wrote: > --On Tuesday, November 23, 2004 8:28 AM -0800 Jerry Toung > > wrote: > > we are looking at other L2 protocols to implement and test. > > What's the simplest alternative to 802.11? > > CSMA/CA with ethernet framing is probably as simple as you can get (and it > works pretty well!) > > We built the first version of the Monarch testbed using the original 900 > MHz WaveLAN product from Lucent, which used pure CSMA/CA for floor control. > Don't know if you can still find the hardware for sale in a store, but it's > probably out there. > > I had a student write a CSMA/CA MAC module for ns-2. I don't recall which > versions of the Monarch extensions it's in, or if it's been integrated into > the mainline ns-2 distribution. > > The very first DSR tests were run using IBM diffuse infrared cards. I > forget what the MAC was for those cards. > > Cheers, > -dam _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 16:55:17 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09469 for ; Tue, 23 Nov 2004 16:55:17 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWigq-0004Ph-09 for manet-web-archive@ietf.org; Tue, 23 Nov 2004 16:59:12 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWiN4-0007Jm-FD; Tue, 23 Nov 2004 16:38:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWiAD-0005IX-Se for manet@megatron.ietf.org; Tue, 23 Nov 2004 16:25:30 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04752 for ; Tue, 23 Nov 2004 16:25:26 -0500 (EST) Received: from mail.netgate.com ([64.62.194.115] helo=netgate.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWiDw-0008Re-Or for manet@ietf.org; Tue, 23 Nov 2004 16:29:21 -0500 Received: by netgate.com (Postfix, from userid 45) id A350528002D; Tue, 23 Nov 2004 13:25:20 -0800 (PST) Received: from [192.168.1.199] (rrcs-67-52-77-54.west.biz.rr.com [67.52.77.54]) by netgate.com (Postfix) with ESMTP id 0BCBE28001A; Tue, 23 Nov 2004 13:25:12 -0800 (PST) In-Reply-To: <200411231152.05213.jtoung@arc.nasa.gov> References: <200411230828.55350.jtoung@arc.nasa.gov> <185733560.1101218204@DMALTZ.WV.CS.cmu.edu> <200411231152.05213.jtoung@arc.nasa.gov> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <288ADF47-3D96-11D9-BF31-000A95AB7778@netgate.com> Content-Transfer-Encoding: 7bit From: Jim Thompson Subject: Re: [manet] data link protocol for manet Date: Tue, 23 Nov 2004 11:25:11 -1000 To: jtoung@arc.nasa.gov X-Mailer: Apple Mail (2.619) X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on he-colo.netgate.com X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit Cc: Dave Maltz , manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: 7bit something more ... scheduled would be nice as well. On Nov 23, 2004, at 9:52 AM, Jerry Toung wrote: > Thank you Dave, good info. That's what I was looking for. > I will also look into getting that csma/ca implementation for ns-2. > Jerry > > On Tuesday 23 November 2004 10:56 am, Dave Maltz wrote: >> --On Tuesday, November 23, 2004 8:28 AM -0800 Jerry Toung >> >> wrote: >>> we are looking at other L2 protocols to implement and test. >>> What's the simplest alternative to 802.11? >> >> CSMA/CA with ethernet framing is probably as simple as you can get >> (and it >> works pretty well!) >> >> We built the first version of the Monarch testbed using the original >> 900 >> MHz WaveLAN product from Lucent, which used pure CSMA/CA for floor >> control. >> Don't know if you can still find the hardware for sale in a store, >> but it's >> probably out there. >> >> I had a student write a CSMA/CA MAC module for ns-2. I don't recall >> which >> versions of the Monarch extensions it's in, or if it's been >> integrated into >> the mainline ns-2 distribution. >> >> The very first DSR tests were run using IBM diffuse infrared cards. I >> forget what the MAC was for those cards. >> >> Cheers, >> -dam > > > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 17:05:07 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11681 for ; Tue, 23 Nov 2004 17:05:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWiqM-0006B7-DX for manet-web-archive@ietf.org; Tue, 23 Nov 2004 17:09:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWiTS-0002fo-1M; Tue, 23 Nov 2004 16:45:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWiKM-0005G9-EQ for manet@megatron.ietf.org; Tue, 23 Nov 2004 16:35:58 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06492 for ; Tue, 23 Nov 2004 16:35:55 -0500 (EST) Received: from ms1.city.ac.uk ([138.40.12.21]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWiO2-0001mX-BN for manet@ietf.org; Tue, 23 Nov 2004 16:39:50 -0500 Received: from mailswitch.city.ac.uk ([138.40.12.12] helo=mailswitch) by ms1.city.ac.uk with smtp (Exim 4.20) id 1CWiIY-0000if-Hg for manet@ietf.org; Tue, 23 Nov 2004 21:34:06 +0000 Received: from cepc43.city.ac.uk ([138.40.163.52] helo=EHSAN) by mailswitch with esmtp (Exim 3.16 #5) id 1CWiIu-0005rL-00 for manet@ietf.org; Tue, 23 Nov 2004 21:34:28 +0000 From: "Ehsan Hamadani" To: Date: Tue, 23 Nov 2004 21:33:55 -0000 Message-ID: <002501c4d1a4$25b1af60$34a3288a@EHSAN> MIME-Version: 1.0 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.2900.2180 X-MailScanner-Information: Please contact Computing Services for more information (2.63) X-City-MailScanner: Found to be clean X-City-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=0.106, required 4.5, HTML_70_80 0.10, HTML_MESSAGE 0.00) X-Spam-Score: 0.1 (/) X-Scan-Signature: d49da3f50144c227c0d2fac65d3953e6 Subject: [manet] TCP Retransmission and Goodput X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0189639835==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: e9d8c60d9288f2c774f26bab15869505 This is a multi-part message in MIME format. --===============0189639835== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0026_01C4D1A4.25B1AF60" This is a multi-part message in MIME format. ------=_NextPart_000_0026_01C4D1A4.25B1AF60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi all, I am simulating a 4 hop static network with one TCP flow between the sender and receiver. There are 2 scenarios: One scenario (let's call it scenario 1) is based on RTS/CTS message exchange for packets larger than 1024 Bytes and the other one (scenario 2) does not use any RTS/CTS to send data over network. When I monitor the behaviour of TCP in the network, I come across the following issue: While scenario 1 has less average congestion window size and flight size (number of sent and unacknowledged data in network) with higher number of TCP retransmission in comparison to scenario 2, the goodput of scenario 1 is greater than scenario 2!!! For measuring the goodput, I am monitoring the sent sequence number by sender. So, for instance, at time 50sec, the sender in scenario 1 is sending packet with sequence number 10000 while the sender in scenario 2 is sending packet with sequence number 6000. Does anyone know the reason behind this? Thanks for your help Ehsan ----------------------------------------- Ehsan Hamadani, PhD student School of Engineering and Math Science City University London, EC1V 0HB United Kingdom Office: +44 (0)207 040 3886 ------=_NextPart_000_0026_01C4D1A4.25B1AF60 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

 

I am simulating a 4 hop static network with one TCP = flow between the sender and receiver. There are 2 scenarios: One scenario = (let’s call it scenario 1) is based on RTS/CTS message exchange for packets = larger than 1024 Bytes and the other one (scenario 2) does not use any RTS/CTS = to send data over network.

When I monitor the = behaviour of TCP in the network, I = come across the following issue:

 

While scenario 1 has less average congestion window = size and flight size (number of sent and unacknowledged data in network) with = higher number of TCP retransmission in comparison to scenario 2, the goodput of scenario 1 is greater than scenario 2!!!    

 

For measuring the goodput, I am monitoring the sent = sequence number by sender. So, for instance, at time 50sec, the sender in = scenario 1 is sending packet with sequence number 10000 while the sender in scenario 2 = is sending packet with sequence number 6000.

 

Does anyone know the reason behind = this?

 

Thanks for your help

 

Ehsan

 

-----= ------------------------------------

Ehsan= Hamadani, PhD student

School of = Engineering and = Math Science

City = University

=

Londo= n, = EC1V = 0HB

=

United = Kingdom

=

=  

Offi= ce: +44 (0)207 040 3886

=  

 

------=_NextPart_000_0026_01C4D1A4.25B1AF60-- --===============0189639835== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0189639835==-- From manet-bounces@ietf.org Tue Nov 23 17:36:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14609 for ; Tue, 23 Nov 2004 17:36:27 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWjKh-00020D-59 for manet-web-archive@ietf.org; Tue, 23 Nov 2004 17:40:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWj8s-0004PF-Cw; Tue, 23 Nov 2004 17:28:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWj5C-0003K0-Nf for manet@megatron.ietf.org; Tue, 23 Nov 2004 17:24:24 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13284 for ; Tue, 23 Nov 2004 17:24:19 -0500 (EST) Received: from aplexpress.dom1.jhuapl.edu ([128.244.198.132]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWj8w-0000N8-8E for manet@ietf.org; Tue, 23 Nov 2004 17:28:14 -0500 Received: from APLESLIBERTY.dom1.jhuapl.edu ([128.244.198.134]) by APLEXPRESS.dom1.jhuapl.edu with Microsoft SMTPSVC(6.0.3790.0); Tue, 23 Nov 2004 17:23:40 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [manet] TCP Retransmission and Goodput Date: Tue, 23 Nov 2004 17:23:40 -0500 Message-ID: <0F5AC32D8E455545AD0349BA8400A3CA1B0484@aplesliberty.dom1.jhuapl.edu> Thread-Topic: [manet] TCP Retransmission and Goodput Thread-Index: AcTRqIeD/2r7xUwsQqCus7C8roLp6wAAN7ug From: "Farrag, Osama" To: X-OriginalArrivalTime: 23 Nov 2004 22:23:40.0428 (UTC) FILETIME=[158B4CC0:01C4D1AB] X-Spam-Score: 0.2 (/) X-Scan-Signature: 544c2133b952fa264803d857bb70855b X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0693783966==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: ba9cd4f9acda58dbe142afff7265daff This is a multi-part message in MIME format. --===============0693783966== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4D1AB.15663D0B" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4D1AB.15663D0B Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Ehsan, =20 There could be many factors, in general 802.11 networks perform better in terms goodput when RTS/CTS handshake is used. =20 a) RTS/CTS mode allows nodes to detect collision faster than in Data/ACK mode because Data messages are much longer than RTS messages. So the channel revert to idle state faster and nodes will start contending again in shorter time.=20 b) Probability of collisions from Hidden node problem is reduced when RTS/CTS handshake is used. Less collision results in better throughput. =20 Hope that helps. =20 Best Regards Osama Farrag Johns Hopkins University/ APL =20 -----Original Message----- From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of Ehsan Hamadani Sent: Tuesday, November 23, 2004 4:34 PM To: manet@ietf.org Subject: [manet] TCP Retransmission and Goodput =20 Hi all, =20 I am simulating a 4 hop static network with one TCP flow between the sender and receiver. There are 2 scenarios: One scenario (let's call it scenario 1) is based on RTS/CTS message exchange for packets larger than 1024 Bytes and the other one (scenario 2) does not use any RTS/CTS to send data over network. When I monitor the behaviour of TCP in the network, I come across the following issue: =20 While scenario 1 has less average congestion window size and flight size (number of sent and unacknowledged data in network) with higher number of TCP retransmission in comparison to scenario 2, the goodput of scenario 1 is greater than scenario 2!!! =20 =20 For measuring the goodput, I am monitoring the sent sequence number by sender. So, for instance, at time 50sec, the sender in scenario 1 is sending packet with sequence number 10000 while the sender in scenario 2 is sending packet with sequence number 6000. =20 Does anyone know the reason behind this? =20 Thanks for your help =20 Ehsan =20 ----------------------------------------- Ehsan Hamadani, PhD student School of Engineering and Math Science City University London, EC1V 0HB United Kingdom =20 Office: +44 (0)207 040 3886 =20 =20 ------_=_NextPart_001_01C4D1AB.15663D0B Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Ehsan,

 

There could be many factors, in = general 802.11 networks perform better in terms goodput when RTS/CTS handshake is = used.

 

a)       RTS/CTS mode = allows nodes to detect collision faster than in Data/ACK mode because Data messages = are much longer than RTS messages. So the channel revert to idle state faster and = nodes will start contending again in shorter time.

b)       Probability of = collisions from Hidden node problem is reduced when RTS/CTS handshake is used. Less collision results in better throughput.

 

Hope that helps.

 

Best Regards

Osama Farrag

Johns Hopkins University= / APL

 

-----Original = Message-----
From: = manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On = Behalf Of Ehsan Hamadani
Sent: Tuesday, November 23, 2004 4:34 PM
To: manet@ietf.org
Subject: [manet] TCP Retransmission and Goodput

 

Hi all,

 

I am simulating a 4 hop = static network with one TCP flow between the sender and receiver. There are 2 scenarios: One scenario (let’s call it scenario 1) is based on = RTS/CTS message exchange for packets larger than 1024 Bytes and the other one = (scenario 2) does not use any RTS/CTS to send data over network.

When I monitor = the behaviour of TCP in the network, I come across the following = issue:

 

While scenario 1 has less = average congestion window size and flight size (number of sent and = unacknowledged data in network) with higher number of TCP retransmission in comparison to = scenario 2, the goodput of scenario 1 is greater than scenario = 2!!!   

 

For measuring the goodput, = I am monitoring the sent sequence number by sender. So, for instance, at time = 50sec, the sender in scenario 1 is sending packet with sequence number 10000 = while the sender in scenario 2 is sending packet with sequence number = 6000.

 

Does anyone know the reason = behind this?

 

Thanks for your = help

 

Ehsan

 

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

Ehsan Hamadani, PhD = student

School of Engineering and Math = Science

City University

London, EC1V 0HB

United = Kingdom

 

Office: +44 (0)207 040 3886

 

 

=00 ------_=_NextPart_001_01C4D1AB.15663D0B-- --===============0693783966== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0693783966==-- From manet-bounces@ietf.org Tue Nov 23 18:04:56 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16881 for ; Tue, 23 Nov 2004 18:04:56 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWjmF-0005xA-MF for manet-web-archive@ietf.org; Tue, 23 Nov 2004 18:08:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWjbk-0004M3-A9; Tue, 23 Nov 2004 17:58:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWjWA-0002mq-OP for manet@megatron.ietf.org; Tue, 23 Nov 2004 17:52:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15861 for ; Tue, 23 Nov 2004 17:52:11 -0500 (EST) Received: from avas4.olemiss.edu ([130.74.120.14]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWjZv-0003zO-2j for manet@ietf.org; Tue, 23 Nov 2004 17:56:07 -0500 Received: from olemiss.edu (webmail.olemiss.edu [130.74.120.12] (may be forged)) by avas4.olemiss.edu (8.12.11/8.12.11) with ESMTP id iANMpeiQ010476 for ; Tue, 23 Nov 2004 16:51:40 -0600 (envelope-from srgopal@olemiss.edu) From: "srgopal" To: manet@ietf.org X-Mailer: Quality Web Email v3.1e, http://netwinsite.com/refw.htm Date: Tue, 23 Nov 2004 16:51:40 -0600 Message-id: <41a3befc.19f.546b.749776427@olemiss.edu> X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2004.11.23.22 X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [manet] (null) - invalid packet type (exp).error in simulating ad hoc network! X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: srgopal@olemiss.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Dear All, I was simulating a network in ns-2 network simulator with two nodes with packet voice being generated from one node using exponential traffic generator and the other node is used as a null. I encountered the following problem: (null) - invalid packet type (exp). Basically, i ran the simulation for the example4.tcl in Marc Greis' tutorial available on the ns-2 webpage (8th one creating output files for X-graph) with wired network scenario and obtained good results. Next, i tried the same with wireless nodes and i encountered the above problem. I could not fix it. I even tried changing the CMUTrace.cc and CMUTrace.h files for adding my packet type(both null type and exp also). But it did not work out. Please help me figure it at the earliest. Any help will be appreciated. Regards, raja. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 18:29:36 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20028 for ; Tue, 23 Nov 2004 18:29:36 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWkA8-0000dG-Vg for manet-web-archive@ietf.org; Tue, 23 Nov 2004 18:33:33 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWk3J-0001mU-SQ; Tue, 23 Nov 2004 18:26:29 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWjwZ-00075z-L1 for manet@megatron.ietf.org; Tue, 23 Nov 2004 18:19:31 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19192 for ; Tue, 23 Nov 2004 18:19:28 -0500 (EST) Received: from aragorn.bbn.com ([128.33.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWk0K-0007aG-1Z for manet@ietf.org; Tue, 23 Nov 2004 18:23:24 -0500 Received: from [128.89.80.51] (ram-pbook.bbn.com [128.89.80.51]) by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id iANNIvje013081; Tue, 23 Nov 2004 18:18:57 -0500 (EST) In-Reply-To: <0F5AC32D8E455545AD0349BA8400A3CA1B0484@aplesliberty.dom1.jhuapl.edu> References: <0F5AC32D8E455545AD0349BA8400A3CA1B0484@aplesliberty.dom1.jhuapl.edu> Mime-Version: 1.0 (Apple Message framework v606) Content-Type: text/plain; charset=WINDOWS-1252; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Ram Ramanathan Subject: Re: [manet] TCP Retransmission and Goodput Date: Tue, 23 Nov 2004 18:23:07 -0500 To: "Farrag, Osama" X-Mailer: Apple Mail (2.606) X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) X-Spam-Score: 0.0 (/) X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f Content-Transfer-Encoding: quoted-printable Is this really true in practice -- that 802.11 networks have better=20 goodput when RTS/CTS is turned on? Researchers doing experimental work with testbeds more often than not=20 report better throughput with RTS/CTS turned off (at least those I've=20 spoken to), hidden terminals notwithstanding. While RTS/CTS solves the hidden terminal problem, it does introduce=20 exposed terminals, and the overhead of the handshake. And in some=20 cases, the negatives may be more than the positives. For instance, at=20 high data rates (e.g. 54 Mbps) the time for RTS/CTS as a fraction of=20 total packet transfer time gets to be significant, especially if=20 RTS/CTS are sent at lower data rate as is typical. I'm not disputing your statement, but do you (or anyone on this list)=20 know of any study that corrobarates this statement? Are there=20 comprehensive simulation or testbed based studies on this and does one=20= differ from the other in conclusions? If so, I'd appreciate a pointer. It would be good for the community to really understand the benefits of=20= RTS/CTS for ad hoc networks. cheers, -Ram On Nov 23, 2004, at 5:23 PM, Farrag, Osama wrote: > Ehsan, > > =A0 > > There could be many factors, in general 802.11 networks perform better=20= > in terms goodput when RTS/CTS handshake is used. > > =A0 > > a)=A0=A0=A0=A0=A0=A0RTS/CTS mode allows nodes to detect collision = faster than in=20 > Data/ACK mode because Data messages are much longer than RTS messages.=20= > So the channel revert to idle state faster and nodes will start=20 > contending again in shorter time. > > b)=A0=A0=A0=A0=A0=A0Probability of collisions from Hidden node problem = is reduced=20 > when RTS/CTS handshake is used. Less collision results in better=20 > throughput. > > =A0 > > Hope that helps. > > =A0 > > Best Regards > > Osama Farrag > > Johns Hopkins University/ APL > > =A0 > > -----Original Message----- > From:manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]On Behalf=20= > OfEhsan Hamadani > Sent: Tuesday, November 23, 2004 4:34 PM > To:manet@ietf.org > Subject:[manet] TCP Retransmission and Goodput > > =A0 > > Hi all, > > =A0 > > I am simulating a 4 hop static network with one TCP flow between the=20= > sender and receiver. There are 2 scenarios: One scenario (let=92s call=20= > it scenario 1) is based on RTS/CTS message exchange for packets larger=20= > than 1024 Bytes and the other one (scenario 2) does not use any=20 > RTS/CTS to send data over network. > > When I monitor thebehaviourof TCP in the network, I come across the=20 > following issue: > > =A0 > > While scenario 1 has less average congestion window size and flight=20 > size (number of sent and unacknowledged data in network) with higher=20= > number of TCP retransmission in comparison to scenario 2, the goodput=20= > of scenario 1 is greater than scenario 2!!!=A0=A0=A0 > > =A0 > > For measuring the goodput, I am monitoring the sent sequence number by=20= > sender. So, for instance, at time 50sec, the sender in scenario 1 is=20= > sending packet with sequence number 10000 while the sender in scenario=20= > 2 is sending packet with sequence number 6000. > > =A0 > > Does anyone know the reason behind this? > > =A0 > > Thanks for your help > > =A0 > > Ehsan > > =A0 > > ----------------------------------------- > > Ehsan Hamadani, PhD student > > SchoolofEngineeringand Math Science > > City University > > London,EC1V 0HB > > United Kingdom > > =A0 > > Office:+44 (0)207 040 3886 > > =A0 > > =A0 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 18:52:47 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22078 for ; Tue, 23 Nov 2004 18:52:47 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWkWZ-0003sA-NT for manet-web-archive@ietf.org; Tue, 23 Nov 2004 18:56:43 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWkQt-0007l6-5M; Tue, 23 Nov 2004 18:50:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWkNY-0006oX-9x for manet@megatron.ietf.org; Tue, 23 Nov 2004 18:47:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21670 for ; Tue, 23 Nov 2004 18:47:20 -0500 (EST) Received: from exstudent9.city.unisa.edu.au ([130.220.84.78]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWkRI-00036N-AN for manet@ietf.org; Tue, 23 Nov 2004 18:51:17 -0500 Received: by exstudent9.city.unisa.edu.au with Internet Mail Service (5.5.2656.59) id ; Wed, 24 Nov 2004 10:17:15 +1030 Message-ID: <329F3E3CDCDD9C4E91AA1CE184942ED101AC8737@exstudenta.city.unisa.edu.au> From: "Liaw, Yong Shyang - LIAYS001" To: "'Ram Ramanathan'" , "Farrag, Osama" Subject: RE: [manet] TCP Retransmission and Goodput Date: Wed, 24 Nov 2004 10:17:17 +1030 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 156eddb66af16eef49a76ae923b15b92 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176 Content-Transfer-Encoding: quoted-printable Below is a paper that shows with RTS/CTS off is better than RTS/CTS on = for ad-hoc network.=20 Aruna Jayasuriya, Sylvie Perreau, Arek Dadej, Steven Gordon, "Hidden = vs. Exposed Terminal Problem in Ad hoc Networks", Proc. of Australian Telecommunication Networks and Applications Conference (ATNAC 2004), = Dec 2004. http://www.itr.unisa.edu.au/~sgordon/research/publications -----Original Message----- From: Ram Ramanathan [mailto:ramanath@bbn.com]=20 Sent: Wednesday, 24 November 2004 9:53 AM To: Farrag, Osama Cc: manet@ietf.org Subject: Re: [manet] TCP Retransmission and Goodput Is this really true in practice -- that 802.11 networks have better=20 goodput when RTS/CTS is turned on? Researchers doing experimental work with testbeds more often than not=20 report better throughput with RTS/CTS turned off (at least those I've=20 spoken to), hidden terminals notwithstanding. While RTS/CTS solves the hidden terminal problem, it does introduce=20 exposed terminals, and the overhead of the handshake. And in some=20 cases, the negatives may be more than the positives. For instance, at=20 high data rates (e.g. 54 Mbps) the time for RTS/CTS as a fraction of=20 total packet transfer time gets to be significant, especially if=20 RTS/CTS are sent at lower data rate as is typical. I'm not disputing your statement, but do you (or anyone on this list)=20 know of any study that corrobarates this statement? Are there=20 comprehensive simulation or testbed based studies on this and does one=20 differ from the other in conclusions? If so, I'd appreciate a pointer. It would be good for the community to really understand the benefits of = RTS/CTS for ad hoc networks. cheers, -Ram On Nov 23, 2004, at 5:23 PM, Farrag, Osama wrote: > Ehsan, > > =A0 > > There could be many factors, in general 802.11 networks perform = better=20 > in terms goodput when RTS/CTS handshake is used. > > =A0 > > a)=A0=A0=A0=A0=A0=A0RTS/CTS mode allows nodes to detect collision = faster than in=20 > Data/ACK mode because Data messages are much longer than RTS = messages.=20 > So the channel revert to idle state faster and nodes will start=20 > contending again in shorter time. > > b)=A0=A0=A0=A0=A0=A0Probability of collisions from Hidden node = problem is reduced=20 > when RTS/CTS handshake is used. Less collision results in better=20 > throughput. > > =A0 > > Hope that helps. > > =A0 > > Best Regards > > Osama Farrag > > Johns Hopkins University/ APL > > =A0 > > -----Original Message----- > From:manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]On Behalf=20 > OfEhsan Hamadani > Sent: Tuesday, November 23, 2004 4:34 PM > To:manet@ietf.org > Subject:[manet] TCP Retransmission and Goodput > > =A0 > > Hi all, > > =A0 > > I am simulating a 4 hop static network with one TCP flow between the=20 > sender and receiver. There are 2 scenarios: One scenario (let's call=20 > it scenario 1) is based on RTS/CTS message exchange for packets = larger=20 > than 1024 Bytes and the other one (scenario 2) does not use any=20 > RTS/CTS to send data over network. > > When I monitor thebehaviourof TCP in the network, I come across the=20 > following issue: > > =A0 > > While scenario 1 has less average congestion window size and flight=20 > size (number of sent and unacknowledged data in network) with higher=20 > number of TCP retransmission in comparison to scenario 2, the goodput = > of scenario 1 is greater than scenario 2!!!=A0=A0=A0 > > =A0 > > For measuring the goodput, I am monitoring the sent sequence number = by=20 > sender. So, for instance, at time 50sec, the sender in scenario 1 is=20 > sending packet with sequence number 10000 while the sender in = scenario=20 > 2 is sending packet with sequence number 6000. > > =A0 > > Does anyone know the reason behind this? > > =A0 > > Thanks for your help > > =A0 > > Ehsan > > =A0 > > ----------------------------------------- > > Ehsan Hamadani, PhD student > > SchoolofEngineeringand Math Science > > City University > > London,EC1V 0HB > > United Kingdom > > =A0 > > Office:+44 (0)207 040 3886 > > =A0 > > =A0 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 23 19:09:58 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23281 for ; Tue, 23 Nov 2004 19:09:58 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWknC-0005r8-7G for manet-web-archive@ietf.org; Tue, 23 Nov 2004 19:13:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWkbz-0001ti-Dm; Tue, 23 Nov 2004 19:02:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWkYt-0000r1-IG for manet@megatron.ietf.org; Tue, 23 Nov 2004 18:59:07 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22448 for ; Tue, 23 Nov 2004 18:59:04 -0500 (EST) Received: from web20927.mail.yahoo.com ([216.136.224.145]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CWkcd-0004ec-GM for manet@irtf.org; Tue, 23 Nov 2004 19:03:00 -0500 Received: (qmail 61286 invoked by uid 60001); 23 Nov 2004 23:59:02 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=KmRgZ6qNGJF/4TZzL5zdf5O8YOsw2WMHUmnfZg7KRKjHfU0/ReSMsik+b4ee5y6534NgNGJNzX6j2Vsg44YJNhhvu+sHwJHgu5nWxrH6RTAkb24xxxDqlMxeOpp5pOP/puK/GZ/lG6sbRAMDSwO5SfV0NUmHADR3wvFOfPguLyw= ; Message-ID: <20041123235902.61284.qmail@web20927.mail.yahoo.com> Received: from [203.208.193.230] by web20927.mail.yahoo.com via HTTP; Tue, 23 Nov 2004 15:59:02 PST Date: Tue, 23 Nov 2004 15:59:02 -0800 (PST) From: Praveen Choudary To: manet@irtf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [manet] QOS issue X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1286247449==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 --===============1286247449== Content-Type: multipart/alternative; boundary="0-1368358111-1101254342=:60891" --0-1368358111-1101254342=:60891 Content-Type: text/plain; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id SAA22448 Content-Transfer-Encoding: quoted-printable I am working on QOS issues in Wireless Sensor Networks. There are publica= tions related to this. Suppose the constraint is that the high priority p= ackets should reach the destination with in a deadline. Can a node estima= te that it has a high probability of getting a high priority in the futur= e based on the priorities of the past received packets. I mean if a node = can estimate the time of arrival of a high priority packet, it can take s= ome action. Please let me know your comments. =09 --------------------------------- Do you Yahoo!? Meet the all-new My Yahoo! =96 Try it today!=20 --0-1368358111-1101254342=:60891 Content-Type: text/html; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id SAA22448 Content-Transfer-Encoding: quoted-printable
I am working on QOS issues in Wireless Sensor Networks. There are pu= blications related to this. Suppose the constraint is that the high prior= ity packets should reach the destination with in a deadline. Can a node e= stimate that it has a high probability of getting a high priority in the = future based on the priorities of the past received packets. I mean if a = node can estimate the time of arrival of a high priority packet, it can t= ake some action.
Please let me know your comments.

Do you Yahoo!?
=20 Meet the all-new My Yahoo! =96 Try it= today!=20 --0-1368358111-1101254342=:60891-- --===============1286247449== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1286247449==-- From manet-bounces@ietf.org Tue Nov 23 22:07:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06994 for ; Tue, 23 Nov 2004 22:07:43 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWnZE-0003uI-Au for manet-web-archive@ietf.org; Tue, 23 Nov 2004 22:11:40 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWnRH-0003Uo-Aq; Tue, 23 Nov 2004 22:03:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWnKw-0002ML-0O for manet@megatron.ietf.org; Tue, 23 Nov 2004 21:56:55 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05991 for ; Tue, 23 Nov 2004 21:56:51 -0500 (EST) Received: from jpnmailout01.yamato.ibm.com ([203.141.80.81]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWnOh-0002IA-KC for manet@ietf.org; Tue, 23 Nov 2004 22:00:49 -0500 Received: from e19f3n15.jp.ibm.com (d19relay02.sagamino.japan.ibm.com [203.141.80.91] (may be forged)) by jpnmailout01.yamato.ibm.com (8.12.11/8.12.11) with ESMTP id iAO2u9eY011610 for ; Wed, 24 Nov 2004 11:56:09 +0900 Received: from d19av04.sagamino.japan.ibm.com (d19av04.sagamino.japan.ibm.com [9.189.5.112]) by e19f3n15.jp.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id iAO2u8CW187824 for ; Wed, 24 Nov 2004 11:56:09 +0900 Received: from d19av04.sagamino.japan.ibm.com (loopback [127.0.0.1]) by d19av04.sagamino.japan.ibm.com (8.12.11/8.12.11) with ESMTP id iAO2u8Jc032284 for ; Wed, 24 Nov 2004 11:56:08 +0900 Received: from D19ML114.sagamino.japan.ibm.com (d19ml114.sagamino.japan.ibm.com [9.189.4.139]) by d19av04.sagamino.japan.ibm.com (8.12.11/8.12.11) with ESMTP id iAO2u8M5032281 for ; Wed, 24 Nov 2004 11:56:08 +0900 To: manet@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.2CF2 July 23, 2003 From: Akihiko Mizutani Message-ID: Date: Wed, 24 Nov 2004 11:56:07 +0900 X-MIMETrack: Serialize by Router on D19ML114/19/M/IBM(Release 6.51HF338 | June 21, 2004) at 2004/11/24 11:56:08, Serialize complete at 2004/11/24 11:56:08 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8a961490db2a74c7613bf0201229f176 Subject: [manet] IPSJ ICMU2005: Last CFP: Submission dead line December 1 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1791459752==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2fe944273194be3112d13b31c91e6941 This is a multipart message in MIME format. --===============1791459752== Content-Type: multipart/alternative; boundary="=_alternative 001027E649256F56_=" This is a multipart message in MIME format. --=_alternative 001027E649256F56_= Content-Type: text/plain; charset="ISO-2022-JP" ======================================================================== CALL FOR PAPERS Second International Conference on Mobile Computing and Ubiquitous Networking (ICMU 2005) April 13 through 15, 2005 Osaka University Convention Center, Osaka, Japan http://www.ipsj.or.jp/sig/mbl/icmu2005/ IMPORTANT DATES Deadline for submissions: December 1, 2004 Notification of acceptance: January 15, 2005 Camera ready due: February 15, 2005 Sponsored by IPSJ SIG-MBL (Information Processing Society of Japan, Special Interest Group of Mobile Computing and Ubiquitous Networking) IPSJ SIG-BCC (Study Group of Broadcast Communication and Computing) Supported by IPSJ SIG-ITS (Special Interest Group of Intelligent Transport Systems) IPSJ SIG-UBI (Ubiquitous Computing System) Telecommunications Advancement Foundation. ------------------------------------------------------------------------------- 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 management for ubiquitous networking * Data management for mobile computing * Wireless and mobile communications * Performance evaluation for mobile computing and ubiquitous networking systems * Broadcast communication * Network architectures, protocols, or service models for ubiquitous networking * Security in mobile computing and ubiquitous networking * Nomadic computing * Mobile Internetworking * Ad hoc networks * Sensor networks * Location-based Service 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 the web site of the conference http://www.ishilab.net/icmu2005/ http://www.ipsj.or.jp/sig/mbl/icmu2005/ for further submission instructions. Important Dates ~~~~~~~~~~~~~~~ Deadline for submissions: December 1, 2004 Notification of acceptance: January 15, 2005 Camera ready due: February 15, 2005 After the conference, a selected number of papers will be published as special issues in IPSJ journal. Committees ~~~~~~~~~~ General Chair Yasuo Hirata (KDDI R&D Laboratories, Japan) Executive Committee Co-Chairs: Tadanori Mizuno (Shizuoka University, Japan) Osamu Takahashi (Future University-Hakodate, Japan) Technical Program Committee Chair: Takashi Watanabe (Shizuoka University, Japan) Publication Chair Hidetoshi Yokota (KDDI R&D Laboratories, Japan) Publicity Chair Akihiko Mizutani (IBM Japan, Japan) Local Arrangement Masahiko Tsukamoto (Kobe University, Japan) Treasurer Hirozumi Yamaguchi (Osaka University, Japan) Technical Program Committee Mohammed Atiquzzaman (University of Oklahoma, USA) Masaki Bandai (Shizuoka University, Japan) Po-Jen Chuang (Tamkang University, Taiwan) Xiuzhen Cheng (George Washington University, USA) Nobutsugu Fujino (Fujitsu Laboratories, Japan) Jeong Hye Han (Cheongju National University of Education, Korea) Chung-Ming Huang (National Cheng Kung University, Taiwan) Tetsuo Ideguchi (Aichi Prefectural University, Japan) Fumiyuki Iizuka (Fujitsu Laboratories, Japan) Akino Inoue (Matsushita Electric Industrial, Japan) Masugi Inoue (National Institute of Information and CommunicationsTechnology, Japan) Susumu Ishihara (Shizuoka University, Japan) Masahiro Ishiyama (Toshiba Corporation, Japan) Tomoko Itao (NTT, Japan) Shuichi Karino (NEC, Japan) Nobuo Kawaguchi (Nagoya University, Japan) Dong Yoon Kim (Ajou University, Korea) Cheeha Kim (Pohang University of Science and Technology, Korea) Kane Kim (University of California at Irvine, USA) Gen Kitagata (Tohoku University, Japan) Peter Langendoerfer (IHP Microelectronics, Germany) Mitsuji Matshumoto(Waseda University, Japan) Masateru Minami (Shibaura Institute of Technology, Japan) Akihiko Mizutani (IBM Japan, Japan) Eigo Mori (Nokia Japan, Japan) Hiroyuki Morikawa (University of Tokyo, Japan) Yasuto Nakanishi (Tokyo University of Agriculture and Technology, Japan) Junya Nakata (Japan Advanced Institute of Science and Technology, Japan$B!K(B Masahiro Nishi (Hiroshima City University, Japan) Akiyoshi Ogawa (Vodafone, Japan) Ken Ohta (NTT DoCoMo, Japan) Minoru Okada (Nara Institute of Science and Technology, Japan) Kouji Okamura (Kyushu University, Japan) Ryouji Ono (Mitsubishi Electric, Japan) Yuko Onoe (NTT DoCoMo, Japan) Antonio Pescape (University of Napoli, Italy) Keizo Saisho (Kagawa University, Japan) Ichiro Satoh (National Institute of Informatics, Japan) Winston Seah (Institute for Infocomm Research, Singapore) Hiroshi Shigeno (Keio University, Japan) Akio Shinohara (NTT, Japan) Biplab Sikdar (Rensselaer Polytechnic Institute, USA) Tatsuya Suda (University of California at Irvine$B!$(BUSA) Shinta Sugimoto (Nippon Ericsson, Japan) Keisuke Suwa (Musashi Institute of Technology, Japan) Kastumi Takahashi (NTT, Japan) Osamu Takahashi (Future University-Hakodate, Japan) Kazunori Takashio (Keio University, Japan) Takamichi Tateoka (University of Electro-Communications, Japan) Chai-Keong Toh (Queen Mary University of London, UK) Msahiko Tsukamoto (Kobe University, Japan) Hirozumi Yamaguchi (Osaka University, Japan) Hirofumi Yamaki (Kyoto University, Japan) Miki Yamamoto (Osaka University, Japan) Nagatsugu Yamanouchi (Toho University, Japan) Masashi Yano (Hitachi Ltd., Japan) Takashi Yoshino (Wakayama University, Japan) --=_alternative 001027E649256F56_= Content-Type: text/html; charset="ISO-2022-JP"
<Please forgive us if you receive this information from multiple sources>
========================================================================
                          CALL FOR PAPERS

               Second International Conference on
      Mobile Computing and Ubiquitous Networking (ICMU 2005)

                   April 13 through 15, 2005
         Osaka University Convention Center, Osaka, Japan

            http://www.ipsj.or.jp/sig/mbl/icmu2005/

                        IMPORTANT DATES

          Deadline for submissions: December 1, 2004
           Notification of acceptance: January 15, 2005
           Camera ready due: February 15, 2005

Sponsored by

IPSJ SIG-MBL (Information Processing Society of Japan, Special Interest
              Group of Mobile Computing and Ubiquitous Networking)
IPSJ SIG-BCC (Study Group of Broadcast Communication and Computing)

Supported by

IPSJ SIG-ITS (Special Interest Group of Intelligent Transport Systems)
IPSJ SIG-UBI (Ubiquitous Computing System)
Telecommunications Advancement Foundation.

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

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 management for ubiquitous networking
* Data management for mobile computing
* Wireless and mobile communications
* Performance evaluation for mobile computing and
ubiquitous networking systems
* Broadcast communication
* Network architectures, protocols, or service models
for ubiquitous networking
* Security in mobile computing and ubiquitous networking
* Nomadic computing
* Mobile Internetworking
* Ad hoc networks
* Sensor networks
* Location-based Service


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 the web site of the conference

http://www.ishilab.net/icmu2005/
http://www.ipsj.or.jp/sig/mbl/icmu2005/

for further submission instructions.

Important Dates
~~~~~~~~~~~~~~~
Deadline for submissions: December 1, 2004
Notification of acceptance: January 15, 2005
Camera ready due: February 15, 2005


After the conference, a selected number of papers will be published
as special issues in IPSJ journal.


Committees
~~~~~~~~~~
General Chair
Yasuo Hirata (KDDI R&D Laboratories, Japan)

Executive Committee Co-Chairs:
Tadanori Mizuno (Shizuoka University, Japan)
Osamu Takahashi (Future University-Hakodate, Japan)

Technical Program Committee Chair:
Takashi Watanabe (Shizuoka University, Japan)

Publication Chair
Hidetoshi Yokota (KDDI R&D Laboratories, Japan)

Publicity Chair
Akihiko Mizutani (IBM Japan, Japan)

Local Arrangement
Masahiko Tsukamoto (Kobe University, Japan)

Treasurer
Hirozumi Yamaguchi (Osaka University, Japan)

Technical Program Committee
Mohammed Atiquzzaman (University of Oklahoma, USA)
Masaki Bandai (Shizuoka University, Japan)
Po-Jen Chuang (Tamkang University, Taiwan)
Xiuzhen Cheng (George Washington University, USA)
Nobutsugu Fujino (Fujitsu Laboratories, Japan)
Jeong Hye Han (Cheongju National University of Education, Korea)
Chung-Ming Huang (National Cheng Kung University, Taiwan)
Tetsuo Ideguchi (Aichi Prefectural University, Japan)
Fumiyuki Iizuka (Fujitsu Laboratories, Japan)
Akino Inoue (Matsushita Electric Industrial, Japan)
Masugi Inoue (National Institute of Information and CommunicationsTechnology, Japan)
Susumu Ishihara (Shizuoka University, Japan)
Masahiro Ishiyama (Toshiba Corporation, Japan)
Tomoko Itao (NTT, Japan)
Shuichi Karino (NEC, Japan)
Nobuo Kawaguchi (Nagoya University, Japan)
Dong Yoon Kim (Ajou University, Korea)
Cheeha Kim (Pohang University of Science and Technology, Korea)
Kane Kim (University of California at Irvine, USA)
Gen Kitagata (Tohoku University, Japan)
Peter Langendoerfer (IHP Microelectronics, Germany)
Mitsuji Matshumoto(Waseda University, Japan)
Masateru Minami (Shibaura Institute of Technology, Japan)
Akihiko Mizutani (IBM Japan, Japan)
Eigo Mori (Nokia Japan, Japan)
Hiroyuki Morikawa (University of Tokyo, Japan)
Yasuto Nakanishi (Tokyo University of Agriculture and Technology,  Japan)
Junya Nakata  (Japan Advanced Institute of Science and Technology, Japan$B!K(B
Masahiro Nishi (Hiroshima City University, Japan)
Akiyoshi Ogawa (Vodafone, Japan)
Ken Ohta (NTT DoCoMo, Japan)
Minoru Okada (Nara Institute of Science and Technology, Japan)
Kouji Okamura (Kyushu University, Japan)
Ryouji Ono (Mitsubishi Electric, Japan)
Yuko Onoe (NTT DoCoMo, Japan)
Antonio Pescape (University of Napoli, Italy)
Keizo Saisho (Kagawa University, Japan)
Ichiro Satoh (National Institute of Informatics, Japan)
Winston Seah (Institute for Infocomm Research, Singapore)
Hiroshi Shigeno (Keio University, Japan)
Akio Shinohara (NTT, Japan)
Biplab Sikdar (Rensselaer Polytechnic Institute, USA)
Tatsuya Suda (University of California at Irvine$B!$(BUSA)
Shinta Sugimoto (Nippon Ericsson, Japan)
Keisuke Suwa (Musashi Institute of Technology, Japan)
Kastumi Takahashi (NTT, Japan)
Osamu Takahashi (Future University-Hakodate, Japan)
Kazunori Takashio (Keio University, Japan)
Takamichi Tateoka (University of Electro-Communications, Japan)
Chai-Keong Toh (Queen Mary University of London, UK)
Msahiko Tsukamoto (Kobe University, Japan)
Hirozumi Yamaguchi (Osaka University, Japan)
Hirofumi Yamaki (Kyoto University, Japan)
Miki Yamamoto (Osaka University, Japan)
Nagatsugu Yamanouchi (Toho University, Japan)
Masashi Yano (Hitachi Ltd., Japan)
Takashi Yoshino (Wakayama University, Japan) --=_alternative 001027E649256F56_=-- --===============1791459752== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1791459752==-- From manet-bounces@ietf.org Wed Nov 24 01:54:54 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA21374 for ; Wed, 24 Nov 2004 01:54:54 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWr76-0007Vh-28 for manet-web-archive@ietf.org; Wed, 24 Nov 2004 01:58:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWqvu-0003cg-Rp; Wed, 24 Nov 2004 01:47:18 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWqr0-0002MW-HU for manet@megatron.ietf.org; Wed, 24 Nov 2004 01:42:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20787 for ; Wed, 24 Nov 2004 01:42:13 -0500 (EST) Received: from mta1.aucegypt.edu ([213.181.245.106]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWquk-0005wh-Hk for manet@ietf.org; Wed, 24 Nov 2004 01:46:11 -0500 Received: from aucegypt.edu (smms2.aucegypt.edu [10.0.0.109]) by mta1.aucegypt.edu (Switch-3.1.5/Switch-3.1.0) with ESMTP id iAO6cq1G026341; Wed, 24 Nov 2004 08:38:52 +0200 Date: Wed, 24 Nov 2004 06:37:45 +0000 Message-Id: MIME-Version: 1.0 X-Sensitivity: 3 From: "mhelali" To: "ns mail list" To: "manet" X-XaM3-API-Version: 4.1 (B13) X-type: 0 X-SenderIP: 213.181.237.79 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Subject: [manet] Changes in c++ files are not reflected after running make X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0803642931==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 --===============0803642931== Content-Type: multipart/alternative; boundary="_=__=_XaM3_.1101278265.2A.685564.42.4148.52.42.007.275552409" --_=__=_XaM3_.1101278265.2A.685564.42.4148.52.42.007.275552409 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello ns users I have this peculiar problem. After making changes to a .= cc file the changes are not reflected when running ns2 even after running= configure and then make in the ns2 directory. The changes that I did wer= e just adding printf to some part of the AODV.C file. Also after uncommen= ting the statement #define DEBUG to display debugging information on t= he screen, yet no output is displayed. I have done configure and make aft= er any change and I am running ns2.27 under redhat fedora. I cannot unde= rstand how to solve this problem. please your instant reply is greatly ap= preciated --_=__=_XaM3_.1101278265.2A.685564.42.4148.52.42.007.275552409 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hello = ns users
I have this peculiar problem. After making changes t= o a .cc file the changes are not reflected when running ns2 even after ru= nning configure and then make in the ns2 directory. The changes that I di= d were just adding printf to some part of the AODV.C file. Also after unc= ommenting the statement
#define DEBUG
to display= debugging information on the screen, yet no output is displayed. I have = done configure and make after any change and I am running ns2.27 under re= dhat fedora.
I cannot understand how to solve this problem. p= lease your instant reply is greatly appreciated
 
<= /DIV> --_=__=_XaM3_.1101278265.2A.685564.42.4148.52.42.007.275552409-- --===============0803642931== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0803642931==-- From manet-bounces@ietf.org Wed Nov 24 02:03:35 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24358 for ; Wed, 24 Nov 2004 02:03:35 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWrFU-0000D6-Fm for manet-web-archive@ietf.org; Wed, 24 Nov 2004 02:07:33 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWr26-00058X-5l; Wed, 24 Nov 2004 01:53:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWqt2-00033O-Ol for manet@megatron.ietf.org; Wed, 24 Nov 2004 01:44:20 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20930 for ; Wed, 24 Nov 2004 01:44:19 -0500 (EST) Received: from mta1.aucegypt.edu ([213.181.245.106]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWqwr-0006Jw-5b for manet@ietf.org; Wed, 24 Nov 2004 01:48:17 -0500 Received: from aucegypt.edu (smms2.aucegypt.edu [10.0.0.109]) by mta1.aucegypt.edu (Switch-3.1.5/Switch-3.1.0) with ESMTP id iAO6f9g9026573; Wed, 24 Nov 2004 08:41:09 +0200 Date: Wed, 24 Nov 2004 06:40:03 +0000 Message-Id: Subject: Re:[manet] Broadcast simulation MIME-Version: 1.0 X-Sensitivity: 3 From: "mhelali" To: "sallyhan" X-XaM3-API-Version: 4.1 (B13) X-type: 0 X-SenderIP: 213.181.237.79 X-Spam-Score: 0.3 (/) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 Cc: manet X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0222179752==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.6 (/) X-Scan-Signature: 2086112c730e13d5955355df27e3074b --===============0222179752== Content-Type: multipart/alternative; boundary="_=__=_XaM3_.1101278403.2A.477743.42.4217.52.42.007.480054909" --_=__=_XaM3_.1101278403.2A.477743.42.4217.52.42.007.480054909 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable All you need to do is access the ip header of your packet and insert IP_B= ROADCAT in the destination address field Frommanet-bounces@ietf.org =0D = Tomanet@ietf.org Cc DateTue, 23 Nov 2004 10:36:11 -0500 (EST) Su= bject[manet] Broadcast simulation > Hi Folks, > > Does someo= ne know how to send broadcast message in MANET, for example use DSR as th= e routing protocol? > > > Regards, > > sally --_=__=_XaM3_.1101278403.2A.477743.42.4217.52.42.007.480054909 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
All you need to do is access the ip header of your packet and insert= IP_BROADCAT in the destination address field
From manet-bounces@ietf.org
=0D = To manet@ietf.org
=0D =
Cc
Date Tu= e, 23 Nov 2004 10:36:11 -0500 (EST)
Subject [manet] Broadcast simulation
=0D =
  
=0D =
> Hi Folks,
>  
> Does someone= know how to send broadcast message in MANET, for example use DSR as the = routing protocol?
>  
>  
=0D =
> Regards,
>  
> sally
--_=__=_XaM3_.1101278403.2A.477743.42.4217.52.42.007.480054909-- --===============0222179752== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0222179752==-- From manet-bounces@ietf.org Wed Nov 24 03:41:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28874 for ; Wed, 24 Nov 2004 03:41:37 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWsmP-0004kk-Lk for manet-web-archive@ietf.org; Wed, 24 Nov 2004 03:45:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWsae-0005WW-8G; Wed, 24 Nov 2004 03:33:28 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWsXi-0004hj-Ie for manet@megatron.ietf.org; Wed, 24 Nov 2004 03:30:26 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA27470 for ; Wed, 24 Nov 2004 03:30:24 -0500 (EST) Received: from anyida.tts.lth.se ([130.235.18.10]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWsbX-0003Aq-Nx for manet@ietf.org; Wed, 24 Nov 2004 03:34:24 -0500 Received: from [192.168.2.19] (lina23.tts.lth.se [130.235.18.83]) by anyida.tts.lth.se (8.9.3/8.9.3) with ESMTP id JAA20448; Wed, 24 Nov 2004 09:29:25 +0100 (MET) Message-ID: <41A44644.4020502@telecom.lth.se> Date: Wed, 24 Nov 2004 09:28:52 +0100 From: Ali Hamidian User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: srgopal@olemiss.edu Subject: Re: [manet] (null) - invalid packet type (exp).error in simulating ad hoc network! References: <41a3befc.19f.546b.749776427@olemiss.edu> In-Reply-To: <41a3befc.19f.546b.749776427@olemiss.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: 7bit Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: 7bit Hi Raja, Have you tried the advice here? http://mailman.isi.edu/pipermail/ns-users/2003-January/029130.html Which version of ns-2 are you using? Ali srgopal wrote: >Dear All, > >I was simulating a network in ns-2 network simulator with >two nodes with packet voice being generated from one node >using exponential traffic generator and the other node is >used as a null. I encountered the following problem: (null) >- invalid packet type (exp). > >Basically, i ran the simulation for the example4.tcl in Marc >Greis' tutorial available on the ns-2 webpage (8th one >creating output files for X-graph) with wired network >scenario and obtained good results. Next, i tried the same >with wireless nodes and i encountered the above problem. I >could not fix it. >I even tried changing the CMUTrace.cc and CMUTrace.h files >for adding my packet type(both null type and exp also). But >it did not work out. >Please help me figure it at the earliest. Any help will be >appreciated. > >Regards, >raja. > >_______________________________________________ >manet mailing list >manet@ietf.org >https://www1.ietf.org/mailman/listinfo/manet > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 24 06:46:05 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA12681 for ; Wed, 24 Nov 2004 06:46:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWvex-00008K-Cn for manet-web-archive@ietf.org; Wed, 24 Nov 2004 06:50:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWvVN-0000P1-PA; Wed, 24 Nov 2004 06:40:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWvR0-0007pL-9j for manet@megatron.ietf.org; Wed, 24 Nov 2004 06:35:42 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11510 for ; Wed, 24 Nov 2004 06:35:39 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.207]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWvUr-0007Pf-At for manet@ietf.org; Wed, 24 Nov 2004 06:39:41 -0500 Received: by rproxy.gmail.com with SMTP id a36so61732rnf for ; Wed, 24 Nov 2004 03:35:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=eUaa7DNxtGzJ1EPeecnByPPu7VIsDnbTXQdCKEf1o9nMJlZeKGo6MRV1/AUQAqbaNN1ufjBA13iYGAW6N3fDr5WxS6qHuPv1M//Tv36LDIS+v+vDgsV63i+kKIGVWoyADEHkgSJk3EvyM7mDdQdVWt8OvOBEM/Pma41Y8l6dYL4= Received: by 10.38.15.57 with SMTP id 57mr294899rno; Wed, 24 Nov 2004 03:35:40 -0800 (PST) Received: by 10.38.164.52 with HTTP; Wed, 24 Nov 2004 03:35:40 -0800 (PST) Message-ID: Date: Wed, 24 Nov 2004 12:35:40 +0100 From: Jinshan Liu To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48 Content-Transfer-Encoding: quoted-printable Subject: [manet] CFP [Deadline Extended] iTrust 2005 --Third International Conference on Trust Management X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jinshan Liu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610 Content-Transfer-Encoding: quoted-printable [Sincere apologies if you receive multiple copies of this CFP] ****************************************** Due to several requests, the paper submission deadline has been extended to: December 10, 2004 ****************************************** CFP -- iTrust 2005 international conference on Trust management Call for Papers 3rd International Conference on Trust Management (iTrust'2005) 23-26 May 2005, INRIA-Rocquencourt, France http://www-rocq.inria.fr/arles/events/iTrust2005/ The iTrust international Conference looks at trust from multidisciplinary= =20 perspectives: economic, legal, pyschology, philosophy, sociology as well=20 as information technology.=20 Building upon the work of the IST iTrust working group=20 (http://www.itrust.uoc.gr) and the success of the two previous iTrust=20 International conferences (http://www.trustmanagement.cclrc.ac.uk/), the ai= ms=20 of iTrust'2005 are to attract a critical mass of experts from industry,=20 government and academia with a keen interest in the area of trust managemen= t.=20 The objectives of the Conference are:=20 - To facilitate the cross-disciplinary investigation of fundamental=20 issues underpinning computational trust models by bringing together=20 expertise from technology oriented sciences, law, philosophy and social= =20 sciences.=20 - To facilitate the emergence of widely acceptable trust management process= es=20 or dynamic open systems and applications.=20 - To facilitate the development of new paradigms in the area of dynamic=20 open systems which effectively utilise computational trust models.=20 - To facilitate the integration of new trust management paradigms and=20 emerging architectures for Grid computing and Virtual Organisations.=20 - To help the incorporation of trust management elements in existing standa= rds. =20 Topics of Interest: Full technical papers contributing to the issue of trust management are=20 solicited in the relevant areas, including but not limited to:=20 - The legal notion of trust in computer science and engineering - Requirements and methodologies to ensure that the user can trust the=20 functioning of software systems - Trust management frameworks for secure collaborations in dynamic Virtual= =20 Organisations=20 - Design of trust based architectures and decision-making mechanisms for=20 e-community and e-service interactions - Trust specification, analysis and reasoning - Dynamics of trust dispositions and relations=20 - Realisation of prototypes of software architectures and applications - Trust elements in contract negotiation, execution monitoring, re-negotiat= ion=20 and arbitration - Legal contribution to trust in technological infrastructures and=20 interactions: the on-line identification of subjects, the evaluation of= =20 their reliability, the data protection, privacy,=20 confidentiality, security, commercial transactions, the resolution of=20 disputes, software agents, the access to source code - The conditions for the reliance in the artefact and the machine - Trust in the interaction and cooperation "mediated" through computer and= =20 network, and the balance between control and intervention.=20 - Research of on-line trust, the trust of the consumer towards the web site= =20 of the distribution company - Analysis of the relationship between trust and such notions as confidence= ,=20 distrust, diffidence, expectation, risk and reliance. Important Dates:=20 Papers:=20 Submission of papers: December 10, 2004=20 Notification of paper acceptance: January 14, 2005 Submission of final camera ready version: February 25, 2005 How to Submit: Submissions must be original and must not have been submitted for publicati= on=20 elsewhere. =20 The proceedings of the Conference will be published by Springer in the=20 Lecture Notes in Computer Science series. Submissions must be in English=20 and authors should ensure that papers are formatted according to=20 the LNCS format (see author's instructions given on the Conference Web site= ).=20 Full technical papers should not exceed 15 pages in the abovementioned=20 format.=20 Submissions should be made through the Conference Web Site. =20 Organization: General Chair:=20 Valerie Issarny (INRIA) Programme Co-Chairs: Peter Herrmann, University of Dortmund, Germany Simon Shiu, Hewlett Packard, UK Conference Committee: Demonstration Chair: Nikolaos Georgantas, INRIA, France Panel Chair: Paul Kearney, BTexact, UK Tutorial Chair: Yuecel Karabulut, SAP AG, Germany Publicity Chair: Jinshan Liu, INRIA, France Local Arrangement: Dominique Potherat, INRIA, France Programme Committee: =20 Eliza Bertino, University of Milano, Italy Jon Bing, NRCCL-University of Oslo, Norway Jeremy Bryans, University of Newcastle, UK Cristiano Castelfranchi, CNR, Italy David Chadwick, University of Salford, UK Andrew Charlesworth, University of Bristol, UK David Crocker, Brandenburg InternetWorking, USA Mark Roger Dibben, University of St. Andrews, UK Theo Dimitrakos, CCLRC, UK Rino Falcone, CNR, Italy Peter Herrmann, University of Dortmund, Germany Valerie Issarny, INRIA, France Keith Jeffery, CCLRC, UK Christian Jensen, DTU, Denmark Andrew Jones, King's College, UK Audun Josang, DSTC, Australia Yuecel Karabulut, SAP AG, Germany Paul Kearney, BTexact, UK Graham Klyne, Nine by Nine, UK Heiko Krumm, University of Dortmund, Germany Ninghui Li, Stanford University, USA Peter Linington, University of Kent at Canterbury, UK Stephane Lo Presti, University of Southampton, UK Fabio Martinelli, CNR, Italy Fabio Massacci, Universit=E0 di Trento, Italy Erich Neuhold, Darmstadt University of Technology and Fraunhofer IPSI, Germ= any Christos Nikolaou, University of Crete, Greece Paddy Nixon, University of Strathclyde, UK Stefan Poslad, Queen Mary Colledge, UK Jens Riegelsberger, University of Newcastle, UK Peter Ryan, University of Newcastle, UK Babak Sadighi, SICS, Sweden Simon Shiu, Hewlett Packard, UK Morris Sloman, Imperial College, UK Ketil Stoelen, SINTEF & University of Oslo, Norway Yao-Hua Tan, Free University of Amsterdam, Holland Sotirios Terzis, University of Strathclyde, UK Dimitris Tsigos, Virtual Trip Ltd, Greece Stavroula Tsinorema, University of Crete, Greece Andrew Twigg, University of Cambridge, UK Emily Weitzenboeck, NRCCL-University of Oslo, Norway Marianne Winslett, University of Illinois at Urbana-Champaign, USA _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 24 07:45:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17886 for ; Wed, 24 Nov 2004 07:45:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWwaO-0006Br-Vv for manet-web-archive@ietf.org; Wed, 24 Nov 2004 07:49:30 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWwUJ-0005Ua-3r; Wed, 24 Nov 2004 07:43:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWwNe-0004N3-OY for manet@megatron.ietf.org; Wed, 24 Nov 2004 07:36:18 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17361 for ; Wed, 24 Nov 2004 07:36:17 -0500 (EST) Received: from web26405.mail.ukl.yahoo.com ([217.146.176.29]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CWwRW-0005Hl-E4 for manet@ietf.org; Wed, 24 Nov 2004 07:40:18 -0500 Received: (qmail 50490 invoked by uid 60001); 24 Nov 2004 12:35:44 -0000 Message-ID: <20041124123544.50488.qmail@web26405.mail.ukl.yahoo.com> Received: from [193.95.33.18] by web26405.mail.ukl.yahoo.com via HTTP; Wed, 24 Nov 2004 13:35:44 CET Date: Wed, 24 Nov 2004 13:35:44 +0100 (CET) From: amine elabidi To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id HAA17361 Subject: [manet] autoconfiguration in manet networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: quoted-printable i would like to know about new researchs in autoconfiguration of IP address in ad hoc networks Thanks =09 =09 =09 Vous manquez d=92espace pour stocker vos mails ?=20 Yahoo! Mail vous offre GRATUITEMENT 100 Mo ! Cr=E9ez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/ Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveau= t=E9s pour dialoguer instantan=E9ment avec vos amis. A t=E9l=E9charger gr= atuitement sur http://fr.messenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 24 10:39:47 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04518 for ; Wed, 24 Nov 2004 10:39:46 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWzJ8-00071p-Kq for manet-web-archive@ietf.org; Wed, 24 Nov 2004 10:43:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWzBu-0001Y9-QV; Wed, 24 Nov 2004 10:36:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CWz48-0000Ai-3M for manet@megatron.ietf.org; Wed, 24 Nov 2004 10:28:21 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03816 for ; Wed, 24 Nov 2004 10:28:17 -0500 (EST) Received: from aplexpony.dom1.jhuapl.edu ([128.244.198.131]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CWz80-00066B-1P for manet@ietf.org; Wed, 24 Nov 2004 10:32:21 -0500 Received: from APLESLIBERTY.dom1.jhuapl.edu ([128.244.198.134]) by APLEXPONY.dom1.jhuapl.edu with Microsoft SMTPSVC(6.0.3790.0); Wed, 24 Nov 2004 10:27:41 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [manet] TCP Retransmission and Goodput Date: Wed, 24 Nov 2004 10:27:41 -0500 Message-ID: <0F5AC32D8E455545AD0349BA8400A3CA1B0485@aplesliberty.dom1.jhuapl.edu> Thread-Topic: [manet] TCP Retransmission and Goodput Thread-Index: AcTRtt5vEwp69jK8Sy+9E7BKvycP0AAgN7WA From: "Farrag, Osama" To: X-OriginalArrivalTime: 24 Nov 2004 15:27:41.0358 (UTC) FILETIME=[233134E0:01C4D23A] X-Spam-Score: 0.0 (/) X-Scan-Signature: 43317e64100dd4d87214c51822b582d1 Content-Transfer-Encoding: quoted-printable X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b8f3559805f7873076212d6f63ee803e Content-Transfer-Encoding: quoted-printable The exposed node impacts overall network capacity, The original email = measure "one TCP flow". In this case, you would get better protection = for this flow. Contentions, collisions, and hidden nodes contributions, = most likely from the four hop forwarding nodes topology and the two = nodes terminating the full-duplex TCP flow. I agree with RAM that the = beneficial impact of CTS/RTS on goodput is reduced when operating at = 54M. Regards Osama=20 =20 -----Original Message----- From: Liaw, Yong Shyang - LIAYS001 = [mailto:Yong.Liaw@postgrads.unisa.edu.au]=20 Sent: Tuesday, November 23, 2004 6:47 PM To: 'Ram Ramanathan'; Farrag, Osama Cc: manet@ietf.org Subject: RE: [manet] TCP Retransmission and Goodput Below is a paper that shows with RTS/CTS off is better than RTS/CTS on = for ad-hoc network.=20 Aruna Jayasuriya, Sylvie Perreau, Arek Dadej, Steven Gordon, "Hidden vs. Exposed Terminal Problem in Ad hoc Networks", Proc. of Australian Telecommunication Networks and Applications Conference (ATNAC 2004), Dec = 2004. http://www.itr.unisa.edu.au/~sgordon/research/publications -----Original Message----- From: Ram Ramanathan [mailto:ramanath@bbn.com]=20 Sent: Wednesday, 24 November 2004 9:53 AM To: Farrag, Osama Cc: manet@ietf.org Subject: Re: [manet] TCP Retransmission and Goodput Is this really true in practice -- that 802.11 networks have better=20 goodput when RTS/CTS is turned on? Researchers doing experimental work with testbeds more often than not=20 report better throughput with RTS/CTS turned off (at least those I've=20 spoken to), hidden terminals notwithstanding. While RTS/CTS solves the hidden terminal problem, it does introduce=20 exposed terminals, and the overhead of the handshake. And in some=20 cases, the negatives may be more than the positives. For instance, at=20 high data rates (e.g. 54 Mbps) the time for RTS/CTS as a fraction of=20 total packet transfer time gets to be significant, especially if=20 RTS/CTS are sent at lower data rate as is typical. I'm not disputing your statement, but do you (or anyone on this list)=20 know of any study that corrobarates this statement? Are there=20 comprehensive simulation or testbed based studies on this and does one=20 differ from the other in conclusions? If so, I'd appreciate a pointer. It would be good for the community to really understand the benefits of=20 RTS/CTS for ad hoc networks. cheers, -Ram On Nov 23, 2004, at 5:23 PM, Farrag, Osama wrote: > Ehsan, > > =A0 > > There could be many factors, in general 802.11 networks perform better = > in terms goodput when RTS/CTS handshake is used. > > =A0 > > a)=A0=A0=A0=A0=A0=A0RTS/CTS mode allows nodes to detect collision = faster than in=20 > Data/ACK mode because Data messages are much longer than RTS messages. = > So the channel revert to idle state faster and nodes will start=20 > contending again in shorter time. > > b)=A0=A0=A0=A0=A0=A0Probability of collisions from Hidden node problem = is reduced=20 > when RTS/CTS handshake is used. Less collision results in better=20 > throughput. > > =A0 > > Hope that helps. > > =A0 > > Best Regards > > Osama Farrag > > Johns Hopkins University/ APL > > =A0 > > -----Original Message----- > From:manet-bounces@ietf.org [mailto:manet-bounces@ietf.org]On Behalf=20 > OfEhsan Hamadani > Sent: Tuesday, November 23, 2004 4:34 PM > To:manet@ietf.org > Subject:[manet] TCP Retransmission and Goodput > > =A0 > > Hi all, > > =A0 > > I am simulating a 4 hop static network with one TCP flow between the=20 > sender and receiver. There are 2 scenarios: One scenario (let's call=20 > it scenario 1) is based on RTS/CTS message exchange for packets larger = > than 1024 Bytes and the other one (scenario 2) does not use any=20 > RTS/CTS to send data over network. > > When I monitor thebehaviourof TCP in the network, I come across the=20 > following issue: > > =A0 > > While scenario 1 has less average congestion window size and flight=20 > size (number of sent and unacknowledged data in network) with higher=20 > number of TCP retransmission in comparison to scenario 2, the goodput=20 > of scenario 1 is greater than scenario 2!!!=A0=A0=A0 > > =A0 > > For measuring the goodput, I am monitoring the sent sequence number by = > sender. So, for instance, at time 50sec, the sender in scenario 1 is=20 > sending packet with sequence number 10000 while the sender in scenario = > 2 is sending packet with sequence number 6000. > > =A0 > > Does anyone know the reason behind this? > > =A0 > > Thanks for your help > > =A0 > > Ehsan > > =A0 > > ----------------------------------------- > > Ehsan Hamadani, PhD student > > SchoolofEngineeringand Math Science > > City University > > London,EC1V 0HB > > United Kingdom > > =A0 > > Office:+44 (0)207 040 3886 > > =A0 > > =A0 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Nov 24 18:59:35 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18343 for ; Wed, 24 Nov 2004 18:59:35 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CX76u-0001sW-Nh for manet-web-archive@ietf.org; Wed, 24 Nov 2004 19:03:44 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CX70Y-0003o9-N9; Wed, 24 Nov 2004 18:57:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CX6zC-0003RT-1v for manet@megatron.ietf.org; Wed, 24 Nov 2004 18:55:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18047 for ; Wed, 24 Nov 2004 18:55:42 -0500 (EST) Received: from ms-smtp-02-lbl.southeast.rr.com ([24.25.9.101] helo=ms-smtp-02-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CX739-0001m0-BH for manet@ietf.org; Wed, 24 Nov 2004 18:59:51 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-02-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iAONtd4R012890 for ; Wed, 24 Nov 2004 18:55:41 -0500 (EST) From: "Christopher P. Rigano" To: Date: Wed, 24 Nov 2004 18:55:38 -0500 Message-ID: <000001c4d281$193367f0$0300a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.1 (/) X-Scan-Signature: 2e8fc473f5174be667965460bd5288ba Subject: [manet] MANET Transport Protocols X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1136742527==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff This is a multi-part message in MIME format. --===============1136742527== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C4D257.30606D30" This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C4D257.30606D30 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings could someone point me to references on MANET Transport and upper layer protocols. Thanks and happy "turkey", Chris ------=_NextPart_000_0001_01C4D257.30606D30 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings could someone point me to references on = MANET Transport and upper layer protocols.

 

Thanks and happy = “turkey”,

 

Chris

------=_NextPart_000_0001_01C4D257.30606D30-- --===============1136742527== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1136742527==-- From manet-bounces@ietf.org Wed Nov 24 19:52:14 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22137 for ; Wed, 24 Nov 2004 19:52:13 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CX7vr-000314-US for manet-web-archive@ietf.org; Wed, 24 Nov 2004 19:56:24 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CX7nA-0005MZ-Ey; Wed, 24 Nov 2004 19:47:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CX7iY-0004TO-1z for manet@megatron.ietf.org; Wed, 24 Nov 2004 19:42:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA21543 for ; Wed, 24 Nov 2004 19:42:34 -0500 (EST) Received: from web25009.mail.ukl.yahoo.com ([217.12.10.45]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CX7mV-0002p7-M2 for manet@ietf.org; Wed, 24 Nov 2004 19:46:44 -0500 Received: (qmail 8804 invoked by uid 60001); 25 Nov 2004 00:42:05 -0000 Message-ID: <20041125004205.8802.qmail@web25009.mail.ukl.yahoo.com> Received: from [62.252.0.10] by web25009.mail.ukl.yahoo.com via HTTP; Thu, 25 Nov 2004 00:42:05 GMT Date: Thu, 25 Nov 2004 00:42:05 +0000 (GMT) From: l s To: manet@ietf.org In-Reply-To: <000001c4d281$193367f0$0300a8c0@CPQ73745201364> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.1 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: 8bit Subject: [manet] where does OLSR loss most occur in lightly loaded networks? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: 8bit Dear researchers, I have a question for those most familiar with OLSR. I am comparing AODV and OLSR in lightly loaded networks. I am much less familiar with how OLSR internally operates than I am with AODV. I have 20 applications running (CBR 4 packets per sec) in the network of 50 nodes moving Random Way Point in 1500x300. There is no loss from Queue Overflow. AODV has 3% Transport Loss (loss occuring somewhere between departure from the source's transport layer and arrival at the distination's transport layer) whilst OLSR has 36% Transport Loss. The number of Radio Collisions are 3 times lower in OLSR than in AODV, so where and how is the most likely way in which the OLSR loss is occuring. Thanks in advance for your thoughts. Cheers, Lee -S- CCSR, Uni of Surrey, UK. ___________________________________________________________ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 25 03:51:29 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16444 for ; Thu, 25 Nov 2004 03:51:29 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXFPi-0005I8-6J for manet-web-archive@ietf.org; Thu, 25 Nov 2004 03:55:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXFIZ-00080z-8a; Thu, 25 Nov 2004 03:48:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXFHX-0007Cq-QK for manet@megatron.ietf.org; Thu, 25 Nov 2004 03:47:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16031 for ; Thu, 25 Nov 2004 03:47:14 -0500 (EST) Received: from xenon2.um.es ([155.54.212.101] helo=smtp.um.es) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXFLX-0005AY-69 for manet@ietf.org; Thu, 25 Nov 2004 03:51:26 -0500 Received: from smtp.um.es (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id D9760307C8 for ; Thu, 25 Nov 2004 09:46:34 +0100 (CET) Received: from aries.dif.um.es (aries.dif.um.es [155.54.210.253]) by smtp.um.es (Postfix) with SMTP id 96B2718926 for ; Thu, 25 Nov 2004 09:46:34 +0100 (CET) Received: (qmail 15484 invoked from network); 25 Nov 2004 08:46:06 -0000 Received: from cartman.dif.um.es (155.54.210.126) by aries.dif.um.es with SMTP; 25 Nov 2004 08:46:06 -0000 From: "Francisco J. Ros" Organization: Universidad de Murcia To: manet@ietf.org Subject: Re: [manet] where does OLSR loss most occur in lightly loaded networks? Date: Thu, 25 Nov 2004 09:47:12 +0100 User-Agent: KMail/1.7 References: <20041125004205.8802.qmail@web25009.mail.ukl.yahoo.com> In-Reply-To: <20041125004205.8802.qmail@web25009.mail.ukl.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200411250947.12705.fjrm@dif.um.es> X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Content-Transfer-Encoding: quoted-printable Cc: l s X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Content-Transfer-Encoding: quoted-printable Hi, I guess that mobility could be the cause of your results. With high mobilit= y=20 AODV behaves better than OLSR because it can adapt itself fastly to changes= =20 in the network topology. Imagine a node must forward a data packet but it has no route for it (this= =20 happens often in high mobility scenarios). In the case of AODV, the node=20 initiates a route search process which may result in a valid route. But OLS= R=20 simply drops the packet. If yor network is (almost) static, then forget what I told you ;). Please=20 correct me if someone thinks I'm wrong. Best regards, =46rancisco J. Ros El Jueves, 25 de Noviembre de 2004 01:42, l s escribi=F3: > Dear researchers, > > I have a question for those most familiar with OLSR. > > I am comparing AODV and OLSR in lightly loaded > networks. I am much less familiar with how OLSR > internally operates than I am with AODV. > > I have 20 applications running (CBR 4 packets per sec) > in the network of 50 nodes moving Random Way Point in > 1500x300. There is no loss from Queue Overflow. > > AODV has 3% Transport Loss (loss occuring somewhere > between departure from the source's transport layer > and arrival at the distination's transport layer) > whilst OLSR has 36% Transport Loss. > The number of Radio Collisions are 3 times lower in > OLSR than in AODV, so where and how is the most likely > way in which the OLSR loss is occuring. > > Thanks in advance for your thoughts. > > Cheers, > Lee -S- > CCSR, Uni of Surrey, UK. > > > > > ___________________________________________________________ > Win a castle for NYE with your mates and Yahoo! Messenger > http://uk.messenger.yahoo.com > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 25 04:07:02 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18053 for ; Thu, 25 Nov 2004 04:07:02 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXFek-0005ml-Jp for manet-web-archive@ietf.org; Thu, 25 Nov 2004 04:11:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXFVs-0003gm-TT; Thu, 25 Nov 2004 04:02:04 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXFMg-0000pM-QH for manet@megatron.ietf.org; Thu, 25 Nov 2004 03:52:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16579 for ; Thu, 25 Nov 2004 03:52:33 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.193]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXFQi-0005Jr-IL for manet@ietf.org; Thu, 25 Nov 2004 03:56:45 -0500 Received: by rproxy.gmail.com with SMTP id a36so158114rnf for ; Thu, 25 Nov 2004 00:52:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=fCjYch8/ZZLO1HWTiTtrRG8a0jcFmc7yYmiEXWCjW4FndJmzMtEsNEo6o3gfO92RTu0114XwQXQLHWhPoq8F2Lue2z+8gxv8AfUSvWN5/35eX/LsyICi8kTUrSpDSNwVaRXCNv2WTPFzzCje0nC/Y/XgFnzBaVxFR2H4Ccwgp1M= Received: by 10.38.171.64 with SMTP id t64mr48143rne; Thu, 25 Nov 2004 00:52:32 -0800 (PST) Received: by 10.38.79.55 with HTTP; Thu, 25 Nov 2004 00:52:32 -0800 (PST) Message-ID: <27233685041125005210b78c1d@mail.gmail.com> Date: Thu, 25 Nov 2004 13:52:32 +0500 From: Muhammad Mustafa Rafique To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7bit Subject: [manet] Good "Multicast routing in MANET" References! X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Muhammad Mustafa Rafique List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Hi All, I am a student working on MS thesis in the area of multicasting in MANET. I've read several papers on multicasting techniques but unable to find any paper which gives a good overview of multicast routing in MANET. Is there anyone on the list who can quote me some good references to get an overview of multicast routing techniques in MANET. I would be very thankful. Best regards, Muhammad Mustafa Rafique! _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 25 04:43:40 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21322 for ; Thu, 25 Nov 2004 04:43:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXGED-0006eA-PK for manet-web-archive@ietf.org; Thu, 25 Nov 2004 04:47:53 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXFzu-0003Bf-7T; Thu, 25 Nov 2004 04:33:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXFwL-00022o-8u for manet@megatron.ietf.org; Thu, 25 Nov 2004 04:29:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20245 for ; Thu, 25 Nov 2004 04:29:23 -0500 (EST) Received: from mail.icu.ac.kr ([210.107.128.19] helo=icu.ac.kr) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXG0M-0006Jn-TZ for manet@ietf.org; Thu, 25 Nov 2004 04:33:36 -0500 Received: from doggy (Debian-exim@v85-109.icu.ac.kr [220.69.185.109]) by icu.ac.kr (8.12.10/8.12.8) with ESMTP id iAP9KIj7005812; Thu, 25 Nov 2004 18:20:18 +0900 (KST) Received: from newcat by doggy with local (Exim 4.34) id 1CXFxX-0003z2-PI; Thu, 25 Nov 2004 18:30:39 +0900 Date: Thu, 25 Nov 2004 18:30:39 +0900 From: YangWoo Ko To: Muhammad Mustafa Rafique Subject: Re: [manet] Good "Multicast routing in MANET" References! Message-ID: <20041125093039.GA14455@doggy> References: <27233685041125005210b78c1d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <27233685041125005210b78c1d@mail.gmail.com> User-Agent: Mutt/1.5.6+20040907i X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Dealt a couple of days ago. ;-) http://www1.ietf.org/mail-archive/web/manet/current/msg06131.html On Thu, Nov 25, 2004 at 06:04:12PM +0900, Muhammad Mustafa Rafique wrote: > > Hi All, > > I am a student working on MS thesis in the area of multicasting in > MANET. I've read several papers on multicasting techniques but unable > to find any paper which gives a good overview of multicast routing in > MANET. > > Is there anyone on the list who can quote me some good references to > get an overview of multicast routing techniques in MANET. I would be > very thankful. > > Best regards, > Muhammad Mustafa Rafique! > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > > -- /*------------------------------------------------ The ones doing their job, doing what they were meant to do, are invisible. -- Matrix Reloaded Ko, YangWoo / Searcher / newcat@icu.ac.kr ------------------------------------------------*/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 25 04:54:53 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22481 for ; Thu, 25 Nov 2004 04:54:53 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXGP4-0006x1-I5 for manet-web-archive@ietf.org; Thu, 25 Nov 2004 04:59:06 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXGIL-0006tF-LT; Thu, 25 Nov 2004 04:52:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXGGp-0006XC-NW for manet@megatron.ietf.org; Thu, 25 Nov 2004 04:50:35 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22091 for ; Thu, 25 Nov 2004 04:50:33 -0500 (EST) From: Hakim.Badis@lri.fr Received: from ext.lri.fr ([129.175.15.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXGKf-0006oF-69 for manet@ietf.org; Thu, 25 Nov 2004 04:54:46 -0500 Received: from localhost (localhost [127.0.0.1]) by ext.lri.fr (Postfix) with ESMTP id C329219E70D; Thu, 25 Nov 2004 10:49:38 +0100 (CET) Received: from ext.lri.fr ([127.0.0.1]) by localhost (ext.lri.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03652-02; Thu, 25 Nov 2004 10:49:38 +0100 (CET) Received: from www.lri.fr (newww [129.175.15.10]) by ext.lri.fr (Postfix) with ESMTP id AEE7E19E6F3; Thu, 25 Nov 2004 10:49:38 +0100 (CET) Received: from pc11-175 ([129.175.11.175]) (SquirrelMail authenticated user badis); by www.lri.fr with HTTP; Thu, 25 Nov 2004 10:49:38 +0100 (CET) Message-ID: <1235.129.175.11.175.1101376178.squirrel@www.lri.fr> In-Reply-To: <20041125004205.8802.qmail@web25009.mail.ukl.yahoo.com> References: <000001c4d281$193367f0$0300a8c0@CPQ73745201364> <20041125004205.8802.qmail@web25009.mail.ukl.yahoo.com> Date: Thu, 25 Nov 2004 10:49:38 +0100 (CET) Subject: Re: [manet] where does OLSR loss most occur in lightly loaded networks? To: "l s" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new at lri.fr X-Spam-Score: 0.3 (/) X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id EAA22091 Cc: manet@ietf.org X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Content-Transfer-Encoding: quoted-printable Hi Lee ;=3D=3D) In OLSR, when a node moves, it goes out of the neighborhood of a node which may be sending it the data packets. The data packets are lost because the next-hop node is unreachable. A node keeps an entry about its neighbor in its neighbor table for about 3 x Hello_interval seconds. If a neighbor moves which is the next-hop node in a route, the node continues to forward it the data packets. only after the entry expiration, the link failure could be detected. Also few of the packets are lost because of the unavailability. This happen: 1) at the begin of the simulation, a node need a time to exchange vicinity and topology information to build its routing table. So, in your simulation, it=92s preferable to start packets transmission after few seconds, and use a default route (a neighbor node which is an MPR that covers the maximum number of 2-hop nodes or a simple neighbor is the source node has not yet selected an MPR). 2) when a node movement causes the node to be disconnected from the network temporarily. OLSR (with hello interval of 2 secondes, and neighbor entries life time o= f 6 secondes) supports the mobility of nodes but at low speeds. When the speed increases, packet loss increases. To deal with this problem (high speeds), you can decrease the hello interval and neighbor life time values. This is the objective of the Fast-OLSR protocol. Fast-OLSR is proposed by INRIA & LRI laboratories. You can see this paper: =93Analysis and simulation of Fast-OLSR=94 In proceedings of the 57th IEEE Semiannua= l Vehicular Technology Conference (VTC), Jeju Korea, April 2003. Hakim. > Dear researchers, > > I have a question for those most familiar with OLSR. > > I am comparing AODV and OLSR in lightly loaded > networks. I am much less familiar with how OLSR > internally operates than I am with AODV. > > I have 20 applications running (CBR 4 packets per sec) > in the network of 50 nodes moving Random Way Point in > 1500x300. There is no loss from Queue Overflow. > > AODV has 3% Transport Loss (loss occuring somewhere > between departure from the source's transport layer > and arrival at the distination's transport layer) > whilst OLSR has 36% Transport Loss. > The number of Radio Collisions are 3 times lower in > OLSR than in AODV, so where and how is the most likely > way in which the OLSR loss is occuring. > > Thanks in advance for your thoughts. > > Cheers, > Lee -S- > CCSR, Uni of Surrey, UK. > > > > > ___________________________________________________________ > Win a castle for NYE with your mates and Yahoo! Messenger > http://uk.messenger.yahoo.com > > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 25 08:40:53 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11639 for ; Thu, 25 Nov 2004 08:40:52 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXJvm-0003no-Em for manet-web-archive@ietf.org; Thu, 25 Nov 2004 08:45:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXJo9-0006Nh-Qe; Thu, 25 Nov 2004 08:37:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXJiv-0005YT-I6 for manet@megatron.ietf.org; Thu, 25 Nov 2004 08:31:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11115 for ; Thu, 25 Nov 2004 08:31:48 -0500 (EST) Received: from web20924.mail.yahoo.com ([216.136.224.139]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CXJn0-0003do-Ht for manet@irtf.org; Thu, 25 Nov 2004 08:36:02 -0500 Received: (qmail 47928 invoked by uid 60001); 25 Nov 2004 13:31:47 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=OBqAHAbfFswDWOue4eRe+Si3fCUAQ9sGSIdCe1Mf2OkJL1aGqkw2YJEpjq8C66HvCywqGZMYeWXEaKz0Whmgh2bx2g//Rnga7/Fw6tPpe/zksRB2s44ubXf61qAX+Vil6HtWvtS/nM2eFdqb0BrytnxoepjIpbv39VugY3H/d1Q= ; Message-ID: <20041125133147.47926.qmail@web20924.mail.yahoo.com> Received: from [203.208.193.230] by web20924.mail.yahoo.com via HTTP; Thu, 25 Nov 2004 05:31:47 PST Date: Thu, 25 Nov 2004 05:31:47 -0800 (PST) From: Praveen Choudary To: manet@irtf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Subject: [manet] 802.16 in WSN X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1976263191==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 --===============1976263191== Content-Type: multipart/alternative; boundary="0-386316240-1101389507=:47902" --0-386316240-1101389507=:47902 Content-Type: text/plain; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id IAA11115 Content-Transfer-Encoding: quoted-printable Hi, I am mainly interested in multi-hop Wireless Sensor Networks. Are there = any publications which talk about using 802.16 in Wireless Sensor Network= s(WSN) . I have came across publications which use 802.11 in WSN. Many MA= C protocols have been proposed for WSN like S-MAC, T-MAC etc. Many routin= g schemes assume 802.11 based MAC scheme. =20 I want to know, which is better to use 802.11 or 802.16. Are there any p= ublications related to WSN which assume 802.16. If MAC protocols like S-M= AC, T-MAC etc are proposed especially for WSN then why are people using 8= 02.11. Can anybody tell me the applications or situation when to use 802.= 11, 802.16 and S-MAC in wireless sensor networks. =20 I am asking this question because the S-MAC, T-MAC etc says 802.11 is not= suitable for WSN. They say that " PS mode in 802.11 DCF is designed for = a single-hop network. Generalizing it to multi-hop network is not easy, s= ince problems may arise in clock synchronization, neighbour discovery and= network partioning". On the other side there are many publications whic= h assume 802.11 for multi-hop wireless sensor networks.=20 =20 I request the researchers in this group to give their comments and sugges= tions. Praveen. =09 --------------------------------- Do you Yahoo!? All your favorites on one personal page =96 Try My Yahoo! --0-386316240-1101389507=:47902 Content-Type: text/html; charset=us-ascii X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id IAA11115 Content-Transfer-Encoding: quoted-printable
Hi,
 I am mainly interested in multi-hop Wireless Sensor Networks. = Are there any publications which talk about using 802.16 in Wireless Sens= or Networks(WSN) . I have came across publications which use 802.11 in WS= N. Many MAC protocols have been proposed for WSN like S-MAC, T-MAC etc. M= any routing schemes assume 802.11 based MAC scheme.
 
I want to know, which is better to use 802.11 or 802.16.  Are t= here any publications related to WSN which assume 802.16. If MAC protocol= s like S-MAC, T-MAC etc are proposed especially for WSN then why are= people using 802.11. Can anybody tell me the applications or situation w= hen to use 802.11,  802.16 and S-MAC in wireless sensor network= s.
 
I am asking this question because the S-MAC, T-MAC etc say= s 802.11 is not suitable for WSN. They say that " PS mode in 802.11 = DCF is designed for a single-hop network. Generalizing it to multi-hop ne= twork is not easy, since problems may arise in clock synchronization, nei= ghbour discovery and network partioning".  On the other side there a= re many publications which assume 802.11 for multi-hop wireless sensor ne= tworks.
 
I request the researchers in this group to give their comments and s= uggestions.
Praveen.

Do you Yahoo!?
=20 All your favorites on one personal page =96 Try My Yahoo! --0-386316240-1101389507=:47902-- --===============1976263191== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1976263191==-- From manet-bounces@ietf.org Thu Nov 25 09:11:05 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14640 for ; Thu, 25 Nov 2004 09:11:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXKP2-0004as-SF for manet-web-archive@ietf.org; Thu, 25 Nov 2004 09:15:21 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXKD5-0003zx-1T; Thu, 25 Nov 2004 09:02:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXK7j-0002Vt-NZ for manet@megatron.ietf.org; Thu, 25 Nov 2004 08:57:27 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA13457 for ; Thu, 25 Nov 2004 08:57:26 -0500 (EST) Received: from nez-perce.inria.fr ([192.93.2.78]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXKBo-0004FE-SX for manet@ietf.org; Thu, 25 Nov 2004 09:01:41 -0500 Received: from yamacraw.inria.fr (yamacraw.inria.fr [128.93.24.137]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id iAPDurS1016489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Nov 2004 14:56:53 +0100 Received: from yamacraw.inria.fr (localhost [127.0.0.1]) by yamacraw.inria.fr (8.13.0/8.13.0) with ESMTP id iAPDuqB0030252; Thu, 25 Nov 2004 14:56:52 +0100 Received: (from apache@localhost) by yamacraw.inria.fr (8.13.0/8.12.10/Submit) id iAPDuqDf030249; Thu, 25 Nov 2004 14:56:52 +0100 X-Authentication-Warning: yamacraw.inria.fr: apache set sender to philippe.jacquet@inria.fr using -f Received: from oracle.polytechnique.fr (oracle.polytechnique.fr [129.104.11.57]) by pops-rocq.inria.fr (IMP) with HTTP for ; Thu, 25 Nov 2004 14:56:51 +0100 Message-ID: <1101391011.41a5e4a3dab29@pops-rocq.inria.fr> Date: Thu, 25 Nov 2004 14:56:51 +0100 From: Philippe Jacquet To: Hakim.Badis@lri.fr Subject: Re: [manet] where does OLSR loss most occur in lightly loaded networks? References: <000001c4d281$193367f0$0300a8c0@CPQ73745201364> <20041125004205.8802.qmail@web25009.mail.ukl.yahoo.com> <1235.129.175.11.175.1101376178.squirrel@www.lri.fr> In-Reply-To: <1235.129.175.11.175.1101376178.squirrel@www.lri.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 User-Agent: Internet Messaging Program (IMP) 3.2.2 X-Originating-IP: 129.104.11.57 X-Miltered: at nez-perce with ID 41A5E4A5.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by nez-perce.inria.fr id iAPDurS1016489 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813 Content-Transfer-Encoding: quoted-printable Cc: manet@ietf.org, l s X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7 Content-Transfer-Encoding: quoted-printable Hello, Please notice that fast OLSR is in some way included in the RFC with vari= able Hello rate time and variable neighbor holding time. I also agree with Fra= ncisco that the discrepancies could also come from link buffering or link failur= e notification options.=20 Philippe Quoting Hakim.Badis@lri.fr: > Hi Lee ;=3D=3D) >=20 > In OLSR, when a node moves, it goes out of the neighborhood of a node > which may be sending it the data packets. The data packets are lost > because the next-hop node is unreachable. A node keeps an entry about i= ts > neighbor in its neighbor table for about 3 x Hello_interval seconds. If= a > neighbor moves which is the next-hop node in a route, the node continue= s > to forward it the data packets. only after the entry expiration, the li= nk > failure could be detected. Also few of the packets are lost because of > the unavailability. This happen: 1) at the begin of the simulation, a > node need a time to exchange vicinity and topology information to build > its routing table. So, in your simulation, it=92s preferable to start > packets transmission after few seconds, and use a default route (a > neighbor node which is an MPR that covers the maximum number of 2-hop > nodes or a simple neighbor is the source node has not yet selected an > MPR). 2) when a node movement causes the node to be disconnected from t= he > network temporarily. >=20 > OLSR (with hello interval of 2 secondes, and neighbor entries life time= of > 6 secondes) supports the mobility of nodes but at low speeds. When the > speed increases, packet loss increases. To deal with this problem (high > speeds), you can decrease the hello interval and neighbor life time > values. This is the objective of the Fast-OLSR protocol. Fast-OLSR is > proposed by INRIA & LRI laboratories. You can see this paper: =93Analys= is > and simulation of Fast-OLSR=94 In proceedings of the 57th IEEE Semiann= ual > Vehicular Technology Conference (VTC), Jeju Korea, April 2003. >=20 > Hakim. >=20 >=20 >=20 > > Dear researchers, > > > > I have a question for those most familiar with OLSR. > > > > I am comparing AODV and OLSR in lightly loaded > > networks. I am much less familiar with how OLSR > > internally operates than I am with AODV. > > > > I have 20 applications running (CBR 4 packets per sec) > > in the network of 50 nodes moving Random Way Point in > > 1500x300. There is no loss from Queue Overflow. > > > > AODV has 3% Transport Loss (loss occuring somewhere > > between departure from the source's transport layer > > and arrival at the distination's transport layer) > > whilst OLSR has 36% Transport Loss. > > The number of Radio Collisions are 3 times lower in > > OLSR than in AODV, so where and how is the most likely > > way in which the OLSR loss is occuring. > > > > Thanks in advance for your thoughts. > > > > Cheers, > > Lee -S- > > CCSR, Uni of Surrey, UK. > > > > > > > > > > ___________________________________________________________ > > Win a castle for NYE with your mates and Yahoo! Messenger > > http://uk.messenger.yahoo.com > > > > _______________________________________________ > > manet mailing list > > manet@ietf.org > > https://www1.ietf.org/mailman/listinfo/manet > > >=20 >=20 >=20 > _______________________________________________ > manet mailing list > manet@ietf.org > https://www1.ietf.org/mailman/listinfo/manet >=20 >=20 --=20 Philippe Jacquet Hipercom project team leader INRIA tel: +33 1 39 63 52 63 fax: +33 1 39 63 55 66 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 25 09:30:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA16094 for ; Thu, 25 Nov 2004 09:30:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXKhn-00054V-MV for manet-web-archive@ietf.org; Thu, 25 Nov 2004 09:34:43 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXKYc-0001Wd-Mb; Thu, 25 Nov 2004 09:25:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXKVW-0000ei-9j for manet@megatron.ietf.org; Thu, 25 Nov 2004 09:22:02 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15514 for ; Thu, 25 Nov 2004 09:22:00 -0500 (EST) Received: from lennier.cc.vt.edu ([198.82.162.213]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXKZb-0004sX-UO for manet@ietf.org; Thu, 25 Nov 2004 09:26:16 -0500 Received: from zidane.cc.vt.edu (IDENT:mirapoint@evil-zidane.cc.vt.edu [10.1.1.13]) by lennier.cc.vt.edu (8.12.11/8.12.11) with ESMTP id iAPEJEr2030941; Thu, 25 Nov 2004 09:19:14 -0500 Received: from qwertyuiop2003 (sun.irean.vt.edu [128.173.52.26]) by zidane.cc.vt.edu (MOS 3.4.8-GR) with SMTP id CBE02815; Thu, 25 Nov 2004 09:21:23 -0500 (EST) Message-ID: <000e01c4d2fa$09e86a60$6401a8c0@qwertyuiop2003> From: "Tao Lin" To: Subject: Re: [manet] where does OLSR loss most occur in lightly loaded networks? Date: Thu, 25 Nov 2004 09:21:21 -0500 Organization: Virginia Tech MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" 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 X-MIME-Autoconverted: from 8bit to quoted-printable by lennier.cc.vt.edu id iAPEJEr2030941 X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: quoted-printable Cc: quantumparadox@yahoo.co.uk X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tao Lin List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4 Content-Transfer-Encoding: quoted-printable One reason is that in AODV, there is a data packet queue which holds pack= ets up to 10 seconds if there is no valid route or the original route fails. = In OLSR, there is no such queue. Once the packet delivery to neighboring no= de fails, that packet is discarded immediately. Therefore, the data packet queue is kind of "unfair" comparison condition (which is required by reactive protocols). My suggestion is to implement the same queue for OL= SR as well when compare it with AODV. Of course, another important reason is that AODV reacts faster than OLSR since it tries to find a new route once a route broken is detected. OLSR= 's link state requires a longer converge time when a topology change occurs = due to constant hello interval and propagation delay of MPRS control messages. However, on the other hands, AODV does have increasing control overhead w= hen the network topology changes faster. You can refer to one of my paper or PhD dissertation for more details on discussion on different MANET leading protocols from a general relay node set framework's point of view. Best, Tao Lin, Post-doc ECE Department, McMaster University Hamilton, ON, Canada El Jueves, 25 de Noviembre de 2004 01:42, l s escribi=A8=AE: > Dear researchers, > > I have a question for those most familiar with OLSR. > > I am comparing AODV and OLSR in lightly loaded > networks. I am much less familiar with how OLSR > internally operates than I am with AODV. > > I have 20 applications running (CBR 4 packets per sec) > in the network of 50 nodes moving Random Way Point in > 1500x300. There is no loss from Queue Overflow. > > AODV has 3% Transport Loss (loss occuring somewhere > between departure from the source's transport layer > and arrival at the distination's transport layer) > whilst OLSR has 36% Transport Loss. > The number of Radio Collisions are 3 times lower in > OLSR than in AODV, so where and how is the most likely > way in which the OLSR loss is occuring. > > Thanks in advance for your thoughts. > > Cheers, > Lee -S- > CCSR, Uni of Surrey, UK. > > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 25 11:36:22 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26636 for ; Thu, 25 Nov 2004 11:36:22 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXMff-00081F-FI for manet-web-archive@ietf.org; Thu, 25 Nov 2004 11:40:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXMXc-0005us-03; Thu, 25 Nov 2004 11:32:20 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXMXD-0005gh-PN for manet@megatron.ietf.org; Thu, 25 Nov 2004 11:31:55 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26203 for ; Thu, 25 Nov 2004 11:31:53 -0500 (EST) Received: from web25107.mail.ukl.yahoo.com ([217.12.10.55]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CXMbK-0007t6-CK for manet@ietf.org; Thu, 25 Nov 2004 11:36:10 -0500 Received: (qmail 86623 invoked by uid 60001); 25 Nov 2004 16:31:23 -0000 Message-ID: <20041125163123.86621.qmail@web25107.mail.ukl.yahoo.com> Received: from [193.95.41.225] by web25107.mail.ukl.yahoo.com via HTTP; Thu, 25 Nov 2004 17:31:23 CET Date: Thu, 25 Nov 2004 17:31:23 +0100 (CET) From: Gadri Moez To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.2 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Subject: [manet] Cooperative Caching X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0385788116==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.6 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 --===============0385788116== Content-Type: multipart/alternative; boundary="0-1398458474-1101400283=:86088" --0-1398458474-1101400283=:86088 Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA26203 Content-Transfer-Encoding: quoted-printable Hello, =20 One proposition to achieve scalability (to size) of ad hoc networks is us= ing of cooperative caching, when each set of nodes shares their caches (s= hares the memories or uses a distributed algorithm to manage their caches= ). There is any advantage of this approach? =20 Thanks. =09 --------------------------------- Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo de stockage ! Cr=E9ez votre Yahoo! Mail Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveau= t=E9s pour dialoguer instantan=E9ment avec vos amis.T=E9l=E9chargez GRATU= ITEMENT ici ! --0-1398458474-1101400283=:86088 Content-Type: text/html; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA26203 Content-Transfer-Encoding: quoted-printable

Hello,

 

One proposition = to achieve scalability (to size) of ad hoc networks is using of cooperati= ve caching, when each set of nodes shares their caches (shares the memori= es or uses a distributed algorithm to manage their caches).

There is any adv= antage of this approach?

 

Thanks.

Cr=E9ez gratuitement votre Yahoo! Mail avec 100 Mo= de stockage !
Cr=E9ez votre Yahoo! Mail

Le nouveau Yahoo! Messenger est arriv=E9 ! D=E9couvrez toutes les nouveaut=E9s pour dialoguer instantan=E9ment a= vec vos amis. T=E9l=E9chargez GRATUITEMENT ici ! --0-1398458474-1101400283=:86088-- --===============0385788116== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0385788116==-- From manet-bounces@ietf.org Thu Nov 25 12:45:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03184 for ; Thu, 25 Nov 2004 12:45:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXNkt-0001DC-9t for manet-web-archive@ietf.org; Thu, 25 Nov 2004 12:50:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXNdg-00085J-BX; Thu, 25 Nov 2004 12:42:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXNcl-0007oZ-De for manet@megatron.ietf.org; Thu, 25 Nov 2004 12:41:44 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02927 for ; Thu, 25 Nov 2004 12:41:40 -0500 (EST) Received: from web25004.mail.ukl.yahoo.com ([217.12.10.40]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CXNgs-000182-CD for manet@ietf.org; Thu, 25 Nov 2004 12:45:59 -0500 Received: (qmail 82561 invoked by uid 60001); 25 Nov 2004 17:41:11 -0000 Message-ID: <20041125174111.82559.qmail@web25004.mail.ukl.yahoo.com> Received: from [62.252.0.10] by web25004.mail.ukl.yahoo.com via HTTP; Thu, 25 Nov 2004 17:41:11 GMT Date: Thu, 25 Nov 2004 17:41:11 +0000 (GMT) From: l s Subject: Re: [manet] where does OLSR loss most occur in lightly loaded networks? To: manet@ietf.org In-Reply-To: <000e01c4d2fa$09e86a60$6401a8c0@qwertyuiop2003> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.1 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Content-Transfer-Encoding: 8bit Cc: Philippe Jacquet , Tao Lin X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: 8bit Thanks Everyone, indeed, OLSR seems to be just dropping the datagrams, compared to AODV holding the packets, being more familiar with AODV I found the OLSR results unbelievable. What you describe can completely explain my results. Thank you. Hakim, the apps start 100s after sim start. Thanks for the detail, and also reference to Fast-OLSR, I'll have a closer look at this. Francisco, Philippe, I've just become aware there are extensions to the glomosim implementation I am using to reduce this with the link notification you mention, which I'll consider along with buffering changes to either AODV or OLSR depending on the application requirements. Tao Lin, with the up to 10s buffering in AODV then datagrams may take a significant amount of time to get across the network, and may then be useless if they are say VoIP datagrams etc. I'll have a think about this. Cheers, Lee -S- CCSR, Uni of Surrey, UK. ___________________________________________________________ Win a castle for NYE with your mates and Yahoo! Messenger http://uk.messenger.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Nov 25 15:47:39 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15300 for ; Thu, 25 Nov 2004 15:47:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXQas-0004vG-HV for manet-web-archive@ietf.org; Thu, 25 Nov 2004 15:51:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXQOo-00044l-VD; Thu, 25 Nov 2004 15:39:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXQOF-0003fl-K1 for manet@megatron.ietf.org; Thu, 25 Nov 2004 15:38:55 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14893 for ; Thu, 25 Nov 2004 15:38:54 -0500 (EST) Received: from ms-smtp-02-lbl.southeast.rr.com ([24.25.9.101] helo=ms-smtp-02-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXQSL-0004mB-UF for manet@ietf.org; Thu, 25 Nov 2004 15:43:13 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-02-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iAPKcm4R029782 for ; Thu, 25 Nov 2004 15:38:49 -0500 (EST) From: "Christopher P. Rigano" To: Date: Thu, 25 Nov 2004 15:38:44 -0500 Message-ID: <000501c4d32e$c186cd90$0300a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.1 (/) X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d Subject: [manet] RE: 802.16.a,e and 802.20 MAC mail lists and references X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0329862452==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c This is a multi-part message in MIME format. --===============0329862452== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C4D304.D8B0C590" This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C4D304.D8B0C590 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings, I know this is not the primary concern of this group, but any pointers are greatly appreciated! I looked at some of the material but the MACs are a mystery! Happy turkey, Chris ------=_NextPart_000_0006_01C4D304.D8B0C590 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings,

 

I know this is not the primary concern of this group, = but any pointers are greatly appreciated! I looked at some of the material = but the MACs are a mystery!

 

Happy turkey,

 

Chris

------=_NextPart_000_0006_01C4D304.D8B0C590-- --===============0329862452== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0329862452==-- From manet-bounces@ietf.org Thu Nov 25 19:57:27 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01496 for ; Thu, 25 Nov 2004 19:57:27 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXUUf-0001TA-Hd for manet-web-archive@ietf.org; Thu, 25 Nov 2004 20:01:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXULM-0008Fx-Aa; Thu, 25 Nov 2004 19:52:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXUJW-0007vf-37 for manet@megatron.ietf.org; Thu, 25 Nov 2004 19:50:18 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00883 for ; Thu, 25 Nov 2004 19:50:14 -0500 (EST) Received: from maru.ajou.ac.kr ([202.30.0.18] helo=mail.ajou.ac.kr) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CXUNg-0001IK-Jw for manet@ietf.org; Thu, 25 Nov 2004 19:54:37 -0500 Received: from spam.ajou.ac.kr ([202.30.0.9]) by maru (Crinity Message Backbone-2.6.23.1) with SMTP ID 324 for ; Fri, 26 Nov 2004 09:50:48 +0900 (KST) Message-ID: <00e201c4d352$03862b00$bbcb6bd2@ajoudayhakyu> From: Faisal Adeem Siddiqui To: manet@ietf.org Date: Fri, 26 Nov 2004 09:51:01 +0900 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 1.9 (+) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Subject: [manet] Difference between Mobile Ad hoc Networks and Spontaneous Networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0838838614==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.4 (+) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 This is a multi-part message in MIME format. --===============0838838614== Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DF_01C4D39D.6FC73930" This is a multi-part message in MIME format. ------=_NextPart_000_00DF_01C4D39D.6FC73930 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi everyone, I want to know what is the key difference between Mobile Ad hoc Networks = and Spontaneous Networks ? To me a Spontaneous Network is the = application level view of a mobile ad hoc network. Other distinction = could be that the mobile ad hoc networks are mostly homogenous with = nodes of similar capabilities and running the same routing protocol = while spontaneous networks can have variety of nodes with varying = capabilities. (correct me if I am wrong) When I search on the Google for Spontaneous Networks, I get many = documents of mobile ad hoc networks and some documents use these terms = interchangeably. I want to know what different technologies are = involved in Spontaneous Networks ? Are there any specialized mechanisms, = routing protocols, service discovery protocols etc. involved in = Spontaneous Networks ? Eagerly waiting for your answers. Thanks. Faisal Adeem Siddiqui ------=_NextPart_000_00DF_01C4D39D.6FC73930 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi everyone,
I want to know what is the = key difference=20 between Mobile Ad hoc Networks and Spontaneous Networks ? To me a = Spontaneous=20 Network is the application level view of a mobile ad hoc network. Other=20 distinction could be that the mobile ad hoc networks are mostly = homogenous=20 with nodes of similar capabilities and running the same routing protocol = while=20 spontaneous networks can have variety of nodes with varying=20 capabilities. (correct me if I am wrong)
When I search on the = Google for=20 Spontaneous Networks, I get many documents of mobile ad hoc = networks=20 and some documents use these terms interchangeably.  I want to = know=20 what different technologies are involved in Spontaneous Networks ? Are = there any=20 specialized mechanisms, routing protocols, service = discovery protocols etc.=20 involved in Spontaneous Networks ?
 
Eagerly waiting for your=20 answers.
Thanks.
Faisal Adeem Siddiqui
 
------=_NextPart_000_00DF_01C4D39D.6FC73930-- --===============0838838614== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0838838614==-- From manet-bounces@ietf.org Fri Nov 26 11:38:33 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27033 for ; Fri, 26 Nov 2004 11:38:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXjBW-0005uW-MZ for manet-web-archive@ietf.org; Fri, 26 Nov 2004 11:43:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXiyo-0004Ti-PB; Fri, 26 Nov 2004 11:29:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXixQ-0003eN-LR for manet@megatron.ietf.org; Fri, 26 Nov 2004 11:28:28 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25420 for ; Fri, 26 Nov 2004 11:28:26 -0500 (EST) Received: from web53109.mail.yahoo.com ([206.190.39.212]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CXj1i-0005e0-TX for manet@ietf.org; Fri, 26 Nov 2004 11:32:56 -0500 Received: (qmail 23434 invoked by uid 60001); 26 Nov 2004 16:27:56 -0000 Message-ID: <20041126162756.23432.qmail@web53109.mail.yahoo.com> Received: from [129.175.11.168] by web53109.mail.yahoo.com via HTTP; Fri, 26 Nov 2004 17:27:56 CET Date: Fri, 26 Nov 2004 17:27:56 +0100 (CET) From: stream stream To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id LAA25420 Subject: [manet] synchronisation in ad hoc networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: quoted-printable hi there, is there any synchronisation model or method which we can use in ad hoc networks. thanks in advance =09 ______________________________________________ Renovamos el Correo Yahoo!: =A1100 MB GRATIS! Nuevos servicios, m=E1s seguridad http://correo.yahoo.es _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 26 13:14:49 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04278 for ; Fri, 26 Nov 2004 13:14:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXkgi-00087E-Ib for manet-web-archive@ietf.org; Fri, 26 Nov 2004 13:19:20 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXkYn-0004qP-V7; Fri, 26 Nov 2004 13:11:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXkVG-00039q-0M for manet@megatron.ietf.org; Fri, 26 Nov 2004 13:07:30 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03911 for ; Fri, 26 Nov 2004 13:07:27 -0500 (EST) Received: from avas1.olemiss.edu ([130.74.126.32]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXkZa-0007yI-CD for manet@ietf.org; Fri, 26 Nov 2004 13:11:58 -0500 Received: from olemiss.edu (webmail.olemiss.edu [130.74.120.12] (may be forged)) by avas1.olemiss.edu (8.12.11/8.12.11) with ESMTP id iAQI6tta017754 for ; Fri, 26 Nov 2004 12:06:55 -0600 (envelope-from srgopal@olemiss.edu) From: "srgopal" To: manet@ietf.org X-Mailer: Quality Web Email v3.1e, http://netwinsite.com/refw.htm Date: Fri, 26 Nov 2004 12:06:55 -0600 Message-id: <41a770bf.2b3.4d2d.971759122@olemiss.edu> X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2004.11.25.56 X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Subject: [manet] Query regarding generation of packet voice in ad hoc network! X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: srgopal@olemiss.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Dear all, I am relatively new to ns and so i have problems in figuring some issues out, kindly help. I have the following questions regarding the simulation of ad hoc networks using ns-2, and i appreciate your help in this regard. 1. When i want to simulate voip in ad hoc network, i am using the exponential packet generator to generate packet voice in the network, but should i have this traffic generator attached to both the nodes or only to one? Since voice calls are bi-directional; should this traffic generator be attached to both the nodes involved in calling? If so, should i start this generator at the same time at both the nodes or when exactly? Please correct me. 2. And for calculating the bw(bandwidth) at the sink from each source connected to it as per the Marc Greis tutorial from his 8th lesson; i got the error saying "bytes_" is not declared in the procedure record. When i run the tutorial it was working. So to use it in other tcl scripts should i add something to any files? Please let me know this. Kindly let me know these at your earliest. Thanks in advance to all. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Nov 26 22:20:12 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24420 for ; Fri, 26 Nov 2004 22:20:12 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXtCZ-0005An-Lz for manet-web-archive@ietf.org; Fri, 26 Nov 2004 22:24:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXt0B-0002PE-Bv; Fri, 26 Nov 2004 22:11:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXsw6-0001MZ-7h for manet@megatron.ietf.org; Fri, 26 Nov 2004 22:07:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23052 for ; Fri, 26 Nov 2004 22:07:38 -0500 (EST) Received: from ms-smtp-03-lbl.southeast.rr.com ([24.25.9.102] helo=ms-smtp-03-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXt0O-0004bH-K3 for manet@ietf.org; Fri, 26 Nov 2004 22:12:13 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-03-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iAR37Ykc014452 for ; Fri, 26 Nov 2004 22:07:35 -0500 (EST) From: "Christopher P. Rigano" To: Date: Fri, 26 Nov 2004 22:07:33 -0500 Message-ID: <000501c4d42e$3d989350$0300a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.1 (/) X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff Subject: [manet] Information on MANET Transport Protocols NORM X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0779561609==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 501044f827b673024f6a4cb1d46e67d2 This is a multi-part message in MIME format. --===============0779561609== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01C4D404.54C28B50" This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C4D404.54C28B50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings NORM - Does NORM use any form of adaptive congestion control or other adaptive schemes? I am looking at adaptive behavior in MANET Transport Protocols and would appreciate any information and references. Thanks and regards, Chris ------=_NextPart_000_0006_01C4D404.54C28B50 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings

 

 

NORM – Does NORM use any form of adaptive = congestion control or other adaptive schemes? I am looking at adaptive behavior in = MANET Transport Protocols and would appreciate any information and = references.

 

Thanks and regards,

 

Chris

------=_NextPart_000_0006_01C4D404.54C28B50-- --===============0779561609== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0779561609==-- From manet-bounces@ietf.org Fri Nov 26 22:23:51 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24693 for ; Fri, 26 Nov 2004 22:23:50 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXtG6-0005Jl-6b for manet-web-archive@ietf.org; Fri, 26 Nov 2004 22:28:26 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXtA4-0004dR-Fk; Fri, 26 Nov 2004 22:22:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CXt32-0002yN-V5 for manet@megatron.ietf.org; Fri, 26 Nov 2004 22:14:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23998 for ; Fri, 26 Nov 2004 22:14:54 -0500 (EST) Received: from ms-smtp-03-lbl.southeast.rr.com ([24.25.9.102] helo=ms-smtp-03-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXt7R-0004w9-ST for manet@ietf.org; Fri, 26 Nov 2004 22:19:30 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-03-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iAR3Epkc019906 for ; Fri, 26 Nov 2004 22:14:53 -0500 (EST) From: "Christopher P. Rigano" To: Date: Fri, 26 Nov 2004 22:14:50 -0500 Message-ID: <000001c4d42f$424cd720$0300a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 0.1 (/) X-Scan-Signature: 0e9ebc0cbd700a87c0637ad0e2c91610 Subject: [manet] MANET Transport Protocols X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0500822550==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017 This is a multi-part message in MIME format. --===============0500822550== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C4D405.5976CF20" This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C4D405.5976CF20 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings, Which of these protocols are in the main-stream for use in MANETS; TCP-S, TCP-F, ATCP, ENIC, NORM? Any information is greatly appreciated! Chris ------=_NextPart_000_0001_01C4D405.5976CF20 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings,

 

Which of these protocols are in the main-stream for = use in MANETS; TCP-S, TCP-F, ATCP, ENIC, NORM?

 

Any information is greatly = appreciated!

 

Chris

------=_NextPart_000_0001_01C4D405.5976CF20-- --===============0500822550== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0500822550==-- From manet-bounces@ietf.org Sat Nov 27 11:56:12 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03066 for ; Sat, 27 Nov 2004 11:56:11 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CY5wN-0001He-00 for manet-web-archive@ietf.org; Sat, 27 Nov 2004 12:00:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CY5lz-0006GK-PS; Sat, 27 Nov 2004 11:50:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CY5lF-00060O-Dd for manet@megatron.ietf.org; Sat, 27 Nov 2004 11:49:26 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23767 for ; Sat, 27 Nov 2004 09:49:16 -0500 (EST) Received: from reserv5.univ-lille1.fr ([193.49.225.19] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CY3xU-00056l-MW for manet@ietf.org; Sat, 27 Nov 2004 09:53:57 -0500 Received: from kriek (pm3-ass-135.univ-lille1.fr [194.57.139.135]) by reserv5.univ-lille1.fr (8.13.1/jtpda-5.3.1) with ESMTP id iAREgeKK011117 ; Sat, 27 Nov 2004 15:43:12 +0100 From: "David Simplot-Ryl" To: , , , , Date: Sat, 27 Nov 2004 15:43:28 +0100 Message-ID: <006901c4d48f$98bdbd80$8b8b39c2@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.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-USTL-MailScanner-Information: Please contact the ISP for more information X-USTL-MailScanner: Found to be clean X-MailScanner-From: david.simplot@lifl.fr X-Spam-Score: 0.0 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b Content-Transfer-Encoding: quoted-printable Subject: [manet] 2nd CFP SaNSO 2005, Fukuota, Japan, July 20-22, 2005 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f Content-Transfer-Encoding: quoted-printable Please accept our apologies in case you receive this information from multiple sources. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 2nd Call for Papers SaNSO 2005 First International Workshop on System and Networking for Smart Objects to be held in conjunction with 11th International Conference on Parallel and Distributed Systems (ICPADS-2005) Fukuoka, Japan, July 20 - 22, 2005 http://www.lifl.fr/RD2P/SANSO2005 ---------------------------------------------------------------------- Ubiquitous computing leads to the appearance of new networked devices and creates a unique challenge by the proliferation of distributed computing involving all heterogeneous computing devices. The concept of "smart object" is defined as the junction between miniaturization with the development of wireless communications. A large number of applications in daily life enriched can be imagined: from PDA networks to smart space, from wireless smartcard to smart fridges. Smart objects like smartcards, RFID tags, wireless sensors, smart dust, require suitable basic software which takes into account the specificity of smart objects: limited resources, mobile and untrusted environment. This workshop covers the area of system and networking for smart devices. In particular, it will cover operating system architecture, network and transport layers, as well as applications, power management, security. It is the goal of this workshop to provide up to date information on research and development activities in this rapidly rising research area. Areas of relevant interest we foresee (but not limited to) include: * Smart devices like smartcards, RFID tags, sensors and smart dusts * Embedded operating system dedicated to smart objects * Mobile and ad hoc networking protocols and service discovery * Design principles and techniques for smart embedded systems * Middleware services for deployment and management of smart objects * Security and safety issues of ubiquitous computing systems * Location-dependent / personalized applications * Wireless sensor networks and group management of sensor nodes=20 * Submission and Timetable * The submission deadline is January 14, 2005. Send papers as pdf file to David.Simplot@lifl.fr. Submitted papers should be formatted in a two-column IEEE Computer Society format (URL: http://computer.org/cspress/instruct.htm) and should not exceed 6 pages including figures and references. After SaNSO 2005, distinguished papers which are presented will be published in a special issue of International Journal of Parallel, Emergent and Distributed Systems (IJPEDS). Manuscript Submission: January 14, 2005 Acceptance Notification: March 7, 2005 Final Manuscript Due: April 20, 2005 * Workshop Chair * David SIMPLOT-RYL IRCICA/LIFL, Univ. Lille 1, INRIA Futurs, France David.Simplot@lifl.fr * Program Committee * * Matthias Anlauff, Kestrel Institute, USA * Michel B=E2natre, IRISA, France * Cristian Borcea, New Jersey Institute of Technology, USA * Grzegorz Czajkowski, SUN Microsystems Laboratories, USA * Bart Dhoedt, University of Gent, Belgium * Laura Marie Feeney, SICS, Kista, Sweden * Bertil Folliot, University of Paris, France * Isabelle Gu=E9rin Lassous, INSA Lyon, France * Gilles Grimaud, University of Lille, France * Liviu Iftode, Rutgers University, USA * Chandra Krintz, University of California, Santa Barbara, USA * Jean-Louis Lanet, INRIA Sophia-Antipolis, France * Jay Lepreau, University of Utah, USA * Stephan Olariu, Old Dominion University, USA * Ian Marshall, University of Kent, UK * Michael Montgomery, Axalto, USA * Gilles Muller, Ecole des Mines de Nantes, France * Pierre Paradinas, CNAM Paris, France * Isabelle Simplot-Ryl, University of Lille, France * Ivan Stojmenovic, University of Ottawa, Canada * Asuman Suenbuel, SAP Research Labs, USA * Jean-Jacques Vandewalle, Gemplus, France * Takashi Watanabe, Shizuoka University, Japan * Jie Wu, Florida Atlantic University, USA * Wanghong Yuan, NTT DoCoMo, USA _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Nov 27 14:16:22 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15309 for ; Sat, 27 Nov 2004 14:16:22 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CY883-00078z-Qg for manet-web-archive@ietf.org; Sat, 27 Nov 2004 14:21:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CY80P-0005PO-MT; Sat, 27 Nov 2004 14:13:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CY7uI-0004ya-8Z for manet@megatron.ietf.org; Sat, 27 Nov 2004 14:06:54 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14837 for ; Sat, 27 Nov 2004 14:06:50 -0500 (EST) Received: from taurus.cs.albany.edu ([169.226.2.109] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CY7yp-0006nU-V5 for manet@ietf.org; Sat, 27 Nov 2004 14:11:36 -0500 Received: from broomstick.cs.albany.edu (ravi@broomstick.cs.albany.edu [169.226.2.89]) by taurus.cs.albany.edu (8.12.8p1-20030918/8.12.8) with ESMTP id iARJ6guX019179 for ; Sat, 27 Nov 2004 14:06:42 -0500 (EST) Received: (from ravi@localhost) by broomstick.cs.albany.edu (8.12.8p1-20030918/8.12.8/Submit) id iARJ6h2D007399 for manet@ietf.org; Sat, 27 Nov 2004 14:06:43 -0500 (EST) Date: Sat, 27 Nov 2004 14:06:43 -0500 (EST) From: "S.S.Ravi" Message-Id: <200411271906.iARJ6h2D007399@broomstick.cs.albany.edu> To: manet@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Subject: [manet] Call for papers -- WiMob 2005 X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 PLEASE ACCEPT OUR APOLOGIES IF YOU RECEIVE MULTIPLE COPIES Second Call for Papers -- WiMob'2005 International Conference on Wireless and Mobile Computing, Networking and Communications Conference dates: August 22-24, 2005 Location: Hotel Delta Centre-Ville Montreal, Canada Website: http://congresbcu.com/wimob2005/ Important Dates: Submissions due: December 21, 2004 Notification of acceptance: February 21, 2005 Tutorial and special session proposals due: March 21, 2005 Final manuscripts due: April 21, 2005 Registration and full payment due: April 30, 2005 Topics of Interest: WiMob'2005 addresses three main areas: Wireless Communications, Mobile Networking, Ubiquitous Computing and Applications. This conference aims to stimulate interactions between participants through them by exchanging new ideas and practical experience in these areas. The conference offers opportunities for in-depth exploration of the most recent research and results in these fields. The conference will be comprised of the following three symposia: Symposium 1: Wireless Communications Symposium 2: Mobile Networking Symposium 3: Ubiquitous Computing, Services and Applications Please see the conference website for the list of topics for each of the above symposia as well as for information regarding Tutorials, Special Sessions and Industrial Exhibits. Proceedings: To be published by Springer-Verlag, as part of the Lecture Notes in Computer Science (LNCS) series. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Nov 27 14:46:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17344 for ; Sat, 27 Nov 2004 14:46:08 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CY8as-0008Dh-N1 for manet-web-archive@ietf.org; Sat, 27 Nov 2004 14:50:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CY8V8-0000U6-O2; Sat, 27 Nov 2004 14:44:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CY8Sq-0000Cm-7z for manet@megatron.ietf.org; Sat, 27 Nov 2004 14:42:36 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17208 for ; Sat, 27 Nov 2004 14:42:32 -0500 (EST) Received: from sunlight.wichita.edu ([156.26.1.5]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CY8XO-00083f-2q for manet@ietf.org; Sat, 27 Nov 2004 14:47:18 -0500 Received: from CONVERSION-DAEMON.sunlight.wichita.edu by sunlight.wichita.edu (PMDF V6.2-X27 #30772) id <0I7U00101S24UJ@sunlight.wichita.edu> for manet@ietf.org; Sat, 27 Nov 2004 13:42:04 -0600 (CST) Received: from webmail.wichita.edu (BIERSTADT.WICHITA.EDU [156.26.1.165]) by sunlight.wichita.edu (PMDF V6.2-X27 #30772) with ESMTP id <0I7U001EVS23GW@sunlight.wichita.edu> for manet@ietf.org; Sat, 27 Nov 2004 13:42:03 -0600 (CST) Date: Sat, 27 Nov 2004 13:42:03 -0600 From: fxbaloch To: manet@ietf.org Message-id: <41A658A1@webmail.wichita.edu> MIME-version: 1.0 X-Mailer: WebMail (Hydra) SMTP v3.62 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: quoted-printable X-WebMail-UserID: fxbaloch@wichita.edu X-EXP32-SerialNo: 00003023, 00003770 X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: quoted-printable Subject: [manet] Multicasting with 802.11e X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Content-Transfer-Encoding: quoted-printable Hello manet-users, I was just wondering if anyone knows how does multicast works in 802.11e ad hoc networks. For example, if I am using MAODV at the routing layer and 802.11e on MAC layer, how will the EDCF treat these multicasting packets as compared to non multicast packets. In an article I read, it says that in 802.11e networks, multicast packets are dealt by the Access Point (AP), but if we do not have an AP like in ad hoc networks how will these packets be transmitted across the network. My second question is, in my simulations I am using tkn's 802.11e implementation (in ns2) by Professor Sven Wieth=F6lter. Does it support multicasting routing protocols? Please send me any input or articles/papers that could be useful to me. Thanks Fariha Baloch Fariha Baloch GRA Electrical and Computer Dept., Wichita State University. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sun Nov 28 23:50:07 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24219 for ; Sun, 28 Nov 2004 23:50:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYdZ7-0006lF-Pf for manet-web-archive@ietf.org; Sun, 28 Nov 2004 23:55:10 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYdS6-0002xf-IW; Sun, 28 Nov 2004 23:47:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYdO7-0001w4-7t for manet@megatron.ietf.org; Sun, 28 Nov 2004 23:43:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23232 for ; Sun, 28 Nov 2004 23:43:44 -0500 (EST) Received: from ms-smtp-02-lbl.southeast.rr.com ([24.25.9.101] helo=ms-smtp-02-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYdSw-0006Y5-Ht for manet@ietf.org; Sun, 28 Nov 2004 23:48:47 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-02-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iAT4ha4R012510 for ; Sun, 28 Nov 2004 23:43:37 -0500 (EST) From: "Christopher P. Rigano" To: Date: Sun, 28 Nov 2004 23:43:35 -0500 Message-ID: <000001c4d5cd$fcbfb290$0300a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 1.2 (+) X-Scan-Signature: 0770535483960d190d4a0d020e7060bd Subject: [manet] Are 802.11e, 802.16a and 802.20 used in MANETS X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2125444696==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f This is a multi-part message in MIME format. --===============2125444696== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C4D5A4.13EB3130" This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C4D5A4.13EB3130 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Greetings, are these MACs used in MANETS? Many thanks, Chris ------=_NextPart_000_0001_01C4D5A4.13EB3130 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Greetings, are these MACs used in MANETS? =

 

Many thanks,

 

Chris

------=_NextPart_000_0001_01C4D5A4.13EB3130-- --===============2125444696== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2125444696==-- From manet-bounces@ietf.org Mon Nov 29 10:00:01 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27126 for ; Mon, 29 Nov 2004 10:00:01 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYn5P-0003PJ-Mo for manet-web-archive@ietf.org; Mon, 29 Nov 2004 10:05:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYmrz-00055V-3k; Mon, 29 Nov 2004 09:51:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYmfN-0002NN-7E for manet@megatron.ietf.org; Mon, 29 Nov 2004 09:38:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA25222 for ; Mon, 29 Nov 2004 09:38:11 -0500 (EST) Received: from rproxy.gmail.com ([64.233.170.205]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYmkH-0002or-9B for manet@ietf.org; Mon, 29 Nov 2004 09:43:18 -0500 Received: by rproxy.gmail.com with SMTP id b11so383406rne for ; Mon, 29 Nov 2004 06:38:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=JQGgd+u+1j7G0wb2mpARrne2QGEhkYJ8RWdhW0CkYEB/3NtMQCcwXaPcLaJdq9jSJwoMSXVr0bL0j0FOAEM4GG0NpYvI4WpXE4GkOj12lRSZA32BCAniSLsAT9YrKoqjdhZygflHfWRDHi8rfv51u7wC1yX0SFo/12t6eMSz6kQ= Received: by 10.38.181.80 with SMTP id d80mr1583973rnf; Mon, 29 Nov 2004 06:38:06 -0800 (PST) Received: by 10.38.125.74 with HTTP; Mon, 29 Nov 2004 06:38:06 -0800 (PST) Message-ID: <89f024904112906387c34f9f6@mail.gmail.com> Date: Mon, 29 Nov 2004 19:38:06 +0500 From: Usman Gardezi To: manet@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Subject: [manet] Paper needed! X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Usman Gardezi List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit hi I need the paper "Comparison of broadcasting techniques for mobile ad hoc networks" by Brad Williams, Tracy Camp any1 having d copy plz mail it Regards -- ~ Gardezi _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Nov 29 22:33:20 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14730 for ; Mon, 29 Nov 2004 22:33:20 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYyqY-0007aj-2x for manet-web-archive@ietf.org; Mon, 29 Nov 2004 22:38:34 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYyjJ-0002B7-Bz; Mon, 29 Nov 2004 22:31:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CYyi9-0001xa-JX for manet@megatron.ietf.org; Mon, 29 Nov 2004 22:29:53 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14606 for ; Mon, 29 Nov 2004 22:29:51 -0500 (EST) Received: from havana.ucdavis.edu ([169.237.104.156]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CYynA-0007Xo-Sa for manet@ietf.org; Mon, 29 Nov 2004 22:35:05 -0500 Received: from celerio.ucdavis.edu (celerio.ucdavis.edu [169.237.104.178]) by havana.ucdavis.edu (8.12.10/8.12.9/it-defang-5.2.0) with ESMTP id iAU3TmGV013245 for ; Mon, 29 Nov 2004 19:29:49 -0800 (PST) Received: from celerio.ucdavis.edu (localhost [127.0.0.1]) by celerio.ucdavis.edu (8.12.10/8.12.9/UCD5.2.0) with ESMTP id iAU3Tmom002029 for ; Mon, 29 Nov 2004 19:29:48 -0800 (PST) Received: (from www@localhost) by celerio.ucdavis.edu (8.12.10/8.12.9/Submit) id iAU3Tmiq002028; Mon, 29 Nov 2004 19:29:48 -0800 (PST) Date: Mon, 29 Nov 2004 19:29:48 -0800 (PST) Message-Id: <200411300329.iAU3Tmiq002028@celerio.ucdavis.edu> To: manet@ietf.org From: "Fan Zhao" X-Errors-To: fanzhao@blue.ucdavis.edu X-Mailer: Geckomail-b16 X-Originating-IP: [128.120.178.196] X-User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) X-Scanned-By: MIMEDefang 2.41 X-Spam-Score: 0.0 (/) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 Subject: [manet] Call for Papers: IEEE JSAC MRNM X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8 PLEASE ACCEPT OUR APOLOGIES IF YOU RECEIVE MULTIPLE COPIES CALL FOR PAPERS IEEE Journal on Selected Areas in Communications MOBILE ROUTERS AND NETWORK MOBILITY http://www.argreenhouse.com/society/J-SAC/Calls/mobile_routers.html Network mobility support is concerned with managing the mobility of an entire network that is changing its point of attachment to the Internet and thus its reachability in the Internet topology. If network mobility is not explicitly supported by some mechanisms, existing sessions break and connectivity to the global Internet is lost. A mobile network is composed of Mobile Router(s) (MR) and Mobile Network Nodes (MNN) that can be fixed or mobile. There has been rapid development in network mobility support, i.e., providing Internet connectivity to the networks that move using mobile routers since the inception of Mobile IPv4 in 1996. Seamless Internet access in public transportation such as in trains and busses can be possible if mobile routers are used. Cars with low-power sensors seamlessly connected to the Internet constitute yet another example of networks which move. To date, some airline companies announced Internet connectivity support during commercial flights and this trend is expected to accelerate and cover most if not all flights. This issue is focused on modeling, analysis, and simulation of network mobility support protocols. We solicit papers presenting original and unpublished work including, but not limited to the following topics: * Modeling and Analysis of Network Mobility o Modeling, analysis and simulation of mobile router o Protocols for route optimization o Mobility issues inside a mobile network o Mobile IPv6 extensions for route optimization o Nested mobile networks o Multihomed mobile networks o Operational issues to deploy mobile networks o Auto-configuration for mobile networks o Mobile router support on cellular phone platforms * Services in the Networks that Move o Service advertisement and discovery protocols in networks that move o Specifications nad models of services for network mobility o Encryption and authentication in service access for network mobility * Security Issues in Network Mobility o Security analysis of present network mobility support protocols o Applications of AAA and EAP to network mobility o Interaction with security-enhanced modules in other layers (vertically) or other middle boxes (horizontally) Prospective authors should follow the IEEE J-SAC manuscript format described in the Information for Authors. Authors MUST submit their draft manuscripts through the EDAS peer review website, together with a short abstract (approximately 150 words) in the EDAS website form. Please note potential authors should create their own accounts through the EDAS peer review website before submitting manuscript(s). EDAS will accept manuscripts in PDF format only. There will be one round of reviewers and acceptance will be limited to those papers requiring only moderate revisions. The following timetable applies: Manuscript Submission: JUNE 1, 2005 Acceptance Notification: December 1, 2005 Final Manuscript Due: March 1, 2006 Publication: 3rd Quarter 2006 Guest Editorial Board: Behcet Sarikaya Computer Science Dept Univ of Northern British Columbia Prince George, BC Canada V2N 4Z9 sarikaya@unbc.ca S. Felix Wu Dept of Computer Science Univ of California at Davis Davis, CA 95616 USA wu@cs.ucdavis.edu Gopal Dommety Cisco Systems, Inc 170 West Tasman Dr San Jose, CA 95134-1706 USA gdommety@cisco.com Claude Castelluccia INRIA Rhône-Alpes ZIRST 655 Ave de l'Europe Montbonnot 38334 Saint Ismier cedex France claude.castelluccia@inria.fr Thierry Ernst Jun Murai Lab Keio Univ K-square Town Campus 1488-8 Ogura, Saiwai-ku, Kawasaki, Kanagawa 212-0054 Japan ernst@sfc.wide.ad.jp Charles E. Perkins Communication Systems Lab Nokia Research Center 313 Fairchild Dr Mountain View, CA 94943 USA charliep@iprg.nokia.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 30 00:33:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23840 for ; Tue, 30 Nov 2004 00:33:18 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ0ig-0001iC-Hs for manet-web-archive@ietf.org; Tue, 30 Nov 2004 00:38:34 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ0bJ-0000Hx-9y; Tue, 30 Nov 2004 00:30:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ0b3-00005r-IU for manet@megatron.ietf.org; Tue, 30 Nov 2004 00:30:41 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23543 for ; Tue, 30 Nov 2004 00:30:38 -0500 (EST) Received: from avas2.olemiss.edu ([130.74.126.33]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ0g6-0001dV-H7 for manet@ietf.org; Tue, 30 Nov 2004 00:35:54 -0500 Received: from olemiss.edu (webmail.olemiss.edu [130.74.120.12] (may be forged)) by avas2.olemiss.edu (8.12.11/8.12.11) with ESMTP id iAU5U9HO014588 for ; Mon, 29 Nov 2004 23:30:09 -0600 (envelope-from srgopal@olemiss.edu) From: "srgopal" To: manet@ietf.org X-Mailer: Quality Web Email v3.1e, http://netwinsite.com/refw.htm Date: Mon, 29 Nov 2004 23:30:09 -0600 Message-id: <41ac0561.6a.1e46.851813317@olemiss.edu> X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2004.11.29.33 X-Spam-Score: 0.0 (/) X-Scan-Signature: 789c141a303c09204b537a4078e2a63f Subject: [manet] Problem with wireless simulation of adhoc network in ns-2.27, Urgent Help needed! X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: srgopal@olemiss.edu List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d16ce744298aacf98517bc7c108bd198 Dear all, I was trying to simulate an ad hoc network carrying voice calls in ns-2.27 to analyze the call carrying capacity of the network. I did the tutorials given by Mr. Marc Greis. Then i have written a tcl script for simulating 50 node network and have invoked 12 voice calls between different source-destination pairs. When i run the tutorials i can see the "exp" exponential packets being exchanged between the nodes, but for my code i do not see any "exp" packets being exchanged between the nodes except the "message" type of packets which i think are control packets. I am hereby attaching my tcl script for your kind reference. Please have a look at it and tell me where is the mistake, if any. I really appreciate any help in this regard and also this is very urgent fro me as i have to submit a project report on it. Kindly do the needful at the earliest. Thanks in advance. set val(chan) Channel/WirelessChannel ;# channel type set val(prop) Propagation/TwoRayGround ;# radio-propagation model set val(netif) Phy/WirelessPhy ;# network interface type set val(mac) Mac/802_11 ;# MAC type set val(ifq) Queue/DropTail/PriQueue ;# interface queue type #set val(ifq) CMUPriQueue ;# interface queue type set val(ll) LL ;# link layer type set val(ant) Antenna/OmniAntenna ;# antenna model set val(x) 1000 ;# X dimension of the topography set val(y) 1000 ;# Y dimension of the topography set val(ifqlen) 50 ;# max packet in ifq set val(nn) 50 ;# number of mobilenodes set val(rp) DSDV ;# routing protocol set val(seed) 0.0 set val(stop) 300.0 ;# simulation time #Create a simulator object set ns [new Simulator] #Open the output files set tracefd [open p11.tr w] $ns use-newtrace $ns trace-all $tracefd # set up topography object set topo [new Topography] $topo load_flatgrid $val(x) $val(y) create-god $val(nn) $ns node-config -adhocRouting $val(rp) \ -llType $val(ll) \ -macType $val(mac) \ -ifqType $val(ifq) \ -ifqLen $val(ifqlen) \ -antType $val(ant) \ -propType $val(prop) \ -phyType $val(netif) \ -channelType $val(chan) \ -topoInstance $topo \ -agentTrace OFF \ -routerTrace OFF \ -macTrace ON \ -movementTrace OFF Mac/802_11 set dataRate_ 2e6 for {set i 0} {$i < $val(nn) } {incr i} { set node_($i) [$ns node] $node_($i) random-motion 0 ;# disable random motion } for { set i 0} {$i < $val(nn) } {incr i} { $node_($i) set X_ [expr {rand()*$val(x)}] $node_($i) set Y_ [expr {rand()*$val(y)}] $node_($i) set Z_ 0 } puts "POSITIONS DONE!" #Source-Destination pair proc attach-expoo-traffic { node sink size burst idle rate } { #Get an instance of the simulator set ns [Simulator instance] #Create a UDP agent and attach it to the node set source [new Agent/UDP] $ns attach-agent $node $source #Create an Expoo traffic agent and set its configuration parameters set traffic [new Application/Traffic/Exponential] $traffic set packetSize_ $size $traffic set burst_time_ $burst $traffic set idle_time_ $idle $traffic set rate_ $rate #$traffic set interval_ $interval # Attach traffic source to the traffic generator $traffic attach-agent $source #Connect the source and the sink $ns connect $source $sink return $traffic } set sink30 [new Agent/Null] $ns attach-agent $node_(30) $sink30 #Create three traffic sources set source0 [attach-expoo-traffic $node_(0) $sink30 160 1.004s 1.587s 32k ] ns at 0.0 "$source0 start" ns at 40.0 "$source0 stop" #Call the finish procedure after 300 seconds simulation time for {set i 0} {$i < $val(nn) } {incr i} { $ns at 300.0 "$node_($i) reset"; } $ns at 300.0 "finish" $ns at 300.0 "puts \"NS EXITING...\" ; $ns halt" proc finish {} { #global f0 global ns tracefd $ns flush-trace close $tracefd #Close the output files #close $f0 #Call xgraph to display the results #exec xgraph tout0.tr -geometry 800x400 & exit 0 } #Run the simulation puts "Starting simulation ........" $ns run _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 30 00:45:26 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24819 for ; Tue, 30 Nov 2004 00:45:26 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZ0uP-0001x7-O1 for manet-web-archive@ietf.org; Tue, 30 Nov 2004 00:50:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ0kp-0003HO-ES; Tue, 30 Nov 2004 00:40:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZ0gS-0002E8-MD for manet@megatron.ietf.org; Tue, 30 Nov 2004 00:36:16 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA24009 for ; Tue, 30 Nov 2004 00:36:14 -0500 (EST) Received: from web50610.mail.yahoo.com ([206.190.38.249]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CZ0lU-0001kv-ST for manet@ietf.org; Tue, 30 Nov 2004 00:41:30 -0500 Received: (qmail 32062 invoked by uid 60001); 30 Nov 2004 05:35:44 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=CDrG9s1AQp3c+n96BLRP38RKUAcHdLeJVGdlTl4uAz8fxiCiQSmNhze+qAPLzr+yG/HvQl2YI3p7W3HA/d2zf8X3JG1iO1Wv/GKnft0Hfmg08Z+Kd3bGhAp4VhvK0ZyzqyGubXRCN9+tZLMROm6H/k/a94/i8j8nSVQhcgF5J3M= ; Message-ID: <20041130053544.32060.qmail@web50610.mail.yahoo.com> Received: from [130.74.176.55] by web50610.mail.yahoo.com via HTTP; Mon, 29 Nov 2004 21:35:44 PST Date: Mon, 29 Nov 2004 21:35:44 -0800 (PST) From: Raja Sombhotla To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.9 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Subject: [manet] How to measure throughput and packet loss! X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1661848944==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 --===============1661848944== Content-Type: multipart/alternative; boundary="0-668996496-1101792944=:31104" --0-668996496-1101792944=:31104 Content-Type: text/plain; charset=us-ascii Hi All, I tried to use the Agent/Lossmonitor to estimate the packet loss as per the tutorial given by Marc Greis and i had an error that "bytes_" is not declared. I do not know what to do. I simply followed the procedure given in the tutorial and it did not work. Do i have to do any changes in any of the files for it to work? Please let me know. I need it at the earliest. Thanks in advance. Regards, Raja. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --0-668996496-1101792944=:31104 Content-Type: text/html; charset=us-ascii
Hi All,
 
I tried to use the Agent/Lossmonitor to estimate the packet loss as per the tutorial given by Marc Greis and i had an error that "bytes_" is not declared. I do not know what to do. I simply followed the procedure given in the tutorial and it did not work. Do i have to do any changes in any of the files for it to work? Please let me know. I need it at the earliest. Thanks in advance.
 
Regards,
Raja.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com --0-668996496-1101792944=:31104-- --===============1661848944== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1661848944==-- From manet-bounces@ietf.org Tue Nov 30 13:03:28 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14898 for ; Tue, 30 Nov 2004 13:03:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZCQl-0002M5-4C for manet-web-archive@ietf.org; Tue, 30 Nov 2004 13:08:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZCCt-00058K-BC; Tue, 30 Nov 2004 12:54:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZC8H-0003fc-Qp for manet@megatron.ietf.org; Tue, 30 Nov 2004 12:49:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13166 for ; Tue, 30 Nov 2004 12:49:42 -0500 (EST) Received: from ms-smtp-01-lbl.southeast.rr.com ([24.25.9.100] helo=ms-smtp-01-eri0.southeast.rr.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZCDP-0001t9-Sv for manet@ietf.org; Tue, 30 Nov 2004 12:55:05 -0500 Received: from CPQ73745201364 (rdu168-179-206.nc.rr.com [24.168.179.206]) by ms-smtp-01-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id iAUHnbKj014788 for ; Tue, 30 Nov 2004 12:49:40 -0500 (EST) From: "Christopher P. Rigano" To: Date: Tue, 30 Nov 2004 12:49:37 -0500 Message-ID: <000a01c4d704$f5823a10$0300a8c0@CPQ73745201364> MIME-Version: 1.0 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.2900.2180 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Spam-Score: 1.2 (+) X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407 Subject: [manet] 802.11e X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0754637236==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.2 (/) X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44 This is a multi-part message in MIME format. --===============0754637236== Content-Type: multipart/alternative; boundary="----=_NextPart_000_000B_01C4D6DB.0CAC3210" This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C4D6DB.0CAC3210 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Is anyone planning to use 802.11e in MANETs. How would it be used? Best regards, Chris ------=_NextPart_000_000B_01C4D6DB.0CAC3210 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Is anyone planning to use 802.11e in MANETs. How = would it be used?

 

Best regards,

 

Chris

------=_NextPart_000_000B_01C4D6DB.0CAC3210-- --===============0754637236== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0754637236==-- From manet-bounces@ietf.org Tue Nov 30 15:01:08 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27711 for ; Tue, 30 Nov 2004 15:01:08 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZEGc-0005sH-8V for manet-web-archive@ietf.org; Tue, 30 Nov 2004 15:06:31 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZE2z-0000RX-Be; Tue, 30 Nov 2004 14:52:25 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZDms-0003L0-BR for manet@megatron.ietf.org; Tue, 30 Nov 2004 14:35:46 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24629 for ; Tue, 30 Nov 2004 14:35:44 -0500 (EST) Received: from maru.ajou.ac.kr ([202.30.0.18] helo=mail.ajou.ac.kr) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CZDry-000529-C9 for manet@ietf.org; Tue, 30 Nov 2004 14:41:07 -0500 Received: from seodang.ajou.ac.kr ([202.30.0.9]) by maru (Crinity Message Backbone-2.6.23.1) with SMTP ID 968 for ; Wed, 1 Dec 2004 04:34:52 +0900 (KST) Message-ID: <006701c4d713$b2cf5860$bbcb6bd2@ajoudayhakyu> From: Faisal Adeem Siddiqui To: manet@ietf.org Date: Wed, 1 Dec 2004 04:35:06 +0900 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 2.2 (++) X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e Subject: [manet] Difference between Mobile Ad hoc Networks and Spontaneous Networks X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1734645237==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 1.9 (+) X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c This is a multi-part message in MIME format. --===============1734645237== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0064_01C4D75F.21B2FDE0" This is a multi-part message in MIME format. ------=_NextPart_000_0064_01C4D75F.21B2FDE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello manet users, I am sending this message for the second time as I didn't receive ANY = reply the first time I sent it. Hope I'll get your valuable comments and = answers this time. Any information will be highly appreciated. Thanks.=20 Faisal. ----- Original Message -----=20 From: Faisal Adeem Siddiqui=20 To: manet@ietf.org=20 Sent: Friday, November 26, 2004 9:51 AM Subject: Difference between Mobile Ad hoc Networks and Spontaneous = Networks Hi everyone, I want to know what is the key difference between Mobile Ad hoc Networks = and Spontaneous Networks ? To me a Spontaneous Network is the = application level view of a mobile ad hoc network. Other distinction = could be that the mobile ad hoc networks are mostly homogenous with = nodes of similar capabilities and running the same routing protocol = while spontaneous networks can have variety of nodes with varying = capabilities. (correct me if I am wrong) When I search on the Google for Spontaneous Networks, I get many = documents of mobile ad hoc networks and some documents use these terms = interchangeably. I want to know what different technologies are = involved in Spontaneous Networks ? Are there any specialized mechanisms, = routing protocols, service discovery protocols etc. involved in = Spontaneous Networks ? Eagerly waiting for your answers. Thanks. Faisal Adeem Siddiqui ------=_NextPart_000_0064_01C4D75F.21B2FDE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello manet = users,
I am sending this message for = the second=20 time as I didn't receive ANY reply the first time I sent it. Hope = I'll get=20 your valuable comments and answers this time. Any information will be = highly=20 appreciated.
Thanks. 
Faisal.
----- Original Message -----=20
From: Faisal Adeem = Siddiqui
Sent: Friday, November 26, 2004 9:51 AM
Subject: Difference between Mobile Ad hoc Networks and = Spontaneous=20 Networks

Hi everyone,
I want to know what is the = key difference=20 between Mobile Ad hoc Networks and Spontaneous Networks ? To me a = Spontaneous=20 Network is the application level view of a mobile ad hoc network. Other=20 distinction could be that the mobile ad hoc networks are mostly = homogenous=20 with nodes of similar capabilities and running the same routing protocol = while=20 spontaneous networks can have variety of nodes with varying=20 capabilities. (correct me if I am wrong)
When I search on the = Google for=20 Spontaneous Networks, I get many documents of mobile ad hoc = networks=20 and some documents use these terms interchangeably.  I want to = know=20 what different technologies are involved in Spontaneous Networks ? Are = there any=20 specialized mechanisms, routing protocols, service = discovery protocols etc.=20 involved in Spontaneous Networks ?
 
Eagerly waiting for your=20 answers.
Thanks.
Faisal Adeem Siddiqui
 
------=_NextPart_000_0064_01C4D75F.21B2FDE0-- --===============1734645237== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1734645237==-- From manet-bounces@ietf.org Tue Nov 30 17:26:53 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22919 for ; Tue, 30 Nov 2004 17:26:53 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZGXi-00057Y-D4 for manet-web-archive@ietf.org; Tue, 30 Nov 2004 17:32:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZGAa-0005TR-Ni; Tue, 30 Nov 2004 17:08:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZErf-0001TT-0I for manet@megatron.ietf.org; Tue, 30 Nov 2004 15:44:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02659 for ; Tue, 30 Nov 2004 15:44:42 -0500 (EST) Received: from taurus.cs.albany.edu ([169.226.2.109] ident=root) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZEwo-0006zg-4W for manet@ietf.org; Tue, 30 Nov 2004 15:50:06 -0500 Received: from broomstick.cs.albany.edu (ravi@broomstick.cs.albany.edu [169.226.2.89]) by taurus.cs.albany.edu (8.12.8p1-20030918/8.12.8) with ESMTP id iAUKiMuX027481; Tue, 30 Nov 2004 15:44:22 -0500 (EST) Received: (from ravi@localhost) by broomstick.cs.albany.edu (8.12.8p1-20030918/8.12.8/Submit) id iAUKiK6D002984; Tue, 30 Nov 2004 15:44:20 -0500 (EST) Date: Tue, 30 Nov 2004 15:44:20 -0500 (EST) From: "S.S.Ravi" Message-Id: <200411302044.iAUKiK6D002984@broomstick.cs.albany.edu> To: Cabernet-events@jiscmail.ac.uk, manet@ietf.org, performance@msr.csm.ornl.gov, podc@acm.org, tccc@cs.columbia.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Subject: [manet] Correction -- WiMob 2005 call for papers X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 PLEASE ACCEPT OUR APOLOGIES IF YOU RECEIVE MULTIPLE COPIES CORRECTION to Call for Papers -- WiMob'2005 International Conference on Wireless and Mobile Computing, Networking and Communications Conference dates: August 22-24, 2005 Location: Hotel Delta Centre-Ville Montreal, Canada Website: http://congresbcu.com/wimob2005/ The call for papers for WiMob 2005 posted to this group indicated that the proceedings of the conference will be published as Springer-Verlag Lecture Notes in Computer Science. This is incorrect. Instead, the proceedings will be published by IEEE and will be accessible through IEEE eXplore. Please accept our apologies for the error. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 30 18:25:43 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29870 for ; Tue, 30 Nov 2004 18:25:42 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZHSe-0006uP-R1 for manet-web-archive@ietf.org; Tue, 30 Nov 2004 18:31:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZHIr-00075n-JY; Tue, 30 Nov 2004 18:21:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZHH8-00067P-LV for manet@megatron.ietf.org; Tue, 30 Nov 2004 18:19:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29217 for ; Tue, 30 Nov 2004 18:19:11 -0500 (EST) Received: from sunlight.wichita.edu ([156.26.1.5]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZHML-0006mn-8T for manet@ietf.org; Tue, 30 Nov 2004 18:24:37 -0500 Received: from CONVERSION-DAEMON.sunlight.wichita.edu by sunlight.wichita.edu (PMDF V6.2-X27 #30772) id <0I8000701M35OI@sunlight.wichita.edu> for manet@ietf.org; Tue, 30 Nov 2004 17:18:41 -0600 (CST) Received: from webmail.wichita.edu (BIERSTADT.WICHITA.EDU [156.26.1.165]) by sunlight.wichita.edu (PMDF V6.2-X27 #30772) with ESMTP id <0I800073HM35LZ@sunlight.wichita.edu> for manet@ietf.org; Tue, 30 Nov 2004 17:18:41 -0600 (CST) Date: Tue, 30 Nov 2004 17:18:41 -0600 From: fxbaloch To: manet@ietf.org Message-id: <41AD3883@webmail.wichita.edu> MIME-version: 1.0 X-Mailer: WebMail (Hydra) SMTP v3.62 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-WebMail-UserID: fxbaloch@wichita.edu X-EXP32-SerialNo: 00003023, 00003770 X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: 7bit Subject: [manet] new ns2 documents? X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7bit Hello all, I think a few weeks back I saw some link on this list or on the ns2's list for a new documentation of ns2. I remember it was very precise documentation and had very nice explanation of all sort of things. Did anyone of you also saw that email? I was wondering if you did, could you pass the address of the document or the document itself to me, please. Thanks Fariha Fariha Baloch GRA Electrical and Computer Dept., Wichita State University. _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Nov 30 22:43:50 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21203 for ; Tue, 30 Nov 2004 22:43:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZLUT-00048i-Lc for manet-web-archive@ietf.org; Tue, 30 Nov 2004 22:49:17 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZLMq-0004Sv-Rm; Tue, 30 Nov 2004 22:41:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZLLe-00045l-1d for manet@megatron.ietf.org; Tue, 30 Nov 2004 22:40:10 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20941 for ; Tue, 30 Nov 2004 22:40:06 -0500 (EST) Received: from web8402.mail.in.yahoo.com ([202.43.219.150]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CZLQr-00044j-4y for manet@ietf.org; Tue, 30 Nov 2004 22:45:34 -0500 Received: (qmail 72798 invoked by uid 60001); 1 Dec 2004 03:39:30 -0000 Message-ID: <20041201033929.72795.qmail@web8402.mail.in.yahoo.com> Received: from [210.212.228.8] by web8402.mail.in.yahoo.com via HTTP; Wed, 01 Dec 2004 03:39:29 GMT Date: Wed, 1 Dec 2004 03:39:29 +0000 (GMT) From: M koteswara rao To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 3.5 (+++) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Subject: [manet] request on multicast routing X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mkoteswararao@gmail.com List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1756491440==" Sender: manet-bounces@ietf.org Errors-To: manet-bounces@ietf.org X-Spam-Score: 3.0 (+++) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 --===============1756491440== Content-Type: multipart/alternative; boundary="0-1338015729-1101872369=:72668" --0-1338015729-1101872369=:72668 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hai friends, Iam m koteswara rao, doing project on multicast routing. I have referred ns2 material, in that i have findout some programs related to my project.But in that they are some cc files, i tried to run those files..iam gettinf many errors.... I do not know what to do. Do i have to do any changes in any of the files for it to work? Please let me know. I need it at the earliest..waiting for ur reply.. with regards, M.Koteswara Rao. Yahoo! India Matrimony: Find your life partneronline. --0-1338015729-1101872369=:72668 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Hai friends,
Iam m koteswara rao, doing project on multicast routing. I have referred ns2 material, in that i have findout some programs related to my project.But in that they are some cc files, i tried to run those files..iam gettinf many errors.... I do not know what to do. Do i have to do any changes in any of the files for it to work? Please let me know. I need it at the earliest..waiting for ur reply..
 
with regards,
M.Koteswara Rao.

Yahoo! India Matrimony: Find your life partner online. --0-1338015729-1101872369=:72668-- --===============1756491440== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1756491440==--