From owner-manet@itd.nrl.navy.mil  Thu Feb  1 13:36:50 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 NAA06362
	for <manet-archive@odin.ietf.org>; Thu, 1 Feb 2001 13:36:48 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA15633
	for manet-outgoing; Thu, 1 Feb 2001 11:19:47 -0500 (EST)
Received: from corewars.org (ns.ghostserver.net [63.67.58.4])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id LAA15627
	for <manet@itd.nrl.navy.mil>; Thu, 1 Feb 2001 11:19:45 -0500 (EST)
Date: Thu,  1 Feb 2001 08:21:40 -0600
Message-Id: <200102010821.AA2796421188@corewars.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: "Abhishek Kumar" <abhishek@corewars.org>
Reply-To: <abhishek@corewars.org>
To: <dpamio@mail.com>
CC: <manet@itd.nrl.navy.mil>
Subject: Re: Throughput measurement in Ad-Hoc Networks
X-Mailer: <IMail v6.00>
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by itd.nrl.navy.mil id LAA15633
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA06362

HI

>We are trying to measure the throughput of an ad-hoc Network that we
> have
>simulated using ns (2.1b7a). Does anyone know how to do this? We tried
> to
>use per-flow monitors but it seems it doesn't work in ad-hoc networks
>because it needs a (wired) link between the nodes.

If your flows are TCP, you can get the total number of packets acknowledged on a flow at any point in time. This can be done by acessing the configuration parameter ack_ of your TCP objects.
The NS documentation (chapter 10.8) defines it as :

ack_ 
Highest acknowledgment seen from receiver.

This can be used to get both the cumulative and instantanious "throughput" for individual TCP flows. Note that you can get only the number of acknowledged packets and thus the lost packets are not counted. Thus what you are really measuring is not raw throughput of the network, but the "goodput" of TCP flows.

Hope it is useful.

Cheers
abhishek

ççççççççççççççççççççççççççççççççççççç

Abhishek Kumar
Chambre C-503
I.N.S.A.
20, Avenue Albert Einstein
69621, Villeurbanne CEDEX
France

ph: +33 4 7243 7568

email: abhishek@corewars.org

web: www.if.insa-lyon.fr/eleves/akumar/


From owner-manet@itd.nrl.navy.mil  Sat Feb  3 17:53:27 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 RAA13683
	for <manet-archive@odin.ietf.org>; Sat, 3 Feb 2001 17:53:27 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id QAA06902
	for manet-outgoing; Sat, 3 Feb 2001 16:09:30 -0500 (EST)
Received: from mail.hosokawa.co.jp ([202.229.20.29])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with SMTP id QAA06897
	for <manet@itd.nrl.navy.mil>; Sat, 3 Feb 2001 16:09:28 -0500 (EST)
From: bigjoe@japan.com
Received: (qmail 12806 invoked from network); 3 Feb 2001 17:58:21 -0000
Received: from 1cust46.tnt3.irving2.tx.da.uu.net (HELO 1Cust46.tnt3.irving2.tx.da.uu.net??63.24.178.46?) (63.24.178.46)
  by sorc3r3r.org with SMTP; 3 Feb 2001 17:58:21 -0000
Received: from mailhost.telematics.com by 1Cust46.tnt3.irving2.tx.da.uu.net with ESMTP; Sat, 03 Feb 2001 11:55:38 -0600
Message-ID: <000058ab562d$00005ab8$00002581@mailhost.telematics.com>
To: <Undisclosed.Recipients@itd.nrl.navy.mil>
Subject: Brand New E-Mail pager for FR-EE!                         9601
Date: Sat, 03 Feb 2001 11:55:34 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Reply-To: bigjoe@japan.com
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 7bit

   No big prepayment of airtime
   No credit check

   PAGING AMERICA is going to give you absolutely Free the Brand new Motorola
   Accessmate E-Mail display pager. This is the top of the line PCS technology
   pager made today. This side viewable display pager has a retail value of
   $189.00and comes with its own e-mail address so you can receive your e-mails
   as well as alpha-numeric and numeric messages instantly where ever you are.
   Your new e-mail pager has features like 50,000 character memory, message time
   stamping, automatic garbled message correction, beeps or vibrates,
   incandescent backlight, saved message folder, a unique never out of range
   feature that allows your pager to retrieve messages sent earlier when your
   pager was out of range or turned completely off. You can also receive
   weather, news and sports .The Motorola e-mail pager is very small and uses
   only a single double A battery. All we ask before we ship you your Free pager
   is for you to allow us to provide the airtime for you. There is no long term
   contract or credit check. Airtime is month to month and can be cancelled at
   any time. This pager will comes pre-programmed with its own e-mail address as
   well as a local telephone number to receive numeric pages. This pager comes
   with a complete 30 day money back guarantee, if after receiving this pager
   you're not completely happy, send it back and receive a full refund.

   For immediate delivery call Paging America at toll free at 877-699-8546











   Brand New E-Mail pager for FREE!

   No long term contract
   No activation fee




From owner-manet@itd.nrl.navy.mil  Mon Feb  5 18:26:26 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 SAA20468
	for <manet-archive@odin.ietf.org>; Mon, 5 Feb 2001 18:26:26 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id QAA12883
	for manet-outgoing; Mon, 5 Feb 2001 16:33:20 -0500 (EST)
Received: from craig.purcell ([200.255.70.210])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with SMTP id QAA12834;
	Mon, 5 Feb 2001 16:33:07 -0500 (EST)
From: Edetect@connect4free.net
To: @itd.nrl.navy.mil
Date: Mon, 05 Feb 2001 14:32:44 -0700
Subject: Find Out the TRUTH About AnyOne !
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7BIT
Message-Id: <nqbaggf.eyoklitewkf@craig.purcell>
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 7BIT

<html>

<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<title>Software - Investigative Utility Tools</title>
</head>

<body>

<div align="center">
  <center>
  <table border="0" cellspacing="1" width="67%">
    <tr>
      <td width="100%">
        <p align="center"><span style='text-decoration:
  none;text-underline:none'>
  <a href="http://3506561040/i312315345/index.htm">
  <img border=0 width=468 height=60 id="_x0000_i1025" 
src="http://3506561040/i312315345/banner.gif">
  </a></span></td>
    </tr>
  </table>
  </center>
</div>

</body>

</html>



From owner-manet@itd.nrl.navy.mil  Mon Feb  5 18:37:24 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 SAA20586
	for <manet-archive@odin.ietf.org>; Mon, 5 Feb 2001 18:37:24 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id QAA12678
	for manet-outgoing; Mon, 5 Feb 2001 16:28:06 -0500 (EST)
Received: from topaz.3com.com (topaz.3com.com [192.156.136.158])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id QAA12647
	for <manet@itd.nrl.navy.mil>; Mon, 5 Feb 2001 16:27:50 -0500 (EST)
From: Phil_Neumiller@3com.com
Received: from opal.3com.com (opal.3com.com [139.87.50.117])
	by topaz.3com.com (Switch-2.0.1/Switch-2.0.1) with ESMTP id f15LQc127034;
	Mon, 5 Feb 2001 13:26:38 -0800 (PST)
Received: from hqoutbound.ops.3com.com (hqoutbound.ops.3com.com [139.87.48.104])
	by opal.3com.com (Switch-2.0.1/Switch-2.0.1) with SMTP id f15LRoA27509;
	Mon, 5 Feb 2001 13:27:50 -0800 (PST)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 882569EA.00760E10 ; Mon, 5 Feb 2001 13:29:28 -0800
X-Lotus-FromDomain: 3COM
To: Charlie Perkins <charliep@iprg.nokia.com>
cc: seamoby@diameter.org, manet@itd.nrl.navy.mil
Message-ID: <882569EA.00760153.00@hqoutbound.ops.3com.com>
Date: Mon, 5 Feb 2001 15:23:59 -0600
Subject: Re: [seamoby] Upcoming REAL IP for Bluetooth BOF
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk




Hi Charlie,

I cross-posted this to MANET, please forgive multiple copies.

BTW, Thanks for the AODV recommendation...

As a casual observer of MANET activity I look at the work and I see no RFC
for basic ad hoc networking.  Case closed.  I do see the following work in
progress (which as been in progress for some time):

o (AODV) Routing
o Temporally-Ordered Routing Algorithm (TORA)
o The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks
o Optimized Link State Routing Protocol
o Differential Destination Multicast (DDM) Specification
o Multicast Ad hoc On-Demand Distance Vector (MAODV)
o Topology Broadcast based on Reverse-Path Forwarding (TBRPF)
o Landmark Routing Protocol (LANMAR) for Large Scale Ad Hoc Networks
o A Simple Protocol for Multicast and Broadcast in Mobile Ad Hoc Networks
o Fisheye State Routing Protocol (FSR) for Ad Hoc Networks

While I am quite convinced that ALL this work is valuable and useful it
does not solve my basic problems (at least not in a standard way).
WHAT IS THE IETF's consensus and current recommendation for basic
ad hoc networking???  Would this work not prove to be better served
in the IRTF?  It seems the MANET WG should be working more towards
a consensus and a standard RFC protocol for ad hoc networking right?
If I am out of order here please explain.

Thanks,

-Phil




From owner-manet@itd.nrl.navy.mil  Mon Feb  5 23:22:28 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 XAA25027
	for <manet-archive@odin.ietf.org>; Mon, 5 Feb 2001 23:22:27 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id VAA19003
	for manet-outgoing; Mon, 5 Feb 2001 21:34:04 -0500 (EST)
Received: from mail.ndsc.com.cn ([202.102.238.206])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id VAA18998
	for <manet@itd.nrl.navy.mil>; Mon, 5 Feb 2001 21:33:57 -0500 (EST)
Received: from CSQ ([192.168.200.248]) by mail.ndsc.com.cn
          (Netscape Messaging Server 3.5)  with SMTP id AAA1BC3
          for <manet@itd.nrl.navy.mil>; Tue, 6 Feb 2001 10:31:01 +0800
Message-ID: <005b01c00068$eec858c0$f8c8a8c0@CSQ>
From: "Chen Shuqiao" <csq@mail.ndsc.com.cn>
To: <manet@itd.nrl.navy.mil>
Subject: Source code
Date: Mon, 7 Aug 2000 20:13:43 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by itd.nrl.navy.mil id VAA18999
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi all,

Are there vendors have source code supporting MobileIP?

Best regards,
Shuqiao Chen

Any questions, please contact me.
MPhone:13607656855
OPhone:(086)0371-3941430-32986
HPhone:(086)0371-3941430-32028
Email:99csq@ndsc.com.cn


From owner-manet@itd.nrl.navy.mil  Tue Feb  6 02:55: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 CAA09896
	for <manet-archive@odin.ietf.org>; Tue, 6 Feb 2001 02:55:48 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id BAA22119
	for manet-outgoing; Tue, 6 Feb 2001 01:14:37 -0500 (EST)
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 BAA22114
	for <manet@itd.nrl.navy.mil>; Tue, 6 Feb 2001 01:14:36 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161])
	by boreas.isi.edu (8.9.3/8.9.3) with SMTP id VAA06180
	for <manet@itd.nrl.navy.mil>; Mon, 5 Feb 2001 21:15:13 -0800 (PST)
Date: Mon, 5 Feb 2001 21:15:13 -0800 (PST)
From: Ya Xu <yaxu@isi.edu>
To: manet@itd.nrl.navy.mil
Subject: mobility model in ad hoc network
In-Reply-To: <005b01c00068$eec858c0$f8c8a8c0@CSQ>
Message-ID: <Pine.GSO.3.96.1010205210555.4750A-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,

I realized that the random mobility model(way point) has been widely used
in ad hoc routing research. I'd like to know if there are any other 
mobility models studied in the ad hoc network research. More generally,
does mobility model have big impact on the ad hoc routing research ?

thanks

-Ya



From owner-manet@itd.nrl.navy.mil  Tue Feb  6 05:44:28 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 FAA10777
	for <manet-archive@odin.ietf.org>; Tue, 6 Feb 2001 05:44:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id DAA23879
	for manet-outgoing; Tue, 6 Feb 2001 03:40:14 -0500 (EST)
Received: from smtp.Stanford.EDU (smtp.Stanford.EDU [171.64.14.23])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id DAA23872
	for <manet@itd.nrl.navy.mil>; Tue, 6 Feb 2001 03:40:12 -0500 (EST)
Received: from raw.stanford.edu (raw.Stanford.EDU [128.12.174.44])
	by smtp.Stanford.EDU (8.11.1/8.11.1) with ESMTP id f168eBW17027;
	Tue, 6 Feb 2001 00:40:11 -0800 (PST)
Message-Id: <4.3.1.2.20010206003250.02992ca0@rayw.pobox.stanford.edu>
X-Sender: rayw@rayw.pobox.stanford.edu
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 06 Feb 2001 00:40:12 -0800
To: Ya Xu <yaxu@isi.edu>, manet@itd.nrl.navy.mil
From: Raymond Wang <rayw@stanford.edu>
Subject: Re: mobility model in ad hoc network
In-Reply-To: <Pine.GSO.3.96.1010205210555.4750A-100000@boreas.isi.edu>
References: <005b01c00068$eec858c0$f8c8a8c0@CSQ>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi Ya,

