From manet-bounces@ietf.org Mon May 01 11:32:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FaaNJ-0006o8-BU; Mon, 01 May 2006 11:31:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FaaNH-0006gt-If
	for manet@ietf.org; Mon, 01 May 2006 11:31:47 -0400
Received: from nz-out-0102.google.com ([64.233.162.206])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaaNG-0007K8-B1
	for manet@ietf.org; Mon, 01 May 2006 11:31:47 -0400
Received: by nz-out-0102.google.com with SMTP id 40so2576373nzk
	for <manet@ietf.org>; Mon, 01 May 2006 08:31:45 -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=Df+CNc1+xYuCn28DolfeHZdcivDjKiWbKtVvPoyUMTpKt7BUTIfMZLjkH+fQUx/41ZihK99LuWS86Z7jT1ClRUnuLSsMTsJoAXY/vDAyK9ur9pEL7aUT1lva5g1lgvEHhIcsBpENqZC+fCV8XaE2z+E0Hy0ptwSxzejwFtU3AtQ=
Received: by 10.36.132.15 with SMTP id f15mr1866633nzd;
	Mon, 01 May 2006 08:31:44 -0700 (PDT)
Received: by 10.37.18.76 with HTTP; Mon, 1 May 2006 08:31:44 -0700 (PDT)
Message-ID: <374005f30605010831s7f4feadfv1335337ba59bc0d9@mail.gmail.com>
Date: Mon, 1 May 2006 08:31:44 -0700
From: "Ian Chakeres" <ian.chakeres@gmail.com>
To: manet <manet@ietf.org>
In-Reply-To: <E1FWqfX-0002HH-LB@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <E1FWqfX-0002HH-LB@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: [manet] IETF 65 Meeting Survey
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

---------- Forwarded message ----------
From: IETF Administrative Director <iad@ietf.org>
Subject: IETF 65 Meeting Survey


The IAD is interested in your IETF 65 meeting experience, whether you
participated  in Dallas or remotely.  The information will be used to impro=
ve
future meetings.  Your participation is anonymous and your candor is most
welcome.
Thanks for taking part in this brief survey:
http://www.surveymonkey.com/s.asp?u=3D649182049947

Ray Pelletier
IAD
iad@ietf.org

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

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



From manet-bounces@ietf.org Mon May 01 13:09:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fabtb-0006ad-4R; Mon, 01 May 2006 13:09:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FabtZ-0006aV-JC
	for manet@ietf.org; Mon, 01 May 2006 13:09:13 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FabtX-0003Rw-4Y
	for manet@ietf.org; Mon, 01 May 2006 13:09:13 -0400
Received: from c1-vpn2.isi.edu (c1-vpn2.isi.edu [128.9.176.28])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k41H8IQ27011
	for <manet@ietf.org>; Mon, 1 May 2006 10:08:18 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: manet@ietf.org
Content-Type: text/plain; charset=UTF-8
Date: Mon, 01 May 2006 10:08:15 -0700
Message-Id: <1146503295.3398.23.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) 
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
	k41H8IQ27011
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 29dc808194f5fb921c09d0040806d6eb
Subject: [manet] CFP: ACM Workshop on Underwater Networks (WUWNet 2006)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Our Apologies if you have received multiple copies of the CFP.

Volkan Rodoplu and Wei Ye
WUWNet 2006 Publicity Co-Chairs


-----------------------------------------------------
      The First ACM International Workshop on
         UnderWater Networks (WUWNet 2006)
           http://wuwnet.engr.uconn.edu/

        In conjunction with ACM MobiCom 2006
                 September 29, 2006
           Los Angeles, California, USA
            Sponsored by ACM SIGMOBILE
-----------------------------------------------------


Overview & Scope =20
****************

The oceans cover 71% of the earth's surface and represent=20
one of the least explored frontiers, yet the oceans are=20
integral to climate regulation, nutrient production, oil=20
retrieval and transportation. As such, there is significant=20
interest in monitoring aquatic environments for scientific,=20
environmental, commercial, safety, and military reasons.=20
While there is a need for highly precise, real-time, fine=20
grained spatio-temporal sampling of the ocean environment,=20
current methods such as remote telemetry and sequential=20
local sensing cannot satisfy current needs, let alone=20
future needs. The notion of an underwater network is=20
relatively new due to the lack of maturity of underwater=20
acoustic communication. However, networks are necessary=20
in order to achieve the monitoring goals noted above. The=20
physical challenges of acoustic underwater communication=20
require us to completely re-think how a network should be=20
designed and deployed in this environment. Challenges to=20
be overcome by underwater acoustic modem and network=20
designers include: severely limited range-dependent bandwidth=20
and attenuation, extensive time-varying multipath propagation,=20
and low speed of sound propagation in water resulting in long=20
propagation delays. Moreover, a unique feature of underwater=20
networks is that the environment is constantly mobile, naturally=20
causing the node passive mobility. All the above distinct=20
features of underwater networks yield new challenges for every=20
level of the network protocol suite.

The goal of the proposed workshop is to bring together=20
researchers and practioners in areas relevant to underwater=20
networks. Thus, many layers of the "stack" from the physical=20
layer to the application layer will be represented. The objective=20
is to serve as a forum for presenting state of the art research,=20
exchanging ideas and experiences, and facilitating interaction=20
and collaboration.=20

The workshop will span one day, including presentations of technical=20
papers, tutorial/survey papers, a panel session and a poster/demo=20
session. Submissions for regular technical papers and poster/demo=20
extended abstracts should describe original research, not published=20
or currently under review for other workshops, conferences, or
journals.  =20

Topics of interest include, but are not limited to:

-	Network architecture design=20
-	Efficient acoustic communications
-	Cooperative underwater communications
-	Medium access control
-	Routing and forwarding
-	Reliable data transfer
-	Security and robustness
-	Power management
-	Data storage and management=20
-	Localization and synchronization
-	Data fusion, dissemination, tracking
-	Network modeling and simulations
-	Capacity analysis
-	New techniques for aquatic applications
-	New applications for underwater networks


Submission Guidelines
*********************

All paper submissions will be handled electronically. Papers must=20
be in PDF format, no longer than 8 pages for regular papers (10=20
pages for tutorial/survey papers and 4 pages for poster/demo papers),=20
and must follow ACM single-space, double-column format, 10 pt.=20
Submitted papers will be judged based on their quality and novelty=20
through a rigorous review process. Over-length papers will be=20
automatically rejected. Detailed instructions for paper submission
are posted on the workshop website.


Important Dates
***************

Submission deadline: June 30, 2006
Acceptance notification: July 28, 2006
Camera-ready version: August 11, 2006
Workshop date: September 29, 2006


Organizing Committee
********************
=20
General Co-chairs:=20

Jun-Hong Cui (University of Connecticut)=20
Urbashi Mitra (University of Southern California)

Technical Program Co-chairs:

Kevin Fall (Intel Research, Berkeley)
Milica Stojanovic (MIT/WHOI)

Publicity Co-chairs:

Volkan Rodoplu (University of California, Santa Barbara)
Wei Ye (USC/ISI)

Treasurer:

Shengli Zhou (University of Connecticut)

Publications Chair:

Xiuzhen Cheng (George Washington University)


Technical Program Committee
***************************

Ian Akyildiz (Georgia Institute of Technology)=20
Lee Freitag (Woods Hole Oceanographic Institution)
Mario Gerla (University of California, Los Angeles)
Jo=C3=A3o Pedro Gomes (Instituto Superior T=C3=A9cnico, Portugal)
John Heidemann (USC/ISI)
Ronald A. Iltis (University of California, Santa Barbara)
Jim Kurose (University of Massachusetts, Amherst)
Mehul Motani (National University of Singapore)
Joseph A. Rice (Naval Postgraduate School)
Daniela Rus (Massachusetts Institute of Technology)
Mani Srivastava (University of California, Los Angeles)
Yongguang Zhang (Microsoft Research Asia, China)
Michele Zorzi (Universita'di Ferrara, Italy)=20



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



From manet-bounces@ietf.org Tue May 02 04:44:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FaqUe-0008DL-BT; Tue, 02 May 2006 04:44:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FaqUd-0008DG-NX
	for manet@ietf.org; Tue, 02 May 2006 04:44:27 -0400
Received: from posta.ti-edu.ch ([195.176.176.171] helo=ti-edu.ch)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FaqUb-0007cc-S1
	for manet@ietf.org; Tue, 02 May 2006 04:44:27 -0400
X-Virus-Scanned: by cgpav
Received: from [212.201.107.167] (account frederick@idsia.ch HELO
	[10.117.55.167]) by ti-edu.ch (CommuniGate Pro SMTP 5.0.9)
	with ESMTPA id 12724788 for manet@ietf.org;
	Tue, 02 May 2006 10:43:42 +0200
Message-ID: <44571BC3.70809@idsia.ch>
Date: Tue, 02 May 2006 10:43:47 +0200
From: Frederick Ducatelle <frederick@idsia.ch>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: manet@ietf.org
Subject: [manet] reply: How to calculate the average node degree and,	the
References: <E1Faaok-0006Cy-QS@megatron.ietf.org>
In-Reply-To: <E1Faaok-0006Cy-QS@megatron.ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 32029c790f79bd4a84a26bd2915c54b9
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

You could also check out the BonnMotion software: 
http://web.informatik.uni-bonn.de/IV/Mitarbeiter/dewaal/BonnMotion/. It 
allows you to generate movement patterns and get a number of statistics 
out of them.

Frederick.

manet-request@ietf.org wrote:

>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. reply: How to calculate the average node degree and the
>      (Daniel luu)
>   2. CFP: VANET 2006, The Third ACM International Workshop on
>      Vehicular Ad Hoc Networks (Yih-Chun Hu)
>   3. IETF 65 Meeting Survey (Ian Chakeres)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Sun, 30 Apr 2006 15:29:45 -0400
>From: "Daniel luu" <danieluu@gmail.com>
>Subject: [manet] reply: How to calculate the average node degree and
>	the
>To: manet@ietf.org
>Message-ID:
>	<26b99bb00604301229q4e0132ddx322ea6ccefbc6cc6@mail.gmail.com>
>Content-Type: text/plain; charset="iso-8859-1"
>
>Hi zhangzhi,
>
>     If u just wanna get the average degree for each node, after creating
>the random nodes, u can simply calculate the distance between each one node
>with others. If the distance is less than 70m, this two nodes are neighbors.
>get sum of neighbors and divide by number of nodes, then u can get the
>average degree. As for the average hop count, I belive different routing
>algorithms have different results.
>
>   Good Luck!
>
>
>
>                     Daniel
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: http://www1.ietf.org/pipermail/manet/attachments/20060430/45414078/attachment.html
>
>------------------------------
>
>Message: 2
>Date: Sun, 30 Apr 2006 17:00:35 -0500
>From: Yih-Chun Hu <yihchun@crhc.uiuc.edu>
>Subject: [manet] CFP: VANET 2006, The Third ACM International Workshop
>	on Vehicular Ad Hoc Networks
>To: manet@ietf.org
>Message-ID: <44553383.3000508@crhc.uiuc.edu>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>ANNOUNCEMENT and CALL FOR PAPERS
>
>VANET 2006
>
>The Third ACM International Workshop on Vehicular Ad Hoc Networks
>
>In conjunction with ACM MobiCom 2006
>September 29, 2006
>Los Angeles, California, USA
>
>Sponsored by ACM SIGMOBILE
>
>http://www.sigmobile.org/workshops/vanet2006/
>
>Important Dates:
>Paper Submission Deadline: May 26, 2006
>Notification of Acceptance: July 10, 2006
>Camera-Ready Deadline: July 31, 2006
>
>The goal of this workshop is to present and discuss recent advances
>in the development of wireless vehicular ad hoc networking (VANET)
>technologies.  Based on short- to medium-range communication systems
>(vehicle-to-vehicle and vehicle-to-roadside), vehicular ad hoc
>networks will enable vehicular safety applications including collision
>and other safety warnings as well as non-safety applications like
>real-time traffic congestion and routing information, high-speed
>tolling, mobile infotainment, and many others.
>
>The creation of high-performance, highly reliable, highly scalable,
>and secure VANET technologies, though, presents an extraordinary
>challenge to the wireless research community: a high degree of
>communication reliability is needed under unfavorable channel
>conditions.  Clearly, the specificity of vehicular ad hoc networks in
>terms of mobility behavior and applications scenarios and requirements
>makes VANET research an exciting and demanding application- and
>purpose-driven sub-discipline of wireless networking.
>
>Following the successes of VANET 2004 held in Philadelphia and VANET
>2005 held in Cologne, Germany, the Third ACM International Workshop on
>Vehicular Ad Hoc Networks will be held in Los Angeles, September 29,
>2006, in conjunction with MobiCom 2006.
>
>Authors are invited to submit papers presenting new research related
>to the theory or practice of vehicular ad hoc networks (VANET).
>All submissions must describe original research, not published or
>currently under review for another workshop, conference, or
>journal.  Areas of interest include, but are not limited to:
>
>- Safety and non-safety applications
>- Roadside-to-vehicle and vehicle-to-vehicle communication
>- Communication protocol design
>- Channel modeling
>- Modulation and coding
>- Power control and scalability issues
>- Multi-channel organization and operation
>- Security issues and countermeasures
>- Privacy issues
>- Network management
>- Simulation frameworks & real-world testbeds
>
>VANETs present a highly active field of research, development,
>standardization and field trials.  Throughout the world, there are many
>national/international projects in government, industry, and academia
>devoted to VANETs, for example consortia like VSC (US), C2CCC (Europe)
>and InternetITS (Japan), standardization efforts like IEEE 802.11p
>(WAVE) and field trials like the large-scale Vehicle Infrastructure
>Integration Program (VII) in the US.
>
>Submission Instructions
>
>All paper submissions will be handled electronically.  Papers must be
>in PDF format, no longer than 10 pages (single- or double-column), in
>font no smaller than 11 points, and must fit properly on US
>Letter-sized paper (8.5 inch x 11 inch) with reasonable
>margins.  Submitted papers will be judged based on their quality
>through a double-blind review process, where the identities of the
>authors are withheld from the reviewers.  Detailed instructions for
>paper submission will be posted on the VANET 2006 web page at:
>http://www.sigmobile.org/workshops/vanet2006/.
>
>Please email questions related to paper submission or the technical
>program to: vanet2006-pc-chairs@rz.uni-karlsruhe.de.
>
>
>General Co-Chairs:
>Wieland Holfelder, DaimlerChrysler RTNA, Inc.
>David B. Johnson, Computer Science Department, Rice University
>
>Technical Program Co-Chairs:
>Victor Bahl, Microsoft Research
>Hannes Hartenstein, Universitat Karlsruhe
>
>Publicity Chair:
>Yih-Chun Hu, University of Illinois at Urbana-Champaign
>
>Web Chair:
>Ken Laberteaux, Toyota Technical Center
>
>Technical Program Committee (partial list):
>Sharad Agarwal, Microsoft Research
>Tracy Camp, Colorado School of Mines
>Wai Chen, Telcordia Technologies
>Chen-Nee Chua, Univ. of California Davis
>Costas Constantinou, Univ. of Birmingham
>Luca Delgrossi, DaimlerChrysler RTNA, Inc.
>Eylem Ekici, Ohio State University
>Tamer El-Batt, HRL Laboratories
>Andreas Festag, NEC
>Jean-Pierre Hubaux, EPFL
>Markus Jakobsson, Indiana Universtity
>Daniel Jiang, DaimlerChrysler RTNA, Inc.
>Timo Kosch, BMW Research and Technology
>Ken Laberteaux, Toyota Technical Center
>Martin Mauve, University of Duesseldorf
>Paolo Santi, Italian Natl. Research Council
>Raja Sengupta, Univ. of California Berkeley
>Marc Torrent-Moreno, Universitat Karlsruhe
>
>
>
>
>
>
>------------------------------
>
>Message: 3
>Date: Mon, 1 May 2006 08:31:44 -0700
>From: "Ian Chakeres" <ian.chakeres@gmail.com>
>Subject: [manet] IETF 65 Meeting Survey
>To: manet <manet@ietf.org>
>Message-ID:
>	<374005f30605010831s7f4feadfv1335337ba59bc0d9@mail.gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>---------- Forwarded message ----------
>From: IETF Administrative Director <iad@ietf.org>
>Subject: IETF 65 Meeting Survey
>
>
>The IAD is interested in your IETF 65 meeting experience, whether you
>participated  in Dallas or remotely.  The information will be used to improve
>future meetings.  Your participation is anonymous and your candor is most
>welcome.
>Thanks for taking part in this brief survey:
>http://www.surveymonkey.com/s.asp?u=649182049947
>
>Ray Pelletier
>IAD
>iad@ietf.org
>
>_______________________________________________
>IETF-Announce mailing list
>IETF-Announce@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf-announce
>
>
>
>------------------------------
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet
>
>
>End of manet Digest, Vol 25, Issue 1
>************************************
>
>  
>

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



From manet-bounces@ietf.org Tue May 02 13:34:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fayko-00062V-8C; Tue, 02 May 2006 13:33:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Faykm-00062J-Ek
	for manet@ietf.org; Tue, 02 May 2006 13:33:40 -0400
Received: from mail.cs.dartmouth.edu ([129.170.212.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Faykj-00068U-5I
	for manet@ietf.org; Tue, 02 May 2006 13:33:40 -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 k42HXa47028628
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <manet@ietf.org>; Tue, 2 May 2006 13:33:36 -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
	k42HXasf009076 for <manet@ietf.org>; Tue, 2 May 2006 13:33:36 -0400
Received: (from tristan@localhost)
	by beaver.cs.dartmouth.edu (8.13.6/8.13.4/Submit) id k42HXawp009075
	for manet@ietf.org; Tue, 2 May 2006 13:33:36 -0400
Date: Tue, 2 May 2006 13:33:36 -0400
From: Tristan Henderson <tristan@cs.dartmouth.edu>
To: manet@ietf.org
Message-ID: <20060502173336.GB8493@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: d185fa790257f526fedfd5d01ed9c976
Subject: [manet] WICON Industry Track: deadline extended to 12 May
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

                     WICON2006 Industry Track

The focus of the WICON2006 conference is on architectural, networking,
security, performance and management aspects of cellular, WiFi, WiMax and
other Wireless Internet technologies. Preference will be given to papers
describing implementations, deployment, measurements, empirical performance
evaluation and experiments. The conference will also put a special emphasis on
integration and convergence issues of various wireless technologies and
architectures, as well as cross-layer aspects, such as QoS, billing, and
security. Given the existence of other conferences on mobile ad hoc networks,
sensor networks, and the like, papers that are oriented to ad hoc and sensor
networks  are discouraged unless they directly focus on the conference theme
of the Wireless Internet.

WICON is initiating a industrial research track for the first time with the
hope of showcasing  ongoing high quality research in the industry and
fostering much needed  dialog between industry researchers and academia. One
full day of the  conference will be devoted to the industrial track. WICON
industry track papers should describe original work that has been neither
previously published nor is under review by another conference or journal. The
page limit is 10 pages in IEEE double column format. Industry track papers
must have at least one author from industry, and should describe interesting
technical aspects of industrial applications, prototypes, experiences, and
standards; performance and design details are encouraged, whereas papers
focused on marketing or product information will not be accepted. For easy
identification, all industry track papers should have as their title "Industry
Track: rest of title."  Papers will be submitted by electronic submission
through COCUS system: http://cocus.create-net.it. Topics of interest include,
but are not limited to, the following:

Implementation, deployment and measurements
 - performance  of 2G, 3G, WiFi and WiMax systems
 - wireless network design, dimensioning and analysis
 - implementation, experimental systems and measurements
 - user behavior, traffic measurements and forecasting

Mobile network architectures
 - mobile networks beyond the 3rd generation
 - IP Multimedia Subsystem architecture and protocols
 - hybrid wireless architectures, fixed mobile convergence
 - service network architectures

Applications and services for mobile users
 - application platforms and middleware
 - application performance, performance enhancement
 - VoIP over wireless and cellular networks
 - vertical wireless application design (e.g. health care)
 - design and performance of wireless Internet applications
   (e.g., mobile gaming)

Wireless management, security and systems issues
 - wireless network management and diagnosis
 - security, malware, viruses and spam in wireless Internet
 - pricing and billing
 - reliability of wireless networks and services
=======================================================================

Industry Track Chair
    Sujata Banerjee, HP Labs
    Milind Buddhikot, Lucent Bell Labs

Program Committee
    Arup Acharya, IBM Watson
    John Chapin, Vanu, Inc.
    Richard Chen, Philips Labs
    Gabor Fodor, Ericcson Research
    Stefan Mangold, Swisscomm
    Ajita John, Avaya labs
    Thierry Kline, Bell Labs
    Satya Mallya, France Telecom R&D
    Amit Nanavati, IBM India Research Labs
    Anand Prasad, Euro DoCoMo labs
    Jacky Shen, Microsoft Research
    Rajeev Shorey, GM Research, Bangalore
    G. Venkatesh, Sasken India
    John Wullert, Telcordia

Important Dates:
    Submission of full papers: May 12, 2006 (extended)
    Acceptance Notification: June 2, 2006
    Final Camera Ready Version Due: June 16, 2006

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



From manet-bounces@ietf.org Tue May 02 13:52:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Faz2i-00026q-7r; Tue, 02 May 2006 13:52:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Faz2g-00026k-V6
	for manet@ietf.org; Tue, 02 May 2006 13:52:10 -0400
Received: from borg.juniper.net ([207.17.137.119])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Faz2e-0007Px-NG
	for manet@ietf.org; Tue, 02 May 2006 13:52:10 -0400
Received: from unknown (HELO proton.jnpr.net) ([10.10.2.37])
	by borg.juniper.net with ESMTP; 02 May 2006 10:52:08 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.05,80,1146466800"; 
	d="vcf'?scan'208"; a="547603407:sNHT33482184"
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C66E11.205B2C53"
Date: Tue, 2 May 2006 13:52:06 -0400
Message-ID: <1E8ACF422ADD1A458AAFFAD2E6FF70C808FBB91A@proton.jnpr.net>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Cancel Subscription Pls
Thread-Index: AcZuER5qtJeL7oWbTa+yKznqEnfoRA==
From: "Michael Covington" <mcovington@juniper.net>
To: <manet@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
Subject: [manet] Cancel Subscription Pls
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C66E11.205B2C53
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

To whom it may concern

Pls cancel my subscription to participate in this alias.  If I need to
log onto a specific site to cancel pls forward the URL.

Mike

Michael A. Covington
Dir Business Development -DOD
Juniper Networks=20
2251 Corporate Park Drive
Herndon, VA 20171-2808


------_=_NextPart_001_01C66E11.205B2C53
Content-Type: text/x-vcard;
	name="Michael Covington.vcf"
Content-Transfer-Encoding: base64
Content-Description: Michael Covington.vcf
Content-Disposition: attachment;
	filename="Michael Covington.vcf"

QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpOOkNvdmluZ3RvbjtNaWNoYWVsDQpGTjpNaWNoYWVs
IENvdmluZ3Rvbg0KT1JHOjtGaWVsZCBTYWxlcw0KVEVMO1dPUks7Vk9JQ0U6KDU3MSkgMjAzLTE5
ODANCkFEUjtXT1JLO0VOQ09ESU5HPVFVT1RFRC1QUklOVEFCTEU6OzsyMjUxIENvcnBvcmF0ZSBQ
YXJrIERyaXZlPTBEPTBBU1VJVEUgIzEwMDtIZXJuZG9uO1ZBOzIwMTcxO1VTQQ0KTEFCRUw7V09S
SztFTkNPRElORz1RVU9URUQtUFJJTlRBQkxFOjIyNTEgQ29ycG9yYXRlIFBhcmsgRHJpdmU9MEQ9
MEFTVUlURSAjMTAwPTBEPTBBSGVybmRvbiwgVkEgMjAxNzE9MEQ9MEFVU0ENCkVNQUlMO1BSRUY7
SU5URVJORVQ6bWNvdmluZ3RvbkBqdW5pcGVyLm5ldA0KUkVWOjIwMDUwNjIwVDE4MTcxMloNCkVO
RDpWQ0FSRA0K

------_=_NextPart_001_01C66E11.205B2C53
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_001_01C66E11.205B2C53--




From manet-bounces@ietf.org Wed May 03 03:36:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbBu8-00017S-7R; Wed, 03 May 2006 03:36:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbBu5-000151-Bh
	for manet@ietf.org; Wed, 03 May 2006 03:36:09 -0400
Received: from web31606.mail.mud.yahoo.com ([68.142.198.152])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FbBu3-0001BQ-Mi
	for manet@ietf.org; Wed, 03 May 2006 03:36:09 -0400
Received: (qmail 76261 invoked by uid 60001); 3 May 2006 07:36:07 -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=r+MthWI5KKRLXL2ZjXG+WfF7B4vOkQ/7Tp75rN1TMKsfLCmfelyZ+usNiln2TprygdNffLvpSqHwfrUV+byNIGvDgW2uuCtxgu23EniBmGjpJaLQ9xCPPje58zhHX/7i3xBzbrdE1Qw9oD1iXy3000NpDVlxEM2A/C9OP8iRuDQ=
	; 
Message-ID: <20060503073607.76259.qmail@web31606.mail.mud.yahoo.com>
Received: from [164.100.28.3] by web31606.mail.mud.yahoo.com via HTTP;
	Wed, 03 May 2006 00:36:07 PDT
Date: Wed, 3 May 2006 00:36:07 -0700 (PDT)
From: pooja kailay <poojakailay@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [manet] dsdv in glomosim
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

hi
i urgently need dsdv implementation in glomosim
pooja

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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



From manet-bounces@ietf.org Wed May 03 07:35:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbFdy-00006v-2T; Wed, 03 May 2006 07:35:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbFdw-00006q-1Z
	for manet@ietf.org; Wed, 03 May 2006 07:35:44 -0400
Received: from web26606.mail.ukl.yahoo.com ([217.146.176.56])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FbFdu-0003Yi-JY
	for manet@ietf.org; Wed, 03 May 2006 07:35:44 -0400
Received: (qmail 91150 invoked by uid 60001); 3 May 2006 11:35:11 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=zNZDUEn/q1XOk0rNXH1jWLAoHov+gFC4tyY+cEaYejrlTLVJ2bHDGoSgsr2Qc7HGpsY/cdzDNrB/fY4GYi0N6ygdYdOTQc8AeDEYl4g50GopDCRjOLn4kNoExryV5hCfDlfqzjYPMdOlCnhP/3HC/LyOkM3/PYKUSTNsYHY+jeg=
	; 
Message-ID: <20060503113511.91148.qmail@web26606.mail.ukl.yahoo.com>
Received: from [196.200.133.130] by web26606.mail.ukl.yahoo.com via HTTP;
	Wed, 03 May 2006 13:35:11 CEST
Date: Wed, 3 May 2006 13:35:11 +0200 (CEST)
From: www triste <unhapy1983@yahoo.fr>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [manet] the definition of neighbor
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0184931075=="
Errors-To: manet-bounces@ietf.org

--===============0184931075==
Content-Type: multipart/alternative; boundary="0-315710861-1146656111=:87443"
Content-Transfer-Encoding: 8bit

--0-315710861-1146656111=:87443
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello everybody
  i want to know what is the real definition of neighbor?
  x is neighbor of y = distance between x and y < 250 (and why exactly 250)
   
  or
   
  x is neighbor of y=y can receive hello paquets
   
  (i discuss in general,with olsr,aodv,dsdv .... routing protocols)
   
  Thanks for help or indication, 
   
   

		
---------------------------------
 Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Cliquez ici.
--0-315710861-1146656111=:87443
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>Hello everybody</div>  <div>i want to know what is the real definition of neighbor?</div>  <div>x is neighbor of y = distance between x and y &lt; 250 (and why exactly 250)</div>  <div>&nbsp;</div>  <div>or</div>  <div>&nbsp;</div>  <div>x is neighbor of y=y can receive hello paquets</div>  <div>&nbsp;</div>  <div>(i discuss in general,with olsr,aodv,dsdv ....&nbsp;routing protocols)</div>  <div>&nbsp;</div>  <div>Thanks for help or indication,&nbsp;</div>  <div>&nbsp;</div>  <div>&nbsp;</div><p>
		<hr size="1" /> 
<b>Faites de Yahoo! votre page d'accueil sur le web</b> pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. <a href="http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yahoo.com/set" target=_blank>Cliquez ici</a>.
--0-315710861-1146656111=:87443--


--===============0184931075==
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

--===============0184931075==--




From manet-bounces@ietf.org Wed May 03 11:14:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbJ2Y-0001ny-7R; Wed, 03 May 2006 11:13:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbJ2X-0001nt-Cj
	for manet@ietf.org; Wed, 03 May 2006 11:13:21 -0400
Received: from diri.bris.ac.uk ([137.222.10.112])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbJ2T-0004AO-U0
	for manet@ietf.org; Wed, 03 May 2006 11:13:21 -0400
Received: from ncsc.bris.ac.uk ([137.222.10.41])
	by diri.bris.ac.uk with esmtp (Exim 4.60)
	(envelope-from <E.J.Collins@bristol.ac.uk>) id 1FbJ2R-0007c2-DB
	for manet@ietf.org; Wed, 03 May 2006 16:13:16 +0100
Received: from math-pc14.maths.bris.ac.uk ([137.222.80.53])
	by ncsc.bris.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60)
	(envelope-from <E.J.Collins@bristol.ac.uk>) id 1FbJ2R-0001Ey-6v
	for manet@ietf.org; Wed, 03 May 2006 16:13:15 +0100
Date: Wed, 03 May 2006 16:13:15 +0100
From: "EJ Collins, Mathematics" <E.J.Collins@bristol.ac.uk>
To: manet@ietf.org
Message-ID: <AD84AF4B18D62C4BF231C981@math-pc14.maths.bris.ac.uk>
Originator-Info: login-token=Mulberry:0130BIN0yhraENgcGhDUWmdaAXor5aH1G2dpkcqsFbDUJuvaI=;
	token_authority=postmaster@bristol.ac.uk
X-Mailer: Mulberry/3.1.5 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; FORMAT=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: -0.6
X-Spam-Level: /
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Subject: [manet] FINAL CFP:  INTER-PERF (with VALUETOOLS 2006) 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

------------------------------------------------------------------
**                APOLOGIES FOR CROSS-POSTING                   **
**                                                              **
**     ** Final Submission Deadline  --  May 17, 2006 **        **
------------------------------------------------------------------

                 ********   INTER-PERF   *********
                   ****   Call for Papers   ****
                 *** http://www.inter-perf.org ***

                Workshop on Interdisciplinary Systems
           Approach in Performance Evaluation and Design
               of Computer & Communication Systems
                  Pisa, Italy / October 14, 2006

                 Co-located with VALUETOOLS 2006
                    http://www.valuetools.org/
                First International Conference on
            Performance Evaluation Methodologies and Tools

                   In technical cooperation with:
                          Create-Net/ICST
                       IEEE Computer Society

                         Corporate Sponsor
                         Microsoft Research

       **** Note the final deadline extension to May 17 2006 ****

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

The area of communication networks has become increasingly diverse
over the past decade, driven by an increasingly wide range of
application scenarios including ad-hoc networks, mobile networks,
sensor networks, and peer to peer networks. Issues of particular
interest relate to networks that are large scale in terms computing
elements and users, or closely coupled to the spatial environment
of their deployment.

At an appropriate level of abstraction, the operational principles
of such systems may exhibit great similarity with systems found in
other sciences, and this naturally suggests using models and
techniques that are standard in other scienctific areas such as
biological systems, economics, epidemiology, physics and the social
sciences.

Inter-Perf aims to bring together researchers and practioners from
the many scientific disciplines where such issues of scalability,
self-organization and robustness arise. In particular, it seeks
contributions which derive insights and techniques from these areas
that can be used either to evaluate the performance of existing
communication systems or to inspire the design of new ones.

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

**  Keynote speakers:                                           **
**  Laurent Massoulie, Microsoft Research, UK                   **
**  Karl Sigmund, University of Vienna, Austria                 **
**                                                              **
**  The proceedings will be published by IEEE and               **
**  accepted papers will be available online via IEEE Xplore    **

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

Topics of interest include but are not limited to:
- Bayesian belief propagation
- Bio-inspired systems
- Chemical-reaction type models
- Electromagnetism-inspired models
- Artificial immune systems
- Interacting particle systems
- Mathematics of epidemiology and infectious diseases
- Microeconomics of networks
- Percolation
- Population dynamics
- Random graphs
- Reaction-diffusion models
- Reinforced random walks in networks
- Replicator dynamics, Lotka-Volterra systems
- Self-organization
- Statistical physics models

-------------------------------------------------------------------
IMPORTANT DATES

Final Submission Deadline:       May   17, 2006
Notification of Acceptance:      June  10, 2006
Camera-ready Manuscripts due:    July  10, 2006

-------------------------------------------------------------------
PAPER SUBMISSION INSTRUCTIONS

Authors are invited to submit full papers of up to 12 pages in IEEE
conference proceedings format through COCUS (http://cocus.info).

-------------------------------------------------------------------
WORKSHOP CO-CHAIRS

Sean Collins, University of Bristol, UK - e.j.collins@bristol.ac.uk
Milan Vojnovic, Microsoft Research,  UK - milanv@microsoft.com

-------------------------------------------------------------------
TECHNICAL PROGRAM COMMITTEE

Sem Borst (Bell Labs, USA & CWI, Netherlands)
Mark Burgess (Oslo College, Norway)
Hana El-Samad (UCSF, USA)
Ayalvadi Ganesh (Microsoft Research, UK)
Ramesh Johari (Stanford University, USA)
George Kesidis (University of Pennsylvania, USA)
Jean-Yves Le Boudec (EPFL, Switzerland)
Armand M. Makowski (University of Maryland, USA)
Peter Marbach (University of Toronto, CA)
Jose Fernando Mendes (University of Aveiro, Portugal)
David Nicol (University of Illinois-Urbana Champaign, USA)
Devavrat Shah (MIT, USA)
Anil Somayaji (Carleton University, CA)
Leandros Tassiulas (University of Thessaly, Greece)
Patrick Thiran (EPFL, Switzerland)
Don Towsley (University of Massachusetts at Amherst, USA)
Gustavo de Veciana (University of Texas at Austin, USA)
-------------------------------------------------------------------
---------------------------------------------------------------------
Dr E J Collins                 |  Telephone:   +44 (0)117 928 7977
Department of Mathematics      |  Fax:         +44 (0)117 928 7999
University of Bristol          |  email:    E.J.Collins@bris.ac.uk
University Walk,               |
Bristol BS8 1TW, U.K.          |  http://www.maths.bris.ac.uk/~maejc
---------------------------------------------------------------------

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



From manet-bounces@ietf.org Wed May 03 12:33:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbKHO-0007HE-K4; Wed, 03 May 2006 12:32:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbKHM-0007G4-Hq
	for manet@ietf.org; Wed, 03 May 2006 12:32:44 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbKHL-0007Fk-3q
	for manet@ietf.org; Wed, 03 May 2006 12:32:44 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [manet] the definition of neighbor
Date: Wed, 3 May 2006 10:32:40 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEEBFA@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] the definition of neighbor
Thread-Index: AcZupcz4ZjfBEvzbQ2+WIA1rNcT9KQAIMbiA
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "www triste" <unhapy1983@yahoo.fr>,
	<manet@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1593759357=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1593759357==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C66ECF.31D287C2"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C66ECF.31D287C2
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
Generally, a neighbors are considered nodes that can communicate with =
each other.  However, when it gets to modeling and implementation, this =
definition can be a bit iffy.  I've seen terms like "two-hop neighbors," =
which would include nodes that cannot connect with the node in question =
directly, but can connect with a one-hop neighbor.  "Neighborness" also =
depends on the data rate.  Two nodes that can communicate at 1Mb/s may =
not be able to at 10Mb/s, so two nodes that can exchange Hello messages =
may not be able to exchange data packets.
=20
The situation gets even messier when fine-grained variations in signal =
strength are taken into account.  Then, a neighbor definition would =
include som minimum service quality.
=20
In simulation, one sometimes assumes that there is a range, within which =
nodes can communicate and beyond which they cannot.  This is a =
simplifying assumption.  The value of that range will depend on what =
other assumptions you are making, such as the type of transmitter, =
allowances for fading and shadowing, the channel, the nature of the =
receiver, the waveform you are using, engoding, error correction, etc.  =
If you look into the background of the model you are using, you will =
probably find a statement of why 250 was selected. =20
=20

John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
 =20

=20

________________________________

From: www triste [mailto:unhapy1983@yahoo.fr]=20
Sent: Wednesday, May 03, 2006 5:35 AM
To: manet@ietf.org
Subject: [manet] the definition of neighbor


Hello everybody
i want to know what is the real definition of neighbor?
x is neighbor of y =3D distance between x and y < 250 (and why exactly =
250)
=20
or
=20
x is neighbor of y=3Dy can receive hello paquets
=20
(i discuss in general,with olsr,aodv,dsdv .... routing protocols)
=20
Thanks for help or indication,=20
=20
=20

________________________________

Faites de Yahoo! votre page d'accueil sur le web pour retrouver =
directement vos services pr=E9f=E9r=E9s : v=E9rifiez vos nouveaux mails, =
lancez vos recherches et suivez l'actualit=E9 en temps r=E9el. Cliquez =
ici =
<http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yahoo.com/s=
et> .

------_=_NextPart_001_01C66ECF.31D287C2
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D985583015-03052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D985583015-03052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D985583015-03052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Generally, a neighbors are =
considered&nbsp;nodes that can=20
communicate with each other.&nbsp; However, when it gets to modeling and =

implementation, this definition can be a bit iffy.&nbsp; I've seen terms =
like=20
"two-hop neighbors," which would include nodes that cannot connect with =
the node=20
in question directly, but can connect with a one-hop neighbor.&nbsp;=20
"Neighborness" also depends on the data rate.&nbsp; Two nodes that can=20
communicate at 1Mb/s may not be able to at 10Mb/s, so two nodes that can =

exchange Hello messages may not be able to exchange data=20
packets.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D985583015-03052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D985583015-03052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The situation gets even messier when =
fine-grained=20
variations in signal strength are taken into account.&nbsp; Then, a =
neighbor=20
definition would include som minimum service =
quality.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D985583015-03052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D985583015-03052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>In simulation, one sometimes assumes that there =
is a range,=20
within which nodes can communicate and beyond which they cannot.&nbsp; =
This is a=20
simplifying assumption.&nbsp; The value of that range will depend on =
what other=20
assumptions you are making, such as the type of transmitter, allowances =
for=20
fading and shadowing, the channel, the nature of the receiver, the =
waveform you=20
are using, engoding, error correction, etc.&nbsp; If you look into the=20
background of the model you are using, you will probably find a =
statement of why=20
250 was selected.&nbsp; </FONT></SPAN></DIV>
<DIV>&nbsp;</DIV><!-- Converted from text/plain format -->
<P><FONT size=3D2>John P. Mullen, Ph.D.<BR>(505)=20
646-2958<BR>jomullen@nmsu.edu<BR>&nbsp;</FONT> </P>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> www triste =
[mailto:unhapy1983@yahoo.fr]=20
<BR><B>Sent:</B> Wednesday, May 03, 2006 5:35 AM<BR><B>To:</B>=20
manet@ietf.org<BR><B>Subject:</B> [manet] the definition of=20
neighbor<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hello everybody</DIV>
<DIV>i want to know what is the real definition of neighbor?</DIV>
<DIV>x is neighbor of y =3D distance between x and y &lt; 250 (and why =
exactly=20
250)</DIV>
<DIV>&nbsp;</DIV>
<DIV>or</DIV>
<DIV>&nbsp;</DIV>
<DIV>x is neighbor of y=3Dy can receive hello paquets</DIV>
<DIV>&nbsp;</DIV>
<DIV>(i discuss in general,with olsr,aodv,dsdv ....&nbsp;routing=20
protocols)</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks for help or indication,&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<P>
<HR SIZE=3D1>
<B>Faites de Yahoo! votre page d'accueil sur le web</B> pour retrouver=20
directement vos services pr=E9f=E9r=E9s : v=E9rifiez vos nouveaux mails, =
lancez vos=20
recherches et suivez l'actualit=E9 en temps r=E9el. <A=20
href=3D"http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yaho=
o.com/set"=20
target=3D_blank>Cliquez ici</A>.</BODY></HTML>

------_=_NextPart_001_01C66ECF.31D287C2--


--===============1593759357==
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

--===============1593759357==--




From manet-bounces@ietf.org Wed May 03 13:06:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbKnl-0003fO-A5; Wed, 03 May 2006 13:06:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbKnk-0003fJ-36
	for manet@ietf.org; Wed, 03 May 2006 13:06:12 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbKnj-0000XZ-H6
	for manet@ietf.org; Wed, 03 May 2006 13:06:12 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by sj-iport-4.cisco.com with ESMTP; 03 May 2006 10:06:11 -0700
X-IronPort-AV: i="4.05,85,1146466800"; 
	d="scan'208"; a="1800999018:sNHT32727500"
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k43H6AYg025273;
	Wed, 3 May 2006 10:06:10 -0700 (PDT)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com
	[10.32.244.218])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k43H4XeH002057;
	Wed, 3 May 2006 10:04:33 -0700
In-Reply-To: <20060503113511.91148.qmail@web26606.mail.ukl.yahoo.com>
References: <20060503113511.91148.qmail@web26606.mail.ukl.yahoo.com>
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Message-Id: <A405524C-901B-4C74-9B57-D6DFC3215BEF@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] the definition of neighbor
Date: Wed, 3 May 2006 10:06:09 -0700
To: www triste <unhapy1983@yahoo.fr>
X-Mailer: Apple Mail (2.749.3)
DKIM-Signature: a=rsa-sha1; q=dns; l=5718; t=1146675873; x=1147539873;
	c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20<fred@cisco.com>
	|Subject:Re=3A=20[manet]=20the=20definition=20of=20neighbor
	|To:www=20triste=20<unhapy1983@yahoo.fr>;
	X=v=3Dcisco.com=3B=20h=3Dlvidq/IhAfw6WnatJ0akM/QscIo=3D;
	b=InV+yx4CVhActEvURRYZP/Si90ahG8cFjc0VhMUR+dN+w0T/SeHsDYw8PASOG4rqiWU6xZgI
	E1Uu+zmmE325X9BJ/g9P99wXpjBPtpc98gPYGoZRsjcro5fvDJD8tvqH;
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

The real definition of a neighbor, in any routing protocol, is a =20
routing process that this routing process may communicate with =20
directly, as opposed to one that must be reached via an intermediary =20
at the same layer. Note that there may be intermediaries at a lower =20
layer, through, such as a layer 2 switch or (in the case of BGP) an =20
IP route within this AS to a system in a neighboring AS.

RFC 1142 (IS-IS) defines "Neighbour" as "An adjacent system reachable =20=

by traversal of a single subnetwork by a PDU."

RFC 2328 (OSPF) states this in the words: "Two routers that have =20
interfaces to a common network".

RFC 4271 (BGP4) uses it in two senses: a neighboring system is a BGP =20
process (identified by an IP address) that a TCP connection will be =20
made to or accepted from, and a neighboring AS is the AS that a given =20=

route was received from.

RFC 3561 (AODV) doesn't define the word in so many words, but it =20
makes some interesting assumptions about neighbors that become a =20
definition. In its protocol description, it says that "Whenever a =20
node receives a Hello message from a neighbor" certain things happen, =20=

and it notes that 'each node keeps a "precursor list", containing the =20=

IP address for each its neighbors that are likely to use it as a next =20=

hop towards each destination.' A neieghbor in AODV, by inference, is =20
any node that a given node might receive an AODV message (and =20
especially a HELLO) directly from.

RFC 3684 (TBRPF) defines:
    neighbor node
       A node j is said to be a neighbor of node i if node i can hear
       node j on some interface.  Node j is said to be a 2-way neighbor
       if there is a bidirectional link between i and j.

RFC 3626 (OLSR) keeps track of neighbors, two hop neighbors =20
(neighbors of neighbors), and nodes further away. It therefore spends =20=

quite a bit of effort on the definition of the concept. It defines:

       neighbor node

          A node X is a neighbor node of node Y if node Y can hear =20
node X
          (i.e., a link exists between an OLSR interface on node X =20
and an
          OLSR interface on Y).

       2-hop neighbor

          A node heard by a neighbor.

       strict 2-hop neighbor

          a 2-hop neighbor which is not the node itself or a neighbor of
          the node, and in addition is a neighbor of a neighbor, with
          willingness different from WILL_NEVER, of the node.

          A node which is selected by its 1-hop neighbor, node X, to
          "re-transmit" all the broadcast messages that it receives from
          X, provided that the message is not a duplicate, and that the
          time to live field of the message is greater than one.

          A node which has selected its 1-hop neighbor, node X, as its
          multipoint relay, will be called a multipoint relay =20
selector of
          node X.

       symmetric 1-hop neighborhood

          The symmetric 1-hop neighborhood of any node X is the set of
          nodes which have at least one symmetric link to X.

       symmetric 2-hop neighborhood

          The symmetric 2-hop neighborhood of X is the set of nodes,
          excluding X itself, which have a symmetric link to the
          symmetric 1-hop neighborhood of X.

       symmetric strict 2-hop neighborhood

          The symmetric strict 2-hop neighborhood of X is the set of
          nodes, excluding X itself and its neighbors, which have a
          symmetric link to some symmetric 1-hop neighbor, with
          willingness different of WILL_NEVER, of X.

http://www.ietf.org/rfc/rfc1142.txt
1142 OSI IS-IS Intra-domain Routing Protocol. D. Oran, Ed.. February
      1990. (Format: TXT=3D425379, PS=3D1440951, PDF=3D490300 bytes) =
(Status:
      INFORMATIONAL)

http://www.ietf.org/rfc/rfc2328.txt
2328 OSPF Version 2. J. Moy. April 1998. (Format: TXT=3D447367 bytes)
      (Obsoletes RFC2178) (Also STD0054) (Status: STANDARD)

http://www.ietf.org/rfc/rfc4271.txt
4271 A Border Gateway Protocol 4 (BGP-4). Y. Rekhter, Ed., T. Li, Ed.,
      S. Hares, Ed.. January 2006. (Format: TXT=3D222702 bytes) =
(Obsoletes
      RFC1771) (Status: DRAFT STANDARD)

http://www.ietf.org/rfc/rfc3561.txt
3561 Ad hoc On-Demand Distance Vector (AODV) Routing. C. Perkins, E.
      Belding-Royer, S. Das. July 2003. (Format: TXT=3D90356 bytes) =20
(Status:
      EXPERIMENTAL)

http://www.ietf.org/rfc/rfc3684.txt
3684 Topology Dissemination Based on Reverse-Path Forwarding (TBRPF).
      R. Ogier, F. Templin, M. Lewis. February 2004. (Format: TXT=3D107963=

      bytes) (Status: EXPERIMENTAL)

http://www.ietf.org/rfc/rfc3626.txt
3626 Optimized Link State Routing Protocol (OLSR). T. Clausen, Ed., P.
      Jacquet, Ed.. October 2003. (Format: TXT=3D161265 bytes) (Status:
      EXPERIMENTAL)

On May 3, 2006, at 4:35 AM, www triste wrote:

> Hello everybody
> i want to know what is the real definition of neighbor?
> x is neighbor of y =3D distance between x and y < 250 (and why =20
> exactly 250)
>
> or
>
> x is neighbor of y=3Dy can receive hello paquets
>
> (i discuss in general,with olsr,aodv,dsdv .... routing protocols)
>
> Thanks for help or indication,
>
>
>
> Faites de Yahoo! votre page d'accueil sur le web pour retrouver =20
> directement vos services pr=E9f=E9r=E9s : v=E9rifiez vos nouveaux =
mails, =20
> lancez vos recherches et suivez l'actualit=E9 en temps r=E9el. Cliquez =
=20
> ici.
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-bounces@ietf.org Wed May 03 14:15:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbLsv-00022N-S1; Wed, 03 May 2006 14:15:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbLsu-00022I-2V
	for manet@ietf.org; Wed, 03 May 2006 14:15:36 -0400
Received: from hostree9f.alcatel.com ([143.209.238.159]
	helo=audl952.usa.alcatel.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbLst-0003eG-Fh
	for manet@ietf.org; Wed, 03 May 2006 14:15:36 -0400
Received: from usdaln07347 (usdaln07347.usa.alcatel.com [143.209.105.69])
	by audl952.usa.alcatel.com (ALCANET) with ESMTP id k43IFV01007905;
	Wed, 3 May 2006 13:15:31 -0500
From: "Tim Ozugur" <tim.ozugur@alcatel.com>
To: <manet@ietf.org>
Date: Wed, 3 May 2006 13:15:31 -0500
Message-ID: <00b801c66edd$904470b0$4569d18f@ad3.ad.alcatel.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Thread-index: AcZu3RZf2J7ICLthSTyN8QWpYrkJBwAAGpSQ
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a1dc446dc7ac353b90b60743d0e479e3
Cc: tpc@bwan.org
Subject: [manet] Call For Papers: BWAN 2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0462772320=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0462772320==
Content-Type: multipart/related;
	boundary="----=_NextPart_000_00B9_01C66EB3.A76E68B0"

This is a multi-part message in MIME format.

------=_NextPart_000_00B9_01C66EB3.A76E68B0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_00BA_01C66EB3.A76E68B0"


------=_NextPart_001_00BA_01C66EB3.A76E68B0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

(Apologies if you are receiving this message more than once)

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

CALL FOR PAPERS

INTERNATIONAL WORKSHOP ON BROADBAND WIRELESS

ACCESS FOR UBIQUITOUS NETWORKING (BWAN 2006)

20 September 2006 - Alghero, Sardinia, Italy 

(www.bwan.org)

Technically sponsored by IEEE (approval pending) 

 

IMPORTANT DATES:

Submission of Summaries: 15 May 2006

 

SPECIAL STUDENT REGISTRATION RATE: 

Early registration rate for students: USD 270 (cut-off date: one month prior
to the workshop)

The late registration rate for students: USD 320

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

Scope and Interests 

Today Broadband Wireless access (mobile/nomadic) is emerging to offer
outstanding opportunities. In this new world of communicating devices, the
evolution towards ubiquitous networking is promising new paradigm with the
aim of providing communication capability all the time, everywhere,
transparently and invisibly to the user, using devices embedded in the
surrounding physical environment. The implementation of such a paradigm
requires innovation in wireless network technologies and devices,
development of infrastructures, enablers supporting enhanced features for
ubiquitous capability. 
The workshop is intended to present features based on new architectures
supporting mobility and/or nomadic features for wireless access (IEEE
802.yx, Mesh,...), the sharing of the network access, bandwidth sharing on
radio access, network enablers all favoring the new perspective of
ubiquitous and ambient networking. Within the framework of BWAN 2006, the
next generation of network access will be investigated. 
Topics of interest to this workshop include (but are not limited to)
performance studies and solutions (algorithms, protocols, architectures)
that tend to improve experience of users of services and applications with
context awareness. 


Workshop topics 

  <http://www.bwan.org/immagini/punto_elenco.gif>   New Architectures and
technologies for broadband wireless access (xDSL/FTTx,etc) with mobility
features 

  <http://www.bwan.org/immagini/punto_elenco.gif>   3G and beyond 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Ambient Networking 

  <http://www.bwan.org/immagini/punto_elenco.gif>   AAA (Authentication,
Authorization, Accounting) 

  <http://www.bwan.org/immagini/punto_elenco.gif>   QoS efficient and
scalable routing 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Transport mechanism for
supporting various high speed traffics

  <http://www.bwan.org/immagini/punto_elenco.gif>   End to end security and
privacy issues for ubiquitous Network access

  <http://www.bwan.org/immagini/punto_elenco.gif>   xDSL/FTTx+WiFi modem
with mobility enhancement 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Radio extension such as
802.xy (WiFi, WiMax, etc) P2P network 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Standard and regulations

  <http://www.bwan.org/immagini/punto_elenco.gif>   Low cost and low power
integrated Modulation

  <http://www.bwan.org/immagini/punto_elenco.gif>   Network cost performance
and Business Models

  <http://www.bwan.org/immagini/punto_elenco.gif>   RFID tags,
sensors,actuators, etc

  <http://www.bwan.org/immagini/punto_elenco.gif>   Interference mitigation
for multiple access

  <http://www.bwan.org/immagini/punto_elenco.gif>   IPv6 impact

  <http://www.bwan.org/immagini/punto_elenco.gif>   Cognitive radio


Submission Dates 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Submission of summaries:
15 May 2006

  <http://www.bwan.org/immagini/punto_elenco.gif>   Notification of
Acceptance: 15 June 2006 


  <http://www.bwan.org/immagini/punto_elenco.gif>   Submission Camera Ready
Papers: 10 July 2006 


Publication 

The submissions to be presented at the workshop will be selected, based on
their originality, technical merit and topical relevance of their contents.
All accepted papers will be published in the conference proceedings that
will be available at the workshop.


------=_NextPart_001_00BA_01C66EB3.A76E68B0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY>
<DIV></DIV>
<DIV><FONT face=3DArial><FONT face=3DVerdana><FONT color=3D#003366><B>
<P><FONT size=3D2>(Apologies if you are receiving this message more than =

once)</FONT></P>
<P><FONT =
size=3D2>--------------------------------------------------</FONT></P>
<P><FONT size=3D2>CALL FOR PAPERS</FONT></P>
<P><FONT size=3D2>INTERNATIONAL WORKSHOP ON BROADBAND =
WIRELESS</FONT></P>
<P><FONT size=3D2>ACCESS FOR UBIQUITOUS NETWORKING (BWAN =
2006)</FONT></P>
<P><FONT size=3D2></FONT></P>
<P><FONT size=3D2>20 September 2006 - Alghero, Sardinia, Italy =
</FONT></P>
<P><FONT size=3D2>(</FONT><A href=3D"www.bwan.org"><U><FONT =
color=3D#0000ff><FONT=20
size=3D2>www.bwan.org</FONT></U></FONT></A><FONT size=3D2>)</FONT></P>
<P><FONT size=3D2>Technically sponsored by IEEE (approval pending) =
</FONT></P>
<P><FONT size=3D2></FONT>&nbsp;</P>
<P><FONT size=3D2>IMPORTANT DATES:</FONT></P>
<P><FONT size=3D2>Submission of Summaries: 15 May 2006</FONT></P>
<P><FONT face=3DArial size=3D2><SPAN=20
class=3D348430518-03052006></SPAN></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2><SPAN class=3D348430518-03052006>SPECIAL =
STUDENT=20
REGISTRATION RATE: </SPAN></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D348430518-03052006>E</SPAN>arly=20
registration rate for students: USD 270<SPAN class=3D348430518-03052006> =
(cut-off=20
date:&nbsp;one month prior to the workshop)</SPAN></FONT></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D348430518-03052006></SPAN></FONT></FONT><FONT face=3DArial =
size=3D2>The late=20
registration rate for students: USD 320</FONT></P>
<P><FONT=20
size=3D2>---------------------------------------------------</FONT></P></=
B></FONT></FONT>
<P align=3Djustify><FONT size=3D2><FONT face=3DVerdana><FONT =
color=3D#003366><B>Scope=20
and Interests</B> </FONT><BR><BR>Today Broadband Wireless access=20
(mobile/nomadic) is emerging to offer outstanding opportunities. In this =
new=20
world of communicating devices, the evolution towards ubiquitous =
networking is=20
promising new paradigm with the aim of providing communication =
capability all=20
the time, everywhere, transparently and invisibly to the user, using =
devices=20
embedded in the surrounding physical environment. The implementation of =
such a=20
paradigm requires innovation in wireless network technologies and =
devices,=20
development of infrastructures, enablers supporting enhanced features =
for=20
ubiquitous capability. <BR>The workshop is intended to present features =
based on=20
new architectures supporting mobility and/or nomadic features for =
wireless=20
access (IEEE 802.yx, Mesh,...), the sharing of the network access, =
bandwidth=20
sharing on radio access, network enablers all favoring the new =
perspective of=20
ubiquitous and ambient networking. Within the framework of BWAN 2006, =
the next=20
generation of network access will be investigated. <BR>Topics of =
interest to=20
this workshop include (but are not limited to) performance studies and =
solutions=20
(algorithms, protocols, architectures) that tend to improve experience =
of users=20
of services and applications with context awareness. <BR><BR><BR><FONT=20
color=3D#003366><B>Workshop topics</B> </FONT><BR><BR><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; New=20
Architectures and technologies for broadband wireless access =
(xDSL/FTTx,etc)=20
with mobility features </FONT></FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; 3G=20
and beyond </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Ambient Networking </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; AAA=20
(Authentication, Authorization, Accounting) </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; QoS=20
efficient and sca<SPAN class=3D348430518-03052006>la</SPAN>ble routing =
</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Transport mechanism for supporting various high speed =
traffics</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; End=20
to end security and privacy issues for ubiquitous Network =
access</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
xDSL/FTTx+WiFi modem with mobility enhancement </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Radio extension such as 802.xy (WiFi, WiMax, etc) P2P network =
</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Standard and regulations</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; Low=20
cost and low power integrated Modulation</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Network cost performance and Business Models</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
RFID tags, sensors,actuators, etc</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Interference mitigation for multiple access</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
IPv6 impact</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Cognitive radio</FONT></P><BR>
<P align=3Djustify><FONT color=3D#003366><FONT size=3D2><FONT=20
face=3DVerdana><B>Submission Dates</B> </FONT></FONT></FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Submission of summaries: 15 May 2006</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Notification of Acceptance: 15 June 2006 </FONT>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D11 =
border=3D0>&nbsp;=20
Submission Camera Ready Papers: 10 July 2006 </FONT></P><BR>
<P align=3Djustify><FONT size=3D2><FONT face=3DVerdana><FONT=20
color=3D#003366><B>Publication</B> </FONT><BR><BR>The submissions to be =
presented=20
at the workshop will be selected, based on their originality, technical =
merit=20
and topical relevance of their contents. All accepted papers will be =
published=20
in the conference proceedings that will be available at the=20
workshop.</FONT></FONT></P></FONT></DIV></BODY></HTML>

------=_NextPart_001_00BA_01C66EB3.A76E68B0--

------=_NextPart_000_00B9_01C66EB3.A76E68B0
Content-Type: image/gif;
	name="punto_elenco.gif"
Content-Transfer-Encoding: base64
Content-Location: http://www.bwan.org/immagini/punto_elenco.gif

R0lGODlhDAAMAHcAACH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAY
AAAADG1zT1BNU09GRklDRTkuMAgRTF2IACH/C01TT0ZGSUNFOS4wGAAAAAxjbVBQSkNtcDA3MTIC
AAABDAfaGwAh+QQBAAAAACwAAAAADAAMAIPAwMDMmTPMmQDMZgDMMwCZZgCZMwCZAAABAgMBAgMB
AgMBAgMBAgMBAgMBAgMBAgMDKQi63P4wPjMGuYYwUjkRA1MYVDUETKZa4UKqlOYSRoG1Ss1izGH4
L0MCADs=

------=_NextPart_000_00B9_01C66EB3.A76E68B0--



--===============0462772320==
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

--===============0462772320==--





From manet-bounces@ietf.org Thu May 04 02:28:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbXJg-0000fa-Ug; Thu, 04 May 2006 02:28:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbXJQ-0000fM-2F
	for manet@ietf.org; Thu, 04 May 2006 02:27:45 -0400
Received: from molure.int-evry.fr ([157.159.10.18])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbXJO-00019h-Q9
	for manet@ietf.org; Thu, 04 May 2006 02:27:44 -0400
Received: from pat4227 (pivert.int-evry.fr [157.159.100.42])
	by molure.int-evry.fr (Postfix) with SMTP id AD3AA3781F
	for <manet@ietf.org>; Thu,  4 May 2006 08:27:39 +0200 (CEST)
Message-ID: <001101c66f43$b4506f20$2a649f9d@intevry.fr>
From: "bekara c" <chakib.bekara@int-evry.fr>
To: <manet@ietf.org>
Date: Thu, 4 May 2006 08:26:40 +0200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: [manet] question about sensor network 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2010382105=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2010382105==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C66F54.77CE90C0"

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C66F54.77CE90C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all !

Can some one tell me whic simulator (NS2, Glomosim, etc.) is the best =
suitable for simulating sensor networks ?

Thinks!


------=_NextPart_000_000E_01C66F54.77CE90C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2716.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi all !</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Can some one tell me whic simulator =
(NS2, Glomosim,=20
etc.) is the best suitable for simulating sensor networks ?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thinks!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_000E_01C66F54.77CE90C0--



--===============2010382105==
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

--===============2010382105==--





From manet-bounces@ietf.org Thu May 04 04:44:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbZRs-0001DL-9w; Thu, 04 May 2006 04:44:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbZRp-0001Bl-L3
	for manet@ietf.org; Thu, 04 May 2006 04:44:33 -0400
Received: from web54608.mail.yahoo.com ([206.190.49.178])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FbZRl-0006xF-7b
	for manet@ietf.org; Thu, 04 May 2006 04:44:33 -0400
Received: (qmail 22600 invoked by uid 60001); 4 May 2006 08:44:28 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=ag7ufmD2GbNpDDzFmE2GnSbtxmoMp+1GYJoDJobT9TlWPaRiEgOwk+ksvrALq6Hqh/JZxjYkgqDoE2F5yG1f3Mhklt8hhbunO4vBvLjeC/GF1xa3lAYNzWsF54RVdhBuZ9/oEfLgTr3ukbf2L3t5sx62wsTpeJSVh3l7Zv5Hb5E=
	; 
Message-ID: <20060504084428.22598.qmail@web54608.mail.yahoo.com>
Received: from [82.201.196.144] by web54608.mail.yahoo.com via HTTP;
	Thu, 04 May 2006 01:44:28 PDT
Date: Thu, 4 May 2006 01:44:28 -0700 (PDT)
From: amr hassan <amr_hassan1@yahoo.com>
To: manet@ietf.org
In-Reply-To: <E1FbJlu-0005Wy-O9@megatron.ietf.org>
MIME-Version: 1.0
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Subject: [manet] Re: the definition of neighbor
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1234484160=="
Errors-To: manet-bounces@ietf.org

--===============1234484160==
Content-Type: multipart/alternative; boundary="0-1807145441-1146732268=:21725"
Content-Transfer-Encoding: 8bit

--0-1807145441-1146732268=:21725
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi,
   
  A neighbor is a node that you can reach with a single hop. Of course this depends on the value of the radio TX power (so it is not absolutely 250m, it depends).

If you apply this to the hello messages being sent in AODV. Then yes, nodes receiving the hello messages are neighbors.
   
  Kind regards,
  Amr
  
Message: 4
Date: Wed, 3 May 2006 13:35:11 +0200 (CEST)
From: www triste 
Subject: [manet] the definition of neighbor
To: manet@ietf.org
Message-ID: <20060503113511.91148.qmail@web26606.mail.ukl.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"

Hello everybody
i want to know what is the real definition of neighbor?
x is neighbor of y = distance between x and y < 250 (and why exactly 250)

or

x is neighbor of y=y can receive hello paquets

(i discuss in general,with olsr,aodv,dsdv .... routing protocols)

Thanks for help or indication, 

		
---------------------------------
New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.
--0-1807145441-1146732268=:21725
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>Hi,</DIV>  <DIV>&nbsp;</DIV>  <DIV>A neighbor is a node that you can reach with a single hop. Of course this depends on the value of the radio&nbsp;TX power (so it is not absolutely 250m, it depends).<BR><BR>If you apply this to the hello messages being sent in AODV. Then yes, nodes receiving the hello messages are neighbors.</DIV>  <DIV>&nbsp;</DIV>  <DIV>Kind regards,</DIV>  <DIV>Amr</DIV>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"><BR>Message: 4<BR>Date: Wed, 3 May 2006 13:35:11 +0200 (CEST)<BR>From: www triste <UNHAPY1983@YAHOO.FR><BR>Subject: [manet] the definition of neighbor<BR>To: manet@ietf.org<BR>Message-ID: &lt;20060503113511.91148.qmail@web26606.mail.ukl.yahoo.com&gt;<BR>Content-Type: text/plain; charset="iso-8859-1"<BR><BR>Hello everybody<BR>i want to know what is the real definition of neighbor?<BR>x is neighbor of y = distance between x and y &lt; 250 (and why exactly 250)<BR><BR>or<BR><BR>x is
 neighbor of y=y can receive hello paquets<BR><BR>(i discuss in general,with olsr,aodv,dsdv .... routing protocols)<BR><BR>Thanks for help or indication, <BR></BLOCKQUOTE><p>
		<hr size=1>New Yahoo! Messenger with Voice. <a href="http://us.rd.yahoo.com/mail_us/taglines/postman5/*http://us.rd.yahoo.com/evt=39666/*http://messenger.yahoo.com">Call regular phones from your PC</a> and save big.
--0-1807145441-1146732268=:21725--


--===============1234484160==
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

--===============1234484160==--




From manet-bounces@ietf.org Thu May 04 12:50:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbh1N-0004iG-17; Thu, 04 May 2006 12:49:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbh1L-0004iB-BV
	for manet@ietf.org; Thu, 04 May 2006 12:49:43 -0400
Received: from mx2.buaa.edu.cn ([219.239.227.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbh1F-0003tm-Ky
	for manet@ietf.org; Thu, 04 May 2006 12:49:43 -0400
Received: from mx1.buaa.edu.cn (mx1.buaa.edu.cn [192.168.128.5])
	by mx2.buaa.edu.cn (Postfix) with ESMTP id 535CA37E9F
	for <manet@ietf.org>; Fri,  5 May 2006 00:47:42 +0800 (CST)
Received: from [211.71.6.143] by 10.0.0.130 with StormMail ESMTP id
	17294.1612854181; Fri, 5 May 2006 01:06:39 +0800 (CST)
Date: Fri, 5 May 2006 00:48:11 +0800
From: "Luo.Gang" <luogang@vrlab.buaa.edu.cn>
To: "manet" <manet@ietf.org>
Organization: BUAA VR lab
X-mailer: Foxmail 5.0 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
Message-Id: <20060504164742.535CA37E9F@mx2.buaa.edu.cn>
X-Spam-Score: 4.1 (++++)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Subject: [manet] Curious about how to evaluate the performance of ad hoc
	network protocols
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: luogang@vrlab.buaa.edu.cn
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi all,

	Many routing protocol have been proposed to MANET WG, such as AODV, DSR, OLSR, even RMP, PMP. People usuall evaluate the protocol performance by simulation in their literatures.

	I believe that the antena model, the mobility model and the traffic model have a large effect on the performance evaluation of an ad hoc network protocol.
	I wonder is there any performance evaluation test-suit/benchmark/standard or something similar have been proposed for evaluate these protocols in some specific scenarios?

	Does MANET WG concern about this problem? (How to evaluate the performance of ad hoc network protocols without bias)
	I am sorry if I've asked a stupid question.:)
	Any Information, opinion and recommands will be helpful to me, thanks in advance.

Regards,
--
Luo Gang


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



From manet-bounces@ietf.org Thu May 04 13:25:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbha6-0003Ll-B8; Thu, 04 May 2006 13:25:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbha5-0003Lg-7s
	for manet@ietf.org; Thu, 04 May 2006 13:25:37 -0400
Received: from mail.av.it.pt ([193.136.92.53] helo=av.it.pt)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbha2-0005Cd-S3
	for manet@ietf.org; Thu, 04 May 2006 13:25:37 -0400
Received: from [193.136.93.160] (account vjesus [193.136.93.160] verified)
	by av.it.pt (CommuniGate Pro SMTP 5.0.9)
	with ESMTPSA id 4634682; Thu, 04 May 2006 18:25:33 +0100
Message-ID: <445A3915.4080003@av.it.pt>
Date: Thu, 04 May 2006 18:25:41 +0100
From: =?GB2312?B?VqiqdG9yIEplc3Vz?= <vjesus@av.it.pt>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: luogang@vrlab.buaa.edu.cn
Subject: Re: [manet] Curious about how to evaluate the performance of ad hoc
	network protocols
References: <20060504164742.535CA37E9F@mx2.buaa.edu.cn>
In-Reply-To: <20060504164742.535CA37E9F@mx2.buaa.edu.cn>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: manet <manet@ietf.org>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Luo,

Actually, your question is extremelly pertinent and I have thought of it
many many times and sometimes I just wished there were some kind of a
template or guidelaines for simulations in MANETs.

>From my own experience, it can be very hard to compare two solutions for
the same problem in MANETs. When it comes to routing, it can be a
nightmare, since you end up wondering how a routing protocol evaluation
can be so much subjective.

Part of the problem is... defining the problem. Even a routing protocol
can be analysed in multiples ways, each with its own performance metrics.
The other problem is the conditions under which the performance is
evaluated. Take a look at a paper called "MANET Simulation Studies: The
Incredibles" by Kurkowski and others.

Best regards,
--v¨ªtor jesus







Luo.Gang wrote:
> Hi all,
>
> 	Many routing protocol have been proposed to MANET WG, such as AODV, DSR, OLSR, even RMP, PMP. People usuall evaluate the protocol performance by simulation in their literatures.
>
> 	I believe that the antena model, the mobility model and the traffic model have a large effect on the performance evaluation of an ad hoc network protocol.
> 	I wonder is there any performance evaluation test-suit/benchmark/standard or something similar have been proposed for evaluate these protocols in some specific scenarios?
>
> 	Does MANET WG concern about this problem? (How to evaluate the performance of ad hoc network protocols without bias)
> 	I am sorry if I've asked a stupid question.:)
> 	Any Information, opinion and recommands will be helpful to me, thanks in advance.
>
> Regards,
> --
> Luo Gang
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>
>   


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



From manet-bounces@ietf.org Thu May 04 13:56:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbi3W-0005Io-5a; Thu, 04 May 2006 13:56:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbi3U-0005Ij-2B
	for manet@ietf.org; Thu, 04 May 2006 13:56:00 -0400
Received: from fw02.rockwellcollins.com ([205.175.225.45])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbi3T-0006QR-6q
	for manet@ietf.org; Thu, 04 May 2006 13:56:00 -0400
Received: by fw02.Rockwellcollins.com; id MAA09766;
	Thu, 4 May 2006 12:55:55 -0500 (CDT)
From: <jasteven@rockwellcollins.com>
Received: from nodnsquery(131.198.169.131) by fw02.rockwellcollins.com via
	smap (V5.5) id xma009409; Thu, 4 May 06 12:55:03 -0500
Received: from vs01.rockwellcollins.com (localhost [127.0.0.1])
	by localhost.rockwellcollins.com (Postfix) with ESMTP id 277BC31881
	for <manet@ietf.org>; Thu,  4 May 2006 12:55:04 -0500 (CDT)
Received: from crnotes2.rockwellcollins.com (crnotes2.rockwellcollins.com
	[131.198.64.109])
	by vs01.rockwellcollins.com (Postfix) with ESMTP id DCE4C3187B
	for <manet@ietf.org>; Thu,  4 May 2006 12:55:03 -0500 (CDT)
In-Reply-To: <E1FbgFa-0007Yt-8w@megatron.ietf.org>
To: manet@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.2 June 01, 2004
Message-ID: <OF85C47C99.169C5FB8-ON86257164.00621C23-86257164.00626B1C@rockwellcollins.com>
Date: Thu, 4 May 2006 12:54:59 -0500
X-MIMETrack: Serialize by Router on
	CollinsCRSMTP02/CedarRapids/RockwellCollins(Release
	6.5.4FP3|January 09, 2006) at 05/04/2006 12:55:02 PM,
	Serialize complete at 05/04/2006 12:55:02 PM
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Subject: [manet] Re: MANET definition of a neighbor
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1577077620=="
Errors-To: manet-bounces@ietf.org

This is a multipart message in MIME format.
--===============1577077620==
Content-Type: multipart/alternative;
	boundary="=_alternative 00626B1686257164_="

This is a multipart message in MIME format.
--=_alternative 00626B1686257164_=
Content-Type: text/plain; charset="US-ASCII"

The definition of a neighbor is why wireless MANETs are so much more 
difficult than wireline networks.  In fact, one could say that the problem 
of determining who is a MANET neighbor and controlling the link to MANET 
neighbors sums up the problems and complexities associated with MANETs - 
at least to a first order approximation!

The old DARPA Packet Radio and SURAN work (from 1970s through 1980s) used 
the term neighbor to indicate nodes that had been heard over the air 
within a given time period.  [for example, see Jubin, J., and Tornow, J. 
D. (January 1987). "The DARPA Packet Radio Network Protocols". Proceedings 
of the IEEE]

If it was judged that the probability of transmitting and receiving 
packets to/from the neighboring node was estimated to be above some 
threshold, say 80%, then the neighbor was considered to be a GOOD NEIGHBOR 
and it was considered to be a neighbor for routing.

If it was judged that the probability of transmitting or receiving packets 
to/from the neighboring node was estimated to be below that same 
threshold, then the node was considered to be a BAD NEIGHBOR and it was 
not considered to be a neighbor for routing.

Information was maintained about the ability of the link between good 
neighbors to carry traffic at different data rates.  Stateful control 
loops were used to decide when to switch a node between {"not-a-neighbor", 
"bad-neighbor", and "good-neighbor"} states.  Nodes could get out of synch 
with one another, i.e. node A thinks it is a good neighbor to node B while 
node B thinks they are bad neighbors.  And the neighbor states can change 
dynamically, i.e. as nodes move about, two nodes will dynamically move 
from bad-neighbor to good-neighbor and back to bad-neighbor.

Variants of Least Interference Routing (LIR) in the DARPA SURAN work even 
went further to consider an additional state for potential interfering 
nodes & added an additional state called INTERFERING NEIGHBOR - which 
might be nodes 2 hops away from a routing sense.  [Stevens, J, 1988, 
"Spatial Reuse Through Dynamic Power and Routing Control in Common-Channel 
Random-Access Packet Radio Networks", UTD PhD thesis] This would be 
neighbors that are so far away that they cannot be heard well enough to be 
considered even a bad-neighbor, but are close enough that their 
transmissions can interfere at the channel access layer. 

These cross-layer interactions in MANET networks are what make MANETs so 
difficult to optimize.  This is why DARPA has started their new CBMANET 
work.

As Dr. Mullen noted, many simulations use simplistic assumptions, such as 
all nodes within a radius X are neighbors (i.e. can transmit and receive 
packets) while all nodes outside that radius are not neighbor (i.e. cannot 
transmit and receive - not even to interfere with one another).  These 
simplifying assumptions speed up the simulation development and execution, 
but can lead to significantly inaccurate results.

So why am I making this soliloquy?  I guess it is to encourage all of us 
working in MANETs to think about what it means to be a neighbor and the 
fact that being a neighbor is not just hearing a protocol beacon.  And we 
need to apply control theory to our algorithms that determine neighbor 
state (as well as the link state to our neighbors) to keep the algorithm 
output stable.

Jim Stevens
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
James A. Stevens, PhD
Chief Network Architect
Rockwell Collins Government Systems

--=_alternative 00626B1686257164_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">The definition of a neighbor is why
wireless MANETs are so much more difficult than wireline networks. &nbsp;In
fact, one could say that the problem of determining who is a MANET neighbor
and controlling the link to MANET neighbors sums up the problems and complexities
associated with MANETs - at least to a first order approximation!</font>
<br>
<br><font size=2 face="sans-serif">The old DARPA Packet Radio and SURAN
work (from 1970s through 1980s) used the term neighbor to indicate nodes
that had been heard over the air within a given time period. &nbsp;[for
example, see Jubin, J., and Tornow, J. D. (January 1987). &quot;The DARPA
Packet Radio Network Protocols&quot;. Proceedings of the IEEE]</font>
<br>
<br><font size=2 face="sans-serif">If it was judged that the probability
of transmitting and receiving packets to/from the neighboring node was
estimated to be above some threshold, say 80%, then the neighbor was considered
to be a GOOD NEIGHBOR and it was considered to be a neighbor for routing.</font>
<br>
<br><font size=2 face="sans-serif">If it was judged that the probability
of transmitting or receiving packets to/from the neighboring node was estimated
to be below that same threshold, then the node was considered to be a BAD
NEIGHBOR and it was not considered to be a neighbor for routing.</font>
<br>
<br><font size=2 face="sans-serif">Information was maintained about the
ability of the link between good neighbors to carry traffic at different
data rates. &nbsp;Stateful control loops were used to decide when to switch
a node between {&quot;not-a-neighbor&quot;, &quot;bad-neighbor&quot;, and
&quot;good-neighbor&quot;} states. &nbsp;Nodes could get out of synch with
one another, i.e. node A thinks it is a good neighbor to node B while node
B thinks they are bad neighbors. &nbsp;And the neighbor states can change
dynamically, i.e. as nodes move about, two nodes will dynamically move
from bad-neighbor to good-neighbor and back to bad-neighbor.</font>
<br>
<br><font size=2 face="sans-serif">Variants of Least Interference Routing
(LIR) in the DARPA SURAN work even went further to consider an additional
state for potential interfering nodes &amp; added an additional state called
INTERFERING NEIGHBOR - which might be nodes 2 hops away from a routing
sense. &nbsp;[Stevens, J, 1988, &quot;Spatial Reuse Through Dynamic Power
and Routing Control in Common-Channel Random-Access Packet Radio Networks&quot;,
UTD PhD thesis] This would be neighbors that are so far away that they
cannot be heard well enough to be considered even a bad-neighbor, but are
close enough that their transmissions can interfere at the channel access
layer. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">These cross-layer interactions in MANET
networks are what make MANETs so difficult to optimize. &nbsp;This is why
DARPA has started their new CBMANET work.</font>
<br>
<br><font size=2 face="sans-serif">As Dr. Mullen noted, many simulations
use simplistic assumptions, such as all nodes within a radius X are neighbors
(i.e. can transmit and receive packets) while all nodes outside that radius
are not neighbor (i.e. cannot transmit and receive - not even to interfere
with one another). &nbsp;These simplifying assumptions speed up the simulation
development and execution, but can lead to significantly inaccurate results.</font>
<br>
<br><font size=2 face="sans-serif">So why am I making this soliloquy? &nbsp;I
guess it is to encourage all of us working in MANETs to think about what
it means to be a neighbor and the fact that being a neighbor is not just
hearing a protocol beacon. &nbsp;And we need to apply control theory to
our algorithms that determine neighbor state (as well as the link state
to our neighbors) to keep the algorithm output stable.</font>
<br>
<br><font size=2 face="sans-serif">Jim Stevens</font>
<br><font size=2 face="sans-serif">- - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - -</font>
<br><font size=2 face="sans-serif">James A. Stevens, PhD</font>
<br><font size=2 face="sans-serif">Chief Network Architect</font>
<br><font size=2 face="sans-serif">Rockwell Collins Government Systems</font>
<br>
--=_alternative 00626B1686257164_=--


--===============1577077620==
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

--===============1577077620==--




From manet-bounces@ietf.org Thu May 04 14:14:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbiKt-0008Lg-Tp; Thu, 04 May 2006 14:13:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbiKs-0008Lb-J1
	for manet@ietf.org; Thu, 04 May 2006 14:13:58 -0400
Received: from smtp-bedford-x.mitre.org ([192.160.51.76]
	helo=smtp-bedford.mitre.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbiKp-00070n-91
	for manet@ietf.org; Thu, 04 May 2006 14:13:58 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-bedford.mitre.org (8.12.11.20060308/8.11.6) with SMTP id
	k44IDrGu002723 for <manet@ietf.org>; Thu, 4 May 2006 14:13:53 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-bedford.mitre.org (Postfix) with ESMTP id CCA24BF00
	for <manet@ietf.org>; Thu,  4 May 2006 14:13:52 -0400 (EDT)
Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4])
	by smtp-bedford.mitre.org (8.12.11.20060308/8.12.11) with ESMTP id
	k44IDook002690 for <manet@ietf.org>; Thu, 4 May 2006 14:13:50 -0400
Received: from [129.83.175.29] ([129.83.175.29]) by imcfe2.MITRE.ORG with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 4 May 2006 14:13:50 -0400
Message-ID: <445A44ED.5040903@mitre.org>
Date: Thu, 04 May 2006 14:16:13 -0400
From: Kenneth Brayer <kb@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor
References: <OF85C47C99.169C5FB8-ON86257164.00621C23-86257164.00626B1C@rockwellcollins.com>
In-Reply-To: <OF85C47C99.169C5FB8-ON86257164.00621C23-86257164.00626B1C@rockwellcollins.com>
X-OriginalArrivalTime: 04 May 2006 18:13:50.0595 (UTC)
	FILETIME=[7E9A8D30:01C66FA6]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0179403894=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.
--===============0179403894==
Content-Type: multipart/alternative;
	boundary="------------050400030807060406060705"

This is a multi-part message in MIME format.
--------------050400030807060406060705
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

It strikes me that a neighbor of Node A is any node that A can setup a 
link to, whether it be next door or 300 miles away. A node that the 
second node can setup a link to but that A cannot setup a link to is a 
neighbor once removed, etc. Once you know who the neighbors are you can 
build a network routing table.

See
Packet switching for mobile earth stations via low-orbit satellite network
Brayer, K.;
Proceedings of the IEEE 
<http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=5>
Volume 72,  Issue 11,  Nov. 1984 Page(s):1627 - 1636

Available online in IEEE XPLORE

Ken


-- 
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841


--------------050400030807060406060705
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
It strikes me that a neighbor of Node A is any node that A can setup a
link to, whether it be next door or 300 miles away. A node that the
second node can setup a link to but that A cannot setup a link to is a
neighbor once removed, etc. Once you know who the neighbors are you can
build a network routing table.<br>
<br>
See<br>
<strong>Packet switching for mobile earth stations via low-orbit
satellite network</strong><br>
Brayer, K.;<br>
<a href="http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=5">Proceedings
of the IEEE</a><br>
Volume 72,&nbsp;
Issue 11,&nbsp;
Nov. 1984
Page(s):1627 - 1636
<br>
<br>
Available online in IEEE XPLORE<br>
<br>
Ken<br>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: <a class="moz-txt-link-abbreviated" href="mailto:kb@mitre.org">kb@mitre.org</a>
tele: 781-271-5254
fax: 781-271-2841
</pre>
</body>
</html>

--------------050400030807060406060705--


--===============0179403894==
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

--===============0179403894==--




From manet-bounces@ietf.org Thu May 04 14:33:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbidP-0001a7-QZ; Thu, 04 May 2006 14:33:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbidO-0001a2-Gk
	for manet@ietf.org; Thu, 04 May 2006 14:33:06 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbidN-0008C8-2K
	for manet@ietf.org; Thu, 04 May 2006 14:33:06 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Thu, 4 May 2006 12:33:02 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF02D@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvpongNUynhltrS4m+ywY9GpusJAAAPjOA
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "Kenneth Brayer" <kb@mitre.org>,
	<manet@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0270584447=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0270584447==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C66FA9.2E3CBB09"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C66FA9.2E3CBB09
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Ken,
=20
Well, that is a good functional definition, but a bit tricky in
practice.  As Jim pointed out, wireless communications is a random
process and it may not be clear whether or not you can set up a link.
For example, due to fading, you may receive an especially hot packet and
assume, incorrectly, that there is a reliable link.  The same randomness
could cause a packet to be dropped due to a chance low-powered signal.
Also, there are the effects of shadowing, fluctuating interference
levels and the possibility of a data collision.  A buffer could overflow
on a heavily-used node and we could infur, incorrectly, that the link is
bad.  Finally, MANETs are, by definition, mobile, so any data table you
have now is likely to be in error in a few minutes or less.
=20
You are correct in that if we knew who our neighbors are, we could set
up the network.  The problem is that in practice, we know nothing and
need to proceed on the basis of intelligent guesses.  I think that a
bigger problem is that so much work is done in MANET protocol design
that completely ignores this problem.
=20

John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
 =20

=20

________________________________

From: Kenneth Brayer [mailto:kb@mitre.org]=20
Sent: Thursday, May 04, 2006 12:16 PM
To: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


It strikes me that a neighbor of Node A is any node that A can setup a
link to, whether it be next door or 300 miles away. A node that the
second node can setup a link to but that A cannot setup a link to is a
neighbor once removed, etc. Once you know who the neighbors are you can
build a network routing table.

See
Packet switching for mobile earth stations via low-orbit satellite
network
Brayer, K.;
Proceedings of the IEEE
<http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=3D5>=20
Volume 72,  Issue 11,  Nov. 1984 Page(s):1627 - 1636=20

Available online in IEEE XPLORE

Ken



--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841

------_=_NextPart_001_01C66FA9.2E3CBB09
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D963062118-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Ken,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D963062118-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D963062118-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Well, that is a good functional definition, but =
a bit=20
tricky in practice.&nbsp; As Jim pointed out, wireless communications is =
a=20
random process and it may not be clear whether or not you can set up a=20
link.&nbsp; For example, due to fading, you may receive an especially =
hot packet=20
and assume, incorrectly, that there is a reliable link.&nbsp; The same=20
randomness could cause a packet to be dropped due to a chance =
low-powered=20
signal.&nbsp; Also, there are the effects of shadowing,&nbsp;fluctuating =

interference levels and the possibility of a data collision.&nbsp; A =
buffer=20
could overflow on a heavily-used node and we could infur, incorrectly, =
that the=20
link is bad.&nbsp; Finally,&nbsp;MANETs are, by definition,&nbsp;mobile, =
so any=20
data table you have now is likely to be in error in a few minutes or=20
less.</FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D963062118-04052006><FONT face=3DArial color=3D#0000ff =
size=3D2>You=20
are correct in that if we knew who our neighbors are, we could set up =
the=20
network.&nbsp; The problem is that in practice, we know nothing and need =
to=20
proceed on the basis of intelligent guesses.&nbsp; I think that a bigger =
problem=20
is that so much work is done in MANET protocol design that completely =
ignores=20
this problem.</FONT></SPAN></DIV>
<DIV><SPAN class=3D963062118-04052006><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV><!-- Converted from text/plain format =
-->
<P><FONT size=3D2>John P. Mullen, Ph.D.<BR>(505)=20
646-2958<BR>jomullen@nmsu.edu<BR>&nbsp;</FONT> </P>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Kenneth Brayer =
[mailto:kb@mitre.org]=20
<BR><B>Sent:</B> Thursday, May 04, 2006 12:16 PM<BR><B>To:</B>=20
manet@ietf.org<BR><B>Subject:</B> Re: [manet] Re: MANET definition of a=20
neighbor<BR></FONT><BR></DIV>
<DIV></DIV>It strikes me that a neighbor of Node A is any node that A =
can setup=20
a link to, whether it be next door or 300 miles away. A node that the =
second=20
node can setup a link to but that A cannot setup a link to is a neighbor =
once=20
removed, etc. Once you know who the neighbors are you can build a =
network=20
routing table.<BR><BR>See<BR><STRONG>Packet switching for mobile earth =
stations=20
via low-orbit satellite network</STRONG><BR>Brayer, K.;<BR><A=20
href=3D"http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=3D5">Proc=
eedings of=20
the IEEE</A><BR>Volume 72,&nbsp; Issue 11,&nbsp; Nov. 1984 Page(s):1627 =
- 1636=20
<BR><BR>Available online in IEEE XPLORE<BR><BR>Ken<BR><BR><BR><PRE =
class=3Dmoz-signature cols=3D"72">--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:kb@mitre.org">kb@mitre.org</A>
tele: 781-271-5254
fax: 781-271-2841
</PRE></BODY></HTML>

------_=_NextPart_001_01C66FA9.2E3CBB09--


--===============0270584447==
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

--===============0270584447==--




From manet-bounces@ietf.org Thu May 04 14:45:08 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbioy-00041R-7v; Thu, 04 May 2006 14:45:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbiow-0003rC-6q
	for manet@ietf.org; Thu, 04 May 2006 14:45:02 -0400
Received: from smtp-bedford-x.mitre.org ([192.160.51.76]
	helo=smtp-bedford.mitre.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbiou-0000N2-OU
	for manet@ietf.org; Thu, 04 May 2006 14:45:02 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-bedford.mitre.org (8.12.11.20060308/8.11.6) with SMTP id
	k44Ij0KS028566 for <manet@ietf.org>; Thu, 4 May 2006 14:45:00 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-bedford.mitre.org (Postfix) with ESMTP id 59682BF01
	for <manet@ietf.org>; Thu,  4 May 2006 14:45:00 -0400 (EDT)
Received: from imcfe2.MITRE.ORG (imcfe2.mitre.org [129.83.29.4])
	by smtp-bedford.mitre.org (8.12.11.20060308/8.12.11) with ESMTP id
	k44IixZW028555; Thu, 4 May 2006 14:44:59 -0400
Received: from [129.83.175.29] ([129.83.175.29]) by imcfe2.MITRE.ORG with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 4 May 2006 14:44:59 -0400
Message-ID: <445A4C3A.2030203@mitre.org>
Date: Thu, 04 May 2006 14:47:22 -0400
From: Kenneth Brayer <kb@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Mullen, John" <jomullen@ad.nmsu.edu>
Subject: Re: [manet] Re: MANET definition of a neighbor
References: <8536FDFA3AD04A49A15804915996569106DEF02D@exchange1.ACN.ad.nmsu.edu>
In-Reply-To: <8536FDFA3AD04A49A15804915996569106DEF02D@exchange1.ACN.ad.nmsu.edu>
X-OriginalArrivalTime: 04 May 2006 18:44:59.0762 (UTC)
	FILETIME=[D8B6CD20:01C66FAA]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0bb031f3a6fb29f760794ac9bf1997ae
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1907641464=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1907641464==
Content-Type: multipart/alternative;
	boundary="------------060705050501000709050605"

This is a multi-part message in MIME format.
--------------060705050501000709050605
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

John
What you are saying is that the topology is , for many reasons, 
variable. Your neighbors are constantly changing. So you also need a 
means to track who your neighbors are as a function of time. So now you 
are into reactive and proactive protocols.

So the real question is who are your neighbors as a function of time in 
a MANET. A MANET protocol should try to determine this so it can deliver 
messages when they are presented to the network.

My paper deals with point to point satellites, but you have the never 
ending list of protocols, DSR, ABR, ZRP, OLSR, etc. all of which try to 
deal with this problem, how to track topology changes.

Ken

Mullen, John wrote:

> Hi Ken,
>  
> Well, that is a good functional definition, but a bit tricky in 
> practice.  As Jim pointed out, wireless communications is a random 
> process and it may not be clear whether or not you can set up a link.  
> For example, due to fading, you may receive an especially hot packet 
> and assume, incorrectly, that there is a reliable link.  The same 
> randomness could cause a packet to be dropped due to a chance 
> low-powered signal.  Also, there are the effects of 
> shadowing, fluctuating interference levels and the possibility of a 
> data collision.  A buffer could overflow on a heavily-used node and we 
> could infur, incorrectly, that the link is bad.  Finally, MANETs are, 
> by definition, mobile, so any data table you have now is likely to be 
> in error in a few minutes or less.
>  
> You are correct in that if we knew who our neighbors are, we could set 
> up the network.  The problem is that in practice, we know nothing and 
> need to proceed on the basis of intelligent guesses.  I think that a 
> bigger problem is that so much work is done in MANET protocol design 
> that completely ignores this problem.
>  
>
> John P. Mullen, Ph.D.
> (505) 646-2958
> jomullen@nmsu.edu
>  
>
>  
>
> ------------------------------------------------------------------------
> From: Kenneth Brayer [mailto:kb@mitre.org]
> Sent: Thursday, May 04, 2006 12:16 PM
> To: manet@ietf.org
> Subject: Re: [manet] Re: MANET definition of a neighbor
>
> It strikes me that a neighbor of Node A is any node that A can setup a 
> link to, whether it be next door or 300 miles away. A node that the 
> second node can setup a link to but that A cannot setup a link to is a 
> neighbor once removed, etc. Once you know who the neighbors are you 
> can build a network routing table.
>
> See
> Packet switching for mobile earth stations via low-orbit satellite network
> Brayer, K.;
> Proceedings of the IEEE 
> <http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=5>
> Volume 72,  Issue 11,  Nov. 1984 Page(s):1627 - 1636
>
> Available online in IEEE XPLORE
>
> Ken
>
>
>-- 
>Kenneth Brayer
>Fellow of the IEEE
>M/S M370
>The MITRE Corporation
>202 Burlington Road
>Bedford, MA 01730
>
>e-mail: kb@mitre.org
>tele: 781-271-5254
>fax: 781-271-2841
>  
>

-- 
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841


--------------060705050501000709050605
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
John<br>
What you are saying is that the topology is , for many reasons,
variable. Your neighbors are constantly changing. So you also need a
means to track who your neighbors are as a function of time. So now you
are into reactive and proactive protocols.<br>
<br>
So the real question is who are your neighbors as a function of time in
a MANET. A MANET protocol should try to determine this so it can
deliver messages when they are presented to the network. <br>
<br>
My paper deals with point to point satellites, but you have the never
ending list of protocols, DSR, ABR, ZRP, OLSR, etc. all of which try to
deal with this problem, how to track topology changes.<br>
<br>
Ken<br>
<br>
Mullen, John wrote:<br>
<blockquote
 cite="mid8536FDFA3AD04A49A15804915996569106DEF02D@exchange1.ACN.ad.nmsu.edu"
 type="cite">
  <title></title>
  <meta http-equiv="Content-Type" content="text/html; ">
  <meta content="MSHTML 6.00.2900.2873" name="GENERATOR">
  <div align="left" dir="ltr"><span class="963062118-04052006"><font
 color="#0000ff" face="Arial" size="2">Hi Ken,</font></span></div>
  <div align="left" dir="ltr"><span class="963062118-04052006"></span>&nbsp;</div>
  <div align="left" dir="ltr"><span class="963062118-04052006"><font
 color="#0000ff" face="Arial" size="2">Well, that is a good functional
definition, but a bit tricky in practice.&nbsp; As Jim pointed out, wireless
communications is a random process and it may not be clear whether or
not you can set up a link.&nbsp; For example, due to fading, you may receive
an especially hot packet and assume, incorrectly, that there is a
reliable link.&nbsp; The same randomness could cause a packet to be dropped
due to a chance low-powered signal.&nbsp; Also, there are the effects of
shadowing,&nbsp;fluctuating interference levels and the possibility of a
data collision.&nbsp; A buffer could overflow on a heavily-used node and we
could infur, incorrectly, that the link is bad.&nbsp; Finally,&nbsp;MANETs are,
by definition,&nbsp;mobile, so any data table you have now is likely to be
in error in a few minutes or less.</font></span></div>
  <div>&nbsp;</div>
  <div><span class="963062118-04052006"><font color="#0000ff"
 face="Arial" size="2">You are correct in that if we knew who our
neighbors are, we could set up the network.&nbsp; The problem is that in
practice, we know nothing and need to proceed on the basis of
intelligent guesses.&nbsp; I think that a bigger problem is that so much
work is done in MANET protocol design that completely ignores this
problem.</font></span></div>
  <div><span class="963062118-04052006"></span>&nbsp;</div>
<!-- Converted from text/plain format -->
  <p><font size="2">John P. Mullen, Ph.D.<br>
(505) 646-2958<br>
<a class="moz-txt-link-abbreviated" href="mailto:jomullen@nmsu.edu">jomullen@nmsu.edu</a><br>
&nbsp;</font> </p>
  <div>&nbsp;</div>
  <br>
  <div class="OutlookMessageHeader" align="left" dir="ltr" lang="en-us">
  <hr tabindex="-1"><font face="Tahoma" size="2"><b>From:</b> Kenneth
Brayer [<a class="moz-txt-link-freetext" href="mailto:kb@mitre.org">mailto:kb@mitre.org</a>] <br>
  <b>Sent:</b> Thursday, May 04, 2006 12:16 PM<br>
  <b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:manet@ietf.org">manet@ietf.org</a><br>
  <b>Subject:</b> Re: [manet] Re: MANET definition of a neighbor<br>
  </font><br>
  </div>
It strikes me that a neighbor of Node A is any node that A can setup a
link to, whether it be next door or 300 miles away. A node that the
second node can setup a link to but that A cannot setup a link to is a
neighbor once removed, etc. Once you know who the neighbors are you can
build a network routing table.<br>
  <br>
See<br>
  <strong>Packet switching for mobile earth stations via low-orbit
satellite network</strong><br>
Brayer, K.;<br>
  <a href="http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=5">Proceedings
of the IEEE</a><br>
Volume 72,&nbsp; Issue 11,&nbsp; Nov. 1984 Page(s):1627 - 1636 <br>
  <br>
Available online in IEEE XPLORE<br>
  <br>
Ken<br>
  <br>
  <br>
  <pre class="moz-signature" cols="72">-- 
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: <a class="moz-txt-link-abbreviated" href="mailto:kb@mitre.org">kb@mitre.org</a>
tele: 781-271-5254
fax: 781-271-2841
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: <a class="moz-txt-link-abbreviated" href="mailto:kb@mitre.org">kb@mitre.org</a>
tele: 781-271-5254
fax: 781-271-2841
</pre>
</body>
</html>

--------------060705050501000709050605--


--===============1907641464==
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

--===============1907641464==--




From manet-bounces@ietf.org Thu May 04 15:00:48 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbj3s-0007QL-SX; Thu, 04 May 2006 15:00:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbj3r-0007PJ-1u
	for manet@ietf.org; Thu, 04 May 2006 15:00:27 -0400
Received: from fw01.rockwellcollins.com ([205.175.225.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbj3o-00011W-MO
	for manet@ietf.org; Thu, 04 May 2006 15:00:27 -0400
Received: by fw01.rockwellcollins.com; id OAA23988;
	Thu, 4 May 2006 14:00:23 -0500 (CDT)
From: <jasteven@rockwellcollins.com>
Received: from nodnsquery(131.198.169.131) by fw01.rockwellcollins.com via
	smap (V5.5) id xma023583; Thu, 4 May 06 14:00:01 -0500
Received: from vs01.rockwellcollins.com (localhost [127.0.0.1])
	by localhost.rockwellcollins.com (Postfix) with ESMTP id 81BC63187F
	for <manet@ietf.org>; Thu,  4 May 2006 14:00:03 -0500 (CDT)
Received: from crnotes2.rockwellcollins.com (crnotes2.rockwellcollins.com
	[131.198.64.109])
	by vs01.rockwellcollins.com (Postfix) with ESMTP id 530553187B
	for <manet@ietf.org>; Thu,  4 May 2006 14:00:03 -0500 (CDT)
In-Reply-To: <E1Fbioz-00047W-MZ@megatron.ietf.org>
To: manet@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.2 June 01, 2004
Message-ID: <OF7BED0D40.CD503A84-ON86257164.0067B14D-86257164.00685D79@rockwellcollins.com>
Date: Thu, 4 May 2006 13:59:56 -0500
X-MIMETrack: Serialize by Router on
	CollinsCRSMTP02/CedarRapids/RockwellCollins(Release
	6.5.4FP3|January 09, 2006) at 05/04/2006 02:00:01 PM,
	Serialize complete at 05/04/2006 02:00:01 PM
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Subject: [manet] Re: Neighbors
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1609023235=="
Errors-To: manet-bounces@ietf.org

This is a multipart message in MIME format.
--===============1609023235==
Content-Type: multipart/alternative;
	boundary="=_alternative 00685D7886257164_="

This is a multipart message in MIME format.
--=_alternative 00685D7886257164_=
Content-Type: text/plain; charset="US-ASCII"

Ken, you said that

>  So the real question is who are your neighbors
>  as a function of time in a MANET. A MANET protocol
>  should try to determine this so it can deliver 
>  messages when they are presented to the network.
>
>  My paper deals with point to point satellites, 
>  but you have the never ending list of protocols, 
>  DSR, ABR, ZRP, OLSR, etc. all of which try to deal 
>  with this problem, how to track topology changes."

The difficult problem in MANETs is not tracking the network topology per 
se (e.g. the never ending list of routing protocols), instead the 
difficult problem in MANETs is reliably & stably knowing who your 
neighbors are.

So, I agree with John that

>  ... if we knew who our neighbors are, we could set
>  up the network.  The problem is that in practice, 
>  we know nothing and need to proceed on the basis 
>  of intelligent guesses.  I think that a bigger 
>  problem is that so much work is done in MANET 
>  protocol design that completely ignores this problem.

Jim

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
James A. Stevens, PhD
Chief Network Architect
Rockwell Collins Government Systems

--=_alternative 00685D7886257164_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Ken, you said that</font>
<br>
<br><font size=2><tt>&gt; &nbsp;So the real question is who are your neighbors</tt></font>
<br><font size=2><tt>&gt; &nbsp;as a function of time in a MANET. A MANET
protocol</tt></font>
<br><font size=2><tt>&gt; &nbsp;should try to determine this so it can
deliver </tt></font>
<br><font size=2><tt>&gt; &nbsp;messages when they are presented to the
network.<br>
&gt;<br>
&gt; &nbsp;My paper deals with point to point satellites, </tt></font>
<br><font size=2><tt>&gt; &nbsp;but you have the never ending list of protocols,
</tt></font>
<br><font size=2><tt>&gt; &nbsp;DSR, ABR, ZRP, OLSR, etc. all of which
try to deal </tt></font>
<br><font size=2><tt>&gt; &nbsp;with this problem, how to track topology
changes.&quot;</tt></font>
<br>
<br><font size=2><tt>The difficult problem in MANETs is not tracking the
network topology per se (e.g. the never ending list of routing protocols),
instead the difficult problem in MANETs is reliably &amp; stably knowing
who your neighbors are.</tt></font>
<br>
<br><font size=2><tt>So, I agree with John that</tt></font>
<br>
<br><font size=2><tt>&gt; &nbsp;... if we knew who our neighbors are, we
could set</tt></font>
<br><font size=2><tt>&gt; &nbsp;up the network. &nbsp;The problem is that
in practice, </tt></font>
<br><font size=2><tt>&gt; &nbsp;we know nothing and need to proceed on
the basis </tt></font>
<br><font size=2><tt>&gt; &nbsp;of intelligent guesses. &nbsp;I think that
a bigger </tt></font>
<br><font size=2><tt>&gt; &nbsp;problem is that so much work is done in
MANET </tt></font>
<br><font size=2><tt>&gt; &nbsp;protocol design that completely ignores
this problem.</tt></font>
<br>
<br><font size=2><tt>Jim</tt></font>
<br><font size=2><tt><br>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<br>
James A. Stevens, PhD<br>
Chief Network Architect<br>
Rockwell Collins Government Systems</tt></font>
<br>
--=_alternative 00685D7886257164_=--


--===============1609023235==
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

--===============1609023235==--




From manet-bounces@ietf.org Thu May 04 15:07:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbjAf-0006QO-Ut; Thu, 04 May 2006 15:07:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbjAe-0006QJ-Lq
	for manet@ietf.org; Thu, 04 May 2006 15:07:28 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbjAc-0001Jy-V2
	for manet@ietf.org; Thu, 04 May 2006 15:07:28 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Thu, 4 May 2006 13:07:24 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF043@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvqt2NWFE4iSyMRnmMInpNywbArwAAIgvw
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "Kenneth Brayer" <kb@mitre.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: da41e01217ab11ad82db577473e913ae
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0619802368=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0619802368==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C66FAD.FB42EB89"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C66FAD.FB42EB89
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Ken,
=20
Not really.  What I'm saying is that while the topology is changing and
we need to keep up with the changes, the information available to any
node is a random sample from an extremely variable random process.  Even
if the nodes are stationary, the effects I mentioned earlier will occur.
These effects cloud the issue when a node tries to determine its local
topology. =20
=20
Regardless of whether the protocol is reactive or proactive, each node
must determine, on the basis of what it can and cannot detect,  whether
or not to consider a link good.  That is, the node is constantly testing
the hypothisis that a link is good against the alternative that it is
not.  As with any such tests, there is both a Type I and a Type II error
and efforts to reduce the probability of one will tend to increase the
probability of the other.  Furthermore, both errors lead to a
significant decrease in performance.  This is an extremely difficult
problem in a MANET, not only because the topology is changing, but also
because the traffic patterns are changing and nodes will have differing
levels of information from different local transmitters.
=20
Many of these problem do not exist in point-to-point satellite
communications.  For example, fading is not as great a factor and there
are fewer missing values.  Generally, one can use hefty power levels in
PTP and the beam is focused, but in MANETS, high power levels lead to
higher average interference levels and beaming is problemetic.  Finally,
in PTP, you expect transmissions from a  single transmitter, so you can
estimate average SNIR on the basis of signals that are too weak to
reliably decode, but in a MANET, a signal may be from any one of a
number of transmitters, so if it cannot be decoded, that information is
lost.
=20
But, if was easy, ....
=20
:-)
=20
John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
 =20
=20

________________________________

From: Kenneth Brayer [mailto:kb@mitre.org]=20
Sent: Thursday, May 04, 2006 12:47 PM
To: Mullen, John
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


John
What you are saying is that the topology is , for many reasons,
variable. Your neighbors are constantly changing. So you also need a
means to track who your neighbors are as a function of time. So now you
are into reactive and proactive protocols.

So the real question is who are your neighbors as a function of time in
a MANET. A MANET protocol should try to determine this so it can deliver
messages when they are presented to the network.=20

My paper deals with point to point satellites, but you have the never
ending list of protocols, DSR, ABR, ZRP, OLSR, etc. all of which try to
deal with this problem, how to track topology changes.

Ken

Mullen, John wrote:


	Hi Ken,
	=20
	Well, that is a good functional definition, but a bit tricky in
practice.  As Jim pointed out, wireless communications is a random
process and it may not be clear whether or not you can set up a link.
For example, due to fading, you may receive an especially hot packet and
assume, incorrectly, that there is a reliable link.  The same randomness
could cause a packet to be dropped due to a chance low-powered signal.
Also, there are the effects of shadowing, fluctuating interference
levels and the possibility of a data collision.  A buffer could overflow
on a heavily-used node and we could infur, incorrectly, that the link is
bad.  Finally, MANETs are, by definition, mobile, so any data table you
have now is likely to be in error in a few minutes or less.
	=20
	You are correct in that if we knew who our neighbors are, we
could set up the network.  The problem is that in practice, we know
nothing and need to proceed on the basis of intelligent guesses.  I
think that a bigger problem is that so much work is done in MANET
protocol design that completely ignores this problem.
	=20

	John P. Mullen, Ph.D.
	(505) 646-2958
	jomullen@nmsu.edu
	 =20

	=20

________________________________

	From: Kenneth Brayer [mailto:kb@mitre.org]=20
	Sent: Thursday, May 04, 2006 12:16 PM
	To: manet@ietf.org
	Subject: Re: [manet] Re: MANET definition of a neighbor
=09
=09
	It strikes me that a neighbor of Node A is any node that A can
setup a link to, whether it be next door or 300 miles away. A node that
the second node can setup a link to but that A cannot setup a link to is
a neighbor once removed, etc. Once you know who the neighbors are you
can build a network routing table.
=09
	See
	Packet switching for mobile earth stations via low-orbit
satellite network
	Brayer, K.;
	Proceedings of the IEEE
<http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=3D5>=20
	Volume 72,  Issue 11,  Nov. 1984 Page(s):1627 - 1636=20
=09
	Available online in IEEE XPLORE
=09
	Ken
=09
=09
=09
	--=20
	Kenneth Brayer
	Fellow of the IEEE
	M/S M370
	The MITRE Corporation
	202 Burlington Road
	Bedford, MA 01730
=09
	e-mail: kb@mitre.org
	tele: 781-271-5254
	fax: 781-271-2841
	 =20


--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841

------_=_NextPart_001_01C66FAD.FB42EB89
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Ken,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Not really.&nbsp; What I'm saying is that while =
the=20
topology is changing and we need to keep up with the changes, the =
information=20
available to any node is a random sample from an extremely variable =
random=20
process.&nbsp; Even if the nodes are stationary, the effects I mentioned =
earlier=20
will occur.&nbsp; These effects cloud the issue when a node tries to =
determine=20
its local topology.&nbsp; </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Regardless of whether the protocol is reactive =
or=20
proactive, each&nbsp;node must determine, on the basis of what it can =
and cannot=20
detect, &nbsp;whether or not to consider a link good.&nbsp; That is, the =
node is=20
constantly testing the hypothisis that a link is good against the =
alternative=20
that it is not.&nbsp; As with any such tests, there is both a Type I and =
a Type=20
II error and efforts to reduce the probability of one will tend to =
increase the=20
probability of the other.&nbsp; Furthermore, both errors lead to a =
significant=20
decrease in performance.&nbsp; This is an extremely difficult problem in =
a=20
MANET, not only because the topology is changing, but also because the =
traffic=20
patterns are changing and nodes will have differing levels of =
information from=20
different local transmitters.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Many of these problem do not exist in =
point-to-point=20
satellite communications.&nbsp; For example, fading is not as great a =
factor and=20
there are fewer missing values.&nbsp; Generally, one can use hefty power =
levels=20
in PTP and the beam is focused, but in MANETS, high power levels lead to =
higher=20
average interference levels and beaming is problemetic.&nbsp; Finally, =
in PTP,=20
you expect transmissions from a&nbsp; single transmitter, so you can =
estimate=20
average SNIR on the basis of signals that are too weak to reliably =
decode, but=20
in a MANET, a signal may be from any one of a number of transmitters, so =
if it=20
cannot be decoded, that information is lost.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>But, if was easy, ....</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D385564818-04052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>:-)</FONT></SPAN></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>John P. Mullen, Ph.D.<BR>(505)=20
646-2958<BR>jomullen@nmsu.edu<BR>&nbsp;</FONT> </DIV>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Kenneth Brayer =
[mailto:kb@mitre.org]=20
<BR><B>Sent:</B> Thursday, May 04, 2006 12:47 PM<BR><B>To:</B> Mullen,=20
John<BR><B>Cc:</B> manet@ietf.org<BR><B>Subject:</B> Re: [manet] Re: =
MANET=20
definition of a neighbor<BR></FONT><BR></DIV>
<DIV></DIV>John<BR>What you are saying is that the topology is , for =
many=20
reasons, variable. Your neighbors are constantly changing. So you also =
need a=20
means to track who your neighbors are as a function of time. So now you =
are into=20
reactive and proactive protocols.<BR><BR>So the real question is who are =
your=20
neighbors as a function of time in a MANET. A MANET protocol should try =
to=20
determine this so it can deliver messages when they are presented to the =

network. <BR><BR>My paper deals with point to point satellites, but you =
have the=20
never ending list of protocols, DSR, ABR, ZRP, OLSR, etc. all of which =
try to=20
deal with this problem, how to track topology =
changes.<BR><BR>Ken<BR><BR>Mullen,=20
John wrote:<BR>
<BLOCKQUOTE=20
cite=3Dmid8536FDFA3AD04A49A15804915996569106DEF02D@exchange1.ACN.ad.nmsu.=
edu=20
type=3D"cite">
  <META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D963062118-04052006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Hi Ken,</FONT></SPAN></DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN =
class=3D963062118-04052006></SPAN>&nbsp;</DIV>
  <DIV dir=3Dltr align=3Dleft><SPAN class=3D963062118-04052006><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>Well, that is a good functional definition, =
but a bit=20
  tricky in practice.&nbsp; As Jim pointed out, wireless communications =
is a=20
  random process and it may not be clear whether or not you can set up a =

  link.&nbsp; For example, due to fading, you may receive an especially =
hot=20
  packet and assume, incorrectly, that there is a reliable link.&nbsp; =
The same=20
  randomness could cause a packet to be dropped due to a chance =
low-powered=20
  signal.&nbsp; Also, there are the effects of =
shadowing,&nbsp;fluctuating=20
  interference levels and the possibility of a data collision.&nbsp; A =
buffer=20
  could overflow on a heavily-used node and we could infur, incorrectly, =
that=20
  the link is bad.&nbsp; Finally,&nbsp;MANETs are, by =
definition,&nbsp;mobile,=20
  so any data table you have now is likely to be in error in a few =
minutes or=20
  less.</FONT></SPAN></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><SPAN class=3D963062118-04052006><FONT face=3DArial =
color=3D#0000ff size=3D2>You=20
  are correct in that if we knew who our neighbors are, we could set up =
the=20
  network.&nbsp; The problem is that in practice, we know nothing and =
need to=20
  proceed on the basis of intelligent guesses.&nbsp; I think that a =
bigger=20
  problem is that so much work is done in MANET protocol design that =
completely=20
  ignores this problem.</FONT></SPAN></DIV>
  <DIV><SPAN class=3D963062118-04052006></SPAN>&nbsp;</DIV><!-- =
Converted from text/plain format -->
  <P><FONT size=3D2>John P. Mullen, Ph.D.<BR>(505) 646-2958<BR><A=20
  class=3Dmoz-txt-link-abbreviated=20
  =
href=3D"mailto:jomullen@nmsu.edu">jomullen@nmsu.edu</A><BR>&nbsp;</FONT> =
</P>
  <DIV>&nbsp;</DIV><BR>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Kenneth Brayer [<A=20
  class=3Dmoz-txt-link-freetext=20
  href=3D"mailto:kb@mitre.org">mailto:kb@mitre.org</A>] <BR><B>Sent:</B> =
Thursday,=20
  May 04, 2006 12:16 PM<BR><B>To:</B> <A =
class=3Dmoz-txt-link-abbreviated=20
  href=3D"mailto:manet@ietf.org">manet@ietf.org</A><BR><B>Subject:</B> =
Re: [manet]=20
  Re: MANET definition of a neighbor<BR></FONT><BR></DIV>It strikes me =
that a=20
  neighbor of Node A is any node that A can setup a link to, whether it =
be next=20
  door or 300 miles away. A node that the second node can setup a link =
to but=20
  that A cannot setup a link to is a neighbor once removed, etc. Once =
you know=20
  who the neighbors are you can build a network routing=20
  table.<BR><BR>See<BR><STRONG>Packet switching for mobile earth =
stations via=20
  low-orbit satellite network</STRONG><BR>Brayer, K.;<BR><A=20
  =
href=3D"http://ieeexplore.ieee.org/xpl/RecentIssue.jsp?punumber=3D5">Proc=
eedings=20
  of the IEEE</A><BR>Volume 72,&nbsp; Issue 11,&nbsp; Nov. 1984 =
Page(s):1627 -=20
  1636 <BR><BR>Available online in IEEE =
XPLORE<BR><BR>Ken<BR><BR><BR><PRE class=3Dmoz-signature cols=3D"72">--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:kb@mitre.org">kb@mitre.org</A>
tele: 781-271-5254
fax: 781-271-2841
  </PRE></BLOCKQUOTE><BR><PRE class=3Dmoz-signature cols=3D"72">--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:kb@mitre.org">kb@mitre.org</A>
tele: 781-271-5254
fax: 781-271-2841
</PRE></BODY></HTML>

------_=_NextPart_001_01C66FAD.FB42EB89--


--===============0619802368==
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

--===============0619802368==--




From manet-bounces@ietf.org Thu May 04 15:08:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbjBk-0006lS-AY; Thu, 04 May 2006 15:08:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbjBi-0006lK-9z
	for manet@ietf.org; Thu, 04 May 2006 15:08:34 -0400
Received: from smtpproxy2.mitre.org ([192.80.55.71] helo=smtp-mclean.mitre.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbjBh-0001MK-UI
	for manet@ietf.org; Thu, 04 May 2006 15:08:34 -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
	k44J8LXn028084 for <manet@ietf.org>; Thu, 4 May 2006 15:08:21 -0400
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-mclean.mitre.org (Postfix) with ESMTP id 78C901BD82
	for <manet@ietf.org>; Thu,  4 May 2006 15:08:21 -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
	k44J8BvU027935; Thu, 4 May 2006 15:08:11 -0400
Received: from [129.83.175.29] ([129.83.175.29]) by imcfe2.MITRE.ORG with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 4 May 2006 15:08:11 -0400
Message-ID: <445A51AA.8030209@mitre.org>
Date: Thu, 04 May 2006 15:10:34 -0400
From: Kenneth Brayer <kb@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: jasteven@rockwellcollins.com
Subject: Re: [manet] Re: Neighbors
References: <OF7BED0D40.CD503A84-ON86257164.0067B14D-86257164.00685D79@rockwellcollins.com>
In-Reply-To: <OF7BED0D40.CD503A84-ON86257164.0067B14D-86257164.00685D79@rockwellcollins.com>
X-OriginalArrivalTime: 04 May 2006 19:08:11.0094 (UTC)
	FILETIME=[16033760:01C66FAE]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0080718095=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.
--===============0080718095==
Content-Type: multipart/alternative;
	boundary="------------020003050704050107050508"

This is a multi-part message in MIME format.
--------------020003050704050107050508
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Jim
For all the reasons that John gave the network may not be stable. I 
think reliably knowing who your neighbors are is the same as tracking 
the network topology. I agree that MANET designers should seek to do this.
Ken

jasteven@rockwellcollins.com wrote:

>
> Ken, you said that
>
> >  So the real question is who are your neighbors
> >  as a function of time in a MANET. A MANET protocol
> >  should try to determine this so it can deliver
> >  messages when they are presented to the network.
> >
> >  My paper deals with point to point satellites,
> >  but you have the never ending list of protocols,
> >  DSR, ABR, ZRP, OLSR, etc. all of which try to deal
> >  with this problem, how to track topology changes."
>
> The difficult problem in MANETs is not tracking the network topology 
> per se (e.g. the never ending list of routing protocols), instead the 
> difficult problem in MANETs is reliably & stably knowing who your 
> neighbors are.
>
> So, I agree with John that
>
> >  ... if we knew who our neighbors are, we could set
> >  up the network.  The problem is that in practice,
> >  we know nothing and need to proceed on the basis
> >  of intelligent guesses.  I think that a bigger
> >  problem is that so much work is done in MANET
> >  protocol design that completely ignores this problem.
>
> Jim
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> James A. Stevens, PhD
> Chief Network Architect
> Rockwell Collins Government Systems
>
>------------------------------------------------------------------------
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet
>  
>

-- 
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841


--------------020003050704050107050508
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Jim<br>
For all the reasons that John gave the network may not be stable. I
think reliably knowing who your neighbors are is the same as tracking
the network topology. I agree that MANET designers should seek to do
this.<br>
Ken<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:jasteven@rockwellcollins.com">jasteven@rockwellcollins.com</a> wrote:<br>
<blockquote
 cite="midOF7BED0D40.CD503A84-ON86257164.0067B14D-86257164.00685D79@rockwellcollins.com"
 type="cite"><br>
  <font face="sans-serif" size="2">Ken, you said that</font>
  <br>
  <br>
  <font size="2"><tt>&gt; &nbsp;So the real question is who are your
neighbors</tt></font>
  <br>
  <font size="2"><tt>&gt; &nbsp;as a function of time in a MANET. A MANET
protocol</tt></font>
  <br>
  <font size="2"><tt>&gt; &nbsp;should try to determine this so it can
deliver </tt></font>
  <br>
  <font size="2"><tt>&gt; &nbsp;messages when they are presented to the
network.<br>
&gt;<br>
&gt; &nbsp;My paper deals with point to point satellites, </tt></font>
  <br>
  <font size="2"><tt>&gt; &nbsp;but you have the never ending list of
protocols,
  </tt></font><br>
  <font size="2"><tt>&gt; &nbsp;DSR, ABR, ZRP, OLSR, etc. all of which
try to deal </tt></font>
  <br>
  <font size="2"><tt>&gt; &nbsp;with this problem, how to track topology
changes."</tt></font>
  <br>
  <br>
  <font size="2"><tt>The difficult problem in MANETs is not tracking
the
network topology per se (e.g. the never ending list of routing
protocols),
instead the difficult problem in MANETs is reliably &amp; stably
knowing
who your neighbors are.</tt></font>
  <br>
  <br>
  <font size="2"><tt>So, I agree with John that</tt></font>
  <br>
  <br>
  <font size="2"><tt>&gt; &nbsp;... if we knew who our neighbors are, we
could set</tt></font>
  <br>
  <font size="2"><tt>&gt; &nbsp;up the network. &nbsp;The problem is that
in practice, </tt></font>
  <br>
  <font size="2"><tt>&gt; &nbsp;we know nothing and need to proceed on
the basis </tt></font>
  <br>
  <font size="2"><tt>&gt; &nbsp;of intelligent guesses. &nbsp;I think that
a bigger </tt></font>
  <br>
  <font size="2"><tt>&gt; &nbsp;problem is that so much work is done in
MANET </tt></font>
  <br>
  <font size="2"><tt>&gt; &nbsp;protocol design that completely ignores
this problem.</tt></font>
  <br>
  <br>
  <font size="2"><tt>Jim</tt></font>
  <br>
  <font size="2"><tt><br>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<br>
James A. Stevens, PhD<br>
Chief Network Architect<br>
Rockwell Collins Government Systems</tt></font>
  <br>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
manet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:manet@ietf.org">manet@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/manet">https://www1.ietf.org/mailman/listinfo/manet</a>
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: <a class="moz-txt-link-abbreviated" href="mailto:kb@mitre.org">kb@mitre.org</a>
tele: 781-271-5254
fax: 781-271-2841
</pre>
</body>
</html>

--------------020003050704050107050508--


--===============0080718095==
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

--===============0080718095==--




From manet-bounces@ietf.org Thu May 04 15:09:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbjCK-0007EB-8Q; Thu, 04 May 2006 15:09:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbjCI-0007DO-K1
	for manet@ietf.org; Thu, 04 May 2006 15:09:10 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbjCH-0001OK-AT
	for manet@ietf.org; Thu, 04 May 2006 15:09:10 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138])
	by sj-iport-5.cisco.com with ESMTP; 04 May 2006 12:09:09 -0700
X-IronPort-AV: i="4.05,89,1146466800"; 
	d="scan'208"; a="272787691:sNHT27577140"
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k44J98Yg010282;
	Thu, 4 May 2006 12:09:08 -0700 (PDT)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com
	[10.32.244.218])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k44J7QW5013741;
	Thu, 4 May 2006 12:07:26 -0700
In-Reply-To: <445A4C3A.2030203@mitre.org>
References: <8536FDFA3AD04A49A15804915996569106DEF02D@exchange1.ACN.ad.nmsu.edu>
	<445A4C3A.2030203@mitre.org>
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <08FF3949-AE6F-498C-A5AC-5C3B969B916D@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
Date: Thu, 4 May 2006 12:09:05 -0700
To: Kenneth Brayer <kb@mitre.org>
X-Mailer: Apple Mail (2.749.3)
DKIM-Signature: a=rsa-sha1; q=dns; l=2090; t=1146769647; x=1147633647;
	c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20<fred@cisco.com>
	|Subject:Re=3A=20[manet]=20Re=3A=20MANET=20definition=20of=20a=20neighbor
	|To:Kenneth=20Brayer=20<kb@mitre.org>;
	X=v=3Dcisco.com=3B=20h=3DHk1wepC3iEml5uWsgXGxy3raHJ0=3D;
	b=SLhxhvy0KYBosIidxSJGSa2ZMjBmd68ro345LqGImUMztO6iShi9sVC1H/gazpGOLeYOANMG
	OGgmI0B8Fp4Yy8VDNvdO4XF8s7jdolJYSm6NfJy6grOuZRJBkJAfvdOG;
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

On May 4, 2006, at 11:47 AM, Kenneth Brayer wrote:
> So the real question is who are your neighbors as a function of  
> time in a MANET. A MANET protocol should try to determine this so  
> it can deliver messages when they are presented to the network.

It is "at a point in time" even in a wired and highly reliable  
network. Things go bump in the night in the most stable networks.

I have argued along the lines, though, that the most important metric  
for a path in a manet network is not its speed or degree of  
congestion (although those are very interesting second-order  
metrics), but the probability that it will be useful at the time I  
want to use it.

In many scenarios, mobility is well described as "brownian motion",  
in which things moving approximately together but bump in and out of  
sight of each other, or using the word "zoom". If one thinks, for  
example, of cars on a highway, I might try to use cars traveling in  
the opposite direction as links ("zoom"), cars on orthogonal roads  
("zoom" to the point of "blip" in many cases), routers on light poles  
("zoom" at half the speed), routers in other cars I happen to be  
traveling with for a few exits (relatively stable during the  
interval, but blipping in and out around corners/tunnels/etc), and  
the occasional router on a hill (which it will be able to see for a  
long time as it passes the hill). Which is the tres cool route? The  
one that has the highest probability of working when the route is  
needed...

So for example if one has a pair of UAVs in orbit over a domain, one  
should be able to watch the characteristics of the radio signal and  
see that one's signal is slowly degrading while the other's is slowly  
improving. At some point, one wants to bring up the approaching UAV,  
shift routes to it, and then shut down the now-unused departing UAV  
for a smooth switchover, rather than saying "ohmygoshwhatdoidonow"  
when the UAV one is using suddenly goes out of sight. The sudden mass  
change model is a leftover from wired concepts...

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



From manet-bounces@ietf.org Thu May 04 15:22:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbjPQ-0001fu-6b; Thu, 04 May 2006 15:22:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbjPP-0001fp-1X
	for manet@ietf.org; Thu, 04 May 2006 15:22:43 -0400
Received: from ext-nj2ut-11.online-age.net ([64.14.54.241])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbjPN-0001n2-NW
	for manet@ietf.org; Thu, 04 May 2006 15:22:43 -0400
Received: from int-nj2ut-1.online-age.net (int-nj2ut-1.online-age.net
	[3.159.237.70])
	by ext-nj2ut-11.online-age.net (8.13.6/8.13.6/20051114-SVVS-TLS-DNSBL)
	with ESMTP id k44JMa8m015421
	for <manet@ietf.org>; Thu, 4 May 2006 15:22:36 -0400
Received: from cinmlef08.e2k.ad.ge.com (localhost.localdomain [127.0.0.1])
	by int-nj2ut-1.online-age.net (8.11.6/8.11.6/20050510-SVVS) with ESMTP
	id k44JMWh31485 for <manet@ietf.org>; Thu, 4 May 2006 15:22:36 -0400
Received: from SCHMLVEM01.e2k.ad.ge.com ([3.159.168.31]) by
	cinmlef08.e2k.ad.ge.com with Microsoft SMTPSVC(6.0.3790.2499); 
	Thu, 4 May 2006 15:22:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Thu, 4 May 2006 15:22:30 -0400
Message-ID: <FA26BEF1EA775E4584FB34B91E14A1C407E94337@SCHMLVEM01.e2k.ad.ge.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvrk5UvSbKquwBTK2bFuZ5wpXhOQAAXGsQ
From: "Bush, Stephen F \(GE, Research\)" <bushsf@research.ge.com>
To: "Fred Baker" <fred@cisco.com>, "Kenneth Brayer" <kb@mitre.org>
X-OriginalArrivalTime: 04 May 2006 19:22:31.0370 (UTC)
	FILETIME=[16C6EAA0:01C66FB0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


Perhaps MANET could benefit from some of the DTN concepts
and flash routes =
(http://www.research.ge.com/~bushsf/pdfpapers/bush_worldacademy.pdf).

Steve

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:09 PM
To: Kenneth Brayer
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 11:47 AM, Kenneth Brayer wrote:
> So the real question is who are your neighbors as a function of =20
> time in a MANET. A MANET protocol should try to determine this so =20
> it can deliver messages when they are presented to the network.

It is "at a point in time" even in a wired and highly reliable =20
network. Things go bump in the night in the most stable networks.

I have argued along the lines, though, that the most important metric =20
for a path in a manet network is not its speed or degree of =20
congestion (although those are very interesting second-order =20
metrics), but the probability that it will be useful at the time I =20
want to use it.

In many scenarios, mobility is well described as "brownian motion", =20
in which things moving approximately together but bump in and out of =20
sight of each other, or using the word "zoom". If one thinks, for =20
example, of cars on a highway, I might try to use cars traveling in =20
the opposite direction as links ("zoom"), cars on orthogonal roads =20
("zoom" to the point of "blip" in many cases), routers on light poles =20
("zoom" at half the speed), routers in other cars I happen to be =20
traveling with for a few exits (relatively stable during the =20
interval, but blipping in and out around corners/tunnels/etc), and =20
the occasional router on a hill (which it will be able to see for a =20
long time as it passes the hill). Which is the tres cool route? The =20
one that has the highest probability of working when the route is =20
needed...

So for example if one has a pair of UAVs in orbit over a domain, one =20
should be able to watch the characteristics of the radio signal and =20
see that one's signal is slowly degrading while the other's is slowly =20
improving. At some point, one wants to bring up the approaching UAV, =20
shift routes to it, and then shut down the now-unused departing UAV =20
for a smooth switchover, rather than saying "ohmygoshwhatdoidonow" =20
when the UAV one is using suddenly goes out of sight. The sudden mass =20
change model is a leftover from wired concepts...

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

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



From manet-bounces@ietf.org Thu May 04 15:28:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbjV7-0007QW-7v; Thu, 04 May 2006 15:28:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbjV5-0007QJ-T8
	for manet@ietf.org; Thu, 04 May 2006 15:28:35 -0400
Received: from smtpproxy1.mitre.org ([192.160.51.76]
	helo=smtp-bedford.mitre.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbjV3-000259-J3
	for manet@ietf.org; Thu, 04 May 2006 15:28:35 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-bedford.mitre.org (8.12.11.20060308/8.11.6) with SMTP id
	k44JSX6i000446 for <manet@ietf.org>; Thu, 4 May 2006 15:28:33 -0400
Received: from smtp-bedford.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-bedford.mitre.org (Postfix) with ESMTP id 34A54BF00
	for <manet@ietf.org>; Thu,  4 May 2006 15:28:33 -0400 (EDT)
Received: from IMCFE1.MITRE.ORG (imcfe1.mitre.org [129.83.29.3])
	by smtp-bedford.mitre.org (8.12.11.20060308/8.12.11) with ESMTP id
	k44JSWEP000427; Thu, 4 May 2006 15:28:32 -0400
Received: from [129.83.175.29] ([129.83.175.29]) by IMCFE1.MITRE.ORG with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 4 May 2006 15:28:32 -0400
Message-ID: <445A566F.9030506@mitre.org>
Date: Thu, 04 May 2006 15:30:55 -0400
From: Kenneth Brayer <kb@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
References: <8536FDFA3AD04A49A15804915996569106DEF02D@exchange1.ACN.ad.nmsu.edu>
	<445A4C3A.2030203@mitre.org>
	<08FF3949-AE6F-498C-A5AC-5C3B969B916D@cisco.com>
In-Reply-To: <08FF3949-AE6F-498C-A5AC-5C3B969B916D@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 May 2006 19:28:32.0476 (UTC)
	FILETIME=[EE0351C0:01C66FB0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Fred
I agree with the following:
"I have argued along the lines, though, that the most important metric  
for a path in a manet network is not its speed or degree of  congestion 
(although those are very interesting second-order  metrics), but the 
probability that it will be useful at the time I  want to use it."

When you get a message to deliver you need to know what to do. I am 
interested in delivering messages rapidly.

as far as
"So for example if one has a pair of UAVs in orbit over a domain, one  
should be able to watch the characteristics of the radio signal and  see 
that one's signal is slowly degrading while the other's is slowly  
improving. At some point, one wants to bring up the approaching UAV,  
shift routes to it, and then shut down the now-unused departing UAV  for 
a smooth switchover, rather than saying "ohmygoshwhatdoidonow"  when the 
UAV one is using suddenly goes out of sight."

For all of the reasons that John stated this is very hard. Just because 
the signal is degrading doesn't mean it will continue to degrade. It is 
even harder to determine when a signal will improve. I made Fellow of 
the IEEE in Fading Channels, like HF Radio, and signal quality 
prediction and its direction is very difficult. Some real world MANETS 
deal with this by trying to eliminate the problem through coding. THey 
give up usable channel capacity to reduce the error rate and increase 
channel reliability.

Ken

Fred Baker wrote:

> On May 4, 2006, at 11:47 AM, Kenneth Brayer wrote:
>
>> So the real question is who are your neighbors as a function of  time 
>> in a MANET. A MANET protocol should try to determine this so  it can 
>> deliver messages when they are presented to the network.
>
>
> It is "at a point in time" even in a wired and highly reliable  
> network. Things go bump in the night in the most stable networks.
>
> I have argued along the lines, though, that the most important metric  
> for a path in a manet network is not its speed or degree of  
> congestion (although those are very interesting second-order  
> metrics), but the probability that it will be useful at the time I  
> want to use it.
>
> In many scenarios, mobility is well described as "brownian motion",  
> in which things moving approximately together but bump in and out of  
> sight of each other, or using the word "zoom". If one thinks, for  
> example, of cars on a highway, I might try to use cars traveling in  
> the opposite direction as links ("zoom"), cars on orthogonal roads  
> ("zoom" to the point of "blip" in many cases), routers on light poles  
> ("zoom" at half the speed), routers in other cars I happen to be  
> traveling with for a few exits (relatively stable during the  
> interval, but blipping in and out around corners/tunnels/etc), and  
> the occasional router on a hill (which it will be able to see for a  
> long time as it passes the hill). Which is the tres cool route? The  
> one that has the highest probability of working when the route is  
> needed...
>
> So for example if one has a pair of UAVs in orbit over a domain, one  
> should be able to watch the characteristics of the radio signal and  
> see that one's signal is slowly degrading while the other's is slowly  
> improving. At some point, one wants to bring up the approaching UAV,  
> shift routes to it, and then shut down the now-unused departing UAV  
> for a smooth switchover, rather than saying "ohmygoshwhatdoidonow"  
> when the UAV one is using suddenly goes out of sight. The sudden mass  
> change model is a leftover from wired concepts...


-- 
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841


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



From manet-bounces@ietf.org Thu May 04 15:41:11 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbjh6-0004q3-Ev; Thu, 04 May 2006 15:41:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbjh4-0004py-86
	for manet@ietf.org; Thu, 04 May 2006 15:40:58 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbjh3-0002eY-0b
	for manet@ietf.org; Thu, 04 May 2006 15:40:58 -0400
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
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Thu, 4 May 2006 13:40:55 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF077@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvrjvU0hY8z8vsTPmlEpuKwYzDqAAAr/JA
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "Fred Baker" <fred@cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Fred,

You said:

So for example if one has a pair of UAVs in orbit over a domain, one
should be able to watch the characteristics of the radio signal and see
that one's signal is slowly degrading while the other's is slowly
improving. At some point, one wants to bring up the approaching UAV,
shift routes to it, and then shut down the now-unused departing UAV for
a smooth switchover, rather than saying "ohmygoshwhatdoidonow" =20
when the UAV one is using suddenly goes out of sight. The sudden mass
change model is a leftover from wired concepts...

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

The problem is that this does not happen.  Instead, received signal
strength fluctualtes wildly and there is a very large interval over
which either UAV might be equally good or bad.  Some sort of integration
and filtering is needed.  The trick is to come up with a scheme that
will reliably switch to the new UAV when it should without unnecessarily
switching between the two.=20

John Mullen

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



From manet-bounces@ietf.org Thu May 04 15:42:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbjiN-0005k6-HO; Thu, 04 May 2006 15:42:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbjiL-0005jG-Lq
	for manet@ietf.org; Thu, 04 May 2006 15:42:17 -0400
Received: from p02m143.mxlogic.net ([66.179.26.143])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbjiK-0002gg-VS
	for manet@ietf.org; Thu, 04 May 2006 15:42:17 -0400
Received: from unknown [208.251.151.99] (EHLO EXV1.corp.adtran.com)
	by p02m143.mxlogic.net (mxl_mta-2.14.0-12)
	with ESMTP id 8195a544.290843568.11270.p02m143.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Thu, 04 May 2006 13:42:16 -0600 (MDT)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 4 May 2006 14:42:15 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F0B@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: MANET definition of a neighbor
Thread-Index: AcZvsPpib5g9q4SFTrGsmaKb1xrXGQAAODtw
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: <manet@ietf.org>
X-Spam: [F=0.0100000000; S=0.010(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.251.151.99]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Subject: [manet] Re: MANET definition of a neighbor
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Just rebuild the routing tables every 3 seconds or so.  This eliminates
guessing, measuring signal strength, watching traffic etc.  You could
even make invalidating the tables user configurable.  If the user knows
he will be relatively stationary, ie. in Barnes and Noble, they could
set the protocol to the stationary model.  If the user is travelling
down the highway at 80 MPH or on a subway, then choose the roaming model
which invalidates and updates the routes at a faster pace.

-----Original Message-----
From: Kenneth Brayer [mailto:kb@mitre.org]=20
Sent: Thursday, May 04, 2006 2:31 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor

Fred
I agree with the following:
"I have argued along the lines, though, that the most important metric
for a path in a manet network is not its speed or degree of  congestion
(although those are very interesting second-order  metrics), but the
probability that it will be useful at the time I  want to use it."

When you get a message to deliver you need to know what to do. I am
interested in delivering messages rapidly.

as far as
"So for example if one has a pair of UAVs in orbit over a domain, one
should be able to watch the characteristics of the radio signal and  see
that one's signal is slowly degrading while the other's is slowly
improving. At some point, one wants to bring up the approaching UAV,
shift routes to it, and then shut down the now-unused departing UAV  for
a smooth switchover, rather than saying "ohmygoshwhatdoidonow"  when the
UAV one is using suddenly goes out of sight."

For all of the reasons that John stated this is very hard. Just because
the signal is degrading doesn't mean it will continue to degrade. It is
even harder to determine when a signal will improve. I made Fellow of
the IEEE in Fading Channels, like HF Radio, and signal quality
prediction and its direction is very difficult. Some real world MANETS
deal with this by trying to eliminate the problem through coding. THey
give up usable channel capacity to reduce the error rate and increase
channel reliability.

Ken

Fred Baker wrote:

> On May 4, 2006, at 11:47 AM, Kenneth Brayer wrote:
>
>> So the real question is who are your neighbors as a function of  time

>> in a MANET. A MANET protocol should try to determine this so  it can=20
>> deliver messages when they are presented to the network.
>
>
> It is "at a point in time" even in a wired and highly reliable=20
> network. Things go bump in the night in the most stable networks.
>
> I have argued along the lines, though, that the most important metric=20
> for a path in a manet network is not its speed or degree of congestion

> (although those are very interesting second-order metrics), but the=20
> probability that it will be useful at the time I want to use it.
>
> In many scenarios, mobility is well described as "brownian motion", in

> which things moving approximately together but bump in and out of=20
> sight of each other, or using the word "zoom". If one thinks, for=20
> example, of cars on a highway, I might try to use cars traveling in=20
> the opposite direction as links ("zoom"), cars on orthogonal roads=20
> ("zoom" to the point of "blip" in many cases), routers on light poles=20
> ("zoom" at half the speed), routers in other cars I happen to be=20
> traveling with for a few exits (relatively stable during the interval,

> but blipping in and out around corners/tunnels/etc), and the=20
> occasional router on a hill (which it will be able to see for a long=20
> time as it passes the hill). Which is the tres cool route? The one=20
> that has the highest probability of working when the route is=20
> needed...
>
> So for example if one has a pair of UAVs in orbit over a domain, one=20
> should be able to watch the characteristics of the radio signal and=20
> see that one's signal is slowly degrading while the other's is slowly=20
> improving. At some point, one wants to bring up the approaching UAV,=20
> shift routes to it, and then shut down the now-unused departing UAV=20
> for a smooth switchover, rather than saying "ohmygoshwhatdoidonow"
> when the UAV one is using suddenly goes out of sight. The sudden mass=20
> change model is a leftover from wired concepts...


--
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841


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

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



From manet-bounces@ietf.org Thu May 04 15:52:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbjsG-00081r-50; Thu, 04 May 2006 15:52:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbjsE-00081l-Kj
	for manet@ietf.org; Thu, 04 May 2006 15:52:30 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbjsE-0003H0-60
	for manet@ietf.org; Thu, 04 May 2006 15:52:30 -0400
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
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Thu, 4 May 2006 13:52:28 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF086@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvsPpib5g9q4SFTrGsmaKb1xrXGQAAODtwAABT5mA=
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>,
	<manet@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Dan,

Easier said than done.

The problem is that the information available to the node does not
indicate clearly who are and who are not neighbors.  Gratutiously
rebuilding tables is as likely to make things worse than better.
Understand, too, that the degree to which a MANET is dynamic depends on
factors other than node mobility.  For example, if the local in-band and
near-band traffic level increases, so will interference, which could
render an otherwise useful link useless due to an unacceptably high
SNIR.  Also, even in B&N, people could be turning on or off their
computers, so the network topology could change drastically in a short
period of time even if none of the nodes move.

In other words, there is no way to eliminate guessing as long as the
MANET uses wireless links.

John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Thursday, May 04, 2006 1:42 PM
To: manet@ietf.org
Subject: [manet] Re: MANET definition of a neighbor

Just rebuild the routing tables every 3 seconds or so.  This eliminates
guessing, measuring signal strength, watching traffic etc.  You could
even make invalidating the tables user configurable.  If the user knows
he will be relatively stationary, ie. in Barnes and Noble, they could
set the protocol to the stationary model.  If the user is travelling
down the highway at 80 MPH or on a subway, then choose the roaming model
which invalidates and updates the routes at a faster pace.

-----Original Message-----
From: Kenneth Brayer [mailto:kb@mitre.org]
Sent: Thursday, May 04, 2006 2:31 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor

Fred
I agree with the following:
"I have argued along the lines, though, that the most important metric
for a path in a manet network is not its speed or degree of  congestion
(although those are very interesting second-order  metrics), but the
probability that it will be useful at the time I  want to use it."

When you get a message to deliver you need to know what to do. I am
interested in delivering messages rapidly.

as far as
"So for example if one has a pair of UAVs in orbit over a domain, one
should be able to watch the characteristics of the radio signal and  see
that one's signal is slowly degrading while the other's is slowly
improving. At some point, one wants to bring up the approaching UAV,
shift routes to it, and then shut down the now-unused departing UAV  for
a smooth switchover, rather than saying "ohmygoshwhatdoidonow"  when the
UAV one is using suddenly goes out of sight."

For all of the reasons that John stated this is very hard. Just because
the signal is degrading doesn't mean it will continue to degrade. It is
even harder to determine when a signal will improve. I made Fellow of
the IEEE in Fading Channels, like HF Radio, and signal quality
prediction and its direction is very difficult. Some real world MANETS
deal with this by trying to eliminate the problem through coding. THey
give up usable channel capacity to reduce the error rate and increase
channel reliability.

Ken

Fred Baker wrote:

> On May 4, 2006, at 11:47 AM, Kenneth Brayer wrote:
>
>> So the real question is who are your neighbors as a function of  time

>> in a MANET. A MANET protocol should try to determine this so  it can=20
>> deliver messages when they are presented to the network.
>
>
> It is "at a point in time" even in a wired and highly reliable=20
> network. Things go bump in the night in the most stable networks.
>
> I have argued along the lines, though, that the most important metric=20
> for a path in a manet network is not its speed or degree of congestion

> (although those are very interesting second-order metrics), but the=20
> probability that it will be useful at the time I want to use it.
>
> In many scenarios, mobility is well described as "brownian motion", in

> which things moving approximately together but bump in and out of=20
> sight of each other, or using the word "zoom". If one thinks, for=20
> example, of cars on a highway, I might try to use cars traveling in=20
> the opposite direction as links ("zoom"), cars on orthogonal roads=20
> ("zoom" to the point of "blip" in many cases), routers on light poles=20
> ("zoom" at half the speed), routers in other cars I happen to be=20
> traveling with for a few exits (relatively stable during the interval,

> but blipping in and out around corners/tunnels/etc), and the=20
> occasional router on a hill (which it will be able to see for a long=20
> time as it passes the hill). Which is the tres cool route? The one=20
> that has the highest probability of working when the route is=20
> needed...
>
> So for example if one has a pair of UAVs in orbit over a domain, one=20
> should be able to watch the characteristics of the radio signal and=20
> see that one's signal is slowly degrading while the other's is slowly=20
> improving. At some point, one wants to bring up the approaching UAV,=20
> shift routes to it, and then shut down the now-unused departing UAV=20
> for a smooth switchover, rather than saying "ohmygoshwhatdoidonow"
> when the UAV one is using suddenly goes out of sight. The sudden mass=20
> change model is a leftover from wired concepts...


--
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841


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

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

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



From manet-bounces@ietf.org Thu May 04 16:11:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbkAP-0007hy-Jx; Thu, 04 May 2006 16:11:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbkAO-0007ht-LC
	for manet@ietf.org; Thu, 04 May 2006 16:11:16 -0400
Received: from p02m141.mxlogic.net ([66.179.26.141])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbkAM-0004aA-Pn
	for manet@ietf.org; Thu, 04 May 2006 16:11:16 -0400
Received: from unknown [208.61.208.100]
	by p02m141.mxlogic.net (mxl_mta-2.14.0-12)
	with SMTP id 2ef5a544.1793403824.69286.p02m141.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Thu, 04 May 2006 14:11:14 -0600 (MDT)
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] Re: MANET definition of a neighbor
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 4 May 2006 15:10:49 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F0C@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvsPpib5g9q4SFTrGsmaKb1xrXGQAAODtwAABT5mAAAG60EA==
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: <manet@ietf.org>
X-Spam: [F=0.0100000000; S=0.010(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.61.208.100]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

John,
How would gratuitously rebuilding tables make things worse?  If as you
say the local in-band and near-band traffic level increases rendering an
otherwise useful link useless due to an unacceptably high SNIR, wouldn't
rebuilding the links make it better? =20

Obviously the links would be rebuilt within a best available case
scenario.  I.e.. Pick the best link every time you rebuild.

Yes guessing is not eliminated, but extra processing overhead which may
or may not amount to anything is.

I guess what I'm afraid of is unnecessarily complicating algorithms by
trying to solve every conceivable problem with 100% accuracy.  Just make
everything best effort!  Correlating to the wired world -- it works for
Ethernet and complexity is killing ATM.  It'll make the hardware
cheaper, faster and more broadly accepted, and "most of the time" it'll
be more than adequate. =20

I guess I'm thinking more like and engineer and less like a researcher.
Blame it on my job description. ;-)


-----Original Message-----
From: Mullen, John [mailto:jomullen@ad.nmsu.edu]=20
Sent: Thursday, May 04, 2006 2:52 PM
To: DANIEL BYRNE; manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Hi Dan,

Easier said than done.

The problem is that the information available to the node does not
indicate clearly who are and who are not neighbors.  Gratutiously
rebuilding tables is as likely to make things worse than better.
Understand, too, that the degree to which a MANET is dynamic depends on
factors other than node mobility.  For example, if the local in-band and
near-band traffic level increases, so will interference, which could
render an otherwise useful link useless due to an unacceptably high
SNIR.  Also, even in B&N, people could be turning on or off their
computers, so the network topology could change drastically in a short
period of time even if none of the nodes move.

In other words, there is no way to eliminate guessing as long as the
MANET uses wireless links.

John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]
Sent: Thursday, May 04, 2006 1:42 PM
To: manet@ietf.org
Subject: [manet] Re: MANET definition of a neighbor

Just rebuild the routing tables every 3 seconds or so.  This eliminates
guessing, measuring signal strength, watching traffic etc.  You could
even make invalidating the tables user configurable.  If the user knows
he will be relatively stationary, ie. in Barnes and Noble, they could
set the protocol to the stationary model.  If the user is travelling
down the highway at 80 MPH or on a subway, then choose the roaming model
which invalidates and updates the routes at a faster pace.

-----Original Message-----
From: Kenneth Brayer [mailto:kb@mitre.org]
Sent: Thursday, May 04, 2006 2:31 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor

Fred
I agree with the following:
"I have argued along the lines, though, that the most important metric
for a path in a manet network is not its speed or degree of  congestion
(although those are very interesting second-order  metrics), but the
probability that it will be useful at the time I  want to use it."

When you get a message to deliver you need to know what to do. I am
interested in delivering messages rapidly.

as far as
"So for example if one has a pair of UAVs in orbit over a domain, one
should be able to watch the characteristics of the radio signal and  see
that one's signal is slowly degrading while the other's is slowly
improving. At some point, one wants to bring up the approaching UAV,
shift routes to it, and then shut down the now-unused departing UAV  for
a smooth switchover, rather than saying "ohmygoshwhatdoidonow"  when the
UAV one is using suddenly goes out of sight."

For all of the reasons that John stated this is very hard. Just because
the signal is degrading doesn't mean it will continue to degrade. It is
even harder to determine when a signal will improve. I made Fellow of
the IEEE in Fading Channels, like HF Radio, and signal quality
prediction and its direction is very difficult. Some real world MANETS
deal with this by trying to eliminate the problem through coding. THey
give up usable channel capacity to reduce the error rate and increase
channel reliability.

Ken

Fred Baker wrote:

> On May 4, 2006, at 11:47 AM, Kenneth Brayer wrote:
>
>> So the real question is who are your neighbors as a function of  time

>> in a MANET. A MANET protocol should try to determine this so  it can=20
>> deliver messages when they are presented to the network.
>
>
> It is "at a point in time" even in a wired and highly reliable=20
> network. Things go bump in the night in the most stable networks.
>
> I have argued along the lines, though, that the most important metric=20
> for a path in a manet network is not its speed or degree of congestion

> (although those are very interesting second-order metrics), but the=20
> probability that it will be useful at the time I want to use it.
>
> In many scenarios, mobility is well described as "brownian motion", in

> which things moving approximately together but bump in and out of=20
> sight of each other, or using the word "zoom". If one thinks, for=20
> example, of cars on a highway, I might try to use cars traveling in=20
> the opposite direction as links ("zoom"), cars on orthogonal roads=20
> ("zoom" to the point of "blip" in many cases), routers on light poles=20
> ("zoom" at half the speed), routers in other cars I happen to be=20
> traveling with for a few exits (relatively stable during the interval,

> but blipping in and out around corners/tunnels/etc), and the=20
> occasional router on a hill (which it will be able to see for a long=20
> time as it passes the hill). Which is the tres cool route? The one=20
> that has the highest probability of working when the route is=20
> needed...
>
> So for example if one has a pair of UAVs in orbit over a domain, one=20
> should be able to watch the characteristics of the radio signal and=20
> see that one's signal is slowly degrading while the other's is slowly=20
> improving. At some point, one wants to bring up the approaching UAV,=20
> shift routes to it, and then shut down the now-unused departing UAV=20
> for a smooth switchover, rather than saying "ohmygoshwhatdoidonow"
> when the UAV one is using suddenly goes out of sight. The sudden mass=20
> change model is a leftover from wired concepts...


--
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841


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

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

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



From manet-bounces@ietf.org Thu May 04 16:27:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbkPb-0004vM-Lv; Thu, 04 May 2006 16:26:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbkPZ-0004vH-F5
	for manet@ietf.org; Thu, 04 May 2006 16:26:57 -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 1FbkPY-0005MM-7R
	for manet@ietf.org; Thu, 04 May 2006 16:26:57 -0400
Received: from saffron.ece.neu.edu (saffron.ece.neu.edu [129.10.60.111])
	by SMTP1.ECE.NEU.EDU (8.12.5/8.12.5) with SMTP id k44KQrvD026103
	for <manet@ietf.org>; Thu, 4 May 2006 16:26:53 -0400 (EDT)
Received: (from gateway [129.10.60.71])
	by saffron.ece.neu.edu (SMSSMTP 4.1.5.31) with SMTP id
	M2006050416265322027
	for <manet@ietf.org>; Thu, 04 May 2006 16:26:53 -0400
Date: Thu, 4 May 2006 16:26:53 -0400 (EDT)
From: ACM MobiHoc 2006 <mobihoc@ECE.NEU.EDU>
To: manet@ietf.org
Message-ID: <Pine.GSO.4.58.0605041626180.29292@gateway.ece.neu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Subject: [manet] ACM/SIGMOBILE MobiHoc 2006, Early Registration
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

(Sorry for multiple reception of this announcement)

The  ACM   MobiHoc  2005  early   registration  deadline  is
approaching!

                    *** May 5 2006 ***
------------------------------------------------------------

           CALL FOR PARTICIPATION IN MOBIHOC 2006
                 EARLY REGISTRATION DEADLINE
                    and ADVANCE PROGRAM


                ACM/SIGMOBILE MobiHoc 2006
            7th ACM International Symposium on
          Mobile Ad Hoc Networking and Computing

             May 22-25, 2006, Florence, ITALY

          http://www.sigmobile.org/mobihoc/2006/

               Sponsored by ACM SIGMOBILE


ACM MobiHoc  is the premier  international meeting dedicated
to  addressing  challenges  emerging  from wireless  ad  hoc
networking and  computing. This year program  will include a
highly selective, single-track technical program, as well as
hands-on   research  demonstrations,  keynote,   panel,  and
tutorials.


ADVANCE REGISTRATION DEADLINE (special discounted rates:

                  **** MAY 5  2006 ****

For further information see:
http://www.sigmobile.org/mobihoc/2006/Registration.html

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



From manet-bounces@ietf.org Thu May 04 16:28:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbkR2-0005Wd-Th; Thu, 04 May 2006 16:28:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbkR2-0005WY-72
	for manet@ietf.org; Thu, 04 May 2006 16:28:28 -0400
Received: from p02m141.mxlogic.net ([66.179.26.141])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbkR1-0005c0-UM
	for manet@ietf.org; Thu, 04 May 2006 16:28:28 -0400
Received: from unknown [208.61.208.100] (EHLO EXV1.corp.adtran.com)
	by p02m141.mxlogic.net (mxl_mta-2.14.0-12)
	with ESMTP id be36a544.2236611504.15856.p02m141.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Thu, 04 May 2006 14:28:27 -0600 (MDT)
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] Re: MANET definition of a neighbor
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 4 May 2006 15:28:26 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F0E@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvsPpib5g9q4SFTrGsmaKb1xrXGQAAODtwAABT5mAAAG60EAAAzbFw
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: <manet@ietf.org>
X-Spam: [F=0.1593537643; S=0.159(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.61.208.100]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

"I have argued along the lines, though, that the most important metric
for a path in a manet network is not its speed or degree of  congestion
(although those are very interesting second-order  metrics), but the
probability that it will be useful at the time I  want to use it."=20

-Agreed. Speed and degree of congestion are second to reliability.
Rebuilding lists of reliable neighbor nodes every 3 seconds or so will
increase the probability that the links in the list will be useful.

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



From manet-bounces@ietf.org Thu May 04 16:35:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbkXb-0004BH-IQ; Thu, 04 May 2006 16:35:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbkXZ-0004AE-Vd
	for manet@ietf.org; Thu, 04 May 2006 16:35:13 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbkXY-00063W-Ef
	for manet@ietf.org; Thu, 04 May 2006 16:35:13 -0400
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
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Thu, 4 May 2006 14:35:12 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF0D2@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvsPpib5g9q4SFTrGsmaKb1xrXGQAAODtwAABT5mAAAG60EAAAkh/g
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>,
	<manet@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Dan,

The problem is that the node doesn't know which links are good and must
make intelligent guesses.  If you rebuild your table without reason to
suspect a route is bad, you will increase the risk of excluding a good
route or including a bad one.

As a related example, in statistical quality control, one frequently
asks "has the situation changed?" When doing so, the null hypothesis is
that nothing has changed and one does not conclude there has been a
change without definite evidence.  In essence, the node's neighbor
problem is similar, except that in SQC, one may ask the question twice
an hour, but in a MANET, the node may ask it twice a minute.  Thus, the
risk of a Type I error is very high. =20

If the interference level increases, one should reassess the links which
have marginal SNIRs, but there may be no need to reassess those with
high initial SNIRs, if the increase in interference doesn't lead to a
marginal SNIR.  It's like rocks in the bay.  They are more of a problem
at low tide than high tide, but if you are in a deep channel, the change
in tide levels doesn't matter that much.

You cannot be sure of picking the best links.  You can only pick the
links that appear best.  More than that, it is not at all clear what
"best" is.  A marginal link might be the best if the alternative is
network partition, but you won't know that without comparing notes with
other nodes.  You are not picking among alternate links to your
neighbors, but picking your neighbors.  Which links are chosen is the
result of a local decision, but has global consequences.

Failing to consider these problems can reduce your throughput by 80 or
90%.  This is not a second-order problem, but a central problem that
must be managed to have an acceptable MANET.

John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Thursday, May 04, 2006 2:11 PM
To: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

John,
How would gratuitously rebuilding tables make things worse?  If as you
say the local in-band and near-band traffic level increases rendering an
otherwise useful link useless due to an unacceptably high SNIR, wouldn't
rebuilding the links make it better? =20

Obviously the links would be rebuilt within a best available case
scenario.  I.e.. Pick the best link every time you rebuild.

Yes guessing is not eliminated, but extra processing overhead which may
or may not amount to anything is.

I guess what I'm afraid of is unnecessarily complicating algorithms by
trying to solve every conceivable problem with 100% accuracy.  Just make
everything best effort!  Correlating to the wired world -- it works for
Ethernet and complexity is killing ATM.  It'll make the hardware
cheaper, faster and more broadly accepted, and "most of the time" it'll
be more than adequate. =20

I guess I'm thinking more like and engineer and less like a researcher.
Blame it on my job description. ;-)


-----Original Message-----
From: Mullen, John [mailto:jomullen@ad.nmsu.edu]
Sent: Thursday, May 04, 2006 2:52 PM
To: DANIEL BYRNE; manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Hi Dan,

Easier said than done.

The problem is that the information available to the node does not
indicate clearly who are and who are not neighbors.  Gratutiously
rebuilding tables is as likely to make things worse than better.
Understand, too, that the degree to which a MANET is dynamic depends on
factors other than node mobility.  For example, if the local in-band and
near-band traffic level increases, so will interference, which could
render an otherwise useful link useless due to an unacceptably high
SNIR.  Also, even in B&N, people could be turning on or off their
computers, so the network topology could change drastically in a short
period of time even if none of the nodes move.

In other words, there is no way to eliminate guessing as long as the
MANET uses wireless links.

John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]
Sent: Thursday, May 04, 2006 1:42 PM
To: manet@ietf.org
Subject: [manet] Re: MANET definition of a neighbor

Just rebuild the routing tables every 3 seconds or so.  This eliminates
guessing, measuring signal strength, watching traffic etc.  You could
even make invalidating the tables user configurable.  If the user knows
he will be relatively stationary, ie. in Barnes and Noble, they could
set the protocol to the stationary model.  If the user is travelling
down the highway at 80 MPH or on a subway, then choose the roaming model
which invalidates and updates the routes at a faster pace.

-----Original Message-----
From: Kenneth Brayer [mailto:kb@mitre.org]
Sent: Thursday, May 04, 2006 2:31 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor

Fred
I agree with the following:
"I have argued along the lines, though, that the most important metric
for a path in a manet network is not its speed or degree of  congestion
(although those are very interesting second-order  metrics), but the
probability that it will be useful at the time I  want to use it."

When you get a message to deliver you need to know what to do. I am
interested in delivering messages rapidly.

as far as
"So for example if one has a pair of UAVs in orbit over a domain, one
should be able to watch the characteristics of the radio signal and  see
that one's signal is slowly degrading while the other's is slowly
improving. At some point, one wants to bring up the approaching UAV,
shift routes to it, and then shut down the now-unused departing UAV  for
a smooth switchover, rather than saying "ohmygoshwhatdoidonow"  when the
UAV one is using suddenly goes out of sight."

For all of the reasons that John stated this is very hard. Just because
the signal is degrading doesn't mean it will continue to degrade. It is
even harder to determine when a signal will improve. I made Fellow of
the IEEE in Fading Channels, like HF Radio, and signal quality
prediction and its direction is very difficult. Some real world MANETS
deal with this by trying to eliminate the problem through coding. THey
give up usable channel capacity to reduce the error rate and increase
channel reliability.

Ken

Fred Baker wrote:

> On May 4, 2006, at 11:47 AM, Kenneth Brayer wrote:
>
>> So the real question is who are your neighbors as a function of  time

>> in a MANET. A MANET protocol should try to determine this so  it can=20
>> deliver messages when they are presented to the network.
>
>
> It is "at a point in time" even in a wired and highly reliable=20
> network. Things go bump in the night in the most stable networks.
>
> I have argued along the lines, though, that the most important metric=20
> for a path in a manet network is not its speed or degree of congestion

> (although those are very interesting second-order metrics), but the=20
> probability that it will be useful at the time I want to use it.
>
> In many scenarios, mobility is well described as "brownian motion", in

> which things moving approximately together but bump in and out of=20
> sight of each other, or using the word "zoom". If one thinks, for=20
> example, of cars on a highway, I might try to use cars traveling in=20
> the opposite direction as links ("zoom"), cars on orthogonal roads=20
> ("zoom" to the point of "blip" in many cases), routers on light poles=20
> ("zoom" at half the speed), routers in other cars I happen to be=20
> traveling with for a few exits (relatively stable during the interval,

> but blipping in and out around corners/tunnels/etc), and the=20
> occasional router on a hill (which it will be able to see for a long=20
> time as it passes the hill). Which is the tres cool route? The one=20
> that has the highest probability of working when the route is=20
> needed...
>
> So for example if one has a pair of UAVs in orbit over a domain, one=20
> should be able to watch the characteristics of the radio signal and=20
> see that one's signal is slowly degrading while the other's is slowly=20
> improving. At some point, one wants to bring up the approaching UAV,=20
> shift routes to it, and then shut down the now-unused departing UAV=20
> for a smooth switchover, rather than saying "ohmygoshwhatdoidonow"
> when the UAV one is using suddenly goes out of sight. The sudden mass=20
> change model is a leftover from wired concepts...


--
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841


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

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

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

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



From manet-bounces@ietf.org Thu May 04 16:39:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbkbh-0005oD-K0; Thu, 04 May 2006 16:39:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbkbf-0005nM-NI
	for manet@ietf.org; Thu, 04 May 2006 16:39:27 -0400
Received: from nz-out-0102.google.com ([64.233.162.207])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbkbd-0006ag-8s
	for manet@ietf.org; Thu, 04 May 2006 16:39:27 -0400
Received: by nz-out-0102.google.com with SMTP id i28so539595nzi
	for <manet@ietf.org>; Thu, 04 May 2006 13:39:22 -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:content-transfer-encoding:content-disposition;
	b=h7AxAclOM20EyW9+REeGe5s02/BygygYhnqNPSerTpYLVVGSMaErs57IWNoZm83+Gr+fiDoYr74oy3Tx+y3MIYRbyz0yzeRHuPxyOKfe88D4YgUu9RGq34fM+uO9r5p54IB7t0BvdK+3GMAhhmNXe+wQQLfXJol/e4VE0VnhU50=
Received: by 10.36.157.10 with SMTP id f10mr779353nze;
	Thu, 04 May 2006 13:39:22 -0700 (PDT)
Received: by 10.36.251.17 with HTTP; Thu, 4 May 2006 13:39:22 -0700 (PDT)
Message-ID: <a888afbf0605041339p3538c6dbt55096f8f2ba6bf48@mail.gmail.com>
Date: Thu, 4 May 2006 22:39:22 +0200
From: DAIS'06 <lund.ketil@gmail.com>
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-Spam-Score: 0.4 (/)
X-Scan-Signature: f60fbf3dbcaca652b6d10036f0630412
Subject: [manet] DAIS 2006 - CALL FOR PARTICIPATION
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

                            6th IFIP WG 6.1
                       International Conference on
          Distributed Applications and Interoperable Systems

                            DAIS 2006

                "From service-oriented architectures
                   to self-managing applications"

                          Bologna, Italy
                         June 13-16, 2006


                http://www.discotec06.cs.unibo.it/DAIS06/

                   To be held in conjunction with
                 FMOODS 2006  and  Coordination 2006
                   http://discotec06.cs.unibo.it




ABOUT THE CONFERENCE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The conference program presents the state of the art in research
concerning distributed and interoperable systems. In recent
years, distributed applications have indeed gained a practical
and widely-known footing in everyday  computing. Use of new
communication technologies have brought up divergent application
areas, including mobile computing, inter-enterprise collaborations,
and  ubiquitous services, just to name a few. New challenges
include the need for service-oriented architectures, autonomous and
self-managing systems, peer-to-peer systems, grid computing, sensor
networks, semantic enhancements, and adaptivity and dynamicity of
distribution constellations.

Following the evolution of the field, DAIS 2006 focuses on architectures,
models, technologies and platforms for interoperable, scalable and adaptabl=
e
systems that are related to the latest trends towards service orientation a=
nd
self-* properties. The papers to be presented at DAIS 2006 cover methodolog=
ical
aspects, tools and language of building adaptable distributed and interoper=
able
services, fault tolerance and dependability, peer-to-peer systems, mobility
issues, web services applications and performance issues and composition,
semantic web and semantic integration, and context- and location-aware
applications.

This year, the technical program of DAIS drew from 99 submitted papers,
among which 10 were explicitly submitted as work-in-progress papers. From
these, 21 regular and 5 work-in-progress papers were selected for inclusion=
 in
the proceedings. The DAIS 2006 conference is sponsored by IFIP (Internation=
al
Federation for Information Processing) and it was the sixth conference in t=
he
DAIS series of events organized by IFIP Working Group 6.1.

DAIS'06 will be held in the beautiful city of Bologna, Italy, colocated
with the 8th IFIP Formal Methods for Open Object-Based Distributed Systems
(FMOODS'06) and Coordination'06. Attendants of DAIS'06 will have the
opportunity to attend the sessions of the two colocated conferences.


TECHNICAL PROGRAM OF DAIS 06
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D


SESSION 1 (joint with FMOODS and Coordination): Invited talk

"Mobile Service Oriented Architectures (MOSOA)"
Jan Bosch, NOKIA Research Center


SESSION 2; Mobile and pervasive computing

"A Spatial Programming Model for Real Global Smart Space Applications"
Rene Meier, Anthony Harrington, Thomas Termin, Vinny Cahill

"Mobile Process Description and Execution"
Christian P. Kunze, Sonja Zaplata, Winfried Lamersdorf

"An Application Framework for Nomadic, Collaborative Applications"
James O'Brien, Marc Shapiro

"Interfering effects of service adaptation: implications on
self-adapting systems architecture"
Jacqueline Floch, Erlend Stav and Svein Hallsteinsen


SESSION 3: Peer-to-peer systems

"Discovery of Stable Peers in a Self-organising Peer-to-Peer Gradient Topol=
ogy"
Jan Sacha, Jim Dowling, Raymond Cunningham, Rene Meier,


"On the Value of Random Opinions in Decentralized Recommendation"
Elth Ogston, Arno Bakker, Maarten van Steen


SESSION 4: Semantic web

"Information Agents That Learn to Understand Each Other Via Semantic
Negotiation"
Salvatore Garruzzo, Domenico Rosaci

"Discovering Semantic Web Services with Process Speci?cations"
Piya Suwannopas, Twittie Senivongse

"Towards Building a Semantic Grid for E-learning"
Wenya Tian, Huajun Chen


SESSION 5 (joint with FMOODS and Coordination): Invited talk

Chris Hankin, Department of Computing, Imperial College


SESSION 6:  Web services

"A Code Migration Framework for AJAX Applications"
Arno Puder

"High Performance SOAP Processing Driven by Data Mapping Template"
Wei Jun, Hua Lei, Niu Chunlei, Zheng Haoran

"An Approach for Fine-Grained Web Service Performance Monitoring"
Jan Schaefer

"WSInterConnect: Dynamic Composition of Web Services through Web Services"
Josef Spillner, Iris Braun, Alexander Schill


SESSION 7: Fault tolerance 1

"Bounding Recovery Time in Rollback-Recovery Protocol for Mobile
Systems Preserving Session Guarantees"
Jerzy Brzezinski, Anna Kobusinska, Jacek Kobusinski

"Intelligent Dependability Services for Overlay Networks"
Barry Porter, Geoff Coulson, Daniel Hughes


SESSION 8: Architectural adaptation and modelling

"Model-Driven Development of Context-Aware Services"
Joao Paulo A. Almeida, Maria-Eugenia Iacob, Henk Jonkers, Dick Quartel

"Utilising Alternative Application Configurations in Context- and
QoS-Aware Mobile Middleware"
Sten A. Lundesgaard, Ketil Lund, Frank Eliassen

"Timing Driven Architectural Adaptation"
Andrew Wils, Yolande Berbers, Tom Holvoet, Karel De Vlaminck

SESSION 9 (joint with FMOODS and Coordination): Invited talk

Jos=E9 Luiz Fiadeiro, Department of Computer Science,
University of Leicester


SESSION 10: Fault tolerance 2

"Fault-Tolerant Replication Based on Fragmented Objects"
Hans P. Reiser, Rudiger Kapitza, Jorg Domaschka, Franz J. Hauck

"Towards Context-Aware Transaction Services"
Romain Rouvoy, Patricia Serrano-Alvarado, Philippe Merle

"A Local Self-stabilizing Enumeration Algorithm"
Brahim Hamid, Mohamed Mosbah

"Adding Fault-Tolerance to a Hierarchical DRE System"
Paul Rubel, Joseph Loyall, Richard Schantz, Matthew Gillen

"Using Speculative Push for Unnecessary Checkpoint Creation Avoidance"
Arkadiusz Danilecki and Micha l Szychowiak


SESSION 11: Software tools and languages

"A Versatile Kernel for Distributed AOP"
Eric Tanter, Rodolfo Toledo

"Transformation of Centralized Software Components into Distributed"
Abdelhak Seriai, Gautier Bastide, Mourad Oussalah

"PAGE: a distributed infrastructure for fostering RDF-based interoperabilit=
y"
Emanuele Della Valle, Andrea Turati and Alessandro Ghioni



REGISTRATION
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Registration now open.

    o Early registration: until 31 May 2006.

    o for

        - further registration details (student reductions, presenter
          reductions, workshop fees...),
        - travel information and information about Bologna,

       see (under registration)

            http://www.discotec06.cs.unibo.it


ORGANISERS
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

General chair:
Gianluigi Zavattaro, University of Bologna, Italy

Steering committee:
Lea Kutvonen, University of Helsinki, Finland
Hartmut Koenig, BTU Cottbus, Germany
Kurt Geihs, University of Kassel, Germany
Elie Najm, ENST, Paris, France

PC Chairs:
Frank Eliassen, University of Oslo, Norway
Alberto Montresor, University of Trento, Italy


Publicity chair:
Ketil Lund, Simula Research Laboratory, Norway

Local arrangements:

Program committee:
N. Alonistioti, University of Athens, Greece
D. Bakken, Washington State University, USA
A. Bartoli, University of Trieste, Italy
Y. Berbers, Yolande, Katholieke Universiteit Leuven, Belgium  =09
A. Beugnard,  ENST-Bretagne, France=09
G. Blair, Lancaster University, UK
A. Corsaro, Alenia Marconi System, Italy    =09
I. Demeure, ENST, France=09=09
F. Eliassen, University of Oslo, Norway=09
P. Felber, Universit=E9 de Neuch=E2tel, Switzerland,
K. Geihs, University of Kassel, Germany=09
K. M. Goschka, Technical University of Vienna, Austria
S. Graupner, HP Labs, USA
R. Gr=F8nmo,  SINTEF ICT, Norway   =09=09
D. Hagimont, INP Toulouse, France
S. Hallsteinsen, SINTEF ICT, Norway
J. Indulska, University of Queensland, Australia=09=09
E. Jul, Microsoft Research, Cambridge, UK
A. Keller, IBM Thomas J. Watson Research Center, USA=09=09
H. Koenig, BTU Cottbus, Germany=09=09
R. Kroeger, Univeristy of Applied Sciences Wiesbaden, Germany=09
H. Krumm, University of Dortmund, Germany=09
L. Kutvonen, University of Helsinki, Finland
W. Lamersdorf, University of Hamburg, Germany
C. Linnhof-Popien, University of Munich, Germany
K. Lund, Simula Research Laboratory, Norway
R. Meier, Trinity College Dublin, Ireland=09
A. Montresor, University of Trento, Italy
E. Najm, ENST, France
R. Oliveira, Universidade do Minho, Portugal
K. Raymond, University of Queensland, Australia
R. Schantz, BBN Technologies, USA
A. Romanovsky, University of Newcastle upon Tyne, UK
W. Schreiner, Johannes Kepler University Linz, Austria=09
T. Senivongse, Chulalongkorn University, Thailand
K. Sere, =C5bo Akademi University, Finland
J.-B. Stefani, INRIA, France
N. Wang, Tech-X Corporation, USA

--
Ketil Lund
Publicity chair
DAIS'06

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



From manet-bounces@ietf.org Thu May 04 16:42:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbkeZ-0007HX-EG; Thu, 04 May 2006 16:42:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbkeY-0007Fx-Fi
	for manet@ietf.org; Thu, 04 May 2006 16:42:26 -0400
Received: from test-iport-1.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FbkeW-0006vi-7b
	for manet@ietf.org; Thu, 04 May 2006 16:42:26 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by test-iport-1.cisco.com with ESMTP; 04 May 2006 13:42:23 -0700
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k44KgNw1022825;
	Thu, 4 May 2006 13:42:23 -0700 (PDT)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com
	[10.32.244.218])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k44Kef1l016640;
	Thu, 4 May 2006 13:40:41 -0700
In-Reply-To: <445A566F.9030506@mitre.org>
References: <8536FDFA3AD04A49A15804915996569106DEF02D@exchange1.ACN.ad.nmsu.edu>
	<445A4C3A.2030203@mitre.org>
	<08FF3949-AE6F-498C-A5AC-5C3B969B916D@cisco.com>
	<445A566F.9030506@mitre.org>
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <85AA776A-51AD-4880-97C8-CF64015D5A2F@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
Date: Thu, 4 May 2006 13:42:20 -0700
To: Kenneth Brayer <kb@mitre.org>
X-Mailer: Apple Mail (2.749.3)
DKIM-Signature: a=rsa-sha1; q=dns; l=682; t=1146775241; x=1147639241;
	c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20<fred@cisco.com>
	|Subject:Re=3A=20[manet]=20Re=3A=20MANET=20definition=20of=20a=20neighbor
	|To:Kenneth=20Brayer=20<kb@mitre.org>;
	X=v=3Dcisco.com=3B=20h=3DHk1wepC3iEml5uWsgXGxy3raHJ0=3D;
	b=ndpfaCHoAepeMrzKaalnmOa0ZfBddIT1sIuh40damcAWwnTz90DhRVTYTSBbEWKYtw9jw1tD
	yCkeoWJqZpGmU8qzdGWGBEEtaolPC2i9ZYL5NTlLtTmokxezmJ570sDW;
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:

> Some real world MANETS deal with this by trying to eliminate the  
> problem through coding. THey give up usable channel capacity to  
> reduce the error rate and increase channel reliability.

I think they all do. Even 802.11 does that.

But there are longer term issues. A link that goes in and out every  
60 seconds may have wonderful channel characteristics while it is in.  
If I have the option of one that has been stable for ten minutes and  
is otherwise comparable, though, I will opt for the latter ten times  
out of ten. It has a greater probability of being useful at the time  
I want to use it.

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



From manet-bounces@ietf.org Thu May 04 16:42:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbkf2-0007Zb-Ju; Thu, 04 May 2006 16:42:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbkf0-0007ZM-5p
	for manet@ietf.org; Thu, 04 May 2006 16:42:54 -0400
Received: from virginia.nps.edu ([205.155.65.15])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbkex-0006xy-Ch
	for manet@ietf.org; Thu, 04 May 2006 16:42:54 -0400
Received: from north-latitude.nps.navy.mil ([131.120.179.249] RDNS failed) by
	virginia.nps.edu with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 4 May 2006 13:42:38 -0700
Subject: RE: [manet] Re: MANET definition of a neighbor
From: Rex Buddenberg <budden@nps.navy.mil>
To: DANIEL BYRNE <daniel.byrne@adtran.com>
In-Reply-To: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F0E@EXV1.corp.adtran.com>
References: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F0E@EXV1.corp.adtran.com>
Content-Type: text/plain
Date: Thu, 04 May 2006 13:41:59 -0700
Message-Id: <1146775319.8922.449.camel@north-latitude.nps.navy.mil>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.0 
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 May 2006 20:42:38.0631 (UTC)
	FILETIME=[4820BB70:01C66FBB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

I've experienced this enough that it's the way I teach my students.
When you're trying to do requirements analysis, the only think you know
about the capacity requirements statements is that they're wrong.  And
even if they were right once, they're not any more.

On the other hand, if you do the availability requirements work first,
you quite often overtake the capacity issues and shove them off into the
no-nevermind locker.  

My hands-on experience with this requirements analysis gouge is in wired
networks and in radionavigation systems, but it should apply equally
well in radio networks.  


On Thu, 2006-05-04 at 15:28 -0500, DANIEL BYRNE wrote:
> "I have argued along the lines, though, that the most important metric
> for a path in a manet network is not its speed or degree of  congestion
> (although those are very interesting second-order  metrics), but the
> probability that it will be useful at the time I  want to use it." 
> 
> -Agreed. Speed and degree of congestion are second to reliability.
> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will
> increase the probability that the links in the list will be useful.
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
-- 
Rex Buddenberg
Naval Postgraduate School
Code IS/Bu
Monterey, Ca 93943

831/656-3576


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



From manet-bounces@ietf.org Thu May 04 16:47:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbkjB-0001Xj-98; Thu, 04 May 2006 16:47:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbkjA-0001XR-CI
	for manet@ietf.org; Thu, 04 May 2006 16:47:12 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Fbkj9-000784-46
	for manet@ietf.org; Thu, 04 May 2006 16:47:12 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by sj-iport-2.cisco.com with ESMTP; 04 May 2006 13:47:12 -0700
X-IronPort-AV: i="4.05,89,1146466800"; 
	d="scan'208"; a="321694971:sNHT24362004"
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k44KlART023183;
	Thu, 4 May 2006 13:47:10 -0700 (PDT)
Received: from [10.32.244.218] (stealth-10-32-244-218.cisco.com
	[10.32.244.218])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k44KjSYv016788;
	Thu, 4 May 2006 13:45:28 -0700
In-Reply-To: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F0E@EXV1.corp.adtran.com>
References: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F0E@EXV1.corp.adtran.com>
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B37D901B-48CB-4903-A9B2-AA986EACD5EC@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
Date: Thu, 4 May 2006 13:47:07 -0700
To: DANIEL BYRNE <daniel.byrne@adtran.com>
X-Mailer: Apple Mail (2.749.3)
DKIM-Signature: a=rsa-sha1; q=dns; l=777; t=1146775528; x=1147639528;
	c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20<fred@cisco.com>
	|Subject:Re=3A=20[manet]=20Re=3A=20MANET=20definition=20of=20a=20neighbor
	|To:DANIEL=20BYRNE=20<daniel.byrne@adtran.com>;
	X=v=3Dcisco.com=3B=20h=3D383sTy6u8OnOsdsm4weKh9aER4M=3D;
	b=lBF5/o0glOi/8EiJI/cZ+DopyBe9Zxb4+urhQrOjv86XxTSATT8d7fLQtvFWJOKpJNGc/+tA
	4y4GWn02r8bO4q6TE+ucI08mbljjpmJM7ICbfbIU07fzQF/avI48gQUv;
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will
> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the  
table will result in the same table and consume a lot of power and  
CPU while doing so. If something has changed but it is not relevant  
to the communications I am involved in, it is the proverbial tree  
falling in the forest - whether I adapt to the change or not has no  
near term effect. And if there has been a change that affects my  
communications (as end point or relay), any routing protocol I am  
aware of will adapt to it anyway.

Why, specifically, does this accomplish anything?

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



From manet-bounces@ietf.org Thu May 04 16:54:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbkpy-00032F-8Q; Thu, 04 May 2006 16:54:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbkpx-00032A-K6
	for manet@ietf.org; Thu, 04 May 2006 16:54:13 -0400
Received: from smtp-mclean-x.mitre.org ([192.80.55.71]
	helo=smtp-mclean.mitre.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbkpr-0007Fc-No
	for manet@ietf.org; Thu, 04 May 2006 16:54:13 -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
	k44KrvcU004716 for <manet@ietf.org>; Thu, 4 May 2006 16:53:57 -0400
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-mclean.mitre.org (Postfix) with ESMTP id 650571BD80
	for <manet@ietf.org>; Thu,  4 May 2006 16:53:57 -0400 (EDT)
Received: from IMCFE1.MITRE.ORG (imcfe1.mitre.org [129.83.29.3])
	by smtp-mclean.mitre.org (8.12.11.20060308/8.12.11) with ESMTP id
	k44Krk3b004594; Thu, 4 May 2006 16:53:46 -0400
Received: from [129.83.175.29] ([129.83.175.29]) by IMCFE1.MITRE.ORG with
	Microsoft SMTPSVC(6.0.3790.211); Thu, 4 May 2006 16:53:44 -0400
Message-ID: <445A6A68.6040004@mitre.org>
Date: Thu, 04 May 2006 16:56:08 -0400
From: Kenneth Brayer <kb@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
References: <8536FDFA3AD04A49A15804915996569106DEF02D@exchange1.ACN.ad.nmsu.edu>
	<445A4C3A.2030203@mitre.org>
	<08FF3949-AE6F-498C-A5AC-5C3B969B916D@cisco.com>
	<445A566F.9030506@mitre.org>
	<85AA776A-51AD-4880-97C8-CF64015D5A2F@cisco.com>
In-Reply-To: <85AA776A-51AD-4880-97C8-CF64015D5A2F@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 04 May 2006 20:53:44.0869 (UTC)
	FILETIME=[D53C9550:01C66FBC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Fred
You need to look at the link over a long period of time. Ten minutes 
stable may be the fluke.
Ken

Fred Baker wrote:

>
> On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:
>
>> Some real world MANETS deal with this by trying to eliminate the  
>> problem through coding. THey give up usable channel capacity to  
>> reduce the error rate and increase channel reliability.
>
>
> I think they all do. Even 802.11 does that.
>
> But there are longer term issues. A link that goes in and out every  
> 60 seconds may have wonderful channel characteristics while it is in.  
> If I have the option of one that has been stable for ten minutes and  
> is otherwise comparable, though, I will opt for the latter ten times  
> out of ten. It has a greater probability of being useful at the time  
> I want to use it.


-- 
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841


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



From manet-bounces@ietf.org Thu May 04 17:00:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbkvp-00041S-Cl; Thu, 04 May 2006 17:00:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbkvn-00041N-Sb
	for manet@ietf.org; Thu, 04 May 2006 17:00:15 -0400
Received: from p02m142.mxlogic.net ([66.179.26.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbkvm-0007Mp-JA
	for manet@ietf.org; Thu, 04 May 2006 17:00:15 -0400
Received: from unknown [208.61.208.100] (EHLO p02m142.mxlogic.net)
	by p02m142.mxlogic.net (mxl_mta-2.14.0-12)
	with ESMTP id e5b6a544.1409334192.27703.p02m142.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Thu, 04 May 2006 15:00:14 -0600 (MDT)
Received: from unknown [208.61.208.100]
	by p02m142.mxlogic.net (mxl_mta-2.14.0-12)
	with SMTP id c5b6a544.696023984.27681.p02m142.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Thu, 04 May 2006 15:00:12 -0600 (MDT)
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] Re: MANET definition of a neighbor
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 4 May 2006 15:59:45 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F0F@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvu+vPhfojYl4fQNyKDTF6aAqd+QAABwFw
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: "Fred Baker" <fred@cisco.com>
X-Spam: [F=0.0100000000; S=0.010(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.61.208.100]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



From manet-bounces@ietf.org Thu May 04 17:01:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbkx6-0004kA-KG; Thu, 04 May 2006 17:01:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbkx5-0004hV-59
	for manet@ietf.org; Thu, 04 May 2006 17:01:35 -0400
Received: from p02m143.mxlogic.net ([66.179.26.143])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbkx3-0007P3-Ru
	for manet@ietf.org; Thu, 04 May 2006 17:01:35 -0400
Received: from unknown [208.251.151.99]
	by p02m143.mxlogic.net (mxl_mta-2.14.0-12)
	with SMTP id 7ab6a544.1411509168.10617.p02m143.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Thu, 04 May 2006 15:01:27 -0600 (MDT)
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] Re: MANET definition of a neighbor
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 4 May 2006 16:01:15 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F10@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvsPpib5g9q4SFTrGsmaKb1xrXGQAAODtwAABT5mAAAG60EAAAkh/gAAGh3yA=
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: "Mullen, John" <jomullen@ad.nmsu.edu>,
	<manet@ietf.org>
X-Spam: [F=0.0110101924; S=0.011(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.251.151.99]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

=20
Hi Dan,

The problem is that the node doesn't know which links are good and must
make intelligent guesses.  If you rebuild your table without reason to
suspect a route is bad, you will increase the risk of excluding a good
route or including a bad one.

- If you accidently include a bad route, it will be weeded out in the
next cycle or two.  The trick is to update fast enough so that the bad
routes don't have a lasting impact.

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



From manet-bounces@ietf.org Thu May 04 17:03:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbkyi-00066a-ED; Thu, 04 May 2006 17:03:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbkyh-00066R-3Y
	for manet@ietf.org; Thu, 04 May 2006 17:03:15 -0400
Received: from p02m142.mxlogic.net ([66.179.26.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbkyg-0007SP-QV
	for manet@ietf.org; Thu, 04 May 2006 17:03:15 -0400
Received: from unknown [208.61.208.100] (EHLO p02m142.mxlogic.net)
	by p02m142.mxlogic.net (mxl_mta-2.14.0-12)
	with ESMTP id 21c6a544.1021209520.29862.p02m142.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Thu, 04 May 2006 15:03:14 -0600 (MDT)
Received: from unknown [208.61.208.100]
	by p02m142.mxlogic.net (mxl_mta-2.14.0-12)
	with SMTP id f0c6a544.758963120.29787.p02m142.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Thu, 04 May 2006 15:03:11 -0600 (MDT)
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] Re: MANET definition of a neighbor
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 4 May 2006 16:03:00 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F11@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvu0z32JBzAJmpT06ojWPmSs2EIAAACDtQ
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: "Fred Baker" <fred@cisco.com>,
	"Kenneth Brayer" <kb@mitre.org>
X-Spam: [F=0.0100000000; S=0.010(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.61.208.100]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

It only has better long term reliability.  A manet packet doesn't take
60 seconds to transmit, so you are looking for a very small window of
opportunity.  Statistically the differnce between the two links is very
small when considering the transmission time of the manet packet.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:42 PM
To: Kenneth Brayer
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:

> Some real world MANETS deal with this by trying to eliminate the=20
> problem through coding. THey give up usable channel capacity to reduce

> the error rate and increase channel reliability.

I think they all do. Even 802.11 does that.

But there are longer term issues. A link that goes in and out every 60
seconds may have wonderful channel characteristics while it is in. =20
If I have the option of one that has been stable for ten minutes and is
otherwise comparable, though, I will opt for the latter ten times out of
ten. It has a greater probability of being useful at the time I want to
use it.

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

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



From manet-bounces@ietf.org Thu May 04 17:14:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbl9T-0007ek-9u; Thu, 04 May 2006 17:14:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbl9R-0007ef-Or
	for manet@ietf.org; Thu, 04 May 2006 17:14:21 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbl9R-0007al-F2
	for manet@ietf.org; Thu, 04 May 2006 17:14:21 -0400
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
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Thu, 4 May 2006 15:14:18 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF0FE@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvu+vPhfojYl4fQNyKDTF6aAqd+QAABwFwAAB/LNA=
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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

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



From manet-bounces@ietf.org Thu May 04 17:47:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fblex-00008r-Be; Thu, 04 May 2006 17:46:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fblev-00007N-Re
	for manet@ietf.org; Thu, 04 May 2006 17:46:53 -0400
Received: from mx11.bbn.com ([128.33.0.80])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbleu-0000C4-Jg
	for manet@ietf.org; Thu, 04 May 2006 17:46:53 -0400
Received: from dommiel.bbn.com ([192.1.122.15] helo=7C-517.bbn.com)
	by mx11.bbn.com with esmtp (Exim 4.60)
	(envelope-from <celliott@bbn.com>)
	id 1Fbles-0004y1-3q; Thu, 04 May 2006 17:46:50 -0400
Message-Id: <6.2.1.2.2.20060504174629.038a6ae0@127.0.0.1>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Thu, 04 May 2006 17:47:36 -0400
To: <jasteven@rockwellcollins.com>,manet@ietf.org
From: Chip Elliott <celliott@bbn.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
In-Reply-To: <OF85C47C99.169C5FB8-ON86257164.00621C23-86257164.00626B1C@
	rockwellcollins.com>
References: <E1FbgFa-0007Yt-8w@megatron.ietf.org>
	<OF85C47C99.169C5FB8-ON86257164.00621C23-86257164.00626B1C@rockwellcollins.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org



I think Jim has stated the fundamental challenge with MANETs
very succinctly, and his comment is worth some reflection:

At 01:54 PM 5/4/2006, jasteven@rockwellcollins.com wrote:

>The definition of a neighbor is why wireless MANETs are so much more 
>difficult than wireline networks.  In fact, one could say that the problem 
>of determining who is a MANET neighbor and controlling the link to MANET 
>neighbors sums up the problems and complexities associated with MANETs - 
>at least to a first order approximation!

 From my own perspective, even the term "link" can lead to
great mental confusion. And once one relies on simulations where
everyone within range has 100% reception, and everyone outside
a range has 0%, one has missed most of what makes a
real MANET so challenging.

Mobility adds more complexity, but the probabilistic,
self-noisy, shared channel is the core problem, I think. And as
Jim points out, layering doesn't help and can even hurt.

Nice statement of the problem, Jim.

Chip Elliott
Principal Engineer, BBN 


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



From manet-bounces@ietf.org Thu May 04 17:49:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fblgz-0000SQ-KE; Thu, 04 May 2006 17:49:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fblgx-0000SG-TD
	for manet@ietf.org; Thu, 04 May 2006 17:48:59 -0400
Received: from p02m143.mxlogic.net ([66.179.26.143])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fblgx-0000OA-8u
	for manet@ietf.org; Thu, 04 May 2006 17:48:59 -0400
Received: from unknown [208.251.151.99] (EHLO EXV1.corp.adtran.com)
	by p02m143.mxlogic.net (mxl_mta-2.14.0-12)
	with ESMTP id bc67a544.1327299504.12792.p02m143.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Thu, 04 May 2006 15:48:59 -0600 (MDT)
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] Re: MANET definition of a neighbor
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 4 May 2006 16:48:57 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F12@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvu+vPhfojYl4fQNyKDTF6aAqd+QAABwFwAAB/LNAAAImI4A==
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: "Mullen, John" <jomullen@ad.nmsu.edu>
X-Spam: [F=0.0100000000; S=0.010(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.251.151.99]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Yeah, I agree, an AGC is a better analog and better solution.  Basically
low pass the table through constant sampling.=20

-----Original Message-----
From: Mullen, John [mailto:jomullen@ad.nmsu.edu]=20
Sent: Thursday, May 04, 2006 4:14 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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

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



From manet-bounces@ietf.org Thu May 04 21:12:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbor6-000435-B8; Thu, 04 May 2006 21:11:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbor4-000430-Ie
	for manet@ietf.org; Thu, 04 May 2006 21:11:38 -0400
Received: from bay0-omc2-s8.bay0.hotmail.com ([65.54.246.144])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbor3-0008HK-7N
	for manet@ietf.org; Thu, 04 May 2006 21:11:38 -0400
Received: from BAY116-W3 ([65.54.246.190]) by bay0-omc2-s8.bay0.hotmail.com
	with Microsoft SMTPSVC(6.0.3790.211); Thu, 4 May 2006 18:11:36 -0700
X-Originating-IP: [131.107.0.105]
X-Originating-Email: [alec.wolman@hotmail.com]
Message-ID: <BAY116-W3149F02EAD192A9051E17FCB50@phx.gbl>
MIME-Version: 1.0
From: "Alec Wolman" <alec.wolman@hotmail.com>
To: <manet@ietf.org>
Date: Thu, 4 May 2006 18:11:36 -0700
X-OriginalArrivalTime: 05 May 2006 01:11:36.0797 (UTC)
	FILETIME=[DB3970D0:01C66FE0]
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Subject: [manet] MobiSys 2006 Call for Participation
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1191644000=="
Errors-To: manet-bounces@ietf.org

--===============1191644000==
Content-Type: multipart/alternative;
	boundary="_450cdbee-984e-4c23-b23f-256a0d7e1ac2_"

--_450cdbee-984e-4c23-b23f-256a0d7e1ac2_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

***************************
Call for participation
MobiSys 2006 - The Fourth International Conference on Mobile Systems, Appli=
cations, and Services
Uppsala, Sweden, June 19-22, 2006.
***************************
=20
The advance registration deadline for MobiSys 2006 is fast approaching: *Ma=
y 15th, 2006*
=20
See the MobiSys website - http://www.sigmobile.org/mobisys/2006/index.html =
for details on the program and registration information.
=20
_________________________________________________________________
Join the next generation of Hotmail and you could win the adventure of a li=
fetime
http://www.imagine-msn.com/minisites/sweepstakes/mail/register.aspx=

--_450cdbee-984e-4c23-b23f-256a0d7e1ac2_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>=0A=
<head>=0A=
<style>=0A=
P=0A=
{=0A=
margin:0px;=0A=
padding:0px=0A=
}=0A=
body=0A=
{=0A=
FONT-SIZE: 10pt;=0A=
FONT-FAMILY:Tahoma=0A=
}=0A=
</style>=0A=
</head>=0A=
<body><P ><BR >***************************</P>
<P >Call for participation</P>
<P ><FONT class=3D"">MobiSys</FONT> 2006 - The Fourth International Confere=
nce on Mobile Systems, Applications, and Services</P>
<P >Uppsala, Sweden, June 19-22, 2006.</P>
<P >***************************</P>
<P >&nbsp;</P>
<P >The advance registration deadline for <FONT class=3D"">MobiSys</FONT> 2=
006 is fast approaching: *May 15th, 2006*</P>
<P >&nbsp;</P>
<P >See the <FONT class=3D"" >MobiSys</FONT> website - <A href=3D"http://ww=
w.sigmobile.org/mobisys/2006/index.html" >http://www.sigmobile.org/<FONT cl=
ass=3D"">mobisys</FONT>/2006/index.html</A> for details on the program and =
registration information.<BR ></P>
<P >&nbsp;</P><br /><hr />Enter the Windows Live Mail beta sweepstakes <a h=
ref=3D'http://www.imagine-msn.com/minisites/sweepstakes/mail/register.aspx'=
 target=3D'_new'>Upgrade today</a></body>=0A=
</html>=

--_450cdbee-984e-4c23-b23f-256a0d7e1ac2_--


--===============1191644000==
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

--===============1191644000==--




From manet-bounces@ietf.org Fri May 05 02:35:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fbtto-0002jd-Ko; Fri, 05 May 2006 02:34:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fbttl-0002jV-JL
	for manet@ietf.org; Fri, 05 May 2006 02:34:45 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbttj-0003Gn-Vl
	for manet@ietf.org; Fri, 05 May 2006 02:34:45 -0400
Received: from c1-vpn7.isi.edu (c1-vpn7.isi.edu [128.9.176.37])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k456XrN24083
	for <manet@ietf.org>; Thu, 4 May 2006 23:33:53 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: manet@ietf.org
Content-Type: text/plain
Date: Thu, 04 May 2006 23:33:49 -0700
Message-Id: <1146810830.3374.28.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) 
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: weiye@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Subject: [manet] ACM SenSys'06 call for posters and demos
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Our Apologies if you have received multiple copies.

Wei Ye and Cormac J. Sreenan
SenSys'06 Publicity Co-Chairs
------------

ACM SenSys 2006: Call for Posters and Demos

The 4th ACM Conference on Embedded Networked Sensor Systems
Sponsored by ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS, SIGMETRICS and  
SIGBED; with support from NSF.
Boulder, Colorado, USA
November 1-3, 2006
http://sensys.acm.org/2006/

CALL FOR POSTERS

The poster session will provide a forum for researchers to showcase  
their work and obtain feedback on ongoing research from knowledgeable  
conference attendees. Areas of interest are the same as those listed  
in the technical call for papers. While the poster need not describe  
completed work, it should report on research for which at least  
preliminary results are available. We especially encourage  
submissions by students (that is, for which a student is the first  
author on the poster).

POSTER SUBMISSION INSTRUCTIONS

Poster proposals must be submitted as a single PDF file with no more  
than 3 pages. The first two pages should contain an abstract  
describing the research content of the poster, along with title,  
authors, institutional affiliations and contact information. The  
third page should contain a thumbnail draft of the poster's contents.  
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  
deadline. Any questions for the Poster Co-chairs Henry Tirri (Nokia),  
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  
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 

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



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



From manet-bounces@ietf.org Fri May 05 04:34:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FbvlC-0004vg-7E; Fri, 05 May 2006 04:34:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FbvlA-0004v8-6P
	for manet@ietf.org; Fri, 05 May 2006 04:34:00 -0400
Received: from mx-serv.inrialpes.fr ([194.199.18.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fbvl6-0000Pz-MP
	for manet@ietf.org; Fri, 05 May 2006 04:34:00 -0400
Received: from noisetier.inrialpes.fr (noisetier.inrialpes.fr [194.199.18.79])
	by mx-serv.inrialpes.fr (8.13.6/8.13.0) with ESMTP id k458XiLs009623;
	Fri, 5 May 2006 10:33:44 +0200 (MEST)
Received: from [134.214.144.147] (ares-fleury-1.insa-lyon.fr [134.214.144.147])
	(authenticated bits=0)
	by noisetier.inrialpes.fr (8.13.6/8.13.4) with ESMTP id k458XgUc027825
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 5 May 2006 10:33:43 +0200 (MEST)
Message-ID: <445B0DDC.70506@inria.fr>
Date: Fri, 05 May 2006 10:33:32 +0200
From: Eric Fleury CITI/ARES <Eric.Fleury@inria.fr>
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: fr, en
MIME-Version: 1.0
To: tarot@hds.utc.fr, arp@cines.fr, manet@ietf.org, PODC@LISTSERV.ACM.ORG
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0
	(mx-serv.inrialpes.fr [194.199.18.100]);
	Fri, 05 May 2006 10:33:45 +0200 (MEST)
X-mx-serv-inrialpes-fr-MailScanner-Information: Please contact
	postmaster@inrialpes.fr for more information
X-mx-serv-inrialpes-fr-MailScanner: Found to be clean
X-mx-serv-inrialpes-fr-MailScanner-SpamCheck: n'est pas un polluriel,
	SpamAssassin (score=1.442, requis 6, MAILTO_TO_SPAM_ADDR 0.28,
	SUBJ_ALL_CAPS 1.17)
X-mx-serv-inrialpes-fr-MailScanner-SpamScore: 1
X-mx-serv-inrialpes-fr-MailScanner-From: eric.fleury@inria.fr
X-Spam-Status: No
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx-serv.inrialpes.fr id
	k458XiLs009623
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Cc: 
Subject: [manet] MSN-2006 CFP
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

CALL FOR PAPERS

2nd International Conference on Mobile Ad-hoc and Sensor Networks (MSN'06=
)
13-15 Dec 2006, Hong Kong, China
http://www.comp.polyu.edu.hk/msn06

Organized and supported by Hong Kong Polytechnic University
-------------------------------------------------------------------------

Following the success of the first conference MSN=A1=AF05, held in Wuhan,=
 China, MSN=A1=AF06 provides a forum for researchers and practitioners to=
 exchange research results and share development experiences. Topics of i=
nterest include, but are not limited to, the following areas in mobile ad=
 hoc and sensor networks:

- Network architecture and protocols
- Software platforms and development tools=20
- Self-organization and synchronization=20
- Routing and data dissemination=20
- Failure resilience and fault isolation
- Energy management
- Data, information, and signal processing
- Security and privacy
- Network planning, provisioning, and deployment
- Network modeling and performance evaluation=20
- Developments and applications=20
- Integration with other systems=20


SUBMISSION GUIDELINES
---------------------
MSN invites authors to submit original and unpublished work. Submissions =
should include an abstract, key words, the e-mail address of the correspo=
ndingauthor, and must not exceed 15 pages, including tables and figures, =
with PDF, PostScript, or MSWord format.  Electronic
submission through the submission website is strongly encouraged. Hard co=
pies will be accepted only if electronic submission is not possible. Subm=
ission of a paper should be regarded as an undertaking that, should the p=
aper be accepted,at least one ofthe authors will register and
attend the conference to present the work.=20

Questions concerning hardcopy submissions or any other issues may be dire=
cted to the Program Chair at msn06@comp.polyu.edu.hk.=20

IMPORTANT DATES
---------------------
Important Dates:
Submission deadline:        10 June, 2006=20
Notification of acceptacne: 20 Aug, 2006
Final Manuscript due:       5 Sept, 2006
Conference:                 13 - 15 Dec. 2006

PUBLICATION
---------------------
The conference proceedings will be published in Springer's Lecture Notes =
in Computer Science (pending) and distributed at the conference. Selected=
 papers of best quality will be published in a special issue at journal s=
pecial issues.

BEST PAPER AWARDS
---------------------
The program committee will select one winner for the Best Paper Award
(all regular papers areeligible) and one winner for the Best Student
Paper Award (only the regular papers whose firstauthor is a full-time
student are eligible). Each winner will be presented at the conferencewit=
h
a certificate and US$100.=20

KEYNOTE SPEECHES:
---------------------
MSN'06 will feature three keynote speeches. Speakers and topics will soon=
 be announced.

ORGANIZING AND PROGRAM COMMITTES
--------------------------------
Advisory Committees=20
Keith K.C. Chan, H.K. Polytechnic Univ., H.K.
Marco Conti, IIT, CNR, Italy
Mario Gerla, UCLA, USA
Lionel Ni, H.K. Univ. of Sci. & Tech., H.K.
Jie Wu, Florida Atlantic Univ., USA

General Co-Chairs=20
Sajal K. Das, Univ. of Texas at Arlington, USA
Xiaohua Jia, HK CityU

Program Co-Chairs=20
Jiannong Cao, HK PolyU
Ivan Stojmenovic, Univ. of Ottawa, Canada

Program Vice Co-Chairs=20
- Physical layer, power, and other architecture issues
Amiya Nayak, Univ. of Ottawa, Canada

- Data link layer and MAC protocols
Vojislav B. Misic, University of Manitoba, Canada

- Routing and broadcasting
Pedro M. Ruiz, University of Murcia, Spain

- Deployment, topology control, clustering,
Paolo Santi, Istituto di Informatica e Telematica del CNR, Italy=20

- Transport layer, session layer protocols
Soung-Chang Liew, Chinese University of Hong Kong, Hong Kong=20

- Data centric, tracking, and positioning protocols in sensor networks
Eric Fleury, INRIA, France=20

- Query processing, Middleware
Jingyuan(Alex) Zhang, University of Alabama, USA

- Security, privacy, and reliability
Zhen Jiang, West Chester University, USA

- Systems and applications
Yunhao Liu, Hong Kong University of Science and Technology, H.K.

Progrma Committee
Please see MSN=A1=AF06 Website for the list of program committee members

Publicity Co-Chairs=20
Wei Lou, Hong Kong Polytechnic Univ. H.K.
Isabelle Simplot-Ryl, Univ. Lille 1, France
Yu Wang, Univ. of North Carolina at Charlotte, USA

Local Organization Chair=20
Allan Wong, Hong Kong Polytechnic Univ. H.K.

Publication Chair=20
Jianliang Xu, Hong Kong Baptist Univ., H.K.

Awards Co-Chairs
Stephen Olariu, Old Dominion University, USA
Symeon Papavasileiou, National Technical Univ. of Athens, Greece
Makoto Takizawa, Tokyo Denki Univ., Japan

Webmaster
Hui Cheng (cshcheng@comp.polyu.edu.hk)

----------------------------------------
For more information,  please contact:

Prof. Jiannong Cao
Deartment of Computing
Hong Kong Polytechnic University
Email: csjcao@comp.polyu.edu.hk

Prof. Ivan Stojmenovic
School of Information Technology and Engineering
Univ. of Ottawa, Canada
Email: ivan@site.uottawa.ca=20

--=20
Eric FLEURY
PROF. AT INSA of LYON
Co-HEAD OF CITI LAB & Co-Leader of ARES INRIA PROJECT
TEL: +33 472 436 421  FAX: +33 472 436 227
WEB: http://ares.insa-lyon.fr/~efleury/


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



From manet-bounces@ietf.org Fri May 05 09:51:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fc0iM-0007jt-5v; Fri, 05 May 2006 09:51:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc0iL-0007jo-3g
	for manet@ietf.org; Fri, 05 May 2006 09:51:25 -0400
Received: from smtp107.biz.mail.re2.yahoo.com ([206.190.52.176])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Fc0iK-00055D-Lp
	for manet@ietf.org; Fri, 05 May 2006 09:51:25 -0400
Received: (qmail 50888 invoked from network); 5 May 2006 13:51:24 -0000
Received: from unknown (HELO YEOBS) (boonsain.yeo@sensimesh.com@218.186.168.49
	with login)
	by smtp107.biz.mail.re2.yahoo.com with SMTP; 5 May 2006 13:51:23 -0000
Message-ID: <023401c6704a$ff127b90$6501a8c0@Wavex.com>
From: "Boon Sain Yeo" <eleybs@nus.edu.sg>
To: <manet@ietf.org>
Subject: [manet] CFP ICCS 2006, 30 Oct - 2 Nov 2006, Singapore
Date: Fri, 5 May 2006 21:50:40 +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: 0.1 (/)
X-Scan-Signature: 6fc5b1c74c5bed09a3a9da2884900dec
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0049812244=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0049812244==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_022F_01C6708D.F34A99D0"

This is a multi-part message in MIME format.

------=_NextPart_000_022F_01C6708D.F34A99D0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Our apologies if you receive multiple copies of this email


CALL FOR PAPERS=20

Tenth IEEE International Conference on Communication Systems
30 Oct - 2 Nov 2006, Singapore

http://www.i2r.a-star.edu.sg/iccs2006=20

Technically co-sponsored by the IEEE and the IEEE Communications Society
co-organized by the IEEE Singapore Section, Singapore Communications =
Society Local Chapter, the National University of Singapore (NUS) and =
the Institute for Infocomm Research (I2R), Singapore.=20

The organising and technical committees of the symposium are seeking =
original contributions in the areas of, but not limited to:

. Antennas, propagation and channel modeling
. Cognitive radio
. Communication software & electronics
. Dynamic spectrum management
. Grid networks
. High speed networks=20
. Information Theory=20
. Microwave devices and systems=20
. Mobile radio communication systems=20
. Modulation and coding=20
. Network architecture=20
. Network Security=20
. Optical communications and photonics
. Optical networks
. Resource allocation, mobility management and QoS provisioning=20
. Satellite communications
. Signal processing for communications=20
. Space time processing & MIMO systems=20
. Speech, video and image processing=20
. Spread spectrum systems=20
. Ultra wideband technology
. Wireless ad-hoc and sensor networks=20


SUBMISSION GUIDELINES

Authors are invited to submit full papers in PDF format with sufficient =
detail to permit reasonable evaluation.  Detailed instructions can be =
found on the conference website:  http://www.i2r.a-star.edu.sg/iccs2006. =


The proposal for tutorial should include the title and clear explanation =
of the content of the proposed tutorial. Please include in the proposal =
(1) Organizer Name, (2) Name of proposed instructor, (3) Title of =
tutorial and detailed outline, (4) Qualifications of proposed =
instructor, (5) Full contact information: mailing address, telephone & =
fax number, and email address.=20

Special Session Proposal
The proposal should include the title of the proposed special session =
and brief description of the proposed session. Please include in the =
proposal (1) Full Organizer Name, (2) Short biography of proposed =
session organizer, (3) Complete mailing address, (4) Telephone, (5) Fax =
number, (6) Email address, and (7) Potential authors that could =
contribute to the session.

Detailed submission guidelines and manuscript templates will be =
published on the conference's website.

IMPORTANT DATES=20

Abstract submission deadline: May 31, 2006
Notification of acceptance: July 31, 2006
Tutorials proposals deadline:  August 31, 2006
Final paper due: July 1, 2006


CONFERENCE COMMITTEE=20

General Chair:
Lawrence Wong
I2R, Singapore

Organizing Chair:
Yong Huat Chew
I2R, Singapore

Technical Program Co-Chairs:
Tjeng Thiang Tjung
I2R, Singapore
=20
Mehul Motani
NUS, Singapore

Mohan Gurusamy
NUS, Singapore

Ying Chang Liang
I2R, Singapore=20

Publication Chair:
Nallanathan Arumugam
NUS, Singapore=20

Finance Chair:
Michael Ong
NUS, Singapore

Publicity Chair:=20
Boon Sain Yeo
I2R, Singapore

Local Arrangement Chair:
Emily Hao Jianzhong
I2R, Singapore

Sponsorship Chair:
Manjeet Singh=20
I2R, Singapore

Committee Members
Zhining Chen
I2R, Singapore

Chen Khong Tham
NUS, Singapore

International Advisory Panel:
Tjeng Thiang Tjung (Chair)
I2R, Singapore                                                       =20

Fumiyuki Adachi         =20
Tohoku University, Japan   =20

Vijay Bhargava
University of British Columbia, Canada

Hsiao-Hwa Chen
National Sun Yat Sen University, Taiwan.

Kah Seng Chung
Curtin University of Technology, Australia   =20

Lajos Hanzo
University of Southampton, UK                     =20

Paul K M Ho
Simon Fraser University, Canada
Chi Chung Ko                                      =20
NUS, Singapore
                             =20
Witold A. Krzymien
University of Alberta, Canada =20

Jon W. Mark
University of Waterloo, Canada

Kenneth K Mei   =20
City Uiniversity of Hong Kong, China                     =20

Tung Sang Ng    =20
The University of Hong Kong, China=20

Ramjee Prasad                              =20
Aalborg University, Denmark

Yoshihide Yamada   =20
National Defense Academy, Japan

Kiyotoshi Yasumoto  =20
Kyushu University, Japan              =20

Susumu Yoshida                          =20
Kyoto University, Japan                       =20

Peter T S Yum
Chinese University Hong Kong, China                  =20

Keith Q T Zhang                              =20
City University of Hong Kong, China

------=_NextPart_000_022F_01C6708D.F34A99D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Our apologies if you receive multiple =
copies of=20
this email</FONT></DIV>
<DIV>&nbsp;</DIV><FONT face=3DArial size=3D2>
<DIV><BR>CALL FOR PAPERS </DIV>
<DIV>&nbsp;</DIV>
<DIV>Tenth IEEE International Conference on Communication Systems<BR>30 =
Oct - 2=20
Nov 2006, Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV><A=20
href=3D"http://www.i2r.a-star.edu.sg/iccs2006">http://www.i2r.a-star.edu.=
sg/iccs2006</A>=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Technically co-sponsored by the IEEE and the IEEE Communications=20
Society<BR>co-organized by the IEEE Singapore Section, Singapore =
Communications=20
Society Local Chapter, the National University of Singapore (NUS) and =
the=20
Institute for Infocomm Research (I2R), Singapore. </DIV>
<DIV>&nbsp;</DIV>
<DIV>The organising and technical committees of the symposium are =
seeking=20
original contributions in the areas of, but not limited to:</DIV>
<DIV>&nbsp;</DIV>
<DIV>=95&nbsp;Antennas, propagation and channel =
modeling<BR>=95&nbsp;Cognitive=20
radio<BR>=95&nbsp;Communication software &amp; =
electronics<BR>=95&nbsp;Dynamic=20
spectrum management<BR>=95&nbsp;Grid networks<BR>=95&nbsp;High speed =
networks=20
<BR>=95&nbsp;Information Theory <BR>=95&nbsp;Microwave devices and =
systems=20
<BR>=95&nbsp;Mobile radio communication systems <BR>=95&nbsp;Modulation =
and coding=20
<BR>=95&nbsp;Network architecture <BR>=95&nbsp;Network Security =
<BR>=95&nbsp;Optical=20
communications and photonics<BR>=95&nbsp;Optical =
networks<BR>=95&nbsp;Resource=20
allocation, mobility management and QoS provisioning =
<BR>=95&nbsp;Satellite=20
communications<BR>=95&nbsp;Signal processing for communications =
<BR>=95&nbsp;Space=20
time processing &amp; MIMO systems <BR>=95&nbsp;Speech, video and image =
processing=20
<BR>=95&nbsp;Spread spectrum systems <BR>=95&nbsp;Ultra wideband=20
technology<BR>=95&nbsp;Wireless ad-hoc and sensor networks </DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>SUBMISSION GUIDELINES</DIV>
<DIV>&nbsp;</DIV>
<DIV>Authors are invited to submit full papers in PDF format with =
sufficient=20
detail to permit reasonable evaluation.&nbsp; Detailed instructions can =
be found=20
on the conference website:&nbsp; <A=20
href=3D"http://www.i2r.a-star.edu.sg/iccs2006">http://www.i2r.a-star.edu.=
sg/iccs2006</A>.=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>The proposal for tutorial should include the title and clear =
explanation of=20
the content of the proposed tutorial. Please include in the proposal (1) =

Organizer Name, (2) Name of proposed instructor, (3) Title of tutorial =
and=20
detailed outline, (4) Qualifications of proposed instructor, (5) Full =
contact=20
information: mailing address, telephone &amp; fax number, and email =
address.=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Special Session Proposal<BR>The proposal should include the title =
of the=20
proposed special session and brief description of the proposed session. =
Please=20
include in the proposal (1) Full Organizer Name, (2) Short biography of =
proposed=20
session organizer, (3) Complete mailing address, (4) Telephone, (5) Fax =
number,=20
(6) Email address, and (7) Potential authors that could contribute to =
the=20
session.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Detailed submission guidelines and manuscript templates will be =
published=20
on the conference's website.</DIV>
<DIV>&nbsp;</DIV>
<DIV>IMPORTANT DATES </DIV>
<DIV>&nbsp;</DIV>
<DIV>Abstract submission deadline: May 31, 2006<BR>Notification of =
acceptance:=20
July 31, 2006<BR>Tutorials proposals deadline:&nbsp; August 31, =
2006<BR>Final=20
paper due: July 1, 2006</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>CONFERENCE COMMITTEE </DIV>
<DIV>&nbsp;</DIV>
<DIV>General Chair:<BR>Lawrence Wong<BR>I2R, Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV>Organizing Chair:<BR>Yong Huat Chew<BR>I2R, Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV>Technical Program Co-Chairs:<BR>Tjeng Thiang Tjung<BR>I2R,=20
Singapore<BR>&nbsp;<BR>Mehul Motani<BR>NUS, Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV>Mohan Gurusamy<BR>NUS, Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV>Ying Chang Liang<BR>I2R, Singapore </DIV>
<DIV>&nbsp;</DIV>
<DIV>Publication Chair:<BR>Nallanathan Arumugam<BR>NUS, Singapore </DIV>
<DIV>&nbsp;</DIV>
<DIV>Finance Chair:<BR>Michael Ong<BR>NUS, Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV>Publicity Chair: <BR>Boon Sain Yeo<BR>I2R, Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV>Local Arrangement Chair:<BR>Emily Hao Jianzhong<BR>I2R, =
Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV>Sponsorship Chair:<BR>Manjeet Singh <BR>I2R, Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV>Committee Members<BR>Zhining Chen<BR>I2R, Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV>Chen Khong Tham<BR>NUS, Singapore</DIV>
<DIV>&nbsp;</DIV>
<DIV>International Advisory Panel:<BR>Tjeng Thiang Tjung (Chair)<BR>I2R, =

Singapore&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Fumiyuki =
Adachi&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>Tohoku University, Japan&nbsp;&nbsp;&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>Vijay Bhargava<BR>University of British Columbia, Canada</DIV>
<DIV>&nbsp;</DIV>
<DIV>Hsiao-Hwa Chen<BR>National Sun Yat Sen University, Taiwan.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Kah Seng Chung<BR>Curtin University of Technology,=20
Australia&nbsp;&nbsp;&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>Lajos Hanzo<BR>University of Southampton,=20
UK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Paul K M Ho<BR>Simon Fraser University, Canada<BR>Chi Chung=20
Ko&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;=20
<BR>NUS,=20
Singapore<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>Witold A. Krzymien<BR>University of Alberta, Canada&nbsp; </DIV>
<DIV>&nbsp;</DIV>
<DIV>Jon W. Mark<BR>University of Waterloo, Canada</DIV>
<DIV>&nbsp;</DIV>
<DIV>Kenneth K Mei&nbsp;&nbsp;&nbsp; <BR>City Uiniversity of Hong Kong,=20
China&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Tung Sang Ng&nbsp;&nbsp;&nbsp;&nbsp; <BR>The University of Hong =
Kong, China=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Ramjee=20
Prasad&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>Aalborg University, Denmark</DIV>
<DIV>&nbsp;</DIV>
<DIV>Yoshihide Yamada&nbsp;&nbsp;&nbsp; <BR>National Defense Academy,=20
Japan</DIV>
<DIV>&nbsp;</DIV>
<DIV>Kiyotoshi Yasumoto&nbsp;&nbsp; <BR>Kyushu University,=20
Japan&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Susumu=20
Yoshida&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;=20
<BR>Kyoto University,=20
Japan&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Peter T S Yum<BR>Chinese University Hong Kong,=20
China&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
</DIV>
<DIV>&nbsp;</DIV>
<DIV>Keith Q T=20
Zhang&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
<BR>City University of Hong Kong, China<BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_022F_01C6708D.F34A99D0--



--===============0049812244==
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

--===============0049812244==--





From manet-bounces@ietf.org Fri May 05 10:55:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fc1iT-0008Rx-AU; Fri, 05 May 2006 10:55:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc1iR-0008NZ-LQ
	for manet@ietf.org; Fri, 05 May 2006 10:55:35 -0400
Received: from web26602.mail.ukl.yahoo.com ([217.146.176.52])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Fc1iN-0007T5-UP
	for manet@ietf.org; Fri, 05 May 2006 10:55:35 -0400
Received: (qmail 22763 invoked by uid 60001); 5 May 2006 14:38:03 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=2p0emvgixkF7igKQYeCCjVi1w9dbFWUfbUHOBpHfusxsXQ1CdG7j5e8zrsCyR+RGko2rFHEv2LNQwVqrPSaVsdefNE7z2jYGjvIjfYEGh8zRvGFe23NKNTROoXgsfFdVPq2r8Aev5jBtVJd/Yzp5VGK0ybdSKJSzimr7HhYZ1U0=
	; 
Message-ID: <20060505143803.22761.qmail@web26602.mail.ukl.yahoo.com>
Received: from [196.217.107.89] by web26602.mail.ukl.yahoo.com via HTTP;
	Fri, 05 May 2006 16:38:03 CEST
Date: Fri, 5 May 2006 16:38:03 +0200 (CEST)
From: www triste <unhapy1983@yahoo.fr>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: [manet] the working of OLSR protocole
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0324218444=="
Errors-To: manet-bounces@ietf.org

--===============0324218444==
Content-Type: multipart/alternative; boundary="0-1479464263-1146839883=:21948"
Content-Transfer-Encoding: 8bit

--0-1479464263-1146839883=:21948
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello everybody
  i tryed to understand the rfc 3626 concerning the OLSR routing protocole,i remarked that the time is always using for determination of links,and neighbors,and mprs.
  but i didn't understand a lot of things.
   
  1) L_SYM_time is the time until the link is concedered symetric.
  thats mean,the link is initialated firstly to L_SYM_time.
  2) if you can explain me the process to determinate the link,and the symetric link i will be very happy,thanks  a lot for help
   

		
---------------------------------
 Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Cliquez ici.
--0-1479464263-1146839883=:21948
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>Hello everybody</div>  <div>i tryed to understand the rfc 3626 concerning the OLSR routing protocole,i remarked that the time is always using for determination of links,and neighbors,and mprs.</div>  <div>but i didn't understand a lot of things.</div>  <div>&nbsp;</div>  <div>1) L_SYM_time is the time until the link is concedered symetric.</div>  <div>thats mean,the link is initialated firstly to L_SYM_time.</div>  <div>2) if you can explain me the process to determinate the link,and the symetric link i will be very happy,thanks&nbsp; a lot for help</div>  <div>&nbsp;</div><p>
		<hr size="1" /> 
<b>Faites de Yahoo! votre page d'accueil sur le web</b> pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. <a href="http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yahoo.com/set" target=_blank>Cliquez ici</a>.
--0-1479464263-1146839883=:21948--


--===============0324218444==
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

--===============0324218444==--




From manet-bounces@ietf.org Fri May 05 11:00:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fc1nM-0002Tg-8w; Fri, 05 May 2006 11:00:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc1nK-0002Tb-4Z
	for manet@ietf.org; Fri, 05 May 2006 11:00:38 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc1nI-0007fi-TA
	for manet@ietf.org; Fri, 05 May 2006 11:00:38 -0400
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
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Fri, 5 May 2006 09:00:59 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF23A@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvsPpib5g9q4SFTrGsmaKb1xrXGQAAODtwAABT5mAAAG60EAAAkh/gAAGh3yAAJbNEQA==
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>,
	<manet@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Dan,

It doesn't work that way.  The chances of selecting a bad link may,
depending on the scheme you pick, be higher than that of picking a good
on.  In field trials, this has turned out to be a major source of
trouble.  Repeated attempts will simply lead to repeated bad choices.=20


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Thursday, May 04, 2006 3:01 PM
To: Mullen, John; manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

=20
Hi Dan,

The problem is that the node doesn't know which links are good and must
make intelligent guesses.  If you rebuild your table without reason to
suspect a route is bad, you will increase the risk of excluding a good
route or including a bad one.

- If you accidently include a bad route, it will be weeded out in the
next cycle or two.  The trick is to update fast enough so that the bad
routes don't have a lasting impact.

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



From manet-bounces@ietf.org Fri May 05 11:18:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fc24E-0007MP-6p; Fri, 05 May 2006 11:18:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc20m-0003jA-CG
	for manet@ietf.org; Fri, 05 May 2006 11:14:32 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc20k-0008J0-U9
	for manet@ietf.org; Fri, 05 May 2006 11:14:32 -0400
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
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Fri, 5 May 2006 09:14:33 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF25F@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvu+vPhfojYl4fQNyKDTF6aAqd+QAABwFwAAB/LNAAAImI4AAlPAEw
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Daniel,

Well, we agree.

I think that the best bet is to continually sample nodes in range and
use that to decide which nodes are, in fact, "good" neighbors.  This
definition is conditional.  When the MANET is dense, the node will want
to be picky, selecting only very good neighbors, but if the MANET is
sparse, the node might want to use dodgy neighbors, if this leads to
better overall performance and avoids partition.  In short, I think the
solution will involve some sort of cross layer design because there are
both local and global issues.

The low-pass filter is a good concept, but there are difficulties in
MANETs to be dealt with that the model does not consider.  The problem
is that a node will receive transimssions from numerous sources and
needs to track which signal came from where.  However, if the signal is
too weak to determine the address of the source, it cannot be used by
the receiver to update the estimate of servicability.  Because the only
data the receiver will get is that contained in messages strong enough
to decode, a straight low-pass and integration scheme will tend to
overestimate the SNIR, and that bias will increase as SNIR becomes
smaller.  The trick is to find a way to detect and account for the
missing transmissions.

That is the trick I'm working on.

http://web.nmsu.edu/~jomullen/MyPapers/Mullen_PE_WASUN05.pdf

:-)

John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Thursday, May 04, 2006 3:49 PM
To: Mullen, John
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Yeah, I agree, an AGC is a better analog and better solution.  Basically
low pass the table through constant sampling.=20

-----Original Message-----
From: Mullen, John [mailto:jomullen@ad.nmsu.edu]
Sent: Thursday, May 04, 2006 4:14 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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

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



From manet-bounces@ietf.org Fri May 05 12:41:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fc3MG-0006VI-P0; Fri, 05 May 2006 12:40:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc3MF-0006VD-Qg
	for manet@ietf.org; Fri, 05 May 2006 12:40:47 -0400
Received: from web25715.mail.ukl.yahoo.com ([217.146.176.243])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Fc3MA-0003OE-F2
	for manet@ietf.org; Fri, 05 May 2006 12:40:47 -0400
Received: (qmail 66209 invoked by uid 60001); 5 May 2006 16:40:41 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr;
	h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=UfHZJ6SEt771ZOIY8+8xioSihSHRSIeUSdW3LONeDhhbgk7/sf9A6BzkvZjo3/AYsCmH/A0Xe63TvW5Z32FOo2Gf7vubOBmlXcsBp7ZwWjwJu7cHiklSE7vbIooozaZyuvYDUc7luXII92Nfi91z9aKhJpu8fTD56oH3Dakqinw=
	; 
Message-ID: <20060505164041.66207.qmail@web25715.mail.ukl.yahoo.com>
Received: from [193.194.94.4] by web25715.mail.ukl.yahoo.com via HTTP;
	Fri, 05 May 2006 18:40:41 CEST
Date: Fri, 5 May 2006 18:40:41 +0200 (CEST)
From: dendene elhadi <dendene2004@yahoo.fr>
To: manet@ietf.org
In-Reply-To: <E1Fc2j5-0007aY-E3@megatron.ietf.org>
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: [manet] Re: MANET definition of a neighbor (Elhadi DENDENE)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0664886206=="
Errors-To: manet-bounces@ietf.org

--===============0664886206==
Content-Type: multipart/alternative; boundary="0-1784881727-1146847241=:66164"
Content-Transfer-Encoding: 8bit

--0-1784881727-1146847241=:66164
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit


  I have not a high experience in MANET, but, logically we say that x is neighbour of y if the relation (Hear –H-) is symmetric,
   
  x H y and y H x.
but in a distributed and wireless context, we need certain mechanisms for proving the symmetry of  H, we can use authentication using timely or  signals density constraints. 
		
---------------------------------
 Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Cliquez ici.
--0-1784881727-1146847241=:66164
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<BR>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB"><FONT size=3><FONT face="Times New Roman">I have not a high experience in MANET, but, logically we say that x is neighbour of y if the relation (Hear –H-) is symmetric,<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></FONT></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-GB style="mso-ansi-language: EN-GB"><FONT size=3><FONT face="Times New Roman">x H y and y H x.<o:p></o:p></FONT></FONT></SPAN></div><SPAN lang=EN-GB style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-ansi-language: EN-GB; mso-fareast-font-family: 'Times New Roman'; mso-fareast-language: FR; mso-bidi-language: AR-SA">but in a distributed and wireless
 context, we need certain mechanisms for proving the symmetry of<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>H, we can use authentication using timely or<SPAN style="mso-spacerun: yes">&nbsp; </SPAN>signals density constraints. </SPAN><p>
		<hr size="1" /> 
<b>Faites de Yahoo! votre page d'accueil sur le web</b> pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. <a href="http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yahoo.com/set" target=_blank>Cliquez ici</a>.
--0-1784881727-1146847241=:66164--


--===============0664886206==
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

--===============0664886206==--




From manet-bounces@ietf.org Fri May 05 12:49:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fc3Ux-0002Bx-JM; Fri, 05 May 2006 12:49:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc3Uv-0002Bs-Li
	for manet@ietf.org; Fri, 05 May 2006 12:49:45 -0400
Received: from p02m143.mxlogic.net ([66.179.26.143])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc3Ut-0003h4-Ad
	for manet@ietf.org; Fri, 05 May 2006 12:49:45 -0400
Received: from unknown [208.251.151.99]
	by p02m143.mxlogic.net (mxl_mta-2.14.0-12)
	with SMTP id 7228b544.1507085232.4911.p02m143.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Fri, 05 May 2006 10:49:43 -0600 (MDT)
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: [manet] Re: MANET definition of a neighbor
Date: Fri, 5 May 2006 11:48:07 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F19@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvu+vPhfojYl4fQNyKDTF6aAqd+QAABwFwAAB/LNAAAImI4AAlPAEwAAEFvpAAAp3tkA==
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: <manet@ietf.org>
X-Spam: [F=0.1944734586; S=0.194(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.251.151.99]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

"The low-pass filter is a good concept, but there are difficulties in
MANETs to be dealt with that the model does not consider.  The problem
is that a node will receive transmissions from numerous sources and
needs to track which signal came from where.  However, if the signal is
too weak to determine the address of the source, it cannot be used by
the receiver to update the estimate of serviceability."

I think we are saying the same thing just in different words.  In case
we are not, here's my point.

Obviously you'd want to pick a algorithm that converges on the correct
solution, and using say a 10 tap FIR filter should smooth out the random
errors.  The tap weights should be algorithmic, as opposed to basing
them simply on signal strength.  Because of the problems you mentioned,
SINR isn't a good enough indicator by itself.  The MANET protocol for
example could use valid CRCs, parity checks, ping times, subnet
affiliation, signal strength, and/or whatever you as filtering criteria.
Place a weight of importance on each selection criteria  then add them
together and then store its combined weight with the route in a table.
When an entry gets too light, toss it.  Everyone's implementation can
and should be different based on the MANET deployment environment, but
the basic premise of CONSTANT sampling, and filtering out bad links
remains the same.=20

"...The chances of selecting a bad link may, depending on the scheme you
pick, be higher than that of picking a good on.  In field trials, this
has turned out to be a major source of trouble.  Repeated attempts will
simply lead to repeated bad choices."

Constant sampling in itself isn't a problem.  If the sampling procedure
doesn't converge on an optimal list and constantly picks "bad" nodes
then the selection and filtering criteria is too blame and not the mere
act of sampling.

"This definition is conditional.  When the MANET is dense, the node will
want to be picky, selecting only very good neighbors, but if the MANET
is sparse..."

The FIR will be picky by nature without adjusting the algorithm.
Stronger nodes, as defined by the weighted selection criteria, will
swamp weaker nodes in a dense MANET; conversely weaker nodes will be
brought out in a quieter MANET.


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



From manet-bounces@ietf.org Fri May 05 13:09:54 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fc3oF-0002yI-Mo; Fri, 05 May 2006 13:09:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc3oD-0002xP-Qw
	for manet@ietf.org; Fri, 05 May 2006 13:09:41 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc3oD-0004Ky-G2
	for manet@ietf.org; Fri, 05 May 2006 13:09:41 -0400
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
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Fri, 5 May 2006 11:09:38 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF2FB@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvu+vPhfojYl4fQNyKDTF6aAqd+QAABwFwAAB/LNAAAImI4AAlPAEwAAEFvpAAAp3tkAAAIW+Q
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>,
	<manet@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Daniel,

My replies are in line with --'s separating topics=20


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Friday, May 05, 2006 10:48 AM
To: manet@ietf.org
Subject: [manet] Re: MANET definition of a neighbor

"The low-pass filter is a good concept, but there are difficulties in
MANETs to be dealt with that the model does not consider.  The problem
is that a node will receive transmissions from numerous sources and
needs to track which signal came from where.  However, if the signal is
too weak to determine the address of the source, it cannot be used by
the receiver to update the estimate of serviceability."

I think we are saying the same thing just in different words.  In case
we are not, here's my point.

Obviously you'd want to pick a algorithm that converges on the correct
solution, and using say a 10 tap FIR filter should smooth out the random
errors.  The tap weights should be algorithmic, as opposed to basing
them simply on signal strength.  Because of the problems you mentioned,
SINR isn't a good enough indicator by itself.  The MANET protocol for
example could use valid CRCs, parity checks, ping times, subnet
affiliation, signal strength, and/or whatever you as filtering criteria.
Place a weight of importance on each selection criteria  then add them
together and then store its combined weight with the route in a table.
When an entry gets too light, toss it.  Everyone's implementation can
and should be different based on the MANET deployment environment, but
the basic premise of CONSTANT sampling, and filtering out bad links
remains the same.=20

Reply:

Certainly, we should use all we can, but we need to be aware that unless
we conpensate in some way for missing values, our figure of merit will
depend solely on signals strong enough to have, at least, the TX ID
decoded.  What happens is that the response curve based on available
information becomes very flat over a wide range.  A link could become
quite marginal, but the receiving node might not know it because the
transmitter's worst failures are not visible to it.  People have
compensated for this by using a fudge factor, but the fudge only works
in a limited context.  This implies a higher level of sophistication in
the filter techniques than I've seen so far.

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


"...The chances of selecting a bad link may, depending on the scheme you
pick, be higher than that of picking a good on.  In field trials, this
has turned out to be a major source of trouble.  Repeated attempts will
simply lead to repeated bad choices."

Constant sampling in itself isn't a problem.  If the sampling procedure
doesn't converge on an optimal list and constantly picks "bad" nodes
then the selection and filtering criteria is too blame and not the mere
act of sampling.

Reply:

Not really.  Due to effects like multipath fading, the chance of
selecting a poor link are fairly high.  Better filtering can help, but
the deck is stacked against you.  Setting up a null hypothesis and
acting when the evidence is sufficient is a good way to reduce false
positives, which in turn, will reduce the risk of selecting a poor link.

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

"This definition is conditional.  When the MANET is dense, the node will
want to be picky, selecting only very good neighbors, but if the MANET
is sparse..."

The FIR will be picky by nature without adjusting the algorithm.
Stronger nodes, as defined by the weighted selection criteria, will
swamp weaker nodes in a dense MANET; conversely weaker nodes will be
brought out in a quieter MANET.

Reply:

This is not automatic.  For example, a node could have a high density to
the West and a low density to the East.  If the nodes needs to send a
packet East and there is a good path using the West side nodes, the
optimal solution may be to use the longer, but more reliable, route.
However, if the only viable path is to use the Eastern nodes, the
alternative to using that poor route is partition.  That is why I feel a
cross-layer approach will win out in the end.  The physical and link
layers will have information that is normally hidden from the routing
layer that will be needed to evaluate potential links, but the MANET
protocol will have the job of finding an optimal network solution.

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



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



From manet-bounces@ietf.org Fri May 05 13:45:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fc4Mr-0006kJ-A3; Fri, 05 May 2006 13:45:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc4Mq-0006kB-12
	for manet@ietf.org; Fri, 05 May 2006 13:45:28 -0400
Received: from smtp-mclean-x.mitre.org ([192.80.55.71]
	helo=smtp-mclean.mitre.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc4Mp-0005xP-MR
	for manet@ietf.org; Fri, 05 May 2006 13:45:28 -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
	k45HjHjE032433 for <manet@ietf.org>; Fri, 5 May 2006 13:45:17 -0400
Received: from smtp-mclean.mitre.org (localhost.localdomain [127.0.0.1])
	by smtp-mclean.mitre.org (Postfix) with ESMTP id 3B5FA1BDA2
	for <manet@ietf.org>; Fri,  5 May 2006 13:45:17 -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
	k45Hj747032328; Fri, 5 May 2006 13:45:07 -0400
Received: from [129.83.175.29] ([129.83.175.29]) by imcfe2.MITRE.ORG with
	Microsoft SMTPSVC(6.0.3790.211); Fri, 5 May 2006 13:45:06 -0400
Message-ID: <445B8FB3.2040406@mitre.org>
Date: Fri, 05 May 2006 13:47:31 -0400
From: Kenneth Brayer <kb@mitre.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dendene elhadi <dendene2004@yahoo.fr>
Subject: Re: [manet] Re: MANET definition of a neighbor (Elhadi DENDENE)
References: <20060505164041.66207.qmail@web25715.mail.ukl.yahoo.com>
In-Reply-To: <20060505164041.66207.qmail@web25715.mail.ukl.yahoo.com>
X-OriginalArrivalTime: 05 May 2006 17:45:06.0532 (UTC)
	FILETIME=[A5652A40:01C6706B]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1751052775=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.
--===============1751052775==
Content-Type: multipart/alternative;
	boundary="------------050804010202000407050901"

This is a multi-part message in MIME format.
--------------050804010202000407050901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by smtp-mclean.mitre.org
	id k45HjHjE032433

One of the problems in radio comm is symmetry does not always apply,=20
especially on fading channels. In many frequency bands it is very common=20
that you can hear me but I cannot hear you.
Ken


dendene elhadi wrote:

>
> I have not a high experience in MANET, but, logically we say that x is=20
> neighbour of y if the relation (Hear -H-) is symmetric,
> =20
> x H y and y H x.
> but in a distributed and wireless context, we need certain mechanisms=20
> for proving the symmetry of  H, we can use authentication using timely=20
> or  signals density constraints.
>
> -----------------------------------------------------------------------=
-
> Faites de Yahoo! votre page d'accueil sur le web pour retrouver=20
> directement vos services pr=E9f=E9r=E9s : v=E9rifiez vos nouveaux mails=
,=20
> lancez vos recherches et suivez l'actualit=E9 en temps r=E9el. Cliquez =
ici=20
> <http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yahoo.com=
/set>.=20
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet
> =20
>

--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841


--------------050804010202000407050901
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
One of the problems in radio comm is symmetry does not always apply,
especially on fading channels. In many frequency bands it is very
common that you can hear me but I cannot hear you.<br>
Ken<br>
<br>
<br>
dendene elhadi wrote:<br>
<blockquote
 cite="mid20060505164041.66207.qmail@web25715.mail.ukl.yahoo.com"
 type="cite"><br>
  <div class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
 lang="EN-GB"><font size="3"><font face="Times New Roman">I have not a
high experience in MANET, but, logically we say that x is neighbour of
y if the relation (Hear &#8211;H-) is symmetric,<o:p></o:p></font></font></span></div>
  <div class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
 lang="EN-GB"><o:p><font face="Times New Roman" size="3">&nbsp;</font></o:p></span></div>
  <div class="MsoNormal" style="margin: 0cm 0cm 0pt;"><span style=""
 lang="EN-GB"><font size="3"><font face="Times New Roman">x H y and y H
x.<o:p></o:p></font></font></span></div>
  <span style="font-size: 12pt; font-family: 'Times New Roman';"
 lang="EN-GB">but in a distributed and wireless context, we need
certain mechanisms for proving the symmetry of<span style="">&nbsp; </span>H,
we can use authentication using timely or<span style="">&nbsp; </span>signals
density constraints. </span>
  <p> </p>
  <hr size="1"> <b>Faites de Yahoo! votre page d'accueil sur le web</b>
pour retrouver directement vos services pr&eacute;f&eacute;r&eacute;s : v&eacute;rifiez vos
nouveaux mails, lancez vos recherches et suivez l'actualit&eacute; en temps
r&eacute;el. <a
 href="http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yahoo.com/set"
 target="_blank">Cliquez ici</a>.
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
manet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:manet@ietf.org">manet@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/manet">https://www1.ietf.org/mailman/listinfo/manet</a>
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: <a class="moz-txt-link-abbreviated" href="mailto:kb@mitre.org">kb@mitre.org</a>
tele: 781-271-5254
fax: 781-271-2841
</pre>
</body>
</html>

--------------050804010202000407050901--


--===============1751052775==
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

--===============1751052775==--




From manet-bounces@ietf.org Fri May 05 16:07:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fc6a1-0001RB-NQ; Fri, 05 May 2006 16:07:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc6a0-0001Qo-84
	for manet@ietf.org; Fri, 05 May 2006 16:07:12 -0400
Received: from ecs.syr.edu ([128.230.208.14] helo=erebus.ecs.syr.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc6Zy-0005hX-Rs
	for manet@ietf.org; Fri, 05 May 2006 16:07:12 -0400
Received: (from nobody@localhost)
	by erebus.ecs.syr.edu (8.11.7p2+Sun/8.10.2) id k45K7AC25780;
	Fri, 5 May 2006 16:07:10 -0400 (EDT)
To: manet@ietf.org
Subject: my two cents Re: [manet] Re: MANET definition of a neighbor
Message-ID: <1146859630.445bb06e30b65@webmail.ecs.syr.edu>
Date: Fri, 05 May 2006 16:07:10 -0400 (EDT)
From: dazhi chen <dchen02@ecs.syr.edu>
References: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F0B@EXV1.corp.adtran.com>
In-Reply-To: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F0B@EXV1.corp.adtran.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.8
X-Originating-IP: 128.230.196.151
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 43317e64100dd4d87214c51822b582d1
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


Just my two cents about the defintion of neighbors in MANET.

The most important thing is that at which protocol layer you will define
a neighbor for your protocol or algorithm. For example:

1. Physical neighbor

It depends on geographic locations of nodes.

2. Communication neigbhor
It can be defined as any node within the 
radio communication range of the sender or 
any receiver where the signal sent by the sender 
can be reliably recevied. Further, you can distingush
outing neighbors with incoming neighbors due to unidirectional links.

3. Routing neighbor
It can be defined as one node, from which group of nodes, can be selected as a 
next-hop node for a sender.

4. Application neighbor
Think about P2P applications. 

Note that nodes in MANET depend on wireless channel to communicate with each 
other and the status of a wireless channel ususally varies at the scale of a  
few milliseconds. However, such neigbhoring information is unstable 
and we do not need to update it at this scale at each node (either too costly 
or no demand). A simple MAC retransmission at the MAC layer can make this 
variability transparent to the upper protocol layers.

Instead, at the routing layer, coarse-grained routing 
maintains stable routes in the long time (e.g. tens of seconds or more). It 
may not be possible at this time scale due to node mobility.

Some recent work on wireless routing is to maintain some long-term (you can 
define how long for your own protocol) stable Routing neighbors while using 
short-term communication neigbhor in an opportunistic manner to achieve the 
better performance such as a high throughput.

These are just some thinkings in my mind. Hope this helps.

Best,

dazhi

---------------------------------------------------------
Dazhi Chen
Department of Electrical Engineering and Computer Science
371 Link Hall, Syracuse University, Syracuse NY USA 13244
Tel:+(1)-(315)428-8208
Email: billchendz@ieee.org  http://web.syr.edu/~dchen02/
---------------------------------------------------------

Quoting DANIEL BYRNE <daniel.byrne@adtran.com>:

> Just rebuild the routing tables every 3 seconds or so.  This eliminates
> guessing, measuring signal strength, watching traffic etc.  You could
> even make invalidating the tables user configurable.  If the user knows
> he will be relatively stationary, ie. in Barnes and Noble, they could
> set the protocol to the stationary model.  If the user is travelling
> down the highway at 80 MPH or on a subway, then choose the roaming
> model
> which invalidates and updates the routes at a faster pace.
> 
> -----Original Message-----
> From: Kenneth Brayer [mailto:kb@mitre.org] 
> Sent: Thursday, May 04, 2006 2:31 PM
> To: Fred Baker
> Cc: manet@ietf.org
> Subject: Re: [manet] Re: MANET definition of a neighbor
> 
> Fred
> I agree with the following:
> "I have argued along the lines, though, that the most important metric
> for a path in a manet network is not its speed or degree of  congestion
> (although those are very interesting second-order  metrics), but the
> probability that it will be useful at the time I  want to use it."
> 
> When you get a message to deliver you need to know what to do. I am
> interested in delivering messages rapidly.
> 
> as far as
> "So for example if one has a pair of UAVs in orbit over a domain, one
> should be able to watch the characteristics of the radio signal and 
> see
> that one's signal is slowly degrading while the other's is slowly
> improving. At some point, one wants to bring up the approaching UAV,
> shift routes to it, and then shut down the now-unused departing UAV 
> for
> a smooth switchover, rather than saying "ohmygoshwhatdoidonow"  when
> the
> UAV one is using suddenly goes out of sight."
> 
> For all of the reasons that John stated this is very hard. Just because
> the signal is degrading doesn't mean it will continue to degrade. It is
> even harder to determine when a signal will improve. I made Fellow of
> the IEEE in Fading Channels, like HF Radio, and signal quality
> prediction and its direction is very difficult. Some real world MANETS
> deal with this by trying to eliminate the problem through coding. THey
> give up usable channel capacity to reduce the error rate and increase
> channel reliability.
> 
> Ken
> 
> Fred Baker wrote:
> 
> > On May 4, 2006, at 11:47 AM, Kenneth Brayer wrote:
> >
> >> So the real question is who are your neighbors as a function of 
> time
> 
> >> in a MANET. A MANET protocol should try to determine this so  it can
> 
> >> deliver messages when they are presented to the network.
> >
> >
> > It is "at a point in time" even in a wired and highly reliable 
> > network. Things go bump in the night in the most stable networks.
> >
> > I have argued along the lines, though, that the most important metric
> 
> > for a path in a manet network is not its speed or degree of
> congestion
> 
> > (although those are very interesting second-order metrics), but the 
> > probability that it will be useful at the time I want to use it.
> >
> > In many scenarios, mobility is well described as "brownian motion",
> in
> 
> > which things moving approximately together but bump in and out of 
> > sight of each other, or using the word "zoom". If one thinks, for 
> > example, of cars on a highway, I might try to use cars traveling in 
> > the opposite direction as links ("zoom"), cars on orthogonal roads 
> > ("zoom" to the point of "blip" in many cases), routers on light poles
> 
> > ("zoom" at half the speed), routers in other cars I happen to be 
> > traveling with for a few exits (relatively stable during the
> interval,
> 
> > but blipping in and out around corners/tunnels/etc), and the 
> > occasional router on a hill (which it will be able to see for a long 
> > time as it passes the hill). Which is the tres cool route? The one 
> > that has the highest probability of working when the route is 
> > needed...
> >
> > So for example if one has a pair of UAVs in orbit over a domain, one 
> > should be able to watch the characteristics of the radio signal and 
> > see that one's signal is slowly degrading while the other's is slowly
> 
> > improving. At some point, one wants to bring up the approaching UAV, 
> > shift routes to it, and then shut down the now-unused departing UAV 
> > for a smooth switchover, rather than saying "ohmygoshwhatdoidonow"
> > when the UAV one is using suddenly goes out of sight. The sudden mass
> 
> > change model is a leftover from wired concepts...
> 
> 
> --
> Kenneth Brayer
> Fellow of the IEEE
> M/S M370
> The MITRE Corporation
> 202 Burlington Road
> Bedford, MA 01730
> 
> e-mail: kb@mitre.org
> tele: 781-271-5254
> fax: 781-271-2841
> 
> 
> _______________________________________________
> 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
> 



---------------------------------------------------------
Dazhi Chen
Department of Electrical Engineering and Computer Science
371 Link Hall, Syracuse University, Syracuse NY USA 13244
Tel:+(1)-(315)428-8208
Email: billchendz@ieee.org  http://web.syr.edu/~dchen02/
---------------------------------------------------------

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



From manet-bounces@ietf.org Fri May 05 16:53:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fc7IW-0005D1-1l; Fri, 05 May 2006 16:53:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fc7IU-0005Cv-As
	for manet@ietf.org; Fri, 05 May 2006 16:53:10 -0400
Received: from ext-nj2ut-11.online-age.net ([64.14.54.241])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fc7IS-0001En-3E
	for manet@ietf.org; Fri, 05 May 2006 16:53:10 -0400
Received: from int-nj2ut-3.online-age.net (int-nj2ut-3.online-age.net
	[3.159.237.72])
	by ext-nj2ut-11.online-age.net (8.13.6/8.13.6/20051114-SVVS-TLS-DNSBL)
	with ESMTP id k45Kr7Zd009469
	for <manet@ietf.org>; Fri, 5 May 2006 16:53:07 -0400
Received: from cinmlef10.e2k.ad.ge.com (localhost.localdomain [127.0.0.1])
	by int-nj2ut-3.online-age.net (8.11.6/8.11.6/20050510-SVVS) with ESMTP
	id k45Kr7h00882 for <manet@ietf.org>; Fri, 5 May 2006 16:53:07 -0400
Received: from SCHMLVEM01.e2k.ad.ge.com ([3.159.168.31]) by
	cinmlef10.e2k.ad.ge.com with Microsoft SMTPSVC(6.0.3790.2499); 
	Fri, 5 May 2006 16:53:06 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [manet] Re: MANET definition of a neighbor
Date: Fri, 5 May 2006 16:53:05 -0400
Message-ID: <FA26BEF1EA775E4584FB34B91E14A1C40FCADAC8@SCHMLVEM01.e2k.ad.ge.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: my two cents Re: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZwf6DiBB0ZEbvzRoK/Q+M5CGcqHwAAaJog
From: "Bush, Stephen F \(GE, Research\)" <bushsf@research.ge.com>
To: <manet@ietf.org>
X-OriginalArrivalTime: 05 May 2006 20:53:06.0222 (UTC)
	FILETIME=[E89D44E0:01C67085]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


The reason I mentioned DTN earlier is because:

1) Predictive connection/mobility algorithms are increasingly being =
employed

2) The concept of "unstable" links are taken to an extreme-- no end to =
end
path is required to exist at any single point time for information to be
routed. E2E connections may be dispersed in time.

Stephen F Bush (http://www.research.ge.com/~bushsf)

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



From manet-bounces@ietf.org Sat May 06 17:54:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FcUjB-0001iz-SM; Sat, 06 May 2006 17:54:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FcUjA-0001iu-28
	for manet@ietf.org; Sat, 06 May 2006 17:54:16 -0400
Received: from web26601.mail.ukl.yahoo.com ([217.146.176.51])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FcUj6-0003tt-9b
	for manet@ietf.org; Sat, 06 May 2006 17:54:15 -0400
Received: (qmail 23270 invoked by uid 60001); 6 May 2006 21:54:11 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=zOD1doLSF240lGgTv0mamlIfnzf/NF+2FTyh+PTFv3ENobumzAcUhJCuQgvN5hgRxYDNc7Bo6pD64GIbwY6kGEgwi9Ly57+h4Tdclm/NQnOTNLLB2WU9q+QRxearJpxaDXz0mlsGz2FH5KYoP3jexihJ6Mqn98eR0Fo3wGkIpaM=
	; 
Message-ID: <20060506215411.23268.qmail@web26601.mail.ukl.yahoo.com>
Received: from [196.206.64.34] by web26601.mail.ukl.yahoo.com via HTTP;
	Sat, 06 May 2006 23:54:10 CEST
Date: Sat, 6 May 2006 23:54:10 +0200 (CEST)
From: www triste <unhapy1983@yahoo.fr>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Subject: [manet] the distance between nodes in adhoc network using olsr
	routing protocole
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1324658064=="
Errors-To: manet-bounces@ietf.org

--===============1324658064==
Content-Type: multipart/alternative; boundary="0-922791236-1146952450=:20248"
Content-Transfer-Encoding: 8bit

--0-922791236-1146952450=:20248
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello everybody
  i wish you will help me ,its very urgent
  thanks in advance.
   
  i want to calculate the distance between nodes ;by using the delay of paquets HELLO;i use the olsr routing protocole
   
  i wana to know if it true:
   
                              delay= time of reception to the HELLO- time of sending the HELLO
     
                    distance between nodes=(3,6 *10^8) *delay     
   
   
  because i want to use the distance betwwen nodes;i have two ideas:
                            1)use the distance between nodes i have already give the relation with delay 
         
                               2)use the GPS positioning  system,for giving the x,y,z for the nodes
   
  thanks,i am waiting for your ansswer
   
  faithfully yours;and best regards

		
---------------------------------
 Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Cliquez ici.
--0-922791236-1146952450=:20248
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>Hello everybody</div>  <div>i wish you will help me ,its very urgent</div>  <div>thanks in advance.</div>  <div>&nbsp;</div>  <div>i want to calculate the distance between nodes ;by using the delay of paquets HELLO;i use the olsr routing protocole</div>  <div>&nbsp;</div>  <div>i wana to know if it true:</div>  <div>&nbsp;</div>  <div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; delay= time of reception to the HELLO- time of sending the HELLO</div>  <div>&nbsp;&nbsp; </div>  <div><STRONG>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; distance between nodes=(3,6 *10^8) *delay&nbsp;&nbsp;&nbsp;&nbsp; </STRONG></div>  <div>&nbsp;</div>  <div>&nbsp;</div>  <div>because i want to use the distance betwwen nodes;i have two ideas:</div> 
 <div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1)use the distance between nodes i have already give the relation with delay </div>  <div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </div>  <div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2)use the GPS positioning&nbsp; system,for giving the x,y,z for the nodes</div>  <div>&nbsp;</div>  <div>thanks,i am waiting for your ansswer</div>  <div>&nbsp;</div>  <div>faithfully yours;and best regards</div><p>
		<hr size="1" /> 
<b>Faites de Yahoo! votre page d'accueil sur le web</b> pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. <a href="http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yahoo.com/set" target=_blank>Cliquez ici</a>.
--0-922791236-1146952450=:20248--


--===============1324658064==
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

--===============1324658064==--




From manet-bounces@ietf.org Sat May 06 18:09:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FcUxM-0006pi-Hn; Sat, 06 May 2006 18:08:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FcUxK-0006pd-SR
	for manet@ietf.org; Sat, 06 May 2006 18:08:54 -0400
Received: from web26603.mail.ukl.yahoo.com ([217.146.176.53])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FcUxI-0004md-FV
	for manet@ietf.org; Sat, 06 May 2006 18:08:54 -0400
Received: (qmail 9083 invoked by uid 60001); 6 May 2006 22:08:51 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr;
	h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=FWzF7skoK2dZ2yX5XkMPzHTAFtx8yiweDUk8X7dwNWIAmM2J2hBWjZMEV+REjqnn/omuYXGgAYJSCoSFVCCsECL+YFYyynWpNOFdFCX7FPGzMGF+Ed0h0hqytsSlBapYY+rS67gqifHQWRNM8CZQrGH1r5JdrVE+coK7fNTuiqo=
	; 
Message-ID: <20060506220851.9081.qmail@web26603.mail.ukl.yahoo.com>
Received: from [196.206.64.34] by web26603.mail.ukl.yahoo.com via HTTP;
	Sun, 07 May 2006 00:08:51 CEST
Date: Sun, 7 May 2006 00:08:51 +0200 (CEST)
From: www triste <unhapy1983@yahoo.fr>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [manet] the speed of paquets
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0262584937=="
Errors-To: manet-bounces@ietf.org

--===============0262584937==
Content-Type: multipart/alternative; boundary="0-144533725-1146953331=:96476"
Content-Transfer-Encoding: 8bit

--0-144533725-1146953331=:96476
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello again
  i want to ask an other question,what is the speed of paquets sent,in adhoc network?it is 3,6 * 10^8  
   
  Thanks

		
---------------------------------
 Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Cliquez ici.
--0-144533725-1146953331=:96476
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>Hello again</div>  <div>i want to ask an other question,what is the speed of paquets sent,in adhoc network?it is 3,6 * 10^8&nbsp; </div>  <div>&nbsp;</div>  <div>Thanks</div><p>
		<hr size="1" /> 
<b>Faites de Yahoo! votre page d'accueil sur le web</b> pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. <a href="http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yahoo.com/set" target=_blank>Cliquez ici</a>.
--0-144533725-1146953331=:96476--


--===============0262584937==
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

--===============0262584937==--




From manet-bounces@ietf.org Sun May 07 14:15:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fcniv-0003DM-Jr; Sun, 07 May 2006 14:11:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fcniu-0003DH-IZ
	for manet@ietf.org; Sun, 07 May 2006 14:11:16 -0400
Received: from p02m143.mxlogic.net ([66.179.26.143])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fcnis-0000R7-Na
	for manet@ietf.org; Sun, 07 May 2006 14:11:16 -0400
Received: from unknown [208.251.151.99] (EHLO EXV1.corp.adtran.com)
	by p02m143.mxlogic.net (mxl_mta-2.14.0-12)
	with ESMTP id 2483e544.383560624.190953.p02m143.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Sun, 07 May 2006 12:11:14 -0600 (MDT)
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: my two cents Re: [manet] Re: MANET definition of a neighbor
Date: Sun, 7 May 2006 13:11:06 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F1A@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: my two cents Re: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZwf5IOpTsr0TqlSh6XoakGm97JlgBgcQ8Q
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: "dazhi chen" <dchen02@ecs.syr.edu>,
	<manet@ietf.org>
X-Spam: [F=0.0100000000; S=0.010(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.251.151.99]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Good points.  I agree.  Neighbor definitions should be qualified by the
adjective "layer".  So we should be talking about Layer Neighbors.

-----Original Message-----
From: dazhi chen [mailto:dchen02@ecs.syr.edu]=20
Sent: Friday, May 05, 2006 3:07 PM
To: manet@ietf.org
Subject: my two cents Re: [manet] Re: MANET definition of a neighbor


Just my two cents about the defintion of neighbors in MANET.

The most important thing is that at which protocol layer you will define
a neighbor for your protocol or algorithm. For example:

1. Physical neighbor

It depends on geographic locations of nodes.

2. Communication neigbhor
It can be defined as any node within the radio communication range of
the sender or any receiver where the signal sent by the sender can be
reliably recevied. Further, you can distingush outing neighbors with
incoming neighbors due to unidirectional links.

3. Routing neighbor
It can be defined as one node, from which group of nodes, can be
selected as a next-hop node for a sender.

4. Application neighbor
Think about P2P applications.=20

Note that nodes in MANET depend on wireless channel to communicate with
each other and the status of a wireless channel ususally varies at the
scale of a few milliseconds. However, such neigbhoring information is
unstable and we do not need to update it at this scale at each node
(either too costly or no demand). A simple MAC retransmission at the MAC
layer can make this variability transparent to the upper protocol
layers.

Instead, at the routing layer, coarse-grained routing maintains stable
routes in the long time (e.g. tens of seconds or more). It may not be
possible at this time scale due to node mobility.

Some recent work on wireless routing is to maintain some long-term (you
can define how long for your own protocol) stable Routing neighbors
while using short-term communication neigbhor in an opportunistic manner
to achieve the better performance such as a high throughput.

These are just some thinkings in my mind. Hope this helps.

Best,

dazhi

---------------------------------------------------------
Dazhi Chen
Department of Electrical Engineering and Computer Science
371 Link Hall, Syracuse University, Syracuse NY USA 13244
Tel:+(1)-(315)428-8208
Email: billchendz@ieee.org  http://web.syr.edu/~dchen02/
---------------------------------------------------------

Quoting DANIEL BYRNE <daniel.byrne@adtran.com>:

> Just rebuild the routing tables every 3 seconds or so.  This=20
> eliminates guessing, measuring signal strength, watching traffic etc.

> You could even make invalidating the tables user configurable.  If the

> user knows he will be relatively stationary, ie. in Barnes and Noble,=20
> they could set the protocol to the stationary model.  If the user is=20
> travelling down the highway at 80 MPH or on a subway, then choose the=20
> roaming model which invalidates and updates the routes at a faster=20
> pace.
>=20
> -----Original Message-----
> From: Kenneth Brayer [mailto:kb@mitre.org]
> Sent: Thursday, May 04, 2006 2:31 PM
> To: Fred Baker
> Cc: manet@ietf.org
> Subject: Re: [manet] Re: MANET definition of a neighbor
>=20
> Fred
> I agree with the following:
> "I have argued along the lines, though, that the most important metric

> for a path in a manet network is not its speed or degree of =20
> congestion (although those are very interesting second-order =20
> metrics), but the probability that it will be useful at the time I
want to use it."
>=20
> When you get a message to deliver you need to know what to do. I am=20
> interested in delivering messages rapidly.
>=20
> as far as
> "So for example if one has a pair of UAVs in orbit over a domain, one=20
> should be able to watch the characteristics of the radio signal and=20
> see that one's signal is slowly degrading while the other's is slowly=20
> improving. At some point, one wants to bring up the approaching UAV,=20
> shift routes to it, and then shut down the now-unused departing UAV=20
> for a smooth switchover, rather than saying "ohmygoshwhatdoidonow" =20
> when the UAV one is using suddenly goes out of sight."
>=20
> For all of the reasons that John stated this is very hard. Just=20
> because the signal is degrading doesn't mean it will continue to=20
> degrade. It is even harder to determine when a signal will improve. I=20
> made Fellow of the IEEE in Fading Channels, like HF Radio, and signal=20
> quality prediction and its direction is very difficult. Some real=20
> world MANETS deal with this by trying to eliminate the problem through

> coding. THey give up usable channel capacity to reduce the error rate=20
> and increase channel reliability.
>=20
> Ken
>=20
> Fred Baker wrote:
>=20
> > On May 4, 2006, at 11:47 AM, Kenneth Brayer wrote:
> >
> >> So the real question is who are your neighbors as a function of
> time
>=20
> >> in a MANET. A MANET protocol should try to determine this so  it=20
> >> can
>=20
> >> deliver messages when they are presented to the network.
> >
> >
> > It is "at a point in time" even in a wired and highly reliable=20
> > network. Things go bump in the night in the most stable networks.
> >
> > I have argued along the lines, though, that the most important=20
> > metric
>=20
> > for a path in a manet network is not its speed or degree of
> congestion
>=20
> > (although those are very interesting second-order metrics), but the=20
> > probability that it will be useful at the time I want to use it.
> >
> > In many scenarios, mobility is well described as "brownian motion",
> in
>=20
> > which things moving approximately together but bump in and out of=20
> > sight of each other, or using the word "zoom". If one thinks, for=20
> > example, of cars on a highway, I might try to use cars traveling in=20
> > the opposite direction as links ("zoom"), cars on orthogonal roads=20
> > ("zoom" to the point of "blip" in many cases), routers on light=20
> > poles
>=20
> > ("zoom" at half the speed), routers in other cars I happen to be=20
> > traveling with for a few exits (relatively stable during the
> interval,
>=20
> > but blipping in and out around corners/tunnels/etc), and the=20
> > occasional router on a hill (which it will be able to see for a long

> > time as it passes the hill). Which is the tres cool route? The one=20
> > that has the highest probability of working when the route is=20
> > needed...
> >
> > So for example if one has a pair of UAVs in orbit over a domain, one

> > should be able to watch the characteristics of the radio signal and=20
> > see that one's signal is slowly degrading while the other's is=20
> > slowly
>=20
> > improving. At some point, one wants to bring up the approaching UAV,

> > shift routes to it, and then shut down the now-unused departing UAV=20
> > for a smooth switchover, rather than saying "ohmygoshwhatdoidonow"
> > when the UAV one is using suddenly goes out of sight. The sudden=20
> > mass
>=20
> > change model is a leftover from wired concepts...
>=20
>=20
> --
> Kenneth Brayer
> Fellow of the IEEE
> M/S M370
> The MITRE Corporation
> 202 Burlington Road
> Bedford, MA 01730
>=20
> e-mail: kb@mitre.org
> tele: 781-271-5254
> fax: 781-271-2841
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>=20



---------------------------------------------------------
Dazhi Chen
Department of Electrical Engineering and Computer Science
371 Link Hall, Syracuse University, Syracuse NY USA 13244
Tel:+(1)-(315)428-8208
Email: billchendz@ieee.org  http://web.syr.edu/~dchen02/
---------------------------------------------------------

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

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



From manet-bounces@ietf.org Sun May 07 14:18:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FcnpE-0007fk-Dd; Sun, 07 May 2006 14:17:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FcnpC-0007e1-V9
	for manet@ietf.org; Sun, 07 May 2006 14:17:46 -0400
Received: from p02m143.mxlogic.net ([66.179.26.143])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FcnpB-0000fm-Ky
	for manet@ietf.org; Sun, 07 May 2006 14:17:46 -0400
Received: from unknown [208.251.151.99] (EHLO EXV1.corp.adtran.com)
	by p02m143.mxlogic.net (mxl_mta-2.14.0-12)
	with ESMTP id 9c93e544.150444976.192650.p02m143.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Sun, 07 May 2006 12:17:45 -0600 (MDT)
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] Re: MANET definition of a neighbor
Date: Sun, 7 May 2006 13:17:44 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F1B@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvu+vPhfojYl4fQNyKDTF6aAqd+QAABwFwAAB/LNAAAImI4AAlPAEwAAEFvpAAAp3tkAAAIW+QAGdtmkA=
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: "Mullen, John" <jomullen@ad.nmsu.edu>,
	<manet@ietf.org>
X-Spam: [F=0.0259196632; S=0.025(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.251.151.99]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

"...That is why I feel a cross-layer approach will win out in the end.
The physical and link layers will have information that is normally
hidden from the routing layer that will be needed to evaluate potential
links, but the MANET protocol will have the job of finding an optimal
network solution."

True, the routing protocol could use information attained by lower
layers.  A mechanism to pass information up the stack is needed, or the
protocol needs to be multi-layer aware. However, the later causes
problems when there are changes in technologies.  Maybe a new stack
architecture is needed for MANETS where protocols can still partition
layer specific items yet share cross applicable information.

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



From manet-bounces@ietf.org Sun May 07 14:34:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fco52-00079a-Ic; Sun, 07 May 2006 14:34:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fco50-00079V-VQ
	for manet@ietf.org; Sun, 07 May 2006 14:34:06 -0400
Received: from sccrmhc11.comcast.net ([63.240.77.81])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fco50-0001ms-O4
	for manet@ietf.org; Sun, 07 May 2006 14:34:06 -0400
Received: from [192.168.1.10]
	(c-67-162-153-173.hsd1.co.comcast.net[67.162.153.173])
	by comcast.net (sccrmhc11) with ESMTP
	id <20060507183403011008u4goe>; Sun, 7 May 2006 18:34:04 +0000
Message-ID: <445E3DA2.3080802@fidelity-comtech.com>
Date: Sun, 07 May 2006 12:34:10 -0600
From: Joe Carey <joe.carey@fidelity-comtech.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: DANIEL BYRNE <daniel.byrne@adtran.com>
References: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F1B@EXV1.corp.adtran.com>
In-Reply-To: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F1B@EXV1.corp.adtran.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: manet@ietf.org
Subject: [manet] 802.11s: Neighbors, Link Layer and Network Layer
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Daniel's post prompts me to ask a question of the list.  Perhaps 
somebody in the 802.11s world would care to comment on this.

In a traditional OSI network model, there's the PHY layer, the LINK 
layer and the NETWORK layer.

It appears from my limited exposure that the 802.11s protocol - and many 
vendors proprietary implementations of mesh - that they are attempting 
to implement multi-hop mesh networks at the LINK layer.  This seems to 
be exactly the wrong way to partition the problem; it would seem that 
the store-and-forward nature of mesh networking, including multiple 
links, should remain at layer 3 (the IP layer), where most current 
implementations have it.  However, these are smart people with a lot of 
experience.  So what is motivating this?

If I've misunderstood the problem, please correct me.

Thanks,

joe

DANIEL BYRNE wrote:
> "...That is why I feel a cross-layer approach will win out in the end.
> The physical and link layers will have information that is normally
> hidden from the routing layer that will be needed to evaluate potential
> links, but the MANET protocol will have the job of finding an optimal
> network solution."
>
> True, the routing protocol could use information attained by lower
> layers.  A mechanism to pass information up the stack is needed, or the
> protocol needs to be multi-layer aware. However, the later causes
> problems when there are changes in technologies.  Maybe a new stack
> architecture is needed for MANETS where protocols can still partition
> layer specific items yet share cross applicable information.
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>
>   


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



From manet-bounces@ietf.org Mon May 08 00:23:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FcxFn-0003NK-8q; Mon, 08 May 2006 00:21:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FcxFl-0003NC-OW
	for manet@ietf.org; Mon, 08 May 2006 00:21:49 -0400
Received: from che.ojctech.com ([64.198.255.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FcxFj-0008Qq-Ei
	for manet@ietf.org; Mon, 08 May 2006 00:21:49 -0400
Received: from che.ojctech.com (localhost [127.0.0.1])
	by che.ojctech.com (8.12.8/8.12.8) with ESMTP id k484LYHm010527;
	Sun, 7 May 2006 23:21:34 -0500
Received: (from dyoung@localhost)
	by che.ojctech.com (8.12.8/8.12.8/Submit) id k484LXVo010525;
	Sun, 7 May 2006 23:21:33 -0500
Date: Sun, 7 May 2006 23:21:33 -0500
From: David Young <dyoung@pobox.com>
To: "Mullen, John" <jomullen@ad.nmsu.edu>
Subject: Re: [manet] Re: MANET definition of a neighbor
Message-ID: <20060508042133.GP8159@che.ojctech.com>
Mail-Followup-To: "Mullen, John" <jomullen@ad.nmsu.edu>,
	DANIEL BYRNE <daniel.byrne@adtran.com>, manet@ietf.org
References: <8536FDFA3AD04A49A15804915996569106DEF23A@exchange1.ACN.ad.nmsu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8536FDFA3AD04A49A15804915996569106DEF23A@exchange1.ACN.ad.nmsu.edu>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: manet@ietf.org, DANIEL BYRNE <daniel.byrne@adtran.com>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

On Fri, May 05, 2006 at 09:00:59AM -0600, Mullen, John wrote:
> Hi Dan,
> 
> It doesn't work that way.  The chances of selecting a bad link may,
> depending on the scheme you pick, be higher than that of picking a good
> on.  In field trials, this has turned out to be a major source of
> trouble.  Repeated attempts will simply lead to repeated bad choices. 

Three observations, and a question: (1) Any choice of a single receiver
may be a bad choice, most of the time.  (2) The link conditions may not
outlast the decision process.  (3) You will broadcast the packet at the
physical layer, anyway---i.e., more than one receiver will receive it.
So, why choose?  (It only occurs to me to ask because I have fallen
under the influence of the Roofnet ExOR[1] study.)

Dave

[1] http://pdos.csail.mit.edu/papers/roofnet:exor-sigcomm05/roofnet_exor-sigcomm05.pdf

-- 
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 Mon May 08 01:48:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FcyaR-00076l-NL; Mon, 08 May 2006 01:47:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FcyaO-00075h-JK
	for manet@ietf.org; Mon, 08 May 2006 01:47:12 -0400
Received: from smtp-5.smtp.ucla.edu ([169.232.47.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FcyP9-0003u3-Sw
	for manet@ietf.org; Mon, 08 May 2006 01:35:38 -0400
Received: from mail.ucla.edu (mail.ucla.edu [169.232.48.151])
	by smtp-5.smtp.ucla.edu (8.13.6/8.13.6) with ESMTP id k485ZYuA002419;
	Sun, 7 May 2006 22:35:34 -0700
Received: from DD93FQ41 (Cs-120-200.CS.UCLA.EDU [131.179.120.200])
	(authenticated bits=0)
	by mail.ucla.edu (8.13.6/8.13.6) with ESMTP id k485ZYst016947
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT);
	Sun, 7 May 2006 22:35:34 -0700
Message-Id: <200605080535.k485ZYst016947@mail.ucla.edu>
From: "Mahesh Marina" <mahesh@cs.ucla.edu>
To: <manet@ietf.org>
Date: Sun, 7 May 2006 22:35:29 -0700
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: AcZyYTc68mXqKf/kRty64L2OL4DHSg==
X-Probable-Spam: no
X-Spam-Hits: 1.717
X-Spam-Score: **
X-Spam-Report: HTML_MESSAGE,HTML_NONELEMENT_30_40,MSGID_FROM_MTA_ID
X-Scanned-By: smtp.ucla.edu on 169.232.47.138
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8403cbbf1773e27474a13192645c46f
Subject: [manet] CFP: WiNTECH Workshop with ACM MobiCom 2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1456926163=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1456926163==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0016_01C67226.8B183120"

This is a multi-part message in MIME format.

------=_NextPart_000_0016_01C67226.8B183120
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Our apologies if you have received multiple copies of this CFP.

 

CALL FOR PAPERS

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

 

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/ 

 

*** Submission Deadline: June 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.

 

We are seeking original, previously unpublished papers addressing
experimental wireless networking issues. 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

 

IMPORTANT DATES

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

Submission deadline: June 15, 2006

Author notification: July 21, 2006

Camera ready papers: August 11, 2006

Workshop date: September 29, 2006

 

ORGANIZING COMMITTEE

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

Technical Program Co-Chairs:

Rajive Bagrodia (UCLA) 

Mahesh Marina (UCLA)

 

Program Committee Members (partial list):

Victor Bahl (Microsoft Research) 

Elizabeth Belding-Royer (UCSB) 

Tzi-cker Chiueh (SUNY-Stony Brook) 

Marco Conti (IIT-CNR, Italy) 

Edward Coyle (Purdue) 

Christophe Diot (Thomson Paris Research Lab) 

Joe Evans (University of Kansas) 

Richard Fujimoto (Georgia Tech) 

Ravi Jain (Google) 

Ed Knightly (Rice University) 

Jay Lepreau (University of Utah) 

Prasant Mohapatra (UC-Davis) 

Dina Papagiannaki (Intel Research Cambridge) 

Dipankar Raychauduri (Rutgers) 

Mani Srivastava (UCLA) 

Peter Steenkiste (CMU) 

Mineo Takai (UCLA) 

 

FURTHER INFORMATION

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

Please visit the WiNTECH 2006 workshop website:

http://chenyen.cs.ucla.edu/events/wintech06/ 

 


------=_NextPart_000_0016_01C67226.8B183120
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceName"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Trebuchet MS";
	panose-1:2 11 6 3 2 2 2 2 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Trebuchet MS";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Our apologies if you have received =
multiple
copies of this CFP.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>CALL FOR =
PAPERS<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet =
MS"'>--------------------------------------------------------------------=
-------------------------------------------------------------------------=
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>The First International Workshop on =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Wireless Network Testbeds, =
Experimental
evaluation and CHaracterization (WiNTECH 2006) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>in conjunction with ACM MobiCom =
2006<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>September 29, =
2006<o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:place w:st=3D"on"><st1:City w:st=3D"on"><font =
size=3D3
  face=3D"Trebuchet MS"><span =
style=3D'font-size:12.0pt;font-family:"Trebuchet MS"'>Los
  Angeles</span></font></st1:City><font face=3D"Trebuchet MS"><span
 style=3D'font-family:"Trebuchet MS"'>, <st1:State =
w:st=3D"on">CA</st1:State>, <st1:country-region
 w:st=3D"on">USA</st1:country-region></span></font></st1:place><font
face=3D"Trebuchet MS"><span style=3D'font-family:"Trebuchet =
MS"'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Sponsored by ACM =
SIGMOBILE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><a
href=3D"http://chenyen.cs.ucla.edu/events/wintech06/"
title=3D"http://chenyen.cs.ucla.edu/events/wintech06/">http://chenyen.cs.=
ucla.edu/events/wintech06/</a>
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>*** Submission Deadline: June 15, =
2006 ***<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet =
MS"'>--------------------------------------------------------------------=
-------------------------------------------------------------------------=
--<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>OVERVIEW AND =
SCOPE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet =
MS"'>-----------------------------<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>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.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>We are seeking original, previously
unpublished papers addressing experimental wireless networking issues. =
Topics
of interest include, but are not limited to: =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Design and evaluation of wireless
testbeds, prototypes and platforms<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Experiences/lessons from recent =
testbed
design efforts<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Hybrid experimentation approaches
combining use of multiple evaluation =
methodologies<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Integration of diverse and =
distributed
testbed infrastructures<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Testbed management issues and =
monitoring
support<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Wireless testbed case =
studies<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Experimental evaluation of =
applications
and protocols (at different layers), and the impact of cross-layer =
interactions<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Large-scale and heterogeneous =
wireless
network evaluations<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Approaches for real-world =
evaluation of
mobile networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Evaluation environments for sensor =
and
satellite networks<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Techniques for improving =
reproducibility
of real-world testing<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Implementation approaches to ease
transition between various evaluation methodologies as well as to =
improve
testbed accessibility<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* New measurement methodologies and
infrastructures <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Measurement and characterization
(modeling) of various real-world aspects such as usage patterns, =
traffic,
mobility and channel characteristics<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Interference and spectrum usage
measurements<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Validation of existing simulation =
models,
and results across different testbeds/evaluation =
methodologies<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>* Software tools in support of =
measurements,
trace/data collection and management<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>IMPORTANT =
DATES<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet =
MS"'>------------------------<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Submission deadline: June 15, =
2006<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Author notification: July 21, =
2006<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Camera ready papers: August 11, =
2006<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Workshop date: September 29, =
2006<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>ORGANIZING =
COMMITTEE<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet =
MS"'>--------------------------------<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Technical Program =
Co-Chairs:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Rajive Bagrodia (UCLA) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Mahesh Marina =
(UCLA)<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Program Committee Members (partial =
list):<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Victor Bahl (Microsoft Research) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Elizabeth Belding-Royer (UCSB) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Tzi-cker Chiueh (SUNY-Stony Brook) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
lang=3DIT
style=3D'font-size:12.0pt;font-family:"Trebuchet MS"'>Marco Conti =
(IIT-CNR,
Italy) <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Edward Coyle (Purdue) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Christophe Diot (Thomson Paris =
Research Lab)
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Joe Evans (<st1:place =
w:st=3D"on"><st1:PlaceType
 w:st=3D"on">University</st1:PlaceType> of <st1:PlaceName =
w:st=3D"on">Kansas</st1:PlaceName></st1:place>)
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Richard Fujimoto (Georgia Tech) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:place w:st=3D"on"><font size=3D3 =
face=3D"Trebuchet MS"><span
 style=3D'font-size:12.0pt;font-family:"Trebuchet =
MS"'>Ravi</span></font></st1:place><font
face=3D"Trebuchet MS"><span style=3D'font-family:"Trebuchet MS"'> Jain =
(Google) <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Ed Knightly (<st1:place =
w:st=3D"on"><st1:PlaceName
 w:st=3D"on">Rice</st1:PlaceName> <st1:PlaceType =
w:st=3D"on">University</st1:PlaceType></st1:place>)
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Jay Lepreau (<st1:place =
w:st=3D"on"><st1:PlaceType
 w:st=3D"on">University</st1:PlaceType> of <st1:PlaceName =
w:st=3D"on">Utah</st1:PlaceName></st1:place>)
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Prasant Mohapatra (UC-Davis) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Dina Papagiannaki (Intel Research =
<st1:place
w:st=3D"on"><st1:City w:st=3D"on">Cambridge</st1:City></st1:place>) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Dipankar Raychauduri (<st1:place =
w:st=3D"on">Rutgers</st1:place>)
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
lang=3DIT
style=3D'font-size:12.0pt;font-family:"Trebuchet MS"'>Mani Srivastava =
(UCLA) <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
lang=3DIT
style=3D'font-size:12.0pt;font-family:"Trebuchet MS"'>Peter Steenkiste =
(CMU) <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Mineo Takai (UCLA) =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>FURTHER =
INFORMATION<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet =
MS"'>-------------------------------<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'>Please visit the WiNTECH 2006 =
workshop
website:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><a
href=3D"http://chenyen.cs.ucla.edu/events/wintech06/"
title=3D"http://chenyen.cs.ucla.edu/events/wintech06/">http://chenyen.cs.=
ucla.edu/events/wintech06/</a>
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Trebuchet MS"><span =
style=3D'font-size:
12.0pt;font-family:"Trebuchet MS"'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0016_01C67226.8B183120--



--===============1456926163==
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

--===============1456926163==--





From manet-bounces@ietf.org Mon May 08 02:57:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fczf1-0004ee-Mq; Mon, 08 May 2006 02:56:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fczew-0004cz-V4
	for manet@ietf.org; Mon, 08 May 2006 02:55:58 -0400
Received: from web54610.mail.yahoo.com ([206.190.49.180])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FczQI-0008OG-MT
	for manet@ietf.org; Mon, 08 May 2006 02:40:52 -0400
Received: (qmail 64524 invoked by uid 60001); 8 May 2006 06:40:50 -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=fBisEi+laEpG+c2RDdq1Z8RIoH/VEmnolhTe+nsKAD+QdamyndrriOWENsIr4PKqtUhN5vjcAG1KPmMJLzS1tbPGjyJmhxLFwx6FLlpad/d06difwViGkcWGp43TftTZVzUhAGB2erDvbZwzY2HuF0L3Fvmu6nAV5RRMHxNXUWQ=
	; 
Message-ID: <20060508064050.64522.qmail@web54610.mail.yahoo.com>
Received: from [82.201.196.144] by web54610.mail.yahoo.com via HTTP;
	Sun, 07 May 2006 23:40:50 PDT
Date: Sun, 7 May 2006 23:40:50 -0700 (PDT)
From: amr hassan <amr_hassan1@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: [manet] Promiscuous mode in DSR
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1009265090=="
Errors-To: manet-bounces@ietf.org

--===============1009265090==
Content-Type: multipart/alternative; boundary="0-1211304972-1147070450=:64507"
Content-Transfer-Encoding: 8bit

--0-1211304972-1147070450=:64507
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hello everybody,
   
  I had a question regarding the promiscuous mode in DSR. As far as I understand the nodes employing the DSR protocol are able to disable filtering on their Network Interface Cards (NICs) so that they can monitor link failures and the rapid changing network topology. 
   
  My question is: during employing this mode, is there any type of MAC messages used? And if the answer is NO, then what is the reason for the large MAC overhead introduced for nodes using a DSR protocol compared to others using AODV for example?
   
  Kind regards,
  Amr

		
---------------------------------
New Yahoo! Messenger with Voice. Call regular phones from your PC and save big.
--0-1211304972-1147070450=:64507
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face="Times New Roman" size=3>Hello everybody,</FONT></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face="Times New Roman" size=3>I had a question regarding the promiscuous mode in DSR. As far as I understand the nodes employing the DSR protocol are able to disable filtering on their Network Interface Cards (NICs) so that they can monitor link failures and the rapid changing network topology. </FONT></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face="Times New Roman" size=3>My question is: during employing this mode, is there any type of MAC messages used? And if the answer is NO,
 then what is the reason for the large MAC overhead introduced for nodes using a DSR protocol compared to others using AODV for example?</FONT></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face="Times New Roman" size=3>Kind regards,</FONT></div>  <div class=MsoNormal style="MARGIN: 0in 0in 0pt"><FONT face="Times New Roman" size=3>Amr</FONT></div><p>
		<hr size=1>New Yahoo! Messenger with Voice. <a href="http://us.rd.yahoo.com/mail_us/taglines/postman5/*http://us.rd.yahoo.com/evt=39666/*http://messenger.yahoo.com">Call regular phones from your PC</a> and save big.
--0-1211304972-1147070450=:64507--


--===============1009265090==
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

--===============1009265090==--




From manet-bounces@ietf.org Mon May 08 09:09:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fd5TL-0005uT-C2; Mon, 08 May 2006 09:08:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fd5TJ-0005uO-Sz
	for manet@ietf.org; Mon, 08 May 2006 09:08:21 -0400
Received: from ultra.cs.binghamton.edu ([128.226.123.107])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fd5TI-0007TF-IP
	for manet@ietf.org; Mon, 08 May 2006 09:08:21 -0400
Received: from localhost ([127.0.0.1] ident=amavis)
	by ultra.cs.binghamton.edu with esmtp (Exim 4.50)
	id 1Fd5TF-00016u-GN; Mon, 08 May 2006 09:08:17 -0400
Received: from ultra.cs.binghamton.edu ([127.0.0.1])
	by localhost (ultra [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
	id 03794-06; Mon, 8 May 2006 09:08:13 -0400 (EDT)
Received: from alpha.cs.binghamton.edu
	([128.226.123.105] helo=aplha.cs.binghamton.edu ident=Debian-exim)
	by ultra.cs.binghamton.edu with esmtp (Exim 4.50)
	id 1Fd5TB-00016R-Hg; Mon, 08 May 2006 09:08:13 -0400
Received: from nael (helo=localhost)
	by aplha.cs.binghamton.edu with local-esmtp (Exim 4.50)
	id 1Fd5TA-0006wG-Vy; Mon, 08 May 2006 09:08:13 -0400
Date: Mon, 8 May 2006 09:08:12 -0400 (EDT)
From: Nael Abu-Ghazaleh <nael@cs.binghamton.edu>
To: manet@ietf.org
Message-ID: <Pine.LNX.4.62.0605080906280.26650@aplha.cs.binghamton.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at cs.binghamton.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 200d029292fbb60d25b263122ced50fc
Cc: podc@acm.org, tccc@cs.columbia.edu
Subject: [manet] Deadline Extended -- MSWiM 2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


-------------------------------------------------------------------
   Our apologies if you have received multiple copies
-------------------------------------------------------------------

------------------------------------------------------------------------------
                       ACM/IEEE  MSWiM 2006
------------------------------------------------------------------------------
                        Call for Papers
                 The 9th ACM/IEEE* International Symposium on
       Modeling, Analysis and Simulation of Wireless and Mobile Systems
                        Torremolinos, SPAIN
                         October 2--6, 2006
                  http://www.cs.unibo.it/mswim2006

------------------------------------------------------------------------------
* ACM and IEEE pending approval
------------------------------------------------------------------------------
New submission deadline: May 15th, 2006 
------------------------------------------------------------------------------

*Scope and Overview: 
ACM/IEEE MSWiM 2006 is the Ninth Annual International Symposium on 
Modeling, Analysis and Simulation of Wireless and Mobile Systems. 
MSWiM is an international forum dedicated to high level discussion 
of Wireless and Mobile systems, networks, algorithms and applications, 
with an emphasis on rigorous performance evaluation. 
MSWiM is a highly selective conference that is recognized as one of 
the most prestigious sources of innovative ideas and breakthroughs 
in the field.  MSWiM 2006 will be held October 2 to 6, 2006, 
in sunny Terremolinos, in Spain.

Authors are encouraged to submit full papers presenting new research
related to the theory or practice of all aspects of modeling, analysis
and simulation of mobile and wireless systems.  Submitted papers must
not have been published elsewhere nor currently be under review by
another conference or journal.


*Topics of Interest.  Papers related to wireless and mobile network
  Modeling, Analysis, Design, and Simulation are solicited on, but not
  limited to, the following topics:

- Analytical Models
- New simulation languages and tools for wireless systems
- Design methodologies
- Performance evaluation and modeling 
- Formal methods for analysis of wireless systems
- Wireless Network Protocols 
- Wireless Multimedia Systems
- Tools, Prototype and Testbeds
- Wireless PANs, LANs
- Survivability and reliability evaluation 
- Ad Hoc Networks
- Traffic measurements and models for wireless networks
- Sensor and Actuator Networks 
- RF channel capacity modeling and analysis
- Pervasive computing and emerging models
- QoS provisioning in wireless and mobile networks
- Integration of wired and wireless systems
- Security and privacy of mobile/wireless systems
- Mobility modeling and management 
- Algorithms and protocols for energy efficent operation and power 
control
- Mobile applications, system software and algorithms
- Parallel and distributed simulation of wireless systems


Submission instructions and publication

  will be published on the conference
web site shortly (http://www.cs.unibo.it/mswim2006).  Accepted papers
will appear in the conference proceedings to be published by ACM press.

-------------------------------------------------------------------------------
A Special Issue with (Elsevier) Computer Network Journal containing 
Best Papers 
will be scheduled
-------------------------------------------------------------------------------

------------------------------------------------------------
* Submission instructions and publication:
------------------------------------------------------------
High-quality original papers are solicited. Papers must be
unpublished and must not be submitted for publication
elsewhere. All papers will be reviewed by Technical Program
Committee members and other experts active in the field to
ensure high quality and relevance to the conference. Paper
length should not exceed 20 pages. Only Postscript and PDF
formats are accepted.
Instructions for paper submission will be posted at:
http://www.cs.unibo.it/mswim2006/
Accepted papers will appear in the symposium proceedings published by 
ACM.
A Journal Special Issue will be planned which will contain
selected papers from MSWiM.



------------------------------------------------------------------------------
*Important Dates:

Paper submission deadline          May 15 2006
Notification of acceptance         July 5 2006
Tutorial submission deadline       July 5th, 2006
------------------------------------------------------------------------------

General Co-Chairs:
Carla-Fabiana Chiasserini, Politecnico di Torino, Italy
Email: chiasserini@polito.it

Enrique Alba, University of Malaga, Spain 
Email: eat@lcc.uma.es

Program Committee Chairs:
Renato Lo Cigno, University of Trento, Italy
Email: cigno@dit.unitn.it

Nael Abu-Ghazaleh, State University of New York at Binghamton, USA
Email: nael@cs.binghamton.edu

Poster Co-Chairs:

Sotiris Nikoletseas 
University of Patra, Greece
Email: nikole@cti.gr

Steve Olariu
Old Dominion University, USA
Email: olariu@cs.odu.edu


Tutorial Chair

Mineo Takai
University of Los Angeles, California, USA
Email: mineo@cs.ucla.edu

Local Organization Chair:
Enrique Alba, University of Malaga, Spain

Steering Committee Chair
Azzedine Boukerche, University of Ottawa, Canada





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



From manet-bounces@ietf.org Mon May 08 12:05:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fd8Dl-0002Yt-00; Mon, 08 May 2006 12:04:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fd8Dj-0002Yn-Il
	for manet@ietf.org; Mon, 08 May 2006 12:04:27 -0400
Received: from mx4.iit.cnr.it ([146.48.98.151] helo=smtp.iit.cnr.it)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fd8Dg-0000Jt-RD
	for manet@ietf.org; Mon, 08 May 2006 12:04:27 -0400
Received: from localhost (localhost [127.0.0.1])
	by smtp.iit.cnr.it (Postfix) with ESMTP id 223051F591;
	Mon,  8 May 2006 18:04:15 +0200 (CEST)
Received: from smtp.iit.cnr.it ([127.0.0.1])
	by localhost (mx4.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 31641-04; Mon,  8 May 2006 18:04:12 +0200 (CEST)
Received: from [146.48.99.42] (dhcp75.iit.cnr.it [146.48.99.42])
	by smtp.iit.cnr.it (Postfix) with ESMTP id 24CA01E1F9;
	Mon,  8 May 2006 18:04:11 +0200 (CEST)
Mime-Version: 1.0
X-Sender: marco.conti@iit.cnr.it@mail.iit.cnr.it
Message-Id: <a0602040cc085174ff72d@[146.48.99.42]>
Date: Mon, 8 May 2006 18:04:08 +0200
To: CABERNET-EVENTS@JISCMAIL.AC.UK, manet@ietf.org, ifip_tc6.3@di.uoa.gr
From: Marco Conti <Marco.Conti@iit.cnr.it>
X-Virus-Scanned: amavisd-new at iit.cnr.it
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 6a45e05c1e4343200aa6b327df2c43fc
Cc: 
Subject: [manet] Journal on Wireless Communications & Networking - special
 issue on Mobile Multi-hop Ad Hoc Networks: From Theory to Reality
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0178893374=="
Errors-To: manet-bounces@ietf.org

--===============0178893374==
Content-Type: multipart/alternative;
	boundary="============_-1065018246==_ma============"

--============_-1065018246==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"


  Apologies if you receive multiple copies
----------------------------------------------------------------------

Call for Papers

EURASIP Journal on Wireless Communications & Networking

Special issue on
MobileMAN (Mobile Multi-hop Ad Hoc Networks): From Theory to Reality
http://www.hindawi.com/journals/WCN/si/MobileMAN.html


The aim of this special issue is to present, from an experimental 
perspective, architectures and protocols for implementing (mobile) ad 
hoc networks. This special issue constitutes a unique forum to 
present measurements/experiences/lessons obtained by implementing ad 
hoc networks testbeds and prototypes. The special issue will 
investigate the whole protocol stack from enabling technologies to 
middleware and applications.

Original contributions are solicited, related to system and protocol 
development, measurement, and testing, in all areas related to ad hoc 
networking. Specifically, topics of interest include, but are not 
limited to:
	*	Ad hoc networks applications
	*	System prototypes and experiences
	*	Mobile ad hoc networks
	*	Opportunistic and delay tolerant networks
	*	Sensor networks
	*	Mesh networks
	*	Vehicular networks
	*	Protocol implementation and testing
	*	Middleware platforms for ad hoc networks
	*	Ad hoc networking for pervasive environments
	*	Situated and autonomic communications
	*	Location services
	*	Positioning and tracking technologies and services
	*	Measurement studies
	*	Mobility models based on real data
	*	Enabling technologies measurements (802.11, 802.15, etc.)
	*	Experiment-based socio-economic analysis of ad hoc networks

Authors should follow the EURASIP JWCN manuscript format described at 
the journal site http://www.hindawi.com/journals/wcn/. Prospective 
authors should submit an electronic copy of their complete manuscript 
through the EURASIP JWCN's manuscript tracking system at 
http://www.hindawi.com/mts/, according to the following timetable:

Manuscript Due
July 1, 2006

Acceptance Notification
November 1, 2006

Final Manuscript Due
February 1, 2007

Publication Date
2nd Quarter, 2007

Guest Editor:

Marco Conti, Consiglio Nazionale delle Ricerche (CNR), Instituto di 
Informatica e Telematica (IIT-CNR), Via Giuseppe, Moruzzi 1, 56124 
Pisa, Italy,
e-mail: Marco.Conti@iit.cnr.it



-- 
==============================================
Marco Conti
Pervasive Computing & Networking Lab. (PerLab)
http://www.perlab.it

Institute for Informatics and Telematics (IIT)
National Research Council (CNR)
Via G. Moruzzi, 1
56124 Pisa,Italy
tel.: + 39 050 315 3062 (direct)
mobile: +39 348 3966807
fax.: +39 050 3152113




--============_-1065018246==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Journal on Wireless Communications &amp; Networking
- special</title></head><body>
<div align="center"><br></div>
<div align="center">&nbsp;Apologies if you receive multiple
copies</div>
<div
>--------------------------------------------------------------------<span
></span>--</div>
<div align="center"><font color="#000000"><br></font></div>
<div align="center"><font color="#000000">Call for Papers</font></div>
<div align="center"><font size="-4"
color="#000000"><b><br></b></font></div>
<div align="center">EURASIP Journal on Wireless Communications &amp;
Networking</div>
<div align="center"><br></div>
<div align="center">Special issue on</div>
<div align="center"><font color="#000000">MobileMAN (Mobile Multi-hop
Ad Hoc Networks): From Theory to Reality</font></div>
<div align="center"><font
color="#000000">http://www.hindawi.com/journals/WCN/si/MobileMAN.html</font
></div>
<div><font color="#000000"><b><br></b></font></div>
<div><font color="#000000"><b><br></b></font></div>
<div><font size="-4" color="#000000">The aim of this special issue is
to present, from an experimental perspective, architectures and
protocols for implementing (mobile) ad hoc networks. This special
issue constitutes a unique forum to present
measurements/experiences/lessons obtained by implementing ad hoc
networks testbeds and prototypes. The special issue will investigate
the whole protocol stack from enabling technologies to middleware and
applications.<br>
<br>
Original contributions are solicited, related to system and protocol
development, measurement, and testing, in all areas related to ad hoc
networking. Specifically, topics of interest include, but are not
limited to:</font></div>
<div><font size="-4"
color="#000000"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>Ad hoc
networks applications<br>
<x-tab>&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>System
prototypes and experiences<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>Mobile ad
hoc networks<br>
<x-tab>&nbsp; </x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>Opportunistic and delay tolerant networks<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>Sensor
networks<br>
<x-tab> </x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>Mesh networks<br>
<x-tab>&nbsp;&nbsp; </x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>Vehicular networks<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>Protocol
implementation and testing<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>Middleware platforms for ad hoc networks<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>Ad hoc
networking for pervasive environments<br>
<x-tab>&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>Situated
and autonomic communications<br>
<x-tab>&nbsp;&nbsp; </x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>Location services<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>Positioning and tracking technologies and
services</font></div>
<div><font size="-4"
color="#000000"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>Measurement studies<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>Mobility
models based on real data</font></div>
<div><font size="-4"
color="#000000"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>Enabling technologies measurements (802.11, 802.15,
etc.)</font></div>
<div><font size="-4"
color="#000000"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>Experiment-based socio-economic analysis of ad hoc
networks</font></div>
<div><font size="-4" color="#000000"><br>
Authors should follow the EURASIP JWCN manuscript format described at
the journal site</font><font size="-4" color="#0000AA">
http://www.hindawi.com/journals/wcn/</font><font size="-4"
color="#000000">. Prospective authors should submit an electronic copy
of their complete manuscript through the EURASIP JWCN's manuscript
tracking system at</font><font size="-4" color="#0000AA">
http://www.hindawi.com/mts/</font><font size="-4" color="#000000">,
according to the following timetable:</font><br>
<font size="-4" color="#000000"></font></div>
<div><font size="-4" color="#000000">Manuscript Due<br>
July 1, 2006<br>
<br>
Acceptance Notification<br>
November 1, 2006<br>
<br>
Final Manuscript Due<br>
February 1, 2007<br>
<br>
Publication Date<br>
2nd Quarter, 2007<br>
</font></div>
<div><font size="-4" color="#000000"><b>Guest Editor:</b></font><br>
<font size="-4" color="#000000"><b></b></font></div>
<div><font size="-4" color="#0000AA">Marco Conti</font><font
size="-4" color="#000000">, Consiglio Nazionale delle Ricerche (CNR),
Instituto di Informatica e Telematica (IIT-CNR), Via Giuseppe, Moruzzi
1, 56124 Pisa, Italy,</font></div>
<div>e-mail: Marco.Conti@iit.cnr.it</div>
<div><br></div>
<div><br></div>
<div><br></div>
<x-sigsep><pre>-- 
</pre></x-sigsep>
<div>==============================================<br>
Marco Conti<br>
Pervasive Computing &amp; Networking Lab. (PerLab)<br>
http://www.perlab.it<br>
<br>
Institute for Informatics and Telematics (IIT)<br>
National Research Council (CNR)<br>
Via G. Moruzzi, 1<br>
56124 Pisa,Italy<br>
tel.: + 39 050 315 3062 (direct)<br>
mobile: +39 348 3966807<br>
fax.: +39 050 3152113<br>
<br>
<br>
<br>
</div>
</body>
</html>
--============_-1065018246==_ma============--


--===============0178893374==
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

--===============0178893374==--




From manet-bounces@ietf.org Mon May 08 12:19:34 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fd8Rw-0007jd-M1; Mon, 08 May 2006 12:19:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fd8Rv-0007jS-94
	for manet@ietf.org; Mon, 08 May 2006 12:19:07 -0400
Received: from p02m141.mxlogic.net ([66.179.26.141])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fd8Rs-000105-OW
	for manet@ietf.org; Mon, 08 May 2006 12:19:07 -0400
Received: from unknown [208.61.208.100]
	by p02m141.mxlogic.net (mxl_mta-2.14.0-12)
	with SMTP id 87f6f544.1148591024.25139.p02m141.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Mon, 08 May 2006 10:19:04 -0600 (MDT)
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] Re: MANET definition of a neighbor
Date: Mon, 8 May 2006 11:18:47 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F28@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZyVugEQ+lqkUeHSuyDvWnQCm/PWgAYi1Ig
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: "David Young" <dyoung@pobox.com>,
	"Mullen, John" <jomullen@ad.nmsu.edu>
X-Spam: [F=0.1136979296; S=0.113(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.61.208.100]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Yeah, why choose!?  Seems logical.  In fact I was thinking something
similar.  Using nature as a guide.  Light, Electromagnetic Radiation,
Photons, etc. are transmited and all directions, and nearly everyone and
everything around interacts with the ambient light. Every piece of
clothing in a tailor's shop for instance will interact with the ambient
light and reflect its color and texture, ie. (forward the packet) albeit
on his own frequency.  If we could just follow this simple model but
make the forwarding of packets more intelligent. =20

I haven't read past the introduction of the paper, so just let me
expound on what I was thinking.

- Links do not neccessisarily need to be pre-established.  Just
broadcast assuming someone is listening.  If you in turn hear your
broadcast retransmitted, then assume it is on its way.

- Tx Packets may include a preferred destination.  If for some
reason,(lost packet, garbled data, congestion, buffer overrun, etc.) the
packet gets tossed at the preferred destination.  Another listening
station within earshot can wait to hear from the preferred station. If
he doesn't hear it then he is free to forward the packet to the next
hop.


"Three observations, and a question: (1) Any choice of a single receiver
may be a bad choice, most of the time.  (2) The link conditions may not
outlast the decision process.  (3) You will broadcast the packet at the
physical layer, anyway---i.e., more than one receiver will receive it.
So, why choose?  (It only occurs to me to ask because I have fallen
under the influence of the Roofnet ExOR[1] study.)

Dave

[1]
http://pdos.csail.mit.edu/papers/roofnet:exor-sigcomm05/roofnet_exor-sig
comm05.pdf"

--=20
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 Mon May 08 12:35:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fd8hI-0005aC-QA; Mon, 08 May 2006 12:35:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fd8hH-0005Zz-7W
	for manet@ietf.org; Mon, 08 May 2006 12:34:59 -0400
Received: from p02m143.mxlogic.net ([66.179.26.143])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fd8hE-0001zO-Sb
	for manet@ietf.org; Mon, 08 May 2006 12:34:59 -0400
Received: from unknown [208.251.151.99]
	by p02m143.mxlogic.net (mxl_mta-2.14.0-12)
	with SMTP id 0337f544.1514068912.17215.p02m143.mxlogic.net
	(envelope-from <daniel.byrne@adtran.com>); 
	Mon, 08 May 2006 10:34:56 -0600 (MDT)
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] Re: MANET definition of a neighbor
Date: Mon, 8 May 2006 11:34:27 -0500
Message-ID: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F29@EXV1.corp.adtran.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZyVugEQ+lqkUeHSuyDvWnQCm/PWgAZSx5g
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
To: "David Young" <dyoung@pobox.com>,
	"Mullen, John" <jomullen@ad.nmsu.edu>
X-Spam: [F=0.0100000000; S=0.010(2006042401)]
X-MAIL-FROM: <daniel.byrne@adtran.com>
X-SOURCE-IP: [208.251.151.99]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

On Fri, May 05, 2006 at 09:00:59AM -0600, Mullen, John wrote:
> Hi Dan,
>=20
> It doesn't work that way.  The chances of selecting a bad link may,=20
> depending on the scheme you pick, be higher than that of picking a=20
> good on.  In field trials, this has turned out to be a major source of

> trouble.  Repeated attempts will simply lead to repeated bad choices.

This statement simply doesn't make any sense.  If repeated attempts
produce repeated bad choices, then the decision making process behind
choosing is incorrect, not the sampling.  Choosing once and assuming all
is good just doesn't work.

Imagine if you plotted a trip with your family to Disney world.  You
figured gas, speed, and route to the best of your ability before you
started the trip.  If you didn't subsequently modify your careful
calculations to account for weather, traffic, stop lights, road
construction, pot holes, pedestrians, and any number of other
interferences, then you would wreck before you left your neighborhood.
Constant sampling always produces better results unless of course your 3
year old is driving.  In that case it is better to point the steering
wheel in the right direction, and just see how far he can get before
wrecking.  He will probably make it further this way then if you let him
run the controls all by himself. I.e.. The decision making person in
this process is the problem.

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



From manet-bounces@ietf.org Mon May 08 13:09:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fd9ER-00018l-DR; Mon, 08 May 2006 13:09:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fd9EP-00018g-GK
	for manet@ietf.org; Mon, 08 May 2006 13:09:13 -0400
Received: from mailfe01.tele2.fr ([212.247.154.12] helo=swip.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fd9EN-0003ym-SR
	for manet@ietf.org; Mon, 08 May 2006 13:09:13 -0400
X-T2-Posting-ID: awqqfnaTsr4Tdz6hsMRmdZcsIOrGCpI/YK875gkeDuo=
X-Cloudmark-Score: 0.000000 []
Received: from [80.170.101.80] (HELO DAMIEN)
	by mailfe01.swip.net (CommuniGate Pro SMTP 5.0.8)
	with SMTPS id 171816647; Mon, 08 May 2006 19:08:56 +0200
Message-ID: <023f01c672c2$b87512e0$0a1e140a@DAMIEN>
From: "Damien Magoni" <magoni@dpt-info.u-strasbg.fr>
To: <manet@ietf.org>
Date: Mon, 8 May 2006 19:13:25 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: Petre DINI <pdini@cisco.com>, dumitru.roman@deri.org
Subject: [manet] CfP ICSNC 2006 || International Conference on Systems and
	Networks Communications, Tahiti, November 2 - November 4, 2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

===================================================
Apologies for multiple postings

CALL FOR PAPERS

International Conference on  Systems and Networks Communications,
ICSNC 2006
November 2 - November 4, 2006, Tahiti.

Call for Papers:
http://www.iaria.org/conferences/CfPICSNC06.html

Submission:
Go to http://www.iaria.org/conferences/ICSNC06.html
and click "Submit a paper"

Deadlines:
Submission deadline: June 1, 2006
Notification: July 1, 2006
Camera ready: July 15, 2006

The Second International Conference on Systems and Networks
Communications continues a series of events covering a broad spectrum of
systems and networks related topics. The conference covers fundamentals
on wireless, high speed, sensor and mobile and ad hoc networks,
security, policy based systems, and education systems. Topics are
targeting design, implementation, testing, use cases, tools, and lessons
learnt for such networks and systems.

The conference has the following specialized topics (mini-conferences) :

WINET 2006       Wireless networks
HSNET 2006       High speed networks
SENET 2006       Sensor networks
MHNET 2006     Mobile and Ad hoc networks
SESYS 2006       Security systems
MCSYS 2006      Multimedia communications systems
POSYS 2006       Policy-based systems
PESYS 2006        Pervasive education systems

We welcome technical papers presenting research and practical results,
position papers addressing the pros and cons of specific proposals, such
as those being discussed in the standard fora or in industry consortia,
survey papers addressing the key problems and solutions on any of the
above topics short papers on work in progress, and panel proposals.

The topics suggested by the conference can be discussed in term of
concepts, state of the art, standards, implementations, running
experiments and applications. Authors are invited to submit complete
unpublished papers, which are not under review in any other conference
or journal in the following, but not limited topic areas. Industrial
presentations are not subject to these constraints. Tutorials on
specific related topics and panels on challenging areas are encouraged.

http://www.iaria.org/conferences/CfPICSEA06.html
The ICSNC  2006 Proceedings are published by the
IEEE Computer Society Press,
and are indexed by SCI and EI via IEEE.

Regular papers
Only .pdf or .doc files will be accepted for paper submission. All
papers submitted via the EDAS system will receive an ID that will be
e-mailed to the contact author.

Final author manuscripts will be 8.5" x 11" (two columns IEEE format),
not exceeding 6 pages; max 4 extra pages allowed at additional cost. The
formatting instructions can be found via anonymous FTP site at:
ftp://pubftp.computer.org/Press/Outgoing/proceedings/8.5x11%20-%20Formatting%20files/instruct.pdf

Once you receive the notification of paper acceptance, you will be
provided by the IEEE CS Press an online author kit with all the steps an
author needs to follow to submit the final version. .

Technical marketing/business/positioning presentations
The conference initiates a series of business, technical marketing, and
positioning presentations on the same topics. Speakers must submit a
10-12 slide deck presentations with substantial notes accompanying the
slides, in the .ppt format (.pdf-ed). The slide deck will be published
in the conference's CD collection, together with the regular papers.
Please send your presentations to petre@iaria.org.

Tutorials
Tutorials provide overviews of current high interest topics. Proposals
can be for half or full day tutorials. Please send your proposals to
petre@iaria.org.

Panel proposals:
The organizers encourage scientists and industry leaders to organize
dedicated panels dealing with controversial and challenging topics and
paradigms. Panel moderators are asked to identify their guests and
manage that their appropriate talk supports timely reach our deadlines.
Moderators must specifically submit an official proposal, indicating
their background, panelist names, their affiliation, the topic of the
panel, as well as short biographies. For more information,
petre@iaria.org.

Workshop proposals
We welcome workshop proposals on issues complementary to the topics of
this conference. Your requests should be forwarded to petre@iaria.org.

Looking  forward for your submissions,

Thanks,
On behalf of the ICSNC Advisory Committee
Petre Dini, pdini@cisco.com
==================================================


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



From manet-bounces@ietf.org Mon May 08 13:38:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fd9fz-0002EZ-74; Mon, 08 May 2006 13:37:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fd9fy-0002EQ-05
	for manet@ietf.org; Mon, 08 May 2006 13:37:42 -0400
Received: from louie.udel.edu ([128.4.40.12] helo=mail.eecis.udel.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fd9fv-0005ty-O2
	for manet@ietf.org; Mon, 08 May 2006 13:37:41 -0400
Received: by mail.eecis.udel.edu (Postfix, from userid 62)
	id 9EAA7C1; Mon,  8 May 2006 13:37:37 -0400 (EDT)
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on louie.udel.edu
X-Spam-Level: **
X-Spam-Status: No, score=3.0 required=4.1 tests=AWL,BAYES_00,
	RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=no version=3.1.1
Received: from [192.168.0.4] (c-69-136-93-157.hsd1.de.comcast.net
	[69.136.93.157])
	by mail.eecis.udel.edu (Postfix) with ESMTP id 00D7642;
	Mon,  8 May 2006 13:37:33 -0400 (EDT)
Message-ID: <445F81D5.5050609@cis.udel.edu>
Date: Mon, 08 May 2006 13:37:25 -0400
From: Justin Yackoski <yackoski@cis.udel.edu>
User-Agent: Thunderbird 1.5.0.2 (X11/20060420)
To: DANIEL BYRNE <daniel.byrne@adtran.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
References: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F28@EXV1.corp.adtran.com>
In-Reply-To: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F28@EXV1.corp.adtran.com>
X-Sanitizer: This message has been sanitized!
X-Sanitizer-URL: http://mailtools.anomy.net/
X-Sanitizer-Rev: UDEL-ECECIS: Sanitizer.pm, v 1.64 2002/10/22 MIME-Version: 1.0
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: manet@ietf.org, David Young <dyoung@pobox.com>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

DANIEL BYRNE wrote:
> Yeah, why choose!?  Seems logical.  In fact I was thinking something
> similar.  Using nature as a guide.  Light, Electromagnetic Radiation,
> Photons, etc. are transmited and all directions, and nearly everyone and
> everything around interacts with the ambient light. Every piece of
> clothing in a tailor's shop for instance will interact with the ambient
> light and reflect its color and texture, ie. (forward the packet) albeit
> on his own frequency.  If we could just follow this simple model but
> make the forwarding of packets more intelligent.  
> 
> I haven't read past the introduction of the paper, so just let me
> expound on what I was thinking.
> 
> - Links do not neccessisarily need to be pre-established.  Just
> broadcast assuming someone is listening.  If you in turn hear your
> broadcast retransmitted, then assume it is on its way.
> 
> - Tx Packets may include a preferred destination.  If for some
> reason,(lost packet, garbled data, congestion, buffer overrun, etc.) the
> packet gets tossed at the preferred destination.  Another listening
> station within earshot can wait to hear from the preferred station. If
> he doesn't hear it then he is free to forward the packet to the next
> hop.

This concept is similar to Witness Aided Routing, and 2 newer 
cross-layer protocols (which also reference some other related concepts) 
where some subset of your neighbors are able to respond and forward, and 
one is elected on a per-packet basis if needed.

- Cross-Layer Inference-based Fast Link Error Recovery (CIFLER). 
Yackoski, J. Shen, C.-C. WCNC 2006
- Guesswork: robust routing in an uncertain world. Parker, T. and 
Langendoen, K. MASS 2005

Justin

-- 
Justin Yackoski
DEGAS Networking Group
Dept. Of Computer and Info. Sciences
University of Delaware, Newark, DE 19711
http://degas.cis.udel.edu

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



From manet-bounces@ietf.org Mon May 08 13:45:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fd9nR-0004yj-Qx; Mon, 08 May 2006 13:45:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fd9nP-0004ye-Ux
	for manet@ietf.org; Mon, 08 May 2006 13:45:23 -0400
Received: from fw01.rockwellcollins.com ([205.175.225.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fd9nP-0006Ep-Db
	for manet@ietf.org; Mon, 08 May 2006 13:45:23 -0400
Received: by fw01.rockwellcollins.com; id MAA17158;
	Mon, 8 May 2006 12:45:17 -0500 (CDT)
From: <jasteven@rockwellcollins.com>
Received: from nodnsquery(131.198.169.132) by fw01.rockwellcollins.com via
	smap (V5.5) id xma016847; Mon, 8 May 06 12:44:32 -0500
Received: from vs02.rockwellcollins.com (localhost [127.0.0.1])
	by localhost.rockwellcollins.com (Postfix) with ESMTP id 7DCEE3188A
	for <manet@ietf.org>; Mon,  8 May 2006 12:44:35 -0500 (CDT)
Received: from crnotes2.rockwellcollins.com (crnotes2.rockwellcollins.com
	[131.198.64.109])
	by vs02.rockwellcollins.com (Postfix) with ESMTP id 60A2831886
	for <manet@ietf.org>; Mon,  8 May 2006 12:44:35 -0500 (CDT)
To: manet@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.2 June 01, 2004
Message-ID: <OF4DAEDF8C.A8F8D5B9-ON86257168.005242F9-86257168.0061537C@rockwellcollins.com>
Date: Mon, 8 May 2006 12:43:03 -0500
X-MIMETrack: Serialize by Router on
	CollinsCRSMTP02/CedarRapids/RockwellCollins(Release
	6.5.4FP3|January 09, 2006) at 05/08/2006 12:44:34 PM,
	Serialize complete at 05/08/2006 12:44:34 PM
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53
Subject: [manet] MANET protocol stacks
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0419370354=="
Errors-To: manet-bounces@ietf.org

This is a multipart message in MIME format.
--===============0419370354==
Content-Type: multipart/alternative;
	boundary="=_alternative 0061537886257168_="

This is a multipart message in MIME format.
--=_alternative 0061537886257168_=
Content-Type: text/plain; charset="US-ASCII"

Joe Carey wrote on 7 May 06

> In a traditional OSI network model, there's the PHY layer, the LINK
> layer and the NETWORK layer.
>
> It appears from my limited exposure that the 802.11s protocol - and
> many vendors proprietary implementations of mesh - that they are
> attempting to implement multi-hop mesh networks at the LINK layer. 
> This seems to be exactly the wrong way to partition the problem; it 
> would seem that the store-and-forward nature of mesh networking,
> including multiple links, should remain at layer 3 (the IP layer), 
> where most current implementations have it.  However, these are 
> smart people with a lot of experience.  So what is motivating this?

Two comments:

1.  Actually, the OSI and Internet networking efforts have always 
considered hierarchical layering of networks, where one multi-hop routing 
network provides what looks like a link (via tunneling or routing through 
the lower network) to the higher network.

ISO 8648 "Internal Organization of the Network Layer" breaks the Network 
Layer into 3 sublayers:  SubNetwork Independent Convergence Protocol 
(SNICP), SubNetwork Dependent Convergence Protocol (SNDCP), and SubNetwork 
Access Protocol (SNAcP). 

IEN 48, "The Catanet Model for Internetworking" by Vint Cerf talks about 
the Internet as being a collection of gateways with interfaces to local 
networks.  The local networks in turn provide the higher layer with what 
looks like an IP link (even if it is tunneled through the lower layer). 
And, discussions of internet protocols in the 1970s and 1980s (before the 
7-layer OSI model became the de facto protocol model) talked about four 
layers:  a Host/Application Layer, a Transport Layer, an Internet Layer, 
and a Subnetwork/Local Networks Layer.  (For example, look at figure 1 in 
RFC 791 "Internet Protocol" where 4 protocol layers are shown.)  The 
subnet layer basically subsumes the OSI Physical, Data Link, and SNAcP 
functionality.  It was back then that we started talking about layers 3A 
and 3B.  Most say 3A = Subnet and 3B = Internet (although others say the 
opposite: 3A = Internet and 3B = Subnet).

Anyway, the point is that both the traditional OSI and the Internet 
protocol architectures assume that routing may occur at multiple layers.

And, when we think about wireline networks, I never see/hear arguments 
that MPLS/VPLS violates layering because routing is performed below IP. So 
why do we argue about it in wireless networks.


2.  I believe an appropriate architecture for MANETs includes two 
networking layers.  The two layers are the Internet Protocol layer and a 
wireless MANET layer.

The Internet Protocol layer provides networking where neighbors and links 
look nice and graph-like.  In other words, the links are independent(i.e. 
what happens on one link does not affect other links contrary to wireless 
networks where transmissions on one link can interfere or congest other 
links) and links are fairly reliable and stable.  And, the concept of a 
neighbor is straight forward.  In addition, the protocol suite is 
standardized and predicted to be stable on the scale of decades.

The wireless MANET layer provides networking where neighbors and links are 
fuzzy and less graph-like.  In other words, the performance of one link 
may be dependent on that of other links (i.e. what happens on one link can 
affect what happens on other links) and links can operate in all manner of 
dynamic, and possibly poorly predictable ways.  And, the concept of a 
neighbor is more complicated. In addition, the protocol suite may change 
as wireless technologies change - although the protocol suite should 
provide a standard interface and service to the upper IP layer.

Thus, I believe that the MANET work should focus on multiple layers like 
the original Internet model - namely the Internet layer (which may have 
different routing hierarchical domains, but links basically look nice and 
graph-theoretic-like) and Wireless Subnets that may be just a star-like 
WLAN based around APs or may be full-blown mesh subnetworks. 

In the MANETs that I am involved with, we do subnet routing to (a) hide 
the link dynamics in the wireless subnets from the Internet so that 
changes in subnet routes are hidden from the Internet, (b) we found it 
more efficient (from a throughput, spectrum usage, and responsiveness to 
RF dynamics) to adapt to the dynamics at the subnet - analogous to how 
MPLS is more efficient than IP routing for wireline subnets, (c) it allows 
us to do some nice information assurance defense in depth protection 
mechanisms tailored to the particular wireless environment we are 
operating in, and (d) it hides the evolving wireless technologies and 
their cross-layer solutions from the more static IP networking.

Jim Stevens

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
James A. Stevens, PhD
Chief Network Architect
Rockwell Collins Government Systems

--=_alternative 0061537886257168_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2><tt>Joe Carey wrote on 7 May 06</tt></font>
<br>
<br><font size=2><tt>&gt; In a traditional OSI network model, there's the
PHY layer, the LINK</tt></font>
<br><font size=2><tt>&gt; layer and the NETWORK layer.<br>
&gt;</tt></font>
<br><font size=2><tt>&gt; It appears from my limited exposure that the
802.11s protocol - and</tt></font>
<br><font size=2><tt>&gt; many vendors proprietary implementations of mesh
- that they are</tt></font>
<br><font size=2><tt>&gt; attempting to implement multi-hop mesh networks
at the LINK layer. </tt></font>
<br><font size=2><tt>&gt; This seems to be exactly the wrong way to partition
the problem; it </tt></font>
<br><font size=2><tt>&gt; would seem that the store-and-forward nature
of mesh networking,</tt></font>
<br><font size=2><tt>&gt; including multiple links, should remain at layer
3 (the IP layer), </tt></font>
<br><font size=2><tt>&gt; where most current implementations have it. &nbsp;However,
these are </tt></font>
<br><font size=2><tt>&gt; smart people with a lot of experience. &nbsp;So
what is motivating this?<br>
</tt></font>
<br><font size=2><tt>Two comments:</tt></font>
<br>
<br><font size=2><tt>1. &nbsp;Actually, the OSI and Internet networking
efforts have always considered hierarchical layering of networks, where
one multi-hop routing network provides what looks like a link (via tunneling
or routing through the lower network) to the higher network.</tt></font>
<br>
<br><font size=2><tt>ISO 8648 &quot;Internal Organization of the Network
Layer&quot; breaks the Network Layer into 3 sublayers: &nbsp;SubNetwork
Independent Convergence Protocol (SNICP), SubNetwork Dependent Convergence
Protocol (SNDCP), and SubNetwork Access Protocol (SNAcP). &nbsp;</tt></font>
<br>
<br><font size=2><tt>IEN 48, &quot;The Catanet Model for Internetworking&quot;
by Vint Cerf talks about the Internet as being a collection of gateways
with interfaces to local networks. &nbsp;The local networks in turn provide
the higher layer with what looks like an IP link (even if it is tunneled
through the lower layer). &nbsp;And, discussions of internet protocols
in the 1970s and 1980s (before the 7-layer OSI model became the de facto
protocol model) talked about four layers: &nbsp;a Host/Application Layer,
a Transport Layer, an Internet Layer, and a Subnetwork/Local Networks Layer.
&nbsp;(For example, look at figure 1 in RFC 791 &quot;Internet Protocol&quot;
where 4 protocol layers are shown.) &nbsp;The subnet layer basically subsumes
the OSI Physical, Data Link, and SNAcP functionality. &nbsp;It was back
then that we started talking about layers 3A and 3B. &nbsp;Most say 3A
= Subnet and 3B = Internet (although others say the opposite: 3A = Internet
and 3B = Subnet).</tt></font>
<br>
<br><font size=2><tt>Anyway, the point is that both the traditional OSI
and the Internet protocol architectures assume that routing may occur at
multiple layers.</tt></font>
<br>
<br><font size=2><tt>And, when we think about wireline networks, I never
see/hear arguments that MPLS/VPLS violates layering because routing is
performed below IP. &nbsp;So why do we argue about it in wireless networks.</tt></font>
<br>
<br>
<br><font size=2><tt>2. &nbsp;I believe an appropriate architecture for
MANETs includes two networking layers. &nbsp;The two layers are the Internet
Protocol layer and a wireless MANET layer.</tt></font>
<br>
<br><font size=2><tt>The Internet Protocol layer provides networking where
neighbors and links look nice and graph-like. &nbsp;In other words, the
links are independent(i.e. what happens on one link does not affect other
links contrary to wireless networks where transmissions on one link can
interfere or congest other links) and links are fairly reliable and stable.
&nbsp;And, the concept of a neighbor is straight forward. &nbsp;In addition,
the protocol suite is standardized and predicted to be stable on the scale
of decades.</tt></font>
<br>
<br><font size=2><tt>The wireless MANET layer provides networking where
neighbors and links are fuzzy and less graph-like. &nbsp;In other words,
the performance of one link may be dependent on that of other links (i.e.
what happens on one link can affect what happens on other links) and links
can operate in all manner of dynamic, and possibly poorly predictable ways.
&nbsp;And, the concept of a neighbor is more complicated. In addition,
the protocol suite may change as wireless technologies change - although
the protocol suite should provide a standard interface and service to the
upper IP layer.</tt></font>
<br>
<br><font size=2><tt>Thus, I believe that the MANET work should focus on
multiple layers like the original Internet model - namely the Internet
layer (which may have different routing hierarchical domains, but links
basically look nice and graph-theoretic-like) and Wireless Subnets that
may be just a star-like WLAN based around APs or may be full-blown mesh
subnetworks. </tt></font>
<br>
<br><font size=2><tt>In the MANETs that I am involved with, we do subnet
routing to (a) hide the link dynamics in the wireless subnets from the
Internet so that changes in subnet routes are hidden from the Internet,
(b) we found it more efficient (from a throughput, spectrum usage, and
responsiveness to RF dynamics) to adapt to the dynamics at the subnet -
analogous to how MPLS is more efficient than IP routing for wireline subnets,
(c) it allows us to do some nice information assurance defense in depth
protection mechanisms tailored to the particular wireless environment we
are operating in, and (d) it hides the evolving wireless technologies and
their cross-layer solutions from the more static IP networking.</tt></font>
<br>
<br><font size=2><tt>Jim Stevens<br>
<br>
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -<br>
James A. Stevens, PhD<br>
Chief Network Architect<br>
Rockwell Collins Government Systems</tt></font>
<br>
--=_alternative 0061537886257168_=--


--===============0419370354==
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

--===============0419370354==--




From manet-bounces@ietf.org Mon May 08 14:10:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdAAO-0005Ca-MC; Mon, 08 May 2006 14:09:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdAAN-0005CS-NB
	for manet@ietf.org; Mon, 08 May 2006 14:09:07 -0400
Received: from mlbe2k1.cs.myharris.net ([137.237.90.88])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdAAL-0007kK-Gy
	for manet@ietf.org; Mon, 08 May 2006 14:09:07 -0400
Received: from mail pickup service by mlbe2k1.cs.myharris.net with Microsoft
	SMTPSVC; Mon, 8 May 2006 14:09:00 -0400
Received: from mlbe2k5.cs.myharris.net ([192.107.153.229]) by
	mlbe2k1.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 8 May 2006 14:08:59 -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
Date: Mon, 8 May 2006 14:08:58 -0400
Message-ID: <5A11D9659A856A4AA8B1292A74D60BB7B7805B@mlbe2k5.cs.myharris.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: manet Digest, Vol 25, Issue 10
Thread-Index: AcZv4Qq53y7f6B6aSHGgMy59uG91gQC0EyBwAAWtubA=
From: "Kennedy, Robert" <rkenne01@harris.com>
To: <fred@cisco.com>, <daniel.byrne@adtran.com>, <kb@mitre.com>,
	<jomullen@ad.nmsu.edu>
X-OriginalArrivalTime: 08 May 2006 18:08:59.0038 (UTC)
	FILETIME=[7A797BE0:01C672CA]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 5d99cba2a085c3987933aa34e30e85ab
Cc: "Cain, Joseph" <jcain01@harris.com>, manet@ietf.org, "Windham,
	William" <wwindham@harris.com>
Subject: [manet] FW: manet Digest, Vol 25, Issue 10
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Suggest that those of you who are interested in the complex interplay of
so many factors that affect MANET, including "who is my neighbor", check
out the United States Patent and Trademark Office's Web site.  Once you
get to there, search for the term "Psiactive" (for networks, not gaming
or parapsychology) with the following patents pending application
numbers:  20040219909, 20040218582 and 20040218548.  These are quite
relevant to the discussions in your discussions.  Knowing what the
factors are is one thing.  Knowing how to handle the complexity of
assimilating all the relevant ones is much more difficult.  Knowing that
cross-layering is critical to MANET is a good start, but figuring out
how to intelligently fuse all this information is in general very
challenging -- especially when you know that your MANET has to interact
with many fixed and evolving network standards.

Robert A. Kennedy
Network Architect
Networks Technology Department
Government Communications Systems Division
Harris Corporation

-----Original Message-----
From: manet-request@ietf.org [mailto:manet-request@ietf.org]=20
Sent: Thursday, May 04, 2006 9:12 PM
To: manet@ietf.org
Subject: manet Digest, Vol 25, Issue 10

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: Re: MANET definition of a neighbor (Fred Baker)
   2. Re: Re: MANET definition of a neighbor (Kenneth Brayer)
   3. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   4. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   5. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   6. RE: Re: MANET definition of a neighbor (Mullen, John)
   7. Re: Re: MANET definition of a neighbor (Chip Elliott)
   8. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   9. MobiSys 2006 Call for Participation (Alec Wolman)


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

Message: 1
Date: Thu, 4 May 2006 13:47:07 -0700
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: DANIEL BYRNE <daniel.byrne@adtran.com>
Cc: manet@ietf.org
Message-ID: <B37D901B-48CB-4903-A9B2-AA986EACD5EC@cisco.com>
Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; =
format=3Dflowed


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will
> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the =20
table will result in the same table and consume a lot of power and =20
CPU while doing so. If something has changed but it is not relevant =20
to the communications I am involved in, it is the proverbial tree =20
falling in the forest - whether I adapt to the change or not has no =20
near term effect. And if there has been a change that affects my =20
communications (as end point or relay), any routing protocol I am =20
aware of will adapt to it anyway.

Why, specifically, does this accomplish anything?



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

Message: 2
Date: Thu, 04 May 2006 16:56:08 -0400
From: Kenneth Brayer <kb@mitre.org>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: Fred Baker <fred@cisco.com>
Cc: manet@ietf.org
Message-ID: <445A6A68.6040004@mitre.org>
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed

Fred
You need to look at the link over a long period of time. Ten minutes=20
stable may be the fluke.
Ken

Fred Baker wrote:

>
> On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:
>
>> Some real world MANETS deal with this by trying to eliminate the =20
>> problem through coding. THey give up usable channel capacity to =20
>> reduce the error rate and increase channel reliability.
>
>
> I think they all do. Even 802.11 does that.
>
> But there are longer term issues. A link that goes in and out every =20
> 60 seconds may have wonderful channel characteristics while it is in.

> If I have the option of one that has been stable for ten minutes and =20
> is otherwise comparable, though, I will opt for the latter ten times =20
> out of ten. It has a greater probability of being useful at the time =20
> I want to use it.


--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841




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

Message: 3
Date: Thu, 4 May 2006 15:59:45 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Fred Baker" <fred@cisco.com>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F0F@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?



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

Message: 4
Date: Thu, 4 May 2006 16:01:15 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Mullen, John" <jomullen@ad.nmsu.edu>,	<manet@ietf.org>
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F10@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

=20
Hi Dan,

The problem is that the node doesn't know which links are good and must
make intelligent guesses.  If you rebuild your table without reason to
suspect a route is bad, you will increase the risk of excluding a good
route or including a bad one.

- If you accidently include a bad route, it will be weeded out in the
next cycle or two.  The trick is to update fast enough so that the bad
routes don't have a lasting impact.



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

Message: 5
Date: Thu, 4 May 2006 16:03:00 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Fred Baker" <fred@cisco.com>,	"Kenneth Brayer" <kb@mitre.org>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F11@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

It only has better long term reliability.  A manet packet doesn't take
60 seconds to transmit, so you are looking for a very small window of
opportunity.  Statistically the differnce between the two links is very
small when considering the transmission time of the manet packet.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:42 PM
To: Kenneth Brayer
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:

> Some real world MANETS deal with this by trying to eliminate the=20
> problem through coding. THey give up usable channel capacity to reduce

> the error rate and increase channel reliability.

I think they all do. Even 802.11 does that.

But there are longer term issues. A link that goes in and out every 60
seconds may have wonderful channel characteristics while it is in. =20
If I have the option of one that has been stable for ten minutes and is
otherwise comparable, though, I will opt for the latter ten times out of
ten. It has a greater probability of being useful at the time I want to
use it.

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



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

Message: 6
Date: Thu, 4 May 2006 15:14:18 -0600
From: "Mullen, John" <jomullen@ad.nmsu.edu>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Cc: manet@ietf.org
Message-ID:
=09
<8536FDFA3AD04A49A15804915996569106DEF0FE@exchange1.ACN.ad.nmsu.edu>
Content-Type: text/plain;	charset=3D"us-ascii"

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



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

Message: 7
Date: Thu, 04 May 2006 17:47:36 -0400
From: Chip Elliott <celliott@bbn.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: <jasteven@rockwellcollins.com>,manet@ietf.org
Message-ID: <6.2.1.2.2.20060504174629.038a6ae0@127.0.0.1>
Content-Type: text/plain; charset=3D"us-ascii"; format=3Dflowed



I think Jim has stated the fundamental challenge with MANETs
very succinctly, and his comment is worth some reflection:

At 01:54 PM 5/4/2006, jasteven@rockwellcollins.com wrote:

>The definition of a neighbor is why wireless MANETs are so much more=20
>difficult than wireline networks.  In fact, one could say that the
problem=20
>of determining who is a MANET neighbor and controlling the link to
MANET=20
>neighbors sums up the problems and complexities associated with MANETs
-=20
>at least to a first order approximation!

 From my own perspective, even the term "link" can lead to
great mental confusion. And once one relies on simulations where
everyone within range has 100% reception, and everyone outside
a range has 0%, one has missed most of what makes a
real MANET so challenging.

Mobility adds more complexity, but the probabilistic,
self-noisy, shared channel is the core problem, I think. And as
Jim points out, layering doesn't help and can even hurt.

Nice statement of the problem, Jim.

Chip Elliott
Principal Engineer, BBN=20




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

Message: 8
Date: Thu, 4 May 2006 16:48:57 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Mullen, John" <jomullen@ad.nmsu.edu>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F12@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

Yeah, I agree, an AGC is a better analog and better solution.  Basically
low pass the table through constant sampling.=20

-----Original Message-----
From: Mullen, John [mailto:jomullen@ad.nmsu.edu]=20
Sent: Thursday, May 04, 2006 4:14 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



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

Message: 9
Date: Thu, 4 May 2006 18:11:36 -0700
From: "Alec Wolman" <alec.wolman@hotmail.com>
Subject: [manet] MobiSys 2006 Call for Participation
To: <manet@ietf.org>
Message-ID: <BAY116-W3149F02EAD192A9051E17FCB50@phx.gbl>
Content-Type: text/plain; charset=3D"iso-8859-1"

***************************
Call for participation
MobiSys 2006 - The Fourth International Conference on Mobile Systems,
Applications, and Services
Uppsala, Sweden, June 19-22, 2006.
***************************
=20
The advance registration deadline for MobiSys 2006 is fast approaching:
*May 15th, 2006*
=20
See the MobiSys website -
http://www.sigmobile.org/mobisys/2006/index.html for details on the
program and registration information.
=20
_________________________________________________________________
Join the next generation of Hotmail and you could win the adventure of a
lifetime
http://www.imagine-msn.com/minisites/sweepstakes/mail/register.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www1.ietf.org/pipermail/manet/attachments/20060504/fab7e2ac/attac
hment.html

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

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


End of manet Digest, Vol 25, Issue 10
*************************************

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



From manet-bounces@ietf.org Mon May 08 14:16:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdAHI-0006pP-Cw; Mon, 08 May 2006 14:16:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdAHH-0006pK-LT
	for manet@ietf.org; Mon, 08 May 2006 14:16:15 -0400
Received: from ext-ch1gw-3.online-age.net ([216.34.191.37])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdAHF-0007wJ-Ph
	for manet@ietf.org; Mon, 08 May 2006 14:16:15 -0400
Received: from int-ch1gw-2.online-age.net (int-ch1gw-2 [3.159.232.66])
	by ext-ch1gw-3.online-age.net (8.13.6/8.13.6/20051111-SVVS-TLS-DNSBL)
	with ESMTP id k48IFvET011467
	for <manet@ietf.org>; Mon, 8 May 2006 14:15:58 -0400 (EDT)
Received: from cinmlef10.e2k.ad.ge.com (localhost [127.0.0.1])
	by int-ch1gw-2.online-age.net (8.12.9/8.12.3/990426-RLH) with ESMTP id
	k48IFuPd004823
	for <manet@ietf.org>; Mon, 8 May 2006 14:15:56 -0400 (EDT)
Received: from SCHMLVEM01.e2k.ad.ge.com ([3.159.168.31]) by
	cinmlef10.e2k.ad.ge.com with Microsoft SMTPSVC(6.0.3790.2499); 
	Mon, 8 May 2006 14:15:55 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [manet] FW: manet Digest, Vol 25, Issue 10
Date: Mon, 8 May 2006 14:15:53 -0400
Message-ID: <FA26BEF1EA775E4584FB34B91E14A1C407E94350@SCHMLVEM01.e2k.ad.ge.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: manet Digest, Vol 25, Issue 10
Thread-Index: AcZv4Qq53y7f6B6aSHGgMy59uG91gQC0EyBwAAWtubAAAMgnUA==
From: "Bush, Stephen F \(GE, Research\)" <bushsf@research.ge.com>
To: "Kennedy, Robert" <rkenne01@harris.com>, <fred@cisco.com>,
	<daniel.byrne@adtran.com>, <kb@mitre.com>, <jomullen@ad.nmsu.edu>
X-OriginalArrivalTime: 08 May 2006 18:15:55.0723 (UTC)
	FILETIME=[72D691B0:01C672CB]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ce0328cdf9c90e4680655d09dccace5
Cc: "Cain, Joseph" <jcain01@harris.com>, manet@ietf.org, "Windham,
	William" <wwindham@harris.com>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


Robert,

As I recall, Psiactive gets into predictive routing aspects, does it =
not?

Thanks,
Stephen F Bush (http://www.research.ge.com/~bushsf)


-----Original Message-----
From: Kennedy, Robert [mailto:rkenne01@harris.com]
Sent: Monday, May 08, 2006 2:09 PM
To: fred@cisco.com; daniel.byrne@adtran.com; kb@mitre.com;
jomullen@ad.nmsu.edu
Cc: Cain, Joseph; manet@ietf.org; Windham,William
Subject: [manet] FW: manet Digest, Vol 25, Issue 10


Suggest that those of you who are interested in the complex interplay of
so many factors that affect MANET, including "who is my neighbor", check
out the United States Patent and Trademark Office's Web site.  Once you
get to there, search for the term "Psiactive" (for networks, not gaming
or parapsychology) with the following patents pending application
numbers:  20040219909, 20040218582 and 20040218548.  These are quite
relevant to the discussions in your discussions.  Knowing what the
factors are is one thing.  Knowing how to handle the complexity of
assimilating all the relevant ones is much more difficult.  Knowing that
cross-layering is critical to MANET is a good start, but figuring out
how to intelligently fuse all this information is in general very
challenging -- especially when you know that your MANET has to interact
with many fixed and evolving network standards.

Robert A. Kennedy
Network Architect
Networks Technology Department
Government Communications Systems Division
Harris Corporation

-----Original Message-----
From: manet-request@ietf.org [mailto:manet-request@ietf.org]=20
Sent: Thursday, May 04, 2006 9:12 PM
To: manet@ietf.org
Subject: manet Digest, Vol 25, Issue 10

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: Re: MANET definition of a neighbor (Fred Baker)
   2. Re: Re: MANET definition of a neighbor (Kenneth Brayer)
   3. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   4. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   5. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   6. RE: Re: MANET definition of a neighbor (Mullen, John)
   7. Re: Re: MANET definition of a neighbor (Chip Elliott)
   8. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   9. MobiSys 2006 Call for Participation (Alec Wolman)


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

Message: 1
Date: Thu, 4 May 2006 13:47:07 -0700
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: DANIEL BYRNE <daniel.byrne@adtran.com>
Cc: manet@ietf.org
Message-ID: <B37D901B-48CB-4903-A9B2-AA986EACD5EC@cisco.com>
Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; =
format=3Dflowed


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will
> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the =20
table will result in the same table and consume a lot of power and =20
CPU while doing so. If something has changed but it is not relevant =20
to the communications I am involved in, it is the proverbial tree =20
falling in the forest - whether I adapt to the change or not has no =20
near term effect. And if there has been a change that affects my =20
communications (as end point or relay), any routing protocol I am =20
aware of will adapt to it anyway.

Why, specifically, does this accomplish anything?



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

Message: 2
Date: Thu, 04 May 2006 16:56:08 -0400
From: Kenneth Brayer <kb@mitre.org>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: Fred Baker <fred@cisco.com>
Cc: manet@ietf.org
Message-ID: <445A6A68.6040004@mitre.org>
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed

Fred
You need to look at the link over a long period of time. Ten minutes=20
stable may be the fluke.
Ken

Fred Baker wrote:

>
> On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:
>
>> Some real world MANETS deal with this by trying to eliminate the =20
>> problem through coding. THey give up usable channel capacity to =20
>> reduce the error rate and increase channel reliability.
>
>
> I think they all do. Even 802.11 does that.
>
> But there are longer term issues. A link that goes in and out every =20
> 60 seconds may have wonderful channel characteristics while it is in.

> If I have the option of one that has been stable for ten minutes and =20
> is otherwise comparable, though, I will opt for the latter ten times =20
> out of ten. It has a greater probability of being useful at the time =20
> I want to use it.


--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841




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

Message: 3
Date: Thu, 4 May 2006 15:59:45 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Fred Baker" <fred@cisco.com>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F0F@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?



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

Message: 4
Date: Thu, 4 May 2006 16:01:15 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Mullen, John" <jomullen@ad.nmsu.edu>,	<manet@ietf.org>
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F10@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

=20
Hi Dan,

The problem is that the node doesn't know which links are good and must
make intelligent guesses.  If you rebuild your table without reason to
suspect a route is bad, you will increase the risk of excluding a good
route or including a bad one.

- If you accidently include a bad route, it will be weeded out in the
next cycle or two.  The trick is to update fast enough so that the bad
routes don't have a lasting impact.



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

Message: 5
Date: Thu, 4 May 2006 16:03:00 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Fred Baker" <fred@cisco.com>,	"Kenneth Brayer" <kb@mitre.org>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F11@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

It only has better long term reliability.  A manet packet doesn't take
60 seconds to transmit, so you are looking for a very small window of
opportunity.  Statistically the differnce between the two links is very
small when considering the transmission time of the manet packet.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:42 PM
To: Kenneth Brayer
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:

> Some real world MANETS deal with this by trying to eliminate the=20
> problem through coding. THey give up usable channel capacity to reduce

> the error rate and increase channel reliability.

I think they all do. Even 802.11 does that.

But there are longer term issues. A link that goes in and out every 60
seconds may have wonderful channel characteristics while it is in. =20
If I have the option of one that has been stable for ten minutes and is
otherwise comparable, though, I will opt for the latter ten times out of
ten. It has a greater probability of being useful at the time I want to
use it.

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



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

Message: 6
Date: Thu, 4 May 2006 15:14:18 -0600
From: "Mullen, John" <jomullen@ad.nmsu.edu>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Cc: manet@ietf.org
Message-ID:
=09
<8536FDFA3AD04A49A15804915996569106DEF0FE@exchange1.ACN.ad.nmsu.edu>
Content-Type: text/plain;	charset=3D"us-ascii"

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



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

Message: 7
Date: Thu, 04 May 2006 17:47:36 -0400
From: Chip Elliott <celliott@bbn.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: <jasteven@rockwellcollins.com>,manet@ietf.org
Message-ID: <6.2.1.2.2.20060504174629.038a6ae0@127.0.0.1>
Content-Type: text/plain; charset=3D"us-ascii"; format=3Dflowed



I think Jim has stated the fundamental challenge with MANETs
very succinctly, and his comment is worth some reflection:

At 01:54 PM 5/4/2006, jasteven@rockwellcollins.com wrote:

>The definition of a neighbor is why wireless MANETs are so much more=20
>difficult than wireline networks.  In fact, one could say that the
problem=20
>of determining who is a MANET neighbor and controlling the link to
MANET=20
>neighbors sums up the problems and complexities associated with MANETs
-=20
>at least to a first order approximation!

 From my own perspective, even the term "link" can lead to
great mental confusion. And once one relies on simulations where
everyone within range has 100% reception, and everyone outside
a range has 0%, one has missed most of what makes a
real MANET so challenging.

Mobility adds more complexity, but the probabilistic,
self-noisy, shared channel is the core problem, I think. And as
Jim points out, layering doesn't help and can even hurt.

Nice statement of the problem, Jim.

Chip Elliott
Principal Engineer, BBN=20




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

Message: 8
Date: Thu, 4 May 2006 16:48:57 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Mullen, John" <jomullen@ad.nmsu.edu>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F12@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

Yeah, I agree, an AGC is a better analog and better solution.  Basically
low pass the table through constant sampling.=20

-----Original Message-----
From: Mullen, John [mailto:jomullen@ad.nmsu.edu]=20
Sent: Thursday, May 04, 2006 4:14 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



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

Message: 9
Date: Thu, 4 May 2006 18:11:36 -0700
From: "Alec Wolman" <alec.wolman@hotmail.com>
Subject: [manet] MobiSys 2006 Call for Participation
To: <manet@ietf.org>
Message-ID: <BAY116-W3149F02EAD192A9051E17FCB50@phx.gbl>
Content-Type: text/plain; charset=3D"iso-8859-1"

***************************
Call for participation
MobiSys 2006 - The Fourth International Conference on Mobile Systems,
Applications, and Services
Uppsala, Sweden, June 19-22, 2006.
***************************
=20
The advance registration deadline for MobiSys 2006 is fast approaching:
*May 15th, 2006*
=20
See the MobiSys website -
http://www.sigmobile.org/mobisys/2006/index.html for details on the
program and registration information.
=20
_________________________________________________________________
Join the next generation of Hotmail and you could win the adventure of a
lifetime
http://www.imagine-msn.com/minisites/sweepstakes/mail/register.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www1.ietf.org/pipermail/manet/attachments/20060504/fab7e2ac/attac
hment.html

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

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


End of manet Digest, Vol 25, Issue 10
*************************************

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

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



From manet-bounces@ietf.org Mon May 08 14:17:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdAIp-000787-CZ; Mon, 08 May 2006 14:17:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdAIn-00077x-Bn
	for manet@ietf.org; Mon, 08 May 2006 14:17:49 -0400
Received: from mlbe2k1.cs.myharris.net ([137.237.90.88])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdAIm-0007yG-FV
	for manet@ietf.org; Mon, 08 May 2006 14:17:49 -0400
Received: from mail pickup service by mlbe2k1.cs.myharris.net with Microsoft
	SMTPSVC; Mon, 8 May 2006 14:17:47 -0400
Received: from mlbe2k5.cs.myharris.net ([192.107.153.229]) by
	mlbe2k1.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 8 May 2006 14:17:45 -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] FW: manet Digest, Vol 25, Issue 10
Date: Mon, 8 May 2006 14:17:44 -0400
Message-ID: <5A11D9659A856A4AA8B1292A74D60BB7B7805C@mlbe2k5.cs.myharris.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] FW: manet Digest, Vol 25, Issue 10
Thread-Index: AcZv4Qq53y7f6B6aSHGgMy59uG91gQC0EyBwAAWtubAAAMgnUAAAF0UQ
From: "Kennedy, Robert" <rkenne01@harris.com>
To: "Bush, Stephen F \(GE, Research\)" <bushsf@research.ge.com>,
	<fred@cisco.com>, <daniel.byrne@adtran.com>, <kb@mitre.com>,
	<jomullen@ad.nmsu.edu>
X-OriginalArrivalTime: 08 May 2006 18:17:45.0404 (UTC)
	FILETIME=[B4368FC0:01C672CB]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: b656e85d4d33f5403d96bac6146425d9
Cc: "Cain, Joseph" <jcain01@harris.com>, manet@ietf.org, "Windham,
	William" <wwindham@harris.com>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Stephen,

Yes, that is correct.

Robert=20

-----Original Message-----
From: Bush, Stephen F (GE, Research) [mailto:bushsf@research.ge.com]=20
Sent: Monday, May 08, 2006 2:16 PM
To: Kennedy, Robert; fred@cisco.com; daniel.byrne@adtran.com;
kb@mitre.com; jomullen@ad.nmsu.edu
Cc: Cain, Joseph; manet@ietf.org; Windham, William
Subject: RE: [manet] FW: manet Digest, Vol 25, Issue 10


Robert,

As I recall, Psiactive gets into predictive routing aspects, does it
not?

Thanks,
Stephen F Bush (http://www.research.ge.com/~bushsf)


-----Original Message-----
From: Kennedy, Robert [mailto:rkenne01@harris.com]
Sent: Monday, May 08, 2006 2:09 PM
To: fred@cisco.com; daniel.byrne@adtran.com; kb@mitre.com;
jomullen@ad.nmsu.edu
Cc: Cain, Joseph; manet@ietf.org; Windham,William
Subject: [manet] FW: manet Digest, Vol 25, Issue 10


Suggest that those of you who are interested in the complex interplay of
so many factors that affect MANET, including "who is my neighbor", check
out the United States Patent and Trademark Office's Web site.  Once you
get to there, search for the term "Psiactive" (for networks, not gaming
or parapsychology) with the following patents pending application
numbers:  20040219909, 20040218582 and 20040218548.  These are quite
relevant to the discussions in your discussions.  Knowing what the
factors are is one thing.  Knowing how to handle the complexity of
assimilating all the relevant ones is much more difficult.  Knowing that
cross-layering is critical to MANET is a good start, but figuring out
how to intelligently fuse all this information is in general very
challenging -- especially when you know that your MANET has to interact
with many fixed and evolving network standards.

Robert A. Kennedy
Network Architect
Networks Technology Department
Government Communications Systems Division
Harris Corporation

-----Original Message-----
From: manet-request@ietf.org [mailto:manet-request@ietf.org]=20
Sent: Thursday, May 04, 2006 9:12 PM
To: manet@ietf.org
Subject: manet Digest, Vol 25, Issue 10

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: Re: MANET definition of a neighbor (Fred Baker)
   2. Re: Re: MANET definition of a neighbor (Kenneth Brayer)
   3. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   4. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   5. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   6. RE: Re: MANET definition of a neighbor (Mullen, John)
   7. Re: Re: MANET definition of a neighbor (Chip Elliott)
   8. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   9. MobiSys 2006 Call for Participation (Alec Wolman)


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

Message: 1
Date: Thu, 4 May 2006 13:47:07 -0700
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: DANIEL BYRNE <daniel.byrne@adtran.com>
Cc: manet@ietf.org
Message-ID: <B37D901B-48CB-4903-A9B2-AA986EACD5EC@cisco.com>
Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; =
format=3Dflowed


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will
> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the =20
table will result in the same table and consume a lot of power and =20
CPU while doing so. If something has changed but it is not relevant =20
to the communications I am involved in, it is the proverbial tree =20
falling in the forest - whether I adapt to the change or not has no =20
near term effect. And if there has been a change that affects my =20
communications (as end point or relay), any routing protocol I am =20
aware of will adapt to it anyway.

Why, specifically, does this accomplish anything?



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

Message: 2
Date: Thu, 04 May 2006 16:56:08 -0400
From: Kenneth Brayer <kb@mitre.org>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: Fred Baker <fred@cisco.com>
Cc: manet@ietf.org
Message-ID: <445A6A68.6040004@mitre.org>
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed

Fred
You need to look at the link over a long period of time. Ten minutes=20
stable may be the fluke.
Ken

Fred Baker wrote:

>
> On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:
>
>> Some real world MANETS deal with this by trying to eliminate the =20
>> problem through coding. THey give up usable channel capacity to =20
>> reduce the error rate and increase channel reliability.
>
>
> I think they all do. Even 802.11 does that.
>
> But there are longer term issues. A link that goes in and out every =20
> 60 seconds may have wonderful channel characteristics while it is in.

> If I have the option of one that has been stable for ten minutes and =20
> is otherwise comparable, though, I will opt for the latter ten times =20
> out of ten. It has a greater probability of being useful at the time =20
> I want to use it.


--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841




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

Message: 3
Date: Thu, 4 May 2006 15:59:45 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Fred Baker" <fred@cisco.com>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F0F@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?



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

Message: 4
Date: Thu, 4 May 2006 16:01:15 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Mullen, John" <jomullen@ad.nmsu.edu>,	<manet@ietf.org>
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F10@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

=20
Hi Dan,

The problem is that the node doesn't know which links are good and must
make intelligent guesses.  If you rebuild your table without reason to
suspect a route is bad, you will increase the risk of excluding a good
route or including a bad one.

- If you accidently include a bad route, it will be weeded out in the
next cycle or two.  The trick is to update fast enough so that the bad
routes don't have a lasting impact.



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

Message: 5
Date: Thu, 4 May 2006 16:03:00 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Fred Baker" <fred@cisco.com>,	"Kenneth Brayer" <kb@mitre.org>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F11@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

It only has better long term reliability.  A manet packet doesn't take
60 seconds to transmit, so you are looking for a very small window of
opportunity.  Statistically the differnce between the two links is very
small when considering the transmission time of the manet packet.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:42 PM
To: Kenneth Brayer
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:

> Some real world MANETS deal with this by trying to eliminate the=20
> problem through coding. THey give up usable channel capacity to reduce

> the error rate and increase channel reliability.

I think they all do. Even 802.11 does that.

But there are longer term issues. A link that goes in and out every 60
seconds may have wonderful channel characteristics while it is in. =20
If I have the option of one that has been stable for ten minutes and is
otherwise comparable, though, I will opt for the latter ten times out of
ten. It has a greater probability of being useful at the time I want to
use it.

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



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

Message: 6
Date: Thu, 4 May 2006 15:14:18 -0600
From: "Mullen, John" <jomullen@ad.nmsu.edu>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Cc: manet@ietf.org
Message-ID:
=09
<8536FDFA3AD04A49A15804915996569106DEF0FE@exchange1.ACN.ad.nmsu.edu>
Content-Type: text/plain;	charset=3D"us-ascii"

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



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

Message: 7
Date: Thu, 04 May 2006 17:47:36 -0400
From: Chip Elliott <celliott@bbn.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: <jasteven@rockwellcollins.com>,manet@ietf.org
Message-ID: <6.2.1.2.2.20060504174629.038a6ae0@127.0.0.1>
Content-Type: text/plain; charset=3D"us-ascii"; format=3Dflowed



I think Jim has stated the fundamental challenge with MANETs
very succinctly, and his comment is worth some reflection:

At 01:54 PM 5/4/2006, jasteven@rockwellcollins.com wrote:

>The definition of a neighbor is why wireless MANETs are so much more=20
>difficult than wireline networks.  In fact, one could say that the
problem=20
>of determining who is a MANET neighbor and controlling the link to
MANET=20
>neighbors sums up the problems and complexities associated with MANETs
-=20
>at least to a first order approximation!

 From my own perspective, even the term "link" can lead to
great mental confusion. And once one relies on simulations where
everyone within range has 100% reception, and everyone outside
a range has 0%, one has missed most of what makes a
real MANET so challenging.

Mobility adds more complexity, but the probabilistic,
self-noisy, shared channel is the core problem, I think. And as
Jim points out, layering doesn't help and can even hurt.

Nice statement of the problem, Jim.

Chip Elliott
Principal Engineer, BBN=20




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

Message: 8
Date: Thu, 4 May 2006 16:48:57 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Mullen, John" <jomullen@ad.nmsu.edu>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F12@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

Yeah, I agree, an AGC is a better analog and better solution.  Basically
low pass the table through constant sampling.=20

-----Original Message-----
From: Mullen, John [mailto:jomullen@ad.nmsu.edu]=20
Sent: Thursday, May 04, 2006 4:14 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



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

Message: 9
Date: Thu, 4 May 2006 18:11:36 -0700
From: "Alec Wolman" <alec.wolman@hotmail.com>
Subject: [manet] MobiSys 2006 Call for Participation
To: <manet@ietf.org>
Message-ID: <BAY116-W3149F02EAD192A9051E17FCB50@phx.gbl>
Content-Type: text/plain; charset=3D"iso-8859-1"

***************************
Call for participation
MobiSys 2006 - The Fourth International Conference on Mobile Systems,
Applications, and Services
Uppsala, Sweden, June 19-22, 2006.
***************************
=20
The advance registration deadline for MobiSys 2006 is fast approaching:
*May 15th, 2006*
=20
See the MobiSys website -
http://www.sigmobile.org/mobisys/2006/index.html for details on the
program and registration information.
=20
_________________________________________________________________
Join the next generation of Hotmail and you could win the adventure of a
lifetime
http://www.imagine-msn.com/minisites/sweepstakes/mail/register.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www1.ietf.org/pipermail/manet/attachments/20060504/fab7e2ac/attac
hment.html

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

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


End of manet Digest, Vol 25, Issue 10
*************************************

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

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



From manet-bounces@ietf.org Mon May 08 15:31:22 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdBRE-0007Vv-6m; Mon, 08 May 2006 15:30:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdBRC-0007Vq-M5
	for manet@ietf.org; Mon, 08 May 2006 15:30:34 -0400
Received: from mlbe2k1.cs.myharris.net ([137.237.90.88])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdBRA-0002zT-PN
	for manet@ietf.org; Mon, 08 May 2006 15:30:34 -0400
Received: from mail pickup service by mlbe2k1.cs.myharris.net with Microsoft
	SMTPSVC; Mon, 8 May 2006 15:30:31 -0400
Received: from mlbe2k5.cs.myharris.net ([192.107.153.229]) by
	mlbe2k1.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 8 May 2006 15:30:30 -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] FW: manet Digest, Vol 25, Issue 10
Date: Mon, 8 May 2006 15:30:30 -0400
Message-ID: <5A11D9659A856A4AA8B1292A74D60BB7B7805D@mlbe2k5.cs.myharris.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] FW: manet Digest, Vol 25, Issue 10
Thread-Index: AcZv4Qq53y7f6B6aSHGgMy59uG91gQC0EyBwAAWtubAAAMgnUAACZHmw
From: "Kennedy, Robert" <rkenne01@harris.com>
To: "Bush, Stephen F \(GE, Research\)" <bushsf@research.ge.com>,
	<fred@cisco.com>, <daniel.byrne@adtran.com>, <kb@mitre.com>,
	<jomullen@ad.nmsu.edu>
X-OriginalArrivalTime: 08 May 2006 19:30:30.0814 (UTC)
	FILETIME=[DE3343E0:01C672D5]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 645960076aa293effd9740db2f975dc3
Cc: "Cain, Joseph" <jcain01@harris.com>, manet@ietf.org, "Windham,
	William" <wwindham@harris.com>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

In a dynamical system (a MANET certainly fits that category), there are
some larger questions to answer other than just who IS my neighbor.  Who
WILL BE my neighbor when I need them?  How good a neighbor will they be?
Are they going to stay long or are they just transients?  An associated
question is who will be my neighbors' neighbors when I need them?  Are
my neighbors stable?  Will they talk when I want to talk?  The
principles in Psiactive Routing address a lot of dynamical networking
concerns.

Robert Kennedy

-----Original Message-----
From: Bush, Stephen F (GE, Research) [mailto:bushsf@research.ge.com]=20
Sent: Monday, May 08, 2006 2:16 PM
To: Kennedy, Robert; fred@cisco.com; daniel.byrne@adtran.com;
kb@mitre.com; jomullen@ad.nmsu.edu
Cc: Cain, Joseph; manet@ietf.org; Windham, William
Subject: RE: [manet] FW: manet Digest, Vol 25, Issue 10


Robert,

As I recall, Psiactive gets into predictive routing aspects, does it
not?

Thanks,
Stephen F Bush (http://www.research.ge.com/~bushsf)


-----Original Message-----
From: Kennedy, Robert [mailto:rkenne01@harris.com]
Sent: Monday, May 08, 2006 2:09 PM
To: fred@cisco.com; daniel.byrne@adtran.com; kb@mitre.com;
jomullen@ad.nmsu.edu
Cc: Cain, Joseph; manet@ietf.org; Windham,William
Subject: [manet] FW: manet Digest, Vol 25, Issue 10


Suggest that those of you who are interested in the complex interplay of
so many factors that affect MANET, including "who is my neighbor", check
out the United States Patent and Trademark Office's Web site.  Once you
get to there, search for the term "Psiactive" (for networks, not gaming
or parapsychology) with the following patents pending application
numbers:  20040219909, 20040218582 and 20040218548.  These are quite
relevant to the discussions in your discussions.  Knowing what the
factors are is one thing.  Knowing how to handle the complexity of
assimilating all the relevant ones is much more difficult.  Knowing that
cross-layering is critical to MANET is a good start, but figuring out
how to intelligently fuse all this information is in general very
challenging -- especially when you know that your MANET has to interact
with many fixed and evolving network standards.

Robert A. Kennedy
Network Architect
Networks Technology Department
Government Communications Systems Division
Harris Corporation

-----Original Message-----
From: manet-request@ietf.org [mailto:manet-request@ietf.org]=20
Sent: Thursday, May 04, 2006 9:12 PM
To: manet@ietf.org
Subject: manet Digest, Vol 25, Issue 10

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: Re: MANET definition of a neighbor (Fred Baker)
   2. Re: Re: MANET definition of a neighbor (Kenneth Brayer)
   3. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   4. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   5. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   6. RE: Re: MANET definition of a neighbor (Mullen, John)
   7. Re: Re: MANET definition of a neighbor (Chip Elliott)
   8. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   9. MobiSys 2006 Call for Participation (Alec Wolman)


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

Message: 1
Date: Thu, 4 May 2006 13:47:07 -0700
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: DANIEL BYRNE <daniel.byrne@adtran.com>
Cc: manet@ietf.org
Message-ID: <B37D901B-48CB-4903-A9B2-AA986EACD5EC@cisco.com>
Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; =
format=3Dflowed


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will
> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the =20
table will result in the same table and consume a lot of power and =20
CPU while doing so. If something has changed but it is not relevant =20
to the communications I am involved in, it is the proverbial tree =20
falling in the forest - whether I adapt to the change or not has no =20
near term effect. And if there has been a change that affects my =20
communications (as end point or relay), any routing protocol I am =20
aware of will adapt to it anyway.

Why, specifically, does this accomplish anything?



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

Message: 2
Date: Thu, 04 May 2006 16:56:08 -0400
From: Kenneth Brayer <kb@mitre.org>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: Fred Baker <fred@cisco.com>
Cc: manet@ietf.org
Message-ID: <445A6A68.6040004@mitre.org>
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed

Fred
You need to look at the link over a long period of time. Ten minutes=20
stable may be the fluke.
Ken

Fred Baker wrote:

>
> On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:
>
>> Some real world MANETS deal with this by trying to eliminate the =20
>> problem through coding. THey give up usable channel capacity to =20
>> reduce the error rate and increase channel reliability.
>
>
> I think they all do. Even 802.11 does that.
>
> But there are longer term issues. A link that goes in and out every =20
> 60 seconds may have wonderful channel characteristics while it is in.

> If I have the option of one that has been stable for ten minutes and =20
> is otherwise comparable, though, I will opt for the latter ten times =20
> out of ten. It has a greater probability of being useful at the time =20
> I want to use it.


--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841




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

Message: 3
Date: Thu, 4 May 2006 15:59:45 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Fred Baker" <fred@cisco.com>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F0F@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?



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

Message: 4
Date: Thu, 4 May 2006 16:01:15 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Mullen, John" <jomullen@ad.nmsu.edu>,	<manet@ietf.org>
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F10@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

=20
Hi Dan,

The problem is that the node doesn't know which links are good and must
make intelligent guesses.  If you rebuild your table without reason to
suspect a route is bad, you will increase the risk of excluding a good
route or including a bad one.

- If you accidently include a bad route, it will be weeded out in the
next cycle or two.  The trick is to update fast enough so that the bad
routes don't have a lasting impact.



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

Message: 5
Date: Thu, 4 May 2006 16:03:00 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Fred Baker" <fred@cisco.com>,	"Kenneth Brayer" <kb@mitre.org>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F11@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

It only has better long term reliability.  A manet packet doesn't take
60 seconds to transmit, so you are looking for a very small window of
opportunity.  Statistically the differnce between the two links is very
small when considering the transmission time of the manet packet.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:42 PM
To: Kenneth Brayer
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:

> Some real world MANETS deal with this by trying to eliminate the=20
> problem through coding. THey give up usable channel capacity to reduce

> the error rate and increase channel reliability.

I think they all do. Even 802.11 does that.

But there are longer term issues. A link that goes in and out every 60
seconds may have wonderful channel characteristics while it is in. =20
If I have the option of one that has been stable for ten minutes and is
otherwise comparable, though, I will opt for the latter ten times out of
ten. It has a greater probability of being useful at the time I want to
use it.

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



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

Message: 6
Date: Thu, 4 May 2006 15:14:18 -0600
From: "Mullen, John" <jomullen@ad.nmsu.edu>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Cc: manet@ietf.org
Message-ID:
=09
<8536FDFA3AD04A49A15804915996569106DEF0FE@exchange1.ACN.ad.nmsu.edu>
Content-Type: text/plain;	charset=3D"us-ascii"

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



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

Message: 7
Date: Thu, 04 May 2006 17:47:36 -0400
From: Chip Elliott <celliott@bbn.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: <jasteven@rockwellcollins.com>,manet@ietf.org
Message-ID: <6.2.1.2.2.20060504174629.038a6ae0@127.0.0.1>
Content-Type: text/plain; charset=3D"us-ascii"; format=3Dflowed



I think Jim has stated the fundamental challenge with MANETs
very succinctly, and his comment is worth some reflection:

At 01:54 PM 5/4/2006, jasteven@rockwellcollins.com wrote:

>The definition of a neighbor is why wireless MANETs are so much more=20
>difficult than wireline networks.  In fact, one could say that the
problem=20
>of determining who is a MANET neighbor and controlling the link to
MANET=20
>neighbors sums up the problems and complexities associated with MANETs
-=20
>at least to a first order approximation!

 From my own perspective, even the term "link" can lead to
great mental confusion. And once one relies on simulations where
everyone within range has 100% reception, and everyone outside
a range has 0%, one has missed most of what makes a
real MANET so challenging.

Mobility adds more complexity, but the probabilistic,
self-noisy, shared channel is the core problem, I think. And as
Jim points out, layering doesn't help and can even hurt.

Nice statement of the problem, Jim.

Chip Elliott
Principal Engineer, BBN=20




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

Message: 8
Date: Thu, 4 May 2006 16:48:57 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Mullen, John" <jomullen@ad.nmsu.edu>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F12@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

Yeah, I agree, an AGC is a better analog and better solution.  Basically
low pass the table through constant sampling.=20

-----Original Message-----
From: Mullen, John [mailto:jomullen@ad.nmsu.edu]=20
Sent: Thursday, May 04, 2006 4:14 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



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

Message: 9
Date: Thu, 4 May 2006 18:11:36 -0700
From: "Alec Wolman" <alec.wolman@hotmail.com>
Subject: [manet] MobiSys 2006 Call for Participation
To: <manet@ietf.org>
Message-ID: <BAY116-W3149F02EAD192A9051E17FCB50@phx.gbl>
Content-Type: text/plain; charset=3D"iso-8859-1"

***************************
Call for participation
MobiSys 2006 - The Fourth International Conference on Mobile Systems,
Applications, and Services
Uppsala, Sweden, June 19-22, 2006.
***************************
=20
The advance registration deadline for MobiSys 2006 is fast approaching:
*May 15th, 2006*
=20
See the MobiSys website -
http://www.sigmobile.org/mobisys/2006/index.html for details on the
program and registration information.
=20
_________________________________________________________________
Join the next generation of Hotmail and you could win the adventure of a
lifetime
http://www.imagine-msn.com/minisites/sweepstakes/mail/register.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www1.ietf.org/pipermail/manet/attachments/20060504/fab7e2ac/attac
hment.html

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

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


End of manet Digest, Vol 25, Issue 10
*************************************

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

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



From manet-bounces@ietf.org Mon May 08 15:34:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdBV9-00082N-2r; Mon, 08 May 2006 15:34:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdBV8-00082I-GL
	for manet@ietf.org; Mon, 08 May 2006 15:34:38 -0400
Received: from ext-ch1gw-8.online-age.net ([64.37.194.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdBV7-0003BC-Ih
	for manet@ietf.org; Mon, 08 May 2006 15:34:38 -0400
Received: from int-ch1gw-4.online-age.net (int-ch1gw-4 [3.159.232.68])
	by ext-ch1gw-8.online-age.net (8.13.6/8.13.6/20051111-SVVS-TLS-DNSBL)
	with ESMTP id k48JYXYU031956
	for <manet@ietf.org>; Mon, 8 May 2006 15:34:33 -0400
Received: from cinmlef06.e2k.ad.ge.com (localhost [127.0.0.1])
	by int-ch1gw-4.online-age.net (8.12.9/8.12.3/990426-RLH) with ESMTP id
	k48JYV1E005448
	for <manet@ietf.org>; Mon, 8 May 2006 15:34:32 -0400 (EDT)
Received: from SCHMLVEM01.e2k.ad.ge.com ([3.159.168.31]) by
	cinmlef06.e2k.ad.ge.com with Microsoft SMTPSVC(6.0.3790.2499); 
	Mon, 8 May 2006 15:34:31 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [manet] FW: manet Digest, Vol 25, Issue 10
Date: Mon, 8 May 2006 15:34:30 -0400
Message-ID: <FA26BEF1EA775E4584FB34B91E14A1C407E94355@SCHMLVEM01.e2k.ad.ge.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] FW: manet Digest, Vol 25, Issue 10
Thread-Index: AcZv4Qq53y7f6B6aSHGgMy59uG91gQC0EyBwAAWtubAAAMgnUAACZHmwAABko+A=
From: "Bush, Stephen F \(GE, Research\)" <bushsf@research.ge.com>
To: "Kennedy, Robert" <rkenne01@harris.com>, <fred@cisco.com>,
	<daniel.byrne@adtran.com>, <kb@mitre.com>, <jomullen@ad.nmsu.edu>
X-OriginalArrivalTime: 08 May 2006 19:34:31.0231 (UTC)
	FILETIME=[6D7FFCF0:01C672D6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 778b456acd32f555185589e04d062871
Cc: "Cain, Joseph" <jcain01@harris.com>, manet@ietf.org, "Windham,
	William" <wwindham@harris.com>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


Yes, I agree with this point.

Stephen F Bush (http://www.research.ge.com/~bushsf)



-----Original Message-----
From: Kennedy, Robert [mailto:rkenne01@harris.com]
Sent: Monday, May 08, 2006 3:31 PM
To: Bush, Stephen F (GE, Research); fred@cisco.com;
daniel.byrne@adtran.com; kb@mitre.com; jomullen@ad.nmsu.edu
Cc: Cain, Joseph; manet@ietf.org; Windham, William
Subject: RE: [manet] FW: manet Digest, Vol 25, Issue 10


In a dynamical system (a MANET certainly fits that category), there are
some larger questions to answer other than just who IS my neighbor.  Who
WILL BE my neighbor when I need them?  How good a neighbor will they be?
Are they going to stay long or are they just transients?  An associated
question is who will be my neighbors' neighbors when I need them?  Are
my neighbors stable?  Will they talk when I want to talk?  The
principles in Psiactive Routing address a lot of dynamical networking
concerns.

Robert Kennedy

-----Original Message-----
From: Bush, Stephen F (GE, Research) [mailto:bushsf@research.ge.com]=20
Sent: Monday, May 08, 2006 2:16 PM
To: Kennedy, Robert; fred@cisco.com; daniel.byrne@adtran.com;
kb@mitre.com; jomullen@ad.nmsu.edu
Cc: Cain, Joseph; manet@ietf.org; Windham, William
Subject: RE: [manet] FW: manet Digest, Vol 25, Issue 10


Robert,

As I recall, Psiactive gets into predictive routing aspects, does it
not?

Thanks,
Stephen F Bush (http://www.research.ge.com/~bushsf)


-----Original Message-----
From: Kennedy, Robert [mailto:rkenne01@harris.com]
Sent: Monday, May 08, 2006 2:09 PM
To: fred@cisco.com; daniel.byrne@adtran.com; kb@mitre.com;
jomullen@ad.nmsu.edu
Cc: Cain, Joseph; manet@ietf.org; Windham,William
Subject: [manet] FW: manet Digest, Vol 25, Issue 10


Suggest that those of you who are interested in the complex interplay of
so many factors that affect MANET, including "who is my neighbor", check
out the United States Patent and Trademark Office's Web site.  Once you
get to there, search for the term "Psiactive" (for networks, not gaming
or parapsychology) with the following patents pending application
numbers:  20040219909, 20040218582 and 20040218548.  These are quite
relevant to the discussions in your discussions.  Knowing what the
factors are is one thing.  Knowing how to handle the complexity of
assimilating all the relevant ones is much more difficult.  Knowing that
cross-layering is critical to MANET is a good start, but figuring out
how to intelligently fuse all this information is in general very
challenging -- especially when you know that your MANET has to interact
with many fixed and evolving network standards.

Robert A. Kennedy
Network Architect
Networks Technology Department
Government Communications Systems Division
Harris Corporation

-----Original Message-----
From: manet-request@ietf.org [mailto:manet-request@ietf.org]=20
Sent: Thursday, May 04, 2006 9:12 PM
To: manet@ietf.org
Subject: manet Digest, Vol 25, Issue 10

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: Re: MANET definition of a neighbor (Fred Baker)
   2. Re: Re: MANET definition of a neighbor (Kenneth Brayer)
   3. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   4. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   5. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   6. RE: Re: MANET definition of a neighbor (Mullen, John)
   7. Re: Re: MANET definition of a neighbor (Chip Elliott)
   8. RE: Re: MANET definition of a neighbor (DANIEL BYRNE)
   9. MobiSys 2006 Call for Participation (Alec Wolman)


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

Message: 1
Date: Thu, 4 May 2006 13:47:07 -0700
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: DANIEL BYRNE <daniel.byrne@adtran.com>
Cc: manet@ietf.org
Message-ID: <B37D901B-48CB-4903-A9B2-AA986EACD5EC@cisco.com>
Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; =
format=3Dflowed


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will
> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the =20
table will result in the same table and consume a lot of power and =20
CPU while doing so. If something has changed but it is not relevant =20
to the communications I am involved in, it is the proverbial tree =20
falling in the forest - whether I adapt to the change or not has no =20
near term effect. And if there has been a change that affects my =20
communications (as end point or relay), any routing protocol I am =20
aware of will adapt to it anyway.

Why, specifically, does this accomplish anything?



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

Message: 2
Date: Thu, 04 May 2006 16:56:08 -0400
From: Kenneth Brayer <kb@mitre.org>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: Fred Baker <fred@cisco.com>
Cc: manet@ietf.org
Message-ID: <445A6A68.6040004@mitre.org>
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed

Fred
You need to look at the link over a long period of time. Ten minutes=20
stable may be the fluke.
Ken

Fred Baker wrote:

>
> On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:
>
>> Some real world MANETS deal with this by trying to eliminate the =20
>> problem through coding. THey give up usable channel capacity to =20
>> reduce the error rate and increase channel reliability.
>
>
> I think they all do. Even 802.11 does that.
>
> But there are longer term issues. A link that goes in and out every =20
> 60 seconds may have wonderful channel characteristics while it is in.

> If I have the option of one that has been stable for ten minutes and =20
> is otherwise comparable, though, I will opt for the latter ten times =20
> out of ten. It has a greater probability of being useful at the time =20
> I want to use it.


--=20
Kenneth Brayer
Fellow of the IEEE
M/S M370
The MITRE Corporation
202 Burlington Road
Bedford, MA 01730

e-mail: kb@mitre.org
tele: 781-271-5254
fax: 781-271-2841




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

Message: 3
Date: Thu, 4 May 2006 15:59:45 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Fred Baker" <fred@cisco.com>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F0F@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?



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

Message: 4
Date: Thu, 4 May 2006 16:01:15 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Mullen, John" <jomullen@ad.nmsu.edu>,	<manet@ietf.org>
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F10@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

=20
Hi Dan,

The problem is that the node doesn't know which links are good and must
make intelligent guesses.  If you rebuild your table without reason to
suspect a route is bad, you will increase the risk of excluding a good
route or including a bad one.

- If you accidently include a bad route, it will be weeded out in the
next cycle or two.  The trick is to update fast enough so that the bad
routes don't have a lasting impact.



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

Message: 5
Date: Thu, 4 May 2006 16:03:00 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Fred Baker" <fred@cisco.com>,	"Kenneth Brayer" <kb@mitre.org>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F11@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

It only has better long term reliability.  A manet packet doesn't take
60 seconds to transmit, so you are looking for a very small window of
opportunity.  Statistically the differnce between the two links is very
small when considering the transmission time of the manet packet.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]=20
Sent: Thursday, May 04, 2006 3:42 PM
To: Kenneth Brayer
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 12:30 PM, Kenneth Brayer wrote:

> Some real world MANETS deal with this by trying to eliminate the=20
> problem through coding. THey give up usable channel capacity to reduce

> the error rate and increase channel reliability.

I think they all do. Even 802.11 does that.

But there are longer term issues. A link that goes in and out every 60
seconds may have wonderful channel characteristics while it is in. =20
If I have the option of one that has been stable for ten minutes and is
otherwise comparable, though, I will opt for the latter ten times out of
ten. It has a greater probability of being useful at the time I want to
use it.

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



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

Message: 6
Date: Thu, 4 May 2006 15:14:18 -0600
From: "Mullen, John" <jomullen@ad.nmsu.edu>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Cc: manet@ietf.org
Message-ID:
=09
<8536FDFA3AD04A49A15804915996569106DEF0FE@exchange1.ACN.ad.nmsu.edu>
Content-Type: text/plain;	charset=3D"us-ascii"

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



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

Message: 7
Date: Thu, 04 May 2006 17:47:36 -0400
From: Chip Elliott <celliott@bbn.com>
Subject: Re: [manet] Re: MANET definition of a neighbor
To: <jasteven@rockwellcollins.com>,manet@ietf.org
Message-ID: <6.2.1.2.2.20060504174629.038a6ae0@127.0.0.1>
Content-Type: text/plain; charset=3D"us-ascii"; format=3Dflowed



I think Jim has stated the fundamental challenge with MANETs
very succinctly, and his comment is worth some reflection:

At 01:54 PM 5/4/2006, jasteven@rockwellcollins.com wrote:

>The definition of a neighbor is why wireless MANETs are so much more=20
>difficult than wireline networks.  In fact, one could say that the
problem=20
>of determining who is a MANET neighbor and controlling the link to
MANET=20
>neighbors sums up the problems and complexities associated with MANETs
-=20
>at least to a first order approximation!

 From my own perspective, even the term "link" can lead to
great mental confusion. And once one relies on simulations where
everyone within range has 100% reception, and everyone outside
a range has 0%, one has missed most of what makes a
real MANET so challenging.

Mobility adds more complexity, but the probabilistic,
self-noisy, shared channel is the core problem, I think. And as
Jim points out, layering doesn't help and can even hurt.

Nice statement of the problem, Jim.

Chip Elliott
Principal Engineer, BBN=20




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

Message: 8
Date: Thu, 4 May 2006 16:48:57 -0500
From: "DANIEL BYRNE" <daniel.byrne@adtran.com>
Subject: RE: [manet] Re: MANET definition of a neighbor
To: "Mullen, John" <jomullen@ad.nmsu.edu>
Cc: manet@ietf.org
Message-ID:
	<9AC3F0E75060224C8BBC5BA2DDC8853A03528F12@EXV1.corp.adtran.com>
Content-Type: text/plain;	charset=3D"us-ascii"

Yeah, I agree, an AGC is a better analog and better solution.  Basically
low pass the table through constant sampling.=20

-----Original Message-----
From: Mullen, John [mailto:jomullen@ad.nmsu.edu]=20
Sent: Thursday, May 04, 2006 4:14 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Hi Daniel,

In a PLL you have access to the actual output frequency.  In a MANET,
you do not have access to the actual link condition.  The method you
propose would cause endless cycling as the node continually updates its
routing tables on the basis of the random error, rather than the actual
situation.

A better analog would be the AGC signal in a receiver, in which the
fluctuations in the received signal are averaged out through an
integrator.  The analog is not perfect, however, since the AGC works on
a single signal, while the MANET must estimate a link's condition on the
basis of occasional signals from the transmitter.  However, the task is
similar in that the only way to sort the signal out from the random
error is to take repeated measures and apply some sort of integrating
filter to the resulting data.


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]
Sent: Thursday, May 04, 2006 3:00 PM
To: Fred Baker
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

Think of it as a feedback system.  You iteratively arrive at an optimal
solution by periodically sampling the output and feeding it back to the
input.=20

Think of a PLL, it constantly samples the output frequency and compares
it to the reference frequency.  The phase comparator constantly zeros in
on the targeted frequency by adjusting up and down over and over again.
If it jumps too high or too low, it is immediately fixed in the next few
clock cycles. =20

Feedback always makes a system more stable.  Imagine if the PLL assumed
"nothing has changed and did not conclude there has been a change
without definite evidence".  The clock would be out of its desired range
very quickly, and there would be more adjusting needed to fix the
problem.

"If something has changed but it is not relevant to the communications I
am involved in, it is the proverbial tree falling in the forest -
whether I adapt to the change or not has no near term effect."

Your neighbors are always of prime importance in a MANET.  It is through
them that you pass all data.

-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Thursday, May 04, 2006 3:47 PM
To: DANIEL BYRNE
Cc: manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor


On May 4, 2006, at 1:28 PM, DANIEL BYRNE wrote:

> Rebuilding lists of reliable neighbor nodes every 3 seconds or so will

> increase the probability that the links in the list will be useful.

Not sure I buy the argument. If nothing has changed, rebuilding the
table will result in the same table and consume a lot of power and CPU
while doing so. If something has changed but it is not relevant to the
communications I am involved in, it is the proverbial tree falling in
the forest - whether I adapt to the change or not has no near term
effect. And if there has been a change that affects my communications
(as end point or relay), any routing protocol I am aware of will adapt
to it anyway.

Why, specifically, does this accomplish anything?

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



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

Message: 9
Date: Thu, 4 May 2006 18:11:36 -0700
From: "Alec Wolman" <alec.wolman@hotmail.com>
Subject: [manet] MobiSys 2006 Call for Participation
To: <manet@ietf.org>
Message-ID: <BAY116-W3149F02EAD192A9051E17FCB50@phx.gbl>
Content-Type: text/plain; charset=3D"iso-8859-1"

***************************
Call for participation
MobiSys 2006 - The Fourth International Conference on Mobile Systems,
Applications, and Services
Uppsala, Sweden, June 19-22, 2006.
***************************
=20
The advance registration deadline for MobiSys 2006 is fast approaching:
*May 15th, 2006*
=20
See the MobiSys website -
http://www.sigmobile.org/mobisys/2006/index.html for details on the
program and registration information.
=20
_________________________________________________________________
Join the next generation of Hotmail and you could win the adventure of a
lifetime
http://www.imagine-msn.com/minisites/sweepstakes/mail/register.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www1.ietf.org/pipermail/manet/attachments/20060504/fab7e2ac/attac
hment.html

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

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


End of manet Digest, Vol 25, Issue 10
*************************************

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

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



From manet-bounces@ietf.org Mon May 08 15:40:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdBaK-0003iw-6e; Mon, 08 May 2006 15:40:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdBaH-0003fx-UA
	for manet@ietf.org; Mon, 08 May 2006 15:39:57 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdBaG-0003kG-LW
	for manet@ietf.org; Mon, 08 May 2006 15:39:57 -0400
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
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Mon, 8 May 2006 13:40:35 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF6AF@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZyVugEQ+lqkUeHSuyDvWnQCm/PWgAZSx5gAAawrZA=
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Daniel,

The conditions under which you choose a new link and those under which
you decide to keep or toss an existing one are different.  For the new
link, you may only have hello messages, which can be related to packet
reception, but generally have a much higher success rate.  For an
existing link, you have hello messages, control packets, and data
packets.  Becaue you have much more information about a link in use than
one that is not in use, you are more likely to make a mistake when
choosing a new link than when evaluating an existing one.



John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Monday, May 08, 2006 10:34 AM
To: David Young; Mullen, John
Cc: manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

On Fri, May 05, 2006 at 09:00:59AM -0600, Mullen, John wrote:
> Hi Dan,
>=20
> It doesn't work that way.  The chances of selecting a bad link may,=20
> depending on the scheme you pick, be higher than that of picking a=20
> good on.  In field trials, this has turned out to be a major source of

> trouble.  Repeated attempts will simply lead to repeated bad choices.

This statement simply doesn't make any sense.  If repeated attempts
produce repeated bad choices, then the decision making process behind
choosing is incorrect, not the sampling.  Choosing once and assuming all
is good just doesn't work.

Imagine if you plotted a trip with your family to Disney world.  You
figured gas, speed, and route to the best of your ability before you
started the trip.  If you didn't subsequently modify your careful
calculations to account for weather, traffic, stop lights, road
construction, pot holes, pedestrians, and any number of other
interferences, then you would wreck before you left your neighborhood.
Constant sampling always produces better results unless of course your 3
year old is driving.  In that case it is better to point the steering
wheel in the right direction, and just see how far he can get before
wrecking.  He will probably make it further this way then if you let him
run the controls all by himself. I.e.. The decision making person in
this process is the problem.

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



From manet-bounces@ietf.org Mon May 08 15:50:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdBiX-0006mJ-Rn; Mon, 08 May 2006 15:48:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdBiW-0006mB-CB
	for manet@ietf.org; Mon, 08 May 2006 15:48:28 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdBiV-00049C-3p
	for manet@ietf.org; Mon, 08 May 2006 15:48:28 -0400
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
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Mon, 8 May 2006 13:48:33 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF6B6@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZvu+vPhfojYl4fQNyKDTF6aAqd+QAABwFwAAB/LNAAAImI4AAlPAEwAAEFvpAAAp3tkAAAIW+QAGdtmkAANZeBsA==
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "DANIEL BYRNE" <daniel.byrne@adtran.com>,
	<manet@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

"Maybe a new stack architecture is needed for MANETS where protocols can
still partition layer specific items yet share cross applicable
information."

I agree, but we may still be able to pull it off without having to mess
up the stack.

John Mullen=20


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: DANIEL BYRNE [mailto:daniel.byrne@adtran.com]=20
Sent: Sunday, May 07, 2006 12:18 PM
To: Mullen, John; manet@ietf.org
Subject: RE: [manet] Re: MANET definition of a neighbor

"...That is why I feel a cross-layer approach will win out in the end.
The physical and link layers will have information that is normally
hidden from the routing layer that will be needed to evaluate potential
links, but the MANET protocol will have the job of finding an optimal
network solution."

True, the routing protocol could use information attained by lower
layers.  A mechanism to pass information up the stack is needed, or the
protocol needs to be multi-layer aware. However, the later causes
problems when there are changes in technologies.  Maybe a new stack
architecture is needed for MANETS where protocols can still partition
layer specific items yet share cross applicable information.

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



From manet-bounces@ietf.org Mon May 08 15:56:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdBpq-0002j4-U1; Mon, 08 May 2006 15:56:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdBpp-0002in-4c
	for manet@ietf.org; Mon, 08 May 2006 15:56:01 -0400
Received: from web25701.mail.ukl.yahoo.com ([217.12.10.173])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FdBpn-0004iq-LR
	for manet@ietf.org; Mon, 08 May 2006 15:56:01 -0400
Received: (qmail 95278 invoked by uid 60001); 8 May 2006 19:55:58 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr;
	h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=XTUWMNo6/6rMIvzG4eAmgvuux2sD/ev4JVT+8exxjE8vUHaUB/kdPR6vrlbwpSDkexXZB7+UHOcSs6is1LVUNg+zZTPt1g/BPftmTfOonSqAUnM7tOnuHpb0dD2tRVLA0Im46bRcLBod2u+R6oag8EoBfytNICMbr1OHsgyPXzU=
	; 
Message-ID: <20060508195558.95276.qmail@web25701.mail.ukl.yahoo.com>
Received: from [213.192.200.2] by web25701.mail.ukl.yahoo.com via HTTP;
	Mon, 08 May 2006 21:55:58 CEST
Date: Mon, 8 May 2006 21:55:58 +0200 (CEST)
From: dendene elhadi <dendene2004@yahoo.fr>
To: manet@ietf.org
In-Reply-To: <E1Fc7IW-0005DE-TI@megatron.ietf.org>
MIME-Version: 1.0
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [manet] . Re: Re: MANET definition of a neighbor (Kenneth Brayer )
	(Elhadi DENDENE)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1226060226=="
Errors-To: manet-bounces@ietf.org

--===============1226060226==
Content-Type: multipart/alternative; boundary="0-1015437484-1147118158=:90981"
Content-Transfer-Encoding: 8bit

--0-1015437484-1147118158=:90981
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi sir,
  you say that i can hear you but you cannot hear me, this is naturally, we are not neighbors in this case, the scenario is similar to a famous person where people can hear him, but he can't hear them, i say that authentication can resolve the problem, if i hear you then i'll try to initiate some exchanges with you, if you don't respond within a certain time, i'll consider that you are not a neighbor, the security aspect require this. 

		
---------------------------------
 Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Cliquez ici.
--0-1015437484-1147118158=:90981
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>Hi sir,</DIV>  <DIV>you say that i can hear you but you cannot hear me, this is naturally, we are not neighbors in this case, the scenario&nbsp;is similar to a famous person where people can hear him, but he can't hear them, i say that authentication can resolve the problem, if i hear you then i'll try to initiate some exchanges with you, if you don't respond within a certain time, i'll consider that you are not a neighbor, the security aspect require this.&nbsp;</DIV><p>
		<hr size="1" /> 
<b>Faites de Yahoo! votre page d'accueil sur le web</b> pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. <a href="http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yahoo.com/set" target=_blank>Cliquez ici</a>.
--0-1015437484-1147118158=:90981--


--===============1226060226==
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

--===============1226060226==--




From manet-bounces@ietf.org Mon May 08 17:46:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdDYH-0005dG-Sq; Mon, 08 May 2006 17:46:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdDYG-0005d0-8X
	for manet@ietf.org; Mon, 08 May 2006 17:46:00 -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 1FdCWj-0007Ih-0K
	for manet@ietf.org; Mon, 08 May 2006 16:40:21 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FdC90-00031h-PA
	for manet@ietf.org; Mon, 08 May 2006 16:15:52 -0400
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
Subject: RE: [manet] Re: MANET definition of a neighbor
Date: Mon, 8 May 2006 14:15:49 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106DEF6E6@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Re: MANET definition of a neighbor
Thread-Index: AcZyVug9UtceDIuhTiKpa3AB9Pf9BAAhDhTw
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "David Young" <dyoung@pobox.com>
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: manet@ietf.org, DANIEL BYRNE <daniel.byrne@adtran.com>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi David,

1) In a MANET, we assume limited power, which means we want just one
node to forward a packet.=20

2) That is possible.  A good MANET design is one that works in most
conditions, but it is always possible to find a set of conditions under
which any particular MANET may not work.

3) Because a) both node power and the shared channel are scarce
resources, and b) a global solution to the routing problem can be
expected to be better than a local one.=20


John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
=20
-----Original Message-----
From: David Young [mailto:dyoung@pobox.com]=20
Sent: Sunday, May 07, 2006 10:22 PM
To: Mullen, John
Cc: DANIEL BYRNE; manet@ietf.org
Subject: Re: [manet] Re: MANET definition of a neighbor

On Fri, May 05, 2006 at 09:00:59AM -0600, Mullen, John wrote:
> Hi Dan,
>=20
> It doesn't work that way.  The chances of selecting a bad link may,=20
> depending on the scheme you pick, be higher than that of picking a=20
> good on.  In field trials, this has turned out to be a major source of

> trouble.  Repeated attempts will simply lead to repeated bad choices.

Three observations, and a question: (1) Any choice of a single receiver
may be a bad choice, most of the time.  (2) The link conditions may not
outlast the decision process.  (3) You will broadcast the packet at the
physical layer, anyway---i.e., more than one receiver will receive it.
So, why choose?  (It only occurs to me to ask because I have fallen
under the influence of the Roofnet ExOR[1] study.)

Dave

[1]
http://pdos.csail.mit.edu/papers/roofnet:exor-sigcomm05/roofnet_exor-sig
comm05.pdf

--=20
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 Mon May 08 18:51:33 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdEYu-0007Wq-PN; Mon, 08 May 2006 18:50:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdEYs-0007Vy-6Z
	for manet@ietf.org; Mon, 08 May 2006 18:50:42 -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 1FdE0d-0004lc-Ix
	for manet@ietf.org; Mon, 08 May 2006 18:15:19 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FdDkV-0004p3-GI
	for manet@ietf.org; Mon, 08 May 2006 17:58:44 -0400
Received: from sj-core-5.cisco.com ([171.71.177.238])
	by sj-iport-2.cisco.com with ESMTP; 08 May 2006 14:58:39 -0700
X-IronPort-AV: i="4.05,103,1146466800"; 
	d="scan'208"; a="321995851:sNHT32643532"
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k48LwcRT015021;
	Mon, 8 May 2006 14:58:38 -0700 (PDT)
Received: from [10.32.244.220] (stealth-10-32-244-220.cisco.com
	[10.32.244.220])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k48Luf0V005509;
	Mon, 8 May 2006 14:56:41 -0700
In-Reply-To: <445E3DA2.3080802@fidelity-comtech.com>
References: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F1B@EXV1.corp.adtran.com>
	<445E3DA2.3080802@fidelity-comtech.com>
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <94AFBBAB-A532-4A65-BAB2-0D333B308837@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] 802.11s: Neighbors, Link Layer and Network Layer
Date: Mon, 8 May 2006 14:58:35 -0700
To: Joe Carey <joe.carey@fidelity-comtech.com>
X-Mailer: Apple Mail (2.749.3)
DKIM-Signature: a=rsa-sha1; q=dns; l=4672; t=1147125401; x=1147989401;
	c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20<fred@cisco.com>
	|Subject:Re=3A=20[manet]=20802.11s=3A=20Neighbors,
	=20Link=20Layer=20and=20Network =20Layer
	|To:Joe=20Carey=20<joe.carey@fidelity-comtech.com>;
	X=v=3Dcisco.com=3B=20h=3D1u3eWP3pCrQa9fCOrhSF4E4JTdQ=3D;
	b=N+URCrfMvPN35M64bTGjncKkCMHbdyk+2m81lCY3wKbV80rrhQvhZQ6+Nxll2xROU0iQBfAG
	tqWGBHamvBMcOzqosrz4rKPZYodjlh/Bggqgor4eCev2IYQr/QPZ0Li3;
Authentication-Results: imail.cisco.com; header.From=fred@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


On May 7, 2006, at 11:34 AM, Joe Carey wrote:

> It appears from my limited exposure that the 802.11s protocol - and  
> many vendors proprietary implementations of mesh - that they are  
> attempting to implement multi-hop mesh networks at the LINK layer.   
> This seems to be exactly the wrong way to partition the problem; it  
> would seem that the store-and-forward nature of mesh networking,  
> including multiple links, should remain at layer 3 (the IP layer),  
> where most current implementations have it.  However, these are  
> smart people with a lot of experience.  So what is motivating this?

To answer this, we have to go back to about 1985 when IEEE wanted to  
get involved with bridging networks and that was ostensibly ANSI's job.

As you say, the original layered reference model worked on some  
pretty basic questions:

The physical layer answers the question "what physically connects two  
or more systems, and how do we send signals across it?"

The link layer answers the question set "how do I interpret those  
signals as zero/one, manage link reliability and rate of delivery (if  
that is an issue), turn them into distinct frames if it is a framed  
protocol, etc,to enable two physically connected systems to exchange  
data?"

The network layer answers the question "given that I have a set of  
systems that are not physically connected en mesh but which form a  
set of interconnected systems in a graph, how do I logically connect  
and in fact deliver data from any system in the network to any other?"

In the original Ethernet specification (and therefore in 802.3) there  
was a physical layer way to do this, using repeaters. But they had a  
fundamental problem, or maybe a couple. Any time that any electrical  
energy was placed on a coax, it went throughout the various coaxes,  
and so one got more systems on the network but no additional  
capacity. Also, any problem anywhere in the coax potentially affected  
other areas as well, and so on. Oh, and there was a timing thing -  
the minimum frame size in Ethernet was calculated from the amount of  
time required to ensure that if any two devices in the network spoke  
they would both see a collision and do the right thing. Various  
products improved that situation, but bottom line they needed some  
kind of gateway between coaxes.

Now, in a strictly layer-theory sense, the right solution to this was  
to subdivide the network layer into an upper and a lower sublayer  
(which I call the Internet and Intranet Layers). The layer cake now  
looks like this:


N              +---------------------------------------+
  e     Internet|           IP and things like it       |
L t            +---------------------------------------+
   a w          +-----------+ +-----------+ +-----------+
    y o Intranet|  802.1    | |   ATM VC  | |Frame Relay|
     e r        +-----------+ +-----------+ +-----------+
      r k       +-----------+ +-----------+ +-----------+
                |+---------+| |           | |           |
                ||  LLC    || |   ATM     | |  HDLC     |
        Link    |+---------+| |   Framing | |           |
        Layer   ||  MAC    || |           | |           |
                |+---------+| |           | |           |
                +-----------+ +-----------+ +-----------+
                +-----------+ +-----------+ +-----------+
        Physical|  Coax etc | |  Fiber etc| |DS1/DS3/etc|
                +-----------+ +-----------+ +-----------+

However, that had problems with what we now call "political  
correctness"; IEEE 802.1 would have had to go off to ANSI, since ANSI  
was accredited to handle network layer problems and send the results  
off to ITU. And in this sense, a "bridged Ethernet" (as we called it  
then) was clearly a certain kind of network, just like an ATM, Frame  
Relay, or X.25 network was. But someone decided that since a bridged  
Ethernet worked off the MAC header, it could be called "MAC Layer  
Bridging", and sidestep the issue - and do the work in IEEE.

It has been that way for 20-odd years now.

That said, trust me, you are absolutely correct. In point of fact, we  
are using pretty standard network layer approaches to solve a pretty  
standard network layer question: "how do we make systems that are not  
physically interconnected but form a graph to be able to talk with  
each other over virtual connections overlaid on the underlying  
physical network". And the real picture is in fact a lot like the one  
I describe above.

Don't tell anyone. This is our little secret....
	

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



From manet-bounces@ietf.org Tue May 09 02:15:47 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdLU3-0003SE-B7; Tue, 09 May 2006 02:14:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdLU0-0003S9-U4
	for manet@ietf.org; Tue, 09 May 2006 02:14:08 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdLU0-0004kW-A0
	for manet@ietf.org; Tue, 09 May 2006 02:14:08 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-4.cisco.com with ESMTP; 08 May 2006 23:14:08 -0700
X-IronPort-AV: i="4.05,104,1146466800"; 
	d="scan'208"; a="1802860488:sNHT35799468"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id k496E7BP023872; 
	Mon, 8 May 2006 23:14:07 -0700
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k496E7B9018847;
	Mon, 8 May 2006 23:14:07 -0700 (PDT)
Received: from [10.32.244.220] (stealth-10-32-244-220.cisco.com
	[10.32.244.220])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k496C9vg019474;
	Mon, 8 May 2006 23:12:09 -0700
In-Reply-To: <94AFBBAB-A532-4A65-BAB2-0D333B308837@cisco.com>
References: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F1B@EXV1.corp.adtran.com>
	<445E3DA2.3080802@fidelity-comtech.com>
	<94AFBBAB-A532-4A65-BAB2-0D333B308837@cisco.com>
Mime-Version: 1.0 (Apple Message framework v749.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A0778C79-0439-4627-8949-C5D8630D8953@cisco.com>
Content-Transfer-Encoding: 7bit
From: Fred Baker <fred@cisco.com>
Subject: Re: [manet] 802.11s: Neighbors, Link Layer and Network Layer
Date: Mon, 8 May 2006 23:14:01 -0700
To: Joe Carey <joe.carey@fidelity-comtech.com>
X-Mailer: Apple Mail (2.749.3)
Authentication-Results: sj-dkim-4.cisco.com; header.From=fred@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
DKIM-Signature: a=rsa-sha1; q=dns; l=8313; t=1147155247; x=1148019247;
	c=relaxed/simple; s=sjdkim4001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=fred@cisco.com; z=From:Fred=20Baker=20<fred@cisco.com>
	|Subject:Re=3A=20[manet]=20802.11s=3A=20Neighbors,
	=20Link=20Layer=20and=20Network =20Layer;
	X=v=3Dcisco.com=3B=20h=3Dph0az0e9y2TefFyotnXT6Xdfemw=3D;
	b=ig40evGkLgCkaHNQY344lAV0ngiQDjkhli2THIqX9BL0JvHHSAobZLctusXyqJ7l4RGpY0pH
	WBFTWx2pP7833DEvPjNGftFmMmhtMLpRQ3CiUEvt2H5XZhGKLgRGZ6/q;
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Let me go a step further in the discussion. You have asked whether it  
is wacko to use link layer networks, as they are called. The answer  
is "maybe". The reason why...

The Internet Layer is designed for conscious management: one assigns  
IP addresses by whatever means to devices, names things, talks about  
what routers are neighbors of others, and all that kind of thing.  
This is because the Internet Layer is designed to be the interface  
between things that one traverses consciously. We don't necessarily  
want to advertise all of the subnets in our domain into that other  
domain, but we might want to advertise an aggregate of them, or we  
might want to send that other domain a default route, or something.  
We might check that datagrams coming out of that domain are using  
addresses we believe are within it, and drop all others. We might not  
believe things it tells us. We might not accept all traffic that  
comes from it. Bottom line, we use routing to separate between things  
that at one time or another, for one reason or another, we want to  
separate. Maybe for management reasons, security reasons,  
administrative reasons, dumb reasons, good reasons, whatever reasons.

The Intranet Layer is designed to connect things that should normally  
be thought of as connected. I might have five guy in one building and  
five guys in another who are in the same department and I want to  
think of them as logically co-located; if I do, I put them on the  
same VLAN. I might have several buildings that I want to consider as  
"one campus", and I join them together in my network to make them  
appear that way.

When we first developed the concept that we now call 802.1 bridged  
LANs, we had a number of customers that built really large networks,  
like 10 and 15 thousand users. They had a number of problems, and we  
wound up building in interesting features to allow network managers  
to decide a lot of things.  "We don't necessarily want to advertise  
all of the MAC Addresses in our domain into that other domain, but we  
might want to advertise some of them. We might check that datagrams  
coming out of that domain are using addresses we believe are within  
it, and drop all others. We might not accept all traffic that comes  
from it. Bottom line, we use routing to separate between things that  
at one time or another, for one reason or another, we want to  
separate. Maybe for management reasons, security reasons,  
administrative reasons, dumb reasons, good reasons, whatever  
reasons." Think about it. In such cases, 20 years ago we learned the  
hard way that the right way to solve that kind of problem was  
actually to *use* the layered architecture, and let the Internet  
Layer do that kind of thing.

That said, there were a lot of people at the time who hated  
"bridges", because they thought that one should ONLY use the Internet  
layer. And in practice we have found it useful to use the Intranet  
layer when what we really wanted to connect things that one wants  
administratively treat as connected.

So to directly answer your question - 'is it wacko to build "link  
layer networks" instead of Internet layer networks?'... The answer is  
"if they cross an administrative or network management boundary, yes,  
that's wacko, and if they are within a manageable domain, no that's  
not wacko at all."

On May 8, 2006, at 2:58 PM, Fred Baker wrote:
> On May 7, 2006, at 11:34 AM, Joe Carey wrote:
>> It appears from my limited exposure that the 802.11s protocol -  
>> and many vendors proprietary implementations of mesh - that they  
>> are attempting to implement multi-hop mesh networks at the LINK  
>> layer.  This seems to be exactly the wrong way to partition the  
>> problem; it would seem that the store-and-forward nature of mesh  
>> networking, including multiple links, should remain at layer 3  
>> (the IP layer), where most current implementations have it.   
>> However, these are smart people with a lot of experience.  So what  
>> is motivating this?
>
> To answer this, we have to go back to about 1985 when IEEE wanted  
> to get involved with bridging networks and that was ostensibly  
> ANSI's job.
>
> As you say, the original layered reference model worked on some  
> pretty basic questions:
>
> The physical layer answers the question "what physically connects  
> two or more systems, and how do we send signals across it?"
>
> The link layer answers the question set "how do I interpret those  
> signals as zero/one, manage link reliability and rate of delivery  
> (if that is an issue), turn them into distinct frames if it is a  
> framed protocol, etc,to enable two physically connected systems to  
> exchange data?"
>
> The network layer answers the question "given that I have a set of  
> systems that are not physically connected en mesh but which form a  
> set of interconnected systems in a graph, how do I logically  
> connect and in fact deliver data from any system in the network to  
> any other?"
>
> In the original Ethernet specification (and therefore in 802.3)  
> there was a physical layer way to do this, using repeaters. But  
> they had a fundamental problem, or maybe a couple. Any time that  
> any electrical energy was placed on a coax, it went throughout the  
> various coaxes, and so one got more systems on the network but no  
> additional capacity. Also, any problem anywhere in the coax  
> potentially affected other areas as well, and so on. Oh, and there  
> was a timing thing - the minimum frame size in Ethernet was  
> calculated from the amount of time required to ensure that if any  
> two devices in the network spoke they would both see a collision  
> and do the right thing. Various products improved that situation,  
> but bottom line they needed some kind of gateway between coaxes.
>
> Now, in a strictly layer-theory sense, the right solution to this  
> was to subdivide the network layer into an upper and a lower  
> sublayer (which I call the Internet and Intranet Layers). The layer  
> cake now looks like this:
>
>
> N              +---------------------------------------+
>  e     Internet|           IP and things like it       |
> L t            +---------------------------------------+
>   a w          +-----------+ +-----------+ +-----------+
>    y o Intranet|  802.1    | |   ATM VC  | |Frame Relay|
>     e r        +-----------+ +-----------+ +-----------+
>      r k       +-----------+ +-----------+ +-----------+
>                |+---------+| |           | |           |
>                ||  LLC    || |   ATM     | |  HDLC     |
>        Link    |+---------+| |   Framing | |           |
>        Layer   ||  MAC    || |           | |           |
>                |+---------+| |           | |           |
>                +-----------+ +-----------+ +-----------+
>                +-----------+ +-----------+ +-----------+
>        Physical|  Coax etc | |  Fiber etc| |DS1/DS3/etc|
>                +-----------+ +-----------+ +-----------+
>
> However, that had problems with what we now call "political  
> correctness"; IEEE 802.1 would have had to go off to ANSI, since  
> ANSI was accredited to handle network layer problems and send the  
> results off to ITU. And in this sense, a "bridged Ethernet" (as we  
> called it then) was clearly a certain kind of network, just like an  
> ATM, Frame Relay, or X.25 network was. But someone decided that  
> since a bridged Ethernet worked off the MAC header, it could be  
> called "MAC Layer Bridging", and sidestep the issue - and do the  
> work in IEEE.
>
> It has been that way for 20-odd years now.
>
> That said, trust me, you are absolutely correct. In point of fact,  
> we are using pretty standard network layer approaches to solve a  
> pretty standard network layer question: "how do we make systems  
> that are not physically interconnected but form a graph to be able  
> to talk with each other over virtual connections overlaid on the  
> underlying physical network". And the real picture is in fact a lot  
> like the one I describe above.
>
> Don't tell anyone. This is our little secret....
> 	

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



From manet-bounces@ietf.org Tue May 09 05:39:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdOfg-0004q8-VW; Tue, 09 May 2006 05:38:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdOfe-0004mj-R7
	for manet@ietf.org; Tue, 09 May 2006 05:38:22 -0400
Received: from smtp8.clb.oleane.net ([213.56.31.28])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdOfd-0005r6-EI
	for manet@ietf.org; Tue, 09 May 2006 05:38:22 -0400
Received: from Pavillonquatre ([194.3.133.88]) 
	by smtp8.clb.oleane.net with ESMTP id k499cFVk009337
	for <manet@ietf.org>; Tue, 9 May 2006 11:38:15 +0200
Message-Id: <200605090938.k499cFVk009337@smtp8.clb.oleane.net>
From: "Chantal Ladouce" <chantal.ladouce@upperside.fr>
To: <manet@ietf.org>
Date: Tue, 9 May 2006 11:37:00 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Thread-Index: AcZzTB8LhCBe6KeMTA++6DdSwFClBg==
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Subject: [manet] Wireless/WiFi Convergence Conference 2006 - Paris - France
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1583836917=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1583836917==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0276_01C6735C.E3068A80"

This is a multi-part message in MIME format.

------=_NextPart_000_0276_01C6735C.E3068A80
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

UMA how? IMS when?

Don't miss the 2006 Wireless/WiFi Convergence Conference to be held next
week in Paris (on May 16 to May 19). Distinguished experts and key players
in the convergence field will address technical issues. 

Registration is still open.

Get all details at:

 

 
<http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006intro.htm>
http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006intro.htm

 

 


------=_NextPart_000_0276_01C6735C.E3068A80
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City" =
downloadurl=3D"http://www.5iamas-microsoft-com:office:smarttags"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><em><b><i><font size=3D1 face=3DArial><span =
lang=3DEN-GB
style=3D'font-size:9.0pt;font-family:Arial;font-weight:bold'>UMA how? =
IMS when?</span></font></i></b></em><font
size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:Arial'><o:p></o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>Don't miss the <strong><b><font =
face=3DArial><span
style=3D'font-family:Arial'>2006 Wireless/WiFi Convergence Conference =
</span></font></b></strong>to
be held next week in <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Paris</st1:City></st1:place>
(on May 16 to May 19<strong><b><font face=3DArial><span =
style=3D'font-family:Arial'>)</span></font></b></strong>.
Distinguished experts and key players in the convergence field will =
address
technical issues. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>Registration is still =
open.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>Get all details =
at:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:9.0pt;
font-family:Arial'><a
href=3D"http://www.upperside.fr/wirelessconvergence2006/wwconvergence2006=
intro.htm"
title=3D"http://www.upperside.fr/wirelessconvergence2006/wwconvergence200=
6intro.htm"><span
lang=3DEN-GB>http://www.upperside.fr/wirelessconvergence2006/wwconvergenc=
e2006intro.htm</span></a></span></font><font
size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:Arial'><o:p></o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0276_01C6735C.E3068A80--



--===============1583836917==
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

--===============1583836917==--





From manet-bounces@ietf.org Tue May 09 19:23:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdbX9-0004M7-Hv; Tue, 09 May 2006 19:22:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdbX8-0004M2-8l
	for manet@ietf.org; Tue, 09 May 2006 19:22:26 -0400
Received: from mclmx2.mail.saic.com ([149.8.64.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdbX7-0003ax-0a
	for manet@ietf.org; Tue, 09 May 2006 19:22:26 -0400
Received: from 0015-its-ieg01.mail.saic.com ([149.8.64.21] [149.8.64.21]) by
	mclmx2.mail.saic.com for manet@ietf.org;
	Tue, 9 May 2006 19:22:13 -0400
Received: from mcl-its-exig01.mail.saic.com ([149.8.64.12])
	by 0015-its-ieg01.mail.saic.com (SMSSMTP 4.0.5.66) with SMTP id
	M2006050919221325307
	for <manet@ietf.org>; Tue, 09 May 2006 19:22:13 -0400
Received: by mcl-its-exig01.mail.saic.com with Internet Mail Service
	(5.5.2657.72) id <GFJJPVNR>; Tue, 9 May 2006 19:22:13 -0400
Message-Id: <62D92A9A02BCC845B202323D49A48426209CBC@0591-ITS-EXMP02.us.saic.com>
From: "Roy, Radhika R." <RADHIKA.R.ROY@saic.com>
To: manet@ietf.org
Subject: RE: [manet] 802.11s: Neighbors, Link Layer and Network Layer
Date: Tue, 9 May 2006 19:21:16 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

 

Hi, Baker and all:

Baker has provided a right analysis.

It shows that wireless LANs, being a wireless media that provides an
illusion like physical layer as provided in TDMA, CDMA, FDMA schemes, are
hiding the different layers like LLC and MAC layer embedded inside it
(please see the figure Baker provided below).

It clearly shows that the protocols that are embedded inside the wireless
medium need to be understood clearly. Otherwise, the use of term "wireless"
will create confusions just to think, as if, it is a physical layer.

In another topic, the cross layer communications in wireless environments
are trying optimize the case whether all those layering inside the wireless
networking. They are trying to prove that some of those layers, unlike
physical wire/coax/fiber layer, are not needed. Rather, it would be better
to bypass them, and these are known as cross layer communications.

Best regards,

Radhika

 <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 May 10 05:54:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdlOB-0005iK-4R; Wed, 10 May 2006 05:53:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdlOA-0005iF-8K
	for manet@ietf.org; Wed, 10 May 2006 05:53:50 -0400
Received: from nofilter.italway.it ([193.70.27.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FdlO1-0004fp-LS
	for manet@ietf.org; Wed, 10 May 2006 05:53:50 -0400
X-Spam-Status: No, hits=0.0 required=5.0
	tests=SARE_RECV_ADDR: 0.027
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by nofilter.italway.it
	for manet@ietf.org; Wed, 10 May 2006 11:23:22 +0200
X-Spam-Status: No, hits=0.0 required=6.0
	tests=SARE_RECV_ADDR: 0.027
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by mail2.italway.it for manet@ietf.org;
	Wed, 10 May 2006 11:23:16 +0200
Received: (qmail 9609 invoked from network); 10 May 2006 09:35:56 -0000
Received: from unknown (HELO ?192.168.9.215?) (nicscal@213.21.183.194)
	by server.italway.it with SMTP; 10 May 2006 09:35:56 -0000
Message-ID: <4461B103.6050304@iit.cnr.it>
Date: Wed, 10 May 2006 11:23:15 +0200
From: Nicola Scalabrino <nicola.scalabrino@iit.cnr.it>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: tccc@cs.columbia.edu,  manet@ietf.org,  sigmobile-l@acm.uiuc.edu
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: 
Subject: [manet] Last reminder: CFP for the first International Workshop on
 "Wireless mesh: moving towards applications" (WiMeshNets 2006)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

CALL FOR PAPERS

WiMeshNets 2006 (http://wimeshnets.org)

First International Workshop on "Wireless mesh: moving towards applications"
(Co-located with QShine 2006, Waterloo, Ontario, Canada) August 10, 2006

Recent advances in wireless mesh networks (WMNs) provide promising
opportunities in communication paradigms. WMNs do not depend on wired
communication infrastructure and their mesh connectivity provides
inherent built-in redundancy. This makes them also good candidates for
providing an alternative communication mechanism in the face of
disasters when normal communication infrastructure is destroyed. WMNs
build upon multi-hop forwarding of data packets from access nodes
towards gateways to the fixed network and thus share many properties of
Mobile Ad Hoc Networks. So far almost all existing research effort
related to Mobile Ad Hoc networks has been based mostly on the
assumptions that the nodes are highly mobile and are mainly battery
operated. Thus, most of the protocols and mechanisms try to conserve
energy and cope with frequent topology changes. In WMNs these
assumptions can be relaxed which enables the design of new protocols and
services for WMNs.
Supporting any application over wireless mesh networks is however a
challenging task due to the multi-hop forwarding of packets which also
limits the scalability of WMNs. Nevertheless, WMNs have promising
commercial potential as they are supposed to provide cheap wireless
network coverage and access. Towards this aim the traditional approaches
to routing and to service provisioning should be reconsidered taking
into account the intrinsic characteristics of WMNs and those of new and
emerging applications. This could pave the way to the assessment of this
technology which is expected to conquer new markets in the next few
years by taking advantage of the growth of heterogeneous networks.
Authors are invited to submit original full papers not currently under
review by other conferences on any aspect of “Wireless mesh: moving
towards applications”. Contributions describing theoretical research,
protocol design, experiments and measurements, commercial deployments,
business models, or position/vision statements are all encouraged.
Descriptions of work in progress, test trials, and future work plans are
highly appreciated. Topics of interest include, but are not limited to:

•    Architectures for Wireless Mesh Networks
•    Middleware support in Wireless Mesh Networks
•    Routing in Wireless Mesh Networks
•    Fairness Issues for Wireless Mesh Networks
•    Multicasting and Broadcasting issues in Wireless Mesh Networks
•    Security and Intrusion Detection for Wireless Mesh Networks
•    Handoff and mobility management in Wireless Mesh Networks
•    System prototypes and experimental evaluation of Wireless Mesh Networks
•    Scheduling and Queuing mechanisms to provide QoS in Wireless Mesh
Networks
•    Gaming applications over Wireless Mesh Networks
•    Service level agreement and mesh organization
•    Modeling and Performance Evaluation
•    Seamless internetworking with other type of networks (like sensor
networks)
•    Cross Layer Design and Interactions in Wireless Mesh Networks
•    Transport Layer Protocols over Wireless Mesh Networks
•    Deployment and configuration management
•    Voice and Video over Wireless Mesh Networks
•    Traffic Modeling
•    Mesh Networking Proposal Standards for IEEE 802(R) Wireless Lans
•    Authentication, Charging and Cooperation for Wireless Mesh Networks

Submitted papers will be reviewed by at least two independent experts in
the field. Proceedings of the workshop will be published in the same
manner as those of QShine, and will be available from the ACM Digital
Library. Authors of accepted papers will be required to register in
order for the paper to appear in the workshop proceedings.

Important dates
Full paper manuscript due:      May 12, 2006 Midnight US EST
Acceptance Notification:        June 13, 2006
Camera ready manuscripts due:   June 30, 2006
Workshop date:                  August 10, 2006

Submission Instructions

Prospective authors are encouraged to submit a PDF version of the full
paper in English language. Papers are limited to 5 two-column pages, in
a font no smaller than 10-points, IEEE conference proceedings format.
Papers should be submitted to the respective symposium through COCUS
systems at http://cocus.create-net.it/cocus/welcome.do. Authors of
accepted papers are required to register at regular registration rates
in order for the paper to appear in the conference proceedings.

Organizing Committee

Workshop Chair:
Giovanni Iacovoni, CreateNet, Italy (giovanni.iacovoni@create-net.it)
Technical Program Committee Chair:
Andreas J. Kassler, Karlstad University, Sweden (kassler@ieee.org)
Publicity Chair:
Nicola Scalabrino, CreateNet, Italy (nicola.scalabrino@create-net.it)







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



From manet-bounces@ietf.org Wed May 10 10:22:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FdpZ0-0002vD-4X; Wed, 10 May 2006 10:21:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FdpYy-0002v3-SG
	for manet@ietf.org; Wed, 10 May 2006 10:21:16 -0400
Received: from web50405.mail.yahoo.com ([206.190.38.70])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FdpYv-0007j0-GM
	for manet@ietf.org; Wed, 10 May 2006 10:21:16 -0400
Received: (qmail 2732 invoked by uid 60001); 10 May 2006 14:14:33 -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=4OgeuDHDVZ+c0D3ecYGnS1TJSQybKPO8Gim2R5arU9/1qc8CfwbIa+ysBB69E42xWcZfp4tFBTZEII+Eq+RSmXT9Tfin4zPEXC2FWi3w0Z+toN4ncUZZRgf2aZm7zhtJSsDX9JGPh8dN9hIZdy0tTET6JITxnHPJXUluGHa/xhY=
	; 
Message-ID: <20060510141433.2730.qmail@web50405.mail.yahoo.com>
Received: from [81.129.162.199] by web50405.mail.yahoo.com via HTTP;
	Wed, 10 May 2006 07:14:33 PDT
Date: Wed, 10 May 2006 07:14:33 -0700 (PDT)
From: Robert Frank <robert_frank80@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 1.0 (+)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Subject: [manet] AOMDV linux implementation: src code
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0019208400=="
Errors-To: manet-bounces@ietf.org

--===============0019208400==
Content-Type: multipart/alternative; boundary="0-15446040-1147270473=:1364"
Content-Transfer-Encoding: 8bit

--0-15446040-1147270473=:1364
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Dear all
   
  I wish to know whether there exists any AOMDV implementation for the linux OS, so that i can tested it up on my testbed. 
   
  If so, please let me know from where i can downlaod the source code.
   
  Many thanks
   
  Rob

		
---------------------------------
Blab-away for as little as 1¢/min. Make  PC-to-Phone Calls using Yahoo! Messenger with Voice.
--0-15446040-1147270473=:1364
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>Dear all</div>  <div>&nbsp;</div>  <div>I wish to know whether there&nbsp;exists&nbsp;any AOMDV implementation for the linux OS, so that i can tested it up on my&nbsp;testbed. </div>  <div>&nbsp;</div>  <div>If so, please let me know from where i can downlaod the source code.</div>  <div>&nbsp;</div>  <div>Many thanks</div>  <div>&nbsp;</div>  <div>Rob</div><p>
		<hr size=1>Blab-away for as little as 1¢/min. Make <a href="http://us.rd.yahoo.com/mail_us/taglines/postman2/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com"> PC-to-Phone Calls</a> using Yahoo! Messenger with Voice.
--0-15446040-1147270473=:1364--


--===============0019208400==
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

--===============0019208400==--




From manet-bounces@ietf.org Wed May 10 12:31:55 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fdrae-0002Hi-N9; Wed, 10 May 2006 12:31:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fdrad-0002Gm-CU
	for manet@ietf.org; Wed, 10 May 2006 12:31:07 -0400
Received: from smtp.ing.unipi.it ([131.114.28.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fdrab-00050l-SS
	for manet@ietf.org; Wed, 10 May 2006 12:31:07 -0400
Received: from [131.114.9.4] (empedocle.iet.unipi.it [131.114.9.4])
	by smtp.ing.unipi.it (Postfix) with ESMTP id 7C1EB12EC17;
	Wed, 10 May 2006 18:30:54 +0200 (CEST)
Message-ID: <4462153D.6020109@iet.unipi.it>
Date: Wed, 10 May 2006 18:30:53 +0200
From: Mario Di Francesco <mario.difrancesco@iet.unipi.it>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060502)
X-Accept-Language: it, it-it, en-us, en
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-CSIFI-MailScanner-Information: Please contact Centro Servizi Informatici
	della Facolta` di Ingegneria for more information
X-CSIFI-MailScanner: Found to be clean
X-MailScanner-From: mario.difrancesco@iet.unipi.it
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Subject: [manet] CFP: Minitrack on Wireless Sensor Networks and Applications
 (within HICSS-40)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

              [Apologies for possible multiple copies]


---------------------------------------------------------------------
                             Minitrack on	
           WIRELESS SENSOR NETWORKS AND APPLICATIONS
         http://www.cs.odu.edu/~olariu/s-minitrack.html

                          to be held within
                The Software Technology Track of the
   40th HAWAII INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES (HICSS-40)

                         January 3-6, 2007
           Hilton Waikoloa Village Resort, Big Island, Hawaii
---------------------------------------------------------------------


CALL FOR PAPERS

Developments in computing and sensing hardware and in wireless 
communications have made it technologically feasible and economically 
viable to develop low-power sensor nodes that integrate general-purpose 
computing with multi-purpose sensing and wireless communications 
capabilities. Aggregating sensor nodes into sophisticated sensing, 
computational and communication infrastructures to form wireless sensor 
networks will have a significant impact 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 
redefining the way in which we live and work.

This minitrack focuses on fundamental challenges arising in the design 
of wireless sensor networks and their applications. Our goal is to offer 
a forum for high caliber research and experimentation in this booming 
area. We will provide the participants with an up-to-date survey on 
wireless sensor networks and applications.
Topics of interest include, but are not limited to:

* Sensor-based systems and applications
* Visualization of sensor data
* Middleware and software tools
* Data gathering, aggregation and dissemination
* Embedded network-oriented operating systems
* Networking architectures and protocols
* Hardware aspects of sensor/node design
* Self-organization and governance
* Location and mobility management
* Topology control and time synchronization
* Power Management and energy-efficient design
* Cross-layer architectures
* Intelligent sensors
* Security and dependability issues
* Scalability of wireless sensor networks
* Interfacing with other wireless/mobile systems
* Work models for wireless sensor networks
* Modeling and performance evaluation
* Implementation experience and measurements
* Demos and prototypes


PAPER SUBMISSION

Authors must submit the full paper (by June 15, 2006). For full paper 
preparation and submission, authors must follow the instructions 
available at http://www.hicss.hawaii.edu/.  Papers should contain 
original material and not be previously published, or currently 
submitted for consideration elsewhere. At least one author of each 
accepted paper must register to attend the conference



IMPORTANT DATES

Submission of full manuscript		June 15, 2006
Acceptance/Reject notifications		August 15, 2006
Submission of final version		September 15, 2006



MINITRACK CO-CHAIRS

Edoardo Biagioni
Dept. of Information and Computer Science
University of Hawaii
Honolulu, HI 96822
E-mail: esb@hawaii.edu

Stephan Olariu
Dept. of Computer Science
Old Dominion University
Norfolk, VA 23529-0162
E-mail: olariu@cs.odu.edu

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



From manet-bounces@ietf.org Thu May 11 10:29:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FeC9X-0006un-Ao; Thu, 11 May 2006 10:28:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FeC9U-0006ui-QT
	for manet@ietf.org; Thu, 11 May 2006 10:28:28 -0400
Received: from winger.mail.pas.earthlink.net ([207.217.120.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FeC9S-0003za-2F
	for manet@ietf.org; Thu, 11 May 2006 10:28:28 -0400
Received: from [216.40.189.210] (helo=[192.168.100.149])
	by winger.mail.pas.earthlink.net with asmtp (Exim 3.36 #1)
	id 1FeC9N-0002o8-00
	for manet@ietf.org; Thu, 11 May 2006 07:28:21 -0700
Mime-Version: 1.0 (Apple Message framework v749.3)
In-Reply-To: <94AFBBAB-A532-4A65-BAB2-0D333B308837@cisco.com>
References: <9AC3F0E75060224C8BBC5BA2DDC8853A03528F1B@EXV1.corp.adtran.com>
	<445E3DA2.3080802@fidelity-comtech.com>
	<94AFBBAB-A532-4A65-BAB2-0D333B308837@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <249AB7A6-9601-4F4A-892C-C9F6F06D998C@corp.earthlink.net>
Content-Transfer-Encoding: 7bit
From: Christian Kuhtz <kuhtzch@corp.earthlink.net>
Subject: Re: [manet] 802.11s: Neighbors, Link Layer and Network Layer
Date: Thu, 11 May 2006 10:28:22 -0400
To: manet@ietf.org
X-Mailer: Apple Mail (2.749.3)
X-ELNK-Trace: 0f78cbcd564a78b899ec86cd75d8498d27ce4652caded48f1e9530bfde916645400199c07f7d2d5f2c57ba4de81673b1715ed6d3cd8c1f1f715ed6d3cd8c1f1f
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


So presently, the joint SeeMESH/WiMesh proposal adopted in Denver by  
TGs does exactly what is described below, it is a link layer  
approach.  In fact, 802.11s charter (the PAR) specifically requires  
it to be a LAN segment (and we can certainly all debate whether  
that's a good idea).  Whether this proposal will ever see the light  
in its current form remains to be seen.  In fact, it does actually  
prescribe specific IP(!) based routing mechanisms (AODV-RM) as a  
lowest common denominator protocol.

 From a carrier point of view, an IP only mesh is likely the wrong  
answer, it needs to have the fundamental ability to carry traffic  
from a number of virtual networks.  And we can certainly debate and  
argue how that should be done.  Something that looks like a VLAN may  
not be an altogether bad approach, although I think I need some  
convincing as to how that's really going to work at scale (and at  
all, really).

If it's more of a network layer solution (and I'm specifically not  
limiting this to pure IP), it might be a good idea to discuss just  
how those would work at scale and cost effectively.  There certainly  
is a good bit of perception always that network layer increases cost  
and complexity.

Anyone here going to be in Jax next week?  I'd love to get us service  
provider types talking about these things.  Up to this point, the  
authors of the proposal in TGs have made guesses about carrier needs,  
rather than having any actual involvement (this isn't my deduction,  
it's a statement made to several people in Denver by the authors of  
the proposal).

Best regards,
Christian

PS: There's an assertion in Joe's original email that most  
implementations in use today are at IP.  Not sure I agree with that,  
I think what you see is hybrid approaches (link layer and network  
layer), and TGs current proposal is fundamentally the same. 802.11 is  
a fundamentally PHY/MAC based technology.  If you want something  
else, it probably should be defined outside of the 802 LMSC.

On May 8, 2006, at 5:58 PM, Fred Baker wrote:

>
> On May 7, 2006, at 11:34 AM, Joe Carey wrote:
>
>> It appears from my limited exposure that the 802.11s protocol -  
>> and many vendors proprietary implementations of mesh - that they  
>> are attempting to implement multi-hop mesh networks at the LINK  
>> layer.  This seems to be exactly the wrong way to partition the  
>> problem; it would seem that the store-and-forward nature of mesh  
>> networking, including multiple links, should remain at layer 3  
>> (the IP layer), where most current implementations have it.   
>> However, these are smart people with a lot of experience.  So what  
>> is motivating this?
>
> To answer this, we have to go back to about 1985 when IEEE wanted  
> to get involved with bridging networks and that was ostensibly  
> ANSI's job.
>
> As you say, the original layered reference model worked on some  
> pretty basic questions:
>
> The physical layer answers the question "what physically connects  
> two or more systems, and how do we send signals across it?"
>
> The link layer answers the question set "how do I interpret those  
> signals as zero/one, manage link reliability and rate of delivery  
> (if that is an issue), turn them into distinct frames if it is a  
> framed protocol, etc,to enable two physically connected systems to  
> exchange data?"
>
> The network layer answers the question "given that I have a set of  
> systems that are not physically connected en mesh but which form a  
> set of interconnected systems in a graph, how do I logically  
> connect and in fact deliver data from any system in the network to  
> any other?"
>
> In the original Ethernet specification (and therefore in 802.3)  
> there was a physical layer way to do this, using repeaters. But  
> they had a fundamental problem, or maybe a couple. Any time that  
> any electrical energy was placed on a coax, it went throughout the  
> various coaxes, and so one got more systems on the network but no  
> additional capacity. Also, any problem anywhere in the coax  
> potentially affected other areas as well, and so on. Oh, and there  
> was a timing thing - the minimum frame size in Ethernet was  
> calculated from the amount of time required to ensure that if any  
> two devices in the network spoke they would both see a collision  
> and do the right thing. Various products improved that situation,  
> but bottom line they needed some kind of gateway between coaxes.
>
> Now, in a strictly layer-theory sense, the right solution to this  
> was to subdivide the network layer into an upper and a lower  
> sublayer (which I call the Internet and Intranet Layers). The layer  
> cake now looks like this:
>
>
> N              +---------------------------------------+
>  e     Internet|           IP and things like it       |
> L t            +---------------------------------------+
>   a w          +-----------+ +-----------+ +-----------+
>    y o Intranet|  802.1    | |   ATM VC  | |Frame Relay|
>     e r        +-----------+ +-----------+ +-----------+
>      r k       +-----------+ +-----------+ +-----------+
>                |+---------+| |           | |           |
>                ||  LLC    || |   ATM     | |  HDLC     |
>        Link    |+---------+| |   Framing | |           |
>        Layer   ||  MAC    || |           | |           |
>                |+---------+| |           | |           |
>                +-----------+ +-----------+ +-----------+
>                +-----------+ +-----------+ +-----------+
>        Physical|  Coax etc | |  Fiber etc| |DS1/DS3/etc|
>                +-----------+ +-----------+ +-----------+
>
> However, that had problems with what we now call "political  
> correctness"; IEEE 802.1 would have had to go off to ANSI, since  
> ANSI was accredited to handle network layer problems and send the  
> results off to ITU. And in this sense, a "bridged Ethernet" (as we  
> called it then) was clearly a certain kind of network, just like an  
> ATM, Frame Relay, or X.25 network was. But someone decided that  
> since a bridged Ethernet worked off the MAC header, it could be  
> called "MAC Layer Bridging", and sidestep the issue - and do the  
> work in IEEE.
>
> It has been that way for 20-odd years now.
>
> That said, trust me, you are absolutely correct. In point of fact,  
> we are using pretty standard network layer approaches to solve a  
> pretty standard network layer question: "how do we make systems  
> that are not physically interconnected but form a graph to be able  
> to talk with each other over virtual connections overlaid on the  
> underlying physical network". And the real picture is in fact a lot  
> like the one I describe above.
>
> Don't tell anyone. This is our little secret....
> 	
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-bounces@ietf.org Fri May 12 02:28:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FeR74-0002hD-FM; Fri, 12 May 2006 02:26:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FeR72-0002h8-SX
	for manet@ietf.org; Fri, 12 May 2006 02:26:56 -0400
Received: from mail.ajou.ac.kr ([202.30.0.18])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FeR6z-00071L-5O
	for manet@ietf.org; Fri, 12 May 2006 02:26:56 -0400
Received: from spam.ajou.ac.kr ([202.30.0.9])
	by maru (Crinity Message Backbone-2.8) with SMTP ID 904
	for <manet@ietf.org>; Fri, 12 May 2006 15:25:07 +0900 (KST)
Received: from 210.107.197.180 ([210.107.197.180])
	by seodang.ajou.ac.kr (Spambreaker ESMTP Server);
	Fri, 12 May 2006 15:21:31 +0900 (KST)
MIME-Version: 1.0
Message-Id: <4464296B.000003.03636@JUNAID-42023936>
Date: Fri, 12 May 2006 15:21:31 +0900
Content-Type: Text/Plain;
  charset="iso-8859-1"
X-Mailer: IncrediMail (5002253)
From: Junaid Chaudhry <junaid@ajou.ac.kr>
X-FID: PLAINTXT-NONE-0000-0000-000000000000
Content-Transfer-Encoding: 7bit
X-Priority: 3
To: manet@ietf.org
X-Spam-Score: 2.3 (++)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [manet] Service Composition and Preferred Technologies
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Junaid Chaudhry <junaid@ajou.ac.kr>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


Dear Sir/Madam

 

I hope this message finds you in the best of spirits.

 

We are working on a Dynamic Service Composition Scheme. Our objective is to
provide the user/user device to enjoy the same service environment whenever
he requests a (re)configuration. 

 

I am wondering which technology can be used to give us the minimum design
time work and developing as much as possible to run time processing. Thanks
in advance and waiting to hear from you soon.

 

Junaid Chaudhry

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



From manet-bounces@ietf.org Fri May 12 12:37:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FeadL-000845-Rc; Fri, 12 May 2006 12:36:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FeadK-0007zC-K1
	for manet@ietf.org; Fri, 12 May 2006 12:36:54 -0400
Received: from mx2.buaa.edu.cn ([219.239.227.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Feacx-00052h-31
	for manet@ietf.org; Fri, 12 May 2006 12:36:35 -0400
Received: from mx1.buaa.edu.cn (unknown [192.168.128.6])
	by mx2.buaa.edu.cn (Postfix) with ESMTP id 7E19A37F54
	for <manet@ietf.org>; Sat, 13 May 2006 00:34:59 +0800 (CST)
Received: from [211.71.6.143] by 10.0.0.131 with StormMail ESMTP id
	93557.3441827347; Sat, 13 May 2006 01:50:59 +0800 (CST)
Date: Sat, 13 May 2006 00:35:25 +0800
From: "Luo Gang" <luogang@vrlab.buaa.edu.cn>
To: "=?gb2312?B?VqiqdG9yIEplc3Vz?=" <vjesus@av.it.pt>
Subject: Re: [manet] Curious about how to evaluate the performance of ad hoc
	network protocols
Organization: Beihang University, VR laboratory
X-mailer: Foxmail 5.0 [cn]
Mime-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
Message-Id: <20060512163459.7E19A37F54@mx2.buaa.edu.cn>
X-Spam-Score: 4.1 (++++)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: "manet@ietf.org " <manet@ietf.org>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: luogang@vrlab.buaa.edu.cn
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Dear Jesus, Sridhara and Antonakakis,

Thanks for sharing your vision with me.
I've read all paper you mentioned.

>Part of the problem is... defining the problem. Even a routing protocol
>can be analysed in multiples ways, each with its own performance metrics.
>The other problem is the conditions under which the performance is
>evaluated. Take a look at a paper called "MANET Simulation Studies: The
>Incredibles" by Kurkowski and others.
I agree Jesus's opinion,
it's important to define the problem clearly first,
such as which scenarios MANETs is expected to applied to?
if we don't know exactly about the expected scenarios,
we can not choose the suitable performace metrics to evaluate it.
I learn much from the paper he commended.

Sridhara present their study on "realistic mobility (derived from various urban
planning institutions and US Bureau of labor statistics)" for Urban Mesh Networks.
http://udelmodels.eecis.udel.edu
it must be useful!

but I am not sure if the Urban Mesh Networks is a kind of typical MANET,
since we certainly could build infrastructure for such networks...

While Sridhara introduce their "mLab", a tool for ad hoc routing protocol
and application developers to bridge the gap between simulations and field testing.
http://csrc.nist.gov/manet
I've read their paper servals month ago,
it's interesting, especially to those who concern security.

Thanks for all of you.

Regards,
--
Luo Gang


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



From manet-bounces@ietf.org Sat May 13 18:08:13 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ff2Fp-0002Su-02; Sat, 13 May 2006 18:06:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ff2Fm-0002S0-W6
	for manet@ietf.org; Sat, 13 May 2006 18:06:26 -0400
Received: from nf-out-0910.google.com ([64.233.182.188])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ff2Fk-00067i-LB
	for manet@ietf.org; Sat, 13 May 2006 18:06:26 -0400
Received: by nf-out-0910.google.com with SMTP id l36so194820nfa
	for <manet@ietf.org>; Sat, 13 May 2006 15:06:23 -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:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
	b=hMuYskoYL41PuHjU+s1X8YZ/ALQvb0p3VoEAq+B85zvb1MVRt/y6ekFJLZlxfQ6H1XMu58pJO7PACdgK+C45ybaDxQNkekYwxnShkIoaehFzkD53IF4upYgNhZ/UQbLxaeyqqfzYJv7LXAIN5TS7eIDiYZ/4LcNCx/PC27tXxYg=
Received: by 10.48.254.16 with SMTP id b16mr2172848nfi;
	Sat, 13 May 2006 15:06:23 -0700 (PDT)
Received: by 10.49.41.15 with HTTP; Sat, 13 May 2006 15:06:23 -0700 (PDT)
Message-ID: <5dd2e0970605131506wdb8878csb43af96a7589176e@mail.gmail.com>
Date: Sat, 13 May 2006 18:06:23 -0400
From: "Paul Ward" <pasward@ccng.uwaterloo.ca>
To: "jasteven@rockwellcollins.com" <jasteven@rockwellcollins.com>
Subject: Re: [manet] MANET protocol stacks
In-Reply-To: <OF4DAEDF8C.A8F8D5B9-ON86257168.005242F9-86257168.0061537C@rockwellcollins.com>
MIME-Version: 1.0
References: <OF4DAEDF8C.A8F8D5B9-ON86257168.005242F9-86257168.0061537C@rockwellcollins.com>
X-Google-Sender-Auth: 5aedc8cf85bb998a
X-Spam-Score: 2.4 (++)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: manet@ietf.org
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0955428342=="
Errors-To: manet-bounces@ietf.org

--===============0955428342==
Content-Type: multipart/alternative; 
	boundary="----=_Part_31647_29804759.1147557983390"

------=_Part_31647_29804759.1147557983390
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

How do you model ExOR as having "nice and graph-theoretic-like" links?

On 5/8/06, jasteven@rockwellcollins.com <jasteven@rockwellcollins.com>
wrote:
>
> Thus, I believe that the MANET work should focus on multiple layers like
> the original Internet model - namely the Internet layer (which may have
> different routing hierarchical domains, but links basically look nice and
> graph-theoretic-like) and Wireless Subnets that may be just a star-like W=
LAN
> based around APs or may be full-blown mesh subnetworks.
>

------=_Part_31647_29804759.1147557983390
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

How do you model ExOR as having &quot;nice and graph-theoretic-like&quot; l=
inks?<br><br><div><span class=3D"gmail_quote">On 5/8/06, <b class=3D"gmail_=
sendername"><a href=3D"mailto:jasteven@rockwellcollins.com">jasteven@rockwe=
llcollins.com
</a></b> &lt;<a href=3D"mailto:jasteven@rockwellcollins.com">jasteven@rockw=
ellcollins.com</a>&gt; wrote:</span><blockquote class=3D"gmail_quote" style=
=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; p=
adding-left: 1ex;">
<div>
<font size=3D"2"><tt></tt></font><font size=3D"2"><tt>Thus, I believe that =
the MANET work should focus on
multiple layers like the original Internet model - namely the Internet
layer (which may have different routing hierarchical domains, but links
basically look nice and graph-theoretic-like) and Wireless Subnets that
may be just a star-like WLAN based around APs or may be full-blown mesh
subnetworks. </tt></font>
<br>
</div></blockquote></div><br>

------=_Part_31647_29804759.1147557983390--


--===============0955428342==
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

--===============0955428342==--




From manet-bounces@ietf.org Sun May 14 09:14:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FfGPA-0005Lp-TG; Sun, 14 May 2006 09:13:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FfGP8-0005Lk-Vc
	for manet@ietf.org; Sun, 14 May 2006 09:13:02 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfGP6-0007Vo-8d
	for manet@ietf.org; Sun, 14 May 2006 09:13:02 -0400
Received: from ex1.ad.dcs.gla.ac.uk ([130.209.249.157]:8213)
	by mr1.dcs.gla.ac.uk with esmtp (Exim 4.42)
	id 1FfGOz-000266-9j; Sun, 14 May 2006 14:12:53 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 14 May 2006 14:12:52 +0100
Message-ID: <BED9D15F73EDDE48BF480604236A4560116F7B@ex1.ad.dcs.gla.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFPs -- MSWiM 2006
Thread-Index: AcZ2+xcPOzEf6WnxQYqfNRJRVPG08wAW3LaH
References: <3832.127.0.0.1.1147572412.squirrel@127.0.0.1>
From: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>
To: <manet@ietf.org>, <podc@acm.org>, <tccc@cs.columbia.edu>,
	<performance@merlot.usc.edu>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 10d2fdecab7a7fa796e06e001d026c91
Cc: 
Subject: [manet] CFPs -- MSWiM 2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1546609882=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1546609882==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67758.1B7B79BB"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67758.1B7B79BB
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

---------------------------------------------------------------------
   Our apologies if you have received multiple copies
----------------------------------------------------------------------
                    ACM/IEEE  MSWiM 2006
-----------------------------------------------------------------------

                        Call for Papers
               The 9th ACM/IEEE International Symposium on
     Modeling, Analysis and Simulation of Wireless and Mobile Systems
                      Torremolinos, SPAIN
                       October 2--6, 2006
                http://www.cs.unibo.it/mswim2006

-------------------------------------------------------------------------=
-
-------------------------------------------------------------------------=
-
Submission deadline has been Extended to May 15th, 2006

-------------------------------------------------------------------------=
-
A Journal Special Issue will be planned with Computer Network, Elsevier.
It will contain selected best papers from MSWiM.
-------------------------------------------------------------------------=
-

*Scope and Overview:
ACM/IEEE MSWiM 2006 is the Ninth Annual International Symposium on
Modeling, Analysis and Simulation of Wireless and Mobile Systems.
MSWiM is an international forum dedicated to high level discussion
of Wireless and Mobile systems, networks, algorithms and applications,
with an emphasis on rigorous performance evaluation.
MSWiM is a highly selective conference that is recognized as one of
the most prestigious sources of innovative ideas and breakthroughs
in the field.  MSWiM 2006 will be held October 2 to 6, 2006,
in sunny Terremolinos, in Spain.

Authors are encouraged to submit full papers presenting new research
related to the theory or practice of all aspects of modeling, analysis
and simulation of mobile and wireless systems.  Submitted papers must
not have been published elsewhere nor currently be under review by
another conference or journal.


*Topics of Interest.  Papers related to wireless and mobile network
Modeling, Analysis, Design, and Simulation are solicited on, but not
limited to, the following topics:

- Analytical Models
- New simulation languages and tools for wireless systems
- Design methodologies
- Performance evaluation and modeling
- Formal methods for analysis of wireless systems
- Wireless Network Protocols
- Wireless Multimedia Systems
- Tools, Prototype and Testbeds
- Wireless PANs, LANs
- Survivability and reliability evaluation
- Ad Hoc Networks
- Traffic measurements and models for wireless networks
- Sensor and Actuator Networks
- RF channel capacity modeling and analysis
- Pervasive computing and emerging models
- QoS provisioning in wireless and mobile networks
- Integration of wired and wireless systems
- Security and privacy of mobile/wireless systems
- Mobility modeling and management
- Algorithms and protocols for energy efficent operation and power =
control
- Mobile applications, system software and algorithms
- Parallel and distributed simulation of wireless systems


Submission instructions and publication can be found at
(http://www.cs.unibo.it/mswim2006).
Accepted papers will appear in the conference proceedings to be =
published
by ACM press.


-------------------------------------------------------------------------=
-
*Important Dates:

Paper submission deadline          May  15 2006
Notification of acceptance         July 5 2006

Tutorial submission deadline       July 5th, 2006
-------------------------------------------------------------------------=
-

General Co-Chairs:
Carla-Fabiana Chiasserini, Politecnico di Torino, Italy
Email: chiasserini@polito.it

Enrique Alba, University of Malaga, Spain
Email: eat@lcc.uma.es

Program Committee Chairs:
Renato Lo Cigno, University of Trento, Italy
Email: cigno@dit.unitn.it

Nael Abu-Ghazaleh, State University of New York at Binghamton, USA
Email: nael@cs.binghamton.edu

Poster Co-Chairs:

Sotiris Nikoletseas
University of Patra, Greece
Email: nikole@cti.gr

Steve Olariu
Old Dominion University, USA
Email: olariu@cs.odu.edu


Tutorial Chair

Mineo Takai
University of Los Angeles, California, USA
Email: mineo@cs.ucla.edu

Local Organization Chair:
Enrique Alba, University of Malaga, Spain




------_=_NextPart_001_01C67758.1B7B79BB
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">=0A=
<TITLE>[MESSAGE NOT SCANNED]</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText7311 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT =0A=
size=3D2>----------------------------------------------------------------=
-----<BR>&nbsp;&nbsp; =0A=
Our apologies if you have received multiple =0A=
copies<BR>---------------------------------------------------------------=
-------<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
ACM/IEEE&nbsp; MSWiM =0A=
2006<BR>-----------------------------------------------------------------=
------<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; =0A=
Call for =0A=
Papers<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; =0A=
The 9th ACM/IEEE International Symposium on<BR>&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Modeling, Analysis and Simulation of Wireless and Mobile =0A=
Systems<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Torremolinos, =0A=
SPAIN<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
October 2--6, =0A=
2006<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
<A =0A=
href=3D"http://www.cs.unibo.it/mswim2006">http://www.cs.unibo.it/mswim200=
6</A><BR><BR>------------------------------------------------------------=
--------------<BR>-------------------------------------------------------=
-------------------<BR>Submission =0A=
deadline has been Extended to May 15th, =0A=
2006<BR><BR>-------------------------------------------------------------=
-------------<BR>A =0A=
Journal Special Issue will be planned with Computer Network, =
Elsevier.<BR>It =0A=
will contain selected best papers from =0A=
MSWiM.<BR>---------------------------------------------------------------=
-----------<BR><BR>*Scope =0A=
and Overview:<BR>ACM/IEEE MSWiM 2006 is the Ninth Annual International =
Symposium =0A=
on<BR>Modeling, Analysis and Simulation of Wireless and Mobile =
Systems.<BR>MSWiM =0A=
is an international forum dedicated to high level discussion<BR>of =
Wireless and =0A=
Mobile systems, networks, algorithms and applications,<BR>with an =
emphasis on =0A=
rigorous performance evaluation.<BR>MSWiM is a highly selective =
conference that =0A=
is recognized as one of<BR>the most prestigious sources of innovative =
ideas and =0A=
breakthroughs<BR>in the field.&nbsp; MSWiM 2006 will be held October 2 =
to 6, =0A=
2006,<BR>in sunny Terremolinos, in Spain.<BR><BR>Authors are encouraged =
to =0A=
submit full papers presenting new research<BR>related to the theory or =
practice =0A=
of all aspects of modeling, analysis<BR>and simulation of mobile and =
wireless =0A=
systems.&nbsp; Submitted papers must<BR>not have been published =
elsewhere nor =0A=
currently be under review by<BR>another conference or =0A=
journal.<BR><BR><BR>*Topics of Interest.&nbsp; Papers related to =
wireless and =0A=
mobile network<BR>Modeling, Analysis, Design, and Simulation are =
solicited on, =0A=
but not<BR>limited to, the following topics:<BR><BR>- Analytical =
Models<BR>- New =0A=
simulation languages and tools for wireless systems<BR>- Design =0A=
methodologies<BR>- Performance evaluation and modeling<BR>- Formal =
methods for =0A=
analysis of wireless systems<BR>- Wireless Network Protocols<BR>- =
Wireless =0A=
Multimedia Systems<BR>- Tools, Prototype and Testbeds<BR>- Wireless =
PANs, =0A=
LANs<BR>- Survivability and reliability evaluation<BR>- Ad Hoc =
Networks<BR>- =0A=
Traffic measurements and models for wireless networks<BR>- Sensor and =
Actuator =0A=
Networks<BR>- RF channel capacity modeling and analysis<BR>- Pervasive =
computing =0A=
and emerging models<BR>- QoS provisioning in wireless and mobile =
networks<BR>- =0A=
Integration of wired and wireless systems<BR>- Security and privacy of =0A=
mobile/wireless systems<BR>- Mobility modeling and management<BR>- =
Algorithms =0A=
and protocols for energy efficent operation and power control<BR>- =
Mobile =0A=
applications, system software and algorithms<BR>- Parallel and =
distributed =0A=
simulation of wireless systems<BR><BR><BR>Submission instructions and =0A=
publication can be found at<BR>(<A =0A=
href=3D"http://www.cs.unibo.it/mswim2006">http://www.cs.unibo.it/mswim200=
6</A>).<BR>Accepted =0A=
papers will appear in the conference proceedings to be published<BR>by =
ACM =0A=
press.<BR><BR><BR>-------------------------------------------------------=
-------------------<BR>*Important =0A=
Dates:<BR><BR>Paper submission =0A=
deadline&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; May&nbsp; =
15 =0A=
2006<BR>Notification of =0A=
acceptance&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; July 5 =0A=
2006<BR><BR>Tutorial submission =
deadline&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
July 5th, =0A=
2006<BR>-----------------------------------------------------------------=
---------<BR><BR>General =0A=
Co-Chairs:<BR>Carla-Fabiana Chiasserini, Politecnico di Torino, =
Italy<BR>Email: =0A=
chiasserini@polito.it<BR><BR>Enrique Alba, University of Malaga, =
Spain<BR>Email: =0A=
eat@lcc.uma.es<BR><BR>Program Committee Chairs:<BR>Renato Lo Cigno, =
University =0A=
of Trento, Italy<BR>Email: cigno@dit.unitn.it<BR><BR>Nael Abu-Ghazaleh, =
State =0A=
University of New York at Binghamton, USA<BR>Email: =0A=
nael@cs.binghamton.edu<BR><BR>Poster Co-Chairs:<BR><BR>Sotiris =0A=
Nikoletseas<BR>University of Patra, Greece<BR>Email: =
nikole@cti.gr<BR><BR>Steve =0A=
Olariu<BR>Old Dominion University, USA<BR>Email: =0A=
olariu@cs.odu.edu<BR><BR><BR>Tutorial Chair<BR><BR>Mineo =
Takai<BR>University of =0A=
Los Angeles, California, USA<BR>Email: mineo@cs.ucla.edu<BR><BR>Local =0A=
Organization Chair:<BR>Enrique Alba, University of Malaga, =0A=
Spain<BR><BR><BR></FONT></DIV></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C67758.1B7B79BB--


--===============1546609882==
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

--===============1546609882==--




From manet-bounces@ietf.org Mon May 15 03:50:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FfXm0-0003hg-8r; Mon, 15 May 2006 03:45:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FfXly-0003gx-9J
	for manet@ietf.org; Mon, 15 May 2006 03:45:46 -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 1FfVxF-0006QL-L1
	for manet@ietf.org; Mon, 15 May 2006 01:49:17 -0400
Received: from evaki.its.uow.edu.au ([130.130.68.32])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FfVoT-0002X1-Dl
	for manet@ietf.org; Mon, 15 May 2006 01:40:17 -0400
Received: from csm-server-nat-ip.its.uow.edu.au ([130.130.68.220]
	helo=febris.its.uow.edu.au)
	by evaki.its.uow.edu.au with esmtp (Exim 4.60)
	(envelope-from <mehrana@uow.edu.au>) id 1FfVoQ-00025S-Kc
	for manet@ietf.org; Mon, 15 May 2006 15:40:10 +1000
Received: from minerva.its.uow.edu.au (csm-server-nat-ip.its.uow.edu.au
	[130.130.68.220]) by febris.its.uow.edu.au (MOS 3.7.5-GA)
	with ESMTP id CRH19092; Mon, 15 May 2006 15:40:09 +1000 (EST)
Received: (from minerva.its.uow.edu.au [130.130.10.111])
	by minerva.its.uow.edu.au (MOS 3.7.5-GA)
	with HTTP/1.1 id AEQ97571 (AUTH mehrana);
	Mon, 15 May 2006 15:40:08 +1000 (EST)
From: <mehrana@uow.edu.au>
To: manet@ietf.org
X-Mailer: Mirapoint Webmail Direct 3.7.5-GA
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20060515154008.AEQ97571@minerva.its.uow.edu.au>
Date: Mon, 15 May 2006 15:40:08 +1000 (EST)
X-Junkmail-Status: score=10/60, host=febris.its.uow.edu.au
X-Junkmail-SD-Raw: score=unknown,
	refid=str=0001.0A090203.44681212.0011,ss=1,fgs=0,
	ip=130.130.68.220, so=2006-03-30 10:46:40,
	dmn=5.2.4/2006-05-04
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 42e3ed3f10a1d8bef690f09da16f507a
Cc: wysocki@uow.edu.au
Subject: [manet] CFP for 5th Workshop of the Internet Telecommunications
 and Signal Processing, WITSP'2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Apologize if you have received multiple copies of this CFP
---------------------------------------------------------

Call for papers

The 5th Workshop on the Internet, Telecommunications and Signal Processing WITSP'06

11th-13th December 2006
Hobart (Tasmania), Australia

www.dspcs-witsp.com


The 5th Workshop of the Internet Telecommunications and Signal Processing, WITSP'2006 has been planned by a group of academics and professionals to provide a forum for exchange of ideas between researchers including postgraduate research students and practicing engineers on all aspects related to the Internet and Telecommunication Systems. The main emphasis, as in all the previous WITSPs is on the use of signal  processing as a tool to make the Internet operate better and more efficiently. However, the scope of the papers considered for the Workshop is not limited just to this area. Contributions are also sought from the area of networking, including protocols, security, and applications. 
In addition, it is expected that, as during the previous events, several contributions will be dealing with image, video and audio processing for multimedia, and forensic applications, the security of private and corporate data, and advanced data processing algorithms. The Organizing 
Committee of the Workshop decided to hold it in Hobart on 11-13 December 2006.

Previously unpublished contributions to the following technical areas, but not limited to, are solicited:

Internet

    * Traffic modelling
    * Protocols
    * Embedded Internet devices
    * New and enhanced services
    * Resource and information management
    * Adaptive QoS provisioning
    * End-to-end QoS
    * Emerging technologies

Fixed Networks

    * Optical networks and switching
    * Network architectures and equipment
    * Programmable networks
    * Test-beds and trials
    * New and enhanced services
    * Network gaming

Wireless Networks

    * Mobile ad hoc networking
    * Personal area networking
    * Convergence of different network types
    * Broadband Wireless Access
    * IP and Mobility
    * Home networking
    * Access technologies
    * Future wireless networks
    * Test-beds and new applications

Telecommunication technology

    * Channel measurements and modelling
    * Coding and modulation techniques
    * MIMO - theory and trials
    * Spread Spectrum and CDMA systems
    * OFDM technology
    * Space-time coding
    * Ultra Wide-Band Communications
    * Antenna systems

Information Security

    * Security primitives and algorithms
    * Security of wireless and distribution networks
    * Programmable networks security
    * Authentication and authorization
    * Encryption
    * Data integrity
    * Data mining

Multimedia signal processing

    * Streamed multimedia applications
    * Algorithms and implementations
    * Image and video processing
    * Error concealment techniques
    * Management of multimedia services
    * Test-beds and trials
    * Multimedia games

DSP algorithms and hardware implementations

    * DSP implementation in hardware
    * DSP algorithms
    * Smart antennas and tracking algorithms
    * Signal separation
    * Signal identification

	
Technical Program Committee

Mehran Abolhasan, University of Wollongong, Australia
Marek Bialkowski, University of Queensland, Australia
Manora Caldera, University of Western Australia, Australia
Mounir Hamdi, Hong Kong University of Science and Technology, Hong Kong
Leandro de Haro, Madrid University of Technology, Spain
Mieso Denko, University of Guelph, Canada
Karu Esselle, Macquarie University, Australia
Peter Farkas, Slovak Technical University, Slovakia
Bernard Guillemin, University of Auckland, New Zealand
John Leis, University of Southern Queensland, Australia
Jerzy Lopatka, Military University of Technology, Poland
Alfred Mertins, University of Oldenburg, Germany
Christian Ritz, University of Wollongong, Australia
Jennifer Seberry, University of Wollongong, Australia
Miroslaw Slominski, Warsaw University of Technology, Poland
Sarah Spence Adams, Franklin W. Olin College of Engineering, USA
David Stirling, University of Wollongong, Australia
Willy Susilo, University of Wollongong, Australia
Lang White, University of Adelaide, Australia
Hamid Sharif, University of Nebraska-Lincoln, USA
Beata Wysocki, University of Wollongong, Australia
Tadeusz Wysocki, University of Wollongong, Australia
Jinhong Yuan, University of New South Wales, Australia
Hans-Juergen Zepernick, Blekinge Institute of Technology, Sweden 

The papers should be emailed to: submissions@dspcs-witsp.com in PDF format. Each full paper of up to 6 double column pages of A4 (single space, font size 10 points minimum) will be peer-reviewed by two independent reviewers and the authors will be notified about the acceptance via email.

Important Dates

Full Paper Submission Deadline: 30 July 2006
Notification of acceptance: 	15 September 2006
Camera-Ready Copy: 		15 October 2006
Registeration:			TBA

For further information please contact:

Assoc. Prof. T Wysocki

Fax: +61 2 4285 7576, E-mail: chair@dspcs-witsp.com 
	


==============================================================
Mehran Abolhasan PhD, MIEEE
Project Leader - Desert Knowledge CRC
Research Fellow - Telecommunications and IT Research Institute (TITR)
University of Wollongong, Northfields Ave, NSW 2522, Australia
Phone: +61 2 4221 3347
Fax: +61 2 4227 3277
www.titr.uow.edu.au/~mehran
Email 1: mehrana@uow.edu.au
Email 2: mehran@titr.uow.edu.au

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



From manet-bounces@ietf.org Mon May 15 03:58:35 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FfXvq-0006DT-TQ; Mon, 15 May 2006 03:55:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FfXvp-0006CT-JG
	for manet@ietf.org; Mon, 15 May 2006 03:55:57 -0400
Received: from bay0-omc2-s9.bay0.hotmail.com ([65.54.246.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfXvo-0003k7-6Y
	for manet@ietf.org; Mon, 15 May 2006 03:55:57 -0400
Received: from BAY116-W6 ([64.4.38.106]) by bay0-omc2-s9.bay0.hotmail.com with
	Microsoft SMTPSVC(6.0.3790.211); Mon, 15 May 2006 00:55:55 -0700
X-Originating-IP: [131.107.0.88]
X-Originating-Email: [alec.wolman@hotmail.com]
Message-ID: <BAY116-W6F5C2FBA37005500282BAFCA30@phx.gbl>
MIME-Version: 1.0
From: "Alec Wolman" <alec.wolman@hotmail.com>
To: <manet@ietf.org>
Date: Mon, 15 May 2006 00:55:55 -0700
X-OriginalArrivalTime: 15 May 2006 07:55:55.0600 (UTC)
	FILETIME=[FEBA8500:01C677F4]
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Subject: [manet] Reminder: May 15th is the MobiSys 2006 Early Registration
	Deadline
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0195347920=="
Errors-To: manet-bounces@ietf.org

--===============0195347920==
Content-Type: multipart/alternative;
	boundary="_ce59643e-26e4-47ed-aa52-ff18d053710d_"

--_ce59643e-26e4-47ed-aa52-ff18d053710d_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


***************************
=20
Call for participation
MobiSys 2006 - The Fourth International Conference on Mobile Systems, Appli=
cations, and Services
Uppsala, Sweden, June 19-22, 2006.
=20
***************************
=20
See the MobiSys website - http://www.sigmobile.org/mobisys/2006/index.html =
for details on the program and registration information.
=20
_________________________________________________________________
Enter the Windows Live Mail beta sweepstakes
http://www.imagine-msn.com/minisites/sweepstakes/mail/register.aspx=

--_ce59643e-26e4-47ed-aa52-ff18d053710d_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>=0A=
<head>=0A=
<style>=0A=
P=0A=
{=0A=
margin:0px;=0A=
padding:0px=0A=
}=0A=
body=0A=
{=0A=
FONT-SIZE: 10pt;=0A=
FONT-FAMILY:Tahoma=0A=
}=0A=
</style>=0A=
</head>=0A=
<body><FONT size=3D2 >
<P >***************************</P>
<P >&nbsp;</P>
<P >Call for participation</P>
<P ><FONT class=3D"">MobiSys</FONT> 2006 - The Fourth International Confere=
nce on Mobile Systems, Applications, and Services</P>
<P >Uppsala, Sweden, June 19-22, 2006.</P>
<P >&nbsp;</P>
<P >***************************</P>
<P >&nbsp;</P>
<P >See the <FONT class=3D"" >MobiSys</FONT> website - </FONT><A href=3D"ht=
tp://www.sigmobile.org/mobisys/2006/index.html" ><U ><FONT color=3D#0000ff =
size=3D2 >http://www.sigmobile.org/<FONT class=3D"">mobisys</FONT>/2006/ind=
ex.html</U></FONT></A><FONT size=3D2 > for details on the program and regis=
tration information.</FONT></P>
<P ><FONT size=3D2 >&nbsp;</P></FONT><br /><hr />Upgrade for free to Window=
s Live Mail beta and you could win an African Safari <a href=3D'http://www.=
imagine-msn.com/minisites/sweepstakes/mail/register.aspx' target=3D'_new'>L=
earn more</a></body>=0A=
</html>=

--_ce59643e-26e4-47ed-aa52-ff18d053710d_--


--===============0195347920==
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

--===============0195347920==--




From manet-bounces@ietf.org Mon May 15 07:35:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FfbLW-0000On-Pr; Mon, 15 May 2006 07:34:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FfbLV-0000Oh-CU
	for manet@ietf.org; Mon, 15 May 2006 07:34:41 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfbLR-000516-05
	for manet@ietf.org; Mon, 15 May 2006 07:34:41 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	284784F013E
	for <manet@ietf.org>; Mon, 15 May 2006 13:34:30 +0200 (CEST)
Received: from esealmw126.eemea.ericsson.se ([153.88.254.170]) by
	esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 15 May 2006 13:34:29 +0200
Received: from esealnt747.al.sw.ericsson.se ([153.88.251.7]) by
	esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 15 May 2006 13:34:29 +0200
Received: by ESEALNT747.al.sw.ericsson.se with Internet Mail Service
	(5.5.2653.19) id <J44W0FBM>; Mon, 15 May 2006 13:34:29 +0200
Message-ID: <A1268066EC4D5E458783200F89AEF31F0A5E5FCB@eiedbnt503>
From: "Srdjan Krco (BH/LMI)" <srdjan.krco@ericsson.com>
To: manet@ietf.org
Date: Mon, 15 May 2006 13:35:05 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-OriginalArrivalTime: 15 May 2006 11:34:29.0749 (UTC)
	FILETIME=[875EDA50:01C67813]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ba0d4c5f57f7c289496fce758bbf4798
Subject: [manet] 2nd call: Summer school on Applications of Wireless Sensor
	Networ ks 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0822521234=="
Errors-To: manet-bounces@ietf.org


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0822521234==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67813.9CDB526E"


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C67813.9CDB526E
Content-Type: text/plain

Sorry for cross postings. Please feel free to distribute.


=========================================================== 

Summer School on Applications of Wireless Sensor Networks 

===========================================================
July 31 - Aug 4, 2006, School of Technical Sciences, University of Novi Sad, Serbia and Montenegro 

+ + + 

Telematics, telemedicine, environmental monitoring, home applications and control, security and surveillance, industrial applications like process industry automation and agricultural applications are examples of potential applications of wireless sensor networks. Thanks to its broad range of possible applications and potential to change the way we interact with our environment, wireless sensor networks have gained a lot of attention in the research world and are becoming increasingly popular in business world as well. The goal of this summer school is to:

- survey the most relevant research domains
- present various perspectives and underlying technologies
- discuss integration of sensor information into applications
- identify the most important challenges and research themes
- interact with distinguished scholars and establish contacts that may lead to research collaborations in the future. 

The intended audience are post-graduate students, PhD students, and young researchers from universities and industrial laboratories around the world.
We expect about 40 participants.

PROGRAM (tentative)
The summer school will last for 5 days and will feature a number of different activities
- Lectures: Each day will feature lectures and discussions around a research theme like integration of WSN with mobile networks, security in WSN, ZigBee vs. Bluetooth, remote health monitoring, integration of context information delivered by sensors into applications, etc. Lecturers include prof. Ivan Stojmenovic (University of Ottawa), prof. David Simplot-Ryl (University of Lille), Konrad Wrona (SAP Research), Srdjan Krco (Ericsson Ireland), Vlasios Tsiatis (Ericsson Research). 

- Participants Workshop: All participants will have an opportunity to present their own work and involvement in the field. 

- Application Competition: Participants can submit their ideas about application scenarios involving sensor networks and smart objects. 
- Design and development paradigms: Introduction to design and programming of wireless sensor network applications. 
- Social activities: One day is scheduled for an excursion; a dinner party will be organized as well as other social activities, which should help to form a community among the young researchers.

VENUE
The summer school will take place at the Faculty of Technical Sciences (http://www.ftn.ns.ac.yu <http://www.ftn.ns.ac.yu> ), University of Novi Sad (http://www.ns.ac.yu <http://www.ns.ac.yu> ), Serbia and Montenegro. Novi Sad (http://www.gradnovisad.org.yu <http://www.gradnovisad.org.yu> ) is a beautiful and friendly city, where citizens, cheerful and in the good mood, welcome you honestly, sincerely and friendly. It is an university, economic and cultural centre ("Athens of Serbia"), located on the banks of the Danube river in the northern part of Serbia, 80km from Belgrade and 100km from the Serbia-Hungary border, easily accessible by air (Belgrade or Budapest airports), car, train or bus. Beautiful Petrovaradin fortress, located on a hill above the Danube river, the "Gibraltar on the Danube" as it used to be called, is the venue of the EXIT, one of the biggest music festivals in Europe, and the main city landmark. University campus is located on the opposite bank of the ri
 ver and has an easy access to sandy river beaches as well as city centre and other  amenities. National park Fruska Gora, a mountain located nearby the city, provides an excellent opportunity for long walks in beautiful surroundings.
It also hosts a number of old ortodox monasteries which are worth visit. 

REGISTRATION, COSTS and TRAVELLING
Participation is open to all qualified applicants, but the number of participants is limited to a maximum of 40. If we receive more applications, we will select participants based on their work area and background, geographic distribution, and date of registration. To indicate an interest to participate, please send an e-mail with the pertinent information (name, contact information, research area and

background) to srdjan.krco@ericsson.com. 
The registration fee of EUR 250 includes accommodation at University of Novi Sad Student centre and all meals. 
Participants are expected to arrive in the afternoon or evening of Sunday, July 30th. The school will start on Monday morning and end on Friday afternoon. 

IMPORTANTS DATES
Application deadline: June 2, 2006
Notification of admittance: June 9, 2006 

ORGANIZATION
The summer school is jointly organized by the European research project MOSQUITO, Ericsson Ireland and University of Novi Sad.

Konrad Wrona and Srdjan Krco
SAP Research France and LM Ericsson Ireland  


_____________________________
Srdjan Krco
Systems Manager

Ericsson R&D Ireland
3G Transport Network Solutions
E-mail: srdjan.krco@ericsson.com
Phone:+353 1 2072238

NOTE: If you still have my old e-mail address srdjan.krco@eei.ericsson.se, please update with the new one: srdjan.krco@ericsson.com


------_=_NextPart_001_01C67813.9CDB526E
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2658.34">
<TITLE>2nd call: Summer school on Applications of Wireless Sensor =
Networks </TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">Sorry for cross postings. Please feel =
free to distribute.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Courier =
New">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Summer School on Applications of =
Wireless Sensor Networks </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier =
New">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">July 31 - Aug 4, 2006, School =
of Technical Sciences, University of Novi Sad, Serbia and Montenegro =
</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">+ + + </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Telematics, telemedicine, =
environmental monitoring, home applications and control, security and =
surveillance, industrial applications like process industry automation =
and agricultural applications are examples of potential applications of =
wireless sensor networks. Thanks to its broad range of possible =
applications and potential to change the way we interact with our =
environment, wireless sensor networks have gained a lot of attention in =
the research world and are becoming increasingly popular in business =
world as well. The goal of this summer school is to:</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">- survey the most relevant =
research domains</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">- present various perspectives =
and underlying technologies</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">- discuss integration of sensor =
information into applications</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">- identify the most important =
challenges and research themes</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">- interact with distinguished =
scholars and establish contacts that may lead to research =
collaborations in the future. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">The intended audience are =
post-graduate students, PhD students, and young researchers from =
universities and industrial laboratories around the world.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">We expect about 40 =
participants.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">PROGRAM (tentative)</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">The summer school will last for =
5 days and will feature a number of different activities</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">- Lectures: Each day will =
feature lectures and discussions around a research theme like =
integration of WSN with mobile networks, security in WSN, ZigBee vs. =
Bluetooth, remote health monitoring, integration of context information =
delivered by sensors into applications, etc. Lecturers include prof. =
Ivan Stojmenovic (University of Ottawa), prof. David Simplot-Ryl =
(University of Lille), Konrad Wrona (SAP Research), Srdjan Krco =
(Ericsson Ireland), Vlasios Tsiatis (Ericsson Research). </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">- Participants Workshop: All =
participants will have an opportunity to present their own work and =
involvement in the field. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">- Application Competition: =
Participants can submit their ideas about application scenarios =
involving sensor networks and smart objects. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">- Design and development =
paradigms: Introduction to design and programming of wireless sensor =
network applications. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">- Social activities: One day is =
scheduled for an excursion; a dinner party will be organized as well as =
other social activities, which should help to form a community among =
the young researchers.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">VENUE</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">The summer school will take =
place at the Faculty of Technical Sciences (</FONT><A =
HREF=3D"http://www.ftn.ns.ac.yu"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">http://www.ftn.ns.ac.yu</FONT></U></A><FONT =
SIZE=3D2 FACE=3D"Courier New">), University of Novi Sad (</FONT><A =
HREF=3D"http://www.ns.ac.yu"><U><FONT COLOR=3D"#0000FF" SIZE=3D2 =
FACE=3D"Courier New">http://www.ns.ac.yu</FONT></U></A><FONT SIZE=3D2 =
FACE=3D"Courier New">), Serbia and Montenegro. Novi Sad (</FONT><A =
HREF=3D"http://www.gradnovisad.org.yu"><U><FONT COLOR=3D"#0000FF" =
SIZE=3D2 FACE=3D"Courier =
New">http://www.gradnovisad.org.yu</FONT></U></A><FONT SIZE=3D2 =
FACE=3D"Courier New">) is a beautiful and friendly city, where =
citizens, cheerful and in the good mood, welcome you honestly, =
sincerely and friendly. It is an university, economic and cultural =
centre (&quot;Athens of Serbia&quot;), located on the banks of the =
Danube river in the northern part of Serbia, 80km from Belgrade and =
100km from the Serbia-Hungary border, easily accessible by air =
(Belgrade or Budapest airports), car, train or bus. Beautiful =
Petrovaradin fortress, located on a hill above the Danube river, the =
&quot;Gibraltar on the Danube&quot; as it used to be called, is the =
venue of the EXIT, one of the biggest music festivals in Europe, and =
the main city landmark. University campus is located on the opposite =
bank of the river and has an easy access to sandy river beaches as well =
as city centre and other&nbsp; amenities. National park Fruska Gora, a =
mountain located nearby the city, provides an excellent opportunity for =
long walks in beautiful surroundings.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">It also hosts a number of old =
ortodox monasteries which are worth visit. </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">REGISTRATION, COSTS and =
TRAVELLING</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Participation is open to all =
qualified applicants, but the number of participants is limited to a =
maximum of 40. If we receive more applications, we will select =
participants based on their work area and background, geographic =
distribution, and date of registration. To indicate an interest to =
participate, please send an e-mail with the pertinent information =
(name, contact information, research area and</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">background) to =
srdjan.krco@ericsson.com. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">The registration fee of EUR 250 =
includes accommodation at University of Novi Sad Student centre and all =
meals. </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Participants are expected to =
arrive in the afternoon or evening of Sunday, July 30th. The school =
will start on Monday morning and end on Friday afternoon. </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">IMPORTANTS DATES</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Application deadline: June 2, =
2006</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">Notification of admittance: =
June 9, 2006 </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">ORGANIZATION</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">The summer school is jointly =
organized by the European research project MOSQUITO, Ericsson Ireland =
and University of Novi Sad.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">Konrad Wrona and Srdjan =
Krco</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Courier New">SAP Research France and LM =
Ericsson Ireland&nbsp; </FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">_____________________________</FONT>
<BR><B><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Srdjan =
Krco</FONT></B>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Systems Manager</FONT>
</P>

<P><B><FONT SIZE=3D2 FACE=3D"Arial">Ericsson R&amp;D Ireland</FONT></B>
<BR><FONT SIZE=3D2 FACE=3D"Arial">3G Transport Network Solutions</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">E-mail: =
srdjan.krco@ericsson.com</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Phone:+353 1 2072238</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">NOTE: If you still have my old e-mail =
address srdjan.krco@eei.ericsson.se, please update with the new one: =
srdjan.krco@ericsson.com</FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C67813.9CDB526E--


--===============0822521234==
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

--===============0822521234==--




From manet-bounces@ietf.org Mon May 15 08:25:53 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ffc6N-0004eV-7J; Mon, 15 May 2006 08:23:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ffc6K-0004eI-IS
	for manet@ietf.org; Mon, 15 May 2006 08:23:04 -0400
Received: from py-out-1112.google.com ([64.233.166.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ffc6F-0008Go-Tm
	for manet@ietf.org; Mon, 15 May 2006 08:23:04 -0400
Received: by py-out-1112.google.com with SMTP id e30so1064194pya
	for <manet@ietf.org>; Mon, 15 May 2006 05:22:59 -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:references:subject:date:organization:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole:sender;
	b=Bh0FHfyzf5yAkxZygM6PsyfTqYGaMGGokWG2ddE0pOiVb05xAOXIgJ/QyiFIIu6LTNvpVpJaJzWVFoz88Q0Sz5tPi5oqh2PSA12RvhAqPwksWqoX5a01hl9wS3ySRAEj5x3ddWAveZTRPAApstQrQYF4d9MpD2L/SWITvr5zSTk=
Received: by 10.35.22.17 with SMTP id z17mr1345697pyi;
	Mon, 15 May 2006 05:22:59 -0700 (PDT)
Received: from IBMD2594A07A1F ( [59.189.78.190])
	by mx.gmail.com with ESMTP id y21sm148284pyd.2006.05.15.05.22.56;
	Mon, 15 May 2006 05:22:58 -0700 (PDT)
Message-ID: <011101c6781a$46789bf0$0200a8c0@IBMD2594A07A1F>
From: "Yan ZHANG" <yanzhang@ieee.org>
To: <manet@ietf.org>, <tccc@cs.columbia.edu>, <itc@comsoc.org>,
	<multicomm@comsoc.org>
References: <021b01c6546b$ea509020$3101a8c0@sin.crl.com.sg>
	<02b601c65ea0$e5d5cc10$3101a8c0@sin.crl.com.sg>
Date: Mon, 15 May 2006 20:22:42 +0800
Organization: Simula
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: hshwchen@ieee.org
Subject: [manet] Call for Book Chapter: Wireless Metropolitan Area Networks
	(Deadline Approaching...)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Yan ZHANG <yanzhang@ieee.org>
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

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

CALL FOR BOOK CHAPTER

Title: Wireless Metropolitan Area Networks
(to be published by Auerbach Publications, CRC Press
http://www.crcpress.com/)

http://yanzhangsg.googlepages.com/WirelessMANCFP.html

Introduction
============
Wireless Metropolitan Area Networks ( Wireless MAN) is emerging as a highly
promising Broadband Wireless Access (BWA) technology to provide high-speed,
high-bandwidth and high-capacity multimedia services for residential as well
as enterprise applications. It is observed that Wireless MAN (e.g. WiMAX) is
even regarded as 4G technology. On 7, Dec. 2005, IEEE just released the
latest version IEEE 802.16e to support the mobility capability, which marks
the maturation of BWA. For the success of the Wireless MAN, great efforts in
the research and industry communities are in progress to address the
problems in all layers of protocol stack.

This book provides readers a comprehensive technical, practical, deploying,
policy guidance covering fundamentals and recent advances in general
Wireless MAN, as well as the latest standard specifications in IEEE
802.16a/c/d/e families. The primary focus of this book is the basic concepts
introduction, fundamentals exploration, standard specifications, security
management, effective protocols, practical system integration, performance
theory/analysis model, simulation and experiment, and future directions in
the Wireless MAN.

Recommended Topics(not limited to)
==================================
MIMO, smart antenna and distributed antenna systems
Efficient signal processing algorithms for Wireless MAN
Cooperative transmission and reception
Capacity and connectivity
Spectrum management
Cognitive radio
OFDM-based Wireless MAN
OFDM+MIMO Wireless MAN
MAC in the emerging standards for Wireless MAN, e.g. IEEE 802.16a/d/e, WiBro
MAC in multi-radio/multi-channel multi-hop Wireless MAN
MAC with directional/smart antenna in Wireless MAN
MAC in single-hop and multi-hop Wireless MAN
Routing, broadcasting, multicasting, anycasting
Routing in Multi-radio/multi-channel multi-hop Wireless MAN
Dynamic/adaptive/distributed channel assignment algorithms
Call admission control for Wireless MAN
Topology control
Scalability
Fault-tolerance
Load balancing
Link adaptation
Scheduling and congestion control
Multimedia services
Quality-of-Service architecture, algorithms and provision
Handoff management, mobility management architecture and strategy
Network management and control
PHY-MAC-RLC-RRC-Routing cross-layer design, modeling and optimization
Mobility, resource, energy, security management mechanisms and interactions
Access authentication, trustworthy networks, privacy and security models
Wireless MAN system introduction
Testbed, prototype, practical system architecture for Wireless MAN
Standardization activities, specifications and enhancements in the emerging
standards 802.16a/d/e
Point-to-point, point-to-multipoint, multi-hop and mesh working mode
3G, B3G, 4G, Wireless PAN, Wireless LAN and Wireless MAN integration
Interference management and public policy
Multi-radio, multi-channel and multi-hop systems
Performance analysis, simulation and experiment
Anomaly, intrusion detection and error recovery
Case studies and market analysis


Important Dates
===============
You are invited to submit a 1-2 pages proposal discribing the topic of your
chapter. The proposal should include the chapter organization, number of
pages of the final manuscript and contact authors. Deadline: 30, May 2006
Notification of proposal acceptance: 15, June 2006
Full chapter submission: 30, Aug. 2006
Review report received: 30, Sep. 2006
Final version submission: 30, Oct. 2006

Manuscript Submission
=====================
*Set as double-spaced
*Estimated, each chapter should has about 20 pages in the typeset format;
i.e. about 35-45 pages with double-space format.
***Note: each lead chapter author will get a free copy of the book.

Contact
========
Please make correspondence and paper submissions to:

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

Dr. Hsiao-Hwa Chen
National Sun Yat-Sen University
Email: hshwchen@ieee.org




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



From manet-bounces@ietf.org Mon May 15 09:02:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FfchM-0006G8-6A; Mon, 15 May 2006 09:01:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FfchK-0006G2-2d
	for manet@ietf.org; Mon, 15 May 2006 09:01:18 -0400
Received: from wr-out-0506.google.com ([64.233.184.238])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FfchH-0002TS-BW
	for manet@ietf.org; Mon, 15 May 2006 09:01:18 -0400
Received: by wr-out-0506.google.com with SMTP id 71so812358wri
	for <manet@ietf.org>; Mon, 15 May 2006 06:01:13 -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:x-google-sender-auth;
	b=ddi/u1H7uN34iac5QE1Kz/rSWI4BgDkiJs88FAI0GZO99/gaxJ9GPzMMj653B4qiwtUEkS11wANmy0lz5mWxd+Z2yRbWh9vD7Clvk7v8i2RFnbCy+5+RWDMiCZ0IN9GdQ0XIdPzPFb0IHrOjGVfQKwTJIxqkX2quDg5lzf2pbgg=
Received: by 10.65.218.14 with SMTP id v14mr1742005qbq;
	Mon, 15 May 2006 06:01:12 -0700 (PDT)
Received: by 10.65.124.18 with HTTP; Mon, 15 May 2006 06:01:12 -0700 (PDT)
Message-ID: <83d5521f0605150601p5847eb90n7ebe3feb7a7419a7@mail.gmail.com>
Date: Mon, 15 May 2006 09:01:12 -0400
From: "Zheng Jun" <junzheng@ieee.org>
To: itc@comsoc.org, manet@ietf.org, multicomm@comsoc.org, tccc@cs.columbia.edu,
	"Miao Ma" <miaom@i2r.a-star.edu.sg>, "Yan Zhang" <yanzhang@ieee.org>
MIME-Version: 1.0
X-Google-Sender-Auth: 4ec48105aab7b8d3
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 4fc59e88b356924367ae169e6a06365d
Cc: 
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  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1708118416=="
Errors-To: manet-bounces@ietf.org

--===============1708118416==
Content-Type: multipart/alternative; 
	boundary="----=_Part_45720_20709752.1147698072810"

------=_Part_45720_20709752.1147698072810
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

We apologize in advance if you receive multiple copies of this CFP
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

CALL FOR 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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Security, defined as ensuring protected communication among terminals,
networks and services, is one of the most significant components in wireles=
s
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
=3D=3D=3D=3D=3D=3D=3D=3D
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 an=
d
concepts related to security in various wireless systems. This handbook wil=
l
be written by the leading experts in the field from both academics and
industries.

Recommended Topics include, but are not limited to:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Chapter proposals should clearly outline the purpose and organization of th=
e
chapter. Upon acceptance of chapter proposals, authors will be sent chapter
guidelines. Drafts of chapters must be between 5,000-7,500 words and includ=
e
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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
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
=3D=3D=3D=3D=3D=3D=3D=3D
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_45720_20709752.1147698072810
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

We apologize in advance if you receive multiple copies of this CFP<br>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br><div style=3D"direction: l=
tr;">

<br>

CALL FOR BOOK CHAPTER<br>

<br>

Title: Handbook of Research on Wireless Security<br>

Publisher: Idea Group Reference, USA (<a href=3D"http://www.idea-group-ref.=
com/" target=3D"_blank" onclick=3D"return top.js.OpenExtLink(window,event,t=
his)">http://www.idea-group-ref.com</a>)<br>

Further information:<br>

<a href=3D"http://yanzhangsg.googlepages.com/WirelessSecurityCFP.html" targ=
et=3D"_blank" onclick=3D"return top.js.OpenExtLink(window,event,this)">http=
://yanzhangsg.googlepages.com/WirelessSecurityCFP.html</a><br>

<br>

Background &amp; Goal<br>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>

Security, defined as ensuring protected communication among terminals,<br>

networks and services, is one of the most significant components in wireles=
s<br>

systems. Both architectures and protocols on security have been extensively=
<br>

studied in academics and industries. This handbook aims to provide a<br>

comprehensive guide on security-related subjects in the wireless<br>

communication field, and it will be a valuable reference for students,<br>

instructors, researchers, engineers and strategists in this field.<br>

<br>

Coverage<br>

=3D=3D=3D=3D=3D=3D=3D=3D<br>

Wireless security is explored with various challenges in diverse<br>

environments and standards, such as authentication, encryption, key<br>

distribution and management, etc. This handbook will feature chapters<br>

(5,000-7,500 words) and provide an in-depth description of terminologies an=
d<br>

concepts related to security in various wireless systems. This handbook wil=
l<br>

be written by the leading experts in the field from both academics and<br>

industries.<br>

<br>

Recommended Topics include, but are not limited to:<br>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<br>

Security in mobile ad hoc networks<br>

Security in peer-to-peer networks<br>

Security in Wireless Mesh Networking<br>

Security in Wireless Sensor Network<br>

Security in Wireless Personal Area Network (WPAN)<br>

Security in Wireless Local Area Network (WLAN)<br>

Security in Wireless Metropolitan Area Network (WMAN)<br>

Security in Wireless Wide Area Network (WAN)<br>

Security in GSM, GPRS<br>

Security in UMTS, CDMA2000, TD-SCDMA<br>

Security in B3G, 4G<br>

Security in Bluetooth and WiMAX<br>

Security in IEEE 802.x families<br>

Security in wireless multimedia systems<br>

Security architecture in heterogeneous networks<br>

Secure PHY/MAC/routing protocols<br>

Secure group communication/multicast<br>

Secure cross-layer protocols<br>

Secure location-based service<br>

Trustworthy networks; authentication, privacy and security models<br>

Fault tolerance, anomaly detection and error recovery schemes<br>

Security and privacy protection<br>

Vulnerability analysis and countermeasures<br>

Tradeoff between performance and security<br>

Authentication, authorization and access control<br>

Data confidentiality and integrity<br>

Encryption and decryption<br>

Key distribution and management<br>

Identity management<br>

Intrusion and anomaly detection<br>

Fraudulent usage<br>

Secure billing<br>

Secure self-configuration<br>

Secure service discovery<br>

Testbed, prototype, practical system and case studies<br>

<br>

Submission Guidelines<br>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>

Chapter proposals should clearly outline the purpose and organization of th=
e<br>

chapter. Upon acceptance of chapter proposals, authors will be sent chapter=
<br>

guidelines. Drafts of chapters must be between 5,000-7,500 words and includ=
e<br>

7-10 related terms and their appropriate definitions. All chapters will<br>

undergo a double-blind peer review. This book is tentatively scheduled for<=
br>

publishing by Idea Group Reference (<a href=3D"http://www.idea-group.com/re=
ference/" target=3D"_blank" onclick=3D"return top.js.OpenExtLink(window,eve=
nt,this)">http://www.idea-group.com/reference/</a>),<br>

an imprint of Idea Group Inc. in early 2008.<br>

<br>

Important Dates<br>

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>

31 July, 2006: Proposal due<br>

31 August, 2006: Notification of proposal acceptance<br>

15 December, 2006: Draft of chapter due<br>

30 April, 2007: Notification of chapter acceptance<br>

Early of 2008: Publication of handbook<br>

<br>

Contact<br>

=3D=3D=3D=3D=3D=3D=3D=3D<br>

Inquiries and submissions can be forwarded to the editors:<br>

<br>

Dr. Yan ZHANG<br>

National Institute of Information and Communications Technology<br>

Email: yanzhang &lt;AT&gt; <a href=3D"http://ieee.org/" target=3D"_blank" o=
nclick=3D"return top.js.OpenExtLink(window,event,this)">ieee.org</a><br>

<br>

Dr. Jun ZHENG<br>

Queens College, City University of New York, USA<br>

Email: zheng &lt;AT&gt; <a href=3D"http://cs.qc.edu/" target=3D"_blank" onc=
lick=3D"return top.js.OpenExtLink(window,event,this)">cs.qc.edu</a><br>

<br>

Dr. Miao MA<br>

Institute of Infocomm Research, Singapore<br>

Email: miaom &lt;AT&gt; <a href=3D"http://i2r.a-star.edu.sg/" target=3D"_bl=
ank" onclick=3D"return top.js.OpenExtLink(window,event,this)">i2r.a-star.ed=
u.sg</a></div>


------=_Part_45720_20709752.1147698072810--


--===============1708118416==
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

--===============1708118416==--




From manet-bounces@ietf.org Mon May 15 10:12:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ffdn3-00087O-F9; Mon, 15 May 2006 10:11:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ffdn2-00087J-7e
	for manet@ietf.org; Mon, 15 May 2006 10:11:16 -0400
Received: from fw01.rockwellcollins.com ([205.175.225.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ffdmz-00056s-TF
	for manet@ietf.org; Mon, 15 May 2006 10:11:16 -0400
Received: by fw01.rockwellcollins.com; id JAA28001;
	Mon, 15 May 2006 09:11:07 -0500 (CDT)
From: <jasteven@rockwellcollins.com>
Received: from nodnsquery(131.198.169.132) by fw01.rockwellcollins.com via
	smap (V5.5) id xma027547; Mon, 15 May 06 09:10:27 -0500
Received: from vs02.rockwellcollins.com (localhost [127.0.0.1])
	by localhost.rockwellcollins.com (Postfix) with ESMTP
	id 312D031873; Mon, 15 May 2006 09:10:28 -0500 (CDT)
Received: from crnotes2.rockwellcollins.com (crnotes2.rockwellcollins.com
	[131.198.64.109]) by vs02.rockwellcollins.com (Postfix) with ESMTP
	id 1574C31868; Mon, 15 May 2006 09:10:28 -0500 (CDT)
In-Reply-To: <5dd2e0970605131506wdb8878csb43af96a7589176e@mail.gmail.com>
To: manet@ietf.org
Subject: Re: [manet] MANET protocol stacks
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.2 June 01, 2004
Message-ID: <OFBB686671.A0F45E82-ON8625716F.004D290B-8625716F.004DDB6B@rockwellcollins.com>
Date: Mon, 15 May 2006 09:10:24 -0500
X-MIMETrack: Serialize by Router on
	CollinsCRSMTP02/CedarRapids/RockwellCollins(Release
	6.5.4FP3|January 09, 2006) at 05/15/2006 09:10:28 AM,
	Serialize complete at 05/15/2006 09:10:28 AM
X-Spam-Score: 0.7 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: pasward@ccng.uwaterloo.ca
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0573500157=="
Errors-To: manet-bounces@ietf.org

This is a multipart message in MIME format.
--===============0573500157==
Content-Type: multipart/alternative;
	boundary="=_alternative 004DDB5C8625716F_="

This is a multipart message in MIME format.
--=_alternative 004DDB5C8625716F_=
Content-Type: text/plain; charset="US-ASCII"

Paul,

When you asked on 5/13/06 about how to model ExOR as having "nice and 
graph-theoretic-like" links, I think that your email implies that we are 
in agreement that wireless mesh networks have lots of interactions and 
effects that make it important to have merged cross-layer aware protocols 
rather than segregated cross-layer unaware protocols.

So, I recommend that we perform this cross-layer MAC/networking in the 
subnet below the Internet Protocol - leaving the Internet Protocol to 
operate with "nice and graph-theoretic-like" links.  So I would think that 
things like ExOR should be performed at a subnet (merged layer 3A/2) below 
IP rather than at a layer 3B.

Jim Stevens

--=_alternative 004DDB5C8625716F_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Paul,</font>
<br>
<br><font size=2 face="sans-serif">When you asked on 5/13/06 about how
to model ExOR as having &quot;nice and graph-theoretic-like&quot; links,
I think that your email implies that we are in agreement that wireless
mesh networks have lots of interactions and effects that make it important
to have merged cross-layer aware protocols rather than segregated cross-layer
unaware protocols.</font>
<br>
<br><font size=2 face="sans-serif">So, I recommend that we perform this
cross-layer MAC/networking in the subnet below the Internet Protocol -
leaving the Internet Protocol to operate with &quot;nice and graph-theoretic-like&quot;
links. &nbsp;So I would think that things like ExOR should be performed
at a subnet (merged layer 3A/2) below IP rather than at a layer 3B.</font>
<br>
<br><font size=2 face="sans-serif">Jim Stevens</font>
<br>
--=_alternative 004DDB5C8625716F_=--


--===============0573500157==
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

--===============0573500157==--




From manet-bounces@ietf.org Mon May 15 11:11:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ffej7-00085x-5Z; Mon, 15 May 2006 11:11:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ffej6-00085k-4B
	for manet@ietf.org; Mon, 15 May 2006 11:11:16 -0400
Received: from web25106.mail.ukl.yahoo.com ([217.12.10.54])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Ffej3-00077N-NQ
	for manet@ietf.org; Mon, 15 May 2006 11:11:16 -0400
Received: (qmail 51704 invoked by uid 60001); 15 May 2006 15:11:12 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr;
	h=Message-ID:Received:Date:From:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=aRynlMlqq/TBu0RRv7+9TOoWnmTyDpG+7FK86A6A8oaqYxIOgmk6Bw79B7iCvnxkizsPx6h2eQi9t7fP630cwokeXd1TYFWMw8LoGSMMe+nuJ0UYexP4facnbq33QbNChBtQ8WLOQiEuS/gpFMfBGDdLsgFGlpcMd0QSU6jDyPo=
	; 
Message-ID: <20060515151112.51702.qmail@web25106.mail.ukl.yahoo.com>
Received: from [193.95.37.75] by web25106.mail.ukl.yahoo.com via HTTP;
	Mon, 15 May 2006 17:11:12 CEST
Date: Mon, 15 May 2006 17:11:12 +0200 (CEST)
From: nawel salhi <salhi_nawel_2005@yahoo.fr>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 2.5 (++)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [manet] (no subject)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1761655650=="
Errors-To: manet-bounces@ietf.org

--===============1761655650==
Content-Type: multipart/alternative; boundary="0-300756718-1147705872=:51392"
Content-Transfer-Encoding: 8bit

--0-300756718-1147705872=:51392
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

please i want to know how use ns to simulate wimax and how can i get wimax patch
		
---------------------------------
 Faites de Yahoo! votre page d'accueil sur le web pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. Cliquez ici.
--0-300756718-1147705872=:51392
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

please i want to know how use ns to simulate wimax and how can i get wimax patch<p>
		<hr size="1" /> 
<b>Faites de Yahoo! votre page d'accueil sur le web</b> pour retrouver directement vos services préférés : vérifiez vos nouveaux mails, lancez vos recherches et suivez l'actualité en temps réel. <a href="http://us.rd.yahoo.com/mail/mail_taglines/yahoofr/*http://fr.yahoo.com/set" target=_blank>Cliquez ici</a>.
--0-300756718-1147705872=:51392--


--===============1761655650==
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

--===============1761655650==--




From manet-bounces@ietf.org Mon May 15 12:11:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fffer-0001Fy-JE; Mon, 15 May 2006 12:10:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fffeq-0001E7-Bs
	for manet@ietf.org; Mon, 15 May 2006 12:10:56 -0400
Received: from rimp2.nist.gov ([129.6.16.227] helo=smtp.nist.gov)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fffep-0004Nt-3A
	for manet@ietf.org; Mon, 15 May 2006 12:10:56 -0400
Received: from postmark.nist.gov (pushme.nist.gov [129.6.16.92])
	by smtp.nist.gov (8.13.1/8.13.1) with ESMTP id k4FGAmlK001220
	for <manet@ietf.org>; Mon, 15 May 2006 12:10:49 -0400
Received: from cspa13.nist.gov (cspa13.ncsl.nist.gov [129.6.54.204])
	by postmark.nist.gov (8.13.6/8.13.6) with ESMTP id k4FGAHvn000494
	for <manet@ietf.org>; Mon, 15 May 2006 12:10:17 -0400 (EDT)
Message-Id: <5.1.0.14.2.20060515120249.0282bbf8@email.nist.gov>
X-Sender: tomkary@email.nist.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 15 May 2006 12:07:53 -0400
To: manet@ietf.org
From: "T. Karygiannis" <karygiannis@nist.gov>
In-Reply-To: <E1FffUW-0004pj-3C@megatron.ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-NIST-MailScanner: Found to be clean
X-NIST-MailScanner-From: karygiannis@nist.gov
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: [manet] SecureComm 2006 Call for Demos
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org



Any research group that is interested in demonstrating MANET security 
technologies at the SecureComm conference in Baltimore this year, please 
send me a short description of your demo. Detailed information on the 
SecureComm CFP can be found at http://www.securecomm.org/cfp.html. Tom 
Karygiannis karygiannis @ nist.gov


RESEARCH DEMOS: Informal proposals for research demos are solicited. 
Proposals will be reviewed and selection will be made based on the 
perceived value to the research community and interest level for the 
conference attendees. Proposals should not exceed 3 pages and should 
include: the focus area, technologies involved, specific equipment to be 
used, demo layout and space required. Please submit proposals to the 
Research Demos Chair(s) by June 1, 2006.


Areas of interest include, but ARE NOT limited to the following:
* Security & Privacy in Wired, Wireless, Mobile, Hybrid, Sensor, Ad Hoc 
networks
* Network Intrusion Detection and Prevention, DoS Countermeasures
* Firewalls, Routers, Filters and Malware detectors
* Public Key Infrastructures and Other Security Architectures
* Secure Web Communication
* Communication Privacy and Anonymity
* Secure/Private E-commerce
* Secure Routing, Naming/Addressing, Network Management
* Security & Privacy in Pervasive and Ubiquitous Computing, e.g., RFIDs


SecureComm 2006Second IEEE Communications Society/CreateNet International 
Conference on Security and Privacy in Communication Networks
Baltimore, MD, USA, Aug. 28 - Sep. 1, 2006


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



From manet-bounces@ietf.org Mon May 15 17:41:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ffknf-00075S-4D; Mon, 15 May 2006 17:40:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ffknd-00075I-WF
	for manet@ietf.org; Mon, 15 May 2006 17:40:22 -0400
Received: from nofilter.italway.it ([193.70.27.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ffkna-0006g0-80
	for manet@ietf.org; Mon, 15 May 2006 17:40:21 -0400
X-Spam-Status: No, hits=0.0 required=5.0
	tests=SARE_RECV_ADDR: 0.027
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by nofilter.italway.it
	for manet@ietf.org; Mon, 15 May 2006 23:40:02 +0200
X-Spam-Status: No, hits=0.0 required=6.0
	tests=SARE_RECV_ADDR: 0.027
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by mail2.italway.it for manet@ietf.org;
	Mon, 15 May 2006 23:39:58 +0200
Received: (qmail 3362 invoked from network); 15 May 2006 21:52:35 -0000
Received: from unknown (HELO ?192.168.2.6?) (nicscal@82.56.44.253)
	by server.italway.it with SMTP; 15 May 2006 21:52:35 -0000
Message-ID: <4468F52C.5070107@iit.cnr.it>
Date: Mon, 15 May 2006 23:39:56 +0200
From: Nicola Scalabrino <nicola.scalabrino@iit.cnr.it>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: tccc@cs.columbia.edu,  manet@ietf.org,  sigmobile-l@acm.uiuc.edu
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: 
Subject: [manet] Deadline Extension for the First International Workshop on
 "Wireless mesh: moving towards applications" (WiMeshNets 2006)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Apologies for possible duplicates
==================================================================

------------------------------------------------------------------
        PAPER SUBMISSION DEADLINE HAS BEEN EXTENDED TO
                24 MAY 2006, midnight CET
------------------------------------------------------------------

CALL FOR PAPERS

WiMeshNets 2006 (http://wimeshnets.org)

First International Workshop on "Wireless mesh: moving towards applications"
(Co-located with QShine 2006, Waterloo, Ontario, Canada) August 10, 2006

Recent advances in wireless mesh networks (WMNs) provide promising
opportunities in communication paradigms. WMNs do not depend on wired
communication infrastructure and their mesh connectivity provides
inherent built-in redundancy. This makes them also good candidates for
providing an alternative communication mechanism in the face of
disasters when normal communication infrastructure is destroyed. WMNs
build upon multi-hop forwarding of data packets from access nodes
towards gateways to the fixed network and thus share many properties of
Mobile Ad Hoc Networks. So far almost all existing research effort
related to Mobile Ad Hoc networks has been based mostly on the
assumptions that the nodes are highly mobile and are mainly battery
operated. Thus, most of the protocols and mechanisms try to conserve
energy and cope with frequent topology changes. In WMNs these
assumptions can be relaxed which enables the design of new protocols and
services for WMNs.
Supporting any application over wireless mesh networks is however a
challenging task due to the multi-hop forwarding of packets which also
limits the scalability of WMNs. Nevertheless, WMNs have promising
commercial potential as they are supposed to provide cheap wireless
network coverage and access. Towards this aim the traditional approaches
to routing and to service provisioning should be reconsidered taking
into account the intrinsic characteristics of WMNs and those of new and
emerging applications. This could pave the way to the assessment of this
technology which is expected to conquer new markets in the next few
years by taking advantage of the growth of heterogeneous networks.
Authors are invited to submit original full papers not currently under
review by other conferences on any aspect of “Wireless mesh: moving
towards applications”. Contributions describing theoretical research,
protocol design, experiments and measurements, commercial deployments,
business models, or position/vision statements are all encouraged.
Descriptions of work in progress, test trials, and future work plans are
highly appreciated. Topics of interest include, but are not limited to:

•    Architectures for Wireless Mesh Networks
•    Middleware support in Wireless Mesh Networks
•    Routing in Wireless Mesh Networks
•    Fairness Issues for Wireless Mesh Networks
•    Multicasting and Broadcasting issues in Wireless Mesh Networks
•    Security and Intrusion Detection for Wireless Mesh Networks
•    Handoff and mobility management in Wireless Mesh Networks
•    System prototypes and experimental evaluation of Wireless Mesh Networks
•    Scheduling and Queuing mechanisms to provide QoS in Wireless Mesh
Networks
•    Gaming applications over Wireless Mesh Networks
•    Service level agreement and mesh organization
•    Modeling and Performance Evaluation
•    Seamless internetworking with other type of networks (like sensor
networks)
•    Cross Layer Design and Interactions in Wireless Mesh Networks
•    Transport Layer Protocols over Wireless Mesh Networks
•    Deployment and configuration management
•    Voice and Video over Wireless Mesh Networks
•    Traffic Modeling
•    Mesh Networking Proposal Standards for IEEE 802(R) Wireless Lans
•    Authentication, Charging and Cooperation for Wireless Mesh Networks

Submitted papers will be reviewed by at least two independent experts in
the field. Proceedings of the workshop will be published in the same
manner as those of QShine. Authors of accepted papers will be required
to register in order for the paper to appear in the workshop proceedings.

Important dates
Full paper manuscript due:      May 24, 2006 Midnight CET
Acceptance Notification:        June 25, 2006
Camera ready manuscripts due:   July 9, 2006
Workshop date:                  August 10, 2006

Submission Instructions

Prospective authors are encouraged to submit a PDF version of the full
paper in English language. Papers are limited to 5 two-column pages, in
a font no smaller than 10-points, IEEE conference proceedings format.
Papers should be submitted to the respective symposium through COCUS
systems at http://cocus.create-net.it/cocus/welcome.do. Authors of
accepted papers are required to register at regular registration rates
in order for the paper to appear in the conference proceedings.

Organizing Committee

Workshop Chair:
Giovanni Iacovoni, CreateNet, Italy (giovanni.iacovoni@create-net.it)
Technical Program Committee Chair:
Andreas J. Kassler, Karlstad University, Sweden (kassler@ieee.org)
Publicity Chair:
Nicola Scalabrino, CreateNet, Italy (nicola.scalabrino@create-net.it)



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



From manet-bounces@ietf.org Tue May 16 09:30:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Ffzbu-0004bH-LO; Tue, 16 May 2006 09:29:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Ffzbs-0004aN-Lu
	for manet@ietf.org; Tue, 16 May 2006 09:29:12 -0400
Received: from mx-serv.inrialpes.fr ([194.199.18.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ffzbm-0006UL-VH
	for manet@ietf.org; Tue, 16 May 2006 09:29:12 -0400
Received: from curumo.inrialpes.fr (curumo.inrialpes.fr [194.199.18.105])
	by mx-serv.inrialpes.fr (8.13.6/8.13.0) with ESMTP id k4GDSl96019210
	for <manet@ietf.org>; Tue, 16 May 2006 15:28:51 +0200 (MEST)
Received: (from nobody@localhost)
	by curumo.inrialpes.fr (8.13.6/8.11.3) id k4GDSmNt027980
	for manet@ietf.org; Tue, 16 May 2006 15:28:48 +0200 (MEST)
X-Authentication-Warning: curumo.inrialpes.fr: nobody set sender to
	ccastel@inrialpes.fr using -f
Received: from 194.199.24.118 ( [194.199.24.118])
	as user ccastel@imap-serv.inrialpes.fr by listes-serv.inrialpes.fr with
	HTTP; Tue, 16 May 2006 15:28:48 +0200
Message-ID: <1147786128.4469d39006f9e@listes-serv.inrialpes.fr>
Date: Tue, 16 May 2006 15:28:48 +0200
From: Claude.Castelluccia@inrialpes.fr
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
User-Agent: Internet Messaging Program (IMP) 3.1
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0
	(mx-serv.inrialpes.fr [194.199.18.100]);
	Tue, 16 May 2006 15:28:51 +0200 (MEST)
X-mx-serv-inrialpes-fr-MailScanner-Information: Please contact
	postmaster@inrialpes.fr for more information
X-mx-serv-inrialpes-fr-MailScanner: Found to be clean
X-mx-serv-inrialpes-fr-MailScanner-SpamCheck: n'est pas un polluriel (inscrit
	sur la liste blanche), 
	SpamAssassin (score=0.55, requis 6, NO_REAL_NAME 0.55)
X-mx-serv-inrialpes-fr-MailScanner-From: ccastel@inrialpes.fr
X-Spam-Status: No
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx-serv.inrialpes.fr id
	k4GDSl96019210
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 225414c974e0d6437992164e91287a51
Subject: [manet] CFP: ESAS 2006 ...the submission deadline is coming...
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


Dear all,

Please find attached the call for papers for the third =20
Workshop on Security and Privacy in Ad hoc and Sensor Networks (ESAS2006)
to be held in  Hamburg, Germany from September 20-21, 2006.

This year ESAS will be held in conjunction with the European Symposium on=
=20
Research in Computer Security (ESORICS 2006- http://www.esorics06.tu-
harburg.de/).

As in previous years, the proceedings will be published by Springer in th=
e=20
Lecture Notes in Computer Science (LNCS) Series.

 The complete information is available on the ESAS website:=20
http://www.crysys.hu/ESAS2006/cfp.html

We apologize if you receive multiple copies of this message. Please=20
 feel free to distribute this Cfp...=20

cheers,=20

Claude Castelluccia.

--------------
ESAS 2006 (http://www.crysys.hu/ESAS2006)
Third European Workshop on Security and Privacy in Ad hoc and Sensor Netw=
orks
September 20-21, 2006, Hamburg, Germany
in conjunction with the European Symposium on Research in Computer Securi=
ty=20
(ESORICS 2006)

Call for Papers=20
-----------------
The vision of ubiquitous computing has generated a lot of interest in wir=
eless=20
ad hoc and sensor networks. However, besides their potential advantages, =
these=20
new generations of networks also raise some challenging problems with res=
pect=20
to security and privacy. The aim of this workshop is to bring together th=
e=20
network security, cryptography, and wireless networking communities in or=
der=20
to discuss these problems and to propose new solutions. The third ESAS=20
workshop seeks submissions that present original research on all aspects =
of=20
security and privacy in wireless ad hoc and sensor networks. Submission o=
f=20
papers based on work-in-progress is encouraged. Topics of interest includ=
e,=20
but are not limited to the following:=20

Privacy and anonymity=20
Prevention of traffic analysis=20
Location privacy=20
Secure positioning and localization=20
Secure MAC protocols=20
Secure topology control=20
Secure routing=20
Secure in-network processing=20
 Secure context aware computing=20
Attack resistant data aggregation=20
Cooperation and fairness=20
Key management=20
Trust establishment=20
Embedded security=20
Cryptography for resource constrained applications=20
Distributed intrusion detection=20
=20


Important Dates
---------------
Submission deadline:  May 29, 2006=20
Notification of acceptance:  July 31, 2006=20
Workshop:  September 20-21, 2006=20
Camera ready version:  October 9, 2006=20

General Chair
---------------
Dirk Westhoff, NEC Europe Network Lab, Germany=20

Program Chairs
--------------
Levente Butty=E1n, BME, CrySyS Lab, Hungary=20
Virgil Gligor, University of Maryland, USA=20

Publicity Chairs
------------------
Claude Castelluccia, INRIA, France=20
Susanne Wetzel, Stevens Institute of Technology, USA=20

Program Committee
------------------
Imad Aad, DoCoMo Lab Europe, Germany=20
N. Asokan, Nokia, Finland=20
Sonja Buchegger, University of California, Berkeley, USA=20
Srdjan Capkun, Technical University of Denmark=20
Claude Castelluccia, INRIA, France=20
Xuhua Ding, Singapore Management University, Singapore=20
Roberto Di Pietro, Universita "La Sapienza" - Roma, Italy=20
Hannes Hartenstein, University of Karlsruhe, Germany=20
Yih-Chun Hu, University of Illinois UC, USA=20
Markus Jakobsson, Indiana University, Bloomington, USA=20
Frank Kargl, University of Ulm, Germany=20
Yongdae Kim, University of Minnesota, Minneapolis, USA=20
Breno de Medeiros, Florida State University, USA=20
Ludovic Me, Supelec, France=20
Pietro Michiardi, Eurecom, France=20
Gabriel Montenegro, Microsoft, USA=20
Cristina Nita-Rotaru, Purdue University, USA=20
Guevara Noubir, Northeastern University, USA=20
Kaisa Nyberg, Helsinki University of Technology, Finland=20
Panagiotis Papadimitratos, EPFL, Switzerland=20
Adrian Perrig, Carnegie Mellon University, USA=20
Radha Poovendran, University of Washington, USA=20
Frank Stajano, Cambridge University, UK=20
Andre Weimerskirch, University of Bochum, Germany=20
Dirk Westhoff, NEC Europe Network Lab, Germany=20
Susanne Wetzel, Stevens Institute of Technology, USA=20
Jeong Yi, Samsung Advanced Institute of Technology, Korea=20


Instructions for Authors
-------------------------
Authors are invited to submit an extended abstract of their original work=
.=20
Maximum length for submissions is 8 pages. The preferred submission forma=
t is=20
PDF or PostScript. Submissions must not substantially duplicate work that=
 any=20
of the authors have published elsewhere or have submitted in parallel. Al=
l=20
submissions will be refereed. Accepted papers should be presented at the=20
workshop, in which case they will appear in the post-workshop proceedings=
. The=20
final camera ready version should be sent in after the workshop and it mu=
st=20
not exceed 15 pages. Further information on how to submit papers will be=20
available here.=20

Workshop Proceedings
---------------------
As in previous years, the proceedings will be published by Springer after=
 the=20
workshop in the Lecture Notes in Computer Science (LNCS) Series=20
(www.springer.de/comp/lncs/). Note that in order to be included in the=20
proceedings, an accepted paper must be presented at the workshop. In addi=
tion,=20
when preparing the final manuscript, the authors should take into account=
 the=20
reviewers' comments and the comments received at the workshop.=20
=20





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



From manet-bounces@ietf.org Wed May 17 08:04:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FgKkp-0005Cw-CQ; Wed, 17 May 2006 08:03:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FgKko-0005Cr-6U
	for manet@ietf.org; Wed, 17 May 2006 08:03:50 -0400
Received: from ug-out-1314.google.com ([66.249.92.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FgKkk-0004fS-S5
	for manet@ietf.org; Wed, 17 May 2006 08:03:50 -0400
Received: by ug-out-1314.google.com with SMTP id m3so198508uge
	for <manet@ietf.org>; Wed, 17 May 2006 05:03:43 -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=UGVzWuqui+YO5owKfrXl2FYMIJc1Q6H/ugt4jSqEZFB6IscBbG6KZ6h8A1Z3QNrr/FRSDuf24cZZDy93RQqyelch9R/VXbt8a06E9F7eUKjJq6HXK7x85Jx+TJK4X7zKGhdFb3jdIIrXR8ajO8fJrG1mX4YmIxrCmtfELjQH1W4=
Received: by 10.78.17.1 with SMTP id 1mr161345huq;
	Wed, 17 May 2006 05:03:43 -0700 (PDT)
Received: by 10.78.53.20 with HTTP; Wed, 17 May 2006 05:03:43 -0700 (PDT)
Message-ID: <146563590605170503i6ecdd47h44f83515dc740ad6@mail.gmail.com>
Date: Wed, 17 May 2006 20:03:43 +0800
From: "chen jiming" <jmchen.zju@gmail.com>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Subject: [manet] OPNET project for sensor actuator networks
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1474648479=="
Errors-To: manet-bounces@ietf.org

--===============1474648479==
Content-Type: multipart/alternative; 
	boundary="----=_Part_1530_2181049.1147867423634"

------=_Part_1530_2181049.1147867423634
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Dear all:

I would like to get the source of
the OPENT project for sensor actuator networks
see the link http://www.imtek.de/emp/content/OpnetProjectMackensen.htm

maybe it can be downloaded from OPNET support
with a valid account

thanks a lot

jiming Chen

------=_Part_1530_2181049.1147867423634
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>Dear all:</div>
<div>&nbsp;</div>
<div>I would like to get the source of</div>
<div>the OPENT&nbsp;project&nbsp;for sensor actuator networks </div>
<div>see the link <a href=3D"http://www.imtek.de/emp/content/OpnetProjectMa=
ckensen.htm">http://www.imtek.de/emp/content/OpnetProjectMackensen.htm</a><=
/div>
<div>&nbsp;</div>
<div>maybe it can be downloaded from OPNET support</div>
<div>with a valid account</div>
<div>&nbsp;</div>
<div>thanks a lot </div>
<div>&nbsp;</div>
<div>jiming Chen</div>

------=_Part_1530_2181049.1147867423634--


--===============1474648479==
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

--===============1474648479==--




From manet-bounces@ietf.org Thu May 18 04:17:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fgdgg-0005ma-3i; Thu, 18 May 2006 04:16:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgdgd-0005mU-UT
	for manet@ietf.org; Thu, 18 May 2006 04:16: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 1Fgdgd-0008KG-SG
	for manet@ietf.org; Thu, 18 May 2006 04:16:47 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FgdeL-0008Fe-Qp
	for manet@ietf.org; Thu, 18 May 2006 04:14:28 -0400
Received: from ex1.ad.dcs.gla.ac.uk ([130.209.249.157]:16358)
	by mr1.dcs.gla.ac.uk with esmtp (Exim 4.42)
	id 1FgdeF-0006zr-OU; Thu, 18 May 2006 09:14:19 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 18 May 2006 09:13:59 +0100
Message-ID: <BED9D15F73EDDE48BF480604236A4560116FD2@ex1.ad.dcs.gla.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
Thread-Index: AcZlxbx8iOSvNfkUTRyLkeSW6R422QAACIzMAAAgo3MAAF/kTgAAG4FQAADVrOAFIdelpQ==
References: <BED9D15F73EDDE48BF480604236A4560116E59@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5A@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5B@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5C@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5D@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5F@ex1.ad.dcs.gla.ac.uk>
From: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>
To: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>, <manet@ietf.org>,
	<itc@comsoc.org>, <multicomm@comsoc.org>
X-Spam-Score: -1.2 (-)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6
Cc: 
Subject: [manet] CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1466680967=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1466680967==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67A53.0FEAFB07"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67A53.0FEAFB07
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

[Please accept our apologies if you receive multiple copies of this CFP]
-------------------------------------------------------------------------=
-----------------------------------------
=20
CALL FOR PAPERS
=20
ACM International Workshop on Performance Monitoring, Measurement,
and Evaluation of Heterogeneous Wireless and Wired Networks (PM2HW2N =
2006)
=20
http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html =
<http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html>=20
<http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html>=20
=20
To be held in conjunction with  ACM/IEEE MSWiM 2006
http://www.cs.unibo.it/mswim2006/ <http://www.cs.unibo.it/mswim2006/>=20
=20
October 2-6, 2006
Torremolinos, (Malaga), Spain
=20
=20
Scope:
Wireless networks, including ad hoc, sensor, along with ubiquitous, have =
witnessed=20
over the past few years their fastest growth period and have become =
increasingly complex.=20
Nonetheless, their perfFrom manet-bounces@ietf.org Thu May 18 04:17:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fgdgg-0005ma-3i; Thu, 18 May 2006 04:16:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgdgd-0005mU-UT
	for manet@ietf.org; Thu, 18 May 2006 04:16: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 1Fgdgd-0008KG-SG
	for manet@ietf.org; Thu, 18 May 2006 04:16:47 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FgdeL-0008Fe-Qp
	for manet@ietf.org; Thu, 18 May 2006 04:14:28 -0400
Received: from ex1.ad.dcs.gla.ac.uk ([130.209.249.157]:16358)
	by mr1.dcs.gla.ac.uk with esmtp (Exim 4.42)
	id 1FgdeF-0006zr-OU; Thu, 18 May 2006 09:14:19 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 18 May 2006 09:13:59 +0100
Message-ID: <BED9D15F73EDDE48BF480604236A4560116FD2@ex1.ad.dcs.gla.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
Thread-Index: AcZlxbx8iOSvNfkUTRyLkeSW6R422QAACIzMAAAgo3MAAF/kTgAAG4FQAADVrOAFIdelpQ==
References: <BED9D15F73EDDE48BF480604236A4560116E59@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5A@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5B@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5C@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5D@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5F@ex1.ad.dcs.gla.ac.uk>
From: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>
To: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>, <manet@ietf.org>,
	<itc@comsoc.org>, <multicomm@comsoc.org>
X-Spam-Score: -1.2 (-)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6
Cc: 
Subject: [manet] CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1466680967=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1466680967==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67A53.0FEAFB07"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67A53.0FEAFB07
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

[Please accept our apologies if you receive multiple copies of this CFP]
-------------------------------------------------------------------------=
-----------------------------------------
=20
CALL FOR PAPERS
=20
ACM International Workshop on Performance Monitoring, Measurement,
and Evaluation of Heterogeneous Wireless and Wired Networks (PM2HW2N =
2006)
=20
http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html =
<http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html>=20
<http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html>=20
=20
To be held in conjunction with  ACM/IEEE MSWiM 2006
http://www.cs.unibo.it/mswim2006/ <http://www.cs.unibo.it/mswim2006/>=20
=20
October 2-6, 2006
Torremolinos, (Malaga), Spain
=20
=20
Scope:
Wireless networks, including ad hoc, sensor, along with ubiquitous, have =
witnessed=20
over the past few years their fastest growth period and have become =
increasingly complex.=20
Nonetheless, their performance evaluation and analysis have been =
conducted mostly through=20
software simulations. Very recently, some research efforts have been =
directed towards measuring=20
real-world commercial and experimental networks; constructing models =
based on real-world data=20
and using prototypes to more realistically and comprehensively evaluate =
the suggested solutions=20
and more specifically validate the assumptions and the conclusions =
reached via the simulation approach.
=20
The aim of this workshop is to bring together scientists, engineers, and =
practitioners to share and exchange=20
their experiences, discuss challenges, and report state-of-the-art and =
in-progress research on all aspects=20
of performance measurements, monitoring, and evaluation of heterogeneous =
wired and wireless mobile networks,=20
including, wireless ad hoc, sensor, and ubiquitous networks. Topics of =
interest include, but are not limited to:
=20
- Performance measurement, monitoring, and evaluation tools for =
heterogeneous wireless and wired networks
- Performance tools for ad hoc, sensor, and ubiquitous networks
- Tracing and trace analysis
- Discrete and continuous models
- Measurement-based performance modelling
- Measurement architectures and systems
- QoS monitoring and sampling
- Measurement-based optimisation of for heterogeneous wireless and wired =
networks
- Novel measurement tools of wireless networks
- Performance measurements of ad hoc, sensor, and ubiquitous networks
- Performance analysis and evaluation of mobile services
- Software tools for wireless network performance and evaluation
- Automatic performance analysis=20
- Performance of wireless and sensor devices
- Mobility modeling and management
- Prototype implementation of wireless/mobile networks and systems
- Techniques for prototyping wireless networks
- Validation through measurement and prototyping
- Probabilistic models for ad hoc, sensor, and ubiquitous networks
- Improvement in network performance through prototyping
- Performance tools for ad hoc, sensor and ubiquitous networks
- Performance and security issues in ad hoc, sensor, and ubiquitous =
networks
- Performance and power management control
- Case studies demonstrating the role of performance monitoring, =
measurement, and=20
evaluation in the design of ad hoc, sensor, and ubiquitous networks
-Applications of performance monitoring, measurement, and evaluation as =
a feedback to improve network QoS
=20

Workshop Co-Chairs:
M. Ould-Khaoua
University of Glasgow
UK=20
=20
B. Caminero
University of Castilla-La Mancha
Albacete (Spain)
=20
=20
Program Committee (in progress):
K. Al-Begain, Univ. of Glamorgan (UK)
A. Al-Dubai, Napier Univ. (UK)
N. Abu-Ghazaleh,  SUNY,Binghamton (USA)
I. Awan, Univ. of Bradford (UK)
A. Bermudez, University of Castilla-La Mancha (Spain)
L. Bononi, University of Bologna (Italy)
A. Boukerche, Univ. of Ottawa (Canada)
C.-C. Shen, Univeristy of Delaware (USA)
J.C. Cano, Technical University of Valencia (Spain)
C. Carrion, University of Castilla-La Mancha (Spain)
M. Colajanni, Univ. of Modena (Italy)
P. Cuenca, University of Castilla-La Mancha (Spain)
F.M. Delicado, University of Castilla-La Mancha (Spain)
E. Fleury, INSA de Lyon (France)
V. Gianuzzi, Univ. of Genova (Italy)
E. Karatza, Aristotle University of Thessaloniki (Greece)
A. Ksentini, University of Cergy-Pontoise (France)
P. Manzoni, Technical University of Valencia (Spain)
G. Min, Univ. of Bradford (UK)
M. Naimi, University of Cergy-Pontoise (France)
S. Nikoletseas, Computer Technology Institute (Greece)=20
M. S. M. Annoni Notare, Barddal Univ. (Brazil)
S. Olariu, Old Dominion Univ. (USA)
T. Olivares, University of Castilla-La Mancha (Spain)
L. Orozco-Barbosa, University of Castilla-La Mancha (Spain)
A. Passarella, Univ. Of Cambridge (UK)
Y. Pan, Georgia State Univ. (USA)
M. Perez-Malumbres, Miguel Hernandez University (Spain)
F. Quiles, University of Castilla-La Mancha (Spain)
P. Ruiz, University of Murcia (Spain)
J.L. Sanchez, University of Castilla-La Mancha (Spain)
M. S. Squillante, IBM T.J. Watson Research Center (Uormance evaluation and analysis have been =
conducted mostly through=20
software simulations. Very recently, some research efforts have been =
directed towards measuring=20
real-world commercial and experimental networks; constructing models =
based on real-world data=20
and using prototypes to more realistically and comprehensively evaluate =
the suggested solutions=20
and more specifically validate the assumptions and the conclusions =
reached via the simulation approach.
=20
The aim of this workshop is to bring together scientists, engineers, and =
practitioners to share and exchange=20
their experiences, discuss challenges, and report state-of-the-art and =
in-progress research on all aspects=20
of performance measurements, monitoring, and evaluation of heterogeneous =
wired and wireless mobile networks,=20
including, wireless ad hoc, sensor, and ubiquitous networks. Topics of =
interest include, but are not limited to:
=20
- Performance measurement, monitoring, and evaluation tools for =
heterogeneous wireless and wired networks
- Performance tools for ad hoc, sensor, and ubiquitous networks
- Tracing and trace analysis
- Discrete and continuous models
- Measurement-based performance modelling
- Measurement architectures and systems
- QoS monitoring and sampling
- Measurement-based optimisation of for heterogeneous wireless and wired =
networks
- Novel measurement tools of wireless networks
- Performance measurements of ad hoc, sensor, and ubiquitous networks
- Performance analysis and evaluation of mobile services
- Software tools for wireless network performance and evaluation
- Automatic performance analysis=20
- Performance of wireless and sensor devices
- Mobility modeling and management
- Prototype implementation of wireless/mobile networks and systems
- Techniques for prototyping wireless networks
- Validation through measurement and prototyping
- Probabilistic models for ad hoc, sensor, and ubiquitous networks
- Improvement in network performance through prototyping
- Performance tools for ad hoc, sensor and ubiquitous networks
- Performance and security issues in ad hoc, sensor, and ubiquitous =
networks
- Performance and power management control
- Case studies demonstrating the role of performance monitoring, =
measurement, and=20
evaluation in the design of ad hoc, sensor, and ubiquitous networks
-Applications of performance monitoring, measurement, and evaluation as =
a feedback to improve network QoS
=20

Workshop Co-Chairs:
M. Ould-Khaoua
University of Glasgow
UK=20
=20
B. Caminero
University of Castilla-La Mancha
Albacete (Spain)
=20
=20
Program Committee (in progress):
K. Al-Begain, Univ. of Glamorgan (UK)
A. Al-Dubai, Napier Univ. (UK)
N. Abu-Ghazaleh,  SUNY,Binghamton (USA)
I. Awan, Univ. of Bradford (UK)
A. Bermudez, University of Castilla-La Mancha (Spain)
L. Bononi, University of Bologna (Italy)
A. Boukerche, Univ. of Ottawa (Canada)
C.-C. Shen, Univeristy of Delaware (USA)
J.C. Cano, Technical University of Valencia (Spain)
C. Carrion, University of Castilla-La Mancha (Spain)
M. Colajanni, Univ. of Modena (Italy)
P. Cuenca, University of Castilla-La Mancha (Spain)
F.M. Delicado, University of Castilla-La Mancha (Spain)
E. Fleury, INSA de Lyon (France)
V. Gianuzzi, Univ. of Genova (Italy)
E. Karatza, Aristotle University of Thessaloniki (Greece)
A. Ksentini, University of Cergy-Pontoise (France)
P. Manzoni, Technical University of Valencia (Spain)
G. Min, Univ. of Bradford (UK)
M. Naimi, University of Cergy-Pontoise (France)
S. Nikoletseas, Computer Technology Institute (Greece)=20
M. S. M. Annoni Notare, Barddal Univ. (Brazil)
S. Olariu, Old Dominion Univ. (USA)
T. Olivares, University of Castilla-La Mancha (Spain)
L. Orozco-Barbosa, University of Castilla-La Mancha (Spain)
A. Passarella, Univ. Of Cambridge (UK)
Y. Pan, Georgia State Univ. (USA)
M. Perez-Malumbres, Miguel Hernandez University (Spain)
F. Quiles, University of Castilla-La Mancha (Spain)
P. Ruiz, University of Murcia (Spain)
J.L. Sanchez, University of Castilla-La Mancha (Spain)
M. S. Squillante, IBM T.J. Watson Research Center (USA)=20
A. Shahrabi, Glasgow Caledonian University (UK)
T. Miklos, Technical University of Budapest (Hungary)
S. Yoshida, Kyoto University (Japan)
J. Wu, Florida Atlantic University (USA)
A. Zomaya, Univ. of Sydney (Australia)
=20

Publicity Chair
M. S.-M. Annoni Notare
Barddal University, Florianopolis, SC=20
Brazil
  =20
=20
Paper Submission:
Authors are invited to submit manuscripts reporting original unpublished =
research and recent developments=20
in the topics related to the workshop. The length of the papers should =
not exceed 10 single-spaced pages,=20
formatted using the ACM style (LaTex2e  and MS Word templates can be =
found at <http://www.acm.org/sigs/pubs/proceed/template.html =
<http://www.acm.org/sigs/pubs/proceed/template.html> >).

Papers should be submitted electronically in PDF format (or postscript) =
by sending it as an e-mail attachment to=20
mohamed@dcs.gla.ac.uk <mailto:mohamed@dcs.gla.ac.uk>  or =
blanca@dsi.uclm.es <mailto:blanca@dsi.uclm.es> . All papers will be peer =
reviewed and the comments will=20
be provided to the authors.
=20
Accepted papers will appear in the workshop proceedings and a special =
issue will be planned in a scholarly=20
journal to include selected high-quality papers from the workshop.
=20
Important Dates:
Submission Deadline: 10 June 2006=20
Author Notification: 10 July 2006


------_=_NextPart_001_01C67A53.0FEAFB07
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML =
DIR=3Dltr><HEAD></HEAD><BODY>=0A=
<DIV id=3DidOWAReplyText55528 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2><FONT =0A=
face=3D"Times New Roman">[Please accept our apologies if you receive =
multiple =0A=
copies of this =0A=
CFP]<BR>-----------------------------------------------------------------=
-------------------------------------------------</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>CALL FOR PAPERS</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>ACM International Workshop =
on =0A=
Performance Monitoring, Measurement,<BR>and Evaluation of Heterogeneous =
Wireless =0A=
and Wired Networks (PM2HW2N 2006)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html</FONT></A></D=
IV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html"><FONT =0A=
face=3D"Times New Roman"></FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">To be held in conjunction with&nbsp; =
ACM/IEEE =0A=
MSWiM 2006<BR></FONT><A href=3D"http://www.cs.unibo.it/mswim2006/"><FONT =0A=
face=3D"Times New =
Roman">http://www.cs.unibo.it/mswim2006/</FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;<BR>October 2-6, 2006</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Torremolinos, (Malaga), =0A=
Spain<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Scope:<BR>Wireless networks, =
including ad hoc, =0A=
sensor, along with ubiquitous, have witnessed <BR>over the past few =
years their =0A=
fastest growth period and have become increasingly complex. =
<BR>Nonetheless, =0A=
their performance evaluation and analysis have been conducted mostly =
through =0A=
<BR>software simulations. Very recently, some research efforts have been =0A=
directed towards measuring </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">real-world commercial and =
experimental =0A=
networks; constructing models based on real-world data </FONT></DSA)=20
A. Shahrabi, Glasgow Caledonian University (UK)
T. Miklos, Technical University of Budapest (Hungary)
S. Yoshida, Kyoto University (Japan)
J. Wu, Florida Atlantic University (USA)
A. Zomaya, Univ. of Sydney (Australia)
=20

Publicity Chair
M. S.-M. Annoni Notare
Barddal University, Florianopolis, SC=20
Brazil
  =20
=20
Paper Submission:
Authors are invited to submit manuscripts reporting original unpublished =
research and recent developments=20
in the topics related to the workshop. The length of the papers should =
not exceed 10 single-spaced pages,=20
formatted using the ACM style (LaTex2e  and MS Word templates can be =
found at <http://www.acm.org/sigs/pubs/proceed/template.html =
<http://www.acm.org/sigs/pubs/proceed/template.html> >).

Papers should be submitted electronically in PDF format (or postscript) =
by sending it as an e-mail attachment to=20
mohamed@dcs.gla.ac.uk <mailto:mohamed@dcs.gla.ac.uk>  or =
blanca@dsi.uclm.es <mailto:blanca@dsi.uclm.es> . All papers will be peer =
reviewed and the comments will=20
be provided to the authors.
=20
Accepted papers will appear in the workshop proceedings and a special =
issue will be planned in a scholarly=20
journal to include selected high-quality papers from the workshop.
=20
Important Dates:
Submission Deadline: 10 June 2006=20
Author Notification: 10 July 2006


------_=_NextPart_001_01C67A53.0FEAFB07
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML =
DIR=3Dltr><HEAD></HEAD><BODY>=0A=
<DIV id=3DidOWAReplyText55528 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2><FONT =0A=
face=3D"Times New Roman">[Please accept our apologies if you receive =
multiple =0A=
copies of this =0A=
CFP]<BR>-----------------------------------------------------------------=
-------------------------------------------------</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>CALL FOR PAPERS</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>ACM International Workshop =
on =0A=
Performance Monitoring, Measurement,<BR>and Evaluation of Heterogeneous =
Wireless =0A=
and Wired Networks (PM2HW2N 2006)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html</FONT></A></D=
IV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html"><FONT =0A=
face=3D"Times New Roman"></FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">To be held in conjunction with&nbsp; =
ACM/IEEE =0A=
MSWiM 2006<BR></FONT><A href=3D"http://www.cs.unibo.it/mswim2006/"><FONT =0A=
face=3D"Times New =
Roman">http://www.cs.unibo.it/mswim2006/</FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;<BR>October 2-6, 2006</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Torremolinos, (Malaga), =0A=
Spain<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Scope:<BR>Wireless networks, =
including ad hoc, =0A=
sensor, along with ubiquitous, have witnessed <BR>over the past few =
years their =0A=
fastest growth period and have become increasingly complex. =
<BR>Nonetheless, =0A=
their performance evaluation and analysis have been conducted mostly =
through =0A=
<BR>software simulations. Very recently, some research efforts have been =0A=
directed towards measuring </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">real-world commercial and =
experimental =0A=
networks; constructing models based on real-world data </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and using prototypes to more =
realistically and =0A=
comprehensively evaluate the suggested solutions </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and more specifically validate the =
assumptions =0A=
and the conclusions reached via the simulation =
approach.<BR>&nbsp;<BR>The aim of =0A=
this workshop is to bring together scientists, engineers, and =
practitioners to =0A=
share and exchange </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">their experiences, discuss =
challenges, and =0A=
report state-of-the-art and in-progress research on all aspects =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">of performance measurements, =
monitoring, and =0A=
evaluation of heterogeneous wired and wireless mobile networks, =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">including, wireless ad hoc, sensor, =
and =0A=
ubiquitous networks. Topics of interest&nbsp;include, but are not =
limited =0A=
to:<BR>&nbsp;<BR>- Performance measurement, monitoring, and evaluation =
tools for =0A=
heterogeneous wireless and wired networks<BR>- Performance tools for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Tracing and trace analysis<BR>- =
Discrete =0A=
and continuous models<BR>- Measurement-based performance modelling<BR>- =0A=
Measurement architectures and systems<BR>- QoS monitoring and =
sampling<BR>- =0A=
Measurement-based optimisation of for heterogeneous wireless and wired =0A=
networks<BR>- Novel measurement tools of wireless networks<BR>- =
Performance =0A=
measurements of ad hoc, sensor, and ubiquitous networks<BR>- Performance =0A=
analysis and evaluation of mobile services<BR>- Software tools for =
wireless =0A=
network performance and evaluation<BR>- Automatic performance analysis =
<BR>- =0A=
Performance of wireless and sensor devices<BR>- Mobility modeling and =0A=
management<BR>- Prototype implementation of wireless/mobile networks and =0A=
systems<BR>- Techniques for prototyping wireless networks<BR>- =
Validation =0A=
through measurement and prototyping<BR>- Probabilistic models for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Improvement in network performance =
through =0A=
prototyping<BR>- Performance tools for ad hoc, sensor and ubiquitous =0A=
networks<BR>- Performance and security issues in ad hoc, sensor, and =
ubiquitous =0A=
networks<BR>- Performance and power management control<BR>- Case studies =0A=
demonstrating the role of performance monitoring, measurement, and =0A=
<BR>evaluation in the design of ad hoc, sensor, and ubiquitous =0A=
networks<BR>-Applications of performance monitoring, measurement, and =
evaluation =0A=
as a feedback to improve network QoS<BR>&nbsp;<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Workshop Co-Chairs:<BR>M. =0A=
Ould-Khaoua<BR>University of Glasgow<BR>UK&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">B. Caminero<BR>University of =
Castilla-La =0A=
Mancha<BR>Albacete (Spain)<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Program Committee (in =
progress):<BR>K. =0A=
Al-Begain, Univ. of Glamorgan (UK)<BR>A. Al-Dubai, Napier Univ. =
(UK)<BR>N. =0A=
Abu-Ghazaleh,&nbsp; SUNY,Binghamton (USA)<BR>I. Awan, Univ. of Bradford =0A=
(UK)<BR>A. Bermudez, University of Castilla-La Mancha (Spain)<BR>L. =
Bononi, =0A=
University of Bologna (Italy)<BR>A. Boukerche, Univ. of Ottawa =
(Canada)<BR>C.-C. =0A=
Shen, Univeristy of Delaware (USA)<BR>J.C. Cano, Technical University of =0A=
Valencia (Spain)<BR>C. Carrion, University of Castilla-La Mancha =
(Spain)<BR>M. =0A=
Colajanni, Univ. of Modena (Italy)<BR>P. Cuenca, University of =
Castilla-La =0A=
Mancha (Spain)<BR>F.M. Delicado, University of Castilla-La Mancha =
(Spain)<BR>E. =0A=
Fleury, INSA de Lyon (France)<BR>V. Gianuzzi, Univ. of Genova =
(Italy)<BR>E. =0A=
Karatza, Aristotle University of Thessaloniki (Greece)<BR>A. Ksentini, =0A=
University of Cergy-Pontoise (France)<BR>P. Manzoni, Technical =
UniverIV>=0A=
<DIV><FONT face=3D"Times New Roman">and using prototypes to more =
realistically and =0A=
comprehensively evaluate the suggested solutions </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and more specifically validate the =
assumptions =0A=
and the conclusions reached via the simulation =
approach.<BR>&nbsp;<BR>The aim of =0A=
this workshop is to bring together scientists, engineers, and =
practitioners to =0A=
share and exchange </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">their experiences, discuss =
challenges, and =0A=
report state-of-the-art and in-progress research on all aspects =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">of performance measurements, =
monitoring, and =0A=
evaluation of heterogeneous wired and wireless mobile networks, =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">including, wireless ad hoc, sensor, =
and =0A=
ubiquitous networks. Topics of interest&nbsp;include, but are not =
limited =0A=
to:<BR>&nbsp;<BR>- Performance measurement, monitoring, and evaluation =
tools for =0A=
heterogeneous wireless and wired networks<BR>- Performance tools for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Tracing and trace analysis<BR>- =
Discrete =0A=
and continuous models<BR>- Measurement-based performance modelling<BR>- =0A=
Measurement architectures and systems<BR>- QoS monitoring and =
sampling<BR>- =0A=
Measurement-based optimisation of for heterogeneous wireless and wired =0A=
networks<BR>- Novel measurement tools of wireless networks<BR>- =
Performance =0A=
measurements of ad hoc, sensor, and ubiquitous networks<BR>- Performance =0A=
analysis and evaluation of mobile services<BR>- Software tools for =
wireless =0A=
network performance and evaluation<BR>- Automatic performance analysis =
<BR>- =0A=
Performance of wireless and sensor devices<BR>- Mobility modeling and =0A=
management<BR>- Prototype implementation of wireless/mobile networks and =0A=
systems<BR>- Techniques for prototyping wireless networks<BR>- =
Validation =0A=
through measurement and prototyping<BR>- Probabilistic models for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Improvement in network performance =
through =0A=
prototyping<BR>- Performance tools for ad hoc, sensor and ubiquitous =0A=
networks<BR>- Performance and security issues in ad hoc, sensor, and =
ubiquitous =0A=
networks<BR>- Performance and power management control<BR>- Case studies =0A=
demonstrating the role of performance monitoring, measurement, and =0A=
<BR>evaluation in the design of ad hoc, sensor, and ubiquitous =0A=
networks<BR>-Applications of performance monitoring, measurement, and =
evaluation =0A=
as a feedback to improve network QoS<BR>&nbsp;<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Workshop Co-Chairs:<BR>M. =0A=
Ould-Khaoua<BR>University of Glasgow<BR>UK&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">B. Caminero<BR>University of =
Castilla-La =0A=
Mancha<BR>Albacete (Spain)<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Program Committee (in =
progress):<BR>K. =0A=
Al-Begain, Univ. of Glamorgan (UK)<BR>A. Al-Dubai, Napier Univ. =
(UK)<BR>N. =0A=
Abu-Ghazaleh,&nbsp; SUNY,Binghamton (USA)<BR>I. Awan, Univ. of Bradford =0A=
(UK)<BR>A. Bermudez, University of Castilla-La Mancha (Spain)<BR>L. =
Bononi, =0A=
University of Bologna (Italy)<BR>A. Boukerche, Univ. of Ottawa =
(Canada)<BR>C.-C. =0A=
Shen, Univeristy of Delaware (USA)<BR>J.C. Cano, Technical University of =0A=
Valencia (Spain)<BR>C. Carrion, University of Castilla-La Mancha =
(Spain)<BR>M. =0A=
Colajanni, Univ. of Modena (Italy)<BR>P. Cuenca, University of =
Castilla-La =0A=
Mancha (Spain)<BR>F.M. Delicado, University of Castilla-La Mancha =
(Spain)<BR>E. =0A=
Fleury, INSA de Lyon (France)<BR>V. Gianuzzi, Univ. of Genova =
(Italy)<BR>E. =0A=
Karatza, Aristotle University of Thessaloniki (Greece)<BR>A. Ksentini, =0A=
University of Cergy-Pontoise (France)<BR>P. Manzoni, Technical =
University of =0A=
Valencia (Spain)<BR>G. Min, Univ. of Bradford (UK)<BR>M. Naimi, =
University of =0A=
Cergy-Pontoise (France)<BR>S. Nikoletseas, Computer Technology Institute =0A=
(Greece) <BR>M. S. M. Annoni Notare, Barddal Univ. (Brazil)<BR>S. =
Olariu, Old =0A=
Dominion Univ. (USA)<BR>T. Olivares, University of Castilla-La Mancha =0A=
(Spain)<BR>L. Orozco-Barbosa, University of Castilla-La Mancha =
(Spain)<BR>A. =0A=
Passarella, Univ. Of Cambridge (UK)<BR>Y. Pan, Georgia State Univ. =
(USA)<BR>M. =0A=
Perez-Malumbres, Miguel Hernandez University (Spain)<BR>F. Quiles, =
University of =0A=
Castilla-La Mancha (Spain)<BR>P. Ruiz, University of Murcia =
(Spain)<BR>J.L. =0A=
Sanchez, University of Castilla-La Mancha (Spain)<BR>M. S. Squillante, =
IBM T.J. =0A=
Watson Research Center (USA) <BR>A. Shahrabi, Glasgow Caledonian =
University =0A=
(UK)<BR>T. Miklos, Technical University of Budapest (Hungary)<BR>S. =
Yoshida, =0A=
Kyoto University (Japan)<BR>J. Wu, Florida Atlantic University =
(USA)<BR>A. =0A=
Zomaya, Univ. of Sydney (Australia)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><BR><FONT face=3D"Times New Roman">Publicity Chair<BR>M. S.-M. =
Annoni =0A=
Notare<BR>Barddal University, Florianopolis, SC =
<BR>Brazil<BR>&nbsp;&nbsp; =0A=
<BR>&nbsp;<BR>Paper Submission:<BR>Authors are invited to submit =
manuscripts =0A=
reporting original unpublished research and recent developments <BR>in =
the =0A=
topics related to the workshop. The length of the papers should not =
exceed 10 =0A=
single-spaced pages, <BR>formatted using the ACM style (LaTex2e&nbsp; =
and MS =0A=
Word templates can be found at &lt;</FONT><A =0A=
href=3D"http://www.acm.org/sigs/pubs/proceed/template.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.acm.org/sigs/pubs/proceed/template.html</FONT></A><FONT=
 =0A=
face=3D"Times New Roman">&gt;).<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Papers should be submitted =
electronically in =0A=
PDF format (or postscript) by sending it as an e-mail attachment to =0A=
<BR></FONT><A href=3D"mailto:mohamed@dcs.gla.ac.uk"><FONT =0A=
face=3D"Times New Roman">mohamed@dcs.gla.ac.uk</FONT></A><FONT =0A=
face=3D"Times New Roman"> or </FONT><A =
href=3D"mailto:blanca@dsi.uclm.es"><FONT =0A=
face=3D"Times New Roman">blanca@dsi.uclm.es</FONT></A><FONT =0A=
face=3D"Times New Roman">. All papers will be peer reviewed and the =
comments will =0A=
<BR>be provided to the authors.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Accepted papers will appear in the =
workshop =0A=
proceedings and a special issue will be planned in a scholarly =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">journal to include selected =
high-quality =0A=
papers from the workshop.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Important Dates:<BR>Submission =
Deadline: 10 =0A=
June 2006 <BR>Author Notification: 10 July =0A=
2006</FONT><BR></FONT></DIV></DIV></DIV></DIV></DIV></DIV></DIV></BODY></=
HTML>
------_=_NextPart_001_01C67A53.0FEAFB07--


--===============1466680967==
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

--===============1466680967==--


From manet-bounces@ietf.org Thu May 18 04:17:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fgdgv-0005qW-6M; Thu, 18 May 2006 04:17:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgdgt-0005pB-1i
	for manet@ietf.org; Thu, 18 May 2006 04:17: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 1Fgdgs-0008KM-VA
	for manet@ietf.org; Thu, 18 May 2006 04:17:03 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	bsity of =0A=
Valencia (Spain)<BR>G. Min, Univ. of Bradford (UK)<BR>M. Naimi, =
University of =0A=
Cergy-Pontoise (France)<BR>S. Nikoletseas, Computer Technology Institute =0A=
(Greece) <BR>M. S. M. Annoni Notare, Barddal Univ. (Brazil)<BR>S. =
Olariu, Old =0A=
Dominion Univ. (USA)<BR>T. Olivares, University of Castilla-La Mancha =0A=
(Spain)<BR>L. Orozco-Barbosa, University of Castilla-La Mancha =
(Spain)<BR>A. =0A=
Passarella, Univ. Of Cambridge (UK)<BR>Y. Pan, Georgia State Univ. =
(USA)<BR>M. =0A=
Perez-Malumbres, Miguel Hernandez University (Spain)<BR>F. Quiles, =
University of =0A=
Castilla-La Mancha (Spain)<BR>P. Ruiz, University of Murcia =
(Spain)<BR>J.L. =0A=
Sanchez, University of Castilla-La Mancha (Spain)<BR>M. S. Squillante, =
IBM T.J. =0A=
Watson Research Center (USA) <BR>A. Shahrabi, Glasgow Caledonian =
University =0A=
(UK)<BR>T. Miklos, Technical University of Budapest (Hungary)<BR>S. =
Yoshida, =0A=
Kyoto University (Japan)<BR>J. Wu, Florida Atlantic University =
(USA)<BR>A. =0A=
Zomaya, Univ. of Sydney (Australia)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><BR><FONT face=3D"Times New Roman">Publicity Chair<BR>M. S.-M. =
Annoni =0A=
Notare<BR>Barddal University, Florianopolis, SC =
<BR>Brazil<BR>&nbsp;&nbsp; =0A=
<BR>&nbsp;<BR>Paper Submission:<BR>Authors are invited to submit =
manuscripts =0A=
reporting original unpublished research and recent developments <BR>in =
the =0A=
topics related to the workshop. The length of the papers should not =
exceed 10 =0A=
single-spaced pages, <BR>formatted using the ACM style (LaTex2e&nbsp; =
and MS =0A=
Word templates can be found at &lt;</FONT><A =0A=
href=3D"http://www.acm.org/sigs/pubs/proceed/template.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.acm.org/sigs/pubs/proceed/template.html</FONT></A><FONT=
 =0A=
face=3D"Times New Roman">&gt;).<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Papers should be submitted =
electronically in =0A=
PDF format (or postscript) by sending it as an e-mail attachment to =0A=
<BR></FONT><A href=3D"mailto:mohamed@dcs.gla.ac.uk"><FONT =0A=
face=3D"Times New Roman">mohamed@dcs.gla.ac.uk</FONT></A><FONT =0A=
face=3D"Times New Roman"> or </FONT><A =
href=3D"mailto:blanca@dsi.uclm.es"><FONT =0A=
face=3D"Times New Roman">blanca@dsi.uclm.es</FONT></A><FONT =0A=
face=3D"Times New Roman">. All papers will be peer reviewed and the =
comments will =0A=
<BR>be provided to the authors.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Accepted papers will appear in the =
workshop =0A=
proceedings and a special issue will be planned in a scholarly =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">journal to include selected =
high-quality =0A=
papers from the workshop.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Important Dates:<BR>Submission =
Deadline: 10 =0A=
June 2006 <BR>Author Notification: 10 July =0A=
2006</FONT><BR></FONT></DIV></DIV></DIV></DIV></DIV></DIV></DIV></BODY></=
HTML>
------_=_NextPart_001_01C67A53.0FEAFB07--


--===============1466680967==
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

--===============1466680967==--


From manet-bounces@ietf.org Thu May 18 04:17:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fgdgv-0005qW-6M; Thu, 18 May 2006 04:17:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgdgt-0005pB-1i
	for manet@ietf.org; Thu, 18 May 2006 04:17: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 1Fgdgs-0008KM-VA
	for manet@ietf.org; Thu, 18 May 2006 04:17:03 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FgdTM-000890-Nu
	for manet@ietf.org; Thu, 18 May 2006 04:03:08 -0400
Received: from ex1.ad.dcs.gla.ac.uk ([130.209.249.157]:16016)
	by mr1.dcs.gla.ac.uk with esmtp (Exim 4.42)
	id 1FgdTL-0006Bq-IM; Thu, 18 May 2006 09:03:03 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 18 May 2006 08:59:05 +0100
Message-ID: <BED9D15F73EDDE48BF480604236A4560116FCF@ex1.ad.dcs.gla.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
Thread-Index: AcZlxbx8iOSvNfkUTRyLkeSW6R422QAACIzMAAAgo3MAAF/kTgAAG4FQAADVrOAFIVJ8vQ==
References: <BED9D15F73EDDE48BF480604236A4560116E59@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5A@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5B@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5C@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5D@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5F@ex1.ad.dcs.gla.ac.uk>
From: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>
To: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>, <manet@ietf.org>,
	<itc@comsoc.org>, <multicomm@comsoc.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6
Cc: blanca@dsi.uclm.es
Subject: [manet] CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0588293463=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0588293463==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67A51.7CF79672"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67A51.7CF79672
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

[Please accept our apologies if you receive multiple copies of this CFP]
-------------------------------------------------------------------------=
-----------------------------------------
=20
CALL FOR PAPERS
=20
ACM International Workshop on Performance Monitoring, Measurement,
and Evaluation of Heterogeneous Wireless and Wired Networks (PM2HW2N =
2006)
=20
http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html =
<http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html>=20
<http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html>=20
=20
To be held in conjunction with  ACM/IEEE MSWiM 2006
http://www.cs.unibo.it/mswim2006/ <http://www.cs.unibo.it/mswim2006/>=20
=20
October 2-6, 2006
Torremolinos, (Malaga), Spain
=20
=20
Scope:
Wireless networks, including ad hoc, sensor, along with ubiquitous, have =
witnessed=20
over the past few years their fastest growth period and have become =
increasingly complex.=20
Nonetheless, their performance evaluation and analysis have been =
conducted mostly through=20
software simulations. Very recently, some research efforts have been =
directed towards measuring=20
real-world commercial and experimental networks; constructing models =
based on real-world data=20
and using prototypes to more realistically and comprehensively evaluate =
the suggested solutions=20
and more specifically validate the assumptions and the conclusions =
reached via the simulation approach.
=20
The aim of this workshop is to bring together scientists, engineers, and =
practitioners to share and exchange=20
their experiences, discuss challenges, and rey chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FgdTM-000890-Nu
	for manet@ietf.org; Thu, 18 May 2006 04:03:08 -0400
Received: from ex1.ad.dcs.gla.ac.uk ([130.209.249.157]:16016)
	by mr1.dcs.gla.ac.uk with esmtp (Exim 4.42)
	id 1FgdTL-0006Bq-IM; Thu, 18 May 2006 09:03:03 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 18 May 2006 08:59:05 +0100
Message-ID: <BED9D15F73EDDE48BF480604236A4560116FCF@ex1.ad.dcs.gla.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
Thread-Index: AcZlxbx8iOSvNfkUTRyLkeSW6R422QAACIzMAAAgo3MAAF/kTgAAG4FQAADVrOAFIVJ8vQ==
References: <BED9D15F73EDDE48BF480604236A4560116E59@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5A@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5B@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5C@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5D@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5F@ex1.ad.dcs.gla.ac.uk>
From: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>
To: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>, <manet@ietf.org>,
	<itc@comsoc.org>, <multicomm@comsoc.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6
Cc: blanca@dsi.uclm.es
Subject: [manet] CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0588293463=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0588293463==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67A51.7CF79672"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67A51.7CF79672
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

[Please accept our apologies if you receive multiple copies of this CFP]
-------------------------------------------------------------------------=
-----------------------------------------
=20
CALL FOR PAPERS
=20
ACM International Workshop on Performance Monitoring, Measurement,
and Evaluation of Heterogeneous Wireless and Wired Networks (PM2HW2N =
2006)
=20
http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html =
<http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html>=20
<http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html>=20
=20
To be held in conjunction with  ACM/IEEE MSWiM 2006
http://www.cs.unibo.it/mswim2006/ <http://www.cs.unibo.it/mswim2006/>=20
=20
October 2-6, 2006
Torremolinos, (Malaga), Spain
=20
=20
Scope:
Wireless networks, including ad hoc, sensor, along with ubiquitous, have =
witnessed=20
over the past few years their fastest growth period and have become =
increasingly complex.=20
Nonetheless, their performance evaluation and analysis have been =
conducted mostly through=20
software simulations. Very recently, some research efforts have been =
directed towards measuring=20
real-world commercial and experimental networks; constructing models =
based on real-world data=20
and using prototypes to more realistically and comprehensively evaluate =
the suggested solutions=20
and more specifically validate the assumptions and the conclusions =
reached via the simulation approach.
=20
The aim of this workshop is to bring together scientists, engineers, and =
practitioners to share and exchange=20
their experiences, discuss challenges, and report state-of-the-art and =
in-progress research on all aspects=20
of performance measurements, monitoring, and evaluation of heterogeneous =
wired and wireless mobile networks,=20
including, wireless ad hoc, sensor, and ubiquitous networks. Topics of =
interest include, but are not limited to:
=20
- Performance measurement, monitoring, and evaluation tools for =
heterogeneous wireless and wired networks
- Performance tools for ad hoc, sensor, and ubiquitous networks
- Tracing and trace analysis
- Discrete and continuous models
- Measurement-based performance modelling
- Measurement architectures and systems
- QoS monitoring and sampling
- Measurement-based optimisation of for heterogeneous wireless and wired =
networks
- Novel measurement tools of wireless networks
- Performance measurements of ad hoc, sensor, and ubiquitous networks
- Performance analysis and evaluation of mobile services
- Software tools for wireless network performance and evaluation
- Automatic performance analysis=20
- Performance of wireless and sensor devices
- Mobility modeling and management
- Prototype implementation of wireless/mobile networks and systems
- Techniques for prototyping wireless networks
- Validation through measurement and prototyping
- Probabilistic models for ad hoc, sensor, and ubiquitous networks
- Improvement in network performance through prototyping
- Performance tools for ad hoc, sensor and ubiquitous networks
- Performance and security issues in ad hoc, sensor, and ubiquitous =
networks
- Performance and power management control
- Case studies demonstrating the role of performance monitoring, =
measurement, and=20
evaluation in the design of ad hoc, sensor, and ubiquitous networks
-Applications of performance monitoring, measurement, and evaluation as =
a feedback to improve network QoS
=20

Workshop Co-Chairs:
M. Ould-Khaoua
University of Glasgow
UK=20
=20
B. Caminero
University of Castilla-La Mancha
Albacete (Spain)
=20
=20
Program Committee (in progress):
K. Al-Begain, Univ. of Glamorgan (UK)
A. Al-Dubai, Napier Univ. (UK)
N. Abu-Ghazaleh,  SUNY,Binghamton (USA)
I. Awan, Univ. of Bradford (UK)
A. Bermudez, University of Castilla-La Mancha (Spain)
L. Bononi, University of Bologna (Italy)
A. Boukerche, Univ. of Ottawa (Canada)
C.-C. Shen, Univeristy of Delaware (USA)
J.C. Cano, Technical University of Valencia (Spain)
C. Carrion, University of Castilla-La Mancha (Spain)
M. Colajanni, Univ. of Modena (Italy)
P. Cuenca, University of Castilla-La Mancha (Spain)
F.M. Delicado, University of Castilla-La Mancha (Spain)
E. Fleury, INSA de Lyon (France)
V. Gianuzzi, Univ. of Genova (Italy)
E. Karatza, Aristotle University of Thessaloniki (Greece)
A. Ksentini, University of Cergy-Pontoise (France)
P. Manzoni, Technical University of Valencia (Spain)
G. Min, Univ. of Bradford (UK)
M. Naimi, University of Cergy-Pontoise (France)
S. Nikoletseas, Computer Technology Institute (Greece)=20
M. S. M. Annoni Notare, Barddal Univ. (Brazil)
S. Olariu, Old Dominion Univ. (USA)
T. Olivares, University of Castilla-La Mancha (Spain)
L. Orozco-Barbosa, University of Castilla-La Mancha (Spain)
A. Passarella, Univ. Of Cambridge (UK)
Y. Pan, Georgia State Univ. (USA)
M. Perez-Malumbres, Miguel Hernandez University (Spain)
F. Quiles, University of Castilla-La Mancha (Spain)
P. Ruiz, University of Murcia (Spain)
J.L. Sanchez, University of Castilla-La Mancha (Spain)
M. S. Squillante, IBM T.J. Watson Research Center (USA)=20
A. Shahrabi, Glasgow Caledonian University (UK)
T. Miklos, Technical University of Budapest (Hungary)
S. Yoshida, Kyoto University (Japan)
J. Wu, Florida Atlantic University (USA)
A. Zomaya, Univ. of Sydney (Australia)
=20

Publicity Chair
M. S.-M. Annoni Notare
Barddal University, Florianopolis, SC=20
Brazil
  =20
=20
Paper Submission:
Authors are invited to submit manuscripts reporting original unpublished =
research and recent developments=20
in the topics related to the workshop. The length of the papers should =
not exceed 10 single-spaced pages,=20
formatted using the ACM style (LaTex2e  and MS Word templates can be =
fouport state-of-the-art and =
in-progress research on all aspects=20
of performance measurements, monitoring, and evaluation of heterogeneous =
wired and wireless mobile networks,=20
including, wireless ad hoc, sensor, and ubiquitous networks. Topics of =
interest include, but are not limited to:
=20
- Performance measurement, monitoring, and evaluation tools for =
heterogeneous wireless and wired networks
- Performance tools for ad hoc, sensor, and ubiquitous networks
- Tracing and trace analysis
- Discrete and continuous models
- Measurement-based performance modelling
- Measurement architectures and systems
- QoS monitoring and sampling
- Measurement-based optimisation of for heterogeneous wireless and wired =
networks
- Novel measurement tools of wireless networks
- Performance measurements of ad hoc, sensor, and ubiquitous networks
- Performance analysis and evaluation of mobile services
- Software tools for wireless network performance and evaluation
- Automatic performance analysis=20
- Performance of wireless and sensor devices
- Mobility modeling and management
- Prototype implementation of wireless/mobile networks and systems
- Techniques for prototyping wireless networks
- Validation through measurement and prototyping
- Probabilistic models for ad hoc, sensor, and ubiquitous networks
- Improvement in network performance through prototyping
- Performance tools for ad hoc, sensor and ubiquitous networks
- Performance and security issues in ad hoc, sensor, and ubiquitous =
networks
- Performance and power management control
- Case studies demonstrating the role of performance monitoring, =
measurement, and=20
evaluation in the design of ad hoc, sensor, and ubiquitous networks
-Applications of performance monitoring, measurement, and evaluation as =
a feedback to improve network QoS
=20

Workshop Co-Chairs:
M. Ould-Khaoua
University of Glasgow
UK=20
=20
B. Caminero
University of Castilla-La Mancha
Albacete (Spain)
=20
=20
Program Committee (in progress):
K. Al-Begain, Univ. of Glamorgan (UK)
A. Al-Dubai, Napier Univ. (UK)
N. Abu-Ghazaleh,  SUNY,Binghamton (USA)
I. Awan, Univ. of Bradford (UK)
A. Bermudez, University of Castilla-La Mancha (Spain)
L. Bononi, University of Bologna (Italy)
A. Boukerche, Univ. of Ottawa (Canada)
C.-C. Shen, Univeristy of Delaware (USA)
J.C. Cano, Technical University of Valencia (Spain)
C. Carrion, University of Castilla-La Mancha (Spain)
M. Colajanni, Univ. of Modena (Italy)
P. Cuenca, University of Castilla-La Mancha (Spain)
F.M. Delicado, University of Castilla-La Mancha (Spain)
E. Fleury, INSA de Lyon (France)
V. Gianuzzi, Univ. of Genova (Italy)
E. Karatza, Aristotle University of Thessaloniki (Greece)
A. Ksentini, University of Cergy-Pontoise (France)
P. Manzoni, Technical University of Valencia (Spain)
G. Min, Univ. of Bradford (UK)
M. Naimi, University of Cergy-Pontoise (France)
S. Nikoletseas, Computer Technology Institute (Greece)=20
M. S. M. Annoni Notare, Barddal Univ. (Brazil)
S. Olariu, Old Dominion Univ. (USA)
T. Olivares, University of Castilla-La Mancha (Spain)
L. Orozco-Barbosa, University of Castilla-La Mancha (Spain)
A. Passarella, Univ. Of Cambridge (UK)
Y. Pan, Georgia State Univ. (USA)
M. Perez-Malumbres, Miguel Hernandez University (Spain)
F. Quiles, University of Castilla-La Mancha (Spain)
P. Ruiz, University of Murcia (Spain)
J.L. Sanchez, University of Castilla-La Mancha (Spain)
M. S. Squillante, IBM T.J. Watson Research Center (USA)=20
A. Shahrabi, Glasgow Caledonian University (UK)
T. Miklos, Technical University of Budapest (Hungary)
S. Yoshida, Kyoto University (Japan)
J. Wu, Florida Atlantic University (USA)
A. Zomaya, Univ. of Sydney (Australia)
=20

Publicity Chair
M. S.-M. Annoni Notare
Barddal University, Florianopolis, SC=20
Brazil
  =20
=20
Paper Submission:
Authors are invited to submit manuscripts reporting original unpublished =
research and recent developments=20
in the topics related to the workshop. The length of the papers should =
not exceed 10 single-spaced pages,=20
formatted using the ACM style (LaTex2e  and MS Word templates can be =
found at <http://www.acm.org/sigs/pubs/proceed/template.html =
<http://www.acm.org/sigs/pubs/proceed/template.html> >).

Papers should be submitted electronically in PDF format (or postscript) =
by sending it as an e-mail attachment to=20
mohamed@dcs.gla.ac.uk <mailto:mohamed@dcs.gla.ac.uk>  or =
blanca@dsi.uclm.es <mailto:blanca@dsi.uclm.es> . All papers will be peer =
reviewed and the comments will=20
be provided to the authors.
=20
Accepted papers will appear in the workshop proceedings and a special =
issue will be planned in a scholarly=20
journal to include selected high-quality papers from the workshop.
=20
Important Dates:
Submission Deadline: 10 June 2006=20
Author Notification: 10 July 2006


------_=_NextPart_001_01C67A51.7CF79672
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML =
DIR=3Dltr><HEAD></HEAD><BODY>=0A=
<DIV id=3DidOWAReplyText71136 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2><FONT =0A=
face=3D"Times New Roman">[Please accept our apologies if you receive =
multiple =0A=
copies of this =0A=
CFP]<BR>-----------------------------------------------------------------=
-------------------------------------------------</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>CALL FOR PAPERS</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>ACM International Workshop =
on =0A=
Performance Monitoring, Measurement,<BR>and Evaluation of Heterogeneous =
Wireless =0A=
and Wired Networks (PM2HW2N 2006)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html</FONT></A></D=
IV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html"><FONT =0A=
face=3D"Times New Roman"></FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">To be held in conjunction with&nbsp; =
ACM/IEEE =0A=
MSWiM 2006<BR></FONT><A href=3D"http://www.cs.unibo.it/mswim2006/"><FONT =0A=
face=3D"Times New =
Roman">http://www.cs.unibo.it/mswim2006/</FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;<BR>October 2-6, 2006</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Torremolinos, (Malaga), =0A=
Spain<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Scope:<BR>Wireless networks, =
including ad hoc, =0A=
sensor, along with ubiquitous, have witnessed <BR>over the past few =
years their =0A=
fastest growth period and have become increasingly complex. =
<BR>Nonetheless, =0A=
their performance evaluation and analysis have been conducted mostly =
through =0A=
<BR>software simulations. Very recently, some research efforts have been =0A=
directed towards measuring </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">real-world commercial and =
experimental =0A=
networks; constructing models based on real-world data </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and using prototypes to more =
realistically and =0A=
comprehensively evaluate the suggested solutions </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and more specifically validate the =
assumptions =0A=
and the conclusions reached via the simulation =
approach.<BR>&nbsp;<BR>The aim of =0A=
this workshop is to bring together scientists, engineers, and =
practitioners to =0A=
share and exchange </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">their experiences, discuss =
challenges, and =0A=
report state-of-the-art and in-progress research on all aspects =
</FONT></DIV>=0A=
<DIV><nd at <http://www.acm.org/sigs/pubs/proceed/template.html =
<http://www.acm.org/sigs/pubs/proceed/template.html> >).

Papers should be submitted electronically in PDF format (or postscript) =
by sending it as an e-mail attachment to=20
mohamed@dcs.gla.ac.uk <mailto:mohamed@dcs.gla.ac.uk>  or =
blanca@dsi.uclm.es <mailto:blanca@dsi.uclm.es> . All papers will be peer =
reviewed and the comments will=20
be provided to the authors.
=20
Accepted papers will appear in the workshop proceedings and a special =
issue will be planned in a scholarly=20
journal to include selected high-quality papers from the workshop.
=20
Important Dates:
Submission Deadline: 10 June 2006=20
Author Notification: 10 July 2006


------_=_NextPart_001_01C67A51.7CF79672
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML =
DIR=3Dltr><HEAD></HEAD><BODY>=0A=
<DIV id=3DidOWAReplyText71136 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2><FONT =0A=
face=3D"Times New Roman">[Please accept our apologies if you receive =
multiple =0A=
copies of this =0A=
CFP]<BR>-----------------------------------------------------------------=
-------------------------------------------------</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>CALL FOR PAPERS</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>ACM International Workshop =
on =0A=
Performance Monitoring, Measurement,<BR>and Evaluation of Heterogeneous =
Wireless =0A=
and Wired Networks (PM2HW2N 2006)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html</FONT></A></D=
IV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html"><FONT =0A=
face=3D"Times New Roman"></FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">To be held in conjunction with&nbsp; =
ACM/IEEE =0A=
MSWiM 2006<BR></FONT><A href=3D"http://www.cs.unibo.it/mswim2006/"><FONT =0A=
face=3D"Times New =
Roman">http://www.cs.unibo.it/mswim2006/</FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;<BR>October 2-6, 2006</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Torremolinos, (Malaga), =0A=
Spain<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Scope:<BR>Wireless networks, =
including ad hoc, =0A=
sensor, along with ubiquitous, have witnessed <BR>over the past few =
years their =0A=
fastest growth period and have become increasingly complex. =
<BR>Nonetheless, =0A=
their performance evaluation and analysis have been conducted mostly =
through =0A=
<BR>software simulations. Very recently, some research efforts have been =0A=
directed towards measuring </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">real-world commercial and =
experimental =0A=
networks; constructing models based on real-world data </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and using prototypes to more =
realistically and =0A=
comprehensively evaluate the suggested solutions </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and more specifically validate the =
assumptions =0A=
and the conclusions reached via the simulation =
approach.<BR>&nbsp;<BR>The aim of =0A=
this workshop is to bring together scientists, engineers, and =
practitioners to =0A=
share and exchange </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">their experiences, discuss =
challenges, and =0A=
report state-of-the-art and in-progress research on all aspects =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">of performance measurements, =
monitoring, and =0A=
evaluation of heterogeneous wired and wireless mobile networks, =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">including, wireless ad hoc, sensor, =
and =0A=
ubiquitous networks. Topics of interest&nbsp;include, but are not =
limited =0A=
to:<BR>&nbsp;<BR>- Performance measurement, monitoring, and evaluation =
tools for =0A=
heterogeneous wireless and wired networks<BR>- Performance tools for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Tracing and trace analysis<BR>- =
Discrete =0A=
and continuous models<BR>- Measurement-based performance modelling<BR>- =0A=
Measurement architectures and systems<BR>- QoS monitoring and =
sampling<BR>- =0A=
Measurement-based optimisation of for heterogeneous wireless and wired =0A=
networks<BR>- Novel measurement tools of wireless networks<BR>- =
Performance =0A=
measurements of ad hoc, sensor, and ubiquitous networks<BR>- Performance =0A=
analysis and evaluation of mobile services<BR>- Software tools for =
wireless =0A=
network performance and evaluation<BR>- Automatic performance analysis =
<BR>- =0A=
Performance of wireless and sensor devices<BR>- Mobility modeling and =0A=
management<BR>- Prototype implementation of wireless/mobile networks and =0A=
systems<BR>- Techniques for prototyping wireless networks<BR>- =
Validation =0A=
through measurement and prototyping<BR>- Probabilistic models for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Improvement in network performance =
through =0A=
prototyping<BR>- Performance tools for ad hoc, sensor and ubiquitous =0A=
networks<BR>- Performance and security issues in ad hoc, sensor, and =
ubiquitous =0A=
networks<BR>- Performance and power management control<BR>- Case studies =0A=
demonstrating the role of performance monitoring, measurement, and =0A=
<BR>evaluation in the design of ad hoc, sensor, and ubiquitous =0A=
networks<BR>-Applications of performance monitoring, measurement, and =
evaluation =0A=
as a feedback to improve network QoS<BR>&nbsp;<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Workshop Co-Chairs:<BR>M. =0A=
Ould-Khaoua<BR>University of Glasgow<BR>UK&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">B. Caminero<BR>University of =
Castilla-La =0A=
Mancha<BR>Albacete (Spain)<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Program Committee (in =
progress):<BR>K. =0A=
Al-Begain, Univ. of Glamorgan (UK)<BR>A. Al-Dubai, Napier Univ. =
(UK)<BR>N. =0A=
Abu-Ghazaleh,&nbsp; SUNY,Binghamton (USA)<BR>I. Awan, Univ. of Bradford =0A=
(UK)<BR>A. Bermudez, University of Castilla-La Mancha (Spain)<BR>L. =
Bononi, =0A=
University of Bologna (Italy)<BR>A. Boukerche, Univ. of Ottawa =
(Canada)<BR>C.-C. =0A=
Shen, Univeristy of Delaware (USA)<BR>J.C. Cano, Technical University of =0A=
Valencia (Spain)<BR>C. Carrion, University of Castilla-La Mancha =
(Spain)<BR>M. =0A=
Colajanni, Univ. of Modena (Italy)<BR>P. Cuenca, University of =
Castilla-La =0A=
Mancha (Spain)<BR>F.M. Delicado, University of Castilla-La Mancha =
(Spain)<BR>E. =0A=
Fleury, INSA de Lyon (France)<BR>V. Gianuzzi, Univ. of Genova =
(Italy)<BR>E. =0A=
Karatza, Aristotle University of Thessaloniki (Greece)<BR>A. Ksentini, =0A=
University of Cergy-Pontoise (France)<BR>P. Manzoni, Technical =
University of =0A=
Valencia (Spain)<BR>G. Min, Univ. of Bradford (UK)<BR>M. Naimi, =
University of =0A=
Cergy-Pontoise (France)<BR>S. Nikoletseas, Computer Technology Institute =0A=
(Greece) <BR>M. S. M. Annoni Notare, Barddal Univ. (Brazil)<BR>S. =
Olariu, Old =0A=
Dominion Univ. (USA)<BR>T. Olivares, University of Castilla-La Mancha =0A=
(Spain)<BR>L. Orozco-Barbosa, University of Castilla-La Mancha =
(Spain)<BR>A. =0A=
Passarella, Univ. Of Cambridge (UK)<BR>Y. Pan, Georgia State Univ. =
(USA)<BR>M. =0A=
Perez-Malumbres, Miguel Hernandez University (Spain)<BR>F. Quiles, =
University of =0A=
Castilla-La Mancha (Spain)<BR>P. Ruiz, UniversitFONT face=3D"Times New Roman">of performance measurements, =
monitoring, and =0A=
evaluation of heterogeneous wired and wireless mobile networks, =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">including, wireless ad hoc, sensor, =
and =0A=
ubiquitous networks. Topics of interest&nbsp;include, but are not =
limited =0A=
to:<BR>&nbsp;<BR>- Performance measurement, monitoring, and evaluation =
tools for =0A=
heterogeneous wireless and wired networks<BR>- Performance tools for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Tracing and trace analysis<BR>- =
Discrete =0A=
and continuous models<BR>- Measurement-based performance modelling<BR>- =0A=
Measurement architectures and systems<BR>- QoS monitoring and =
sampling<BR>- =0A=
Measurement-based optimisation of for heterogeneous wireless and wired =0A=
networks<BR>- Novel measurement tools of wireless networks<BR>- =
Performance =0A=
measurements of ad hoc, sensor, and ubiquitous networks<BR>- Performance =0A=
analysis and evaluation of mobile services<BR>- Software tools for =
wireless =0A=
network performance and evaluation<BR>- Automatic performance analysis =
<BR>- =0A=
Performance of wireless and sensor devices<BR>- Mobility modeling and =0A=
management<BR>- Prototype implementation of wireless/mobile networks and =0A=
systems<BR>- Techniques for prototyping wireless networks<BR>- =
Validation =0A=
through measurement and prototyping<BR>- Probabilistic models for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Improvement in network performance =
through =0A=
prototyping<BR>- Performance tools for ad hoc, sensor and ubiquitous =0A=
networks<BR>- Performance and security issues in ad hoc, sensor, and =
ubiquitous =0A=
networks<BR>- Performance and power management control<BR>- Case studies =0A=
demonstrating the role of performance monitoring, measurement, and =0A=
<BR>evaluation in the design of ad hoc, sensor, and ubiquitous =0A=
networks<BR>-Applications of performance monitoring, measurement, and =
evaluation =0A=
as a feedback to improve network QoS<BR>&nbsp;<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Workshop Co-Chairs:<BR>M. =0A=
Ould-Khaoua<BR>University of Glasgow<BR>UK&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">B. Caminero<BR>University of =
Castilla-La =0A=
Mancha<BR>Albacete (Spain)<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Program Committee (in =
progress):<BR>K. =0A=
Al-Begain, Univ. of Glamorgan (UK)<BR>A. Al-Dubai, Napier Univ. =
(UK)<BR>N. =0A=
Abu-Ghazaleh,&nbsp; SUNY,Binghamton (USA)<BR>I. Awan, Univ. of Bradford =0A=
(UK)<BR>A. Bermudez, University of Castilla-La Mancha (Spain)<BR>L. =
Bononi, =0A=
University of Bologna (Italy)<BR>A. Boukerche, Univ. of Ottawa =
(Canada)<BR>C.-C. =0A=
Shen, Univeristy of Delaware (USA)<BR>J.C. Cano, Technical University of =0A=
Valencia (Spain)<BR>C. Carrion, University of Castilla-La Mancha =
(Spain)<BR>M. =0A=
Colajanni, Univ. of Modena (Italy)<BR>P. Cuenca, University of =
Castilla-La =0A=
Mancha (Spain)<BR>F.M. Delicado, University of Castilla-La Mancha =
(Spain)<BR>E. =0A=
Fleury, INSA de Lyon (France)<BR>V. Gianuzzi, Univ. of Genova =
(Italy)<BR>E. =0A=
Karatza, Aristotle University of Thessaloniki (Greece)<BR>A. Ksentini, =0A=
University of Cergy-Pontoise (France)<BR>P. Manzoni, Technical =
University of =0A=
Valencia (Spain)<BR>G. Min, Univ. of Bradford (UK)<BR>M. Naimi, =
University of =0A=
Cergy-Pontoise (France)<BR>S. Nikoletseas, Computer Technology Institute =0A=
(Greece) <BR>M. S. M. Annoni Notare, Barddal Univ. (Brazil)<BR>S. =
Olariu, Old =0A=
Dominion Univ. (USA)<BR>T. Olivares, University of Castilla-La Mancha =0A=
(Spain)<BR>L. Orozco-Barbosa, University of Castilla-La Mancha =
(Spain)<BR>A. =0A=
Passarella, Univ. Of Cambridge (UK)<BR>Y. Pan, Georgia State Univ. =
(USA)<BR>M. =0A=
Perez-Malumbres, Miguel Hernandez University (Spain)<BR>F. Quiles, =
University of =0A=
Castilla-La Mancha (Spain)<BR>P. Ruiz, University of Murcia =
(Spain)<BR>J.L. =0A=
Sanchez, University of Castilla-La Mancha (Spain)<BR>M. S. Squillante, =
IBM T.J. =0A=
Watson Research Center (USA) <BR>A. Shahrabi, Glasgow Caledonian =
University =0A=
(UK)<BR>T. Miklos, Technical University of Budapest (Hungary)<BR>S. =
Yoshida, =0A=
Kyoto University (Japan)<BR>J. Wu, Florida Atlantic University =
(USA)<BR>A. =0A=
Zomaya, Univ. of Sydney (Australia)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><BR><FONT face=3D"Times New Roman">Publicity Chair<BR>M. S.-M. =
Annoni =0A=
Notare<BR>Barddal University, Florianopolis, SC =
<BR>Brazil<BR>&nbsp;&nbsp; =0A=
<BR>&nbsp;<BR>Paper Submission:<BR>Authors are invited to submit =
manuscripts =0A=
reporting original unpublished research and recent developments <BR>in =
the =0A=
topics related to the workshop. The length of the papers should not =
exceed 10 =0A=
single-spaced pages, <BR>formatted using the ACM style (LaTex2e&nbsp; =
and MS =0A=
Word templates can be found at &lt;</FONT><A =0A=
href=3D"http://www.acm.org/sigs/pubs/proceed/template.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.acm.org/sigs/pubs/proceed/template.html</FONT></A><FONT=
 =0A=
face=3D"Times New Roman">&gt;).<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Papers should be submitted =
electronically in =0A=
PDF format (or postscript) by sending it as an e-mail attachment to =0A=
<BR></FONT><A href=3D"mailto:mohamed@dcs.gla.ac.uk"><FONT =0A=
face=3D"Times New Roman">mohamed@dcs.gla.ac.uk</FONT></A><FONT =0A=
face=3D"Times New Roman"> or </FONT><A =
href=3D"mailto:blanca@dsi.uclm.es"><FONT =0A=
face=3D"Times New Roman">blanca@dsi.uclm.es</FONT></A><FONT =0A=
face=3D"Times New Roman">. All papers will be peer reviewed and the =
comments will =0A=
<BR>be provided to the authors.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Accepted papers will appear in the =
workshop =0A=
proceedings and a special issue will be planned in a scholarly =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">journal to include selected =
high-quality =0A=
papers from the workshop.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Important Dates:<BR>Submission =
Deadline: 10 =0A=
June 2006 <BR>Author Notification: 10 July =0A=
2006</FONT><BR></FONT></DIV></DIV></DIV></DIV></DIV></DIV></DIV></BODY></=
HTML>
------_=_NextPart_001_01C67A51.7CF79672--


--===============0588293463==
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

--===============0588293463==--






y of Murcia =
(Spain)<BR>J.L. =0A=
Sanchez, University of Castilla-La Mancha (Spain)<BR>M. S. Squillante, =
IBM T.J. =0A=
Watson Research Center (USA) <BR>A. Shahrabi, Glasgow Caledonian =
University =0A=
(UK)<BR>T. Miklos, Technical University of Budapest (Hungary)<BR>S. =
Yoshida, =0A=
Kyoto University (Japan)<BR>J. Wu, Florida Atlantic University =
(USA)<BR>A. =0A=
Zomaya, Univ. of Sydney (Australia)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><BR><FONT face=3D"Times New Roman">Publicity Chair<BR>M. S.-M. =
Annoni =0A=
Notare<BR>Barddal University, Florianopolis, SC =
<BR>Brazil<BR>&nbsp;&nbsp; =0A=
<BR>&nbsp;<BR>Paper Submission:<BR>Authors are invited to submit =
manuscripts =0A=
reporting original unpublished research and recent developments <BR>in =
the =0A=
topics related to the workshop. The length of the papers should not =
exceed 10 =0A=
single-spaced pages, <BR>formatted using the ACM style (LaTex2e&nbsp; =
and MS =0A=
Word templates can be found at &lt;</FONT><A =0A=
href=3D"http://www.acm.org/sigs/pubs/proceed/template.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.acm.org/sigs/pubs/proceed/template.html</FONT></A><FONT=
 =0A=
face=3D"Times New Roman">&gt;).<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Papers should be submitted =
electronically in =0A=
PDF format (or postscript) by sending it as an e-mail attachment to =0A=
<BR></FONT><A href=3D"mailto:mohamed@dcs.gla.ac.uk"><FONT =0A=
face=3D"Times New Roman">mohamed@dcs.gla.ac.uk</FONT></A><FONT =0A=
face=3D"Times New Roman"> or </FONT><A =
href=3D"mailto:blanca@dsi.uclm.es"><FONT =0A=
face=3D"Times New Roman">blanca@dsi.uclm.es</FONT></A><FONT =0A=
face=3D"Times New Roman">. All papers will be peer reviewed and the =
comments will =0A=
<BR>be provided to the authors.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Accepted papers will appear in the =
workshop =0A=
proceedings and a special issue will be planned in a scholarly =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">journal to include selected =
high-quality =0A=
papers from the workshop.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Important Dates:<BR>Submission =
Deadline: 10 =0A=
June 2006 <BR>Author Notification: 10 July =0A=
2006</FONT><BR></FONT></DIV></DIV></DIV></DIV></DIV></DIV></DIV></BODY></=
HTML>
------_=_NextPart_001_01C67A51.7CF79672--


--===============0588293463==
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

--===============0588293463==--






From manet-bounces@ietf.org Thu May 18 13:57:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fgmjn-0002r5-GY; Thu, 18 May 2006 13:56:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgmjl-0002r0-Cg
	for manet@ietf.org; Thu, 18 May 2006 13:56:37 -0400
Received: from mailfe03.tele2.fr ([212.247.154.76] helo=swip.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fgmjj-0000SC-PX
	for manet@ietf.org; Thu, 18 May 2006 13:56:37 -0400
X-T2-Posting-ID: awqqfnaTsr4Tdz6hsMRmdZcsIOrGCpI/YK875gkeDuo=
X-Cloudmark-Score: 0.000000 []
Received: from [213.103.23.57] (HELO DAMIEN)
	by mailfe03.swip.net (CommuniGate Pro SMTP 5.0.8)
	with ESMTP id 204695929; Thu, 18 May 2006 19:56:20 +0200
Message-ID: <17715159.81147974998816.JavaMail.Commandeur@DAMIEN>
Date: Thu, 18 May 2006 19:56:35 +0200 (CEST)
From: magoni@dpt-info.u-strasbg.fr
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: pdini@cisco.com, dumitru.roman@deri.org
Subject: [manet] CFP ICSEA 2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


===================================================
Apologies for multiple postings
 
2nd CALL FOR PAPERS
 
International Conference on Software Engineering Advances, ICSEA 2006 
October 29 -November 1, 2006, Tahiti.
 
Call for Papers: http://www.iaria.org/conferences/CfPICSEA06.html
 
Submission: Go to http://www.iaria.org/conferences/ICSEA06.html
and click "Submit a paper"

Deadlines:
Submission deadline: June 1, 2006
Notification: July 1, 2006
Camera ready: July 15, 2006 

ICSEA 2006 initiates a series of events covering a broad spectrum of
software-related topics. The conference covers fundamentals on
designing, implementing, testing, validating and maintaining various
kinds of software. Several tracks are proposed to treat the topics from
theory to practice, in terms of methodologies, design, implementation,
testing, use cases, tools, and lessons learnt. The conference topics
cover classical and advanced methodologies, open source, agile software,
as well as software deployment and software economics and education.  

The conference has the following tracks:

Track 1 Advances in fundamentals for software development 
Track 2 Advanced mechanisms for software development 
Track 3 Advanced design tools for developing software 
Track 4 Advanced facilities for accessing software 
Track 5 Software performance 
Track 6 Software security, privacy, safeness
Track 7 Advances in software testing
Track 8 Specialized software advanced applications 
Track 9 Open source software 
Track 10 Agile software techniques 
Track 11 Software deployment and maintenance 
Track 12 Software economics, adoption, and education

We welcome technical papers presenting research and practical results,
position papers addressing the pros and cons of specific proposals, such
as those being discussed in the standard fora or in industry consortia,
survey papers addressing the key problems and solutions on any of the
above topics short papers on work in progress, and panel proposals. 

The topics suggested by the conference can be discussed in term of
concepts, state of the art, standards, implementations, running
experiments and applications. Authors are invited to submit complete
unpublished papers, which are not under review in any other conference
or journal in the following, but not limited topic areas. Industrial
presentations are not subject to these constraints. Tutorials on
specific related topics and panels on challenging areas are encouraged.

http://www.iaria.org/conferences/CfPICSEA06.html

The ICSEA 2006 Proceedings are published by the IEEE Computer Society
Press, and are indexed by SCI and EI via IEEE. 

Regular papers
Only .pdf or .doc files will be accepted for paper submission. All
papers submitted via the EDAS system will receive an ID that will be
e-mailed to the contact author. 

Final author manuscripts will be 8.5" x 11" (two columns IEEE format),
not exceeding 6 pages; max 4 extra pages allowed at additional cost. The
formatting instructions can be found via anonymous FTP site at:
ftp://pubftp.computer.org/Press/Outgoing/proceedings/8.5x11%20-%20Formatting%20files/instruct.pdf

Once you receive the notification of paper acceptance, you will be
provided by the IEEE CS Press an online author kit with all the steps an
author needs to follow to submit the final version.

Technical marketing/business/positioning presentations
The conference initiates a series of business, technical marketing, and
positioning presentations on the same topics. Speakers must submit a
10-12 slide deck presentations with substantial notes accompanying the
slides, in the .ppt format (.pdf-ed). The slide deck will be published
in the conference's CD collection, together with the regular papers.
Please send your presentations to petre@iaria.org.
 
Tutorials
Tutorials provide overviews of current high interest topics. Proposals
can be for half or full day tutorials. Please send your proposals to
petre@iaria.org.

 
Panel proposals:
The organizers encourage scientists and industry leaders to organize
dedicated panels dealing with controversial and challenging topics and
paradigms. Panel moderators are asked to identify their guests and
manage that their appropriate talk supports timely reach our deadlines.
Moderators must specifically submit an official proposal, indicating
their background, panelist names, their affiliation, the topic of the
panel, as well as short biographies. For more information,
petre@iaria.org.
 
Workshop proposals
We welcome workshop proposals on issues complementary to the topics of
this conference. Your requests should be forwarded to petre@iaria.org.

Looking  forward for your submissions,

Thanks,
On behalf of the ICSEA Advisory Committee
Petre Dini, pdini@cisco.com
==================================================

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



From manet-bounces@ietf.org Thu May 18 13:59:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fgmms-0006Bg-3U; Thu, 18 May 2006 13:59:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgmmq-0006Bb-Rr
	for manet@ietf.org; Thu, 18 May 2006 13:59:48 -0400
Received: from mailfe11.tele2.fr ([212.247.155.76] helo=swip.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fgmmq-0000j4-C5
	for manet@ietf.org; Thu, 18 May 2006 13:59:48 -0400
X-T2-Posting-ID: awqqfnaTsr4Tdz6hsMRmdZcsIOrGCpI/YK875gkeDuo=
X-Cloudmark-Score: 0.000000 []
Received: from [213.103.23.57] (HELO DAMIEN)
	by mailfe11.swip.net (CommuniGate Pro SMTP 5.0.8)
	with ESMTP id 29326846; Thu, 18 May 2006 19:59:42 +0200
Message-ID: <23056977.231147975201848.JavaMail.Commandeur@DAMIEN>
Date: Thu, 18 May 2006 19:59:58 +0200 (CEST)
From: magoni@dpt-info.u-strasbg.fr
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: pdini@cisco.com, dumitru.roman@deri.org
Subject: [manet] 2nd Cfp - ICSNC 2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


===================================================
Apologies for multiple postings
 
2nd CALL FOR PAPERS
 
International Conference on  Systems and Networks Communications, ICSNC 2006 
November 2 - November 4, 2006, Tahiti.
 
Call for Papers: http://www.iaria.org/conferences/CfPICSNC06.html
 
Submission: Go to http://www.iaria.org/conferences/ICSNC06.html and click 
"Submit a paper"

Deadlines:
Submission deadline: June 1, 2006
Notification: July 1, 2006
Camera ready: July 15, 2006 

The Second International Conference on Systems and Networks
Communications continues a series of events covering a broad spectrum of
systems and networks related topics. The conference covers fundamentals
on wireless, high speed, sensor and mobile and ad hoc networks,
security, policy based systems, and education systems. Topics are
targeting design, implementation, testing, use cases, tools, and lessons
learnt for such networks and systems.

The conference has the following specialized topics (mini-conferences) :


WINET 2006       Wireless networks                            
HSNET 2006       High speed networks                            
SENET 2006       Sensor networks
MHNET 2006     Mobile and Ad hoc networks                
SESYS 2006       Security systems
MCSYS 2006      Multimedia communications systems   
POSYS 2006       Policy-based systems                            
PESYS 2006        Pervasive education systems      

We welcome technical papers presenting research and practical results,
position papers addressing the pros and cons of specific proposals, such
as those being discussed in the standard fora or in industry consortia,
survey papers addressing the key problems and solutions on any of the
above topics short papers on work in progress, and panel proposals. 

The topics suggested by the conference can be discussed in term of
concepts, state of the art, standards, implementations, running
experiments and applications. Authors are invited to submit complete
unpublished papers, which are not under review in any other conference
or journal in the following, but not limited topic areas. Industrial
presentations are not subject to these constraints. Tutorials on
specific related topics and panels on challenging areas are encouraged. 

http://www.iaria.org/conferences/CfPICSEA06.html

The ICSNC  2006 Proceedings are published by the IEEE Computer Society
Press, and are indexed by SCI and EI via IEEE. 

Regular papers
Only .pdf or .doc files will be accepted for paper submission. All
papers submitted via the EDAS system will receive an ID that will be
e-mailed to the contact author. 

Final author manuscripts will be 8.5" x 11" (two columns IEEE format),
not exceeding 6 pages; max 4 extra pages allowed at additional cost. The
formatting instructions can be found via anonymous FTP site at:
ftp://pubftp.computer.org/Press/Outgoing/proceedings/8.5x11%20-%20Formatting%20files/instruct.pdf

Once you receive the notification of paper acceptance, you will be
provided by the IEEE CS Press an online author kit with all the steps an
author needs to follow to submit the final version. .

Technical marketing/business/positioning presentations
The conference initiates a series of business, technical marketing, and
positioning presentations on the same topics. Speakers must submit a
10-12 slide deck presentations with substantial notes accompanying the
slides, in the .ppt format (.pdf-ed). The slide deck will be published
in the conference's CD collection, together with the regular papers.
Please send your presentations to petre@iaria.org.
 
Tutorials
Tutorials provide overviews of current high interest topics. Proposals
can be for half or full day tutorials. Please send your proposals to
petre@iaria.org.

Panel proposals:
The organizers encourage scientists and industry leaders to organize
dedicated panels dealing with controversial and challenging topics and
paradigms. Panel moderators are asked to identify their guests and
manage that their appropriate talk supports timely reach our deadlines.
Moderators must specifically submit an official proposal, indicating
their background, panelist names, their affiliation, the topic of the
panel, as well as short biographies. For more information,
petre@iaria.org.
 
Workshop proposals
We welcome workshop proposals on issues complementary to the topics of
this conference. Your requests should be forwarded to petre@iaria.org.

Looking  forward for your submissions,

Thanks,
On behalf of the ICSNC Advisory Committee
Petre Dini, pdini@cisco.com
==================================================

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



From manet-bounces@ietf.org Thu May 18 18:14:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fgqi5-0006fW-0L; Thu, 18 May 2006 18:11:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgqi4-0006fO-Cj
	for manet@ietf.org; Thu, 18 May 2006 18:11:08 -0400
Received: from wx-out-0102.google.com ([66.249.82.193])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fgqi3-0002Is-6m
	for manet@ietf.org; Thu, 18 May 2006 18:11:08 -0400
Received: by wx-out-0102.google.com with SMTP id s12so464702wxc
	for <manet@ietf.org>; Thu, 18 May 2006 15:11:07 -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=hes9grcwhuJZtr5lbwvAz5WRPSgD4/2ffAmfnDAGevSBR1vT6aGGI2Pf7l8JEuMerF0VroBnHU7BP2GgYCp7jMxfFWgy3OgfwQlXxZ/Rx1Bg+jTFYpOD3nzsKZPDyi4Sa2nhNjoQ3NAhKe8C2QM1sEWOicTXvggR+HXvP6VfJYs=
Received: by 10.70.18.1 with SMTP id 1mr1286122wxr;
	Thu, 18 May 2006 15:11:05 -0700 (PDT)
Received: by 10.70.100.2 with HTTP; Thu, 18 May 2006 15:11:05 -0700 (PDT)
Message-ID: <bc0406d70605181511w4b585733g4352cc434e8233b8@mail.gmail.com>
Date: Thu, 18 May 2006 17:11:05 -0500
From: "Taha Ben Brahim" <bbtaha@gmail.com>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Subject: [manet] Manet losses
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1500776258=="
Errors-To: manet-bounces@ietf.org

--===============1500776258==
Content-Type: multipart/alternative; 
	boundary="----=_Part_123250_11874858.1147990265600"

------=_Part_123250_11874858.1147990265600
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Dear All,

I am looking for the kinds of errors that generate a packet loss in a MANET=
,
as far as i know there is just four kinds:

1- Routing loss.
2- Congestion loss.
3- link failure loss.
4- power loss.

is there any other kind of error that makes a packet be lost?
references are highly

cheers,

Ben

------=_Part_123250_11874858.1147990265600
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>Dear All,</div>
<div>&nbsp;</div>
<div>I am looking for the kinds of errors that generate a packet loss in a =
MANET, as far as i know there is just four kinds:</div>
<div>&nbsp;</div>
<div>1- Routing loss.</div>
<div>2- Congestion loss.</div>
<div>3- link failure loss.</div>
<div>4- power loss.</div>
<div>&nbsp;</div>
<div>is there any other kind of error that makes a packet be lost?</div>
<div>references are highly</div>
<div>&nbsp;</div>
<div>cheers,</div>
<div>&nbsp;</div>
<div>Ben&nbsp;</div>

------=_Part_123250_11874858.1147990265600--


--===============1500776258==
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

--===============1500776258==--




From manet-bounces@ietf.org Thu May 18 18:20:40 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fgqov-00031t-Sb; Thu, 18 May 2006 18:18:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fgqot-00031Y-Qw
	for manet@ietf.org; Thu, 18 May 2006 18:18:11 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fgqom-0002c5-H0
	for manet@ietf.org; Thu, 18 May 2006 18:18:06 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [manet] Manet losses
Date: Thu, 18 May 2006 16:17:58 -0600
Message-ID: <8536FDFA3AD04A49A15804915996569106FEC7D2@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] Manet losses
Thread-Index: AcZ6yBFMyXxmfbH+RyCluevrzBjX1wAAD54w
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "Taha Ben Brahim" <bbtaha@gmail.com>,
	<manet@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0302529686=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0302529686==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67AC8.EB52D882"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67AC8.EB52D882
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

HI Ben,
=20
I'm not sure how your categories work.  For example, congestion could
refer to data collisions, timeouts due to excessive dealy, or buffer
overflows. At any rate, in wireless nets, there are random packet losses
due to shadowing, fading, and increases in local interference.  That is,
you may be able to sucessfully deliver 90% of the packets on a link,
which means 10% are randomly lost.  If you haven't included them, you
would want to add them.
=20

John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
 =20

=20

________________________________

From: Taha Ben Brahim [mailto:bbtaha@gmail.com]=20
Sent: Thursday, May 18, 2006 4:11 PM
To: manet@ietf.org
Subject: [manet] Manet losses


Dear All,
=20
I am looking for the kinds of errors that generate a packet loss in a
MANET, as far as i know there is just four kinds:
=20
1- Routing loss.
2- Congestion loss.
3- link failure loss.
4- power loss.
=20
is there any other kind of error that makes a packet be lost?
references are highly
=20
cheers,
=20
Ben=20

------_=_NextPart_001_01C67AC8.EB52D882
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D748371322-18052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>HI Ben,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D748371322-18052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D748371322-18052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I'm not sure how your categories work.&nbsp; =
For example,=20
congestion could refer to data collisions, timeouts due to excessive =
dealy, or=20
buffer overflows. At any rate, in wireless nets, there are random packet =
losses=20
due to shadowing, fading, and increases in local interference.&nbsp; =
That is,=20
you may be able to sucessfully deliver 90% of the packets on a link, =
which means=20
10% are randomly lost.&nbsp; </FONT></SPAN><SPAN =
class=3D748371322-18052006><FONT=20
face=3DArial color=3D#0000ff size=3D2>If you haven't included them, you =
would want to=20
add them.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV><!-- Converted from text/plain format -->
<P><FONT size=3D2>John P. Mullen, Ph.D.<BR>(505)=20
646-2958<BR>jomullen@nmsu.edu<BR>&nbsp;</FONT> </P>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Taha Ben Brahim =
[mailto:bbtaha@gmail.com]=20
<BR><B>Sent:</B> Thursday, May 18, 2006 4:11 PM<BR><B>To:</B>=20
manet@ietf.org<BR><B>Subject:</B> [manet] Manet =
losses<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Dear All,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I am looking for the kinds of errors that generate a packet loss in =
a=20
MANET, as far as i know there is just four kinds:</DIV>
<DIV>&nbsp;</DIV>
<DIV>1- Routing loss.</DIV>
<DIV>2- Congestion loss.</DIV>
<DIV>3- link failure loss.</DIV>
<DIV>4- power loss.</DIV>
<DIV>&nbsp;</DIV>
<DIV>is there any other kind of error that makes a packet be lost?</DIV>
<DIV>references are highly</DIV>
<DIV>&nbsp;</DIV>
<DIV>cheers,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Ben&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C67AC8.EB52D882--


--===============0302529686==
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

--===============0302529686==--




From manet-bounces@ietf.org Thu May 18 19:47:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FgsC9-0004n5-65; Thu, 18 May 2006 19:46:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FgsC7-0004mY-SL
	for manet@ietf.org; Thu, 18 May 2006 19:46:15 -0400
Received: from wr-out-0506.google.com ([64.233.184.230])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FgsC6-00088r-Hh
	for manet@ietf.org; Thu, 18 May 2006 19:46:15 -0400
Received: by wr-out-0506.google.com with SMTP id 57so487110wri
	for <manet@ietf.org>; Thu, 18 May 2006 16:46:14 -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=ltj4qDFdfXUpJwFcunfdzA8QwBThMqEEPUOY0YoNJiaAXFuvEWq2snVx68IXFDrGdlv6CcE1aLuSJ2trTmwiCcmtCRHYQzFsVEMPSkikujOqX80XIFH28Ayfnyvmav3OS3Dgh8psqvP1SIJmdQ8wvPGeUfzyoxGTTSdjAroDz0M=
Received: by 10.64.91.12 with SMTP id o12mr1036788qbb;
	Thu, 18 May 2006 16:46:14 -0700 (PDT)
Received: by 10.65.181.10 with HTTP; Thu, 18 May 2006 16:46:14 -0700 (PDT)
Message-ID: <738ad5960605181646g7335fedcl1c7c80a3d918b3d7@mail.gmail.com>
Date: Fri, 19 May 2006 01:46:14 +0200
From: "iaria - announce" <iaria.announce@gmail.com>
To: ifip-tc6@informatik.rwth-aachen.de, 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-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: pdini@cisco.com
Subject: [manet] 2nd CFP: International Conference on Software Engineering
	Advances, ICSEA 2006, October 29 -November 1, 2006, Tahiti
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
Apologies for multiple postings

2nd CALL FOR PAPERS

International Conference on Software Engineering Advances, ICSEA 2006
October 29 -November 1, 2006, Tahiti.

Call for Papers: http://www.iaria.org/conferences/CfPICSEA06.html

Submission: Go to http://www.iaria.org/conferences/ICSEA06.html
and click "Submit a paper"

Deadlines:
Submission deadline: June 1, 2006
Notification: July 1, 2006
Camera ready: July 15, 2006

ICSEA 2006 initiates a series of events covering a broad spectrum of
software-related topics. The conference covers fundamentals on
designing, implementing, testing, validating and maintaining various
kinds of software. Several tracks are proposed to treat the topics from
theory to practice, in terms of methodologies, design, implementation,
testing, use cases, tools, and lessons learnt. The conference topics
cover classical and advanced methodologies, open source, agile software,
as well as software deployment and software economics and education.

The conference has the following tracks:

Track 1 Advances in fundamentals for software development
Track 2 Advanced mechanisms for software development
Track 3 Advanced design tools for developing software
Track 4 Advanced facilities for accessing software
Track 5 Software performance
Track 6 Software security, privacy, safeness
Track 7 Advances in software testing
Track 8 Specialized software advanced applications
Track 9 Open source software
Track 10 Agile software techniques
Track 11 Software deployment and maintenance
Track 12 Software economics, adoption, and education

We welcome technical papers presenting research and practical results,
position papers addressing the pros and cons of specific proposals, such
as those being discussed in the standard fora or in industry consortia,
survey papers addressing the key problems and solutions on any of the
above topics short papers on work in progress, and panel proposals.

The topics suggested by the conference can be discussed in term of
concepts, state of the art, standards, implementations, running
experiments and applications. Authors are invited to submit complete
unpublished papers, which are not under review in any other conference
or journal in the following, but not limited topic areas. Industrial
presentations are not subject to these constraints. Tutorials on
specific related topics and panels on challenging areas are encouraged.

http://www.iaria.org/conferences/CfPICSEA06.html

The ICSEA 2006 Proceedings are published by the IEEE Computer Society
Press, and are indexed by SCI and EI via IEEE.

Regular papers
Only .pdf or .doc files will be accepted for paper submission. All
papers submitted via the EDAS system will receive an ID that will be
e-mailed to the contact author.

Final author manuscripts will be 8.5" x 11" (two columns IEEE format),
not exceeding 6 pages; max 4 extra pages allowed at additional cost. The
formatting instructions can be found via anonymous FTP site at:
ftp://pubftp.computer.org/Press/Outgoing/proceedings/8.5x11%20-%20Formattin=
g%20files/instruct.pdf

Once you receive the notification of paper acceptance, you will be
provided by the IEEE CS Press an online author kit with all the steps an
author needs to follow to submit the final version.

Technical marketing/business/positioning presentations
The conference initiates a series of business, technical marketing, and
positioning presentations on the same topics. Speakers must submit a
10-12 slide deck presentations with substantial notes accompanying the
slides, in the .ppt format (.pdf-ed). The slide deck will be published
in the conference's CD collection, together with the regular papers.
Please send your presentations to petre@iaria.org.

Tutorials
Tutorials provide overviews of current high interest topics. Proposals
can be for half or full day tutorials. Please send your proposals to
petre@iaria.org.


Panel proposals:
The organizers encourage scientists and industry leaders to organize
dedicated panels dealing with controversial and challenging topics and
paradigms. Panel moderators are asked to identify their guests and
manage that their appropriate talk supports timely reach our deadlines.
Moderators must specifically submit an official proposal, indicating
their background, panelist names, their affiliation, the topic of the
panel, as well as short biographies. For more information,
petre@iaria.org.

Workshop proposals
We welcome workshop proposals on issues complementary to the topics of
this conference. Your requests should be forwarded to petre@iaria.org.

Looking  forward for your submissions,

Thanks,
On behalf of the ICSEA Advisory Committee
Petre Dini, pdini@cisco.com
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From manet-bounces@ietf.org Thu May 18 19:55:06 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FgsKa-000240-6F; Thu, 18 May 2006 19:55:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FgsKY-00023v-QR
	for manet@ietf.org; Thu, 18 May 2006 19:54:58 -0400
Received: from wr-out-0506.google.com ([64.233.184.231])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FgsKY-0000Cz-GP
	for manet@ietf.org; Thu, 18 May 2006 19:54:58 -0400
Received: by wr-out-0506.google.com with SMTP id 57so488247wri
	for <manet@ietf.org>; Thu, 18 May 2006 16:54:58 -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=VcTLgXwSoLFlxCDahh268fCamqxRuhUxt4NqF1lglackN7FbZ3aPf3fMPud0CsfecpQnKLe4oTi5pxRl0K9I+D7jeZLElp6HBgC3qwPdwApbigM4tcfrLL8SkR5RQ7OlPiuBbJujeAhp2/GnGBn5jYUBxWYYWV2oxJkDcHcNuZU=
Received: by 10.64.91.12 with SMTP id o12mr1040066qbb;
	Thu, 18 May 2006 16:54:58 -0700 (PDT)
Received: by 10.65.181.10 with HTTP; Thu, 18 May 2006 16:54:58 -0700 (PDT)
Message-ID: <738ad5960605181654i21ea6d1em5890a2d496a33139@mail.gmail.com>
Date: Fri, 19 May 2006 01:54:58 +0200
From: "iaria - announce" <iaria.announce@gmail.com>
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-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Cc: pdini@cisco.com
Subject: [manet] 2nd CFP: International Conference on Systems and Networks
	Communications, ICSNC 2006, November 2 - November 4, 2006, Tahiti
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
Apologies for multiple postings

2nd CALL FOR PAPERS

International Conference on  Systems and Networks Communications, ICSNC 200=
6
November 2 - November 4, 2006, Tahiti.

Call for Papers: http://www.iaria.org/conferences/CfPICSNC06.html

Submission: Go to http://www.iaria.org/conferences/ICSNC06.html and click
"Submit a paper"

Deadlines:
Submission deadline: June 1, 2006
Notification: July 1, 2006
Camera ready: July 15, 2006

The Second International Conference on Systems and Networks
Communications continues a series of events covering a broad spectrum of
systems and networks related topics. The conference covers fundamentals
on wireless, high speed, sensor and mobile and ad hoc networks,
security, policy based systems, and education systems. Topics are
targeting design, implementation, testing, use cases, tools, and lessons
learnt for such networks and systems.

The conference has the following specialized topics (mini-conferences) :


WINET 2006       Wireless networks
HSNET 2006       High speed networks
SENET 2006       Sensor networks
MHNET 2006     Mobile and Ad hoc networks
SESYS 2006       Security systems
MCSYS 2006      Multimedia communications systems
POSYS 2006       Policy-based systems
PESYS 2006        Pervasive education systems

We welcome technical papers presenting research and practical results,
position papers addressing the pros and cons of specific proposals, such
as those being discussed in the standard fora or in industry consortia,
survey papers addressing the key problems and solutions on any of the
above topics short papers on work in progress, and panel proposals.

The topics suggested by the conference can be discussed in term of
concepts, state of the art, standards, implementations, running
experiments and applications. Authors are invited to submit complete
unpublished papers, which are not under review in any other conference
or journal in the following, but not limited topic areas. Industrial
presentations are not subject to these constraints. Tutorials on
specific related topics and panels on challenging areas are encouraged.

http://www.iaria.org/conferences/CfPICSEA06.html

The ICSNC  2006 Proceedings are published by the IEEE Computer Society
Press, and are indexed by SCI and EI via IEEE.

Regular papers
Only .pdf or .doc files will be accepted for paper submission. All
papers submitted via the EDAS system will receive an ID that will be
e-mailed to the contact author.

Final author manuscripts will be 8.5" x 11" (two columns IEEE format),
not exceeding 6 pages; max 4 extra pages allowed at additional cost. The
formatting instructions can be found via anonymous FTP site at:
ftp://pubftp.computer.org/Press/Outgoing/proceedings/8.5x11%20-%20Formattin=
g%20files/instruct.pdf

Once you receive the notification of paper acceptance, you will be
provided by the IEEE CS Press an online author kit with all the steps an
author needs to follow to submit the final version. .

Technical marketing/business/positioning presentations
The conference initiates a series of business, technical marketing, and
positioning presentations on the same topics. Speakers must submit a
10-12 slide deck presentations with substantial notes accompanying the
slides, in the .ppt format (.pdf-ed). The slide deck will be published
in the conference's CD collection, together with the regular papers.
Please send your presentations to petre@iaria.org.

Tutorials
Tutorials provide overviews of current high interest topics. Proposals
can be for half or full day tutorials. Please send your proposals to
petre@iaria.org.

Panel proposals:
The organizers encourage scientists and industry leaders to organize
dedicated panels dealing with controversial and challenging topics and
paradigms. Panel moderators are asked to identify their guests and
manage that their appropriate talk supports timely reach our deadlines.
Moderators must specifically submit an official proposal, indicating
their background, panelist names, their affiliation, the topic of the
panel, as well as short biographies. For more information,
petre@iaria.org.

Workshop proposals
We welcome workshop proposals on issues complementary to the topics of
this conference. Your requests should be forwarded to petre@iaria.org.

Looking  forward for your submissions,

Thanks,
On behalf of the ICSNC Advisory Committee
Petre Dini, pdini@cisco.com
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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



From manet-bounces@ietf.org Fri May 19 09:27:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fh4z4-0003Il-TG; Fri, 19 May 2006 09:25:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fh4z3-0003GB-PH
	for manet@ietf.org; Fri, 19 May 2006 09:25:37 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fh4z0-0007f6-Qi
	for manet@ietf.org; Fri, 19 May 2006 09:25:37 -0400
Received: from ex1.ad.dcs.gla.ac.uk ([130.209.249.157]:3862)
	by mr1.dcs.gla.ac.uk with esmtp (Exim 4.42)
	id 1Fh4z0-0007Q4-A9; Fri, 19 May 2006 14:25:34 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 19 May 2006 14:25:00 +0100
Message-ID: <BED9D15F73EDDE48BF480604236A4560116FE3@ex1.ad.dcs.gla.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
Thread-Index: AcZlxbx8iOSvNfkUTRyLkeSW6R422QAACIzMAAAgo3MAAF/kTgAAG4FQAAD2q90FXt36jw==
References: <BED9D15F73EDDE48BF480604236A4560116E59@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5A@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5B@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5C@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5D@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E62@ex1.ad.dcs.gla.ac.uk>
From: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>
To: <ifip-tc6@informatik.rwth-aachen.de>,
	<manet@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6
Cc: blanca@dsi.uclm.es
Subject: [manet] CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1254036152=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1254036152==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67B47.B4EB126F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67B47.B4EB126F
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

[Please accept our apologies if you receive multiple copies of this CFP]
-------------------------------------------------------------------------=
-----------------------------------------
=20
CALL FOR PAPERS
=20
ACM International Workshop on Performance Monitoring, Measurement,
and Evaluation of Heterogeneous Wireless and Wired Networks (PM2HW2N =
2006)
=20
http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html =
<http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html>=20
<http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html>=20
=20
To be held in conjunction with  ACM/IEEE MSWiM 2006
http://www.cs.unibo.it/mswim2006/ <http://www.cs.unibo.it/mswim2006/>=20
=20
October 2-6, 2006
Torremolinos, (Malaga), Spain
=20
=20
Scope:
Wireless networks, including ad hoc, sensor, along with ubiquitous, have =
witnessed=20
over the past few years their fastest growth period and have become =
increasingly complex.=20
Nonetheless, their performance evaluation and analysis have been =
conducted mostly through=20
software simulations. Very recently, some research efforts have been =
directed towards measuring=20
real-world commercial and experimental networks; constructing models =
based on real-world data=20
and using prototypes to more realistically and comprehensively evaluate =
the suggested solutions=20
and more specifically validate the assumptions and the conclusions =
reached via the simulation approach.
=20
The aim of this workshop is to bring together scientists, engineers, and =
practitioners to share and exchange=20
their experiences, discuss challenges, and report state-of-the-art and =
in-progress research on all aspects=20
of performance measurements, monitoring, and evaluation of heterogeneous =
wired and wireless mobile networks,=20
including, wireless ad hoc, sensor, and ubiquitous networks. Topics of =
interest include, but are not limited to:
=20
- Performance measurement, monitoring, and evaluation tools for =
heterogeneous wireless and wired networks
- Performance tools for ad hoc, sensor, and ubiquitous networks
- Tracing and trace analysis
- Discrete and continuous models
- Measurement-based performance modelling
- Measurement architectures and systems
- QoS monitoring and sampling
- Measurement-based optimisation of for heterogeneous wireless and wired =
networks
- Novel measurement tools of wireless networks
- Performance measurements of ad hoc, sensor, and ubiquitous networks
- Performance analysis and evaluation of mobile services
- Software tools for wireless network performance and evaluation
- Automatic performance analysis=20
- Performance of wireless and sensor devices
- Mobility modeling and management
- Prototype implementation of wireless/mobile networks and systems
- Techniques for prototyping wireless networks
- Validation through measurement and prototyping
- Probabilistic models for ad hoc, sensor, and ubiquitous networks
- Improvement in network performance through prototyping
- Performance tools for ad hoc, sensor and ubiquitous networks
- Performance and security issues in ad hoc, sensor, and ubiquitous =
networks
- Performance and power management control
- Case studies demonstrating the role of performance monitoring, =
measurement, and=20
evaluation in the design of ad hoc, sensor, and ubiquitous networks
-Applications of performance monitoring, measurement, and evaluation as =
a feedback to improve network QoS
=20

Workshop Co-Chairs:
M. Ould-Khaoua
University of Glasgow
UK=20
=20
B. Caminero
University of Castilla-La Mancha
Albacete (Spain)
=20
=20
Program Committee (in progress):
K. Al-Begain, Univ. of Glamorgan (UK)
A. Al-Dubai, Napier Univ. (UK)
N. Abu-Ghazaleh,  SUNY,Binghamton (USA)
I. Awan, Univ. of Bradford (UK)
A. Bermudez, University of Castilla-La Mancha (Spain)
L. Bononi, University of Bologna (Italy)
A. Boukerche, Univ. of Ottawa (Canada)
C.-C. Shen, Univeristy of Delaware (USA)
J.C. Cano, Technical University of Valencia (Spain)
C. Carrion, University of Castilla-La Mancha (Spain)
M. Colajanni, Univ. of Modena (Italy)
P. Cuenca, University of Castilla-La Mancha (Spain)
F.M. Delicado, University of Castilla-La Mancha (Spain)
E. Fleury, INSA de Lyon (France)
V. Gianuzzi, Univ. of Genova (Italy)
E. Karatza, Aristotle University of Thessaloniki (Greece)
A. Ksentini, University of Cergy-Pontoise (France)
P. Manzoni, Technical University of Valencia (Spain)
G. Min, Univ. of Bradford (UK)
M. Naimi, University of Cergy-Pontoise (France)
S. Nikoletseas, Computer Technology Institute (Greece)=20
M. S. M. Annoni Notare, Barddal Univ. (Brazil)
S. Olariu, Old Dominion Univ. (USA)
T. Olivares, University of Castilla-La Mancha (Spain)
L. Orozco-Barbosa, University of Castilla-La Mancha (Spain)
A. Passarella, Univ. Of Cambridge (UK)
Y. Pan, Georgia State Univ. (USA)
M. Perez-Malumbres, Miguel Hernandez University (Spain)
F. Quiles, University of Castilla-La Mancha (Spain)
P. Ruiz, University of Murcia (Spain)
J.L. Sanchez, University of Castilla-La Mancha (Spain)
M. S. Squillante, IBM T.J. Watson Research Center (USA)=20
A. Shahrabi, Glasgow Caledonian University (UK)
T. Miklos, Technical University of Budapest (Hungary)
S. Yoshida, Kyoto University (Japan)
J. Wu, Florida Atlantic University (USA)
A. Zomaya, Univ. of Sydney (Australia)
=20

Publicity Chair
M. S.-M. Annoni Notare
Barddal University, Florianopolis, SC=20
Brazil
  =20
=20
Paper Submission:
Authors are invited to submit manuscripts reporting original unpublished =
research and recent developments=20
in the topics related to the workshop. The length of the papers should =
not exceed 10 single-spaced pages,=20
formatted using the ACM style (LaTex2e  and MS Word templates can be =
found at <http://www.acm.org/sigs/pubs/proceed/template.html =
<http://www.acm.org/sigs/pubs/proceed/template.html> >).

Papers should be submitted electronically in PDF format (or postscript) =
by sending it as an e-mail attachment to=20
mohamed@dcs.gla.ac.uk <mailto:mohamed@dcs.gla.ac.uk>  or =
blanca@dsi.uclm.es <mailto:blanca@dsi.uclm.es> . All papers will be peer =
reviewed and the comments will=20
be provided to the authors.
=20
Accepted papers will appear in the workshop proceedings and a special =
issue will be planned in a scholarly=20
journal to include selected high-quality papers from the workshop.
=20
Important Dates:
Submission Deadline: 10 June 2006=20
Author Notification: 10 July 2006


------_=_NextPart_001_01C67B47.B4EB126F
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML =
DIR=3Dltr><HEAD></HEAD><BODY>=0A=
<DIV id=3DidOWAReplyText15704 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2><FONT =0A=
face=3D"Times New Roman">[Please accept our apologies if you receive =
multiple =0A=
copies of this =0A=
CFP]<BR>-----------------------------------------------------------------=
-------------------------------------------------</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>CALL FOR PAPERS</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>ACM International Workshop =
on =0A=
Performance Monitoring, Measurement,<BR>and Evaluation of Heterogeneous =
Wireless =0A=
and Wired Networks (PM2HW2N 2006)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html</FONT></A></D=
IV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html"><FONT =0A=
face=3D"Times New Roman"></FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">To be held in conjunction with&nbsp; =
ACM/IEEE =0A=
MSWiM 2006<BR></FONT><A href=3D"http://www.cs.unibo.it/mswim2006/"><FONT =0A=
face=3D"Times New =
Roman">http://www.cs.unibo.it/mswim2006/</FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;<BR>October 2-6, 2006</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Torremolinos, (Malaga), =0A=
Spain<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Scope:<BR>Wireless networks, =
including ad hoc, =0A=
sensor, along with ubiquitous, have witnessed <BR>over the past few =
years their =0A=
fastest growth period and have become increasingly complex. =
<BR>Nonetheless, =0A=
their performance evaluation and analysis have been conducted mostly =
through =0A=
<BR>software simulations. Very recently, some research efforts have been =0A=
directed towards measuring </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">real-world commercial and =
experimental =0A=
networks; constructing models based on real-world data </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and using prototypes to more =
realistically and =0A=
comprehensively evaluate the suggested solutions </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and more specifically validate the =
assumptions =0A=
and the conclusions reached via the simulation =
approach.<BR>&nbsp;<BR>The aim of =0A=
this workshop is to bring together scientists, engineers, and =
practitioners to =0A=
share and exchange </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">their experiences, discuss =
challenges, and =0A=
report state-of-the-art and in-progress research on all aspects =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">of performance measurements, =
monitoring, and =0A=
evaluation of heterogeneous wired and wireless mobile networks, =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">including, wireless ad hoc, sensor, =
and =0A=
ubiquitous networks. Topics of interest&nbsp;include, but are not =
limited =0A=
to:<BR>&nbsp;<BR>- Performance measurement, monitoring, and evaluation =
tools for =0A=
heterogeneous wireless and wired networks<BR>- Performance tools for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Tracing and trace analysis<BR>- =
Discrete =0A=
and continuous models<BR>- Measurement-based performance modelling<BR>- =0A=
Measurement architectures and systems<BR>- QoS monitoring and =
sampling<BR>- =0A=
Measurement-based optimisation of for heterogeneous wireless and wired =0A=
networks<BR>- Novel measurement tools of wireless networks<BR>- =
Performance =0A=
measurements of ad hoc, sensor, and ubiquitous networks<BR>- Performance =0A=
analysis and evaluation of mobile services<BR>- Software tools for =
wireless =0A=
network performance and evaluation<BR>- Automatic performance analysis =
<BR>- =0A=
Performance of wireless and sensor devices<BR>- Mobility modeling and =0A=
management<BR>- Prototype implementation of wireless/mobile networks and =0A=
systems<BR>- Techniques for prototyping wireless networks<BR>- =
Validation =0A=
through measurement and prototyping<BR>- Probabilistic models for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Improvement in network performance =
through =0A=
prototyping<BR>- Performance tools for ad hoc, sensor and ubiquitous =0A=
networks<BR>- Performance and security issues in ad hoc, sensor, and =
ubiquitous =0A=
networks<BR>- Performance and power management control<BR>- Case studies =0A=
demonstrating the role of performance monitoring, measurement, and =0A=
<BR>evaluation in the design of ad hoc, sensor, and ubiquitous =0A=
networks<BR>-Applications of performance monitoring, measurement, and =
evaluation =0A=
as a feedback to improve network QoS<BR>&nbsp;<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Workshop Co-Chairs:<BR>M. =0A=
Ould-Khaoua<BR>University of Glasgow<BR>UK&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">B. Caminero<BR>University of =
Castilla-La =0A=
Mancha<BR>Albacete (Spain)<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Program Committee (in =
progress):<BR>K. =0A=
Al-Begain, Univ. of Glamorgan (UK)<BR>A. Al-Dubai, Napier Univ. =
(UK)<BR>N. =0A=
Abu-Ghazaleh,&nbsp; SUNY,Binghamton (USA)<BR>I. Awan, Univ. of Bradford =0A=
(UK)<BR>A. Bermudez, University of Castilla-La Mancha (Spain)<BR>L. =
Bononi, =0A=
University of Bologna (Italy)<BR>A. Boukerche, Univ. of Ottawa =
(Canada)<BR>C.-C. =0A=
Shen, Univeristy of Delaware (USA)<BR>J.C. Cano, Technical University of =0A=
Valencia (Spain)<BR>C. Carrion, University of Castilla-La Mancha =
(Spain)<BR>M. =0A=
Colajanni, Univ. of Modena (Italy)<BR>P. Cuenca, University of =
Castilla-La =0A=
Mancha (Spain)<BR>F.M. Delicado, University of Castilla-La Mancha =
(Spain)<BR>E. =0A=
Fleury, INSA de Lyon (France)<BR>V. Gianuzzi, Univ. of Genova =
(Italy)<BR>E. =0A=
Karatza, Aristotle University of Thessaloniki (Greece)<BR>A. Ksentini, =0A=
University of Cergy-Pontoise (France)<BR>P. Manzoni, Technical =
University of =0A=
Valencia (Spain)<BR>G. Min, Univ. of Bradford (UK)<BR>M. Naimi, =
University of =0A=
Cergy-Pontoise (France)<BR>S. Nikoletseas, Computer Technology Institute =0A=
(Greece) <BR>M. S. M. Annoni Notare, Barddal Univ. (Brazil)<BR>S. =
Olariu, Old =0A=
Dominion Univ. (USA)<BR>T. Olivares, University of Castilla-La Mancha =0A=
(Spain)<BR>L. Orozco-Barbosa, University of Castilla-La Mancha =
(Spain)<BR>A. =0A=
Passarella, Univ. Of Cambridge (UK)<BR>Y. Pan, Georgia State Univ. =
(USA)<BR>M. =0A=
Perez-Malumbres, Miguel Hernandez University (Spain)<BR>F. Quiles, =
University of =0A=
Castilla-La Mancha (Spain)<BR>P. Ruiz, University of Murcia =
(Spain)<BR>J.L. =0A=
Sanchez, University of Castilla-La Mancha (Spain)<BR>M. S. Squillante, =
IBM T.J. =0A=
Watson Research Center (USA) <BR>A. Shahrabi, Glasgow Caledonian =
University =0A=
(UK)<BR>T. Miklos, Technical University of Budapest (Hungary)<BR>S. =
Yoshida, =0A=
Kyoto University (Japan)<BR>J. Wu, Florida Atlantic University =
(USA)<BR>A. =0A=
Zomaya, Univ. of Sydney (Australia)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><BR><FONT face=3D"Times New Roman">Publicity Chair<BR>M. S.-M. =
Annoni =0A=
Notare<BR>Barddal University, Florianopolis, SC =
<BR>Brazil<BR>&nbsp;&nbsp; =0A=
<BR>&nbsp;<BR>Paper Submission:<BR>Authors are invited to submit =
manuscripts =0A=
reporting original unpublished research and recent developments <BR>in =
the =0A=
topics related to the workshop. The length of the papers should not =
exceed 10 =0A=
single-spaced pages, <BR>formatted using the ACM style (LaTex2e&nbsp; =
and MS =0A=
Word templates can be found at &lt;</FONT><A =0A=
href=3D"http://www.acm.org/sigs/pubs/proceed/template.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.acm.org/sigs/pubs/proceed/template.html</FONT></A><FONT=
 =0A=
face=3D"Times New Roman">&gt;).<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Papers should be submitted =
electronically in =0A=
PDF format (or postscript) by sending it as an e-mail attachment to =0A=
<BR></FONT><A href=3D"mailto:mohamed@dcs.gla.ac.uk"><FONT =0A=
face=3D"Times New Roman">mohamed@dcs.gla.ac.uk</FONT></A><FONT =0A=
face=3D"Times New Roman"> or </FONT><A =
href=3D"mailto:blanca@dsi.uclm.es"><FONT =0A=
face=3D"Times New Roman">blanca@dsi.uclm.es</FONT></A><FONT =0A=
face=3D"Times New Roman">. All papers will be peer reviewed and the =
comments will =0A=
<BR>be provided to the authors.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Accepted papers will appear in the =
workshop =0A=
proceedings and a special issue will be planned in a scholarly =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">journal to include selected =
high-quality =0A=
papers from the workshop.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Important Dates:<BR>Submission =
Deadline: 10 =0A=
June 2006 <BR>Author Notification: 10 July =0A=
2006</FONT><BR></FONT></DIV></DIV></DIV></DIV></DIV></DIV></DIV></BODY></=
HTML>
------_=_NextPart_001_01C67B47.B4EB126F--


--===============1254036152==
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

--===============1254036152==--




From manet-bounces@ietf.org Fri May 19 16:01:03 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FhB94-0006hG-51; Fri, 19 May 2006 16:00:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FhB93-0006hB-15
	for manet@ietf.org; Fri, 19 May 2006 16:00:21 -0400
Received: from students2.iit.edu ([216.47.143.102])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhB90-0000o4-FT
	for manet@ietf.org; Fri, 19 May 2006 16:00:21 -0400
Received: from BigBlue (wireless-197-248.uchicago.edu [128.135.197.248])
	by students2.iit.edu
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTPA
	id <0IZJ00EAT3KBX2@students2.iit.edu> for manet@ietf.org; Fri,
	19 May 2006 15:00:16 -0500 (CDT)
Date: Fri, 19 May 2006 16:00:04 -0400
From: Yu Wang <wangyu1@iit.edu>
To: Tccc@cs.columbia.edu
Message-id: <004101c67b7e$d238c770$f8c58780@BigBlue>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-Priority: 3
X-MSMail-priority: Normal
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 578c2c9d0cb01ffe6e1ca36540edd070
Cc: manet@ietf.org
Subject: [manet] CFP: Third International Conference on Algorithmic Aspects
 in Information and Management (AAIM'07)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1067982579=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1067982579==
Content-type: multipart/alternative;
	boundary="Boundary_(ID_pWk6TrY4sKC3OWdo/3CtQQ)"

This is a multi-part message in MIME format.

--Boundary_(ID_pWk6TrY4sKC3OWdo/3CtQQ)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

[Please accept our apologies if you receive multiple copies of this CFP]

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

                     CALL FOR PAPER

          The Third International Conference on
Algorithmic Aspects in Information and Management (AAIM'07) 
                      6-8 June 2007
                       Portland, OR, USA

            http://www.cs.iit.edu/~aaim07


CONFERENCE THEME
   While the areas of operations research and management science
   are full of algorithmic challenges, the proliferation of
   information has called for the design of smart algorithms and
   data structures for their management.  This conference is
   intended for original algorithmic research on immediate
   applications and/or fundamental problems pertinent to information
   management and management science, broadly construed.

   Typical topics include (but not limited to):

   Approximation Algorithms            Graph Algorithms
   Biological Data Management          Mechanism Design
   Computational Finance               Network Optimization
   Computational Game Theory           Operations Research
   Data Structures                     Online Algorithms
   Discrete Optimization               Scheduling Algorithms
   Geometric Data Management

IMPORTANT DATES
   Submission of Papers:        10 December 2006
   Notification of Acceptance:  14 February 2007
   Final version:                14 March 2007

SUBMISSION INSTRUCTIONS
   AAIM'07 will only accept electronic on-line submissions.  Detailed
   instructions can be found in the conference web page.  Accepted papers
   will be published by Springer-Verlag in the Lecture Notes in Computer
   Science (www.springeronline.com/lncs) series (pending approval).  
   Simultaneous submissions to other conferences with published proceedings 
   are not allowed.

PROGRAM CO-CHAIRs:
   Ming-Yao Kao, Northwestern University, USA
   Xiang-Yang Li, Illinois Institute of Technology, USA

LOCAL ARRANGEMENT CHAIR:
   Wen-Zhan Song, Washington State University, USA

PUBLICITY CHAIR:
   Yu Wang, Univ. of North Carolina at Charlotte, USA
   Wen-Zhan Song, Washington State University, USA

PROGRAM COMMITTEE:
   Hee-Kap Ahn, Korean Advanced Inst. of Sci. & Tech., Korea
   Takao Asano, Chuo University, Japan
   Amotz Bar-Noy, City Univ. of New York, USA
   Hans Bodlaender, University Utrecht, Netherlands
   Peter Brucker, University Osnabrueck, Germany
   Leizhen Cai, Chinese University of Hong Kong, China
   Gruia Calinescu, Illinois Institute of Technology, USA
   Jianer Chen, Texas A&M University, USA
   Siu-Wing Cheng, Hong Kong Univ. of Sci. & Tech., China
   Marek Chrobak, Univ. of California at Riverside, USA
   Yang Dai, University of Illinois at Chicago, USA
   Bhaskar DasGupta, University at Illinois at Chicago, USA
   Rudolf Fleischer, Fudan University, China
   Jie Gao, University of SUNY Stony Brook, USA
   Joachim Gudmundsson, National ICT, Australia
   Gregory Gutin, Royal Holloway, U. of London, U. of Haifa, UK
   Wen-Lian Hsu, Academia Sinica, Taiwan
   Giuseppe F. Italiano, Univ. of Roma "Tor Vergata", Italy
   Ming-Yang Kao, Northwestern University, USA 
   Sanjiv Kapoor, Illinois Institute of Technology, USA
   Tak-Wah Lam, University of Hong Kong, China
   Jan van Leeuwen, University Utrecht, Netherlands 
   Erran Li Li, Bell Labs, USA
   Jing Li, Case Western Reserve University, USA
   Xiang-Yang Li, Illinois Institute of Technology, USA
   Peter Bro Miltersen, University of Aarhus, Denmark
   Pat Morin, Carleton University, Canada
   Seffi Naor, Technion and Microsoft Research, Israel
   Chung Keung Poon, City Univ. of Hong Kong, China
   Kirk Pruhs, University of Pittsburgh, USA
   Vijaya Ramachandran, Univ. of Texas at Austin, USA
   Rajeev Raman, Leicester University, UK
   Paul Spirakis, University of Patras & CTI, Greece
   Zheng Sun, Google, USA
   Wing Kin Sung, National Univ. of Singapore, Singapore
   Hisao Tamaki, Meiji University, Japan
   Shang-Hua Teng, Boston Univiersty, USA
   Peng-Jun Wan, Illinois Institute of Technology, USA
   Jie Wang, University of Massachusetts Lowell, USA
   Lusheng Wang, City Univ. of Hong Kong, China
   Yu Wang, University of North Carolina at Charlotte, USA 
   JinHui Xu, University of SUNY Buffalo, USA
   Yinfeng Xu, Xi'an Jiaotong University, China
   Binhai Zhu, Montana State University, USA

STEERING COMMITTEE:
   Tetsuo Asano, JAIST, Austria
   Franz Aurenhammer, TU Graz, Austria
   Bernard Chazelle, Princeton University, USA
   Danny Z. Chen, University of North Dame, USA
   Siu-Wing Cheng, Hong Kong Univ. of Sci. & Tech., China
   Otfried Cheong, Korean Advanced Inst. of Sci. & Tech., Korea
   Rudolf Fleischer, Fudan University, China
   Wen-Lian Hsu, Academia Sinica, Taiwan
   Tao Jiang, UC-Riverside, USA
   Naoki Katoh, Kyoto, Japan
   Ming-Yang Kao, Northwestern University, USA
   Xiang-Yang Li, Illinois Institute of Technology, USA
   C.K. Poon, City Univ. of Hong Kong, China
   Rajeev Raman, Leicester University, Great Britain
   Peter Widmayer, ETH Zurich, Switzerland
   Yinfeng Xu, Xi'an Jiaotong University, China
   Binhai Zhu, Montana State University, USA

--Boundary_(ID_pWk6TrY4sKC3OWdo/3CtQQ)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1226" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>[Please accept our apologies if you receive multiple copies of 
this CFP]</FONT><BR></DIV>
<DIV><FONT face=Arial 
size=2>-----------------------------------------------------------------------</FONT></DIV><FONT 
face=Arial size=2>
<DIV><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
CALL FOR PAPER</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The Third 
International Conference on<BR>Algorithmic Aspects in Information and Management 
(AAIM'07) 
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
6-8 June 
2007<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Portland, OR, USA</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <A 
href="http://www.cs.iit.edu/~aaim07">http://www.cs.iit.edu/~aaim07</A></DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>CONFERENCE THEME<BR>&nbsp;&nbsp; While the areas of operations research 
and management science<BR>&nbsp;&nbsp; are full of algorithmic challenges, the 
proliferation of<BR>&nbsp;&nbsp; information has called for the design of smart 
algorithms and<BR>&nbsp;&nbsp; data structures for their management.&nbsp; This 
conference is<BR>&nbsp;&nbsp; intended for original algorithmic research on 
immediate<BR>&nbsp;&nbsp; applications and/or fundamental problems pertinent to 
information<BR>&nbsp;&nbsp; management and management science, broadly 
construed.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; Typical topics include (but not limited to):</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;&nbsp; Approximation 
Algorithms&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Graph Algorithms<BR>&nbsp;&nbsp; Biological Data 
Management&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mechanism 
Design<BR>&nbsp;&nbsp; Computational 
Finance&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Network Optimization<BR>&nbsp;&nbsp; Computational Game 
Theory&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Operations 
Research<BR>&nbsp;&nbsp; Data 
Structures&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Online Algorithms<BR>&nbsp;&nbsp; Discrete 
Optimization&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Scheduling Algorithms<BR>&nbsp;&nbsp; Geometric Data Management</DIV>
<DIV>&nbsp;</DIV>
<DIV>IMPORTANT DATES<BR>&nbsp;&nbsp; Submission of 
Papers:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10 December 
2006<BR>&nbsp;&nbsp; Notification of Acceptance:&nbsp; 14 February 
2007<BR>&nbsp;&nbsp; Final 
version:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
14 March 2007</DIV>
<DIV>&nbsp;</DIV>
<DIV>SUBMISSION INSTRUCTIONS<BR>&nbsp;&nbsp; AAIM'07 will only accept electronic 
on-line submissions.&nbsp; Detailed<BR>&nbsp;&nbsp; instructions can be found in 
the conference web page.&nbsp; Accepted papers<BR>&nbsp;&nbsp; will be published 
by Springer-Verlag in the Lecture Notes in Computer<BR>&nbsp;&nbsp; Science (<A 
href="http://www.springeronline.com/lncs">www.springeronline.com/lncs</A>) 
series (pending approval).&nbsp; <BR>&nbsp;&nbsp; Simultaneous submissions to 
other conferences with published proceedings <BR>&nbsp;&nbsp; are not 
allowed.</DIV>
<DIV>&nbsp;</DIV>
<DIV>PROGRAM CO-CHAIRs:<BR>&nbsp;&nbsp; Ming-Yao Kao, Northwestern University, 
USA<BR>&nbsp;&nbsp; Xiang-Yang Li, Illinois Institute of Technology, USA</DIV>
<DIV>&nbsp;</DIV>
<DIV>LOCAL ARRANGEMENT CHAIR:<BR>&nbsp;&nbsp; Wen-Zhan Song, Washington State 
University, USA</DIV>
<DIV>&nbsp;</DIV>
<DIV>PUBLICITY CHAIR:<BR>&nbsp;&nbsp; Yu Wang, Univ. of North Carolina at 
Charlotte, USA<BR>&nbsp;&nbsp; Wen-Zhan Song, Washington State University, 
USA</DIV>
<DIV>&nbsp;</DIV>
<DIV>PROGRAM COMMITTEE:<BR>&nbsp;&nbsp; Hee-Kap Ahn, Korean Advanced Inst. of 
Sci. &amp; Tech., Korea<BR>&nbsp;&nbsp; Takao Asano, Chuo University, 
Japan<BR>&nbsp;&nbsp; Amotz Bar-Noy, City Univ. of New York, USA<BR>&nbsp;&nbsp; 
Hans Bodlaender, University Utrecht, Netherlands<BR>&nbsp;&nbsp; Peter Brucker, 
University Osnabrueck, Germany<BR>&nbsp;&nbsp; Leizhen Cai, Chinese University 
of Hong Kong, China<BR>&nbsp;&nbsp; Gruia Calinescu, Illinois Institute of 
Technology, USA<BR>&nbsp;&nbsp; Jianer Chen, Texas A&amp;M University, 
USA<BR>&nbsp;&nbsp; Siu-Wing Cheng, Hong Kong Univ. of Sci. &amp; Tech., 
China<BR>&nbsp;&nbsp; Marek Chrobak, Univ. of California at Riverside, 
USA<BR>&nbsp;&nbsp; Yang Dai, University of Illinois at Chicago, 
USA<BR>&nbsp;&nbsp; Bhaskar DasGupta, University at Illinois at Chicago, 
USA<BR>&nbsp;&nbsp; Rudolf Fleischer, Fudan University, China<BR>&nbsp;&nbsp; 
Jie Gao, University of SUNY Stony Brook, USA<BR>&nbsp;&nbsp; Joachim 
Gudmundsson, National ICT, Australia<BR>&nbsp;&nbsp; Gregory Gutin, Royal 
Holloway, U. of London, U. of Haifa, UK<BR>&nbsp;&nbsp; Wen-Lian Hsu, Academia 
Sinica, Taiwan<BR>&nbsp;&nbsp; Giuseppe F. Italiano, Univ. of Roma "Tor 
Vergata", Italy<BR>&nbsp;&nbsp; Ming-Yang Kao, Northwestern University, USA 
<BR>&nbsp;&nbsp; Sanjiv Kapoor, Illinois Institute of Technology, 
USA<BR>&nbsp;&nbsp; Tak-Wah Lam, University of Hong Kong, China<BR>&nbsp;&nbsp; 
Jan van Leeuwen, University Utrecht, Netherlands <BR>&nbsp;&nbsp; Erran Li Li, 
Bell Labs, USA<BR>&nbsp;&nbsp; Jing Li, Case Western Reserve University, 
USA<BR>&nbsp;&nbsp; Xiang-Yang Li, Illinois Institute of Technology, 
USA<BR>&nbsp;&nbsp; Peter Bro Miltersen, University of Aarhus, 
Denmark<BR>&nbsp;&nbsp; Pat Morin, Carleton University, Canada<BR>&nbsp;&nbsp; 
Seffi Naor, Technion and Microsoft Research, Israel<BR>&nbsp;&nbsp; Chung Keung 
Poon, City Univ. of Hong Kong, China<BR>&nbsp;&nbsp; Kirk Pruhs, University of 
Pittsburgh, USA<BR>&nbsp;&nbsp; Vijaya Ramachandran, Univ. of Texas at Austin, 
USA<BR>&nbsp;&nbsp; Rajeev Raman, Leicester University, UK<BR>&nbsp;&nbsp; Paul 
Spirakis, University of Patras &amp; CTI, Greece<BR>&nbsp;&nbsp; Zheng Sun, 
Google, USA<BR>&nbsp;&nbsp; Wing Kin Sung, National Univ. of Singapore, 
Singapore<BR>&nbsp;&nbsp; Hisao Tamaki, Meiji University, Japan<BR>&nbsp;&nbsp; 
Shang-Hua Teng, Boston Univiersty, USA<BR>&nbsp;&nbsp; Peng-Jun Wan, Illinois 
Institute of Technology, USA<BR>&nbsp;&nbsp; Jie Wang, University of 
Massachusetts Lowell, USA<BR>&nbsp;&nbsp; Lusheng Wang, City Univ. of Hong Kong, 
China<BR>&nbsp;&nbsp; Yu Wang, University of North Carolina at Charlotte, USA 
<BR>&nbsp;&nbsp; JinHui Xu, University of SUNY Buffalo, USA<BR>&nbsp;&nbsp; 
Yinfeng Xu, Xi'an Jiaotong University, China<BR>&nbsp;&nbsp; Binhai Zhu, Montana 
State University, USA</DIV>
<DIV>&nbsp;</DIV>
<DIV>STEERING COMMITTEE:<BR>&nbsp;&nbsp; Tetsuo Asano, JAIST, 
Austria<BR>&nbsp;&nbsp; Franz Aurenhammer, TU Graz, Austria<BR>&nbsp;&nbsp; 
Bernard Chazelle, Princeton University, USA<BR>&nbsp;&nbsp; Danny Z. Chen, 
University of North Dame, USA<BR>&nbsp;&nbsp; Siu-Wing Cheng, Hong Kong Univ. of 
Sci. &amp; Tech., China<BR>&nbsp;&nbsp; Otfried Cheong, Korean Advanced Inst. of 
Sci. &amp; Tech., Korea<BR>&nbsp;&nbsp; Rudolf Fleischer, Fudan University, 
China<BR>&nbsp;&nbsp; Wen-Lian Hsu, Academia Sinica, Taiwan<BR>&nbsp;&nbsp; Tao 
Jiang, UC-Riverside, USA<BR>&nbsp;&nbsp; Naoki Katoh, Kyoto, 
Japan<BR>&nbsp;&nbsp; Ming-Yang Kao, Northwestern University, 
USA<BR>&nbsp;&nbsp; Xiang-Yang Li, Illinois Institute of Technology, 
USA<BR>&nbsp;&nbsp; C.K. Poon, City Univ. of Hong Kong, China<BR>&nbsp;&nbsp; 
Rajeev Raman, Leicester University, Great Britain<BR>&nbsp;&nbsp; Peter 
Widmayer, ETH Zurich, Switzerland<BR>&nbsp;&nbsp; Yinfeng Xu, Xi'an Jiaotong 
University, China<BR>&nbsp;&nbsp; Binhai Zhu, Montana State University, 
USA<BR></FONT></DIV></BODY></HTML>

--Boundary_(ID_pWk6TrY4sKC3OWdo/3CtQQ)--


--===============1067982579==
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

--===============1067982579==--




From manet-bounces@ietf.org Sun May 21 10:14:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fhofj-0000pQ-7R; Sun, 21 May 2006 10:12:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fhofh-0000pL-Fa
	for manet@ietf.org; Sun, 21 May 2006 10:12:41 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fhofb-00071I-I8
	for manet@ietf.org; Sun, 21 May 2006 10:12:41 -0400
Received: from ex1.ad.dcs.gla.ac.uk ([130.209.249.157]:52118)
	by mr1.dcs.gla.ac.uk with esmtp (Exim 4.42)
	id 1FhofY-0005gw-DZ; Sun, 21 May 2006 15:12:32 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 21 May 2006 15:12:31 +0100
Message-ID: <BED9D15F73EDDE48BF480604236A4560116FF4@ex1.ad.dcs.gla.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFPS-- 2nd ACM International Workhop on Wireless Multimedia
	Networking and Performance Modeling (WMuNeP '06)
Thread-Index: AcZ8Oxr93usqozwvRW2rB6G7zRwLAQApL1fe
References: <BED9D15F73EDDE48BF480604236A4560116EC3@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116ED2@ex1.ad.dcs.gla.ac.uk>
	<446F5FA3.6010604@site.uottawa.ca>
From: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>
To: <tccc@cs.columbia.edu>, <discuss@ieeetcsc.org>, <manet@ietf.org>,
	<itc@comsoc.org>, <multicomm@comsoc.org>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: df1883a27a831c1ea5e8cfe5eb3ad38e
Cc: 
Subject: [manet] CFPS-- 2nd ACM International Workhop on Wireless Multimedia
	Networking and Performance Modeling (WMuNeP '06)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0784187986=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0784187986==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67CE0.99AF8001"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67CE0.99AF8001
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

CALL FOR PAPERS
--------------------------------------------------------------------
=20
                           2nd ACM WMuNeP 2006
   Second ACM International Workshop on Wireless Multimedia Networking =
and
                    Performance Modeling (WMuNeP '06)
                    http://www.dc.ufscar.br/wmunep06/

               To be held jointly with the 9th ACM MSWiM 2006
                           October 2-6th, 2006
                        Torremolinos, Malaga, Spain
                      http://www.cs.unibo.it/mswim2006

*ACM Pending Approval

--------------------------------------------------------------------
Due date: June 10th, 2006
---------------------------------------------------------------------
Selected papers will be published on a special issue of ACM/Springer =
Multimedia Systems
---------------------------------------------------------------------


The Second ACM International Workshop on Wireless Multimedia Networking =
and
Performance Modeling (WMuNeP '06) will be a one-day workshop, held in
conjunction with the 9th Annual ACM Symposium on Modeling, Analysis and
Simulation of Wireless and Mobile Systems (MSWiM=C2=B406). The demand =
for
wireless multimedia communications thrives in today's consumer and
corporate market. The need to evolve multimedia applications and =
services,
and their associated protocols for emerging networks is at a critical
point given the proliferation and integration of wireless systems to
intelligent and broadband networks, mobility of people, data/voice
convergence and the integration of computing and communication in mobile
devices.

This workshop is devoted to cover different aspects of wireless =
multimedia
networking and performance modeling for WLANs, WPANs, WMANs, WWANs, =
MANETs
and sensor networks such as wireless video and wireless streaming,
systematic design methodologies, algorithms, synchronization, analysis =
and
performance modeling. The workshop will provide a forum for researchers
and practitioners to present their contributions related to the above
high-level aspects.

Topics of interest include (but are not limited to):

- Wireless multimedia network management
- Wireless multimedia traffic modeling
- Middleware and reflective systems support for wireless multimedia
- Proxy-based systems for video transcoding and content distribution
- Performance modeling, monitoring and evaluation of wireless multimedia
  networks and systems
- Multipoint, multicast wireless multimedia services
- Deployment of wireless multimedia applications, services and networks
- Protocols for wireless multimedia networks
- QoS in wireless multimedia networks
- Integration of wireless multimedia networks to broadband networks
- End-to-end IP multimedia wireless communications
- Coding and transmission for wireless multimedia networks
- Distributed wireless multimedia services
- Content-based wireless multimedia information retrieval tools
- Video, streaming, real-time wireless multimedia communications and
   applications
- Security in wireless multimedia networks
- Wireless multimedia right protection and watermarking
- Pricing mechanisms for wireless multimedia networks
- E-Commerce and related applications for wireless multimedia networks
- Multimedia evaluation and processing for wireless networks
- Cross layer design for wireless multimedia networks
- Analytical modeling of wireless multimedia networks
- Software tools for system performance and evaluation of wireless
  multimedia networks
- Performance comparison of wireless multimedia networks
- Case studies showing the role of evaluation in the design of systems

-------------------------------------------------------------------------=
--
Important Dates:
Submission deadline:         June 10th, 2006
Notification of acceptance:  July 10th, 2006
Camera ready papers:  TBA
-------------------------------------------------------------------------=
--

Paper Submission Guidelines:
Authors are invited to submit research contributions representing =
original,
previously unpublished work. Submitted papers will be carefully =
evaluated
based on originality, significance, technical soundness, and clarity of
exposition.

Accepted papers will appear on the workshop proceedings that will be
published by ACM press. At least one of the authors of accepted papers
must attend the conference to present his/her paper.

Paper length should be no more than 10 pages, double column, ACM style
including tables and figures. A template for ACM SIG Proceedings style
(LaTeX2e and MS Word) can be found here. Only Postscript and PDF formats
are accepted. Papers must be submitted electronically via the JEMS =
system
(Brazilian EDAS).

WMuNeP  2006 electronic submission is now active on the JEMS system
(Brazilian EDAS) at https://submissoes.sbc.org.br/wmunep2006. Once you =
are
a registered JEMS user, this link will address you directly to the =
WMuNeP
2006 Paper Submission page. Important - For any question or problem
related to WMuNeP 2006, please contact wmunep2006@dc.ufscar.br
-------------------------------------------------------------------------=
--
-------------------------------------------------------------------------=
--

Workshop Co-Chairs:

Prof. Regina B. Araujo
Federal University of S?o Carlos
S?o Carlos, SP, Brazil
regina@dc.ufscar.br

Prof. Hussein M Alnuweiri
University of British Columbia
Vancouver, Canada
hussein@ece.ubc.ca

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

Program Committee:

Hussein Alnuweiri, University of British Columbia, Canada
Rossana Andrade, Federal University of Ceara, Brazil
Regina Araujo, Federal University of Sao Carlos, Brazil
Nazim Agoulmine, University of Evry, France
Azzedine Boukerche, University of Ottawa, Canada
Raffaele Bruno, CNR, Italy
Hsiao-Hwa Chen, National Sun Yat-Sen University, Taiwan
Zihua Guo, Lenovo Corporate R&D, China
Anna Hac, University of Hawaii, USA
Hai Jiang, University of Waterloo, Canada
Victor Leung, University of British Columbia, Canada
Wei Li, University of Toledo, USA
Jiangchuan Liu, Simon Fraser University, Canada
Pascal Lorenz, University of Haute Alsace, France
Antonio A. F. Loureiro, Federal University of Minas Gerais, Brazil
Andreas Meissner,  Fraunhofer Institute, Germany
Jelena Misic, University of Manitoba, Canada
Edmundo Monteiro, University of Coimbra, Portugal
Jander Moreira, Federal University of Sao Carlos, Brazil
Mirela S. M. Notare, Barddal University, Brazil
Stephen Olariu, Old Dominion University, USA
Jianping Pan, NTT MCL, USA
Bjorn Pehrson, Royal Institute of Technology, Sweden
Yu-Chee Tseng, National Chiao Tung Univ., Taiwan
Murat Uysal, University of Waterloo, Canada
Qi Xue,  Qualcomm Inc., USA
Yang Yang, University College London, UK
Weihua Zhuang, University of Waterloo, Canada

------_=_NextPart_001_01C67CE0.99AF8001
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">=0A=
<TITLE>Re: Help</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV dir=3Dltr><FONT size=3D2>CALL FOR PAPERS</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT =0A=
size=3D2>----------------------------------------------------------------=
----</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT =0A=
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =0A=
2nd ACM WMuNeP 2006<BR>&nbsp;&nbsp; Second ACM International Workshop on =0A=
Wireless Multimedia Networking =0A=
and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Performance Modeling (WMuNeP =0A=
'06)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
<A =0A=
href=3D"http://www.dc.ufscar.br/wmunep06/">http://www.dc.ufscar.br/wmunep=
06/</A><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
To be held jointly with the 9th ACM MSWiM =0A=
2006<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; =0A=
October 2-6th, =0A=
2006<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 =0A=
Torremolinos, Malaga, =0A=
Spain<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
<A =0A=
href=3D"http://www.cs.unibo.it/mswim2006">http://www.cs.unibo.it/mswim200=
6</A><BR><BR>*ACM =0A=
Pending =0A=
Approval<BR><BR>---------------------------------------------------------=
-----------<BR>Due =0A=
date: June 10th, =0A=
2006<BR>-----------------------------------------------------------------=
----<BR>Selected =0A=
papers will be published on a special issue of ACM/Springer Multimedia =0A=
Systems<BR>--------------------------------------------------------------=
-------<BR><BR><BR>The =0A=
Second ACM International Workshop on Wireless Multimedia Networking =0A=
and<BR>Performance Modeling (WMuNeP '06) will be a one-day workshop, =
held =0A=
in<BR>conjunction with the 9th Annual ACM Symposium on Modeling, =
Analysis =0A=
and<BR>Simulation of Wireless and Mobile Systems (MSWiM=C2=B406). The =
demand =0A=
for<BR>wireless multimedia communications thrives in today's consumer =0A=
and<BR>corporate market. The need to evolve multimedia applications and =0A=
services,<BR>and their associated protocols for emerging networks is at =
a =0A=
critical<BR>point given the proliferation and integration of wireless =
systems =0A=
to<BR>intelligent and broadband networks, mobility of people, =0A=
data/voice<BR>convergence and the integration of computing and =
communication in =0A=
mobile<BR>devices.<BR><BR>This workshop is devoted to cover different =
aspects of =0A=
wireless multimedia<BR>networking and performance modeling for WLANs, =
WPANs, =0A=
WMANs, WWANs, MANETs<BR>and sensor networks such as wireless video and =
wireless =0A=
streaming,<BR>systematic design methodologies, algorithms, =
synchronization, =0A=
analysis and<BR>performance modeling. The workshop will provide a forum =
for =0A=
researchers<BR>and practitioners to present their contributions related =
to the =0A=
above<BR>high-level aspects.<BR><BR>Topics of interest include (but are =
not =0A=
limited to):<BR><BR>- Wireless multimedia network management<BR>- =
Wireless =0A=
multimedia traffic modeling<BR>- Middleware and reflective systems =
support for =0A=
wireless multimedia<BR>- Proxy-based systems for video transcoding and =
content =0A=
distribution<BR>- Performance modeling, monitoring and evaluation of =
wireless =0A=
multimedia<BR>&nbsp; networks and systems<BR>- Multipoint, multicast =
wireless =0A=
multimedia services<BR>- Deployment of wireless multimedia applications, =0A=
services and networks<BR>- Protocols for wireless multimedia =
networks<BR>- QoS =0A=
in wireless multimedia networks<BR>- Integration of wireless multimedia =
networks =0A=
to broadband networks<BR>- End-to-end IP multimedia wireless =
communications<BR>- =0A=
Coding and transmission for wireless multimedia networks<BR>- =
Distributed =0A=
wireless multimedia services<BR>- Content-based wireless multimedia =
information =0A=
retrieval tools<BR>- Video, streaming, real-time wireless multimedia =0A=
communications and<BR>&nbsp;&nbsp; applications<BR>- Security in =
wireless =0A=
multimedia networks<BR>- Wireless multimedia right protection and =0A=
watermarking<BR>- Pricing mechanisms for wireless multimedia =
networks<BR>- =0A=
E-Commerce and related applications for wireless multimedia =
networks<BR>- =0A=
Multimedia evaluation and processing for wireless networks<BR>- Cross =
layer =0A=
design for wireless multimedia networks<BR>- Analytical modeling of =
wireless =0A=
multimedia networks<BR>- Software tools for system performance and =
evaluation of =0A=
wireless<BR>&nbsp; multimedia networks<BR>- Performance comparison of =
wireless =0A=
multimedia networks<BR>- Case studies showing the role of evaluation in =
the =0A=
design of =0A=
systems<BR><BR>----------------------------------------------------------=
-----------------<BR>Important =0A=
Dates:<BR>Submission =
deadline:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
June 10th, 2006<BR>Notification of acceptance:&nbsp; July 10th, =
2006<BR>Camera =0A=
ready papers:&nbsp; =0A=
TBA<BR>------------------------------------------------------------------=
---------<BR><BR>Paper =0A=
Submission Guidelines:<BR>Authors are invited to submit research =
contributions =0A=
representing original,<BR>previously unpublished work. Submitted papers =
will be =0A=
carefully evaluated<BR>based on originality, significance, technical =
soundness, =0A=
and clarity of<BR>exposition.<BR><BR>Accepted papers will appear on the =
workshop =0A=
proceedings that will be<BR>published by ACM press. At least one of the =
authors =0A=
of accepted papers<BR>must attend the conference to present his/her =0A=
paper.<BR><BR>Paper length should be no more than 10 pages, double =
column, ACM =0A=
style<BR>including tables and figures. A template for ACM SIG =
Proceedings =0A=
style<BR>(LaTeX2e and MS Word) can be found here. Only Postscript and =
PDF =0A=
formats<BR>are accepted. Papers must be submitted electronically via the =
JEMS =0A=
system<BR>(Brazilian EDAS).<BR><BR>WMuNeP&nbsp; 2006 electronic =
submission is =0A=
now active on the JEMS system<BR>(Brazilian EDAS) at <A =0A=
href=3D"https://submissoes.sbc.org.br/wmunep2006">https://submissoes.sbc.=
org.br/wmunep2006</A>. =0A=
Once you are<BR>a registered JEMS user, this link will address you =
directly to =0A=
the WMuNeP<BR>2006 Paper Submission page. Important - For any question =
or =0A=
problem<BR>related to WMuNeP 2006, please contact =0A=
wmunep2006@dc.ufscar.br<BR>----------------------------------------------=
-----------------------------<BR>----------------------------------------=
-----------------------------------<BR><BR>Workshop =0A=
Co-Chairs:<BR><BR>Prof. Regina B. Araujo<BR>Federal University of S?o =0A=
Carlos<BR>S?o Carlos, SP, Brazil<BR>regina@dc.ufscar.br<BR><BR>Prof. =
Hussein M =0A=
Alnuweiri<BR>University of British Columbia<BR>Vancouver, =0A=
Canada<BR>hussein@ece.ubc.ca<BR><BR>-------------------------------------=
--------------------------------------<BR><BR>Program =0A=
Committee:<BR><BR>Hussein Alnuweiri, University of British Columbia, =0A=
Canada<BR>Rossana Andrade, Federal University of Ceara, Brazil<BR>Regina =
Araujo, =0A=
Federal University of Sao Carlos, Brazil<BR>Nazim Agoulmine, University =
of Evry, =0A=
France<BR>Azzedine Boukerche, University of Ottawa, Canada<BR>Raffaele =
Bruno, =0A=
CNR, Italy<BR>Hsiao-Hwa Chen, National Sun Yat-Sen University, =
Taiwan<BR>Zihua =0A=
Guo, Lenovo Corporate R&amp;D, China<BR>Anna Hac, University of Hawaii, =0A=
USA<BR>Hai Jiang, University of Waterloo, Canada<BR>Victor Leung, =
University of =0A=
British Columbia, Canada<BR>Wei Li, University of Toledo, =
USA<BR>Jiangchuan Liu, =0A=
Simon Fraser University, Canada<BR>Pascal Lorenz, University of Haute =
Alsace, =0A=
France<BR>Antonio A. F. Loureiro, Federal University of Minas Gerais, =0A=
Brazil<BR>Andreas Meissner,&nbsp; Fraunhofer Institute, =
Germany<BR>Jelena Misic, =0A=
University of Manitoba, Canada<BR>Edmundo Monteiro, University of =
Coimbra, =0A=
Portugal<BR>Jander Moreira, Federal University of Sao Carlos, =
Brazil<BR>Mirela =0A=
S. M. Notare, Barddal University, Brazil<BR>Stephen Olariu, Old Dominion =0A=
University, USA<BR>Jianping Pan, NTT MCL, USA<BR>Bjorn Pehrson, Royal =
Institute =0A=
of Technology, Sweden<BR>Yu-Chee Tseng, National Chiao Tung Univ., =0A=
Taiwan<BR>Murat Uysal, University of Waterloo, Canada<BR>Qi Xue,&nbsp; =
Qualcomm =0A=
Inc., USA<BR>Yang Yang, University College London, UK<BR>Weihua Zhuang, =0A=
University of Waterloo, Canada</DIV></FONT>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C67CE0.99AF8001--


--===============0784187986==
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

--===============0784187986==--




From manet-bounces@ietf.org Sun May 21 10:32:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FhoyL-0007SK-0h; Sun, 21 May 2006 10:31:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FhoyJ-0007SF-Bw
	for manet@ietf.org; Sun, 21 May 2006 10:31:55 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhoyG-0007kk-E7
	for manet@ietf.org; Sun, 21 May 2006 10:31:55 -0400
Received: from ex1.ad.dcs.gla.ac.uk ([130.209.249.157]:52526)
	by mr1.dcs.gla.ac.uk with esmtp (Exim 4.42) id 1FhoyG-0006gM-20
	for manet@ietf.org; Sun, 21 May 2006 15:31:52 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sun, 21 May 2006 15:30:56 +0100
Message-ID: <BED9D15F73EDDE48BF480604236A4560116FFC@ex1.ad.dcs.gla.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFPS-- 2nd ACM International Workhop on Wireless Multimedia
	Networking and Performance Modeling (WMuNeP '06)
Thread-Index: AcZ8Oxr93usqozwvRW2rB6G7zRwLAQApL1feAAAyF/sAAKLX1w==
References: <BED9D15F73EDDE48BF480604236A4560116EC3@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116ED2@ex1.ad.dcs.gla.ac.uk>
	<446F5FA3.6010604@site.uottawa.ca>
	<BED9D15F73EDDE48BF480604236A4560116FF4@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116FF5@ex1.ad.dcs.gla.ac.uk>
From: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>
To: <manet@ietf.org>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: da41e01217ab11ad82db577473e913ae
Subject: [manet] CFPS-- 2nd ACM International Workhop on Wireless Multimedia
	Networking and Performance Modeling (WMuNeP '06)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1667792800=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1667792800==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C67CE3.4CFBF2AF"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C67CE3.4CFBF2AF
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

CALL FOR PAPERS
--------------------------------------------------------------------
=20
                           2nd ACM WMuNeP 2006
   Second ACM International Workshop on Wireless Multimedia Networking =
and
                    Performance Modeling (WMuNeP '06)
                    http://www.dc.ufscar.br/wmunep06/

               To be held jointly with the 9th ACM MSWiM 2006
                           October 2-6th, 2006
                        Torremolinos, Malaga, Spain
                      http://www.cs.unibo.it/mswim2006

*ACM Pending Approval

--------------------------------------------------------------------
Due date: June 10th, 2006
---------------------------------------------------------------------
Selected papers will be published on a special issue of ACM/Springer =
Multimedia Systems
---------------------------------------------------------------------


The Second ACM International Workshop on Wireless Multimedia Networking =
and
Performance Modeling (WMuNeP '06) will be a one-day workshop, held in
conjunction with the 9th Annual ACM Symposium on Modeling, Analysis and
Simulation of Wireless and Mobile Systems (MSWiM=C2=B406). The demand =
for
wireless multimedia communications thrives in today's consumer and
corporate market. The need to evolve multimedia applications and =
services,
and their associated protocols for emerging networks is at a critical
point given the proliferation and integration of wireless systems to
intelligent and broadband networks, mobility of people, data/voice
convergence and the integration of computing and communication in mobile
devices.

This workshop is devoted to cover different aspects of wireless =
multimedia
networking and performance modeling for WLANs, WPANs, WMANs, WWANs, =
MANETs
and sensor networks such as wireless video and wireless streaming,
systematic design methodologies, algorithms, synchronization, analysis =
and
performance modeling. The workshop will provide a forum for researchers
and practitioners to present their contributions related to the above
high-level aspects.

Topics of interest include (but are not limited to):

- Wireless multimedia network management
- Wireless multimedia traffic modeling
- Middleware and reflective systems support for wireless multimedia
- Proxy-based systems for video transcoding and content distribution
- Performance modeling, monitoring and evaluation of wireless multimedia
  networks and systems
- Multipoint, multicast wireless multimedia services
- Deployment of wireless multimedia applications, services and networks
- Protocols for wireless multimedia networks
- QoS in wireless multimedia networks
- Integration of wireless multimedia networks to broadband networks
- End-to-end IP multimedia wireless communications
- Coding and transmission for wireless multimedia networks
- Distributed wireless multimedia services
- Content-based wireless multimedia information retrieval tools
- Video, streaming, real-time wireless multimedia communications and
   applications
- Security in wireless multimedia networks
- Wireless multimedia right protection and watermarking
- Pricing mechanisms for wireless multimedia networks
- E-Commerce and related applications for wireless multimedia networks
- Multimedia evaluation and processing for wireless networks
- Cross layer design for wireless multimedia networks
- Analytical modeling of wireless multimedia networks
- Software tools for system performance and evaluation of wireless
  multimedia networks
- Performance comparison of wireless multimedia networks
- Case studies showing the role of evaluation in the design of systems

-------------------------------------------------------------------------=
--
Important Dates:
Submission deadline:         June 10th, 2006
Notification of acceptance:  July 10th, 2006
Camera ready papers:  TBA
-------------------------------------------------------------------------=
--

Paper Submission Guidelines:
Authors are invited to submit research contributions representing =
original,
previously unpublished work. Submitted papers will be carefully =
evaluated
based on originality, significance, technical soundness, and clarity of
exposition.

Accepted papers will appear on the workshop proceedings that will be
published by ACM press. At least one of the authors of accepted papers
must attend the conference to present his/her paper.

Paper length should be no more than 10 pages, double column, ACM style
including tables and figures. A template for ACM SIG Proceedings style
(LaTeX2e and MS Word) can be found here. Only Postscript and PDF formats
are accepted. Papers must be submitted electronically via the JEMS =
system
(Brazilian EDAS).

WMuNeP  2006 electronic submission is now active on the JEMS system
(Brazilian EDAS) at https://submissoes.sbc.org.br/wmunep2006. Once you =
are
a registered JEMS user, this link will address you directly to the =
WMuNeP
2006 Paper Submission page. Important - For any question or problem
related to WMuNeP 2006, please contact wmunep2006@dc.ufscar.br
-------------------------------------------------------------------------=
--
-------------------------------------------------------------------------=
--

Workshop Co-Chairs:

Prof. Regina B. Araujo
Federal University of S?o Carlos
S?o Carlos, SP, Brazil
regina@dc.ufscar.br

Prof. Hussein M Alnuweiri
University of British Columbia
Vancouver, Canada
hussein@ece.ubc.ca

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

Program Committee:

Hussein Alnuweiri, University of British Columbia, Canada
Rossana Andrade, Federal University of Ceara, Brazil
Regina Araujo, Federal University of Sao Carlos, Brazil
Nazim Agoulmine, University of Evry, France
Azzedine Boukerche, University of Ottawa, Canada
Raffaele Bruno, CNR, Italy
Hsiao-Hwa Chen, National Sun Yat-Sen University, Taiwan
Zihua Guo, Lenovo Corporate R&D, China
Anna Hac, University of Hawaii, USA
Hai Jiang, University of Waterloo, Canada
Victor Leung, University of British Columbia, Canada
Wei Li, University of Toledo, USA
Jiangchuan Liu, Simon Fraser University, Canada
Pascal Lorenz, University of Haute Alsace, France
Antonio A. F. Loureiro, Federal University of Minas Gerais, Brazil
Andreas Meissner,  Fraunhofer Institute, Germany
Jelena Misic, University of Manitoba, Canada
Edmundo Monteiro, University of Coimbra, Portugal
Jander Moreira, Federal University of Sao Carlos, Brazil
Mirela S. M. Notare, Barddal University, Brazil
Stephen Olariu, Old Dominion University, USA
Jianping Pan, NTT MCL, USA
Bjorn Pehrson, Royal Institute of Technology, Sweden
Yu-Chee Tseng, National Chiao Tung Univ., Taiwan
Murat Uysal, University of Waterloo, Canada
Qi Xue,  Qualcomm Inc., USA
Yang Yang, University College London, UK
Weihua Zhuang, University of Waterloo, Canada

------_=_NextPart_001_01C67CE3.4CFBF2AF
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
=0A=
=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">=0A=
<HTML>=0A=
<HEAD>=0A=
=0A=
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7638.1">=0A=
<TITLE>Re: Help</TITLE>=0A=
</HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText22605 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT size=3D2>CALL FOR PAPERS</FONT></DIV></DIV>=0A=
<DIV>=0A=
<DIV>=0A=
<DIV dir=3Dltr><FONT =0A=
size=3D2>----------------------------------------------------------------=
----</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT =0A=
size=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; =0A=
2nd ACM WMuNeP 2006<BR>&nbsp;&nbsp; Second ACM International Workshop on =0A=
Wireless Multimedia Networking =0A=
and<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
Performance Modeling (WMuNeP =0A=
'06)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
<A =0A=
href=3D"http://www.dc.ufscar.br/wmunep06/">http://www.dc.ufscar.br/wmunep=
06/</A><BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
To be held jointly with the 9th ACM MSWiM =0A=
2006<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; =0A=
October 2-6th, =0A=
2006<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 =0A=
Torremolinos, Malaga, =0A=
Spain<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
<A =0A=
href=3D"http://www.cs.unibo.it/mswim2006">http://www.cs.unibo.it/mswim200=
6</A><BR><BR>*ACM =0A=
Pending =0A=
Approval<BR><BR>---------------------------------------------------------=
-----------<BR>Due =0A=
date: June 10th, =0A=
2006<BR>-----------------------------------------------------------------=
----<BR>Selected =0A=
papers will be published on a special issue of ACM/Springer Multimedia =0A=
Systems<BR>--------------------------------------------------------------=
-------<BR><BR><BR>The =0A=
Second ACM International Workshop on Wireless Multimedia Networking =0A=
and<BR>Performance Modeling (WMuNeP '06) will be a one-day workshop, =
held =0A=
in<BR>conjunction with the 9th Annual ACM Symposium on Modeling, =
Analysis =0A=
and<BR>Simulation of Wireless and Mobile Systems (MSWiM=C2=B406). The =
demand =0A=
for<BR>wireless multimedia communications thrives in today's consumer =0A=
and<BR>corporate market. The need to evolve multimedia applications and =0A=
services,<BR>and their associated protocols for emerging networks is at =
a =0A=
critical<BR>point given the proliferation and integration of wireless =
systems =0A=
to<BR>intelligent and broadband networks, mobility of people, =0A=
data/voice<BR>convergence and the integration of computing and =
communication in =0A=
mobile<BR>devices.<BR><BR>This workshop is devoted to cover different =
aspects of =0A=
wireless multimedia<BR>networking and performance modeling for WLANs, =
WPANs, =0A=
WMANs, WWANs, MANETs<BR>and sensor networks such as wireless video and =
wireless =0A=
streaming,<BR>systematic design methodologies, algorithms, =
synchronization, =0A=
analysis and<BR>performance modeling. The workshop will provide a forum =
for =0A=
researchers<BR>and practitioners to present their contributions related =
to the =0A=
above<BR>high-level aspects.<BR><BR>Topics of interest include (but are =
not =0A=
limited to):<BR><BR>- Wireless multimedia network management<BR>- =
Wireless =0A=
multimedia traffic modeling<BR>- Middleware and reflective systems =
support for =0A=
wireless multimedia<BR>- Proxy-based systems for video transcoding and =
content =0A=
distribution<BR>- Performance modeling, monitoring and evaluation of =
wireless =0A=
multimedia<BR>&nbsp; networks and systems<BR>- Multipoint, multicast =
wireless =0A=
multimedia services<BR>- Deployment of wireless multimedia applications, =0A=
services and networks<BR>- Protocols for wireless multimedia =
networks<BR>- QoS =0A=
in wireless multimedia networks<BR>- Integration of wireless multimedia =
networks =0A=
to broadband networks<BR>- End-to-end IP multimedia wireless =
communications<BR>- =0A=
Coding and transmission for wireless multimedia networks<BR>- =
Distributed =0A=
wireless multimedia services<BR>- Content-based wireless multimedia =
information =0A=
retrieval tools<BR>- Video, streaming, real-time wireless multimedia =0A=
communications and<BR>&nbsp;&nbsp; applications<BR>- Security in =
wireless =0A=
multimedia networks<BR>- Wireless multimedia right protection and =0A=
watermarking<BR>- Pricing mechanisms for wireless multimedia =
networks<BR>- =0A=
E-Commerce and related applications for wireless multimedia =
networks<BR>- =0A=
Multimedia evaluation and processing for wireless networks<BR>- Cross =
layer =0A=
design for wireless multimedia networks<BR>- Analytical modeling of =
wireless =0A=
multimedia networks<BR>- Software tools for system performance and =
evaluation of =0A=
wireless<BR>&nbsp; multimedia networks<BR>- Performance comparison of =
wireless =0A=
multimedia networks<BR>- Case studies showing the role of evaluation in =
the =0A=
design of =0A=
systems<BR><BR>----------------------------------------------------------=
-----------------<BR>Important =0A=
Dates:<BR>Submission =
deadline:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =0A=
June 10th, 2006<BR>Notification of acceptance:&nbsp; July 10th, =
2006<BR>Camera =0A=
ready papers:&nbsp; =0A=
TBA<BR>------------------------------------------------------------------=
---------<BR><BR>Paper =0A=
Submission Guidelines:<BR>Authors are invited to submit research =
contributions =0A=
representing original,<BR>previously unpublished work. Submitted papers =
will be =0A=
carefully evaluated<BR>based on originality, significance, technical =
soundness, =0A=
and clarity of<BR>exposition.<BR><BR>Accepted papers will appear on the =
workshop =0A=
proceedings that will be<BR>published by ACM press. At least one of the =
authors =0A=
of accepted papers<BR>must attend the conference to present his/her =0A=
paper.<BR><BR>Paper length should be no more than 10 pages, double =
column, ACM =0A=
style<BR>including tables and figures. A template for ACM SIG =
Proceedings =0A=
style<BR>(LaTeX2e and MS Word) can be found here. Only Postscript and =
PDF =0A=
formats<BR>are accepted. Papers must be submitted electronically via the =
JEMS =0A=
system<BR>(Brazilian EDAS).<BR><BR>WMuNeP&nbsp; 2006 electronic =
submission is =0A=
now active on the JEMS system<BR>(Brazilian EDAS) at <A =0A=
href=3D"https://submissoes.sbc.org.br/wmunep2006">https://submissoes.sbc.=
org.br/wmunep2006</A>. =0A=
Once you are<BR>a registered JEMS user, this link will address you =
directly to =0A=
the WMuNeP<BR>2006 Paper Submission page. Important - For any question =
or =0A=
problem<BR>related to WMuNeP 2006, please contact =0A=
wmunep2006@dc.ufscar.br<BR>----------------------------------------------=
-----------------------------<BR>----------------------------------------=
-----------------------------------<BR><BR>Workshop =0A=
Co-Chairs:<BR><BR>Prof. Regina B. Araujo<BR>Federal University of S?o =0A=
Carlos<BR>S?o Carlos, SP, Brazil<BR>regina@dc.ufscar.br<BR><BR>Prof. =
Hussein M =0A=
Alnuweiri<BR>University of British Columbia<BR>Vancouver, =0A=
Canada<BR>hussein@ece.ubc.ca<BR><BR>-------------------------------------=
--------------------------------------<BR><BR>Program =0A=
Committee:<BR><BR>Hussein Alnuweiri, University of British Columbia, =0A=
Canada<BR>Rossana Andrade, Federal University of Ceara, Brazil<BR>Regina =
Araujo, =0A=
Federal University of Sao Carlos, Brazil<BR>Nazim Agoulmine, University =
of Evry, =0A=
France<BR>Azzedine Boukerche, University of Ottawa, Canada<BR>Raffaele =
Bruno, =0A=
CNR, Italy<BR>Hsiao-Hwa Chen, National Sun Yat-Sen University, =
Taiwan<BR>Zihua =0A=
Guo, Lenovo Corporate R&amp;D, China<BR>Anna Hac, University of Hawaii, =0A=
USA<BR>Hai Jiang, University of Waterloo, Canada<BR>Victor Leung, =
University of =0A=
British Columbia, Canada<BR>Wei Li, University of Toledo, =
USA<BR>Jiangchuan Liu, =0A=
Simon Fraser University, Canada<BR>Pascal Lorenz, University of Haute =
Alsace, =0A=
France<BR>Antonio A. F. Loureiro, Federal University of Minas Gerais, =0A=
Brazil<BR>Andreas Meissner,&nbsp; Fraunhofer Institute, =
Germany<BR>Jelena Misic, =0A=
University of Manitoba, Canada<BR>Edmundo Monteiro, University of =
Coimbra, =0A=
Portugal<BR>Jander Moreira, Federal University of Sao Carlos, =
Brazil<BR>Mirela =0A=
S. M. Notare, Barddal University, Brazil<BR>Stephen Olariu, Old Dominion =0A=
University, USA<BR>Jianping Pan, NTT MCL, USA<BR>Bjorn Pehrson, Royal =
Institute =0A=
of Technology, Sweden<BR>Yu-Chee Tseng, National Chiao Tung Univ., =0A=
Taiwan<BR>Murat Uysal, University of Waterloo, Canada<BR>Qi Xue,&nbsp; =
Qualcomm =0A=
Inc., USA<BR>Yang Yang, University College London, UK<BR>Weihua Zhuang, =0A=
University of Waterloo, Canada</DIV></FONT></DIV></DIV>=0A=
=0A=
</BODY>=0A=
</HTML>
------_=_NextPart_001_01C67CE3.4CFBF2AF--


--===============1667792800==
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

--===============1667792800==--




From manet-bounces@ietf.org Sun May 21 23:24:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fi10T-0003W3-LE; Sun, 21 May 2006 23:22:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fi10S-0003Vs-IC
	for manet@ietf.org; Sun, 21 May 2006 23:22:56 -0400
Received: from basm.cerias.purdue.edu ([128.10.243.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fi10C-00088W-Cp
	for manet@ietf.org; Sun, 21 May 2006 23:22:56 -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 k4M3MHHZ012396
	for <manet@ietf.org>; Sun, 21 May 2006 23:22:17 -0400 (EDT)
Received: from localhost (crisn@localhost)
	by basm.cerias.purdue.edu (8.13.6/8.13.6/Submit) with ESMTP id
	k4M3MFRl012274
	for <manet@ietf.org>; Sun, 21 May 2006 23:22:17 -0400 (EDT)
Date: Sun, 21 May 2006 23:22:15 -0400 (EDT)
From: Cristina Nita-Rotaru <crisn@cerias.purdue.edu>
To: manet@ietf.org
Message-ID: <Pine.GSO.4.58.0605212312510.9319@basm.cerias.purdue.edu>
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=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on 
	basm.cerias.purdue.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff0adf256e4dd459cc25215cfa732ac1
Subject: [manet] SecureComm 2006 - CALL FOR POSTER/DEMOS and CALL FOR
	PARTICIPATION
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


 Dear Colleague,

 Please find attached the call for participation for the Second IEEE
 Communications Society/CreateNet International Conference on Security
 and Privacy for 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

 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 POSTER/DEMOS and CALL FOR PARTICIPATION

                           SecureComm 2006

      Second IEEE Communications Society/CreateNet International
       Conference on Security and Privacy for Communication Networks

              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. Topics in other areas
(e.g., formal methods, database security, secure OS/software,
theoretical cryptography, e-commerce) will be considered only if a
clear connection to privacy and/or security in
communication/networking is demonstrated.

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.

Areas of interest include, but ARE NOT limited to, the following:
-----------------------------------------------------------------

* Security & Privacy in Wired, Wireless, Mobile, Hybrid, Sensor, Ad Hoc networks
* Network Intrusion Detection and Prevention, DoS Countermeasures
* Firewalls, Routers, Filters and Malware detectors
* Public Key Infrastructures and Other Security Architectures
* Secure Web Communication
* Communication Privacy and Anonymity
* Secure/Private E-commerce
* Secure Routing, Naming/Addressing, Network Management
* Security & Privacy in Pervasive and Ubiquitous Computing, e.g., RFIDs


PAPERS: Regular Technical Paper submissions are closed.


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.

Proposals for posters/demo presentations are solicited.  Proposals
will be reviewed and selection will be made based on the perceived
value to the research community and interest level for the conference
attendees. Proposals should not exceed 3 pages and should include: a
description of the poster/demo, the focus area, technologies involved,
specific equipment to be used (for demos), demo layout and space
required. Please submit proposals to the Research Demos Chair by
June 15, 2006 by email to: karygiannis@nist.gov.


IMPORTANT DATES
---------------

POSTER/DEMO Submissions due:    June 15, 2006
NOTIFICATION date:              July 6, 2006
Author 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
 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
 Kwok-Yan Lam           Tsinghua University
 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 May 22 00:26:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fi1z4-0005qv-QJ; Mon, 22 May 2006 00:25:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fi1z3-0005qq-JP
	for manet@ietf.org; Mon, 22 May 2006 00:25:33 -0400
Received: from ug-out-1314.google.com ([66.249.92.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fi1z1-00027b-9j
	for manet@ietf.org; Mon, 22 May 2006 00:25:33 -0400
Received: by ug-out-1314.google.com with SMTP id m3so1220561uge
	for <manet@ietf.org>; Sun, 21 May 2006 21:25:30 -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=O6btAE5hft9nHzT7RuY9geyRXZ/8Uq8yei1OSaJVzK5wG/jNFAONhSdzc0piOgssV9/tEMDnWjdZP6gwBGWxZEtGiVKUsuACbB05ZLg88ib72JmG350I5LRiaDs29gXAZKAkb3z7qZ84JTxZ8igqZxUvW0H17lxsU/kwN0UCl6E=
Received: by 10.78.31.18 with SMTP id e18mr1023899hue;
	Sun, 21 May 2006 21:25:30 -0700 (PDT)
Received: by 10.78.53.20 with HTTP; Sun, 21 May 2006 21:25:30 -0700 (PDT)
Message-ID: <146563590605212125r7a322ad6m93dd4df311241334@mail.gmail.com>
Date: Mon, 22 May 2006 12:25:30 +0800
From: "chen jiming" <jmchen.zju@gmail.com>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: [manet] OPENT help for sensor actuator networks
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1294162277=="
Errors-To: manet-bounces@ietf.org

--===============1294162277==
Content-Type: multipart/alternative; 
	boundary="----=_Part_29381_16620540.1148271930425"

------=_Part_29381_16620540.1148271930425
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Dear all:

I would like to get the source of
the OPENT project for sensor actuator networks
see the link http://www.imtek.de/emp/content/OpnetProjectMackensen.htm

maybe it can be downloaded from OPNET support
with a valid account

thanks a lot

jiming Chen

------=_Part_29381_16620540.1148271930425
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Dear all:<br><br>I would like to get the source of<br>the OPENT project for sensor actuator networks<br><span></span>see the link <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.imtek.de/emp/content/OpnetProjectMackensen.htm" target="_blank">
http://www.imtek.de/emp/content/OpnetProjectMackensen.htm</a><br><br>maybe it can be downloaded from OPNET support<br>with a valid account<br><br>thanks a lot<br><br>jiming Chen<br>

------=_Part_29381_16620540.1148271930425--


--===============1294162277==
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

--===============1294162277==--




From manet-bounces@ietf.org Mon May 22 10:31:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiBOu-0005Er-HD; Mon, 22 May 2006 10:28:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiBOs-0005Ek-7F
	for manet@ietf.org; Mon, 22 May 2006 10:28:50 -0400
Received: from mail.um.es ([155.54.212.109])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiBOn-00035u-BT
	for manet@ietf.org; Mon, 22 May 2006 10:28:50 -0400
Received: from localhost (localhost [127.0.0.1])
	by mail.um.es (Postfix) with ESMTP id 0736823CE5E
	for <manet@ietf.org>; Mon, 22 May 2006 16:28:44 +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 17292-01-35 for <manet@ietf.org>;
	Mon, 22 May 2006 16:28:43 +0200 (CEST)
Received: from [155.54.205.190] (unknown [155.54.205.190])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.um.es (Postfix) with ESMTP id 6895023CEA9
	for <manet@ietf.org>; Mon, 22 May 2006 16:28:43 +0200 (CEST)
Message-ID: <4471CA9B.3060403@dif.um.es>
Date: Mon, 22 May 2006 16:28:43 +0200
From: "Pedro M. Ruiz" <pedrom@dif.um.es>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: 'IETF Manet' <manet@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at telemat.um.es
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Subject: [manet] CFP LOCAN 2006: 2nd Int. Workshop on Localized
 Communication and Topology Control for Ad Hoc Networks
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


Our apologies for duplicate postings.

---------------------------------------------------------------------------
                  CALL FOR PAPERS - LOCAN 2006
        2nd International Workshop on Localized Communication
              and Topology Protocols for Ad hoc Networks

          in conjunction with MASS-2006 (www.ieee-mass.org)
               Vancouver, Canada, October 9 - 12, 2006

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

SUBJECT AND SCOPE
-----------------
This workshop covers comprehensively the algorithmic issues in the hot
area of ad hoc and sensor networking. The design of data communication
techniques in multi-hop ad hoc networks has challenges at all layers
of communication. This workshop concentrates on the network layer
problems like data communication (routing, QoS-routing, geocasting,
multicasting, broadcasting, etc.)  and topology control (neighbor
discovery, power adjustment, neighbor elimination, etc.).

Additionally, sensor networks are currently recognized as one of the
priority research areas by NSF. The area of sensor networking is
gaining momentum within the research community. This workshop will
address ongoing research on this field, including problems such as:
physical properties, sensor training, security through intelligent
node cooperation, medium access, sensor area coverage with random and
deterministic placement, object location, sensor position
determination, energy efficient broadcasting and activity scheduling,
routing, connectivity, data dissemination and gathering, sensor
centric quality of routing, temporal message ordering, path exposure,
tree reconfiguration, topology construction, and transport layer.

The main paradigm shift is to apply localized (or greedy) schemes as
opposed to existing protocols requiring global information. Localized
algorithms are distributed algorithms where simple local node
behaviour achieves a desired global objective. Localized protocols
provide scalable solutions, that is, solutions for wireless networks
with an arbitrary number of nodes, which is the main goal of this
plan. Sensor and rooftop/mesh networks, for instance, have hundreds or
thousands of nodes.

The main objective of the workshop is to present state of the art
research results on data communication and topology control in rapidly
growing area of ad hoc and sensor networks, with emphasizes on
localized techniques.

Topics of interest include, but are not limited to:
* Medium access control
* Analytical, mobility and validation models for ad hoc networks
* Hybrid networks and wireless Internet
* Security in ad hoc networks
* Data management issues, query processing, and data delivery
* Routing, broadcasting and multicasting in ad hoc networks
* Energy-efficient protocols for ad hoc networks
* Quality of service in medium access control and routing
* Topology construction and maintenance in ad hoc networks
* Neighborhood discovery and mobility management

IMPORTANT DATES
---------------
Manuscript Submission: June 19, 2006
Acceptance Notification: July 19, 2006
Final Manuscript Due: August 10, 2006

PAPER SUBMISSION
----------------
Papers must not exceed 10 single-spaced and two-column pages using at
least 10 point size type on 8.5 x 11 inches pages. See style files,
author guidelines and instructions at the conference website. Accepted
papers will be published by IEEE Computer Society Press, as
proceedings of the MASS2006 workshops. Please submit papers via email
to both program co-chairs (pedrom@dif.um.es, fei.dai@ndsu.edu).

GENERAL CO-CHAIRS
-----------------
David Simplot-Ryl, University of Lille, France
Ivan Stojmenovic, University of Ottawa, Canada

PROGRAM CO-CHAIRS
-----------------
Pedro M. Ruiz, University of Murcia, Spain
Fei Dai, North Dakota State University, USA


Program Committee
-----------------
Michel Barbeau, Carleton University, Ottawa, Canada
Raffaele Bruno, IIT-CNR, Italy
Ian Chakeres, Boing Inc., USA
Misha Dohler, France Telecom R&D, France
Stefan Dulman, University of Twente, Netherlands
Jie Gao, State University of New York, USA
J. J. Garcia-Luna-Aceves, Univ. of California, Santa Cruz, USA
Silvia Giordano, University of Applied Science, SUPSI, Switzerland
Antonio F. Gomez-Skarmeta, University of Murcia, Spain
Isabelle Guerin Lassous, INRIA Rhone Alpes, France
Mattias Handy, Univ. Rostock, Germany
Thomas Kunz, Carleton University, Canada
Miguel A. Labrador, Univ. South Florida, USA
Pietro Manzoni, Univ. Politecnica de Valencia, Spain
Luis Orozco, Univ. Castilla La Mancha, Spain
S. S. Ravi, State University of New York at Albany, USA
Isabelle Simplot-Ryl, University of Lille, France


ADDITIONAL INFORMATION
----------------------
Additional information about the workshop will be continuously
updated at the LOCAN 2006 website.

                http://ants.dif.um.es/locan2006/

-- 
---------------------------------------------------------------------
Pedro M. Ruiz, Ph.D.                    E-mail: pedrom@dif.um.es
Fac. Informatica, Univ. of Murcia       Phone:  +34968364335
Campus de Espinardo s/n                 Fax:    +34968364151
E-30100, Espinardo, Murcia              www: ants.dif.um.es/~pedrom/
SPAIN
---------------------------------------------------------------------


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



From manet-bounces@ietf.org Mon May 22 15:06:44 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiFjL-0004pL-9C; Mon, 22 May 2006 15:06:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiFjJ-0004p6-IV
	for manet@ietf.org; Mon, 22 May 2006 15:06:13 -0400
Received: from hostreea1.alcatel.com ([143.209.238.161]
	helo=audl951.usa.alcatel.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiFjH-0007SN-U2
	for manet@ietf.org; Mon, 22 May 2006 15:06:13 -0400
Received: from usdaln07347 (usdaln07347.usa.alcatel.com [143.209.105.69])
	by audl951.usa.alcatel.com (ALCANET) with ESMTP id k4MJ68C5009738;
	Mon, 22 May 2006 14:06:08 -0500
From: "Tim Ozugur" <tim.ozugur@alcatel.com>
To: <manet@ietf.org>
Date: Mon, 22 May 2006 14:06:08 -0500
Message-ID: <008d01c67dd2$c82c2be0$4569d18f@ad3.ad.alcatel.com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
Thread-index: AcZu3RZf2J7ICLthSTyN8QWpYrkJBwO9IIBAAABH6DA=
X-Scanned-By: MIMEDefang 2.51 on 143.209.238.34
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b058151374d77ee76edaac850f7449fb
Cc: tpc@bwan.org
Subject: [manet] Call For Papers: BWAN 2006 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1363442711=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1363442711==
Content-Type: multipart/related;
	boundary="----=_NextPart_000_008E_01C67DA8.DF5623E0"

This is a multi-part message in MIME format.

------=_NextPart_000_008E_01C67DA8.DF5623E0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_008F_01C67DA8.DF5623E0"


------=_NextPart_001_008F_01C67DA8.DF5623E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

 
 (Apologies if you are receiving this message more than once) 
 (Submission deadline is extended to 15 June 2006)

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

CALL FOR PAPERS

INTERNATIONAL WORKSHOP ON BROADBAND WIRELESS

ACCESS FOR UBIQUITOUS NETWORKING (BWAN 2006)

20 September 2006 - Alghero, Sardinia, Italy 

(www.bwan.org)

Technically sponsored by IEEE (approval pending) 

 

IMPORTANT DATES:

Submission of Summaries: 15 June 2006

 

SPECIAL STUDENT REGISTRATION RATE: 

Early registration rate for students: USD 270 (cut-off date: one month prior
to the workshop)

The late registration rate for students: USD 320

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

Scope and Interests 

Today Broadband Wireless access (mobile/nomadic) is emerging to offer
outstanding opportunities. In this new world of communicating devices, the
evolution towards ubiquitous networking is promising new paradigm with the
aim of providing communication capability all the time, everywhere,
transparently and invisibly to the user, using devices embedded in the
surrounding physical environment. The implementation of such a paradigm
requires innovation in wireless network technologies and devices,
development of infrastructures, enablers supporting enhanced features for
ubiquitous capability. 
The workshop is intended to present features based on new architectures
supporting mobility and/or nomadic features for wireless access (IEEE
802.yx, Mesh,...), the sharing of the network access, bandwidth sharing on
radio access, network enablers all favoring the new perspective of
ubiquitous and ambient networking. Within the framework of BWAN 2006, the
next generation of network access will be investigated. 
Topics of interest to this workshop include (but are not limited to)
performance studies and solutions (algorithms, protocols, architectures)
that tend to improve experience of users of services and applications with
context awareness. 


Workshop topics 

  <http://www.bwan.org/immagini/punto_elenco.gif>   New Architectures and
technologies for broadband wireless access (xDSL/FTTx,etc) with mobility
features 

  <http://www.bwan.org/immagini/punto_elenco.gif>   3G and beyond 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Ambient Networking 

  <http://www.bwan.org/immagini/punto_elenco.gif>   AAA (Authentication,
Authorization, Accounting) 

  <http://www.bwan.org/immagini/punto_elenco.gif>   QoS efficient and
scalable routing 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Transport mechanism for
supporting various high speed traffics

  <http://www.bwan.org/immagini/punto_elenco.gif>   End to end security and
privacy issues for ubiquitous Network access

  <http://www.bwan.org/immagini/punto_elenco.gif>   xDSL/FTTx+WiFi modem
with mobility enhancement 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Radio extension such as
802.xy (WiFi, WiMax, etc) P2P network 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Standard and regulations

  <http://www.bwan.org/immagini/punto_elenco.gif>   Low cost and low power
integrated Modulation

  <http://www.bwan.org/immagini/punto_elenco.gif>   Network cost performance
and Business Models

  <http://www.bwan.org/immagini/punto_elenco.gif>   RFID tags,
sensors,actuators, etc

  <http://www.bwan.org/immagini/punto_elenco.gif>   Interference mitigation
for multiple access

  <http://www.bwan.org/immagini/punto_elenco.gif>   IPv6 impact

  <http://www.bwan.org/immagini/punto_elenco.gif>   Cognitive radio


Submission Dates 

  <http://www.bwan.org/immagini/punto_elenco.gif>   Submission of summaries:
15 June 2006

  <http://www.bwan.org/immagini/punto_elenco.gif>   Notification of
Acceptance: 15 July  2006 


  <http://www.bwan.org/immagini/punto_elenco.gif>   Submission Camera Ready
Papers: 10 August 2006 


Publication 

The submissions to be presented at the workshop will be selected, based on
their originality, technical merit and topical relevance of their contents.
All accepted papers will be published in the conference proceedings that
will be available at the workshop.


------=_NextPart_001_008F_01C67DA8.DF5623E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2800.1528" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><FONT =
face=3DVerdana><FONT=20
color=3D#003366><FONT size=3D2><SPAN class=3D487385718-22052006><FONT =
face=3DArial=20
color=3D#0000ff></FONT></SPAN></FONT></FONT></FONT></FONT>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DArial><FONT face=3DVerdana><FONT color=3D#003366><FONT =
size=3D2><SPAN=20
class=3D487385718-22052006>&nbsp;</SPAN><STRONG>(Apologies if you are =
receiving=20
this message more than once)</STRONG><SPAN =
class=3D487385718-22052006><FONT=20
face=3DArial =
color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></FONT></FONT></DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
face=3DArial><FONT face=3DVerdana><FONT color=3D#003366><FONT =
size=3D2><SPAN=20
class=3D487385718-22052006><STRONG>&nbsp;(Submission deadline is =
extended to 15=20
June 2006)</STRONG></SPAN></FONT></DIV>
<DIV>
<P><FONT=20
size=3D2><STRONG>--------------------------------------------------</STRO=
NG></FONT></P>
<P><FONT size=3D2><STRONG>CALL FOR PAPERS</STRONG></FONT></P>
<P><FONT size=3D2><STRONG>INTERNATIONAL WORKSHOP ON BROADBAND=20
WIRELESS</STRONG></FONT></P>
<P><FONT size=3D2><STRONG>ACCESS FOR UBIQUITOUS NETWORKING (BWAN=20
2006)</STRONG></FONT></P>
<P><FONT size=3D2></FONT></P>
<P><FONT size=3D2><STRONG>20 September 2006 - Alghero, Sardinia, Italy=20
</STRONG></FONT></P>
<P><FONT size=3D2><STRONG>(</STRONG></FONT><A =
href=3D"www.bwan.org"><U><FONT=20
color=3D#0000ff><FONT=20
size=3D2><STRONG>www.bwan.org</STRONG></FONT></U></FONT></A><FONT=20
size=3D2><STRONG>)</STRONG></FONT></P>
<P><FONT size=3D2><STRONG>Technically sponsored by IEEE (approval =
pending)=20
</STRONG></FONT></P>
<P><FONT size=3D2></FONT>&nbsp;</P>
<P><FONT size=3D2><STRONG>IMPORTANT DATES:</STRONG></FONT></P>
<P><FONT size=3D2><STRONG>Submission of Summaries: 15</STRONG><SPAN=20
class=3D487385718-22052006><FONT face=3DArial =
color=3D#0000ff><STRONG><FONT=20
face=3DVerdana =
color=3D#003366>&nbsp;</FONT></STRONG></FONT></SPAN><STRONG><SPAN=20
class=3D487385718-22052006><FONT face=3DArial color=3D#0000ff><FONT =
face=3DVerdana=20
color=3D#003366>June</FONT></FONT></SPAN> 2006</STRONG></FONT></P>
<P><FONT face=3DArial size=3D2><SPAN=20
class=3D348430518-03052006></SPAN></FONT>&nbsp;</P>
<P><FONT face=3DArial size=3D2><SPAN =
class=3D348430518-03052006><STRONG>SPECIAL=20
STUDENT REGISTRATION RATE: </STRONG></SPAN></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><STRONG><SPAN=20
class=3D348430518-03052006>E</SPAN>arly registration rate for students: =
USD=20
270<SPAN class=3D348430518-03052006> (cut-off date:&nbsp;one month prior =
to the=20
workshop)</SPAN></STRONG></FONT></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D348430518-03052006></SPAN></FONT></FONT><FONT face=3DArial=20
size=3D2><STRONG>The late registration rate for students: USD=20
320</STRONG></FONT></P>
<P><FONT=20
size=3D2><STRONG>---------------------------------------------------</STR=
ONG></FONT></P></FONT></FONT>
<P align=3Djustify><FONT size=3D2><FONT face=3DVerdana><FONT =
color=3D#003366><B>Scope=20
and Interests</B> </FONT><BR><BR>Today Broadband Wireless access=20
(mobile/nomadic) is emerging to offer outstanding opportunities. In this =
new=20
world of communicating devices, the evolution towards ubiquitous =
networking is=20
promising new paradigm with the aim of providing communication =
capability all=20
the time, everywhere, transparently and invisibly to the user, using =
devices=20
embedded in the surrounding physical environment. The implementation of =
such a=20
paradigm requires innovation in wireless network technologies and =
devices,=20
development of infrastructures, enablers supporting enhanced features =
for=20
ubiquitous capability. <BR>The workshop is intended to present features =
based on=20
new architectures supporting mobility and/or nomadic features for =
wireless=20
access (IEEE 802.yx, Mesh,...), the sharing of the network access, =
bandwidth=20
sharing on radio access, network enablers all favoring the new =
perspective of=20
ubiquitous and ambient networking. Within the framework of BWAN 2006, =
the next=20
generation of network access will be investigated. <BR>Topics of =
interest to=20
this workshop include (but are not limited to) performance studies and =
solutions=20
(algorithms, protocols, architectures) that tend to improve experience =
of users=20
of services and applications with context awareness. <BR><BR><BR><FONT=20
color=3D#003366><B>Workshop topics</B> </FONT><BR><BR><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; New=20
Architectures and technologies for broadband wireless access =
(xDSL/FTTx,etc)=20
with mobility features </FONT></FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; 3G=20
and beyond </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Ambient Networking </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; AAA=20
(Authentication, Authorization, Accounting) </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; QoS=20
efficient and sca<SPAN class=3D348430518-03052006>la</SPAN>ble routing =
</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Transport mechanism for supporting various high speed =
traffics</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; End=20
to end security and privacy issues for ubiquitous Network =
access</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
xDSL/FTTx+WiFi modem with mobility enhancement </FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Radio extension such as 802.xy (WiFi, WiMax, etc) P2P network =
</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Standard and regulations</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp; Low=20
cost and low power integrated Modulation</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Network cost performance and Business Models</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
RFID tags, sensors,actuators, etc</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Interference mitigation for multiple access</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
IPv6 impact</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Cognitive radio</FONT></P><BR>
<P align=3Djustify><FONT color=3D#003366><FONT size=3D2><FONT=20
face=3DVerdana><B>Submission Dates</B> </FONT></FONT></FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Submission of summaries: 15&nbsp;<SPAN=20
class=3D487385718-22052006>June&nbsp;</SPAN>2006</FONT></P>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D12 =
border=3D0>&nbsp;=20
Notification of Acceptance: 15 Ju<SPAN =
class=3D487385718-22052006>ly&nbsp;</SPAN>=20
2006 </FONT>
<P align=3Dleft><FONT face=3DVerdana size=3D2><IMG height=3D12=20
src=3D"http://www.bwan.org/immagini/punto_elenco.gif" width=3D11 =
border=3D0>&nbsp;=20
Submission Camera Ready Papers: 10&nbsp;<SPAN=20
class=3D487385718-22052006>August</SPAN> 2006 </FONT></P><BR>
<P align=3Djustify><FONT size=3D2><FONT face=3DVerdana><FONT=20
color=3D#003366><B>Publication</B> </FONT><BR><BR>The submissions to be =
presented=20
at the workshop will be selected, based on their originality, technical =
merit=20
and topical relevance of their contents. All accepted papers will be =
published=20
in the conference proceedings that will be available at the=20
workshop.</FONT></FONT></P></FONT></DIV></BODY></HTML>

------=_NextPart_001_008F_01C67DA8.DF5623E0--

------=_NextPart_000_008E_01C67DA8.DF5623E0
Content-Type: image/gif;
	name="punto_elenco.gif"
Content-Transfer-Encoding: base64
Content-Location: http://www.bwan.org/immagini/punto_elenco.gif

R0lGODlhDAAMAHcAACH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAY
AAAADG1zT1BNU09GRklDRTkuMAgRTF2IACH/C01TT0ZGSUNFOS4wGAAAAAxjbVBQSkNtcDA3MTIC
AAABDAfaGwAh+QQBAAAAACwAAAAADAAMAIPAwMDMmTPMmQDMZgDMMwCZZgCZMwCZAAABAgMBAgMB
AgMBAgMBAgMBAgMBAgMBAgMDKQi63P4wPjMGuYYwUjkRA1MYVDUETKZa4UKqlOYSRoG1Ss1izGH4
L0MCADs=

------=_NextPart_000_008E_01C67DA8.DF5623E0--



--===============1363442711==
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

--===============1363442711==--





From manet-bounces@ietf.org Tue May 23 05:15:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiSy4-0008La-9Z; Tue, 23 May 2006 05:14:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiSy2-0008LQ-9v
	for manet@ietf.org; Tue, 23 May 2006 05:14:18 -0400
Received: from diana.create-net.org ([213.21.183.211] helo=create-net.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiSxz-0004RK-UR
	for manet@ietf.org; Tue, 23 May 2006 05:14:18 -0400
Received: from YabinYe ([213.21.183.209]) (authenticated bits=0)
	by create-net.org (8.12.11/8.12.11) with ESMTP id k4N9DwLl031382
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <manet@ietf.org>; Tue, 23 May 2006 11:13:58 +0200
Message-Id: <200605230913.k4N9DwLl031382@create-net.org>
From: "Yabin Ye" <yabin.ye@create-net.it>
To: <manet@ietf.org>
Date: Tue, 23 May 2006 11:13:54 +0200
Organization: Create-Net
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: AcZ+SNNPanmFEOslQVyzZrkkNhV38QAAAwMAAAAGDBAAAAKPoAAABIxQAAADhKAAAALW8A==
X-Virus-Scanned: clamd / ClamAV version 0.72, clamav-milter version 0.72
	on 127.0.0.1
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21f6736b171db90b7af90d77f0c0e285
Subject: [manet] Call For Workshop Ideas co-located with CHINACOM2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0051010368=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0051010368==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0197_01C67E59.FA824BB0"

This is a multi-part message in MIME format.

------=_NextPart_000_0197_01C67E59.FA824BB0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

(Apology for duplicates)

 

Dear Colleague,

 

We have received more than 750 submissions for CHINACOM conference.
Currently we are accepting proposals for workshops.

 

OVERVIEW: The "First International Conference on Communications and
Networking in China," (CHINACOM2006) will be held in Beijing, China, from
25th to 27th October 2006. 

 

CHINACOM 2006 is being positioned as the premier international annual
conference for the presentation of original and fundamental advances in the
field of Communications, Networks, and Internet Applications. The conference
will consist of Technical Symposia, and Workshops. The Technical Symposia
will describe significant research in all areas defined below; while the
Workshops will focus on development, applications and related business
issues.

 

WORKSHOP SUBMISSION: CHINACOM 2006 is currently accepting proposals for
one-day workshops. Potential chairs are requested to submit a workshop
proposal of at most 5 pages. An ideal proposal should focus on a specific
theme, of current interest, and of interest to a large, diverse group of
professionals. It should clearly identify the theme, the scope, and specific
topic areas of interest which define the scope of the workshop. The proposal
should also provide suggestions for potential program chairs and committee
members.  A biographical sketch of each chair should be included

 

Evaluation of workshop proposals will be based on the relevance of the
subject matter, and the expertise and experience of the chair. The workshops
will be held in conjunction to the main conference. 

 

SUBMISSION GUIDELINES: Please send workshop proposals in PDF format by June
6th, 2006 to the workshops chairs, 

 

Jing (James) Yang, UTstarcom, USA,  <mailto:james.yang@utstar.com>
james.yang@utstar.com 

T. Russell Hsing, Telcordia, USA, thsing@telcordia.com 

 

IMPORTANT DATES:

Workshop Proposals Submission Deadline:                6th  June, 2006

Workshops:
24th and 28th October, 2006

 

We look forward to your submissions.


------=_NextPart_000_0197_01C67E59.FA824BB0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City" =
downloadurl=3D"http://www.5iamas-microsoft-com:office:smarttags"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0mm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0mm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p
	{mso-margin-top-alt:auto;
	margin-right:0mm;
	mso-margin-bottom-alt:auto;
	margin-left:0mm;
	font-size:12.0pt;
	font-family:SimSun;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:Arial;
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:Arial;
	color:navy;}
span.EmailStyle25
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>(Apology for
duplicates)<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>Dear =
Colleague,<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>We =
have received
more than 750 submissions for CHINACOM conference. Currently we are =
accepting
proposals for workshops.<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><b><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;letter-spacing:
-.1pt;font-weight:bold'><o:p>&nbsp;</o:p></span></font></b></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><b><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;letter-spacing:
-.1pt;font-weight:bold'>OVERVIEW: </span></font></b><span =
style=3D'letter-spacing:
-.1pt'>The &#8220;<b><i><span =
style=3D'font-weight:bold;font-style:italic'>First
International Conference on Communications and Networking in =
<st1:country-region
w:st=3D"on">China</st1:country-region>,&#8221; =
</span></i></b>(CHINACOM2006) will
be held in <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Beijing</st1:City>, <st1:country-region
 w:st=3D"on">China</st1:country-region></st1:place>, from =
25<sup>th</sup> to 27<sup>th</sup>
October 2006. <o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;letter-spacing:
-.1pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><b><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;font-weight:bold'>CHINACOM
2006</span></font></b> is being positioned as the premier international =
annual
conference for the presentation of original and fundamental advances in =
the
field of Communications, Networks, and Internet Applications. The =
conference
will consist of Technical Symposia, and Workshops. The Technical =
Symposia will
describe significant research in all areas defined below; while the =
Workshops
will focus on development, applications and related business =
issues.<span
style=3D'letter-spacing:-.1pt'><o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt;letter-spacing:-.1pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><b><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;letter-spacing:
-.1pt;font-weight:bold'>WORKSHOP SUBMISSION: <i><span =
style=3D'font-style:italic'>CHINACOM
2006 </span></i></span></font></b><span =
style=3D'letter-spacing:-.1pt'>is currently
accepting proposals for one-day workshops. </span>Potential chairs are
requested to submit a workshop proposal of at most 5 pages. <span
style=3D'letter-spacing:-.1pt'>An ideal proposal should focus on a =
specific
theme, of current interest, and of interest to a large, diverse group of =
professionals.
It should clearly identify the theme, the scope, and specific topic =
areas of
interest which define the scope of the workshop. The proposal should =
also
provide suggestions for potential program chairs and committee =
members.&nbsp; </span>A
biographical sketch of each chair should be included<span =
style=3D'letter-spacing:
-.1pt'><o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt'>Evaluation of
workshop proposals will be based on the relevance of the subject matter, =
and
the expertise and experience of the chair.<span =
style=3D'letter-spacing:-.1pt'>
The workshops will be held in conjunction to the main conference. =
<o:p></o:p></span></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;letter-spacing:
-.1pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><b><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt;letter-spacing:-.1pt;font-weight:bold'>SUBMISSI=
ON
GUIDELINES: </span></font></b><span =
style=3D'letter-spacing:-.1pt'>Please send
workshop proposals in PDF format by <b><span =
style=3D'font-weight:bold'>June 6<sup>th</sup>,
2006 </span></b>to the workshops chairs, <o:p></o:p></span></p>

<p class=3DMsoNormal><i><font size=3D3 face=3D"Times New Roman"><span =
lang=3DSV
style=3D'font-size:12.0pt;font-style:italic'><o:p>&nbsp;</o:p></span></fo=
nt></i></p>

<p class=3DMsoNormal><i><font size=3D3 face=3D"Times New Roman"><span =
lang=3DSV
style=3D'font-size:12.0pt;font-style:italic'>Jing (James) Yang, =
</span></font></i><span
lang=3DSV>UTstarcom, USA, </span><a =
href=3D"mailto:james.yang@utstar.com"><span
lang=3DSV>james.yang@utstar.com</span></a> <span =
lang=3DSV><o:p></o:p></span></p>

<p class=3DMsoNormal><i><font size=3D3 face=3D"Times New Roman"><span
style=3D'font-size:12.0pt;font-style:italic'>T. Russell =
Hsing</span></font></i>, <st1:place
w:st=3D"on"><st1:City w:st=3D"on">Telcordia</st1:City>, =
<st1:country-region =
w:st=3D"on">USA</st1:country-region></st1:place>,<font
color=3Dblue><span style=3D'color:blue'> <a =
href=3D"mailto:thsing@telcordia.com">thsing@telcordia.com</a></span></fon=
t><font
size=3D2><span style=3D'font-size:11.0pt'> <o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;letter-spacing:
-.1pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><b><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;letter-spacing:
-.1pt;font-weight:bold'>IMPORTANT =
DATES:<o:p></o:p></span></font></b></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;letter-spacing:
-.1pt'>Workshop Proposals Submission
Deadline:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;
6<sup>th</sup> &nbsp;June, 2006<o:p></o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'text-align:justify;text-justify:inter-ideograph'><font
size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;letter-spacing:
-.1pt'>Workshops:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
24<sup>th</sup> and 28<sup>th</sup> October, =
2006<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt;letter-spacing:-.1pt'>We look forward to your =
submissions.</span></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

</div>

</body>

</html>

------=_NextPart_000_0197_01C67E59.FA824BB0--



--===============0051010368==
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

--===============0051010368==--





From manet-bounces@ietf.org Tue May 23 06:47:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiUPI-0001s0-66; Tue, 23 May 2006 06:46:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiUPG-0001rF-Dh
	for manet@ietf.org; Tue, 23 May 2006 06:46:30 -0400
Received: from web34711.mail.mud.yahoo.com ([209.191.68.160])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FiUG8-00008a-J2
	for manet@ietf.org; Tue, 23 May 2006 06:37:10 -0400
Received: (qmail 51360 invoked by uid 60001); 23 May 2006 10:37:03 -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=Bshaq4ELF0XAiY+pT7SagSegayH6gG59FEEpk6Qf29j0lN1tPo1VfcUmmBBLQuP4OVCcj3D9u05En09DGOtwwzoj6ECY3LUJYCdWdl3t2ZKN9xgHg1Tc75KOXiB5oNFWFsUohtqT0GzXz15AQtQ5rfG+3BUZG4utkuDfNfECjQ8=
	; 
Message-ID: <20060523103703.51358.qmail@web34711.mail.mud.yahoo.com>
Received: from [62.135.105.86] by web34711.mail.mud.yahoo.com via HTTP;
	Tue, 23 May 2006 03:37:03 PDT
Date: Tue, 23 May 2006 03:37:03 -0700 (PDT)
From: Hossam El-Moshrify <hossamrashad@yahoo.com>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [manet] need help in AODV
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1604663851=="
Errors-To: manet-bounces@ietf.org

--===============1604663851==
Content-Type: multipart/alternative; boundary="0-1237094959-1148380623=:48500"
Content-Transfer-Encoding: 8bit

--0-1237094959-1148380623=:48500
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

dear all ,
  iam hossam studyin for my Master study iam now in thesis about 
AODV , really i didnt find good point to start from it & also cant find simulation file good for starting because iam new in NS2 ,, anyone pls can you help me , need good TCL file to begin with my thesis  & good point to start with it thanks so much for your help
  Eng. Hossam El-Moshrify
  Senoir Network Engineer in CAIRO International Airport
  Tech. Manager in ITplus4U Group
  hossam@ITplus4U.com
   

		
---------------------------------
Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls.  Great rates starting at 1&cent;/min.
--0-1237094959-1148380623=:48500
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>dear all ,</div>  <div>iam hossam studyin for my Master study iam now in thesis about <BR>AODV , really i didnt find good point to start from it &amp; also cant find simulation file good for starting because iam new in NS2 ,, anyone pls can you help me , need good TCL file to begin with my thesis&nbsp; &amp; good point to start with it thanks so much for your help</div>  <div>Eng. Hossam El-Moshrify</div>  <div>Senoir Network Engineer in CAIRO International Airport</div>  <div>Tech. Manager in ITplus4U Group</div>  <div><A href="mailto:hossam@ITplus4U.com">hossam@ITplus4U.com</A></div>  <div>&nbsp;</div><p>
		<hr size=1>Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. <a href="http://us.rd.yahoo.com/mail_us/taglines/postman7/*http://us.rd.yahoo.com/evt=39666/*http://messenger.yahoo.com"> Great rates starting at 1&cent;/min.
--0-1237094959-1148380623=:48500--


--===============1604663851==
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

--===============1604663851==--




From manet-bounces@ietf.org Tue May 23 09:10:52 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiWdn-0002LE-Eq; Tue, 23 May 2006 09:09:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiWdl-0002L6-MR
	for manet@ietf.org; Tue, 23 May 2006 09:09:37 -0400
Received: from amber.crhc.uiuc.edu ([130.126.143.254])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiWdk-0006uK-An
	for manet@ietf.org; Tue, 23 May 2006 09:09:37 -0400
Received: from [127.0.0.1] (chaos.crhc.uiuc.edu [130.126.143.233])
	by amber.crhc.uiuc.edu (8.13.6/8.13.6) with ESMTP id k4ND9BNv012971
	for <manet@ietf.org>; Tue, 23 May 2006 08:09:34 -0500
Message-ID: <44730976.1030704@crhc.uiuc.edu>
Date: Tue, 23 May 2006 08:09:10 -0500
From: Yih-Chun Hu <yihchun@crhc.uiuc.edu>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.49 on 130.126.143.254
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
Subject: [manet] Extension for VANET 2006,
 The Third ACM International Workshop on Vehicular Ad Hoc Networks
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org


Please accept my apologies if you receive multiple copies of this CFP. 
The deadline for VANET 2006 has been extended to June 5, 2006.


ANNOUNCEMENT and CALL FOR PAPERS

VANET 2006

The Third ACM International Workshop on Vehicular Ad Hoc Networks

In conjunction with ACM MobiCom 2006
September 29, 2006
Los Angeles, California, USA

Sponsored by ACM SIGMOBILE

http://www.sigmobile.org/workshops/vanet2006/

Important Dates:
Paper Submission Deadline: May 26, 2006 -- Extended to June 5, 2006
Notification of Acceptance: July 10, 2006
Camera-Ready Deadline: July 31, 2006

The goal of this workshop is to present and discuss recent advances
in the development of wireless vehicular ad hoc networking (VANET)
technologies.  Based on short- to medium-range communication systems
(vehicle-to-vehicle and vehicle-to-roadside), vehicular ad hoc
networks will enable vehicular safety applications including collision
and other safety warnings as well as non-safety applications like
real-time traffic congestion and routing information, high-speed
tolling, mobile infotainment, and many others.

The creation of high-performance, highly reliable, highly scalable,
and secure VANET technologies, though, presents an extraordinary
challenge to the wireless research community: a high degree of
communication reliability is needed under unfavorable channel
conditions.  Clearly, the specificity of vehicular ad hoc networks in
terms of mobility behavior and applications scenarios and requirements
makes VANET research an exciting and demanding application- and
purpose-driven sub-discipline of wireless networking.

Following the successes of VANET 2004 held in Philadelphia and VANET
2005 held in Cologne, Germany, the Third ACM International Workshop on
Vehicular Ad Hoc Networks will be held in Los Angeles, September 29,
2006, in conjunction with MobiCom 2006.

Authors are invited to submit papers presenting new research related
to the theory or practice of vehicular ad hoc networks (VANET).
All submissions must describe original research, not published or
currently under review for another workshop, conference, or
journal.  Areas of interest include, but are not limited to:

- Safety and non-safety applications
- Roadside-to-vehicle and vehicle-to-vehicle communication
- Communication protocol design
- Channel modeling
- Modulation and coding
- Power control and scalability issues
- Multi-channel organization and operation
- Security issues and countermeasures
- Privacy issues
- Network management
- Simulation frameworks & real-world testbeds

VANETs present a highly active field of research, development,
standardization and field trials.  Throughout the world, there are many
national/international projects in government, industry, and academia
devoted to VANETs, for example consortia like VSC (US), C2CCC (Europe)
and InternetITS (Japan), standardization efforts like IEEE 802.11p
(WAVE) and field trials like the large-scale Vehicle Infrastructure
Integration Program (VII) in the US.

Submission Instructions

All paper submissions will be handled electronically.  Papers must be
in PDF format, no longer than 10 pages (single- or double-column), in
font no smaller than 11 points, and must fit properly on US
Letter-sized paper (8.5 inch x 11 inch) with reasonable
margins.  Submitted papers will be judged based on their quality
through a double-blind review process, where the identities of the
authors are withheld from the reviewers.  Detailed instructions for
paper submission will be posted on the VANET 2006 web page at:
http://www.sigmobile.org/workshops/vanet2006/.

Please email questions related to paper submission or the technical
program to: vanet2006-pc-chairs@rz.uni-karlsruhe.de.


General Co-Chairs:
Wieland Holfelder, DaimlerChrysler RTNA, Inc.
David B. Johnson, Computer Science Department, Rice University

Technical Program Co-Chairs:
Victor Bahl, Microsoft Research
Hannes Hartenstein, Universitat Karlsruhe

Publicity Chair:
Yih-Chun Hu, University of Illinois at Urbana-Champaign

Web Chair:
Ken Laberteaux,Toyota Technical Center

Technical Program Committee (partial list):
Sharad Agarwal, Microsoft Research
Tracy Camp, Colorado School of Mines
Wai Chen, Telcordia Technologies
Chen-Nee Chua, Univ. of California Davis
Costas Constantinou, Univ. of Birmingham
Luca Delgrossi, DaimlerChrysler RTNA, Inc.
Eylem Ekici, Ohio State University
Tamer El-Batt, HRL Laboratories
Andreas Festag,	NEC
Jean-Pierre Hubaux, EPFL
Markus Jakobsson, Indiana Universtity
Daniel Jiang, DaimlerChrysler RTNA, Inc.
Timo Kosch, BMW Research and Technology
Ken Laberteaux, Toyota Technical Center
Martin Mauve, University of Duesseldorf
Paolo Santi, Italian Natl. Research Council
Raja Sengupta, Univ. of California Berkeley
Marc Torrent-Moreno, Universitat Karlsruhe


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



From manet-bounces@ietf.org Tue May 23 13:14:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FiaOw-0006Kw-L1; Tue, 23 May 2006 13:10:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FiaOu-0006Kr-NY
	for manet@ietf.org; Tue, 23 May 2006 13:10:32 -0400
Received: from wr-out-0506.google.com ([64.233.184.228])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FiaOr-0000V5-FR
	for manet@ietf.org; Tue, 23 May 2006 13:10:32 -0400
Received: by wr-out-0506.google.com with SMTP id i3so1289692wra
	for <manet@ietf.org>; Tue, 23 May 2006 10:10:29 -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=C51R0C4ShuhvzUWC6D0l3mqNenknjlnUFSQ6yZCzAPUsqcDvMG3Nuub8vc0D0o8FL9S6chMsquLfVHz1EZ+vBLEuP/m3N5VjgwKHyOvge3cVv+Qjwz3SM/bMIdxRiHN+Q8VFfX2bNRZDf6g11MeJ89e1RU7mef+Rq8+CReFccMA=
Received: by 10.65.97.16 with SMTP id z16mr36500qbl;
	Tue, 23 May 2006 10:10:28 -0700 (PDT)
Received: by 10.64.201.18 with HTTP; Tue, 23 May 2006 10:10:28 -0700 (PDT)
Message-ID: <c853c1da0605231010y5d2e9eb8k8b8d2c4fee279423@mail.gmail.com>
Date: Tue, 23 May 2006 19:10:28 +0200
From: "Ramzi Tka" <ramzi.tka@gmail.com>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168
Subject: [manet] Wimax mesh networks!!
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0453350682=="
Errors-To: manet-bounces@ietf.org

--===============0453350682==
Content-Type: multipart/alternative; 
	boundary="----=_Part_140747_887085.1148404228634"

------=_Part_140747_887085.1148404228634
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi everybody ,

I'm a Phd student. I have recently begun my thesis mainly on 802.16 mesh
networks.

I would be much obliged if you could give answers to some of my questions.

- If I have well understood 802.16-2004 standard, in mesh mode, all nodes
uses the same frame to schedule and transmit data using TDMA access. This
means that nodes signal could reach any node in the mesh network. In the
other hand, when resolving contention (control subframe), each node conside=
r
only its extended neighbourhood (2-hop neighbors) to set Next Xmt Time. Is
there any contradiction in this?

- Could we consider a case when nodes are geographically very espaced . But=
,
nodes could ensure radio connectivity with a set of neighbors. Do the
802.16-2004 specifications still applicable in this case (the use of a
single frame) ?

- What are the cretiria used to decide the establishment or not of neighbou=
r
links ?

- What the use of 3-Hop neighbourhood type in the Network Descriptor IE (
802.16-2004)



Thank you in advance

Ramzi TKA

------=_Part_140747_887085.1148404228634
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline



<p class=3D"MsoNormal"><span style=3D"" lang=3D"EN-GB">Hi everybody
,</span></p>

<p class=3D"MsoNormal"><span style=3D"" lang=3D"EN-GB">I'm a Phd
student. I have recently begun my thesis mainly on 802.16 mesh networks. </=
span></p>

<p class=3D"MsoNormal" style=3D""><span style=3D"" lang=3D"EN-GB">I would b=
e much obliged if you could
give answers to some of my questions.</span><span style=3D"font-size: 10pt;=
 font-family: TimesNewRomanPS-BoldMT;" lang=3D"EN-GB"></span></p>

<p class=3D"MsoNormal"><span style=3D"" lang=3D"EN-GB">- If I have
well understood 802.16-2004 standard, in mesh mode, all nodes uses the same
frame to schedule and transmit data using TDMA access. This means that node=
s
signal could reach any node in the mesh network. In the other hand, when
resolving contention (control subframe), each node consider only its extend=
ed
neighbourhood (2-hop neighbors) to set Next Xmt Time. Is there any
contradiction in this?</span></p>

<p class=3D"MsoNormal"><span style=3D"" lang=3D"EN-GB">- Could we
consider a case when nodes are geographically very espaced . But, nodes cou=
ld
ensure radio connectivity with a set of neighbors. Do the 802.16-2004
specifications still applicable in this case (the use of a single frame) ?<=
/span></p>

<p class=3D"MsoNormal"><span style=3D"" lang=3D"EN-GB">- What are
the cretiria used to decide the establishment or not of neighbour links ?</=
span></p>

<p class=3D"MsoNormal"><span style=3D"" lang=3D"EN-GB">- What the
use of 3-Hop neighbourhood type in the Network Descriptor IE (802.16-2004)<=
/span></p>

<p class=3D"MsoNormal"><span style=3D"" lang=3D"EN-GB">&nbsp;</span></p>

<p class=3D"MsoNormal"><span style=3D"" lang=3D"EN-GB">Thank you
in advance</span></p>

<p class=3D"MsoNormal"><span style=3D"" lang=3D"EN-GB">Ramzi TKA</span></p>


------=_Part_140747_887085.1148404228634--


--===============0453350682==
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

--===============0453350682==--




From manet-bounces@ietf.org Wed May 24 02:46:39 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fin7W-0006Cf-Mt; Wed, 24 May 2006 02:45:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fin7Q-0006Br-QD
	for manet@ietf.org; Wed, 24 May 2006 02:45:20 -0400
Received: from i4mail.informatik.rwth-aachen.de ([137.226.12.21])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fimzo-00050B-Pt
	for manet@ietf.org; Wed, 24 May 2006 02:37:33 -0400
Received: from i4mail (i4mail.informatik.rwth-aachen.de [137.226.12.21])
	by i4mail.informatik.rwth-aachen.de (Postfix) with ESMTP id 2F0761849A
	for <manet@ietf.org>; Wed, 24 May 2006 08:37:23 +0200 (CEST)
Received: from bender.informatik.rwth-aachen.de ([137.226.12.211])
	by i4mail.informatik.rwth-aachen.de (MailMonitor for SMTP v1.2.2 ) ;
	Wed, 24 May 2006 08:37:23 +0200 (CEST)
Message-ID: <4473FF23.3050709@i4.informatik.rwth-aachen.de>
Date: Wed, 24 May 2006 08:37:23 +0200
From: Martin Wenig <wenig@i4.informatik.rwth-aachen.de>
User-Agent: Thunderbird 1.5.0.2 (X11/20060411)
MIME-Version: 1.0
To: manet@ietf.org
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Subject: [manet] CFP -- MSPE 2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

 Our apologies if you have received multiple copies

*******************************************************************
             MSPE'06, 1st international Workshop on
 	  Mobile Services and Personalized Environments

              RWTH Aachen University, Aachen, Germany
 			  November 16-17, 2006

 		  http://www.mspe.rwth-aachen.de/
*******************************************************************

The first international Workshop on Mobile Services and Personalized
Environments (MSPE'06) focuses on recent research results on mobile
computer systems.

For this workshop, authors are invited to submit full papers presenting
new research related to the application of mobile communication
technologies to enable mobile services and facilitate personalized
environments in a mobile context. All submissions must describe original
research, not published nor currently under review for another
conference or journal.

The workshop will include two invited talks.

Areas of interest include, but are not limited to:

    * Adaptive middleware for pervasive systems
    * Context and location aware applications
    * Cross Layer Design of Access Systems for Multimedia Transmission,
Channel Feedback
    * Fixed and nomadic wireless internet access
    * Hop-by-Hop Video Quality Optimization, Loss Delay Trade off
regarding Video Quality
    * Location-based services and tracking
    * Mobile ad hoc networks, wireless mesh networks
    * Mobile service discovery and service provisioning
    * Mobile Multimedia (QoS, Mobile Television, multimedia streaming)

    * Multi-user conflicts in Personalized Environments
    * Reconfigurability of Personalized Environments (smart homes)
    * Strategies for service migration
    * Toolkits, development environments, case studies, and test beds
for ubiquitous computing
    * User profile management
    * Mobile Web Services (discovery, composition, orchestration, and
choreography)
    * Web service based grid computing


Submission Guidelines

It is planned to publish the proceedings at Springer's LNCS series.
(Approval pending)

For the submission format of your full paper, we strongly prefer, but do
not require strict adherence to the LNCS format. However, the final
paper must be in strict LNCS format, the number of LNCS pages must not
be larger than 12, and it must be provided according to the LNCS
guidelines, or it cannot be included in the workshop proceedings. The
LNCS format is quite different from plain A4, so to limit your
reformatting effort, we strongly suggest you also provide the submitted
paper in LNCS format. Please refer to Springer's author guidelines for
LNCS papers.

All papers will be reviewed by the technical program committee members.
Accepted papers will appear in the workshop proceedings. Authors are
required to attend the workshop and present their paper.

For questions regarding paper submission or general questions regarding
the organization of the workshop contact iwmspe@i4.informatik.rwth-aachen.de



-- 
---
* Dipl.-Inform. Martin Wenig
* RWTH Aachen University
* Computer Science Department
* Informatik 4 (Communication and Distributed Systems)
* Ahornstr. 55, D-52074 Aachen, Germany
* Tel.: +49 (241) 80-21416
* Fax:  +49 (241) 80-22220
* EMail: wenig@i4.informatik.rwth-aachen.de


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



From manet-bounces@ietf.org Wed May 24 04:33:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fiona-0001ua-GU; Wed, 24 May 2006 04:32:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FionY-0001t3-WC
	for manet@ietf.org; Wed, 24 May 2006 04:32:57 -0400
Received: from bay121-f23.bay121.hotmail.com ([207.46.10.103] helo=hotmail.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FionX-0001xp-O7
	for manet@ietf.org; Wed, 24 May 2006 04:32:56 -0400
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	Wed, 24 May 2006 01:32:55 -0700
Message-ID: <BAY121-F23471BC3742D4DAA6946E8FB980@phx.gbl>
Received: from 207.46.10.123 by by121fd.bay121.hotmail.msn.com with HTTP;
	Wed, 24 May 2006 08:32:53 GMT
X-Originating-IP: [193.194.92.58]
X-Originating-Email: [dj_moussaoui@hotmail.com]
X-Sender: dj_moussaoui@hotmail.com
In-Reply-To: <E1FiZIr-0001Rb-Py@megatron.ietf.org>
From: "Djilali MOUSSAOUI" <dj_moussaoui@hotmail.com>
To: manet@ietf.org
Bcc: 
Date: Wed, 24 May 2006 08:32:53 +0000
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
X-OriginalArrivalTime: 24 May 2006 08:32:55.0274 (UTC)
	FILETIME=[A779A4A0:01C67F0C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: [manet] AODV, DSDV QoS  extension for NS-2
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hello,
Please, I need to implement the the extesion of AODV and DSDV to make 
comparaison in QoS parameters, if you have any information or idea

Best regards...

_________________________________________________________________
Gardez le contrôle grâce à la protection contre les fenêtres pop-up 
articulée sur la technologie brevetée Microsoft SmartScreen 
http://join.msn.com/?pgmarket=fr-ca&page=features/popup Commencez dès 
maintenant à profiter de tous les avantages de MSN Premium et obtenez les 
deux premiers mois GRATUITS*.


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



From manet-bounces@ietf.org Wed May 24 10:07:43 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fiu0e-0006lb-Fp; Wed, 24 May 2006 10:06:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fiu0c-0006kl-Uj
	for manet@ietf.org; Wed, 24 May 2006 10:06:46 -0400
Received: from smtp1.clb.oleane.net ([213.56.31.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fiu0a-0000UT-HK
	for manet@ietf.org; Wed, 24 May 2006 10:06:46 -0400
Received: from Pavillonquatre ([194.3.133.88]) 
	by smtp1.clb.oleane.net with ESMTP id k4OE6dSK013626
	for <manet@ietf.org>; Wed, 24 May 2006 16:06:41 +0200
Message-Id: <200605241406.k4OE6dSK013626@smtp1.clb.oleane.net>
From: "Chantal Ladouce" <chantal.ladouce@upperside.fr>
To: <manet@ietf.org>
Date: Wed, 24 May 2006 16:06:38 +0200
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcZ/O0X8JQ3JHyVnT6qm4mZkwNq9fg==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Subject: [manet] WiMAX Summit 2007 - Call for proposals
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0131701534=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0131701534==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0310_01C67F4C.09FC9CB0"

This is a multi-part message in MIME format.

------=_NextPart_000_0310_01C67F4C.09FC9CB0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

The fourth edition of the WiMAX Summit will stand in Paris next February 27
to March 02, 2007.

A  <http://www.upperside.fr/wimax2007/wimax2007cfp.htm> call for proposals
has been launched and will close on July 15. Members of the scientific
committee will examine the proposals submitted. 

 

All details at:

 <http://www.upperside.fr/wimax2007/wimax2007intro.htm>
http://www.upperside.fr/wimax2007/wimax2007intro.htm

 


------=_NextPart_000_0310_01C67F4C.09FC9CB0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>The fourth edition of the <b><u><span
style=3D'font-weight:bold'>WiMAX Summit</span></u></b> will stand in =
<st1:place
w:st=3D"on"><st1:City w:st=3D"on">Paris</st1:City></st1:place> next =
February 27 to
March 02, 2007.</span></font><font size=3D1><span lang=3DEN-GB =
style=3D'font-size:
9.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>A </span></font><font size=3D1><span =
style=3D'font-size:
9.0pt'><a href=3D"http://www.upperside.fr/wimax2007/wimax2007cfp.htm"
title=3D"http://www.upperside.fr/wimax2007/wimax2007cfp.htm"><font =
color=3Dblack
face=3DArial =
title=3D"http://www.upperside.fr/wimax2007/wimax2007cfp.htm"><span
lang=3DEN-GB style=3D'font-family:Arial;color:black'>call for =
proposals</span></font></a></span></font><font
size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:9.0pt;font-family:Arial'>
has been launched and will close on July 15. Members of the scientific
committee will examine the proposals submitted. </span></font><font =
size=3D1><span
lang=3DEN-GB style=3D'font-size:9.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:9.0pt'>&nbsp;<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'>All details at:</span></font><font =
size=3D1><span
lang=3DEN-GB style=3D'font-size:9.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span =
style=3D'font-size:9.0pt;
font-family:Arial'><a
href=3D"http://www.upperside.fr/wimax2007/wimax2007intro.htm"
title=3D"http://www.upperside.fr/wimax2007/wimax2007intro.htm"><span =
lang=3DEN-GB>http://www.upperside.fr/wimax2007/wimax2007intro.htm</span><=
/a></span></font><font
size=3D1><span lang=3DEN-GB =
style=3D'font-size:9.0pt'><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D1 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
9.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0310_01C67F4C.09FC9CB0--



--===============0131701534==
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

--===============0131701534==--





From manet-bounces@ietf.org Thu May 25 08:59:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FjFQE-0003y3-NM; Thu, 25 May 2006 08:58:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FjFQD-0003xt-B0
	for manet@ietf.org; Thu, 25 May 2006 08:58:37 -0400
Received: from web25708.mail.ukl.yahoo.com ([217.12.10.180])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FjFQ7-0007Gn-Uk
	for manet@ietf.org; Thu, 25 May 2006 08:58:37 -0400
Received: (qmail 6729 invoked by uid 60001); 25 May 2006 12:58:30 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.fr;
	h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=QK7LUqTk/pF65DLw5uz+lYWJIbzeiJ/WjQS/MIRQKptoYwtlxUnoEs+GUFnVwvu5sARNnKwa1XsSNmBqKF3rDTjm2tD8xBWQ+nWFpteCFEN42//STdPtRKMGOtQMzErgtxHp4VvfTdGrx2MWalLvhUqGY5foKH8pChcTk1OqT2I=
	; 
Message-ID: <20060525125830.6727.qmail@web25708.mail.ukl.yahoo.com>
Received: from [193.194.94.24] by web25708.mail.ukl.yahoo.com via HTTP;
	Thu, 25 May 2006 14:58:30 CEST
Date: Thu, 25 May 2006 14:58:30 +0200 (CEST)
From: dendene elhadi <dendene2004@yahoo.fr>
To: manet@ietf.org
In-Reply-To: <E1FivmS-0008Sm-BI@megatron.ietf.org>
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: [manet] Energy management in IEEE802.11
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0230766802=="
Errors-To: manet-bounces@ietf.org

--===============0230766802==
Content-Type: multipart/alternative; boundary="0-868901288-1148561910=:6339"
Content-Transfer-Encoding: 8bit

--0-868901288-1148561910=:6339
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

I want to know about the determination of the distance between two nodes using IEEE802.11 standard, does it possible?
   
  Best regards. 

		
---------------------------------
 Yahoo! Mail réinvente le mail ! Découvrez le nouveau Yahoo! Mail et son interface révolutionnaire.
--0-868901288-1148561910=:6339
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-US style="mso-ansi-language: EN-US"><FONT size=3><FONT face="Times New Roman">I want to know about the determination of the distance between two nodes using IEEE802.11 standard, does it possible?</FONT></FONT></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-US style="mso-ansi-language: EN-US"><?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p><FONT face="Times New Roman" size=3>&nbsp;</FONT></o:p></SPAN></div>  <div class=MsoNormal style="MARGIN: 0cm 0cm 0pt"><SPAN lang=EN-US style="mso-ansi-language: EN-US"><FONT size=3><FONT face="Times New Roman">Best regards. </FONT></FONT></SPAN></div><p>
		<hr size="1"> 
<b>Yahoo! Mail réinvente le mail !</b> Découvrez le <a href="http://fr.rd.yahoo.com/evt=40577/*http://fr.promotions.yahoo.com/mail/nouveaumail.html 
">nouveau Yahoo! Mail</a> et son interface révolutionnaire.

--0-868901288-1148561910=:6339--


--===============0230766802==
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

--===============0230766802==--




From manet-bounces@ietf.org Sun May 28 08:07:07 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FkK1J-0002Hz-KJ; Sun, 28 May 2006 08:05:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FkK1I-0002Ha-4G
	for manet@ietf.org; Sun, 28 May 2006 08:05:20 -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 1FkK1H-00010a-MR
	for manet@ietf.org; Sun, 28 May 2006 08:05:20 -0400
Received: from isis.lip6.fr ([132.227.60.2])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FkJwv-0007Ga-DN
	for manet@ietf.org; Sun, 28 May 2006 08:00:51 -0400
Received: from tibre.lip6.fr (tibre.lip6.fr [132.227.74.2])
	by isis.lip6.fr (8.13.6/jtpda-5.4+mv) with ESMTP id k4SC0kkP014394
	for <manet@ietf.org>; Sun, 28 May 2006 14:00:46 +0200
X-pt: isis.lip6.fr
Received: from [127.0.0.1] (sphinx [132.227.74.253])
	by tibre.lip6.fr (8.13.3p0/8.13.3) with ESMTP id k4SC289C018298
	for <manet@ietf.org>; Sun, 28 May 2006 14:02:10 +0200 (MEST)
Message-ID: <447990F7.2060301@lip6.fr>
Date: Sun, 28 May 2006 09:00:55 -0300
From: Marcelo Dias de Amorim <Marcelo.Amorim@lip6.fr>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: fr, en
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2
	(isis.lip6.fr [132.227.60.2]);
	Sun, 28 May 2006 14:00:46 +0200 (CEST)
X-Scanned-By: isis.lip6.fr
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by isis.lip6.fr id
	k4SC0kkP014394
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2beba50d0fcdeee5f091c59f204d4365
Subject: [manet] CFP 3rd ACM International Workshop on Performance
 Evaluation of Wireless Ad Hoc, Sensor, and Ubiquitous Networks
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Please apologize for any duplicates.


                    !!! * Deadline approaching * !!!

-------------------------------------------------------------------
                  CALL FOR PAPERS: ACM* PE-WASUN 2006
-------------------------------------------------------------------

     3rd ACM* International Workshop on Performance Evaluation of
           Wireless Ad Hoc, Sensor, and Ubiquitous Networks
                 http://ares.insa-lyon.fr/pe-wasun06
           Torremolinos, Malaga, SPAIN, October 2-6, 2006

           Jointly with the 9th ACM/IEEE * MSWiM Symposium
                  http://www.cs.unibo.it/mswim2006


*ACM Pending upon Approval
-------------------------------------------------------------------

IMPORTANT: Full paper due:         June 10th, 2006
-------------------------------------------------------------------

Scope:

  Wireless ad hoc, sensor, along with ubiquitous networks have recently
  witnessed their fastest growth period ever in history, and this trend
  is likely to continue for the foreseeable future. However, as such
  networks become increasingly complex, performance modeling and
  evaluation will play a crucial part in their design process to ensure
  their successful deployment and exploitation in practice.

  This workshop brings together scientists, engineers, and
  practitioners to share and exchange their experiences, discuss
  challenges, and report state-of-the-art and in-progress research on
  all aspects of wireless ad hoc, sensor, and ubiquitous networks with
  a specific emphasis on their performance evaluation and analysis.

Topics of interest include, but are not limited to:

- Probabilistic or predictive performance models and analysis of ad
   hoc, sensor, pervasive and ubiquitous networks
- RF channel capacity modeling and analysis
- Traffic models for ad hoc, sensor networks
- Mobility modeling and management
- Analytical modeling
- Simulation methods
- Tracing and trace analysis
- Performance measurement, monitoring and evaluation tools for ad hoc,
   sensor and ubiquitous networks
- Software tools for automatic network performance and evaluation
- Network performance improvements by optimization algorithms
- Energy-efficient protocols for ad hoc and sensor networks
- Wireless mesh networks
- Case studies demonstrating the role of performance evaluation in the
   design of ad hoc, sensor, and ubiquitous networks

Workshop Co-Chairs:

  Lichun Bao              University of California, Irvine, USA
  Isabelle Guerin Lassous INRIA/CITI, Lyon, France

Technical Program Committee Members:

  Khalid Al-Begain        Univ. of Glamorgan, UK
  Prithwish Basu          BBN Technologies, USA
  Paolo Bellavista        University of Trento, Italy
  Brahim Bensaou          Hong Kong University of Science and
                          Technology, HK
  Fernando Boavida        University of Coimbra, Portugal
  Luciano Bononi          University of Bologna, Italy
  Azzedine Boukerche      University of Ottawa, Canada
  Michele Colajanni       University of Modena, Italy
  J.J. Garcia-Luna-Aceves University of California, Santa Cruz, USA
  Mario Gerla             UCLA, USA
  Vittoria Gianuzzi       University of Genova, Italy
  Ben Liang               University of Toronto, Canada
  Zhen Liu                IBM T. J. Watson Research Center, USA
  Bernard Mans            Macquarie University, Australia
  Pietro Manzoni          Politechnic University of Valencia, Spain
  Kenichi Mase            Niigata University, Japan
  Jelena Misic            University of Manitoba (Canada)
  Mohamed Naimi           University of Cergy-Pontoise, France
  Sotiris Nikoletseas     Computer Technology Institute, Greece
  Mirela Notare           Barddal University, Brazil
  Mohamed Ould-Khaoua     University of Glasgow, UK
  Guy Pujolle             Universit=E9 Paris 6, France
  Pedro M. Ruiz           University of Murcia, Spain
  Marco Spohn             Federal University of Campina Grande, Brazil
  Mineo Takai             University of California, Los Angeles, USA
  Damla Turgut            University of Central Florida, USA
  Fabrice Valois          Insa de Lyon, France


Publicity Chair:
  Marcelo Dias de Amorim  CNRS/LIP6, France

-------------------------------------------------------------------------
Paper Submission:

  High-quality original papers are solicited. Papers must be
  unpublished and must not be submitted for publication elsewhere. All
  papers will be reviewed by Technical Program Committee members and
  other experts active in the field to ensure high quality and relevance
  to the conference. Accepted papers will appear on the workshop
  proceedings that will be published by ACM press.

  At least one of the authors of accepted papers must attend the
  conference to present his paper.

  Paper should be submitted on PE-WASUN web site:
  http://ares.insa-lyon.fr/pe-wasun06/authors.html. Paper length should
  be no mo re than 10 pages, double column, ACM style including tables
  and figures. A template for ACM SIG Proceedings style (LaTeX2e and MS
  Word) ca n be found at
  http://www.acm.org/sigs/pubs/proceed/template.html. Only Postscript
  and PDF formats are accepted.

  A special issue will be planned in a scholarly journal to include
  selected high-quality papers from the workshop.

-------------------------------------------------------------------------
Important Dates

  Full paper due:           June 10th, 2006
  Acceptance notification:  July 10th, 2006
  Camera ready due:         TBA



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



From manet-bounces@ietf.org Mon May 29 11:00:31 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FkjCv-00020F-NZ; Mon, 29 May 2006 10:59:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FkjCu-000209-Gi
	for manet@ietf.org; Mon, 29 May 2006 10:59:00 -0400
Received: from wr-out-0506.google.com ([64.233.184.236])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FkjCr-0004h9-3Q
	for manet@ietf.org; Mon, 29 May 2006 10:59:00 -0400
Received: by wr-out-0506.google.com with SMTP id i7so896759wra
	for <manet@ietf.org>; Mon, 29 May 2006 07:58:56 -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=ppp7wHRWDMXxTdxJu/GZHh+Pmp5uu41cO3Y0zOBNMo6oihE8DEM+fmnBgoooRPARWEQeN9gnYJeHWED+QbRpasBNOoi343HrPdFlGQT/IHejRu6p3pQ3OencQV/Xu3iSQxAsp6ykNLlslW85Ef2l8Ey+Pd88KFzmAShl4m0WRJQ=
Received: by 10.64.48.20 with SMTP id v20mr3166589qbv;
	Mon, 29 May 2006 07:58:56 -0700 (PDT)
Received: by 10.65.244.1 with HTTP; Mon, 29 May 2006 07:58:56 -0700 (PDT)
Message-ID: <edf34f450605290758w33ee8566lb1a9a79ab390d07@mail.gmail.com>
Date: Mon, 29 May 2006 09:58:56 -0500
From: "Hang Su" <hangsu@gmail.com>
To: manet@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.2 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Subject: [manet] The interference of two transceivers in a single terminal
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0941331079=="
Errors-To: manet-bounces@ietf.org

--===============0941331079==
Content-Type: multipart/alternative; 
	boundary="----=_Part_119665_6006231.1148914736679"

------=_Part_119665_6006231.1148914736679
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi all,

I am currently studying multi-channel MAC protocols. Let us assume that in
each node there's two sets of transceivers that can work simultaneously. At
the same time slot, the two transceivers work over different channels (say,
5.21G-5.22G and 5.22G-5.23G). If the Transceiver #1 is transmitting while
the Transceiver #2 is receiving, how is the interference? Is there any
effective solution to resolve this kind of problem? Any help will be
appreciated.

Thanks,
Hs

------=_Part_119665_6006231.1148914736679
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi all,<br><br>I am currently studying multi-channel MAC protocols. Let us =
assume that in<br>each node there's two sets of transceivers that can work =
simultaneously. At<br>the same time slot, the two transceivers work over di=
fferent channels (say,
<br>5.21G-5.22G and 5.22G-5.23G). If the Transceiver #1 is transmitting whi=
le<br>the Transceiver #2 is receiving, how is the interference? Is there an=
y<br>effective solution to resolve this kind of problem? Any help will be
<br>appreciated.<br><br>Thanks,<br>Hs<br>

------=_Part_119665_6006231.1148914736679--


--===============0941331079==
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

--===============0941331079==--




From manet-bounces@ietf.org Tue May 30 05:20:32 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fl0NR-0007F0-Ga; Tue, 30 May 2006 05:19:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fl0NQ-0007EK-0y
	for manet@ietf.org; Tue, 30 May 2006 05:19:00 -0400
Received: from smtp.eurecom.fr ([193.55.113.210])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fl0NM-0005DK-9P
	for manet@ietf.org; Tue, 30 May 2006 05:18:59 -0400
Received: from monza.eurecom.fr (localhost [127.0.0.1])
	by smtp.eurecom.fr (8.13.1/8.13.1) with ESMTP id k4U9IkfE024736
	for <manet@ietf.org>; Tue, 30 May 2006 11:18:47 +0200 (CEST)
Received: from [172.17.20.17] (kim.eurecom.fr [172.17.20.17])
	by monza.eurecom.fr (Postfix) with ESMTP id C40CF3C35A
	for <manet@ietf.org>; Tue, 30 May 2006 11:18:46 +0200 (MEST)
Message-ID: <447C0DF5.2080503@eurecom.fr>
Date: Tue, 30 May 2006 11:18:45 +0200
From: Jerome Haerri <Jerome.Haerri@eurecom.fr>
User-Agent: Thunderbird 1.5.0.2 (X11/20060420)
MIME-Version: 1.0
To: manet@ietf.org
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by smtp.eurecom.fr id
	k4U9IkfE024736
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
Subject: [manet] Call for Papers Special Track on Broadband Wireless Access
 for Users on the Road (ST-BWA-2006)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Our Apologies for duplicate postings.

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

CALL FOR PAPERS - ST-BWA 2006

Special Track on Broadband Wireless Access for Users on the Road
(http://m2usic.mmu.edu.my/main/sp-track-bwa.html)

in conjunction with M2USIC-2006 (http://m2usic.mmu.edu.my/main/index.html=
)

PJ Hilton Hotel, Petaling Jaya, Malaysia

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


SUBJECT AND SCOPE
-----------------
The demand for broadband wireless access (BWA) has increased
tremendously over the last few years. The provision of BWA on the road
may involve several technologies such as vehicle-to-infrastructure
communications, inter-vehicular communications (IVC), vehicle-to-vehicle
communications (V2V) or vehicular ad-hoc network (VANET). IVC enables
local information, such as road condition, to be disseminated to
surrounding vehicles. Numerous emerging applications may be offered to
users on the road and provide a wide array of benefits to our society by
enforcing a higher degree of safety, productivity, and convenience.

These emerging applications are not well supported currently.  Numerous
research challenges need to be addressed in order for BWA for users on
the road to be widely deployed. The combination of unique features of
IVC applications and networking opens new opportunities for many
interesting research areas. The vehicular ad-hoc networking among cars
has different characteristics from other ad-hoc networking problems. For
example, cars may frequently move in cluster which is different from the
random way point assumption in the study of mobile ad-hoc network.

The purpose of this special track is to showcase the variety of research
being conducted in BWA for users on the road and survey the
state-of-the-art in this field. Previously unpublished contributions to
the following areas are solicited:

=95 System/ Network Architectures
   =95 Access network
   =95 Vehicle-to-vehicle communications, IVC, VANET
   =95 Inter-working

=95 BWA Applications for Users on the Roads
   =95 Vehicular communications applications
   =95 Navigation safety applications
   =95 Vehicle data collection and harvesting
   =95 Intelligent Transport Systems (ITS)

=95 Wireless Access Technologies
   =95 Mesh networking, WiFi mesh, WiMax mesh
   =95 Single-radio, multi-radio, single-channel, multi-channel
   =95 Link and physical layer issues
   =95 Frequency planning or channel assignment
   =95 Network protocols and algorithms, clustering, routing, etc.
   =95 Cross-layer protocol design

=95 Signal Processing Techniques
   =95 Channel modeling and estimation for inter-vehicular channels
   =95 Modulation and coding methods for IVC
   =95 Equalization, synchronization, and receiver design
   =95 Adaptation techniques for detection and parameter estimation
   =95 Emerging technologies (MIMO/adaptive arrays, etc)

=95 APIs and Application Platforms
   =95 Service creation and management
   =95 Advanced API
   =95 Content distribution to vehicles

=95 Mobility Management
   =95 Mobile IP
   =95 AAA and Security

=95 Performance Analysis
   =95 Realistic vehicle movement simulation
   =95 Mobility modeling

=95 Network Management for IVC


IMPORTANT DATES
---------------
Manuscript Submission: July 2nd, 2006
Acceptance Notification: September 8th, 2006
Final Manuscript Due: October 8th, 2006

PAPER SUBMISSION
----------------
All papers are to be submitted following the standard IEEE format and
not exceed 6 single-spaced and two-column pages using at least 10 points
size type on A4 format. See full instructions for author guidelines and
paper submissions at the conference website.
Papers are to be submitted electronically on the conference website no=20
later than July 2nd 2006.


PROGRAM CO-CHAIRS
-----------------
Moh Lim Sim MMU, Malaysia
Teong Chee Chuah MMU, Malaysia


Program Committee
-----------------
Alain C. Houle Universit=E9 Sherbrooke , Canada
Andreas Kassler Karlstads Universitet, Sweden
Chai Kiat Yeo NTU, Singapore
Chor Min Tan BT Multimedia, Malaysia
Daniel Wong MUST, Malaysia
Eisuke Kudoh Tohoku Univ. , Japan
J=E9r=F4me Haerri Institut Eur=E9com , France
Kae-Hsiang Kwong Univ. of Strathclyde, UK
Maziar Nekovee BT Group, UK
Mooi Choo Chuah Lehigh Univ. , USA
M.Yusoff Alias MMU, Malaysia
Ren Fengyuan Tsinghua Univ. , China
Seng Chen Univ. of Southampton, UK.
Soon Xin Ng Univ. of Southampton, UK
Swee Keow Goo Univ. of Strathclyde , UK
Teck Meng Lim NTU, Singapore
Yen Choon Ching Christian-Albrechts-Univ. , Germany

ADDITIONAL INFORMATION
----------------------
Additional information about the workshop will be continuously
updated at the  ST-BWA 2006 website

http://m2usic.mmu.edu.my/main/sp-track-bwa.html

and on the M2USIC website

http://m2usic.mmu.edu.my/main/index.html

--=20
Jerome Haerri
Ph.D Candidate

Eurecom Institute
Mobile Communications Department
2229, Route des Cretes
B.P. 193
06904 Sophia-Antipolis Cedex
France

Home   : +33 (0)4 92 38 97 09
Office : +33 (0)4 93 00 81 76
Mob    : +33 (0)6 10 79 72 83

E-mail : jerome.haerri@eurecom.fr

Web    : http://www.eurecom.fr/people/haerri.en.htm


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



From manet-bounces@ietf.org Tue May 30 08:21:38 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fl3CO-0001FL-M9; Tue, 30 May 2006 08:19:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fl3CM-0001FF-Uw
	for manet@ietf.org; Tue, 30 May 2006 08:19:46 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fl3CK-00042V-1a
	for manet@ietf.org; Tue, 30 May 2006 08:19:46 -0400
Received: from ex1.ad.dcs.gla.ac.uk ([130.209.249.157]:43092)
	by mr1.dcs.gla.ac.uk with esmtp (Exim 4.42) id 1Fl3CJ-0007SJ-D8
	for manet@ietf.org; Tue, 30 May 2006 13:19:43 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 30 May 2006 13:19:17 +0100
Message-ID: <BED9D15F73EDDE48BF480604236A4560117062@ex1.ad.dcs.gla.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
Thread-Index: AcZlxbx8iOSvNfkUTRyLkeSW6R422QAACIzMAAAgo3MAAF/kTgAAG4FQAADVrOAHhegLIA==
References: <BED9D15F73EDDE48BF480604236A4560116E59@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5A@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5B@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5C@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5D@ex1.ad.dcs.gla.ac.uk>
	<BED9D15F73EDDE48BF480604236A4560116E5F@ex1.ad.dcs.gla.ac.uk>
From: "Mohamed Ould-Khaoua" <mohamed@dcs.gla.ac.uk>
To: <manet@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3a331e4a192f4d33f18e6f8376287cf6
Subject: [manet] CFP- ACM Workshop on Performance Monitoring, Measurement,
	and Evaluation of Heterogeneous Wireless and Wired Networks
	(PM2HW2N 2006)
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0716733964=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0716733964==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C683E3.55788D5C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C683E3.55788D5C
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

[Please accept our apologies if you receive multiple copies of this CFP]
-------------------------------------------------------------------------=
-----------------------------------------
=20
CALL FOR PAPERS
=20
ACM International Workshop on Performance Monitoring, Measurement,
and Evaluation of Heterogeneous Wireless and Wired Networks (PM2HW2N =
2006)
=20
http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html =
<http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html>=20
<http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html>=20
=20
To be held in conjunction with  ACM/IEEE MSWiM 2006
http://www.cs.unibo.it/mswim2006/ <http://www.cs.unibo.it/mswim2006/>=20
=20
October 2-6, 2006
Torremolinos, (Malaga), Spain
=20
=20
Scope:
Wireless networks, including ad hoc, sensor, along with ubiquitous, have =
witnessed=20
over the past few years their fastest growth period and have become =
increasingly complex.=20
Nonetheless, their performance evaluation and analysis have been =
conducted mostly through=20
software simulations. Very recently, some research efforts have been =
directed towards measuring=20
real-world commercial and experimental networks; constructing models =
based on real-world data=20
and using prototypes to more realistically and comprehensively evaluate =
the suggested solutions=20
and more specifically validate the assumptions and the conclusions =
reached via the simulation approach.
=20
The aim of this workshop is to bring together scientists, engineers, and =
practitioners to share and exchange=20
their experiences, discuss challenges, and report state-of-the-art and =
in-progress research on all aspects=20
of performance measurements, monitoring, and evaluation of heterogeneous =
wired and wireless mobile networks,=20
including, wireless ad hoc, sensor, and ubiquitous networks. Topics of =
interest include, but are not limited to:
=20
- Performance measurement, monitoring, and evaluation tools for =
heterogeneous wireless and wired networks
- Performance tools for ad hoc, sensor, and ubiquitous networks
- Tracing and trace analysis
- Discrete and continuous models
- Measurement-based performance modelling
- Measurement architectures and systems
- QoS monitoring and sampling
- Measurement-based optimisation of for heterogeneous wireless and wired =
networks
- Novel measurement tools of wireless networks
- Performance measurements of ad hoc, sensor, and ubiquitous networks
- Performance analysis and evaluation of mobile services
- Software tools for wireless network performance and evaluation
- Automatic performance analysis=20
- Performance of wireless and sensor devices
- Mobility modeling and management
- Prototype implementation of wireless/mobile networks and systems
- Techniques for prototyping wireless networks
- Validation through measurement and prototyping
- Probabilistic models for ad hoc, sensor, and ubiquitous networks
- Improvement in network performance through prototyping
- Performance tools for ad hoc, sensor and ubiquitous networks
- Performance and security issues in ad hoc, sensor, and ubiquitous =
networks
- Performance and power management control
- Case studies demonstrating the role of performance monitoring, =
measurement, and=20
evaluation in the design of ad hoc, sensor, and ubiquitous networks
-Applications of performance monitoring, measurement, and evaluation as =
a feedback to improve network QoS
=20

Workshop Co-Chairs:
M. Ould-Khaoua
University of Glasgow
UK=20
=20
B. Caminero
University of Castilla-La Mancha
Albacete (Spain)
=20
=20
Program Committee (in progress):
K. Al-Begain, Univ. of Glamorgan (UK)
A. Al-Dubai, Napier Univ. (UK)
N. Abu-Ghazaleh,  SUNY,Binghamton (USA)
I. Awan, Univ. of Bradford (UK)
A. Bermudez, University of Castilla-La Mancha (Spain)
L. Bononi, University of Bologna (Italy)
A. Boukerche, Univ. of Ottawa (Canada)
C.-C. Shen, Univeristy of Delaware (USA)
J.C. Cano, Technical University of Valencia (Spain)
C. Carrion, University of Castilla-La Mancha (Spain)
M. Colajanni, Univ. of Modena (Italy)
P. Cuenca, University of Castilla-La Mancha (Spain)
F.M. Delicado, University of Castilla-La Mancha (Spain)
E. Fleury, INSA de Lyon (France)
V. Gianuzzi, Univ. of Genova (Italy)
E. Karatza, Aristotle University of Thessaloniki (Greece)
A. Ksentini, University of Cergy-Pontoise (France)
P. Manzoni, Technical University of Valencia (Spain)
G. Min, Univ. of Bradford (UK)
M. Naimi, University of Cergy-Pontoise (France)
S. Nikoletseas, Computer Technology Institute (Greece)=20
M. S. M. Annoni Notare, Barddal Univ. (Brazil)
S. Olariu, Old Dominion Univ. (USA)
T. Olivares, University of Castilla-La Mancha (Spain)
L. Orozco-Barbosa, University of Castilla-La Mancha (Spain)
A. Passarella, Univ. Of Cambridge (UK)
Y. Pan, Georgia State Univ. (USA)
M. Perez-Malumbres, Miguel Hernandez University (Spain)
F. Quiles, University of Castilla-La Mancha (Spain)
P. Ruiz, University of Murcia (Spain)
J.L. Sanchez, University of Castilla-La Mancha (Spain)
M. S. Squillante, IBM T.J. Watson Research Center (USA)=20
A. Shahrabi, Glasgow Caledonian University (UK)
T. Miklos, Technical University of Budapest (Hungary)
S. Yoshida, Kyoto University (Japan)
J. Wu, Florida Atlantic University (USA)
A. Zomaya, Univ. of Sydney (Australia)
=20

Publicity Chair
M. S.-M. Annoni Notare
Barddal University, Florianopolis, SC=20
Brazil
  =20
=20
Paper Submission:
Authors are invited to submit manuscripts reporting original unpublished =
research and recent developments=20
in the topics related to the workshop. The length of the papers should =
not exceed 10 single-spaced pages,=20
formatted using the ACM style (LaTex2e  and MS Word templates can be =
found at <http://www.acm.org/sigs/pubs/proceed/template.html =
<http://www.acm.org/sigs/pubs/proceed/template.html> >).

Papers should be submitted electronically in PDF format (or postscript) =
by sending it as an e-mail attachment to=20
mohamed@dcs.gla.ac.uk <mailto:mohamed@dcs.gla.ac.uk>  or =
blanca@dsi.uclm.es <mailto:blanca@dsi.uclm.es> . All papers will be peer =
reviewed and the comments will=20
be provided to the authors.
=20
Accepted papers will appear in the workshop proceedings and a special =
issue will be planned in a scholarly=20
journal to include selected high-quality papers from the workshop.
=20
Important Dates:
Submission Deadline: 10 June 2006=20
Author Notification: 10 July 2006


------_=_NextPart_001_01C683E3.55788D5C
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML =
DIR=3Dltr><HEAD></HEAD><BODY>=0A=
<DIV id=3DidOWAReplyText48187 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2><FONT =0A=
face=3D"Times New Roman">[Please accept our apologies if you receive =
multiple =0A=
copies of this =0A=
CFP]<BR>-----------------------------------------------------------------=
-------------------------------------------------</FONT></DIV></DIV>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV dir=3Dltr>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>CALL FOR PAPERS</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman" size=3D3>ACM International Workshop =
on =0A=
Performance Monitoring, Measurement,<BR>and Evaluation of Heterogeneous =
Wireless =0A=
and Wired Networks (PM2HW2N 2006)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.dcs.gla.ac.uk/~mohamed/pmmh06/pmmh06.html</FONT></A></D=
IV>=0A=
<DIV><A =
href=3D"http://www.dcs.gla.ac.uk/~mohamed/wasun05/pe-wasun05.html"><FONT =0A=
face=3D"Times New Roman"></FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">To be held in conjunction with&nbsp; =
ACM/IEEE =0A=
MSWiM 2006<BR></FONT><A href=3D"http://www.cs.unibo.it/mswim2006/"><FONT =0A=
face=3D"Times New =
Roman">http://www.cs.unibo.it/mswim2006/</FONT></A><BR><FONT =0A=
face=3D"Times New Roman">&nbsp;<BR>October 2-6, 2006</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Torremolinos, (Malaga), =0A=
Spain<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Scope:<BR>Wireless networks, =
including ad hoc, =0A=
sensor, along with ubiquitous, have witnessed <BR>over the past few =
years their =0A=
fastest growth period and have become increasingly complex. =
<BR>Nonetheless, =0A=
their performance evaluation and analysis have been conducted mostly =
through =0A=
<BR>software simulations. Very recently, some research efforts have been =0A=
directed towards measuring </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">real-world commercial and =
experimental =0A=
networks; constructing models based on real-world data </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and using prototypes to more =
realistically and =0A=
comprehensively evaluate the suggested solutions </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">and more specifically validate the =
assumptions =0A=
and the conclusions reached via the simulation =
approach.<BR>&nbsp;<BR>The aim of =0A=
this workshop is to bring together scientists, engineers, and =
practitioners to =0A=
share and exchange </FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">their experiences, discuss =
challenges, and =0A=
report state-of-the-art and in-progress research on all aspects =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">of performance measurements, =
monitoring, and =0A=
evaluation of heterogeneous wired and wireless mobile networks, =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">including, wireless ad hoc, sensor, =
and =0A=
ubiquitous networks. Topics of interest&nbsp;include, but are not =
limited =0A=
to:<BR>&nbsp;<BR>- Performance measurement, monitoring, and evaluation =
tools for =0A=
heterogeneous wireless and wired networks<BR>- Performance tools for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Tracing and trace analysis<BR>- =
Discrete =0A=
and continuous models<BR>- Measurement-based performance modelling<BR>- =0A=
Measurement architectures and systems<BR>- QoS monitoring and =
sampling<BR>- =0A=
Measurement-based optimisation of for heterogeneous wireless and wired =0A=
networks<BR>- Novel measurement tools of wireless networks<BR>- =
Performance =0A=
measurements of ad hoc, sensor, and ubiquitous networks<BR>- Performance =0A=
analysis and evaluation of mobile services<BR>- Software tools for =
wireless =0A=
network performance and evaluation<BR>- Automatic performance analysis =
<BR>- =0A=
Performance of wireless and sensor devices<BR>- Mobility modeling and =0A=
management<BR>- Prototype implementation of wireless/mobile networks and =0A=
systems<BR>- Techniques for prototyping wireless networks<BR>- =
Validation =0A=
through measurement and prototyping<BR>- Probabilistic models for ad =
hoc, =0A=
sensor, and ubiquitous networks<BR>- Improvement in network performance =
through =0A=
prototyping<BR>- Performance tools for ad hoc, sensor and ubiquitous =0A=
networks<BR>- Performance and security issues in ad hoc, sensor, and =
ubiquitous =0A=
networks<BR>- Performance and power management control<BR>- Case studies =0A=
demonstrating the role of performance monitoring, measurement, and =0A=
<BR>evaluation in the design of ad hoc, sensor, and ubiquitous =0A=
networks<BR>-Applications of performance monitoring, measurement, and =
evaluation =0A=
as a feedback to improve network QoS<BR>&nbsp;<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Workshop Co-Chairs:<BR>M. =0A=
Ould-Khaoua<BR>University of Glasgow<BR>UK&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">B. Caminero<BR>University of =
Castilla-La =0A=
Mancha<BR>Albacete (Spain)<BR>&nbsp;</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Program Committee (in =
progress):<BR>K. =0A=
Al-Begain, Univ. of Glamorgan (UK)<BR>A. Al-Dubai, Napier Univ. =
(UK)<BR>N. =0A=
Abu-Ghazaleh,&nbsp; SUNY,Binghamton (USA)<BR>I. Awan, Univ. of Bradford =0A=
(UK)<BR>A. Bermudez, University of Castilla-La Mancha (Spain)<BR>L. =
Bononi, =0A=
University of Bologna (Italy)<BR>A. Boukerche, Univ. of Ottawa =
(Canada)<BR>C.-C. =0A=
Shen, Univeristy of Delaware (USA)<BR>J.C. Cano, Technical University of =0A=
Valencia (Spain)<BR>C. Carrion, University of Castilla-La Mancha =
(Spain)<BR>M. =0A=
Colajanni, Univ. of Modena (Italy)<BR>P. Cuenca, University of =
Castilla-La =0A=
Mancha (Spain)<BR>F.M. Delicado, University of Castilla-La Mancha =
(Spain)<BR>E. =0A=
Fleury, INSA de Lyon (France)<BR>V. Gianuzzi, Univ. of Genova =
(Italy)<BR>E. =0A=
Karatza, Aristotle University of Thessaloniki (Greece)<BR>A. Ksentini, =0A=
University of Cergy-Pontoise (France)<BR>P. Manzoni, Technical =
University of =0A=
Valencia (Spain)<BR>G. Min, Univ. of Bradford (UK)<BR>M. Naimi, =
University of =0A=
Cergy-Pontoise (France)<BR>S. Nikoletseas, Computer Technology Institute =0A=
(Greece) <BR>M. S. M. Annoni Notare, Barddal Univ. (Brazil)<BR>S. =
Olariu, Old =0A=
Dominion Univ. (USA)<BR>T. Olivares, University of Castilla-La Mancha =0A=
(Spain)<BR>L. Orozco-Barbosa, University of Castilla-La Mancha =
(Spain)<BR>A. =0A=
Passarella, Univ. Of Cambridge (UK)<BR>Y. Pan, Georgia State Univ. =
(USA)<BR>M. =0A=
Perez-Malumbres, Miguel Hernandez University (Spain)<BR>F. Quiles, =
University of =0A=
Castilla-La Mancha (Spain)<BR>P. Ruiz, University of Murcia =
(Spain)<BR>J.L. =0A=
Sanchez, University of Castilla-La Mancha (Spain)<BR>M. S. Squillante, =
IBM T.J. =0A=
Watson Research Center (USA) <BR>A. Shahrabi, Glasgow Caledonian =
University =0A=
(UK)<BR>T. Miklos, Technical University of Budapest (Hungary)<BR>S. =
Yoshida, =0A=
Kyoto University (Japan)<BR>J. Wu, Florida Atlantic University =
(USA)<BR>A. =0A=
Zomaya, Univ. of Sydney (Australia)</FONT></DIV>=0A=
<DIV>&nbsp;</DIV>=0A=
<DIV><BR><FONT face=3D"Times New Roman">Publicity Chair<BR>M. S.-M. =
Annoni =0A=
Notare<BR>Barddal University, Florianopolis, SC =
<BR>Brazil<BR>&nbsp;&nbsp; =0A=
<BR>&nbsp;<BR>Paper Submission:<BR>Authors are invited to submit =
manuscripts =0A=
reporting original unpublished research and recent developments <BR>in =
the =0A=
topics related to the workshop. The length of the papers should not =
exceed 10 =0A=
single-spaced pages, <BR>formatted using the ACM style (LaTex2e&nbsp; =
and MS =0A=
Word templates can be found at &lt;</FONT><A =0A=
href=3D"http://www.acm.org/sigs/pubs/proceed/template.html"><FONT =0A=
face=3D"Times New =
Roman">http://www.acm.org/sigs/pubs/proceed/template.html</FONT></A><FONT=
 =0A=
face=3D"Times New Roman">&gt;).<BR></FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Papers should be submitted =
electronically in =0A=
PDF format (or postscript) by sending it as an e-mail attachment to =0A=
<BR></FONT><A href=3D"mailto:mohamed@dcs.gla.ac.uk"><FONT =0A=
face=3D"Times New Roman">mohamed@dcs.gla.ac.uk</FONT></A><FONT =0A=
face=3D"Times New Roman"> or </FONT><A =
href=3D"mailto:blanca@dsi.uclm.es"><FONT =0A=
face=3D"Times New Roman">blanca@dsi.uclm.es</FONT></A><FONT =0A=
face=3D"Times New Roman">. All papers will be peer reviewed and the =
comments will =0A=
<BR>be provided to the authors.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Accepted papers will appear in the =
workshop =0A=
proceedings and a special issue will be planned in a scholarly =
</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman">journal to include selected =
high-quality =0A=
papers from the workshop.</FONT></DIV>=0A=
<DIV><FONT face=3D"Times New Roman"></FONT>&nbsp;</DIV>=0A=
<DIV><FONT face=3D"Times New Roman">Important Dates:<BR>Submission =
Deadline: 10 =0A=
June 2006 <BR>Author Notification: 10 July =0A=
2006</FONT><BR></FONT></DIV></DIV></DIV></DIV></DIV></DIV></DIV></BODY></=
HTML>
------_=_NextPart_001_01C683E3.55788D5C--


--===============0716733964==
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

--===============0716733964==--




From manet-bounces@ietf.org Tue May 30 11:07:18 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fl5nI-0007sE-F7; Tue, 30 May 2006 11:06:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fl5nG-0007qi-8F
	for manet@ietf.org; Tue, 30 May 2006 11:06:02 -0400
Received: from exchange.nmsu.edu ([128.123.34.79] helo=ad.nmsu.edu)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fl5nE-0005Jh-V5
	for manet@ietf.org; Tue, 30 May 2006 11:06:02 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [manet] The interference of two transceivers in a single terminal
Date: Tue, 30 May 2006 09:05:59 -0600
Message-ID: <8536FDFA3AD04A49A158049159965691070F3102@exchange1.ACN.ad.nmsu.edu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [manet] The interference of two transceivers in a single terminal
Thread-Index: AcaDMI2qWWmR6bAlR1Wr60dHnThWAAAyc6ZA
From: "Mullen, John" <jomullen@ad.nmsu.edu>
To: "Hang Su" <hangsu@gmail.com>,
	<manet@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1222354977=="
Errors-To: manet-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1222354977==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C683FA.8F5EFE4A"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C683FA.8F5EFE4A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Hs,
=20
It would depend on a number of factors, but the biggest are probably
transmit power and the ability of the receiver to reject out of band
signals.
=20

John P. Mullen, Ph.D.
(505) 646-2958
jomullen@nmsu.edu
 =20

=20

________________________________

From: Hang Su [mailto:hangsu@gmail.com]=20
Sent: Monday, May 29, 2006 8:59 AM
To: manet@ietf.org
Subject: [manet] The interference of two transceivers in a single
terminal


Hi all,

I am currently studying multi-channel MAC protocols. Let us assume that
in
each node there's two sets of transceivers that can work simultaneously.
At
the same time slot, the two transceivers work over different channels
(say,=20
5.21G-5.22G and 5.22G-5.23G). If the Transceiver #1 is transmitting
while
the Transceiver #2 is receiving, how is the interference? Is there any
effective solution to resolve this kind of problem? Any help will be=20
appreciated.

Thanks,
Hs


------_=_NextPart_001_01C683FA.8F5EFE4A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D991330415-30052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Hi Hs,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D991330415-30052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D991330415-30052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>It would depend on a number of factors, but the =
biggest are=20
probably&nbsp;transmit power and&nbsp;the ability of the receiver to =
reject out=20
of band signals.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV><!-- Converted from text/plain format -->
<P><FONT size=3D2>John P. Mullen, Ph.D.<BR>(505)=20
646-2958<BR>jomullen@nmsu.edu<BR>&nbsp;</FONT> </P>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Hang Su =
[mailto:hangsu@gmail.com]=20
<BR><B>Sent:</B> Monday, May 29, 2006 8:59 AM<BR><B>To:</B>=20
manet@ietf.org<BR><B>Subject:</B> [manet] The interference of two =
transceivers=20
in a single terminal<BR></FONT><BR></DIV>
<DIV></DIV>Hi all,<BR><BR>I am currently studying multi-channel MAC =
protocols.=20
Let us assume that in<BR>each node there's two sets of transceivers that =
can=20
work simultaneously. At<BR>the same time slot, the two transceivers work =
over=20
different channels (say, <BR>5.21G-5.22G and 5.22G-5.23G). If the =
Transceiver #1=20
is transmitting while<BR>the Transceiver #2 is receiving, how is the=20
interference? Is there any<BR>effective solution to resolve this kind of =

problem? Any help will be=20
<BR>appreciated.<BR><BR>Thanks,<BR>Hs<BR></BODY></HTML>

------_=_NextPart_001_01C683FA.8F5EFE4A--


--===============1222354977==
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

--===============1222354977==--




From manet-bounces@ietf.org Tue May 30 12:44:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fl7Jn-00030N-Dz; Tue, 30 May 2006 12:43:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fl7Jl-00030E-BL
	for manet@ietf.org; Tue, 30 May 2006 12:43:41 -0400
Received: from ee.tamu.edu ([165.91.241.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fl7Jj-0004qD-0Z
	for manet@ietf.org; Tue, 30 May 2006 12:43:41 -0400
Received: from eesun1.tamu.edu (eesun1.tamu.edu [165.91.243.35])
	by ee.tamu.edu (8.13.6/8.13.6) with ESMTP id k4UGih9X026531;
	Tue, 30 May 2006 11:44:43 -0500 (CDT)
Date: Tue, 30 May 2006 11:49:20 -0500 (CDT)
From: Xi Zhang <xizhang@ece.tamu.edu>
X-Sender: xizhang@eesun1.tamu.edu
To: manet@ietf.org
Message-ID: <Pine.GSO.4.21.0605301147310.24408-100000@eesun1.tamu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: 
Subject: [manet] Call for Poster: QShine 2006. Extended Due Date: June 25,
	2006. 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org



Sorry for multiple copies.

*****************************************************
Call for Posters
QShine 2006
August 7-9, 2006
University of Waterloo, Waterloo, Ontario, Canada
http://www.qshine.org/posters.html
******************************************************

The 3rd International Conference on Quality of Service in Heterogeneous
Wired/Wireless Networks (QShine 2006),  Sponsored by Create-Net and ICST
In-cooperation with ACM SIGMOBILE

IMPORTANT DATES (Extended Due Dates)
---------------------------

4-page extended poster abstract:                 June 25, 2006
Notification of acceptance:                     June 30, 2006 
Camera-ready extended poster abstract:           July 7, 2006
Posters session date:                          August 7, 2006

OVERVIEW
---------------

QShine 2006 supports a poster session to provide a good forum for
researchers, engineers, and practitioners to showcase their on-going work
and obtain feedback from other experts in the field. Demonstrations and
posters showing innovative ideas and applications are highly
encouraged. Submissions from both academia and industries are welcome. The
scope of the selected poster papers includes, but is not limited to:

*	Cross-layer protocol design in wireless networks 
*	Quality of Service provisioning in wireless access networks 
*	Design, implementation/architectures related to QoS-enabled
        wireless networks 
*	Energy-aware protocols and algorithms in wireless networks 
*	QoS in WLAN, WPAN, WMAN and WiMAX (IEEE 802.11/15/16/20) 
*	QoS in wireless sensor and ad hoc networks 
*	QoS in cellular and satellite networks 
*	QoS support across heterogeneous wired and wireless subnetworks 
*	MAC protocols with QoS support 
*	Scheduling, resource management, queue management, and admission
        control 
*	QoS and survivability in mobile environments 
*	Game-theoretic aspects in wired, peer-to-peer, overlay, and
        wireless networks 
*	Incentive engineering in wired, peer-to-peer, overlay, and
        wireless networks 
*	QoS routing in wired, peer-to-peer, overlay, and wireless networks 
*	Traffic analysis, traffic engineering, and traffic shaping in
        heterogeneous environments 
*	Cross-layer performance optimization for energy, network lifetime,
        and capacity 
*	Topology control for QoS support in wireless networks 
*	QoS middleware in overlay and wireless networks 
*	QoS-aware service composition in overlay and wireless networks 
*	Security protocols and algorithms in wired, overlay and wireless
        networks 
*	Pricing, billing, and resource allocation in wired, overlay and
        wireless networks 
*	QoS adaptation, modeling and measurements 
*	Performance optimization in peer-to-peer and overlay networks 
*	Scalability of large-scale overlay and wireless networks 
*	Resilience of overlay and wireless protocols 

SUBMISSION INSTRUCTIONS
----------------------------------------

Please send at most 4-page poster extended abstract in an IEEE
double-column PDF file describing your poster to Professor Xi Zhang,
QShine 2006 Poster Chair, Texas A&M University, by email:

xizhang@ece.tamu.edu

Please put the subject line as "QShine Poster Extended Abstract
Submission". Please be as specific as possible in describing what you will
show. Extended abstracts of accepted posters will be published in the
conference proceedings.


=========================================================================
Xi Zhang                            Assistant Professor
Dept. of Elec. & Comput. Engin.     Phone: 979-458-1416 
Texas A&M University                Fax:   979-845-2630 
315-B WERC Building                 Email: xizhang@ece.tamu.edu 
College Station, Texas 77843, USA   URL http://dropzone.tamu.edu/~xizhang
=========================================================================








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



From manet-bounces@ietf.org Tue May 30 14:57:01 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fl9Nt-0001MO-0X; Tue, 30 May 2006 14:56:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fl9Nr-0001MD-DM; Tue, 30 May 2006 14:56: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 1Fl9Nr-0008Mt-Bh; Tue, 30 May 2006 14:56:03 -0400
Received: from cypress.neustar.com ([209.173.57.84])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1Fl8yZ-0000fS-GR; Tue, 30 May 2006 14:29:58 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10])
	by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k4UISsmU000874
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Tue, 30 May 2006 18:28:54 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1Fl8xa-0000EV-4O; Tue, 30 May 2006 14:28:54 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1Fl8xa-0000EV-4O@stiedprstage1.ietf.org>
Date: Tue, 30 May 2006 14:28:54 -0400
X-Spam-Score: -2.6 (--)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: manet mailing list <manet@ietf.org>,
	Internet Architecture Board <iab@iab.org>,
	manet chair <macker@itd.nrl.navy.mil>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [manet] Document Action: 'The Dynamic Source Routing Protocol for 
 Mobile Ad Hoc Networks (DSR)' to Experimental RFC 
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

The IESG has approved the following document:

- 'The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks (DSR) '
   <draft-ietf-manet-dsr-10.txt> as an Experimental RFC

This document is the product of the Mobile Ad-hoc Networks Working Group. 

The IESG contact persons are Bill Fenner and Ross Callon.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-dsr-10.txt

Technical Summary
 
   The Dynamic Source Routing protocol (DSR) is a routing protocol
    designed specifically for use in multi-hop wireless ad hoc
   networks of mobile nodes.  DSR allows the network to be completely
   self-organizing and self-configuring, without the need for any
   existing network infrastructure or administration.
 
Working Group Summary
 
   The Working Group had consensus to publish the four existing protocols
   as Experimental, as the first step down the path towards DYMO.
 
Protocol Quality
 
   Bill Fenner reviewed the specification for the IESG.

Note to RFC Editor

Please make the following two changes:

OLD (title):

                  The Dynamic Source Routing Protocol
                    for Mobile Ad Hoc Networks (DSR)

NEW:

                  The Dynamic Source Routing Protocol
               for Mobile Ad Hoc Networks (DSR) for IPv4

OLD (near the end of section 1, change "are" to "will be"):

   This document specifies the operation of the DSR protocol for
   routing unicast IPv4 packets in multi-hop wireless ad hoc networks.
   Advanced, optional features, such as Quality of Service (QoS) support
   and efficient multicast routing, and operation of DSR with IPv6 [7],
   are covered in other documents.

NEW:

   This document specifies the operation of the DSR protocol for
   routing unicast IPv4 packets in multi-hop wireless ad hoc networks.
   Advanced, optional features, such as Quality of Service (QoS) support
   and efficient multicast routing, and operation of DSR with IPv6 [7],
   will be covered in other documents.


IANA Note

   Please reassign IP Protocol 48 to DSR.  David Johnson (the main
   author of DSR) was able to confirm that this protocol number was
   originally assigned for a proposal for Mobile IP (Mobile Host
   Routing Protocol) that was never deployed.  Under RFC 2780
   section 4.3, this is the IESG Approval of this assignment.


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



From manet-bounces@ietf.org Wed May 31 03:55:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlLXW-00056P-1e; Wed, 31 May 2006 03:54:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlLXU-00056K-Os
	for manet@ietf.org; Wed, 31 May 2006 03:54:48 -0400
Received: from boreas.isi.edu ([128.9.160.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlLXR-0007uV-8i
	for manet@ietf.org; Wed, 31 May 2006 03:54:48 -0400
Received: from c1-vpn5.isi.edu (c1-vpn5.isi.edu [128.9.176.35])
	by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k4V7rUR26858
	for <manet@ietf.org>; Wed, 31 May 2006 00:53:30 -0700 (PDT)
From: Wei Ye <weiye@ISI.EDU>
To: manet@ietf.org
Content-Type: text/plain; charset=UTF-8
Date: Wed, 31 May 2006 00:53:29 -0700
Message-Id: <1149062010.3651.17.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) 
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
	k4V7rUR26858
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1
Subject: [manet] CFP: Workshops at ACM Sensys 2006
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Our Apologies if you have received multiple copies of the CFP.

Wei Ye and Cormac J. Sreenan
SenSys'06 Publicity Co-Chairs
------------


CFP: Workshops at ACM Sensys 2006

ACM Sensys 2006 is sponsored by ACM SIGCOMM, SIGMOBILE, SIGARCH, SIGOPS,
SIGMETRICS and SIGBED; with support from NSF.
http://sensys.acm.org/2006/
=20
--------------------------

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 Wed May 31 12:17:15 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlTMc-0000WM-W6; Wed, 31 May 2006 12:16:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlTMb-0000WH-6r
	for manet@ietf.org; Wed, 31 May 2006 12:16:05 -0400
Received: from wr-out-0506.google.com ([64.233.184.236])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlTMW-0004bQ-OU
	for manet@ietf.org; Wed, 31 May 2006 12:16:05 -0400
Received: by wr-out-0506.google.com with SMTP id i31so60233wra
	for <manet@ietf.org>; Wed, 31 May 2006 09:15:58 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:from:to:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole;
	b=jpn4z+kvw5OeL6IoHJDtOEiZZqje3rRNwKuA3eRbTchpjD8sbaRkRpz/dpQinr01O7Yo36RRkR5vqFJe5R8a/OPYHO4ZzQ4bJW+gMaqcOZ+gNXMTbFk6knkagz1zsat+5pS4s7wNpteLhrzVSxYrdW1HoEPQBSx2+JjH0htLQG8=
Received: by 10.64.53.12 with SMTP id b12mr380423qba;
	Wed, 31 May 2006 09:15:55 -0700 (PDT)
Received: from TIGERQ ( [69.195.22.67])
	by mx.gmail.com with ESMTP id e13sm155628qba.2006.05.31.09.15.55;
	Wed, 31 May 2006 09:15:55 -0700 (PDT)
Message-ID: <001e01c684cd$8032e8e0$6500a8c0@TIGERQ>
From: "Yihu Li" <yihuli@gmail.com>
To: "manet mailing list" <manet@ietf.org>
References: <E1Fl8xa-0000EV-4O@stiedprstage1.ietf.org>
Date: Wed, 31 May 2006 12:15:52 -0400
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [manet] A question in multiuser MIMO/SIMO
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi all,

I have a question about the synchronization problem in a SIMO system.

    S1(one antenna)-------->R (two antennas)<----------S2(one antenna)

In the scenario above, two transmitters S1 and S2 each have one antenna, and 
the receiver R has two antennas. Assuming spatial multiplexing mode is used, 
S1 first sends a packet to R, and then S2 also starts to send another packet 
to R while the transmission between S1 to R is still ongoing. Could R 
receive the two packets successfully or the two packets will be collided? If 
R can receive both, it has to first sychronize to S1 for reception, how can 
it sychronize to S2 thereafter? Is it possible?

Thanks.

Yihu 


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



From manet-bounces@ietf.org Wed May 31 13:36:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlUcG-00031W-3W; Wed, 31 May 2006 13:36:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlUcE-00031R-1V
	for manet@ietf.org; Wed, 31 May 2006 13:36:18 -0400
Received: from rmsi08.cluboffice.net ([72.19.154.194])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlUcA-0003ie-Mg
	for manet@ietf.org; Wed, 31 May 2006 13:36:18 -0400
Received: from [192.168.221.12] (81-172-17-66.mesanetworks.net [66.17.172.81]
	(may be forged)) (authenticated bits=0)
	by rmsi08.cluboffice.net (8.13.6/8.13.6) with ESMTP id k4VHZv17026319; 
	Wed, 31 May 2006 11:35:57 -0600
Message-ID: <447DD4FB.2060607@fidelity-comtech.com>
Date: Wed, 31 May 2006 11:40:11 -0600
From: Joe Carey <joe.carey@fidelity-comtech.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Yihu Li <yihuli@gmail.com>
Subject: Re: [manet] A question in multiuser MIMO/SIMO
References: <E1Fl8xa-0000EV-4O@stiedprstage1.ietf.org>
	<001e01c684cd$8032e8e0$6500a8c0@TIGERQ>
In-Reply-To: <001e01c684cd$8032e8e0$6500a8c0@TIGERQ>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_50 autolearn=no 
	version=3.0.5
X-Spam-Checker-Version: SpamAssassin 3.0.5 (2005-11-28) on 
	rmsi08.cluboffice.net
X-rmsi-MailScanner-Information: Please contact the ISP for more information
X-rmsi-MailScanner: Found to be clean
X-rmsi-MailScanner-From: joe.carey@fidelity-comtech.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: manet mailing list <manet@ietf.org>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Yihu,

Yes, it is possible.  In fact, CDMA cell phones work this way (except R 
usually has only one antenna).  Typically we describe the problem with 
S1 and S2 being the same station, but it could be made to work with them 
being different stations.

It requires some fancy waveform coding.  You are correct, 
synchronization is one of the big issues.  Determining the propagation 
channel characteristics so you can sort it out on the far end is another 
big issue.

Here is a link to the Enhanced Wireless Consortium.  Download the 
802.11n draft spec, which gives some detail on a particular MIMO 
implementation:
http://www.enhancedwirelessconsortium.org/home
It'll cure any insomnia you might have.

You can also google or do a literature search on "space time coding."

joe

Yihu Li wrote:
> Hi all,
>
> I have a question about the synchronization problem in a SIMO system.
>
>    S1(one antenna)-------->R (two antennas)<----------S2(one antenna)
>
> In the scenario above, two transmitters S1 and S2 each have one 
> antenna, and the receiver R has two antennas. Assuming spatial 
> multiplexing mode is used, S1 first sends a packet to R, and then S2 
> also starts to send another packet to R while the transmission between 
> S1 to R is still ongoing. Could R receive the two packets successfully 
> or the two packets will be collided? If R can receive both, it has to 
> first sychronize to S1 for reception, how can it sychronize to S2 
> thereafter? Is it possible?
>
> Thanks.
>
> Yihu
>
> _______________________________________________
> 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 May 31 14:36:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlVXT-0005Pk-TC; Wed, 31 May 2006 14:35:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlVXS-0005Pf-JY
	for manet@ietf.org; Wed, 31 May 2006 14:35:26 -0400
Received: from wr-out-0506.google.com ([64.233.184.224])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlVXR-0000Mm-7x
	for manet@ietf.org; Wed, 31 May 2006 14:35:26 -0400
Received: by wr-out-0506.google.com with SMTP id i31so91506wra
	for <manet@ietf.org>; Wed, 31 May 2006 11:35:24 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:from:to:cc:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole;
	b=Ls8sxYdr5AiGjsG3q0Hy2gM80gIbGMXmZIVxtaOfNpkESJ99tlyLD2OSoRRqQyq1SA95kSQt+UBbVqAAiTq7/W0PEiIrb8MDlvzSfF1sRG/OGrCXT7eSyVgRh5zE2YMHU+MezDYUMNMdtb1WiWWEbn5qN+o7xX/3v8UjeJBMgu0=
Received: by 10.65.189.12 with SMTP id r12mr595612qbp;
	Wed, 31 May 2006 11:35:23 -0700 (PDT)
Received: from TIGERQ ( [69.195.22.67])
	by mx.gmail.com with ESMTP id d12sm257638qbc.2006.05.31.11.35.21;
	Wed, 31 May 2006 11:35:23 -0700 (PDT)
Message-ID: <005101c684e0$fba9fc80$6500a8c0@TIGERQ>
From: "Yihu Li" <yihuli@gmail.com>
To: "Joe Carey" <joe.carey@fidelity-comtech.com>
References: <E1Fl8xa-0000EV-4O@stiedprstage1.ietf.org>
	<001e01c684cd$8032e8e0$6500a8c0@TIGERQ>
	<447DD4FB.2060607@fidelity-comtech.com>
Subject: Re: [manet] A question in multiuser MIMO/SIMO
Date: Wed, 31 May 2006 14:35:17 -0400
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: manet mailing list <manet@ietf.org>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Joe,

Thanks a lot.

I just want to double confirm the problem: nodes S1 and S2 are not 
synchronized in transmission (not as the conventional single-user MIMO in 
which multiple antennas in a transmitter transmit at the same time slot or 
MIMO coorperative communication in which the nodes with single antennas are 
coordinated to transmit at the same time slot). Instead, S1 and S2 start 
their transmissions in different time slots. So, you think node R can still 
receive the packets from both stations correctly in this case, right? If so, 
what is the differences/comlexities of this case to the one where 
transmissions through different antennas are synchronized?

Thanks again.

Yihu
----- Original Message ----- 
From: "Joe Carey" <joe.carey@fidelity-comtech.com>
To: "Yihu Li" <yihuli@gmail.com>
Cc: "manet mailing list" <manet@ietf.org>
Sent: Wednesday, May 31, 2006 1:40 PM
Subject: Re: [manet] A question in multiuser MIMO/SIMO


> Yihu,
>
> Yes, it is possible.  In fact, CDMA cell phones work this way (except R 
> usually has only one antenna).  Typically we describe the problem with S1 
> and S2 being the same station, but it could be made to work with them 
> being different stations.
>
> It requires some fancy waveform coding.  You are correct, synchronization 
> is one of the big issues.  Determining the propagation channel 
> characteristics so you can sort it out on the far end is another big 
> issue.
>
> Here is a link to the Enhanced Wireless Consortium.  Download the 802.11n 
> draft spec, which gives some detail on a particular MIMO implementation:
> http://www.enhancedwirelessconsortium.org/home
> It'll cure any insomnia you might have.
>
> You can also google or do a literature search on "space time coding."
>
> joe
>
> Yihu Li wrote:
>> Hi all,
>>
>> I have a question about the synchronization problem in a SIMO system.
>>
>>    S1(one antenna)-------->R (two antennas)<----------S2(one antenna)
>>
>> In the scenario above, two transmitters S1 and S2 each have one antenna, 
>> and the receiver R has two antennas. Assuming spatial multiplexing mode 
>> is used, S1 first sends a packet to R, and then S2 also starts to send 
>> another packet to R while the transmission between S1 to R is still 
>> ongoing. Could R receive the two packets successfully or the two packets 
>> will be collided? If R can receive both, it has to first sychronize to S1 
>> for reception, how can it sychronize to S2 thereafter? Is it possible?
>>
>> Thanks.
>>
>> Yihu
>>
>> _______________________________________________
>> 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 May 31 18:49:27 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlZV3-0004UV-77; Wed, 31 May 2006 18:49:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlZV1-0004Tz-KV
	for manet@ietf.org; Wed, 31 May 2006 18:49:11 -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 1FlXhB-0007lm-HY
	for manet@ietf.org; Wed, 31 May 2006 16:53:37 -0400
Received: from rmsi08.cluboffice.net ([72.19.154.194])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FlX0j-0005AK-3O
	for manet@ietf.org; Wed, 31 May 2006 16:09:50 -0400
Received: from [192.168.221.12] (81-172-17-66.mesanetworks.net [66.17.172.81]
	(may be forged)) (authenticated bits=0)
	by rmsi08.cluboffice.net (8.13.6/8.13.6) with ESMTP id k4VK9WIt019289; 
	Wed, 31 May 2006 14:09:32 -0600
Message-ID: <447DF8D8.90103@fidelity-comtech.com>
Date: Wed, 31 May 2006 14:13:12 -0600
From: Joe Carey <joe.carey@fidelity-comtech.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: Yihu Li <yihuli@gmail.com>
Subject: Re: [manet] A question in multiuser MIMO/SIMO
References: <E1Fl8xa-0000EV-4O@stiedprstage1.ietf.org>
	<001e01c684cd$8032e8e0$6500a8c0@TIGERQ>
	<447DD4FB.2060607@fidelity-comtech.com>
	<005101c684e0$fba9fc80$6500a8c0@TIGERQ>
In-Reply-To: <005101c684e0$fba9fc80$6500a8c0@TIGERQ>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=0.0 required=5.0 tests=BAYES_50 autolearn=no 
	version=3.0.5
X-Spam-Checker-Version: SpamAssassin 3.0.5 (2005-11-28) on 
	rmsi08.cluboffice.net
X-rmsi-MailScanner-Information: Please contact the ISP for more information
X-rmsi-MailScanner: Found to be clean
X-rmsi-MailScanner-From: joe.carey@fidelity-comtech.com
X-Spam-Score: -2.6 (--)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e
Cc: manet mailing list <manet@ietf.org>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Yihu,

Yes, its still possible when the systems are unsynchronized, but timing 
recovery is more complicated.  This is the CDMA reverse link problem, 
from the handset to the base station.  You might be tempted to argue 
that the handsets synchronize off the same forward link, but I would 
make the counterpoint that in a CDMA system the two handsets could be 
traveling and therefore have different doppler shifts and so are 
effectively unsynchronized.

The key to making this work is the coding.  Pick the right spreading / 
timing / synchronization / channel sounding codes and it can be made to 
work.

Another significant problem in the situation you describe is the 
difference in amplitude between signals received from S1 and S2.  If one 
station is closer than the other, coding gain alone will not be 
sufficient.  In that case you need to implement power control in place 
to keep the two signals received at R at approximately the same level, 
so that coding gain can effectively separate the two signals.

Ramanathan at BBN wrote an interesting paper recently on future network 
topologies that explored variations on this idea for ad-hoc networks.

joe

Yihu Li wrote:
> Hi Joe,
>
> Thanks a lot.
>
> I just want to double confirm the problem: nodes S1 and S2 are not 
> synchronized in transmission (not as the conventional single-user MIMO 
> in which multiple antennas in a transmitter transmit at the same time 
> slot or MIMO coorperative communication in which the nodes with single 
> antennas are coordinated to transmit at the same time slot). Instead, 
> S1 and S2 start their transmissions in different time slots. So, you 
> think node R can still receive the packets from both stations 
> correctly in this case, right? If so, what is the 
> differences/comlexities of this case to the one where transmissions 
> through different antennas are synchronized?
>
> Thanks again.
>
> Yihu
> ----- Original Message ----- From: "Joe Carey" 
> <joe.carey@fidelity-comtech.com>
> To: "Yihu Li" <yihuli@gmail.com>
> Cc: "manet mailing list" <manet@ietf.org>
> Sent: Wednesday, May 31, 2006 1:40 PM
> Subject: Re: [manet] A question in multiuser MIMO/SIMO
>
>
>> Yihu,
>>
>> Yes, it is possible.  In fact, CDMA cell phones work this way (except 
>> R usually has only one antenna).  Typically we describe the problem 
>> with S1 and S2 being the same station, but it could be made to work 
>> with them being different stations.
>>
>> It requires some fancy waveform coding.  You are correct, 
>> synchronization is one of the big issues.  Determining the 
>> propagation channel characteristics so you can sort it out on the far 
>> end is another big issue.
>>
>> Here is a link to the Enhanced Wireless Consortium.  Download the 
>> 802.11n draft spec, which gives some detail on a particular MIMO 
>> implementation:
>> http://www.enhancedwirelessconsortium.org/home
>> It'll cure any insomnia you might have.
>>
>> You can also google or do a literature search on "space time coding."
>>
>> joe
>>
>> Yihu Li wrote:
>>> Hi all,
>>>
>>> I have a question about the synchronization problem in a SIMO system.
>>>
>>>    S1(one antenna)-------->R (two antennas)<----------S2(one antenna)
>>>
>>> In the scenario above, two transmitters S1 and S2 each have one 
>>> antenna, and the receiver R has two antennas. Assuming spatial 
>>> multiplexing mode is used, S1 first sends a packet to R, and then S2 
>>> also starts to send another packet to R while the transmission 
>>> between S1 to R is still ongoing. Could R receive the two packets 
>>> successfully or the two packets will be collided? If R can receive 
>>> both, it has to first sychronize to S1 for reception, how can it 
>>> sychronize to S2 thereafter? Is it possible?
>>>
>>> Thanks.
>>>
>>> Yihu
>>>
>>> _______________________________________________
>>> 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 May 31 21:20:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FlbrN-0006UJ-Lu; Wed, 31 May 2006 21:20:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FlbrL-0006Tt-BI
	for manet@ietf.org; Wed, 31 May 2006 21:20:23 -0400
Received: from wr-out-0506.google.com ([64.233.184.232])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlbrA-0002R7-FE
	for manet@ietf.org; Wed, 31 May 2006 21:20:15 -0400
Received: by wr-out-0506.google.com with SMTP id 36so166154wra
	for <manet@ietf.org>; Wed, 31 May 2006 18:20:11 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:from:to:cc:references:subject:date:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:x-mimeole;
	b=lsVLIU1xbJzPOlYbB5A/jEvYuE30EV/WuLrgu4OHiaRShgmAg6lQU8I0o7yQnnmVf9/PQd9S5L1ZQPV6T8C70FJyEBGRr3Jtk3qOCdqL9devX0Wyuevpn2A1jSVBF7NzPbvxjfEdVsnBjaWFnLpsWQwO5YYGpZySNwhhPSI4Mzw=
Received: by 10.65.185.17 with SMTP id m17mr23351qbp;
	Wed, 31 May 2006 18:20:11 -0700 (PDT)
Received: from TIGERQ ( [69.195.22.67])
	by mx.gmail.com with ESMTP id f12sm405115qba.2006.05.31.18.20.11;
	Wed, 31 May 2006 18:20:11 -0700 (PDT)
Message-ID: <00e601c68519$88d4c580$6500a8c0@TIGERQ>
From: "Yihu Li" <yihuli@gmail.com>
To: "Joe Carey" <joe.carey@fidelity-comtech.com>
References: <E1Fl8xa-0000EV-4O@stiedprstage1.ietf.org>
	<001e01c684cd$8032e8e0$6500a8c0@TIGERQ>
	<447DD4FB.2060607@fidelity-comtech.com>
	<005101c684e0$fba9fc80$6500a8c0@TIGERQ>
	<447DF8D8.90103@fidelity-comtech.com>
Subject: Re: [manet] A question in multiuser MIMO/SIMO
Date: Wed, 31 May 2006 21:20:07 -0400
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: manet mailing list <manet@ietf.org>
X-BeenThere: manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:manet@ietf.org>
List-Help: <mailto:manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet>,
	<mailto:manet-request@ietf.org?subject=subscribe>
Errors-To: manet-bounces@ietf.org

Hi Joe,

Thank you for your explaination. It helps a lot.

As you pointed out, "The key to making this work is the coding.  Pick the 
right spreading /  timing / synchronization / channel sounding codes" and 
"timing recovery is more comlicated". So, do you know any work on this, that 
is, coding and timing recovery to make this work or discuss this? Any 
reference will be great helpful.

Regards,

Yihu
----- Original Message ----- 
From: "Joe Carey" <joe.carey@fidelity-comtech.com>
To: "Yihu Li" <yihuli@gmail.com>
Cc: "manet mailing list" <manet@ietf.org>
Sent: Wednesday, May 31, 2006 4:13 PM
Subject: Re: [manet] A question in multiuser MIMO/SIMO


> Hi Yihu,
>
> Yes, its still possible when the systems are unsynchronized, but timing 
> recovery is more complicated.  This is the CDMA reverse link problem, from 
> the handset to the base station.  You might be tempted to argue that the 
> handsets synchronize off the same forward link, but I would make the 
> counterpoint that in a CDMA system the two handsets could be traveling and 
> therefore have different doppler shifts and so are effectively 
> unsynchronized.
>
> The key to making this work is the coding.  Pick the right spreading / 
> timing / synchronization / channel sounding codes and it can be made to 
> work.
>
> Another significant problem in the situation you describe is the 
> difference in amplitude between signals received from S1 and S2.  If one 
> station is closer than the other, coding gain alone will not be 
> sufficient.  In that case you need to implement power control in place to 
> keep the two signals received at R at approximately the same level, so 
> that coding gain can effectively separate the two signals.
>
> Ramanathan at BBN wrote an interesting paper recently on future network 
> topologies that explored variations on this idea for ad-hoc networks.
>
> joe
>
> Yihu Li wrote:
>> Hi Joe,
>>
>> Thanks a lot.
>>
>> I just want to double confirm the problem: nodes S1 and S2 are not 
>> synchronized in transmission (not as the conventional single-user MIMO in 
>> which multiple antennas in a transmitter transmit at the same time slot 
>> or MIMO coorperative communication in which the nodes with single 
>> antennas are coordinated to transmit at the same time slot). Instead, S1 
>> and S2 start their transmissions in different time slots. So, you think 
>> node R can still receive the packets from both stations correctly in this 
>> case, right? If so, what is the differences/comlexities of this case to 
>> the one where transmissions through different antennas are synchronized?
>>
>> Thanks again.
>>
>> Yihu
>> ----- Original Message ----- From: "Joe Carey" 
>> <joe.carey@fidelity-comtech.com>
>> To: "Yihu Li" <yihuli@gmail.com>
>> Cc: "manet mailing list" <manet@ietf.org>
>> Sent: Wednesday, May 31, 2006 1:40 PM
>> Subject: Re: [manet] A question in multiuser MIMO/SIMO
>>
>>
>>> Yihu,
>>>
>>> Yes, it is possible.  In fact, CDMA cell phones work this way (except R 
>>> usually has only one antenna).  Typically we describe the problem with 
>>> S1 and S2 being the same station, but it could be made to work with them 
>>> being different stations.
>>>
>>> It requires some fancy waveform coding.  You are correct, 
>>> synchronization is one of the big issues.  Determining the propagation 
>>> channel characteristics so you can sort it out on the far end is another 
>>> big issue.
>>>
>>> Here is a link to the Enhanced Wireless Consortium.  Download the 
>>> 802.11n draft spec, which gives some detail on a particular MIMO 
>>> implementation:
>>> http://www.enhancedwirelessconsortium.org/home
>>> It'll cure any insomnia you might have.
>>>
>>> You can also google or do a literature search on "space time coding."
>>>
>>> joe
>>>
>>> Yihu Li wrote:
>>>> Hi all,
>>>>
>>>> I have a question about the synchronization problem in a SIMO system.
>>>>
>>>>    S1(one antenna)-------->R (two antennas)<----------S2(one antenna)
>>>>
>>>> In the scenario above, two transmitters S1 and S2 each have one 
>>>> antenna, and the receiver R has two antennas. Assuming spatial 
>>>> multiplexing mode is used, S1 first sends a packet to R, and then S2 
>>>> also starts to send another packet to R while the transmission between 
>>>> S1 to R is still ongoing. Could R receive the two packets successfully 
>>>> or the two packets will be collided? If R can receive both, it has to 
>>>> first sychronize to S1 for reception, how can it sychronize to S2 
>>>> thereafter? Is it possible?
>>>>
>>>> Thanks.
>>>>
>>>> Yihu
>>>>
>>>> _______________________________________________
>>>> 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



