From manet-bounces@ietf.org Sat Jul 01 00:47:32 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FwXO4-0004q9-Jv; Sat, 01 Jul 2006 00:47:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FwXO3-0004q4-6c for manet@ietf.org; Sat, 01 Jul 2006 00:47:19 -0400 Received: from ug-out-1314.google.com ([66.249.92.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FwXO1-0005Kz-U3 for manet@ietf.org; Sat, 01 Jul 2006 00:47:19 -0400 Received: by ug-out-1314.google.com with SMTP id m2so504882ugc for ; Fri, 30 Jun 2006 21:47:16 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=UZaq42EPZT4DvYZSzoCB4nUwOog5vmYi8lFRsSZAApG1yVO7dTj1Rpd+vE+MfkIVG5ssjFbh1FAnsSrIsa+e6XnIdLnLP+Ca4REVABVKnyMV84f7gCMbzp4sN7yhj4GEVWn+HXm6Rc4UyVVQZ0f/9pNTfrMA1D3eL28NDeum3qQ= Received: by 10.78.157.15 with SMTP id f15mr346729hue; Fri, 30 Jun 2006 21:47:16 -0700 (PDT) Received: by 10.78.56.9 with HTTP; Fri, 30 Jun 2006 21:47:16 -0700 (PDT) Message-ID: <146563590606302147j796c6e85lea9927553881443@mail.gmail.com> Date: Sat, 1 Jul 2006 12:47:16 +0800 From: "chen jiming" To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.3 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Subject: [manet] help 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="===============0105966903==" Errors-To: manet-bounces@ietf.org --===============0105966903== Content-Type: multipart/alternative; boundary="----=_Part_21758_3939855.1151729236761" ------=_Part_21758_3939855.1151729236761 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Dear all: because I didnot present at IEEE ICC 2006 anyboday who got the CD of proceeding can help me? I would like to get PDF file of my paper entitled"Grid Scan: A Simple and Effective Approach for Coverage Issue in Wireless Sensor Networks " and the author is Xingfa Shen, Jiming Chen, Youxian Sun, Zhejiang University, China many thanks Jiming Chen ------=_Part_21758_3939855.1151729236761 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Dear all:
 
 
because I didnot present at IEEE ICC 2006
anyboday who got the CD of proceeding can help me?
 
I would like to get PDF file of my paper  entitled"Grid Scan: A Simple and Effective Approach for Coverage Issue in Wireless Sensor Networks
" and the author is   Xingfa Shen, Jiming Chen, Youxian Sun, Zhejiang University, China
 
many thanks

 

 

Jiming Chen
------=_Part_21758_3939855.1151729236761-- --===============0105966903== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0105966903==-- From manet-bounces@ietf.org Sun Jul 02 08:31:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fx16h-0008V9-FN; Sun, 02 Jul 2006 08:31:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fx16f-0008V4-RF for manet@ietf.org; Sun, 02 Jul 2006 08:31:21 -0400 Received: from nz-out-0102.google.com ([64.233.162.195]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fx16e-0008QX-3H for manet@ietf.org; Sun, 02 Jul 2006 08:31:21 -0400 Received: by nz-out-0102.google.com with SMTP id v1so678184nzb for ; Sun, 02 Jul 2006 05:31:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:reply-to:from:to:cc:subject:date:organization:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole:sender; b=L+ZUcI4AfW/ZXCl3OjuHARPjFLkSODPFQgUGXHi4HbtI9mxM5dmSqhf0oZDx3MXZUE9+uo/WEGzz0fkKh5RXbExcFSfCN5uVdmY9qN2Fckv4FwVPRGLhMpiruleu/KeQROmEX5Wk9wa/GtI+q3Q/R/npCZp2smMsUZ2v1zbifv4= Received: by 10.36.22.10 with SMTP id 10mr2622244nzv; Sun, 02 Jul 2006 05:31:19 -0700 (PDT) Received: from IBMD2594A07A1F ( [211.167.39.49]) by mx.gmail.com with ESMTP id j4sm2098906nzd.2006.07.02.05.31.16; Sun, 02 Jul 2006 05:31:19 -0700 (PDT) Message-ID: <006b01c69dd3$6a2be640$0300a8c0@IBMD2594A07A1F> From: "Yan \(Josh\) ZHANG" To: , , , Date: Sun, 2 Jul 2006 20:27:36 +0800 Organization: Simula MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: meiyang , "Jun Zheng \(QC\)" Subject: [manet] [CFP] Special Session "Wireless Mesh Networks" in PDCS 2006 (Deadline extended to 10, July) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Yan \(Josh\) ZHANG" List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: manet-bounces@ietf.org We apologize in advance if you receive multiple copies of this CFP ================================================================= Special Session "Wireless Mesh Networks" in the 18th IASTED International Conference on PARALLEL AND DISTRIBUTED COMPUTING AND SYSTEMS ~ PDCS 2006 ~ November 13-15, 2006; Dallas, Texas, USA http://www.iasted.org/conferences/2006/Dallas/pdcs-specsess1.htm Scope ===== Wireless Mesh Networks (WMN) is emerging as a new technology extending and converging the future generation wireless networks. Standard organizations are actively calling for specifications for mesh networking, e.g. IEEE 802.11, IEEE 802.15, IEEE 802.16 and IEEE 802.20. WMN is characterized by dynamic self-organization, self-configuration and self-healing to enable flexible integration, secure communications, easy maintenance, high scalability and reliable services. To achieve these goals, great efforts are ongoing in both academy and industry communities. A special session on Wireless Mesh Networks will be organized at the PDCS2006 conference. This session constitutes a unique forum to present the latest research results by international researchers and developers. Original contributions are solicited, related to all areas in wireless mesh networking. Topics of interest include, but are not limited to: ==================================================== Mesh networking for Ad hoc network, Wireless PAN, LAN, MAN and WAN Mesh networking architecture in heterogeneous networks Multi-radio and multi-channel Wireless Mesh Networking QoS provisioning Multimedia services MAC protocol design Routing protocols Scheduling Load balancing Topology control Channel assignment algorithms Cross-layer optimization Physical layer techniques Security, authentication and privacy Fault tolerance, anomaly detection and error recovery schemes Standardization in emerging standards: IEEE 802.11, 802.15, 802.16 mesh, 802.20 mesh Testbed, prototype, practical system for WMN Submission Guidelines and Publications ======================================= Each should include authors names, affiliations, addresses, email addresses of all authors, and corresponding author and contact on the cover page. Each paper should include up to 5 keywords and an abstract of no more than 250 words. Please submit full paper, not exceeding 6 pages in length (single-space) in PS or PDF format for consideration, to the special session organizer by June 15, 2006 via email. Submission implies the willingness of at least one author to register and present the paper. All papers selected for this session by peer-review process will be published in the PDCS2006 conference proceedings through ACTA Press, USA. All final papers should be received by Sept. 1, 2006 and should adhere to the IASTED final paper formatting requirements outlined at http://www.iasted.org/formatting-final.htm. IMPORTANT DEADLINES =================== Paper received: July 10, 2006 Notification of acceptance: August 1, 2006 Final manuscript due: September 1, 2006 Registration Deadline: September 15, 2006 Special session organizers ========================== Dr. Yan ZHANG National Institute of Information and Communications Technology Email: yanzhang ieee.org Dr. Jun ZHENG Dept. of Computer Science Queens College New York, NY, USA Email: zheng cs.qc.edu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 05 04:56:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy3Az-0004lB-WE; Wed, 05 Jul 2006 04:56:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy3Ay-0004kw-D7 for manet@ietf.org; Wed, 05 Jul 2006 04:56:04 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy3Ay-0005Oa-Bg for manet@ietf.org; Wed, 05 Jul 2006 04:56:04 -0400 Received: from ppsw-0.csi.cam.ac.uk ([131.111.8.130]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fy38o-00050V-Me for manet@ietf.org; Wed, 05 Jul 2006 04:53:53 -0400 X-Cam-SpamDetails: Not scanned X-Cam-AntiVirus: No virus found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from c056.vpn.cl.cam.ac.uk ([128.232.105.56]:1341 helo=OAHU) by ppsw-0.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.150]:25) with esmtp id 1Fy38c-000467-02 (Exim 4.54) for manet@ietf.org (return-path ); Wed, 05 Jul 2006 09:53:38 +0100 From: "Eiko Yoneki" To: Date: Wed, 5 Jul 2006 09:53:29 +0100 Message-ID: <004901c6a010$7f7b3660$916ee880@cl.cam.ac.uk> 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.2869 Importance: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017 Subject: [manet] [DL July 10th RDDS 2006] Workshop on Reliability in Decentralized Distributed Systems X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ey204@cl.cam.ac.uk List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: manet-bounces@ietf.org (Apologies if you receive multiple copies of this message) =20 **** Final Submission Deadline is July 10, 2006 ****=20 -------------------------------------------------------------------------= - International Workshop on Reliability in Decentralized Distributed = Systems (RDDS 2006)=20 http://www.cs.rmit.edu.au/fedconf/index.html?page=3Drdds2006cfp In conjunction with ON THE MOVE FEDERATED CONFERENCES 2006 (OTM'06-ODBASE/DOA/CoopIS/GADA) http://www.cs.rmit.edu.au/fedconf=20 Montpellier, France, Oct 29 - Nov 3, 2006 Proceedings will be published by Springer Verlag -------------------------------------------------------------------------= - WORKSHOP THEME=20 Middleware has become a popular technology for building distributed = systems from tiny sensor networks to large scale peer-to-peer (P2P) networks. Support such as asynchronous and multipoint communication is well suited = for constructing reactive distributed computing applications over wired and wireless networks environments. While middleware infrastructures exhibit attractive features from an application development perspective (e.g., portability, interoperability, adaptability etc.), they are often = lacking in robustness and reliability. Distributed systems become increasingly = large and complex, thereby compounding many reliability problems that = necessitate different strategies and solutions. For example, in the inherently distributed nature of P2P networks, the = most common solution to reliability is to take advantage of redundancy. The = same task can be initially assigned to multiple peers. In file sharing applications, data can be replicated across many peers. In messaging applications, messages can be simultaneously sent along multiple paths. Redundancy may not be appropriate, however, in resource-constrained environments such as wireless ad hoc networks where more lightweight alternatives are needed. Some systems even rely on autonomic management technologies inspired by nature and biological organisms to cope with = the challenges of scale, complexity, heterogeneity and unpredictability. In = any case, the system model (e.g., communication, failures) and application requirements are key factors in the design of reliably mechanisms. Among different aspects of reliability issues, this workshop focuses on reliability in decentralized distributed systems. While decentralized architectures are gaining adoption is most application domains, there is still some reluctance in deploying them in systems with high = dependability requirements. This has led, over the past few years, to several academic = and industrial research efforts aimed at correcting this deficiency. For the most part, these research efforts have been independent of each other, = and have often focused on specific pieces of the dependability puzzle. Our = aim, in this Workshop, is to bring researchers and practitioners together, to further our insights on reliable decentralized architectures and to investigate collectively the challenges that remain. GOAL The purpose of the RDDS 2006 workshop on Reliability in Distributed Decentralized Systems is to bring together researchers from diverse communities who are interested in building dependable reliable = distributed systems in decentralized form, to explore ways of making today's = middleware technologies more robust, and to discuss and exchange experimental or theoretical results, novel design, work-in-progress, experience, case = study, and trend-setting ideas. We seek contributions from researchers of all backgrounds, in particular peer-to-peer systems, messaging, ad hoc communication, middleware and distributed systems, and autonomic = management systems. TOPICS OF INTEREST=20 The Workshop solicits contributions on topics related to, but not = limited to, the following:=20 - Reliable communication, architectures and algorithms=20 - Lessons learned in building/using dependable middleware: what works, = what doesn't?=20 - Integrating dependable embedded and enterprise middleware systems=20 - Trade-offs in adding other "-ilities" (survivability, adaptability, scalability, availability, mobility, security, real-time, etc.) to = reliable middleware infrastructures=20 - Integration of dependability into formal distributed object models=20 - Shaping/enhancing standards for reliable middleware=20 - Evaluating dependability for middleware applications=20 - Limitations of existing fault tolerance technologies in the context = of middleware applications=20 - Metrics, benchmarks and performance studies in evaluating reliability = for middleware applications=20 - Combining different dependability strategies, e.g., replication with transactions=20 - Self-healing, self-protecting systems=20 - Autonomic system management=20 - Reliability measurement, modelling and evaluation=20 - Tools for design and evaluation of reliable systems=20 - Application-specific reliable system (e.g.embedded systems, Web, databases)=20 - Enabling technologies for self-managing systems and networks=20 - Economic, biological and social models used for autonomic = communications=20 - Timeliness and availability in support of reliability=20 - QoS for reliable systems IMPORTANT DATES Deadline for paper submission June 30th, 2006 Notification of acceptance August 10th, 2006 Deadline for camera-ready papers August 20th, 2006 SUBMISSION GUIDELINES All submitted papers will be carefully evaluated based on originality, significance, technical soundness, and clarity of expression. All submissions must be in English. Submissions should be in PDF format and = must not exceed 10 pages in the final camera-ready format for regular papers = and 4 pages for position papers.=20 Authors instructions can be found at:=20 http://www.springer.de/comp/lncs/authors.html=20 The paper submission site is located at:=20 http://www.cs.rmit.edu.au/fedconf/rdds/2006/papers=20 Accepted workshop contributions will be published by Springer-Verlag as = LNCS (Lecture Notes in Computer Science) as a part of the workshop = proceedings of the 2006 International On The Move Federated Conferences (OTM). = Registering to the OTM conference and RDDS workshop is a prerequisite for the paper = to be published.=20 CONTACT PEOPLE: Eiko Yoneki Computer Laboratory University of Cambridge=20 United Kingdom Email: eiko.yoneki@cl.cam.ac.uk Pascal Felber Dependable and Distributed Computing Group Universit=E9 de Neuch=E2tel=20 Institut d'informatique Switzerland Email: pascal.felber@unine.ch PROGRAM COMMITTEE - Licia Capra (University College London, UK)=20 - Mariano Cilia (Darmstadt University of Technology, Germany)=20 - Vittorio Cortellessa (Universita' de L'Aquila, Italy)=20 - Simon Courtenage (University of Westminster, UK)=20 - Patrick Eugster (Purdue University, USA)=20 - Ludger Fiege (Siemens Research, Germany)=20 - Maria Gradinariu (IRISA/INRIA-CNRS, France) - Eli Katsiri (Imperial College London, UK)=20 - Michael Kounavis (Intel Research, USA)=20 - Marco Mamei (Universit=E0 di Modena, Italy)=20 - Jon Munson (IBM T J Watson Research Center, USA)=20 - Maziar Nekovee (BT Research, UK)=20 - Andrea Passarella (IIT-CNR, Italy)=20 - Peter Pietzuch (Harvard University, USA)=20 - Matthieu Roy (LAAS-CNRS, France) - Fran=E7ois Ta=EFani (Lancaster University, UK)=20 - Niki Trigoni (Birkbeck University London, UK)=20 - Einar Vollset (Cornell University, USA)=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 05 07:37:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy5hL-00042X-Sq; Wed, 05 Jul 2006 07:37:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fy5hJ-000427-Kt for manet@ietf.org; Wed, 05 Jul 2006 07:37:37 -0400 Received: from p-mail2.rd.francetelecom.com ([195.101.245.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fy5hH-0003YN-Vw for manet@ietf.org; Wed, 05 Jul 2006 07:37:37 -0400 Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Wed, 5 Jul 2006 13:37:33 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Wed, 5 Jul 2006 13:37:37 +0200 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Special Issue on Analysis & Design of Cross-Layer Optimized Wireless Sensor Networks (deadline 1 October 2006) Thread-Index: AcagF95KO2QYLv4LRNGgQEiCyi46KQADmqWQAABFpQA= From: "DOHLER Mischa RD-TECH-GRE" To: X-OriginalArrivalTime: 05 Jul 2006 11:37:33.0788 (UTC) FILETIME=[682239C0:01C6A027] X-Spam-Score: 0.6 (/) X-Scan-Signature: 1e467ff145ef391eb7b594ef62b8301f Cc: Stavros Toumpis , "Prof. Lionel Ni" , Taieb Znati Subject: [manet] Special Issue on Analysis & Design of Cross-Layer Optimized Wireless Sensor Networks (deadline 1 October 2006) 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="===============2010555310==" Errors-To: manet-bounces@ietf.org This is a multi-part message in MIME format. --===============2010555310== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6A027.67E0E5DE" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6A027.67E0E5DE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear colleagues, You are kindly invited to submit high-quality contributions according to below CFP for a special issue on sensor networks. Kind regards, Mischa. ------------------------------------------------ EURASIP Journal on Wireless Communications and Networking Special Issue on Novel Techniques for Analysis & Design of Cross-Layer Optimized Wireless Sensor Networks Sensor networks have been researched and deployed for decades; their wireless extension, however, has witnessed a tremendous upsurge in recent years. This is mainly attributed to the unprecedented operating conditions of wireless sensor networks (WSNs), i.e. - a potentially enormous amount of sensor nodes, - reliably operating under stringent energy constraints. The virtually infinite degrees of freedom of wireless sensor networks have ignited intense research activities, which in turn led to thousands of publications, white papers and patents in less than a decade, with new contributions emerging on a daily basis. The rich mathematical and technical toolboxes already available from the design of wireless cellular and ad hoc systems clearly aided the birth of new ideas tailored to the problems in WSNs. To date, the main problem in deploying WSNs is their dependence on limited battery power. A main design criterion is to extend the lifetime of the network without jeopardizing reliable and efficient communications from sensor nodes to other nodes or to data sinks. A prominent example of today's non-optimized WSN deployment experiences is that the start-up alone costs the network half its battery power. Optimizing every facet of the communication protocols is therefore vital and imperative. Such stringent design requirements can be met by a plethora of approaches, e.g. optimizing each layer of the protocol stack separately (traditional) or jointly (cross-layer), for each node separately (traditional) or for an ensemble of nodes (distributed and cooperative), etc. This has led to copious novel distributed signal processing algorithms, energy-efficient medium access control and fault-tolerant routing protocols, self-organizing and self-healing sensor network mechanisms, etc. In the light of the above, the main purpose of this special issue is twofold: - to obtain a coherent and concise technical synthesis from the abundance of recently emerged material in the area of WSNs, and - to promote novel approaches in analyzing, designing and optimizing large-scale WSNs, preferably inspired by approaches from other disciplines, such as physics or biology. Very few papers are currently available which synthesize the large amount of fairly dispersed technical contributions; a coherent exposure, also touching upon open research issues, will certainly be appreciated by the academic and industrial research community. We believe that novel approaches, potentially inspired by entirely disjoint disciplines, may help considerably in dealing with networks of thousands of nodes. Topics of interest in the area of energy-constraint WSNs include, but are not limited to: - network capacity w/out imperfections - joint source and channel coding - cooperative and distributed signal processing - data fusion and data aggregation - novel PHY, MAC and network paradigms - cross-layer and cross-functionality design - security, robustness, reliability - self-healing, self-stabilization, self-organization - applications, architectures and topologies - (macroscopic) information flows - physically and biologically inspired approaches Submission details can be found under (copy entire link): http://www.hindawi.com/GetPage.aspx?journal=3DWCN&page=3DCLOWS . Submission deadline: 1 October 2006 Notification: 1 February 2007 Publication: 3rd Q 2007 Guest Editors Dr Mischa Dohler France Telecom R&D France mischa.dohler@orange-ft.com Prof Taieb Znati University of Pittsburgh USA znati@cs.pitt.edu Dr Stavros Toumpis University of Cyprus Cyprus toumpis@ucy.ac.cy Prof Lionel M. Ni Hong Kong University of Science and Technology Hong Kong, China ni@cs.ust.hk=20 ------_=_NextPart_001_01C6A027.67E0E5DE Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear colleagues,

You = are kindly=20 invited to submit high-quality contributions according to below CFP for = a=20 special issue on sensor networks.

Kind=20 regards,
Mischa.

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

EURASIP=20 Journal on Wireless Communications and Networking

Special Issue=20 on
Novel Techniques for Analysis & Design of Cross-Layer=20 Optimized Wireless Sensor Networks

Sensor networks have = been=20 researched and deployed for decades; their wireless extension, however, = has=20 witnessed a tremendous upsurge in recent years. This is mainly = attributed to the=20 unprecedented operating conditions of wireless sensor networks (WSNs), = i.e.
-=20 a potentially enormous amount of sensor nodes,
- reliably operating = under=20 stringent energy constraints.

The virtually infinite degrees of = freedom=20 of wireless sensor networks have ignited intense research activities, = which in=20 turn led to thousands of publications, white papers and patents in less = than a=20 decade, with new contributions emerging on a daily basis. The rich = mathematical=20 and technical toolboxes already available from the design of wireless = cellular=20 and ad hoc systems clearly aided the birth of new ideas tailored to the = problems=20 in WSNs.

To date, the main problem in deploying WSNs is their = dependence=20 on limited battery power. A main design criterion is to extend the = lifetime of=20 the network without jeopardizing reliable and efficient communications = from=20 sensor nodes to other nodes or to data sinks. A prominent example of = today’s=20 non-optimized WSN deployment experiences is that the start-up alone = costs the=20 network half its battery power.

Optimizing every facet of the=20 communication protocols is therefore vital and imperative. Such = stringent design=20 requirements can be met by a plethora of approaches, e.g. optimizing = each layer=20 of the protocol stack separately (traditional) or jointly (cross-layer), = for=20 each node separately (traditional) or for an ensemble of nodes = (distributed and=20 cooperative), etc. This has led to copious novel distributed signal = processing=20 algorithms, energy-efficient medium access control and fault-tolerant = routing=20 protocols, self-organizing and self-healing sensor network mechanisms,=20 etc.

In the light of the above, the main purpose of this special = issue is=20 twofold:
- to obtain a coherent and concise technical synthesis from = the=20 abundance of recently emerged material in the area of WSNs, and
- to = promote=20 novel approaches in analyzing, designing and optimizing large-scale = WSNs,=20 preferably inspired by approaches from other disciplines, such as = physics or=20 biology.

Very few papers are currently available which synthesize = the=20 large amount of fairly dispersed technical contributions; a coherent = exposure,=20 also touching upon open research issues, will certainly be appreciated = by the=20 academic and industrial research community. We believe that novel = approaches,=20 potentially inspired by entirely disjoint disciplines, may help = considerably in=20 dealing with networks of thousands of nodes.

Topics of interest = in the=20 area of energy-constraint WSNs include, but are not limited to:
- = network=20 capacity w/out imperfections
- joint source and channel coding
-=20 cooperative and distributed signal processing
- data fusion and data=20 aggregation
- novel PHY, MAC and network paradigms
- cross-layer = and=20 cross-functionality design
- security, robustness, reliability
-=20 self-healing, self-stabilization, self-organization
- applications,=20 architectures and topologies
- (macroscopic) information flows
-=20 physically and biologically inspired approaches

Submission = details can be=20 found under (copy entire link):  http://www.hindawi.com/GetPage.aspx?journal=3DWCN&page=3DCLOWS.

Submission=20 deadline:          &nbs= p; 1=20 October=20 2006
Notification:        &nbs= p;         =20 1 February=20 2007
Publication:         = ;          =20 3rd Q 2007

Guest Editors
Dr Mischa Dohler
France Telecom=20 R&D
France
mischa.dohler@orange-ft.com

Prof Taieb=20 Znati
University of Pittsburgh
USA
znati@cs.pitt.edu

Dr = Stavros=20 Toumpis
University of = Cyprus
Cyprus
toumpis@ucy.ac.cy

Prof=20 Lionel M. Ni
Hong Kong University of Science and Technology
Hong = Kong,=20 China
ni@cs.ust.hk =

------_=_NextPart_001_01C6A027.67E0E5DE-- --===============2010555310== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============2010555310==-- From manet-bounces@ietf.org Thu Jul 06 17:24:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FybKa-0007K5-3l; Thu, 06 Jul 2006 17:24:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FybKX-0007K0-RR for manet@ietf.org; Thu, 06 Jul 2006 17:24:13 -0400 Received: from mail2.microsoft.com ([131.107.1.7]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FybKV-0004NP-I6 for manet@ietf.org; Thu, 06 Jul 2006 17:24:13 -0400 Received: from mailout6.microsoft.com ([157.54.69.150]) by mail2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 6 Jul 2006 14:24:10 -0700 Received: from RED-MSG-50.redmond.corp.microsoft.com ([157.54.61.148]) by mailout6.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 6 Jul 2006 14:24:09 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 6 Jul 2006 14:23:34 -0700 Message-ID: <1152E22EE8996742A7E36BBBA7768FEE0A3B8706@RED-MSG-50.redmond.corp.microsoft.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Wireless Networking & Communications -- Educational Resources Thread-Index: AcahQnABzD7DILHNROyIKOJKyK/oKw== From: "Victor Bahl" To: , , X-OriginalArrivalTime: 06 Jul 2006 21:24:09.0813 (UTC) FILETIME=[85033050:01C6A142] X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: Mythreyee Ganapathy , "U. B. Desai" Subject: [manet] Wireless Networking & Communications -- Educational Resources 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: , Errors-To: manet-bounces@ietf.org I would like to bring to your attention some materials on wireless networking & communications.=20 On April 7 & 8, 2006, we organized a Wireless Networking Summit in Goa, India. Over 60 researchers from industry, academia, and government got together to exchange ideas and discuss problems and opportunities in this field. All presentations were video-taped and they are now available to the community for on-demand viewing on the summit's web site.=20 http://research.microsoft.com/india/events/wins2006.=20 Also, a similar summit, on Mesh Networking, was held in Snoqualmie, Washington in June 2004. The presentations & videos from that are also available at:=20 http://research.microsoft.com/meshsummit/ Drop me a note if you find these useful, and please forward this message to colleagues and students who may be interested in knowing about this. Thanks! Victor Bahl Microsoft Research _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Jul 07 10:48:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyrdN-0005ut-9C; Fri, 07 Jul 2006 10:48:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FyrdL-0005uZ-63 for manet@ietf.org; Fri, 07 Jul 2006 10:48:43 -0400 Received: from basm.cerias.purdue.edu ([128.10.243.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FyrdH-0000RQ-Mh for manet@ietf.org; Fri, 07 Jul 2006 10:48:43 -0400 Received: from basm.cerias.purdue.edu (crisn@localhost [127.0.0.1]) by basm.cerias.purdue.edu (8.13.6/8.13.6/PURDUE_CERIAS-2.0) with ESMTP id k67EmZNR025620 for ; Fri, 7 Jul 2006 10:48:35 -0400 (EDT) Received: from localhost (crisn@localhost) by basm.cerias.purdue.edu (8.13.6/8.13.6/Submit) with ESMTP id k67EmXQu025616 for ; Fri, 7 Jul 2006 10:48:35 -0400 (EDT) Date: Fri, 7 Jul 2006 10:48:32 -0400 (EDT) From: Cristina Nita-Rotaru To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on basm.cerias.purdue.edu X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL, SPF_HELO_PASS autolearn=unavailable version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on basm.cerias.purdue.edu X-Spam-Score: 0.0 (/) X-Scan-Signature: e16ce0269ccb2f59707d16700199d13b Subject: [manet] SecureComm 2006 - CALL FOR PARTICIPATION 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: , Errors-To: manet-bounces@ietf.org Dear Colleague, Please find attached the call for participation for the Second International Conference on Security and Privacy in Communication Networks (SecureComm 2006) to be held in Baltimore, MD from Aug. 28 to Sept. 1, 2006. The complete information is available on the website: www.securecomm.org The list of accepted papers is included in this announcement. The detailed technical program will be available shortly. We apologize if you receive multiple copies of this message. Please feel free to distribute this to colleagues who might be interested. Best Regards, SecureComm 2006 Organizing Committee ******************************************************************* CALL FOR PARTICIPATION SecureComm 2006 Second International Conference on Security and Privacy in Communication Networks (SecureComm 2006) Baltimore, MD, USA, Aug. 28 - Sep. 1, 2006 URL: http://www.securecomm.org CO-SPONSORED BY: IEEE Communications Society (www.comsoc.org) CreateNet (www.create-net.it) In Cooperation with ACM SIGSAC Early Registration Ends August 1, 2006 ******************************************************************* The scope of Securecomm 2006 has been broadened since the inaugural 2005 event. Topics of interest encompass research advances in ALL areas of secure communications and networking. Securecomm aims to bring together security and privacy experts in academia, industry and government as well as practitioners, standards developers and policy makers. Securecomm also serves as a venue for learning about state-of-the-art in security and privacy research. Presentations reporting on cutting-edge research results are supplemented by panels on controversial issues and invited talks on timely and important topics. KEYNOTE/INVITED TALKS: * Tue, August 29th, Speaker: Charles Palmer, IBM * Wed, August 30th, Speaker: Brian Snow, Recently with DoD/NSA PAPERS: The list of accepted papers is below. A detailed technical program will be announced shortly. ******* A Double Horizon Defense Design for Robust Regulation of Malicious Traffic Ying Xu, Roch Guerin A Flexible Approach to Intrusion Alert Anonymization and Correlation Dingbang Xu, Peng Ning A Framework for Identifying Compromised Nodes in Sensor Networks Qing Zhang, Ting Yu, Peng Ning A Server-Side Proxy for Preventing Cross Site Request Forgery Attacks Nenad Jovanovic, Christopher Kruegel, Engin Kirda An Architecture for an Email Worm Prevention System Mohamed Taibah, Ehab Al-Shaer An Identity-based Ring Signature Scheme with Enhanced Privacy Chandana Gamage, Ben Gras, Andrew Tanenbaum, Bruno Crispo An Intelligent Infrastructure Strategy to Improving the Performance and Detection Capability of Intrusion Detection Systems Emmanuel Hooper Attacking Mobile Phones by Exploiting Emerging Vulnerabilities in Cellular Data Services Hao Chen, Denys Ma, Radmilo Racic DaTA -- Data Transparent Authentication without Communication Overhead Songqing Chen Denial of Service Attacks and Defenses in Decentralized Trust Management Ninghui Li, Jiangtao Li, XiaoFeng Wang, Ting Yu Detecting the Sybil Attack in Ad hoc Networks Clay Shields, Chris Piro, Brian N. Levine Detection of Anomalous Network Packets using Lightweight Stateless Payload Inspection Nnamdi Nwanze, Douglas Summerville, Victor Skormin Discount Anonymous On Demand Routing for Mobile Ad hoc Networks Liu Yang, Markus Jakobsson, Susanne Wetzel Distributed Authentication of Program Integrity Verification in Wireless Sensor Networks Katharine Chang, Kang G. Shin Distributed Stealthy Coordination Mechanism for Worm Synchronization Gaurav Kataria, Adrian Perrig, Dawn Song, Ramayya Krishnan, Gaurav Anand, Rudolph Araujo Effective Detection of Active Worms with Varying Scan Rate Wei Yu, Xun Wang, Dong Xuan, David Lee Enabling Confidentiality in Content-Based Publish/Subscribe Infrastructures Costin Raiciu, David Rosenblum Enhancing Benign User Cooperation in the Presence of Malicious Adversaries in Ad Hoc Networks John Baras, George Theodorakopoulos How to Design Connected Sensor Networks that are Provably Secure Roberto Di Pietro, Luigi Mancini, Alessandro Mei, Alessandro Panconesi, Jaikumar Radhakrishnan Implementation and Performance Evaluation of EAP-TLS-KS Susanne Wetzel, Jared Cordasco, Ulrike Meyer In-Band Wormholes and Countermeasures in OLSR Networks Peter Kruus, Dan Sterne, Richard Gopaul, Michael Heyman, Brian Rivera, Peter Budulas, Brian Luu, Tommy Johnson, Natalie Ivanic, Geoff Lawler Leveraging IPsec for Mandatory Access Control Across Systems Trent Jaeger, Dave King, Kevin Butler, Serge Hallyn, Joy Latten, Xiaolan Zhang Message Dropping Attacks in Overlay Networks: Attack Detection and Attacker Identification Liang Xie, Sencun Zhu MOBIWORP: Mitigation of the Wormhole Attack in Mobile Multihop Wireless Networks Issa Khalil, Saurabh Bagchi, Ness Shroff Non-Invasive Methods for Host Certification Patrick Traynor, Michael Chien, Scott Weaver, Boniface Hicks, Patrick McDaniel On filtering of DDoS attacks based on source address prefixes Cristian Estan, Gary Pack, Jaeyoung Yoon, Eli Collins On Mobile Viruses Exploiting Messaging and Bluetooth Services Abhijit Bose, Kang G. Shin Packet coding for strong anonymity in ad hoc networks Imad Aad, Claude Castelluccia, Jean-Pierre Hubaux Provably Secure Ubiquitous Systems: Universally Composable RFID Authentication Protocols Mike Burmester, Tri van Le, Breno de Medeiros Secure Real-time User Preference Collection for Broadcast Scheduling Xuhua Ding, Baihua Zheng, Shuhong Wang TOPO: A Topology-aware Single Packet Attack Traceback Scheme Linfeng Zhang, Yong Guan Towards More Efficient Distance Bounding Protocols for Use in Sensor Networks Catherine Meadows, Paul Syverson, LiWu Chang ****************** POSTERS/DEMOS: Securecomm 2006 will include poster/demonstration sessions that shall provide a forum to present and discuss: works in progress, industry demonstrations of new applications and techniques, practical implementations, industrial and commercial developments, research testbeds and demonstrations, recent research/implementation results, upcoming research challenges, future directions, and novel approaches in the fields of communications and network security and privacy. WORKSHOPS: The conference will also feature workshops on hot topics related to communication network security. IMPORTANT DATES --------------- Early Registration Deadline: August 1, 2006 Conference Dates: Aug. 28 - Sep. 1, 2006 For information regarding the conference, please visit http://www.securecomm.org or contact one of the Chairs below. CONFERENCE ORGANIZING COMMITTEE General Co-Chairs ----------------- Mukesh Singhal, University of Kentucky, singhal@cs.uky.edu John Baras, University of Maryland, College Park, baras@isr.umd.edu Technical Program Co-Chairs --------------------------- Steve Kent, BBN, kent@bbn.com Gene Tsudik, UC Irvine, gts@ics.uci.edu Workshops Chair --------------- G. Manimaran, Iowa State University, gmani@iastate.edu Panels Co-Chairs ---------------- Bruno Crispo, Vrije Universiteit, Netherlands, crispo@few.vu.nl Avishai Wool, Technion, Israel, yash@eng.tau.ac.il Research Demos/Exhibits Chair ----------------------------- Tom Karygiannis, NIST, karygiannis@nist.gov Sponsorships Chair ------------------ Byrav Ramamurthy, University of Nebraska, Lincoln, byrav@cse.unl.edu Publicity Co-Chairs ------------------- Peng Liu, Penn State University, pliu@ist.psu.edu Cristina Nita-Rotaru, Purdue University, crisn@cs.purdue.edu Publication Chair ----------------- Farooq Anjum, Telcordia Technologies, fanjum@telcordia.com Steering Committee: ------------------- Imrich Chlamtac (Chair), Create-Net Krishna M. Sivalingam (Co-Chair), University of Maryland, Baltimore County Gene Tsudik, University of California, Irvine Brian Bigalke, (Staff Liaison, IEEE Communications Society) TECHNICAL PROGRAM COMMITTEE --------------------------- N. Asokan Nokia Research Giuseppe Ateniese Johns Hopkins University Tuomas Aura Microsoft Research Dirk Balfanz PARC Bharat Bhargava Purdue Matt Bishop University of California, Davis Levente Buttyan Budapest University of Technology Srdjan Capkun Technical University of Denmark Claude Castelluccia Inria Rhone-Alpes Tom Chen Southern Methodist University Giovanni Di Crescenzo Telcordia Research Bruno Crispo Vrije Universitet Breno de Medeiros University of Central Florida Robert Deng Singapore Management University Xuhua Ding Singapore Management University Glenn Durfee PARC Bao Feng Institute for Infocomm Research Dieter Gollmann Technical University of Hamburg-Harb Richard Han University of Colorado at Boulder Tom Karygiannis NIST Yongdae Kim University of Minnessota Christopher Kruegel Technical University of Vienna Brian LaMacchia Microsoft Carl Landwehr University of Maryland Wenke Lee Georgia Tech Albert Levi Sabanci University, Ninghui Li Purdue Peng Liu Pennsylvania State University Luigi Mancini Unversity of Rome - La Sapienza Fabio Massacci University of Trento Ludovic Me' Supelec Pietro Michiardi Eurecom Institute Refik Molva Eurecom Institute Mats Naslund Ericsson Research Pekka Nikander Ericsson Nomadiclab Cristina Nita-Rotaru Purdue Radha Poovendran University of Washington Byrav Ramamurthy University of Nebraska-Lincoln Michael Roe Microsoft Research Sanjeev Setia George Mason University Cliff Wang Army Research Laboratory Helen Wang Microsoft Research Ron Watro BBN Dirk Westhoff NEC Research Susanne Wetzel Stevens Institute of Technology Avishai Wool Tel Aviv University Shouhuai Xu University of Texas, San Antonio Xiaowei Yang University of California, Irvine Bulent Yener Rensselauer Polytechnic Institute Jeong Hyun Yi Samsung Advanced Institute of Technology Jianying Zhou Institute for Infocomm Research Alf Zugenmaier DoCoMo Labs ************************************************************************ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Jul 10 11:04:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzxIc-0006bj-MC; Mon, 10 Jul 2006 11:03:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzxIa-0006az-Fv for manet@ietf.org; Mon, 10 Jul 2006 11:03:48 -0400 Received: from mail.cs.dartmouth.edu ([129.170.212.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FzxIY-0003ls-3x for manet@ietf.org; Mon, 10 Jul 2006 11:03:48 -0400 Received: from beaver.cs.dartmouth.edu (beaver.cs.dartmouth.edu [129.170.213.211]) by mail.cs.dartmouth.edu (8.13.6/8.13.4) with ESMTP id k6AF3heI024468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 10 Jul 2006 11:03:43 -0400 Received: from beaver.cs.dartmouth.edu (localhost.localdomain [127.0.0.1]) by beaver.cs.dartmouth.edu (8.13.6/8.12.11) with ESMTP id k6AF3hBw018480 for ; Mon, 10 Jul 2006 11:03:43 -0400 Received: (from tristan@localhost) by beaver.cs.dartmouth.edu (8.13.6/8.13.4/Submit) id k6AF3hjO018479 for manet@ietf.org; Mon, 10 Jul 2006 11:03:43 -0400 Date: Mon, 10 Jul 2006 11:03:43 -0400 From: Tristan Henderson To: manet@ietf.org Message-ID: <20060710150343.GC18433@beaver.cs.dartmouth.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 48472a944c87678fcfe8db15ffecdfff Subject: [manet] Call for participation: WICON 2006 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: , Errors-To: manet-bounces@ietf.org Apologies if you receive this more than once. CALL FOR PARTICIPATION Wireless Internet Conference (WICON 2006) August 2-5 2006, Boston, USA http://www.wicon.org Sponsored by ICST, Create-Net and EU (IST-FET) In cooperation with ACM SIGMOBILE and IEEE Computer Society (pending approval) PROGRAM: August 2 9:00 Welcome 9:15 Session I: Wireless Measurement - Spatio-Temporal Modeling of Traffic Workload in a Campus WLAN. Felix Hernandez-Campos, Merkouris Karaliopoulos, Maria Papadopouli, and Haipeng Shen (University of North Carolina-Chapel Hill, USA) - Characterization by Measurement of a CDMA 1x EVDO Network. Mark Claypool (WPI, USA) - End-To-End Microflow Performance Measurement of IPv6 Traffic Over Diverse Wireless Topologies. Dimitrios Pezaros, Manolis Sifalakis, David Hutchison (Lancaster University, UK) 10:30 Coffee break 11:00 Keynote 1 12:00 Lunch 1:00 Session II: Wireless Mesh Networks - A Simple and Efficient Hop-by-hop Congestion Control Protocol for Wireless Mesh Networks. Bahareh Sadeghi (Intel, USA), Akira Yamada, Atsushi Fujiwara (DoCoMo, Japan), Lily Yang (Intel, USA) - Proposed Routing for IEEE 802.11s Mesh Networks. Michael Bahr (Siemens, Germany) - VoIP over Wireless Mesh Neworks: Challenges and Approaches. Xudong Wang, Abhishek Patil, and Weilin Wang (Kiyon, USA) - Mesh Technology enabling Ubiquitous Wireless Networks. Guido R. Hiertz, Sebastian Max, Erik Wei, Lars Berlemann (RWTH Aachen, Germany), Dee Denteneer (Philips, Netherlands), Stefan Mangold (Swisscom, Switzerland) 2:45 Coffee break 3:15 Session III: Congestion Control - Congestion Control in CSMA-Based Networks with Inconsistent Channel State. V. Gambiroza and E. Knightly (Rice University, USA) - A TCP with Guaranteed Performance in Networks with Dynamic Congestion and Random Wireless Losses, Stefan Schmid, Roger Wattenhofer (ETH, Switzerland) 4:00 Session IV: Wireless Performance - Combinatorial Approaches to QoS Scheduling in Multichannel Wireless Networks. Rajagopal Iyengar (RPI, USA). - Design and Implementation of a Socket-level Bandwidth Aggregation Mechanism for Wireless Networks. Hiroshi Sakakibara (Keio University, Japan). - Improving Layer 3 Handoff Delay in IEEE 802.11 Wireless Networks. Andrea Forte, Sangho Shin, Henning Schulzrinne (Columbia University, USA). August 3 9:00 Session V: Spectrum Efficiency - Opportunistic Spectrum Access: Challenges, Architecture, and Protocols. C. Santivanez, Ram Ramanathan, Craig Partridge, R. Krishnan, M. Condell, S. Polit (BBN Technologies, USA) - Single-Packet Radiolocation of 802.11 Wireless Sources Using an Array of Stationary Antennas and High-Speed RF Multiplexing. Danko Antolovic (Indiana University, USA) - Selecting Transmit Powers and Carrier Sense Thresholds in CSMA. Jason A. Fuemmeler, Nitin H. Vaidya, Venugopal V. Veeravalli, UIUC. 10:30 Coffee break 11:00 Keynote 2 12:00 Lunch 1:00 Panel organized by Dr. Sneha Kumar 2:30 Session VI: Wireless Security - An efficient signature representation and matching method for mobile devices. Deepak Venugopal. - A Low-Cost Robust Localization Scheme for WLAN. S. Pandey, F. Anjum, B. Kim and P. Agrawal. 3:15 Coffee break 3:45 Session VII: Future Wireless Networks - Toward People-Centric Urban Sensing. Andrew Campbell (Dartmouth University, USA). - Vehicular Grid Communications: The Role of the Internet Infrastructure. Mario Gerla, Biao Zhou, Yeng-Zhong Lee, Fabio Soldo, Uichin Lee, Gustavo Marfia (UCLA, USA). - Context Reactive User Experience. Babak Hodjat (Dejima Inc., USA) August 4: Industry Track 9:00 Welcome 9:15 Session I: Applications - Adaptive Wireless Video Streaming Proxy for Home Entertainment Networks. Richard Chen (Philips Research), Pei Liu (Polytechnic University) , Karl Wittig , Ruediger Schmitt (Philips Research) - Intel VoIP over WLAN Architecture. Ajay V. Bakre (Intel Research, Berkeley) - Ontology and Application to Improve Dynamic Bindings in Mobile Distributed Systems. Ben Falchuk, Dave Marples (Telcordia Technologies) 10:30 Coffee break 11:00 Keynote 12:00 Lunch 1:00 Session II: Infrastructure - Towards an Internet Mobility Management Architecture. James Kempf (DoCoMo labs, USA) and Phil Roberts (Motorola Labs) - Antenna Tilt Control in CDMA Networks. George Calcev , Matt Dillon (Motorola, Inc.) - Impact of the 802.11e MAC Layer on Mixed TCP-based Applications. Marina Thottan (Bell Labs) and Michele Weigle (Clemson University) - Evolution of Spectrum-Agile Cognitive Radios: First Wireless Internet Standard and Beyond. Kiran Challapali, Carlos Cordeiro, Dagnachew Birru (Philips Research) 2:45 Coffee break 3:15 Panel August 5: Workshops - TAPAS (Workshop on Technology and Policy for Accessing Spectrum) www.tapas.org - WISEC (Workshop on Security in Wireless Networks) www.secwin.org - WITMEMO (Workshop on Wireless Traffic Measurements and Modelling) www.witmemo.org COMMITTEES: General Chair: Ravi Jain, Google Ram Ramjee, Bell Labs Technical Program Co-Chairs: Lili Qiu, University of Texas at Austin Andras Valko, Ericsson Steering Committee Chair: Imrich Chlamtac, Create-Net Publicity Co-Chairs: Tristan Henderson, Dartmouth Mun Coon Chan, Bell Labs Carla-Fabiana Chiasserini, Politechnico di Torino Local Chair: Guevara Noubir Workshop Co-Chairs: Suman Banerjee, Univ. of Wisconsin Chiara Petrioli, Rome University Industry track Co-Chairs: Sujata Banerjee, HP Milind Buddhikot, Bell Labs Panel Chair: Sneha Kasera, University of Utah Poster Co-Chair: Christian Bettstetter, University of Klagenfurt Rajeev Shorey, National Univ. of Singapore _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Jul 10 12:52:41 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fzyzr-0000eH-VS; Mon, 10 Jul 2006 12:52:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fzyzq-0000Zb-4L for manet@ietf.org; Mon, 10 Jul 2006 12:52:34 -0400 Received: from nz-out-0102.google.com ([64.233.162.199]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fzyzo-0003fi-Sy for manet@ietf.org; Mon, 10 Jul 2006 12:52:34 -0400 Received: by nz-out-0102.google.com with SMTP id r28so166194nza for ; Mon, 10 Jul 2006 09:52:32 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=Nic7kMxOofO1CV/Qt3ifB6Dwd/gbKCTocbr8IrbWzTfgbZxhKCSntvPTKyvkCT5PkjFj9VhBl43X+cdAa+2g+sPDW5qy+i1gDaf2SY8C1llUNMD3lPFWJEaWJe8VX7DpnU8ebR1DHNUJOvdD36X6Nkw67fyMY2qto1O3LqvQKXk= Received: by 10.36.113.8 with SMTP id l8mr5831576nzc; Mon, 10 Jul 2006 09:52:32 -0700 (PDT) Received: by 10.36.160.3 with HTTP; Mon, 10 Jul 2006 09:52:32 -0700 (PDT) Message-ID: <738ad5960607100952v2fcdfb7ar1249227b6b675644@mail.gmail.com> Date: Mon, 10 Jul 2006 18:52:32 +0200 From: "iaria - announce" To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Cc: pdini@cisco.com Subject: [manet] CFP: ICQNM 2007 || ICDS 2007 || Guadeloupe, January 2-7, 2007. 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: , Errors-To: manet-bounces@ietf.org ======================================= Apologies for multiple copies and cross-posting CALL FOR SUBMISSIONS Place: Guadeloupe, French Caribbean Date: January 2-7, 2007 Important deadlines: Paper submission August 15, 2006 Notification September 10, 2006 Registration September 30, 2006 ICQNM 2007, TheFirst International Conference on Quantum, Nano, and Micro Technologies General: http://www.iaria.org/conferences2007/ICQNM07.html CFP: http://www.iaria.org/conferences2007/CfPICQNM07.html January 2-4, 2007, Guadeloupe, French Caribbean includes NBR 2007: The First International Workshop on Nano and Bio Robotics CFP: http://www.iaria.org/conferences2007/NBR.html includes QSEC 2007: The First International Workshop on Quantum Security CFP: http://www.iaria.org/conferences2007/QSEC.html ICDS 2007, The First International Conference on the Digital Society General: http://www.iaria.org/conferences2007/ICDS07.html CFP: http://www.iaria.org/conferences2007/CfPICDS07.html January 5-7, 2007, Guadeloupe, French Caribbean includes EKNOW 2007: The First International Workshop on Information and Knowledge Management CFP: http://www.iaria.org/conferences2007/EKNOW.html includes TELEMED 2007: The First International Workshop on Telemedicine CFP: http://www.iaria.org/conferences2007/TELEMED.html Proceedings are published by the IEEE Computer Society Press and on-line via IEEE XPlore Digital Library. The papers are indexed by major indexes. see: http://www.iaria.org/conferences.html, window "Accessing Papers on-line" Submissions could be regular papers, position papers, tutorials, and panels. see: http://www.iaria.org/conferences.html, window "Selection Process, Policies, and Instructions" For details on topics, see the CFP for the appropriate event. Looking for your contributions, ICQNM 2007 and ICDS 2007 Organizing Committees _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Jul 10 13:03:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzzAb-0006b7-84; Mon, 10 Jul 2006 13:03:41 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzzAa-0006b2-C3 for manet@ietf.org; Mon, 10 Jul 2006 13:03:40 -0400 Received: from smtp-2.smtp.ucla.edu ([169.232.47.136]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FzzAY-0004J2-Mf for manet@ietf.org; Mon, 10 Jul 2006 13:03:40 -0400 Received: from mail.ucla.edu (mail.ucla.edu [169.232.47.146]) by smtp-2.smtp.ucla.edu (8.13.6/8.13.6) with ESMTP id k6AH3bwU023694 for ; Mon, 10 Jul 2006 10:03:37 -0700 Received: from [192.168.0.100] (64-121-53-50.c3-0.snmt-ubr1.sfrn-snmt.ca.cable.rcn.com [64.121.53.50]) (authenticated bits=0) by mail.ucla.edu (8.13.6/8.13.6) with ESMTP id k6AH3bKH003786 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 10 Jul 2006 10:03:37 -0700 Message-ID: <44B2886A.4050305@cs.ucla.edu> Date: Mon, 10 Jul 2006 10:03:38 -0700 From: Maneesh Varshney User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: manet@ietf.org X-Probable-Spam: no X-Spam-Hits: 0.296 X-Spam-Report: HTML_10_20,HTML_MESSAGE X-Scanned-By: smtp.ucla.edu on 169.232.47.136 X-Spam-Score: 0.3 (/) X-Scan-Signature: 71f780ffdd80c541d3e75aa5f2710d3d Subject: [manet] Deadline Extended: Call for Posters and Demos: WiNTECH 2006, in conjunction with ACM Mobicom 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="===============0689174449==" Errors-To: manet-bounces@ietf.org This is a multi-part message in MIME format. --===============0689174449== Content-Type: multipart/alternative; boundary="------------050203010302030503080506" This is a multi-part message in MIME format. --------------050203010302030503080506 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit [Our apologies if you have received multiple copies of this CFP]. CALL FOR POSTERS AND DEMOS -------------------------------------------------------------------------------------------- The First International Workshop on Wireless Network Testbeds, Experimental evaluation and CHaracterization (WiNTECH 2006) in conjunction with ACM MobiCom 2006 September 29, 2006 Los Angeles, CA, USA Sponsored by ACM SIGMOBILE http://chenyen.cs.ucla.edu/events/wintech06/ *** Poster and Demo Abstract Submission Deadline: July 15, 2006 *** --------------------------------------------------------------------------------------------- OVERVIEW AND SCOPE -------------------------------------- In recent years, some wireless technologies (e.g., WiFi, sensor networks) have matured to the point of finding wide acceptance in the real-world and leading to many new and interesting applications. At the same time, several new networking and radio technologies (e.g., dynamic spectrum access, UWB) are emerging to address the performance limitations of existing technologies and make wireless networking more ubiquitous. Realistic evaluation of such diverse set of technologies and their mutual interactions will play a major role in identifying the key performance bottlenecks, thus shape future advances in wireless technology. With this in mind, this workshop intends to bring together researchers working in the broad area of experimental wireless networking. This workshop will serve as a forum to share new ideas/experiences in all experimental aspects of wireless networks and systems, and facilitate discussions of key unresolved challenges in this area. WiNTECH 2006 is soliciting proposals for research demonstrations of novel wireless testbed capabilities and measurement results. The session is intended to present the advances in tesbed and wireless characterizations and to foster discussions on future directions for wireless network evaluations. Demonstrations of works published earlier are also welcome. WiNTECH 2006 is also seeking proposals for posters describing novel work in wireless network testbeds, measurements and characterizations. The posters may describe work in progress and offers an excellent opportunity for feedback and discussions on early research. Topics of interest include, but are not limited to: * Design and evaluation of wireless testbeds, prototypes and platforms * Experiences/lessons from recent testbed design efforts * Hybrid experimentation approaches combining use of multiple evaluation methodologies * Integration of diverse and distributed testbed infrastructures * Testbed management issues and monitoring support * Wireless testbed case studies * Experimental evaluation of applications and protocols (at different layers), and the impact of cross-layer interactions * Large-scale and heterogeneous wireless network evaluations * Approaches for real-world evaluation of mobile networks * Evaluation environments for sensor and satellite networks * Techniques for improving reproducibility of real-world testing * Implementation approaches to ease transition between various evaluation methodologies as well as to improve testbed accessibility * New measurement methodologies and infrastructures * Measurement and characterization (modeling) of various real-world aspects such as usage patterns, traffic, mobility and channel characteristics * Interference and spectrum usage measurements * Validation of existing simulation models, and results across different testbeds/evaluation methodologies * Software tools in support of measurements, trace/data collection and management For submission instructions please refer the workshop website. All submissions will be reviewed by the technical program committee and will be judged by their technical merit and relevance to workshop. The extended abstract of the accepted posters and demos will be published in the workshop proceedings and will be available at the ACM digital library. IMPORTANT DATES -------------------------------- Submission deadline: July 15, 2006 Author notification: August 1, 2006 Camera ready papers: August 11, 2006 Workshop date: September 29, 2006 FURTHER INFORMATION ---------------------------------------- Please visit the WiNTECH 2006 workshop website: http://chenyen.cs.ucla.edu/events/wintech06/ --------------050203010302030503080506 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit [Our apologies if you have received multiple copies of this CFP].

CALL FOR POSTERS AND DEMOS
--------------------------------------------------------------------------------------------

The First International Workshop on Wireless Network Testbeds, Experimental evaluation and CHaracterization (WiNTECH 2006)
in conjunction with ACM MobiCom 2006
September 29, 2006
Los Angeles, CA, USA

Sponsored by ACM SIGMOBILE

http://chenyen.cs.ucla.edu/events/wintech06/ 
*** Poster and Demo Abstract Submission Deadline: July 15, 2006 ***

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

OVERVIEW AND SCOPE
--------------------------------------

In recent years, some wireless technologies (e.g., WiFi, sensor networks) have matured to the point of finding wide acceptance in the real-world and leading to many new and interesting applications. At the same time, several new networking and radio technologies (e.g., dynamic spectrum access, UWB) are emerging to address the performance limitations of existing technologies and make wireless networking more ubiquitous. Realistic evaluation of such diverse set of technologies and their mutual interactions will play a major role in identifying the key performance bottlenecks, thus shape future advances in wireless technology. With this in mind, this workshop intends to bring together researchers working in the broad area of experimental wireless networking. This workshop will serve as a forum to share new ideas/experiences in all experimental aspects of wireless networks and systems, and facilitate discussions of key unresolved challenges in this area.

WiNTECH 2006 is soliciting proposals for research demonstrations of novel wireless testbed capabilities and measurement results. The session is intended to present the advances in tesbed and wireless characterizations and to foster discussions on future directions for wireless network evaluations. Demonstrations of works published earlier are also welcome.

WiNTECH 2006 is also seeking proposals for posters describing novel work in wireless network testbeds, measurements and characterizations. The posters may describe work in progress and offers an excellent opportunity
for feedback and discussions on early research. Topics of interest include, but are not limited to:

* Design and evaluation of wireless testbeds, prototypes and platforms
* Experiences/lessons from recent testbed design efforts
* Hybrid experimentation approaches combining use of multiple evaluation methodologies
* Integration of diverse and distributed testbed infrastructures
* Testbed management issues and monitoring support
* Wireless testbed case studies
* Experimental evaluation of applications and protocols (at different layers), and the impact of cross-layer interactions
* Large-scale and heterogeneous wireless network evaluations
* Approaches for real-world evaluation of mobile networks
* Evaluation environments for sensor and satellite networks
* Techniques for improving reproducibility of real-world testing
* Implementation approaches to ease transition between various evaluation methodologies as well as to improve testbed accessibility
* New measurement methodologies and infrastructures
* Measurement and characterization (modeling) of various real-world aspects such as usage patterns, traffic, mobility and channel characteristics
* Interference and spectrum usage measurements
* Validation of existing simulation models, and results across different testbeds/evaluation methodologies
* Software tools in support of measurements, trace/data collection and management


For submission instructions please refer the workshop website. All submissions will be reviewed by the technical program committee and will be judged by their technical merit and relevance to workshop. The extended abstract of the accepted posters and demos will be published in the workshop proceedings and will be available at the ACM digital library.


IMPORTANT DATES
--------------------------------
Submission deadline: July 15, 2006
Author notification: August 1, 2006
Camera ready papers: August 11, 2006
Workshop date: September 29, 2006


FURTHER INFORMATION
----------------------------------------
Please visit the WiNTECH 2006 workshop website:
http://chenyen.cs.ucla.edu/events/wintech06/
--------------050203010302030503080506-- --===============0689174449== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0689174449==-- From manet-bounces@ietf.org Mon Jul 10 13:10:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzzH2-0004c8-Vl; Mon, 10 Jul 2006 13:10:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FzzH1-0004av-Cj for manet@ietf.org; Mon, 10 Jul 2006 13:10:19 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FzzH0-0004Zn-OW for manet@ietf.org; Mon, 10 Jul 2006 13:10:19 -0400 Received: from wee.isi.edu (wee.isi.edu [128.9.168.112]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k6AH8tu21725 for ; Mon, 10 Jul 2006 10:08:55 -0700 (PDT) From: Wei Ye To: manet@ietf.org Content-Type: text/plain; charset=UTF-8 Date: Mon, 10 Jul 2006 10:08:50 -0700 Message-Id: <1152551330.9960.15.camel@wee.isi.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: weiye@isi.edu Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by boreas.isi.edu id k6AH8tu21725 X-Spam-Score: 0.0 (/) X-Scan-Signature: 90e8b0e368115979782f8b3d811b226b Subject: [manet] ACM SenSys 2006: Travel Grants, Posters, Demos and Workshops 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: , Errors-To: manet-bounces@ietf.org ACM SenSys 2006: Travel Grants, Posters, Demos and Workshops Our Apologies if you have received multiple copies of this email. Wei Ye and Cormac J. Sreenan SenSys'06 Publicity Co-Chairs --------- The 4th ACM Conference on Embedded Networked Sensor Systems November 1-3, 2006 Boulder, Colorado, USA http://sensys.acm.org/2006/ Sponsored by ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS, SIGMETRICS and =20 SIGBED; with support from NSF. The 4th ACM Conference on Embedded Networked Sensor Systems (SenSys) =20 is a highly selective, single-track forum for the presentation of =20 research results on systems issues in the area of embedded, networked=20 sensors. Distributed systems based on networked sensors and actuators =20 with embedded computation capabilities allow for an instrumentation =20 of the physical world at an unprecedented scale and density, thus =20 enabling a new generation of monitoring and control applications. =20 This conference provides an ideal venue to address the research =20 challenges facing the design, deployment, use, and fundamental limits =20 of these systems. Sensor networks require contributions from many =20 fields, from wireless communication and networking, embedded systems =20 and hardware, distributed systems, data management, and applications, =20 so we welcome cross-disciplinary work. ACM SenSys 2006: Student Travel Grants -------------------------------------- We will assist around 17 US-based graduate students to attend this meeting. The amount of support provided to each student will be $881=20 on average, or the actual documented amount of expenses, whichever is less. It covers travel, lodging, registration, and meals. All travel support is made possible by a travel grant from the US National=20 Science Foundation (NSF). =20 Important Dates Travel applications due: September 1, 2006 Notification of awards: September 8, 2006 Acceptance by recipients: September 15, 2006 Application Procedure Applications for the travel award should be received electronically by Haiyun Luo (haiyun@cs.uiuc.edu) by Friday, September 1, 2006. Please make sure that you receive an email confirmation of your submission. An application will consist of the student's vita, a letter from the student, and a letter from the student's advisor. The letter from the student should include: 1. A brief summary of research interests and accomplishments to date 2. A description of areas reflected in the SenSys 2006 program that=20 would impact the students research 3. Importance of attend the conference to the students research activities =20 In addition, the student's advisor should send a letter of recommendation to the committee. It should include:=20 1. Confirmation that the student is a Ph.D. candidate in good=20 standing 2. The suitability SenSys 2006 program to the students research area 3. Ways in which attending the conference would benefit the particular student=20 4. The strengths and potential contributions of the student. The awards will be announced by Friday, September 8, 2006. Recipients will be required to accept the award by Friday, September 15, 2006, so that alternates can be notified in the event that a recipient declines. Award Selection Committee Nirupama Bulusu, Portland State U. Deepak Ganesan, UMass Haiyun Luo, UIUC Shivakant Mishra, U. of Colorado Sergio Servetto, Cornell=20 CALL FOR POSTERS ---------------- The poster session will provide a forum for researchers to showcase =20 their work and obtain feedback on ongoing research from knowledgeable =20 conference attendees. Areas of interest are the same as those listed =20 in the technical call for papers. While the poster need not describe =20 completed work, it should report on research for which at least =20 preliminary results are available. We especially encourage =20 submissions by students (that is, for which a student is the first =20 author on the poster). POSTER SUBMISSION INSTRUCTIONS Poster proposals must be submitted as a single PDF file with no more =20 than 3 pages. The first two pages should contain an abstract =20 describing the research content of the poster, along with title, =20 authors, institutional affiliations and contact information. The =20 third page should contain a thumbnail draft of the poster's contents. =20 Please submit your poster proposal as a PDF e-mail attachment to sensys06-poster-chairs@isi.edu with the subject line reading "Sensys Poster Submission" before the =20 deadline. Any questions for the Poster Co-chairs Henry Tirri (Nokia), =20 Robert Szewczyk (Moteiv) may also be directed to this address. IMPORTANT DATES Three-page poster proposal: 11:59pm (EST), July 24, 2006 Notification of acceptance: August 7, 2006 Camera-ready abstract: August 22, 2006 Conference dates: November 1-3, 2006 BASIC INFORMATION ABOUT POSTERS Two-page poster abstracts will appear in the conference proceedings. Authors of accepted poster proposals will have a chance to present the poster to interested attendees during a special poster session at SenSys. Well-crafted posters will tell the story well by themselves, but authors of posters are expected to be available to describe and discuss the work in the poster during the session. The poster dimensions are 30" by 40", with poster contents mounted on rectangular poster board that we will provide. You may choose a layout consisting of individual sheets of paper, or a monolithic large piece of poster paper (which can be printed at document companies). Henry Tirri, Nokia Robert Szewczyk, Moteiv SenSys 2006 Poster Chairs CALL FOR DEMOS -------------- Demonstrations showing innovative research and applications are =20 solicited. SenSys'06 is very interested in demonstrations of technology, platforms, and applications of wireless sensor networks. Two-page abstracts of accepted demos will be published in the SenSys conference proceedings. Submissions from both industries and universities are encouraged. Large-scale, outdoor demos can also be accommodated at the conference facility. For the first time, SenSys 2006 will present a best demo award. DEMO SUBMISSION INSTRUCTIONS Please send a two-page description of your demo to=20 sensys06-demo-chairs@isi.edu in PDF format by the dates listed below. An additional one page appendix can be included in the initial submission but will be removed in published proceedings. Be as specific as possible in describing what you will show. IMPORTANT DATES Two-page demo descriptions: 11:59pm (EST), July 24, 2006 Notification of acceptance: August 7, 2006 Camera-ready abstract: August 22, 2006 Conference dates: November 1-3, 2006 Chieh-Yih Wan, Intel Labs Jie Liu, Microsoft Research SenSys 2006 Demo Chairs Workshop on Distributed Smart Cameras (DSC-06) ---------------------------------------------- http://www.iti.tugraz.at/dsc06 Boulder, Colorado, USA October 31, 2006 Scope: Distributed smart cameras combine two concepts: physically =20 distributed cameras and distributed computing. Distributed smart =20 cameras are examples of high-performance multimedia sensor networks. =20 This area brings together researchers in image processing, sensor =20 networks, and embedded system architecture. Several groups are now working on distributed smart cameras, but =20 generally pursuing them in different research communities. This =20 meeting would be the first event to bring together all the research =20 groups working on this problem. We solicit papers addressing =20 theoretical and practical aspects of distributed smart cameras. We =20 particularly encourage submissions describing applications, case =20 studies or deployments. Topics of interest include, but are not limited to: - Distributed embedded systems for video - Smart camera architectures - Collaborative embedded vision - Networking for distributed smart cameras - Multi-sensor systems and sensor fusion - Middleware for distributed smart cameras - Applications of smart cameras in areas such as surveillance, =20 tracking and smart rooms Submission Instructions: We invite authors to submit papers no longer than 5 pages in PDF to =20 dsc06@iti.tugraz.at. Accepted papers will made available to workshop =20 participants. Demo presentations are welcome. If you plan to present =20 a demo of distributed smart cameras contact the workshop co-chairs. Important Dates: - Paper submission: July 31, 2006 - Notification of acceptance: Sep 15, 2006 - CR paper submission: Sep. 30, 2006 - Workshop: Oct. 31, 2006 Program co-chairs: B. Rinner, TU Graz W. Wolf, Princeton U. Program committee: F. Berry, Univ. Clermont-Ferrand S. Bhattacharyya, U. Maryland M. Bove, MIT Media Lab J. Ferryman, Reading Univ. C. Guestrin, CMU R. Kleihorst, Philips Research X. Koutsoukos, Vanderbilt U. C. Regazzoni, Univ. Genova M. Srivastava, UCLA W. Strasser, Univ. T=C3=BCbingen First Workshop on World-Sensor-Web (WSW'2006) --------------------------------------------- Mobile Device Centric Sensory Networks and Applications http://www.sensorplanet.org/wsw2006/ Boulder, Colorado, USA October 31, 200 SCOPE The global use of mobile phones on a scale never seen before enables =20 the development of new types of application scenarios. Furthermore, a =20 mobile device centric approach to large-scale sensory networks =20 provides a challenging platform for research purposes. Additionally, =20 connecting sensory networks to the Internet creates endless =20 opportunities for applications and services, new emerging models of =20 operation. The workshop aims to address these aspects, beside traditional =20 sensory network topics such as power management, communication =20 issues, topology management, distributed architectures, peer-to-peer =20 scenarios, etc. Demonstrations and initial ideas are welcome as well. Original, short or position papers (max 5 page), presenting results =20 on both theoretical and practical aspects of large-scale mobile =20 device centric sensor networks are expected. We are particularly =20 interested in prototype descriptions, reports from on-going trials =20 and demonstrations, real-life deployments. Live or videod demos are =20 encouraged. Topics of interest include but are not limited to: - device centric sensory networks - communication strategies and topology control - location and mobility management - power management, energy-efficient design - data gathering, transport, storage, retrieval, mining and =20 dissemination - data analysis and visualisation - modelling and simulation software tools - experimental systems and demonstrations - real-life deployments, middleware implementations - beyond location sensing - intelligent sensors, body sensors and their utilisation - phone as a gateway - end-user aspects, UI issues, use cases - sensory networks and the Web WORKSHOP CO-ORGANIZERS Henry Tirri, Nokia Research Center, Helsinki, Finland Barbara Heikkinen, Nokia Research Center, Helsinki, Finland Boda P=C3=A9ter, Nokia Research Center, Helsinki, Finland TECHNICAL PROGRAM COMMITTEE Joe Paradiso, MIT Media Laboratory, Cambridge, MA, USA Deborah Estrin, UCLA, Los Angeles, CA, USA Gaetano Borriello, University of Washington, Seattle, WA, USA Philippe Bonnet, University of Copenhagen, Copenhagen, Denmark Sam Madden, MIT CSAIL, Cambridge, USA Jukka Salminen, Nokia research Center, Helsinki, Finland IMPORTANT DATES Papers due: September 1, 2006 Notification of acceptance September 30, 2006 Camera-ready papers due October 10, 2006 SUBMISSION INSTRUCTIONS WSW'2006 invites submissions for position papers or short papers on =20 prototype descriptions, early research results, reports from on-going =20 demonstrations, etc. Demonstrations, live or videod, are mostly =20 encouraged. All papers should meet the following formatting rules: 1. Papers should be submitted in PDF format. 2. The maximum length is five pages. The paper size format is US=20 letter, including all text, figures, references, appendices, etc. 3. Two column formatting 4. One-inch margins on all sides 5. Minimum 10-point font size (smaller fonts are acceptable for =20 footnotes, references, and figure captions). Questions, inquiries Please mail to peter dot boda at nokia dot com with subject WSW2006.=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Jul 10 16:13:19 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G027v-0003Wg-P3; Mon, 10 Jul 2006 16:13:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G027t-0003Wb-Ql for manet@ietf.org; Mon, 10 Jul 2006 16:13:05 -0400 Received: from markov.ece.neu.edu ([129.10.60.83] helo=SMTP1.ECE.NEU.EDU) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G027r-0005Iv-FE for manet@ietf.org; Mon, 10 Jul 2006 16:13:05 -0400 Received: from calvin.ece.neu.edu (calvin.ece.neu.edu [129.10.62.61]) by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id k6AKD3S0017026 for ; Mon, 10 Jul 2006 16:13:03 -0400 (EDT) Received: from ECE.NEU.EDU ([129.10.60.216]) by calvin.ece.neu.edu (SAVSMTP 3.1.0.29) with SMTP id M2006071016130227804 for ; Mon, 10 Jul 2006 16:13:02 -0400 Received: from localhost (basagni@localhost) by ECE.NEU.EDU (8.12.8/8.12.5/Submit) with ESMTP id k6AKD28R001018 for ; Mon, 10 Jul 2006 16:13:03 -0400 Date: Mon, 10 Jul 2006 16:13:02 -0400 (EDT) From: Stefano Basagni To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 1676547e4f33b5e63227e9c02bd359e3 Subject: [manet] IEEE SECON 2006: Call for Demo/Posters, New Deadline 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: , Errors-To: manet-bounces@ietf.org (Apologies if you receive this call multiple times.) *********************************************************************** CALL FOR POSTERS and DEMOS NEW DEADLINE: July 16, 2006, 5 pm EDT* IEEE SECON 2006 The Third IEEE International Conference on Sensors, Mesh and Ad Hoc Communications and Networks http://www.ieee-secon.org/2006/ Sponsored by IEEE Communications Society (www.comsoc.org) Technically Co-Sponsored by AFCEA (www.afcea.org) September 25-28, 2006 Reston, Virginia, USA (Near Washington DC's Dulles airport) ************************************************************************ To provide a forum for discussion and personal interaction between presenter and participants, IEEE SECON 2006 will include poster and demonstration sessions: works in progress, industry demonstrations of new applications and techniques, practical implementations, military, industrial and commercial developments, research testbeds and demonstrations, recent research/implementation results, upcoming research challenges, future directions, and novel approaches in the fields of sensor, mesh and ad hoc communications and networks. One of the key goals of this conference is to foster collaboration between industry, government agencies and academia. Hence, participation of researchers/developers from industry or governement agencies and posters/demonstrations reporting joint work are especially encouraged. Topics considered for posters and demo are, but not limited to: * New architectures and protocols to support communication, localization, time synchronization, routing, data dissemination, and other distributed services in heterogeneous, large-scale distributed, mesh 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 ad hoc and sensor networks, practical implementations and deployments, and real-world experiences * Theories and models on fundamental information and communication aspects of wireless mesh and sensor networks * Mechanisms for authenticated, secure communication and data dissemination in sensor and mesh networks * Algorithms and protocols to support quality of service in mesh and sensor networks, including admission control, resource allocation and fairness, and capacity planning * Integration of sensors into engineered systems, including novel techniques for on-sensor renewable power sources, mechanisms for on-sensor self-calibration and self-testing, and efficient schemes to maximize accuracy and minimize false alarms * Hardware platforms incorporating multiple sensors, computation, actuation, and wireless interfaces * Software platforms, middleware, and tools for mesh and sensor network applications development, deployment, and management Submissions should be in the form of a proposal describing the main contributions of the poster/demo and the merits of the proposed ideas. If available, preliminary results can also be included. Proposals will be evaluated mainly based on their potential to stimulate interesting discussions, exchange of ideas and promote collaborations. A prize will be awarded to the best demo by a jury composed of academic and/or venture capital participants. Submissions should not be more than three pages (preferably IEEE conference format, 2-column) in length. Demonstration submissions should include the space requirements and/or any other equipment-specific requirements. The documents must contain the authors' names, affiliations, and contact information and the designated corresponding author. Accepted authors of posters/demos will have a space in the poster/demo session room to display their posters or exhibit their demos and describe their work in discussions with interested attendees. IEEE Communications Society policy states that all accepted SECON 2006 posters/demos must have at least one registration at the regular rate. For authors co-authoring multiple posters/demos, one regular registration is valid for up to three presentations. Submission will be accepted until Sunday July 16 2006, 5 pm EDT for demos and for posters. Please send the submission material to the poster/demo chairs in pdf format, and make sure to include the first author name and either POSTER or DEMO in the name of the pdf file: Stefano Basagni Cedric Westphal Northeastern University Nokia basagni@ece.neu.edu cedric.westphal@nokia.com Notification of Poster/Demo decisions: August 7, 2006. Presenters MUST register by August 31, 2006. ************************************************************ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 12 06:23:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0bs5-0002mj-9N; Wed, 12 Jul 2006 06:23:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0bs3-0002mc-9L for manet@ietf.org; Wed, 12 Jul 2006 06:23:07 -0400 Received: from nz-out-0102.google.com ([64.233.162.198]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0bs0-0006SH-LI for manet@ietf.org; Wed, 12 Jul 2006 06:23:07 -0400 Received: by nz-out-0102.google.com with SMTP id l8so57558nzf for ; Wed, 12 Jul 2006 03:23:04 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:reply-to:from:to:cc:subject:date:organization:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole:sender; b=H2IJfAKvZhKvJIPLHopXf2vWA9wVuDhZIo/c0K/zPhBRtiP8kh/LQLSiyzFKsg+OA0yS0hmq6YRX6iKIvEXAnV8Bh2wNEymxoAq9GkCu4DNnYui6x3o8APDVmAZ29jxMUsLLwItL/VILRdflwryJ751jUhCMIiRpdmYtmyse87M= Received: by 10.36.77.2 with SMTP id z2mr660355nza; Wed, 12 Jul 2006 03:23:01 -0700 (PDT) Received: from IBMD2594A07A1F ( [211.167.39.49]) by mx.gmail.com with ESMTP id 7sm324198nzo.2006.07.12.03.22.56; Wed, 12 Jul 2006 03:23:01 -0700 (PDT) Message-ID: <011301c6a59d$237cae60$a92ca00a@IBMD2594A07A1F> From: "Yan \(Josh\) ZHANG" To: , , , Date: Wed, 12 Jul 2006 18:22:50 +0800 Organization: Simula MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: meiyang , Si Qing Zheng , "Jun Zheng \(QC\)" Subject: [manet] [CFP] Special Session "Wireless Mesh Networks" in PDCS 2006 (Final extension: 1, August) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Yan \(Josh\) ZHANG" List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: manet-bounces@ietf.org We apologize in advance if you receive multiple copies of this CFP ================================================================= Special Session "Wireless Mesh Networks" in the 18th IASTED International Conference on PARALLEL AND DISTRIBUTED COMPUTING AND SYSTEMS ~ PDCS 2006 ~ November 13-15, 2006; Dallas, Texas, USA http://www.iasted.org/conferences/2006/Dallas/pdcs-specsess1.htm Scope ===== Wireless Mesh Networks (WMN) is emerging as a new technology extending and converging the future generation wireless networks. Standard organizations are actively calling for specifications for mesh networking, e.g. IEEE 802.11, IEEE 802.15, IEEE 802.16 and IEEE 802.20. WMN is characterized by dynamic self-organization, self-configuration and self-healing to enable flexible integration, secure communications, easy maintenance, high scalability and reliable services. To achieve these goals, great efforts are ongoing in both academy and industry communities. A special session on Wireless Mesh Networks will be organized at the PDCS2006 conference. This session constitutes a unique forum to present the latest research results by international researchers and developers. Original contributions are solicited, related to all areas in wireless mesh networking. Topics of interest include, but are not limited to: ==================================================== Mesh networking for Ad hoc network, Wireless PAN, LAN, MAN and WAN Mesh networking architecture in heterogeneous networks Multi-radio and multi-channel Wireless Mesh Networking QoS provisioning Multimedia services MAC protocol design Routing protocols Scheduling Load balancing Topology control Channel assignment algorithms Cross-layer optimization Physical layer techniques Security, authentication and privacy Fault tolerance, anomaly detection and error recovery schemes Standardization in emerging standards: IEEE 802.11, 802.15, 802.16 mesh, 802.20 mesh Testbed, prototype, practical system for WMN Submission Guidelines and Publications ======================================= Each should include authors names, affiliations, addresses, email addresses of all authors, and corresponding author and contact on the cover page. Each paper should include up to 5 keywords and an abstract of no more than 250 words. Please submit full paper, not exceeding 6 pages in length (single-space) in PS or PDF format for consideration, to the special session organizer by June 15, 2006 via email. Submission implies the willingness of at least one author to register and present the paper. All papers selected for this session by peer-review process will be published in the PDCS2006 conference proceedings through ACTA Press, USA. All final papers should be received by Sept. 1, 2006 and should adhere to the IASTED final paper formatting requirements outlined at http://www.iasted.org/formatting-final.htm. IMPORTANT DEADLINES =================== Paper received: August 1, 2006 Notification of acceptance: September 1, 2006 Final manuscript due: September 15, 2006 Registration Deadline: October 1, 2006 Special session organizers ========================== Dr. Yan ZHANG National Institute of Information and Communications Technology Email: yanzhang ieee.org Dr. Jun ZHENG Dept. of Computer Science Queens College New York, NY, USA Email: zheng cs.qc.edu _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 12 10:41:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0fuM-000124-TQ; Wed, 12 Jul 2006 10:41:46 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0fuL-00011t-V0 for manet@ietf.org; Wed, 12 Jul 2006 10:41:45 -0400 Received: from nz-out-0102.google.com ([64.233.162.199]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0fuJ-0008NV-MW for manet@ietf.org; Wed, 12 Jul 2006 10:41:45 -0400 Received: by nz-out-0102.google.com with SMTP id 16so138047nzp for ; Wed, 12 Jul 2006 07:41:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:content-transfer-encoding:message-id:content-type:to:from:subject:date:x-mailer; b=edxPaSJBjqvyU60zU+7xqIU+NoCgvq0vYHbjAAgkElUPr9l13e/DYdX3804SbAo1MQPCUh0qMKv4bjiROVC6kxKG70UZ1d96y9nYJ++c8xb06JGwLajvffOBcpphVh9UeKhxxDGAZVx01cyn5pniH4Bf3X6T2Qc6f43klLeK2vg= Received: by 10.64.142.10 with SMTP id p10mr709889qbd; Wed, 12 Jul 2006 07:41:24 -0700 (PDT) Received: from ?132.219.12.241? ( [132.219.12.241]) by mx.gmail.com with ESMTP id e17sm462887qbe.2006.07.12.07.41.22; Wed, 12 Jul 2006 07:41:23 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: manet , 6lowpan <6lowpan@ietf.org> From: Ian Chakeres Date: Wed, 12 Jul 2006 10:41:06 -0700 X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: Subject: [manet] Reminder: MANET July 13th 1pm Rm 515 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: , Errors-To: manet-bounces@ietf.org Just a reminder that the MANET meeting will be tomorrow at 1pm. Please review the WG documents and be prepared to discuss them. http://www.ietf.org/internet-drafts/draft-ietf-manet-packetbb-01.txt http://www.ietf.org/internet-drafts/draft-ietf-manet-nhdp-00.txt http://www.ietf.org/internet-drafts/draft-ietf-manet-dymo-05.txt http://www.ietf.org/internet-drafts/draft-ietf-manet-olsrv2-02.txt http://www.ietf.org/internet-drafts/draft-ietf-manet-smf-02.txt Ian Chakeres The agenda and presentations will be available at https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=66 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Jul 13 04:37:52 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0whN-00059E-49; Thu, 13 Jul 2006 04:37:29 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0whL-000591-Gy for manet@ietf.org; Thu, 13 Jul 2006 04:37:27 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0wLf-0007xP-Aa for manet@ietf.org; Thu, 13 Jul 2006 04:15:03 -0400 Received: from nz-out-0102.google.com ([64.233.162.199]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G0wGJ-0000BS-20 for manet@ietf.org; Thu, 13 Jul 2006 04:09:34 -0400 Received: by nz-out-0102.google.com with SMTP id x7so44855nzc for ; Thu, 13 Jul 2006 01:09:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:reply-to:from:to:cc:subject:date:organization:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole:sender; b=KLLKBfSbrkBYl/AAOI/X4fte7HgpQvSn5P75RPAlHP/w1GjLRuXwlbIz2Nswjl0+sp9MXMhSQNcVz6S4WI0UNnsAL8PUyyUV+iM+YeXwuIqnoYfah/ImpfQp35RDr7MoHTGGN95pdN6caiyjmAtkxgJqUAKvHRTtcscsQWrCqUw= Received: by 10.36.58.12 with SMTP id g12mr817318nza; Thu, 13 Jul 2006 01:09:29 -0700 (PDT) Received: from IBMD2594A07A1F ( [211.167.39.49]) by mx.gmail.com with ESMTP id 7sm916963nzo.2006.07.13.01.09.26; Thu, 13 Jul 2006 01:09:29 -0700 (PDT) Message-ID: <04cd01c6a653$a70273d0$a92ca00a@IBMD2594A07A1F> From: "Yan \(Josh\) ZHANG" To: , , , Date: Thu, 13 Jul 2006 16:09:19 +0800 Organization: Simula MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Score: -0.3 (/) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 Cc: Mieso Denko , "Laurence T. Yang" , Jian.J.Ma@nokia.com, Agustinus Borgy Waluyo Subject: [manet] [CFP] The Second IEEE International Symposium on Pervasive Computing and Ad Hoc Communications (PCAC-07) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Yan \(Josh\) ZHANG" List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: manet-bounces@ietf.org This message is cross-posted to several lists. Apologies for any duplicate postings. CALL FOR PAPERS =================================================================== The Second IEEE International Symposium on Pervasive Computing and Ad Hoc Communications (PCAC-07) to be held in conjunction with The IEEE 21th International Conference on Advanced Information Networking and Applications (AINA-07),Niagara Falls, Canada, May 21-23, 2007 ==================================================================== Aims and Scopes --------------- Pervasive computing has emerged as a new computing and communication environment with the aim of providing services anytime and anywhere for everyone. To facilitate resource sharing and support group communications, pervasive computing devices should be able to support ad hoc communications and networking. With ad hoc communications, seamless and transparent access to services and applications can be achieved while providing mechanisms for establishing spontaneous and interactive networking among communicating entities. Despite considerable progress in mobile computing and wireless communication technologies, new user demands and emerging applications introduce challenges in several areas including security, privacy, processing, auto configuration, scalability, software infrastructure, communication models and networking infrastructure. To support flexibility and unlimited mobility, services and applications should adapt to heterogeneous networking environment supporting multihop communication in hybrid wired/wireless environment. This symposium will bring together researchers and practitioners from industry and academia to present their current research results and discuss future trends in pervasive computing and ad hoc communications. Topics of Interest ----------------- Topics of interest include, but are not limited to: - Pervasive computing architectures - Wearable computers - Smart devices and smart spaces - Location-dependent and personalized applications - Service discovery mechanisms - Agent technologies - Mobility management - Sensors and actuators - Resource management - Embedded systems - Device and service interaction - Location-aware services - Middleware for pervasive computing - Middleware fro ad hoc computing - Hardware, OS and convergence issues - Security and privacy issues for pervasive computing systems - Positioning and tracking technologies - Identification and authentication technologies - Social Issues and Implications of pervasive computing - Data management infrastructure and algorithms - Caching and prefetching strategies - Resource discovery - Ad hoc communication and networking - Group communication and management - Ad hoc computing - User interfaces and interaction models - Prototyping and performance evaluation - Personal Area networks - Integration of wired and wireless networks - Enabling technologies such as Bluetooth, 802.11, 802.15, 802.16, and 802.20 - Context based and implicit computing - Ad hoc networking protocols and service discovery - Wireless Mesh Network Submissions and Proceedings ------------------------------ The manuscript should follow IEEE two-column format with single-spaced, ten-point font in the text. The maximum manuscript length is eight (8) pages. Submissions will be judged on correctness, originality,technical strength, significance and quality of presentation. The CD proceedings of this symposium will be published by IEEE Computer Society Press and available online through IEEE Xplore. Outstanding papers will be considered for a Special Issue in Journal of Ubiquitous Computing and Intelligence (JUCI) (http://www.aspbs.com/juci.html). PCAC-07 Submission System: http://pcac07.ehpclab.org/ Important Dates --------------- Submission Deadline: Nov. 22, 2006 Authors Notification: Jan. 22, 2007 Authors Registration: Jan. 31, 2007 Final Manuscript Due: Feb. 19, 2007 Organising Committee ----------------------- General Co-Chairs: Mieso Denko, University of Guelph, Canada Jian Ma, Nokia, China Steering Chair: Laurence T. Yang, St. Francis Xavier University, Canada Program Co-Chairs: Agustinus Borgy Waluyo, Monash University, Australia Yan Zhang, Simula Research Laboratory, Norway Program Committee ------------------- See PCAC-07 website* * http://beast.csse.monash.edu.au/~borgy/PCAC-07/ _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Jul 13 06:14:04 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0yCc-0004uY-Mx; Thu, 13 Jul 2006 06:13:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0yCb-0004t7-6i for manet@ietf.org; Thu, 13 Jul 2006 06:13:49 -0400 Received: from sfilter.italway.it ([83.142.230.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0y0I-00086f-Ar for manet@ietf.org; Thu, 13 Jul 2006 06:01:07 -0400 Received: from localhost ([127.0.0.1]) by sfilter.italway.it for manet@ietf.org; Thu, 13 Jul 2006 12:01:01 +0200 Received: from localhost ([127.0.0.1]) by filter.italway.it for manet@ietf.org; Thu, 13 Jul 2006 12:00:56 +0200 Received: from ([127.0.0.1]) with MailEnable ESMTP; Thu, 13 Jul 2006 12:00:55 +0200 Received: (qmail 31293 invoked from network); 13 Jul 2006 10:13:05 -0000 Received: from unknown (HELO ?192.168.9.217?) (nicscal@213.21.183.194) by 80.17.149.5 with SMTP; 13 Jul 2006 10:13:05 -0000 Message-ID: <44B619D6.6030109@iit.cnr.it> Date: Thu, 13 Jul 2006 12:00:54 +0200 From: Nicola Scalabrino User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: sigmobile-l@acm.uiuc.edu, manet@ietf.org, tccc@cs.columbia.edu X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Cc: Subject: [manet] WiMeshNets 2006: Call for Participation and Workshop Program 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: , Errors-To: manet-bounces@ietf.org ======================================== Apologies if you receive this more than once. ======================================== CALL FOR PARTICIPATION First International Workshop on "Wireless mesh: moving towards applications" (WIMESHNETS 2006) August 10th 20006, Waterloo, CAN, http://www.wimeshnets.org/ Sponsored by ICST, Create-Net and EU (IST-FET). In conjunction with Qshine 2006. PROGRAM: 8:45 Welcome 09:00 Keynote by Victor Bahl, Microsoft Research 10:00 Coffee break 10:30 Session I: Internet access and Performance Evaluation - Hassnaa Moustafa, Usman Javaid, Tinku Mohamed Rasheed, Sidi-Mohammed Senouci, Djamal-Eddine Meddour (France Telekom, FR): A Panorama on Wireless Mesh Networks: Architectures, Applications and Technical Challenges (Invited Paper) - Kamran Jamshaid, Lily Li and Paul A.S. Ward (University of Waterloo, CAN): Gateway Control of Wireless Mesh Networks - Wei Ji-bo, Wu Yu, Xi Yong, Huang Qing-yan (National University of Defense Technology, China): Implementing a High Throughput Access to IEEE 802.11 Wireless Mesh Networks - Marisa Catalan, Josep Paradells, Carles Gomez, Anna Calveras, Mireia Marcet (UPC, Spain), Javier Rubio, Daniel Almodovar (Vodafone, Spain): Extending Wireless Mesh Networks over UMTS: A proxy-based approach 12:10 Lunch 13:50 Session II: Routing and Channel Assignment - Francisco J. Ros, Pedro M. Ruiz (University of Murcia, Spain): Low Overhead Architecture for Infrastructure-based Wireless Mesh Networks (Invited Paper) - Di-Wei Huang, Phone Lin (National Taiwan University, Taiwan), Chai-Hien Gan (National Chiao-Tung University, Taiwan), Jeu-Yih Jeng (Chunghwa Telecom, Taiwan): A Mobility Management Mechanism using Location Cache for Wireless Mesh Network - Enzo Baccarelli, Mauro Biagi, Nicola Cordeschi, Cristian Pelizzoni (University of Rome, Italy): Fast Downloading of Large Files via Multi-Channel Wireless Mesh Networks - Timo Vanhatupa , Marko Hännikäinen , Timo D. Hämäläinen (Tampere University of Technology, Finland): Optimization of Mesh WLAN Channel Assignment with a Configurable Genetic Algorithm 15:30 Coffee break 16:00 Session III: Experimental Platforms and Applications - Angelo Annunziata, Mauro Oliviero, Giuseppe Scotti, Alessandro Trifiletti (University of Rome "La Sapienza"): A Low Cost, Low Power Wireless Sensor Network Implementing Pulse Coupled Oscillators Based Synchronization Strategies (Invited paper) - Antonio Capone, Stefano Napoli, Alberto Pollastro (Politecnico of Milan): MobiMESH: An Experimental Platform for Wireless MESH Networks with Mobility Support - Stefan Bouckaert (Ghent University, Belgium), Johan Bergs (University of Antwerp, Belgium), Dries Naudts (Ghent University, Belgium) , John Baekelmans, Erik De Kegel (Cisco Systems, Belgium), Nik Van den Wijngaert, Chris Blondia (University of Antwerp, Belgium), Ingrid Moerman, Piet Demeester (Ghent University, Belgium): A Mobile Crisis Management System for Emergency Services: from Concept to Field Test - Johnathan Ishmael, Nicholas Race (Lancaster University, UK): Routing challenges: Peer to Peer Applications on a Community Mesh Network 17:40 Workshop Closing COMMITTEES: Workshop Chair: Giovanni Iacovoni, Create-Net, Italy Technical Program Chair: Andreas J. Kassler, University of Karlstad, Sweden Publicity Chair: Nicola Scalabrino, Create-Net, Italy _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Sat Jul 15 23:23:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1xDZ-0001Vd-6W; Sat, 15 Jul 2006 23:22:53 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1xDX-0001TY-OO for manet@ietf.org; Sat, 15 Jul 2006 23:22:51 -0400 Received: from web15608.mail.cnb.yahoo.com ([202.165.102.62]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G1xDU-0008Bb-SX for manet@ietf.org; Sat, 15 Jul 2006 23:22:51 -0400 Received: (qmail 79665 invoked by uid 60001); 16 Jul 2006 03:22:44 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.cn; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=i6zJsIeDwJ6fVkhUXD3zhceR3nfU4VWKaT+I7UEO5cWUoa6rNpar+ZRDGweyEqNOOsAADt/ljblGoFXcAoNEIc01YH05SIX2sHrncDVZ+UfK1Tf16he5K0XJzt5IBCvIBST52QCSAKVbzHw3l5Q2dGNNAuDj5g0s0FN9ajxxIdA= ; Message-ID: <20060716032244.79663.qmail@web15608.mail.cnb.yahoo.com> Received: from [221.2.225.133] by web15608.mail.cnb.yahoo.com via HTTP; Sun, 16 Jul 2006 11:22:44 CST Date: Sun, 16 Jul 2006 11:22:44 +0800 (CST) From: lin chen To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.6 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Subject: [manet] If I can find the scource codes of CDS algorithms? 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="===============0370092622==" Errors-To: manet-bounces@ietf.org --===============0370092622== Content-Type: multipart/alternative; boundary="0-462076353-1153020164=:78650" Content-Transfer-Encoding: 8bit --0-462076353-1153020164=:78650 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit Hi, Recently I'm interested in caculating CDS to construct backbone of MANET.I want to analyze them based on simulation.I've read lots of papers,only to find the basic methods of CDS algorithms.I wonder if I can find the source codes of the typical algorithms,such as Wu & Li's pruning based CDS algorithm,or must I realize the algotithms myself? I'm anxious for answers. best regards, Chen Lin --------------------------------- ÑÅ»¢Ãâ·ÑÓÊÏä-3.5GÈÝÁ¿£¬20M¸½¼þ --0-462076353-1153020164=:78650 Content-Type: text/html; charset=gb2312 Content-Transfer-Encoding: 8bit
Hi,
  Recently I'm interested in caculating CDS to construct backbone of MANET.I want to analyze them based on simulation.I've read lots of papers,only to find the basic methods of CDS algorithms.I wonder if I can find the source codes of the typical algorithms,such as Wu & Li's pruning based CDS algorithm,or must I realize the algotithms myself? I'm anxious for answers.
 
 
best regards,
Chen Lin

ÑÅ»¢Ãâ·ÑÓÊÏä-3.5GÈÝÁ¿£¬20M¸½¼þ --0-462076353-1153020164=:78650-- --===============0370092622== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0370092622==-- From manet-bounces@ietf.org Mon Jul 17 11:05:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2Uek-0003IV-RM; Mon, 17 Jul 2006 11:05:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2Uej-0003IF-Ja for manet@ietf.org; Mon, 17 Jul 2006 11:05:09 -0400 Received: from slb-smtpout-01.boeing.com ([130.76.64.48] helo=slb-smtpout-01.ns.cs.boeing.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2Ueh-0004fU-94 for manet@ietf.org; Mon, 17 Jul 2006 11:05:09 -0400 Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with ESMTP id k6HF4jJ1022796; Mon, 17 Jul 2006 08:04:45 -0700 (PDT) Received: from XCH-NWBH-11.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 k6HF50320322; Mon, 17 Jul 2006 10:05:00 -0500 (CDT) Received: from XCH-NW-5V2.nw.nos.boeing.com ([130.247.55.45]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 17 Jul 2006 08:04:52 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [manet] If I can find the scource codes of CDS algorithms? Date: Mon, 17 Jul 2006 08:04:51 -0700 Message-ID: <08590A72DC26A54B85632FF97C2C22DA019ED277@XCH-NW-5V2.nw.nos.boeing.com> In-Reply-To: <20060716032244.79663.qmail@web15608.mail.cnb.yahoo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [manet] If I can find the scource codes of CDS algorithms? Thread-Index: AcaohzvW+d4lNoqmQXmYOxXe9RAF4ABKn+bQ From: "Spagnolo, Phillip A" To: "lin chen" , X-OriginalArrivalTime: 17 Jul 2006 15:04:52.0141 (UTC) FILETIME=[5AED45D0:01C6A9B2] X-Spam-Score: 0.0 (/) X-Scan-Signature: a8a20a483a84f747e56475e290ee868e Cc: 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="===============0036606313==" Errors-To: manet-bounces@ietf.org This is a multi-part message in MIME format. --===============0036606313== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6A9B2.5ACFFD23" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6A9B2.5ACFFD23 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Check out for some = source code in the OSPF MANET work. See ospf6_mdr.c after patching the = quagga source. =20 Sincerely, Phil ________________________________ From: lin chen [mailto:chenlin_83@yahoo.com.cn]=20 Sent: Saturday, July 15, 2006 8:23 PM To: manet@ietf.org Subject: [manet] If I can find the scource codes of CDS algorithms? =09 =09 Hi, Recently I'm interested in caculating CDS to construct backbone of = MANET.I want to analyze them based on simulation.I've read lots of = papers,only to find the basic methods of CDS algorithms.I wonder if I = can find the source codes of the typical algorithms,such as Wu & Li's = pruning based CDS algorithm,or must I realize the algotithms myself? I'm = anxious for answers. =20 =20 best regards, Chen Lin =09 ________________________________ = =D1=C5=BB=A2=C3=E2=B7=D1=D3=CA=CF=E4-3.5G=C8=DD=C1=BF=A3=AC20M=B8=BD=BC=FE= =20 ------_=_NextPart_001_01C6A9B2.5ACFFD23 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
Check out=20 <http://hipserver.mct.phantomworks.org/ietf/ospf/> for some source = code in=20 the OSPF MANET work.  See ospf6_mdr.c after patching the quagga=20 source.
 
Sincerely,
Phil

From: lin chen=20 [mailto:chenlin_83@yahoo.com.cn]
Sent: Saturday, July 15, = 2006 8:23=20 PM
To: manet@ietf.org
Subject: [manet] If I can = find the=20 scource codes of CDS algorithms?

Hi,
  Recently I'm interested in caculating CDS = to=20 construct backbone of MANET.I want to analyze them based on = simulation.I've=20 read lots of papers,only to find the basic methods of CDS algorithms.I = wonder=20 if I can find the source codes of the typical algorithms,such as Wu = & Li's=20 pruning based CDS algorithm,or must I realize the=20 algotithms myself? I'm anxious for answers.
 
 
best regards,
Chen Lin

=D1=C5=BB=A2=C3=E2=B7=D1=D3=CA=CF=E4-3.5G=C8=DD=C1=BF=A3=AC= 20M=B8=BD=BC=FE ------_=_NextPart_001_01C6A9B2.5ACFFD23-- --===============0036606313== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0036606313==-- From manet-bounces@ietf.org Mon Jul 17 11:31:45 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2V4N-00016E-B0; Mon, 17 Jul 2006 11:31:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2V4M-000169-0j for manet@ietf.org; Mon, 17 Jul 2006 11:31:38 -0400 Received: from nz-out-0102.google.com ([64.233.162.202]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2V4I-0006uW-FP for manet@ietf.org; Mon, 17 Jul 2006 11:31:37 -0400 Received: by nz-out-0102.google.com with SMTP id 16so707278nzp for ; Mon, 17 Jul 2006 08:31:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:mime-version:content-type:x-google-sender-auth; b=YZ1fAxXSCzUyaImexUw56g2nC8YXSGw4Gt4wrnbLZJd0Q1X4swz8n+SOERSqejH40elPI/725x+0YfxgKL4crcYSmtZEyeiblz9oIdBA2fuKH6kYtSQW7DfuXiJ5P+O16HGaTDrDJV7q1hgIBdDYBZr5XPGOJwv7MMd2J3O6gkA= Received: by 10.65.182.14 with SMTP id j14mr1464322qbp; Mon, 17 Jul 2006 08:31:33 -0700 (PDT) Received: by 10.65.132.4 with HTTP; Mon, 17 Jul 2006 08:31:03 -0700 (PDT) Message-ID: <83d5521f0607170831x1a173167ha54331a9d5fbed81@mail.gmail.com> Date: Mon, 17 Jul 2006 11:31:03 -0400 From: "Zheng Jun" To: itc@comsoc.org, manet@ietf.org, multicomm@comsoc.org, tccc@cs.columbia.edu MIME-Version: 1.0 X-Google-Sender-Auth: 50db1d80a72c8a58 X-Spam-Score: 0.5 (/) X-Scan-Signature: bd8a74b81c71f965ca7918b90d1c49c0 Cc: Miao Ma Subject: [manet] Call for book chapter: handbook of research on wireless security 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="===============0767507940==" Errors-To: manet-bounces@ietf.org --===============0767507940== Content-Type: multipart/alternative; boundary="----=_Part_42471_29415259.1153150263786" ------=_Part_42471_29415259.1153150263786 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline We apologize in advance if you receive multiple copies of this CFP ================================================================= CALL FOR BOOK CHAPTER Title: Handbook of Research on Wireless Security Publisher: Idea Group Reference, USA (http://www.idea-group-ref.com) Further information: http://yanzhangsg.googlepages.com/WirelessSecurityCFP.html Background & Goal ================= Security, defined as ensuring protected communication among terminals, networks and services, is one of the most significant components in wireless systems. Both architectures and protocols on security have been extensively studied in academics and industries. This handbook aims to provide a comprehensive guide on security-related subjects in the wireless communication field, and it will be a valuable reference for students, instructors, researchers, engineers and strategists in this field. Coverage ======== Wireless security is explored with various challenges in diverse environments and standards, such as authentication, encryption, key distribution and management, etc. This handbook will feature chapters (5,000-7,500 words) and provide an in-depth description of terminologies and concepts related to security in various wireless systems. This handbook will be written by the leading experts in the field from both academics and industries. Recommended Topics include, but are not limited to: =================================================== Security in mobile ad hoc networks Security in peer-to-peer networks Security in Wireless Mesh Networking Security in Wireless Sensor Network Security in Wireless Personal Area Network (WPAN) Security in Wireless Local Area Network (WLAN) Security in Wireless Metropolitan Area Network (WMAN) Security in Wireless Wide Area Network (WAN) Security in GSM, GPRS Security in UMTS, CDMA2000, TD-SCDMA Security in B3G, 4G Security in Bluetooth and WiMAX Security in IEEE 802.x families Security in wireless multimedia systems Security architecture in heterogeneous networks Secure PHY/MAC/routing protocols Secure group communication/multicast Secure cross-layer protocols Secure location-based service Trustworthy networks; authentication, privacy and security models Fault tolerance, anomaly detection and error recovery schemes Security and privacy protection Vulnerability analysis and countermeasures Tradeoff between performance and security Authentication, authorization and access control Data confidentiality and integrity Encryption and decryption Key distribution and management Identity management Intrusion and anomaly detection Fraudulent usage Secure billing Secure self-configuration Secure service discovery Testbed, prototype, practical system and case studies Submission Guidelines ===================== Chapter proposals should clearly outline the purpose and organization of the chapter. Upon acceptance of chapter proposals, authors will be sent chapter guidelines. Drafts of chapters must be between 5,000-7,500 words and include 7-10 related terms and their appropriate definitions. All chapters will undergo a double-blind peer review. This book is tentatively scheduled for publishing by Idea Group Reference (http://www.idea-group.com/reference/), an imprint of Idea Group Inc. in early 2008. Important Dates =============== 31 July, 2006: Proposal due 31 August, 2006: Notification of proposal acceptance 15 December, 2006: Draft of chapter due 30 April, 2007: Notification of chapter acceptance Early of 2008: Publication of handbook Contact ======== Inquiries and submissions can be forwarded to the editors: Dr. Yan ZHANG National Institute of Information and Communications Technology Email: yanzhang ieee.org Dr. Jun ZHENG Queens College, City University of New York, USA Email: zheng cs.qc.edu Dr. Miao MA Institute of Infocomm Research, Singapore Email: miaom i2r.a-star.edu.sg ------=_Part_42471_29415259.1153150263786 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline We apologize in advance if you receive multiple copies of this CFP
=================================================================

CALL FOR BOOK CHAPTER

Title: Handbook of Research on Wireless Security
Publisher: Idea Group Reference, USA (http://www.idea-group-ref.com )
Further information:
http://yanzhangsg.googlepages.com/WirelessSecurityCFP.html

Background & Goal
=================
Security, defined as ensuring protected communication among terminals,
networks and services, is one of the most significant components in wireless
systems. Both architectures and protocols on security have been extensively
studied in academics and industries. This handbook aims to provide a
comprehensive guide on security-related subjects in the wireless
communication field, and it will be a valuable reference for students,
instructors, researchers, engineers and strategists in this field.

Coverage
========
Wireless security is explored with various challenges in diverse
environments and standards, such as authentication, encryption, key
distribution and management, etc. This handbook will feature chapters
(5,000-7,500 words) and provide an in-depth description of terminologies and
concepts related to security in various wireless systems. This handbook will
be written by the leading experts in the field from both academics and
industries.

Recommended Topics include, but are not limited to:
===================================================
Security in mobile ad hoc networks
Security in peer-to-peer networks
Security in Wireless Mesh Networking
Security in Wireless Sensor Network
Security in Wireless Personal Area Network (WPAN)
Security in Wireless Local Area Network (WLAN)
Security in Wireless Metropolitan Area Network (WMAN)
Security in Wireless Wide Area Network (WAN)
Security in GSM, GPRS
Security in UMTS, CDMA2000, TD-SCDMA
Security in B3G, 4G
Security in Bluetooth and WiMAX
Security in IEEE 802.x families
Security in wireless multimedia systems
Security architecture in heterogeneous networks
Secure PHY/MAC/routing protocols
Secure group communication/multicast
Secure cross-layer protocols
Secure location-based service
Trustworthy networks; authentication, privacy and security models
Fault tolerance, anomaly detection and error recovery schemes
Security and privacy protection
Vulnerability analysis and countermeasures
Tradeoff between performance and security
Authentication, authorization and access control
Data confidentiality and integrity
Encryption and decryption
Key distribution and management
Identity management
Intrusion and anomaly detection
Fraudulent usage
Secure billing
Secure self-configuration
Secure service discovery
Testbed, prototype, practical system and case studies

Submission Guidelines
=====================
Chapter proposals should clearly outline the purpose and organization of the
chapter. Upon acceptance of chapter proposals, authors will be sent chapter
guidelines. Drafts of chapters must be between 5,000-7,500 words and include
7-10 related terms and their appropriate definitions. All chapters will
undergo a double-blind peer review. This book is tentatively scheduled for
publishing by Idea Group Reference (http://www.idea-group.com/reference/ ),
an imprint of Idea Group Inc. in early 2008.

Important Dates
===============
31 July, 2006: Proposal due
31 August, 2006: Notification of proposal acceptance
15 December, 2006: Draft of chapter due
30 April, 2007: Notification of chapter acceptance
Early of 2008: Publication of handbook

Contact
========
Inquiries and submissions can be forwarded to the editors:

Dr. Yan ZHANG
National Institute of Information and Communications Technology
Email: yanzhang <AT> ieee.org

Dr. Jun ZHENG
Queens College, City University of New York, USA
Email: zheng <AT> cs.qc.edu

Dr. Miao MA
Institute of Infocomm Research, Singapore
Email: miaom <AT> i2r.a-star.edu.sg
------=_Part_42471_29415259.1153150263786-- --===============0767507940== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0767507940==-- From manet-bounces@ietf.org Mon Jul 17 11:53:14 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2VPB-0003r1-3U; Mon, 17 Jul 2006 11:53:09 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2VP9-0003qv-Ev for manet@ietf.org; Mon, 17 Jul 2006 11:53:07 -0400 Received: from smtp010.mail.ukl.yahoo.com ([217.12.11.79]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G2VP6-0001k3-PH for manet@ietf.org; Mon, 17 Jul 2006 11:53:07 -0400 Received: (qmail 49795 invoked from network); 17 Jul 2006 15:46:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=3LNY6twxoifAGHNCe/1O62qXelQzLKKSLeqSshY5bkWgV2mURD/rwpTIj/ph3E5oJawJoETE7Xs3kpmEWYylnUbmfCMDg9dMghovIN8Jw4KNGJSmOM2GZrgGHjAMWB85T0Id0p/OT4YmjIQ3zD8+4IEdQYOqpvQnIfjzcYyTDIg= ; Received: from unknown (HELO ?134.214.144.170?) (fabrice?theoleyre?listes@134.214.144.170 with plain) by smtp010.mail.ukl.yahoo.com with SMTP; 17 Jul 2006 15:46:24 -0000 Message-ID: <44BBB0C9.7060905@yahoo.fr> Date: Mon, 17 Jul 2006 17:46:17 +0200 From: Fabrice Theoleyre User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: lin chen Subject: Re: [manet] If I can find the scource codes of CDS algorithms? References: <20060716032244.79663.qmail@web15608.mail.cnb.yahoo.com> In-Reply-To: <20060716032244.79663.qmail@web15608.mail.cnb.yahoo.com> Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a 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: , Errors-To: manet-bounces@ietf.org You can see http://gforge.inria.fr/plugins/scmcvs/cvsweb.php/?cvsroot=topo-adhoc for some source codes of different CDS algorithms for OPNET Modeler (and particularly for the Wu & Li pruning algorithm). Sincerely, Fabrice Theoleyre lin chen a ¨¦crit : > Hi, > Recently I'm interested in caculating CDS to construct backbone of > MANET.I want to analyze them based on simulation.I've read lots of > papers,only to find the basic methods of CDS algorithms.I wonder if I > can find the source codes of the typical algorithms,such as Wu & Li's > pruning based CDS algorithm,or must I realize the algotithms myself? > I'm anxious for answers. > best regards, > Chen Lin ___________________________________________________________________________ Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire. http://fr.mail.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 19 14:09:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3GUB-0005QV-24; Wed, 19 Jul 2006 14:09:27 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3GU9-0005QP-Cv for manet@ietf.org; Wed, 19 Jul 2006 14:09:25 -0400 Received: from bos-mail-smail3.bos.lycos.com ([209.202.208.43] helo=smail1.lycosmail.lycos.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3GU8-0003yi-2h for manet@ietf.org; Wed, 19 Jul 2006 14:09:25 -0400 Received: from bos-mail-wwl14.lycosmail.com (bos-mail-wwl14b.bos.lycos.com [10.124.64.94]) by bos-mail-smail3.lycosmail.com (8.13.6/8.9.1) with ESMTP id k6JI5eO9009946; Wed, 19 Jul 2006 14:05:40 -0400 Received: (from hanadmin@localhost) by bos-mail-wwl14.lycosmail.com (8.12.9/8.9.1) id k6JI9sEJ027889 for ; Thu, 20 Jul 2006 03:09:54 +0900 X-Originating-IP: [130.85.169.167] From: "chauhansweety" Organization: Lycos. Inc. To: , X-Mailer: Daum Web Mailer 1.1 Date: Wed, 19 Jul 2006 14:09:38 -0400 (EDT) Message-Id: <20060719140946.HM.00000000000008V@chauhansweety.bos-mail-wwl14.bos.lycos.com.lycos.com> MIME-Version: 1.0 X-Hanmail-Attr: fc=1 X-Spam-Score: 3.4 (+++) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Cc: mehrana.at.uow.edu.au@lycos.com Subject: [manet] ZRP implementation 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="===============0324201452==" Errors-To: manet-bounces@ietf.org --===============0324201452== Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hi,

I am using ZRP GloMoSim implementation from Haas et al group.
http://people.ece.cornell.edu/~haas/wnl/wnlprojects.html

I have gone through ZRP implementation discussion on the group.
http://www1.ietf.org/mail-archive/web/manet/current/msg06851.html

I am getting following error while running 25 and 50 nodes simulations with zone radius = 2 and mobility = NONE.

glomosim: ../network/nwip.pc:1219: Assertion `FALSE' failed.
Aborted

Does anyone faced the same problem?
Any help would be highly appreciated.

Best Regards,
Sweety




Sweety Chauhan
Graduate Student
Department of Computer Science and Electrical Engg.
University of Maryland Baltimore County
Baltimore, MD- 21250
USA
--===============0324201452== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0324201452==-- From manet-bounces@ietf.org Thu Jul 20 10:41:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3ZiF-0003dO-KC; Thu, 20 Jul 2006 10:41:15 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3ZiC-0003b2-6D for manet@ietf.org; Thu, 20 Jul 2006 10:41:12 -0400 Received: from out4.smtp.messagingengine.com ([66.111.4.28]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3Zi9-0004hF-Mw for manet@ietf.org; Thu, 20 Jul 2006 10:41:12 -0400 Received: from frontend3.internal (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id D7784D909CC; Thu, 20 Jul 2006 10:41:08 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by frontend3.internal (MEProxy); Thu, 20 Jul 2006 10:41:11 -0400 X-Sasl-enc: VxuNvncJTxh0fWsWZ+k4F7shFo13K72wP7ZiVmxnVY0t 1153406470 Received: from [130.192.85.114] (unknown [130.192.85.114]) by mail.messagingengine.com (Postfix) with ESMTP id 7F09F2CDE; Thu, 20 Jul 2006 10:41:10 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed Message-Id: <39C1FFC6-481C-4CB9-8740-27754E3CECF0@cs.ucla.edu> Content-Transfer-Encoding: quoted-printable From: Giovanni Pau Date: Thu, 20 Jul 2006 16:41:04 +0200 To: manet@ietf.org X-Mailer: Apple Mail (2.752.2) X-Spam-Score: 0.5 (/) X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c Subject: [manet] IEEE NIME 2007 CFP (Deadline Approaching) 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: , Errors-To: manet-bounces@ietf.org CALL FOR PAPERS 3rd IEEE International Workshop on Networking Issues in Multimedia Entertainment (NIME'07) CCNC 2007 - Satellite Workshop January 11 2007, Las Vegas, Nevada, USA Sponsored by the IEEE Communications Society The growing availability of digital contents and the simultaneous cost reductions in storage, processing, and networking is driving the =20 growth of the entertainment technology. While in the past entertainment technology traditionally offered predominantly passive experiences, continual advances in network and computer technologies are providing tools for implementing greater interactivity and for enabling consumers to enjoy more exciting experiences, such as, for example, interactive digital TV, interactive theatre and orchestrated music and sound design. This phenomenon is pulling together an extremely diverse group of experts specializing in different technical areas, such as networking, computer graphics, artificial intelligence, games, animation, multimedia design, human-computer interaction, educational media and software engineering. Even though high-tech entertainment promotes interdisciplinary =20 fusion, yet only the ubiquity of wireless/wired communication is considered suitable for accepting the challenge of building a large interactive environment for the delivery of the maximum entertainment value to millions of consumers worldwide. In this respect, there is a great hope that the =20 wired and wireless may take over this complex scenario for fulfilling the consumer expectations. The third IEEE International Workshop on =20 Networking Issues in Multimedia Entertainment provides an open forum for =20 researchers, engineers and academia to exchange the latest technical information and research findings on next-generation networked multimedia concepts, technologies, systems, and applications for entertainment covering existing deployments, current developments and future evolution. Authors are solicited to submit complete unpublished papers in the following, =20= but not limited to, topic areas: Technologies for Entertainment: Architectures, Platforms and Protocols for Networked Games Internetworking, Vertical Roaming and Session Handoffs for Entertainment (Internet to WLAN, to 3G/BT/...) Home LANs, Body and Personal Area Networks for Entertainment Media and Device Adaptation Music and Movie Distribution Next Generation Wireless Technologies for Entertainment (IEEE802.11n, UWB and Beyond) Opportunistic Multi-hopping and Opportunistic Networks for Entertainment QoS and Security Support for Entertainment Resource and Service Discovery Technologies (P2P, LDAP, =85) Technologies for Networked In-Home/Car/Flight/Train Entertainment TV-Centric and Broadcast Networks for Entertainment Entertainment Applications: Agent-based Entertainment Augmented, Virtual and Mixed Reality Artificial Intelligence Evolutionary Entertainment Interactive Television and Theater Massive Multiplayer Games Mobile and Wireless Entertainment Networked Entertainment Networked Narrative and Digital Interactive Storytelling Networked Video, Music and Sound Design Pervasive Entertainment Personalized and User-Adapted Television Sport, News and Entertainment Virtual Technology and Virtual Environments for Entertainment Wearable Entertainment Wireless and Mobile Gaming Testbed and Performance Evaluation Guidelines for Submission Submitted papers must represent original material that is not currently under review in any other conference or journal, and has not been previously published. - Paper length should not exceed five-page technical paper manuscript. - Please see author information page for submission guidelines at CCNC=9207 website (http://www.ieee-ccnc.org). The paper should be used as the =20 basis for a 20-30 minute Workshop presentation. - Papers should be submitted in a .pdf or .ps format by selecting =20 CCNC'07 at the EDAS paper submission website (http://www.edas.info) and then selecting the workshop submission link. - A separate cover sheet should show the title of the paper, the =20 author(s) name(s) and affiliation(s), and the address (including e-mail, =20 telephone, and fax) to which the correspondence should be sent. - All accepted papers will be published in the conference proceedings. - At least one author of accepted papers is required to register at the =20= full registration rate. Important Dates August 10, 2006 Paper submission September 15, 2006 Author Notification October 10, 2006 Camera-ready Copy October 8, 2006 Author Registration Deadline January 11, 2007 Workshop date Co-Chairs Marco Roccetti (University of Bologna, Italy, roccetti@cs.unibo.it) Giovanni Pau (UCLA, USA, gpau@cs.ucla.edu) Abdennour El-Rhalibi (Liverpool John Moores University, UK, A.Elrhalibi@ljmu.ac.uk) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D "Opportunity is missed by most people because it is dressed in overalls and looks like work." (Thomas Alva Edison) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Giovanni Pau, PhD Research Scientist UCLA - Computer Science Department 3803A BH, Boelter Hall Los Angeles, 90095 CA Ph: (310) - 206-3212 Cell: (310) - 617-4728 Fax: (310)- 825-7578 http://www.cs.ucla.edu/~gpau _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Jul 20 11:16:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3aGU-00013H-Hu; Thu, 20 Jul 2006 11:16:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3aGS-00010q-Dk for manet@ietf.org; Thu, 20 Jul 2006 11:16:36 -0400 Received: from ug-out-1314.google.com ([66.249.92.168]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3aDa-0000oF-3N for manet@ietf.org; Thu, 20 Jul 2006 11:13:40 -0400 Received: by ug-out-1314.google.com with SMTP id m2so875764uge for ; Thu, 20 Jul 2006 08:13:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=LQjqgQw26oL2Rssy7Bb06OVmu/lc6M0FI7bQH5fAPCFMgVuj3IKWgyWtE5dhGgriKfrrtfkB1L19Y/U/k6PSw72IPjLn5cil3OIdz85GHcydzzG/W5Rj2uJcHvQ8eb29eDZNdKYVNinzklYI/MRZ2MrOchGFrpw8exuf9njb6tI= Received: by 10.78.116.19 with SMTP id o19mr469885huc; Thu, 20 Jul 2006 08:13:36 -0700 (PDT) Received: by 10.78.183.17 with HTTP; Thu, 20 Jul 2006 08:13:36 -0700 (PDT) Message-ID: Date: Thu, 20 Jul 2006 11:13:36 -0400 From: "Rob Bird" To: manet@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Google-Sender-Auth: db13f590cd8e1518 X-Spam-Score: 1.9 (+) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Subject: [manet] CFP: IEEE CI Defense 2007 - Honolulu 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: , Errors-To: manet-bounces@ietf.org I would like to encourage everyone to consider submitting papers to the First IEEE Symposium on Computational Intelligence for Defense Applications to be held April 1-5, 2007 in Honolulu, HI, USA. My apologies if you have received this via another list. Important Due Dates: Special Session Proposals: October 1, 2006 Paper Submissions: November 1, 2006 Notification of Acceptance: December 1, 2006 Camera-Ready Submission: January 1, 2007 The purpose of the conference is to present current and ongoing efforts in computational intelligence (e.g., Neural networks, Fuzzy systems, Evolutionary computation/algorithms, Swarm intelligence, and other emerging learning or optimization techniques) as applied to military and defense security problems. The military and security problems domains of interest for this session include, but are not limited to the following: =B7 Command and Control of Military Operations =B7 Intelligence Gathering and Exploitation =B7 Modeling and Simulation of Military Operations =B7 Advanced Computer Architectures for Military Operations =B7 Cyber Security =B7 Computational Cognitive Modeling =B7 Automatic Target Recognition =B7 Programs for Training =B7 Models for War Games =B7 Mine Detection =B7 Situation Assessment =B7 Logistics Support =B7 Design of military systems/subsystems =B7 Course of Action Generation =B7 Mission Planning and Execution =B7 Airspace Management and Deconfliction =B7 Resource Management =B7 Route/Sortie Planning =B7 Mission Weapon Pairing and Assignment =B7 Employment of Autonomous Vehicles Thank you for your attention. Rob - Rob Bird, Chief Technology Officer Red Lambda, Inc. "The Leaders in Distributed Network Intelligence" www.redlambda.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Thu Jul 20 15:18:00 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3e1s-00022L-RN; Thu, 20 Jul 2006 15:17:48 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3e0P-0000RT-Oz for manet@ietf.org; Thu, 20 Jul 2006 15:16:17 -0400 Received: from mailrelay.naist.jp ([163.221.82.75]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3dom-0005bB-RE for manet@ietf.org; Thu, 20 Jul 2006 15:04:19 -0400 Received: from mailpost.naist.jp (mailscan.naist.jp [163.221.82.70]) by mailrelay.naist.jp (Postfix) with ESMTP id D98241C33 for ; Fri, 21 Jul 2006 04:04:10 +0900 (JST) Received: from [127.0.0.1] (isb2-dhcp-170-213.naist.jp [163.221.170.213]) by mailpost.naist.jp (Postfix) with ESMTP id A8ECD1C12 for ; Fri, 21 Jul 2006 04:04:10 +0900 (JST) Message-ID: <44BFD3A8.1090202@is.naist.jp> Date: Fri, 21 Jul 2006 04:04:08 +0900 From: David Esteban User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: manet@ietf.org References: <20060719140946.HM.00000000000008V@chauhansweety.bos-mail-wwl14.bos.lycos.com.lycos.com> In-Reply-To: <20060719140946.HM.00000000000008V@chauhansweety.bos-mail-wwl14.bos.lycos.com.lycos.com> X-Spam-Score: 1.4 (+) X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9 Subject: [manet] Multimedia in Moblie IP 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: , Content-Type: multipart/mixed; boundary="===============1450007313==" Errors-To: manet-bounces@ietf.org This is a multi-part message in MIME format. --===============1450007313== Content-Type: multipart/related; boundary="------------090201060205040408050804" This is a multi-part message in MIME format. --------------090201060205040408050804 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear all,

I just ask for some help again, im loooking for some documents about Multimedia data trasmission in mobile IP environments. Can anyone recommend me any paper or documentation to get started?

Thanks in advance,
--
----------

=E3=82=A8 =E3=82=B9=E3=83=86=E3=83=90=E3=83=B3=E3=80=80=E3=82=A4=E3=83=8D=E3=82=B9=E3= =80=80=E3=83=80=E3=83=93=E3=83=89<esteban-d@is.naist.jp>=

=E5=A5=88= =E8=89=AF=E5=85=88=E7=AB=AF=E7=A7=91=E5=AD=A6=E6=8A=80=E8=A1=93=E5=A4=A7=E5= =AD=A6=E9=99=A2=E5=A4=A7=E5=AD=A6=E6=83=85=E5=A0=B1=E7=A7=91=E5=AD=A6=E3=82= =BB=E3=83=B3=E3=82=BF=E3=83=BC
http://inet-lab.naist.jp/~esteban-d/

= 3D"View

--------------090201060205040408050804 Content-Type: image/gif; name="btn_linkedin_120x30.gif" Content-Transfer-Encoding: base64 Content-ID: Content-Disposition: inline; filename="btn_linkedin_120x30.gif" R0lGODlheAAeAPcAAP////7+/vz8/Pn8/ff7/fr6+vX6/PT5+/j4+Pb29vT09O32+vD2+Ov1 +ez1+e30+Or1+er0+fLy8uzz9+n0+Ovz9+fz+OXz+Ozy9O/v7+rw8uXw9eLx9u3t7eDx9+Dv 9d/v9ePv9OLu8+Lu9N7u9Ovr693u9dvt9ODs8dns89ns9Nrs9Nfr89Xq8tTp8tvo7dPo8dbo 79Pp8dLo8c/o8d3k59Pm7dHn8NDn8M7l7s3k7cbk78nk7svi7Mri68Ti7sbi7sHh7cjg6sPh 7cff6cHf7L/f67/f7Mjc5MXd58Td57jf7cHb5cLb5b/c6L7c6Lzd67Pd7Lza5rLb6rXa6bXZ 6LLa6a/a6rPZ6KnY6q/X56/X5q3X6K3X57XU4azV5azV5qvV5qrU5anU5aXU5anT5KPU56fS 46vQ4KbR46XS5KLT5qnO3qjO3qTQ4prS5qPP4Z7Q46TN36PN357O4Z/N35TO46fK2J/M35vN 4JnN4p/K3JXM4ZXL4JvK3ZTK35fK34/L4ZvI2pHJ347J4JfH25DH3pDG3JPE2ZPE2InH34/E 2YzF3YzF3IjF3I/C14XE3I/B1o7B1ofD2oPE3IbB2YPA2oPA2YLA2YS+1n3A2n++132+2H69 132+14W603e92H671Hq71Xm813q61Xa51Ha403W403S41HG51Xy0znW1z3C31HW0z3G10XC0 0Gu102m00XCyzmyyz2mz0Wuyzmay0WSxz2muy2evzWWvzWSvzl+vzmauzGKrymGrynKnw1mr zFyoyFyox1mpyVipymukwmClxVSoylOnyU6kx0+ixE6ixUihxU2ewUigxEKdwkibv0ObwDya wDaWvjaVvESOsjCSu0GMsiqPuSSMtx6ItBiEsheCsBaBsBOBsCh4ow1+rSZ2oSZ1oAx7qgd6 qyBzoAd4qQZ4qQ12pgx0pB1unBtvnRtvnBttnBdsmwVwogRuoApmlwZilARhkwJhkwFgkwJg kgJdjwJcjwBcjwFcjwBcjgBbjgAAAAAAACH5BAQUAP8ALAAAAAB4AB4AAAj/AAE8AOauXz98 CBMqXMiwocOHECNKnEhx4TpgEwBUECfu05QlIEOKHEmypMmTKFOqXMlyZBdV7cZNMGbOTJab OHPq3Mmzp8+fQIMKHepzDTtj72S9Wcq0qdOnUKNKnUp1ahQPAwBo3cq16wAPUapCPfYuHyE7 aNOqXcu2rdu3cOO+vdK1rt2tV+SydYQwkN+/gAMLHky4sOHDhiHcXcwVAuLB+fIpmky5suXL mDNr3sx5M+PPWjtjjkyptOnTqFOrXs26tevWoD+/Vh1Zk+3buHPbjsMbUm4+NHb41o0bEu84 xJMn59MbN1cCXMhYiK1VufV9+0Bp3869u/aterpf/9BqxXt3PVvNq1dvQmv47Vx/aB9EHcD6 +9hT6d/Pv7/+rX/0d4JWWvjX3x9bGaigggMCEOB+XAWhXx/1LWghdrBkqOGGHGa4lSEcckJF GB12aMhWJaaY4gpagahhV0dQsUB9KtaInS045qjjjjhu1QiPQNrCCiOM5NjIVjgygsWSrNgy ChQqqDBGkzkyAoQKUFiSglY/5kgdByk4UFeQZOKIHS9opqnmmmhuNcmaLGi1BS9b5WGAVg14 wsskW/ESy50ADMFLHl0ZoCcvanBlQANavZkmV1qgyWekiDo6aFdsZsomdsF06umnoHa6FSag tqDVF8FsBahWEQSDyVbBmP8KQBHBXKLVB4B8cWutW0Ugq1akesoVGJ3aSmwwt4AKBlehNhsq dshEK+201Ea7VSfUuqBVGchsBUIndFzbyVbhAgBCtDxoRUu0RmiFSroA8BAtKtdOy5UY0W4C AL7RVtECKvNyVe3A1WKnzMEIJ6zwwVuRojAMWqWhzFa7HExCxKRsdYBWxTCslQwgU6DVIVuJ gvDFADiMMFdnHCwKAC0rU8nHK2+18M0LY9fMzjz37PPOAQR9is84BA1HM0EHwHPRAcBxStJJ H50M1FTDkbQpPN8gdM9Qu7FzKQB43YwbWs3AM1c/p/0zdtC07fbbcLctwNyvwK3D3HhAM7cA bt//LQAer+zttwC66C0AA3gkrjgxe7vi9gZ0v723AHW07Qrlbdcxdw5uTx7353FjN83opJdu +ugFpL7ILKzPMo0PqfsxTeoFkA57AX7UQvs0T6QewzMipJ7J6bc78cw0s9BeS+m04z568rJP 40fqPZDe/OnYn44dNdx37/333CMg/vjiU0OE+IVQM3735yNQSC/rM4OB+HOEMr4NckghxBzU 2C8+CkIgXy+8R770USMX7uNeIcQnhO6RD3wQBB92rkHBClrwghRMgAY3qMFrKEGDibjGBiv4 wQQk4hcjvEYiNuiLPXBQg0qgIBo4qIEZJuAXFuQgIijoiwTs8BqI0GAS/yrIQQwaEYPYyYYS l8jEJipRElCMIhSz0QooDiMbUVziKiIRCWFIg4uRUGI1wLiKbHyRCUxoQySWsURceIEJgpCG MLgoDSYq4I4KaMIjHsGGPO6xCXd8wR4fgUcFOPGQTtSHPrTByEY68pGQjKQkJ0nJSlJSApjM pCY3yUlMWjKS/ODHNkZJylKa8pSoTKUqV8nKVSIhA7CMpSxnSUsktBKVoewGN3bJy1768pfA DKYwh0lMYTqjA8hMpjKXyUxnFBOY/ZhHOr5BzWpa85rYzKY2t8nNbnIzGneoQQnGSc5ymrMG d4iGN7OpjnlYox7hiKc850nPetrznvjMpz73yUbPfurzHtYYgTzsAY9zlOOgCE2oQhfK0IY6 9KEQjahEJ7rQeNhDHiEAwAiwQQ+DePSjIA2pSEdK0pKa9KQoTelI6YGNjAYEADs= --------------090201060205040408050804-- --===============1450007313== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1450007313==-- From manet-bounces@ietf.org Thu Jul 20 15:18:07 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3e2B-0002oT-0e; Thu, 20 Jul 2006 15:18:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G3e0K-0000QU-Fj for manet@ietf.org; Thu, 20 Jul 2006 15:16:12 -0400 Received: from bos-mail-smail3.bos.lycos.com ([209.202.208.43] helo=smail1.lycosmail.lycos.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G3dvw-0005lG-DQ for manet@ietf.org; Thu, 20 Jul 2006 15:11:41 -0400 Received: from bos-mail-wwl14.lycosmail.com (bos-mail-wwl14b.bos.lycos.com [10.124.64.94]) by bos-mail-smail3.lycosmail.com (8.13.6/8.9.1) with ESMTP id k6KJ7hTv022009; Thu, 20 Jul 2006 15:07:43 -0400 Received: (from hanadmin@localhost) by bos-mail-wwl14.lycosmail.com (8.12.9/8.9.1) id k6KJCDqU004470 for ; Fri, 21 Jul 2006 04:12:13 +0900 X-Originating-IP: [67.62.49.106] From: "chauhansweety" Organization: Lycos. Inc. To: X-Mailer: Daum Web Mailer 1.1 Date: Thu, 20 Jul 2006 15:12:12 -0400 (EDT) Message-Id: <20060720151212.HM.00000000000009W@chauhansweety.bos-mail-wwl14.bos.lycos.com.lycos.com> MIME-Version: 1.0 X-Hanmail-Attr: fc=1 X-Spam-Score: 3.4 (+++) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Cc: olsr-niigata-support@net.ie.niigata-u.ac.jp Subject: [manet] OLSR_Glomosim_Implementation 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="===============1326846073==" Errors-To: manet-bounces@ietf.org --===============1326846073== Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Hi,

I was looking for Glomosim OLSR implementation and found one as mentioned in one of the mailing list post.

http://www1.ietf.org/mail-archive/web/manet/current/msg04637.html

I downloaded OLSR-Niigata Glomosim code but it doesn't seem to be working if I change config file.
I changed the number of nodes from 5 (default config file) to 10 and Node placement from FILE(nodes.input) to RANDOM and I am getting strange results.
Simulation runs until 52% then it generates huge numbers before generating route table as shown below.
Does anyone also faced this problem?

I would highly appreciate any help.


---------------------------------------------------------------------------
Current Sim Time[s] = 987.033320125 Real Time[s] = 0 Completed 47%
Current Sim Time[s] = 1008.000000000 Real Time[s] = 0 Completed 48%
Current Sim Time[s] = 1029.079560157 Real Time[s] = 0 Completed 49%
Current Sim Time[s] = 1050.000000000 Real Time[s] = 0 Completed 50%
Current Sim Time[s] = 1071.051032847 Real Time[s] = 0 Completed 51%
Current Sim Time[s] = 1092.000000000 Real Time[s] = 0 Completed 52%
5 1100386890752 3 2 12
5 1100386890752 3 4 12
5 1100386891052 3 1 12
5 1100386891352 3 0 12
6 1100387138024 3 2
3 1100387138024 3 2 5
6 1100387138024 3 4
3 1100387138024 3 4 5
6 1100387138324 3 1
3 1100387138324 3 1 10
.
.
....(53781 entries like above)

6 2099982737564 1 4
3 2099982737564 1 4 10
At time:2100.000000000
NODE:0 has LinkSet
L_neighbor_iface_addr:1 L_SYM_time:2104.475043860 L_ASYM_time:2104.475043860 L_time:2110.475043860
======================================
Node:0 has neighborNode
Node:1 Status: SYM Willingness:3
======================================
======================================
NODE:0 has two hop neighbor
Node:2 is Node:1's neighbor node N_time:2104.475043860
======================================
======================================
Node:0 has MPR
Node:1
======================================
===================================
Node:0 has no MPR-Selectors
===================================
At time 2100.000000000, the topology set of node 0:
-------------------------------------------------
Last node:1
numNeighbor:2 T_seq:2 T_time:2114.982736964
Dest node:0
Dest node:2

Last node:2
numNeighbor:2 T_seq:2 T_time:2114.982736964
Dest node:3
Dest node:1

Last node:3
numNeighbor:2 T_seq:2 T_time:2113.004114945
Dest node:2
Dest node:4

-------------------------------------------------
the routing table of node 0 time2100.000000000[s]
------------------------------------------------
destNode:[ 1][0] nextNode:1 1hop iface:0
destNode:[ 2][0] nextNode:1 2hop iface:0
destNode:[ 3][0] nextNode:1 3hop iface:0
destNode:[ 4][0] nextNode:1 4hop iface:0
------------------------------------------------

Thanks,
Sweety


Sweety Chauhan
Graduate Student
Department of Computer Science and Electrical Engg.
University of Maryland Baltimore County
Baltimore, MD- 21250
USA
--===============1326846073== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1326846073==-- From manet-bounces@ietf.org Mon Jul 24 17:58:36 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G58RW-0003dO-Qr; Mon, 24 Jul 2006 17:58:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G58RU-0003bH-L1 for manet@ietf.org; Mon, 24 Jul 2006 17:58:24 -0400 Received: from ug-out-1314.google.com ([66.249.92.175]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G58RR-0004y1-8D for manet@ietf.org; Mon, 24 Jul 2006 17:58:24 -0400 Received: by ug-out-1314.google.com with SMTP id m2so2576857uge for ; Mon, 24 Jul 2006 14:58:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=n51jeCcjGMYPzgH8y2gHkpy4ekdMLtzKzNV4OYXwuTRJ6PM1HKeLAgLzj6LyjesZuFuhJ0yC0JBypiW1r/4EEHiFioFTjjxU94sB2lg8kYydY7ZXW7U5Jv1lPXgq98km63Z7nlrrs2zCaGBkOxgxS3Am39fSD76SJA7Q59EIQ6s= Received: by 10.67.29.12 with SMTP id g12mr4028743ugj; Mon, 24 Jul 2006 14:58:20 -0700 (PDT) Received: by 10.66.224.14 with HTTP; Mon, 24 Jul 2006 14:58:20 -0700 (PDT) Message-ID: <374005f30607241458o5dc932ack48945384b224e22@mail.gmail.com> Date: Mon, 24 Jul 2006 14:58:20 -0700 From: "Ian Chakeres" To: manet , autoconf@ietf.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Cc: Subject: [manet] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.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: , Errors-To: manet-bounces@ietf.org Here is the draft I promised during MANET IETF 66 discussing MANET IANA considerations. It is meant to aid in discussing IANA assignments for MANET. I've broken down the different components into different sections. I think we are all in agreement in the immediate need for LL (link-local) MANET Routers multicast group. Less agreement, but definitely useful is a MANET UDP port. More discussion is needed for Scoped MANET Routers and any other scoped "host/node" multicast groups. Please comment on these. I would especially like some feedback from AUTOCONF people. Please email your comments to the lists or to me directly. Thanks. Ian Chakeres BTW: A document discussing MANET architecture should be coming out this week. Once it is posted I'll send an email also. The arch document may help in discussing the different IANA assignments. ---------- Forwarded message ---------- From: Internet-Drafts@ietf.org Date: Jul 24, 2006 12:50 PM Subject: I-D ACTION:draft-chakeres-manet-iana-00.txt To: i-d-announce@ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Discussing MANET IANA Needs Author(s) : I. Chakeres Filename : draft-chakeres-manet-iana-00.txt Pages : 9 Date : 2006-7-24 This document enumerates several possible IANA assignments for MANET protocols. It is meant to aid and stimulate discussion on this topic. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-chakeres-manet-iana-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-chakeres-manet-iana-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-chakeres-manet-iana-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Jul 25 04:21:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5IAa-0008Hq-QA; Tue, 25 Jul 2006 04:21:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5IAZ-0008Hk-J3 for manet@ietf.org; Tue, 25 Jul 2006 04:21:35 -0400 Received: from ppsw-0.csi.cam.ac.uk ([131.111.8.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5IAY-0003Mv-TS for manet@ietf.org; Tue, 25 Jul 2006 04:21:35 -0400 X-Cam-SpamDetails: Not scanned X-Cam-AntiVirus: No virus found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from c008.vpn.cl.cam.ac.uk ([128.232.105.8]:1343 helo=OAHU) by ppsw-0.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.150]:25) with esmtp id 1G5IA8-0000ZJ-08 (Exim 4.54) for manet@ietf.org (return-path ); Tue, 25 Jul 2006 09:21:08 +0100 From: "Eiko Yoneki" To: Date: Tue, 25 Jul 2006 09:20:59 +0100 Message-ID: <001701c6afc3$4581dd20$466ee880@cl.cam.ac.uk> 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.2869 Importance: Normal X-Spam-Score: 0.5 (/) X-Scan-Signature: 6a45e05c1e4343200aa6b327df2c43fc Subject: [manet] FW: [CFP] Workshop on Advanced Data Processing in Ubiquitous Computing (ADPUC 2006) X-BeenThere: manet@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ey204@cl.cam.ac.uk List-Id: Mobile Ad-hoc Networks List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: manet-bounces@ietf.org (Apologies if you receive multiple copies of this message) =20 The aim of workshop is to get together various research communities = (e.g. P2P indexing, composite events in Pub/Sub, stream Data processing, and sensor data aggregation) for future ubiquitous computing. -------------------------------------------------------------------------= - International Workshop on Advanced Data Processing in Ubiquitous = Computing (ADPUC 2006)=20 http://www.cs.waikato.ac.nz/~hinze/ADPUC/ In conjunction with ACM/IFIP/USENIX 7th International Middleware = Conference=20 http://2006.middleware-conference.org/ November 27 - December 1, MELBOURNE, AUSTRALIA =20 **** Submission Deadline August 1, 2006 **** -------------------------------------------------------------------------= - CALL FOR PAPERS Research in ubiquitous computing environments is now turning to novel concepts to address the challenge of providing data and query services. Middleware techniques can make key contributions to these needs. This workshop will address issues of data management in ubiquitous computing environment with a special focus on data processing. It will analyse paradigms for query and data processing that are rooted in the = middleware community and may be beneficial in the future of ubiquitous computing.=20 For those from the middleware research community, the ubiquitous or = mobile computing area raises challenges of system and algorithm design: mobile devices or devices in peer-to-peer networks have different properties to static networks. The environment is seen as being more fluid, with = increased rate of change of environment, and with components that can vary widely = in computing capability, availability and interaction type. Streaming data = or event-based data interchange in peer-to-peer networks are only two = examples. Current research often focuses on P2P networks that are extending to ubiquitous environments. Sensor data are captured beyond edge nodes in = wide area networks. Initial research in wireless sensor networks often = focused on WSN itself. However, in the near future those data will be integrated in Internet environments. At the same time, queries originated in the = Internet will be propagated into WSN environments. Data will be stored and shared among different applications over the Internet. Middleware systems will bridge the gap between these two different networks systems.=20 Aggregating data/events in ubiquitous computing requires management of stateful events. In addition, time in distributed and unreliable environments as well as asynchrony and unstable communication create = further challenges. The workshop aims at addressing a global view of data/event correlation, filtering and aggregation over whole distributed systems. = One of the goals of the workshop is the definition of key terms of data processing (e.g., aggregation, filtering, correlation, indexing, query, subscription, composition) in the light of different contexts and backgrounds.=20 In addition, there is no single typical WSN application, and dependency = on applications is higher than in traditional distributed applications. The application/middleware layer must provide fundamental services for = efficient extraction, manipulation, transport, and representation of information derived from sensor data. Data will be shared by different applications = over Internet. This requires the database community to revisit data models, = query languages, storage support, query optimization, as well as, data and application services integration. It also requires further interaction = with information retrieval, programming languages, artificial intelligence, distributed computing, and workflows.=20 AIM of WORKSHOP =20 The purpose of this workshop is to bring together people from different communities interested in all aspects of data processing in ubiquitous environments. We seek contributions from practitioners in industry and government, as well as from academic and industrial researchers. We specifically seek to encourage cross-fertilizations with related = research areas (e.g., such research areas as stream processing, continuous = queries, active databases, P2P searching and indexing, wireless networks). We = wish to avoid, for example, the database communities and the distributed systems communities independently studying and solving overlapping problems in ubiquitous environments.=20 We seek a balance between research studies relating to design and implementation of such systems, and presentations of either actual experience with the use of such systems for a real problem, or = requirements for future systems to solve projected real problems. Researchers need to make sure they are studying important problems; potential users need to understand the directions in evolving technologies. Since this is a workshop, we encourage position papers and works in progress rather than polished results.=20 Key goals of the workshop are: =20 - Initiate communication between the different research communities=20 - Develop understanding of the different foci of the communities=20 - Clarify the differing constraints and required functionality in representative applications=20 - Identify mutually agreed research questions within the area=20 - Explore methods of evaluation and comparison=20 - Cross-fertilise the ideas and innovations of the largely disjoint = groups=20 Papers do not have to be based on complete and comprehensive works. In = fact, we welcome position papers, requirements for real-world applications, as well as papers based on preliminary results, provided that they are forward-looking and that they remain well-argued and justified in terms = of existing work.=20 TOPICS OF INTEREST=20 The goal of this workshop is to share and discuss original and = innovative ideas. We intend this workshop to act as an initial forum where people = from different areas can find a forum to discuss issues of data management = and processing in these new and emerging environments. Therefore, we invite authors from diverse communities that are interested in data processing = in ubiquitous environments, such as middleware, distributed systems, ad-hoc = and peer-to-peer systems, delay tolerant networks, streaming sensor = networks, wireless sensor networks, databases, mobile computing.=20 Below is a list of possible topics of interest. The list should not be = seen as exhaustive.=20 - Data aggregation/correlation (e.g., for sensor data in ubiquitous environment)=20 - Reactive systems=20 - Event filtering/correlation over distributed systems=20 - Context extracting (e.g. meta-data extraction and annotation)=20 - Search/Query/Indexing mechanisms over P2P based systems=20 - Process models for ubiquitous/P2P environments (e.g. event-based, communication, selection)=20 - Multidimensional data/query model (e.g. Spatial and temporal = attributes)=20 - Semantic data model=20 - Semantic interoperability, and integration=20 - Filtering/composition algorithms also filtering/correlation engine=20 - Location over distributed systems=20 - Representation of database query in complex format for active database = - Data mining and knowledge discovery in distributed systems=20 - High-level language for event query and query task propagation=20 - Distributed stream processing and dissemination=20 - Stream-based and continuous query processing=20 - Query planning and optimization in distributed systems=20 IMPORTANT DATES Deadline for paper submission: August 1st, 2006=20 Decision to paper authors: September 1st, 2006 =20 Camera ready version: October 1st, 2006 =20 ADPUC 2006 workshop: November 27, 2006 =20 Middleware 2006 conference: November 27 - December 1, 2006 =20 SUBMISSION GUIDELINES Submissions should not exceed 6 (six) pages in ACM proceedings style, including all text, references, appendices, and figures. The template = can be found at http://www.acm.org/sigs/pubs/proceed/template.html (Option 1).=20 Please submit your paper by e-mail to a.hinze@cs.waikato.ac.nz no later = than the 1st August 2006. Your submission e-mail must have "ADPUC submission" = as subject and contain the PDF file as a MIME attachment. The sender of the submission will be the contact person, unless otherwise requested in the submission. At least one of the authors of accepted papers is expected = to participate in the workshop.=20 All workshop papers will be published via ACM's Digital Library as part = of the "ACM International Conference Proceeding Series" (AICPS). =20 ORGANIZERS Annika Hinze=20 Department of Computer Science University of Waikato Private Bag 3105 Hamilton, New Zealand Email: a.hinze@cs.waikato.ac.nz=20 Eiko Yoneki=20 University of Cambridge=20 Computer Laboratory JJ Thomson Avenue, Cambridge=20 CB3 0FD, United Kingdom=20 Email: eiko.yoneki@cl.cam.ac.uk=20 PROGRAM COMMITTEE - Mariano Cilia, University of Darmstadt, Germany=20 - Landon Cox (Duke University, USA)=20 - Patrick Eugster, Purdue University, USA=20 - Ludger Fiege, Siemens AG, Germany=20 - Christos Gkantsidis (Microsoft Research)=20 - Birgitta K=F6nig-Ries, Friedrich-Schiller-Universit=E4t, Jena, Germany = - Peter Pietzuch, Harvard University, USA=20 - Manuel Scholz, Freie Universitaet Berlin, Germany=20 - Sasu Tarkoma, University of Helsinki, Finland=20 - Nesime Tatbul (Brown University, USA)=20 - Niki Trigoni, Birkbeck, University of London, UK=20 - Can T=FCrker, UNI / ETH Zurich, Switzerland=20 _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Jul 25 04:22:24 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5IBM-00006J-Oi; Tue, 25 Jul 2006 04:22:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5IBK-00005u-G8 for manet@ietf.org; Tue, 25 Jul 2006 04:22:22 -0400 Received: from [210.51.13.101] (helo=broadmaking.com) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G5IBI-0003TY-EF for manet@ietf.org; Tue, 25 Jul 2006 04:22:22 -0400 Received: from kathmandu ([166.111.68.197]) (envelope-sender ) by 210.51.13.101 with ESMTP for ; Tue, 25 Jul 2006 16:43:25 +0800 From: "ldsheng@bm" To: Date: Tue, 25 Jul 2006 16:21:54 +0800 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 Thread-Index: Acavw2MFOteh+mWnTMiV+ami3U8SMA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f Subject: [manet] Has anybody ever made the mathematical analysis about routing load of AODV? 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="===============0422477553==" Errors-To: manet-bounces@ietf.org Message-Id: This is a multi-part message in MIME format. --===============0422477553== Content-Type: multipart/alternative; boundary="----=_NextPart_000_001E_01C6B006.72277A40" This is a multi-part message in MIME format. ------=_NextPart_000_001E_01C6B006.72277A40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit HI, all, I'm studying in routing technology of MANETs. After reading some articles, I found that almost all the analysis of routing load of routing protocol is being done on network simulation platform such as NS-2 etc. Has anybody ever made the mathematical analysis of it? Or is it possible to do so? Or any suggestion if I want to begin a mathematical analysis on it? ------=_NextPart_000_001E_01C6B006.72277A40 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

HI, all,

        = I’m = studying in routing technology of MANETs. After reading some articles, I found that = almost all the analysis of routing load of routing protocol is being done on = network simulation platform such as NS-2 etc. Has anybody ever made the = mathematical analysis of it? Or is it possible to do so? Or any suggestion if I want = to begin a mathematical analysis on it?

------=_NextPart_000_001E_01C6B006.72277A40-- --===============0422477553== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0422477553==-- From manet-bounces@ietf.org Tue Jul 25 04:42:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5IV3-0000Da-0v; Tue, 25 Jul 2006 04:42:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5IV1-000087-9A; Tue, 25 Jul 2006 04:42:43 -0400 Received: from balu1.urz.unibas.ch ([131.152.1.51]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5IUz-0008Tr-RZ; Tue, 25 Jul 2006 04:42:43 -0400 Received: from [131.152.55.200] (baobab.cs.unibas.ch [131.152.55.200]) by balu1.urz.unibas.ch (8.13.7/8.13.7) with ESMTP id k6P8ge1W002610; Tue, 25 Jul 2006 10:42:40 +0200 Message-ID: <44C5D9B3.7040006@unibas.ch> Date: Tue, 25 Jul 2006 10:43:31 +0200 From: Christophe Jelger Organization: University of Basel User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ian Chakeres References: <374005f30607241458o5dc932ack48945384b224e22@mail.gmail.com> In-Reply-To: <374005f30607241458o5dc932ack48945384b224e22@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SMTP-Vilter-Version: 1.3.1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Cc: autoconf@ietf.org, manet Subject: [manet] Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.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: , Errors-To: manet-bounces@ietf.org Ian/all, I didn't attend the last ietf meeting so I don't know how this topic was discussed but I remember we had a similar discussion in March 2005 and the consensus (March 17th 2005) was that there should be a multicast address for each MANET routing protocol as done with existing routing protocols (e.g. ff02::5 and ff02::6 for OSPF, ff02::9 for RIP, ff02::d for PIM). One argument was to be consistent with current practices, and another argument was that we already have ff02::1 (all nodes) and ff02::2 (all routers) so it was not clear why we should have an extra "all_manet_routers" address (especially if we have a multicast address for each manet routing protocol). Also having a different multicast address for each manet routing protocol prevents a node that does not run a given routing protocol to process packets associated to it: it will not even receive them at the MAC layer. So I'm rather in favor of having for example ff02::DYMO and ff02::OLSRv2, and if a larger scope is required we can instead have ff0x::DYMO and ff0x::OLSRv2. This implies that there would not be an all_manet_routers address. Now for address autoconfiguration, there could also be a dedicated multicast address ff0x::MANET-AUTOCONF. regards, Christophe PS: note that the same reasoning applies to IPv4 Ian Chakeres wrote: > Here is the draft I promised during MANET IETF 66 discussing MANET > IANA considerations. It is meant to aid in discussing IANA assignments > for MANET. I've broken down the different components into different > sections. > > I think we are all in agreement in the immediate need for LL > (link-local) MANET Routers multicast group. > > Less agreement, but definitely useful is a MANET UDP port. > > More discussion is needed for Scoped MANET Routers and any other > scoped "host/node" multicast groups. Please comment on these. I would > especially like some feedback from AUTOCONF people. > > Please email your comments to the lists or to me directly. > > Thanks. > Ian Chakeres > > BTW: A document discussing MANET architecture should be coming out > this week. Once it is posted I'll send an email also. The arch > document may help in discussing the different IANA assignments. > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Jul 25 08:53:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5MPU-00034g-69; Tue, 25 Jul 2006 08:53:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5MPS-00034Y-JJ for manet@ietf.org; Tue, 25 Jul 2006 08:53:14 -0400 Received: from mailgate.cc.niigata-u.ac.jp ([133.35.14.100]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5MPR-0003cc-5n for manet@ietf.org; Tue, 25 Jul 2006 08:53:14 -0400 Received: from mailgate.cc.niigata-u.ac.jp (localhost.localdomain [127.0.0.1]) by localhost.cc.niigata-u.ac.jp (Postfix) with ESMTP id A52D224C28D for ; Tue, 25 Jul 2006 21:53:21 +0900 (JST) Received: from ms01.net.ie.niigata-u.ac.jp (ms01.net.ie.niigata-u.ac.jp [133.35.156.1]) by mailgate.cc.niigata-u.ac.jp (Postfix) with ESMTP id 97D2524C241 for ; Tue, 25 Jul 2006 21:53:21 +0900 (JST) Received: from [172.23.150.106] (ms02.net.ie.niigata-u.ac.jp [133.35.156.2]) by ms01.net.ie.niigata-u.ac.jp (Postfix) with ESMTP id 3031E1205B for ; Tue, 25 Jul 2006 21:52:40 +0900 (JST) Message-ID: <44C61428.4050802@net.ie.niigata-u.ac.jp> Date: Tue, 25 Jul 2006 21:52:56 +0900 From: kim User-Agent: Thunderbird 1.5.0.4 (X11/20060614) MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [manet] OLSR_Glomosim_Implementation(Reply) 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: , Errors-To: manet-bounces@ietf.org Apologies if you receive this more than once. Dear Sweety: I am writing to you in response to previous two question. 1)I think two possibilities may cause such problems. one possibility is glomosim-2.03 has not implemented correctly. you can download glomosim-2.03/ from http://pcl.cs.ucla.edu/projects/glomosim/. Another possibility is CBR packet format is node correct. you can try to set "app.conf" file like below format. CBR 23 0 0 512 0.150000S 1158.912314S 2108.912314S OFF. 2)because 5 nodes were placed in (500, 500) area with randomly and the propagation range was set at 100m in default multiInterface.input file, so a distance of between two neighbor nodes maybe longer then 100m .it cause that hello message can not reach neighbor nodes leading to routing calculation is failed. If you have any questions, please feel free to contact us at any time. best regards. Shouguang Jin _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Jul 25 10:53:43 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5OHs-0007Rs-1p; Tue, 25 Jul 2006 10:53:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5OHq-0007RV-AM for manet@ietf.org; Tue, 25 Jul 2006 10:53:30 -0400 Received: from ug-out-1314.google.com ([66.249.92.170]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5OHo-00087z-Vi for manet@ietf.org; Tue, 25 Jul 2006 10:53:30 -0400 Received: by ug-out-1314.google.com with SMTP id m2so2872603uge for ; Tue, 25 Jul 2006 07:53:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RUU9tRT5M9S7v1LNgC40IRu478e/LD/79IO66TKnrw4Rkcbaxn8GSbgaJOxbEQcGD7bavXSTa/uOPRHUekKZrZrJr2Soz89OWxSQiIVVPkKpAWsaqfSnqGXmMDrJ+oP7wZt8E19nQQr5QP0OSK43IVnycWNfraSHbbZsGH4icSk= Received: by 10.67.101.8 with SMTP id d8mr4786701ugm; Tue, 25 Jul 2006 07:53:27 -0700 (PDT) Received: by 10.66.224.14 with HTTP; Tue, 25 Jul 2006 07:53:27 -0700 (PDT) Message-ID: <374005f30607250753n288fbd81lc1b834312f953a34@mail.gmail.com> Date: Tue, 25 Jul 2006 07:53:27 -0700 From: "Ian Chakeres" To: "Christophe Jelger" In-Reply-To: <44C5D9B3.7040006@unibas.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <374005f30607241458o5dc932ack48945384b224e22@mail.gmail.com> <44C5D9B3.7040006@unibas.ch> X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Cc: autoconf@ietf.org, manet Subject: [manet] Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.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: , Errors-To: manet-bounces@ietf.org Since March 2005, we've come a long way building common building blocks into MANET protocols. We now have a common packet/message format (PacketBB) and a common neighborhood discovery protocol (NHDP). In order to aggregate MANET messages we'd need to send these to the same Multicast group. This is the reasoning behind using a single multicast group; instead of one per protocol. Ian On 7/25/06, Christophe Jelger wrote: > Ian/all, > > I didn't attend the last ietf meeting so I don't know how this topic was > discussed but I remember we had a similar discussion in March 2005 and > the consensus (March 17th 2005) was that there should be a multicast > address for each MANET routing protocol as done with existing routing > protocols (e.g. ff02::5 and ff02::6 for OSPF, ff02::9 for RIP, ff02::d > for PIM). > > One argument was to be consistent with current practices, and another > argument was that we already have ff02::1 (all nodes) and ff02::2 (all > routers) so it was not clear why we should have an extra > "all_manet_routers" address (especially if we have a multicast address > for each manet routing protocol). Also having a different multicast > address for each manet routing protocol prevents a node that does not > run a given routing protocol to process packets associated to it: it > will not even receive them at the MAC layer. > > So I'm rather in favor of having for example ff02::DYMO and > ff02::OLSRv2, and if a larger scope is required we can instead have > ff0x::DYMO and ff0x::OLSRv2. This implies that there would not be an > all_manet_routers address. Now for address autoconfiguration, there > could also be a dedicated multicast address ff0x::MANET-AUTOCONF. > > regards, > Christophe > > PS: note that the same reasoning applies to IPv4 > > Ian Chakeres wrote: > > Here is the draft I promised during MANET IETF 66 discussing MANET > > IANA considerations. It is meant to aid in discussing IANA assignments > > for MANET. I've broken down the different components into different > > sections. > > > > I think we are all in agreement in the immediate need for LL > > (link-local) MANET Routers multicast group. > > > > Less agreement, but definitely useful is a MANET UDP port. > > > > More discussion is needed for Scoped MANET Routers and any other > > scoped "host/node" multicast groups. Please comment on these. I would > > especially like some feedback from AUTOCONF people. > > > > Please email your comments to the lists or to me directly. > > > > Thanks. > > Ian Chakeres > > > > BTW: A document discussing MANET architecture should be coming out > > this week. Once it is posted I'll send an email also. The arch > > document may help in discussing the different IANA assignments. > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Jul 25 11:36:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5OxL-0005A0-Li; Tue, 25 Jul 2006 11:36:23 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5OxJ-00056b-J6; Tue, 25 Jul 2006 11:36:21 -0400 Received: from balu1.urz.unibas.ch ([131.152.1.51]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5OxI-0004Q2-3P; Tue, 25 Jul 2006 11:36:21 -0400 Received: from [131.152.55.200] (baobab.cs.unibas.ch [131.152.55.200]) by balu1.urz.unibas.ch (8.13.7/8.13.7) with ESMTP id k6PFaHK0026124; Tue, 25 Jul 2006 17:36:17 +0200 Message-ID: <44C63AA4.4060907@unibas.ch> Date: Tue, 25 Jul 2006 17:37:08 +0200 From: Christophe Jelger Organization: University of Basel User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ian Chakeres References: <374005f30607241458o5dc932ack48945384b224e22@mail.gmail.com> <44C5D9B3.7040006@unibas.ch> <374005f30607250753n288fbd81lc1b834312f953a34@mail.gmail.com> In-Reply-To: <374005f30607250753n288fbd81lc1b834312f953a34@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SMTP-Vilter-Version: 1.3.1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Cc: autoconf@ietf.org, manet Subject: [manet] Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.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: , Errors-To: manet-bounces@ietf.org Yes that's a good point but having a common packet format is not in contradiction with having a dedicated mcast addr per routing protocol. I understand that having a unique mcast addr makes it easy to aggregate routing information but while I understand this is useful for a given protocol, I cannot see why it's useful among different protocols. I mean, carrying routing messages all over the MANET is one thing, but this makes little sense if intermediate nodes are not ready to partipate in packet forwarding. For example in the following scenario A(DYMO) --- B(OLSRv2) --- C(DYMO) if node C receives DYMO messages from A (messages sent by A are aggregated with the messages sent by B) and vice versa, still node B does not process DYMO messages and hence would not create forwarding states. Communication between A and C is not possible. With dedicated mcast addresses, C and A don't see eachother at the DYMO level but anyway they cannot communicate so it makes perfect sense to me. As I said in an autoconf-only email, having different mcast addresses is an optimization because it introduces some low-level filtering at the MAC layer. For example NHDP introduces the ALL-MANET-NEIGHBORS address: in your view would this be different than the ALL-MANET-ROUTERS address? Personaly I don't see any negative reasons for not having an mcast address per protocol (DYMO, OLSRv2, NHDP). Note that I'm not against your scheme, I just think it's better to have dedicated mcast addresses. regards, Christophe Ian Chakeres wrote: > Since March 2005, we've come a long way building common building > blocks into MANET protocols. We now have a common packet/message > format (PacketBB) and a common neighborhood discovery protocol (NHDP). > In order to aggregate MANET messages we'd need to send these to the > same Multicast group. This is the reasoning behind using a single > multicast group; instead of one per protocol. > > Ian > > On 7/25/06, Christophe Jelger wrote: > >> Ian/all, >> >> I didn't attend the last ietf meeting so I don't know how this topic was >> discussed but I remember we had a similar discussion in March 2005 and >> the consensus (March 17th 2005) was that there should be a multicast >> address for each MANET routing protocol as done with existing routing >> protocols (e.g. ff02::5 and ff02::6 for OSPF, ff02::9 for RIP, ff02::d >> for PIM). >> >> One argument was to be consistent with current practices, and another >> argument was that we already have ff02::1 (all nodes) and ff02::2 (all >> routers) so it was not clear why we should have an extra >> "all_manet_routers" address (especially if we have a multicast address >> for each manet routing protocol). Also having a different multicast >> address for each manet routing protocol prevents a node that does not >> run a given routing protocol to process packets associated to it: it >> will not even receive them at the MAC layer. >> >> So I'm rather in favor of having for example ff02::DYMO and >> ff02::OLSRv2, and if a larger scope is required we can instead have >> ff0x::DYMO and ff0x::OLSRv2. This implies that there would not be an >> all_manet_routers address. Now for address autoconfiguration, there >> could also be a dedicated multicast address ff0x::MANET-AUTOCONF. >> >> regards, >> Christophe >> >> PS: note that the same reasoning applies to IPv4 >> >> Ian Chakeres wrote: >> > Here is the draft I promised during MANET IETF 66 discussing MANET >> > IANA considerations. It is meant to aid in discussing IANA assignments >> > for MANET. I've broken down the different components into different >> > sections. >> > >> > I think we are all in agreement in the immediate need for LL >> > (link-local) MANET Routers multicast group. >> > >> > Less agreement, but definitely useful is a MANET UDP port. >> > >> > More discussion is needed for Scoped MANET Routers and any other >> > scoped "host/node" multicast groups. Please comment on these. I would >> > especially like some feedback from AUTOCONF people. >> > >> > Please email your comments to the lists or to me directly. >> > >> > Thanks. >> > Ian Chakeres >> > >> > BTW: A document discussing MANET architecture should be coming out >> > this week. Once it is posted I'll send an email also. The arch >> > document may help in discussing the different IANA assignments. >> > >> > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Jul 25 13:06:09 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5QLy-0001MW-MB; Tue, 25 Jul 2006 13:05:54 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5QLw-0001KP-KS for manet@ietf.org; Tue, 25 Jul 2006 13:05:52 -0400 Received: from ug-out-1314.google.com ([66.249.92.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5QLw-00087v-38 for manet@ietf.org; Tue, 25 Jul 2006 13:05:52 -0400 Received: by ug-out-1314.google.com with SMTP id m2so2938897uge for ; Tue, 25 Jul 2006 10:05:51 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fBysRkY4tzrTYp8pADtfsSXNKYEg4Rrki0bKZ4XsFpCk+MPbpYm4a6c24UbsB+A9bQu7qmKd31liTX1e/1jc53OLrgWY9HD9EoztiSulX3ffVmF3BanwBKcwDlFOUDptNZl1KHgr7UOT51LMdGVrAYn5DlePTC2LMIhHpC7by1s= Received: by 10.66.219.11 with SMTP id r11mr4949597ugg; Tue, 25 Jul 2006 10:05:51 -0700 (PDT) Received: by 10.66.224.14 with HTTP; Tue, 25 Jul 2006 10:05:46 -0700 (PDT) Message-ID: <374005f30607251005u5ad2cae6ye795e09ef4b30419@mail.gmail.com> Date: Tue, 25 Jul 2006 10:05:46 -0700 From: "Ian Chakeres" To: "Christophe Jelger" In-Reply-To: <44C63AA4.4060907@unibas.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <374005f30607241458o5dc932ack48945384b224e22@mail.gmail.com> <44C5D9B3.7040006@unibas.ch> <374005f30607250753n288fbd81lc1b834312f953a34@mail.gmail.com> <44C63AA4.4060907@unibas.ch> X-Spam-Score: 0.0 (/) X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1 Cc: autoconf@ietf.org, manet Subject: [manet] Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.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: , Errors-To: manet-bounces@ietf.org Given that these protocols are going to run over wireless interfaces (like IEEE 802.11), the main contributor to congestion is channel access (not bits). Therefore; if each protocol uses a separate packet it can result in a significant increase in channel access. Let me give a simple example. OLSR will use NHDP, it will also add certain TLVs to NHDP for determining MPRs. OLSR will also send other messages. It does not really make sense to separate the two onto different multicast addresses or ports. Continuing to add to this example, imagine that a portion of the network is also running DYMO and NHDP. If separate multicast groups were used these messages would consume even more channel access opportunities. One more continuation, it is likely that either reactive or proactive may use SMF with NHDP. Again, if a separate link-local address is used then these messages cannot be aggregated. Realistically, if a certian deployment (provider) requires each part of the solution to use a different multicast group this could be implemented, but I think the default (interoperable behavior) should be to use a single multicast address to reduce channel access. Christophe, do you think we should define one default multicast address and one for each component? Ian Chakeres On 7/25/06, Christophe Jelger wrote: > Yes that's a good point but having a common packet format is not in > contradiction with having a dedicated mcast addr per routing protocol. I > understand that having a unique mcast addr makes it easy to aggregate > routing information but while I understand this is useful for a given > protocol, I cannot see why it's useful among different protocols. I > mean, carrying routing messages all over the MANET is one thing, but > this makes little sense if intermediate nodes are not ready to partipate > in packet forwarding. For example in the following scenario > > A(DYMO) --- B(OLSRv2) --- C(DYMO) > > if node C receives DYMO messages from A (messages sent by A are > aggregated with the messages sent by B) and vice versa, still node B > does not process DYMO messages and hence would not create forwarding > states. Communication between A and C is not possible. With dedicated > mcast addresses, C and A don't see eachother at the DYMO level but > anyway they cannot communicate so it makes perfect sense to me. > > As I said in an autoconf-only email, having different mcast addresses is > an optimization because it introduces some low-level filtering at the > MAC layer. For example NHDP introduces the ALL-MANET-NEIGHBORS address: > in your view would this be different than the ALL-MANET-ROUTERS address? > > Personaly I don't see any negative reasons for not having an mcast > address per protocol (DYMO, OLSRv2, NHDP). Note that I'm not against > your scheme, I just think it's better to have dedicated mcast addresses. > > regards, > Christophe > > Ian Chakeres wrote: > > Since March 2005, we've come a long way building common building > > blocks into MANET protocols. We now have a common packet/message > > format (PacketBB) and a common neighborhood discovery protocol (NHDP). > > In order to aggregate MANET messages we'd need to send these to the > > same Multicast group. This is the reasoning behind using a single > > multicast group; instead of one per protocol. > > > > Ian > > > > On 7/25/06, Christophe Jelger wrote: > > > >> Ian/all, > >> > >> I didn't attend the last ietf meeting so I don't know how this topic was > >> discussed but I remember we had a similar discussion in March 2005 and > >> the consensus (March 17th 2005) was that there should be a multicast > >> address for each MANET routing protocol as done with existing routing > >> protocols (e.g. ff02::5 and ff02::6 for OSPF, ff02::9 for RIP, ff02::d > >> for PIM). > >> > >> One argument was to be consistent with current practices, and another > >> argument was that we already have ff02::1 (all nodes) and ff02::2 (all > >> routers) so it was not clear why we should have an extra > >> "all_manet_routers" address (especially if we have a multicast address > >> for each manet routing protocol). Also having a different multicast > >> address for each manet routing protocol prevents a node that does not > >> run a given routing protocol to process packets associated to it: it > >> will not even receive them at the MAC layer. > >> > >> So I'm rather in favor of having for example ff02::DYMO and > >> ff02::OLSRv2, and if a larger scope is required we can instead have > >> ff0x::DYMO and ff0x::OLSRv2. This implies that there would not be an > >> all_manet_routers address. Now for address autoconfiguration, there > >> could also be a dedicated multicast address ff0x::MANET-AUTOCONF. > >> > >> regards, > >> Christophe > >> > >> PS: note that the same reasoning applies to IPv4 > >> > >> Ian Chakeres wrote: > >> > Here is the draft I promised during MANET IETF 66 discussing MANET > >> > IANA considerations. It is meant to aid in discussing IANA assignments > >> > for MANET. I've broken down the different components into different > >> > sections. > >> > > >> > I think we are all in agreement in the immediate need for LL > >> > (link-local) MANET Routers multicast group. > >> > > >> > Less agreement, but definitely useful is a MANET UDP port. > >> > > >> > More discussion is needed for Scoped MANET Routers and any other > >> > scoped "host/node" multicast groups. Please comment on these. I would > >> > especially like some feedback from AUTOCONF people. > >> > > >> > Please email your comments to the lists or to me directly. > >> > > >> > Thanks. > >> > Ian Chakeres > >> > > >> > BTW: A document discussing MANET architecture should be coming out > >> > this week. Once it is posted I'll send an email also. The arch > >> > document may help in discussing the different IANA assignments. > >> > > >> > > > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Tue Jul 25 13:32:13 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5QlO-0002dH-JP; Tue, 25 Jul 2006 13:32:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5QlM-0002d7-PW for manet@ietf.org; Tue, 25 Jul 2006 13:32:08 -0400 Received: from mail.um.es ([155.54.212.109]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5QlL-00030v-VJ for manet@ietf.org; Tue, 25 Jul 2006 13:32:08 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.um.es (Postfix) with ESMTP id C647123F298 for ; Tue, 25 Jul 2006 19:32:04 +0200 (CEST) Received: from mail.um.es ([127.0.0.1]) by localhost (xenon2 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30025-01-91 for ; Tue, 25 Jul 2006 19:32:04 +0200 (CEST) Received: from aries.dif.um.es (aries.inf.um.es [155.54.210.253]) by mail.um.es (Postfix) with SMTP id 78F1B23F267 for ; Tue, 25 Jul 2006 19:32:04 +0200 (CEST) Received: (qmail 28546 invoked from network); 25 Jul 2006 17:32:12 -0000 Received: from cartman.dif.um.es (155.54.210.126) by aries.dif.um.es with SMTP; 25 Jul 2006 17:32:12 -0000 From: "Francisco J. Ros" Organization: University of Murcia To: manet@ietf.org Subject: Re: [manet] Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt Date: Tue, 25 Jul 2006 19:34:53 +0200 User-Agent: KMail/1.7.2 References: <44C63AA4.4060907@unibas.ch> <374005f30607251005u5ad2cae6ye795e09ef4b30419@mail.gmail.com> In-Reply-To: <374005f30607251005u5ad2cae6ye795e09ef4b30419@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607251934.53978.fjrm@dif.um.es> X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at telemat.um.es X-Spam-Score: 1.9 (+) X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985 Cc: autoconf@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: , Errors-To: manet-bounces@ietf.org Hi everyone, On Tuesday 25 July 2006 19:05, Ian Chakeres wrote: > Given that these protocols are going to run over wireless interfaces > (like IEEE 802.11), the main contributor to congestion is channel > access (not bits). Therefore; if each protocol uses a separate packet > it can result in a significant increase in channel access. > However, if the messages are aggregated the packet size increases and, accordingly, the likelihood of having an error in the transmission. I'm just pointing out that there is a tradeoff there. > Let me give a simple example. OLSR will use NHDP, it will also add > certain TLVs to NHDP for determining MPRs. OLSR will also send other > messages. It does not really make sense to separate the two onto > different multicast addresses or ports. > Agree. > Continuing to add to this example, imagine that a portion of the > network is also running DYMO and NHDP. If separate multicast groups > were used these messages would consume even more channel access > opportunities. > If the NHDP had its own multicast address, it wouldn't make a difference whether the other portion is running DYMO or OLSR. > One more continuation, it is likely that either reactive or proactive > may use SMF with NHDP. Again, if a separate link-local address is used > then these messages cannot be aggregated. > Yes. Right now I can't see which approach is better. I think the point raised by Cristophe is important, since processing messages of a protocol which is not implemented by the node seems a waste of resources. On the other hand, sending OLSRv2 and NHDP messages to different addresses sounds quite strange. Regards, Francisco J. Ros > Realistically, if a certian deployment (provider) requires each part > of the solution to use a different multicast group this could be > implemented, but I think the default (interoperable behavior) should > be to use a single multicast address to reduce channel access. > > Christophe, do you think we should define one default multicast > address and one for each component? > > Ian Chakeres > > On 7/25/06, Christophe Jelger wrote: > > Yes that's a good point but having a common packet format is not in > > contradiction with having a dedicated mcast addr per routing protocol. I > > understand that having a unique mcast addr makes it easy to aggregate > > routing information but while I understand this is useful for a given > > protocol, I cannot see why it's useful among different protocols. I > > mean, carrying routing messages all over the MANET is one thing, but > > this makes little sense if intermediate nodes are not ready to partipate > > in packet forwarding. For example in the following scenario > > > > A(DYMO) --- B(OLSRv2) --- C(DYMO) > > > > if node C receives DYMO messages from A (messages sent by A are > > aggregated with the messages sent by B) and vice versa, still node B > > does not process DYMO messages and hence would not create forwarding > > states. Communication between A and C is not possible. With dedicated > > mcast addresses, C and A don't see eachother at the DYMO level but > > anyway they cannot communicate so it makes perfect sense to me. > > > > As I said in an autoconf-only email, having different mcast addresses is > > an optimization because it introduces some low-level filtering at the > > MAC layer. For example NHDP introduces the ALL-MANET-NEIGHBORS address: > > in your view would this be different than the ALL-MANET-ROUTERS address? > > > > Personaly I don't see any negative reasons for not having an mcast > > address per protocol (DYMO, OLSRv2, NHDP). Note that I'm not against > > your scheme, I just think it's better to have dedicated mcast addresses. > > > > regards, > > Christophe > > > > Ian Chakeres wrote: > > > Since March 2005, we've come a long way building common building > > > blocks into MANET protocols. We now have a common packet/message > > > format (PacketBB) and a common neighborhood discovery protocol (NHDP). > > > In order to aggregate MANET messages we'd need to send these to the > > > same Multicast group. This is the reasoning behind using a single > > > multicast group; instead of one per protocol. > > > > > > Ian > > > > > > On 7/25/06, Christophe Jelger wrote: > > >> Ian/all, > > >> > > >> I didn't attend the last ietf meeting so I don't know how this topic > > >> was discussed but I remember we had a similar discussion in March 2005 > > >> and the consensus (March 17th 2005) was that there should be a > > >> multicast address for each MANET routing protocol as done with > > >> existing routing protocols (e.g. ff02::5 and ff02::6 for OSPF, ff02::9 > > >> for RIP, ff02::d for PIM). > > >> > > >> One argument was to be consistent with current practices, and another > > >> argument was that we already have ff02::1 (all nodes) and ff02::2 (all > > >> routers) so it was not clear why we should have an extra > > >> "all_manet_routers" address (especially if we have a multicast address > > >> for each manet routing protocol). Also having a different multicast > > >> address for each manet routing protocol prevents a node that does not > > >> run a given routing protocol to process packets associated to it: it > > >> will not even receive them at the MAC layer. > > >> > > >> So I'm rather in favor of having for example ff02::DYMO and > > >> ff02::OLSRv2, and if a larger scope is required we can instead have > > >> ff0x::DYMO and ff0x::OLSRv2. This implies that there would not be an > > >> all_manet_routers address. Now for address autoconfiguration, there > > >> could also be a dedicated multicast address ff0x::MANET-AUTOCONF. > > >> > > >> regards, > > >> Christophe > > >> > > >> PS: note that the same reasoning applies to IPv4 > > >> > > >> Ian Chakeres wrote: > > >> > Here is the draft I promised during MANET IETF 66 discussing MANET > > >> > IANA considerations. It is meant to aid in discussing IANA > > >> > assignments for MANET. I've broken down the different components > > >> > into different sections. > > >> > > > >> > I think we are all in agreement in the immediate need for LL > > >> > (link-local) MANET Routers multicast group. > > >> > > > >> > Less agreement, but definitely useful is a MANET UDP port. > > >> > > > >> > More discussion is needed for Scoped MANET Routers and any other > > >> > scoped "host/node" multicast groups. Please comment on these. I > > >> > would especially like some feedback from AUTOCONF people. > > >> > > > >> > Please email your comments to the lists or to me directly. > > >> > > > >> > Thanks. > > >> > Ian Chakeres > > >> > > > >> > BTW: A document discussing MANET architecture should be coming out > > >> > this week. Once it is posted I'll send an email also. The arch > > >> > document may help in discussing the different IANA assignments. > > _______________________________________________ > manet mailing 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 Jul 25 15:15:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5SNM-00068L-GW; Tue, 25 Jul 2006 15:15:28 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5SNK-00065w-GF; Tue, 25 Jul 2006 15:15:26 -0400 Received: from balu1.urz.unibas.ch ([131.152.1.51]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5SNJ-0003Ow-1q; Tue, 25 Jul 2006 15:15:26 -0400 Received: from localhost (webmail.urz.unibas.ch [131.152.1.20]) by balu1.urz.unibas.ch (8.13.7/8.13.7) with ESMTP id k6PJFF70008088; Tue, 25 Jul 2006 21:15:15 +0200 Received: from ip-62-241-100-226.evc.net (ip-62-241-100-226.evc.net [62.241.100.226]) by webmail.unibas.ch (IMP) with HTTP for ; Tue, 25 Jul 2006 21:15:15 +0200 Message-ID: <1153854915.44c66dc3b0716@webmail.unibas.ch> Date: Tue, 25 Jul 2006 21:15:15 +0200 From: Christophe.Jelger@unibas.ch To: Ian Chakeres References: <374005f30607241458o5dc932ack48945384b224e22@mail.gmail.com> <44C5D9B3.7040006@unibas.ch> <374005f30607250753n288fbd81lc1b834312f953a34@mail.gmail.com> <44C63AA4.4060907@unibas.ch> <374005f30607251005u5ad2cae6ye795e09ef4b30419@mail.gmail.com> In-Reply-To: <374005f30607251005u5ad2cae6ye795e09ef4b30419@mail.gmail.com> 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: 62.241.100.226 X-SMTP-Vilter-Version: 1.3.1 X-Spam-Score: 0.2 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Cc: autoconf@ietf.org, manet Subject: [manet] Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.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: , Errors-To: manet-bounces@ietf.org Ian, See my comments inline. Quoting Ian Chakeres : > Given that these protocols are going to run over wireless interfaces > (like IEEE 802.11), the main contributor to congestion is channel > access (not bits). Therefore; if each protocol uses a separate packet > it can result in a significant increase in channel access. ok that's something I didn't think of. However if this is the only point in favor of aggregation I'm afraid I'm still not really convinced. One drawback of aggregation is increased delay. That is, each node will have to wait some small amount of time (1ms?, 10ms?) to be able to aggregate packets. > > Let me give a simple example. OLSR will use NHDP, it will also add > certain TLVs to NHDP for determining MPRs. OLSR will also send other > messages. It does not really make sense to separate the two onto > different multicast addresses or ports. > > Continuing to add to this example, imagine that a portion of the > network is also running DYMO and NHDP. If separate multicast groups > were used these messages would consume even more channel access > opportunities. > > One more continuation, it is likely that either reactive or proactive > may use SMF with NHDP. Again, if a separate link-local address is used > then these messages cannot be aggregated. > > Realistically, if a certian deployment (provider) requires each part > of the solution to use a different multicast group this could be > implemented, but I think the default (interoperable behavior) should > be to use a single multicast address to reduce channel access. ok I understand your points but I'm just not much convinced about the aggregation feature. Of course it's somehow elegant but I'm not sure the extra complexity is worth the effort. > > Christophe, do you think we should define one default multicast > address and one for each component? Well IMHO I'm still in favor of having separate multicast addresses for e.g. respectively DYMO, OLSRv2 and NHDP. But hey after all this is not the most important issue to be resolved so I won't fight very hard. ;-) regards, Christophe ---------------------------------------------------------------- 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 Wed Jul 26 02:26:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5cq5-0003Nn-TH; Wed, 26 Jul 2006 02:25:49 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5cq3-0003My-LD; Wed, 26 Jul 2006 02:25:47 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5cq3-0006Zf-J6; Wed, 26 Jul 2006 02:25:47 -0400 Received: from outbound.mailhop.org ([63.208.196.171]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G5cdK-0006zN-4b; Wed, 26 Jul 2006 02:12:39 -0400 Received: from did75-10-82-236-230-133.fbx.proxad.net ([82.236.230.133] helo=[192.168.147.101]) by outbound.mailhop.org with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.51) id 1G5cdF-0001d5-62; Wed, 26 Jul 2006 02:12:33 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 82.236.230.133 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: voop In-Reply-To: <1153854915.44c66dc3b0716@webmail.unibas.ch> References: <374005f30607241458o5dc932ack48945384b224e22@mail.gmail.com> <44C5D9B3.7040006@unibas.ch> <374005f30607250753n288fbd81lc1b834312f953a34@mail.gmail.com> <44C63AA4.4060907@unibas.ch> <374005f30607251005u5ad2cae6ye795e09ef4b30419@mail.gmail.com> <1153854915.44c66dc3b0716@webmail.unibas.ch> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <593A0455-728A-472B-B760-0BF2252FD9F4@computer.org> Content-Transfer-Encoding: 7bit From: Thomas Clausen Date: Wed, 26 Jul 2006 08:12:29 +0200 To: Christophe.Jelger@unibas.ch X-Mailer: Apple Mail (2.752.2) X-Spam-Score: -2.6 (--) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 Cc: autoconf@ietf.org, manet Subject: [manet] Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.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: , Errors-To: manet-bounces@ietf.org Christophe, On Jul 25, 2006, at 9:15 PM, Christophe.Jelger@unibas.ch wrote: > Ian, > > See my comments inline. > > Quoting Ian Chakeres : > >> Given that these protocols are going to run over wireless interfaces >> (like IEEE 802.11), the main contributor to congestion is channel >> access (not bits). Therefore; if each protocol uses a separate packet >> it can result in a significant increase in channel access. > > ok that's something I didn't think of. However if this is the only > point in > favor of aggregation I'm afraid I'm still not really convinced. One > drawback of > aggregation is increased delay. That is, each node will have to > wait some small > amount of time (1ms?, 10ms?) to be able to aggregate packets. That depends how it is done. If you run a protocol with periodic message emissions on one node, and then that node needs to forward an "occasional" external message, you have two options" either hold the external message while you wait for your next scheduled periodic message to be up for transmission (which incurs a delay). Or you may chose to immediately generate the next periodic message and transmit this immediately with the "external" message, and then reset your periodic schedule. The devil is in the details. I believe that one detail would be that the MANET routing protocols which use periodic messages are perfectly capable of dealing with triggered "out of schedule" messages, and to reset the schedule as appropriate. Of course, one must not forget that it being *possible* to do something does not mean that it is *mandatory* to do so: if in the example given above the next periodic message was scheduled to be sent in 4 hours, it might possibly be that one would not want to reschedule, but just send the external message. But yes, making a good message scheduler that's general enough to understand these things is part of the exercise of an implementation > >> >> Let me give a simple example. OLSR will use NHDP, it will also add >> certain TLVs to NHDP for determining MPRs. OLSR will also send other >> messages. It does not really make sense to separate the two onto >> different multicast addresses or ports. >> And even more: even looking at the messages from a single nodes perspective, OLSRv2-nodes use NHDP for their local topology maintenance and will thus generate TC messages and NHDP-HELLO messages. Since HELLO messages are sent more frequently than TC messages, even a simple scheduler would say "if I am to send a TC message at the latest at deadline XXX, send it with the last HELLO message with a deadline > Continuing to add to this example, imagine that a portion of the >> network is also running DYMO and NHDP. If separate multicast groups >> were used these messages would consume even more channel access >> opportunities. >> >> One more continuation, it is likely that either reactive or proactive >> may use SMF with NHDP. Again, if a separate link-local address is >> used >> then these messages cannot be aggregated. >> >> Realistically, if a certian deployment (provider) requires each part >> of the solution to use a different multicast group this could be >> implemented, but I think the default (interoperable behavior) should >> be to use a single multicast address to reduce channel access. > > ok I understand your points but I'm just not much convinced about the > aggregation feature. Of course it's somehow elegant but I'm not > sure the extra > complexity is worth the effort. > Christophe, which complexity is it that you are worried about? The parsing of multi-message packets is something we've done in OLSR since before RFC3626. The scheduling issues, you can make a scheduler as complex as you like: taking into account aggregation in a clever way -- or as simple as you like by simply not doing aggregation. We've done that in OLSR since before RFC3626 too. >> >> Christophe, do you think we should define one default multicast >> address and one for each component? > > Well IMHO I'm still in favor of having separate multicast addresses > for e.g. > respectively DYMO, OLSRv2 and NHDP. But hey after all this is not > the most > important issue to be resolved so I won't fight very hard. ;-) I think it is important, so I will fight very hard ;) I do not see what different multicast addresses with identical scope for each component would buy us. Again, speaking with the OLSRv2-hat, I definitely would want my TC and HELLO messages to be aggregateable, and would therefore either say "thou shall send both to generic-manet- mcast-address-XXX", or say "thou shall send both to olsrv2-mcast- address-XXX", but I would *never* want to send them to different addresses. Anything that would prevent me from aggregating such TCs and HELLOs would, in my opinion, be broken. --thomas _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 26 04:20:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5ed4-0007y2-3f; Wed, 26 Jul 2006 04:20:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5ed2-0007xk-Mo; Wed, 26 Jul 2006 04:20:28 -0400 Received: from balu1.urz.unibas.ch ([131.152.1.51]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5ed0-0005jG-8U; Wed, 26 Jul 2006 04:20:28 -0400 Received: from [131.152.55.200] (baobab.cs.unibas.ch [131.152.55.200]) by balu1.urz.unibas.ch (8.13.7/8.13.7) with ESMTP id k6Q8KEKa012762; Wed, 26 Jul 2006 10:20:15 +0200 Message-ID: <44C725F2.8080006@unibas.ch> Date: Wed, 26 Jul 2006 10:21:06 +0200 From: Christophe Jelger Organization: University of Basel User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Thomas Clausen References: <374005f30607241458o5dc932ack48945384b224e22@mail.gmail.com> <44C5D9B3.7040006@unibas.ch> <374005f30607250753n288fbd81lc1b834312f953a34@mail.gmail.com> <44C63AA4.4060907@unibas.ch> <374005f30607251005u5ad2cae6ye795e09ef4b30419@mail.gmail.com> <1153854915.44c66dc3b0716@webmail.unibas.ch> <593A0455-728A-472B-B760-0BF2252FD9F4@computer.org> In-Reply-To: <593A0455-728A-472B-B760-0BF2252FD9F4@computer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SMTP-Vilter-Version: 1.3.1 X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: autoconf@ietf.org, manet Subject: [manet] Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.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: , Errors-To: manet-bounces@ietf.org Hello Thomas, Thomas Clausen wrote: > (...) > > Christophe, which complexity is it that you are worried about? The > parsing of multi-message packets is something we've done in OLSR since > before RFC3626. The scheduling issues, you can make a scheduler as > complex as you like: taking into account aggregation in a clever way -- > or as simple as you like by simply not doing aggregation. We've done > that in OLSR since before RFC3626 too. > I refered to what you mention when you say "the devil is in the details" (i.e. the aggregation scheduler). Of course parsing is not an issue. > > I think it is important, so I will fight very hard ;) > > I do not see what different multicast addresses with identical scope > for each component would buy us. Networking is about exchanging messages between interested parties. I just don't buy the idea that each MANET node will have to read and parse messages for which it might have "no interest": this sounds like spam to me. Moreover having a dedicated mcast addr per protocol is the best current practise in the ietf wgs. > Again, speaking with the OLSRv2-hat, I > definitely would want my TC and HELLO messages to be aggregateable, and > would therefore either say "thou shall send both to generic-manet- > mcast-address-XXX", or say "thou shall send both to olsrv2-mcast- > address-XXX", but I would *never* want to send them to different > addresses. At the end the draft authors (DYMO, OLSRv2, NHDP) will choose anyway what they prefer so that's why I cynically say "I won't fight very hard". > > Anything that would prevent me from aggregating such TCs and HELLOs > would, in my opinion, be broken. I realized that. > > > --thomas > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 26 04:51:38 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5f75-0004vK-8J; Wed, 26 Jul 2006 04:51:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5f74-0004vB-AS; Wed, 26 Jul 2006 04:51:30 -0400 Received: from smtp1.bae.co.uk ([20.133.0.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5f72-0000dz-TJ; Wed, 26 Jul 2006 04:51:30 -0400 Received: from ngbaux (ngbaux.msd.bae.co.uk [141.245.68.234]) by smtp1.bae.co.uk (Switch-3.1.9/Switch-3.1.9) with ESMTP id k6Q8pQD0017118; Wed, 26 Jul 2006 09:51:27 +0100 (BST) Received: from glkas0002.GREENLNK.NET ([10.15.184.52]) by ngbaux.net.bae.co.uk (PMDF V5.2-33 #44998) with ESMTP id <0J300063D63PFT@ngbaux.net.bae.co.uk>; Wed, 26 Jul 2006 09:55:01 +0100 (BST) Received: from glkms0001.GREENLNK.NET ([10.15.184.1]) by glkas0002.GREENLNK.NET with InterScan Message Security Suite; Wed, 26 Jul 2006 09:50:54 +0100 Received: from glkms0008.GREENLNK.NET ([10.15.184.8]) by glkms0001.GREENLNK.NET with Microsoft SMTPSVC(5.0.2195.6713); Wed, 26 Jul 2006 09:50:53 +0100 Date: Wed, 26 Jul 2006 09:50:53 +0100 From: "Dearlove, Christopher (UK)" To: Christophe Jelger , Thomas Clausen Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6556.0 Content-type: text/plain; charset="us-ascii" Content-transfer-encoding: quoted-printable Thread-Topic: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt Thread-Index: AcawjGFft20W25k1RROd7QR+pjcrVgAA5w1g Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 26 Jul 2006 08:50:53.0811 (UTC) FILETIME=[9A5B9430:01C6B090] X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: autoconf@ietf.org, manet Subject: [manet] RE: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.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: , Errors-To: manet-bounces@ietf.org Christophe Jelger wrote: > Thomas Clausen wrote: >> I do not see what different multicast addresses with identical scope >> for each component would buy us.=0D > Networking is about exchanging messages between interested parties. I=0D > just don't buy the idea that each MANET node will have to read and parse=0D > messages for which it might have "no interest": this sounds like spam to=0D > me. Moreover having a dedicated mcast addr per protocol is the best=0D > current practise in the ietf wgs. It is of course possible to use the same multicast address, but ignore messages you aren't interested in by using different UDP ports. (OK, you have to parse the IP and UDP headers, but not the routing protocol messages.) I'm not arguing for or against this right now, just throwing it into the mix. ******************************************************************** 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 Wed Jul 26 05:26:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5fej-0004EA-4Z; Wed, 26 Jul 2006 05:26:17 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5fei-0004Dz-Fn for manet@ietf.org; Wed, 26 Jul 2006 05:26:16 -0400 Received: from smtp102.plus.mail.re2.yahoo.com ([206.190.53.27]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G5feh-00060Y-0m for manet@ietf.org; Wed, 26 Jul 2006 05:26:16 -0400 Received: (qmail 75034 invoked from network); 26 Jul 2006 09:26:14 -0000 Received: from unknown (HELO ?192.168.200.2?) (fjrm4@83.34.174.118 with plain) by smtp102.plus.mail.re2.yahoo.com with SMTP; 26 Jul 2006 09:26:14 -0000 From: "Francisco J. Ros" Organization: University of Murcia To: manet@ietf.org Subject: Re: [manet] RE: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt Date: Wed, 26 Jul 2006 11:26:15 +0200 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607261126.16609.fjrm@dif.um.es> X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Cc: autoconf@ietf.org, "Dearlove, Christopher \(UK\)" , Thomas Clausen 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: , Errors-To: manet-bounces@ietf.org Hello, On Wednesday 26 July 2006 10:50, Dearlove, Christopher (UK) wrote: > It is of course possible to use the same multicast address, but ignore > messages you aren't interested in by using different UDP ports. (OK, > you have to parse the IP and UDP headers, but not the routing protocol > messages.) I'm not arguing for or against this right now, just throwing > it into the mix. > Assuming the same mcast address and different ports... Since we don't want OLSRv2 and NHDP messages to be disaggregated, then they should use the same port, right? Then, a node running DYMO and NHDP would process the routing messages sent by a neighbor running OLSRv2. So, even routing protocol messages are processed by nodes which aren't interested in them (unless I'm missing something). Of course, this only happens if the nodes implement NHDP, but that's quite likely. Regards, fran ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 26 06:05:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5gFl-00056O-52; Wed, 26 Jul 2006 06:04:33 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5gFi-00055y-AP; Wed, 26 Jul 2006 06:04:30 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5evi-0007Fb-Uf; Wed, 26 Jul 2006 04:39:46 -0400 Received: from mx1.cdacindia.com ([203.199.132.35] helo=mx1.cdac.in) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1G5egu-0001Vt-Bx; Wed, 26 Jul 2006 04:24:30 -0400 Received: from mailhub.cdac.in ([203.199.132.67]) by mx1.cdac.in (SAVSMTP 3.1.0.29) with SMTP id M2006072613524720137 ; Wed, 26 Jul 2006 13:52:47 +0530 Received: from mailhub.cdac.in (mailhub [196.1.109.254]) by mailhub.cdac.in (8.13.4/8.13.4) with ESMTP id k6Q8OBgl008288; Wed, 26 Jul 2006 13:54:12 +0530 From: Abhishek Misra Received: from cdac.in (localhost [127.0.0.1]) by mailhub.cdac.in (8.13.4/8.13.4) with SMTP id k6Q8OBDk008281; Wed, 26 Jul 2006 13:54:11 +0530 Date: Wed, 26 Jul 2006 13:54:11 +0530 (IST) To: "Thomas Clausen" , X-Mailer: TWIG 2.8.3 Message-ID: In-Reply-To: <593A0455-728A-472B-B760-0BF2252FD9F4@computer.org> References: <374005f30607241458o5dc932ack48945384b224e22@mail.gmail.com> <44C5D9B3.7040006@unibas.ch> <374005f30607250753n288fbd81lc1b834312f953a34@mail.gmail.com> <44C63AA4.4060907@unibas.ch> <374005f30607251005u5ad2cae6ye795e09ef4b30419@mail.gmail.com> <1153854915.44c66dc3b0716@webmail.unibas.ch>, <1153854915.44c66dc3b0716@webmail.unibas.ch> X-Spam-Score: -2.6 (--) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Cc: autoconf@ietf.org, manet Subject: [manet] Auto IP address assignment in mesh 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: , Errors-To: manet-bounces@ietf.org Hello, We are trying to develope Wireless Mesh Router[with multiple interfaces] software I wish to know if some auto ip address assignment schemes for mesh networks have been proposed. We plan to use cards in master mode to support clients on each interface and use wds links for routing and forwarding data. Thank You Abhishek Misra _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 26 06:07:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5gIj-0006ZT-3N; Wed, 26 Jul 2006 06:07:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5gIh-0006ZK-NO; Wed, 26 Jul 2006 06:07:35 -0400 Received: from smtp1.bae.co.uk ([20.133.0.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5gIe-0000XM-2E; Wed, 26 Jul 2006 06:07:35 -0400 Received: from ngbaux (ngbaux.msd.bae.co.uk [141.245.68.234]) by smtp1.bae.co.uk (Switch-3.1.9/Switch-3.1.9) with ESMTP id k6QA7Un3011122; Wed, 26 Jul 2006 11:07:30 +0100 (BST) Received: from glkas0002.GREENLNK.NET ([10.15.184.52]) by ngbaux.net.bae.co.uk (PMDF V5.2-33 #44998) with ESMTP id <0J30008MV9N6VE@ngbaux.net.bae.co.uk>; Wed, 26 Jul 2006 11:11:30 +0100 (BST) Received: from glkms0002.GREENLNK.NET ([10.15.184.2]) by glkas0002.GREENLNK.NET with InterScan Message Security Suite; Wed, 26 Jul 2006 11:07:23 +0100 Received: from glkms0008.GREENLNK.NET ([10.15.184.8]) by glkms0002.GREENLNK.NET with Microsoft SMTPSVC(5.0.2195.6713); Wed, 26 Jul 2006 11:07:22 +0100 Date: Wed, 26 Jul 2006 11:07:22 +0100 From: "Dearlove, Christopher (UK)" Subject: RE: [manet] RE: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt To: "Francisco J. Ros" , manet@ietf.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6556.0 Content-type: text/plain; charset="us-ascii" Content-transfer-encoding: quoted-printable Thread-Topic: [manet] RE: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt Thread-Index: AcawlY/5bG4fp7UXRQeHDAkfEKW/gAABZZYw Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 26 Jul 2006 10:07:22.0957 (UTC) FILETIME=[49B3AFD0:01C6B09B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac Cc: autoconf@ietf.org, Thomas Clausen 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: , Errors-To: manet-bounces@ietf.org > Assuming the same mcast address and different ports... Since we don't want=0D > OLSRv2 and NHDP messages to be disaggregated, then they should use the same=0D > port, right? Then, a node running DYMO and NHDP would process the routing=0D > messages sent by a neighbor running OLSRv2. > > So, even routing protocol messages are processed by nodes which aren't > interested in them (unless I'm missing something). Of course, this only=0D > happens if the nodes implement NHDP, but that's quite likely. This is a point I've been thinking about, to no definite conclusion. In fact it's even more complicated in one regard, but not quite as bad as the above might suggest in another. My previous comment was about if you want to separate protocol messages, different multicast addresses are one option, but different ports are another. But as you note, you may want to put them together, in which case you really want the same multicast address, and maybe the same port. I'll consider OLSRv2 and SMF, as they make the point I want to make. Both use NHDP, and NHDP sends and receives HELLO messages. But it's more than that. Assuming we don't want to duplicate messages: - The basic NHDP HELLO messages aren't sufficient for OLSRv2 or SMF. OLSRv2 needs to add WILLINGNESS and MPR TLVs. SMF may use these or (for a more interesting case) may want to add some other sort of CDS messages. So both protocols want to "decorate" the HELLO message outgoing. Note that having both in the same HELLO message should be fine. - For efficient messages, OLSRv2 would like to control the HELLO message address ordering. SMF might want to do the same, but not in the same order. This needs further consideration. - Both protocols need to see incoming HELLO messages. - OLSRv2 generates and forwards TC messages. These must be able to be piggybacked with HELLO messages in multi-message packets. (Given that in many cases the number of packets is what matters, the size of the packets is not significant, it could even be more efficient to run NHDP twice in parallel than lose this capability.) - Note that a protocol not using message type X can in fact skip that entire message reading only the type, ignoring the semantics, and the message length, and then skipping ahead by that message length. There is no need to even parse the rest of the message header. - OLSRv2 (at least) may want to suggest a rescheduling of HELLO messages to NHDP. It may want to force all addresses to be reported, in particular if its MPR Set changes. - Other scenarios to be considered are that there may be a need to add a signature to a message or packet. In both cases this needs to be the last thing done. The architecture of all this is not trivial, or at least allowing the options everyone might want isn't. In my case I would implement OLSRv2, and SMF can be treated as an extension to OLSRv2. But others may not want to do that. And I haven't even considered if DYMO wants to join the party - noting that running OLSRv2 and DYMO together is a mostly futile exercise, except on a node which reports itself as a gateway into each of two separate MANETs, one running DYMO, one running OLSRv2. ******************************************************************** 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 Wed Jul 26 06:22:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5gWu-00057C-6r; Wed, 26 Jul 2006 06:22:16 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5gWs-00056l-GS for manet@ietf.org; Wed, 26 Jul 2006 06:22:14 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5gWs-0005cE-Ea for manet@ietf.org; Wed, 26 Jul 2006 06:22:14 -0400 Received: from mx1.cdacindia.com ([203.199.132.35] helo=mx1.cdac.in) by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1G5gJ4-0003oJ-L0 for manet@ietf.org; Wed, 26 Jul 2006 06:08:00 -0400 Received: from mailhub.cdac.in ([203.199.132.67]) by mx1.cdac.in (SAVSMTP 3.1.0.29) with SMTP id M2006072615361930091 for ; Wed, 26 Jul 2006 15:36:19 +0530 Received: from mailhub.cdac.in (mailhub [196.1.109.254]) by mailhub.cdac.in (8.13.4/8.13.4) with ESMTP id k6QA7IWX027225 for ; Wed, 26 Jul 2006 15:37:18 +0530 Received: from mailhub.cdac.in (mailhub [196.1.109.254]) by mailhub.cdac.in (8.13.4/8.13.4) with ESMTP id k6Q9bIpt013995 for ; Wed, 26 Jul 2006 15:07:45 +0530 Received: from mailhub.cdac.in (mailhub [196.1.109.254]) by mailhub.cdac.in (8.13.4/8.13.4) with ESMTP id k6Q8tYXF022417 for ; Wed, 26 Jul 2006 14:25:34 +0530 From: Abhishek Misra Received: from cdac.in (localhost [127.0.0.1]) by mailhub.cdac.in (8.13.4/8.13.4) with SMTP id k6Q8tYU9022414 for ; Wed, 26 Jul 2006 14:25:34 +0530 Date: Wed, 26 Jul 2006 14:25:34 +0530 (IST) To: X-Mailer: TWIG 2.8.3 Message-ID: X-Spam-Score: -2.6 (--) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Subject: [manet] Auto IP address assignment in mesh 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: , Errors-To: manet-bounces@ietf.org Hello, We are trying to develope Wireless Mesh Router[with multiple interfaces] software I wish to know if some auto ip address assignment schemes for mesh networks have been proposed. We plan to use cards in master mode to support clients on each interface and use wds links for routing and forwarding data. Thank You Abhishek Misra _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 26 08:57:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5iwj-0005WU-A4; Wed, 26 Jul 2006 08:57:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5iwh-0005Vr-Ak for manet@ietf.org; Wed, 26 Jul 2006 08:57:03 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5ia1-00019Z-Tc for manet@ietf.org; Wed, 26 Jul 2006 08:33:37 -0400 Received: from smtpproxy2.mitre.org ([192.80.55.71] helo=smtp-mclean.mitre.org) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G5iVs-0006jn-Lm for manet@ietf.org; Wed, 26 Jul 2006 08:29:22 -0400 Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-mclean.mitre.org (8.12.11.20060308/8.12.11) with SMTP id k6QCSwoG007429 for ; Wed, 26 Jul 2006 08:28:58 -0400 Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1]) by smtp-mclean.mitre.org (Postfix) with ESMTP id B92C11BDA3 for ; Wed, 26 Jul 2006 08:28:58 -0400 (EDT) Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4]) by smtp-mclean.mitre.org (8.12.11.20060308/8.12.11) with ESMTP id k6QCSmig007320; Wed, 26 Jul 2006 08:28:48 -0400 Received: from IMCSRV2.MITRE.ORG ([129.83.20.164]) by imcfe2.MITRE.ORG with Microsoft SMTPSVC(6.0.3790.1830); Wed, 26 Jul 2006 08:28:47 -0400 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] Auto IP address assignment in mesh networks Date: Wed, 26 Jul 2006 08:28:46 -0400 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [manet] Auto IP address assignment in mesh networks Thread-Index: AcawnaQ+Sey/OSylQ4SKL9tdALsmiQAEPzIg From: "Grace, Kevin H." To: "Abhishek Misra" , X-OriginalArrivalTime: 26 Jul 2006 12:28:47.0953 (UTC) FILETIME=[0B275410:01C6B0AF] X-Spam-Score: -2.6 (--) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Cc: 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: , Errors-To: manet-bounces@ietf.org Take a look at: "A Distributed Protocol for Dynamic Address Assignment in Mobile Ad Hoc Networks", Mansi Ramakrishnan and Ravi Prakash, IEEE Transactions on Mobile Computing, January 2006=20 >-----Original Message----- >From: Abhishek Misra [mailto:abhishekm@cdac.in]=20 >Sent: Wednesday, July 26, 2006 4:56 AM >To: manet@ietf.org >Subject: [manet] Auto IP address assignment in mesh networks > > Hello, >=20 > We are trying to develope Wireless Mesh Router[with multiple=20 >interfaces] > software I wish to know if some auto ip address assignment schemes for > mesh networks have been proposed. > We plan to use cards in master mode to support clients on=20 >each interface > and use wds links for routing and forwarding data.=20 >=20 > Thank You > Abhishek Misra > > > >_______________________________________________ >manet mailing 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 Jul 26 10:13:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5k8J-0003WC-5m; Wed, 26 Jul 2006 10:13:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5k8I-0003W7-6C for manet@ietf.org; Wed, 26 Jul 2006 10:13:06 -0400 Received: from mm04snlnto.sandia.gov ([132.175.109.21] helo=sentry.sandia.gov) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5k8G-0003uk-Hn for manet@ietf.org; Wed, 26 Jul 2006 10:13:06 -0400 Received: from 132.175.109.1 by sentry.sandia.gov with ESMTP (Tumbleweed MMS SMTP Relay 01 (Email Firewall v6.2.2)); Wed, 26 Jul 2006 08:12:55 -0600 X-Server-Uuid: 4A6F66F3-3BA9-40FF-AC33-461A8279D6D5 Received: from ES23SNLNT.srn.sandia.gov (ec04snlnt.sandia.gov [134.253.164.156] (may be forged)) by mailgate.sandia.gov ( 8.13.6/8.13.6) with ESMTP id k6QECsTe000964 for ; Wed, 26 Jul 2006 08:12:55 -0600 (MDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 26 Jul 2006 08:12:54 -0600 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt (Ian Chakeres) Thread-Index: AcawjHtT1WukiRTNRqaCn7sm6qrnpgAMBGdA From: "Sholander, Peter E" To: manet@ietf.org X-TMWD-Spam-Summary: TS=20060726141255; SEV=2.0.2; DFV=A2006072606; IFV=2.0.4,4.0-8; RPD=4.00.0004; ENG=IBF; RPDID=NA; CAT=NONE; CON=NONE X-MMS-Spam-Filter-ID: A2006072606_4.00.0004_4.0-8 X-WSS-ID: 68D9A7ED1V42619654-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Subject: [manet] Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt (Ian Chakeres) 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: , Errors-To: manet-bounces@ietf.org Dear All, I didn't see any reference to NRL's previous work on the Internet MANET Encapsulation Protocol (IMEP). That vintage (1997?) MANET I-D was intended to deal with the problem that "the main contributor to congestion is channel access (not bits)." Has that IMEP work been discussed again and discarded recently? Or just "lost in the mists" at this point. --Pete Sholander Sandia National Laboratories P.O. Box 5800, M/S 0672 Albuquerque, New Mexico 87185-0672 v: 505-844-0646 e: peshola@sandia.gov -----Original Message----- From: manet-request@ietf.org [mailto:manet-request@ietf.org]=20 Sent: Wednesday, July 26, 2006 2:21 AM To: manet@ietf.org Subject: manet Digest, Vol 27, Issue 15 Send manet mailing list submissions to manet@ietf.org To subscribe or unsubscribe via the World Wide Web, visit https://www1.ietf.org/mailman/listinfo/manet or, via email, send a message with subject or body 'help' to manet-request@ietf.org You can reach the person managing the list at manet-owner@ietf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of manet digest..." Today's Topics: 1. Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt (Ian Chakeres) 2. Re: Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt (Francisco J. Ros) 3. Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt (Christophe.Jelger@unibas.ch) 4. Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt (Thomas Clausen) 5. Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt (Christophe Jelger) ---------------------------------------------------------------------- Message: 1 Date: Tue, 25 Jul 2006 10:05:46 -0700 From: "Ian Chakeres" Subject: [manet] Re: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt To: "Christophe Jelger" Cc: autoconf@ietf.org, manet Message-ID: <374005f30607251005u5ad2cae6ye795e09ef4b30419@mail.gmail.com> Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed Given that these protocols are going to run over wireless interfaces (like IEEE 802.11), the main contributor to congestion is channel access (not bits). Therefore; if each protocol uses a separate packet it can result in a significant increase in channel access. Let me give a simple example. OLSR will use NHDP, it will also add certain TLVs to NHDP for determining MPRs. OLSR will also send other messages. It does not really make sense to separate the two onto different multicast addresses or ports. Continuing to add to this example, imagine that a portion of the network is also running DYMO and NHDP. If separate multicast groups were used these messages would consume even more channel access opportunities. One more continuation, it is likely that either reactive or proactive may use SMF with NHDP. Again, if a separate link-local address is used then these messages cannot be aggregated. Realistically, if a certian deployment (provider) requires each part of the solution to use a different multicast group this could be implemented, but I think the default (interoperable behavior) should be to use a single multicast address to reduce channel access. Christophe, do you think we should define one default multicast address and one for each component? Ian Chakeres _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 26 11:25:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5lGB-0008SX-EL; Wed, 26 Jul 2006 11:25:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5lGA-0008SR-05 for manet@ietf.org; Wed, 26 Jul 2006 11:25:18 -0400 Received: from che.ojctech.com ([64.198.255.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5lG8-0003WW-M9 for manet@ietf.org; Wed, 26 Jul 2006 11:25:17 -0400 Received: from che.ojctech.com (localhost [127.0.0.1]) by che.ojctech.com (8.12.8/8.12.8) with ESMTP id k6QFPGQV030984 for ; Wed, 26 Jul 2006 10:25:16 -0500 Received: (from dyoung@localhost) by che.ojctech.com (8.12.8/8.12.8/Submit) id k6QFPGR8030982 for manet@ietf.org; Wed, 26 Jul 2006 10:25:16 -0500 Date: Wed, 26 Jul 2006 10:25:15 -0500 From: David Young To: manet Subject: Re: [manet] RE: [Autoconf] Fwd: I-D ACTION:draft-chakeres-manet-iana-00.txt Message-ID: <20060726152515.GJ8159@che.ojctech.com> Mail-Followup-To: manet References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a 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: , Errors-To: manet-bounces@ietf.org On Wed, Jul 26, 2006 at 09:50:53AM +0100, Dearlove, Christopher (UK) wrote: > > Christophe Jelger wrote: > > Thomas Clausen wrote: > >> I do not see what different multicast addresses with identical scope > > >> for each component would buy us. > > > Networking is about exchanging messages between interested parties. I > > just don't buy the idea that each MANET node will have to read and > parse > > messages for which it might have "no interest": this sounds like spam > to > > me. Moreover having a dedicated mcast addr per protocol is the best > > current practise in the ietf wgs. > > It is of course possible to use the same multicast address, but ignore > messages you aren't interested in by using different UDP ports. (OK, The difference here is that the NIC's multicast filter may operate without the host computer even being "awake," but the host CPU will ordinarily be involved in UDP filtering. The difference in power consumption and processing overhead may be substantial. Then again, maybe not. This is the kind of thing someone could test in the lab. 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 Wed Jul 26 11:59:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5lmt-0002hl-O6; Wed, 26 Jul 2006 11:59:07 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5lms-0002dK-GQ; Wed, 26 Jul 2006 11:59:06 -0400 Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5lms-00063Y-5b; Wed, 26 Jul 2006 11:59:06 -0400 Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.13.6+Sun/8.12.8) with SMTP id k6QFwUZw028094; Wed, 26 Jul 2006 11:58:36 -0400 (EDT) Received: (from SEXTANT [132.250.92.22]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.12.43) with SMTP id M2006072611591023547 ; Wed, 26 Jul 2006 11:59:10 -0400 From: "Joe Macker" To: "'Dearlove, Christopher \(UK\)'" , "'Francisco J. Ros'" , Subject: RE: [manet] RE: [Autoconf] Fwd: I-DACTION:draft-chakeres-manet-iana-00.txt Date: Wed, 26 Jul 2006 11:58:33 -0400 Message-ID: <008e01c6b0cc$588bc610$165cfa84@SEXTANT> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 In-Reply-To: Thread-Index: AcawlY/5bG4fp7UXRQeHDAkfEKW/gAABZZYwAAwEkoA= X-Spam-Score: 0.0 (/) X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c Cc: autoconf@ietf.org, 'Thomas Clausen' 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: , Errors-To: manet-bounces@ietf.org Chris: I just want to clarify that SMF has three neighborhood discovery modes defined in -02. The writeup below sounds like its always required to run NHDP separately. So SMF does not need to see HELLOs in mode (2) or (1) just for clarification. (3) would be updated to reference NHDP and related TLVs as you mention for independent operation. The present prototype implementations often run in (2) mode which means OLSRv2 or MANET-OSPF,etc would run the neighborhood discovery and the appropriate optimized CDS (e.g., MPR) information would be shared. With respect to neighborhood topology knowledge and/or discovery, there are three basic modes of SMF operation: 1. Classical Flooding (CF) mode with no requirement for discovery or knowledge of neighborhood topology, 2. External control mode where an external process dynamically sets the local SMF relay status (e.g., Early SMF prototypes have leveraged neighborhood toplogy information collected by MANET unicast routing protocols such as OLSRv2 or Manet-OSPF ), and 3. Independent operating mode using a neighborhood discovery ("hello") protocol to collect the local topology information required for the various CDS algorithm modes discussed in the Appendices. >-----Original Message----- >From: Dearlove, Christopher (UK) >[mailto:chris.dearlove@baesystems.com] >Sent: Wednesday, July 26, 2006 6:07 AM >To: Francisco J. Ros; manet@ietf.org >Cc: autoconf@ietf.org; Thomas Clausen >Subject: RE: [manet] RE: [Autoconf] Fwd: >I-DACTION:draft-chakeres-manet-iana-00.txt > > >> Assuming the same mcast address and different ports... Since we don't >want > >> OLSRv2 and NHDP messages to be disaggregated, then they >should use the >same > >> port, right? Then, a node running DYMO and NHDP would process the >routing > >> messages sent by a neighbor running OLSRv2. >> >> So, even routing protocol messages are processed by nodes >which aren't > >> interested in them (unless I'm missing something). Of course, this >only > >> happens if the nodes implement NHDP, but that's quite likely. > >This is a point I've been thinking about, to no definite conclusion. >In fact it's even more complicated in one regard, but not >quite as bad as the above might suggest in another. > >My previous comment was about if you want to separate protocol >messages, different multicast addresses are one option, but >different ports are another. But as you note, you may want to >put them together, in which case you really want the same >multicast address, and maybe the same port. > >I'll consider OLSRv2 and SMF, as they make the point I want to make. >Both use NHDP, and NHDP sends and receives HELLO messages. But >it's more than that. Assuming we don't want to duplicate messages: > >- The basic NHDP HELLO messages aren't sufficient for OLSRv2 or SMF. > OLSRv2 needs to add WILLINGNESS and MPR TLVs. SMF may use these or > (for a more interesting case) may want to add some other sort of > CDS messages. So both protocols want to "decorate" the HELLO message > outgoing. Note that having both in the same HELLO message should be > fine. > >- For efficient messages, OLSRv2 would like to control the HELLO > message address ordering. SMF might want to do the same, but not > in the same order. This needs further consideration. > >- Both protocols need to see incoming HELLO messages. > >- OLSRv2 generates and forwards TC messages. These must be able > to be piggybacked with HELLO messages in multi-message packets. > (Given that in many cases the number of packets is what matters, > the size of the packets is not significant, it could even be more > efficient to run NHDP twice in parallel than lose this capability.) > >- Note that a protocol not using message type X can in fact skip that > entire message reading only the type, ignoring the semantics, and > the message length, and then skipping ahead by that message length. > There is no need to even parse the rest of the message header. > >- OLSRv2 (at least) may want to suggest a rescheduling of HELLO > messages to NHDP. It may want to force all addresses to be > reported, in particular if its MPR Set changes. > >- Other scenarios to be considered are that there may be a need to > add a signature to a message or packet. In both cases this needs > to be the last thing done. > >The architecture of all this is not trivial, or at least >allowing the options everyone might want isn't. In my case I >would implement OLSRv2, and SMF can be treated as an extension >to OLSRv2. But others may not want to do that. And I haven't >even considered if DYMO wants to join the party - noting that >running OLSRv2 and DYMO together is a mostly futile exercise, >except on a node which reports itself as a gateway into each >of two separate MANETs, one running DYMO, one running OLSRv2. > > >******************************************************************** >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. >******************************************************************** > >_______________________________________________ >Autoconf mailing list >Autoconf@ietf.org >https://www1.ietf.org/mailman/listinfo/autoconf > _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Wed Jul 26 12:12:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5lzW-0002lX-8V; Wed, 26 Jul 2006 12:12:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5lzU-0002l9-Gc; Wed, 26 Jul 2006 12:12:08 -0400 Received: from smtp1.bae.co.uk ([20.133.0.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5lzT-0007Pe-3n; Wed, 26 Jul 2006 12:12:08 -0400 Received: from ngbaux (ngbaux.msd.bae.co.uk [141.245.68.234]) by smtp1.bae.co.uk (Switch-3.1.9/Switch-3.1.9) with ESMTP id k6QGBugi018848; Wed, 26 Jul 2006 17:12:05 +0100 (BST) Received: from glkas0002.GREENLNK.NET ([10.15.184.52]) by ngbaux.net.bae.co.uk (PMDF V5.2-33 #44998) with ESMTP id <0J30000KXQIPK5@ngbaux.net.bae.co.uk>; Wed, 26 Jul 2006 17:16:01 +0100 (BST) Received: from glkms0002.GREENLNK.NET ([10.15.184.2]) by glkas0002.GREENLNK.NET with InterScan Message Security Suite; Wed, 26 Jul 2006 17:11:53 +0100 Received: from glkms0008.GREENLNK.NET ([10.15.184.8]) by glkms0002.GREENLNK.NET with Microsoft SMTPSVC(5.0.2195.6713); Wed, 26 Jul 2006 17:11:53 +0100 Date: Wed, 26 Jul 2006 17:11:51 +0100 From: "Dearlove, Christopher (UK)" Subject: RE: [manet] RE: [Autoconf] Fwd: I-DACTION:draft-chakeres-manet-iana-00.txt To: Joe Macker , "Francisco J. Ros" , manet@ietf.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft Exchange V6.0.6556.0 Content-type: text/plain; charset="us-ascii" Content-transfer-encoding: quoted-printable Thread-Topic: [manet] RE: [Autoconf] Fwd: I-DACTION:draft-chakeres-manet-iana-00.txt Thread-Index: AcawlY/5bG4fp7UXRQeHDAkfEKW/gAABZZYwAAwEkoAAAFOMEA== Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: X-OriginalArrivalTime: 26 Jul 2006 16:11:53.0297 (UTC) FILETIME=[3570BC10:01C6B0CE] X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: autoconf@ietf.org, Thomas Clausen 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: , Errors-To: manet-bounces@ietf.org > I just want to clarify that SMF has three neighborhood discovery modes > defined in -02. The writeup below sounds like its always required to run > NHDP separately. So SMF does not need to see HELLOs in mode (2) or (1) just > for clarification. Thanks for that. I was of course just considering your case (3), as it's the one that poses the biggest challenges. But (partly because it wasn't relevant to my point, and partly because I'd forgotten all were actually defined in SMF -02) I didn't spell that out. But for case (3) there are the challenges I noted (or at least I think there are - simplification without loss of capability very welcome). > 1. Classical Flooding (CF) mode with no requirement for discovery or > knowledge of neighborhood topology, > > 2. External control mode where an external process dynamically sets > the local SMF relay status (e.g., Early SMF prototypes have > leveraged neighborhood toplogy information collected by MANET > unicast routing protocols such as OLSRv2 or Manet-OSPF ), and I think something got lost here, but nothing critical to this point. > 3. Independent operating mode using a neighborhood discovery > ("hello") protocol to collect the local topology information > required for the various CDS algorithm modes discussed in the > Appendices.=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 Wed Jul 26 12:14:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5m1t-0003pS-8J; Wed, 26 Jul 2006 12:14:37 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5m1s-0003pN-80 for manet@ietf.org; Wed, 26 Jul 2006 12:14:36 -0400 Received: from smtp104.biz.mail.mud.yahoo.com ([68.142.200.252]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G5m1r-0007bz-LW for manet@ietf.org; Wed, 26 Jul 2006 12:14:36 -0400 Received: (qmail 59886 invoked from network); 26 Jul 2006 16:07:55 -0000 Received: from unknown (HELO YEOBS) (boonsain.yeo@sensimesh.com@218.186.174.131 with login) by smtp104.biz.mail.mud.yahoo.com with SMTP; 26 Jul 2006 16:07:53 -0000 Message-ID: <03df01c6b0cd$a4525040$6901a8c0@Wavex.com> From: "Boon Sain Yeo" To: Date: Thu, 27 Jul 2006 00:07:46 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Score: 1.0 (+) X-Scan-Signature: 16a2b98d831858659c646b3dec9ed22b Subject: [manet] CFP - ISWPC 2007, San Juan, Pureto Rico 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="===============0353309631==" Errors-To: manet-bounces@ietf.org This is a multi-part message in MIME format. --===============0353309631== Content-Type: multipart/alternative; boundary="----=_NextPart_000_03DC_01C6B110.B09648F0" This is a multi-part message in MIME format. ------=_NextPart_000_03DC_01C6B110.B09648F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable (Apologies if you receive multiple copies of this message) ---------------------------------------------------------------------- International Symposium on Wireless Pervasive Computing 2007 (ISWPC 2007) 5-7 February 2007, San Juan, Puerto Rico, USA http://www.iswpc.org/2007/ Technically Sponsored By: IEEE Communications Society and IEEE Vehicular Technology Society Hosted By: University of Puerto Rico at Mayaguez *** Submission Deadline -- August 20, 2006 **** ---------------------------------------------------------------------- SCOPE Wireless pervasive computing is a rapidly growing area that has = attracted=20 significant attention due to its potential impact on the quality of=20 lifestyles of individuals. To enable wireless pervasive computing, it is = necessary to integrate technologies from the fields of communications,=20 signal processing, distributed computing, and numerous other fields. The = aim=20 of this symposium is to provide a platform for researchers in the area = of=20 wireless pervasive computing and related areas to showcase their = results,=20 launch new ideas, as well as to interact with colleagues from these = areas. The scope of the symposium covers all enabling technologies of wireless=20 pervasive computing. This includes a huge variety of topics ranging from = wireless communications and networking to services and applications of=20 pervasive computing. A series of panel and tutorials will also seek to=20 inform and invoke interaction among researchers which are interested in = this=20 area. ---------------------------------------------------------------------- TOPICS OF INTEREST (INCLUDE BUT ARE NOT LIMITED TO THE FOLLOWING) - Ad hoc networks - Air interfaces (e.g. CDMA, OFDM, TDMA) - Bluetooth technologies - Coding and modulation techniques - Cognitive radio - Cooperative communications technologies - Cross-layer design - Detection and estimation - Diversity techniques & equalization - Dynamic spectrum management - Healthcare applications - Hybrid wireless networks - Interference avoidance - Interoperation of WLAN and other wireless systems - Localization and tracking techniques - Location management techniques Middleware - MIMO systems - Multimedia systems - Multirate and multicarrier communications - Multi-user Detection - PCS, GPRS, EDGE, 3GPP, UMTS, GSM and B3G systems - Power control Programmable radio - Propagation and channel characterization - QoS Support in wireless systems - Resource management and interference management - RF systems Security applications - Signal processing - Signal separation and interference rejection - Speech and video processing - Switching and routing techniques - UWB - Wearable devices - WiMAX - Wireless access techniques - Wireless multicasting - Wireless multimedia - Wireless network architecture - Wireless security - Wireless sensor networks - Wireless systems design - WLANs and WPANs ---------------------------------------------------------------------- PAPER SUBMISSION GUIDELINES Acceptance will be based on an extended abstract of about 1500 words = (two=20 pages in the standard IEEE conference format). The extended abstract = should=20 include diagrams, initial results, and details required for the = reviewers to=20 assess the contribution of your work. A short summary of approximately = 150=20 words is also required at the time of submission of the extended = abstract.=20 Extended abstracts must be submitted electronically by August 20, 2006 , = via=20 EDAS (http://edas.info). Proceedings of the conference will be available = on=20 IEEE Xplore after the event. ---------------------------------------------------------------------- PANEL SESSIONS & TUTORIALS Proposals for Tutorial and Panel Sessions are also being solicited.=20 Tutorials (half-day or full-day sessions) are intended to provide = in-depth=20 learning on a specific topic of interest to the participants. Panel = sessions=20 are 60 minutes long. They present leaders in a particular area = discussing a=20 topic of interest within the scope of the symposium. Proposals for = Tutorials=20 and Panel sessions should consist of 1000 words summary, a 150 word=20 abstract, and a cover page listing the details of the author(s). For = further=20 details, please contact either the Tutorial Chair, Prof. Xiaoyan Hong=20 (hxy@cs.ua.edu), or Panel Chair, Prof. Wilson Rivera = (wrivera@ece.uprm.edu). ---------------------------------------------------------------------- IMPORTANT DATES Submission of Papers, proposals for tutorials and panel sessions: =3D> August 20, 2006 Notification of Acceptance: =3D> October 1, 2006 Submission of camera-ready versions of accepted papers: =3D> November 18, 2006 ---------------------------------------------------------------------- http://www.iswpc.org/2007/ ---------------------------------------------------------------------- ------=_NextPart_000_03DC_01C6B110.B09648F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
(Apologies if=20 you receive multiple copies of this=20 message)

---------------------------------------------------------= -------------
International=20 Symposium on Wireless Pervasive Computing=20 2007
           = ;          =20 (ISWPC 2007)

         5-7 = February 2007, San Juan, Puerto Rico,=20 USA
           =      =20 http://www.iswpc.org/2007/


          &nbs= p;        =20 Technically Sponsored By:
IEEE Communications Society and IEEE = Vehicular=20 Technology = Society

        =20 Hosted By: University of Puerto Rico at=20 Mayaguez

      *** Submission = Deadline =20 --  August 20, 2006=20 ****

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

SCOPE

Wireless=20 pervasive computing is a rapidly growing area that has attracted =
significant=20 attention due to its potential impact on the quality of
lifestyles = of=20 individuals. To enable wireless pervasive computing, it is
necessary = to=20 integrate technologies from the fields of communications,
signal = processing,=20 distributed computing, and numerous other fields. The aim
of this = symposium=20 is to provide a platform for researchers in the area of
wireless = pervasive=20 computing and related areas to showcase their results,
launch new = ideas, as=20 well as to interact with colleagues from these areas.

The scope = of the=20 symposium covers all enabling technologies of wireless
pervasive = computing.=20 This includes a huge variety of topics ranging from
wireless = communications=20 and networking to services and applications of
pervasive computing. = A series=20 of panel and tutorials will also seek to
inform and invoke = interaction among=20 researchers which are interested in this=20
area.

--------------------------------------------------------= --------------
TOPICS=20 OF INTEREST (INCLUDE BUT ARE NOT LIMITED TO THE FOLLOWING)

- Ad = hoc=20 networks
- Air interfaces (e.g. CDMA, OFDM, TDMA)
- Bluetooth=20 technologies
- Coding and modulation techniques
- Cognitive = radio
-=20 Cooperative communications technologies
- Cross-layer design
- = Detection=20 and estimation
- Diversity techniques & equalization
- Dynamic = spectrum management
- Healthcare applications
- Hybrid wireless=20 networks
- Interference avoidance
- Interoperation of WLAN and = other=20 wireless systems
- Localization and tracking techniques
- Location = management techniques Middleware
- MIMO systems
- Multimedia = systems
-=20 Multirate and multicarrier communications
- Multi-user Detection
- = PCS,=20 GPRS, EDGE, 3GPP, UMTS, GSM and B3G systems
- Power control = Programmable=20 radio
- Propagation and channel characterization
- QoS Support in = wireless=20 systems
- Resource management and interference management
- RF = systems=20 Security applications
- Signal processing
- Signal separation and=20 interference rejection
- Speech and video processing
- Switching = and=20 routing techniques
- UWB
- Wearable devices
- WiMAX
- = Wireless=20 access techniques
- Wireless multicasting
- Wireless = multimedia
-=20 Wireless network architecture
- Wireless security
- Wireless = sensor=20 networks
- Wireless systems design
- WLANs and=20 WPANs

------------------------------------------------------------= ----------
PAPER=20 SUBMISSION GUIDELINES

Acceptance will be based on an extended = abstract of=20 about 1500 words (two
pages in the standard IEEE conference format). = The=20 extended abstract should
include diagrams, initial results, and = details=20 required for the reviewers to
assess the contribution of your work. = A short=20 summary of approximately 150
words is also required at the time of=20 submission of the extended abstract.
Extended abstracts must be = submitted=20 electronically by August 20, 2006 , via
EDAS (http://edas.info). Proceedings of the conference will = be available=20 on
IEEE Xplore after the=20 event.

-----------------------------------------------------------= -----------
PANEL=20 SESSIONS & TUTORIALS

Proposals for Tutorial and Panel = Sessions are=20 also being solicited.
Tutorials (half-day or full-day sessions) are = intended=20 to provide in-depth
learning on a specific topic of interest to the=20 participants. Panel sessions
are 60 minutes long. They present = leaders in a=20 particular area discussing a
topic of interest within the scope of = the=20 symposium. Proposals for Tutorials
and Panel sessions should consist = of 1000=20 words summary, a 150 word
abstract, and a cover page listing the = details of=20 the author(s). For further
details, please contact either the = Tutorial=20 Chair, Prof. Xiaoyan Hong
(hxy@cs.ua.edu), or Panel=20 Chair, Prof. Wilson Rivera (wrivera@ece.uprm.edu).

------------------------------------------------------= ----------------
IMPORTANT=20 DATES

Submission of Papers, proposals for tutorials and panel=20 sessions:
=3D>  August 20, 2006
Notification of=20 Acceptance:
=3D>  October 1, 2006
Submission of = camera-ready=20 versions of accepted papers:
=3D>  November 18,=20 2006

-------------------------------------------------------------= ---------
          =             &= nbsp;=20 http://www.iswpc.org/2007/
----------------------------------------------------------------= ------



------=_NextPart_000_03DC_01C6B110.B09648F0-- --===============0353309631== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============0353309631==-- From manet-bounces@ietf.org Fri Jul 28 01:41:40 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6L69-0006Bp-8J; Fri, 28 Jul 2006 01:41:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6L66-0006Bk-S6 for manet@ietf.org; Fri, 28 Jul 2006 01:41:18 -0400 Received: from web56710.mail.re3.yahoo.com ([66.196.97.69]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G6L65-0005Rv-K4 for manet@ietf.org; Fri, 28 Jul 2006 01:41:18 -0400 Received: (qmail 61184 invoked by uid 60001); 28 Jul 2006 05:41:17 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=LABR5L6KST2KjD1btv7Ro3SJW6d/b1LF8YSahRQ0ZgHibz0w9rSCip/NuyL1FvNYH/ro++KCw7ebwKjKwvIIwd1273sEum3SA+tqV/Tsk6CLgt2a3GXR40eZ1YMN0ql9eIYjiPEejV0Yyzv4pznfdpx0BnJKXI1pv6CgjSMVb0o= ; Message-ID: <20060728054117.61182.qmail@web56710.mail.re3.yahoo.com> Received: from [203.92.36.18] by web56710.mail.re3.yahoo.com via HTTP; Thu, 27 Jul 2006 22:41:17 PDT Date: Thu, 27 Jul 2006 22:41:17 -0700 (PDT) From: Parag Goswami To: manet@ietf.org MIME-Version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Subject: [manet] SOAP protocol material 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="===============1870237894==" Errors-To: manet-bounces@ietf.org --===============1870237894== Content-Type: multipart/alternative; boundary="0-354666057-1154065277=:59969" Content-Transfer-Encoding: 8bit --0-354666057-1154065277=:59969 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Dear members, Can anyone please share with me some tutorials on SOAP protocol and its implementation to establish connection with the web services servers through Java or any other implementation if done to search the organisations that are involved with it. Thanks and regards, Parag Goswami --------------------------------- How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call rates. --0-354666057-1154065277=:59969 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Dear members,
Can anyone please share with me some tutorials on SOAP protocol and its implementation to establish connection with the web services servers through Java or any other implementation if done to search the organisations that are involved with it.

Thanks and regards,
Parag Goswami

How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call rates. --0-354666057-1154065277=:59969-- --===============1870237894== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --===============1870237894==-- From manet-bounces@ietf.org Fri Jul 28 06:18:11 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6PPi-000383-JU; Fri, 28 Jul 2006 06:17:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6PPh-00037x-Kv for manet@ietf.org; Fri, 28 Jul 2006 06:17:49 -0400 Received: from mx1.cdacindia.com ([203.199.132.35] helo=mx1.cdac.in) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G6PPg-0005pE-DM for manet@ietf.org; Fri, 28 Jul 2006 06:17:49 -0400 Received: from mailhub.cdac.in ([203.199.132.67]) by mx1.cdac.in (SAVSMTP 3.1.0.29) with SMTP id M2006072815461101335 for ; Fri, 28 Jul 2006 15:46:11 +0530 Received: from mailhub.cdac.in (mailhub [196.1.109.254]) by mailhub.cdac.in (8.13.4/8.13.4) with ESMTP id k6SAHiWg031465 for ; Fri, 28 Jul 2006 15:47:44 +0530 From: Abhishek Misra Received: from cdac.in (localhost [127.0.0.1]) by mailhub.cdac.in (8.13.4/8.13.4) with SMTP id k6SAHh9P031457 for ; Fri, 28 Jul 2006 15:47:43 +0530 Date: Fri, 28 Jul 2006 15:47:43 +0530 (IST) To: X-Mailer: TWIG 2.8.3 Message-ID: X-Spam-Score: 0.1 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Subject: [manet] obtaining IP of roaming client 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: , Errors-To: manet-bounces@ietf.org Hello, I have been trying to obtain ip of roaming client with little success. I tried with icmp messages client [192.168.6.100] ap1 [192.168.6.1/24] ap2 [192.168.5.1/24] client is first associated with ap1 it then moves and assiciates with ap2 I need to obtain ip of client at ap2 I sent broadcast ping -b 255.255.255.255 but client did not respond tcpdump at client did show icmp requests but client did not generate icmp reaponse. default gw is configured on the client is not changed I wish to know why did client not generate icmp reply going through the icmp rfc I did not find that a node is not supposed to respond to icmp echo if subet of source is different than its own. all suggestions are welcome _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Jul 28 07:55:00 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6Qvc-0006lR-P3; Fri, 28 Jul 2006 07:54:52 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6Qvb-0006lL-2z for manet@ietf.org; Fri, 28 Jul 2006 07:54:51 -0400 Received: from thsmsgxrt12p.thalesgroup.com ([192.54.144.135]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6QvZ-0003uR-QC for manet@ietf.org; Fri, 28 Jul 2006 07:54:51 -0400 Received: from thsmsgirt23p.corp.thales (unknown [10.33.231.7]) by thsmsgxrt12p.thalesgroup.com (Postfix) with ESMTP id 8B573449C7 for ; Fri, 28 Jul 2006 13:54:48 +0200 (CEST) Received: from [10.33.231.31] (10.33.231.31) by thsmsgirt23p.corp.thales (7.2.055.4) id 44447CD9013D14E6 for manet@ietf.org; Fri, 28 Jul 2006 13:54:55 +0200 Received: from (10.33.231.2) by via smtp id 5ab5_dea87a88_1e2f_11db_9fde_001143d32df6; Fri, 28 Jul 2006 11:54:47 +0000 (UTC) Received: from NODALNET.clb.tcfr.thales (unknown [10.33.8.19]) by thsmsgirt12p.corp.thales (Postfix) with ESMTP id 77C2D3C01A for ; Fri, 28 Jul 2006 13:54:48 +0200 (CEST) Received: by nodalnet.clb.tcfr.thales with Internet Mail Service (5.5.2653.19) id ; Fri, 28 Jul 2006 13:54:48 +0200 Message-ID: <66CE949D18BCB249ABE8D9AF48C4F1CE079FF2CC@helios.clb.tcfr.thales> From: Jeremie.LEGUAY@fr.thalesgroup.com To: manet@ietf.org Date: Fri, 28 Jul 2006 13:54:52 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 2.0 (++) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Subject: [manet] XIAN version 1.0 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: , Errors-To: manet-bounces@ietf.org Dear all, We are glad to inform you that we have just released XIAN. The project = website is located at http://xian.sourceforge.net/ XIAN (Cross-layer Interface for wireless Ad hoc Networks) is a generic = interface for experimenting cross-layer designs with legacy 802.11 = networking cards using the MadWifi driver on Linux plateforms. The code = is freely accessible under the GPL license.=20 XIAN can be used as a service by other network layers or system = components to access information about configuration and performance of = MAC/PHY layers. The interface is fully implemented and is available for = Linux over the MadWifi 802.11 driver.=20 Contributions to this project are welcome, they can be done in = collaboration with the XIAN core developement team. Please do not hesitate to send us any comments or feedback. Best Regards, ------------------------------------------------------------------------= ------------- Herv=E9 AIACHE & J=E9r=E9mie LEGUAY THALES Architecture Framework Centre TAI Laboratory (TAF-Centre/TAI) 160 Bd de valmy - BP 82 - 92704 Colombes Cedex France Phone: +33(0)1 46 13 33 83 - Fax: +33(0)1 46 13 26 86 ------------------------------------------------------------------------= ------------- _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Jul 28 12:03:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6Una-0000N3-G6; Fri, 28 Jul 2006 12:02:50 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6UnY-0000Ms-3c for manet@ietf.org; Fri, 28 Jul 2006 12:02:48 -0400 Received: from gweb.hope.ac.uk ([194.81.33.61] helo=icrit1.hope.ac.uk) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1G6UnW-00011Y-N0 for manet@ietf.org; Fri, 28 Jul 2006 12:02:48 -0400 Received: (qmail 1758 invoked from network); 28 Jul 2006 16:02:44 -0000 Received: from localhost (127.0.0.1) by icrit1.hope.ac.uk with SMTP; 28 Jul 2006 16:02:44 -0000 Received: from icrit1.hope.ac.uk ([127.0.0.1]) by localhost (icrit1.hope.ac.uk [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 01294-02 for ; Fri, 28 Jul 2006 17:02:43 +0100 (BST) Received: (qmail 1749 invoked by uid 510); 28 Jul 2006 16:02:43 -0000 Received: from [172.16.0.61] (HELO gweb.hope.ac.uk) (172.16.0.61) by icrit1.hope.ac.uk (qpsmtpd/0.28) with ESMTP; Fri, 28 Jul 2006 17:02:43 +0100 Received: from R1DOM-MTA by gweb.hope.ac.uk with Novell_GroupWise; Fri, 28 Jul 2006 17:02:43 +0100 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.3 Date: Fri, 28 Jul 2006 17:02:28 +0100 From: "ADRIAN J PULLIN" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by iCritical at icrit1.hope.ac.uk X-Spam-Score: 0.0 (/) X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4 Subject: [manet] Re: manet Digest, Vol 27, Issue 18 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: , Errors-To: manet-bounces@ietf.org I am on leave until 7th August. I'll deal with work related messages when I return. Cheers _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Fri Jul 28 16:00:10 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6YUo-0005mz-Se; Fri, 28 Jul 2006 15:59:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6YUj-0005ZS-Hr; Fri, 28 Jul 2006 15:59:37 -0400 Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6YUi-0007IP-9g; Fri, 28 Jul 2006 15:59:37 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k6SJo1p0023417 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Jul 2006 19:50:02 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1G6YLR-0003zN-OY; Fri, 28 Jul 2006 15:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Fri, 28 Jul 2006 15:50:01 -0400 X-Spam-Score: 0.3 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Cc: manet@ietf.org Subject: [manet] I-D ACTION:draft-ietf-manet-packetbb-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: , Errors-To: manet-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF. Title : Generalized MANET Packet/Message Format Author(s) : T. Clausen, et al. Filename : draft-ietf-manet-packetbb-02.txt Pages : 35 Date : 2006-7-28 This document specifies a multi-message packet format that may be used by mobile ad hoc network routing and other protocols. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-manet-packetbb-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-manet-packetbb-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-manet-packetbb-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-7-28113005.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-manet-packetbb-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-manet-packetbb-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-7-28113005.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet --NextPart-- From manet-bounces@ietf.org Mon Jul 31 14:41:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7cho-0008IX-0G; Mon, 31 Jul 2006 14:41:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7chm-0008IF-DG for manet@ietf.org; Mon, 31 Jul 2006 14:41:30 -0400 Received: from picton.eecg.toronto.edu ([128.100.10.141]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G7chk-0005GM-Hj for manet@ietf.org; Mon, 31 Jul 2006 14:41:30 -0400 Received: from isis.eecg.toronto.edu (jacobsen@isis.eecg.toronto.edu [128.100.10.128]) by picton.eecg.toronto.edu (8.13.6/8.13.6) with ESMTP id k6VIfRpp011565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 31 Jul 2006 14:41:27 -0400 (EDT) Date: Mon, 31 Jul 2006 14:41:25 -0400 (EDT) From: "H.-Arno Jacobsen" X-X-Sender: jacobsen@isis.eecg.toronto.edu To: manet@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b7d60495f1a7f2e853e8cbae7e6dbfc Subject: [manet] CFP: 8th International Conference on Mobile Data Management (MDM'07) 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: , Errors-To: manet-bounces@ietf.org ========================================================================== PRELIMINARY CALL FOR PAPERS 8th International Conference on Mobile Data Management (MDM'07) Mannheim, Germany, May 7-11, 2007 http://mdm2007.uni-mannheim.de In Cooperation with ACM SIGMOD/SIGMOBILE (pending), IEEE CS (pending) and Infos ========================================================================== SCOPE: The rapid advances in computing and wireless communication technologies along with their integration into commodity devices such as personal digital assistants, mobile phones, and portable computers provide a technical infrastructure that enables a broad range of mobile services and applications. These include scenarios where seamless access to a computing infrastructure is provided, scenarios where interaction and data sharing among mobile users occur in mobile ad hoc networks, and hybrid scenarios that combine these two. The continued miniaturization of computing devices along with improvements in the performance/price ratio enable new services and applications, e.g., in environmental monitoring and transportation. Although substantial research has been conducted, this area remains ripe with open research challenges, e.g., in relation to context-aware computing, such as location-based services or ubiquitous computing applications; mobile applications in hybrid networks; and consistency and data processing in sensor networks. The conference focuses on research contributions within data management in relation to mobile, wearable, and pervasive computing. The conference invites submissions within this area. Topics of interest include, but are not limited to, the following. TOPICS OF INTEREST: * Theoretical foundations of data-intensive mobile computing * Location and mobility semantics * Data placement, caching, replication and relocation to support mobility * Data dissemination in mobile environments * Data presentation, scripting and exchange languages * Data management for pervasive computing * Data management in sensor networks * Resource advertising and discovery techniques to support mobility * Metadata management and exchanges * Query processing and optimization for mobile users * Transactions and workflows in mobile computing * Middleware support for mobility * Middleware support for ubiquitous computing * Multimedia delivery in 3G mobile networks * Context-aware computing and location-based services * Operating system and network support for mobile devices * Security and privacy issues of mobile data management * Integration of sensor networks into pervasive environments * Quality of service issues for data-intensive services * Adaptability and stability of pervasive computing systems * Data mining for mobile application SUBMISSION: The conference invites original, unpublished submissions whose length does not exceed 8 pages in the camera-ready IEEE style. Submissions in PDF format must be uploaded to the conference web-based submission system. More information will be available at: . Industrial/experience papers as well as proposals for panels, demos, tutorials, and workshops are also sought by October 30th, 2006. Submission instructions will be made available on the conference homepage. Industrial/experience papers are expected to discuss novel aspects of deployed applications and/or prototypes as well as experiences and standards. Abstract Registration October 23, 2006 Paper Submission October 30, 2006 Notification of Acceptance January 23, 2007 Camera-Ready Copies Due February 23, 2007 CONFERENCE CO-CHAIRS: Gustavo Alonso, ETH Zurich, Switzerland Pedro Jose Marron, University of Stuttgart, Germany PROGRAM COMMITTEE CO-CHAIRS: Christian Becker, University of Mannheim, Germany Christian S. Jensen, Aalborg University, Denmark Jianwen Su, University of California at Santa Barbara, USA INDUSTRIAL/EXPERIENCE TRACK CHAIR: Wolfgang Prinz, Fraunhofer FIT, Germany DEMONSTRATION CHAIR: Dieter Pfoser, CTI, Greece LOCAL ORGANIZING CHAIR AND COMITTEE: Christian Becker, University of Mannheim, Germany (chair) Wolfgang Effelsberg, University of Mannheim, Germany Armin Heinzl, University of Mannheim, Germany Martin Schader, University of Mannheim, Germany PUBLICITY CHAIR: Klemens Boehm, Universitaet Karlsruhe (TH), Germany Hans-Arno Jacobsen, University of Toronto, Canada PANELS CHAIR: Agnes Voisard, Fraunhofer ISST and FU Berlin, Germany TUTORIALS CHAIR: Ralf Hartmut Gueting, FernUniversitaet Hagen, Germany WORKSHOPS CHAIR: Birgitta Koenig-Ries, University of Jena, Germany FINANCIAL/REGISTRATION CHAIR: Torben Weis, University of Stuttgart, Germany TECHNICAL PROGRAM COMMITTEE: Karl Aberer, EPFL Lausanne, Switzerland Jalal Al-Muhtadi, King Saud University, Saudi Arabia Michael Beigl, Technische Universitaet Braunschweig, Germany Michela Bertolotto, University College Dublin, Ireland Claudio Bettini, University of Milano, Italy Peter Boncz, CWI, Netherlands Thomas Brinkhoff, Oldenburg University of Applied Sciences, Germany Erik Buchmann, University of Karlsruhe, Germany Marco Conti, IIT, Italy Bin Cui, Peking University, China Alex Delis, University of Athens, Greece Wolfgang Effelsberg, University of Mannheim, Germany Stefan Fischer, University of Luebeck, Germany Hannes Frey, University of Southern Denmark, Denmark Shahram Ghandeharizadeh, University of Southern California, USA Bugra Gedik, IBM Research, USA Stephane Grumbach, CNRS/LIAMA, China Joerg Haehner, University of Stuttgart, Germany Takahiro Hara, Osaka University, Japan Liviu Iftode, Rutgers University, USA Valerie Issarny, INRIA, France Ibrahim Kamel, University of Sharjah, UAE Dimitris Katsaros, Aristotele University of Thessaloniki, Greece Masaru Kitsuregawa, University of Tokyo, Japan George Kollios, Boston University, USA Alexandros Labrinidis, University of Pittsburgh, USA Dik Lun Lee, Hong Kong University of Science and Technology, China Ki-Joune Li, Pusan National University, Korea Bin Lin, NCR/Teradata, USA Ling Liu, Georgia Institute of Technology, USA Zakaria Maamar, Zayed University, UAE Nikos Mamoulis, University of Hong Kong, China Bernhard Mitschang, University of Stuttgart, Germany Ken Moody, Cambridge University, UK Moira Norrie, ETH Zurich, Switzerland Mourad Ouzzani, Purdue University, USA Dieter Pfoser, CTI, Greece Evaggelia Pitoura, University of Ioannina, Greece Anand Ranganathan, IBM T.J. Watson Research, USA Kay Roemer, ETH Zuerich, Switzerland Simonas Saltenis, Aalborg University, Denmark George Samaras, University of Cyprus, Cyprus Joerg Sander, University of Alberta, Canada Ichiro Satoh, NII, Japan Peter Scheuermann, Northwestern University, USA Markus Schneider, University of Florida, USA Michel Scholl, CNAM Paris, France Timos Sellis, National Technical University of Athens, Greece Makoto Takizawa, Tokyo Denki University, Japan Kian-Lee Tan, National University of Singapore, Singapore Yufei Tao, City University of Hong Kong, China Yannis Theodoridis, University of Pireaus, Greece Goce Trajcevski, Northwestern University, USA Vassilis Tsotras, University of California at Riverside, USA Wei Wang, Fudan University, China Carola Wenk, University of Texas at San Antonio, USA Ouri Wolfson, University of Illinois at Chicago, USA Cui Yu, Monmouth University, USA Arkady Zaslavsky, Monash University, Australia Donghui Zhang, Northeastern University, USA _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet From manet-bounces@ietf.org Mon Jul 31 15:32:09 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7dUk-0004Z2-Co; Mon, 31 Jul 2006 15:32:06 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G7dUi-0004Yx-OR for manet@ietf.org; Mon, 31 Jul 2006 15:32:04 -0400 Received: from mta075d.interbusiness.it ([85.37.17.75]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G7dUf-0000bx-Um for manet@ietf.org; Mon, 31 Jul 2006 15:32:04 -0400 Received: from smtp-out03.alice.it ([85.37.17.99]) by MTA075D.interbusiness.it with ESMTP; 31 Jul 2006 21:32:01 +0200 Received: from FBCMMO02.fbc.local ([192.168.68.196]) by smtp-out03.alice.it with Microsoft SMTPSVC(6.0.3790.1830); Mon, 31 Jul 2006 21:32:01 +0200 Received: from FBCMCL01B06.fbc.local ([192.168.69.87]) by FBCMMO02.fbc.local with Microsoft SMTPSVC(6.0.3790.1830); Mon, 31 Jul 2006 21:32:01 +0200 Received: from [82.61.1.136] ([82.61.1.136]) by FBCMCL01B06.fbc.local with Microsoft SMTPSVC(6.0.3790.1830); Mon, 31 Jul 2006 21:32:00 +0200 Message-ID: <44CE5AB6.5040502@iet.unipi.it> Date: Mon, 31 Jul 2006 21:32:06 +0200 From: Mario Di Francesco User-Agent: Mozilla Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: manet@ietf.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 31 Jul 2006 19:32:00.0469 (UTC) FILETIME=[FE568850:01C6B4D7] X-Spam-Score: 1.8 (+) X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3 Subject: [manet] CFP: Third IEEE International Workshop on Sensor Networks and Systems for Pervasive Computing (PerSeNS 2007) 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: , Errors-To: manet-bounces@ietf.org [Apologies for possible multiple copies] ----------------------------------------------------------------------- Third IEEE International Workshop on Sensor Networks and Systems for Pervasive Computing (PerSeNS 2007) http://www.ing.unipi.it/persens/ March 2007 - White Plains, NY, USA in conjunction with IEEE PerCom 2007 (http://www.percom.org/) ---------------------------------------------------------------------- PRELIMINARY CALL FOR PAPERS Thanks to wireless sensor networks, pervasive computing environments are becoming a reality. Wireless sensor networks are aggregates of sensor nodes into sophisticated sensing, computational and communication infrastructures. These new networks are having a significant impact (and promises to have even more) on a wide array of applications ranging from military, to scientific, to industrial, to health-care, to domestic, establishing ubiquitous computing that will pervade society and redefine the way in which we live and work. The goal of this workshop is to provide a forum to exchange ideas, discuss solutions, and share experiences among researchers, professionals, and application developers both from industry and academia. Original papers addressing both theoretical and practical aspects of sensor networks are solicited. Papers describing prototype and experimental implementations and deployment of sensor networks and systems are particularly welcome. Topics of interest include but are not limited to: - Sensor-based systems and applications - Operating systems - Middleware and software tools - Networking architectures and protocols - Data gathering, aggregation and dissemination - Topology control - Power management and energy-efficient design - Time synchronization - Location and mobility management - Cross-layer architectures - Intelligent sensors - Security and dependability issues - Modelling and performance evaluation - Measurements PAPER SUBMISSION Papers should contain original material and not be previously published, or currently submitted for consideration elsewhere. Manuscripts must be limited to 5 pages in IEEE 8.5x11 conference format, and formatted in accordance with the IEEE Computer Society author guidelines (ftp://pubftp.computer.org/Press/Outgoing/proceedings/INSTRUCT.HTM). All submissions will be handled electronically. Authors should prepare a PDF file and submit it following the submission instructions available at the PerSeNS 2007 website. Accepted papers will be published by the IEEE Computer Society in the combined PerCom 2007 workshops proceedings. IMPORTANT DATES Papers due September 29, 2006 Notification of acceptance November 25, 2007 Camera-ready papers due December 22, 2007 WORKSHOP CO-ORGANIZERS Giuseppe Anastasi Dept. of Information Engineering University of Pisa Via Diotisalvi 2, 56122 Pisa - Italy E-mail: g.anastasi@iet.unipi.it Silvia Giordano Dept. of Technologies and Innovations University of Applied Science - SUPSI Galleria 2 - Via Cantonale 6928 Manno - Switzerland Email: silvia.giordano@supsi.ch Stephan Olariu Department of Computer Science Old Dominion University Norfolk, VA 23529-0162, U.S.A. Email: olariu@cs.odu.edu TECHNICAL PROGRAM COMMITTEE Gaetano Borriello, University of Washington, USA Levente Buttyan, Budapest Univ. of Technology and Economics, Hungary Vinny Cahill, Trinity College, Ireland Tiziana Calamoneri, University of Rome "La Sapienza", Italy Carla Fabiana Chiasserini, Politecnico di Torino, Italy Sajal Das, University of Texas at Arlington, USA Isabelle Guerin Lassous, INRIA, France Qi Han, Colorado School of Mines, USA Holger Karl, University Paderborn, Germany Cecilia Mascolo, University of College London, UK Archan Misra, IBM T. J. Watson Research Center, USA Amy Murphy, University of Lugano, Switzerland Sotiris Nikoletseas, Computer Technology Institute, Greece Symeon Papavassiliou, National Tech University of Athens, Greece Ravi Prakash, University of Texas at Dallas, USA Maria Giovanna Sami, Politecnico di Milano, Italy Rahul Shah, Purdue University, USA Mitali Singh, Juniper Networks, USA Mani Srivastava, UCLA, USA Ivan Stojmenovic, University of Ottawa, Canada Ioannis Stavrakakis, University of Athens, Greece Yu-Chee Tseng, National Chiao Tung University, Taiwan Laura Vanzago, ST Microelectonics, Italy Jie Wu, Florida Atlantic University, USA Mohamed Younis, University of Maryland, USA PUBLICITY CO-CHAIRS Mario Di Francesco, University of Pisa, Italy Qi Han, Colorado School of Mines, USA _______________________________________________ manet mailing list manet@ietf.org https://www1.ietf.org/mailman/listinfo/manet