M. Sanchez, P. Manzoni, and Z.J. Haas, "Determination of Critical
Transmission Range in Ad-Hoc Networks," Multiaccess, Mobility and
Teletraffic for Wireless Communications (MMT'99), Venice, Italy, October
6-8, 1999

has a section on mobility models and useful references.  Mobility models 
are definitely key to a proper performance evaluation.  I am definitely not 
an expert on this issue so I'd be interested in reading further postings to 
this group.

Thanks,
Ray

At 09:15 PM 2/5/2001 -0800, Ya Xu wrote:

>Hi,
>
>I realized that the random mobility model(way point) has been widely used
>in ad hoc routing research. I'd like to know if there are any other
>mobility models studied in the ad hoc network research. More generally,
>does mobility model have big impact on the ad hoc routing research ?
>
>thanks
>
>-Ya



From owner-manet@itd.nrl.navy.mil  Tue Feb  6 17:52: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 RAA04235
	for <manet-archive@odin.ietf.org>; Tue, 6 Feb 2001 17:52:34 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id QAA14893
	for manet-outgoing; Tue, 6 Feb 2001 16:06:47 -0500 (EST)
Received: from ux6.sp.cs.cmu.edu (UX6.SP.CS.CMU.EDU [128.2.181.250])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with SMTP id QAA14888
	for <manet@itd.nrl.navy.mil>; Tue, 6 Feb 2001 16:06:45 -0500 (EST)
Date: Tue, 6 Feb 2001 16:06:20 -0500 (EST)
From: Yih-Chun Hu <yihchun@cs.cmu.edu>
X-Sender: yihchun@ux6.sp.cs.cmu.edu
To: Raymond Wang <rayw@stanford.edu>
cc: Ya Xu <yaxu@isi.edu>, manet@itd.nrl.navy.mil
Subject: Re: mobility model in ad hoc network
In-Reply-To: <4.3.1.2.20010206003250.02992ca0@rayw.pobox.stanford.edu>
Message-ID: <Pine.SOL.3.95L.1010206154605.7577E-100000@ux6.sp.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk


Ya and Ray,

We had a paper at MobiCom 2000 that discusses five mobility models and
performance results for DSR on scenarios generated using these models.
The paper is available on our web page at
	http://www.monarch.cs.cmu.edu/papers.html

The citation is:
Yih-Chun Hu and David B. Johnson. Caching Strategies in On-Demand Routing
Protocols for Wireless Ad Hoc Networks. Proceedings of the Sixth Annual
ACM/IEEE International Conference on Mobile Computing and Networking, ACM,
Boston, MA, August 2000. 

Thanks,
Yih-Chun

On Tue, 6 Feb 2001, Raymond Wang wrote:

>Hi Ya,
>
>M. Sanchez, P. Manzoni, and Z.J. Haas, "Determination of Critical
>Transmission Range in Ad-Hoc Networks," Multiaccess, Mobility and
>Teletraffic for Wireless Communications (MMT'99), Venice, Italy, October
>6-8, 1999
>
>has a section on mobility models and useful references.  Mobility models 
>are definitely key to a proper performance evaluation.  I am definitely not 
>an expert on this issue so I'd be interested in reading further postings to 
>this group.
>
>Thanks,
>Ray
>
>At 09:15 PM 2/5/2001 -0800, Ya Xu wrote:
>
>>Hi,
>>
>>I realized that the random mobility model(way point) has been widely used
>>in ad hoc routing research. I'd like to know if there are any other
>>mobility models studied in the ad hoc network research. More generally,
>>does mobility model have big impact on the ad hoc routing research ?
>>
>>thanks
>>
>>-Ya



From owner-manet@itd.nrl.navy.mil  Wed Feb  7 00:39:29 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 AAA11968
	for <manet-archive@odin.ietf.org>; Wed, 7 Feb 2001 00:39:29 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id WAA22857
	for manet-outgoing; Tue, 6 Feb 2001 22:47:34 -0500 (EST)
Received: from cheetah.cs.ucla.edu (Cheetah.CS.UCLA.EDU [131.179.128.24])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id WAA22846
	for <manet@itd.nrl.navy.mil>; Tue, 6 Feb 2001 22:47:24 -0500 (EST)
Received: from localhost (hxy@localhost)
	by cheetah.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id TAA28478;
	Tue, 6 Feb 2001 19:46:49 -0800 (PST)
Date: Tue, 6 Feb 2001 19:46:49 -0800 (PST)
From: Hong Xiaoyan <hxy@cs.ucla.edu>
To: Ya Xu <yaxu@isi.edu>
cc: Dr Mario Gerla <gerla@cs.ucla.edu>, Yih-Chun Hu <yihchun@cs.cmu.edu>,
        Raymond Wang <rayw@stanford.edu>, manet@itd.nrl.navy.mil
Subject: Re: mobility model in ad hoc network
In-Reply-To: <Pine.SOL.3.95L.1010206154605.7577E-100000@ux6.sp.cs.cmu.edu>
Message-ID: <Pine.SOL.4.10.10102061932460.28482-100000@cheetah.cs.ucla.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi, Ya and all,

We also have two papers covering mobility models. Please find them in the
following NRL under "Recent Publications":
    http://www.cs.ucla.edu/NRL/wireless/

One is: "A Group Mobility Model for Ad Hoc Wireless Networks"
    X. Hong, M. Gerla, G. Pei, and C.-C. Chiang Proceedings of ACM/IEEE
    MSWiM'99, Seattle, WA, Aug. 1999.

The other is not online yet, but can be found in: 
    Proceedings of IEEE MDM 2001, Hong Kong, Jan. 2001.
    X. Hong, T. K. Kwon, M. Gerla, D. L. Gu and G. Pei, "A Mobility
    Framework for Ad Hoc Wireless Networks",

Thanks,

Xiaoyan

On Tue, 6 Feb 2001, Yih-Chun Hu wrote:

> 
> Ya and Ray,
> 
> We had a paper at MobiCom 2000 that discusses five mobility models and
> performance results for DSR on scenarios generated using these models.
> The paper is available on our web page at
> 	http://www.monarch.cs.cmu.edu/papers.html
> 
> The citation is:
> Yih-Chun Hu and David B. Johnson. Caching Strategies in On-Demand Routing
> Protocols for Wireless Ad Hoc Networks. Proceedings of the Sixth Annual
> ACM/IEEE International Conference on Mobile Computing and Networking, ACM,
> Boston, MA, August 2000. 
> 
> Thanks,
> Yih-Chun
> 
> On Tue, 6 Feb 2001, Raymond Wang wrote:
> 
> >Hi Ya,
> >
> >M. Sanchez, P. Manzoni, and Z.J. Haas, "Determination of Critical
> >Transmission Range in Ad-Hoc Networks," Multiaccess, Mobility and
> >Teletraffic for Wireless Communications (MMT'99), Venice, Italy, October
> >6-8, 1999
> >
> >has a section on mobility models and useful references.  Mobility models 
> >are definitely key to a proper performance evaluation.  I am definitely not 
> >an expert on this issue so I'd be interested in reading further postings to 
> >this group.
> >
> >Thanks,
> >Ray
> >
> >At 09:15 PM 2/5/2001 -0800, Ya Xu wrote:
> >
> >>Hi,
> >>
> >>I realized that the random mobility model(way point) has been widely used
> >>in ad hoc routing research. I'd like to know if there are any other
> >>mobility models studied in the ad hoc network research. More generally,
> >>does mobility model have big impact on the ad hoc routing research ?
> >>
> >>thanks
> >>
> >>-Ya
> 
> 



From owner-manet@itd.nrl.navy.mil  Wed Feb  7 19:18:38 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 TAA12742
	for <manet-archive@odin.ietf.org>; Wed, 7 Feb 2001 19:18:38 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id RAA18818
	for manet-outgoing; Wed, 7 Feb 2001 17:10:21 -0500 (EST)
Received: from letters.cs.ucsb.edu (letters.cs.ucsb.edu [128.111.41.13])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id RAA18813
	for <manet@itd.nrl.navy.mil>; Wed, 7 Feb 2001 17:10:19 -0500 (EST)
Received: from saguaro (saguaro [128.111.40.82])
	by letters.cs.ucsb.edu (8.9.3+Sun/8.9.3) with SMTP id OAA16174;
	Wed, 7 Feb 2001 14:10:15 -0800 (PST)
Message-Id: <200102072210.OAA16174@letters.cs.ucsb.edu>
Date: Wed, 7 Feb 2001 14:10:15 -0800 (PST)
From: "Elizabeth M. Royer" <eroyer@cs.ucsb.edu>
Reply-To: "Elizabeth M. Royer" <eroyer@cs.ucsb.edu>
Subject: Re: mobility model in ad hoc network
To: yaxu@isi.edu
Cc: manet@itd.nrl.navy.mil
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: IROtWulAOU5mvvj5Lg+vXA==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi Ya,

In an upcoming ICC'01 paper, we have defined a new mobility
model called the Random Direction model.  The paper title
is "An Analysis of the Optimum Node Density for Ad hoc 
Mobile Networks".  It should be available off of my website
by the end of the month  (http://www.cs.ucsb.edu/~eroyer).


Elizabeth



~> Hi,
~> 
~> I realized that the random mobility model(way point) has been widely used
~> in ad hoc routing research. I'd like to know if there are any other 
~> mobility models studied in the ad hoc network research. More generally,
~> does mobility model have big impact on the ad hoc routing research ?
~> 
~> thanks
~> 
~> -Ya
~> 



From owner-manet@itd.nrl.navy.mil  Wed Feb  7 22: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 WAA16993
	for <manet-archive@odin.ietf.org>; Wed, 7 Feb 2001 22:41:11 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id VAA23035
	for manet-outgoing; Wed, 7 Feb 2001 21:08:30 -0500 (EST)
Received: from ee.cornell.edu (anise.ee.cornell.edu [128.84.239.14])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id VAA23027
	for <manet@itd.nrl.navy.mil>; Wed, 7 Feb 2001 21:08:28 -0500 (EST)
Received: from verdi.ee.cornell.edu (verdi.ee.cornell.edu [128.84.240.71])
	by ee.cornell.edu (8.9.3/8.9.1) with ESMTP id VAA10885;
	Wed, 7 Feb 2001 21:08:19 -0500 (EST)
Date: Wed, 7 Feb 2001 21:07:46 -0500 (EST)
From: Zygmunt Haas <haas@ee.cornell.edu>
To: Phil_Neumiller@3com.com
cc: Charlie Perkins <charliep@iprg.nokia.com>, seamoby@diameter.org,
        manet@itd.nrl.navy.mil
Subject: Re: [seamoby] Upcoming REAL IP for Bluetooth BOF
In-Reply-To: <882569EA.00760153.00@hqoutbound.ops.3com.com>
Message-ID: <Pine.GSO.4.05.10102072103520.8562-100000@verdi.ee.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi Phil,

As a side note, you forgot the issue of hybrid protocols; i.e., the
tradeoff between proactive and reactive routing, as to achieve adaptivity
in the operation/configuration of an ad hoc network. Yes, the Zone Routing
Protocol (ZRP) is an example of a framework that supports such a tradeoff.

Yes, it has been worked on and some preliminary results presented in the
IETF meetings.

Zygmunt.
===--====
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Prof. Zygmunt J. Haas                    tel: +1-607-255-3454
Wireless Networks Laboratory		                  
School of Electrical Engineering         fax: +1-607-255-9072 
Cornell University
323 Frank Rhodes Hall			 e-mail: haas@ece.cornell.edu
Ithaca, NY 14853			 
U.S.A                             http://www.ee.cornell.edu/~haas/wnl.html
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
--------------------------------------------------------------------------
Words of Wisdom:
"Turns out that not where, but who you are with that really matters." 
						       David Matthews
--------------------------------------------------------------------------

On Mon, 5 Feb 2001 Phil_Neumiller@3com.com wrote:

> 
> 
> 
> Hi Charlie,
> 
> I cross-posted this to MANET, please forgive multiple copies.
> 
> BTW, Thanks for the AODV recommendation...
> 
> As a casual observer of MANET activity I look at the work and I see no RFC
> for basic ad hoc networking.  Case closed.  I do see the following work in
> progress (which as been in progress for some time):
> 
> o (AODV) Routing
> o Temporally-Ordered Routing Algorithm (TORA)
> o The Dynamic Source Routing Protocol for Mobile Ad Hoc Networks
> o Optimized Link State Routing Protocol
> o Differential Destination Multicast (DDM) Specification
> o Multicast Ad hoc On-Demand Distance Vector (MAODV)
> o Topology Broadcast based on Reverse-Path Forwarding (TBRPF)
> o Landmark Routing Protocol (LANMAR) for Large Scale Ad Hoc Networks
> o A Simple Protocol for Multicast and Broadcast in Mobile Ad Hoc Networks
> o Fisheye State Routing Protocol (FSR) for Ad Hoc Networks
> 
> While I am quite convinced that ALL this work is valuable and useful it
> does not solve my basic problems (at least not in a standard way).
> WHAT IS THE IETF's consensus and current recommendation for basic
> ad hoc networking???  Would this work not prove to be better served
> in the IRTF?  It seems the MANET WG should be working more towards
> a consensus and a standard RFC protocol for ad hoc networking right?
> If I am out of order here please explain.
> 
> Thanks,
> 
> -Phil
> 
> 
> 



From owner-manet@itd.nrl.navy.mil  Thu Feb  8 13:45:46 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 NAA16254
	for <manet-archive@odin.ietf.org>; Thu, 8 Feb 2001 13:45:46 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08810
	for manet-outgoing; Thu, 8 Feb 2001 11:46:47 -0500 (EST)
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 LAA08803
	for <manet@itd.nrl.navy.mil>; Thu, 8 Feb 2001 11:46:43 -0500 (EST)
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 f18Gkff00126
	for <manet@itd.nrl.navy.mil>; Thu, 8 Feb 2001 18:46:41 +0200 (EET)
Received: from esebh02nok.ntc.nokia.com (unverified) by esvir02nok.nokia.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T519bc906a0ac158f22148@esvir02nok.nokia.com>;
 Thu, 8 Feb 2001 18:46:33 +0200
Received: from loki.research.nokia.com ([172.21.33.76]) by esebh02nok.ntc.nokia.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.78)
	id 1LYJGPVY; Thu, 8 Feb 2001 18:46:33 +0200
Received: from nokia.com (tarom@tarom.research.nokia.com [172.21.60.45])
	by loki.research.nokia.com (8.9.3/8.9.3) with ESMTP id SAA26561;
	Thu, 8 Feb 2001 18:46:33 +0200 (EET)
X-Authentication-Warning: loki.research.nokia.com: Host tarom@tarom.research.nokia.com [172.21.60.45] claimed to be nokia.com
Message-ID: <3A82CD2A.D3FB07E7@nokia.com>
Date: Thu, 08 Feb 2001 18:45:30 +0200
From: Manel Guerrero Zapata <manel.guerrero-zapata@nokia.com>
X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.14 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: "Elizabeth M. Royer" <eroyer@cs.ucsb.edu>
CC: manet@itd.nrl.navy.mil
Subject: about 'draft-ietf-manet-aodv6-00.txt'
References: <200102072210.OAA16174@letters.cs.ucsb.edu>
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 :)

I've just been reading the 'draft-ietf-manet-aodv6-00.txt'.
(I didn't know that it was out since last November)

Just one small detail (probably somebody else has already point it out):

8<-------------------------------------------

4. Route Reply (RREP) Message Format

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |R|A|    Reserved     |Prefix Sz|   Hop Count   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |              32-bit Destination Sequence Number               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   |                128-bit Destination IP Address                 |
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   |                   128-bit Source IP Address                   |
   |                                                               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                           Lifetime                            |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

------------------------------------------->8

I guess the size of the 'Prefix Size' field should be 7 instead of 5.
(5 bits where fine for a 32-bit address,
but 7 are required for a 128-bit one).

So, maybe it should be like:


    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     Type      |R|A|   Reserved  |  Prefix Sz  |   Hop Count   |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                                                               |
   ...



Regards,

	Manel Guerrero


From owner-manet@itd.nrl.navy.mil  Thu Feb  8 16:48:37 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 QAA20468
	for <manet-archive@odin.ietf.org>; Thu, 8 Feb 2001 16:48:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id PAA16461
	for manet-outgoing; Thu, 8 Feb 2001 15:16:10 -0500 (EST)
Received: from rmx470-mta.mail.com (rmx470-mta.mail.com [165.251.48.48])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id PAA16456
	for <manet@itd.nrl.navy.mil>; Thu, 8 Feb 2001 15:16:08 -0500 (EST)
Received: from web584-mc (web584-mc.mail.com [165.251.48.94])
	by rmx470-mta.mail.com (8.9.3/8.9.3) with SMTP id PAA18380
	for <manet@itd.nrl.navy.mil>; Thu, 8 Feb 2001 15:14:47 -0500 (EST)
Message-ID: <385451579.981663287592.JavaMail.root@web584-mc>
Date: Thu, 8 Feb 2001 15:14:47 -0500 (EST)
From: Diego Pamio <dpamio@mail.com>
To: MANET List <manet@itd.nrl.navy.mil>
Subject: Simulation essay design.
Mime-Version: 1.0
Content-Type: text/plain
X-Mailer: mail.com
X-Originating-IP: 200.43.120.157
X-MIME-Autoconverted: from quoted-printable to 8bit by itd.nrl.navy.mil id PAA16457
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by itd.nrl.navy.mil id PAA16461
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA20468

Hi.
We are trying to simulate some ad-hoc routing protocols. As you may know,
there are serveral works in this area. While reading some of them, we found
out that those papers show, for example, the throughput of a netwok against
some variable, for instance, the mobility. Our question is: what happen with
the other parameters? Are they fixed? And if they are, how are they
obtained?
If some of this “fixed” values are changed, what happen with the curve shown
in the graph?

How can we know that one of this graphics won’t turn into the other…

T *************************     T *************************
H *                       *     H *                       *
R *oo                     *     R *o                      *
O *  ooo                  *     O *o                      *
U *     oooo              *     U * o                     *
G *___      oooooo        *     G *__o_____________       *
H *   |____       oooooooo*     H *   oo           |______*
P *        |________      *     P *     ooo               *
U *                 |_____*     U *        ooooooooooooooo*
T *************************     T *************************
MOBILITY                         MOBILITY
o   DSR
_   DSDV

…changing, for instance, the number of nodes involved in the network, or the
traffic pattern, or the total time of the simulation, etc.?

Should we vary this other variables (making all the posible combinations)
and then take the average value, or make some kind of data analysis? Or is
there an easier way to do a valid (and representative) simulation?

Thank you.


______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup


From owner-manet@itd.nrl.navy.mil  Fri Feb  9 20:58:52 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 UAA06149
	for <manet-archive@odin.ietf.org>; Fri, 9 Feb 2001 20:58:52 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id TAA20464
	for manet-outgoing; Fri, 9 Feb 2001 19:02:35 -0500 (EST)
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id TAA20459
	for <manet@itd.nrl.navy.mil>; Fri, 9 Feb 2001 19:02:33 -0500 (EST)
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2650.21)
	id <CTQSWK33>; Fri, 9 Feb 2001 19:02:32 -0500
Message-ID: <FC0292EA4D13D34EA2E5FC728D70A8E3078C23@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'zeroconf@merit.edu'" <zeroconf@merit.edu>, seamoby@cdma-2000.org,
        MOBILE-IP@standards.nortelnetworks.com,
        "'srvloc@srvloc.org'"
	 <srvloc@srvloc.org>,
        "'aaa-wg@merit.edu'" <aaa-wg@merit.edu>,
        "'manet@itd.nrl.navy.mil'" <manet@itd.nrl.navy.mil>,
        "'ipsec@lists.tislabs.com'" <ipsec@lists.tislabs.com>,
        "'ipsec-policy@vpnc.org'" <ipsec-policy@vpnc.org>,
        "'ietf-ipsra@vpnc.org'" <ietf-ipsra@vpnc.org>,
        "'ietf-sacred@imc.org'"
	 <ietf-sacred@imc.org>,
        "'enum@ietf.org'" <enum@ietf.org>,
        "'sigtran@standards.nortelnetworks.com'"
	 <sigtran@standards.nortelnetworks.com>,
        "'ietf@ietf.org'"
	 <ietf@ietf.org>,
        "'IETF-Announce@ietf.org'" <IETF-Announce@ietf.org>,
        "'BLUETOOTH-BOF@mailbag.cps.intel.com'"
	 <BLUETOOTH-BOF@mailbag.cps.intel.com>
Cc: "'Thomas Narten'" <narten@raleigh.ibm.com>,
        Akers Ron-WRA001
	 <Ron.Akers@motorola.com>
Subject: BOF:   IP over Bluetooth for 50th Meeting of IETF. 
Date: Fri, 9 Feb 2001 19:02:30 -0500 
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



Myself and Ron Akers have requested an IP over Bluetooth BOF for the 50th
Meeting of the IETF in Minneapolis.  The BOF will discuss the creation of a
IETF Working Group to investigate the most open and efficient way to place
IP over the Bluetooth Host Controller.

Current work in this area within the Bluetooth SIG concentrates on defining
IP over a set of other lower-layer stacks. Currently there are two options
defined by the Bluetoth SIG:

 Option 1: IP/PPP/RFCOM/L2CAP/Host Controller

 Option 2: IP/PAN Profile/L2CAP/Host Controller
 	   (where the PAN Profile is a Bluetooth SIG work in progress)
 

We are proposing that the IETF form a WG to define a more efficient way of
running IP over Bluetooth. In particular, IP would run
 over an IETF protocol over the Host Controller without L2CAP.  This option
may be adopted by the Bluetooth SIG at a later date as a Profile.  Since all
Bluetooth SIG Profiles are optional, a customer may choose any combination
of Profiles in a final product.  Further, since Bluetooth Working Groups
have it in their mandate to adopt protocols from other standards making
bodies such as the IETF, there exists a clear path for IETF work to be
adopted by the Bluetooth SIG.
 
Whereas the last BOF was informational only and organized by the Bluetooth
SIG itself, the objective of this BOF will be to foster innovation, and
speed progress by placing IP related protocol development wihin the IETF and
Bluetooth-specific protocol development
 within the Bluetooth SIG, by developing an IP over Bluetooth IETF Working
Group.
 
This effort will define its own way of running IP over Bluetooth, by
carefully selecting a set of Bluetooth protocols (freely available from
published specifications at
http://www.bluetooth.com/developer/specification/specification.asp) on which
to build IP.

Please join myself, Kulwinder Atwal, and Ron Akers on the pre-BOF mailing
list:
 
This site runs version 2.0.1 of the "Mailman" list manager.  
The following describes commands you can send to get
information about, and control your subscription to the lists at
this site. Note that much of the following can also be 
accomplished via the World Wide Web, at:

    http://internet.motlabs.com/mailman/listinfo/bluetooth

In particular, you can use the Web site to have your password sent to
your delivery address.

Email commands can be in the subject line or in the body 
of the message. The commands should be set to the following address:

  <bluetooth-request@internet.motlabs.com>

About the descriptions - words in "<>"s signify REQUIRED items and
words in "[]" denote OPTIONAL items.  Do not include the "<>"s or
"[]"s when you use the commands.

The following commands are valid:

    subscribe [password] [digest-option] [address=<address>]
        Subscribe to the mailing list.  Your password must be given to
        unsubscribe or change your options.  When you subscribe to the
        list, you'll be reminded of your password periodically.
        'digest-option' may be either: 'nodigest' or 'digest' (no
        quotes!)  If you wish to subscribe an address other than the
        address you send this request from, you may specify
        "address=<email address>" (no brackets around the email
        address, no quotes!)

    unsubscribe <password> [address]
        Unsubscribe from the mailing list.  Your password must match
        the one you gave when you subscribed.  If you are trying to
        unsubscribe from a different address than the one you
        subscribed from, you may specify it in the 'address' field.

    who
        See everyone who is on this mailing list.

    info
        View the introductory information for this list.

    lists
        See what mailing lists are run by this Mailman server.

    help
        This message.

    set <option> <on|off> <password> 
        Turn on or off list options.  Valid options are:

        ack:
            Turn this on to receive acknowledgement mail when you send
            mail to the list.

        digest:
            Receive mail from the list bundled together instead of one
            post at a time.

        plain:
            Get plain-text, not MIME-compliant, digests (only if
            digest is set)

        nomail:
            Stop delivering mail.  Useful if you plan on taking a
            short vacation.

        norcv:
            Turn this on to NOT receive posts you send to the list.
            Does not work if digest is set.

        hide:
            Conceals your address when people look at who is on this
            list.


    options
        Show the current values of your list options.

    password <oldpassword> <newpassword> 
        Change your list password.
    
    end or --
       Stop processing commands (good to do if your mailer
       automatically adds a signature file - it'll save you from a lot
       of cruft).


Commands should be sent to bluetooth-request@internet.motlabs.com

Questions and concerns for the attention of a person should be sent to

    bluetooth-admin@internet.motlabs.com



Kulwinder Atwal
Bluetooth Design
Zucotto Wireless Inc.
kulwinder.atwal@zucotto.com

------------------------------------------------------------
Ron Akers                               Voice :(847)576-7928
Networks and Infrastructure Research      FAX :(847)576-3240
Motorola Laboratories           email:ron.akers@motorola.com 
1301 Algonquin Rd, Rm 2246
Schaumburg, IL. 60196
------------------------------------------------------------


From owner-manet@itd.nrl.navy.mil  Sun Feb 11 10:18:43 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 KAA09954
	for <manet-archive@odin.ietf.org>; Sun, 11 Feb 2001 10:18:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id IAA03691
	for manet-outgoing; Sun, 11 Feb 2001 08:03:58 -0500 (EST)
Received: from frigg.inter.net.il (frigg.inter.net.il [192.114.186.16])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id IAA03683
	for <manet@itd.nrl.navy.mil>; Sun, 11 Feb 2001 08:03:18 -0500 (EST)
Received: from 1david.tadlys ([192.116.242.18])
	by frigg.inter.net.il (Mirapoint)
	with SMTP id AJR08293;
	Sun, 11 Feb 2001 14:47:24 +0200 (IST)
Message-ID: <004f01c09429$3dceb1e0$589618ac@tadlys>
From: "David Almer zahav" <almer@tadlys.com>
To: <zeroconf@merit.edu>, <seamoby@cdma-2000.org>,
        <MOBILE-IP@marvin.corpeast.baynetworks.com>, <srvloc@srvloc.org>,
        <aaa-wg@merit.edu>, <manet@itd.nrl.navy.mil>,
        <ipsec@lists.tislabs.com>, <ipsec-policy@vpnc.org>,
        <ietf-ipsra@vpnc.org>, <ietf-sacred@imc.org>, <enum@ietf.org>,
        <sigtran@marvin.corpeast.baynetworks.com>, <ietf@ietf.org>,
        <IETF-Announce@ietf.org>, <BLUETOOTH-BOF@mailbag.cps.intel.com>
Cc: "David Almer @tadlys" <almer@tadlys.com>
Subject: BOF: IP over Bluetooth for 50th Meeting of IETF.
Date: Sun, 11 Feb 2001 14:49:15 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_003A_01C09439.CE0A4480"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_003A_01C09439.CE0A4480
Content-Type: text/plain;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

Gentlemen,

Please join myself, David Almer on the pre-BOF mailing list.

Regards,
David Almer
Director Systems Engineering
Tadlys Ltd.
7 Oppenheimer St., Rehovot, Israel
tel:    972 - 8 - 936 6641
email: almer@tadlys.com
=20


------=_NextPart_000_003A_01C09439.CE0A4480
Content-Type: text/html;
	charset="windows-1255"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1255" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Gentlemen,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Please join myself, David Almer on the =
pre-BOF=20
mailing list.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><BR>Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>David Almer</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Director Systems =
Engineering</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Tadlys&nbsp;Ltd.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>7 Oppenheimer St., Rehovot, =
Israel</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>tel:&nbsp;&nbsp;&nbsp; 972 - 8 - 936=20
6641</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>email:=20
almer@tadlys.com<BR>&nbsp;<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_003A_01C09439.CE0A4480--



From owner-manet@itd.nrl.navy.mil  Sun Feb 11 10:18:45 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 KAA09965
	for <manet-archive@odin.ietf.org>; Sun, 11 Feb 2001 10:18:45 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id IAA03777
	for manet-outgoing; Sun, 11 Feb 2001 08:19:34 -0500 (EST)
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id IAA03772
	for <manet@itd.nrl.navy.mil>; Sun, 11 Feb 2001 08:19:32 -0500 (EST)
Received: from randy by rip.psg.com with local (Exim 3.16 #1)
	id 14RwNr-000MOk-00; Sun, 11 Feb 2001 05:17:43 -0800
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: "David Almer zahav" <almer@tadlys.com>
Cc: <zeroconf@merit.edu>, <seamoby@cdma-2000.org>,
        <MOBILE-IP@marvin.corpeast.baynetworks.com>, <srvloc@srvloc.org>,
        <aaa-wg@merit.edu>, <manet@itd.nrl.navy.mil>,
        <ipsec@lists.tislabs.com>, <ipsec-policy@vpnc.org>,
        <ietf-ipsra@vpnc.org>, <ietf-sacred@imc.org>, <enum@ietf.org>,
        <sigtran@marvin.corpeast.baynetworks.com>, <ietf@ietf.org>,
        <IETF-Announce@ietf.org>, <BLUETOOTH-BOF@mailbag.cps.intel.com>
Subject: Re: BOF: IP over Bluetooth for 50th Meeting of IETF.
References: <004f01c09429$3dceb1e0$589618ac@tadlys>
Message-Id: <E14RwNr-000MOk-00@rip.psg.com>
Date: Sun, 11 Feb 2001 05:17:43 -0800
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 7bit

> Gentlemen,

> Please join myself, David Almer on the pre-BOF mailing list.

are women not welcome?

randy


From owner-mmnet@itd.nrl.navy.mil  Sun Feb 11 16:11:49 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 QAA12427
	for <manet-archive@odin.ietf.org>; Sun, 11 Feb 2001 16:11:48 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id OAA06618
	for mmnet-outgoing; Sun, 11 Feb 2001 14:07:33 -0500 (EST)
Received: from ns0.utdallas.edu (ns0.utdallas.edu [129.110.10.1])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id OAA06613
	for <mmnet@itd.NRL.NAVY.MIL>; Sun, 11 Feb 2001 14:07:31 -0500 (EST)
Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9])
	by ns0.utdallas.edu (Postfix) with ESMTP id B20101A0077
	for <mmnet@itd.NRL.NAVY.MIL>; Sun, 11 Feb 2001 13:07:31 -0600 (CST)
Received: from localhost (basagni@localhost)
	by apache.utdallas.edu (8.9.1/8.9.1) with ESMTP id NAA26273
	for <mmnet@itd.NRL.NAVY.MIL>; Sun, 11 Feb 2001 13:07:31 -0600 (CST)
X-Authentication-Warning: apache.utdallas.edu: basagni owned process doing -bs
Date: Sun, 11 Feb 2001 13:07:31 -0600 (CST)
From: Stefano Basagni <basagni@utdallas.edu>
To: mmnet@itd.nrl.navy.mil
Subject: WCMC Special Issue on MANETs
Message-ID: <Pine.GSO.4.21.0102111305440.25512-100000@apache.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-mmnet@itd.nrl.navy.mil
Precedence: bulk

We  apologize if you received multiple copies of this Call for Papers.

Please, feel free to distribute it to those who might be interested.

Very truly yours,

the guest editors

*************************** CALL FOR PAPERS ***************************

                          WILEY INTERSCIENCE 
                announces a Special Issue of the Journal

           WIRELESS COMMUNICATIONS & MOBILE COMPUTING (WCMC)
         (http://www.interscience.wiley.com/jpages/1530-8669/)

                                   on

      MOBILE AD HOC NETWORKING: RESEARCH, TRENDS AND APPLICATIONS


                          With Guest Editors

                         Prof. Stefano Basagni
  Center for Advanced Telecommunications Systems and Services (CATSS)
                     Department of Computer Science
                   The University of Texas at Dallas
                          basagni@utdallas.edu


                            Dr. Sung-Ju Lee
                Internet and Mobile Systems Laboratories
                      Hewlett-Packard Laboratories
                            sjlee@hpl.hp.com


* OVERVIEW:

Tertio millennio ineunte (at the dawn of the third millennium) it is
more and more clear that wireless communications will be the natural
form of communication among people, living beings and things. Virtually
every appliance will be equipped with a small, cheap, lightweight
wireless interface and the possibility of communicating anytime, from
anywhere, to anybody/thing, in the world and beyond, is imminent.

At the focal point between wireless communications and mobile computing,
mobile ad hoc networking is rising as the technology that fits better in
scenarios where fixed infrastructure, such as the one of cellular
wireless networks, is neither available nor a viable choice. Among the
major challenges imposed by the ad hoc architecture, are the mobility of
possibly all network nodes and unpredictable and continuous change in
the network topology. In addition, because of the limited radio
propagation range, routes are mostly multihop. These characteristics in
combination with bandwidth, energy and memory constraints make ad hoc
networking research interesting and challenging.


* SCOPE:

With this special issue we aim at bringing together state-of-the-art
contributions that range from papers that report novel research to
papers that describe commercial and industrial experiences. We are
seeking for papers that are original, unpublished, and not currently
under review by another conference, workshop, or journal. Topics of
interest include, but are not limited to the following:

        * Implementation and testbed experiments
        * Industrial state of the art
        * Routing, multicasting and broadcasting protocols
        * TCP and reliable multicast
        * Security and Privacy
        * Energy efficient protocols
        * Protocol analysis, evaluation and optimization
        * Bluetooth and home networking
        * Medium access control
        * Applications
        * Quality of service
        * Sensor networks
        * Pervasive computing
        * Interoperation with wired/cellular networks
        * Clustering
        * Network architecture and management
        * Congestion, admission and flow control


* PUBLICATION SCHEDULE:

   o MANUSCRIPT DUE: August 31, 2001
   o ACCEPTANCE NOTIFICATION: December 15, 2001
   o FINAL MANUSCRIPT DUE: January 15, 2002
   o PUBLICATION DATE: Second quarter 2002


* SUBMISSION GUIDELINES:

Authors should email an electronic (Postscript or PDF) copy of their
paper to Dr. Sung-Ju Lee, sjlee@hpl.hp.com, by August 31, 2001.
Submissions should be limited to 20 double space pages excluding
figures, graphs and illustrations. If email submission is impossible
then six (6) copies of the paper (double-sided if possible) should be
sent by the due date to:

     Dr. Sung-Ju Lee
     Hewlett-Packard Laboratories
     1501 Page Mill Road, Mailstop 1U-17
     Palo Alto, CA 94304-1126
     Tel. (650)-857-3894


For more information visit:
              http://www.utdallas.edu/~basagni/wcmcsi.html

***********************************************************************


--
Stefano Basagni, Ph.D.          Assistant Professor of Computer Science
Center for Advanced Telecommunications Systems and Services     (CATSS)
The University of Texas at Dallas MS EC31          Richardson, TX 75080
Tel. 972 883 2216 ~~~ Fax 972 883 6204 ~~~ E-mail: basagni@utdallas.edu



From owner-manet@itd.nrl.navy.mil  Sun Feb 11 19:04: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 TAA13770
	for <manet-archive@odin.ietf.org>; Sun, 11 Feb 2001 19:04:39 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id RAA07978
	for manet-outgoing; Sun, 11 Feb 2001 17:06:37 -0500 (EST)
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id RAA07973
	for <manet@itd.nrl.navy.mil>; Sun, 11 Feb 2001 17:06:35 -0500 (EST)
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2650.21)
	id <CTQSWK83>; Sun, 11 Feb 2001 17:06:34 -0500
Message-ID: <FC0292EA4D13D34EA2E5FC728D70A8E3078C30@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'Randy Bush'" <randy@psg.com>, David Almer zahav <almer@tadlys.com>
Cc: zeroconf@merit.edu, seamoby@cdma-2000.org,
        MOBILE-IP@marvin.corpeast.baynetworks.com, srvloc@srvloc.org,
        aaa-wg@merit.edu, manet@itd.nrl.navy.mil, ipsec@lists.tislabs.com,
        ipsec-policy@vpnc.org, ietf-ipsra@vpnc.org, ietf-sacred@imc.org,
        enum@ietf.org, sigtran@marvin.corpeast.baynetworks.com, ietf@ietf.org,
        IETF-Announce@ietf.org, BLUETOOTH-BOF@mailbag.cps.intel.com
Subject: RE: [seamoby] Re: BOF: IP over Bluetooth for 50th Meeting of IETF
	.
Date: Sun, 11 Feb 2001 17:06:26 -0500
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

Everyone's invited!  Welcome.

- Kulwinder Atwal.


> -----Original Message-----
> From: Randy Bush [mailto:randy@psg.com]
> Sent: Sunday, February 11, 2001 8:18 AM
> To: David Almer zahav
> Cc: zeroconf@merit.edu; seamoby@cdma-2000.org;
> MOBILE-IP@marvin.corpeast.baynetworks.com; srvloc@srvloc.org;
> aaa-wg@merit.edu; manet@itd.nrl.navy.mil; ipsec@lists.tislabs.com;
> ipsec-policy@vpnc.org; ietf-ipsra@vpnc.org; ietf-sacred@imc.org;
> enum@ietf.org; sigtran@marvin.corpeast.baynetworks.com; ietf@ietf.org;
> IETF-Announce@ietf.org; BLUETOOTH-BOF@mailbag.cps.intel.com
> Subject: [seamoby] Re: BOF: IP over Bluetooth for 50th 
> Meeting of IETF.
> 
> 
> > Gentlemen,
> 
> > Please join myself, David Almer on the pre-BOF mailing list.
> 
> are women not welcome?
> 
> randy
> 


From owner-manet@itd.nrl.navy.mil  Mon Feb 12 06:57:04 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 GAA03882
	for <manet-archive@odin.ietf.org>; Mon, 12 Feb 2001 06:57:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id FAA13474
	for manet-outgoing; Mon, 12 Feb 2001 05:07:30 -0500 (EST)
Received: from mimesweeper.radioscape.com (mail.radioscape.com [193.122.23.66])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id FAA13456
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 05:05:08 -0500 (EST)
Received: from euler.radioscape.com (unverified) by mimesweeper.radioscape.com
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T51ae8647d20a000006102@mimesweeper.radioscape.com>;
 Mon, 12 Feb 2001 10:06:26 +0000
Received: by EULER with Internet Mail Service (5.5.2653.19)
	id <C03YGBMN>; Mon, 12 Feb 2001 09:58:38 -0000
Message-ID: <3190BC9FA8F6D3119508009027E5B33E1CDBF6@MORSE>
From: "Thakare, Kiran" <KThakare@radioscape.com>
To: "'Randy Bush'" <randy@psg.com>, David Almer zahav <almer@tadlys.com>
Cc: zeroconf@merit.edu, seamoby@cdma-2000.org,
        MOBILE-IP@marvin.corpeast.baynetworks.com, srvloc@srvloc.org,
        aaa-wg@merit.edu, manet@itd.nrl.navy.mil, ipsec@lists.tislabs.com,
        ipsec-policy@vpnc.org, ietf-ipsra@vpnc.org, ietf-sacred@imc.org,
        enum@ietf.org, sigtran@marvin.corpeast.baynetworks.com, ietf@ietf.org,
        IETF-Announce@ietf.org, BLUETOOTH-BOF@mailbag.cps.intel.com
Subject: RE: BOF: IP over Bluetooth for 50th Meeting of IETF.
Date: Mon, 12 Feb 2001 10:06:26 -0000
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

Dear All (whatever gender u amy carry)

Please join myself 'Ms Kiran Thakare' for pre-BOF mailing list.

Thanks
Kiran

-----Original Message-----
From: Randy Bush [mailto:randy@PSG.COM]
Sent: 11 February 2001 13:18
To: David Almer zahav
Cc: zeroconf@merit.edu; seamoby@cdma-2000.org;
MOBILE-IP@marvin.corpeast.baynetworks.com; srvloc@srvloc.org;
aaa-wg@merit.edu; manet@itd.nrl.navy.mil; ipsec@lists.tislabs.com;
ipsec-policy@vpnc.org; ietf-ipsra@vpnc.org; ietf-sacred@imc.org;
enum@ietf.org; sigtran@marvin.corpeast.baynetworks.com; ietf@ietf.org;
IETF-Announce@ietf.org; BLUETOOTH-BOF@mailbag.cps.intel.com
Subject: Re: BOF: IP over Bluetooth for 50th Meeting of IETF.


> Gentlemen,

> Please join myself, David Almer on the pre-BOF mailing list.

are women not welcome?

randy


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
postmaster@radioscape.com.

This footnote also confirms that this email message has been scanned
for the presence of computer viruses known at the time of sending.

www.radioscape.com
**********************************************************************


From owner-manet@itd.nrl.navy.mil  Mon Feb 12 16:21:50 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 QAA21835
	for <manet-archive@odin.ietf.org>; Mon, 12 Feb 2001 16:21:50 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id NAA29406
	for manet-outgoing; Mon, 12 Feb 2001 13:24:54 -0500 (EST)
Received: from NEPTUNE.zucotto.com ([216.95.209.154])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id NAA29396
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 13:24:52 -0500 (EST)
Received: by NEPTUNE.zucotto.com with Internet Mail Service (5.5.2650.21)
	id <CTQSWMHL>; Mon, 12 Feb 2001 13:24:47 -0500
Message-ID: <FC0292EA4D13D34EA2E5FC728D70A8E33935CA@NEPTUNE.zucotto.com>
From: Kulwinder Atwal <kulwinder.atwal@zucotto.com>
To: "'James Kempf'" <kempf@heliopolis.Eng.Sun.COM>, zeroconf@merit.edu,
        seamoby@cdma-2000.org, MOBILE-IP@standards.nortelnetworks.com,
        srvloc@srvloc.org, aaa-wg@merit.edu, manet@itd.nrl.navy.mil,
        ipsec@lists.tislabs.com, ipsec-policy@vpnc.org, ietf-ipsra@vpnc.org,
        ietf-sacred@imc.org, enum@ietf.org,
        sigtran@standards.nortelnetworks.com, ietf@ietf.org,
        IETF-Announce@ietf.org, BLUETOOTH-BOF@mailbag.cps.intel.com,
        kulwinder.atwal@herc.zucotto.com
Cc: narten@raleigh.ibm.com, Ron.Akers@motorola.com
Subject: RE: [seamoby] BOF:   IP over Bluetooth for 50th Meeting of IETF. 
Date: Mon, 12 Feb 2001 13:24:43 -0500
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

Your concerns will be addressed in a favourable manner.
Please join the list.  Your input is very welcome.

- Kulwinder.

> -----Original Message-----
> From: James Kempf [mailto:kempf@heliopolis.Eng.Sun.COM]
> Sent: Monday, February 12, 2001 1:18 PM
> To: zeroconf@merit.edu; seamoby@cdma-2000.org;
> MOBILE-IP@standards.nortelnetworks.com; srvloc@srvloc.org;
> aaa-wg@merit.edu; manet@itd.nrl.navy.mil; ipsec@lists.tislabs.com;
> ipsec-policy@vpnc.org; ietf-ipsra@vpnc.org; ietf-sacred@imc.org;
> enum@ietf.org; sigtran@standards.nortelnetworks.com; ietf@ietf.org;
> IETF-Announce@ietf.org; BLUETOOTH-BOF@mailbag.cps.intel.com;
> kulwinder.atwal@herc.zucotto.com
> Cc: narten@raleigh.ibm.com; Ron.Akers@motorola.com
> Subject: Re: [seamoby] BOF: IP over Bluetooth for 50th 
> Meeting of IETF. 
> 
> 
> Kulwinder,
> 
> There is an issue here with the closed, proprietary nature of 
> the Bluetooth
> SIG. Since information on what the SIG is doing is not available until
> it is complete, there is nothing to prevent the SIG from 
> doing something
> that would invalidate the work that IETF puts into desiging a better
> IP over Bluetooth.
> 
> Is there any possibility of gaining assurance from the SIG that they
> won't do something like this?
> 
> 		jak
> 
> 
> >
> >Myself and Ron Akers have requested an IP over Bluetooth BOF 
> for the 50th
> >Meeting of the IETF in Minneapolis.  The BOF will discuss 
> the creation of a
> >IETF Working Group to investigate the most open and 
> efficient way to place
> >IP over the Bluetooth Host Controller.
> >
> >Current work in this area within the Bluetooth SIG 
> concentrates on defining
> >IP over a set of other lower-layer stacks. Currently there 
> are two options
> >defined by the Bluetoth SIG:
> >
> > Option 1: IP/PPP/RFCOM/L2CAP/Host Controller
> >
> > Option 2: IP/PAN Profile/L2CAP/Host Controller
> > 	   (where the PAN Profile is a Bluetooth SIG work in progress)
> > 
> >
> >We are proposing that the IETF form a WG to define a more 
> efficient way of
> >running IP over Bluetooth. In particular, IP would run
> > over an IETF protocol over the Host Controller without 
> L2CAP.  This option
> >may be adopted by the Bluetooth SIG at a later date as a 
> Profile.  Since all
> >Bluetooth SIG Profiles are optional, a customer may choose 
> any combination
> >of Profiles in a final product.  Further, since Bluetooth 
> Working Groups
> >have it in their mandate to adopt protocols from other 
> standards making
> >bodies such as the IETF, there exists a clear path for IETF 
> work to be
> >adopted by the Bluetooth SIG.
> > 
> >Whereas the last BOF was informational only and organized by 
> the Bluetooth
> >SIG itself, the objective of this BOF will be to foster 
> innovation, and
> >speed progress by placing IP related protocol development 
> wihin the IETF and
> >Bluetooth-specific protocol development
> > within the Bluetooth SIG, by developing an IP over 
> Bluetooth IETF Working
> >Group.
> > 
> >This effort will define its own way of running IP over Bluetooth, by
> >carefully selecting a set of Bluetooth protocols (freely 
> available from
> >published specifications at
> >http://www.bluetooth.com/developer/specification/specificatio
> n.asp) on which
> >to build IP.
> >
> >Please join myself, Kulwinder Atwal, and Ron Akers on the 
> pre-BOF mailing
> >list:
> > 
> >This site runs version 2.0.1 of the "Mailman" list manager.  
> >The following describes commands you can send to get
> >information about, and control your subscription to the lists at
> >this site. Note that much of the following can also be 
> >accomplished via the World Wide Web, at:
> >
> >    http://internet.motlabs.com/mailman/listinfo/bluetooth
> >
> >In particular, you can use the Web site to have your password sent to
> >your delivery address.
> >
> >Email commands can be in the subject line or in the body 
> >of the message. The commands should be set to the following address:
> >
> >  <bluetooth-request@internet.motlabs.com>
> >
> >About the descriptions - words in "<>"s signify REQUIRED items and
> >words in "[]" denote OPTIONAL items.  Do not include the "<>"s or
> >"[]"s when you use the commands.
> >
> >The following commands are valid:
> >
> >    subscribe [password] [digest-option] [address=<address>]
> >        Subscribe to the mailing list.  Your password must 
> be given to
> >        unsubscribe or change your options.  When you 
> subscribe to the
> >        list, you'll be reminded of your password periodically.
> >        'digest-option' may be either: 'nodigest' or 'digest' (no
> >        quotes!)  If you wish to subscribe an address other than the
> >        address you send this request from, you may specify
> >        "address=<email address>" (no brackets around the email
> >        address, no quotes!)
> >
> >    unsubscribe <password> [address]
> >        Unsubscribe from the mailing list.  Your password must match
> >        the one you gave when you subscribed.  If you are trying to
> >        unsubscribe from a different address than the one you
> >        subscribed from, you may specify it in the 'address' field.
> >
> >    who
> >        See everyone who is on this mailing list.
> >
> >    info
> >        View the introductory information for this list.
> >
> >    lists
> >        See what mailing lists are run by this Mailman server.
> >
> >    help
> >        This message.
> >
> >    set <option> <on|off> <password> 
> >        Turn on or off list options.  Valid options are:
> >
> >        ack:
> >            Turn this on to receive acknowledgement mail 
> when you send
> >            mail to the list.
> >
> >        digest:
> >            Receive mail from the list bundled together 
> instead of one
> >            post at a time.
> >
> >        plain:
> >            Get plain-text, not MIME-compliant, digests (only if
> >            digest is set)
> >
> >        nomail:
> >            Stop delivering mail.  Useful if you plan on taking a
> >            short vacation.
> >
> >        norcv:
> >            Turn this on to NOT receive posts you send to the list.
> >            Does not work if digest is set.
> >
> >        hide:
> >            Conceals your address when people look at who is on this
> >            list.
> >
> >
> >    options
> >        Show the current values of your list options.
> >
> >    password <oldpassword> <newpassword> 
> >        Change your list password.
> >    
> >    end or --
> >       Stop processing commands (good to do if your mailer
> >       automatically adds a signature file - it'll save you 
> from a lot
> >       of cruft).
> >
> >
> >Commands should be sent to bluetooth-request@internet.motlabs.com
> >
> >Questions and concerns for the attention of a person should 
> be sent to
> >
> >    bluetooth-admin@internet.motlabs.com
> >
> >
> >
> >Kulwinder Atwal
> >Bluetooth Design
> >Zucotto Wireless Inc.
> >kulwinder.atwal@zucotto.com
> >
> >------------------------------------------------------------
> >Ron Akers                               Voice :(847)576-7928
> >Networks and Infrastructure Research      FAX :(847)576-3240
> >Motorola Laboratories           email:ron.akers@motorola.com 
> >1301 Algonquin Rd, Rm 2246
> >Schaumburg, IL. 60196
> >------------------------------------------------------------
> 


From owner-manet@itd.nrl.navy.mil  Mon Feb 12 16:33:37 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 QAA22014
	for <manet-archive@odin.ietf.org>; Mon, 12 Feb 2001 16:33:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id NAA29112
	for manet-outgoing; Mon, 12 Feb 2001 13:20:02 -0500 (EST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id NAA29101
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 13:19:55 -0500 (EST)
Received: from engmail2.Eng.Sun.COM ([129.146.1.25])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id KAA07466;
	Mon, 12 Feb 2001 10:17:57 -0800 (PST)
Received: from srmtv29a.Eng.Sun.COM (srmtv29a.Eng.Sun.COM [152.70.1.41])
	by engmail2.Eng.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with ESMTP id KAA11825;
	Mon, 12 Feb 2001 10:17:56 -0800 (PST)
Received: from srmtv29a (srmtv29a [152.70.1.41])
	by srmtv29a.Eng.Sun.COM (8.10.2+Sun/8.10.2) with SMTP id f1CIHtB19978;
	Mon, 12 Feb 2001 10:17:55 -0800 (PST)
Message-Id: <200102121817.f1CIHtB19978@srmtv29a.Eng.Sun.COM>
Date: Mon, 12 Feb 2001 10:17:55 -0800 (PST)
From: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Reply-To: James Kempf <kempf@heliopolis.Eng.Sun.COM>
Subject: Re: [seamoby] BOF:   IP over Bluetooth for 50th Meeting of IETF. 
To: zeroconf@merit.edu, seamoby@cdma-2000.org,
        MOBILE-IP@standards.nortelnetworks.com, srvloc@srvloc.org,
        aaa-wg@merit.edu, manet@itd.nrl.navy.mil, ipsec@lists.tislabs.com,
        ipsec-policy@vpnc.org, ietf-ipsra@vpnc.org, ietf-sacred@imc.org,
        enum@ietf.org, sigtran@standards.nortelnetworks.com, ietf@ietf.org,
        IETF-Announce@ietf.org, BLUETOOTH-BOF@mailbag.cps.intel.com,
        kulwinder.atwal@zucotto.com
Cc: narten@raleigh.ibm.com, Ron.Akers@motorola.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: IQNb6xGFCtgsJJ6tIPx3Gg==
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

Kulwinder,

There is an issue here with the closed, proprietary nature of the Bluetooth
SIG. Since information on what the SIG is doing is not available until
it is complete, there is nothing to prevent the SIG from doing something
that would invalidate the work that IETF puts into desiging a better
IP over Bluetooth.

Is there any possibility of gaining assurance from the SIG that they
won't do something like this?

		jak


>
>Myself and Ron Akers have requested an IP over Bluetooth BOF for the 50th
>Meeting of the IETF in Minneapolis.  The BOF will discuss the creation of a
>IETF Working Group to investigate the most open and efficient way to place
>IP over the Bluetooth Host Controller.
>
>Current work in this area within the Bluetooth SIG concentrates on defining
>IP over a set of other lower-layer stacks. Currently there are two options
>defined by the Bluetoth SIG:
>
> Option 1: IP/PPP/RFCOM/L2CAP/Host Controller
>
> Option 2: IP/PAN Profile/L2CAP/Host Controller
> 	   (where the PAN Profile is a Bluetooth SIG work in progress)
> 
>
>We are proposing that the IETF form a WG to define a more efficient way of
>running IP over Bluetooth. In particular, IP would run
> over an IETF protocol over the Host Controller without L2CAP.  This option
>may be adopted by the Bluetooth SIG at a later date as a Profile.  Since all
>Bluetooth SIG Profiles are optional, a customer may choose any combination
>of Profiles in a final product.  Further, since Bluetooth Working Groups
>have it in their mandate to adopt protocols from other standards making
>bodies such as the IETF, there exists a clear path for IETF work to be
>adopted by the Bluetooth SIG.
> 
>Whereas the last BOF was informational only and organized by the Bluetooth
>SIG itself, the objective of this BOF will be to foster innovation, and
>speed progress by placing IP related protocol development wihin the IETF and
>Bluetooth-specific protocol development
> within the Bluetooth SIG, by developing an IP over Bluetooth IETF Working
>Group.
> 
>This effort will define its own way of running IP over Bluetooth, by
>carefully selecting a set of Bluetooth protocols (freely available from
>published specifications at
>http://www.bluetooth.com/developer/specification/specification.asp) on which
>to build IP.
>
>Please join myself, Kulwinder Atwal, and Ron Akers on the pre-BOF mailing
>list:
> 
>This site runs version 2.0.1 of the "Mailman" list manager.  
>The following describes commands you can send to get
>information about, and control your subscription to the lists at
>this site. Note that much of the following can also be 
>accomplished via the World Wide Web, at:
>
>    http://internet.motlabs.com/mailman/listinfo/bluetooth
>
>In particular, you can use the Web site to have your password sent to
>your delivery address.
>
>Email commands can be in the subject line or in the body 
>of the message. The commands should be set to the following address:
>
>  <bluetooth-request@internet.motlabs.com>
>
>About the descriptions - words in "<>"s signify REQUIRED items and
>words in "[]" denote OPTIONAL items.  Do not include the "<>"s or
>"[]"s when you use the commands.
>
>The following commands are valid:
>
>    subscribe [password] [digest-option] [address=<address>]
>        Subscribe to the mailing list.  Your password must be given to
>        unsubscribe or change your options.  When you subscribe to the
>        list, you'll be reminded of your password periodically.
>        'digest-option' may be either: 'nodigest' or 'digest' (no
>        quotes!)  If you wish to subscribe an address other than the
>        address you send this request from, you may specify
>        "address=<email address>" (no brackets around the email
>        address, no quotes!)
>
>    unsubscribe <password> [address]
>        Unsubscribe from the mailing list.  Your password must match
>        the one you gave when you subscribed.  If you are trying to
>        unsubscribe from a different address than the one you
>        subscribed from, you may specify it in the 'address' field.
>
>    who
>        See everyone who is on this mailing list.
>
>    info
>        View the introductory information for this list.
>
>    lists
>        See what mailing lists are run by this Mailman server.
>
>    help
>        This message.
>
>    set <option> <on|off> <password> 
>        Turn on or off list options.  Valid options are:
>
>        ack:
>            Turn this on to receive acknowledgement mail when you send
>            mail to the list.
>
>        digest:
>            Receive mail from the list bundled together instead of one
>            post at a time.
>
>        plain:
>            Get plain-text, not MIME-compliant, digests (only if
>            digest is set)
>
>        nomail:
>            Stop delivering mail.  Useful if you plan on taking a
>            short vacation.
>
>        norcv:
>            Turn this on to NOT receive posts you send to the list.
>            Does not work if digest is set.
>
>        hide:
>            Conceals your address when people look at who is on this
>            list.
>
>
>    options
>        Show the current values of your list options.
>
>    password <oldpassword> <newpassword> 
>        Change your list password.
>    
>    end or --
>       Stop processing commands (good to do if your mailer
>       automatically adds a signature file - it'll save you from a lot
>       of cruft).
>
>
>Commands should be sent to bluetooth-request@internet.motlabs.com
>
>Questions and concerns for the attention of a person should be sent to
>
>    bluetooth-admin@internet.motlabs.com
>
>
>
>Kulwinder Atwal
>Bluetooth Design
>Zucotto Wireless Inc.
>kulwinder.atwal@zucotto.com
>
>------------------------------------------------------------
>Ron Akers                               Voice :(847)576-7928
>Networks and Infrastructure Research      FAX :(847)576-3240
>Motorola Laboratories           email:ron.akers@motorola.com 
>1301 Algonquin Rd, Rm 2246
>Schaumburg, IL. 60196
>------------------------------------------------------------



From owner-manet@itd.nrl.navy.mil  Mon Feb 12 21:34: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 VAA26512
	for <manet-archive@odin.ietf.org>; Mon, 12 Feb 2001 21:34:11 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id SAA10834
	for manet-outgoing; Mon, 12 Feb 2001 18:32:47 -0500 (EST)
Received: from pomo.cse.ucsc.edu (pomo.cse.ucsc.edu [128.114.49.67])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with SMTP id SAA10829
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 18:32:45 -0500 (EST)
Received: (from katia@localhost) by pomo.cse.ucsc.edu (8.6.10/8.6.12) id PAA04218; Mon, 12 Feb 2001 15:32:44 -0800
Date: Mon, 12 Feb 2001 15:32:44 -0800
Message-Id: <200102122332.PAA04218@pomo.cse.ucsc.edu>
From: Katia Obraczka <katia@cse.ucsc.edu>
To: manet@itd.nrl.navy.mil
Subject: Global Internet 2001
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk


                       Sixth Global Internet Symposium
                             in conjunction with

                                Globecom 2001
                           San Antonio, Texas, USA
                            November 25-29, 2001

                       http://www.cs.ucsb.edu/gi2001/
  ------------------------------------------------------------------------

                              Call For Papers

The sixth Global Internet Symposium will be held simultaneously and
co-located with Globecom 2001. Therefore, all of the relevant dates,
location, travel information are derived from the Globecom 2001
(http://www.globecom2001.com/) conference site.

Symposium Topics

Global Internet 2000 solicits technical papers on Internet-related topics.
The Program Committee encourages papers submitted on experimental systems
and emerging technologies. Also encouraged are original submissions
describing promising work in progress, original speculations about the
future of the Internet, and progressive position papers. Topics of interest
include, but are not limited to:

   * Novel applications and new paradigms (telephony, streaming media, etc.)
   * Distributed Internet applications (file sharing, games, conferencing,
     etc.)
   * Service provisioning, monitoring, and management
   * Privacy and/or security issues
   * Charging and billing issues
   * Handling Internet dynamics/heterogeneity (by applications and/or the
     network)
   * Routing (unicast, multicast, anycast, etc.)
   * Traffic measurement, analysis, modeling, and visualization
   * Flow management (fairness/sharing, differentiated services, etc.)
   * The Internet and mobility/mobile devices
   * Wireless device access and Internet gateways

Important Dates

            Manuscript Submission:       March 31, 2001
            Acceptance Notification:     July 31, 2001
            Final Manuscript:            September 31, 2000

Submission Instructions

   Please see the Global Internet Symposium WWW site at:

      http://www.cs.ucsb.edu/gi2001/

Technical Program Chairs

     Kevin Almeroth, UC-Santa Barbara (almeroth@cs.ucsb.edu)
     Katia Obraczka, UC-Santa Cruz (katia@cse.ucsc.edu)

Program Committee

     To be announced.

Sponsorship

The Global Internet Symposium is sponsored by the IEEE Communications
Society InternetTC.



From owner-manet@itd.nrl.navy.mil  Mon Feb 12 23:00: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 XAA28508
	for <manet-archive@odin.ietf.org>; Mon, 12 Feb 2001 23:00:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id VAA13445
	for manet-outgoing; Mon, 12 Feb 2001 21:08:58 -0500 (EST)
Received: from universe.serc.rmit.edu.au (universe.serc.rmit.edu.au [131.170.42.12])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id VAA13440
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 21:08:55 -0500 (EST)
Received: (from null@localhost)
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) id NAA12260;
	Tue, 13 Feb 2001 13:08:51 +1100 (EST)
Received: from fw.serc.rmit.edu.au (fw-in.serc.rmit.edu.au [131.170.42.1])
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) with ESMTP id NAA12253
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 13:08:50 +1100 (EST)
Received: (from mail@localhost)
	by fw.serc.rmit.edu.au (8.9.3/8.9.1) id NAA59529
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 13:16:04 +1100 (EST)
Received: from s2.itd.nrl.navy.mil(132.250.83.3) by fw.serc.rmit.edu.au via smap (V2.1)
	id xma059527; Tue, 13 Feb 01 13:15:58 +1100
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id SAA10834
	for manet-outgoing; Mon, 12 Feb 2001 18:32:47 -0500 (EST)
Received: from pomo.cse.ucsc.edu (pomo.cse.ucsc.edu [128.114.49.67])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with SMTP id SAA10829
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 18:32:45 -0500 (EST)
Received: (from katia@localhost) by pomo.cse.ucsc.edu (8.6.10/8.6.12) id PAA04218; Mon, 12 Feb 2001 15:32:44 -0800
Date: Mon, 12 Feb 2001 15:32:44 -0800
Message-Id: <200102122332.PAA04218@pomo.cse.ucsc.edu>
From: Katia Obraczka <katia@cse.ucsc.edu>
To: manet@itd.nrl.navy.mil
Subject: Global Internet 2001
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Your mail
     Global Internet 2001
to 
     manet@itd.nrl.navy.mil
has encountered a delivery problem.

The user has not left a forwarding address.
Your message has *not* been delivered.

SERC Autoresponder





                       Sixth Global Internet Symposium
                             in conjunction with

                                Globecom 2001
                           San Antonio, Texas, USA
                            November 25-29, 2001

                       http://www.cs.ucsb.edu/gi2001/
  ------------------------------------------------------------------------

                              Call For Papers

The sixth Global Internet Symposium will be held simultaneously and
co-located with Globecom 2001. Therefore, all of the relevant dates,
location, travel information are derived from the Globecom 2001
(http://www.globecom2001.com/) conference site.

Symposium Topics

Global Internet 2000 solicits technical papers on Internet-related topics.
The Program Committee encourages papers submitted on experimental systems
and emerging technologies. Also encouraged are original submissions
describing promising work in progress, original speculations about the
future of the Internet, and progressive position papers. Topics of interest
include, but are not limited to:

   * Novel applications and new paradigms (telephony, streaming media, etc.)
   * Distributed Internet applications (file sharing, games, conferencing,
     etc.)
   * Service provisioning, monitoring, and management
   * Privacy and/or security issues
   * Charging and billing issues
   * Handling Internet dynamics/heterogeneity (by applications and/or the
     network)
   * Routing (unicast, multicast, anycast, etc.)
   * Traffic measurement, analysis, modeling, and visualization
   * Flow management (fairness/sharing, differentiated services, etc.)
   * The Internet and mobility/mobile devices
   * Wireless device access and Internet gateways

Important Dates

            Manuscript Submission:       March 31, 2001
            Acceptance Notification:     July 31, 2001
            Final Manuscript:            September 31, 2000

Submission Instructions

   Please see the Global Internet Symposium WWW site at:

      http://www.cs.ucsb.edu/gi2001/

Technical Program Chairs

     Kevin Almeroth, UC-Santa Barbara (almeroth@cs.ucsb.edu)
     Katia Obraczka, UC-Santa Cruz (katia@cse.ucsc.edu)

Program Committee

     To be announced.

Sponsorship

The Global Internet Symposium is sponsored by the IEEE Communications
Society InternetTC.



From owner-manet@itd.nrl.navy.mil  Tue Feb 13 00:35: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 AAA29632
	for <manet-archive@odin.ietf.org>; Tue, 13 Feb 2001 00:35:55 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id WAA14691
	for manet-outgoing; Mon, 12 Feb 2001 22:39:27 -0500 (EST)
Received: from universe.serc.rmit.edu.au (universe.serc.rmit.edu.au [131.170.42.12])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id WAA14686
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 22:39:24 -0500 (EST)
Received: (from null@localhost)
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) id OAA12549;
	Tue, 13 Feb 2001 14:39:22 +1100 (EST)
Received: from fw.serc.rmit.edu.au (fw-in.serc.rmit.edu.au [131.170.42.1])
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) with ESMTP id OAA12542
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 14:39:22 +1100 (EST)
Received: (from mail@localhost)
	by fw.serc.rmit.edu.au (8.9.3/8.9.1) id OAA59684
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 14:46:36 +1100 (EST)
Received: from s2.itd.nrl.navy.mil(132.250.83.3) by fw.serc.rmit.edu.au via smap (V2.1)
	id xma059682; Tue, 13 Feb 01 14:46:08 +1100
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id VAA13445
	for manet-outgoing; Mon, 12 Feb 2001 21:08:58 -0500 (EST)
Received: from universe.serc.rmit.edu.au (universe.serc.rmit.edu.au [131.170.42.12])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id VAA13440
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 21:08:55 -0500 (EST)
Received: (from null@localhost)
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) id NAA12260;
	Tue, 13 Feb 2001 13:08:51 +1100 (EST)
Received: from fw.serc.rmit.edu.au (fw-in.serc.rmit.edu.au [131.170.42.1])
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) with ESMTP id NAA12253
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 13:08:50 +1100 (EST)
Received: (from mail@localhost)
	by fw.serc.rmit.edu.au (8.9.3/8.9.1) id NAA59529
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 13:16:04 +1100 (EST)
Received: from s2.itd.nrl.navy.mil(132.250.83.3) by fw.serc.rmit.edu.au via smap (V2.1)
	id xma059527; Tue, 13 Feb 01 13:15:58 +1100
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id SAA10834
	for manet-outgoing; Mon, 12 Feb 2001 18:32:47 -0500 (EST)
