From owner-manet@itd.nrl.navy.mil  Fri Jun  1 07:25:32 2001
Received: from itd.nrl.navy.mil ([132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id HAA04785
	for <manet-archive@odin.ietf.org>; Fri, 1 Jun 2001 07:25:31 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id EAA18224
	for manet-outgoing; Fri, 1 Jun 2001 04:30:32 -0400 (EDT)
Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id EAA18219
	for <manet@itd.nrl.navy.mil>; Fri, 1 Jun 2001 04:30:29 -0400 (EDT)
Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19)
	id <LN2K9T1J>; Fri, 1 Jun 2001 10:30:30 +0100
Message-ID: <59063B5B4D98D311BC0D0001FA7E45220428E885@l04.research.kpn.com>
From: "Groten, D." <D.Groten@kpn.com>
To: "'Felix Ko'" <felix.ko@mchp.siemens.de>, manet@itd.nrl.navy.mil
Subject: RE: Power control
Date: Fri, 1 Jun 2001 10:30:29 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi Felix,
At VTC 2001, a paper was presented by my colleague investigating the cell
capacity in a hybrid  network supporting multihop relaying to the base
station:
O.C. Mantel, N. Scully and A. Mawira, "Radio aspects of hybrid wireless
ad-hoc networks", Proceedings of the VTC Spring 2001, IEEE.

Greetings,
Dirk.

------------------------------------------------------------------
Dirk Groten	      	       KPN Research		
------------------------------------------------------------------	
P. O. Box 421		       Tel: +31 6 53747220
2260 AK Leidschendam	       Fax: +31 70 4463477
The Netherlands	             E-mail: d.groten@kpn.com

-----Original Message-----
From: Felix Ko [mailto:felix.ko@mchp.siemens.de]
Sent: woensdag 2 mei 2001 15:09
To: manet@itd.nrl.navy.mil
Subject: Power control


Hi!

I have searched the mailinglist archive but I haven't found
anything:

I am working on my diploma thesis and I am looking
for anything about power control in ad-hoc networks in
order to increase the network's capacity.

I searched the web and the IEEE database, but I found
only two publications about this subject:

- Jeffrey P. Monks "Transmission Power Control for Multiple
Access Wireless Packet Networks"
- Nicholas Bambos, Sunil Kandukuri, "Power Controlled Multiple
Access (PCMA) in Wireless Communication Networks"

From my point of view, research has primarily focused on
energy-conserving MAC/Routing protocols, is this correct?

ANY HELP on this subject is greatly appreciated!!!!!

With kind regards

Felix



From owner-manet@itd.nrl.navy.mil  Fri Jun  1 12:29:43 2001
Received: from itd.nrl.navy.mil ([132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11375
	for <manet-archive@odin.ietf.org>; Fri, 1 Jun 2001 12:29:42 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id JAA24386
	for manet-outgoing; Fri, 1 Jun 2001 09:47:27 -0400 (EDT)
Message-Id: <200106011347.JAA24386@itd.nrl.navy.mil>
Date: Mon, 21 May 2001 00:27:16 -0400
To: manet@itd.nrl.navy.mil
From: Shailesh Humbad <humbads@alum.mit.edu>
Subject: manet for congestion pricing thesis
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Greetings,

I invite you to read my now finalized thesis.

Title: Suitability of Mobile Distributed Wireless Networks for Urban
Traffic Congestion Mitigation

http://www-personal.umich.edu/~humbads/thesis/

Comments welcome,
Shailesh 	



From owner-manet@itd.nrl.navy.mil  Fri Jun  1 12:30:01 2001
Received: from itd.nrl.navy.mil ([132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA11397
	for <manet-archive@odin.ietf.org>; Fri, 1 Jun 2001 12:30:00 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id JAA24366
	for manet-outgoing; Fri, 1 Jun 2001 09:46:53 -0400 (EDT)
Message-Id: <200106011346.JAA24366@itd.nrl.navy.mil>
Date: Thu, 31 May 2001 13:42:00 -0700 (PDT)
From: James Kempf <James.Kempf@sun.com>
Reply-To: James Kempf <James.Kempf@sun.com>
Subject: Re: Wireless Terminology Draft
To: Madjid.Nakhjiri@motorola.com, charliep@iprg.nokia.com
Cc: jmanner@cs.helsinki.fi, hmsyed@nortelnetworks.com, James.Kempf@sun.com,
        seamoby@diameter.org, manet@itd.nrl.navy.mil
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: M1NbEXEz4PsHujlpPsGBHg==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.2 SunOS 5.8 sun4u sparc
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Charlie,

I think this is an excellent idea. IETF needs to get a common set of 
terminology
for wireless. Leaving it up to the individual working groups means
that someone from a different working group must translate terminology
from one to another. Imagine the chaos if half the IETF RFCs referred
to routers as routers and the other half as something else.

This may actually be an IAB kind of item, perhaps we could get their
sponsorship. It seems like the kind of thing they would do. In any
event, I will take a look at your draft and submit comments. Thanks
for taking the initative on this.

		jak

 >MBOX-Line: From owner-manet@itd.nrl.navy.mil Sat May 19 18:05:29 2001
 >X-mProtect: Fri, 18 May 2001 10:50:08 -0700 Nokia Silicon Valley Messaging
Protection
 >Date: Fri, 18 May 2001 10:50:08 -0700
 >From: "Charles E. Perkins" <charliep@iprg.nokia.com>
 >To: Nakhjiri Madjid-MNAKHJI1 <Madjid.Nakhjiri@motorola.com>
 >CC: "'Jukka Manner'" <jmanner@cs.helsinki.fi>, Hamid Syed
<hmsyed@nortelnetworks.com>, "'James Kempf'" <James.Kempf@Sun.COM>,
seamoby@diameter.org, Mobile Ad Hoc IETF working group <manet@itd.nrl.navy.mil>
 >Subject: Re: Wireless Terminology Draft( was: Re: [seamoby] 
Seamoby  Charter
       Last Call)
 >
 >
 >Hello folks,
 >
 >I made an attempt a few years ago to develop such a terminology
 >draft, within the context of the [manet] working group.  Here
 >is a URL for the draft if you are interested:
 >	http://people.nokia.net/~charliep/txt/manet/term.txt
 >
 >If you would like to use some of the definitions in that draft,
 >and/or if you are looking for help in creating the new draft,
 >I'd be happy to work on it.
 >
 >The draft was rejected within the [manet] working group for
 >a reason that I thought was very curious.  Essentially, the
 >objection was made that every working group Internet Draft should
 >contain its own terminology definitions, and that no common
 >terminology draft was desirable.  I disagreed with that reason
 >then, and I still disagree with it, but I haven't felt a very
 >strong need to take up the matter within the [manet] group
 >since I didn't need yet another battle on my hands.
 >
 >I do think it would be a good idea to keep the terminology
 >draft separated out from a more wide-ranging wireless issues
 >draft, such as has generated a lot of recent interest on this
 >mailing list.
 >
 >Regards,
 >Charlie P.
 >
 >PS. to [manet] working group readers: I'd be happy to reintroduce
 >    the old draft, or a revision of it, for reconsideration.
 >
 >
 >
 >
 >Nakhjiri Madjid-MNAKHJI1 wrote:
 >>
 >> Jukka,
 >>
 >> Thanks for taking charge on this. Did you do a diff on your
 >> definitions and CT problem statement draft? Since you were
 >> intimately involved with CT PS draft, I assume you did that.
 >> I think we did a good job of defining CT related terminology,
 >> but I don't know how it differred from MM or Paging terminology,
 >> it would be nice to do a diff with those as well to have a WG
 >> wide common terminology draft.
 >>
 >> Thanks again,
 >> Madjid
 >>
 >> -----Original Message-----
 >> From: Jukka Manner [mailto:jmanner@cs.Helsinki.FI]
 >> Sent: Tuesday, May 15, 2001 1:25 AM
 >> To: Hamid Syed
 >> Cc: 'James Kempf'; seamoby@diameter.org
 >> Subject: RE: Wireless Terminology Draft( was: Re: [seamoby] Seamoby
 >> Charter Last Call)
 >>
 >>         Hamid,
 >>
 >>         Thank you for suggesting it. The draft was originally meant to
 >> support the work in Seamoby, but it would be an even better idea to make it
 >> a more thorough document for use in more or less all work relating to 
mobile
 >> and
 >> wireless environments, including Seamoby, Mobile-IP, and possibly MANET.
 >>
 >>         I would be happy to continue the work on the terminology taking as
 >> basis
 >> the mentioned draft.
 >>
 >>         BR,
 >>
 >>         Jukka
 >>
 >> On Mon, 14 May 2001, Hamid Syed wrote:
 >>
 >> > Hello james,
 >> >
 >> > A draft was submitted to seamoby early this year that attempted to 
capture
 >> > the wireless terminology. her eis the link:
 >> > http://search.ietf.org/internet-drafts/draft-manner-seamoby-terms-01.txt
 >> >
 >> > br
 >> >
 >> > -Hamid
 >> >
 >> > > -----Original Message-----
 >> > > From:       James Kempf [SMTP:James.Kempf@Sun.COM]
 >> > > Sent:       Monday, May 14, 2001 1:47 PM
 >> > > To: seamoby@diameter.org
 >> > > Subject:    Wireless Terminology Draft( was: Re: [seamoby] Seamoby
 >> > > Charter Last  Call)
 >> > >
 >> > >
 >> > > ------------- Begin Forwarded Message -------------
 >> > >
 >> > > Date: Mon, 14 May 2001 10:43:47 -0700 (PDT)
 >> > > From: James Kempf <James.Kempf@sun.com>
 >> > > Subject: Re: [seamoby] Seamoby Charter Last Call
 >> > > To: James.Kempf@sun.com, charliep@iprg.nokia.com
 >> > > Content-MD5: 6F7Vl9kYVVbqr66TeEQyRw==
 >> > >
 >> > > Hi Charlie,
 >> > >
 >> > >
 >> > > >> Maybe we need a terminology draft, or at least, define this term
 >> > > >> somewhere so that it can be referred to. I'm suprised nobody
 >> > > >> has done a generalized terminology draft for wireless terms 
before in
 >> > > the MIP
 >> > > >> group.
 >> > > >
 >> > > >RFC 2002 does start off with a long list of terminology.
 >> > > >
 >> > > >It is questionable whether any specific wireless terms are
 >> > > >needed for a protocol running over IP.  What is needed is
 >> > > >a list of useful terms.  For instance, one might care about
 >> > > >error rate or bandwidth even if the medium were not wireless.
 >> > > >I don't think that chip rate, for instance, should be part
 >> > > >of the [seamoby] terminology list.
 >> > > >
 >> > >
 >> > > Actually, there are plenty of wireless terms that need definition.
 >> > > Access point, handoff (or handover IETF should select which one
 >> > > it wants to use), context transfer, paging, etc. etc.
 >> > >
 >> > > >Do you think that there are terms which SHOULD have been defined
 >> > > >for RFC 2002?  If so, now would be a good time to mention them
 >> > > >before RFC 2002bis goes to the RFC editor's desk.
 >> > > >
 >> > >
 >> > > No, I think they have wider applicability. More and more wireless
 >> > > stuff is going on. There are now two working groups associated
 >> > > with wireless, and others that have a big wireless component. I think
 >> > > having a
 >> > > terminology draft that collects all terminology that could be referred
 >> to
 >> > > by
 >> > > drafts would be a benefit.
 >> > >
 >> > >             jak
 >> > >
 >> > >
 >> > >
 >> > > ------------- End Forwarded Message -------------
 >> > >
 >> > >
 >> >
 >



From owner-manet@itd.nrl.navy.mil  Fri Jun  1 16:59:45 2001
Received: from itd.nrl.navy.mil ([132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA18064
	for <manet-archive@odin.ietf.org>; Fri, 1 Jun 2001 16:59:43 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id OAA05407
	for manet-outgoing; Fri, 1 Jun 2001 14:41:14 -0400 (EDT)
Received: from Tempo.Update.UU.SE (Tempo.Update.UU.SE [130.238.19.17])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id OAA05402
	for <manet@itd.nrl.navy.mil>; Fri, 1 Jun 2001 14:41:10 -0400 (EDT)
Received: from localhost (davidl@localhost)
	by Tempo.Update.UU.SE (8.11.2/8.11.2/Update-Iltempogigante) with ESMTP id f51IYOD23993;
	Fri, 1 Jun 2001 20:34:24 +0200
Date: Fri, 1 Jun 2001 20:34:23 +0200 (CEST)
From: David Lundberg <davidl@update.uu.se>
To: Daniel Lang <dl@leo.org>
cc: manet@itd.nrl.navy.mil, ape@docs.uu.se
Subject: Re: Simulations and protocol evaluation
In-Reply-To: <20010531123705.B97513@atrbg11.informatik.tu-muenchen.de>
Message-ID: <Pine.LNX.4.21.0106012005100.22121-100000@Tempo.Update.UU.SE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by itd.nrl.navy.mil id OAA05403
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by itd.nrl.navy.mil id OAA05407
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA18064


A quick answer before the weekend starts...

> Apart from these, I did not discover any other work, that focuses
> on comparison and simulations. Especially with more sophisticated
> movement and traffic models, like [1]. In [1], the authors state,
> that this paper was just the advent of more simulations to come, comparing
> more protocols and using other traffic models.
> Unfortunately I was not able to find any papers about such
> subsequent work.

At Uppsala University we have a lot of activity going on and several
papers have been submitted for publication. The main focus in them are
how to evaluate protocols and the need for metrics. 

We also have produced a testbed for evaluating different protocols which
we hope to be able to release for public use very soon.

> My plans are, to develop a set of applications scenarios, that
> model real situations and movements patterns as close as
> possible. Further to use more sophistic traffic models,
> e.g. TCP On-Off Traffic. Then, see how far this can be used
> with simulations software (ns2, GloMoSim) in terms of acceptable
> duration and data generated. If things worked out, I will do
> actual simulations, to find what protocols are most suitable
> for which situations.

That sounds interesting!

We currently have two Ms.Sc.thesis reports that cover ad hoc protocol
evaluation that should be finished in the very near future. (One of them
is mine and must be finished within the next few weeks...)

Well. Not much facts, but at least you know there's work going on..

Regards,

// David //


--------------------------------------------------------------
David Lundberg            Phone: Home(Uppsala)  +46-018-460356
Mail: davidl@update.uu.se        Home(Gävle)    +46-026-146743
Http: www.update.uu.se/~davidl   Cellular      +46-070-3531696
ICQ:  13440550                   DoCS @ UU     +46-018-4716231
--------------------------------------------------------------



From owner-manet@itd.nrl.navy.mil  Fri Jun  1 20:54:39 2001
Received: from itd.nrl.navy.mil ([132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA20216
	for <manet-archive@odin.ietf.org>; Fri, 1 Jun 2001 20:54:37 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id SAA10912
	for manet-outgoing; Fri, 1 Jun 2001 18:11:59 -0400 (EDT)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.161.193])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id SAA10903
	for <manet@itd.nrl.navy.mil>; Fri, 1 Jun 2001 18:11:56 -0400 (EDT)
Received: from mail.vt.edu (gkar.cc.vt.edu [198.82.161.190])
	by lennier.cc.vt.edu (8.11.0/8.11.0) with ESMTP id f51MBug168197
	for <manet@itd.nrl.navy.mil>; Fri, 1 Jun 2001 18:11:56 -0400 (EDT)
Received: from ecpe15 ([208.17.194.118])
 by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10)
 with SMTP id <0GE9006DTUZW68@gkar.cc.vt.edu> for manet@itd.nrl.navy.mil; Fri,
 1 Jun 2001 18:11:56 -0400 (EDT)
Date: Fri, 01 Jun 2001 18:18:31 -0400
From: Vikram Dham <vdham@vt.edu>
Subject: test
To: manet@itd.nrl.navy.mil
Reply-to: Vikram Dham <vdham@vt.edu>
Message-id: <000c01c0eae8$ca3c5e00$76c211d0@ecpe15>
MIME-version: 1.0
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
Content-type: MULTIPART/ALTERNATIVE;
 BOUNDARY="Boundary_(ID_qXpz15beYVzk8sJfkiopQg)"
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Priority: 3
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

This is a multi-part message in MIME format.

--Boundary_(ID_qXpz15beYVzk8sJfkiopQg)
Content-type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable



--Boundary_(ID_qXpz15beYVzk8sJfkiopQg)
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 content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>&nbsp;</DIV></BODY></HTML>

--Boundary_(ID_qXpz15beYVzk8sJfkiopQg)--


From owner-manet@itd.nrl.navy.mil  Tue Jun  5 06:37:56 2001
Received: from itd.nrl.navy.mil ([132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA14256
	for <manet-archive@odin.ietf.org>; Tue, 5 Jun 2001 06:37:45 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id DAA02556
	for manet-outgoing; Tue, 5 Jun 2001 03:08:35 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id DAA02551
	for <manet@itd.nrl.navy.mil>; Tue, 5 Jun 2001 03:08:32 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by boreas.isi.edu (8.11.2/8.11.2) with SMTP id f5578UG18897;
	Tue, 5 Jun 2001 00:08:30 -0700 (PDT)
Date: Tue, 5 Jun 2001 00:08:29 -0700 (PDT)
From: Ya Xu <yaxu@isi.edu>
To: Javier Gomez-Castellanos <javierg@comet.columbia.edu>
cc: Felix Ko <felix.ko@mchp.siemens.de>, manet@itd.nrl.navy.mil
Subject: Re: Power control
In-Reply-To: <Pine.GSO.3.95q.1010508111115.7103B-100000@bongo>
Message-ID: <Pine.GSO.3.96.1010604235849.10490C-100000@boreas.isi.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi,

We are working on energy conservation for ad hoc routing protocols at
USC/ISI(joint work with UCLA). We currently have two research papers on
this thread:

1. Geography-informed Energy Conservation for Ad Hoc Routing, Ya Xu,
John Heidemann, and Deborah Estrin. 
 
This paper has been accepted to the ACM MobiCom 2001. 

2. Adaptive Energy-Conserving Routing for Multihop Ad Hoc Networks,
Ya Xu, John Heidemann and Deborah Estrin, USC/ISI research report #527.

You can find the information at
http://www.isi.edu/scadds/publications.html

cheers

-Ya

On Tue, 8 May 2001, Javier Gomez-Castellanos wrote:

> 
> Hi Felix,
> 
> we are developing a power-aware routing optimization protocol for ad hoc 
> networks at Columbia University. Description of the protocol was presented
> a the last IETF meeting. 
> 
> http://www.comet.columbia.edu/~javierg/paro/draft-gomez-paro-manet-00.txt
> 
> cheers
> --Javier
> -----------------------------------------
> COMET Group
> Columbia University, New York. 	
> http://www.comet.columbia.edu/~javierg 
> On Wed, 2 May 2001, Felix Ko wrote:
> 
> > Hi!
> > 
> > I have searched the mailinglist archive but I haven't found
> > anything:
> > 
> > I am working on my diploma thesis and I am looking
> > for anything about power control in ad-hoc networks in
> > order to increase the network's capacity.
> > 
> > I searched the web and the IEEE database, but I found
> > only two publications about this subject:
> > 
> > - Jeffrey P. Monks "Transmission Power Control for Multiple
> > Access Wireless Packet Networks"
> > - Nicholas Bambos, Sunil Kandukuri, "Power Controlled Multiple
> > Access (PCMA) in Wireless Communication Networks"
> > 
> > >From my point of view, research has primarily focused on
> > energy-conserving MAC/Routing protocols, is this correct?
> > 
> > ANY HELP on this subject is greatly appreciated!!!!!
> > 
> > With kind regards
> > 
> > Felix
> > 
> > 
> > 
> 



From owner-manet@itd.nrl.navy.mil  Wed Jun  6 06:41:12 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA24718
	for <manet-archive@odin.ietf.org>; Wed, 6 Jun 2001 06:41:11 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id DAA04686
	for manet-outgoing; Wed, 6 Jun 2001 03:28:58 -0400 (EDT)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id DAA04681
	for <manet@itd.nrl.navy.mil>; Wed, 6 Jun 2001 03:28:54 -0400 (EDT)
Received: from lt.eth.ericsson.se (lt.eth.ericsson.se [164.48.158.205])
	by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with ESMTP id f567SoN15525;
	Wed, 6 Jun 2001 09:28:50 +0200 (MEST)
Received: from lt.eth.ericsson.se by lt.eth.ericsson.se (8.8.8+Sun/SMI-SVR4)
	id JAA07527; Wed, 6 Jun 2001 09:28:47 +0200 (MET DST)
Message-ID: <3B1DDBAF.228C5303@lt.eth.ericsson.se>
Date: Wed, 06 Jun 2001 09:28:47 +0200
From: Andras Valko <andras.valko@eth.ericsson.se>
X-Mailer: Mozilla 4.51 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
To: mobile-ip@sunroof.eng.sun.com, manet@itd.nrl.navy.mil
Subject: CFP : RSRCP Journal - Mobility and Internet
Content-Type: text/plain; charset=iso-8859-1
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by itd.nrl.navy.mil id DAA04686
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id GAA24718


                [Apologies if you receive multiple copies.]

                          CALL for PAPERS
                           SPECIAL ISSUE
                       MOBILITY AND INTERNET
                         of  RSRCP Journal
             http://www-r2.u-strasbg.fr/rsrcp/mintcfp.html


The RSRCP  journal, which  is now  specialized on  thematic issues on
Network and Distributed System is pleased to announce a special issue
on "Mobility and  Internet". This special  issue is sponsored by IEEE
Distributed Systems and the French IEEE Computer Chapter.

Wireless mobile access to the Internet will add new dimensions to the
way we access information and communicate. Currently, several network
protocols  are  being  studied  to  maintain communication between  a
mobile  host  and   its   correspondents  during  the  mobile  host's
movements. This  special  issue  is  devoted  to  the presentation of
recent research on  network  protocols and services  for mobile hosts
and wireless communication on the Internet.

We solicit high quality papers reporting original work in theoretical
or experimental  research. Topics  of  interest include, but  are not
limited to the following :

-  Ad hoc networks
-  Cellular IP networks
-  Distributed system aspects of mobile systems
-  Handoffs in IP networks
-  Header compression in wireless networks
-  Hierarchical mobility
-  IP-based third generation mobile and wireless networks
-  Micro-mobility architectures and protocols
-  Multicast communications for mobile hosts
-  Mobility and IPv6
-  Mobile management
-  Network protocols for mobile nodes
-  QoS in a wireless/mobile environment
-  Security and authentication
-  Service location in wireless environnement
-  Wireless LAN

Important dates:
1. Submission deadline: June 30, 2001;
2. Notifications to the authors: September, 30, 2001;
3. Publication : December 2001;

Submissions: Contributions  should  follow the instructions  and  the
format of the journal edited by Hermes.
(see http://www-r2.u-strasbg.fr/rsrcp/authorsguidelines.pdf)

Contributions  should  be original ones and should not be longer than
25  pages. Submissions  should  be  forwarded  to  the  Guest Editors
(rsrcp@clarinet.u-strasbg.fr - PS or PDF format, compressed).

Guest Editors :

            Thomas Noel                          Andras Valko

  Universite Louis Pasteur - LSIIT                Ericsson Research
Pole API - Boulevard Sébastien Brant          Traffic Laboratory
        F- 67400 - Illkirch              H-1037 Budapest, Laborc u 1.
              France                               Hungary



Editorial Board :

Scott Corson                            Francis Dupont
Flarion Technologies                    ENST - Bretagne
USA                                     France

Philip Eardley                          Thierry Ernst
British Telecom                         INRIA
UK                                      France

Andras Farago                           Hong-Yon Lach
University of Texas - Dallas            Motorola - Paris
USA                                     France

Phil Neumiller                          Thomas Noel
3Com                                    LSIIT
USA                                     France

Hesham Soliman                          Tapio Suihko
Ericsson                                VTT Technical Research Center
Australia                               Finland

C.K. Toh                                Michel Trehel
Georgia Institute of Technology         University of Franche-Comté
USA                                     France

Andras Valko
Ericsson
Hungary


From owner-manet@itd.nrl.navy.mil  Wed Jun  6 16:25:01 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA08778
	for <manet-archive@odin.ietf.org>; Wed, 6 Jun 2001 16:24:59 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id NAA21035
	for manet-outgoing; Wed, 6 Jun 2001 13:06:39 -0400 (EDT)
Received: from meshpdc.meshnetworks.com ([205.245.27.196])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id NAA21027
	for <manet@itd.nrl.navy.mil>; Wed, 6 Jun 2001 13:06:35 -0400 (EDT)
Received: by meshpdc.meshnetworks.com with Internet Mail Service (5.5.2653.19)
	id <LZCJGCK0>; Wed, 6 Jun 2001 13:06:12 -0400
Message-ID: <0DF9FBC42474A24CA50F7A27FB08E0484454F2@meshpdc.meshnetworks.com>
From: Phillip Neumiller <PNeumiller@meshnetworks.com>
To: "'James Kempf'" <James.Kempf@sun.com>, jmanner@cs.helsinki.fi
Cc: Madjid.Nakhjiri@motorola.com, charliep@iprg.nokia.com,
        hmsyed@nortelnetworks.com, seamoby@diameter.org,
        manet@itd.nrl.navy.mil
Subject: RE: [seamoby] Re: Wireless Terminology Draft
Date: Wed, 6 Jun 2001 13:06:07 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk



> -----Original Message-----
> From: James Kempf [mailto:James.Kempf@Sun.COM]
> Sent: Wednesday, June 06, 2001 11:36 AM
> I 
> don't know of any specific IETF mechanism to address this 
> procedurally,
> but I think it will be important to get review by members of all
> working groups, so we can get agreement on terminology going forward.

Hi,

There is the IETF general area....  with
Process for Organization of Internet Standards ONg (poisson) 
Last Modified: 17-May-01 

I suggest asking either:
James Galvin <galvin+ietf@elistx.com>
John Klensin <klensin@jck.com>

if a cross-WG terminology document would fall into their stewardship.




From owner-manet@itd.nrl.navy.mil  Wed Jun  6 20:06:44 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA10847
	for <manet-archive@odin.ietf.org>; Wed, 6 Jun 2001 20:06:43 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id RAA00284
	for manet-outgoing; Wed, 6 Jun 2001 17:03:15 -0400 (EDT)
Received: from email.nist.gov (email.nist.gov [129.6.2.7])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id RAA00276
	for <manet@itd.nrl.navy.mil>; Wed, 6 Jun 2001 17:03:12 -0400 (EDT)
Received: from antd.nist.gov (stratus.antd.nist.gov [129.6.50.8])
	by email.nist.gov (8.9.3/8.9.3) with ESMTP id RAA28179;
	Wed, 6 Jun 2001 17:03:06 -0400 (EDT)
Message-ID: <3B1E9AC8.6EC85E79@antd.nist.gov>
Date: Wed, 06 Jun 2001 17:04:08 -0400
From: Leonard Miller <lmiller@antd.nist.gov>
Organization: NIST
X-Mailer: Mozilla 4.7 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: MANET Discussion <manet@itd.nrl.navy.mil>, NS Users <ns-users@isi.edu>
Subject: AODV model and propagation calculator downloads; ad hoc modeling report
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 7bit

The Wireless Communications Technologies Group (WCTG) at NIST has made
available for downloading several new files related to ad hoc
networking.

OPNET MODEL FOR AODV

The first download files are for an OPNET model for the AODV MANET
routing protocol running on an 802.11 radio node platform.  The files
can be downloaded from

http://w3.antd.nist.gov/wctg/manet/prd_aodvfiles.html

A link to ZIP- and TAR-compressed file of the various model files is
made available after the user fills in a simple form for statistical
purposes.

Also available at the URL given above is a PDF file that describes the
NIST AODV model.  The author of the NIST AODV OPNET model is NIST guest
researcher Lyes Guemari.

OUTDOOR PROPAGATION CALCULATOR

The second set of download files relate to a calculator for the CCIR,
Hata, and Walfish-Ikegama propagation models.  An Excel spreadsheet and
standalone versions of the calculator for Unix and Windows can be
downloaded from

http://w3.antd.nist.gov/wctg/manet/prd_propcalc.html

A link to XLS or to ZIP- and TGZ-compressed file of the various
propagation calculator files is made available after the user fills in a
simple form for statistical
purposes.

The propagation calculator was developed by Tim Hall, based on the
spreadsheet developed by Len Miller. 

GRAPH THEORY AND RELIABILITY APPLIED TO AD HOC NETWORKS

An electronic version (PDF) has been created of the report "Tactical
Communications Network Modelling and Reliability Analysis: An Overview"
by James J. Kelleher (AD-A245339, 1991 contract report).  This report
surveys graph theory as it applies to ad hoc networks and the
calculation of network reliability measures.  The electronic version was
edited by Len Miller.  It can be downloaded at the following URL:

http://w3.antd.nist.gov/wctg/netanal/netanal_index.html


._.. . _.   __ .. ._.. ._.. . ._.   ._ _   _. .. ... _

Leonard E. Miller, Wireless Commun. Technologies Group
    National Institute of Standards & Technology (NIST)
    100 Bureau Drive Stop 8920, Bldg. 820, Room 445
    Gaithersburg, Maryland 20899-8920
Phone: 301-975-8018        Fax: 301-590-0932
email: lmiller@antd.nist.gov, Len_Miller@compuserve.com
http://w3.antd.nist.gov/wctg/
._ _. ._ ._.. _.__ ... .. ...   ._ _. _..  ... .. __ .._
.._. ._ _ .. ___ _. ___...   .__ .. ._. . ._.. . ... ...


From owner-manet@itd.nrl.navy.mil  Mon Jun 11 18:48:06 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20370
	for <manet-archive@odin.ietf.org>; Mon, 11 Jun 2001 18:48:05 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id PAA14707
	for manet-outgoing; Mon, 11 Jun 2001 15:18:57 -0400 (EDT)
Received: from SEXTANT.itd.nrl.navy.mil (sextant.itd.nrl.navy.mil [132.250.92.22])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id PAA14673;
	Mon, 11 Jun 2001 15:18:40 -0400 (EDT)
Message-Id: <5.0.1.4.2.20010611145824.03500008@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Mon, 11 Jun 2001 15:22:11 -0400
To: manet@itd.nrl.navy.mil
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: IMPORTANT: ID revision requirements
Cc: gerla@cs.ucla.edu, hxy@cs.ucla.edu, mary@cs.ucla.edu,
        gpei@rsc.rockwell.com, haas@ee.cornell.edu, pearlman@ee.cornell.edu,
        samar@ee.cornell.edu, park@flarion.com, corson@flarion.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

All:

We (the chairs) have received guidance from the Routing Area ADs that 
RFC2026 non-conforming document statements should be not be allowed in any 
IDs considered within the WG context.  The statement template appeared as 
the last of the three optional headers in the ID author guidance 
document..the guidance document is now out of date.

The chairs agree with this philosophy, but the guidance was unclear in the 
past for non-status IDs and several such documents were allowed to be 
posted with the manet extension.

Authors of affected documents need to revise these statements and resubmit 
to be in a conformant style or their documents will be removed in the near 
future and will not be considered within the manet WG context (nor any 
other WG). I would like to ask the ID authors to please inform us of your 
intentions as soonas possible.

 From my reading this affects the following active documents:

draft-ietf-manet-tora-spec-03.txt
draft-ietf-manet-lanmar-01.txt
draft-ietf-manet-fsr-00.txt
- all zrp derivatives below
draft-ietf-manet-zone-ierp-00.txt
draft-ietf-manet-zone-iarp-00.txt
draft-ietf-manet-zone-brp-00.txt

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



From owner-manet@itd.nrl.navy.mil  Fri Jun 15 09:21:53 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA06985
	for <manet-archive@odin.ietf.org>; Fri, 15 Jun 2001 09:21:52 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id GAA28630
	for manet-outgoing; Fri, 15 Jun 2001 06:48:15 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id GAA28625
	for <manet@itd.nrl.navy.mil>; Fri, 15 Jun 2001 06:48:11 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02814;
	Fri, 15 Jun 2001 06:47:40 -0400 (EDT)
Message-Id: <200106151047.GAA02814@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@itd.nrl.navy.mil
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-manet-lanmar-02.txt
Date: Fri, 15 Jun 2001 06:47:40 -0400
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: Landmark Routing Protocol (LANMAR) for Large Scale Ad 
                          Hoc Networks
	Author(s)	: M. Gerla et al.
	Filename	: draft-ietf-manet-lanmar-02.txt
	Pages		: 19
	Date		: 14-Jun-01
	
The Landmark Routing Protocol (LANMAR) utilizes the concept of 
'landmark' for scalable routing in large, mobile ad hoc networks.  
It relies on the notion of group mobility: i.e., a logical group 
(for example a team of coworkers at a convention) moves in a 
coordinated fashion.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-lanmar-02.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-lanmar-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-lanmar-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010614124538.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-lanmar-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-lanmar-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010614124538.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-manet@itd.nrl.navy.mil  Fri Jun 15 09:22:07 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07013
	for <manet-archive@odin.ietf.org>; Fri, 15 Jun 2001 09:22:06 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id GAA28637
	for manet-outgoing; Fri, 15 Jun 2001 06:48:19 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id GAA28632
	for <manet@itd.nrl.navy.mil>; Fri, 15 Jun 2001 06:48:16 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02830;
	Fri, 15 Jun 2001 06:47:45 -0400 (EDT)
Message-Id: <200106151047.GAA02830@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@itd.nrl.navy.mil
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-manet-fsr-01.txt
Date: Fri, 15 Jun 2001 06:47:44 -0400
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: Fisheye State Routing Protocol (FSR) for Ad Hoc 
                          Networks
	Author(s)	: M. Gerla et al.
	Filename	: draft-ietf-manet-fsr-01.txt
	Pages		: 17
	Date		: 14-Jun-01
	
The Fisheye State Routing (FSR) algorithm for ad hoc networks 
introduces the notion of multi-level 'scope' to reduce routing 
update overhead in large networks.  A node stores the Link State 
for every destination in the network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-fsr-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-fsr-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-fsr-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010614124610.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-fsr-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-fsr-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010614124610.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-manet@itd.nrl.navy.mil  Sun Jun 17 18:31:06 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12575
	for <manet-archive@odin.ietf.org>; Sun, 17 Jun 2001 18:31:06 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id PAA03555
	for manet-outgoing; Sun, 17 Jun 2001 15:31:53 -0400 (EDT)
Received: from mail.utexas.edu (wb3-a.mail.utexas.edu [128.83.126.138])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with SMTP id PAA03550
	for <manet@itd.nrl.navy.mil>; Sun, 17 Jun 2001 15:31:50 -0400 (EDT)
Received: (qmail 26951 invoked by uid 0); 17 Jun 2001 19:31:50 -0000
Received: from fedallah.cs.utexas.edu (HELO mail.utexas.edu) (128.83.144.172)
  by umbs-smtp-3 with SMTP; 17 Jun 2001 19:31:50 -0000
Message-ID: <3B2D05A6.C31F5EEA@mail.utexas.edu>
Date: Sun, 17 Jun 2001 14:31:50 -0500
From: Huaiyu Liu <huaiyu@mail.utexas.edu>
X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: manet@itd.nrl.navy.mil
Subject: Ad hoc network applications
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

Could anybody summarize the existing/potential ad hoc network
applications?

Or does any one know where I can find lists of such applications?

Thanks.

-Kitty



From owner-manet@itd.nrl.navy.mil  Wed Jun 20 10:41:14 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA09455
	for <manet-archive@odin.ietf.org>; Wed, 20 Jun 2001 10:41:13 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id HAA11864
	for manet-outgoing; Wed, 20 Jun 2001 07:29:34 -0400 (EDT)
Received: from omail01.samsung.co.kr (omail01.samsung.co.kr [203.254.197.73])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id HAA11854
	for <manet@itd.nrl.navy.mil>; Wed, 20 Jun 2001 07:29:30 -0400 (EDT)
From: prasad@samsung.co.kr
Received: from localhost (root@localhost)
	by gp_xman. (8.8.8H1/8.8.8) with ESMTP id UAA01948
	for <manet@itd.nrl.navy.mil>; Wed, 20 Jun 2001 20:31:24 +0900 (KST)
X-OpenMail-Hops: 2
Date: Wed, 20 Jun 2001 20:29:25 +0900
Message-Id: <H000103f058ed751.0993035265.secsw0@MHS>
Subject: ZRP :question on query detection 
MIME-Version: 1.0
TO: manet@itd.nrl.navy.mil
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline; filename="mail.txt"
	;Creation-Date="Wed, 20 Jun 2001 20:07:47 +0900"
	;Modification-Date="Wed, 20 Jun 2001 20:29:17 +0900"
Content-Transfer-Encoding: 8bit
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi friends,
 I am implementing ZRP protocol for ad hoc networks. i have a question on boarder Resolution Protocol (BRP) which is implemented as a part of ZRP.
The <draft-ietf-manet-zone-brp-00.txt> says that Query controle mechanisms can be used to efficiently steer the route query packets.
I am not able to understand the concepts of QD1 , QD2 and also Early Termination (ET).
Can any one help me by explaining  these concepts with some examples.
Your help is heighly appreciated.

Thanks in advance
PRASAD
SAMSUNG, India
Bangalore
India.



From owner-manet@itd.nrl.navy.mil  Wed Jun 20 20:35:11 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA27331
	for <manet-archive@odin.ietf.org>; Wed, 20 Jun 2001 20:35:11 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id RAA03154
	for manet-outgoing; Wed, 20 Jun 2001 17:40:59 -0400 (EDT)
Date: Wed, 20 Jun 2001 13:15:32 -0400 (EDT)
From: Marc Pearlman <pearlman@ee.cornell.edu>
To: prasad@samsung.co.kr
cc: manet@itd.nrl.navy.mil, Zygmunt Haas <haas@ee.cornell.edu>,
        Prince Samar <samar@ee.cornell.edu>
Subject: RE: ZRP :question on query detection (fwd)
Message-ID: <Pine.GSO.4.21.0106201305290.21580-100000@descartes.ee.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi Prasad,

First, take a look at the following paper, scheduled to appear in
Transactions on Networking, August 2001:

"The Performance of Query Control Schemes for the Zone Routing Protocol",
Z.J. Haas and M.R. Pearlman
(http://www.ee.cornell.edu/~haas/Publications/tn8.ps)

This paper describes various query control mechanisms (including QD and
ET), and provides illustrative examples.


If you visualize route request (RREQ) messages propagating through the
network, you can divide the network into two regions: covered and
uncovered.  Loosely speaking, the covered region marks where the RREQ has
been, while the uncovered region marks where the RREQ has not yet
appeared.  The objective of is to send RREQs outward into the *uncovered*
region, and not back into the *covered* region.

In broadcast-based route discovery, nodes that receive the RREQ are
covered -  those that have not received the RREQ are uncovered.  We extend
this concept to bordercasting (ZRP) by addressing the role of routing
zones.  In particular, a node is covered if it belongs to the routing zone
of a node that bordercasts the RREQ.  All other nodes in the network are
uncovered.  This is a powerful property, because it means that nodes can
be covered without actually having to receive a RREQ.

This leads into my brief explanation of QD and ET, which are complementary
query control mechanisms for ZRP.  As I stated above, the objective of
query based route discovery protocols is to relay the RREQs to the
uncovered regions and away from the covered regions.  In ZRP, this means
that relaying nodes need to be able to identify covered regions of the
network (Query Detection = QD) and terminate messages that are headed for
those covered regions (Early Termination = ET)

In Query Detection (QD), a node examines each received RREQ and identifies
the most recent bordercaster of the RREQ.  That bordercaster, and *its
entire routing zone*, are marked as covered.  The distinction between QD1
and QD2 has to do with which RREQ messages a node is able to
receive/examine.   At a minimum (QD1), a node receives (and examines) the
messages that it relays from a bordercaster to its peripheral node(s).  In
QD2, a node may receive any RREQ transmitted in its neighborhood, thanks
to a shared broadcast channel.  More received messages == bettery query
detection.

RREQs are relayed from a bordercaster to its peripheral nodes along a
bordercast (multicast) tree. The relaying nodes in the bordercast tree use
Early Termination (ET) to identify *covered* downstream peripheral nodes
and prune them from the bordercast tree (see note at bottom).  The pruning of
covered peripheral nodes serves to steer the RREQ outward.

I hope this sheds some light on the operation of ZRP and its query control
mechanisms.  Let me know if I you'd like me to address any of these issues
in more detail.


regards,

Marc


Note:  in the current incarnation of bordercasting, the rules for ET
pruning are a little more complicated than described above.  Covered nodes
that are not strictly inside (ie. not peripheral) a covered routing zone
need to be dealt with specially (see BRP ID draft or cited ToN paper for
details).  This is to avoid a possible starvation condition that can occur
when two bordercasters forward a RREQ to the same peripheral node at
approximately the same time (the two RREQ "threads" might effectively
cancel each other out).

The Early Termination criteria, as specified in the BRP draft and ToN
paper, provides provably correct ZRP operation.

We have also developed a modifed version of bordercasting / query
control.  This eliminates the starvation problem, allowing ET to simply
prune all covered peripheral nodes, without special consideration.  I
believe Prince Samar described this "MZRP" at the last MANET WG meeting.



 > Hi friends,
 >  I am implementing ZRP protocol for ad hoc networks. i have a
 > question on boarder Resolution Protocol (BRP) which is
 > implemented as a part of ZRP.
 > The <draft-ietf-manet-zone-brp-00.txt> says that Query
 > controle mechanisms can be used to efficiently steer the
 > route query packets.
 > I am not able to understand the concepts of QD1 , QD2 and
 > also Early Termination (ET).
 > Can any one help me by explaining  these concepts with some examples.
 > Your help is heighly appreciated.
 >
 > Thanks in advance
 > PRASAD
 > SAMSUNG, India
 > Bangalore
 > India.
 >
 > 



From owner-manet@itd.nrl.navy.mil  Thu Jun 21 08:59:07 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA26580
	for <manet-archive@odin.ietf.org>; Thu, 21 Jun 2001 08:59:06 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id FAA11585
	for manet-outgoing; Thu, 21 Jun 2001 05:51:19 -0400 (EDT)
Received: from omail01.samsung.co.kr (omail01.samsung.co.kr [203.254.197.73])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id FAA11580
	for <manet@itd.nrl.navy.mil>; Thu, 21 Jun 2001 05:51:15 -0400 (EDT)
From: prasad@samsung.co.kr
Received: from localhost (root@localhost)
	by gp_xman. (8.8.8H1/8.8.8) with ESMTP id SAA07938
	for <manet@itd.nrl.navy.mil>; Thu, 21 Jun 2001 18:53:11 +0900 (KST)
X-OpenMail-Hops: 2
Date: Thu, 21 Jun 2001 18:51:13 +0900
Message-Id: <H000103f0593d621.0993116405.secsw0@MHS>
Subject: RE: ZRP :question on query detection (fwd)
MIME-Version: 1.0
TO: manet@itd.nrl.navy.mil
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline; filename="mail.txt"
	;Creation-Date="Thu, 21 Jun 2001 18:40:08 +0900"
	;Modification-Date="Thu, 21 Jun 2001 18:51:06 +0900"
Content-Transfer-Encoding: 8bit
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi Marc,
              Thank you very much for your clarification and it helped us to a great extent.

     We still have some doubts on following topic.
   
    1. Extended routing zone  -  what is the scope of this extended routing zone and the concept of (2R-1).

     We will be looking forward for your clarification.

Thanks & Regards,
Prasad.
     
      
    
       Hi Prasad,

First, take a look at the following paper, scheduled to appear in 
Transactions on Networking, August 2001:

"The Performance of Query Control Schemes for the Zone Routing Protocol", 
Z.J. Haas and M.R. Pearlman 
(http://www.ee.cornell.edu/~haas/Publications/tn8.ps)

This paper describes various query control mechanisms (including QD and
ET), and provides illustrative examples.


If you visualize route request (RREQ) messages propagating through the
network, you can divide the network into two regions: covered and 
uncovered.  Loosely speaking, the covered region marks where the RREQ has
been, while the uncovered region marks where the RREQ has not yet
appeared.  The objective of is to send RREQs outward into the *uncovered*
region, and not back into the *covered* region.

In broadcast-based route discovery, nodes that receive the RREQ are
covered -  those that have not received the RREQ are uncovered.  We extend
this concept to bordercasting (ZRP) by addressing the role of routing 
zones.  In particular, a node is covered if it belongs to the routing zone
of a node that bordercasts the RREQ.  All other nodes in the network are 
uncovered.  This is a powerful property, because it means that nodes can
be covered without actually having to receive a RREQ.

This leads into my brief explanation of QD and ET, which are complementary 
query control mechanisms for ZRP.  As I stated above, the objective of
query based route discovery protocols is to relay the RREQs to the 
uncovered regions and away from the covered regions.  In ZRP, this means 
that relaying nodes need to be able to identify covered regions of the
network (Query Detection = QD) and terminate messages that are headed for
those covered regions (Early Termination = ET)

In Query Detection (QD), a node examines each received RREQ and identifies 
the most recent bordercaster of the RREQ.  That bordercaster, and *its
entire routing zone*, are marked as covered.  The distinction between QD1
and QD2 has to do with which RREQ messages a node is able to
receive/examine.   At a minimum (QD1), a node receives (and examines) the
messages that it relays from a bordercaster to its peripheral node(s).  In
QD2, a node may receive any RREQ transmitted in its neighborhood, thanks
to a shared broadcast channel.  More received messages == bettery query 
detection.

RREQs are relayed from a bordercaster to its peripheral nodes along a 
bordercast (multicast) tree. The relaying nodes in the bordercast tree use
Early Termination (ET) to identify *covered* downstream peripheral nodes
and prune them from the bordercast tree (see note at bottom).  The pruning of
covered peripheral nodes serves to steer the RREQ outward.

I hope this sheds some light on the operation of ZRP and its query control
mechanisms.  Let me know if I you'd like me to address any of these issues
in more detail.


regards,

Marc


Note:  in the current incarnation of bordercasting, the rules for ET 
pruning are a little more complicated than described above.  Covered nodes
that are not strictly inside (ie. not peripheral) a covered routing zone
need to be dealt with specially (see BRP ID draft or cited ToN paper for 
details).  This is to avoid a possible starvation condition that can occur
when two bordercasters forward a RREQ to the same peripheral node at 
approximately the same time (the two RREQ "threads" might effectively
cancel each other out).

The Early Termination criteria, as specified in the BRP draft and ToN
paper, provides provably correct ZRP operation.  

We have also developed a modifed version of bordercasting / query
control.  This eliminates the starvation problem, allowing ET to simply
prune all covered peripheral nodes, without special consideration.  I
believe Prince Samar described this "MZRP" at the last MANET WG meeting.



> Hi friends,
>  I am implementing ZRP protocol for ad hoc networks. i have a 
> question on boarder Resolution Protocol (BRP) which is 
> implemented as a part of ZRP.
> The <draft-ietf-manet-zone-brp-00.txt> says that Query 
> controle mechanisms can be used to efficiently steer the 
> route query packets.
> I am not able to understand the concepts of QD1 , QD2 and 
> also Early Termination (ET).
> Can any one help me by explaining  these concepts with some examples.
> Your help is heighly appreciated.
> 
> Thanks in advance
> PRASAD
> SAMSUNG, India
> Bangalore
> India.
> 
> 

                                               
/--------------------------------< Header >--------------------------------/
Received: from imail02.samsung.co.kr (imail02.samsung.co.kr [101.1.3.102])
	by gp_xman. (8.8.8H1/8.8.8) with ESMTP id CAA09132
	for <prasad@[101.1.3.30]>; Thu, 21 Jun 2001 02:18:09 +0900 (KST)
Received: from ee.cornell.edu (anise.ee.cornell.edu [128.84.239.14])
	by imail02.samsung.co.kr (8.8.8/8.8.8) with ESMTP id CAA13382
	for <prasad@samsung.co.kr>; Thu, 21 Jun 2001 02:12:51 +0900 (KST)
Received: from descartes (descartes.ee.cornell.edu [128.84.236.60])
	by ee.cornell.edu (8.9.3/8.9.1) with ESMTP id NAA04781;
	Wed, 20 Jun 2001 13:16:06 -0400 (EDT)
Date: Wed, 20 Jun 2001 13:15:32 -0400 (EDT)
From: Marc Pearlman <pearlman@ee.cornell.edu>
To: prasad@samsung.co.kr
cc: manet@itd.nrl.navy.mil, Zygmunt Haas <haas@ee.cornell.edu>,
        Prince Samar <samar@ee.cornell.edu>
Subject: RE: ZRP :question on query detection (fwd)
Message-ID: <Pine.GSO.4.21.0106201305290.21580-100000@descartes.ee.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



From owner-manet@itd.nrl.navy.mil  Fri Jun 22 09:38:01 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA21083
	for <manet-archive@odin.ietf.org>; Fri, 22 Jun 2001 09:38:01 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id HAA04301
	for manet-outgoing; Fri, 22 Jun 2001 07:13:48 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id HAA04293
	for <manet@itd.nrl.navy.mil>; Fri, 22 Jun 2001 07:13:42 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16071;
	Fri, 22 Jun 2001 07:13:06 -0400 (EDT)
Message-Id: <200106221113.HAA16071@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@itd.nrl.navy.mil
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-manet-zone-ierp-01.txt
Date: Fri, 22 Jun 2001 07:13:06 -0400
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: The Interzone Routing Protocol (IERP) for Ad Hoc 
                          Networks
	Author(s)	: Z. Haas et al.
	Filename	: draft-ietf-manet-zone-ierp-01.txt
	Pages		: 14
	Date		: 21-Jun-01
	
This document describes the Interzone Routing Protocol (IERP), the
reactive routing component of the Zone Routing Protocol (ZRP).  
IERP adapts existing reactive routing protocol implementations to
take advantage of the known topology of each node's surrounding 
r-hop neighborhood (routing zone), provided by the Intrazone 
Routing Protocol (IARP).  The availability of routing zone routes 
allows IERP to suppress route queries for local destinations.  
When a global route discovery is required, the routing zone based 
bordercast service can be used to efficiently guide route queries 
outward, rather than blindly relaying queries from neighbor to
neighbor.   Once a route has been discovered, IERP can use routing
zones to automatically redirect data around failed links.  
Similarly, suboptimal route segments can be identified and traffic
re-routed along shorter paths.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-zone-ierp-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-zone-ierp-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-zone-ierp-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010621134525.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-zone-ierp-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-zone-ierp-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010621134525.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-manet@itd.nrl.navy.mil  Fri Jun 22 09:38:14 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA21103
	for <manet-archive@odin.ietf.org>; Fri, 22 Jun 2001 09:38:14 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id HAA04305
	for manet-outgoing; Fri, 22 Jun 2001 07:13:50 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id HAA04299
	for <manet@itd.nrl.navy.mil>; Fri, 22 Jun 2001 07:13:47 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16087;
	Fri, 22 Jun 2001 07:13:11 -0400 (EDT)
Message-Id: <200106221113.HAA16087@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@itd.nrl.navy.mil
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-manet-zone-iarp-01.txt
Date: Fri, 22 Jun 2001 07:13:11 -0400
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: The Intrazone Routing Protocol (IARP) for Ad Hoc 
                          Networks
	Author(s)	: Z. Haas et al.
	Filename	: draft-ietf-manet-zone-iarp-01.txt
	Pages		: 11
	Date		: 21-Jun-01
	
This document describes the Intrazone Routing Protocol (IARP), a
limited scope proactive routing protocol used to improve the
performance of existing globally reactive routing protocols.  With
each node monitoring changes in its surrounding r-hop neighborhood
(routing zone), global route discoveries to local destinations can be
avoided.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-zone-iarp-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-zone-iarp-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-zone-iarp-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010621134535.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-zone-iarp-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-zone-iarp-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010621134535.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-manet@itd.nrl.navy.mil  Fri Jun 22 09:52:55 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA21636
	for <manet-archive@odin.ietf.org>; Fri, 22 Jun 2001 09:52:53 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id HAA04310
	for manet-outgoing; Fri, 22 Jun 2001 07:13:55 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id HAA04291
	for <manet@itd.nrl.navy.mil>; Fri, 22 Jun 2001 07:13:36 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16055;
	Fri, 22 Jun 2001 07:12:59 -0400 (EDT)
Message-Id: <200106221112.HAA16055@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@itd.nrl.navy.mil
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-manet-zone-brp-01.txt
Date: Fri, 22 Jun 2001 07:12:59 -0400
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: The Bordercast Resolution Protocol (BRP) for Ad Hoc 
                          Networks
	Author(s)	: Z. Haas et al.
	Filename	: draft-ietf-manet-zone-brp-01.txt
	Pages		: 13
	Date		: 21-Jun-01
	
The Bordercast Resolution Protocol (BRP) provides the bordercasting
packet delivery service used to support network querying applications.
The BRP uses a map of an extended routing zone, provided by the local
proactive Intrazone Routing Protocol (IARP), to construct bordercast
(multicast) trees, along which query packets are directed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-zone-brp-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-zone-brp-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-zone-brp-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010621134516.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-zone-brp-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-zone-brp-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20010621134516.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-manet@itd.nrl.navy.mil  Fri Jun 22 12:27:56 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA29341
	for <manet-archive@odin.ietf.org>; Fri, 22 Jun 2001 12:27:55 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id KAA09618
	for manet-outgoing; Fri, 22 Jun 2001 10:06:31 -0400 (EDT)
Date: Fri, 22 Jun 2001 07:20:50 -0400 (EDT)
From: Marc Pearlman <pearlman@ee.cornell.edu>
To: manet@itd.nrl.navy.mil
Subject: Fw: ZRP :question on query detection (fwd)
Message-ID: <Pine.GSO.4.21.0106220719080.23524-100000@descartes.ee.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi Prasad,

 >      We still have some doubts on following topic.
 >
 >     1. Extended routing zone  -  what is the scope of this
 > extended routing zone and the concept of (2R-1).
 >
 >

To understand where the (2*R-1) EXTENDED routing zone comes from, we need
to determine how much local topology each node must know in order to
support R hop bordercast (ie. bordercast to peripheral nodes that are R
hops away).

Consider a bordercasting node X.

  I.  A bordercasting node X needs to:
     (a) identify its interior nodes (for Query Detection (QD) / Early 
Termination (ET))
     (b) identify its downstream peripheral nodes (for QD/ET)
     (c) construct its R hop bordercast tree.

To meet criteria a-c, it is sufficient for X to know its surrounding R hop
topology.


  However...

  II.  Each interior node Y of X's routing zone must be able to:
     (a) identify X's interior nodes (for QD/ET)
     (b) identify X's peripheral nodes that are downstream of Y (for QD/ET)
     (c) construct X's R hop bordercast tree.

To meet criteria a-c, X's interior nodes (which are no more than R-1 hops
from X) need to know their surrounding (R)+(R-1) == 2*R-1 hop topology.

  III.  Each peripheral node Z of X's routing zone must be able to:
     (a) identify X's interior nodes (for QD/ET)

      (note:  Conditions (b) and (c) do not apply since Z is the target leaf
		in X's bordercast tree)

To meet this criterion, X's peripheral nodes (which are R hops from X)
need to know their surrounding (R)+(R-1) == 2*R-1 hop topology.


Taking the maximum of the local topology requirements from conditions I,II
and III, we find that bordercasting to R hop peripheral nodes can be
supported if each node proactively tracks the topology of its surrounding
(2*R-1) hop EXTENDED routing zone.


Having said all this, it is worth mentioning that ZRP can be modified to
reduce (and in some cases eliminate) the 2*R-1 hop EXTENDED routing zone
requirement.  For example, X could append a map of its bordercast tree (or
even entire routing zone) to its bordercast RREQ packet.  This "source
directed bordercast" eliminates the need for relaying nodes to reconstruct
X's bordercast tree on their own.  Query Detection / Early termination can
function correctly given a reduced view of X's routing zone.  However,
this degrades the steering capability of the query control mechanisms.
Finally, re-bordercasting can occur before the RREQ reaches X's peripheral
node.  (For example, re-bordercasting occurs at every hop in MZRP.)
This also degrades query steering capability somewhat, but it reduces the
EXTENDED routing zone requirement to R+1 hops (and actually eliminates
the need for EXTENDED routing zones on systems that don't use/have
MAC broadcast).

The point is that there is no free lunch.  We can reduce IARP's burden of
tracking an extended routing zone.  However, it adds some overhead to the
reactive route discovery process.  Our experience to date has been that
these modifications don't have much effect on the overall ZRP traffic
load.  However, there are some secondary benefits (eg. reduced
computational load, less complicated protocol implementation, easier
analysis, etc.) that make some of the aforementioned approaches
attractive.


regards,

Marc


 > > > ---------- Forwarded message ----------
 > > > Date: Thu, 21 Jun 2001 18:51:13 +0900
 > > > From: prasad@samsung.co.kr
 > > > To: manet@itd.nrl.navy.mil
 > > > Subject: RE: ZRP :question on query detection (fwd)
 > > >
 > > > Hi Marc,
 > > >               Thank you very much for your clarification and
 > > > it helped us to a great extent.
 > > >
 > > >      We still have some doubts on following topic.
 > > >
 > > >     1. Extended routing zone  -  what is the scope of this
 > > > extended routing zone and the concept of (2R-1).
 > > >
 > > >      We will be looking forward for your clarification.
 > > >
 > > > Thanks & Regards,
 > > > Prasad.
 > > >
 > > >
 > > >
 > > >        Hi Prasad,
 > > >
 > > > First, take a look at the following paper, scheduled to appear in
 > > > Transactions on Networking, August 2001:
 > > >
 > > > "The Performance of Query Control Schemes for the Zone
 > > > Routing Protocol",
 > > > Z.J. Haas and M.R. Pearlman
 > > > (http://www.ee.cornell.edu/~haas/Publications/tn8.ps)
 > > >
 > > > This paper describes various query control mechanisms
 > > > (including QD and
 > > > ET), and provides illustrative examples.
 > > >
 > > >
 > > > If you visualize route request (RREQ) messages propagating through the
 > > > network, you can divide the network into two regions: covered and
 > > > uncovered.  Loosely speaking, the covered region marks where
 > > > the RREQ has
 > > > been, while the uncovered region marks where the RREQ has not yet
 > > > appeared.  The objective of is to send RREQs outward into the
 > > > *uncovered*
 > > > region, and not back into the *covered* region.
 > > >
 > > > In broadcast-based route discovery, nodes that receive the RREQ are
 > > > covered -  those that have not received the RREQ are
 > > > uncovered.  We extend
 > > > this concept to bordercasting (ZRP) by addressing the role of routing
 > > > zones.  In particular, a node is covered if it belongs to the
 > > > routing zone
 > > > of a node that bordercasts the RREQ.  All other nodes in the
 > > > network are
 > > > uncovered.  This is a powerful property, because it means
 > > > that nodes can
 > > > be covered without actually having to receive a RREQ.
 > > >
 > > > This leads into my brief explanation of QD and ET, which are
 > > > complementary
 > > > query control mechanisms for ZRP.  As I stated above, the objective of
 > > > query based route discovery protocols is to relay the RREQs to the
 > > > uncovered regions and away from the covered regions.  In ZRP,
 > > > this means
 > > > that relaying nodes need to be able to identify covered regions of the
 > > > network (Query Detection = QD) and terminate messages that
 > > > are headed for
 > > > those covered regions (Early Termination = ET)
 > > >
 > > > In Query Detection (QD), a node examines each received RREQ
 > > > and identifies
 > > > the most recent bordercaster of the RREQ.  That bordercaster, and *its
 > > > entire routing zone*, are marked as covered.  The distinction
 > > > between QD1
 > > > and QD2 has to do with which RREQ messages a node is able to
 > > > receive/examine.   At a minimum (QD1), a node receives (and
 > > > examines) the
 > > > messages that it relays from a bordercaster to its peripheral
 > > > node(s).  In
 > > > QD2, a node may receive any RREQ transmitted in its
 > > > neighborhood, thanks
 > > > to a shared broadcast channel.  More received messages ==
 > > > bettery query
 > > > detection.
 > > >
 > > > RREQs are relayed from a bordercaster to its peripheral nodes along a
 > > > bordercast (multicast) tree. The relaying nodes in the
 > > > bordercast tree use
 > > > Early Termination (ET) to identify *covered* downstream
 > > > peripheral nodes
 > > > and prune them from the bordercast tree (see note at bottom).
 > > >  The pruning of
 > > > covered peripheral nodes serves to steer the RREQ outward.
 > > >
 > > > I hope this sheds some light on the operation of ZRP and its
 > > > query control
 > > > mechanisms.  Let me know if I you'd like me to address any of
 > > > these issues
 > > > in more detail.
 > > >
 > > >
 > > > regards,
 > > >
 > > > Marc
 > > >
 > > >
 > > > Note:  in the current incarnation of bordercasting, the rules for ET
 > > > pruning are a little more complicated than described above.
 > > > Covered nodes
 > > > that are not strictly inside (ie. not peripheral) a covered
 > > > routing zone
 > > > need to be dealt with specially (see BRP ID draft or cited
 > > > ToN paper for
 > > > details).  This is to avoid a possible starvation condition
 > > > that can occur
 > > > when two bordercasters forward a RREQ to the same peripheral node at
 > > > approximately the same time (the two RREQ "threads" might effectively

 > > > cancel each other out).
 > > >
 > > > The Early Termination criteria, as specified in the BRP draft and ToN
 > > > paper, provides provably correct ZRP operation.
 > > >
 > > > We have also developed a modifed version of bordercasting / query
 > > > control.  This eliminates the starvation problem, allowing ET
 > > > to simply
 > > > prune all covered peripheral nodes, without special consideration.  I
 > > > believe Prince Samar described this "MZRP" at the last MANET
 > > > WG meeting.
 > > >
 > > >
 > > >
 > > > > Hi friends,
 > > > >  I am implementing ZRP protocol for ad hoc networks. i have a
 > > > > question on boarder Resolution Protocol (BRP) which is
 > > > > implemented as a part of ZRP.
 > > > > The <draft-ietf-manet-zone-brp-00.txt> says that Query
 > > > > controle mechanisms can be used to efficiently steer the
 > > > > route query packets.
 > > > > I am not able to understand the concepts of QD1 , QD2 and
 > > > > also Early Termination (ET).
 > > > > Can any one help me by explaining  these concepts with some
 > > > examples.
 > > > > Your help is heighly appreciated.
 > > > >
 > > > > Thanks in advance
 > > > > PRASAD
 > > > > SAMSUNG, India
 > > > > Bangalore
 > > > > India.
 > > > >
 > > > >
 > > >
 > > >
 > > > /--------------------------------< Header
 > > > >--------------------------------/
 > > > Received: from imail02.samsung.co.kr (imail02.samsung.co.kr
 > > > [101.1.3.102])
 > > > by gp_xman. (8.8.8H1/8.8.8) with ESMTP id CAA09132
 > > > for <prasad@[101.1.3.30]>; Thu, 21 Jun 2001 02:18:09 +0900 (KST)
 > > > Received: from ee.cornell.edu (anise.ee.cornell.edu [128.84.239.14])
 > > > by imail02.samsung.co.kr (8.8.8/8.8.8) with ESMTP id CAA13382
 > > > for <prasad@samsung.co.kr>; Thu, 21 Jun 2001 02:12:51
 > > > +0900 (KST)
 > > > Received: from descartes (descartes.ee.cornell.edu [128.84.236.60])
 > > > by ee.cornell.edu (8.9.3/8.9.1) with ESMTP id NAA04781;
 > > > Wed, 20 Jun 2001 13:16:06 -0400 (EDT)
 > > > Date: Wed, 20 Jun 2001 13:15:32 -0400 (EDT)
 > > > From: Marc Pearlman <pearlman@ee.cornell.edu>
 > > > To: prasad@samsung.co.kr
 > > > cc: manet@itd.nrl.navy.mil, Zygmunt Haas <haas@ee.cornell.edu>,
 > > >         Prince Samar <samar@ee.cornell.edu>
 > > > Subject: RE: ZRP :question on query detection (fwd)
 > > > Message-ID:
 > > > <Pine.GSO.4.21.0106201305290.21580-100000@descartes.ee.cornell.edu>
 > > > MIME-Version: 1.0
 > > > Content-Type: TEXT/PLAIN; charset=US-ASCII
 > > >
 > > >
 > >
 > >
 >



From owner-manet@itd.nrl.navy.mil  Tue Jun 26 09:17:48 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA02686
	for <manet-archive@odin.ietf.org>; Tue, 26 Jun 2001 09:17:46 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id GAA08848
	for manet-outgoing; Tue, 26 Jun 2001 06:25:54 -0400 (EDT)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id GAA08843
	for <manet@itd.nrl.navy.mil>; Tue, 26 Jun 2001 06:25:51 -0400 (EDT)
From: Leping.Huang@nokia.com
Received: from esvir02nok.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34])
	by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f5QAQ7323096
	for <manet@itd.nrl.navy.mil>; Tue, 26 Jun 2001 13:26:07 +0300 (EET DST)
Received: from esebh25nok.ntc.nokia.com (unverified) by esvir02nok.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T546151002bac158f22077@esvir02nok.nokia.com> for <manet@itd.nrl.navy.mil>;
 Tue, 26 Jun 2001 13:25:51 +0300
Received: by esebh25nok with Internet Mail Service (5.5.2652.78)
	id <MV1LZKZ7>; Tue, 26 Jun 2001 13:25:51 +0300
Message-ID: <6468108794D6D311AB850008C72B5EA40468A799@toeis01nok>
To: manet@itd.nrl.navy.mil
Subject: question about QoS for AODV draft
Date: Tue, 26 Jun 2001 13:25:37 +0300
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2652.78)
Content-Type: text/plain;
	charset="iso-2022-jp"
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi:

I have read an expired draft "QoS for AODV" recently.  
I have several questions about this extension.

1. Does an intermdediate node need to make resouce reservation after
forwarding of RREP? (it seems that link is established after forwarding of
RREP)
2. does intermediate node hold the bandwidth/delay information about
downstream node? if so, how can it get these info? if not, intermediate node
can not reply the RREQ.
3. does this extension use priority queue algorithm in intermediate node?

I feel confused with this draft.   Are there any plan to refresh this draft?

I think QoS communication need end-to-end reservation or priority
configuration, but AODV try to reply RREQ at intermediate node, is AODV not
suitable for QOS communication?

I just enter this ML recently, if someone have the copy of discussion about
QoS for AODV, can u forward it to me?
 Besides, are there any research/implementation works now on QoS extention
for AODV?

----------------------------------------------------
Leping HUANG
Research Engineer
Nokia Research Center Japan
2-13-5, Nagata-cho Chiyoda-ku, Tokyo 100-0014, Japan
Tel: +81-3-3592-3528  Fax: +81-3-3592-3555 
-----------------------------------------------------


From owner-manet@itd.nrl.navy.mil  Tue Jun 26 14:00:57 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA01219
	for <manet-archive@odin.ietf.org>; Tue, 26 Jun 2001 14:00:54 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA17854
	for manet-outgoing; Tue, 26 Jun 2001 11:12:50 -0400 (EDT)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id LAA17846
	for <manet@itd.nrl.navy.mil>; Tue, 26 Jun 2001 11:12:46 -0400 (EDT)
Received: from darkstar.iprg.nokia.com (darkstar.iprg.nokia.com [205.226.5.69])
	by mailhost.iprg.nokia.com (8.9.3/8.9.3-GLGS) with ESMTP id IAA13654;
	Tue, 26 Jun 2001 08:12:46 -0700 (PDT)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f5QFCkM03161;
	Tue, 26 Jun 2001 08:12:46 -0700
X-mProtect:  Tue, 26 Jun 2001 08:12:46 -0700 Nokia Silicon Valley Messaging Protection
Received: from charliep.iprg.nokia.com (205.226.2.89, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com(P1.5 smtpdNeg4Vv; Tue, 26 Jun 2001 08:12:44 PDT
Message-ID: <3B38A66B.B348AB22@iprg.nokia.com>
Date: Tue, 26 Jun 2001 08:12:43 -0700
From: "Charles E. Perkins" <charliep@iprg.nokia.com>
Organization: Nokia Research Center
X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Leping.Huang@nokia.com
CC: Govind Krishnamurthi <Govind.Krishnamurthi@nokia.com>,
        Mobile Ad Hoc IETF working group <manet@itd.nrl.navy.mil>
Subject: Re: question about QoS for AODV draft
References: <6468108794D6D311AB850008C72B5EA40468A799@toeis01nok>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hello,

Just a quick response; hopefully more later

Leping.Huang@nokia.com wrote:


> 1. Does an intermdediate node need to make resouce reservation after
> forwarding of RREP? (it seems that link is established after forwarding of
> RREP)

It needs to make a short-lived reservation after forwarding RREQ,
and a longer term reservation after forwarding RREP.

> 2. does intermediate node hold the bandwidth/delay information about
> downstream node? if so, how can it get these info? if not, intermediate node
> can not reply the RREQ.

Nodes do not keep information about downstream nodes.  The intention
is that a node doesn't forward the RREQ if it cannot satisfy the
QoS requirement.

> 3. does this extension use priority queue algorithm in intermediate node?

That is a matter for implementation, not the protocol specfication.

> I feel confused with this draft.   Are there any plan to refresh this draft?

Yes, with a better way to specify QoS needs.  Please let me know
if this message helps dispel the confusion.

> I think QoS communication need end-to-end reservation or priority
> configuration, but AODV try to reply RREQ at intermediate node, is AODV not
> suitable for QOS communication?

I hope so, in view of the comments above.


Regards,
Charlie P.


From owner-manet@itd.nrl.navy.mil  Tue Jun 26 15:39:20 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA07121
	for <manet-archive@odin.ietf.org>; Tue, 26 Jun 2001 15:39:18 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA22520
	for manet-outgoing; Tue, 26 Jun 2001 12:56:32 -0400 (EDT)
Received: from sina.com ([202.106.187.164])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with SMTP id MAA22515
	for <manet@itd.nrl.navy.mil>; Tue, 26 Jun 2001 12:56:28 -0400 (EDT)
Received: (qmail 5484 invoked by uid 99); 26 Jun 2001 17:13:29 -0000
Message-ID: <20010626171329.5483.qmail@sina.com>
From: drliuwg <drliuwg@sina.com>
To: manet@itd.nrl.navy.mil
Subject: Ad hoc emulator based on ethernet
Date: Wed, 27 Jun 2001 01:13:29 +0800
X-Mailer: SinaMail 3.0Beta (FireToad)
X-Priority: 2
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Have you ever thought that there are many similar character between ethernet and MANET. In fact the first IEEE wavelan controlled by ethernet chips.

They all share the media and using CSMA.

The differents between they are connectivity and communication channel performances.

For the transmission range, the connectivity in MANET is incomplete. Ad Hoc netwroks have high frame error rate and communication decay. The frame error rate is the function of distant between transmitter and receiver.

We can insert a small program on top of network interface, and emulate the MANET characteristics on ethernet. We call it MPRN NE (Mobile Packet Radio Network Network Emulator).A center scenarios generator broadcast the position packet to all the emulators. Your real MANET routing protocol can run on top of emulators. TCPDUMP or other network performance analyse software can be used in test.

It's cheaper and more easier to be controlled than ns.  Millions of people use linux TCP/IP stack,You will not worry about the bugs in TCP/IP stacks.

The client part of NE is developed under linux, the scenarios generator and center controller is developed under windows for good graphic interface and easy implementation.

We took a MANET emulation on computing center. More than one hundred computers connected in one network segment worked in true time for 3 hours in mid night.

NE was developed by Beijing Institute of Technology, MPRN research group. It will be provided to all Ad Hoc researcher freely.

If you are interested in this,please email to my, I will give  you more detail information about our emulation.

Weiguo Liu

PHD Student

Computer Engineering Department
Beijing Institute of Technology
China

happydavidliu@yahoo.com

______________________________________

===================================================================
ÐÂÀËÃâ·Ñµç×ÓÓÊÏä (http://mail.sina.com.cn)
¶©ÔÄÊÖ»ú¶ÌÐÅÍ·ÌõÐÂÎÅ£¬ÌìÌì½±¶à¿îÊ±ÉÐÊÖ»ú£¡ (http://dailynews.sina.com.cn/c/272235.html)
¶©ÔÄÊÖ»ú¶ÌÐÅ¶¥¼¶ÐÂÎÅÃ¿ÌìµÃÐÂ¿îÊÖ»ú´ó½±£¡ (http://dailynews.sina.com.cn/c/266499.html)


From owner-manet@itd.nrl.navy.mil  Tue Jun 26 15:54:18 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA07120
	for <manet-archive@odin.ietf.org>; Tue, 26 Jun 2001 15:39:18 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA22485
	for manet-outgoing; Tue, 26 Jun 2001 12:55:50 -0400 (EDT)
Received: from sina.com ([202.106.187.165])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with SMTP id MAA22480
	for <manet@itd.nrl.navy.mil>; Tue, 26 Jun 2001 12:55:46 -0400 (EDT)
From: drliuwg@sina.com
Received: (qmail 2290 invoked by uid 99); 26 Jun 2001 17:03:57 -0000
Message-ID: <20010626170357.2289.qmail@sina.com>
To: manet@itd.nrl.navy.mil
Subject: about CMU extension
Date: Wed, 27 Jun 2001 01:03:57 +0800
X-Mailer: SinaMail 3.0Beta (FireToad)
X-Priority: 2
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Do CMU have the new CMU Wireless extension 1.1.2 for  ns2.1b7a? following the suggestion on CMU web site, I downloaded ns2.1b3 all in one using TCL8.0. It can not be installed smoothly on redhat7 on my computer.

According to the mail list, ns2.1b7 absorbed CMU Wireless extension. Does that means ad-hockey or other tools in CMU wireless extension can work perfectly with ns2.17a, and I need not compile the /ns-src?


Do all the old samples on CMU wireless extension 1.1.2 can work smoothly?

CMU wireless extension1.1.2 is too old created in 1997. Why they did not release the new verson?
Just because new version is included in ns2.1b7a? 

Where I can find the detail document just like "The CMU Monarch Project's Wireless and Mobility Extensions to ns"?
______________________________________

===================================================================
ÐÂÀËÃâ·Ñµç×ÓÓÊÏä (http://mail.sina.com.cn)
¶©ÔÄÊÖ»ú¶ÌÐÅÍ·ÌõÐÂÎÅ£¬ÌìÌì½±¶à¿îÊ±ÉÐÊÖ»ú£¡ (http://dailynews.sina.com.cn/c/272235.html)
¶©ÔÄÊÖ»ú¶ÌÐÅ¶¥¼¶ÐÂÎÅÃ¿ÌìµÃÐÂ¿îÊÖ»ú´ó½±£¡ (http://dailynews.sina.com.cn/c/266499.html)


From owner-manet@itd.nrl.navy.mil  Tue Jun 26 16:14:39 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA11611
	for <manet-archive@odin.ietf.org>; Tue, 26 Jun 2001 16:14:38 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id NAA24580
	for manet-outgoing; Tue, 26 Jun 2001 13:35:36 -0400 (EDT)
Received: from NEXUS.replicants.org.uk (pc-62-30-167-16-ca.blueyonder.co.uk [62.30.167.16])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id NAA24558
	for <manet@itd.nrl.navy.mil>; Tue, 26 Jun 2001 13:35:28 -0400 (EDT)
From: Internet-Drafts@ietf.org
Received: from mail pickup service by NEXUS.replicants.org.uk with Microsoft SMTPSVC;
	 Tue, 26 Jun 2001 18:39:17 +0100
X-From_: ietf-123-owner@loki.ietf.org Fri Jun 15 14:38:09 2001
Envelope-to: david@REPLICANTS.FREESERVE.CO.UK
Delivery-date: Fri, 15 Jun 2001 14:38:09 +0100
Received: from [132.151.1.177] (helo=loki.ietf.org)	by mail8.svr.pol.co.uk with esmtp (Exim 3.13 #0)	id 15Atnc-0006Qa-00; Fri, 15 Jun 2001 14:38:08 +0100
Received: (from adm@localhost)	by loki.ietf.org (8.9.1b+Sun/8.9.1) id IAA17943	for ietf-123-outbound.10@ietf.org; Fri, 15 Jun 2001 08:25:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA17247	for <all-ietf@loki.ietf.org>; Fri, 15 Jun 2001 06:47:47 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02830;	Fri, 15 Jun 2001 06:47:45 -0400 (EDT)
Message-Id: <200106151047.GAA02830@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: manet@itd.nrl.navy.mil
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-manet-fsr-01.txt
Date: Fri, 15 Jun 2001 06:47:44 -0400
X-OriginalArrivalTime: 26 Jun 2001 17:39:17.0234 (UTC) FILETIME=[EC620520:01C0FE66]
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Mobile Ad-hoc Networks Working Group of the IETF.

	Title		: Fisheye State Routing Protocol (FSR) for Ad Hoc 
                          Networks
	Author(s)	: M. Gerla et al.
	Filename	: draft-ietf-manet-fsr-01.txt
	Pages		: 17
	Date		: 14-Jun-01
	
The Fisheye State Routing (FSR) algorithm for ad hoc networks 
introduces the notion of multi-level 'scope' to reduce routing 
update overhead in large networks.  A node stores the Link State 
for every destination in the network.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-manet-fsr-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-manet-fsr-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-manet-fsr-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010614124610.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-manet-fsr-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-manet-fsr-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

C
--OtherAccess--
--NextPart--


From owner-manet@itd.nrl.navy.mil  Wed Jun 27 19:04:36 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA23263
	for <manet-archive@odin.ietf.org>; Wed, 27 Jun 2001 19:04:36 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id PAA02618
	for manet-outgoing; Wed, 27 Jun 2001 15:37:02 -0400 (EDT)
Received: from meshpdc.meshnetworks.com ([205.245.27.196])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id PAA02613
	for <manet@itd.nrl.navy.mil>; Wed, 27 Jun 2001 15:36:59 -0400 (EDT)
Received: by meshpdc.meshnetworks.com with Internet Mail Service (5.5.2653.19)
	id <NXCGAV7L>; Wed, 27 Jun 2001 15:36:50 -0400
Message-ID: <0DF9FBC42474A24CA50F7A27FB08E048445557@meshpdc.meshnetworks.com>
From: Phillip Neumiller <PNeumiller@meshnetworks.com>
To: manet@itd.nrl.navy.mil
Subject: Ad Hoc Network Scalability
Date: Wed, 27 Jun 2001 15:36:48 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hello,

In the paper found at http://www.pdos.lcs.mit.edu/papers/grid:mobicom01/
"Capacity of Ad Hoc Networks" from MIT labs for CS, the paper concludes
that the "key factor" determining whether large ad hoc networks are feasible

is the locality of traffic (which results in fewer hops on average between
communicators).

Have others found this to be the "key factor" in ad hoc network feasibility?

It would seem to me, that "WHAT" the key factor is would depend somewhat
on the network architecture being analyzed and specifically it would depend
heavily on the MAC implementation.  It seems to me that this paper may
have been more appropriately titled "Capacity of Ad Hoc 802.11 Wireless
Networks".  Is it generally agreed that the 802.11 MAC can adequately
represent what the "key scalability factors" are?  I think the 802.11 MAC
is expedient but not necessarily that useful for generalized analysis.  Is
there such a thing as a perfect MAC model?, i.e. a MAC that achieves X%
efficiency (my guess is its just a circuit switch big enough to connect 
everyone to everyone else n(n+1)/2!!!).  This would not be very practical
in an RF MANET so there must be some happy medium (pun intended)!

Thanks,

Phil Neumiller


From owner-manet@itd.nrl.navy.mil  Thu Jun 28 04:05:34 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA09155
	for <manet-archive@odin.ietf.org>; Thu, 28 Jun 2001 04:05:33 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id BAA11374
	for manet-outgoing; Thu, 28 Jun 2001 01:03:27 -0400 (EDT)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id BAA11369
	for <manet@itd.nrl.navy.mil>; Thu, 28 Jun 2001 01:03:24 -0400 (EDT)
Received: from ihemail1.firewall.lucent.com (localhost [127.0.0.1])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f5S53P212118
	for <manet@itd.nrl.navy.mil>; Thu, 28 Jun 2001 01:03:25 -0400 (EDT)
Received: from ii0015exch001u.wins.lucent.com (h135-254-248-252.lucent.com [135.254.248.252])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f5S53OZ12075
	for <manet@itd.nrl.navy.mil>; Thu, 28 Jun 2001 01:03:24 -0400 (EDT)
Received: by II0015EXCH001U with Internet Mail Service (5.5.2650.21)
	id <NJSDJY4G>; Thu, 28 Jun 2001 10:33:17 +0530
Message-ID: <B0BADCAFF5CDD211989700805F85E3F6054FD2B2@II0015EXCH001U>
From: "Rajan, Hridesh (Hridesh)" <hridesh@lucent.com>
To: "'Phillip Neumiller'" <PNeumiller@meshnetworks.com>
Cc: "'manet@itd.nrl.navy.mil'" <manet@itd.nrl.navy.mil>
Subject: RE: Ad Hoc Network Scalability
Date: Thu, 28 Jun 2001 10:33:11 +0530
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi Phil,

> In the paper found at 
> http://www.pdos.lcs.mit.edu/papers/grid:mobicom01/
> "Capacity of Ad Hoc Networks" from MIT labs for CS, the paper 
> concludes that the "key factor" determining whether large ad hoc 
> networks are feasible is the locality of traffic (which results 
> in fewer hops on average between communicators).
> 
> Have others found this to be the "key factor" in ad hoc 
> network feasibility?

I think in the paper they have just substantiated the widely
held belief by experimental evidences. It is pretty much 
obvious that if all the nodes of an Ad Hoc networks will communicate
with a path length equal to network diameter there will lot of 
contentions and as a result decrease in the throughput.

> 
> It would seem to me, that "WHAT" the key factor is would 
> depend somewhat on the network architecture being analyzed and 
> specifically it would depend heavily on the MAC implementation. 

I think the fact can't be denied that in the Ad Hoc networks other 
factors like network architecture become somewhat irrelevant
(Strictly my belief/Comments invited/Guidance towards any research 
work which substantiates my belief also invited). Isn't it the
traffic flow which is most important in this scenario??

Thank you,

Hridesh




From owner-manet@itd.nrl.navy.mil  Thu Jun 28 09:37:19 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA04100
	for <manet-archive@odin.ietf.org>; Thu, 28 Jun 2001 09:37:18 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id HAA14933
	for manet-outgoing; Thu, 28 Jun 2001 07:12:58 -0400 (EDT)
Received: from meshpdc.meshnetworks.com ([205.245.27.196])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id HAA14925
	for <manet@itd.nrl.navy.mil>; Thu, 28 Jun 2001 07:12:55 -0400 (EDT)
Received: by meshpdc.meshnetworks.com with Internet Mail Service (5.5.2653.19)
	id <NXCGAWJ7>; Thu, 28 Jun 2001 07:12:55 -0400
Message-ID: <0DF9FBC42474A24CA50F7A27FB08E048445559@meshpdc.meshnetworks.com>
From: Phillip Neumiller <PNeumiller@meshnetworks.com>
To: "'Rajan, Hridesh (Hridesh)'" <hridesh@lucent.com>,
        "'manet@itd.nrl.navy.mil'" <manet@itd.nrl.navy.mil>
Subject: RE: Ad Hoc Network Scalability
Date: Thu, 28 Jun 2001 07:12:53 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi Rajan,

> I think in the paper they have just substantiated the widely
> held belief by experimental evidences. It is pretty much 
> obvious that if all the nodes of an Ad Hoc networks will communicate
> with a path length equal to network diameter there will lot of 
> contentions and as a result decrease in the throughput.

OK, but they also showed some pretty bad performance of 802.11
in a "generic" ad hoc topology.  My feeling is that one could
probably do a better job in the MAC and this would flush out
some other limiting factors.

My other "feeling" on the subject is that MANET's will "probably"
not be deployed as pure MANET's but may rather be allowable extensions
of existing infrastructures.  As a practical matter, other limiting
factors like the MAC become much more important than the locality
of communication.  Also in situations of high mobility the loss
of packets (lack of seamlessness) will become a problem for various
types of QoS classes.  

I would agree that in a pure ad hoc network, with a CSMA/CA MAC
that locality of reference in traffic will be a big factor IFF
the routing is ignorant of network bottlenecks.  Then again I have
been a big advocate of building some kind of "generic" triggers 
between the MAC/Link protocols and the IP layer so that we can
be smarter and faster about routing without relying on an ARQ in
the transport (i.e. Nagle, etc).

> I think the fact can't be denied that in the Ad Hoc networks other 
> factors like network architecture become somewhat irrelevant
> (Strictly my belief/Comments invited/Guidance towards any research 
> work which substantiates my belief also invited). Isn't it the
> traffic flow which is most important in this scenario??

Traffic flow is EXTREMELY sensitive to the type of routing that is
being done and the assumed mobility model.

I guess I will respectfully disagree.  It seems you have too many
built in assumptions to say that "network architecture is irrelevant".
Are you assuming some type of routing with this statement or is that
also irrelevant in your opinion?

Best regards,

Phil Neumiller


From owner-manet@itd.nrl.navy.mil  Thu Jun 28 16:24:32 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA21867
	for <manet-archive@odin.ietf.org>; Thu, 28 Jun 2001 16:24:31 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id NAA28214
	for manet-outgoing; Thu, 28 Jun 2001 13:12:24 -0400 (EDT)
Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id NAA28203
	for <manet@itd.nrl.navy.mil>; Thu, 28 Jun 2001 13:12:18 -0400 (EDT)
From: philippe.jacquet@inria.fr
Received: from prisse (prisse.inria.fr [128.93.9.64])
	by nez-perce.inria.fr (8.11.1/8.10.0) with SMTP id f5SHC5f04905;
	Thu, 28 Jun 2001 19:12:05 +0200 (MET DST)
Message-Id: <3.0.1.32.20010628192111.016a06e0@menetou.inria.fr>
X-Sender: jacquet@menetou.inria.fr
X-Mailer: Windows Eudora Pro Version 3.0.1 (32) [F]
Date: Thu, 28 Jun 2001 19:21:11 +0200
To: Phillip Neumiller <PNeumiller@meshnetworks.com>, manet@itd.nrl.navy.mil
Subject: Re: Ad Hoc Network Scalability
In-Reply-To: <0DF9FBC42474A24CA50F7A27FB08E048445557@meshpdc.meshnetwork
 s.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-MIME-Autoconverted: from quoted-printable to 8bit by itd.nrl.navy.mil id NAA28205
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by itd.nrl.navy.mil id NAA28214
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA21867

It is clear that multihop impacts the performance. 

In a recent paper (in information theory, I must look in my records), it is
shown that the percentage of throughput in an ad hoc network of N users is
at best of order 1/sqrt(N) in a 2D network with power law signal
attenuation. The impact of routing makes that each packet has to be routed
in an average of sqrt(N) hop. 

If the traffic would have been local (i.e. directed to neighbor), then the
average percentage traffic per node would be O(1) due to spatial reuse.
This is not too bad, since if the network would have been connected on a
single Ethernet hub, then the percentage would have been O(1/N). Notice
that even with routing overhead, the ad hoc network does better than the
Ethernet hub. 

This result is attainable because when the traffic density increases, the
distance between hops decreases and spatial reuse is possible.
Unfortunately this is not completely possible with IEEE 802.11 because the
CSMA carrier sense level is fixed and prevent close spatial reuse. To
obtain theoretical bounds  one should need at least a tunable carrier sense
level. 

Philippe 

A 15:36 27/06/01 -0400, Phillip Neumiller a écrit :
>Hello,
>
>In the paper found at http://www.pdos.lcs.mit.edu/papers/grid:mobicom01/
>"Capacity of Ad Hoc Networks" from MIT labs for CS, the paper concludes
>that the "key factor" determining whether large ad hoc networks are feasible
>
>is the locality of traffic (which results in fewer hops on average between
>communicators).
>
>Have others found this to be the "key factor" in ad hoc network feasibility?
>
>It would seem to me, that "WHAT" the key factor is would depend somewhat
>on the network architecture being analyzed and specifically it would depend
>heavily on the MAC implementation.  It seems to me that this paper may
>have been more appropriately titled "Capacity of Ad Hoc 802.11 Wireless
>Networks".  Is it generally agreed that the 802.11 MAC can adequately
>represent what the "key scalability factors" are?  I think the 802.11 MAC
>is expedient but not necessarily that useful for generalized analysis.  Is
>there such a thing as a perfect MAC model?, i.e. a MAC that achieves X%
>efficiency (my guess is its just a circuit switch big enough to connect 
>everyone to everyone else n(n+1)/2!!!).  This would not be very practical
>in an RF MANET so there must be some happy medium (pun intended)!
>
>Thanks,
>
>Phil Neumiller
>


From owner-manet@itd.nrl.navy.mil  Thu Jun 28 16:36:08 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA29872
	for <manet-archive@odin.ietf.org>; Thu, 28 Jun 2001 16:36:07 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id OAA00683
	for manet-outgoing; Thu, 28 Jun 2001 14:15:51 -0400 (EDT)
Received: from exsassmtpb03.services.microsoft.com ([64.14.142.220])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id OAA00678
	for <manet@itd.nrl.navy.mil>; Thu, 28 Jun 2001 14:15:49 -0400 (EDT)
Received: from exsassmtpa03.services.microsoft.com ([10.69.0.46]) by exsassmtpb03.services.microsoft.com with Microsoft SMTPSVC(5.0.2195.2532);
	 Thu, 28 Jun 2001 11:15:50 -0700
Received: from mail pickup service by exsassmtpa03.services.microsoft.com with Microsoft SMTPSVC;
	 Thu, 28 Jun 2001 11:15:50 -0700
Received: from exsasvwa01.services.microsoft.com ([10.69.0.84]) by exsassmtpa01.services.microsoft.com with Microsoft SMTPSVC(5.0.2195.2532);	 Thu, 28 Jun 2001 08:38:13 -0700
Received: from 132.250.83.3 by exsasvwa01.services.microsoft.com (InterScan E-Mail VirusWall NT); Thu, 28 Jun 2001 08:38:09 -0700 (Pacific Daylight Time)
Received: (from majordom@localhost)	by itd.nrl.navy.mil (8.8.8/8.8.8) id HAA14933	for manet-outgoing; Thu, 28 Jun 2001 07:12:58 -0400 (EDT)
Received: from meshpdc.meshnetworks.com ([205.245.27.196])	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id HAA14925	for <manet@itd.nrl.navy.mil>; Thu, 28 Jun 2001 07:12:55 -0400 (EDT)
Received: by meshpdc.meshnetworks.com with Internet Mail Service (5.5.2653.19)	id <NXCGAWJ7>; Thu, 28 Jun 2001 07:12:55 -0400
Message-ID: <0DF9FBC42474A24CA50F7A27FB08E048445559@meshpdc.meshnetworks.com>
From: Phillip Neumiller <PNeumiller@meshnetworks.com>
To: "'Rajan, Hridesh (Hridesh)'" <hridesh@lucent.com>,
        "'manet@itd.nrl.navy.mil'" <manet@itd.nrl.navy.mil>
Subject: RE: Ad Hoc Network Scalability
Date: Thu, 28 Jun 2001 07:12:53 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;	charset="iso-8859-1"
X-OriginalArrivalTime: 28 Jun 2001 15:38:13.0859 (UTC) FILETIME=[57E67330:01C0FFE8]
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi Rajan,

> I think in the paper they have just substantiated the widely
> held belief by experimental evidences. It is pretty much 
> obvious that if all the nodes of an Ad Hoc networks will communicate
> with a path length equal to network diameter there will lot of 
> contentions and as a result decrease in the throughput.

OK, but they also showed some pretty bad performance of 802.11
in a "generic" ad hoc topology.  My feeling is that one could
probably do a better job in the MAC and this would flush out
some other limiting factors.

My other "feeling" on the subject is that MANET's will "probably"
not be deployed as pure MANET's but may rather be allowable extensions
of existing infrastructures.  As a practical matter, other limiting
factors like the MAC become much more important than the locality
of communication.  Also in situations of high mobility the loss
of packets (lack of seamlessness) will become a problem for various
types of QoS classes.  

I would agree that in a pure ad hoc network, with a CSMA/CA MAC
that locality of reference in traffic will be a big factor IFF
the routing is ignorant of network bottlenecks.  Then again I have
been a big advocate of building some kind of "generic" triggers 
between the MAC/Link protocols and the IP layer so that we can
be smarter and faster about routing without relying on an ARQ in
the transport (i.e. Nagle, etc).

> I think the fact can't be denied that in the Ad Hoc networks other 
> factors like network architecture become somewhat irrelevant
> (Strictly my belief/Comments invited/Guidance towards any research 
> work which substantiates my belief also invited). Isn't it the
> traffic flow which is most important in this scenario??

Traffic flow is EXTREMELY sensitive to the type of routing that is
being done and the assumed mobility model.

I guess I will respectfully disagree.  It seems you have too many
built in assumptions to say that "network architecture is irrelevant".
Are you assuming some type of routing with this statement or is that
also irrelevant in your opinion?

Best regards,

Phil Neumiller


From owner-manet@itd.nrl.navy.mil  Fri Jun 29 14:23:32 2001
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA22046
	for <manet-archive@odin.ietf.org>; Fri, 29 Jun 2001 14:23:32 -0400 (EDT)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id KAA23149
	for manet-outgoing; Fri, 29 Jun 2001 10:54:12 -0400 (EDT)
Received: from SEXTANT.itd.nrl.navy.mil (sextant.itd.nrl.navy.mil [132.250.92.22])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id KAA23127;
	Fri, 29 Jun 2001 10:53:48 -0400 (EDT)
Message-Id: <5.0.1.4.2.20010629105514.019711d8@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Fri, 29 Jun 2001 10:57:52 -0400
To: philippe.jacquet@inria.fr
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: Ad Hoc Network Scalability
Cc: manet@itd.nrl.navy.mil
In-Reply-To: <3.0.1.32.20010628192111.016a06e0@menetou.inria.fr>
References: <0DF9FBC42474A24CA50F7A27FB08E048445557@meshpdc.meshnetwork s.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
X-MIME-Autoconverted: from quoted-printable to 8bit by itd.nrl.navy.mil id KAA23128
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by itd.nrl.navy.mil id KAA23149
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id OAA22046

At 07:21 PM 6/28/2001 +0200, you wrote:
>It is clear that multihop impacts the performance.
>
>In a recent paper (in information theory, I must look in my records), it is
>shown that the percentage of throughput in an ad hoc network of N users is
>at best of order 1/sqrt(N) in a 2D network with power law signal
>attenuation. The impact of routing makes that each packet has to be routed
>in an average of sqrt(N) hop.

Gupta and Kumar, IEEE transactions on Information Theory, vol IT-46, no.2, 
pp 388-404, March 2000.


>If the traffic would have been local (i.e. directed to neighbor), then the
>average percentage traffic per node would be O(1) due to spatial reuse.
>This is not too bad, since if the network would have been connected on a
>single Ethernet hub, then the percentage would have been O(1/N). Notice
>that even with routing overhead, the ad hoc network does better than the
>Ethernet hub.
>
>This result is attainable because when the traffic density increases, the
>distance between hops decreases and spatial reuse is possible.
>Unfortunately this is not completely possible with IEEE 802.11 because the
>CSMA carrier sense level is fixed and prevent close spatial reuse. To
>obtain theoretical bounds  one should need at least a tunable carrier sense
>level.
>
>Philippe
>
>A 15:36 27/06/01 -0400, Phillip Neumiller a écrit :
> >Hello,
> >
> >In the paper found at http://www.pdos.lcs.mit.edu/papers/grid:mobicom01/
> >"Capacity of Ad Hoc Networks" from MIT labs for CS, the paper concludes
> >that the "key factor" determining whether large ad hoc networks are feasible
> >
> >is the locality of traffic (which results in fewer hops on average between
> >communicators).
> >
> >Have others found this to be the "key factor" in ad hoc network feasibility?
> >
> >It would seem to me, that "WHAT" the key factor is would depend somewhat
> >on the network architecture being analyzed and specifically it would depend
> >heavily on the MAC implementation.  It seems to me that this paper may
> >have been more appropriately titled "Capacity of Ad Hoc 802.11 Wireless
> >Networks".  Is it generally agreed that the 802.11 MAC can adequately
> >represent what the "key scalability factors" are?  I think the 802.11 MAC
> >is expedient but not necessarily that useful for generalized analysis.  Is
> >there such a thing as a perfect MAC model?, i.e. a MAC that achieves X%
> >efficiency (my guess is its just a circuit switch big enough to connect
> >everyone to everyone else n(n+1)/2!!!).  This would not be very practical
> >in an RF MANET so there must be some happy medium (pun intended)!
> >
> >Thanks,
> >
> >Phil Neumiller
> >