Received: from pomo.cse.ucsc.edu (pomo.cse.ucsc.edu [128.114.49.67])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with SMTP id SAA10829
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 18:32:45 -0500 (EST)
Received: (from katia@localhost) by pomo.cse.ucsc.edu (8.6.10/8.6.12) id PAA04218; Mon, 12 Feb 2001 15:32:44 -0800
Date: Mon, 12 Feb 2001 15:32:44 -0800
Message-Id: <200102122332.PAA04218@pomo.cse.ucsc.edu>
From: Katia Obraczka <katia@cse.ucsc.edu>
To: manet@itd.nrl.navy.mil
Subject: Global Internet 2001
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Your mail
     Global Internet 2001
to 
     manet@itd.nrl.navy.mil
has encountered a delivery problem.

The user has not left a forwarding address.
Your message has *not* been delivered.

SERC Autoresponder




Your mail
     Global Internet 2001
to 
     manet@itd.nrl.navy.mil
has encountered a delivery problem.

The user has not left a forwarding address.
Your message has *not* been delivered.

SERC Autoresponder





                       Sixth Global Internet Symposium
                             in conjunction with

                                Globecom 2001
                           San Antonio, Texas, USA
                            November 25-29, 2001

                       http://www.cs.ucsb.edu/gi2001/
  ------------------------------------------------------------------------

                              Call For Papers

The sixth Global Internet Symposium will be held simultaneously and
co-located with Globecom 2001. Therefore, all of the relevant dates,
location, travel information are derived from the Globecom 2001
(http://www.globecom2001.com/) conference site.

Symposium Topics

Global Internet 2000 solicits technical papers on Internet-related topics.
The Program Committee encourages papers submitted on experimental systems
and emerging technologies. Also encouraged are original submissions
describing promising work in progress, original speculations about the
future of the Internet, and progressive position papers. Topics of interest
include, but are not limited to:

   * Novel applications and new paradigms (telephony, streaming media, etc.)
   * Distributed Internet applications (file sharing, games, conferencing,
     etc.)
   * Service provisioning, monitoring, and management
   * Privacy and/or security issues
   * Charging and billing issues
   * Handling Internet dynamics/heterogeneity (by applications and/or the
     network)
   * Routing (unicast, multicast, anycast, etc.)
   * Traffic measurement, analysis, modeling, and visualization
   * Flow management (fairness/sharing, differentiated services, etc.)
   * The Internet and mobility/mobile devices
   * Wireless device access and Internet gateways

Important Dates

            Manuscript Submission:       March 31, 2001
            Acceptance Notification:     July 31, 2001
            Final Manuscript:            September 31, 2000

Submission Instructions

   Please see the Global Internet Symposium WWW site at:

      http://www.cs.ucsb.edu/gi2001/

Technical Program Chairs

     Kevin Almeroth, UC-Santa Barbara (almeroth@cs.ucsb.edu)
     Katia Obraczka, UC-Santa Cruz (katia@cse.ucsc.edu)

Program Committee

     To be announced.

Sponsorship

The Global Internet Symposium is sponsored by the IEEE Communications
Society InternetTC.



From owner-manet@itd.nrl.navy.mil  Tue Feb 13 02:04:54 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 CAA12668
	for <manet-archive@odin.ietf.org>; Tue, 13 Feb 2001 02:04:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id AAA16214
	for manet-outgoing; Tue, 13 Feb 2001 00:04:59 -0500 (EST)
Received: from universe.serc.rmit.edu.au (universe.serc.rmit.edu.au [131.170.42.12])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id AAA16209
	for <manet@itd.nrl.navy.mil>; Tue, 13 Feb 2001 00:04:56 -0500 (EST)
Received: (from null@localhost)
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) id QAA12826;
	Tue, 13 Feb 2001 16:04:54 +1100 (EST)
Received: from fw.serc.rmit.edu.au (fw-in.serc.rmit.edu.au [131.170.42.1])
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) with ESMTP id QAA12819
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 16:04:53 +1100 (EST)
Received: (from mail@localhost)
	by fw.serc.rmit.edu.au (8.9.3/8.9.1) id QAA59936
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 16:12:08 +1100 (EST)
Received: from s2.itd.nrl.navy.mil(132.250.83.3) by fw.serc.rmit.edu.au via smap (V2.1)
	id xma059934; Tue, 13 Feb 01 16:11:59 +1100
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id WAA14691
	for manet-outgoing; Mon, 12 Feb 2001 22:39:27 -0500 (EST)
Received: from universe.serc.rmit.edu.au (universe.serc.rmit.edu.au [131.170.42.12])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id WAA14686
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 22:39:24 -0500 (EST)
Received: (from null@localhost)
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) id OAA12549;
	Tue, 13 Feb 2001 14:39:22 +1100 (EST)
Received: from fw.serc.rmit.edu.au (fw-in.serc.rmit.edu.au [131.170.42.1])
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) with ESMTP id OAA12542
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 14:39:22 +1100 (EST)
Received: (from mail@localhost)
	by fw.serc.rmit.edu.au (8.9.3/8.9.1) id OAA59684
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 14:46:36 +1100 (EST)
Received: from s2.itd.nrl.navy.mil(132.250.83.3) by fw.serc.rmit.edu.au via smap (V2.1)
	id xma059682; Tue, 13 Feb 01 14:46:08 +1100
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id VAA13445
	for manet-outgoing; Mon, 12 Feb 2001 21:08:58 -0500 (EST)
Received: from universe.serc.rmit.edu.au (universe.serc.rmit.edu.au [131.170.42.12])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id VAA13440
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 21:08:55 -0500 (EST)
Received: (from null@localhost)
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) id NAA12260;
	Tue, 13 Feb 2001 13:08:51 +1100 (EST)
Received: from fw.serc.rmit.edu.au (fw-in.serc.rmit.edu.au [131.170.42.1])
	by universe.serc.rmit.edu.au (8.9.1b+Sun/8.9.1) with ESMTP id NAA12253
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 13:08:50 +1100 (EST)
Received: (from mail@localhost)
	by fw.serc.rmit.edu.au (8.9.3/8.9.1) id NAA59529
	for <rsewell@serc.rmit.edu.au>; Tue, 13 Feb 2001 13:16:04 +1100 (EST)
Received: from s2.itd.nrl.navy.mil(132.250.83.3) by fw.serc.rmit.edu.au via smap (V2.1)
	id xma059527; Tue, 13 Feb 01 13:15:58 +1100
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id SAA10834
	for manet-outgoing; Mon, 12 Feb 2001 18:32:47 -0500 (EST)
Received: from pomo.cse.ucsc.edu (pomo.cse.ucsc.edu [128.114.49.67])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with SMTP id SAA10829
	for <manet@itd.nrl.navy.mil>; Mon, 12 Feb 2001 18:32:45 -0500 (EST)
Received: (from katia@localhost) by pomo.cse.ucsc.edu (8.6.10/8.6.12) id PAA04218; Mon, 12 Feb 2001 15:32:44 -0800
Date: Mon, 12 Feb 2001 15:32:44 -0800
Message-Id: <200102122332.PAA04218@pomo.cse.ucsc.edu>
From: Katia Obraczka <katia@cse.ucsc.edu>
To: manet@itd.nrl.navy.mil
Subject: Global Internet 2001
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Your mail
     Global Internet 2001
to 
     manet@itd.nrl.navy.mil
has encountered a delivery problem.

The user has not left a forwarding address.
Your message has *not* been delivered.

SERC Autoresponder




Your mail
     Global Internet 2001
to 
     manet@itd.nrl.navy.mil
has encountered a delivery problem.

The user has not left a forwarding address.
Your message has *not* been delivered.

SERC Autoresponder




Your mail
     Global Internet 2001
to 
     manet@itd.nrl.navy.mil
has encountered a delivery problem.

The user has not left a forwarding address.
Your message has *not* been delivered.

SERC Autoresponder





                       Sixth Global Internet Symposium
                             in conjunction with

                                Globecom 2001
                           San Antonio, Texas, USA
                            November 25-29, 2001

                       http://www.cs.ucsb.edu/gi2001/
  ------------------------------------------------------------------------

                              Call For Papers

The sixth Global Internet Symposium will be held simultaneously and
co-located with Globecom 2001. Therefore, all of the relevant dates,
location, travel information are derived from the Globecom 2001
(http://www.globecom2001.com/) conference site.

Symposium Topics

Global Internet 2000 solicits technical papers on Internet-related topics.
The Program Committee encourages papers submitted on experimental systems
and emerging technologies. Also encouraged are original submissions
describing promising work in progress, original speculations about the
future of the Internet, and progressive position papers. Topics of interest
include, but are not limited to:

   * Novel applications and new paradigms (telephony, streaming media, etc.)
   * Distributed Internet applications (file sharing, games, conferencing,
     etc.)
   * Service provisioning, monitoring, and management
   * Privacy and/or security issues
   * Charging and billing issues
   * Handling Internet dynamics/heterogeneity (by applications and/or the
     network)
   * Routing (unicast, multicast, anycast, etc.)
   * Traffic measurement, analysis, modeling, and visualization
   * Flow management (fairness/sharing, differentiated services, etc.)
   * The Internet and mobility/mobile devices
   * Wireless device access and Internet gateways

Important Dates

            Manuscript Submission:       March 31, 2001
            Acceptance Notification:     July 31, 2001
            Final Manuscript:            September 31, 2000

Submission Instructions

   Please see the Global Internet Symposium WWW site at:

      http://www.cs.ucsb.edu/gi2001/

Technical Program Chairs

     Kevin Almeroth, UC-Santa Barbara (almeroth@cs.ucsb.edu)
     Katia Obraczka, UC-Santa Cruz (katia@cse.ucsc.edu)

Program Committee

     To be announced.

Sponsorship

The Global Internet Symposium is sponsored by the IEEE Communications
Society InternetTC.



From owner-manet@itd.nrl.navy.mil  Tue Feb 13 10:53: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 KAA22585
	for <manet-archive@odin.ietf.org>; Tue, 13 Feb 2001 10:53:57 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id IAA17250
	for manet-outgoing; Tue, 13 Feb 2001 08:22:40 -0500 (EST)
Received: from hotmail.com (f309.law12.hotmail.com [64.4.18.184])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id IAA17236
	for <manet@itd.nrl.navy.mil>; Tue, 13 Feb 2001 08:22:36 -0500 (EST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 13 Feb 2001 03:34:07 -0800
Received: from 193.194.81.45 by lw12fd.law12.hotmail.msn.com with HTTP;	Tue, 13 Feb 2001 11:34:07 GMT
X-Originating-IP: [193.194.81.45]
From: "Abdelouahid derhab" <derhabos@hotmail.com>
To: manet@itd.nrl.navy.mil
Subject: about DSR
Date: Tue, 13 Feb 2001 12:34:07 +0100
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Message-ID: <F309azUSxvjPkQTGpao00001615@hotmail.com>
X-OriginalArrivalTime: 13 Feb 2001 11:34:07.0251 (UTC) FILETIME=[E0132E30:01C095B0]
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

in the definition of the protocol DSR you use a constant
SEND_BUFFER_TIMEOUT=30S .
does this constant mean that the data packets stay in the buffer for 30S
or it means that this time is the maximum time allowed to the data packets 
to stay in the buffer and they will be
deleted from it if the REPLY packet arrives at the source before 
SEND_BUFFER_TIMEOUT was expired. ?
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.



From owner-manet@itd.nrl.navy.mil  Tue Feb 13 19:29:47 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 TAA03170
	for <manet-archive@odin.ietf.org>; Tue, 13 Feb 2001 19:29:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id QAA10170
	for manet-outgoing; Tue, 13 Feb 2001 16:59:34 -0500 (EST)
Received: from RRMAIL01.RADIOROUTER_NT ([63.103.94.23])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id QAA10113
	for <manet@itd.nrl.navy.mil>; Tue, 13 Feb 2001 16:59:29 -0500 (EST)
Received: from jewels (scottcorson.lab.flarion.com [216.122.123.4]) by RRMAIL01.RADIOROUTER_NT with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id 1M1X1YJ3; Tue, 13 Feb 2001 16:59:27 -0500
Reply-To: <corson@flarion.com>
From: "M. Scott Corson" <corson@radiorouter.com>
To: <manet@itd.nrl.navy.mil>
Subject: MANET Agenda Requests
Date: Tue, 13 Feb 2001 17:05:29 -0500
Message-ID: <000201c09609$13c19660$047b7ad8@RadioRouterNT>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 7bit

All,

Please send requests for MANET presentation slots to me.

Thanks,

Scott



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:39:27 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 NAA10945
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:39:26 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:42: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 SMTP id NAA11172
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:42:05 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08738
	for manet-outgoing; Wed, 14 Feb 2001 12:10:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:43:29 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 NAA11255
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:43:29 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:48: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 NAA11998
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:48:05 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:50:16 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 NAA12242
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:50:14 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:51:59 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 NAA12334
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:51:58 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:52:40 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 NAA12355
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:52:39 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:53: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 NAA12380
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:53:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:54: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 NAA12442
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:54:18 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:54:52 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 NAA12469
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:54:51 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09371
	for manet-outgoing; Wed, 14 Feb 2001 12:21:50 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09248
	for manet-outgoing; Wed, 14 Feb 2001 12:20:10 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09093
	for manet-outgoing; Wed, 14 Feb 2001 12:17:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08957
	for manet-outgoing; Wed, 14 Feb 2001 12:15:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08883
	for manet-outgoing; Wed, 14 Feb 2001 12:13:56 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08819
	for manet-outgoing; Wed, 14 Feb 2001 12:12:20 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08738
	for manet-outgoing; Wed, 14 Feb 2001 12:10:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:56:28 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 NAA12535
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:56:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:57: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 NAA12604
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:57:06 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08819
	for manet-outgoing; Wed, 14 Feb 2001 12:12:20 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08738
	for manet-outgoing; Wed, 14 Feb 2001 12:10:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:57: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 NAA12617
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:57:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:57:30 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 NAA12640
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:57:29 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 13:58: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 NAA12732
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 13:58:33 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08883
	for manet-outgoing; Wed, 14 Feb 2001 12:13:56 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08819
	for manet-outgoing; Wed, 14 Feb 2001 12:12:20 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08738
	for manet-outgoing; Wed, 14 Feb 2001 12:10:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 14:04:05 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 OAA13013
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 14:04:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 14:10:46 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 OAA13335
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 14:10:46 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 14:11: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 OAA13365
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 14:11:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09248
	for manet-outgoing; Wed, 14 Feb 2001 12:20:10 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09093
	for manet-outgoing; Wed, 14 Feb 2001 12:17:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08957
	for manet-outgoing; Wed, 14 Feb 2001 12:15:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08883
	for manet-outgoing; Wed, 14 Feb 2001 12:13:56 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08819
	for manet-outgoing; Wed, 14 Feb 2001 12:12:20 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08738
	for manet-outgoing; Wed, 14 Feb 2001 12:10:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 14:14: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 OAA13509
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 14:14:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09631
	for manet-outgoing; Wed, 14 Feb 2001 12:24:57 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09523
	for manet-outgoing; Wed, 14 Feb 2001 12:23:26 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09371
	for manet-outgoing; Wed, 14 Feb 2001 12:21:50 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09248
	for manet-outgoing; Wed, 14 Feb 2001 12:20:10 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09093
	for manet-outgoing; Wed, 14 Feb 2001 12:17:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08957
	for manet-outgoing; Wed, 14 Feb 2001 12:15:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08883
	for manet-outgoing; Wed, 14 Feb 2001 12:13:56 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08819
	for manet-outgoing; Wed, 14 Feb 2001 12:12:20 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08738
	for manet-outgoing; Wed, 14 Feb 2001 12:10:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 14:31:05 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 OAA14069
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 14:31:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08957
	for manet-outgoing; Wed, 14 Feb 2001 12:15:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08883
	for manet-outgoing; Wed, 14 Feb 2001 12:13:56 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08819
	for manet-outgoing; Wed, 14 Feb 2001 12:12:20 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08738
	for manet-outgoing; Wed, 14 Feb 2001 12:10:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 14:38: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 OAA14402
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 14:38:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09523
	for manet-outgoing; Wed, 14 Feb 2001 12:23:26 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09371
	for manet-outgoing; Wed, 14 Feb 2001 12:21:50 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09248
	for manet-outgoing; Wed, 14 Feb 2001 12:20:10 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09093
	for manet-outgoing; Wed, 14 Feb 2001 12:17:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08957
	for manet-outgoing; Wed, 14 Feb 2001 12:15:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08883
	for manet-outgoing; Wed, 14 Feb 2001 12:13:56 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08819
	for manet-outgoing; Wed, 14 Feb 2001 12:12:20 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08738
	for manet-outgoing; Wed, 14 Feb 2001 12:10:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 14:38: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 OAA14403
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 14:38:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09093
	for manet-outgoing; Wed, 14 Feb 2001 12:17:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08957
	for manet-outgoing; Wed, 14 Feb 2001 12:15:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08883
	for manet-outgoing; Wed, 14 Feb 2001 12:13:56 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08819
	for manet-outgoing; Wed, 14 Feb 2001 12:12:20 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08738
	for manet-outgoing; Wed, 14 Feb 2001 12:10:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 14:38:46 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 OAA14431
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 14:38:45 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09810
	for manet-outgoing; Wed, 14 Feb 2001 12:26:33 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09631
	for manet-outgoing; Wed, 14 Feb 2001 12:24:57 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09523
	for manet-outgoing; Wed, 14 Feb 2001 12:23:26 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09371
	for manet-outgoing; Wed, 14 Feb 2001 12:21:50 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09248
	for manet-outgoing; Wed, 14 Feb 2001 12:20:10 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA09093
	for manet-outgoing; Wed, 14 Feb 2001 12:17:19 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08957
	for manet-outgoing; Wed, 14 Feb 2001 12:15:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08883
	for manet-outgoing; Wed, 14 Feb 2001 12:13:56 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08819
	for manet-outgoing; Wed, 14 Feb 2001 12:12:20 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08738
	for manet-outgoing; Wed, 14 Feb 2001 12:10:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08642
	for manet-outgoing; Wed, 14 Feb 2001 12:08:36 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08567
	for manet-outgoing; Wed, 14 Feb 2001 12:07:04 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08467
	for manet-outgoing; Wed, 14 Feb 2001 12:05:17 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08407
	for manet-outgoing; Wed, 14 Feb 2001 12:03:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08346
	for manet-outgoing; Wed, 14 Feb 2001 12:02:16 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA08215
	for manet-outgoing; Wed, 14 Feb 2001 12:00:47 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08115
	for manet-outgoing; Wed, 14 Feb 2001 11:59:15 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA08039
	for manet-outgoing; Wed, 14 Feb 2001 11:57:43 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07967
	for manet-outgoing; Wed, 14 Feb 2001 11:56:08 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07898
	for manet-outgoing; Wed, 14 Feb 2001 11:54:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07826
	for manet-outgoing; Wed, 14 Feb 2001 11:53:03 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07763
	for manet-outgoing; Wed, 14 Feb 2001 11:50:54 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07309
	for manet-outgoing; Wed, 14 Feb 2001 11:39:44 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA07296;
	Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Date: Wed, 14 Feb 2001 11:39:43 -0500 (EST)
Message-Id: <200102141639.LAA07296@itd.nrl.navy.mil>
To: manet@itd.nrl.navy.mil
From: Majordomo@itd.nrl.navy.mil
Subject: Welcome to manet
Reply-To: Majordomo@itd.nrl.navy.mil
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

--

Welcome to the manet mailing list!

If you ever want to remove yourself from this mailing list,
send the following command in email to
"manet-request@itd.nrl.navy.mil":

    unsubscribe

Or you can send mail to "Majordomo@itd.nrl.navy.mil" with the following command
in the body of your email message:

    unsubscribe manet manet@itd.nrl.navy.mil

Here's the general information for the list you've
subscribed to, in case you don't already have it:

To subscribe, send your request to majordomo@itd.nrl.navy.mil and 
include as your message content subscribe manet.

Submissions intended for the list should go to manet@itd.nrl.navy.mil.

If you encounter problems with the mailing list, please contact Joe Macker
@ 202-767-2001 or e-mail macker@itd.nrl.navy.mil.



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 20:10: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 UAA20040
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 20:10:38 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id SAA09114
	for manet-outgoing; Wed, 14 Feb 2001 18:28:16 -0500 (EST)
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 SAA09109
	for <manet@itd.nrl.navy.mil>; Wed, 14 Feb 2001 18:28:15 -0500 (EST)
Message-Id: <5.0.1.4.2.20010214175447.02c6b008@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 14 Feb 2001 18:29:01 -0500
To: manet@itd.nrl.navy.mil
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: List Looping Issue
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

All:

The recent welcome message looping was a subscription policy weakness that 
was abused.  We will shortly be reconfiguring to avoid this in the future. 
Don't panic.

-Joe



From owner-manet@itd.nrl.navy.mil  Wed Feb 14 23:50:59 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 XAA25426
	for <manet-archive@odin.ietf.org>; Wed, 14 Feb 2001 23:50:58 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id UAA12779
	for manet-outgoing; Wed, 14 Feb 2001 20:52:41 -0500 (EST)
Received: from barrichello.cs.ucr.edu (barrichello.cs.ucr.edu [138.23.169.5])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id UAA12774
	for <manet@itd.nrl.navy.mil>; Wed, 14 Feb 2001 20:52:40 -0500 (EST)
Received: by barrichello.cs.ucr.edu (Postfix, from userid 2)
	id D500F14EE5; Wed, 14 Feb 2001 17:52:40 -0800 (PST)
Received: from jupiter.cs.ucr.edu (jupiter.cs.ucr.edu [138.23.174.175])
	by barrichello.cs.ucr.edu (Postfix) with ESMTP id 777B9173F8
	for <manet@itd.nrl.navy.mil>; Wed, 14 Feb 2001 17:52:35 -0800 (PST)
Received: from localhost (msamidi@localhost)
	by jupiter.cs.ucr.edu (8.9.3/8.8.8) with ESMTP id RAA01003
	for <manet@itd.nrl.navy.mil>; Wed, 14 Feb 2001 17:52:35 -0800
X-Authentication-Warning: jupiter.cs.ucr.edu: msamidi owned process doing -bs
Date: Wed, 14 Feb 2001 17:52:35 -0800 (PST)
From: Michael Samidi <msamidi@cs.ucr.edu>
To: manet@itd.nrl.navy.mil
Subject: IP within IP
Message-ID: <Pine.LNX.4.10.10102141747480.986-100000@jupiter.cs.ucr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AntiVirus: scanned for viruses by AMaViS perl-6
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk


Hello all,

I am new to mobile IP area. I am working on a project that tries to use IP
within IP. Basically, we create raw socket that follows RFC2003 spec.

However, when I send the IPIP packet from our machine back to our machine
through  any backbone router in the Internet that we believe supports
RFC2003, we do not receive the packet back. 

Is anyone knows how to find out whether or not any router supports
RFC2003?

Any pointer will be helpful. Thank you very much.

Regards,
Michael

************************************************************************
   Michael Samidi                              Office: (909) 787-2784
   Graduate Student (MS Program)                 Home: (909) 786-9792
   Computer Science Dept.              http://www.cs.ucr.edu/~msamidi
   University of California
   Riverside, CA 92521
************************************************************************



From owner-manet@itd.nrl.navy.mil  Fri Feb 16 05:05: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 SMTP id FAA25732
	for <manet-archive@odin.ietf.org>; Fri, 16 Feb 2001 05:05:05 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id CAA28306
	for manet-outgoing; Fri, 16 Feb 2001 02:25:59 -0500 (EST)
Received: from maredsous.cs.rice.edu (maredsous.cs.rice.edu [128.42.1.54])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id CAA28301
	for <manet@itd.nrl.navy.mil>; Fri, 16 Feb 2001 02:25:56 -0500 (EST)
Received: (from dbj@localhost)
        by maredsous.cs.rice.edu id BAA16848;
        Fri, 16 Feb 2001 01:26:53 -0600 (CST)
Date: Fri, 16 Feb 2001 01:26:53 -0600
From: Dave Johnson <dbj@cs.rice.edu>
To: Abdelouahid derhab <derhabos@hotmail.com>
Cc: manet@itd.nrl.navy.mil
Subject: Re: about DSR
Message-ID: <20010216012653.B16809@maredsous.cs.rice.edu>
Reply-To: Dave Johnson <dbj@cs.rice.edu>
References: <F309azUSxvjPkQTGpao00001615@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <F309azUSxvjPkQTGpao00001615@hotmail.com>; from derhabos@hotmail.com on Tue, 13 Feb 2001 12:34:07PM +0100
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Abdelouahid derhab said:
> in the definition of the protocol DSR you use a constant
> SEND_BUFFER_TIMEOUT=30S .
> does this constant mean that the data packets stay in the buffer for 30S
> or it means that this time is the maximum time allowed to the data packets 
> to stay in the buffer and they will be
> deleted from it if the REPLY packet arrives at the source before 
> SEND_BUFFER_TIMEOUT was expired. ?
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.


This is the maximum lifetime that a packet can stay in the Send Buffer
before it must be deleted.  If a route to the destination becomes
available before that, the message is transmitted and removed from the
Send Buffer, too.

					Dave


From owner-manet@itd.nrl.navy.mil  Fri Feb 16 15:49:31 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 PAA09186
	for <manet-archive@odin.ietf.org>; Fri, 16 Feb 2001 15:49:30 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA16083
	for manet-outgoing; Fri, 16 Feb 2001 12:55:13 -0500 (EST)
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 MAA16078
	for <manet@itd.nrl.navy.mil>; Fri, 16 Feb 2001 12:55:10 -0500 (EST)
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 JAA02702;
	Fri, 16 Feb 2001 09:55:10 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id f1GHt7t00542;
	Fri, 16 Feb 2001 09:55:07 -0800
X-mProtect:  Fri, 16 Feb 2001 09:55:07 -0800 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(WTS.12.69) smtpdBv1y3y; Fri, 16 Feb 2001 09:54:06 PST
Message-ID: <3A8D693F.93D0001A@iprg.nokia.com>
Date: Fri, 16 Feb 2001 09:54:07 -0800
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: Phil_Neumiller@3com.com
CC: seamoby-mm@cdma-2000.org,
        Mobile Ad Hoc IETF working group <manet@itd.nrl.navy.mil>
Subject: Re: [seamoby-mm] Ad hoc scnenarios paragraph
References: <Roam.SIMC.2.0.6.982343737.21468.pcalhoun@nasnfs>
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 Phil,

I reckon that AODV and DSR will go to consideration by
the IESG before much longer.  The likely designation
will be Experimental Standard, at least until we get more
deployment experience.

So, I don't agree with your assessment.

Regarding the idea of competition, you are right.  But
consider, for instance, the result of 40 working groups
doing micromobility, or security, or QoS.  You'll have
a lot of "not invented here" and reduplication of finding
all the same mistakes.

It might be feasible to find out where possibilities exist
for cooperation.  Would you volunteer to raise the discussion
on the [manet] list -- most people probably don't remember
your notes from a year ago, and maybe it's time to bring the
subject up again?  That would be better than the direction
of ignoring the work or, as it seems to me, mischaracterizing
it to a certain extent.

Anyway, I truly like the idea of introducing ad hoc
networking into local mobility scenarios.  I wrote
up a sort-of similar idea about community-based ad hoc
networking tied in with regionalized Internet access.
It might have the effect of bringing the Internet back
home where it belongs.

I've cross-posted this to the [manet] list, because it seems
to me like a discussion that ought be heard there.  I hope
that's O.K.

Regards,
Charlie P.


Pat Calhoun wrote:
> 
> > We discussed this at length at the last MM meting.  You were not present.
> > Yes we do want to
> > include it.  I have posted to MANET, and they will not be providing a
> > "STANDARD" ad hoc
> > mechanism for a "LONG TIME".
> 
> ... and opening up that can of worms will bring in all the MANET guys, with
> their various proposals, and slow us down as well (I doubt that we could do it
> faster than they could).
> 
> PatC


From owner-manet@itd.nrl.navy.mil  Mon Feb 19 02:17:10 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 CAA29967
	for <manet-archive@odin.ietf.org>; Mon, 19 Feb 2001 02:17:10 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id XAA01820
	for manet-outgoing; Sun, 18 Feb 2001 23:36:22 -0500 (EST)
Received: from acr.acr.atr.co.jp (acr.atr.co.jp [133.186.50.1])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id XAA01815
	for <manet@itd.nrl.navy.mil>; Sun, 18 Feb 2001 23:36:14 -0500 (EST)
Received: from rpc41 by acr.acr.atr.co.jp (8.9.3+3.2W/3.7W)
	id NAA25084; Mon, 19 Feb 2001 13:36:06 +0900 (JST)
From: "Shingo Horisawa" <horisawa@acr.atr.co.jp>
To: <manet@itd.nrl.navy.mil>
Subject: About MAC using RTS/CTS
Date: Mon, 19 Feb 2001 13:38:43 +0900
Message-ID: <NEBBILNNMKPNKELCBCJOMEBBCDAA.horisawa@acr.atr.co.jp>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi, all.

I have a question about MAC using RTS/CTS.

In the following figure, B sends RTS whose target is C
to neighbor nodes, then A and C, which are neighbor of B, 
receive the RTS. Since A isn't  the target of the RTS,
A enters NAV(RTS) period. The other side, since C is the target
of the RTS, C sends CTS to neighbors. D which receives 
the CTS enter NAV(CTS) period, and B can send data to C. 

  A     B     C     D     E
  | RTS | RTS |     |     |  
  |<----|---->|     |     |  
  *     | CTS | CTS |     |  
  *     |<----|---->|     |  
  *     |     |     * RTS | RTS
  *<----|---->|     *<----|---->  
  *<-D--|--D->|     *  .  |  .
  *<-A--|--A->|     *  .  |  .
  *<-T--|--T->|     *  .  |  .
  *<-A--|--A->|     *     |  
  *<----|---->|     * RTS | RTS 
  *     | ACK | ACK *<----|---->
  *     |<----|---->*     |  
  |     |     |     |     |  
  |     |     |     |     |  

At this point, if the other node E sends RTS to D when E wants to
send DATA to D, since D can't reply to the RTS, E resend RTS to 
the number of times of the maximum retry limit.
If the NAV period of D is long enough, E's retry limit may reach to 
maximum before D's NAV period end.

In this case, is the DATA packet which E wants to send to D dropped?
If so, I think many packets may be dropped when there are a certain 
amount of traffic because congestion occurs in forwarding node. 

Is this true?


Regards.

--  Shingo Horisawa



From owner-manet@itd.nrl.navy.mil  Mon Feb 19 13:17:10 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 NAA10852
	for <manet-archive@odin.ietf.org>; Mon, 19 Feb 2001 13:17:09 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id KAA09997
	for manet-outgoing; Mon, 19 Feb 2001 10:34:37 -0500 (EST)
Received: from blackie.cruzers.com (cruzers.com [205.215.232.2])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id KAA09992
	for <manet@itd.nrl.navy.mil>; Mon, 19 Feb 2001 10:34:35 -0500 (EST)
Received: from mvpcpentile.cse.ucsc.edu (stanley-29.cruzers.com [209.165.194.29])
	by blackie.cruzers.com (8.8.7/8.8.5) with ESMTP id HAA25953;
	Mon, 19 Feb 2001 07:35:24 -0800 (PST)
Message-Id: <5.0.2.1.0.20010219071710.0194a260@mail.cruzers.com>
X-Sender: chane@mail.cruzers.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 19 Feb 2001 07:35:49 -0800
To: "Shingo Horisawa" <horisawa@acr.atr.co.jp>, <manet@itd.nrl.navy.mil>
From: "Dr. Obscure" <chane@cse.ucsc.edu>
Subject: Re: About MAC using RTS/CTS
In-Reply-To: <NEBBILNNMKPNKELCBCJOMEBBCDAA.horisawa@acr.atr.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

At 01:38 PM 2/19/01 +0900, Shingo Horisawa wrote:
>At this point, if the other node E sends RTS to D when E wants to
>send DATA to D, since D can't reply to the RTS, E resend RTS to
>the number of times of the maximum retry limit.
>If the NAV period of D is long enough, E's retry limit may reach to
>maximum before D's NAV period end.
>
>In this case, is the DATA packet which E wants to send to D dropped?
>If so, I think many packets may be dropped when there are a certain
>amount of traffic because congestion occurs in forwarding node.

Shingo, what you suggest is certainly plausible in a multihop wireless 
network, and the protocol designer/implementor must consider congestion and 
fairness  to mitigate the situation you reference.  Generally, (in random 
access protocols) the solution has been to increase back off times when 
packets are dropped (or RTSs go unanswered) to account for 
congestion.  (unfortunately, fading and congestion look a lot alike and 
what is good for one is not necessarily good for the other, but that's a 
different discussion :)  Of course, as with any random access protocol 
excessive traffic can bring the network to it's knees to the point little 
or no real data traffic gets through...

--chane



From owner-manet@itd.nrl.navy.mil  Mon Feb 19 16:39:31 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 QAA15357
	for <manet-archive@odin.ietf.org>; Mon, 19 Feb 2001 16:39:31 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id OAA14753
	for manet-outgoing; Mon, 19 Feb 2001 14:04:46 -0500 (EST)
Received: from cs.tamu.edu (clavin.cs.tamu.edu [128.194.130.106])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id OAA14748
	for <manet@itd.nrl.navy.mil>; Mon, 19 Feb 2001 14:04:43 -0500 (EST)
Received: from robert.cs.tamu.edu (IDENT:8997@robert [128.194.130.200])
	by cs.tamu.edu (8.11.0/8.11.0) with ESMTP id f1JJ4if26185
	for <manet@itd.nrl.navy.mil>; Mon, 19 Feb 2001 13:04:44 -0600 (CST)
Received: from localhost (jchen@localhost)
	by robert.cs.tamu.edu (8.11.0/8.11.0) with ESMTP id f1JJ4ig08665
	for <manet@itd.nrl.navy.mil>; Mon, 19 Feb 2001 13:04:44 -0600 (CST)
X-Authentication-Warning: robert.cs.tamu.edu: jchen owned process doing -bs
Date: Mon, 19 Feb 2001 13:04:43 -0600 (CST)
From: Jian - Chen <jchen@cs.tamu.edu>
X-Sender: jchen@robert
To: manet@itd.nrl.navy.mil
Subject: hi
Message-ID: <Pine.SOL.4.10.10102191301100.8471-100000@robert>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi,
could you recommend me some good papers about "QoS in mobile ad hoc"?
I can't find papers published last year in this field? 

Thank you very much

Jian  



From owner-manet@itd.nrl.navy.mil  Tue Feb 20 05:40: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 FAA09735
	for <manet-archive@odin.ietf.org>; Tue, 20 Feb 2001 05:40:18 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id DAA26290
	for manet-outgoing; Tue, 20 Feb 2001 03:12:04 -0500 (EST)
Received: from samar.sasi.com (samar.sasken.com [164.164.56.2])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id DAA26285
	for <manet@itd.nrl.navy.mil>; Tue, 20 Feb 2001 03:11:57 -0500 (EST)
Received: from samar (samar.sasi.com [164.164.56.2])
	by samar.sasi.com (8.9.3/8.9.3) with SMTP id NAB10032;
	Tue, 20 Feb 2001 13:41:48 +0530 (IST)
Received: from sunc5.sasi.com ([10.0.32.5]) by samar.sasi.com; Tue, 20 Feb 2001 13:41:46 +0000 (IST)
Received: from localhost (kishore@localhost)
	by sunc5.sasi.com (8.9.3/8.9.3) with ESMTP id NAA12850;
	Tue, 20 Feb 2001 13:41:46 +0530 (IST)
Date: Tue, 20 Feb 2001 13:41:46 +0530 (IST)
From: Krishna Kishore K R <kishore@sasken.com>
To: Jian - Chen <jchen@cs.tamu.edu>
cc: <manet@itd.nrl.navy.mil>
Subject: Re: hi
In-Reply-To: <Pine.SOL.4.10.10102191301100.8471-100000@robert>
Message-ID: <Pine.GSO.4.30.0102201339290.12493-100000@sunc5.sasi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi,
  I don't think any work has been done in the area of QoS in Ad
  hoc networks. At present, routing issue is being emphasized
  on.

regards,
Kishore.

On Mon, 19 Feb 2001, Jian - Chen wrote:

> Hi,
> could you recommend me some good papers about "QoS in mobile ad hoc"?
> I can't find papers published last year in this field?
>
> Thank you very much
>
> Jian
>



From owner-manet@itd.nrl.navy.mil  Tue Feb 20 05:57:30 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 FAA09920
	for <manet-archive@odin.ietf.org>; Tue, 20 Feb 2001 05:57:30 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id EAA26986
	for manet-outgoing; Tue, 20 Feb 2001 04:04:22 -0500 (EST)
Received: from m018.com ([210.112.11.138])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id EAA26980
	for <manet@itd.nrl.navy.mil>; Tue, 20 Feb 2001 04:04:19 -0500 (EST)
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Tue, 20 Feb 2001 17:57:57 +0900
Received: from itd.nrl.navy.mil ([132.250.83.3]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Tue, 20 Feb 2001 05:50:54 +0900
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id OAA14753
	for manet-outgoing; Mon, 19 Feb 2001 14:04:46 -0500 (EST)
Received: from cs.tamu.edu (clavin.cs.tamu.edu [128.194.130.106])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id OAA14748
	for <manet@itd.nrl.navy.mil>; Mon, 19 Feb 2001 14:04:43 -0500 (EST)
Received: from robert.cs.tamu.edu (IDENT:8997@robert [128.194.130.200])
	by cs.tamu.edu (8.11.0/8.11.0) with ESMTP id f1JJ4if26185
	for <manet@itd.nrl.navy.mil>; Mon, 19 Feb 2001 13:04:44 -0600 (CST)
Received: from localhost (jchen@localhost)
	by robert.cs.tamu.edu (8.11.0/8.11.0) with ESMTP id f1JJ4ig08665
	for <manet@itd.nrl.navy.mil>; Mon, 19 Feb 2001 13:04:44 -0600 (CST)
X-Authentication-Warning: robert.cs.tamu.edu: jchen owned process doing -bs
Date: Mon, 19 Feb 2001 13:04:43 -0600 (CST)
From: Jian - Chen <jchen@cs.tamu.edu>
X-Sender: jchen@robert
To: manet@itd.nrl.navy.mil
Subject: hi
Message-ID: <Pine.SOL.4.10.10102191301100.8471-100000@robert>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi,
could you recommend me some good papers about "QoS in mobile ad hoc"?
I can't find papers published last year in this field? 

Thank you very much

Jian  


From owner-manet@itd.nrl.navy.mil  Tue Feb 20 05:57: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 FAA09931
	for <manet-archive@odin.ietf.org>; Tue, 20 Feb 2001 05:57:35 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id EAA26916
	for manet-outgoing; Tue, 20 Feb 2001 04:00:52 -0500 (EST)
Received: from m018.com ([210.112.11.138])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id EAA26911
	for <manet@itd.nrl.navy.mil>; Tue, 20 Feb 2001 04:00:49 -0500 (EST)
Received: from mail pickup service by m018.com with Microsoft SMTPSVC;
	 Tue, 20 Feb 2001 17:54:09 +0900
Received: from itd.nrl.navy.mil ([132.250.83.3]) by m018.com  with Microsoft SMTPSVC(5.5.1877.197.19);
	 Tue, 20 Feb 2001 02:38:08 +0900
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id KAA09997
	for manet-outgoing; Mon, 19 Feb 2001 10:34:37 -0500 (EST)
Received: from blackie.cruzers.com (cruzers.com [205.215.232.2])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id KAA09992
	for <manet@itd.nrl.navy.mil>; Mon, 19 Feb 2001 10:34:35 -0500 (EST)
Received: from mvpcpentile.cse.ucsc.edu (stanley-29.cruzers.com [209.165.194.29])
	by blackie.cruzers.com (8.8.7/8.8.5) with ESMTP id HAA25953;
	Mon, 19 Feb 2001 07:35:24 -0800 (PST)
Message-Id: <5.0.2.1.0.20010219071710.0194a260@mail.cruzers.com>
X-Sender: chane@mail.cruzers.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Mon, 19 Feb 2001 07:35:49 -0800
To: "Shingo Horisawa" <horisawa@acr.atr.co.jp>, <manet@itd.nrl.navy.mil>
From: "Dr. Obscure" <chane@cse.ucsc.edu>
Subject: Re: About MAC using RTS/CTS
In-Reply-To: <NEBBILNNMKPNKELCBCJOMEBBCDAA.horisawa@acr.atr.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

At 01:38 PM 2/19/01 +0900, Shingo Horisawa wrote:
>At this point, if the other node E sends RTS to D when E wants to
>send DATA to D, since D can't reply to the RTS, E resend RTS to
>the number of times of the maximum retry limit.
>If the NAV period of D is long enough, E's retry limit may reach to
>maximum before D's NAV period end.
>
>In this case, is the DATA packet which E wants to send to D dropped?
>If so, I think many packets may be dropped when there are a certain
>amount of traffic because congestion occurs in forwarding node.

Shingo, what you suggest is certainly plausible in a multihop wireless 
network, and the protocol designer/implementor must consider congestion and 
fairness  to mitigate the situation you reference.  Generally, (in random 
access protocols) the solution has been to increase back off times when 
packets are dropped (or RTSs go unanswered) to account for 
congestion.  (unfortunately, fading and congestion look a lot alike and 
what is good for one is not necessarily good for the other, but that's a 
different discussion :)  Of course, as with any random access protocol 
excessive traffic can bring the network to it's knees to the point little 
or no real data traffic gets through...

--chane


From owner-manet@itd.nrl.navy.mil  Tue Feb 20 07:59: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 HAA11332
	for <manet-archive@odin.ietf.org>; Tue, 20 Feb 2001 07:59:37 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id FAA28761
	for manet-outgoing; Tue, 20 Feb 2001 05:47:36 -0500 (EST)
Received: from malonne.lifl.fr (malonne.lifl.fr [134.206.10.29])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id FAA28756
	for <manet@itd.nrl.navy.mil>; Tue, 20 Feb 2001 05:47:33 -0500 (EST)
Received: from lifl.lifl.fr (lifl.lifl.fr [134.206.10.18])
          by malonne.lifl.fr (8.9.3/jtpda-5.3.3) with ESMTP id LAA23434
          ; Tue, 20 Feb 2001 11:46:04 +0100 (MET)
Received: from chimay.lifl.fr (mail@chimay [134.206.11.15])
          by lifl.lifl.fr (8.9.3/jtpda-5.3.3) with ESMTP id LAA21424
          ; Tue, 20 Feb 2001 11:47:40 +0100 (MET)
Received: from cartigny (helo=localhost)
	by chimay.lifl.fr with local-esmtp (Exim 3.12 #1 (Debian))
	id 14VAJP-00012Y-00; Tue, 20 Feb 2001 11:46:27 +0100
Date: Tue, 20 Feb 2001 11:46:27 +0100 (CET)
From: "Julien.Cartigny" <Julien.Cartigny@lifl.fr>
To: Krishna Kishore K R <kishore@sasken.com>
cc: Jian - Chen <jchen@cs.tamu.edu>, manet@itd.nrl.navy.mil
Subject: Re: hi
In-Reply-To: <Pine.GSO.4.30.0102201339290.12493-100000@sunc5.sasi.com>
Message-ID: <Pine.LNX.4.21.0102201140460.3931-100000@chimay.lifl.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk


"QoS Support in Mobile Ad Hoc Networks" by Kui Wu and Janelle Harms from
the Computing Science Departement of the university of Alberta. Sorry, no
bibliography or download location, I can't remember myself where i found
this paper.

Other papers:

 - "QoS routing performance in a multi-hop, wireless networks"
     Tsu-Wei Chen, Mario Gerla and Jack Tzu-Chieh Tsai
     In Proceedings of ICUPC '97.


------------------------------------------------------------------
CARTIGNY Julien 
These d'informatique dans l'equipe RD2P  a l'universite de Lille 1 
(Phd of Computer Science at the University of Lille 1 / France)
 
"Sometimes when reading Goethe I have the paralyzing suspicion that he is trying to be funny." - Guy Davenport

On Tue, 20 Feb 2001, Krishna Kishore K R wrote:

> Hi,
>   I don't think any work has been done in the area of QoS in Ad
>   hoc networks. At present, routing issue is being emphasized
>   on.
> 
> regards,
> Kishore.
> 
> On Mon, 19 Feb 2001, Jian - Chen wrote:
> 
> > Hi,
> > could you recommend me some good papers about "QoS in mobile ad hoc"?
> > I can't find papers published last year in this field?
> >
> > Thank you very much
> >
> > Jian
> >
> 



From owner-manet@itd.nrl.navy.mil  Tue Feb 20 10:31:33 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 KAA13992
	for <manet-archive@odin.ietf.org>; Tue, 20 Feb 2001 10:31:32 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id HAA01420
	for manet-outgoing; Tue, 20 Feb 2001 07:57:39 -0500 (EST)
Received: from mail.cse.iitk.ac.in ([210.212.54.4])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id HAA01409
	for <manet@itd.nrl.navy.mil>; Tue, 20 Feb 2001 07:57:34 -0500 (EST)
Received: from cseultra2.cse.iitk.ac.in (cseultra2 [172.31.16.2])
	by mail.cse.iitk.ac.in (8.9.3/8.9.3) with ESMTP id SAA20867;
	Tue, 20 Feb 2001 18:26:40 +0530
Received: from csews12.cse.iitk.ac.in (IDENT:strip@csews12.cse.iitk.ac.in [172.31.18.12])
	by cseultra2.cse.iitk.ac.in (8.10.1/8.10.1) with ESMTP id f1KComJ08207;
	Tue, 20 Feb 2001 18:20:48 +0530 (IST)
Date: Thu, 6 Feb 1997 03:22:18 +0530 (IST)
From: Shailendra Tripathi <strip@cse.iitk.ac.in>
To: "Julien.Cartigny" <Julien.Cartigny@lifl.fr>
cc: Krishna Kishore K R <kishore@sasken.com>, Jian - Chen <jchen@cs.tamu.edu>,
        manet@itd.nrl.navy.mil
Subject: Re: hi
In-Reply-To: <Pine.LNX.4.21.0102201140460.3931-100000@chimay.lifl.fr>
Message-ID: <Pine.LNX.4.04.9702060304510.16746-100000@csews12.cse.iitk.ac.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk



	One draft related with QoS in mobile Ad hoc networks(over AODV) 
by Perkins, Royer & Samir R Das had been published in the past.
	Its name is 
	  draft-ietf-manet-aodvqos-00.txt. 
	It is now expired but the new draft is not available at the site.
In earlier versions of AODV drafts it has been discussed in the same
drafts. Even I have this draft available with me. Concerned people may
tell you more.
	Besides it, one paper by Shigang Chen and Klara Nahrstedt,
Distributed Quality-Of-Service Routing in Ad Hoc Networks is available on
the net.(IEEE Journal On Selected Areas In Communications, Vol17,No8,1999)

Shailendra  
  

> 
> "QoS Support in Mobile Ad Hoc Networks" by Kui Wu and Janelle Harms from
> the Computing Science Departement of the university of Alberta. Sorry, no
> bibliography or download location, I can't remember myself where i found
> this paper.
> 
> Other papers:
> 
>  - "QoS routing performance in a multi-hop, wireless networks"
>      Tsu-Wei Chen, Mario Gerla and Jack Tzu-Chieh Tsai
>      In Proceedings of ICUPC '97.
> 
> 
> ------------------------------------------------------------------
> CARTIGNY Julien 
> These d'informatique dans l'equipe RD2P  a l'universite de Lille 1 
> (Phd of Computer Science at the University of Lille 1 / France)
>  
> "Sometimes when reading Goethe I have the paralyzing suspicion that he is trying to be funny." - Guy Davenport
> 
> On Tue, 20 Feb 2001, Krishna Kishore K R wrote:
> 
> > Hi,
> >   I don't think any work has been done in the area of QoS in Ad
> >   hoc networks. At present, routing issue is being emphasized
> >   on.
> > 
> > regards,
> > Kishore.
> > 
> > On Mon, 19 Feb 2001, Jian - Chen wrote:
> > 
> > > Hi,
> > > could you recommend me some good papers about "QoS in mobile ad hoc"?
> > > I can't find papers published last year in this field?
> > >
> > > Thank you very much
> > >
> > > Jian
> > >
> > 
> 



From owner-manet@itd.nrl.navy.mil  Tue Feb 20 12:00:28 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 MAA16445
	for <manet-archive@odin.ietf.org>; Tue, 20 Feb 2001 12:00:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id JAA03429
	for manet-outgoing; Tue, 20 Feb 2001 09:12:06 -0500 (EST)
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 JAA03421
	for <manet@itd.nrl.navy.mil>; Tue, 20 Feb 2001 09:12:03 -0500 (EST)
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 JAA21957;
	Tue, 20 Feb 2001 09:11:58 -0500 (EST)
Message-ID: <3A927B29.57367CFA@antd.nist.gov>
Date: Tue, 20 Feb 2001 09:11:53 -0500
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: Jian - Chen <jchen@cs.tamu.edu>
CC: manet@itd.nrl.navy.mil
Subject: Re: hi
References: <Pine.SOL.4.10.10102191301100.8471-100000@robert>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jian - Chen wrote:
> 
> Hi,
> could you recommend me some good papers about "QoS in mobile ad hoc"?
> I can't find papers published last year in this field?
> 
> Thank you very much
> 
> Jian

There's a good unpublished survey by Wu and Harms at
  
http://www.cs.ualberta.ca/~wkui/research/QoSReview.ps

This manuscript makes good use of a paper in the Spring 2000 proceeding
of the Vehicular Technology Conference by Hannan Xiao et al., "A
Flexible Quality of Service Model for Mobile Ad Hoc Networks."


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

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  Tue Feb 20 14:40:22 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 OAA22121
	for <manet-archive@odin.ietf.org>; Tue, 20 Feb 2001 14:40:22 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA10413
	for manet-outgoing; Tue, 20 Feb 2001 11:43:59 -0500 (EST)
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 LAA10395
	for <manet@itd.nrl.navy.mil>; Tue, 20 Feb 2001 11:43:56 -0500 (EST)
Message-Id: <5.0.1.4.2.20010220113910.032e72c8@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Tue, 20 Feb 2001 11:45:06 -0500
To: manet@itd.nrl.navy.mil
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Posting Change
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

All:

In the future, whenever possible please post from the mail address that you 
subscribed to the list from.

-Joe



From owner-manet@itd.nrl.navy.mil  Tue Feb 20 18:05:46 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 SAA28880
	for <manet-archive@odin.ietf.org>; Tue, 20 Feb 2001 18:05:45 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id PAA20271
	for manet-outgoing; Tue, 20 Feb 2001 15:23:59 -0500 (EST)
Received: from scapa.cs.ualberta.ca (scapa.cs.ualberta.ca [129.128.4.44])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id PAA20263
	for <manet@itd.nrl.navy.mil>; Tue, 20 Feb 2001 15:23:56 -0500 (EST)
Received: (from localhost user: 'wkui' uid#432 fake: STDIN
        (wkui@newsarepta.cs.ualberta.ca)) by scapa.cs.ualberta.ca
	id <S434007AbRBTUXb>; Tue, 20 Feb 2001 13:23:31 -0700
Date:   Tue, 20 Feb 2001 13:23:31 -0700 (MST)
From: Kui Wu <wkui@cs.ualberta.ca>
To: "Julien.Cartigny" <Julien.Cartigny@lifl.fr>
cc: Krishna Kishore K R <kishore@sasken.com>, Jian - Chen <jchen@cs.tamu.edu>,
        manet@itd.nrl.navy.mil
Subject: Re: hi
In-Reply-To: <Pine.LNX.4.21.0102201140460.3931-100000@chimay.lifl.fr>
Message-ID: <Pine.LNX.4.10.10102201321390.30361-100000@newsarepta.cs.ualberta.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

Hi:

This is not a paper. It is just a broad review for my own use. If you need
it, I can send you a copy.

Kui Wu
    
Computing Science Dept.         |email: wkui@cs.ualberta.ca
U. of Alberta                   |Phone: (780) 492-7747 (O)
Edmonton,AB                     |
T6G 2E8                         |

On Tue, 20 Feb 2001, Julien.Cartigny wrote:

> 
> "QoS Support in Mobile Ad Hoc Networks" by Kui Wu and Janelle Harms from
> the Computing Science Departement of the university of Alberta. Sorry, no
> bibliography or download location, I can't remember myself where i found
> this paper.
> 
> Other papers:
> 
>  - "QoS routing performance in a multi-hop, wireless networks"
>      Tsu-Wei Chen, Mario Gerla and Jack Tzu-Chieh Tsai
>      In Proceedings of ICUPC '97.
> 
> 
> ------------------------------------------------------------------
> CARTIGNY Julien 
> These d'informatique dans l'equipe RD2P  a l'universite de Lille 1 
> (Phd of Computer Science at the University of Lille 1 / France)
>  
> "Sometimes when reading Goethe I have the paralyzing suspicion that he is trying to be funny." - Guy Davenport
> 
> On Tue, 20 Feb 2001, Krishna Kishore K R wrote:
> 
> > Hi,
> >   I don't think any work has been done in the area of QoS in Ad
> >   hoc networks. At present, routing issue is being emphasized
> >   on.
> > 
> > regards,
> > Kishore.
> > 
> > On Mon, 19 Feb 2001, Jian - Chen wrote:
> > 
> > > Hi,
> > > could you recommend me some good papers about "QoS in mobile ad hoc"?
> > > I can't find papers published last year in this field?
> > >
> > > Thank you very much
> > >
> > > Jian
> > >
> > 
> 



From owner-manet@itd.nrl.navy.mil  Tue Feb 20 19:21:46 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 TAA00211
	for <manet-archive@odin.ietf.org>; Tue, 20 Feb 2001 19:21:45 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id QAA24619
	for manet-outgoing; Tue, 20 Feb 2001 16:57:26 -0500 (EST)
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 QAA24614
	for <manet@itd.nrl.navy.mil>; Tue, 20 Feb 2001 16:57:23 -0500 (EST)
Message-Id: <5.0.1.4.2.20010220165813.035cd5c8@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Tue, 20 Feb 2001 16:58:33 -0500
To: manet@itd.nrl.navy.mil
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Fwd: BOUNCE manet@itd.nrl.navy.mil: Non-member submission from
  ["Seoungbum Lee" <sbl@comet.columbia.edu>]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk


>Date: tue, 20 feb 2001 16:09:32 -0500 (est)
>To: owner-manet@itd.nrl.navy.mil
>From: owner-manet@itd.nrl.navy.mil
>Subject: bounce manet@itd.nrl.navy.mil: non-member submission from 
>["seoungbum lee" <sbl@comet.columbia.edu>]
>
> >From macker  Tue Feb 20 16:09:29 2001
>Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu 
>[128.59.64.60])
>         by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id QAA22158
>         for <manet@itd.nrl.navy.mil>; Tue, 20 Feb 2001 16:09:27 -0500 (EST)
>Received: from protoss (protoss.comet.columbia.edu [128.59.68.124]) by 
>sirius.ctr.columbia.edu (8.9.3/8.6.4.287) with SMTP id QAA19597; Tue, 20 
>Feb 2001 16:09:20 -0500 (EST)
>Message-ID: <006601c09b81$0ab71130$7c443b80@comet.columbia.edu>
>From: "Seoungbum Lee" <sbl@comet.columbia.edu>
>To: "Jian - Chen" <jchen@cs.tamu.edu>, <manet@itd.nrl.navy.mil>
>Subject: Re: hi
>Date: Tue, 20 Feb 2001 16:06:49 -0500
>MIME-Version: 1.0
>Content-Type: text/plain;
>         charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Mailer: Microsoft Outlook Express 5.50.4133.2400
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
>
>
>Hi Jian,
>
>[1] The CEDAR Paper can be found at,
>http://timely.crhc.uiuc.edu/Projects/cedar/papers.html
>P. Sinha, R. Sivakumar, and V. Bharghavan, ``CEDAR: a Core-Extraction
>Distributed Ad hoc Routing algorithm.''  IEEE Infocom '99,  New York, NY.
>March 1999.
>
>[2] MMWN paper can be obtained from
>http://www.ir.bbn.com/~ramanath/#pubs
>S. Ramanathan and M. Steenstrup, "Hierarchically-organized, multihop mobile
>networks for multimedia support," ACM/Baltzer Mobile Networks and
>Applications, Vol. 3, No. 1, pp 101-119.
>
>[3] INSIGNIA paper can be obtained from
>The INSIGNIA Project at Columbia is investigating QOS differentiation and
>adaptation
>in ad hoc networks. See http://www.comet.columbia.edu/insignia/ for papers,
>ID and ns source code.
>
>and there are more like the AODV extensions to QOS and etc.
>
>Best Regards,
>
>-----------------------------------------------------
>  Seoung-Bum Lee
>
>  COMET Group, Columbia University
>  e-mail : sbl@comet.columbia.edu
>  http://www.comet.columbia.edu/~sbl
>
>  * Pushing beyond the limits!
>-----------------------------------------------------
>
>
>----- Original Message -----
>From: "Seoungbum Lee" <sbl@comet.columbia.edu>
>To: "Jian - Chen" <jchen@cs.tamu.edu>
>Sent: Monday, February 19, 2001 2:46 PM
>Subject: Re: hi
>
>
> > Hi Jian,
> >
> > You can look at the CEDAR proposal which talks about QoS routing,
> > MMWN proposal by BBN, INSIGNIA proposal (signaling) which is
> > indepent of any routing protocol.
> >
> > Then you can extend your search from these papers.
> >
> > ps. There are some magazine articles on QOS on the
> > Feb issue of IEEE CommMag (2001).
> >
> > Hope this info helps.
> >
> >
> > ----- Original Message -----
> > From: "Jian - Chen" <jchen@cs.tamu.edu>
> > To: <manet@itd.nrl.navy.mil>
> > Sent: Monday, February 19, 2001 2:04 PM
> > Subject: hi
> >
> >
> > > Hi,
> > > could you recommend me some good papers about "QoS in mobile ad hoc"?
> > > I can't find papers published last year in this field?
> > >
> > > Thank you very much
> > >
> > > Jian
> > >
> > >
> >




From owner-manet@itd.nrl.navy.mil  Wed Feb 21 14:09:51 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 OAA06326
	for <manet-archive@odin.ietf.org>; Wed, 21 Feb 2001 14:09:51 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA20566
	for manet-outgoing; Wed, 21 Feb 2001 11:25:50 -0500 (EST)
Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id LAA20558
	for <manet@itd.nrl.navy.mil>; Wed, 21 Feb 2001 11:25:45 -0500 (EST)
Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204])
 by research.kpn.com (PMDF V5.2-31 #42699)
 with ESMTP id <01K0DOXLX8NK000FRD@research.kpn.com> for
 manet@itd.nrl.navy.mil; Wed, 21 Feb 2001 17:25:45 +0100
Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19)
	id <F2KLK52P>; Wed, 21 Feb 2001 17:25:44 +0100
Content-return: allowed
Date: Wed, 21 Feb 2001 17:25:43 +0100
From: "Groten, D." <D.Groten@kpn.com>
Subject: RE: hi
To: "'Jian - Chen'" <jchen@cs.tamu.edu>
Cc: manet@itd.nrl.navy.mil
Message-id: <59063B5B4D98D311BC0D0001FA7E45220428E70E@l04.research.kpn.com>
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,

Another paper addressing the issue of QoS (with a proposal for QoS routing)
is:
"QoS Routing in Ad Hoc Wireless networks" by C.R. Lin and J.-S. Liu, IEEE J.
Sel. Areas Commun., vol. 17 (8), p. 1426, august 1999.

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: Leonard Miller [mailto:lmiller@antd.nist.gov]
Sent: dinsdag 20 februari 2001 15:12
To: Jian - Chen
Cc: manet@itd.nrl.navy.mil
Subject: Re: hi


Jian - Chen wrote:
> 
> Hi,
> could you recommend me some good papers about "QoS in mobile ad hoc"?
> I can't find papers published last year in this field?
> 
> Thank you very much
> 
> Jian

There's a good unpublished survey by Wu and Harms at
  
http://www.cs.ualberta.ca/~wkui/research/QoSReview.ps

This manuscript makes good use of a paper in the Spring 2000 proceeding
of the Vehicular Technology Conference by Hannan Xiao et al., "A
Flexible Quality of Service Model for Mobile Ad Hoc Networks."


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

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  Wed Feb 21 14:39:26 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 OAA06327
	for <manet-archive@odin.ietf.org>; Wed, 21 Feb 2001 14:09:51 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA20399
	for manet-outgoing; Wed, 21 Feb 2001 11:22:30 -0500 (EST)
Received: from scapa.cs.ualberta.ca (scapa.cs.ualberta.ca [129.128.4.44])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id LAA20392
	for <manet@itd.nrl.navy.mil>; Wed, 21 Feb 2001 11:22:27 -0500 (EST)
Received: from async5-3.remote.ualberta.ca ([129.128.238.76]:1032 "EHLO
        cs.ualberta.ca") by scapa.cs.ualberta.ca with ESMTP
	id <S433708AbRBUQVq>; Wed, 21 Feb 2001 09:21:46 -0700
Message-ID: <3A93DF16.62D61043@cs.ualberta.ca>
Date:   Wed, 21 Feb 2001 09:30:30 -0600
From: Kui Wu <wkui@cs.ualberta.ca>
Reply-To: wkui@cs.ualberta.ca
Organization: U.of A.
X-Mailer: Mozilla 4.61 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: manet@itd.nrl.navy.mil
Subject: QoS review- (Re: hi from Kui)
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:

It is very surprising that I have received about 20 requirements for my
review. It can be found at:
www.cs.ualberta.ca/~wkui/research/QoSReview.ps

It should be mentioned that the review is for my own use and I do not
guarantee the correctness of some discussion as well as the completeness
to include all research in this area. I am grateful for your feedback.

I have replied some emails and I am sorry I will not answer further
asking for this survey.

Kui Wu



From owner-manet@itd.nrl.navy.mil  Wed Feb 21 15:15:45 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 PAA08455
	for <manet-archive@odin.ietf.org>; Wed, 21 Feb 2001 15:15:45 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id MAA24277
	for manet-outgoing; Wed, 21 Feb 2001 12:47:16 -0500 (EST)
Received: from sirius.ctr.columbia.edu (sirius.ctr.columbia.edu [128.59.64.60])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id MAA24269
	for <manet@itd.nrl.navy.mil>; Wed, 21 Feb 2001 12:47:13 -0500 (EST)
Received: from protoss (protoss.comet.columbia.edu [128.59.68.124]) by sirius.ctr.columbia.edu (8.9.3/8.6.4.287) with SMTP id MAA08525; Wed, 21 Feb 2001 12:47:14 -0500 (EST)
Message-ID: <002201c09c2d$f9643810$7c443b80@comet.columbia.edu>
From: "Seoungbum Lee" <sbl@ctr.columbia.edu>
To: <manet@itd.nrl.navy.mil>, "Jian - Chen" <jchen@cs.tamu.edu>
References: <5.0.1.4.2.20010220165813.035cd5c8@pop.itd.nrl.navy.mil>
Subject: Re: BOUNCE manet@itd.nrl.navy.mil: Non-member submission from  ["Seoungbum Lee" <sbl@comet.columbia.edu>]
Date: Wed, 21 Feb 2001 12:44:15 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello Jian,

I am resending my mail since previous mail was bounced
by mail.


>Hi Jian,
>
>[1] The CEDAR Paper can be found at,
>http://timely.crhc.uiuc.edu/Projects/cedar/papers.html
>P. Sinha, R. Sivakumar, and V. Bharghavan, ``CEDAR: a Core-Extraction
>Distributed Ad hoc Routing algorithm.''  IEEE Infocom '99,  New York, NY.
>March 1999.
>
>[2] MMWN paper can be obtained from
>http://www.ir.bbn.com/~ramanath/#pubs
>S. Ramanathan and M. Steenstrup, "Hierarchically-organized, multihop mobile
>networks for multimedia support," ACM/Baltzer Mobile Networks and
>Applications, Vol. 3, No. 1, pp 101-119.
>
>[3] INSIGNIA paper can be obtained from
>The INSIGNIA Project at Columbia is investigating QOS differentiation and
>adaptation
>in ad hoc networks. See http://www.comet.columbia.edu/insignia/ for papers,
>ID and ns source code.
>
>and there are more like the AODV extensions to QOS and etc.
>
>Best Regards,
>
>-----------------------------------------------------
>  Seoung-Bum Lee
>
>  COMET Group, Columbia University
>  e-mail : sbl@comet.columbia.edu
>  http://www.comet.columbia.edu/~sbl
>
>  * Pushing beyond the limits!
-----------------------------------------------------


>>----- Original Message -----
> >From: "Seoungbum Lee" <sbl@comet.columbia.edu>
> >To: "Jian - Chen" <jchen@cs.tamu.edu>
> >Sent: Monday, February 19, 2001 2:46 PM
> >Subject: Re: hi
> >
> >
> > > Hi Jian,
> > >
> > > You can look at the CEDAR proposal which talks about QoS routing,
> > > MMWN proposal by BBN, INSIGNIA proposal (signaling) which is
> > > indepent of any routing protocol.
> > >
> > > Then you can extend your search from these papers.
> > >
> > > ps. There are some magazine articles on QOS on the
> > > Feb issue of IEEE CommMag (2001).
> > >
> > > Hope this info helps.
> > >
> > >
> > > ----- Original Message -----
> > > From: "Jian - Chen" <jchen@cs.tamu.edu>
> > > To: <manet@itd.nrl.navy.mil>
> > > Sent: Monday, February 19, 2001 2:04 PM
> > > Subject: hi
> > >
> > >
> > > > Hi,
> > > > could you recommend me some good papers about "QoS in mobile ad
hoc"?
> > > > I can't find papers published last year in this field?
> > > >
> > > > Thank you very much
> > > >
> > > > Jian
> > > >
> > > >
> > >
>
>
>



From owner-manet@itd.nrl.navy.mil  Wed Feb 21 16:05:15 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 QAA10217
	for <manet-archive@odin.ietf.org>; Wed, 21 Feb 2001 16:05:14 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id NAA26192
	for manet-outgoing; Wed, 21 Feb 2001 13:26:23 -0500 (EST)
Received: from barrichello.cs.ucr.edu (barrichello.cs.ucr.edu [138.23.169.5])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id NAA26187
	for <manet@itd.nrl.navy.mil>; Wed, 21 Feb 2001 13:26:20 -0500 (EST)
Received: by barrichello.cs.ucr.edu (Postfix, from userid 2)
	id B5A1E20AF6; Wed, 21 Feb 2001 10:26:21 -0800 (PST)
Received: from jupiter.cs.ucr.edu (jupiter.cs.ucr.edu [138.23.174.175])
	by barrichello.cs.ucr.edu (Postfix) with ESMTP
	id 994B320AF4; Wed, 21 Feb 2001 10:26:20 -0800 (PST)
Received: from localhost (msamidi@localhost)
	by jupiter.cs.ucr.edu (8.9.3/8.8.8) with ESMTP id KAA03164;
	Wed, 21 Feb 2001 10:26:20 -0800
X-Authentication-Warning: jupiter.cs.ucr.edu: msamidi owned process doing -bs
Date: Wed, 21 Feb 2001 10:26:20 -0800 (PST)
From: Michael Samidi <msamidi@cs.ucr.edu>
To: Jian - Chen <jchen@cs.tamu.edu>
Cc: manet@itd.nrl.navy.mil
Subject: Re: hi
In-Reply-To: <Pine.SOL.4.10.10102191301100.8471-100000@robert>
Message-ID: <Pine.LNX.4.10.10102211023390.3149-100000@jupiter.cs.ucr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AntiVirus: scanned for viruses by AMaViS perl-6
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk


Hello all,

I just found out that this month issue of IEEE Comm Magazine has a article
about QoS in Ad Hoc Wireless Networks.

The title of the article is "QoS Issues in Ad Hoc Wireless Networks".
The author is Satyabrata Chakrabarti (Lucent Tech) and Amitabh Mishra
(Virginia Tech).

I hope this will help.

Regards,
Michael

************************************************************************
   Michael Samidi                              Office: (909) 787-2784
   Graduate Student (MS Program)                 Home: (909) 786-9792
   Computer Science Dept.              http://www.cs.ucr.edu/~msamidi
   University of California
   Riverside, CA 92521
************************************************************************

On Mon, 19 Feb 2001, Jian - Chen wrote:

> Hi,
> could you recommend me some good papers about "QoS in mobile ad hoc"?
> I can't find papers published last year in this field? 
> 
> Thank you very much
> 
> Jian  
> 
> 



From owner-manet@itd.nrl.navy.mil  Fri Feb 23 13:57:28 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 NAA15209
	for <manet-archive@odin.ietf.org>; Fri, 23 Feb 2001 13:57:28 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA23445
	for manet-outgoing; Fri, 23 Feb 2001 11:14:35 -0500 (EST)
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 LAA23436
	for <manet@itd.nrl.navy.mil>; Fri, 23 Feb 2001 11:14:32 -0500 (EST)
Message-Id: <5.0.1.4.2.20010223111514.0338e9c0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Fri, 23 Feb 2001 11:15:35 -0500
To: manet@itd.nrl.navy.mil
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: BRP ID Announce
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

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-00.txt
	Pages		: 13
	Date		: 21-Feb-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-00.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-00.txt".

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


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

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

--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:	<20010221145609.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



From owner-manet@itd.nrl.navy.mil  Fri Feb 23 13:57: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 NAA15221
	for <manet-archive@odin.ietf.org>; Fri, 23 Feb 2001 13:57:31 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA23406
	for manet-outgoing; Fri, 23 Feb 2001 11:13:40 -0500 (EST)
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 LAA23401
	for <manet@itd.nrl.navy.mil>; Fri, 23 Feb 2001 11:13:37 -0500 (EST)
Message-Id: <5.0.1.4.2.20010223111245.01946378@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Fri, 23 Feb 2001 11:14:40 -0500
To: manet@itd.nrl.navy.mil
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: ID Announcement
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

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-00.txt
	Pages		: 11
	Date		: 21-Feb-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-00.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-00.txt".

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


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

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

--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:	<20010221145628.I-D@ietf.org>

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

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



From owner-manet@itd.nrl.navy.mil  Fri Feb 23 13:57: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 NAA15222
	for <manet-archive@odin.ietf.org>; Fri, 23 Feb 2001 13:57:31 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id LAA23477
	for manet-outgoing; Fri, 23 Feb 2001 11:15:07 -0500 (EST)
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 LAA23472
	for <manet@itd.nrl.navy.mil>; Fri, 23 Feb 2001 11:15:05 -0500 (EST)
Message-Id: <5.0.1.4.2.20010223111557.031ecec8@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Fri, 23 Feb 2001 11:16:08 -0500
To: manet@itd.nrl.navy.mil
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: IERP ID Announce
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-manet@itd.nrl.navy.mil
Precedence: bulk

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-00.txt
	Pages		: 14
	Date		: 21-Feb-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-00.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-00.txt".

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


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

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

--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:	<20010221145619.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--



From owner-manet@itd.nrl.navy.mil  Sat Feb 24 02:44: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 CAA17590
	for <manet-archive@odin.ietf.org>; Sat, 24 Feb 2001 02:44:56 -0500 (EST)
Received: (from majordom@localhost)
	by itd.nrl.navy.mil (8.8.8/8.8.8) id AAA11741
	for manet-outgoing; Sat, 24 Feb 2001 00:13:23 -0500 (EST)
Received: from trantor.dso.org.sg (trantor.dso.org.sg [192.190.204.1])
	by itd.nrl.navy.mil (8.8.8/8.8.8) with ESMTP id AAA11736
	for <manet@itd.nrl.navy.mil>; Sat, 24 Feb 2001 00:13:14 -0500 (EST)
Received: from demerzel.dso.org.sg (demerzel.dso.org.sg [192.190.204.8])
	by trantor.dso.org.sg (8.10.2/8.10.2) with ESMTP id f1O5DjW25766;
	Sat, 24 Feb 2001 13:13:46 +0800 (SGT)
Received: from dso.org.sg ([172.18.51.32])
	by demerzel.dso.org.sg (8.10.0/8.10.0) with ESMTP id f1O5CnS23240;
	Sat, 24 Feb 2001 13:12:49 +0800 (SGT)
Message-ID: <3A9744DE.6D59C95A@dso.org.sg>
Date: Sat, 24 Feb 2001 13:21:34 +0800
From: Lee Aik Tuan <laiktuan@dso.org.sg>
Organization: DSO National Laboratories
X-Mailer: Mozilla 4.72 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Jian - Chen <jchen@cs.tamu.edu>
CC: manet@itd.nrl.navy.mil
Subject: Re: hi
References: <Pine.SOL.4.10.10102191301100.8471-100000@robert>
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,

Do you want papers from just last year?  Anyway, to add on, I have some
links and biblio which you may want to check out.  Hope this helps.



UCLA Wireless Adaptivity Lab is doing research into similar areas:
http://www.cs.ucla.edu/NRL/wireless/index.html
http://www.cs.ucla.edu/NRL/wireless/papers.html

Ramanathan, StreenStrup. "Hierarchically-organized Multihop Mobile
Wireless Network for Quality-of-Service Support", Mobile Networks and
Applications, ACM, 3(1), 1996.

CEDAR talked about QoS Routing (Can anyone provide an update on the
status of CEDAR?)
Check the paper titled "CEDAR: a Core-Extraction Distributed Ad Hoc
Routing Algorithm".  
Reasearch done at University of Illinois at Urbana-Champaign, but I lost
the URL.

You may also want to check out Insignia (used to be internet draft).

Also, these are in my "To Read" list :

QoS Routing
-----------
Murthy, Garcia-Luna-Aceves "A routing architecture for mobile integrated
services networks", Mobile Applications and Networks, 1998.

Iwata, Chiang, Pei, Gerla, Chen. "Scalabile Routing Strategies for Ad
Hoc Wireless Networks", IEEE JSAC 17 (8), Aug 1999.

Ho, Liu. "On-emand QoS-based Routing Protocol for Ad Hoc Mobile Wireless
Networks", Proc. Symp. Computers and Communications, 2000.

Chen, Nahrstedt. "Distributed Quality-of-Service Routing in Ad Hoc
Networks", IEEE JSAC 17(8), Aug 1999.

Aggelou, Tafazolli. "A Sumulation Analysis on reactive Route Repair
techniques for QoS sensitive applications in Mobile Ad Hoc Networks",
MobiHoc 2000.

Resource Allocation
-------------------
Sobrinho, Krishnakumar. "Quality-of-service in Ad Hoc Carrier Sense
Multiple Access Wireless Networks". IEEE JSAC 17(8), Aug 1999.

Lal, Sousa. "Distributed Resource ALoocation for DS-CDMA-Based
Multimedia ad hoc Wireless LAN's", IEEE JSAC 17(5), May 1999.


Jian - Chen wrote:
> 
> Hi,
> could you recommend me some good papers about "QoS in mobile ad hoc"?
> I can't find papers published last year in this field?
> 
> Thank you very much
> 
> Jian

Lee Aik Tuan
Senior Member of Technical Staff
DSO National Laboratories
20 Science Park Drive, Singapore 118230
http://www.dso.org.sg


