From mailman-owner@ietf.org  Fri Mar  1 07:05:04 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14045
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 07:05:04 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA19250
	for <manet-archive@lists.ietf.org>; Fri, 1 Mar 2002 07:05:06 -0500 (EST)
Date: Fri, 1 Mar 2002 07:05:06 -0500 (EST)
Message-Id: <200203011205.HAA19250@optimus.ietf.org>
From: mailman-owner@ietf.org
Subject: ietf.org mailing list memberships reminder
To: manet-archive@ietf.org
X-No-Archive: yes
Precedence: bulk
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, manet-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for manet-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
manet@ietf.org                           FtOz      
https://www1.ietf.org/mailman/options/manet/manet-archive@lists.ietf.org


From manet-admin@ietf.org  Fri Mar  1 11:21:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03372
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 11:21:45 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04859;
	Fri, 1 Mar 2002 10:56:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04825
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 10:56:33 -0500 (EST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA01588
	for <manet@ietf.org>; Fri, 1 Mar 2002 10:56:30 -0500 (EST)
Received: (qmail 10434 invoked by uid 510); 1 Mar 2002 13:10:20 -0000
Date: 1 Mar 2002 13:10:20 -0000
Message-ID: <20020301131020.10433.qmail@mailFA9.rediffmail.com>
Received: from unknown (128.205.25.30) by rediffmail.com via HTTP; 01 Mar 2002 13:10:20 -0000
MIME-Version: 1.0
From: "vikas p verma" <vvicky72@rediffmail.com>
Reply-To: "vikas p verma" <vvicky72@rediffmail.com>
To: manet@ietf.org
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Subject: [manet] Cost Function - PARO
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi,

I just wanted to know if Power Aware Routing Optimization 
Algorithm 'balances the power at each node' or 'minimizes the 
overall power of the Ad hoc n/w'.
As per the internet draft the cost function is just the minimum 
transmission power Tmin. This indicates that it will 'minimize 
over all power of the n/w'. On the other hand one of the paper on 
PARO states that the cost function is Tmin*f(B) where B - power 
resourse of a node and f(B) is inversly proportional to B. This
would implicate that PARO is trying to 'balance the power at 
individual node'. Can somebody please explain what is the actual 
cost function.

Thanks
Vikas.

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


From manet-admin@ietf.org  Fri Mar  1 11:24:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03628
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 11:24:24 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA05269;
	Fri, 1 Mar 2002 11:00:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA05210
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 11:00:09 -0500 (EST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01851
	for <manet@ietf.org>; Fri, 1 Mar 2002 11:00:04 -0500 (EST)
Received: (qmail 19139 invoked by uid 510); 1 Mar 2002 13:13:48 -0000
Date: 1 Mar 2002 13:13:48 -0000
Message-ID: <20020301131348.19138.qmail@mailFA9.rediffmail.com>
Received: from unknown (128.205.25.30) by rediffmail.com via HTTP; 01 Mar 2002 13:13:48 -0000
MIME-Version: 1.0
From: "vikas p verma" <vvicky72@rediffmail.com>
Reply-To: "vikas p verma" <vvicky72@rediffmail.com>
To: manet@ietf.org
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Subject: [manet] PARO - Route Redirect messages
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi,

According to the internet draft Route Redirect messages in 
PARO(Power Aware Routing Optimization) are sent at two times. One 
will be when the node feels that it can optimize a particular 
route for a given source destination pair. The other would be 
when
it no longer optimizes the route. Can any body please let me know 
as to how will the source node react to the second case. Will it 
start searching a new route all over from scratch? And when will 
the intermediate node calculate that it no longer optimizes a 
route. Is there any fixed interval for this, depending upon 
mobility?

Thanks
Vikas.


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


From daemon@ns.ietf.org  Fri Mar  1 11:24:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03642
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 11:24:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08604
	for manet-archive@odin.ietf.org; Fri, 1 Mar 2002 11:24:26 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA05269;
	Fri, 1 Mar 2002 11:00:14 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA05210
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 11:00:09 -0500 (EST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA01851
	for <manet@ietf.org>; Fri, 1 Mar 2002 11:00:04 -0500 (EST)
Received: (qmail 19139 invoked by uid 510); 1 Mar 2002 13:13:48 -0000
Date: 1 Mar 2002 13:13:48 -0000
Message-ID: <20020301131348.19138.qmail@mailFA9.rediffmail.com>
Received: from unknown (128.205.25.30) by rediffmail.com via HTTP; 01 Mar 2002 13:13:48 -0000
MIME-Version: 1.0
From: "vikas p verma" <vvicky72@rediffmail.com>
Reply-To: "vikas p verma" <vvicky72@rediffmail.com>
To: manet@ietf.org
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Subject: [manet] PARO - Route Redirect messages
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi,

According to the internet draft Route Redirect messages in 
PARO(Power Aware Routing Optimization) are sent at two times. One 
will be when the node feels that it can optimize a particular 
route for a given source destination pair. The other would be 
when
it no longer optimizes the route. Can any body please let me know 
as to how will the source node react to the second case. Will it 
start searching a new route all over from scratch? And when will 
the intermediate node calculate that it no longer optimizes a 
route. Is there any fixed interval for this, depending upon 
mobility?

Thanks
Vikas.


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



From manet-admin@ietf.org  Fri Mar  1 11:37:32 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04571
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 11:37:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA07385;
	Fri, 1 Mar 2002 11:14:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA07354
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 11:14:55 -0500 (EST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03001
	for <manet@ietf.org>; Fri, 1 Mar 2002 11:14:52 -0500 (EST)
Received: (qmail 11364 invoked by uid 510); 1 Mar 2002 13:23:04 -0000
Date: 1 Mar 2002 13:23:04 -0000
Message-ID: <20020301132304.11363.qmail@mailFA9.rediffmail.com>
Received: from unknown (128.205.25.30) by rediffmail.com via HTTP; 01 Mar 2002 13:23:04 -0000
MIME-Version: 1.0
From: "vikas p verma" <vvicky72@rediffmail.com>
Reply-To: "vikas p verma" <vvicky72@rediffmail.com>
To: manet@ietf.org
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Subject: [manet] PARO - Route Redirect messages
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi,

According to the internet draft Route Redirect messages in 
PARO(Power Aware Routing Optimization) are sent at two times. One 
will be when the node feels that it can optimize a particular 
route for a given source destination pair. The other would be 
when
it no longer optimizes the route. Can any body please let me know 
as to how will the source node react to the second case. Will it 
start searching a new route all over from scratch? And when will 
the intermediate node calculate that it no longer optimizes a 
route. Is there any fixed interval for this, depending upon 
mobility?

Thanks
Vikas.


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


From daemon@ns.ietf.org  Fri Mar  1 11:37:33 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04581
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 11:37:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA10114
	for manet-archive@odin.ietf.org; Fri, 1 Mar 2002 11:37:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA07385;
	Fri, 1 Mar 2002 11:14:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA07354
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 11:14:55 -0500 (EST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA03001
	for <manet@ietf.org>; Fri, 1 Mar 2002 11:14:52 -0500 (EST)
Received: (qmail 11364 invoked by uid 510); 1 Mar 2002 13:23:04 -0000
Date: 1 Mar 2002 13:23:04 -0000
Message-ID: <20020301132304.11363.qmail@mailFA9.rediffmail.com>
Received: from unknown (128.205.25.30) by rediffmail.com via HTTP; 01 Mar 2002 13:23:04 -0000
MIME-Version: 1.0
From: "vikas p verma" <vvicky72@rediffmail.com>
Reply-To: "vikas p verma" <vvicky72@rediffmail.com>
To: manet@ietf.org
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Subject: [manet] PARO - Route Redirect messages
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi,

According to the internet draft Route Redirect messages in 
PARO(Power Aware Routing Optimization) are sent at two times. One 
will be when the node feels that it can optimize a particular 
route for a given source destination pair. The other would be 
when
it no longer optimizes the route. Can any body please let me know 
as to how will the source node react to the second case. Will it 
start searching a new route all over from scratch? And when will 
the intermediate node calculate that it no longer optimizes a 
route. Is there any fixed interval for this, depending upon 
mobility?

Thanks
Vikas.


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



From daemon@ns.ietf.org  Fri Mar  1 12:24:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03380
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 11:21:46 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA08277
	for manet-archive@odin.ietf.org; Fri, 1 Mar 2002 11:21:47 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04859;
	Fri, 1 Mar 2002 10:56:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA04825
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 10:56:33 -0500 (EST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA01588
	for <manet@ietf.org>; Fri, 1 Mar 2002 10:56:30 -0500 (EST)
Received: (qmail 10434 invoked by uid 510); 1 Mar 2002 13:10:20 -0000
Date: 1 Mar 2002 13:10:20 -0000
Message-ID: <20020301131020.10433.qmail@mailFA9.rediffmail.com>
Received: from unknown (128.205.25.30) by rediffmail.com via HTTP; 01 Mar 2002 13:10:20 -0000
MIME-Version: 1.0
From: "vikas p verma" <vvicky72@rediffmail.com>
Reply-To: "vikas p verma" <vvicky72@rediffmail.com>
To: manet@ietf.org
Content-type: text/plain;
	format=flowed
Content-Disposition: inline
Subject: [manet] Cost Function - PARO
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi,

I just wanted to know if Power Aware Routing Optimization 
Algorithm 'balances the power at each node' or 'minimizes the 
overall power of the Ad hoc n/w'.
As per the internet draft the cost function is just the minimum 
transmission power Tmin. This indicates that it will 'minimize 
over all power of the n/w'. On the other hand one of the paper on 
PARO states that the cost function is Tmin*f(B) where B - power 
resourse of a node and f(B) is inversly proportional to B. This
would implicate that PARO is trying to 'balance the power at 
individual node'. Can somebody please explain what is the actual 
cost function.

Thanks
Vikas.

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



From manet-admin@ietf.org  Fri Mar  1 14:08:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16090
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 14:08:59 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19418;
	Fri, 1 Mar 2002 13:40:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19385
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 13:40:25 -0500 (EST)
Received: from ponyexpress.ee.columbia.edu (IDENT:root@ponyexpress.ee.columbia.edu [128.59.64.61])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13521
	for <manet@ietf.org>; Fri, 1 Mar 2002 13:40:21 -0500 (EST)
Received: from pareto.comet.columbia.edu (IDENT:root@pareto.comet.columbia.edu [128.59.67.99])
	by ponyexpress.ee.columbia.edu (8.11.3/8.11.3) with ESMTP id g21IeOU06700;
	Fri, 1 Mar 2002 13:40:24 -0500
Received: from localhost (javierg@localhost)
	by pareto.comet.columbia.edu (8.11.6/8.11.0) with ESMTP id g21IeOT06203;
	Fri, 1 Mar 2002 13:40:24 -0500
Date: Fri, 1 Mar 2002 13:40:24 -0500 (EST)
From: Javier Gomez-Castellanos <javierg@ee.columbia.edu>
To: vikas p verma <vvicky72@rediffmail.com>
cc: <manet@ietf.org>
Subject: Re: [manet] Cost Function - PARO
In-Reply-To: <20020301131020.10433.qmail@mailFA9.rediffmail.com>
Message-ID: <Pine.LNX.4.33.0203011252430.6069-100000@pareto.comet.columbia.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org



hello Vikas,

hope i can answer your questions below.

The cost function in the PARO internet draft considers reducing transmission 
power only as the cost function. We did so because not only minimizing 
transmission power increases the lifetime of nodes, but also because 
the definition of such a cost function is unambiguous to understand.

We are aware that such a cost function is likely to consume the power 
reserves of nodes in different proportions. One way to avoid this problem, 
as you mentioned, is to take into account the power reserves in each node 
in order to "balance the power" in the network. This statement is, is 
general true. However the definition of such a cost function is more 
difficult to define formally, and therefore more difficult to understand. 
For this reason we did not include such a cost function in the internet 
draft.

Balancing power in the network is a tricky issue. Basically when you 
try to balance the power in the network, you consume the power resources 
of nodes in the present in some way that you "guess" it will increase the 
overall lifetime of the nodes in the future. Unfortunately unless you can 
predict the future you are not totally sure you are doing the "right" 
thing in the present. Nodes may change locations over time, traffic 
patters may change, etc. Similarly, do we want to maximize the time until 
the first node run out of power?, or the the first 5% of the nodes run 
out of power?. There are some papers that discuss this trade off between 
minimizing transmission power and balancing power that provide very useful 
and interesting insights about this.

cheers.  

--
--Javier
-----------------------------------------
COMET Group
Columbia University, New York.
http://www.comet.columbia.edu/~javierg

 




On 1 Mar 2002, vikas p verma wrote:

> Hi,
> 
> I just wanted to know if Power Aware Routing Optimization 
> Algorithm 'balances the power at each node' or 'minimizes the 
> overall power of the Ad hoc n/w'.
> As per the internet draft the cost function is just the minimum 
> transmission power Tmin. This indicates that it will 'minimize 
> over all power of the n/w'. On the other hand one of the paper on 
> PARO states that the cost function is Tmin*f(B) where B - power 
> resourse of a node and f(B) is inversly proportional to B. This
> would implicate that PARO is trying to 'balance the power at 
> individual node'. Can somebody please explain what is the actual 
> cost function.
> 
> Thanks
> Vikas.
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

-- 
--Javier
-----------------------------------------
COMET Group
Columbia University, New York. 	
http://www.comet.columbia.edu/~javierg 





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


From daemon@ns.ietf.org  Fri Mar  1 14:09:00 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16100
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 14:08:59 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA21901
	for manet-archive@odin.ietf.org; Fri, 1 Mar 2002 14:09:03 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19418;
	Fri, 1 Mar 2002 13:40:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19385
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 13:40:25 -0500 (EST)
Received: from ponyexpress.ee.columbia.edu (IDENT:root@ponyexpress.ee.columbia.edu [128.59.64.61])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13521
	for <manet@ietf.org>; Fri, 1 Mar 2002 13:40:21 -0500 (EST)
Received: from pareto.comet.columbia.edu (IDENT:root@pareto.comet.columbia.edu [128.59.67.99])
	by ponyexpress.ee.columbia.edu (8.11.3/8.11.3) with ESMTP id g21IeOU06700;
	Fri, 1 Mar 2002 13:40:24 -0500
Received: from localhost (javierg@localhost)
	by pareto.comet.columbia.edu (8.11.6/8.11.0) with ESMTP id g21IeOT06203;
	Fri, 1 Mar 2002 13:40:24 -0500
Date: Fri, 1 Mar 2002 13:40:24 -0500 (EST)
From: Javier Gomez-Castellanos <javierg@ee.columbia.edu>
To: vikas p verma <vvicky72@rediffmail.com>
cc: <manet@ietf.org>
Subject: Re: [manet] Cost Function - PARO
In-Reply-To: <20020301131020.10433.qmail@mailFA9.rediffmail.com>
Message-ID: <Pine.LNX.4.33.0203011252430.6069-100000@pareto.comet.columbia.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org



hello Vikas,

hope i can answer your questions below.

The cost function in the PARO internet draft considers reducing transmission 
power only as the cost function. We did so because not only minimizing 
transmission power increases the lifetime of nodes, but also because 
the definition of such a cost function is unambiguous to understand.

We are aware that such a cost function is likely to consume the power 
reserves of nodes in different proportions. One way to avoid this problem, 
as you mentioned, is to take into account the power reserves in each node 
in order to "balance the power" in the network. This statement is, is 
general true. However the definition of such a cost function is more 
difficult to define formally, and therefore more difficult to understand. 
For this reason we did not include such a cost function in the internet 
draft.

Balancing power in the network is a tricky issue. Basically when you 
try to balance the power in the network, you consume the power resources 
of nodes in the present in some way that you "guess" it will increase the 
overall lifetime of the nodes in the future. Unfortunately unless you can 
predict the future you are not totally sure you are doing the "right" 
thing in the present. Nodes may change locations over time, traffic 
patters may change, etc. Similarly, do we want to maximize the time until 
the first node run out of power?, or the the first 5% of the nodes run 
out of power?. There are some papers that discuss this trade off between 
minimizing transmission power and balancing power that provide very useful 
and interesting insights about this.

cheers.  

--
--Javier
-----------------------------------------
COMET Group
Columbia University, New York.
http://www.comet.columbia.edu/~javierg

 




On 1 Mar 2002, vikas p verma wrote:

> Hi,
> 
> I just wanted to know if Power Aware Routing Optimization 
> Algorithm 'balances the power at each node' or 'minimizes the 
> overall power of the Ad hoc n/w'.
> As per the internet draft the cost function is just the minimum 
> transmission power Tmin. This indicates that it will 'minimize 
> over all power of the n/w'. On the other hand one of the paper on 
> PARO states that the cost function is Tmin*f(B) where B - power 
> resourse of a node and f(B) is inversly proportional to B. This
> would implicate that PARO is trying to 'balance the power at 
> individual node'. Can somebody please explain what is the actual 
> cost function.
> 
> Thanks
> Vikas.
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

-- 
--Javier
-----------------------------------------
COMET Group
Columbia University, New York. 	
http://www.comet.columbia.edu/~javierg 





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



From manet-admin@ietf.org  Fri Mar  1 15:34:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24545
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 15:34:11 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24746;
	Fri, 1 Mar 2002 15:01:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24712
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 15:01:23 -0500 (EST)
Received: from ponyexpress.ee.columbia.edu (IDENT:root@ponyexpress.ee.columbia.edu [128.59.64.61])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21637
	for <manet@ietf.org>; Fri, 1 Mar 2002 15:01:21 -0500 (EST)
Received: from pareto.comet.columbia.edu (IDENT:root@pareto.comet.columbia.edu [128.59.67.99])
	by ponyexpress.ee.columbia.edu (8.11.3/8.11.3) with ESMTP id g21K1OU08764;
	Fri, 1 Mar 2002 15:01:24 -0500
Received: from localhost (javierg@localhost)
	by pareto.comet.columbia.edu (8.11.6/8.11.0) with ESMTP id g21K1Oo07025;
	Fri, 1 Mar 2002 15:01:24 -0500
Date: Fri, 1 Mar 2002 15:01:24 -0500 (EST)
From: Javier Gomez-Castellanos <javierg@ee.columbia.edu>
To: vikas p verma <vvicky72@rediffmail.com>
cc: <manet@ietf.org>
Subject: Re: [manet] PARO - Route Redirect messages
In-Reply-To: <20020301131348.19138.qmail@mailFA9.rediffmail.com>
Message-ID: <Pine.LNX.4.33.0203011341420.6069-100000@pareto.comet.columbia.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org



Hello again Vikas,

In the second scenario that you mention where a forwarding node no longer 
optimize a route, this forwarding node is responsible to signal the 
previous node in the route (it could be the source node) to let it know 
the next hop in route. 

In the example shown below if node N6 moves out of the route it will signal 
the source node that the next hop is now node N3.


  S ----N6---->N3---- ... ---N9--->D
        |
        V 


cheers

--
--Javier
-----------------------------------------
COMET Group
Columbia University, New York.
http://www.comet.columbia.edu/~javierg


On 1 Mar 2002, vikas p verma wrote:

> Hi,
> 
> According to the internet draft Route Redirect messages in 
> PARO(Power Aware Routing Optimization) are sent at two times. One 
> will be when the node feels that it can optimize a particular 
> route for a given source destination pair. The other would be 
> when
> it no longer optimizes the route. Can any body please let me know 
> as to how will the source node react to the second case. Will it 
> start searching a new route all over from scratch? And when will 
> the intermediate node calculate that it no longer optimizes a 
> route. Is there any fixed interval for this, depending upon 
> mobility?
> 
> Thanks
> Vikas.
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

-- 
--Javier
-----------------------------------------
COMET Group
Columbia University, New York. 	
http://www.comet.columbia.edu/~javierg 





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


From daemon@ns.ietf.org  Fri Mar  1 15:34:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24581
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 15:34:16 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA26960
	for manet-archive@odin.ietf.org; Fri, 1 Mar 2002 15:34:18 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24746;
	Fri, 1 Mar 2002 15:01:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24712
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 15:01:23 -0500 (EST)
Received: from ponyexpress.ee.columbia.edu (IDENT:root@ponyexpress.ee.columbia.edu [128.59.64.61])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21637
	for <manet@ietf.org>; Fri, 1 Mar 2002 15:01:21 -0500 (EST)
Received: from pareto.comet.columbia.edu (IDENT:root@pareto.comet.columbia.edu [128.59.67.99])
	by ponyexpress.ee.columbia.edu (8.11.3/8.11.3) with ESMTP id g21K1OU08764;
	Fri, 1 Mar 2002 15:01:24 -0500
Received: from localhost (javierg@localhost)
	by pareto.comet.columbia.edu (8.11.6/8.11.0) with ESMTP id g21K1Oo07025;
	Fri, 1 Mar 2002 15:01:24 -0500
Date: Fri, 1 Mar 2002 15:01:24 -0500 (EST)
From: Javier Gomez-Castellanos <javierg@ee.columbia.edu>
To: vikas p verma <vvicky72@rediffmail.com>
cc: <manet@ietf.org>
Subject: Re: [manet] PARO - Route Redirect messages
In-Reply-To: <20020301131348.19138.qmail@mailFA9.rediffmail.com>
Message-ID: <Pine.LNX.4.33.0203011341420.6069-100000@pareto.comet.columbia.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org



Hello again Vikas,

In the second scenario that you mention where a forwarding node no longer 
optimize a route, this forwarding node is responsible to signal the 
previous node in the route (it could be the source node) to let it know 
the next hop in route. 

In the example shown below if node N6 moves out of the route it will signal 
the source node that the next hop is now node N3.


  S ----N6---->N3---- ... ---N9--->D
        |
        V 


cheers

--
--Javier
-----------------------------------------
COMET Group
Columbia University, New York.
http://www.comet.columbia.edu/~javierg


On 1 Mar 2002, vikas p verma wrote:

> Hi,
> 
> According to the internet draft Route Redirect messages in 
> PARO(Power Aware Routing Optimization) are sent at two times. One 
> will be when the node feels that it can optimize a particular 
> route for a given source destination pair. The other would be 
> when
> it no longer optimizes the route. Can any body please let me know 
> as to how will the source node react to the second case. Will it 
> start searching a new route all over from scratch? And when will 
> the intermediate node calculate that it no longer optimizes a 
> route. Is there any fixed interval for this, depending upon 
> mobility?
> 
> Thanks
> Vikas.
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

-- 
--Javier
-----------------------------------------
COMET Group
Columbia University, New York. 	
http://www.comet.columbia.edu/~javierg 





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



From manet-admin@ietf.org  Fri Mar  1 18:46:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06569
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 18:46:56 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06792;
	Fri, 1 Mar 2002 18:20:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06758
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 18:20:01 -0500 (EST)
Received: from ponyexpress.ee.columbia.edu (IDENT:root@ponyexpress.ee.columbia.edu [128.59.64.61])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05670
	for <manet@ietf.org>; Fri, 1 Mar 2002 18:19:59 -0500 (EST)
Received: from SWEETPEA (sweetpea.comet.columbia.edu [128.59.65.202])
	by ponyexpress.ee.columbia.edu (8.11.3/8.11.3) with SMTP id g21NK1U13586;
	Fri, 1 Mar 2002 18:20:01 -0500
From: "Andrew T. Campbell" <campbell@comet.columbia.edu>
To: <manet@ietf.org>
Cc: "Andrew Campbell \(E-mail\)" <campbell@comet.columbia.edu>
Date: Fri, 1 Mar 2002 18:17:22 -0500
Message-ID: <007301c1c177$3e5b89e0$ca413b80@SWEETPEA>
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.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] F I N A L   C A L L   F O R   P A P E R S  for ACM MobiCom 2002
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


***************************************************************
[Appologies if you receive duplicates of this message]

Please note the following changes in this CFP:
- Paper submission details have been revised.
- A Student Poster Session has been added.
- Student travel grants are now available.

 * The server is now open for paper submissions*

See below for details.
***************************************************************


              F I N A L   C A L L   F O R   P A P E R S

                   *** ACM MobiCom 2002 ***
The Eighth Annual International Conference on Mobile Computing and
Networking

                    September 23-26, 2002
                    Westin Peachtree Plaza
                    Atlanta, Georgia, USA

              http://www.acm.org/sigmobile/mobicom/2002/


                 Sponsored by ACM SIGMOBILE

     Paper Submission Deadline (EXTENDED): March 8, 2002

  ******** No further extensions will be given *********


MobiCom 2002 is the eighth annual conference dedicated to addressing new
challenges in mobile computing and networking. MobiCom 2002 solicits papers
describing significant research contributions to the field of mobile
computing and networking.

PAPERS:
-------
Authors are invited to submit full papers related to the theory and practice
of mobile computing and networking. Original research papers (that are not
currently under review by another conference or journal) are solicited.
Areas of interest include, but not limited to:

* Applications and computing services supporting mobile users
* Architectures, protocols, and algorithms to cope with mobility, limited
  bandwidth, or intermittent connectivity
* Database and data management issues in mobile computing
* Performance of mobile/wireless networks and systems
* Security and privacy of mobile/wireless systems
* Interaction between different layers of mobile/wireless systems
* Integration and interworking of wired and wireless networks
* Adaptive applications and systems for mobile environments
* Distributed-system aspects of mobile systems
* Operating system support for mobility
* Location-dependent applications
* Wireless multimedia systems
* Power management
* Mobile agents
* Pervasive computing
* Wireless sensor networks
* Wireless/mobile service management and delivery

All papers will be refereed by the program committee. Accepted papers will
be published in the conference proceedings.

Papers of particular merit will be proposed for publication in the
ACM/Kluwer Wireless Networks (WINET) and
Mobile Networks and Applications (MONET) journals.

CHALLENGES SESSION:
------------------
Short papers (maximum of 8 pages) that challenge the mobile computing
community with new technologies or visionary applications are solicited.
Such papers should provide stimulating ideas or visions that may open up
exciting avenues of mobile computing research. Papers will be reviewed
and should be submitted using the normal submission procedure.
Submitted papers should be clearly identified as intended for the
Challenges Session.

**REVISED SUBMISSION INSTRUCTIONS**:
------------------------------------
All paper submissions will be handled electronically. Authors should prepare
a PostScript or Portable Document Format (PDF) version of their paper. No
other format will be accepted.

Papers must meet the following restrictions:

-  The paper must be original material that has not been previously
   published nor is currently under review by another conference or journal.
-  Full papers should be no longer than *15 pages*, in font no smaller than
   10 points. (Note that accepted papers, when formatted for the
   proceedings, may not exceed 12 pages in font no smaller than 9 points).
-  Challenges papers should be no longer than 8 pages, in font no smaller
   than 10 points.
-  All submitted papers will be judged based on their quality through
   double-blind reviewing, where the identities of the authors are withheld
   from the reviewers. Authors' names *must not* appear in the paper.
-  The paper should fit properly on US Letter-sized paper (8.5x11 inches)
-  PostScript version 2 or later, or Portable Document Format (PDF)
-  Use only Computer Modern or standard Adobe printer fonts (i.e., Courier,
   Times, Roman, or Helvetica)
-  Other fonts may be used, but must be included in the PostScript/PDF file
-  The paper must be formatted for b/w printers and not color printers.

Instructions for submission are available at:
http://www.acm.org/sigmobile/mobicom/2002/submissions/


TUTORIALS:
----------
Proposals for tutorials are solicited, and will be evaluated based on
the expertise of the instructors and the relevance of the subject matter.
Potential instructors should submit a tutorial proposal of at
most five pages, including a biographical sketch, to the Tutorial
Co-chairs (cath@ecn.purdue.edu or nhv@crhc.uiuc.edu).

PANELS:
-------
Proposals are solicited for panels that examine innovative, controversial,
or otherwise provocative issues of interest. Panel proposals should
not exceed 3 pages, including biographical sketches of the panelists.
Potential panel organizers should contact the Panel Co-chairs
(shroff@ecn.purdue.edu or marie-jose.montpetit@nokia.com).

RESEARCH DEMOS:
---------------
Proposals for research demos are solicited. Proposals should not exceed 3
pages and should include a description of the demo and equipment that
will be used. Proposals for demos should be sent to the Research Demo
Chair (ron@oit.gatech.edu).

** STUDENT POSTER SESSION **:
---------------------------
The conference solicits student posters that highlight recent and on-going
research by students on mobile computing topics. Proposals should be a
maximum of two pages in length. While it does not need to describe completed
work,
the poster paper should report on research that is beyond the initial
stages.
The first author of a poster submission must be a student. Poster abstracts
will not be published in the proceedings but will instead be published on
the web
before the conference.  Poster submissions will be reviewed. Authors of
accepted papers
must not submit a poster of the work they present in the conference. For
more information about
student poster applications contact the Student Poster Co-chairs
(ebelding@cs.ucsb.edu or sjlee@hpl.hp.com).

**STUDENT TRAVEL AWARDS**:
--------------------------
MobiCom will offer a limited number of travel grants to support students.
Please contact Student Travel Awards Co-Chairs for application details
(fang@ece.ufl.edu or syrotiuk@utdallas.edu).


BEST STUDENT PAPER AWARD:
-------------------------
Papers with a student as the primary author will be considered
for the Best Student Paper Award with a cash award of $1,000 USD. Students
must indicate with their submissions that they would like to be considered
for this award.

IMPORTANT DATES:
----------------
*  Paper submissions due: March 8, 2002
*  Notification of acceptance: June 30, 2002
*  Camera-ready version due: July 31, 2002
*  Tutorial proposals: May 1, 2002

FOR MORE INFORMATION: Check the conference website or send
email to mobicom2002@comet.columbia.edu


EXECUTIVE COMMITTEE:
--------------------
* General Chair: Ian F. Akyildiz, Georgia Institute of Technology

* General Vice-Chairs:
   - Jason Y. B. Lin, National Chiao Tung University
   - Ravi Jain, Telcordia

* Program Co-Chairs:
   - Vaduvur Bharghavan, Bessemer Venture Partners
   - Andrew T. Campbell, Columbia University

* Panels Co-Chairs:
   - Ness Shroff, Purdue University
   - Marie-Jose Montpetit, Nokia

* Tutorials Co-Chairs:
   - Catherine Rosenberg, Purdue University
   - Nitin Vaidya, University of Illinois at Urbana Champaign

* Steering Committee Chair: Imrich Chlamtac, University of Texas at Dallas

* Publicity Co-Chairs:
   - Chuanyi Ji, Georgia Institute of Technology
   - Marwan M. Krunz, University of Arizona

* Workshop Co-Chairs:
   - Taieb Znati, NSF and University of Pittsburgh
   - Mehmet Ulema, Mercury Corporation

* Research Demos Chair: Ron Hutchins, Georgia Institute of Technology

* Finance Chair: Edward Knightly, Rice University

* Registration Co-Chairs:
   - Suresh Singh, Portland State University
   - Robin Kravets, University of Illinois, Urbana-Champaign

* Student Poster Co-Chairs:
   - Elizabeth M. Belding-Royer, University of California, Santa Barbara
   - Sung-Ju Lee, HP Laboratories

* Student Travel Award Co-Chairs:
  - Yuguang Fang, University of Florida
  - Violet R. Syrotiuk, University of Texas at Dallas


* Sponsorship/Exhibit Chair: Ramesh Govindan, Univ. of Southern California

* Local Arrangements Chair: Raghupathy Sivakumar: Georgia Institute of
Technology

* Webmaster: Michael E. Kounavis, Columbia University

PROGRAM COMMITTEE:
--------------------

Program Co-Chairs:

 - Vaduvur Bharghavan, Bessemer Venture Partners
 - Andrew T. Campbell, Columbia University

Program Committee:

- Arup Acharya, IBM Research
- Prathima Agrawal, Telcordia
- B. R. Badrinath, Rutgers University
- Victor Bahl, Microsoft Research
- Stefano Basagni, Northeastern University
- Roberto Battiti, University of Trento
- Pravin Bhagwat, ReefEdge
- Chatschik Bisdikian, IBM Research
- Scott Corson, Flarion
- Sajal Das, University Texas at Arlington
- Nigel Davies, Lancaster University
- Dan Duchamp, Stevens Institute of Technology
- Maria Ebling, IBM Research
- Magda El-Zarki, University of California, Irvine
- Anthony Ephremides, University of Maryland
- Deborah Estrin, University of California, Los Angeles
- J.J. Garcia-Luna-Aceves, University of California at Santa Cruz
- Mario Gerla, University of California, Los Angeles
- Ramesh Govindan, USC/ISI
- Ravi Jain, Telcordia
- David B. Johnson, Rice University
- Anthony Joseph, University of California, Berkeley
- Edward Knightly, Rice University
- Tom LaPorta, Lucent Technologies
- Songwu Lu, University of California, Los Angeles
- Robert Morris, MIT
- S. Muthukrishnan, AT&T Research
- Brian Noble, University of Michigan
- Venkat Padmanabhan, Microsoft Research
- Charles Perkins, Nokia
- Chiara Petrioli, University "La Sapienza"
- George Polyzos, Athens University of Economics and Business
- Parmesh Ramanathan, University of Wisconsin - Madison
- Ram Ramanathan, BBN Technologies
- Ramachandran Ramjee, Lucent Technologies
- Daniela Rus, Dartmouth College
- Srinivasan Seshan, Carnegie Mellon University
- Kang G. Shin, University of Michigan
- Suresh Singh, Portland State University
- Mani Srivastava, University of California, Los Angeles
- Frank Stajano, AT&T Laboratories Cambridge
- Martha Steenstrup, Stow Research
- Violet R. Syrotiuk, University of Texas at Dallas
- Leandros Tassiulas, University of Maryland
- Nitin H. Vaidya, University of Illinois at Urbana-Champaign
- Andras Valko, Ericsson Research
- Adam Wolisz, Technical University of Berlin
- Michele Zorzi, Universita di Ferrara


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


From daemon@ns.ietf.org  Fri Mar  1 18:46:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06580
	for <manet-archive@odin.ietf.org>; Fri, 1 Mar 2002 18:46:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA08327
	for manet-archive@odin.ietf.org; Fri, 1 Mar 2002 18:46:59 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06792;
	Fri, 1 Mar 2002 18:20:05 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA06758
	for <manet@ns.ietf.org>; Fri, 1 Mar 2002 18:20:01 -0500 (EST)
Received: from ponyexpress.ee.columbia.edu (IDENT:root@ponyexpress.ee.columbia.edu [128.59.64.61])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05670
	for <manet@ietf.org>; Fri, 1 Mar 2002 18:19:59 -0500 (EST)
Received: from SWEETPEA (sweetpea.comet.columbia.edu [128.59.65.202])
	by ponyexpress.ee.columbia.edu (8.11.3/8.11.3) with SMTP id g21NK1U13586;
	Fri, 1 Mar 2002 18:20:01 -0500
From: "Andrew T. Campbell" <campbell@comet.columbia.edu>
To: <manet@ietf.org>
Cc: "Andrew Campbell \(E-mail\)" <campbell@comet.columbia.edu>
Date: Fri, 1 Mar 2002 18:17:22 -0500
Message-ID: <007301c1c177$3e5b89e0$ca413b80@SWEETPEA>
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.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] F I N A L   C A L L   F O R   P A P E R S  for ACM MobiCom 2002
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


***************************************************************
[Appologies if you receive duplicates of this message]

Please note the following changes in this CFP:
- Paper submission details have been revised.
- A Student Poster Session has been added.
- Student travel grants are now available.

 * The server is now open for paper submissions*

See below for details.
***************************************************************


              F I N A L   C A L L   F O R   P A P E R S

                   *** ACM MobiCom 2002 ***
The Eighth Annual International Conference on Mobile Computing and
Networking

                    September 23-26, 2002
                    Westin Peachtree Plaza
                    Atlanta, Georgia, USA

              http://www.acm.org/sigmobile/mobicom/2002/


                 Sponsored by ACM SIGMOBILE

     Paper Submission Deadline (EXTENDED): March 8, 2002

  ******** No further extensions will be given *********


MobiCom 2002 is the eighth annual conference dedicated to addressing new
challenges in mobile computing and networking. MobiCom 2002 solicits papers
describing significant research contributions to the field of mobile
computing and networking.

PAPERS:
-------
Authors are invited to submit full papers related to the theory and practice
of mobile computing and networking. Original research papers (that are not
currently under review by another conference or journal) are solicited.
Areas of interest include, but not limited to:

* Applications and computing services supporting mobile users
* Architectures, protocols, and algorithms to cope with mobility, limited
  bandwidth, or intermittent connectivity
* Database and data management issues in mobile computing
* Performance of mobile/wireless networks and systems
* Security and privacy of mobile/wireless systems
* Interaction between different layers of mobile/wireless systems
* Integration and interworking of wired and wireless networks
* Adaptive applications and systems for mobile environments
* Distributed-system aspects of mobile systems
* Operating system support for mobility
* Location-dependent applications
* Wireless multimedia systems
* Power management
* Mobile agents
* Pervasive computing
* Wireless sensor networks
* Wireless/mobile service management and delivery

All papers will be refereed by the program committee. Accepted papers will
be published in the conference proceedings.

Papers of particular merit will be proposed for publication in the
ACM/Kluwer Wireless Networks (WINET) and
Mobile Networks and Applications (MONET) journals.

CHALLENGES SESSION:
------------------
Short papers (maximum of 8 pages) that challenge the mobile computing
community with new technologies or visionary applications are solicited.
Such papers should provide stimulating ideas or visions that may open up
exciting avenues of mobile computing research. Papers will be reviewed
and should be submitted using the normal submission procedure.
Submitted papers should be clearly identified as intended for the
Challenges Session.

**REVISED SUBMISSION INSTRUCTIONS**:
------------------------------------
All paper submissions will be handled electronically. Authors should prepare
a PostScript or Portable Document Format (PDF) version of their paper. No
other format will be accepted.

Papers must meet the following restrictions:

-  The paper must be original material that has not been previously
   published nor is currently under review by another conference or journal.
-  Full papers should be no longer than *15 pages*, in font no smaller than
   10 points. (Note that accepted papers, when formatted for the
   proceedings, may not exceed 12 pages in font no smaller than 9 points).
-  Challenges papers should be no longer than 8 pages, in font no smaller
   than 10 points.
-  All submitted papers will be judged based on their quality through
   double-blind reviewing, where the identities of the authors are withheld
   from the reviewers. Authors' names *must not* appear in the paper.
-  The paper should fit properly on US Letter-sized paper (8.5x11 inches)
-  PostScript version 2 or later, or Portable Document Format (PDF)
-  Use only Computer Modern or standard Adobe printer fonts (i.e., Courier,
   Times, Roman, or Helvetica)
-  Other fonts may be used, but must be included in the PostScript/PDF file
-  The paper must be formatted for b/w printers and not color printers.

Instructions for submission are available at:
http://www.acm.org/sigmobile/mobicom/2002/submissions/


TUTORIALS:
----------
Proposals for tutorials are solicited, and will be evaluated based on
the expertise of the instructors and the relevance of the subject matter.
Potential instructors should submit a tutorial proposal of at
most five pages, including a biographical sketch, to the Tutorial
Co-chairs (cath@ecn.purdue.edu or nhv@crhc.uiuc.edu).

PANELS:
-------
Proposals are solicited for panels that examine innovative, controversial,
or otherwise provocative issues of interest. Panel proposals should
not exceed 3 pages, including biographical sketches of the panelists.
Potential panel organizers should contact the Panel Co-chairs
(shroff@ecn.purdue.edu or marie-jose.montpetit@nokia.com).

RESEARCH DEMOS:
---------------
Proposals for research demos are solicited. Proposals should not exceed 3
pages and should include a description of the demo and equipment that
will be used. Proposals for demos should be sent to the Research Demo
Chair (ron@oit.gatech.edu).

** STUDENT POSTER SESSION **:
---------------------------
The conference solicits student posters that highlight recent and on-going
research by students on mobile computing topics. Proposals should be a
maximum of two pages in length. While it does not need to describe completed
work,
the poster paper should report on research that is beyond the initial
stages.
The first author of a poster submission must be a student. Poster abstracts
will not be published in the proceedings but will instead be published on
the web
before the conference.  Poster submissions will be reviewed. Authors of
accepted papers
must not submit a poster of the work they present in the conference. For
more information about
student poster applications contact the Student Poster Co-chairs
(ebelding@cs.ucsb.edu or sjlee@hpl.hp.com).

**STUDENT TRAVEL AWARDS**:
--------------------------
MobiCom will offer a limited number of travel grants to support students.
Please contact Student Travel Awards Co-Chairs for application details
(fang@ece.ufl.edu or syrotiuk@utdallas.edu).


BEST STUDENT PAPER AWARD:
-------------------------
Papers with a student as the primary author will be considered
for the Best Student Paper Award with a cash award of $1,000 USD. Students
must indicate with their submissions that they would like to be considered
for this award.

IMPORTANT DATES:
----------------
*  Paper submissions due: March 8, 2002
*  Notification of acceptance: June 30, 2002
*  Camera-ready version due: July 31, 2002
*  Tutorial proposals: May 1, 2002

FOR MORE INFORMATION: Check the conference website or send
email to mobicom2002@comet.columbia.edu


EXECUTIVE COMMITTEE:
--------------------
* General Chair: Ian F. Akyildiz, Georgia Institute of Technology

* General Vice-Chairs:
   - Jason Y. B. Lin, National Chiao Tung University
   - Ravi Jain, Telcordia

* Program Co-Chairs:
   - Vaduvur Bharghavan, Bessemer Venture Partners
   - Andrew T. Campbell, Columbia University

* Panels Co-Chairs:
   - Ness Shroff, Purdue University
   - Marie-Jose Montpetit, Nokia

* Tutorials Co-Chairs:
   - Catherine Rosenberg, Purdue University
   - Nitin Vaidya, University of Illinois at Urbana Champaign

* Steering Committee Chair: Imrich Chlamtac, University of Texas at Dallas

* Publicity Co-Chairs:
   - Chuanyi Ji, Georgia Institute of Technology
   - Marwan M. Krunz, University of Arizona

* Workshop Co-Chairs:
   - Taieb Znati, NSF and University of Pittsburgh
   - Mehmet Ulema, Mercury Corporation

* Research Demos Chair: Ron Hutchins, Georgia Institute of Technology

* Finance Chair: Edward Knightly, Rice University

* Registration Co-Chairs:
   - Suresh Singh, Portland State University
   - Robin Kravets, University of Illinois, Urbana-Champaign

* Student Poster Co-Chairs:
   - Elizabeth M. Belding-Royer, University of California, Santa Barbara
   - Sung-Ju Lee, HP Laboratories

* Student Travel Award Co-Chairs:
  - Yuguang Fang, University of Florida
  - Violet R. Syrotiuk, University of Texas at Dallas


* Sponsorship/Exhibit Chair: Ramesh Govindan, Univ. of Southern California

* Local Arrangements Chair: Raghupathy Sivakumar: Georgia Institute of
Technology

* Webmaster: Michael E. Kounavis, Columbia University

PROGRAM COMMITTEE:
--------------------

Program Co-Chairs:

 - Vaduvur Bharghavan, Bessemer Venture Partners
 - Andrew T. Campbell, Columbia University

Program Committee:

- Arup Acharya, IBM Research
- Prathima Agrawal, Telcordia
- B. R. Badrinath, Rutgers University
- Victor Bahl, Microsoft Research
- Stefano Basagni, Northeastern University
- Roberto Battiti, University of Trento
- Pravin Bhagwat, ReefEdge
- Chatschik Bisdikian, IBM Research
- Scott Corson, Flarion
- Sajal Das, University Texas at Arlington
- Nigel Davies, Lancaster University
- Dan Duchamp, Stevens Institute of Technology
- Maria Ebling, IBM Research
- Magda El-Zarki, University of California, Irvine
- Anthony Ephremides, University of Maryland
- Deborah Estrin, University of California, Los Angeles
- J.J. Garcia-Luna-Aceves, University of California at Santa Cruz
- Mario Gerla, University of California, Los Angeles
- Ramesh Govindan, USC/ISI
- Ravi Jain, Telcordia
- David B. Johnson, Rice University
- Anthony Joseph, University of California, Berkeley
- Edward Knightly, Rice University
- Tom LaPorta, Lucent Technologies
- Songwu Lu, University of California, Los Angeles
- Robert Morris, MIT
- S. Muthukrishnan, AT&T Research
- Brian Noble, University of Michigan
- Venkat Padmanabhan, Microsoft Research
- Charles Perkins, Nokia
- Chiara Petrioli, University "La Sapienza"
- George Polyzos, Athens University of Economics and Business
- Parmesh Ramanathan, University of Wisconsin - Madison
- Ram Ramanathan, BBN Technologies
- Ramachandran Ramjee, Lucent Technologies
- Daniela Rus, Dartmouth College
- Srinivasan Seshan, Carnegie Mellon University
- Kang G. Shin, University of Michigan
- Suresh Singh, Portland State University
- Mani Srivastava, University of California, Los Angeles
- Frank Stajano, AT&T Laboratories Cambridge
- Martha Steenstrup, Stow Research
- Violet R. Syrotiuk, University of Texas at Dallas
- Leandros Tassiulas, University of Maryland
- Nitin H. Vaidya, University of Illinois at Urbana-Champaign
- Andras Valko, Ericsson Research
- Adam Wolisz, Technical University of Berlin
- Michele Zorzi, Universita di Ferrara


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



From manet-admin@ietf.org  Mon Mar  4 13:45:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10121
	for <manet-archive@odin.ietf.org>; Mon, 4 Mar 2002 13:45:57 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19144;
	Mon, 4 Mar 2002 13:13:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19113
	for <manet@ns.ietf.org>; Mon, 4 Mar 2002 13:13:54 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07316
	for <manet@ietf.org>; Mon, 4 Mar 2002 13:13:51 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id KAA28830;
	Mon, 4 Mar 2002 10:11:55 -0800 (PST)
Message-Id: <200203041811.KAA28830@pit.erg.sri.com>
To: Fred Baker <fred@cisco.com>
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
In-reply-to: Your message of "Mon, 25 Feb 2002 17:16:58 PST."
             <4.3.2.7.2.20020225171131.02427f88@mira-sjcm-2.cisco.com> 
Date: Mon, 04 Mar 2002 10:11:55 -0800
Subject: [manet] Re: RE : others cretaria in MANET routing protocol
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

> 
> I'll argue that hop count in and of itself is a poor indicator.  Consider 
> the following
> 
>          A--------------------->B
>           ---------->C--------->
> 
> B and C can both hear A; C hears A with an excellent S/N Ratio and B hears 
> A with a poor signal to noise ratio, such that a small percentage of 
> packets (less than some threshold measured in percent) can actually 
> traverse A->B. I will argue that A->C->B is much kinder to the application 
> than A->B, so adding a hop creates a significantly improved route even 
> though the smaller hop count would be nice.
> 
> It seems to me that hop count might be a tie-breaker amount routes of equal 
> robustness, not the other way around.
 

I agree that MANET routing protocols should allow the selection of 
paths that are shortest w.r.t. a metric (which OSPF does).  This metric 
can take into account signal strength, reliability, bandwidth, link 
stability, etc.  The following example shows why computing a shortest 
path w.r.t. a metric is better than simply deciding whether or not
to use an adjacent link based on whether the link quality is above
or below certain thresholds (e.g., using hysteresis).

       .9   .9   .9
     2 -- 3 -- 4 -- 5
 .9 /                 \ .9 
   1                  10
.89 \                 / 1.0
     6 -- 7 -- 8 -- 9
       1.0  1.0  1.0  

Node 1 wants to select the best path to node 10.
The numbers indicate the reliability for each link.
(Actually, the negative log of the reliability would be
used so that the metric is additive.)
Consider a protocol (which could be OLSR or TBRPF) that selects a 
min-hop path subject to a link quality threshold, and suppose that 
the threshold is .9.  That protocol would use the upper path,
which has reliability .9 * .9 * .9 * .9 * .9 = .59.
However, a protocol that takes into account the metric
of each link along the path would use the lower path, which 
has a much better reliability of .89 * 1 * 1 * 1 * 1 = .89.

Also, it is possible that the *only* path to some node is
one that uses a poor quality but usable link. If only hysteresis
is used, that node would be unreachable (even if an urgent message
must be sent to that node).  It is better to *allow* the use of
of a poor quality link, but select paths based on a link metric so 
that a poor quality link is used only if necessary.

Hop count is also an important objective for MANETs because a packet 
that travels more hops consumes more bandwidth.
Assuming that Dijkstra's algorithm is used by a link-state routing 
protocol to compute shortest paths, the following link cost (used
by TBRPF) will achieve a tradeoff between minimizing the number of 
hops and minimizing a metric:

  c(u,v) = 1 + COEFF * metric(u,v)

If COEFF is very large, then hop count is used only as a tie breaker,
and if COEFF is very small, then the metric is used as a tie breaker.  

We used metrics in the original (full-topology) version of TBRPF,
but dropped them in the partial-topology version in order to
reduce overhead.  We are adding them back as an option in TBRPF
version 05 (submitted last week) because (1) our simulations
(which can be found at www.erg.sri.com/projects/tbrpf)
show that TBRPF generates much less routing overhead than OLSR,
and the inclusion of 8-bit metrics in topology updates increases this 
overhead by only a small amount; and (2) our laboratory experiments
show that the use of metrics can improve performance.

I should also mention that TBRPF version 05 supports multiple 
interfaces and network prefixes.  However, no major changes have 
been made to the core protocol.

Richard

P.S. I thought about the possibility of modifying OLSR so that it 
computes shortest paths w.r.t. a link metric (instead of computing 
min-hop paths subject to the quality of each link being above some 
threshold).  It is not as easy to do this in OLSR, because of the 
requirement that paths must use links (u,v) such that v selected u as 
a multipoint relay (except for the first hop).  This requirement 
severely reduces the path choices, so that the shortest path w.r.t. 
a given metric (other than the hop metric) is not likely to 
satisfy this requirement.


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


From daemon@ns.ietf.org  Mon Mar  4 13:45:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10132
	for <manet-archive@odin.ietf.org>; Mon, 4 Mar 2002 13:45:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA22186
	for manet-archive@odin.ietf.org; Mon, 4 Mar 2002 13:46:01 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19144;
	Mon, 4 Mar 2002 13:13:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA19113
	for <manet@ns.ietf.org>; Mon, 4 Mar 2002 13:13:54 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07316
	for <manet@ietf.org>; Mon, 4 Mar 2002 13:13:51 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id KAA28830;
	Mon, 4 Mar 2002 10:11:55 -0800 (PST)
Message-Id: <200203041811.KAA28830@pit.erg.sri.com>
To: Fred Baker <fred@cisco.com>
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
In-reply-to: Your message of "Mon, 25 Feb 2002 17:16:58 PST."
             <4.3.2.7.2.20020225171131.02427f88@mira-sjcm-2.cisco.com> 
Date: Mon, 04 Mar 2002 10:11:55 -0800
Subject: [manet] Re: RE : others cretaria in MANET routing protocol
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

> 
> I'll argue that hop count in and of itself is a poor indicator.  Consider 
> the following
> 
>          A--------------------->B
>           ---------->C--------->
> 
> B and C can both hear A; C hears A with an excellent S/N Ratio and B hears 
> A with a poor signal to noise ratio, such that a small percentage of 
> packets (less than some threshold measured in percent) can actually 
> traverse A->B. I will argue that A->C->B is much kinder to the application 
> than A->B, so adding a hop creates a significantly improved route even 
> though the smaller hop count would be nice.
> 
> It seems to me that hop count might be a tie-breaker amount routes of equal 
> robustness, not the other way around.
 

I agree that MANET routing protocols should allow the selection of 
paths that are shortest w.r.t. a metric (which OSPF does).  This metric 
can take into account signal strength, reliability, bandwidth, link 
stability, etc.  The following example shows why computing a shortest 
path w.r.t. a metric is better than simply deciding whether or not
to use an adjacent link based on whether the link quality is above
or below certain thresholds (e.g., using hysteresis).

       .9   .9   .9
     2 -- 3 -- 4 -- 5
 .9 /                 \ .9 
   1                  10
.89 \                 / 1.0
     6 -- 7 -- 8 -- 9
       1.0  1.0  1.0  

Node 1 wants to select the best path to node 10.
The numbers indicate the reliability for each link.
(Actually, the negative log of the reliability would be
used so that the metric is additive.)
Consider a protocol (which could be OLSR or TBRPF) that selects a 
min-hop path subject to a link quality threshold, and suppose that 
the threshold is .9.  That protocol would use the upper path,
which has reliability .9 * .9 * .9 * .9 * .9 = .59.
However, a protocol that takes into account the metric
of each link along the path would use the lower path, which 
has a much better reliability of .89 * 1 * 1 * 1 * 1 = .89.

Also, it is possible that the *only* path to some node is
one that uses a poor quality but usable link. If only hysteresis
is used, that node would be unreachable (even if an urgent message
must be sent to that node).  It is better to *allow* the use of
of a poor quality link, but select paths based on a link metric so 
that a poor quality link is used only if necessary.

Hop count is also an important objective for MANETs because a packet 
that travels more hops consumes more bandwidth.
Assuming that Dijkstra's algorithm is used by a link-state routing 
protocol to compute shortest paths, the following link cost (used
by TBRPF) will achieve a tradeoff between minimizing the number of 
hops and minimizing a metric:

  c(u,v) = 1 + COEFF * metric(u,v)

If COEFF is very large, then hop count is used only as a tie breaker,
and if COEFF is very small, then the metric is used as a tie breaker.  

We used metrics in the original (full-topology) version of TBRPF,
but dropped them in the partial-topology version in order to
reduce overhead.  We are adding them back as an option in TBRPF
version 05 (submitted last week) because (1) our simulations
(which can be found at www.erg.sri.com/projects/tbrpf)
show that TBRPF generates much less routing overhead than OLSR,
and the inclusion of 8-bit metrics in topology updates increases this 
overhead by only a small amount; and (2) our laboratory experiments
show that the use of metrics can improve performance.

I should also mention that TBRPF version 05 supports multiple 
interfaces and network prefixes.  However, no major changes have 
been made to the core protocol.

Richard

P.S. I thought about the possibility of modifying OLSR so that it 
computes shortest paths w.r.t. a link metric (instead of computing 
min-hop paths subject to the quality of each link being above some 
threshold).  It is not as easy to do this in OLSR, because of the 
requirement that paths must use links (u,v) such that v selected u as 
a multipoint relay (except for the first hop).  This requirement 
severely reduces the path choices, so that the shortest path w.r.t. 
a given metric (other than the hop metric) is not likely to 
satisfy this requirement.


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



From manet-admin@ietf.org  Mon Mar  4 19:39:09 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01901
	for <manet-archive@odin.ietf.org>; Mon, 4 Mar 2002 19:39:09 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11066;
	Mon, 4 Mar 2002 19:12:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11036
	for <manet@optimus.ietf.org>; Mon, 4 Mar 2002 19:12:54 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01035
	for <manet@ietf.org>; Mon, 4 Mar 2002 19:12:51 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id QAA29535;
	Mon, 4 Mar 2002 16:11:09 -0800 (PST)
Message-Id: <200203050011.QAA29535@pit.erg.sri.com>
To: T.Clausen@computer.org
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
In-reply-to: Your message of "Mon, 04 Feb 2002 16:09:50 +0100."
             <Pine.LNX.4.21.0202041606470.437-100000@armada> 
Date: Mon, 04 Mar 2002 16:11:09 -0800
Subject: [manet] Re: Some follow-up OLSR/AODV results
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Thomas,

> Richard,
> 
> Thanks for looking at our simulation code for OLSR in detail. You are
> correct in pointing out the bug in the simulation code, and your proposed
> solution seems to solve the problem.
> 
> Our belated reply is due to the fact that we wanted to investigate the
> impact of the bug before replying.
> 
> We have been running a set of tests, similar to those presented earlier by
> Joe (http://protean.itd.nrl.navy.mil/manet/olsrstatic.pdf) of the
> simulation code "with the bug" and "without the bug". 
> 
> Exactly the same scenarios being used, our observations basically amount
> to the following:
> 
> 	- the reported overhead (in bytes/sec) indeed is about 50% larger
> 	  with the "bugfix"

I guess you are talking about total control traffic, including RTS/CTS packets
that are used for data packets.  For just routing control traffic, I found
that the reported overhead is between 90% and 120% larger with the bug fix,
depending on the scenario.

> 
> 	- the number of control packets is roughly the same (the
> 	  differences being very small and due to the randomness
> 	  introduced by the jitter)
> 
> 	- more importantly: the delivery ratio is unaffected by the
> 	  change. I.e. the same amount of packets are being delivered.

This may not be the case in every scenario.  For example, when the 
data traffic starts to congest the network, the increased overhead
could affect delivery ratio significantly.  Also, the increased
overhead will have more impact in larger networks.

Richard


> So while we acknowledge that there indeed is a bug, the impacts seems to
be only related to the rapported overhead, not to the functioning of the
> routing protocol.
> 
> Thanks again for pointing out the bug in the code. 
> 
> --thomas
> 
> 
> 
> > I think I found a bug in that code regarding packet size. (I don't know
> > whether the same bug is in Joe's code or in the code used for
> > simulations that others have done.)
> > When running simulations with that code, I noticed in the trace file
> > that every OLSR packet has length 20 bytes, including the 20-byte IP
> > header (i.e., ns-2  considers each OLSR message to have zero length not
> > including the IP header).
> > 
> > So I looked in the file ns-olsragent.cc and noticed the line
> >
> >    ch->size() = IP_HDR_LEN;
> >
> > in the sendPacket() function, which explained the bug. I changed the
> > line to
> >   ch->size() = IP_HDR_LEN + p->datalen();
> >
> > which seemed to fix the bug.  Am I missing something?
> >
> > Richard
> 
> 
> -- 
> 
> -------------------------------------------
>   Thomas Heide Clausen
>   Civilingeniør i Datateknik (cand.polyt)
>   M.Sc in Computer Engineering
> 
>   E-Mail: T.Clausen@computer.org
>   WWW:    http://www.cs.auc.dk/~voop
> -------------------------------------------
> 
> 

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


From daemon@optimus.ietf.org  Mon Mar  4 19:39:10 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01911
	for <manet-archive@odin.ietf.org>; Mon, 4 Mar 2002 19:39:09 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA13169
	for manet-archive@odin.ietf.org; Mon, 4 Mar 2002 19:39:12 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11066;
	Mon, 4 Mar 2002 19:12:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA11036
	for <manet@optimus.ietf.org>; Mon, 4 Mar 2002 19:12:54 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01035
	for <manet@ietf.org>; Mon, 4 Mar 2002 19:12:51 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id QAA29535;
	Mon, 4 Mar 2002 16:11:09 -0800 (PST)
Message-Id: <200203050011.QAA29535@pit.erg.sri.com>
To: T.Clausen@computer.org
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
In-reply-to: Your message of "Mon, 04 Feb 2002 16:09:50 +0100."
             <Pine.LNX.4.21.0202041606470.437-100000@armada> 
Date: Mon, 04 Mar 2002 16:11:09 -0800
Subject: [manet] Re: Some follow-up OLSR/AODV results
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Thomas,

> Richard,
> 
> Thanks for looking at our simulation code for OLSR in detail. You are
> correct in pointing out the bug in the simulation code, and your proposed
> solution seems to solve the problem.
> 
> Our belated reply is due to the fact that we wanted to investigate the
> impact of the bug before replying.
> 
> We have been running a set of tests, similar to those presented earlier by
> Joe (http://protean.itd.nrl.navy.mil/manet/olsrstatic.pdf) of the
> simulation code "with the bug" and "without the bug". 
> 
> Exactly the same scenarios being used, our observations basically amount
> to the following:
> 
> 	- the reported overhead (in bytes/sec) indeed is about 50% larger
> 	  with the "bugfix"

I guess you are talking about total control traffic, including RTS/CTS packets
that are used for data packets.  For just routing control traffic, I found
that the reported overhead is between 90% and 120% larger with the bug fix,
depending on the scenario.

> 
> 	- the number of control packets is roughly the same (the
> 	  differences being very small and due to the randomness
> 	  introduced by the jitter)
> 
> 	- more importantly: the delivery ratio is unaffected by the
> 	  change. I.e. the same amount of packets are being delivered.

This may not be the case in every scenario.  For example, when the 
data traffic starts to congest the network, the increased overhead
could affect delivery ratio significantly.  Also, the increased
overhead will have more impact in larger networks.

Richard


> So while we acknowledge that there indeed is a bug, the impacts seems to
be only related to the rapported overhead, not to the functioning of the
> routing protocol.
> 
> Thanks again for pointing out the bug in the code. 
> 
> --thomas
> 
> 
> 
> > I think I found a bug in that code regarding packet size. (I don't know
> > whether the same bug is in Joe's code or in the code used for
> > simulations that others have done.)
> > When running simulations with that code, I noticed in the trace file
> > that every OLSR packet has length 20 bytes, including the 20-byte IP
> > header (i.e., ns-2  considers each OLSR message to have zero length not
> > including the IP header).
> > 
> > So I looked in the file ns-olsragent.cc and noticed the line
> >
> >    ch->size() = IP_HDR_LEN;
> >
> > in the sendPacket() function, which explained the bug. I changed the
> > line to
> >   ch->size() = IP_HDR_LEN + p->datalen();
> >
> > which seemed to fix the bug.  Am I missing something?
> >
> > Richard
> 
> 
> -- 
> 
> -------------------------------------------
>   Thomas Heide Clausen
>   Civilingeniør i Datateknik (cand.polyt)
>   M.Sc in Computer Engineering
> 
>   E-Mail: T.Clausen@computer.org
>   WWW:    http://www.cs.auc.dk/~voop
> -------------------------------------------
> 
> 

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



From manet-admin@ietf.org  Mon Mar  4 21:20:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04389
	for <manet-archive@odin.ietf.org>; Mon, 4 Mar 2002 21:20:49 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA17131;
	Mon, 4 Mar 2002 20:49:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA17100
	for <manet@optimus.ietf.org>; Mon, 4 Mar 2002 20:49:48 -0500 (EST)
Received: from tiquini.ece.arizona.edu (tiquini.ece.arizona.edu [128.196.29.23])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03607
	for <manet@ietf.org>; Mon, 4 Mar 2002 20:49:44 -0500 (EST)
Received: from krunz (ECE-DHCP-108.ece.arizona.edu [128.196.237.108])
	by tiquini.ece.arizona.edu (8.12.1/8.12.1) with SMTP id g251nigD012367
	for <manet@ietf.org>; Mon, 4 Mar 2002 18:49:45 -0700 (MST)
Reply-To: <krunz@ece.arizona.edu>
From: "Marwan M. Krunz" <krunz@ece.arizona.edu>
To: <manet@ietf.org>
Date: Mon, 4 Mar 2002 18:49:45 -0700
Message-ID: <NEBBICAGBCIDDLGKBHAIOENECFAA.krunz@ece.arizona.edu>
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 IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Subject: [manet] Mobicom 2002 - Final CFP
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit




***************************************************************
[Appologies if you receive duplicates of this message]

Please note the following changes in this CFP:
- Paper submission details have been revised.
- A Student Poster Session has been added.
- Student travel grants are now available.

See below for details.
***************************************************************


              F I N A L   C A L L   F O R   P A P E R S

                   *** ACM MobiCom 2002 ***
The Eighth Annual International Conference on Mobile Computing and
Networking

                    September 23-26, 2002
                    Westin Peachtree Plaza
                    Atlanta, Georgia, USA

              http://www.acm.org/sigmobile/mobicom/2002/


                 Sponsored by ACM SIGMOBILE

     Paper Submission Deadline (EXTENDED): March 8, 2002

  ******** No further extensions will be given *********


MobiCom 2002 is the eighth annual conference dedicated to addressing new
challenges in mobile computing and networking. MobiCom 2002 solicits papers
describing significant research contributions to the field of mobile
computing and networking.

PAPERS:
-------
Authors are invited to submit full papers related to the theory and practice
of mobile computing and networking. Original research papers (that are not
currently under review by another conference or journal) are solicited.
Areas of interest include, but not limited to:

* Applications and computing services supporting mobile users
* Architectures, protocols, and algorithms to cope with mobility, limited
  bandwidth, or intermittent connectivity
* Database and data management issues in mobile computing
* Performance of mobile/wireless networks and systems
* Security and privacy of mobile/wireless systems
* Interaction between different layers of mobile/wireless systems
* Integration and interworking of wired and wireless networks
* Adaptive applications and systems for mobile environments
* Distributed-system aspects of mobile systems
* Operating system support for mobility
* Location-dependent applications
* Wireless multimedia systems
* Power management
* Mobile agents
* Pervasive computing
* Wireless sensor networks
* Wireless/mobile service management and delivery

All papers will be refereed by the program committee. Accepted papers will
be published in the conference proceedings.

Papers of particular merit will be proposed for publication in the
ACM/Kluwer Wireless Networks (WINET) and
Mobile Networks and Applications (MONET) journals.

CHALLENGES SESSION:
------------------
Short papers (maximum of 8 pages) that challenge the mobile computing
community with new technologies or visionary applications are solicited.
Such papers should provide stimulating ideas or visions that may open up
exciting avenues of mobile computing research. Papers will be reviewed
and should be submitted using the normal submission procedure.
Submitted papers should be clearly identified as intended for the
Challenges Session.

**REVISED SUBMISSION INSTRUCTIONS**:
------------------------------------
All paper submissions will be handled electronically. Authors should prepare
a PostScript or Portable Document Format (PDF) version of their paper. No
other format will be accepted.

Papers must meet the following restrictions:

-  The paper must be original material that has not been previously
   published nor is currently under review by another conference or journal.
-  Full papers should be no longer than *15 pages*, in font no smaller than
   10 points. (Note that accepted papers, when formatted for the
   proceedings, may not exceed 12 pages in font no smaller than 9 points).
-  Challenges papers should be no longer than 8 pages, in font no smaller
   than 10 points.
-  All submitted papers will be judged based on their quality through
   double-blind reviewing, where the identities of the authors are withheld
   from the reviewers. Authors' names *must not* appear in the paper.
-  The paper should fit properly on US Letter-sized paper (8.5x11 inches)
-  PostScript version 2 or later, or Portable Document Format (PDF)
-  Use only Computer Modern or standard Adobe printer fonts (i.e., Courier,
   Times, Roman, or Helvetica)
-  Other fonts may be used, but must be included in the PostScript/PDF file
-  The paper must be formatted for b/w printers and not color printers.

Instructions for submission are available at:
http://www.acm.org/sigmobile/mobicom/2002/submissions/


TUTORIALS:
----------
Proposals for tutorials are solicited, and will be evaluated based on
the expertise of the instructors and the relevance of the subject matter.
Potential instructors should submit a tutorial proposal of at
most five pages, including a biographical sketch, to the Tutorial
Co-chairs (cath@ecn.purdue.edu or nhv@crhc.uiuc.edu).

PANELS:
-------
Proposals are solicited for panels that examine innovative, controversial,
or otherwise provocative issues of interest. Panel proposals should
not exceed 3 pages, including biographical sketches of the panelists.
Potential panel organizers should contact the Panel Co-chairs
(shroff@ecn.purdue.edu or marie-jose.montpetit@nokia.com).

RESEARCH DEMOS:
---------------
Proposals for research demos are solicited. Proposals should not exceed 3
pages and should include a description of the demo and equipment that
will be used. Proposals for demos should be sent to the Research Demo
Chair (ron@oit.gatech.edu).

** STUDENT POSTER SESSION **:
---------------------------
The conference solicits student posters that highlight recent and on-going
research by students on mobile computing topics. Proposals should be a
maximum of two pages in length. While it does not need to describe completed
work,
the poster paper should report on research that is beyond the initial
stages.
The first author of a poster submission must be a student. Poster abstracts
will not be published in the proceedings but will instead be published on
the web
before the conference.  Poster submissions will be reviewed. Authors of
accepted papers
must not submit a poster of the work they present in the conference. For
more information about
student poster applications contact the Student Poster Co-chairs
(ebelding@cs.ucsb.edu or sjlee@hpl.hp.com).

**STUDENT TRAVEL AWARDS**:
--------------------------
MobiCom will offer a limited number of travel grants to support students.
Please contact Student Travel Awards Co-Chairs for application details
(fang@ece.ufl.edu or syrotiuk@utdallas.edu).


BEST STUDENT PAPER AWARD:
-------------------------
Papers with a student as the primary author will be considered
for the Best Student Paper Award with a cash award of $1,000 USD. Students
must indicate with their submissions that they would like to be considered
for this award.

IMPORTANT DATES:
----------------
*  Paper submissions due: March 8, 2002
*  Notification of acceptance: June 30, 2002
*  Camera-ready version due: July 31, 2002
*  Tutorial proposals: May 1, 2002

FOR MORE INFORMATION: Check the conference website or send
email to mobicom2002@comet.columbia.edu


EXECUTIVE COMMITTEE:
--------------------
* General Chair: Ian F. Akyildiz, Georgia Institute of Technology

* General Vice-Chairs:
   - Jason Y. B. Lin, National Chiao Tung University
   - Ravi Jain, Telcordia

* Program Co-Chairs:
   - Vaduvur Bharghavan, Bessemer Venture Partners
   - Andrew T. Campbell, Columbia University

* Panels Co-Chairs:
   - Ness Shroff, Purdue University
   - Marie-Jose Montpetit, Nokia

* Tutorials Co-Chairs:
   - Catherine Rosenberg, Purdue University
   - Nitin Vaidya, University of Illinois at Urbana Champaign

* Steering Committee Chair: Imrich Chlamtac, University of Texas at Dallas

* Publicity Co-Chairs:
   - Chuanyi Ji, Georgia Institute of Technology
   - Marwan M. Krunz, University of Arizona

* Workshop Co-Chairs:
   - Taieb Znati, NSF and University of Pittsburgh
   - Mehmet Ulema, Mercury Corporation

* Research Demos Chair: Ron Hutchins, Georgia Institute of Technology

* Finance Chair: Edward Knightly, Rice University

* Registration Co-Chairs:
   - Suresh Singh, Portland State University
   - Robin Kravets, University of Illinois, Urbana-Champaign

* Student Poster Co-Chairs:
   - Elizabeth M. Belding-Royer, University of California, Santa Barbara
   - Sung-Ju Lee, HP Laboratories

* Student Travel Award Co-Chairs:
  - Yuguang Fang, University of Florida
  - Violet R. Syrotiuk, University of Texas at Dallas


* Sponsorship/Exhibit Chair: Ramesh Govindan, Univ. of Southern California

* Local Arrangements Chair: Raghupathy Sivakumar: Georgia Institute of
Technology

* Webmaster: Michael E. Kounavis, Columbia University

PROGRAM COMMITTEE:
--------------------

Program Co-Chairs:

 - Vaduvur Bharghavan, Bessemer Venture Partners
 - Andrew T. Campbell, Columbia University

Program Committee:

- Arup Acharya, IBM Research
- Prathima Agrawal, Telcordia
- B. R. Badrinath, Rutgers University
- Victor Bahl, Microsoft Research
- Stefano Basagni, Northeastern University
- Roberto Battiti, University of Trento
- Pravin Bhagwat, ReefEdge
- Chatschik Bisdikian, IBM Research
- Scott Corson, Flarion
- Sajal Das, University Texas at Arlington
- Nigel Davies, Lancaster University
- Dan Duchamp, Stevens Institute of Technology
- Maria Ebling, IBM Research
- Magda El-Zarki, University of California, Irvine
- Anthony Ephremides, University of Maryland
- Deborah Estrin, University of California, Los Angeles
- J.J. Garcia-Luna-Aceves, University of California at Santa Cruz
- Mario Gerla, University of California, Los Angeles
- Ramesh Govindan, USC/ISI
- Ravi Jain, Telcordia
- David B. Johnson, Rice University
- Anthony Joseph, University of California, Berkeley
- Edward Knightly, Rice University
- Tom LaPorta, Lucent Technologies
- Songwu Lu, University of California, Los Angeles
- Robert Morris, MIT
- S. Muthukrishnan, AT&T Research
- Brian Noble, University of Michigan
- Venkat Padmanabhan, Microsoft Research
- Charles Perkins, Nokia
- Chiara Petrioli, University "La Sapienza"
- George Polyzos, Athens University of Economics and Business
- Parmesh Ramanathan, University of Wisconsin - Madison
- Ram Ramanathan, BBN Technologies
- Ramachandran Ramjee, Lucent Technologies
- Daniela Rus, Dartmouth College
- Srinivasan Seshan, Carnegie Mellon University
- Kang G. Shin, University of Michigan
- Suresh Singh, Portland State University
- Mani Srivastava, University of California, Los Angeles
- Frank Stajano, AT&T Laboratories Cambridge
- Martha Steenstrup, Stow Research
- Violet R. Syrotiuk, University of Texas at Dallas
- Leandros Tassiulas, University of Maryland
- Nitin H. Vaidya, University of Illinois at Urbana-Champaign
- Andras Valko, Ericsson Research
- Adam Wolisz, Technical University of Berlin
- Michele Zorzi, Universita di Ferrara


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


From daemon@optimus.ietf.org  Mon Mar  4 21:20:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04399
	for <manet-archive@odin.ietf.org>; Mon, 4 Mar 2002 21:20:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA18729
	for manet-archive@odin.ietf.org; Mon, 4 Mar 2002 21:20:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA17131;
	Mon, 4 Mar 2002 20:49:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA17100
	for <manet@optimus.ietf.org>; Mon, 4 Mar 2002 20:49:48 -0500 (EST)
Received: from tiquini.ece.arizona.edu (tiquini.ece.arizona.edu [128.196.29.23])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03607
	for <manet@ietf.org>; Mon, 4 Mar 2002 20:49:44 -0500 (EST)
Received: from krunz (ECE-DHCP-108.ece.arizona.edu [128.196.237.108])
	by tiquini.ece.arizona.edu (8.12.1/8.12.1) with SMTP id g251nigD012367
	for <manet@ietf.org>; Mon, 4 Mar 2002 18:49:45 -0700 (MST)
Reply-To: <krunz@ece.arizona.edu>
From: "Marwan M. Krunz" <krunz@ece.arizona.edu>
To: <manet@ietf.org>
Date: Mon, 4 Mar 2002 18:49:45 -0700
Message-ID: <NEBBICAGBCIDDLGKBHAIOENECFAA.krunz@ece.arizona.edu>
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 IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Content-Transfer-Encoding: 7bit
Subject: [manet] Mobicom 2002 - Final CFP
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit




***************************************************************
[Appologies if you receive duplicates of this message]

Please note the following changes in this CFP:
- Paper submission details have been revised.
- A Student Poster Session has been added.
- Student travel grants are now available.

See below for details.
***************************************************************


              F I N A L   C A L L   F O R   P A P E R S

                   *** ACM MobiCom 2002 ***
The Eighth Annual International Conference on Mobile Computing and
Networking

                    September 23-26, 2002
                    Westin Peachtree Plaza
                    Atlanta, Georgia, USA

              http://www.acm.org/sigmobile/mobicom/2002/


                 Sponsored by ACM SIGMOBILE

     Paper Submission Deadline (EXTENDED): March 8, 2002

  ******** No further extensions will be given *********


MobiCom 2002 is the eighth annual conference dedicated to addressing new
challenges in mobile computing and networking. MobiCom 2002 solicits papers
describing significant research contributions to the field of mobile
computing and networking.

PAPERS:
-------
Authors are invited to submit full papers related to the theory and practice
of mobile computing and networking. Original research papers (that are not
currently under review by another conference or journal) are solicited.
Areas of interest include, but not limited to:

* Applications and computing services supporting mobile users
* Architectures, protocols, and algorithms to cope with mobility, limited
  bandwidth, or intermittent connectivity
* Database and data management issues in mobile computing
* Performance of mobile/wireless networks and systems
* Security and privacy of mobile/wireless systems
* Interaction between different layers of mobile/wireless systems
* Integration and interworking of wired and wireless networks
* Adaptive applications and systems for mobile environments
* Distributed-system aspects of mobile systems
* Operating system support for mobility
* Location-dependent applications
* Wireless multimedia systems
* Power management
* Mobile agents
* Pervasive computing
* Wireless sensor networks
* Wireless/mobile service management and delivery

All papers will be refereed by the program committee. Accepted papers will
be published in the conference proceedings.

Papers of particular merit will be proposed for publication in the
ACM/Kluwer Wireless Networks (WINET) and
Mobile Networks and Applications (MONET) journals.

CHALLENGES SESSION:
------------------
Short papers (maximum of 8 pages) that challenge the mobile computing
community with new technologies or visionary applications are solicited.
Such papers should provide stimulating ideas or visions that may open up
exciting avenues of mobile computing research. Papers will be reviewed
and should be submitted using the normal submission procedure.
Submitted papers should be clearly identified as intended for the
Challenges Session.

**REVISED SUBMISSION INSTRUCTIONS**:
------------------------------------
All paper submissions will be handled electronically. Authors should prepare
a PostScript or Portable Document Format (PDF) version of their paper. No
other format will be accepted.

Papers must meet the following restrictions:

-  The paper must be original material that has not been previously
   published nor is currently under review by another conference or journal.
-  Full papers should be no longer than *15 pages*, in font no smaller than
   10 points. (Note that accepted papers, when formatted for the
   proceedings, may not exceed 12 pages in font no smaller than 9 points).
-  Challenges papers should be no longer than 8 pages, in font no smaller
   than 10 points.
-  All submitted papers will be judged based on their quality through
   double-blind reviewing, where the identities of the authors are withheld
   from the reviewers. Authors' names *must not* appear in the paper.
-  The paper should fit properly on US Letter-sized paper (8.5x11 inches)
-  PostScript version 2 or later, or Portable Document Format (PDF)
-  Use only Computer Modern or standard Adobe printer fonts (i.e., Courier,
   Times, Roman, or Helvetica)
-  Other fonts may be used, but must be included in the PostScript/PDF file
-  The paper must be formatted for b/w printers and not color printers.

Instructions for submission are available at:
http://www.acm.org/sigmobile/mobicom/2002/submissions/


TUTORIALS:
----------
Proposals for tutorials are solicited, and will be evaluated based on
the expertise of the instructors and the relevance of the subject matter.
Potential instructors should submit a tutorial proposal of at
most five pages, including a biographical sketch, to the Tutorial
Co-chairs (cath@ecn.purdue.edu or nhv@crhc.uiuc.edu).

PANELS:
-------
Proposals are solicited for panels that examine innovative, controversial,
or otherwise provocative issues of interest. Panel proposals should
not exceed 3 pages, including biographical sketches of the panelists.
Potential panel organizers should contact the Panel Co-chairs
(shroff@ecn.purdue.edu or marie-jose.montpetit@nokia.com).

RESEARCH DEMOS:
---------------
Proposals for research demos are solicited. Proposals should not exceed 3
pages and should include a description of the demo and equipment that
will be used. Proposals for demos should be sent to the Research Demo
Chair (ron@oit.gatech.edu).

** STUDENT POSTER SESSION **:
---------------------------
The conference solicits student posters that highlight recent and on-going
research by students on mobile computing topics. Proposals should be a
maximum of two pages in length. While it does not need to describe completed
work,
the poster paper should report on research that is beyond the initial
stages.
The first author of a poster submission must be a student. Poster abstracts
will not be published in the proceedings but will instead be published on
the web
before the conference.  Poster submissions will be reviewed. Authors of
accepted papers
must not submit a poster of the work they present in the conference. For
more information about
student poster applications contact the Student Poster Co-chairs
(ebelding@cs.ucsb.edu or sjlee@hpl.hp.com).

**STUDENT TRAVEL AWARDS**:
--------------------------
MobiCom will offer a limited number of travel grants to support students.
Please contact Student Travel Awards Co-Chairs for application details
(fang@ece.ufl.edu or syrotiuk@utdallas.edu).


BEST STUDENT PAPER AWARD:
-------------------------
Papers with a student as the primary author will be considered
for the Best Student Paper Award with a cash award of $1,000 USD. Students
must indicate with their submissions that they would like to be considered
for this award.

IMPORTANT DATES:
----------------
*  Paper submissions due: March 8, 2002
*  Notification of acceptance: June 30, 2002
*  Camera-ready version due: July 31, 2002
*  Tutorial proposals: May 1, 2002

FOR MORE INFORMATION: Check the conference website or send
email to mobicom2002@comet.columbia.edu


EXECUTIVE COMMITTEE:
--------------------
* General Chair: Ian F. Akyildiz, Georgia Institute of Technology

* General Vice-Chairs:
   - Jason Y. B. Lin, National Chiao Tung University
   - Ravi Jain, Telcordia

* Program Co-Chairs:
   - Vaduvur Bharghavan, Bessemer Venture Partners
   - Andrew T. Campbell, Columbia University

* Panels Co-Chairs:
   - Ness Shroff, Purdue University
   - Marie-Jose Montpetit, Nokia

* Tutorials Co-Chairs:
   - Catherine Rosenberg, Purdue University
   - Nitin Vaidya, University of Illinois at Urbana Champaign

* Steering Committee Chair: Imrich Chlamtac, University of Texas at Dallas

* Publicity Co-Chairs:
   - Chuanyi Ji, Georgia Institute of Technology
   - Marwan M. Krunz, University of Arizona

* Workshop Co-Chairs:
   - Taieb Znati, NSF and University of Pittsburgh
   - Mehmet Ulema, Mercury Corporation

* Research Demos Chair: Ron Hutchins, Georgia Institute of Technology

* Finance Chair: Edward Knightly, Rice University

* Registration Co-Chairs:
   - Suresh Singh, Portland State University
   - Robin Kravets, University of Illinois, Urbana-Champaign

* Student Poster Co-Chairs:
   - Elizabeth M. Belding-Royer, University of California, Santa Barbara
   - Sung-Ju Lee, HP Laboratories

* Student Travel Award Co-Chairs:
  - Yuguang Fang, University of Florida
  - Violet R. Syrotiuk, University of Texas at Dallas


* Sponsorship/Exhibit Chair: Ramesh Govindan, Univ. of Southern California

* Local Arrangements Chair: Raghupathy Sivakumar: Georgia Institute of
Technology

* Webmaster: Michael E. Kounavis, Columbia University

PROGRAM COMMITTEE:
--------------------

Program Co-Chairs:

 - Vaduvur Bharghavan, Bessemer Venture Partners
 - Andrew T. Campbell, Columbia University

Program Committee:

- Arup Acharya, IBM Research
- Prathima Agrawal, Telcordia
- B. R. Badrinath, Rutgers University
- Victor Bahl, Microsoft Research
- Stefano Basagni, Northeastern University
- Roberto Battiti, University of Trento
- Pravin Bhagwat, ReefEdge
- Chatschik Bisdikian, IBM Research
- Scott Corson, Flarion
- Sajal Das, University Texas at Arlington
- Nigel Davies, Lancaster University
- Dan Duchamp, Stevens Institute of Technology
- Maria Ebling, IBM Research
- Magda El-Zarki, University of California, Irvine
- Anthony Ephremides, University of Maryland
- Deborah Estrin, University of California, Los Angeles
- J.J. Garcia-Luna-Aceves, University of California at Santa Cruz
- Mario Gerla, University of California, Los Angeles
- Ramesh Govindan, USC/ISI
- Ravi Jain, Telcordia
- David B. Johnson, Rice University
- Anthony Joseph, University of California, Berkeley
- Edward Knightly, Rice University
- Tom LaPorta, Lucent Technologies
- Songwu Lu, University of California, Los Angeles
- Robert Morris, MIT
- S. Muthukrishnan, AT&T Research
- Brian Noble, University of Michigan
- Venkat Padmanabhan, Microsoft Research
- Charles Perkins, Nokia
- Chiara Petrioli, University "La Sapienza"
- George Polyzos, Athens University of Economics and Business
- Parmesh Ramanathan, University of Wisconsin - Madison
- Ram Ramanathan, BBN Technologies
- Ramachandran Ramjee, Lucent Technologies
- Daniela Rus, Dartmouth College
- Srinivasan Seshan, Carnegie Mellon University
- Kang G. Shin, University of Michigan
- Suresh Singh, Portland State University
- Mani Srivastava, University of California, Los Angeles
- Frank Stajano, AT&T Laboratories Cambridge
- Martha Steenstrup, Stow Research
- Violet R. Syrotiuk, University of Texas at Dallas
- Leandros Tassiulas, University of Maryland
- Nitin H. Vaidya, University of Illinois at Urbana-Champaign
- Andras Valko, Ericsson Research
- Adam Wolisz, Technical University of Berlin
- Michele Zorzi, Universita di Ferrara


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



From manet-admin@ietf.org  Tue Mar  5 01:29:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10652
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 01:29:16 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA00017;
	Tue, 5 Mar 2002 01:01:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA29977
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 01:01:00 -0500 (EST)
Received: from omail01.samsung.co.kr (omail01.samsung.co.kr [203.254.197.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10263
	for <manet@ietf.org>; Tue, 5 Mar 2002 01:00:58 -0500 (EST)
From: mschoe@samsung.co.kr
Received: from localhost (root@localhost)
	by gp_yman.sdsosc.co.kr (8.8.8H1/8.8.8) with ESMTP id OAA28505
	for <manet@ietf.org>; Tue, 5 Mar 2002 14:58:37 +0900 (KST)
X-OpenMail-Hops: 2
Date: Tue, 5 Mar 2002 15:00:20 +0900
Message-Id: <H0000297084c6a31.1015306901.seckm1@MHS>
MIME-Version: 1.0
TO: manet@ietf.org
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
	;Creation-Date="Tue, 5 Mar 2002 14:41:41 +0900"
	;Modification-Date="Tue, 5 Mar 2002 15:00:19 +0900"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [manet] Please help.
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

I've read an LANDMAR protocol (draft, Dec. 17, 2001) draft recently.
I am so curious about why the sequence number is increased by two in which is specified at 6.3.1 and 6.4.1.
If you know the reason, would you please kindly let me know it?

Thanks in advance.

-
Myongsu.


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


From daemon@optimus.ietf.org  Tue Mar  5 01:29:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10662
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 01:29:16 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id BAA11145
	for manet-archive@odin.ietf.org; Tue, 5 Mar 2002 01:29:17 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA00017;
	Tue, 5 Mar 2002 01:01:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA29977
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 01:01:00 -0500 (EST)
Received: from omail01.samsung.co.kr (omail01.samsung.co.kr [203.254.197.168])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10263
	for <manet@ietf.org>; Tue, 5 Mar 2002 01:00:58 -0500 (EST)
From: mschoe@samsung.co.kr
Received: from localhost (root@localhost)
	by gp_yman.sdsosc.co.kr (8.8.8H1/8.8.8) with ESMTP id OAA28505
	for <manet@ietf.org>; Tue, 5 Mar 2002 14:58:37 +0900 (KST)
X-OpenMail-Hops: 2
Date: Tue, 5 Mar 2002 15:00:20 +0900
Message-Id: <H0000297084c6a31.1015306901.seckm1@MHS>
MIME-Version: 1.0
TO: manet@ietf.org
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
	;Creation-Date="Tue, 5 Mar 2002 14:41:41 +0900"
	;Modification-Date="Tue, 5 Mar 2002 15:00:19 +0900"
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [manet] Please help.
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

I've read an LANDMAR protocol (draft, Dec. 17, 2001) draft recently.
I am so curious about why the sequence number is increased by two in which is specified at 6.3.1 and 6.4.1.
If you know the reason, would you please kindly let me know it?

Thanks in advance.

-
Myongsu.


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



From manet-admin@ietf.org  Tue Mar  5 04:11:10 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21512
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 04:11:10 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA17784;
	Tue, 5 Mar 2002 03:47:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA17753
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 03:46:57 -0500 (EST)
Received: from mailhost.cs.auc.dk (root@mailhost.cs.auc.dk [130.225.194.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21176
	for <manet@ietf.org>; Tue, 5 Mar 2002 03:46:53 -0500 (EST)
From: T.Clausen@computer.org
Received: from localhost (root@borg.cs.auc.dk [130.225.194.22])
	by mailhost.cs.auc.dk (8.12.2/8.12.2) with ESMTP id g258kovU025181;
	Tue, 5 Mar 2002 09:46:50 +0100 (MET)
Date: Tue, 5 Mar 2002 09:46:49 +0100 (CET)
X-Sender: voop@armada
To: ogier@erg.sri.com, manet@ietf.org
In-Reply-To: <200203050011.QAA29535@pit.erg.sri.com>
Message-ID: <Pine.LNX.4.21.0203050941310.401-100000@armada>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-Scanned-By: MIMEDefang 2.2
Content-Transfer-Encoding: 8BIT
Subject: [manet] Re: Some follow-up OLSR/AODV results
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8BIT

Richard,

On Mon, 4 Mar 2002 ogier@erg.sri.com wrote:

> 
> Thomas,
> 
> > Richard,
> > 
> > Thanks for looking at our simulation code for OLSR in detail. You are
> > correct in pointing out the bug in the simulation code, and your proposed
> > solution seems to solve the problem.
> > 
> > Our belated reply is due to the fact that we wanted to investigate the
> > impact of the bug before replying.
> > 
> > We have been running a set of tests, similar to those presented earlier by
> > Joe (http://protean.itd.nrl.navy.mil/manet/olsrstatic.pdf) of the
> > simulation code "with the bug" and "without the bug". 
> > 
> > Exactly the same scenarios being used, our observations basically amount
> > to the following:
> > 
> > 	- the reported overhead (in bytes/sec) indeed is about 50% larger
> > 	  with the "bugfix"
> 
> I guess you are talking about total control traffic, including RTS/CTS packets
> that are used for data packets.  For just routing control traffic, I found
> that the reported overhead is between 90% and 120% larger with the bug fix,
> depending on the scenario.

The control traffic, generated by OLSR, is broadcast. Hence, no RTS/CTS
packets are being exchanged (nor accounted).

Besides, the overhead we've accounted is overhead at the MAC layer (i.e.:
that, which is actually transmitted onto the medium), originating from
transmission of OLSR control packets. This is, indeed, consistently about
50% larger with the "bugfix" on the large selection of scenarios we've
been testing.

-- 

-------------------------------------------
  Thomas Heide Clausen
  Civilingeniør i Datateknik (cand.polyt)
  M.Sc in Computer Engineering

  E-Mail: T.Clausen@computer.org
  WWW:    http://www.cs.auc.dk/~voop
-------------------------------------------


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


From daemon@optimus.ietf.org  Tue Mar  5 04:11:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21522
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 04:11:10 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA19290
	for manet-archive@odin.ietf.org; Tue, 5 Mar 2002 04:11:12 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA17784;
	Tue, 5 Mar 2002 03:47:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA17753
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 03:46:57 -0500 (EST)
Received: from mailhost.cs.auc.dk (root@mailhost.cs.auc.dk [130.225.194.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21176
	for <manet@ietf.org>; Tue, 5 Mar 2002 03:46:53 -0500 (EST)
From: T.Clausen@computer.org
Received: from localhost (root@borg.cs.auc.dk [130.225.194.22])
	by mailhost.cs.auc.dk (8.12.2/8.12.2) with ESMTP id g258kovU025181;
	Tue, 5 Mar 2002 09:46:50 +0100 (MET)
Date: Tue, 5 Mar 2002 09:46:49 +0100 (CET)
X-Sender: voop@armada
To: ogier@erg.sri.com, manet@ietf.org
In-Reply-To: <200203050011.QAA29535@pit.erg.sri.com>
Message-ID: <Pine.LNX.4.21.0203050941310.401-100000@armada>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-Scanned-By: MIMEDefang 2.2
Content-Transfer-Encoding: 8BIT
Subject: [manet] Re: Some follow-up OLSR/AODV results
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8BIT

Richard,

On Mon, 4 Mar 2002 ogier@erg.sri.com wrote:

> 
> Thomas,
> 
> > Richard,
> > 
> > Thanks for looking at our simulation code for OLSR in detail. You are
> > correct in pointing out the bug in the simulation code, and your proposed
> > solution seems to solve the problem.
> > 
> > Our belated reply is due to the fact that we wanted to investigate the
> > impact of the bug before replying.
> > 
> > We have been running a set of tests, similar to those presented earlier by
> > Joe (http://protean.itd.nrl.navy.mil/manet/olsrstatic.pdf) of the
> > simulation code "with the bug" and "without the bug". 
> > 
> > Exactly the same scenarios being used, our observations basically amount
> > to the following:
> > 
> > 	- the reported overhead (in bytes/sec) indeed is about 50% larger
> > 	  with the "bugfix"
> 
> I guess you are talking about total control traffic, including RTS/CTS packets
> that are used for data packets.  For just routing control traffic, I found
> that the reported overhead is between 90% and 120% larger with the bug fix,
> depending on the scenario.

The control traffic, generated by OLSR, is broadcast. Hence, no RTS/CTS
packets are being exchanged (nor accounted).

Besides, the overhead we've accounted is overhead at the MAC layer (i.e.:
that, which is actually transmitted onto the medium), originating from
transmission of OLSR control packets. This is, indeed, consistently about
50% larger with the "bugfix" on the large selection of scenarios we've
been testing.

-- 

-------------------------------------------
  Thomas Heide Clausen
  Civilingeniør i Datateknik (cand.polyt)
  M.Sc in Computer Engineering

  E-Mail: T.Clausen@computer.org
  WWW:    http://www.cs.auc.dk/~voop
-------------------------------------------


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



From manet-admin@ietf.org  Tue Mar  5 05:00:01 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22241
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 05:00:01 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21198;
	Tue, 5 Mar 2002 04:41:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21167
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 04:41:44 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21942
	for <manet@ietf.org>; Tue, 5 Mar 2002 04:41:40 -0500 (EST)
Received: from impression.inria.fr (impression.inria.fr [128.93.17.98])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g259fTf02887;
	Tue, 5 Mar 2002 10:41:29 +0100 (MET)
Received: by impression.inria.fr (sSMTP sendmail emulation); Tue, 5 Mar 2002 10:41:29 +0100
From: Laurent Viennot <Laurent.Viennot@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15492.37577.638149.893527@impression.inria.fr>
Date: Tue, 5 Mar 2002 10:41:29 +0100
To: Fred Baker <fred@cisco.com>, vikas p verma <vvicky72@rediffmail.com>,
        Javier Gomez-Castellanos <javierg@ee.columbia.edu>, ogier@erg.sri.com,
        manet@ietf.org
Subject: [manet] Re: Costs on links in MANET routing protocol
In-Reply-To: <200203041811.KAA28830@pit.erg.sri.com>
References: <4.3.2.7.2.20020225171131.02427f88@mira-sjcm-2.cisco.com>
	<200203041811.KAA28830@pit.erg.sri.com>
X-Mailer: VM 6.92 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Reply-To: Laurent.Viennot@inria.fr
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


Concerning costs on links, I would argue that the situation is very
different from classical link state. Indeed, with radio media, two
different links may interact. Consider for example links A--B and
C--D where each of A,B,C,D can hear each other. If you want your cost
to reflect the available bandwidth then a cost per link is not very
meaningful.

We have already thought about introducing costs in OLSR, there are
simple ways to do that. One of our conclusion considering the above
remark is that putting costs on links is not always meaningful. A
better choice would be to put a cost on interfaces (to reflect for
example the medium utilization around the interface or the power
available on the node).


Two remarks about using power level information :

Considering power saving paths, recall that you may gain on the
emission of packets but the reception is also very costly. A node
consumes power when listening (even when non packet is received).  A
better way of saving power seems to allow nodes to go in sleep mode
from time to time.

Concerning the use of S/N ratio as a cost on links, it seems to me a
heavy solution where a simple link hysteresis is sufficient. Under a
certain threshold, the link is not usable and above a certain
threshold the link will work fine independently from the S/N ratio. So
the matter with the use of S/N information is more to select correct
links than using S/N ratio as a cost function.


laurent


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


From daemon@optimus.ietf.org  Tue Mar  5 05:00:02 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22251
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 05:00:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA22001
	for manet-archive@odin.ietf.org; Tue, 5 Mar 2002 05:00:04 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21198;
	Tue, 5 Mar 2002 04:41:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21167
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 04:41:44 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21942
	for <manet@ietf.org>; Tue, 5 Mar 2002 04:41:40 -0500 (EST)
Received: from impression.inria.fr (impression.inria.fr [128.93.17.98])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g259fTf02887;
	Tue, 5 Mar 2002 10:41:29 +0100 (MET)
Received: by impression.inria.fr (sSMTP sendmail emulation); Tue, 5 Mar 2002 10:41:29 +0100
From: Laurent Viennot <Laurent.Viennot@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15492.37577.638149.893527@impression.inria.fr>
Date: Tue, 5 Mar 2002 10:41:29 +0100
To: Fred Baker <fred@cisco.com>, vikas p verma <vvicky72@rediffmail.com>,
        Javier Gomez-Castellanos <javierg@ee.columbia.edu>, ogier@erg.sri.com,
        manet@ietf.org
Subject: [manet] Re: Costs on links in MANET routing protocol
In-Reply-To: <200203041811.KAA28830@pit.erg.sri.com>
References: <4.3.2.7.2.20020225171131.02427f88@mira-sjcm-2.cisco.com>
	<200203041811.KAA28830@pit.erg.sri.com>
X-Mailer: VM 6.92 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Reply-To: Laurent.Viennot@inria.fr
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


Concerning costs on links, I would argue that the situation is very
different from classical link state. Indeed, with radio media, two
different links may interact. Consider for example links A--B and
C--D where each of A,B,C,D can hear each other. If you want your cost
to reflect the available bandwidth then a cost per link is not very
meaningful.

We have already thought about introducing costs in OLSR, there are
simple ways to do that. One of our conclusion considering the above
remark is that putting costs on links is not always meaningful. A
better choice would be to put a cost on interfaces (to reflect for
example the medium utilization around the interface or the power
available on the node).


Two remarks about using power level information :

Considering power saving paths, recall that you may gain on the
emission of packets but the reception is also very costly. A node
consumes power when listening (even when non packet is received).  A
better way of saving power seems to allow nodes to go in sleep mode
from time to time.

Concerning the use of S/N ratio as a cost on links, it seems to me a
heavy solution where a simple link hysteresis is sufficient. Under a
certain threshold, the link is not usable and above a certain
threshold the link will work fine independently from the S/N ratio. So
the matter with the use of S/N information is more to select correct
links than using S/N ratio as a cost function.


laurent


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



From manet-admin@ietf.org  Tue Mar  5 06:16:43 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23134
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 06:16:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA24295;
	Tue, 5 Mar 2002 05:49:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA24265
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 05:49:00 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22804
	for <manet@ietf.org>; Tue, 5 Mar 2002 05:48:56 -0500 (EST)
Received: from zephyrin (zephyrin-wi.inria.fr [193.51.192.58])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g25Amxf11583
	for <manet@ietf.org>; Tue, 5 Mar 2002 11:48:59 +0100 (MET)
Message-ID: <003801c1c436$121c30c0$3ac033c1@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203041811.KAA28830@pit.erg.sri.com>
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol
Date: Tue, 5 Mar 2002 12:08:24 +0100
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

I don't see the problem. It suffices that the node selects its MPR nodes on
the shortest paths (with respect to the considered metric) to its 2-hop
neighbors. This is pretty straightforward.

Philippe

----- Original Message -----
From: <ogier@erg.sri.com>
To: Fred Baker <fred@cisco.com>
Cc: <manet@ietf.org>; <ogier@erg.sri.com>
Sent: Monday, March 04, 2002 7:11 PM
Subject: [manet] Re: RE : others cretaria in MANET routing protocol
>
> P.S. I thought about the possibility of modifying OLSR so that it
> computes shortest paths w.r.t. a link metric (instead of computing
> min-hop paths subject to the quality of each link being above some
> threshold).  It is not as easy to do this in OLSR, because of the
> requirement that paths must use links (u,v) such that v selected u as
> a multipoint relay (except for the first hop).  This requirement
> severely reduces the path choices, so that the shortest path w.r.t.
> a given metric (other than the hop metric) is not likely to
> satisfy this requirement.
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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


From daemon@optimus.ietf.org  Tue Mar  5 06:16:43 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23145
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 06:16:43 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id GAA25830
	for manet-archive@odin.ietf.org; Tue, 5 Mar 2002 06:16:46 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA24295;
	Tue, 5 Mar 2002 05:49:03 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA24265
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 05:49:00 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22804
	for <manet@ietf.org>; Tue, 5 Mar 2002 05:48:56 -0500 (EST)
Received: from zephyrin (zephyrin-wi.inria.fr [193.51.192.58])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g25Amxf11583
	for <manet@ietf.org>; Tue, 5 Mar 2002 11:48:59 +0100 (MET)
Message-ID: <003801c1c436$121c30c0$3ac033c1@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203041811.KAA28830@pit.erg.sri.com>
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol
Date: Tue, 5 Mar 2002 12:08:24 +0100
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

I don't see the problem. It suffices that the node selects its MPR nodes on
the shortest paths (with respect to the considered metric) to its 2-hop
neighbors. This is pretty straightforward.

Philippe

----- Original Message -----
From: <ogier@erg.sri.com>
To: Fred Baker <fred@cisco.com>
Cc: <manet@ietf.org>; <ogier@erg.sri.com>
Sent: Monday, March 04, 2002 7:11 PM
Subject: [manet] Re: RE : others cretaria in MANET routing protocol
>
> P.S. I thought about the possibility of modifying OLSR so that it
> computes shortest paths w.r.t. a link metric (instead of computing
> min-hop paths subject to the quality of each link being above some
> threshold).  It is not as easy to do this in OLSR, because of the
> requirement that paths must use links (u,v) such that v selected u as
> a multipoint relay (except for the first hop).  This requirement
> severely reduces the path choices, so that the shortest path w.r.t.
> a given metric (other than the hop metric) is not likely to
> satisfy this requirement.
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Tue Mar  5 10:51:33 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05528
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 10:51:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09392;
	Tue, 5 Mar 2002 10:13:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09360
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 10:13:21 -0500 (EST)
Received: from gemini.ncnu.edu.tw (gemini.ncnu.edu.tw [163.22.2.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03871
	for <manet@ietf.org>; Tue, 5 Mar 2002 10:13:11 -0500 (EST)
Received: from yuwei (ip079.puli22.ncnu.edu.tw [163.22.22.79])
	by gemini.ncnu.edu.tw (8.11.1/8.11.1) with SMTP id g25FCKq11072
	for <manet@ietf.org>; Tue, 5 Mar 2002 23:12:20 +0800 (CST)
Message-ID: <007c01c1c457$c87193d0$4f1616a3@yuwei>
From: "Yuwei" <s8213521@ncnu.edu.tw>
To: <manet@ietf.org>
Date: Tue, 5 Mar 2002 23:09:44 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] Ns-2 Implementation of Signal Stability based Adaptive Routing Protocol
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Hello,

 I am a National Chi Nan University student.I want to ask
some questions. How to implement SSA routing protocol using ns-2? Is the SSA
source code for using in ns-2 available?
Thank you very much!!


Best Regards
Yu-Wei Hua



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


From daemon@optimus.ietf.org  Tue Mar  5 10:51:33 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05538
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 10:51:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA11988
	for manet-archive@odin.ietf.org; Tue, 5 Mar 2002 10:51:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09392;
	Tue, 5 Mar 2002 10:13:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA09360
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 10:13:21 -0500 (EST)
Received: from gemini.ncnu.edu.tw (gemini.ncnu.edu.tw [163.22.2.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03871
	for <manet@ietf.org>; Tue, 5 Mar 2002 10:13:11 -0500 (EST)
Received: from yuwei (ip079.puli22.ncnu.edu.tw [163.22.22.79])
	by gemini.ncnu.edu.tw (8.11.1/8.11.1) with SMTP id g25FCKq11072
	for <manet@ietf.org>; Tue, 5 Mar 2002 23:12:20 +0800 (CST)
Message-ID: <007c01c1c457$c87193d0$4f1616a3@yuwei>
From: "Yuwei" <s8213521@ncnu.edu.tw>
To: <manet@ietf.org>
Date: Tue, 5 Mar 2002 23:09:44 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="big5"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] Ns-2 Implementation of Signal Stability based Adaptive Routing Protocol
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Hello,

 I am a National Chi Nan University student.I want to ask
some questions. How to implement SSA routing protocol using ns-2? Is the SSA
source code for using in ns-2 available?
Thank you very much!!


Best Regards
Yu-Wei Hua



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



From manet-admin@ietf.org  Tue Mar  5 13:17:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13931
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 13:17:52 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20590;
	Tue, 5 Mar 2002 12:53:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20380
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 12:53:33 -0500 (EST)
Received: from cheetah.cs.ucla.edu (Cheetah.CS.UCLA.EDU [131.179.128.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12062
	for <manet@ietf.org>; Tue, 5 Mar 2002 12:52:18 -0500 (EST)
Received: from localhost (hxy@localhost)
	by cheetah.cs.ucla.edu (8.10.2+Sun/8.10.2/UCLACS-5.1) with ESMTP id g25Hpst02954;
	Tue, 5 Mar 2002 09:51:54 -0800 (PST)
Date: Tue, 5 Mar 2002 09:51:54 -0800 (PST)
From: Xiaoyan Hong <hxy@CS.UCLA.EDU>
To: <mschoe@samsung.co.kr>
cc: Dr Mario Gerla <gerla@CS.UCLA.EDU>, Xiaoyan Hong <hxy@CS.UCLA.EDU>,
        <manet@ietf.org>
Subject: Re: [manet] Please help.
In-Reply-To: <H0000297084c6a31.1015306901.seckm1@MHS>
Message-ID: <Pine.SOL.4.33.0203050942310.23427-100000@cheetah.cs.ucla.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi, Myongsu,

The way LANMAR using the sequence number follows DSDV, i.e., for
an update from a source, the sequence number is increased by two. Other
nodes when finding a landmark failure or a link break, increase the
sequence number by 1.  In this case, a link break message can be
propagated and the update from the source can replace any old entries.
Let me know if you have further questions.

Thanks,

Xiaoyan
On Tue, 5 Mar 2002 mschoe@samsung.co.kr wrote:

> Hi,
>
> I've read an LANDMAR protocol (draft, Dec. 17, 2001) draft recently.
> I am so curious about why the sequence number is increased by two in
which is specified at 6.3.1 and 6.4.1.
> If you know the reason, would you please kindly let me know it?
>
> Thanks in advance.
>
> -
> Myongsu.
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>


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


From daemon@optimus.ietf.org  Tue Mar  5 13:17:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13942
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 13:17:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA23747
	for manet-archive@odin.ietf.org; Tue, 5 Mar 2002 13:17:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20590;
	Tue, 5 Mar 2002 12:53:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA20380
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 12:53:33 -0500 (EST)
Received: from cheetah.cs.ucla.edu (Cheetah.CS.UCLA.EDU [131.179.128.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12062
	for <manet@ietf.org>; Tue, 5 Mar 2002 12:52:18 -0500 (EST)
Received: from localhost (hxy@localhost)
	by cheetah.cs.ucla.edu (8.10.2+Sun/8.10.2/UCLACS-5.1) with ESMTP id g25Hpst02954;
	Tue, 5 Mar 2002 09:51:54 -0800 (PST)
Date: Tue, 5 Mar 2002 09:51:54 -0800 (PST)
From: Xiaoyan Hong <hxy@CS.UCLA.EDU>
To: <mschoe@samsung.co.kr>
cc: Dr Mario Gerla <gerla@CS.UCLA.EDU>, Xiaoyan Hong <hxy@CS.UCLA.EDU>,
        <manet@ietf.org>
Subject: Re: [manet] Please help.
In-Reply-To: <H0000297084c6a31.1015306901.seckm1@MHS>
Message-ID: <Pine.SOL.4.33.0203050942310.23427-100000@cheetah.cs.ucla.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi, Myongsu,

The way LANMAR using the sequence number follows DSDV, i.e., for
an update from a source, the sequence number is increased by two. Other
nodes when finding a landmark failure or a link break, increase the
sequence number by 1.  In this case, a link break message can be
propagated and the update from the source can replace any old entries.
Let me know if you have further questions.

Thanks,

Xiaoyan
On Tue, 5 Mar 2002 mschoe@samsung.co.kr wrote:

> Hi,
>
> I've read an LANDMAR protocol (draft, Dec. 17, 2001) draft recently.
> I am so curious about why the sequence number is increased by two in
which is specified at 6.3.1 and 6.4.1.
> If you know the reason, would you please kindly let me know it?
>
> Thanks in advance.
>
> -
> Myongsu.
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>


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



From manet-admin@ietf.org  Tue Mar  5 18:14:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05615
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 18:14:57 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA12003;
	Tue, 5 Mar 2002 17:45:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA11586
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 17:44:59 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04170
	for <manet@ietf.org>; Tue, 5 Mar 2002 17:44:54 -0500 (EST)
Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g25MiNg303860;
	Tue, 5 Mar 2002 17:44:23 -0500 (EST)
Received: from TNT (h80ad3776.dhcp.vt.edu [128.173.55.118])
	by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.1.0.36-EA)
	with SMTP id AAE11085;
	Tue, 5 Mar 2002 17:44:36 -0500 (EST)
Message-ID: <004b01c1c497$1522ea00$7637ad80@workgroup>
From: "Tao Lin" <taolin@vt.edu>
To: <manet@ietf.org>, <ogier@erg.sri.com>
References: <H0000297084c6a31.1015306901.seckm1@MHS>
Date: Tue, 5 Mar 2002 17:42:51 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] Question regarding robustness defnition in TBRPF
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

The TBRPF draft says  "To provide increased robustness when sufficient
bandwidth is available, ..." What does this increased robustness refer to?
Does this mean short response latency to link failures, higher throughput or
maintenance of shortes path to all destinations when the topology changes or
potentially something else? Do you have any analytical results? I would like
to see whether this idea can apply to some other protocols.

Thanks!

Tao


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


From daemon@optimus.ietf.org  Tue Mar  5 18:14:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05625
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 18:14:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA15875
	for manet-archive@odin.ietf.org; Tue, 5 Mar 2002 18:15:00 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA12003;
	Tue, 5 Mar 2002 17:45:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA11586
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 17:44:59 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04170
	for <manet@ietf.org>; Tue, 5 Mar 2002 17:44:54 -0500 (EST)
Received: from steiner.cc.vt.edu (IDENT:mirapoint@steiner-lb.cc.vt.edu [10.1.1.14])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g25MiNg303860;
	Tue, 5 Mar 2002 17:44:23 -0500 (EST)
Received: from TNT (h80ad3776.dhcp.vt.edu [128.173.55.118])
	by steiner.cc.vt.edu (Mirapoint Messaging Server MOS 3.1.0.36-EA)
	with SMTP id AAE11085;
	Tue, 5 Mar 2002 17:44:36 -0500 (EST)
Message-ID: <004b01c1c497$1522ea00$7637ad80@workgroup>
From: "Tao Lin" <taolin@vt.edu>
To: <manet@ietf.org>, <ogier@erg.sri.com>
References: <H0000297084c6a31.1015306901.seckm1@MHS>
Date: Tue, 5 Mar 2002 17:42:51 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] Question regarding robustness defnition in TBRPF
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

The TBRPF draft says  "To provide increased robustness when sufficient
bandwidth is available, ..." What does this increased robustness refer to?
Does this mean short response latency to link failures, higher throughput or
maintenance of shortes path to all destinations when the topology changes or
potentially something else? Do you have any analytical results? I would like
to see whether this idea can apply to some other protocols.

Thanks!

Tao


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



From manet-admin@ietf.org  Tue Mar  5 22:57:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14858
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 22:57:47 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA27158;
	Tue, 5 Mar 2002 22:27:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA27127
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 22:27:02 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12507
	for <manet@ietf.org>; Tue, 5 Mar 2002 22:26:58 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id TAA03447;
	Tue, 5 Mar 2002 19:25:17 -0800 (PST)
Message-Id: <200203060325.TAA03447@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
In-reply-to: Your message of "Tue, 05 Mar 2002 12:08:24 +0100."
             <003801c1c436$121c30c0$3ac033c1@inria.fr> 
Date: Tue, 05 Mar 2002 19:25:17 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


> I don't see the problem. It suffices that the node selects its MPR nodes on
> the shortest paths (with respect to the considered metric) to its 2-hop
> neighbors. This is pretty straightforward.
> 
> Philippe

Yes, I agree it is straightforward if you are willing 
to give up your heuristic that attempts to minimize the 
number of MPRs.  But then of course you will have more MPRs, 
which could increase overhead.  

Also (as you know) unless you assume that link costs are symmetric
(which is not a good assumption), each node needs to compute
the shortest path to each 2-hop neighbor using the link costs
for the *reverse* links (from the 2-hop neighbors), since 
data packets travel in the reverse direction along these paths.
This seems to require that each node report the link costs
for both its outgoing links and incoming links.

Richard


> 
> ----- Original Message -----
> From: <ogier@erg.sri.com>
> To: Fred Baker <fred@cisco.com>
> Cc: <manet@ietf.org>; <ogier@erg.sri.com>
> Sent: Monday, March 04, 2002 7:11 PM
> Subject: [manet] Re: RE : others cretaria in MANET routing protocol
> >
> > P.S. I thought about the possibility of modifying OLSR so that it
> > computes shortest paths w.r.t. a link metric (instead of computing
> > min-hop paths subject to the quality of each link being above some
> > threshold).  It is not as easy to do this in OLSR, because of the
> > requirement that paths must use links (u,v) such that v selected u as
> > a multipoint relay (except for the first hop).  This requirement
> > severely reduces the path choices, so that the shortest path w.r.t.
> > a given metric (other than the hop metric) is not likely to
> > satisfy this requirement.
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Tue Mar  5 22:57:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14869
	for <manet-archive@odin.ietf.org>; Tue, 5 Mar 2002 22:57:48 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA29235
	for manet-archive@odin.ietf.org; Tue, 5 Mar 2002 22:57:51 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA27158;
	Tue, 5 Mar 2002 22:27:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA27127
	for <manet@optimus.ietf.org>; Tue, 5 Mar 2002 22:27:02 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12507
	for <manet@ietf.org>; Tue, 5 Mar 2002 22:26:58 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id TAA03447;
	Tue, 5 Mar 2002 19:25:17 -0800 (PST)
Message-Id: <200203060325.TAA03447@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
In-reply-to: Your message of "Tue, 05 Mar 2002 12:08:24 +0100."
             <003801c1c436$121c30c0$3ac033c1@inria.fr> 
Date: Tue, 05 Mar 2002 19:25:17 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


> I don't see the problem. It suffices that the node selects its MPR nodes on
> the shortest paths (with respect to the considered metric) to its 2-hop
> neighbors. This is pretty straightforward.
> 
> Philippe

Yes, I agree it is straightforward if you are willing 
to give up your heuristic that attempts to minimize the 
number of MPRs.  But then of course you will have more MPRs, 
which could increase overhead.  

Also (as you know) unless you assume that link costs are symmetric
(which is not a good assumption), each node needs to compute
the shortest path to each 2-hop neighbor using the link costs
for the *reverse* links (from the 2-hop neighbors), since 
data packets travel in the reverse direction along these paths.
This seems to require that each node report the link costs
for both its outgoing links and incoming links.

Richard


> 
> ----- Original Message -----
> From: <ogier@erg.sri.com>
> To: Fred Baker <fred@cisco.com>
> Cc: <manet@ietf.org>; <ogier@erg.sri.com>
> Sent: Monday, March 04, 2002 7:11 PM
> Subject: [manet] Re: RE : others cretaria in MANET routing protocol
> >
> > P.S. I thought about the possibility of modifying OLSR so that it
> > computes shortest paths w.r.t. a link metric (instead of computing
> > min-hop paths subject to the quality of each link being above some
> > threshold).  It is not as easy to do this in OLSR, because of the
> > requirement that paths must use links (u,v) such that v selected u as
> > a multipoint relay (except for the first hop).  This requirement
> > severely reduces the path choices, so that the shortest path w.r.t.
> > a given metric (other than the hop metric) is not likely to
> > satisfy this requirement.
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Wed Mar  6 00:32:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16993
	for <manet-archive@odin.ietf.org>; Wed, 6 Mar 2002 00:32:03 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA03531;
	Wed, 6 Mar 2002 00:13:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA03485
	for <manet@optimus.ietf.org>; Wed, 6 Mar 2002 00:13:14 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16347
	for <manet@ietf.org>; Wed, 6 Mar 2002 00:13:12 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id VAA03666;
	Tue, 5 Mar 2002 21:11:27 -0800 (PST)
Message-Id: <200203060511.VAA03666@pit.erg.sri.com>
To: "Tao Lin" <taolin@vt.edu>
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Question regarding robustness defnition in TBRPF 
In-reply-to: Your message of "Tue, 05 Mar 2002 17:42:51 EST."
             <004b01c1c497$1522ea00$7637ad80@workgroup> 
Date: Tue, 05 Mar 2002 21:11:26 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Tao,

> The TBRPF draft says  "To provide increased robustness when sufficient
> bandwidth is available, ..." What does this increased robustness refer to?
> Does this mean short response latency to link failures, 

Yes.  You are referring to the option in which a node reports
its entire source tree instead of only part of its source tree.
This will provide each node with more alternate paths and thus
increase the probability that an alternate path is immediately
known following a link failure.  However, this probability is 
already very high, so the improvement may be only slight.

Another (perhaps better) way to increase robustness is to 
report (part of) a biconnected subgraph instead of a tree, which 
is also allowed by TBRPF. This would provide two disjoint paths 
to each destination. 

Richard


> higher throughput or
> maintenance of shortes path to all destinations when the topology changes or
> potentially something else? Do you have any analytical results? I would like
> to see whether this idea can apply to some other protocols.
> 
> Thanks!
> 
> Tao
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Wed Mar  6 00:32:12 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17011
	for <manet-archive@odin.ietf.org>; Wed, 6 Mar 2002 00:32:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA04882
	for manet-archive@odin.ietf.org; Wed, 6 Mar 2002 00:32:04 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA03531;
	Wed, 6 Mar 2002 00:13:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA03485
	for <manet@optimus.ietf.org>; Wed, 6 Mar 2002 00:13:14 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16347
	for <manet@ietf.org>; Wed, 6 Mar 2002 00:13:12 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id VAA03666;
	Tue, 5 Mar 2002 21:11:27 -0800 (PST)
Message-Id: <200203060511.VAA03666@pit.erg.sri.com>
To: "Tao Lin" <taolin@vt.edu>
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Question regarding robustness defnition in TBRPF 
In-reply-to: Your message of "Tue, 05 Mar 2002 17:42:51 EST."
             <004b01c1c497$1522ea00$7637ad80@workgroup> 
Date: Tue, 05 Mar 2002 21:11:26 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Tao,

> The TBRPF draft says  "To provide increased robustness when sufficient
> bandwidth is available, ..." What does this increased robustness refer to?
> Does this mean short response latency to link failures, 

Yes.  You are referring to the option in which a node reports
its entire source tree instead of only part of its source tree.
This will provide each node with more alternate paths and thus
increase the probability that an alternate path is immediately
known following a link failure.  However, this probability is 
already very high, so the improvement may be only slight.

Another (perhaps better) way to increase robustness is to 
report (part of) a biconnected subgraph instead of a tree, which 
is also allowed by TBRPF. This would provide two disjoint paths 
to each destination. 

Richard


> higher throughput or
> maintenance of shortes path to all destinations when the topology changes or
> potentially something else? Do you have any analytical results? I would like
> to see whether this idea can apply to some other protocols.
> 
> Thanks!
> 
> Tao
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Wed Mar  6 05:29:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29631
	for <manet-archive@odin.ietf.org>; Wed, 6 Mar 2002 05:29:27 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27994;
	Wed, 6 Mar 2002 05:08:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27962
	for <manet@optimus.ietf.org>; Wed, 6 Mar 2002 05:07:58 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29043
	for <manet@ietf.org>; Wed, 6 Mar 2002 05:07:53 -0500 (EST)
Received: from zephyrin (zephyrin-wi.inria.fr [193.51.192.58])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g26A7uL13370
	for <manet@ietf.org>; Wed, 6 Mar 2002 11:07:56 +0100 (MET)
Message-ID: <002101c1c4f9$817df160$3ac033c1@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203060325.TAA03447@pit.erg.sri.com>
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
Date: Wed, 6 Mar 2002 11:27:23 +0100
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear Richard,

You are just defining a different metric to the *coverage cost* of MPR and
this leads to a straightforward adaptation of the heuristic. Nothing very
surprising in this. About increasing the overhead I think it is a possible
outcome, since you want to optimize the network in something else than the
hop count and the number of retransmissions. I expect that you will also
have to report more nodes and increase your overhead as well (unless you
take your strange option of full tree report that anyhow rise your overhead
to a maximum).

If OLSR were taking a metric option, the link costs would likely be
advertized in TC packets. But as Laurent explained, we don't think link cost
is a good option since links are not isolated. Furthermore link cost would
likely change frequently and link cost advertizement update would incur a
lot of overhead (any new traffic will affect costs of all links of all the
nodes one hop away from the route).

One realistic design could be to affect the cost on a per node and per
interface basis as Laurent explained. My two cents: in order to limit the
update overhead one could set the interface cost to the nominal capacity of
the interface. But there is the endless issue on how to standardize an
interface cost...

Philippe



----- Original Message -----
From: <ogier@erg.sri.com>
To: <manet@ietf.org>
Cc: <ogier@erg.sri.com>
Sent: Wednesday, March 06, 2002 4:25 AM
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol


>
> > I don't see the problem. It suffices that the node selects its MPR nodes
on
> > the shortest paths (with respect to the considered metric) to its 2-hop
> > neighbors. This is pretty straightforward.
> >
> > Philippe
>
> Yes, I agree it is straightforward if you are willing
> to give up your heuristic that attempts to minimize the
> number of MPRs.  But then of course you will have more MPRs,
> which could increase overhead.
>
> Also (as you know) unless you assume that link costs are symmetric
> (which is not a good assumption), each node needs to compute
> the shortest path to each 2-hop neighbor using the link costs
> for the *reverse* links (from the 2-hop neighbors), since
> data packets travel in the reverse direction along these paths.
> This seems to require that each node report the link costs
> for both its outgoing links and incoming links.
>
> Richard
>
>
> >
> > ----- Original Message -----
> > From: <ogier@erg.sri.com>
> > To: Fred Baker <fred@cisco.com>
> > Cc: <manet@ietf.org>; <ogier@erg.sri.com>
> > Sent: Monday, March 04, 2002 7:11 PM
> > Subject: [manet] Re: RE : others cretaria in MANET routing protocol
> > >
> > > P.S. I thought about the possibility of modifying OLSR so that it
> > > computes shortest paths w.r.t. a link metric (instead of computing
> > > min-hop paths subject to the quality of each link being above some
> > > threshold).  It is not as easy to do this in OLSR, because of the
> > > requirement that paths must use links (u,v) such that v selected u as
> > > a multipoint relay (except for the first hop).  This requirement
> > > severely reduces the path choices, so that the shortest path w.r.t.
> > > a given metric (other than the hop metric) is not likely to
> > > satisfy this requirement.
> > >
> > >
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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


From daemon@optimus.ietf.org  Wed Mar  6 05:29:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29641
	for <manet-archive@odin.ietf.org>; Wed, 6 Mar 2002 05:29:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA29288
	for manet-archive@odin.ietf.org; Wed, 6 Mar 2002 05:29:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27994;
	Wed, 6 Mar 2002 05:08:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA27962
	for <manet@optimus.ietf.org>; Wed, 6 Mar 2002 05:07:58 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29043
	for <manet@ietf.org>; Wed, 6 Mar 2002 05:07:53 -0500 (EST)
Received: from zephyrin (zephyrin-wi.inria.fr [193.51.192.58])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g26A7uL13370
	for <manet@ietf.org>; Wed, 6 Mar 2002 11:07:56 +0100 (MET)
Message-ID: <002101c1c4f9$817df160$3ac033c1@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203060325.TAA03447@pit.erg.sri.com>
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
Date: Wed, 6 Mar 2002 11:27:23 +0100
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear Richard,

You are just defining a different metric to the *coverage cost* of MPR and
this leads to a straightforward adaptation of the heuristic. Nothing very
surprising in this. About increasing the overhead I think it is a possible
outcome, since you want to optimize the network in something else than the
hop count and the number of retransmissions. I expect that you will also
have to report more nodes and increase your overhead as well (unless you
take your strange option of full tree report that anyhow rise your overhead
to a maximum).

If OLSR were taking a metric option, the link costs would likely be
advertized in TC packets. But as Laurent explained, we don't think link cost
is a good option since links are not isolated. Furthermore link cost would
likely change frequently and link cost advertizement update would incur a
lot of overhead (any new traffic will affect costs of all links of all the
nodes one hop away from the route).

One realistic design could be to affect the cost on a per node and per
interface basis as Laurent explained. My two cents: in order to limit the
update overhead one could set the interface cost to the nominal capacity of
the interface. But there is the endless issue on how to standardize an
interface cost...

Philippe



----- Original Message -----
From: <ogier@erg.sri.com>
To: <manet@ietf.org>
Cc: <ogier@erg.sri.com>
Sent: Wednesday, March 06, 2002 4:25 AM
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol


>
> > I don't see the problem. It suffices that the node selects its MPR nodes
on
> > the shortest paths (with respect to the considered metric) to its 2-hop
> > neighbors. This is pretty straightforward.
> >
> > Philippe
>
> Yes, I agree it is straightforward if you are willing
> to give up your heuristic that attempts to minimize the
> number of MPRs.  But then of course you will have more MPRs,
> which could increase overhead.
>
> Also (as you know) unless you assume that link costs are symmetric
> (which is not a good assumption), each node needs to compute
> the shortest path to each 2-hop neighbor using the link costs
> for the *reverse* links (from the 2-hop neighbors), since
> data packets travel in the reverse direction along these paths.
> This seems to require that each node report the link costs
> for both its outgoing links and incoming links.
>
> Richard
>
>
> >
> > ----- Original Message -----
> > From: <ogier@erg.sri.com>
> > To: Fred Baker <fred@cisco.com>
> > Cc: <manet@ietf.org>; <ogier@erg.sri.com>
> > Sent: Monday, March 04, 2002 7:11 PM
> > Subject: [manet] Re: RE : others cretaria in MANET routing protocol
> > >
> > > P.S. I thought about the possibility of modifying OLSR so that it
> > > computes shortest paths w.r.t. a link metric (instead of computing
> > > min-hop paths subject to the quality of each link being above some
> > > threshold).  It is not as easy to do this in OLSR, because of the
> > > requirement that paths must use links (u,v) such that v selected u as
> > > a multipoint relay (except for the first hop).  This requirement
> > > severely reduces the path choices, so that the shortest path w.r.t.
> > > a given metric (other than the hop metric) is not likely to
> > > satisfy this requirement.
> > >
> > >
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Wed Mar  6 14:45:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01133
	for <manet-archive@odin.ietf.org>; Wed, 6 Mar 2002 14:45:56 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07808;
	Wed, 6 Mar 2002 14:15:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07783
	for <manet@optimus.ietf.org>; Wed, 6 Mar 2002 14:15:46 -0500 (EST)
Received: from koa.erg.sri.com (koa.erg.sri.com [128.18.100.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28863
	for <manet@ietf.org>; Wed, 6 Mar 2002 14:15:41 -0500 (EST)
Received: from koa.erg.sri.com (localhost [127.0.0.1])
	by koa.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id LAA12401;
	Wed, 6 Mar 2002 11:11:28 -0800 (PST)
Message-Id: <200203061911.LAA12401@koa.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
In-reply-to: Your message of "Wed, 06 Mar 2002 11:27:23 +0100."
             <002101c1c4f9$817df160$3ac033c1@inria.fr> 
Date: Wed, 06 Mar 2002 11:11:28 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Philippe,

> Dear Richard,
> 
> You are just defining a different metric to the *coverage cost* of MPR and
> this leads to a straightforward adaptation of the heuristic. Nothing very
> surprising in this. About increasing the overhead I think it is a possible
> outcome, since you want to optimize the network in something else than the
> hop count and the number of retransmissions. I expect that you will also
> have to report more nodes and increase your overhead as well (unless you
> take your strange option of full tree report that anyhow rise your overhead
> to a maximum).

Strange option?  I don't see anything strange about having
a node report its full source tree.
Our simulations show that having each TBRPF node report its
full source tree increases routing control traffic by about 50%
(including IP/MAC headers), so that even with this option (which 
also simplifies the protocol), TBRPF still generates less control 
traffic than OLSR, even though TBRPF sends HELLOs twice as frequently.

> If OLSR were taking a metric option, the link costs would likely be
> advertized in TC packets. But as Laurent explained, we don't think link cost
> is a good option since links are not isolated. Furthermore link cost would
> likely change frequently and link cost advertizement update would incur a
> lot of overhead (any new traffic will affect costs of all links of all the
> nodes one hop away from the route).

Advertising a 4-bit link cost for each advertised link would
increase overhead by at most 4/32 = 12.5%, and actually much
less than this if you count packet headers.
You can control the overhead for reporting link costs by
reporting them only periodically, not whenever they change.
(I.e., you would report the link cost only when you would
normally report the link anyway.) 

> One realistic design could be to affect the cost on a per node and per
> interface basis as Laurent explained. My two cents: in order to limit the
> update overhead one could set the interface cost to the nominal capacity of
> the interface. But there is the endless issue on how to standardize an
> interface cost...

I agree that a cost per node and per interface would be good, as I 
have discussed with my coworkers several months ago.
In fact, TBRPF also allows wired interfaces (e.g., to a point-to-point
link or an Ethernet), which would have a lower cost than
a wireless interface.

But I think that link costs are also useful, as I believe the
example I gave two days ago shows (in which using link costs 
increases the end-to-end reliability from .59 to .89). 
Link costs are also useful if power control is used, since the power 
required to reach a neighbor depends on the distance to that neighbor.

Richard

> 
> Philippe
> 
> 
> 
> ----- Original Message -----
> From: <ogier@erg.sri.com>
> To: <manet@ietf.org>
> Cc: <ogier@erg.sri.com>
> Sent: Wednesday, March 06, 2002 4:25 AM
> Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol
> 
> 
> >
> > > I don't see the problem. It suffices that the node selects its MPR nodes
> on
> > > the shortest paths (with respect to the considered metric) to its 2-hop
> > > neighbors. This is pretty straightforward.
> > >
> > > Philippe
> >
> > Yes, I agree it is straightforward if you are willing
> > to give up your heuristic that attempts to minimize the
> > number of MPRs.  But then of course you will have more MPRs,
> > which could increase overhead.
> >
> > Also (as you know) unless you assume that link costs are symmetric
> > (which is not a good assumption), each node needs to compute
> > the shortest path to each 2-hop neighbor using the link costs
> > for the *reverse* links (from the 2-hop neighbors), since
> > data packets travel in the reverse direction along these paths.
> > This seems to require that each node report the link costs
> > for both its outgoing links and incoming links.
> >
> > Richard
> >
> >
> > >
> > > ----- Original Message -----
> > > From: <ogier@erg.sri.com>
> > > To: Fred Baker <fred@cisco.com>
> > > Cc: <manet@ietf.org>; <ogier@erg.sri.com>
> > > Sent: Monday, March 04, 2002 7:11 PM
> > > Subject: [manet] Re: RE : others cretaria in MANET routing protocol
> > > >
> > > > P.S. I thought about the possibility of modifying OLSR so that it
> > > > computes shortest paths w.r.t. a link metric (instead of computing
> > > > min-hop paths subject to the quality of each link being above some
> > > > threshold).  It is not as easy to do this in OLSR, because of the
> > > > requirement that paths must use links (u,v) such that v selected u as
> > > > a multipoint relay (except for the first hop).  This requirement
> > > > severely reduces the path choices, so that the shortest path w.r.t.
> > > > a given metric (other than the hop metric) is not likely to
> > > > satisfy this requirement.
> > > >
> > > >
> > > > _______________________________________________
> > > > manet mailing list
> > > > manet@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/manet
> > >
> > >
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Wed Mar  6 14:45:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01144
	for <manet-archive@odin.ietf.org>; Wed, 6 Mar 2002 14:45:57 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA12251
	for manet-archive@odin.ietf.org; Wed, 6 Mar 2002 14:46:01 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07808;
	Wed, 6 Mar 2002 14:15:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA07783
	for <manet@optimus.ietf.org>; Wed, 6 Mar 2002 14:15:46 -0500 (EST)
Received: from koa.erg.sri.com (koa.erg.sri.com [128.18.100.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28863
	for <manet@ietf.org>; Wed, 6 Mar 2002 14:15:41 -0500 (EST)
Received: from koa.erg.sri.com (localhost [127.0.0.1])
	by koa.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id LAA12401;
	Wed, 6 Mar 2002 11:11:28 -0800 (PST)
Message-Id: <200203061911.LAA12401@koa.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
In-reply-to: Your message of "Wed, 06 Mar 2002 11:27:23 +0100."
             <002101c1c4f9$817df160$3ac033c1@inria.fr> 
Date: Wed, 06 Mar 2002 11:11:28 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Philippe,

> Dear Richard,
> 
> You are just defining a different metric to the *coverage cost* of MPR and
> this leads to a straightforward adaptation of the heuristic. Nothing very
> surprising in this. About increasing the overhead I think it is a possible
> outcome, since you want to optimize the network in something else than the
> hop count and the number of retransmissions. I expect that you will also
> have to report more nodes and increase your overhead as well (unless you
> take your strange option of full tree report that anyhow rise your overhead
> to a maximum).

Strange option?  I don't see anything strange about having
a node report its full source tree.
Our simulations show that having each TBRPF node report its
full source tree increases routing control traffic by about 50%
(including IP/MAC headers), so that even with this option (which 
also simplifies the protocol), TBRPF still generates less control 
traffic than OLSR, even though TBRPF sends HELLOs twice as frequently.

> If OLSR were taking a metric option, the link costs would likely be
> advertized in TC packets. But as Laurent explained, we don't think link cost
> is a good option since links are not isolated. Furthermore link cost would
> likely change frequently and link cost advertizement update would incur a
> lot of overhead (any new traffic will affect costs of all links of all the
> nodes one hop away from the route).

Advertising a 4-bit link cost for each advertised link would
increase overhead by at most 4/32 = 12.5%, and actually much
less than this if you count packet headers.
You can control the overhead for reporting link costs by
reporting them only periodically, not whenever they change.
(I.e., you would report the link cost only when you would
normally report the link anyway.) 

> One realistic design could be to affect the cost on a per node and per
> interface basis as Laurent explained. My two cents: in order to limit the
> update overhead one could set the interface cost to the nominal capacity of
> the interface. But there is the endless issue on how to standardize an
> interface cost...

I agree that a cost per node and per interface would be good, as I 
have discussed with my coworkers several months ago.
In fact, TBRPF also allows wired interfaces (e.g., to a point-to-point
link or an Ethernet), which would have a lower cost than
a wireless interface.

But I think that link costs are also useful, as I believe the
example I gave two days ago shows (in which using link costs 
increases the end-to-end reliability from .59 to .89). 
Link costs are also useful if power control is used, since the power 
required to reach a neighbor depends on the distance to that neighbor.

Richard

> 
> Philippe
> 
> 
> 
> ----- Original Message -----
> From: <ogier@erg.sri.com>
> To: <manet@ietf.org>
> Cc: <ogier@erg.sri.com>
> Sent: Wednesday, March 06, 2002 4:25 AM
> Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol
> 
> 
> >
> > > I don't see the problem. It suffices that the node selects its MPR nodes
> on
> > > the shortest paths (with respect to the considered metric) to its 2-hop
> > > neighbors. This is pretty straightforward.
> > >
> > > Philippe
> >
> > Yes, I agree it is straightforward if you are willing
> > to give up your heuristic that attempts to minimize the
> > number of MPRs.  But then of course you will have more MPRs,
> > which could increase overhead.
> >
> > Also (as you know) unless you assume that link costs are symmetric
> > (which is not a good assumption), each node needs to compute
> > the shortest path to each 2-hop neighbor using the link costs
> > for the *reverse* links (from the 2-hop neighbors), since
> > data packets travel in the reverse direction along these paths.
> > This seems to require that each node report the link costs
> > for both its outgoing links and incoming links.
> >
> > Richard
> >
> >
> > >
> > > ----- Original Message -----
> > > From: <ogier@erg.sri.com>
> > > To: Fred Baker <fred@cisco.com>
> > > Cc: <manet@ietf.org>; <ogier@erg.sri.com>
> > > Sent: Monday, March 04, 2002 7:11 PM
> > > Subject: [manet] Re: RE : others cretaria in MANET routing protocol
> > > >
> > > > P.S. I thought about the possibility of modifying OLSR so that it
> > > > computes shortest paths w.r.t. a link metric (instead of computing
> > > > min-hop paths subject to the quality of each link being above some
> > > > threshold).  It is not as easy to do this in OLSR, because of the
> > > > requirement that paths must use links (u,v) such that v selected u as
> > > > a multipoint relay (except for the first hop).  This requirement
> > > > severely reduces the path choices, so that the shortest path w.r.t.
> > > > a given metric (other than the hop metric) is not likely to
> > > > satisfy this requirement.
> > > >
> > > >
> > > > _______________________________________________
> > > > manet mailing list
> > > > manet@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/manet
> > >
> > >
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Thu Mar  7 05:59:01 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16486
	for <manet-archive@odin.ietf.org>; Thu, 7 Mar 2002 05:59:01 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12186;
	Thu, 7 Mar 2002 05:36:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12154
	for <manet@optimus.ietf.org>; Thu, 7 Mar 2002 05:36:20 -0500 (EST)
Received: from mailhost.cs.auc.dk (root@mailhost.cs.auc.dk [130.225.194.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16060
	for <manet@ietf.org>; Thu, 7 Mar 2002 05:36:14 -0500 (EST)
Received: from localhost (root@borg.cs.auc.dk [130.225.194.22])
	by mailhost.cs.auc.dk (8.12.2/8.12.2) with ESMTP id g27AaFvU020698
	for <manet@ietf.org>; Thu, 7 Mar 2002 11:36:16 +0100 (MET)
Date: Thu, 7 Mar 2002 11:36:15 +0100 (CET)
From: t.clausen@computer.org
X-Sender: voop@armada
Reply-To: t.clausen@computer.org
To: manet@ietf.org
Message-ID: <Pine.LNX.4.21.0203071124100.608-100000@armada>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-Scanned-By: MIMEDefang 2.2
Content-Transfer-Encoding: 8BIT
Subject: [manet] Re: performance comparaison between Ad Hoc routing protocols
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8BIT

Richard,

I suspect serious problems with your control overhead measures. Please see
below.

On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:

> 
> Thomas,
> 
> > Richard,
> > 
> > I am not quite sure what to make from your simulations. It seems to me
> > that they are from a network in overload condition - in which case buffer
> > management has a critical impact on performance. We've been simulating
> > OLSR in conditions, similar to those you've been showing, and our results
> > differ significantly. We experience that a large abmount of (data and
> > control) traffic in these situations are rejected from the various
> > buffers.
> 

<SNIP> 

> To ensure that the protocols were compared on a fair basis,
> since AODV and TBRPF gave control traffic higher priority than
> data traffic, we did the same for OLSR.  It has long been considered
> a good idea to give control traffic higher priority.  This could 
> explain why your results differ from mine.
> You can do this simply by adding the line
>                 case PT_OLSR:
> to the function PriQueue::recv() in priqueue.cc.
> 
> > Also, I notice that we obtain much less overhead for OLSR when counting
> > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > detailed information (e.g. physical overhead etc.) ?
> 
> No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> at the MAC layer.  
> 

<SNIP> 

I've tried to reproduce your published results for OLSR, using a large set
of scenario files, corresponding to the parameters you've used.

Unfortunately I fail to achieve the same results as those you present
(both with and without control traffic priority): in particulary in the
overload condition (packet rate of 6-8 packets/second) I find the overhead
of OLSR to be significantly lower (up to 25-30%) than what your
simulations show.

Also, as we were discussing in another mail, my simulations showed that
the "control packet size" bug resulted in approximately 50% more overhead,
whereas you cited your simulations as showing in the orders of 90-120%
more overhead. I have not had success in reproducing the 90-120% figures 
either.

I am basically looking for an explanation on why we have such different
results.

I am well aware that a paticulary "bad" or "good" choise of scenario (even
corresponding to the same general parameters such as mobility and traffic
patterns) may trigger particulary good or bad results, so I've run a
number of different scenarios through, all with roughly the same results.
This left me wondering if our different results were just a matter of
computing the overhead differently?

The way in which I extract overhead information from the ns2 tracefiles is
to look at all "send" events on the "MAC" layer from the agent
"OLSR". This should yield both the number of packets being transmitted as
well as the number of bytes, actually reaching the MAC layer and not
being dropped somewhere else.

However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
look at all the lines in the tracefile wish an "s" event from "OLSR", it
was possible to end up with overhead figures very close those that you
cite. I do believe, though, that this is a wrong way of accounting, since
(1) control packets, dropped in the protocol stack (and thus not
contributing to diffusion of topology information) are accounted as
protocol overhead and, (2) control packets are accounted multiple times
(each time a layer is sending the packet "downwards" in the stack.)

-- 

-------------------------------------------
  Thomas Heide Clausen
  Civilingeniør i Datateknik (cand.polyt)
  M.Sc in Computer Engineering

  E-Mail: T.Clausen@computer.org
  WWW:    http://www.cs.auc.dk/~voop
-------------------------------------------







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


From daemon@optimus.ietf.org  Thu Mar  7 05:59:01 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16497
	for <manet-archive@odin.ietf.org>; Thu, 7 Mar 2002 05:59:01 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA13695
	for manet-archive@odin.ietf.org; Thu, 7 Mar 2002 05:59:06 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12186;
	Thu, 7 Mar 2002 05:36:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA12154
	for <manet@optimus.ietf.org>; Thu, 7 Mar 2002 05:36:20 -0500 (EST)
Received: from mailhost.cs.auc.dk (root@mailhost.cs.auc.dk [130.225.194.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16060
	for <manet@ietf.org>; Thu, 7 Mar 2002 05:36:14 -0500 (EST)
Received: from localhost (root@borg.cs.auc.dk [130.225.194.22])
	by mailhost.cs.auc.dk (8.12.2/8.12.2) with ESMTP id g27AaFvU020698
	for <manet@ietf.org>; Thu, 7 Mar 2002 11:36:16 +0100 (MET)
Date: Thu, 7 Mar 2002 11:36:15 +0100 (CET)
From: t.clausen@computer.org
X-Sender: voop@armada
Reply-To: t.clausen@computer.org
To: manet@ietf.org
Message-ID: <Pine.LNX.4.21.0203071124100.608-100000@armada>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-Scanned-By: MIMEDefang 2.2
Content-Transfer-Encoding: 8BIT
Subject: [manet] Re: performance comparaison between Ad Hoc routing protocols
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8BIT

Richard,

I suspect serious problems with your control overhead measures. Please see
below.

On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:

> 
> Thomas,
> 
> > Richard,
> > 
> > I am not quite sure what to make from your simulations. It seems to me
> > that they are from a network in overload condition - in which case buffer
> > management has a critical impact on performance. We've been simulating
> > OLSR in conditions, similar to those you've been showing, and our results
> > differ significantly. We experience that a large abmount of (data and
> > control) traffic in these situations are rejected from the various
> > buffers.
> 

<SNIP> 

> To ensure that the protocols were compared on a fair basis,
> since AODV and TBRPF gave control traffic higher priority than
> data traffic, we did the same for OLSR.  It has long been considered
> a good idea to give control traffic higher priority.  This could 
> explain why your results differ from mine.
> You can do this simply by adding the line
>                 case PT_OLSR:
> to the function PriQueue::recv() in priqueue.cc.
> 
> > Also, I notice that we obtain much less overhead for OLSR when counting
> > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > detailed information (e.g. physical overhead etc.) ?
> 
> No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> at the MAC layer.  
> 

<SNIP> 

I've tried to reproduce your published results for OLSR, using a large set
of scenario files, corresponding to the parameters you've used.

Unfortunately I fail to achieve the same results as those you present
(both with and without control traffic priority): in particulary in the
overload condition (packet rate of 6-8 packets/second) I find the overhead
of OLSR to be significantly lower (up to 25-30%) than what your
simulations show.

Also, as we were discussing in another mail, my simulations showed that
the "control packet size" bug resulted in approximately 50% more overhead,
whereas you cited your simulations as showing in the orders of 90-120%
more overhead. I have not had success in reproducing the 90-120% figures 
either.

I am basically looking for an explanation on why we have such different
results.

I am well aware that a paticulary "bad" or "good" choise of scenario (even
corresponding to the same general parameters such as mobility and traffic
patterns) may trigger particulary good or bad results, so I've run a
number of different scenarios through, all with roughly the same results.
This left me wondering if our different results were just a matter of
computing the overhead differently?

The way in which I extract overhead information from the ns2 tracefiles is
to look at all "send" events on the "MAC" layer from the agent
"OLSR". This should yield both the number of packets being transmitted as
well as the number of bytes, actually reaching the MAC layer and not
being dropped somewhere else.

However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
look at all the lines in the tracefile wish an "s" event from "OLSR", it
was possible to end up with overhead figures very close those that you
cite. I do believe, though, that this is a wrong way of accounting, since
(1) control packets, dropped in the protocol stack (and thus not
contributing to diffusion of topology information) are accounted as
protocol overhead and, (2) control packets are accounted multiple times
(each time a layer is sending the packet "downwards" in the stack.)

-- 

-------------------------------------------
  Thomas Heide Clausen
  Civilingeniør i Datateknik (cand.polyt)
  M.Sc in Computer Engineering

  E-Mail: T.Clausen@computer.org
  WWW:    http://www.cs.auc.dk/~voop
-------------------------------------------







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



From manet-admin@ietf.org  Thu Mar  7 13:12:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11933
	for <manet-archive@odin.ietf.org>; Thu, 7 Mar 2002 13:12:46 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15767;
	Thu, 7 Mar 2002 12:40:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15738
	for <manet@optimus.ietf.org>; Thu, 7 Mar 2002 12:40:36 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09721
	for <manet@ietf.org>; Thu, 7 Mar 2002 12:40:30 -0500 (EST)
Received: from zephyrin (zephyrin-wi.inria.fr [193.51.192.58])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g27HeXv13409
	for <manet@ietf.org>; Thu, 7 Mar 2002 18:40:34 +0100 (MET)
Message-ID: <009101c1c601$e82b3fe0$3ac033c1@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203061911.LAA12401@koa.erg.sri.com>
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
Date: Thu, 7 Mar 2002 19:00:02 +0100
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: <ogier@erg.sri.com>
To: <manet@ietf.org>
Cc: <ogier@erg.sri.com>
Sent: Wednesday, March 06, 2002 8:11 PM
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol


>
> Philippe,
>
> > Dear Richard,
> >
> > You are just defining a different metric to the *coverage cost* of MPR
and
> > this leads to a straightforward adaptation of the heuristic. Nothing
very
> > surprising in this. About increasing the overhead I think it is a
possible
> > outcome, since you want to optimize the network in something else than
the
> > hop count and the number of retransmissions. I expect that you will also
> > have to report more nodes and increase your overhead as well (unless you
> > take your strange option of full tree report that anyhow rise your
overhead
> > to a maximum).
>
> Strange option?  I don't see anything strange about having
> a node report its full source tree.
> Our simulations show that having each TBRPF node report its
> full source tree increases routing control traffic by about 50%
> (including IP/MAC headers), so that even with this option (which
> also simplifies the protocol), TBRPF still generates less control
> traffic than OLSR, even though TBRPF sends HELLOs twice as frequently.
>
By strange I just minded that it seems to implicitly acknowledge
unreliability in TBRPF. This change was introduced in your January
submission and was never commented. It seems to be redundant and maybe in
conflict with the older option of reporting additional links. Does it add to
the provability of the protocol?

Philippe





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


From daemon@optimus.ietf.org  Thu Mar  7 13:12:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11943
	for <manet-archive@odin.ietf.org>; Thu, 7 Mar 2002 13:12:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA18780
	for manet-archive@odin.ietf.org; Thu, 7 Mar 2002 13:12:54 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15767;
	Thu, 7 Mar 2002 12:40:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15738
	for <manet@optimus.ietf.org>; Thu, 7 Mar 2002 12:40:36 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09721
	for <manet@ietf.org>; Thu, 7 Mar 2002 12:40:30 -0500 (EST)
Received: from zephyrin (zephyrin-wi.inria.fr [193.51.192.58])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g27HeXv13409
	for <manet@ietf.org>; Thu, 7 Mar 2002 18:40:34 +0100 (MET)
Message-ID: <009101c1c601$e82b3fe0$3ac033c1@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203061911.LAA12401@koa.erg.sri.com>
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
Date: Thu, 7 Mar 2002 19:00:02 +0100
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: <ogier@erg.sri.com>
To: <manet@ietf.org>
Cc: <ogier@erg.sri.com>
Sent: Wednesday, March 06, 2002 8:11 PM
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol


>
> Philippe,
>
> > Dear Richard,
> >
> > You are just defining a different metric to the *coverage cost* of MPR
and
> > this leads to a straightforward adaptation of the heuristic. Nothing
very
> > surprising in this. About increasing the overhead I think it is a
possible
> > outcome, since you want to optimize the network in something else than
the
> > hop count and the number of retransmissions. I expect that you will also
> > have to report more nodes and increase your overhead as well (unless you
> > take your strange option of full tree report that anyhow rise your
overhead
> > to a maximum).
>
> Strange option?  I don't see anything strange about having
> a node report its full source tree.
> Our simulations show that having each TBRPF node report its
> full source tree increases routing control traffic by about 50%
> (including IP/MAC headers), so that even with this option (which
> also simplifies the protocol), TBRPF still generates less control
> traffic than OLSR, even though TBRPF sends HELLOs twice as frequently.
>
By strange I just minded that it seems to implicitly acknowledge
unreliability in TBRPF. This change was introduced in your January
submission and was never commented. It seems to be redundant and maybe in
conflict with the older option of reporting additional links. Does it add to
the provability of the protocol?

Philippe





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



From manet-admin@ietf.org  Fri Mar  8 05:25:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27958
	for <manet-archive@odin.ietf.org>; Fri, 8 Mar 2002 05:25:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA17452;
	Fri, 8 Mar 2002 04:50:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA17422
	for <manet@optimus.ietf.org>; Fri, 8 Mar 2002 04:50:48 -0500 (EST)
Received: from luit.iitg.ernet.in (iitg.ernet.in [202.141.80.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27344
	for <manet@ietf.org>; Fri, 8 Mar 2002 04:50:38 -0500 (EST)
Received: from loktak.iitg.ernet.in (IDENT:c2K2WwJu2BoEeWnwOe89ZEiYQaa4xWjk@loktak.iitg.ernet.in [202.141.80.32])
	by luit.iitg.ernet.in (8.12.2/8.12.0) with ESMTP id g289hchv010972
	for <manet@ietf.org>; Fri, 8 Mar 2002 15:13:38 +0530
Received: from localhost (arijitg@localhost)
	by loktak.iitg.ernet.in (8.11.6/8.9.3) with ESMTP id g289nfP11407
	for <manet@ietf.org>; Fri, 8 Mar 2002 15:19:41 +0530
X-Authentication-Warning: loktak.iitg.ernet.in: arijitg owned process doing -bs
Date: Fri, 8 Mar 2002 15:19:41 +0530 (IST)
From: Arijit Ganguly <arijitg@iitg.ernet.in>
To: Mobile Ad hoc Networks <manet@ietf.org>
Message-ID: <Pine.LNX.4.33.0203081517590.11349-100000@loktak.iitg.ernet.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Multicast AODV
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hello Seniors
I am working on reliable multicasting in ad hoc networks. I wish to use 
multicast AODV for routing. DOes anyone of you have a parcec (Glomosim) 
code for multicast AODV. I don't require a very recent implementation. An 
older one should do?

Thanking you.

Regards
Arijit

-- 
------------------------------------------------------------------------------
                          Arijit Ganguly
                        Final Year Student
            Department of Computer Science & Engineering
              Indian Institute of Technology, Guwahati
                Guwahati - 781039, District Kamrup
                          Assam, India
          ------------------------------------------------
                Phone : +00-91-0361-690763 (room #203)
                Fax   : +91 361 690762
                email : ariganguly@yahoo.co.in
                CC    : ariganguly@hotmail.com
          ------------------------------------------------




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


From daemon@optimus.ietf.org  Fri Mar  8 05:25:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27967
	for <manet-archive@odin.ietf.org>; Fri, 8 Mar 2002 05:25:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA19989
	for manet-archive@odin.ietf.org; Fri, 8 Mar 2002 05:25:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA17452;
	Fri, 8 Mar 2002 04:50:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA17422
	for <manet@optimus.ietf.org>; Fri, 8 Mar 2002 04:50:48 -0500 (EST)
Received: from luit.iitg.ernet.in (iitg.ernet.in [202.141.80.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27344
	for <manet@ietf.org>; Fri, 8 Mar 2002 04:50:38 -0500 (EST)
Received: from loktak.iitg.ernet.in (IDENT:c2K2WwJu2BoEeWnwOe89ZEiYQaa4xWjk@loktak.iitg.ernet.in [202.141.80.32])
	by luit.iitg.ernet.in (8.12.2/8.12.0) with ESMTP id g289hchv010972
	for <manet@ietf.org>; Fri, 8 Mar 2002 15:13:38 +0530
Received: from localhost (arijitg@localhost)
	by loktak.iitg.ernet.in (8.11.6/8.9.3) with ESMTP id g289nfP11407
	for <manet@ietf.org>; Fri, 8 Mar 2002 15:19:41 +0530
X-Authentication-Warning: loktak.iitg.ernet.in: arijitg owned process doing -bs
Date: Fri, 8 Mar 2002 15:19:41 +0530 (IST)
From: Arijit Ganguly <arijitg@iitg.ernet.in>
To: Mobile Ad hoc Networks <manet@ietf.org>
Message-ID: <Pine.LNX.4.33.0203081517590.11349-100000@loktak.iitg.ernet.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Multicast AODV
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hello Seniors
I am working on reliable multicasting in ad hoc networks. I wish to use 
multicast AODV for routing. DOes anyone of you have a parcec (Glomosim) 
code for multicast AODV. I don't require a very recent implementation. An 
older one should do?

Thanking you.

Regards
Arijit

-- 
------------------------------------------------------------------------------
                          Arijit Ganguly
                        Final Year Student
            Department of Computer Science & Engineering
              Indian Institute of Technology, Guwahati
                Guwahati - 781039, District Kamrup
                          Assam, India
          ------------------------------------------------
                Phone : +00-91-0361-690763 (room #203)
                Fax   : +91 361 690762
                email : ariganguly@yahoo.co.in
                CC    : ariganguly@hotmail.com
          ------------------------------------------------




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



From manet-admin@ietf.org  Fri Mar  8 12:26:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18724
	for <manet-archive@odin.ietf.org>; Fri, 8 Mar 2002 12:26:25 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA11697;
	Fri, 8 Mar 2002 11:11:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA11667
	for <manet@optimus.ietf.org>; Fri, 8 Mar 2002 11:11:15 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12512
	for <manet@ietf.org>; Fri, 8 Mar 2002 11:11:12 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id IAA08495;
	Fri, 8 Mar 2002 08:09:07 -0800 (PST)
Message-Id: <200203081609.IAA08495@pit.erg.sri.com>
To: t.clausen@computer.org
cc: manet@ietf.org
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
In-reply-to: Your message of "Thu, 07 Mar 2002 11:36:15 +0100."
             <Pine.LNX.4.21.0203071124100.608-100000@armada> 
Date: Fri, 08 Mar 2002 08:09:06 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Thomas,

> The way in which I extract overhead information from the ns2 tracefiles is
> to look at all "send" events on the "MAC" layer from the agent
> "OLSR". This should yield both the number of packets being transmitted as
> well as the number of bytes, actually reaching the MAC layer and not
> being dropped somewhere else.
> 
> However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> look at all the lines in the tracefile wish an "s" event from "OLSR", it
> was possible to end up with overhead figures very close those that you
> cite. I do believe, though, that this is a wrong way of accounting, since
> (1) control packets, dropped in the protocol stack (and thus not
> contributing to diffusion of topology information) are accounted as
> protocol overhead and, (2) control packets are accounted multiple times
> (each time a layer is sending the packet "downwards" in the stack.)

We counted packets exactly the same way you did, i.e., 
only at the MAC layer.  

To double check, I did the following:

grep "s " out.tr | grep MAC | grep OLSR   

and got exactly the same number of OLSR packets
as our perl script did.

I did this for the following case:
100 nodes, 670x670 area, no mobility, 20 sources, packet rate = 6
For 500 seconds, there were 154744 OLSR packets totaling 20684584, 
so the average size of an OLSR packet (including the IP and MAC 
headers) is 133 bytes. 

I also would like to find out why our results differ.
If you have any more ideas, please let me know.

Regarding the 90-120% increase of overhead for the bug fix, 
that was for 100 nodes.  I later tried 50 nodes and found
the increase to be roughly 75-90%.

Richard


> Richard,
> 
> I suspect serious problems with your control overhead measures. Please see
> below.
> 
> On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:
> 
> > 
> > Thomas,
> > 
> > > Richard,
> > > 
> > > I am not quite sure what to make from your simulations. It seems to me
> > > that they are from a network in overload condition - in which case buffer
> > > management has a critical impact on performance. We've been simulating
> > > OLSR in conditions, similar to those you've been showing, and our results
> > > differ significantly. We experience that a large abmount of (data and
> > > control) traffic in these situations are rejected from the various
> > > buffers.
> > 
> 
> <SNIP> 
> 
> > To ensure that the protocols were compared on a fair basis,
> > since AODV and TBRPF gave control traffic higher priority than
> > data traffic, we did the same for OLSR.  It has long been considered
> > a good idea to give control traffic higher priority.  This could 
> > explain why your results differ from mine.
> > You can do this simply by adding the line
> >                 case PT_OLSR:
> > to the function PriQueue::recv() in priqueue.cc.
> > 
> > > Also, I notice that we obtain much less overhead for OLSR when counting
> > > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > > detailed information (e.g. physical overhead etc.) ?
> > 
> > No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> > at the MAC layer.  
> > 
> 
> <SNIP> 
> 
> I've tried to reproduce your published results for OLSR, using a large set
> of scenario files, corresponding to the parameters you've used.
> 
> Unfortunately I fail to achieve the same results as those you present
> (both with and without control traffic priority): in particulary in the
> overload condition (packet rate of 6-8 packets/second) I find the overhead
> of OLSR to be significantly lower (up to 25-30%) than what your
> simulations show.
> 
> Also, as we were discussing in another mail, my simulations showed that
> the "control packet size" bug resulted in approximately 50% more overhead,
> whereas you cited your simulations as showing in the orders of 90-120%
> more overhead. I have not had success in reproducing the 90-120% figures 
> either.
> 
> I am basically looking for an explanation on why we have such different
> results.
> 
> I am well aware that a paticulary "bad" or "good" choise of scenario (even
> corresponding to the same general parameters such as mobility and traffic
> patterns) may trigger particulary good or bad results, so I've run a
> number of different scenarios through, all with roughly the same results.
> This left me wondering if our different results were just a matter of
> computing the overhead differently?
> 
> The way in which I extract overhead information from the ns2 tracefiles is
> to look at all "send" events on the "MAC" layer from the agent
> "OLSR". This should yield both the number of packets being transmitted as
> well as the number of bytes, actually reaching the MAC layer and not
> being dropped somewhere else.
> 
> However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> look at all the lines in the tracefile wish an "s" event from "OLSR", it
> was possible to end up with overhead figures very close those that you
> cite. I do believe, though, that this is a wrong way of accounting, since
> (1) control packets, dropped in the protocol stack (and thus not
> contributing to diffusion of topology information) are accounted as
> protocol overhead and, (2) control packets are accounted multiple times
> (each time a layer is sending the packet "downwards" in the stack.)


> 
> -- 
> 
> -------------------------------------------
>   Thomas Heide Clausen
>   Civilingeniør i Datateknik (cand.polyt)
>   M.Sc in Computer Engineering
> 
>   E-Mail: T.Clausen@computer.org
>   WWW:    http://www.cs.auc.dk/~voop
> -------------------------------------------
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Fri Mar  8 12:26:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18733
	for <manet-archive@odin.ietf.org>; Fri, 8 Mar 2002 12:26:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA18704
	for manet-archive@odin.ietf.org; Fri, 8 Mar 2002 12:26:27 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA11697;
	Fri, 8 Mar 2002 11:11:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA11667
	for <manet@optimus.ietf.org>; Fri, 8 Mar 2002 11:11:15 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12512
	for <manet@ietf.org>; Fri, 8 Mar 2002 11:11:12 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id IAA08495;
	Fri, 8 Mar 2002 08:09:07 -0800 (PST)
Message-Id: <200203081609.IAA08495@pit.erg.sri.com>
To: t.clausen@computer.org
cc: manet@ietf.org
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
In-reply-to: Your message of "Thu, 07 Mar 2002 11:36:15 +0100."
             <Pine.LNX.4.21.0203071124100.608-100000@armada> 
Date: Fri, 08 Mar 2002 08:09:06 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Thomas,

> The way in which I extract overhead information from the ns2 tracefiles is
> to look at all "send" events on the "MAC" layer from the agent
> "OLSR". This should yield both the number of packets being transmitted as
> well as the number of bytes, actually reaching the MAC layer and not
> being dropped somewhere else.
> 
> However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> look at all the lines in the tracefile wish an "s" event from "OLSR", it
> was possible to end up with overhead figures very close those that you
> cite. I do believe, though, that this is a wrong way of accounting, since
> (1) control packets, dropped in the protocol stack (and thus not
> contributing to diffusion of topology information) are accounted as
> protocol overhead and, (2) control packets are accounted multiple times
> (each time a layer is sending the packet "downwards" in the stack.)

We counted packets exactly the same way you did, i.e., 
only at the MAC layer.  

To double check, I did the following:

grep "s " out.tr | grep MAC | grep OLSR   

and got exactly the same number of OLSR packets
as our perl script did.

I did this for the following case:
100 nodes, 670x670 area, no mobility, 20 sources, packet rate = 6
For 500 seconds, there were 154744 OLSR packets totaling 20684584, 
so the average size of an OLSR packet (including the IP and MAC 
headers) is 133 bytes. 

I also would like to find out why our results differ.
If you have any more ideas, please let me know.

Regarding the 90-120% increase of overhead for the bug fix, 
that was for 100 nodes.  I later tried 50 nodes and found
the increase to be roughly 75-90%.

Richard


> Richard,
> 
> I suspect serious problems with your control overhead measures. Please see
> below.
> 
> On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:
> 
> > 
> > Thomas,
> > 
> > > Richard,
> > > 
> > > I am not quite sure what to make from your simulations. It seems to me
> > > that they are from a network in overload condition - in which case buffer
> > > management has a critical impact on performance. We've been simulating
> > > OLSR in conditions, similar to those you've been showing, and our results
> > > differ significantly. We experience that a large abmount of (data and
> > > control) traffic in these situations are rejected from the various
> > > buffers.
> > 
> 
> <SNIP> 
> 
> > To ensure that the protocols were compared on a fair basis,
> > since AODV and TBRPF gave control traffic higher priority than
> > data traffic, we did the same for OLSR.  It has long been considered
> > a good idea to give control traffic higher priority.  This could 
> > explain why your results differ from mine.
> > You can do this simply by adding the line
> >                 case PT_OLSR:
> > to the function PriQueue::recv() in priqueue.cc.
> > 
> > > Also, I notice that we obtain much less overhead for OLSR when counting
> > > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > > detailed information (e.g. physical overhead etc.) ?
> > 
> > No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> > at the MAC layer.  
> > 
> 
> <SNIP> 
> 
> I've tried to reproduce your published results for OLSR, using a large set
> of scenario files, corresponding to the parameters you've used.
> 
> Unfortunately I fail to achieve the same results as those you present
> (both with and without control traffic priority): in particulary in the
> overload condition (packet rate of 6-8 packets/second) I find the overhead
> of OLSR to be significantly lower (up to 25-30%) than what your
> simulations show.
> 
> Also, as we were discussing in another mail, my simulations showed that
> the "control packet size" bug resulted in approximately 50% more overhead,
> whereas you cited your simulations as showing in the orders of 90-120%
> more overhead. I have not had success in reproducing the 90-120% figures 
> either.
> 
> I am basically looking for an explanation on why we have such different
> results.
> 
> I am well aware that a paticulary "bad" or "good" choise of scenario (even
> corresponding to the same general parameters such as mobility and traffic
> patterns) may trigger particulary good or bad results, so I've run a
> number of different scenarios through, all with roughly the same results.
> This left me wondering if our different results were just a matter of
> computing the overhead differently?
> 
> The way in which I extract overhead information from the ns2 tracefiles is
> to look at all "send" events on the "MAC" layer from the agent
> "OLSR". This should yield both the number of packets being transmitted as
> well as the number of bytes, actually reaching the MAC layer and not
> being dropped somewhere else.
> 
> However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> look at all the lines in the tracefile wish an "s" event from "OLSR", it
> was possible to end up with overhead figures very close those that you
> cite. I do believe, though, that this is a wrong way of accounting, since
> (1) control packets, dropped in the protocol stack (and thus not
> contributing to diffusion of topology information) are accounted as
> protocol overhead and, (2) control packets are accounted multiple times
> (each time a layer is sending the packet "downwards" in the stack.)


> 
> -- 
> 
> -------------------------------------------
>   Thomas Heide Clausen
>   Civilingeniør i Datateknik (cand.polyt)
>   M.Sc in Computer Engineering
> 
>   E-Mail: T.Clausen@computer.org
>   WWW:    http://www.cs.auc.dk/~voop
> -------------------------------------------
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Fri Mar  8 15:03:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00184
	for <manet-archive@odin.ietf.org>; Fri, 8 Mar 2002 15:03:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28081;
	Fri, 8 Mar 2002 14:27:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28055
	for <manet@optimus.ietf.org>; Fri, 8 Mar 2002 14:27:08 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27664
	for <manet@ietf.org>; Fri, 8 Mar 2002 14:27:05 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id LAA09154;
	Fri, 8 Mar 2002 11:25:22 -0800 (PST)
Message-Id: <200203081925.LAA09154@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
In-reply-to: Your message of "Thu, 07 Mar 2002 19:00:02 +0100."
             <009101c1c601$e82b3fe0$3ac033c1@inria.fr> 
Date: Fri, 08 Mar 2002 11:25:22 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Philippe,

<SNIP> 

> > Strange option?  I don't see anything strange about having
> > a node report its full source tree.
> > Our simulations show that having each TBRPF node report its
> > full source tree increases routing control traffic by about 50%
> > (including IP/MAC headers), so that even with this option (which
> > also simplifies the protocol), TBRPF still generates less control
> > traffic than OLSR, even though TBRPF sends HELLOs twice as frequently.
> >
> By strange I just minded that it seems to implicitly acknowledge
> unreliability in TBRPF. This change was introduced in your January
> submission and was never commented. It seems to be redundant and maybe in
> conflict with the older option of reporting additional links. Does it add to
> the provability of the protocol?
> 
> Philippe
> 

You try to find (or imply) fault where there is none. The option in 
which a node can report its full source tree is just a very simple 
way to report additional links, thus potentially increasing 
robustness in highly mobile networks.
It is not in conflict with the other option, which allows a node
to report links that are not in its source tree.  As long as each node 
reports the minimum information (i.e., its reportable subtree), it can 
report additional links that it knows about.

TBRPF is correct with or without these options, and our simulations 
show that it performs very well even if only the minimum information 
is reported.  Sending the minimum information minimizes overhead,
which improves scalability and allows TBRPF to be used in low-bandwidth
radios such as those used by the military.  But if sufficient bandwidth
is available in a highly mobile network, it makes sense to allow
additional topology information to be reported to improve robustness.

Richard

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

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


From daemon@optimus.ietf.org  Fri Mar  8 15:55:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00193
	for <manet-archive@odin.ietf.org>; Fri, 8 Mar 2002 15:03:38 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA02533
	for manet-archive@odin.ietf.org; Fri, 8 Mar 2002 15:03:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28081;
	Fri, 8 Mar 2002 14:27:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28055
	for <manet@optimus.ietf.org>; Fri, 8 Mar 2002 14:27:08 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27664
	for <manet@ietf.org>; Fri, 8 Mar 2002 14:27:05 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id LAA09154;
	Fri, 8 Mar 2002 11:25:22 -0800 (PST)
Message-Id: <200203081925.LAA09154@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
In-reply-to: Your message of "Thu, 07 Mar 2002 19:00:02 +0100."
             <009101c1c601$e82b3fe0$3ac033c1@inria.fr> 
Date: Fri, 08 Mar 2002 11:25:22 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Philippe,

<SNIP> 

> > Strange option?  I don't see anything strange about having
> > a node report its full source tree.
> > Our simulations show that having each TBRPF node report its
> > full source tree increases routing control traffic by about 50%
> > (including IP/MAC headers), so that even with this option (which
> > also simplifies the protocol), TBRPF still generates less control
> > traffic than OLSR, even though TBRPF sends HELLOs twice as frequently.
> >
> By strange I just minded that it seems to implicitly acknowledge
> unreliability in TBRPF. This change was introduced in your January
> submission and was never commented. It seems to be redundant and maybe in
> conflict with the older option of reporting additional links. Does it add to
> the provability of the protocol?
> 
> Philippe
> 

You try to find (or imply) fault where there is none. The option in 
which a node can report its full source tree is just a very simple 
way to report additional links, thus potentially increasing 
robustness in highly mobile networks.
It is not in conflict with the other option, which allows a node
to report links that are not in its source tree.  As long as each node 
reports the minimum information (i.e., its reportable subtree), it can 
report additional links that it knows about.

TBRPF is correct with or without these options, and our simulations 
show that it performs very well even if only the minimum information 
is reported.  Sending the minimum information minimizes overhead,
which improves scalability and allows TBRPF to be used in low-bandwidth
radios such as those used by the military.  But if sufficient bandwidth
is available in a highly mobile network, it makes sense to allow
additional topology information to be reported to improve robustness.

Richard

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

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



From manet-admin@ietf.org  Fri Mar  8 20:37:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15049
	for <manet-archive@odin.ietf.org>; Fri, 8 Mar 2002 20:37:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA18559;
	Fri, 8 Mar 2002 20:03:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA18528
	for <manet@optimus.ietf.org>; Fri, 8 Mar 2002 20:03:07 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14259
	for <manet@ietf.org>; Fri, 8 Mar 2002 20:03:05 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id RAA10048;
	Fri, 8 Mar 2002 17:01:21 -0800 (PST)
Message-Id: <200203090101.RAA10048@pit.erg.sri.com>
To: t.clausen@computer.org, manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
In-reply-to: Your message of "Fri, 08 Mar 2002 08:09:06 PST."
             <200203081609.IAA08495@pit.erg.sri.com> 
Date: Fri, 08 Mar 2002 17:01:20 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Thomas,

So that we can determine why our results differ, I will
provide additional details and scripts, so that you can run
the same experiment I ran.  I will give you the cbr 
and scenario scripts in a separate email.

I will refer to the case with 100 nodes, 20 sources, 670x670 area, 
no mobility, and a packet rate of 6 packets/second/source.  
Each stream begins at a random time between 10 and 40 seconds, and 
changes its destination to a randomly selected node every 30 seconds. 
The size of each data packet is 512 bytes. 
The total number of packets generated in 500 sec is 57261,
which is slightly less than 60000 = 6 * 20 * 500.
Is this similar to what you ran?

Richard


> Thomas,
> 
> > The way in which I extract overhead information from the ns2 tracefiles is
> > to look at all "send" events on the "MAC" layer from the agent
> > "OLSR". This should yield both the number of packets being transmitted as
> > well as the number of bytes, actually reaching the MAC layer and not
> > being dropped somewhere else.
> > 
> > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > was possible to end up with overhead figures very close those that you
> > cite. I do believe, though, that this is a wrong way of accounting, since
> > (1) control packets, dropped in the protocol stack (and thus not
> > contributing to diffusion of topology information) are accounted as
> > protocol overhead and, (2) control packets are accounted multiple times
> > (each time a layer is sending the packet "downwards" in the stack.)
> 
> We counted packets exactly the same way you did, i.e., 
> only at the MAC layer.  
> 
> To double check, I did the following:
> 
> grep "s " out.tr | grep MAC | grep OLSR   
> 
> and got exactly the same number of OLSR packets
> as our perl script did.
> 
> I did this for the following case:
> 100 nodes, 670x670 area, no mobility, 20 sources, packet rate = 6
> For 500 seconds, there were 154744 OLSR packets totaling 20684584, 
> so the average size of an OLSR packet (including the IP and MAC 
> headers) is 133 bytes. 
> 
> I also would like to find out why our results differ.
> If you have any more ideas, please let me know.
> 
> Regarding the 90-120% increase of overhead for the bug fix, 
> that was for 100 nodes.  I later tried 50 nodes and found
> the increase to be roughly 75-90%.
> 
> Richard
> 
> 
> > Richard,
> > 
> > I suspect serious problems with your control overhead measures. Please see
> > below.
> > 
> > On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:
> > 
> > > 
> > > Thomas,
> > > 
> > > > Richard,
> > > > 
> > > > I am not quite sure what to make from your simulations. It seems to me
> > > > that they are from a network in overload condition - in which case buff
er
> > > > management has a critical impact on performance. We've been simulating
> > > > OLSR in conditions, similar to those you've been showing, and our resul
ts
> > > > differ significantly. We experience that a large abmount of (data and
> > > > control) traffic in these situations are rejected from the various
> > > > buffers.
> > > 
> > 
> > <SNIP> 
> > 
> > > To ensure that the protocols were compared on a fair basis,
> > > since AODV and TBRPF gave control traffic higher priority than
> > > data traffic, we did the same for OLSR.  It has long been considered
> > > a good idea to give control traffic higher priority.  This could 
> > > explain why your results differ from mine.
> > > You can do this simply by adding the line
> > >                 case PT_OLSR:
> > > to the function PriQueue::recv() in priqueue.cc.
> > > 
> > > > Also, I notice that we obtain much less overhead for OLSR when counting
> > > > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > > > detailed information (e.g. physical overhead etc.) ?
> > > 
> > > No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> > > at the MAC layer.  
> > > 
> > 
> > <SNIP> 
> > 
> > I've tried to reproduce your published results for OLSR, using a large set
> > of scenario files, corresponding to the parameters you've used.
> > 
> > Unfortunately I fail to achieve the same results as those you present
> > (both with and without control traffic priority): in particulary in the
> > overload condition (packet rate of 6-8 packets/second) I find the overhead
> > of OLSR to be significantly lower (up to 25-30%) than what your
> > simulations show.
> > 
> > Also, as we were discussing in another mail, my simulations showed that
> > the "control packet size" bug resulted in approximately 50% more overhead,
> > whereas you cited your simulations as showing in the orders of 90-120%
> > more overhead. I have not had success in reproducing the 90-120% figures 
> > either.
> > 
> > I am basically looking for an explanation on why we have such different
> > results.
> > 
> > I am well aware that a paticulary "bad" or "good" choise of scenario (even
> > corresponding to the same general parameters such as mobility and traffic
> > patterns) may trigger particulary good or bad results, so I've run a
> > number of different scenarios through, all with roughly the same results.
> > This left me wondering if our different results were just a matter of
> > computing the overhead differently?
> > 
> > The way in which I extract overhead information from the ns2 tracefiles is
> > to look at all "send" events on the "MAC" layer from the agent
> > "OLSR". This should yield both the number of packets being transmitted as
> > well as the number of bytes, actually reaching the MAC layer and not
> > being dropped somewhere else.
> > 
> > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > was possible to end up with overhead figures very close those that you
> > cite. I do believe, though, that this is a wrong way of accounting, since
> > (1) control packets, dropped in the protocol stack (and thus not
> > contributing to diffusion of topology information) are accounted as
> > protocol overhead and, (2) control packets are accounted multiple times
> > (each time a layer is sending the packet "downwards" in the stack.)
> 
> 
> > 
> > -- 
> > 
> > -------------------------------------------
> >   Thomas Heide Clausen
> >   Civilingeniør i Datateknik (cand.polyt)
> >   M.Sc in Computer Engineering
> > 
> >   E-Mail: T.Clausen@computer.org
> >   WWW:    http://www.cs.auc.dk/~voop
> > -------------------------------------------
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Fri Mar  8 20:37:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15058
	for <manet-archive@odin.ietf.org>; Fri, 8 Mar 2002 20:37:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA20558
	for manet-archive@odin.ietf.org; Fri, 8 Mar 2002 20:37:41 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA18559;
	Fri, 8 Mar 2002 20:03:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id UAA18528
	for <manet@optimus.ietf.org>; Fri, 8 Mar 2002 20:03:07 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14259
	for <manet@ietf.org>; Fri, 8 Mar 2002 20:03:05 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id RAA10048;
	Fri, 8 Mar 2002 17:01:21 -0800 (PST)
Message-Id: <200203090101.RAA10048@pit.erg.sri.com>
To: t.clausen@computer.org, manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
In-reply-to: Your message of "Fri, 08 Mar 2002 08:09:06 PST."
             <200203081609.IAA08495@pit.erg.sri.com> 
Date: Fri, 08 Mar 2002 17:01:20 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Thomas,

So that we can determine why our results differ, I will
provide additional details and scripts, so that you can run
the same experiment I ran.  I will give you the cbr 
and scenario scripts in a separate email.

I will refer to the case with 100 nodes, 20 sources, 670x670 area, 
no mobility, and a packet rate of 6 packets/second/source.  
Each stream begins at a random time between 10 and 40 seconds, and 
changes its destination to a randomly selected node every 30 seconds. 
The size of each data packet is 512 bytes. 
The total number of packets generated in 500 sec is 57261,
which is slightly less than 60000 = 6 * 20 * 500.
Is this similar to what you ran?

Richard


> Thomas,
> 
> > The way in which I extract overhead information from the ns2 tracefiles is
> > to look at all "send" events on the "MAC" layer from the agent
> > "OLSR". This should yield both the number of packets being transmitted as
> > well as the number of bytes, actually reaching the MAC layer and not
> > being dropped somewhere else.
> > 
> > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > was possible to end up with overhead figures very close those that you
> > cite. I do believe, though, that this is a wrong way of accounting, since
> > (1) control packets, dropped in the protocol stack (and thus not
> > contributing to diffusion of topology information) are accounted as
> > protocol overhead and, (2) control packets are accounted multiple times
> > (each time a layer is sending the packet "downwards" in the stack.)
> 
> We counted packets exactly the same way you did, i.e., 
> only at the MAC layer.  
> 
> To double check, I did the following:
> 
> grep "s " out.tr | grep MAC | grep OLSR   
> 
> and got exactly the same number of OLSR packets
> as our perl script did.
> 
> I did this for the following case:
> 100 nodes, 670x670 area, no mobility, 20 sources, packet rate = 6
> For 500 seconds, there were 154744 OLSR packets totaling 20684584, 
> so the average size of an OLSR packet (including the IP and MAC 
> headers) is 133 bytes. 
> 
> I also would like to find out why our results differ.
> If you have any more ideas, please let me know.
> 
> Regarding the 90-120% increase of overhead for the bug fix, 
> that was for 100 nodes.  I later tried 50 nodes and found
> the increase to be roughly 75-90%.
> 
> Richard
> 
> 
> > Richard,
> > 
> > I suspect serious problems with your control overhead measures. Please see
> > below.
> > 
> > On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:
> > 
> > > 
> > > Thomas,
> > > 
> > > > Richard,
> > > > 
> > > > I am not quite sure what to make from your simulations. It seems to me
> > > > that they are from a network in overload condition - in which case buff
er
> > > > management has a critical impact on performance. We've been simulating
> > > > OLSR in conditions, similar to those you've been showing, and our resul
ts
> > > > differ significantly. We experience that a large abmount of (data and
> > > > control) traffic in these situations are rejected from the various
> > > > buffers.
> > > 
> > 
> > <SNIP> 
> > 
> > > To ensure that the protocols were compared on a fair basis,
> > > since AODV and TBRPF gave control traffic higher priority than
> > > data traffic, we did the same for OLSR.  It has long been considered
> > > a good idea to give control traffic higher priority.  This could 
> > > explain why your results differ from mine.
> > > You can do this simply by adding the line
> > >                 case PT_OLSR:
> > > to the function PriQueue::recv() in priqueue.cc.
> > > 
> > > > Also, I notice that we obtain much less overhead for OLSR when counting
> > > > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > > > detailed information (e.g. physical overhead etc.) ?
> > > 
> > > No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> > > at the MAC layer.  
> > > 
> > 
> > <SNIP> 
> > 
> > I've tried to reproduce your published results for OLSR, using a large set
> > of scenario files, corresponding to the parameters you've used.
> > 
> > Unfortunately I fail to achieve the same results as those you present
> > (both with and without control traffic priority): in particulary in the
> > overload condition (packet rate of 6-8 packets/second) I find the overhead
> > of OLSR to be significantly lower (up to 25-30%) than what your
> > simulations show.
> > 
> > Also, as we were discussing in another mail, my simulations showed that
> > the "control packet size" bug resulted in approximately 50% more overhead,
> > whereas you cited your simulations as showing in the orders of 90-120%
> > more overhead. I have not had success in reproducing the 90-120% figures 
> > either.
> > 
> > I am basically looking for an explanation on why we have such different
> > results.
> > 
> > I am well aware that a paticulary "bad" or "good" choise of scenario (even
> > corresponding to the same general parameters such as mobility and traffic
> > patterns) may trigger particulary good or bad results, so I've run a
> > number of different scenarios through, all with roughly the same results.
> > This left me wondering if our different results were just a matter of
> > computing the overhead differently?
> > 
> > The way in which I extract overhead information from the ns2 tracefiles is
> > to look at all "send" events on the "MAC" layer from the agent
> > "OLSR". This should yield both the number of packets being transmitted as
> > well as the number of bytes, actually reaching the MAC layer and not
> > being dropped somewhere else.
> > 
> > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > was possible to end up with overhead figures very close those that you
> > cite. I do believe, though, that this is a wrong way of accounting, since
> > (1) control packets, dropped in the protocol stack (and thus not
> > contributing to diffusion of topology information) are accounted as
> > protocol overhead and, (2) control packets are accounted multiple times
> > (each time a layer is sending the packet "downwards" in the stack.)
> 
> 
> > 
> > -- 
> > 
> > -------------------------------------------
> >   Thomas Heide Clausen
> >   Civilingeniør i Datateknik (cand.polyt)
> >   M.Sc in Computer Engineering
> > 
> >   E-Mail: T.Clausen@computer.org
> >   WWW:    http://www.cs.auc.dk/~voop
> > -------------------------------------------
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Mon Mar 11 12:55:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17522
	for <manet-archive@odin.ietf.org>; Mon, 11 Mar 2002 12:55:23 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA02036;
	Mon, 11 Mar 2002 12:18:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA01969
	for <manet@optimus.ietf.org>; Mon, 11 Mar 2002 12:18:19 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15834
	for <manet@ietf.org>; Mon, 11 Mar 2002 12:16:18 -0500 (EST)
Received: from zephyrin (zephyrin-wi.inria.fr [193.51.192.58])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2BHGL121049
	for <manet@ietf.org>; Mon, 11 Mar 2002 18:16:21 +0100 (MET)
Message-ID: <00a901c1c923$32e82ec0$3ac033c1@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203081925.LAA09154@pit.erg.sri.com>
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
Date: Mon, 11 Mar 2002 18:35:55 +0100
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Richard,

I am not looking for errors. This would be a very unpleasant task and the
protocol is far too complex for that. I am just looking for proofs. Unlike
OLSR, TBRPF is not known to be proven. OLSR proofs are rather simple. There
is nothing in the optimisations we have introduced so far that don't go
along OLSR proofs of correctness. Do you have a proof of TBRPF correctness?
I have just some doubts that obsolete topology informations may endlessly
circulate in the network and your complex optimisation process may
potentially increase this risk. I was wondering if  a simpler version of the
protocol without optimisation may have helped you to figure out a proof of
correctness.

Philippe

----- Original Message -----
From: <ogier@erg.sri.com>
To: <manet@ietf.org>
Cc: <ogier@erg.sri.com>
Sent: Friday, March 08, 2002 8:25 PM
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol


>
> Philippe,
>
<SNIP>
>
> > >
> > By strange I just minded that it seems to implicitly acknowledge
> > unreliability in TBRPF. This change was introduced in your January
> > submission and was never commented. It seems to be redundant and maybe
in
> > conflict with the older option of reporting additional links. Does it
add to
> > the provability of the protocol?
> >
> > Philippe
> >
>
> You try to find (or imply) fault where there is none. The option in
> which a node can report its full source tree is just a very simple
> way to report additional links, thus potentially increasing
> robustness in highly mobile networks.
> It is not in conflict with the other option, which allows a node
> to report links that are not in its source tree.  As long as each node
> reports the minimum information (i.e., its reportable subtree), it can
> report additional links that it knows about.
>
> TBRPF is correct with or without these options, and our simulations
> show that it performs very well even if only the minimum information
> is reported.  Sending the minimum information minimizes overhead,
> which improves scalability and allows TBRPF to be used in low-bandwidth
> radios such as those used by the military.  But if sufficient bandwidth
> is available in a highly mobile network, it makes sense to allow
> additional topology information to be reported to improve robustness.
>
> Richard
>
> >
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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


From daemon@optimus.ietf.org  Mon Mar 11 12:55:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17537
	for <manet-archive@odin.ietf.org>; Mon, 11 Mar 2002 12:55:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA04437
	for manet-archive@odin.ietf.org; Mon, 11 Mar 2002 12:55:26 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA02036;
	Mon, 11 Mar 2002 12:18:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA01969
	for <manet@optimus.ietf.org>; Mon, 11 Mar 2002 12:18:19 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15834
	for <manet@ietf.org>; Mon, 11 Mar 2002 12:16:18 -0500 (EST)
Received: from zephyrin (zephyrin-wi.inria.fr [193.51.192.58])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2BHGL121049
	for <manet@ietf.org>; Mon, 11 Mar 2002 18:16:21 +0100 (MET)
Message-ID: <00a901c1c923$32e82ec0$3ac033c1@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203081925.LAA09154@pit.erg.sri.com>
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
Date: Mon, 11 Mar 2002 18:35:55 +0100
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Richard,

I am not looking for errors. This would be a very unpleasant task and the
protocol is far too complex for that. I am just looking for proofs. Unlike
OLSR, TBRPF is not known to be proven. OLSR proofs are rather simple. There
is nothing in the optimisations we have introduced so far that don't go
along OLSR proofs of correctness. Do you have a proof of TBRPF correctness?
I have just some doubts that obsolete topology informations may endlessly
circulate in the network and your complex optimisation process may
potentially increase this risk. I was wondering if  a simpler version of the
protocol without optimisation may have helped you to figure out a proof of
correctness.

Philippe

----- Original Message -----
From: <ogier@erg.sri.com>
To: <manet@ietf.org>
Cc: <ogier@erg.sri.com>
Sent: Friday, March 08, 2002 8:25 PM
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol


>
> Philippe,
>
<SNIP>
>
> > >
> > By strange I just minded that it seems to implicitly acknowledge
> > unreliability in TBRPF. This change was introduced in your January
> > submission and was never commented. It seems to be redundant and maybe
in
> > conflict with the older option of reporting additional links. Does it
add to
> > the provability of the protocol?
> >
> > Philippe
> >
>
> You try to find (or imply) fault where there is none. The option in
> which a node can report its full source tree is just a very simple
> way to report additional links, thus potentially increasing
> robustness in highly mobile networks.
> It is not in conflict with the other option, which allows a node
> to report links that are not in its source tree.  As long as each node
> reports the minimum information (i.e., its reportable subtree), it can
> report additional links that it knows about.
>
> TBRPF is correct with or without these options, and our simulations
> show that it performs very well even if only the minimum information
> is reported.  Sending the minimum information minimizes overhead,
> which improves scalability and allows TBRPF to be used in low-bandwidth
> radios such as those used by the military.  But if sufficient bandwidth
> is available in a highly mobile network, it makes sense to allow
> additional topology information to be reported to improve robustness.
>
> Richard
>
> >
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Mon Mar 11 17:45:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28339
	for <manet-archive@odin.ietf.org>; Mon, 11 Mar 2002 17:45:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19262;
	Mon, 11 Mar 2002 17:22:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19232
	for <manet@optimus.ietf.org>; Mon, 11 Mar 2002 17:22:24 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27626
	for <manet@ietf.org>; Mon, 11 Mar 2002 17:22:19 -0500 (EST)
Received: from zidane.cc.vt.edu (IDENT:mirapoint@zidane-lb.cc.vt.edu [10.1.1.13])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2BMMM2329414
	for <manet@ietf.org>; Mon, 11 Mar 2002 17:22:22 -0500 (EST)
Received: from TNT (h80ad3776.dhcp.vt.edu [128.173.55.118])
	by zidane.cc.vt.edu (Mirapoint)
	with SMTP id AKA22174;
	Mon, 11 Mar 2002 17:22:21 -0500 (EST)
Message-ID: <001101c1c94a$fd72b300$7637ad80@workgroup>
From: "Tao Lin" <taolin@vt.edu>
To: <manet@ietf.org>
References: <200203081925.LAA09154@pit.erg.sri.com> <00a901c1c923$32e82ec0$3ac033c1@inria.fr>
Date: Mon, 11 Mar 2002 17:20:45 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] TBRPF with multicast applications
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

TBRPF provides information for only one path (or maybe two, like an optional
choice indicated in the TBRPF draft) per destination. In a network with
heavy multicast traffic load, I think it might have more congestions with
TBRPF protocol. Are there any multicast extensions for TBRPF or studies on
this topic?

Thanks!

Tao Lin



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


From daemon@optimus.ietf.org  Mon Mar 11 17:45:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28350
	for <manet-archive@odin.ietf.org>; Mon, 11 Mar 2002 17:45:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA20805
	for manet-archive@odin.ietf.org; Mon, 11 Mar 2002 17:45:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19262;
	Mon, 11 Mar 2002 17:22:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19232
	for <manet@optimus.ietf.org>; Mon, 11 Mar 2002 17:22:24 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27626
	for <manet@ietf.org>; Mon, 11 Mar 2002 17:22:19 -0500 (EST)
Received: from zidane.cc.vt.edu (IDENT:mirapoint@zidane-lb.cc.vt.edu [10.1.1.13])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2BMMM2329414
	for <manet@ietf.org>; Mon, 11 Mar 2002 17:22:22 -0500 (EST)
Received: from TNT (h80ad3776.dhcp.vt.edu [128.173.55.118])
	by zidane.cc.vt.edu (Mirapoint)
	with SMTP id AKA22174;
	Mon, 11 Mar 2002 17:22:21 -0500 (EST)
Message-ID: <001101c1c94a$fd72b300$7637ad80@workgroup>
From: "Tao Lin" <taolin@vt.edu>
To: <manet@ietf.org>
References: <200203081925.LAA09154@pit.erg.sri.com> <00a901c1c923$32e82ec0$3ac033c1@inria.fr>
Date: Mon, 11 Mar 2002 17:20:45 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Subject: [manet] TBRPF with multicast applications
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

TBRPF provides information for only one path (or maybe two, like an optional
choice indicated in the TBRPF draft) per destination. In a network with
heavy multicast traffic load, I think it might have more congestions with
TBRPF protocol. Are there any multicast extensions for TBRPF or studies on
this topic?

Thanks!

Tao Lin



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



From manet-admin@ietf.org  Mon Mar 11 22:52:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05744
	for <manet-archive@odin.ietf.org>; Mon, 11 Mar 2002 22:52:25 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA03767;
	Mon, 11 Mar 2002 22:31:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA03736
	for <manet@optimus.ietf.org>; Mon, 11 Mar 2002 22:31:37 -0500 (EST)
Received: from Princeton.EDU (postoffice.Princeton.EDU [128.112.129.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05079
	for <manet@ietf.org>; Mon, 11 Mar 2002 22:31:32 -0500 (EST)
Received: from smtpserver2.Princeton.EDU (smtpserver2.Princeton.EDU [128.112.129.148])
	by Princeton.EDU (8.12.2/8.12.2) with ESMTP id g2C3Tjaa019528
	for <manet@ietf.org>; Mon, 11 Mar 2002 22:29:45 -0500 (EST)
Received: from webmail (mailserver1.Princeton.EDU [128.112.129.147])
	by smtpserver2.Princeton.EDU (8.12.2/8.12.2) with SMTP id g2C3TioB007890;
	Mon, 11 Mar 2002 22:29:44 -0500 (EST)
Date: Mon, 11 Mar 2002 22:29:44 -0500 (EST)
From: iavramop@princeton.edu (Ioannis C Avramopoulos)
To: manet@ietf.org
Cc: iavramop@princeton.edu
X-Mailer: Netscape Messenger Express 3.5.2 [Mozilla/4.76 [en] (Windows NT 5.0; U)]
Message-ID: <3C8D7628.5164@mailserver1.Princeton.EDU>
Subject: [manet] OLSR questions
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Dear MANET Researchers,

I have some questions on OLSR and I would greatly appreciate it if any of
you took the time to answer. My questions are the following:

- What are the advantages of having a LOST_LINK type over having no such
type (version 4 for example did not have such link type)?

- Why should a node have multiple interfaces all running the OLSR protocol?


- Does the IEEE 802.11 specification make any provision for the scenario of
a node possessing multiple interfaces?

- Are MPRs elected per interface or per node? In other words is it possible
for a node that possesses multiple interfaces to elect a different MPR-set
for each of its interfaces? If MPRs are elected per interface what is the
point of doing so?

- It is stated in the draft that the MPR-set is constructed such that any
symmetric 2-hop interface is reached. Why is it desirable to reach any
symmetric 2-hop interface and not just any node possessing at least one
symmetric 2-hop interface?

- How does a node determine which interfaces should be used to (re)transmit
network-wide broadcast messages?

- It is stated that HELLO messages are transmitted on all interfaces. Isn't
this a waste of resources?

Thank you in advance.
Ioannis Avramopoulos



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


From daemon@optimus.ietf.org  Mon Mar 11 22:52:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05755
	for <manet-archive@odin.ietf.org>; Mon, 11 Mar 2002 22:52:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA04645
	for manet-archive@odin.ietf.org; Mon, 11 Mar 2002 22:52:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA03767;
	Mon, 11 Mar 2002 22:31:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA03736
	for <manet@optimus.ietf.org>; Mon, 11 Mar 2002 22:31:37 -0500 (EST)
Received: from Princeton.EDU (postoffice.Princeton.EDU [128.112.129.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05079
	for <manet@ietf.org>; Mon, 11 Mar 2002 22:31:32 -0500 (EST)
Received: from smtpserver2.Princeton.EDU (smtpserver2.Princeton.EDU [128.112.129.148])
	by Princeton.EDU (8.12.2/8.12.2) with ESMTP id g2C3Tjaa019528
	for <manet@ietf.org>; Mon, 11 Mar 2002 22:29:45 -0500 (EST)
Received: from webmail (mailserver1.Princeton.EDU [128.112.129.147])
	by smtpserver2.Princeton.EDU (8.12.2/8.12.2) with SMTP id g2C3TioB007890;
	Mon, 11 Mar 2002 22:29:44 -0500 (EST)
Date: Mon, 11 Mar 2002 22:29:44 -0500 (EST)
From: iavramop@princeton.edu (Ioannis C Avramopoulos)
To: manet@ietf.org
Cc: iavramop@princeton.edu
X-Mailer: Netscape Messenger Express 3.5.2 [Mozilla/4.76 [en] (Windows NT 5.0; U)]
Message-ID: <3C8D7628.5164@mailserver1.Princeton.EDU>
Subject: [manet] OLSR questions
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Dear MANET Researchers,

I have some questions on OLSR and I would greatly appreciate it if any of
you took the time to answer. My questions are the following:

- What are the advantages of having a LOST_LINK type over having no such
type (version 4 for example did not have such link type)?

- Why should a node have multiple interfaces all running the OLSR protocol?


- Does the IEEE 802.11 specification make any provision for the scenario of
a node possessing multiple interfaces?

- Are MPRs elected per interface or per node? In other words is it possible
for a node that possesses multiple interfaces to elect a different MPR-set
for each of its interfaces? If MPRs are elected per interface what is the
point of doing so?

- It is stated in the draft that the MPR-set is constructed such that any
symmetric 2-hop interface is reached. Why is it desirable to reach any
symmetric 2-hop interface and not just any node possessing at least one
symmetric 2-hop interface?

- How does a node determine which interfaces should be used to (re)transmit
network-wide broadcast messages?

- It is stated that HELLO messages are transmitted on all interfaces. Isn't
this a waste of resources?

Thank you in advance.
Ioannis Avramopoulos



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



From manet-admin@ietf.org  Tue Mar 12 08:42:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21537
	for <manet-archive@odin.ietf.org>; Tue, 12 Mar 2002 08:42:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08577;
	Tue, 12 Mar 2002 07:53:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08541
	for <manet@optimus.ietf.org>; Tue, 12 Mar 2002 07:53:15 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20511
	for <manet@ietf.org>; Tue, 12 Mar 2002 07:53:11 -0500 (EST)
Received: from impression.inria.fr (impression.inria.fr [128.93.17.98])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2CCr9T26639;
	Tue, 12 Mar 2002 13:53:09 +0100 (MET)
Received: by impression.inria.fr (sSMTP sendmail emulation); Tue, 12 Mar 2002 13:53:09 +0100
From: Laurent Viennot <Laurent.Viennot@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15501.64053.570314.623276@impression.inria.fr>
Date: Tue, 12 Mar 2002 13:53:09 +0100
To: iavramop@princeton.edu (Ioannis C Avramopoulos)
Cc: manet@ietf.org
Subject: [manet] OLSR questions
In-Reply-To: <3C8D7628.5164@mailserver1.Princeton.EDU>
References: <3C8D7628.5164@mailserver1.Princeton.EDU>
X-Mailer: VM 6.92 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Reply-To: Laurent.Viennot@inria.fr
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


Dear Ioannis,

Comments bellow.

laurent


Ioannis C Avramopoulos writes:
 > 
 > Dear MANET Researchers,
 > 
 > I have some questions on OLSR and I would greatly appreciate it if any of
 > you took the time to answer. My questions are the following:
 > 
 > - What are the advantages of having a LOST_LINK type over having no such
 > type (version 4 for example did not have such link type)?

It allows quicker update of one hop and especially two hop
neighborhood. A node announcing a neighbor loss allows its neighbors
to remove the link (without waiting for expiration) from their 2-hop
neighbor set.

Notice that the use of LOST_LINK was already mentioned in version 2 of
the draft and included in the implementation code, see:

http://hipercom.inria.fr/olsr/


 > 
 > - Why should a node have multiple interfaces all running the OLSR protocol?

It may have several radio interfaces with different radio channels, or
several radio interfaces with directional antennas (and possibly same
radio channel). It may even have a wire interface running OLSR if the
network is hybrid radio/wire.  Running OLSR on all of them allows to
connect everything in a straight forward manner.

 > 
 > 
 > - Does the IEEE 802.11 specification make any provision for the scenario of
 > a node possessing multiple interfaces?

No. It is in charge of the routing layer.

 > 
 > - Are MPRs elected per interface or per node? In other words is it possible
 > for a node that possesses multiple interfaces to elect a different MPR-set
 > for each of its interfaces? If MPRs are elected per interface what is the
 > point of doing so?

MPRs are elected per node (the basic rule is that any control packet
broadcasted by a node is emitted on each of its OLSR interfaces).  It
would be easy to allow MPR-set election per interface as you propose,
we could also envision to specify on which interfaces a MPR should
forward a broadcast packet but it would make the protocol more complex
for an optimization that is useful only when many nodes have multiple
interfaces. We felt keeping the protocol simple was more important.

 > 
 > - It is stated in the draft that the MPR-set is constructed such that any
 > symmetric 2-hop interface is reached. Why is it desirable to reach any
 > symmetric 2-hop interface and not just any node possessing at least one
 > symmetric 2-hop interface?

The formal rule is what you propose: any 2-hop neighbor must have an
interface covered by some MPR. But the proposed heuristic selects an
MPR set such that any 2-hop interface is covered.

This is again for the sake of simplicity versus complex optimization
not so useful. Notice that you have to be careful to avoid a chicken
and egg problem if your computation of MPRs depend from the reception
of MID messages when the forwarding of MID messages depends on MPR
election. (You need to receive a MID message from a 2-hop neighbor to
know all its interfaces.)
 
An optimized implementation could however modify the heuristic such
that at least one interface is covered for 2-hop neighbors for which
the node has received a recent MID message. It should still allow to
cover all 2-hop interfaces of other 2-hop neighbors to avoid the
chicken and egg problem.

 > 
 > - How does a node determine which interfaces should be used to (re)transmit
 > network-wide broadcast messages?

As mentioned above, all interfaces retransmit.

 > 
 > - It is stated that HELLO messages are transmitted on all interfaces. Isn't
 > this a waste of resources?

Hello messages are transmitted on all OLSR interfaces. It is necessary
to monitor connectivity on all interfaces. To allow 2-hop neighbor
knowledge, all the information has to be transmitted on all interfaces
from time to time. However, we could easily allow to send different
messages per interface (it would naturally fit with partial Hellos)
but again we preferred simplicity rather than a minor optimization.

 > 
 > Thank you in advance.
 > Ioannis Avramopoulos
 > 
 > 

Thanks for you remarks, we are very interested in your feedback.


Laurent


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


From daemon@optimus.ietf.org  Tue Mar 12 08:42:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21548
	for <manet-archive@odin.ietf.org>; Tue, 12 Mar 2002 08:42:29 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA12448
	for manet-archive@odin.ietf.org; Tue, 12 Mar 2002 08:42:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08577;
	Tue, 12 Mar 2002 07:53:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA08541
	for <manet@optimus.ietf.org>; Tue, 12 Mar 2002 07:53:15 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20511
	for <manet@ietf.org>; Tue, 12 Mar 2002 07:53:11 -0500 (EST)
Received: from impression.inria.fr (impression.inria.fr [128.93.17.98])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2CCr9T26639;
	Tue, 12 Mar 2002 13:53:09 +0100 (MET)
Received: by impression.inria.fr (sSMTP sendmail emulation); Tue, 12 Mar 2002 13:53:09 +0100
From: Laurent Viennot <Laurent.Viennot@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15501.64053.570314.623276@impression.inria.fr>
Date: Tue, 12 Mar 2002 13:53:09 +0100
To: iavramop@princeton.edu (Ioannis C Avramopoulos)
Cc: manet@ietf.org
Subject: [manet] OLSR questions
In-Reply-To: <3C8D7628.5164@mailserver1.Princeton.EDU>
References: <3C8D7628.5164@mailserver1.Princeton.EDU>
X-Mailer: VM 6.92 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Reply-To: Laurent.Viennot@inria.fr
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


Dear Ioannis,

Comments bellow.

laurent


Ioannis C Avramopoulos writes:
 > 
 > Dear MANET Researchers,
 > 
 > I have some questions on OLSR and I would greatly appreciate it if any of
 > you took the time to answer. My questions are the following:
 > 
 > - What are the advantages of having a LOST_LINK type over having no such
 > type (version 4 for example did not have such link type)?

It allows quicker update of one hop and especially two hop
neighborhood. A node announcing a neighbor loss allows its neighbors
to remove the link (without waiting for expiration) from their 2-hop
neighbor set.

Notice that the use of LOST_LINK was already mentioned in version 2 of
the draft and included in the implementation code, see:

http://hipercom.inria.fr/olsr/


 > 
 > - Why should a node have multiple interfaces all running the OLSR protocol?

It may have several radio interfaces with different radio channels, or
several radio interfaces with directional antennas (and possibly same
radio channel). It may even have a wire interface running OLSR if the
network is hybrid radio/wire.  Running OLSR on all of them allows to
connect everything in a straight forward manner.

 > 
 > 
 > - Does the IEEE 802.11 specification make any provision for the scenario of
 > a node possessing multiple interfaces?

No. It is in charge of the routing layer.

 > 
 > - Are MPRs elected per interface or per node? In other words is it possible
 > for a node that possesses multiple interfaces to elect a different MPR-set
 > for each of its interfaces? If MPRs are elected per interface what is the
 > point of doing so?

MPRs are elected per node (the basic rule is that any control packet
broadcasted by a node is emitted on each of its OLSR interfaces).  It
would be easy to allow MPR-set election per interface as you propose,
we could also envision to specify on which interfaces a MPR should
forward a broadcast packet but it would make the protocol more complex
for an optimization that is useful only when many nodes have multiple
interfaces. We felt keeping the protocol simple was more important.

 > 
 > - It is stated in the draft that the MPR-set is constructed such that any
 > symmetric 2-hop interface is reached. Why is it desirable to reach any
 > symmetric 2-hop interface and not just any node possessing at least one
 > symmetric 2-hop interface?

The formal rule is what you propose: any 2-hop neighbor must have an
interface covered by some MPR. But the proposed heuristic selects an
MPR set such that any 2-hop interface is covered.

This is again for the sake of simplicity versus complex optimization
not so useful. Notice that you have to be careful to avoid a chicken
and egg problem if your computation of MPRs depend from the reception
of MID messages when the forwarding of MID messages depends on MPR
election. (You need to receive a MID message from a 2-hop neighbor to
know all its interfaces.)
 
An optimized implementation could however modify the heuristic such
that at least one interface is covered for 2-hop neighbors for which
the node has received a recent MID message. It should still allow to
cover all 2-hop interfaces of other 2-hop neighbors to avoid the
chicken and egg problem.

 > 
 > - How does a node determine which interfaces should be used to (re)transmit
 > network-wide broadcast messages?

As mentioned above, all interfaces retransmit.

 > 
 > - It is stated that HELLO messages are transmitted on all interfaces. Isn't
 > this a waste of resources?

Hello messages are transmitted on all OLSR interfaces. It is necessary
to monitor connectivity on all interfaces. To allow 2-hop neighbor
knowledge, all the information has to be transmitted on all interfaces
from time to time. However, we could easily allow to send different
messages per interface (it would naturally fit with partial Hellos)
but again we preferred simplicity rather than a minor optimization.

 > 
 > Thank you in advance.
 > Ioannis Avramopoulos
 > 
 > 

Thanks for you remarks, we are very interested in your feedback.


Laurent


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



From manet-admin@ietf.org  Tue Mar 12 15:50:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06661
	for <manet-archive@odin.ietf.org>; Tue, 12 Mar 2002 15:50:55 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08527;
	Tue, 12 Mar 2002 15:22:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08495
	for <manet@optimus.ietf.org>; Tue, 12 Mar 2002 15:21:57 -0500 (EST)
Received: from Princeton.EDU (postoffice.Princeton.EDU [128.112.129.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05392
	for <manet@ietf.org>; Tue, 12 Mar 2002 15:21:54 -0500 (EST)
Received: from smtpserver2.Princeton.EDU (smtpserver2.Princeton.EDU [128.112.129.148])
	by Princeton.EDU (8.12.2/8.12.2) with ESMTP id g2CKKPaa019649;
	Tue, 12 Mar 2002 15:20:25 -0500 (EST)
Received: from webmail (mailserver1.Princeton.EDU [128.112.129.147])
	by smtpserver2.Princeton.EDU (8.12.2/8.12.2) with SMTP id g2CKKOdo004347;
	Tue, 12 Mar 2002 15:20:24 -0500 (EST)
Date: Tue, 12 Mar 2002 15:20:24 -0500 (EST)
From: iavramop@princeton.edu (Ioannis C Avramopoulos)
To: Laurent.Viennot@inria.fr
Cc: manet@ietf.org
Subject: Re: [manet] OLSR questions
X-Mailer: Netscape Messenger Express 3.5.2 [Mozilla/4.76 [en] (Windows NT 5.0; U)]
Message-ID: <3C8E6308.701B@mailserver1.Princeton.EDU>
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Dear Laurent,

thank you for your clarifications. I still have some questions. See below.

Ioannis
 
>> - What are the advantages of having a LOST_LINK type over having no
>>such type (version 4 for example did not have such link type)?

>It allows quicker update of one hop and especially two hop
>neighborhood. A node announcing a neighbor loss allows its neighbors
>to remove the link (without waiting for expiration) from their 2-hop
>neighbor set.

Lets assume that initially nodes A and B have a bidirectional link and at
some time the link becomes unidirectional from A to B (A->B). After the
timeout of A expires and A has not received any HELLO from B, A may instead
of listing B with link type LOST_LINK may not list B at all. We can simply
add a rule in B to consider the link with A unidirectional if B is not
listed in A's HELLO (instead of considering A as a unidirectional link if B
is listed as LOST_LINK) and therefore we don't have to wait for the
timeout.

Similarly if we have another node C that is a neighbor of A and a 2-hop
neighbor of B (C-A-B) when the topology becomes C-A->B if B is not listed
in A's HELLO we may simply add a rule in C that purges B from the 2-hop
neighborhood.

If the aforementioned rule is added I still don't see why a LOST_LINK type
is beneficial.


>> - Why should a node have multiple interfaces all running the OLSR
>>protocol?

>several radio interfaces with directional antennas (and possibly same
>radio channel).

>> - Does the IEEE 802.11 specification make any provision for the
>>scenario of a node possessing multiple interfaces?

>No. It is in charge of the routing layer.

If you have several interfaces with directional antennas then it is
possible that they overlap. Packets that are transmitted over all
interfaces simultaneously will collide at nodes that are within the
overlap. Since IEEE 802.11 does not arbitrate access to the broadcast
channel and it is the responsibility of the routing layer then the routing
layer should deal with such cases.

I have one more general remark. I believe that considering multiple
interfaces makes the presentation of neighbor sensing not very
straightforward (in version 4 for example where multiple interfaces are not
considered the presentation is straighforward). Maybe you could consider
presenting neighbor sensing separately for the cases of single and multiple
interfaces and more clearly state the objectives and assumptions of
multiple interfaces. But this is just my opinion...

Thanks again
Ioannis






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


From daemon@optimus.ietf.org  Tue Mar 12 15:51:00 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06676
	for <manet-archive@odin.ietf.org>; Tue, 12 Mar 2002 15:51:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA11158
	for manet-archive@odin.ietf.org; Tue, 12 Mar 2002 15:51:02 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08527;
	Tue, 12 Mar 2002 15:22:01 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08495
	for <manet@optimus.ietf.org>; Tue, 12 Mar 2002 15:21:57 -0500 (EST)
Received: from Princeton.EDU (postoffice.Princeton.EDU [128.112.129.120])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05392
	for <manet@ietf.org>; Tue, 12 Mar 2002 15:21:54 -0500 (EST)
Received: from smtpserver2.Princeton.EDU (smtpserver2.Princeton.EDU [128.112.129.148])
	by Princeton.EDU (8.12.2/8.12.2) with ESMTP id g2CKKPaa019649;
	Tue, 12 Mar 2002 15:20:25 -0500 (EST)
Received: from webmail (mailserver1.Princeton.EDU [128.112.129.147])
	by smtpserver2.Princeton.EDU (8.12.2/8.12.2) with SMTP id g2CKKOdo004347;
	Tue, 12 Mar 2002 15:20:24 -0500 (EST)
Date: Tue, 12 Mar 2002 15:20:24 -0500 (EST)
From: iavramop@princeton.edu (Ioannis C Avramopoulos)
To: Laurent.Viennot@inria.fr
Cc: manet@ietf.org
Subject: Re: [manet] OLSR questions
X-Mailer: Netscape Messenger Express 3.5.2 [Mozilla/4.76 [en] (Windows NT 5.0; U)]
Message-ID: <3C8E6308.701B@mailserver1.Princeton.EDU>
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Dear Laurent,

thank you for your clarifications. I still have some questions. See below.

Ioannis
 
>> - What are the advantages of having a LOST_LINK type over having no
>>such type (version 4 for example did not have such link type)?

>It allows quicker update of one hop and especially two hop
>neighborhood. A node announcing a neighbor loss allows its neighbors
>to remove the link (without waiting for expiration) from their 2-hop
>neighbor set.

Lets assume that initially nodes A and B have a bidirectional link and at
some time the link becomes unidirectional from A to B (A->B). After the
timeout of A expires and A has not received any HELLO from B, A may instead
of listing B with link type LOST_LINK may not list B at all. We can simply
add a rule in B to consider the link with A unidirectional if B is not
listed in A's HELLO (instead of considering A as a unidirectional link if B
is listed as LOST_LINK) and therefore we don't have to wait for the
timeout.

Similarly if we have another node C that is a neighbor of A and a 2-hop
neighbor of B (C-A-B) when the topology becomes C-A->B if B is not listed
in A's HELLO we may simply add a rule in C that purges B from the 2-hop
neighborhood.

If the aforementioned rule is added I still don't see why a LOST_LINK type
is beneficial.


>> - Why should a node have multiple interfaces all running the OLSR
>>protocol?

>several radio interfaces with directional antennas (and possibly same
>radio channel).

>> - Does the IEEE 802.11 specification make any provision for the
>>scenario of a node possessing multiple interfaces?

>No. It is in charge of the routing layer.

If you have several interfaces with directional antennas then it is
possible that they overlap. Packets that are transmitted over all
interfaces simultaneously will collide at nodes that are within the
overlap. Since IEEE 802.11 does not arbitrate access to the broadcast
channel and it is the responsibility of the routing layer then the routing
layer should deal with such cases.

I have one more general remark. I believe that considering multiple
interfaces makes the presentation of neighbor sensing not very
straightforward (in version 4 for example where multiple interfaces are not
considered the presentation is straighforward). Maybe you could consider
presenting neighbor sensing separately for the cases of single and multiple
interfaces and more clearly state the objectives and assumptions of
multiple interfaces. But this is just my opinion...

Thanks again
Ioannis






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



From manet-admin@ietf.org  Tue Mar 12 17:06:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09876
	for <manet-archive@odin.ietf.org>; Tue, 12 Mar 2002 17:06:07 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA14347;
	Tue, 12 Mar 2002 16:32:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA14313
	for <manet@optimus.ietf.org>; Tue, 12 Mar 2002 16:32:31 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08560
	for <manet@ietf.org>; Tue, 12 Mar 2002 16:32:28 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id NAA15668;
	Tue, 12 Mar 2002 13:30:36 -0800 (PST)
Message-Id: <200203122130.NAA15668@pit.erg.sri.com>
To: "Tao Lin" <taolin@vt.edu>
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] TBRPF with multicast applications 
In-reply-to: Your message of "Mon, 11 Mar 2002 17:20:45 EST."
             <001101c1c94a$fd72b300$7637ad80@workgroup> 
Date: Tue, 12 Mar 2002 13:30:36 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Tao,

> TBRPF provides information for only one path (or maybe two, like an optional
> choice indicated in the TBRPF draft) per destination. In a network with
> heavy multicast traffic load, I think it might have more congestions with
> TBRPF protocol. Are there any multicast extensions for TBRPF or studies on
> this topic?

Yes, you can find our multicast extension to TBRPF at the the TBRPF web site: 
http://www.erg.sri.com/projects/tbrpf/docs/tbrpf_multicast.doc

We also have a flooding extension which is described in our updated draft:
http://ietf.org/internet-drafts/draft-ietf-manet-tbrpf-05.txt

It may also be possible to adapt multicast protocols developed for
other link-state routing protocols, or to use one that is independent
of the underlying routing protocol.  However, my understanding is that
multicast is not currently within the manet scope.

Richard


> Thanks!
> 
> Tao Lin
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Tue Mar 12 17:06:08 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09886
	for <manet-archive@odin.ietf.org>; Tue, 12 Mar 2002 17:06:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA16920
	for manet-archive@odin.ietf.org; Tue, 12 Mar 2002 17:06:10 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA14347;
	Tue, 12 Mar 2002 16:32:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA14313
	for <manet@optimus.ietf.org>; Tue, 12 Mar 2002 16:32:31 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08560
	for <manet@ietf.org>; Tue, 12 Mar 2002 16:32:28 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id NAA15668;
	Tue, 12 Mar 2002 13:30:36 -0800 (PST)
Message-Id: <200203122130.NAA15668@pit.erg.sri.com>
To: "Tao Lin" <taolin@vt.edu>
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] TBRPF with multicast applications 
In-reply-to: Your message of "Mon, 11 Mar 2002 17:20:45 EST."
             <001101c1c94a$fd72b300$7637ad80@workgroup> 
Date: Tue, 12 Mar 2002 13:30:36 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Tao,

> TBRPF provides information for only one path (or maybe two, like an optional
> choice indicated in the TBRPF draft) per destination. In a network with
> heavy multicast traffic load, I think it might have more congestions with
> TBRPF protocol. Are there any multicast extensions for TBRPF or studies on
> this topic?

Yes, you can find our multicast extension to TBRPF at the the TBRPF web site: 
http://www.erg.sri.com/projects/tbrpf/docs/tbrpf_multicast.doc

We also have a flooding extension which is described in our updated draft:
http://ietf.org/internet-drafts/draft-ietf-manet-tbrpf-05.txt

It may also be possible to adapt multicast protocols developed for
other link-state routing protocols, or to use one that is independent
of the underlying routing protocol.  However, my understanding is that
multicast is not currently within the manet scope.

Richard


> Thanks!
> 
> Tao Lin
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Tue Mar 12 17:28:55 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10418
	for <manet-archive@odin.ietf.org>; Tue, 12 Mar 2002 17:28:55 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA10818;
	Tue, 12 Mar 2002 15:48:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA10774
	for <manet@optimus.ietf.org>; Tue, 12 Mar 2002 15:48:39 -0500 (EST)
Received: from email.nist.gov (email.nist.gov [129.6.2.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06471
	for <manet@ietf.org>; Tue, 12 Mar 2002 15:48:36 -0500 (EST)
Received: from gwialo (camelot.antd.nist.gov [129.6.50.51])
	by email.nist.gov (8.12.2/8.12.2) with SMTP id g2CKmdjA025285
	for <manet@ietf.org>; Tue, 12 Mar 2002 15:48:39 -0500 (EST)
From: "Luke Klein-Berndt" <luke.klein-berndt@nist.gov>
To: <manet@ietf.org>
Date: Tue, 12 Mar 2002 15:48:39 -0500
Message-ID: <LMEPJIBDDGLOMAJBLGOMIEFJCCAA.luke.klein-berndt@nist.gov>
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 IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [manet] Kernel AODV Update - v1.5
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


I am happy to announce an update to Kernel AODV. Kernel AODV is an
implemention of AODV developed at NIST that runs in Linux as a Kernel
Module.

The update features:
 - Support for multiple network interfaces
 - Complies with v10 of the AODV draft
 - Easier to compile and run
 - Since it is a module it requires no kernel modifacation
 - Support for ARM processors, tested on Linux PDA

It is available at - http://w3.antd.nist.gov/wctg/aodv_kernel/

Thank you,

Luke Klein-Berndt


............................................
 Luke Klein-Berndt, Computer Scientist
 Wireless Communications Technologies Group
 National Institute of Standards and Technology

 Phone:  (301) 975-8029
 E-Mail:  kleinb@nist.gov
 Web:  http://w3.antd.nist.gov/wctg/index.html
............................................


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


From daemon@ns.ietf.org  Tue Mar 12 17:28:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10429
	for <manet-archive@odin.ietf.org>; Tue, 12 Mar 2002 17:28:55 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA19121
	for manet-archive@odin.ietf.org; Tue, 12 Mar 2002 17:28:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA10818;
	Tue, 12 Mar 2002 15:48:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA10774
	for <manet@optimus.ietf.org>; Tue, 12 Mar 2002 15:48:39 -0500 (EST)
Received: from email.nist.gov (email.nist.gov [129.6.2.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06471
	for <manet@ietf.org>; Tue, 12 Mar 2002 15:48:36 -0500 (EST)
Received: from gwialo (camelot.antd.nist.gov [129.6.50.51])
	by email.nist.gov (8.12.2/8.12.2) with SMTP id g2CKmdjA025285
	for <manet@ietf.org>; Tue, 12 Mar 2002 15:48:39 -0500 (EST)
From: "Luke Klein-Berndt" <luke.klein-berndt@nist.gov>
To: <manet@ietf.org>
Date: Tue, 12 Mar 2002 15:48:39 -0500
Message-ID: <LMEPJIBDDGLOMAJBLGOMIEFJCCAA.luke.klein-berndt@nist.gov>
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 IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [manet] Kernel AODV Update - v1.5
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


I am happy to announce an update to Kernel AODV. Kernel AODV is an
implemention of AODV developed at NIST that runs in Linux as a Kernel
Module.

The update features:
 - Support for multiple network interfaces
 - Complies with v10 of the AODV draft
 - Easier to compile and run
 - Since it is a module it requires no kernel modifacation
 - Support for ARM processors, tested on Linux PDA

It is available at - http://w3.antd.nist.gov/wctg/aodv_kernel/

Thank you,

Luke Klein-Berndt


............................................
 Luke Klein-Berndt, Computer Scientist
 Wireless Communications Technologies Group
 National Institute of Standards and Technology

 Phone:  (301) 975-8029
 E-Mail:  kleinb@nist.gov
 Web:  http://w3.antd.nist.gov/wctg/index.html
............................................


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



From manet-admin@ietf.org  Tue Mar 12 18:02:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11336
	for <manet-archive@odin.ietf.org>; Tue, 12 Mar 2002 18:02:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA20044;
	Tue, 12 Mar 2002 17:39:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA20016
	for <manet@ns.ietf.org>; Tue, 12 Mar 2002 17:39:16 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10692
	for <manet@ietf.org>; Tue, 12 Mar 2002 17:39:12 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id OAA15804;
	Tue, 12 Mar 2002 14:37:21 -0800 (PST)
Message-Id: <200203122237.OAA15804@pit.erg.sri.com>
To: "Philippe Jacquet" <philippe.jacquet@inria.fr>
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
In-reply-to: Your message of "Mon, 11 Mar 2002 18:35:55 +0100."
             <00a901c1c923$32e82ec0$3ac033c1@inria.fr> 
Date: Tue, 12 Mar 2002 14:37:21 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

> Richard,
> 
> I am not looking for errors. This would be a very unpleasant task and the
> protocol is far too complex for that. I am just looking for proofs. Unlike
> OLSR, TBRPF is not known to be proven. OLSR proofs are rather simple. There
> is nothing in the optimisations we have introduced so far that don't go
> along OLSR proofs of correctness. Do you have a proof of TBRPF correctness?
> I have just some doubts that obsolete topology informations may endlessly
> circulate in the network and your complex optimisation process may
> potentially increase this risk. I was wondering if  a simpler version of the
> protocol without optimisation may have helped you to figure out a proof of
> correctness.
> 
> Philippe
> 

Philippe,

The correctness proof for TBRPF is given below.
The property that prevents topology information from endlessly
circulating is the "reporting neighbor rule" (defined below).
This is the same concept that ensures correctness for SPTA
[Bertsekas and Gallager, Data Networks, 1987].  

TBRPF is not really very complex. In fact, the Update_Routes() 
procedure is just a variant of Dijkstra's algorithm, and can be 
implemented so that its running time is the same order as Dijkstra's.
Actually, in some ways TBRPF is simpler than OLSR, which I will discuss
in a later email.  Some aspects of TBRPF may be a little more complex 
than OLSR, but this should be acceptable if it results in significantly
better performance/efficiency.

First I will review some aspects of TBRPF that will help to understand 
the proof. Let RN(i) denote the reportable node set RN that is computed 
by node i. A neighbor j is in RN(i) if and only if there exists another 
neighbor k that is not a neighbor of j, such that node i is the node 
with the smallest ID through which node k can reach node j in 2 hops.  
RN is computed by the procedure Update_RN(), which simply computes 
min-hop paths, up to 2 hops, from each neighbor to each other neighbor.

Each node reports part of its source tree T, called its reportable 
subtree RT, to neighbors in periodic and differential updates.  A node 
uses RN to determine which part of T to report, as follows: A node 
reports all of its adjacent links, and reports only the branches of T 
that are rooted at neighbors in RN.  Each node i maintains the 
reportable subtree RT_j reported by each neighbor j. 

The procedure Update_Routes() is a variant of Dijkstra's algorithm that 
computes min-hop paths to all nodes, and also updates the topology graph
TG, which consists of the links that are "believable". A link (u,v) is
believable if and only if it is reported by the next hop p(u) on the 
min-hop path to node u. This is similar to SPTA, which also does not 
use sequence numbers, maintains the topology reported by each neighbor,
and maintains a set of "believable" links. 
However, in SPTA each node reports the full topology, whereas in TBRPF 
each node reports only part of its source tree.

The paths computed by Update_Routes() have the following two properties
which are important to ensure correctness: 

(1) Reporting neighbor rule: A link (u,v) can be in a computed path (to
any destination) only if it is reported by the next hop p(u) on the path
(i.e., only if it is in TG).

(2) The predecessor (next-to-last node) on the min-hop path to any node
is selected to have the minimum ID. As a result, the computed paths are 
"lexicographic" min-hop paths, defined as follows.

Definition. A min-hop path from node i to node u, with nodes 
i = v_1,..., v_n = u, is said to be a "lexicographic" min-hop path if,
for each m = 2,..., n-1, node v_m has the minimum ID of any predecessor 
to node v_{m+1} in any min-hop path from node i to node v_{m+1}.

A link (u,v) can actually remain in TG for a few seconds 
(PER_UPDATE_INTERVAL) after it is no longer reported by p(u), but this 
does not affect the proof below, since this is only a temporary 
violation of the reporting neighbor rule.

The following proof is similar to the proof of SPTA, and is also similar
to the proof of PTSP [MOMUC '99], which also does not use sequence numbers
and has each node report only part of its source tree.

Theorem 1. If no topology changes occur after some time t_0, then within
some finite time after t_0, the source tree T computed by each node will
contain min-hop paths to all reachable nodes.

Proof. The proof will be by induction on the number of hops m.

Induction hypothesis: For each m = 1,2,..., there exists some finite 
time t_m after which each node (1) has computed a lexicographically 
minimum min-hop path to each node u that is m or fewer hops away, 
and (2) has not computed a path of m or fewer hops to any node that 
is more than m hops away (or is unreachable).

The hypothesis is trivially true for m = 1, since each node knows its 
set of neighbors.  (We assume that neighbor discovery is done correctly.)

Now suppose the hypothesis is true for some m >= 1.  We will show that 
it is true for m+1, which will prove the theorem by induction.

Since each node reports its reportable subtree RT in periodic 
updates, any link that remains in RT is received by all neighbors within 
finite time.  Conversely, since topology information from neighbors 
expires after TOP_HOLD_TIME, if a node removes a link from RT, then
all neighbors will know it is removed within this time interval.

Let i be any node, and let u be any node that is exactly m+1 hops from 
node i. Let P be the lexicographic min-hop path from node i to node u. 
Let j be the second node (next hop), let k be the third node, and let 
w be the next-to-last node on P.

Since node u is m hops from node j, the induction hypothesis for m 
implies that node j has computed the lexicographic min-hop path to 
node u, which by the definition of lexicographic must equal the part
of P from j to u. Also by the definition of lexicographic, node j is 
the next hop from node i to node k having the smallest ID, implying 
that k is in RN(j), so that node j is reporting the branch of its 
source tree rooted at node k. In particular, node j is reporting 
the link (w,u).

Consider the point in Update_Routes() after all m-hop paths have been
computed. By the induction hypothesis for m, node i has computed a 
lexicographic min-hop path to each node that is m or fewer hops away, 
including node w, and has not computed a path having m or fewer hops 
to any node that is more than m hops away.  As a result, since node j 
is reporting link (w,u) and since w is the minimum ID predecessor to 
node u, Update_Routes() will add link (w,u) to its source tree, so that 
its computed path to u is P.  This proves the first part of the 
induction hypothesis for m+1.

To prove the second part, let v be any node that is more than m+1 
hops away from node i, and suppose that node i has computed a path Q 
to node v.  By the reporting neighbor rule, the second node k on Q
must be reporting the part of Q from k to v.  Since node v is more 
than m hops away from node k, by the induction hypothesis for m, 
the path computed by k to node v must have more than m hops, implying 
that path Q has more than m+1 hops.  This proves the second part of 
the induction hypothesis for m+1, thus proving the theorem.

Richard


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


From daemon@ns.ietf.org  Tue Mar 12 18:02:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11347
	for <manet-archive@odin.ietf.org>; Tue, 12 Mar 2002 18:02:54 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA21753
	for manet-archive@odin.ietf.org; Tue, 12 Mar 2002 18:02:57 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA20044;
	Tue, 12 Mar 2002 17:39:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA20016
	for <manet@ns.ietf.org>; Tue, 12 Mar 2002 17:39:16 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10692
	for <manet@ietf.org>; Tue, 12 Mar 2002 17:39:12 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id OAA15804;
	Tue, 12 Mar 2002 14:37:21 -0800 (PST)
Message-Id: <200203122237.OAA15804@pit.erg.sri.com>
To: "Philippe Jacquet" <philippe.jacquet@inria.fr>
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: RE : others cretaria in MANET routing protocol 
In-reply-to: Your message of "Mon, 11 Mar 2002 18:35:55 +0100."
             <00a901c1c923$32e82ec0$3ac033c1@inria.fr> 
Date: Tue, 12 Mar 2002 14:37:21 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

> Richard,
> 
> I am not looking for errors. This would be a very unpleasant task and the
> protocol is far too complex for that. I am just looking for proofs. Unlike
> OLSR, TBRPF is not known to be proven. OLSR proofs are rather simple. There
> is nothing in the optimisations we have introduced so far that don't go
> along OLSR proofs of correctness. Do you have a proof of TBRPF correctness?
> I have just some doubts that obsolete topology informations may endlessly
> circulate in the network and your complex optimisation process may
> potentially increase this risk. I was wondering if  a simpler version of the
> protocol without optimisation may have helped you to figure out a proof of
> correctness.
> 
> Philippe
> 

Philippe,

The correctness proof for TBRPF is given below.
The property that prevents topology information from endlessly
circulating is the "reporting neighbor rule" (defined below).
This is the same concept that ensures correctness for SPTA
[Bertsekas and Gallager, Data Networks, 1987].  

TBRPF is not really very complex. In fact, the Update_Routes() 
procedure is just a variant of Dijkstra's algorithm, and can be 
implemented so that its running time is the same order as Dijkstra's.
Actually, in some ways TBRPF is simpler than OLSR, which I will discuss
in a later email.  Some aspects of TBRPF may be a little more complex 
than OLSR, but this should be acceptable if it results in significantly
better performance/efficiency.

First I will review some aspects of TBRPF that will help to understand 
the proof. Let RN(i) denote the reportable node set RN that is computed 
by node i. A neighbor j is in RN(i) if and only if there exists another 
neighbor k that is not a neighbor of j, such that node i is the node 
with the smallest ID through which node k can reach node j in 2 hops.  
RN is computed by the procedure Update_RN(), which simply computes 
min-hop paths, up to 2 hops, from each neighbor to each other neighbor.

Each node reports part of its source tree T, called its reportable 
subtree RT, to neighbors in periodic and differential updates.  A node 
uses RN to determine which part of T to report, as follows: A node 
reports all of its adjacent links, and reports only the branches of T 
that are rooted at neighbors in RN.  Each node i maintains the 
reportable subtree RT_j reported by each neighbor j. 

The procedure Update_Routes() is a variant of Dijkstra's algorithm that 
computes min-hop paths to all nodes, and also updates the topology graph
TG, which consists of the links that are "believable". A link (u,v) is
believable if and only if it is reported by the next hop p(u) on the 
min-hop path to node u. This is similar to SPTA, which also does not 
use sequence numbers, maintains the topology reported by each neighbor,
and maintains a set of "believable" links. 
However, in SPTA each node reports the full topology, whereas in TBRPF 
each node reports only part of its source tree.

The paths computed by Update_Routes() have the following two properties
which are important to ensure correctness: 

(1) Reporting neighbor rule: A link (u,v) can be in a computed path (to
any destination) only if it is reported by the next hop p(u) on the path
(i.e., only if it is in TG).

(2) The predecessor (next-to-last node) on the min-hop path to any node
is selected to have the minimum ID. As a result, the computed paths are 
"lexicographic" min-hop paths, defined as follows.

Definition. A min-hop path from node i to node u, with nodes 
i = v_1,..., v_n = u, is said to be a "lexicographic" min-hop path if,
for each m = 2,..., n-1, node v_m has the minimum ID of any predecessor 
to node v_{m+1} in any min-hop path from node i to node v_{m+1}.

A link (u,v) can actually remain in TG for a few seconds 
(PER_UPDATE_INTERVAL) after it is no longer reported by p(u), but this 
does not affect the proof below, since this is only a temporary 
violation of the reporting neighbor rule.

The following proof is similar to the proof of SPTA, and is also similar
to the proof of PTSP [MOMUC '99], which also does not use sequence numbers
and has each node report only part of its source tree.

Theorem 1. If no topology changes occur after some time t_0, then within
some finite time after t_0, the source tree T computed by each node will
contain min-hop paths to all reachable nodes.

Proof. The proof will be by induction on the number of hops m.

Induction hypothesis: For each m = 1,2,..., there exists some finite 
time t_m after which each node (1) has computed a lexicographically 
minimum min-hop path to each node u that is m or fewer hops away, 
and (2) has not computed a path of m or fewer hops to any node that 
is more than m hops away (or is unreachable).

The hypothesis is trivially true for m = 1, since each node knows its 
set of neighbors.  (We assume that neighbor discovery is done correctly.)

Now suppose the hypothesis is true for some m >= 1.  We will show that 
it is true for m+1, which will prove the theorem by induction.

Since each node reports its reportable subtree RT in periodic 
updates, any link that remains in RT is received by all neighbors within 
finite time.  Conversely, since topology information from neighbors 
expires after TOP_HOLD_TIME, if a node removes a link from RT, then
all neighbors will know it is removed within this time interval.

Let i be any node, and let u be any node that is exactly m+1 hops from 
node i. Let P be the lexicographic min-hop path from node i to node u. 
Let j be the second node (next hop), let k be the third node, and let 
w be the next-to-last node on P.

Since node u is m hops from node j, the induction hypothesis for m 
implies that node j has computed the lexicographic min-hop path to 
node u, which by the definition of lexicographic must equal the part
of P from j to u. Also by the definition of lexicographic, node j is 
the next hop from node i to node k having the smallest ID, implying 
that k is in RN(j), so that node j is reporting the branch of its 
source tree rooted at node k. In particular, node j is reporting 
the link (w,u).

Consider the point in Update_Routes() after all m-hop paths have been
computed. By the induction hypothesis for m, node i has computed a 
lexicographic min-hop path to each node that is m or fewer hops away, 
including node w, and has not computed a path having m or fewer hops 
to any node that is more than m hops away.  As a result, since node j 
is reporting link (w,u) and since w is the minimum ID predecessor to 
node u, Update_Routes() will add link (w,u) to its source tree, so that 
its computed path to u is P.  This proves the first part of the 
induction hypothesis for m+1.

To prove the second part, let v be any node that is more than m+1 
hops away from node i, and suppose that node i has computed a path Q 
to node v.  By the reporting neighbor rule, the second node k on Q
must be reporting the part of Q from k to v.  Since node v is more 
than m hops away from node k, by the induction hypothesis for m, 
the path computed by k to node v must have more than m hops, implying 
that path Q has more than m+1 hops.  This proves the second part of 
the induction hypothesis for m+1, thus proving the theorem.

Richard


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



From manet-admin@ietf.org  Wed Mar 13 00:46:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20346
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 00:46:57 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA09685;
	Wed, 13 Mar 2002 00:17:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA09655
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 00:17:26 -0500 (EST)
Received: from 263.net ([202.96.44.45])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19892
	for <manet@ietf.org>; Wed, 13 Mar 2002 00:17:24 -0500 (EST)
From: wht_slh@263.net
Received: by 263.net (Postfix, from userid 60001)
	id BB47F1CEB76F2; Wed, 13 Mar 2002 13:23:57 +0800 (CST)
MIME-Version: 1.0
Message-ID: <3C8EE26D.000026.01350@mta3>
Date: Wed, 13 Mar 2002 13:23:57 +0800 (CST)
To: manet@ietf.org
X-Priority: 3
X-Originating-IP: [210.77.247.11]
X-Mailer: Coremail2.0 Copyright Tebie Ltd., 2001
Subject: [manet] =?gb2312?B?QSBRVUVTVElPTiBPTiBNQUMgQU5EIFNDSEVEVUxFIElOIE1BTkVUPw==?=
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

in manet, mac or channel access is a critical function in supporting qos, but schedule is too. And its aim is to improve througput and fairness, while reducing latency, which is similar with mac protocol? who can tell me some difference between mac and schedule?




__________________________________________
ÓÊ¼þµ½ÁËÂð?ÊÖ»ú¸æËßÄã(http://mail.263.net/mmail/index.html)
µã»÷ÏÂÔØ95963ÉÏÍøÖ±Í¨³µ(http://www.263.net/0ji/StarDialer.exe)
ÎÒÄÃÊ²Ã´À´ÓÕ»óÄã(http://95963.263.net/)
»¯×±Æ·ÈýÕÛ,ÏãË®°ë¼Û(http://shopping.263.net/class004.htm)

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


From daemon@ns.ietf.org  Wed Mar 13 00:46:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20356
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 00:46:58 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA11474
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 00:46:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA09685;
	Wed, 13 Mar 2002 00:17:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA09655
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 00:17:26 -0500 (EST)
Received: from 263.net ([202.96.44.45])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19892
	for <manet@ietf.org>; Wed, 13 Mar 2002 00:17:24 -0500 (EST)
From: wht_slh@263.net
Received: by 263.net (Postfix, from userid 60001)
	id BB47F1CEB76F2; Wed, 13 Mar 2002 13:23:57 +0800 (CST)
MIME-Version: 1.0
Message-ID: <3C8EE26D.000026.01350@mta3>
Date: Wed, 13 Mar 2002 13:23:57 +0800 (CST)
To: manet@ietf.org
X-Priority: 3
X-Originating-IP: [210.77.247.11]
X-Mailer: Coremail2.0 Copyright Tebie Ltd., 2001
Subject: [manet] =?gb2312?B?QSBRVUVTVElPTiBPTiBNQUMgQU5EIFNDSEVEVUxFIElOIE1BTkVUPw==?=
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

in manet, mac or channel access is a critical function in supporting qos, but schedule is too. And its aim is to improve througput and fairness, while reducing latency, which is similar with mac protocol? who can tell me some difference between mac and schedule?




__________________________________________
ÓÊ¼þµ½ÁËÂð?ÊÖ»ú¸æËßÄã(http://mail.263.net/mmail/index.html)
µã»÷ÏÂÔØ95963ÉÏÍøÖ±Í¨³µ(http://www.263.net/0ji/StarDialer.exe)
ÎÒÄÃÊ²Ã´À´ÓÕ»óÄã(http://95963.263.net/)
»¯×±Æ·ÈýÕÛ,ÏãË®°ë¼Û(http://shopping.263.net/class004.htm)

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



From manet-admin@ietf.org  Wed Mar 13 00:51:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20458
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 00:51:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA09835;
	Wed, 13 Mar 2002 00:20:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA09807
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 00:20:20 -0500 (EST)
Received: from 263.net ([202.96.44.45])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19927
	for <manet@ietf.org>; Wed, 13 Mar 2002 00:20:18 -0500 (EST)
From: wht_slh@263.net
Received: by 263.net (Postfix, from userid 60001)
	id 77E461CEB7632; Wed, 13 Mar 2002 13:26:49 +0800 (CST)
MIME-Version: 1.0
Message-ID: <3C8EE318.00003F.01350@mta3>
Date: Wed, 13 Mar 2002 13:26:48 +0800 (CST)
To: manet@ietf.org
X-Priority: 3
X-Originating-IP: [210.77.247.11]
X-Mailer: Coremail2.0 Copyright Tebie Ltd., 2001
Subject: [manet] =?gb2312?B?QSBRVUVTVElPTiBPTiBGUkVRVUVOQ1kgQU5EIFNQQVRJQUwgUkVVU0U/?=
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

I read a artical" an architecture for mobile radio networks with dynamically changing topology using virtual subnets¡±. I have some trouble in understanding this article. why one large ad hoc network cannot take advantage of many frequencies because of spatial reuse? who can explain it in detail, better using a example.
   Best regard
                        Wang haitao 





__________________________________________
ÓÊ¼þµ½ÁËÂð?ÊÖ»ú¸æËßÄã(http://mail.263.net/mmail/index.html)
µã»÷ÏÂÔØ95963ÉÏÍøÖ±Í¨³µ(http://www.263.net/0ji/StarDialer.exe)
ÎÒÄÃÊ²Ã´À´ÓÕ»óÄã(http://95963.263.net/)
»¯×±Æ·ÈýÕÛ,ÏãË®°ë¼Û(http://shopping.263.net/class004.htm)

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


From daemon@ns.ietf.org  Wed Mar 13 00:51:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20469
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 00:51:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA11855
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 00:51:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA09835;
	Wed, 13 Mar 2002 00:20:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA09807
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 00:20:20 -0500 (EST)
Received: from 263.net ([202.96.44.45])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA19927
	for <manet@ietf.org>; Wed, 13 Mar 2002 00:20:18 -0500 (EST)
From: wht_slh@263.net
Received: by 263.net (Postfix, from userid 60001)
	id 77E461CEB7632; Wed, 13 Mar 2002 13:26:49 +0800 (CST)
MIME-Version: 1.0
Message-ID: <3C8EE318.00003F.01350@mta3>
Date: Wed, 13 Mar 2002 13:26:48 +0800 (CST)
To: manet@ietf.org
X-Priority: 3
X-Originating-IP: [210.77.247.11]
X-Mailer: Coremail2.0 Copyright Tebie Ltd., 2001
Subject: [manet] =?gb2312?B?QSBRVUVTVElPTiBPTiBGUkVRVUVOQ1kgQU5EIFNQQVRJQUwgUkVVU0U/?=
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

I read a artical" an architecture for mobile radio networks with dynamically changing topology using virtual subnets¡±. I have some trouble in understanding this article. why one large ad hoc network cannot take advantage of many frequencies because of spatial reuse? who can explain it in detail, better using a example.
   Best regard
                        Wang haitao 





__________________________________________
ÓÊ¼þµ½ÁËÂð?ÊÖ»ú¸æËßÄã(http://mail.263.net/mmail/index.html)
µã»÷ÏÂÔØ95963ÉÏÍøÖ±Í¨³µ(http://www.263.net/0ji/StarDialer.exe)
ÎÒÄÃÊ²Ã´À´ÓÕ»óÄã(http://95963.263.net/)
»¯×±Æ·ÈýÕÛ,ÏãË®°ë¼Û(http://shopping.263.net/class004.htm)

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



From manet-admin@ietf.org  Wed Mar 13 14:13:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15476
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 14:13:21 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA04267;
	Wed, 13 Mar 2002 13:45:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA04231
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 13:45:28 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14740
	for <manet@ietf.org>; Wed, 13 Mar 2002 13:45:25 -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 NAA14086
	for <manet@ietf.org>; Wed, 13 Mar 2002 13:45:25 -0500 (EST)
Message-Id: <5.0.1.4.2.20020313135419.03206000@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 13 Mar 2002 13:55:27 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [manet] Draft manet agenda for Minneapolis
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Here is the initial draft agenda for the upcoming meeting.

*************************************************
Salon C RTG manet Mobile Ad-hoc Networks WG 
Mobile Ad Hoc Networks (manet) Agenda
Monday, March 18, 19:30-22:00

Agenda Bashing
 
* Status/Discussion of AODV Submission Review

Updates of Current Drafts

* DSR update, D. Johnson (Rice)

* OLSR update, T. Clausen (INRIA)

* TBRPF Update, Ogier/Templin (SRI)

New Discussions

* Manet extensions to OSPF, Fred Baker (CISCO) 

* Related Activity and Implementation Announcements

* Open Discussion


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


From daemon@ns.ietf.org  Wed Mar 13 14:13:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15489
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 14:13:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA06538
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 14:13:25 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA04267;
	Wed, 13 Mar 2002 13:45:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA04231
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 13:45:28 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14740
	for <manet@ietf.org>; Wed, 13 Mar 2002 13:45:25 -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 NAA14086
	for <manet@ietf.org>; Wed, 13 Mar 2002 13:45:25 -0500 (EST)
Message-Id: <5.0.1.4.2.20020313135419.03206000@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 13 Mar 2002 13:55:27 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [manet] Draft manet agenda for Minneapolis
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Here is the initial draft agenda for the upcoming meeting.

*************************************************
Salon C RTG manet Mobile Ad-hoc Networks WG 
Mobile Ad Hoc Networks (manet) Agenda
Monday, March 18, 19:30-22:00

Agenda Bashing
 
* Status/Discussion of AODV Submission Review

Updates of Current Drafts

* DSR update, D. Johnson (Rice)

* OLSR update, T. Clausen (INRIA)

* TBRPF Update, Ogier/Templin (SRI)

New Discussions

* Manet extensions to OSPF, Fred Baker (CISCO) 

* Related Activity and Implementation Announcements

* Open Discussion


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



From manet-admin@ietf.org  Wed Mar 13 15:06:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17191
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 15:06:53 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA08768;
	Wed, 13 Mar 2002 14:44:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA08740
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 14:44:45 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16444
	for <manet@ietf.org>; Wed, 13 Mar 2002 14:44:36 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id LAA17973;
	Wed, 13 Mar 2002 11:42:47 -0800 (PST)
Message-Id: <200203131942.LAA17973@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Tue, 12 Mar 2002 13:53:09 +0100."
             <15501.64053.570314.623276@impression.inria.fr> 
Date: Wed, 13 Mar 2002 11:42:47 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


I urge everyone to read this message.
It presents perhaps the clearest argument so far that 
OLSR's lack of separation between neighbor sensing and
topology discovery results in increased complexity.

By lack of separation, I mean that OLSR HELLOs are used not 
only for neighbor sensing, but also for discovering paths to 
nodes that are 2 hops away (and also for selecting MPRs),
which to me is part of topology discovery.

Please see my comments below.

> Ioannis C Avramopoulos wrote (referring to OLSR):
>  > 
>  > - It is stated that HELLO messages are transmitted on all interfaces. Isn't
>  > this a waste of resources?

Yes, I think it is a waste of resources. In both TBRPF and OSPF, each HELLO
message is sent only on one interface, i.e., neighbor sensing is performed
separately on each interface.  

The reason OLSR sends HELLOs on all interfaces is because HELLOs 
are used not only for neighbor sensing, but also for discovering nodes
that are 2 hops away.  Since different interfaces might be used for the 
2 hops, HELLOs must be sent on all interfaces. 

Laurent wrote:

> The formal rule is what you propose: any 2-hop neighbor must have an
> interface covered by some MPR. But the proposed heuristic selects an
> MPR set such that any 2-hop interface is covered.

> This is again for the sake of simplicity versus complex optimization
> not so useful. Notice that you have to be careful to avoid a chicken
> and egg problem if your computation of MPRs depend from the reception
> of MID messages when the forwarding of MID messages depends on MPR
> election. (You need to receive a MID message from a 2-hop neighbor to
> know all its interfaces.)

Laurent talks about simplicity, but here is one way in which OLSR is more
complex than TBRPF.  TBRPF does not have such a chicken-egg problem, i.e., 
parent selection does not depend on multiple interface information. 

Laurent may argue that TBRPF must still report all neighbors on all interfaces
in Topology Update messages, but not only are these sent less often than
HELLO_INTERVAL, it provides a clean separation between HELLOs (which are sent
on one interface) and Topology Updates (which are sent on all interfaces).

Laurent wrote:

> Hello messages are transmitted on all OLSR interfaces. It is necessary
> to monitor connectivity on all interfaces. To allow 2-hop neighbor
> knowledge, all the information has to be transmitted on all interfaces
> from time to time. However, we could easily allow to send different
> messages per interface (it would naturally fit with partial Hellos)
> but again we preferred simplicity rather than a minor optimization.

Laurent suggests the possibility of sending some HELLOs on all interfaces
and others on a single interface, to improve efficiency, but avoids this
approach for simplicity. Note that TBRPF achieves this efficiency
(by sending each HELLO on a single interface) as well as simplicity.

I am confident that anyone who reads and understands these arguments will
see that TBRPF is the better approach.  I only hope that enough people
will read and understand these arguments.

Since this message is about separation between neighbor sensing and
topology discovery, I would like to summarize other advantages that
TBRPF has in this regard:

1. If neighbor sensing is already provided in the link/mac layer (and I
know of at least two companies that do this), then TBRPF can be used
without HELLO messages, thus saving overhead.  

2. Since TBRPF neighbor sensing performs *only* neighbor sensing, it can 
be used with other routing protocols.  Conversely, other neighbor sensing
protocols can be used with TBRPF.

3. Because OSLR uses HELLOs to provide 2-hop information, each HELLO must
be sent on all interfaces (as discussed above).

Richard



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


From daemon@ns.ietf.org  Wed Mar 13 15:06:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17201
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 15:06:54 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA10826
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 15:06:55 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA08768;
	Wed, 13 Mar 2002 14:44:48 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA08740
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 14:44:45 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16444
	for <manet@ietf.org>; Wed, 13 Mar 2002 14:44:36 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id LAA17973;
	Wed, 13 Mar 2002 11:42:47 -0800 (PST)
Message-Id: <200203131942.LAA17973@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Tue, 12 Mar 2002 13:53:09 +0100."
             <15501.64053.570314.623276@impression.inria.fr> 
Date: Wed, 13 Mar 2002 11:42:47 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


I urge everyone to read this message.
It presents perhaps the clearest argument so far that 
OLSR's lack of separation between neighbor sensing and
topology discovery results in increased complexity.

By lack of separation, I mean that OLSR HELLOs are used not 
only for neighbor sensing, but also for discovering paths to 
nodes that are 2 hops away (and also for selecting MPRs),
which to me is part of topology discovery.

Please see my comments below.

> Ioannis C Avramopoulos wrote (referring to OLSR):
>  > 
>  > - It is stated that HELLO messages are transmitted on all interfaces. Isn't
>  > this a waste of resources?

Yes, I think it is a waste of resources. In both TBRPF and OSPF, each HELLO
message is sent only on one interface, i.e., neighbor sensing is performed
separately on each interface.  

The reason OLSR sends HELLOs on all interfaces is because HELLOs 
are used not only for neighbor sensing, but also for discovering nodes
that are 2 hops away.  Since different interfaces might be used for the 
2 hops, HELLOs must be sent on all interfaces. 

Laurent wrote:

> The formal rule is what you propose: any 2-hop neighbor must have an
> interface covered by some MPR. But the proposed heuristic selects an
> MPR set such that any 2-hop interface is covered.

> This is again for the sake of simplicity versus complex optimization
> not so useful. Notice that you have to be careful to avoid a chicken
> and egg problem if your computation of MPRs depend from the reception
> of MID messages when the forwarding of MID messages depends on MPR
> election. (You need to receive a MID message from a 2-hop neighbor to
> know all its interfaces.)

Laurent talks about simplicity, but here is one way in which OLSR is more
complex than TBRPF.  TBRPF does not have such a chicken-egg problem, i.e., 
parent selection does not depend on multiple interface information. 

Laurent may argue that TBRPF must still report all neighbors on all interfaces
in Topology Update messages, but not only are these sent less often than
HELLO_INTERVAL, it provides a clean separation between HELLOs (which are sent
on one interface) and Topology Updates (which are sent on all interfaces).

Laurent wrote:

> Hello messages are transmitted on all OLSR interfaces. It is necessary
> to monitor connectivity on all interfaces. To allow 2-hop neighbor
> knowledge, all the information has to be transmitted on all interfaces
> from time to time. However, we could easily allow to send different
> messages per interface (it would naturally fit with partial Hellos)
> but again we preferred simplicity rather than a minor optimization.

Laurent suggests the possibility of sending some HELLOs on all interfaces
and others on a single interface, to improve efficiency, but avoids this
approach for simplicity. Note that TBRPF achieves this efficiency
(by sending each HELLO on a single interface) as well as simplicity.

I am confident that anyone who reads and understands these arguments will
see that TBRPF is the better approach.  I only hope that enough people
will read and understand these arguments.

Since this message is about separation between neighbor sensing and
topology discovery, I would like to summarize other advantages that
TBRPF has in this regard:

1. If neighbor sensing is already provided in the link/mac layer (and I
know of at least two companies that do this), then TBRPF can be used
without HELLO messages, thus saving overhead.  

2. Since TBRPF neighbor sensing performs *only* neighbor sensing, it can 
be used with other routing protocols.  Conversely, other neighbor sensing
protocols can be used with TBRPF.

3. Because OSLR uses HELLOs to provide 2-hop information, each HELLO must
be sent on all interfaces (as discussed above).

Richard



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



From manet-admin@ietf.org  Wed Mar 13 16:54:29 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21066
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 16:54:24 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16238;
	Wed, 13 Mar 2002 16:31:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16206
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 16:31:05 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20188
	for <manet@ietf.org>; Wed, 13 Mar 2002 16:31:02 -0500 (EST)
Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2DLV32477525
	for <manet@ietf.org>; Wed, 13 Mar 2002 16:31:03 -0500 (EST)
Received: from ecpe15 ([208.17.194.151])
	by vivi.cc.vt.edu (Mirapoint)
	with SMTP id ANH96730;
	Wed, 13 Mar 2002 16:31:02 -0500 (EST)
Message-ID: <001a01c1cad7$421200a0$97c211d0@ecpe15>
Reply-To: "Vikram Dham" <vdham@vt.edu>
From: "Vikram Dham" <vdham@vt.edu>
To: <manet@ietf.org>
Date: Wed, 13 Mar 2002 16:37:21 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0017_01C1CAAD.58FEC890"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Subject: [manet] Simulation Scenario
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0017_01C1CAAD.58FEC890
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello Everyone,

 I am trying to simulate a MANET scenario using 802.11. Can anyone =
suggest
what values I should use for following parameters.

1. The area within which nodes are distributed.
2. The density of nodes.
3. The transmitter power of nodes.
4. Minimum detectable SNR of nodes.
5. Average distance between nodes.

With Best Regards

Vikram Dham




------=_NextPart_000_0017_01C1CAAD.58FEC890
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello Everyone,<BR><BR>&nbsp;I am =
trying to=20
simulate a MANET scenario using 802.11. Can anyone suggest<BR>what =
values I=20
should use for following parameters.<BR><BR>1. The area within which =
nodes are=20
distributed.<BR>2. The density of nodes.<BR>3. The transmitter power of=20
nodes.<BR>4. Minimum detectable SNR of nodes.<BR>5. Average distance =
between=20
nodes.<BR><BR>With Best Regards<BR><BR>Vikram=20
Dham<BR><BR><BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_0017_01C1CAAD.58FEC890--


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


From daemon@ns.ietf.org  Wed Mar 13 16:54:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21082
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 16:54:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA17970
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 16:54:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16238;
	Wed, 13 Mar 2002 16:31:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16206
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 16:31:05 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20188
	for <manet@ietf.org>; Wed, 13 Mar 2002 16:31:02 -0500 (EST)
Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2DLV32477525
	for <manet@ietf.org>; Wed, 13 Mar 2002 16:31:03 -0500 (EST)
Received: from ecpe15 ([208.17.194.151])
	by vivi.cc.vt.edu (Mirapoint)
	with SMTP id ANH96730;
	Wed, 13 Mar 2002 16:31:02 -0500 (EST)
Message-ID: <001a01c1cad7$421200a0$97c211d0@ecpe15>
Reply-To: "Vikram Dham" <vdham@vt.edu>
From: "Vikram Dham" <vdham@vt.edu>
To: <manet@ietf.org>
Date: Wed, 13 Mar 2002 16:37:21 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0017_01C1CAAD.58FEC890"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Subject: [manet] Simulation Scenario
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_0017_01C1CAAD.58FEC890
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello Everyone,

 I am trying to simulate a MANET scenario using 802.11. Can anyone =
suggest
what values I should use for following parameters.

1. The area within which nodes are distributed.
2. The density of nodes.
3. The transmitter power of nodes.
4. Minimum detectable SNR of nodes.
5. Average distance between nodes.

With Best Regards

Vikram Dham




------=_NextPart_000_0017_01C1CAAD.58FEC890
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3315.2870" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello Everyone,<BR><BR>&nbsp;I am =
trying to=20
simulate a MANET scenario using 802.11. Can anyone suggest<BR>what =
values I=20
should use for following parameters.<BR><BR>1. The area within which =
nodes are=20
distributed.<BR>2. The density of nodes.<BR>3. The transmitter power of=20
nodes.<BR>4. Minimum detectable SNR of nodes.<BR>5. Average distance =
between=20
nodes.<BR><BR>With Best Regards<BR><BR>Vikram=20
Dham<BR><BR><BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_0017_01C1CAAD.58FEC890--


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



From manet-admin@ietf.org  Wed Mar 13 17:12:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21624
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 17:12:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17321;
	Wed, 13 Mar 2002 16:47:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17288
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 16:47:47 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20786
	for <manet@ietf.org>; Wed, 13 Mar 2002 16:47:44 -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 QAA22311;
	Wed, 13 Mar 2002 16:47:44 -0500 (EST)
Message-Id: <5.0.1.4.2.20020313154903.01a01e28@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 13 Mar 2002 16:56:20 -0500
To: ogier@erg.sri.com, manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: [manet] OLSR questions 
In-Reply-To: <200203131942.LAA17973@pit.erg.sri.com>
References: <Your message of "Tue, 12 Mar 2002 13:53:09 +0100." <15501.64053.570314.623276@impression.inria.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


>
>Yes, I think it is a waste of resources. In both TBRPF and OSPF, each HELLO
>message is sent only on one interface, i.e., neighbor sensing is performed
>separately on each interface.  

Can you clarify your statement in relationship to OSPF..

from RFC2328, OSPFv2
"...9.5. Sending Hello packets Hello packets are sent out each functioning router interface. They are used to discover and maintain neighbor relationships...."

RFC2740, OSPF for IPv6, has "multiple interfaces to single link" modifications where one interface Hello is only used ... BUT that is for "multiple interfaces to a single link"



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


From daemon@ns.ietf.org  Wed Mar 13 17:12:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21643
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 17:12:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA20009
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 17:12:36 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17321;
	Wed, 13 Mar 2002 16:47:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17288
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 16:47:47 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20786
	for <manet@ietf.org>; Wed, 13 Mar 2002 16:47:44 -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 QAA22311;
	Wed, 13 Mar 2002 16:47:44 -0500 (EST)
Message-Id: <5.0.1.4.2.20020313154903.01a01e28@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 13 Mar 2002 16:56:20 -0500
To: ogier@erg.sri.com, manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: [manet] OLSR questions 
In-Reply-To: <200203131942.LAA17973@pit.erg.sri.com>
References: <Your message of "Tue, 12 Mar 2002 13:53:09 +0100." <15501.64053.570314.623276@impression.inria.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


>
>Yes, I think it is a waste of resources. In both TBRPF and OSPF, each HELLO
>message is sent only on one interface, i.e., neighbor sensing is performed
>separately on each interface.  

Can you clarify your statement in relationship to OSPF..

from RFC2328, OSPFv2
"...9.5. Sending Hello packets Hello packets are sent out each functioning router interface. They are used to discover and maintain neighbor relationships...."

RFC2740, OSPF for IPv6, has "multiple interfaces to single link" modifications where one interface Hello is only used ... BUT that is for "multiple interfaces to a single link"



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



From manet-admin@ietf.org  Wed Mar 13 17:30:43 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22313
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 17:30:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19583;
	Wed, 13 Mar 2002 17:07:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19498
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 17:06:53 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21315
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:02:51 -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 RAA23061
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:02:50 -0500 (EST)
Message-Id: <5.0.1.4.2.20020313171035.02eccc20@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 13 Mar 2002 17:12:51 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [manet] (no subject)
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

*************************************************
Salon C RTG manet Mobile Ad-hoc Networks WG 
Mobile Ad Hoc Networks (manet) Agenda
Monday, March 18, 19:30-22:00

Agenda Bashing
 
* Status of AODV EXPERIMENTAL RFC Submission Progress

Updates of Current Drafts
 
* DSR update <draft-ietf-manet-dsr-07.txt>, D. Johnson (Rice)

* OLSR update <draft-ietf-manet-olsr-06.txt>, T. Clausen (INRIA)

* TBRPF Update <draft-ietf-manet-tbrpf-05.txt>, Ogier/Templin (SRI)

New Discussions

* Manet extensions to OSPF, F. Baker (CISCO)

* Redirects for MANET <draft-templin-manet-redirect-00.txt>, Templin (SRI)

* Other Activity and Implementation Announcements

* Open Discussion


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


From daemon@ns.ietf.org  Wed Mar 13 17:30:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22327
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 17:30:45 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA21894
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 17:30:47 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19583;
	Wed, 13 Mar 2002 17:07:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA19498
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 17:06:53 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21315
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:02:51 -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 RAA23061
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:02:50 -0500 (EST)
Message-Id: <5.0.1.4.2.20020313171035.02eccc20@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 13 Mar 2002 17:12:51 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [manet] (no subject)
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

*************************************************
Salon C RTG manet Mobile Ad-hoc Networks WG 
Mobile Ad Hoc Networks (manet) Agenda
Monday, March 18, 19:30-22:00

Agenda Bashing
 
* Status of AODV EXPERIMENTAL RFC Submission Progress

Updates of Current Drafts
 
* DSR update <draft-ietf-manet-dsr-07.txt>, D. Johnson (Rice)

* OLSR update <draft-ietf-manet-olsr-06.txt>, T. Clausen (INRIA)

* TBRPF Update <draft-ietf-manet-tbrpf-05.txt>, Ogier/Templin (SRI)

New Discussions

* Manet extensions to OSPF, F. Baker (CISCO)

* Redirects for MANET <draft-templin-manet-redirect-00.txt>, Templin (SRI)

* Other Activity and Implementation Announcements

* Open Discussion


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



From manet-admin@ietf.org  Wed Mar 13 17:57:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23407
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 17:57:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA22095;
	Wed, 13 Mar 2002 17:31:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA22070
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 17:31:40 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22382
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:31:37 -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 RAA24168
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:31:38 -0500 (EST)
Message-Id: <5.0.1.4.2.20020313173946.02f123f8@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 13 Mar 2002 17:41:39 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [manet] update to agenda
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

(sorry for the redundant message to the list, but the subject line was missing).
Here is a draft agenda update.
*************************************************
Salon C RTG manet Mobile Ad-hoc Networks WG 
Mobile Ad Hoc Networks (manet) Agenda
Monday, March 18, 19:30-22:00

Agenda Bashing
 
* Status of AODV EXPERIMENTAL RFC Submission Progress

Updates of Current Drafts
 
* DSR update <draft-ietf-manet-dsr-07.txt>, D. Johnson (Rice)

* OLSR update <draft-ietf-manet-olsr-06.txt>, T. Clausen (INRIA)

* TBRPF Update <draft-ietf-manet-tbrpf-05.txt>, Ogier/Templin (SRI)

New Discussions

* Manet extensions to OSPF, F. Baker (CISCO)

* Redirects for MANET <draft-templin-manet-redirect-00.txt>, Templin (SRI)

* Other Activity and Implementation Announcements

* Open Discussion 


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


From daemon@ns.ietf.org  Wed Mar 13 17:58:00 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23420
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 17:58:00 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA24498
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 17:58:03 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA22095;
	Wed, 13 Mar 2002 17:31:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA22070
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 17:31:40 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22382
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:31:37 -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 RAA24168
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:31:38 -0500 (EST)
Message-Id: <5.0.1.4.2.20020313173946.02f123f8@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Wed, 13 Mar 2002 17:41:39 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [manet] update to agenda
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

(sorry for the redundant message to the list, but the subject line was missing).
Here is a draft agenda update.
*************************************************
Salon C RTG manet Mobile Ad-hoc Networks WG 
Mobile Ad Hoc Networks (manet) Agenda
Monday, March 18, 19:30-22:00

Agenda Bashing
 
* Status of AODV EXPERIMENTAL RFC Submission Progress

Updates of Current Drafts
 
* DSR update <draft-ietf-manet-dsr-07.txt>, D. Johnson (Rice)

* OLSR update <draft-ietf-manet-olsr-06.txt>, T. Clausen (INRIA)

* TBRPF Update <draft-ietf-manet-tbrpf-05.txt>, Ogier/Templin (SRI)

New Discussions

* Manet extensions to OSPF, F. Baker (CISCO)

* Redirects for MANET <draft-templin-manet-redirect-00.txt>, Templin (SRI)

* Other Activity and Implementation Announcements

* Open Discussion 


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



From manet-admin@ietf.org  Wed Mar 13 18:05:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23764
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 18:05:07 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23338;
	Wed, 13 Mar 2002 17:47:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23309
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 17:47:04 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22954
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:47:00 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id OAA18566;
	Wed, 13 Mar 2002 14:45:11 -0800 (PST)
Message-Id: <200203132245.OAA18566@pit.erg.sri.com>
To: Joe Macker <macker@itd.nrl.navy.mil>
cc: ogier@erg.sri.com, manet@ietf.org
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Wed, 13 Mar 2002 16:56:20 EST."
             <5.0.1.4.2.20020313154903.01a01e28@pop.itd.nrl.navy.mil> 
Date: Wed, 13 Mar 2002 14:45:10 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


> >Yes, I think it is a waste of resources. In both TBRPF and OSPF, each HELLO
> >message is sent only on one interface, i.e., neighbor sensing is performed
> >separately on each interface.  
> 
> Can you clarify your statement in relationship to OSPF..
> 
> from RFC2328, OSPFv2
> "...9.5. Sending Hello packets Hello packets are sent out each functioning router i
nterface. They are used to discover and maintain neighbor relationships...."

Joe,

It is true that Hello packets are sent out each functioning router interface
in OSPF. The question is whether *each* Hello packet is sent out on *all* 
interfaces (as in OLSR), versus sending *different* Hellos on different 
interfaces (where the Hellos sent on a given interface describe only that 
interface, as in TBRPF).

RFC2328 is not very clear about this, but you can tell from the HELLO
packet format that a HELLO sent on a given interface contains only
neighbors for that interface.  For example, a HELLO contains only one
network mask, and the list of neighbors in a HELLO is described as follows,
where a "network" (equivalent to "link" in OSPF for IPv6) corresponds
to a single interface:

    Neighbor
       The Router IDs of each router from whom valid Hello packets have
       been seen recently on the network.  Recently means in the last
       RouterDeadInterval seconds.

Richard

> 
> RFC2740, OSPF for IPv6, has "multiple interfaces to single link" modifications wher
e one interface Hello is only used ... BUT that is for "multiple interfaces to a sing
le link"
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@ns.ietf.org  Wed Mar 13 18:05:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23775
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 18:05:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA25795
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 18:05:10 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23338;
	Wed, 13 Mar 2002 17:47:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23309
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 17:47:04 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22954
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:47:00 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id OAA18566;
	Wed, 13 Mar 2002 14:45:11 -0800 (PST)
Message-Id: <200203132245.OAA18566@pit.erg.sri.com>
To: Joe Macker <macker@itd.nrl.navy.mil>
cc: ogier@erg.sri.com, manet@ietf.org
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Wed, 13 Mar 2002 16:56:20 EST."
             <5.0.1.4.2.20020313154903.01a01e28@pop.itd.nrl.navy.mil> 
Date: Wed, 13 Mar 2002 14:45:10 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


> >Yes, I think it is a waste of resources. In both TBRPF and OSPF, each HELLO
> >message is sent only on one interface, i.e., neighbor sensing is performed
> >separately on each interface.  
> 
> Can you clarify your statement in relationship to OSPF..
> 
> from RFC2328, OSPFv2
> "...9.5. Sending Hello packets Hello packets are sent out each functioning router i
nterface. They are used to discover and maintain neighbor relationships...."

Joe,

It is true that Hello packets are sent out each functioning router interface
in OSPF. The question is whether *each* Hello packet is sent out on *all* 
interfaces (as in OLSR), versus sending *different* Hellos on different 
interfaces (where the Hellos sent on a given interface describe only that 
interface, as in TBRPF).

RFC2328 is not very clear about this, but you can tell from the HELLO
packet format that a HELLO sent on a given interface contains only
neighbors for that interface.  For example, a HELLO contains only one
network mask, and the list of neighbors in a HELLO is described as follows,
where a "network" (equivalent to "link" in OSPF for IPv6) corresponds
to a single interface:

    Neighbor
       The Router IDs of each router from whom valid Hello packets have
       been seen recently on the network.  Recently means in the last
       RouterDeadInterval seconds.

Richard

> 
> RFC2740, OSPF for IPv6, has "multiple interfaces to single link" modifications wher
e one interface Hello is only used ... BUT that is for "multiple interfaces to a sing
le link"
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Wed Mar 13 18:12:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24083
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 18:12:18 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23869;
	Wed, 13 Mar 2002 17:50:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23839
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 17:50:46 -0500 (EST)
Received: from barrichello.cs.ucr.edu (barrichello.cs.ucr.edu [138.23.169.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23078
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:50:42 -0500 (EST)
Received: by barrichello.cs.ucr.edu (Postfix, from userid 2)
	id 3C6718BD33; Wed, 13 Mar 2002 14:50:36 -0800 (PST)
Received: from io.cs.ucr.edu (io.cs.ucr.edu [138.23.174.180])
	by barrichello.cs.ucr.edu (Postfix) with ESMTP
	id 4DDB8480E4; Wed, 13 Mar 2002 14:46:15 -0800 (PST)
Received: by io.cs.ucr.edu (Postfix, from userid 7296)
	id 95365258E5; Wed, 13 Mar 2002 14:45:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by io.cs.ucr.edu (Postfix) with ESMTP
	id 93F9D258E1; Wed, 13 Mar 2002 14:45:49 -0800 (PST)
Date: Wed, 13 Mar 2002 14:45:49 -0800 (PST)
From: Zhenqiang Ye <zye@cs.ucr.edu>
To: Vikram Dham <vdham@vt.edu>
Cc: <manet@ietf.org>
Subject: Re: [manet] Simulation Scenarios
In-Reply-To: <001a01c1cad7$421200a0$97c211d0@ecpe15>
Message-ID: <Pine.LNX.4.30.0203131438030.24271-100000@io.cs.ucr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AntiVirus: scanned for viruses by AMaViS perl-6
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi, Vikram:
  Please check Royer's homepage (The author of the AODV protocol). They
have some results on the optimal network density. It should be based on
802.11. About the detectable SNR, there are some debates in MANET's
mailing list, I suggest you go there to have a look of the archives. They
suppose there are two thresholds: receving threshold (or other name) and
detection threshold.
  About the average distance between two random nodes, please see one of
Kleinrock's papers. I have a copy of it. If anyone else need it, please
let me know.

  Good luck,

Frank


On Wed, 13 Mar 2002, Vikram Dham wrote:

> Hello Everyone,
>
>  I am trying to simulate a MANET scenario using 802.11. Can anyone suggest
> what values I should use for following parameters.
>
> 1. The area within which nodes are distributed.
> 2. The density of nodes.
> 3. The transmitter power of nodes.
> 4. Minimum detectable SNR of nodes.
> 5. Average distance between nodes.
>
> With Best Regards
>
> Vikram Dham
>
>
>
>


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


From daemon@ns.ietf.org  Wed Mar 13 18:12:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24097
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 18:12:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA26328
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 18:12:22 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23869;
	Wed, 13 Mar 2002 17:50:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA23839
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 17:50:46 -0500 (EST)
Received: from barrichello.cs.ucr.edu (barrichello.cs.ucr.edu [138.23.169.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23078
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:50:42 -0500 (EST)
Received: by barrichello.cs.ucr.edu (Postfix, from userid 2)
	id 3C6718BD33; Wed, 13 Mar 2002 14:50:36 -0800 (PST)
Received: from io.cs.ucr.edu (io.cs.ucr.edu [138.23.174.180])
	by barrichello.cs.ucr.edu (Postfix) with ESMTP
	id 4DDB8480E4; Wed, 13 Mar 2002 14:46:15 -0800 (PST)
Received: by io.cs.ucr.edu (Postfix, from userid 7296)
	id 95365258E5; Wed, 13 Mar 2002 14:45:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by io.cs.ucr.edu (Postfix) with ESMTP
	id 93F9D258E1; Wed, 13 Mar 2002 14:45:49 -0800 (PST)
Date: Wed, 13 Mar 2002 14:45:49 -0800 (PST)
From: Zhenqiang Ye <zye@cs.ucr.edu>
To: Vikram Dham <vdham@vt.edu>
Cc: <manet@ietf.org>
Subject: Re: [manet] Simulation Scenarios
In-Reply-To: <001a01c1cad7$421200a0$97c211d0@ecpe15>
Message-ID: <Pine.LNX.4.30.0203131438030.24271-100000@io.cs.ucr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AntiVirus: scanned for viruses by AMaViS perl-6
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi, Vikram:
  Please check Royer's homepage (The author of the AODV protocol). They
have some results on the optimal network density. It should be based on
802.11. About the detectable SNR, there are some debates in MANET's
mailing list, I suggest you go there to have a look of the archives. They
suppose there are two thresholds: receving threshold (or other name) and
detection threshold.
  About the average distance between two random nodes, please see one of
Kleinrock's papers. I have a copy of it. If anyone else need it, please
let me know.

  Good luck,

Frank


On Wed, 13 Mar 2002, Vikram Dham wrote:

> Hello Everyone,
>
>  I am trying to simulate a MANET scenario using 802.11. Can anyone suggest
> what values I should use for following parameters.
>
> 1. The area within which nodes are distributed.
> 2. The density of nodes.
> 3. The transmitter power of nodes.
> 4. Minimum detectable SNR of nodes.
> 5. Average distance between nodes.
>
> With Best Regards
>
> Vikram Dham
>
>
>
>


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



From manet-admin@ietf.org  Wed Mar 13 18:15:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24224
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 18:15:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA24483;
	Wed, 13 Mar 2002 17:57:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA24454
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 17:57:52 -0500 (EST)
Received: from barrichello.cs.ucr.edu (barrichello.cs.ucr.edu [138.23.169.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23404
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:57:48 -0500 (EST)
Received: by barrichello.cs.ucr.edu (Postfix, from userid 2)
	id 9A31A8BD21; Wed, 13 Mar 2002 14:57:48 -0800 (PST)
Received: from io.cs.ucr.edu (io.cs.ucr.edu [138.23.174.180])
	by barrichello.cs.ucr.edu (Postfix) with ESMTP
	id 792D647F14; Wed, 13 Mar 2002 14:57:45 -0800 (PST)
Received: by io.cs.ucr.edu (Postfix, from userid 7296)
	id A2580258ED; Wed, 13 Mar 2002 14:57:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by io.cs.ucr.edu (Postfix) with ESMTP
	id A13A0258EB; Wed, 13 Mar 2002 14:57:46 -0800 (PST)
Date: Wed, 13 Mar 2002 14:57:46 -0800 (PST)
From: Zhenqiang Ye <zye@cs.ucr.edu>
To: Vikram Dham <vdham@vt.edu>
Cc: <manet@ietf.org>
Subject: Re: [manet] Simulation Scenario
In-Reply-To: <001a01c1cad7$421200a0$97c211d0@ecpe15>
Message-ID: <Pine.LNX.4.30.0203131454240.24271-100000@io.cs.ucr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AntiVirus: scanned for viruses by AMaViS perl-6
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Sorry I forgot to tell you the paper's title. It is:
  Optimum transmission radius for packet radio networks or why six is a
magic number

    IEEE 1978 National Telecommunications Conference

Frank


On Wed, 13 Mar 2002, Vikram Dham wrote:

> Hello Everyone,
>
>  I am trying to simulate a MANET scenario using 802.11. Can anyone suggest
> what values I should use for following parameters.
>
> 1. The area within which nodes are distributed.
> 2. The density of nodes.
> 3. The transmitter power of nodes.
> 4. Minimum detectable SNR of nodes.
> 5. Average distance between nodes.
>
> With Best Regards
>
> Vikram Dham
>
>
>
>


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


From daemon@ns.ietf.org  Wed Mar 13 18:15:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24235
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 18:15:38 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA26559
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 18:15:41 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA24483;
	Wed, 13 Mar 2002 17:57:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA24454
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 17:57:52 -0500 (EST)
Received: from barrichello.cs.ucr.edu (barrichello.cs.ucr.edu [138.23.169.5])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23404
	for <manet@ietf.org>; Wed, 13 Mar 2002 17:57:48 -0500 (EST)
Received: by barrichello.cs.ucr.edu (Postfix, from userid 2)
	id 9A31A8BD21; Wed, 13 Mar 2002 14:57:48 -0800 (PST)
Received: from io.cs.ucr.edu (io.cs.ucr.edu [138.23.174.180])
	by barrichello.cs.ucr.edu (Postfix) with ESMTP
	id 792D647F14; Wed, 13 Mar 2002 14:57:45 -0800 (PST)
Received: by io.cs.ucr.edu (Postfix, from userid 7296)
	id A2580258ED; Wed, 13 Mar 2002 14:57:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by io.cs.ucr.edu (Postfix) with ESMTP
	id A13A0258EB; Wed, 13 Mar 2002 14:57:46 -0800 (PST)
Date: Wed, 13 Mar 2002 14:57:46 -0800 (PST)
From: Zhenqiang Ye <zye@cs.ucr.edu>
To: Vikram Dham <vdham@vt.edu>
Cc: <manet@ietf.org>
Subject: Re: [manet] Simulation Scenario
In-Reply-To: <001a01c1cad7$421200a0$97c211d0@ecpe15>
Message-ID: <Pine.LNX.4.30.0203131454240.24271-100000@io.cs.ucr.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AntiVirus: scanned for viruses by AMaViS perl-6
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Sorry I forgot to tell you the paper's title. It is:
  Optimum transmission radius for packet radio networks or why six is a
magic number

    IEEE 1978 National Telecommunications Conference

Frank


On Wed, 13 Mar 2002, Vikram Dham wrote:

> Hello Everyone,
>
>  I am trying to simulate a MANET scenario using 802.11. Can anyone suggest
> what values I should use for following parameters.
>
> 1. The area within which nodes are distributed.
> 2. The density of nodes.
> 3. The transmitter power of nodes.
> 4. Minimum detectable SNR of nodes.
> 5. Average distance between nodes.
>
> With Best Regards
>
> Vikram Dham
>
>
>
>


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



From manet-admin@ietf.org  Wed Mar 13 19:13:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25476
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 19:13:37 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA28521;
	Wed, 13 Mar 2002 18:52:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA28486
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 18:52:21 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24876
	for <manet@ietf.org>; Wed, 13 Mar 2002 18:52:11 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id PAA18795;
	Wed, 13 Mar 2002 15:50:25 -0800 (PST)
Message-Id: <200203132350.PAA18795@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
From: ogier@erg.sri.com
Reply-to: ogier@erg.sri.com
Date: Wed, 13 Mar 2002 15:50:25 -0800
Subject: [manet] Re: performance comparaison between Ad Hoc routing protocols
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Thomas,

I checked very thoroughly to make sure we are extracting
information correctly from the ns2 trace files, and we are
definitely doing this correctly (as you described).

I am very curious to know why our simulations differ from yours.
Maybe we are not even running the same scenario, which is why
I sent you our cbr and scenario script files last Friday.
Did you run that scenario yet?  If so, did you get results
that are similar to ours?

Richard


------- Forwarded Message

Message-Id: <200203090101.RAA10048@pit.erg.sri.com>
To: t.clausen@computer.org, manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
In-reply-to: Your message of "Fri, 08 Mar 2002 08:09:06 PST."
             <200203081609.IAA08495@pit.erg.sri.com> 
Date: Fri, 08 Mar 2002 17:01:20 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Type: text
Content-Length: 7048


Thomas,

So that we can determine why our results differ, I will
provide additional details and scripts, so that you can run
the same experiment I ran.  I will give you the cbr 
and scenario scripts in a separate email.

I will refer to the case with 100 nodes, 20 sources, 670x670 area, 
no mobility, and a packet rate of 6 packets/second/source.  
Each stream begins at a random time between 10 and 40 seconds, and 
changes its destination to a randomly selected node every 30 seconds. 
The size of each data packet is 512 bytes. 
The total number of packets generated in 500 sec is 57261,
which is slightly less than 60000 = 6 * 20 * 500.
Is this similar to what you ran?

Richard


> Thomas,
> 
> > The way in which I extract overhead information from the ns2 tracefiles is
> > to look at all "send" events on the "MAC" layer from the agent
> > "OLSR". This should yield both the number of packets being transmitted as
> > well as the number of bytes, actually reaching the MAC layer and not
> > being dropped somewhere else.
> > 
> > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > was possible to end up with overhead figures very close those that you
> > cite. I do believe, though, that this is a wrong way of accounting, since
> > (1) control packets, dropped in the protocol stack (and thus not
> > contributing to diffusion of topology information) are accounted as
> > protocol overhead and, (2) control packets are accounted multiple times
> > (each time a layer is sending the packet "downwards" in the stack.)
> 
> We counted packets exactly the same way you did, i.e., 
> only at the MAC layer.  
> 
> To double check, I did the following:
> 
> grep "s " out.tr | grep MAC | grep OLSR   
> 
> and got exactly the same number of OLSR packets
> as our perl script did.
> 
> I did this for the following case:
> 100 nodes, 670x670 area, no mobility, 20 sources, packet rate = 6
> For 500 seconds, there were 154744 OLSR packets totaling 20684584, 
> so the average size of an OLSR packet (including the IP and MAC 
> headers) is 133 bytes. 
> 
> I also would like to find out why our results differ.
> If you have any more ideas, please let me know.
> 
> Regarding the 90-120% increase of overhead for the bug fix, 
> that was for 100 nodes.  I later tried 50 nodes and found
> the increase to be roughly 75-90%.
> 
> Richard
> 
> 
> > Richard,
> > 
> > I suspect serious problems with your control overhead measures. Please see
> > below.
> > 
> > On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:
> > 
> > > 
> > > Thomas,
> > > 
> > > > Richard,
> > > > 
> > > > I am not quite sure what to make from your simulations. It seems to me
> > > > that they are from a network in overload condition - in which case buff
er
> > > > management has a critical impact on performance. We've been simulating
> > > > OLSR in conditions, similar to those you've been showing, and our resul
ts
> > > > differ significantly. We experience that a large abmount of (data and
> > > > control) traffic in these situations are rejected from the various
> > > > buffers.
> > > 
> > 
> > <SNIP> 
> > 
> > > To ensure that the protocols were compared on a fair basis,
> > > since AODV and TBRPF gave control traffic higher priority than
> > > data traffic, we did the same for OLSR.  It has long been considered
> > > a good idea to give control traffic higher priority.  This could 
> > > explain why your results differ from mine.
> > > You can do this simply by adding the line
> > >                 case PT_OLSR:
> > > to the function PriQueue::recv() in priqueue.cc.
> > > 
> > > > Also, I notice that we obtain much less overhead for OLSR when counting
> > > > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > > > detailed information (e.g. physical overhead etc.) ?
> > > 
> > > No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> > > at the MAC layer.  
> > > 
> > 
> > <SNIP> 
> > 
> > I've tried to reproduce your published results for OLSR, using a large set
> > of scenario files, corresponding to the parameters you've used.
> > 
> > Unfortunately I fail to achieve the same results as those you present
> > (both with and without control traffic priority): in particulary in the
> > overload condition (packet rate of 6-8 packets/second) I find the overhead
> > of OLSR to be significantly lower (up to 25-30%) than what your
> > simulations show.
> > 
> > Also, as we were discussing in another mail, my simulations showed that
> > the "control packet size" bug resulted in approximately 50% more overhead,
> > whereas you cited your simulations as showing in the orders of 90-120%
> > more overhead. I have not had success in reproducing the 90-120% figures 
> > either.
> > 
> > I am basically looking for an explanation on why we have such different
> > results.
> > 
> > I am well aware that a paticulary "bad" or "good" choise of scenario (even
> > corresponding to the same general parameters such as mobility and traffic
> > patterns) may trigger particulary good or bad results, so I've run a
> > number of different scenarios through, all with roughly the same results.
> > This left me wondering if our different results were just a matter of
> > computing the overhead differently?
> > 
> > The way in which I extract overhead information from the ns2 tracefiles is
> > to look at all "send" events on the "MAC" layer from the agent
> > "OLSR". This should yield both the number of packets being transmitted as
> > well as the number of bytes, actually reaching the MAC layer and not
> > being dropped somewhere else.
> > 
> > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > was possible to end up with overhead figures very close those that you
> > cite. I do believe, though, that this is a wrong way of accounting, since
> > (1) control packets, dropped in the protocol stack (and thus not
> > contributing to diffusion of topology information) are accounted as
> > protocol overhead and, (2) control packets are accounted multiple times
> > (each time a layer is sending the packet "downwards" in the stack.)
> 
> 
> > 
> > -- 
> > 
> > -------------------------------------------
> >   Thomas Heide Clausen
> >   Civilingeniør i Datateknik (cand.polyt)
> >   M.Sc in Computer Engineering
> > 
> >   E-Mail: T.Clausen@computer.org
> >   WWW:    http://www.cs.auc.dk/~voop
> > -------------------------------------------
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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

------- End of Forwarded Message


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


From daemon@ns.ietf.org  Wed Mar 13 19:13:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25487
	for <manet-archive@odin.ietf.org>; Wed, 13 Mar 2002 19:13:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA29993
	for manet-archive@odin.ietf.org; Wed, 13 Mar 2002 19:13:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA28521;
	Wed, 13 Mar 2002 18:52:32 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id SAA28486
	for <manet@ns.ietf.org>; Wed, 13 Mar 2002 18:52:21 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24876
	for <manet@ietf.org>; Wed, 13 Mar 2002 18:52:11 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id PAA18795;
	Wed, 13 Mar 2002 15:50:25 -0800 (PST)
Message-Id: <200203132350.PAA18795@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
From: ogier@erg.sri.com
Reply-to: ogier@erg.sri.com
Date: Wed, 13 Mar 2002 15:50:25 -0800
Subject: [manet] Re: performance comparaison between Ad Hoc routing protocols
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Thomas,

I checked very thoroughly to make sure we are extracting
information correctly from the ns2 trace files, and we are
definitely doing this correctly (as you described).

I am very curious to know why our simulations differ from yours.
Maybe we are not even running the same scenario, which is why
I sent you our cbr and scenario script files last Friday.
Did you run that scenario yet?  If so, did you get results
that are similar to ours?

Richard


------- Forwarded Message

Message-Id: <200203090101.RAA10048@pit.erg.sri.com>
To: t.clausen@computer.org, manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
In-reply-to: Your message of "Fri, 08 Mar 2002 08:09:06 PST."
             <200203081609.IAA08495@pit.erg.sri.com> 
Date: Fri, 08 Mar 2002 17:01:20 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Type: text
Content-Length: 7048


Thomas,

So that we can determine why our results differ, I will
provide additional details and scripts, so that you can run
the same experiment I ran.  I will give you the cbr 
and scenario scripts in a separate email.

I will refer to the case with 100 nodes, 20 sources, 670x670 area, 
no mobility, and a packet rate of 6 packets/second/source.  
Each stream begins at a random time between 10 and 40 seconds, and 
changes its destination to a randomly selected node every 30 seconds. 
The size of each data packet is 512 bytes. 
The total number of packets generated in 500 sec is 57261,
which is slightly less than 60000 = 6 * 20 * 500.
Is this similar to what you ran?

Richard


> Thomas,
> 
> > The way in which I extract overhead information from the ns2 tracefiles is
> > to look at all "send" events on the "MAC" layer from the agent
> > "OLSR". This should yield both the number of packets being transmitted as
> > well as the number of bytes, actually reaching the MAC layer and not
> > being dropped somewhere else.
> > 
> > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > was possible to end up with overhead figures very close those that you
> > cite. I do believe, though, that this is a wrong way of accounting, since
> > (1) control packets, dropped in the protocol stack (and thus not
> > contributing to diffusion of topology information) are accounted as
> > protocol overhead and, (2) control packets are accounted multiple times
> > (each time a layer is sending the packet "downwards" in the stack.)
> 
> We counted packets exactly the same way you did, i.e., 
> only at the MAC layer.  
> 
> To double check, I did the following:
> 
> grep "s " out.tr | grep MAC | grep OLSR   
> 
> and got exactly the same number of OLSR packets
> as our perl script did.
> 
> I did this for the following case:
> 100 nodes, 670x670 area, no mobility, 20 sources, packet rate = 6
> For 500 seconds, there were 154744 OLSR packets totaling 20684584, 
> so the average size of an OLSR packet (including the IP and MAC 
> headers) is 133 bytes. 
> 
> I also would like to find out why our results differ.
> If you have any more ideas, please let me know.
> 
> Regarding the 90-120% increase of overhead for the bug fix, 
> that was for 100 nodes.  I later tried 50 nodes and found
> the increase to be roughly 75-90%.
> 
> Richard
> 
> 
> > Richard,
> > 
> > I suspect serious problems with your control overhead measures. Please see
> > below.
> > 
> > On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:
> > 
> > > 
> > > Thomas,
> > > 
> > > > Richard,
> > > > 
> > > > I am not quite sure what to make from your simulations. It seems to me
> > > > that they are from a network in overload condition - in which case buff
er
> > > > management has a critical impact on performance. We've been simulating
> > > > OLSR in conditions, similar to those you've been showing, and our resul
ts
> > > > differ significantly. We experience that a large abmount of (data and
> > > > control) traffic in these situations are rejected from the various
> > > > buffers.
> > > 
> > 
> > <SNIP> 
> > 
> > > To ensure that the protocols were compared on a fair basis,
> > > since AODV and TBRPF gave control traffic higher priority than
> > > data traffic, we did the same for OLSR.  It has long been considered
> > > a good idea to give control traffic higher priority.  This could 
> > > explain why your results differ from mine.
> > > You can do this simply by adding the line
> > >                 case PT_OLSR:
> > > to the function PriQueue::recv() in priqueue.cc.
> > > 
> > > > Also, I notice that we obtain much less overhead for OLSR when counting
> > > > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > > > detailed information (e.g. physical overhead etc.) ?
> > > 
> > > No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> > > at the MAC layer.  
> > > 
> > 
> > <SNIP> 
> > 
> > I've tried to reproduce your published results for OLSR, using a large set
> > of scenario files, corresponding to the parameters you've used.
> > 
> > Unfortunately I fail to achieve the same results as those you present
> > (both with and without control traffic priority): in particulary in the
> > overload condition (packet rate of 6-8 packets/second) I find the overhead
> > of OLSR to be significantly lower (up to 25-30%) than what your
> > simulations show.
> > 
> > Also, as we were discussing in another mail, my simulations showed that
> > the "control packet size" bug resulted in approximately 50% more overhead,
> > whereas you cited your simulations as showing in the orders of 90-120%
> > more overhead. I have not had success in reproducing the 90-120% figures 
> > either.
> > 
> > I am basically looking for an explanation on why we have such different
> > results.
> > 
> > I am well aware that a paticulary "bad" or "good" choise of scenario (even
> > corresponding to the same general parameters such as mobility and traffic
> > patterns) may trigger particulary good or bad results, so I've run a
> > number of different scenarios through, all with roughly the same results.
> > This left me wondering if our different results were just a matter of
> > computing the overhead differently?
> > 
> > The way in which I extract overhead information from the ns2 tracefiles is
> > to look at all "send" events on the "MAC" layer from the agent
> > "OLSR". This should yield both the number of packets being transmitted as
> > well as the number of bytes, actually reaching the MAC layer and not
> > being dropped somewhere else.
> > 
> > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > was possible to end up with overhead figures very close those that you
> > cite. I do believe, though, that this is a wrong way of accounting, since
> > (1) control packets, dropped in the protocol stack (and thus not
> > contributing to diffusion of topology information) are accounted as
> > protocol overhead and, (2) control packets are accounted multiple times
> > (each time a layer is sending the packet "downwards" in the stack.)
> 
> 
> > 
> > -- 
> > 
> > -------------------------------------------
> >   Thomas Heide Clausen
> >   Civilingeniør i Datateknik (cand.polyt)
> >   M.Sc in Computer Engineering
> > 
> >   E-Mail: T.Clausen@computer.org
> >   WWW:    http://www.cs.auc.dk/~voop
> > -------------------------------------------
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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

------- End of Forwarded Message


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



From manet-admin@ietf.org  Thu Mar 14 09:33:47 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17788
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 09:33:47 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27910;
	Thu, 14 Mar 2002 08:56:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27878
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 08:56:30 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17104
	for <manet@ietf.org>; Thu, 14 Mar 2002 08:56:28 -0500 (EST)
Received: from prisse (prisse.inria.fr [128.93.9.64])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2EDuQ502859
	for <manet@ietf.org>; Thu, 14 Mar 2002 14:56:28 +0100 (MET)
Message-ID: <016501c1cb61$d4ae6630$40095d80@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203131942.LAA17973@pit.erg.sri.com>
Subject: Re: [manet] OLSR questions 
Date: Thu, 14 Mar 2002 15:09:12 +0100
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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

People interested can read this email but we don't feel this is THAT
important to urge everyone;-)

Dear Richard,

I think your points are not a big deal. The same number of hellos will be
sent on each interface anyhow.

In order to improve the tunability of partial hellos we have introduced the
possibility of refreshing neighborhood at a possibly smaller rate than hello
rate, i.e. using partial hellos (ref to REFRESH_PERIOD and HELLO_PERIOD
parameters). This should answer the core of your remark.

One last point, OLSR protocol architecture is based on 1-hop discovery +
2-hop discovery + topology discovery. Including 2-hop discovery in neighbor
discovery or in topology discovery is just a matter of semantics.  In OSPF,
DR selection belongs to hello's protocol and is based on 2-hop informations
directly collected from Hellos, I think to remember.

Philippe

----- Original Message -----
From: <ogier@erg.sri.com>
To: <manet@ietf.org>
Cc: <ogier@erg.sri.com>
Sent: Wednesday, March 13, 2002 8:42 PM
Subject: Re: [manet] OLSR questions


>
> I urge everyone to read this message.
> It presents perhaps the clearest argument so far that
> OLSR's lack of separation between neighbor sensing and
> topology discovery results in increased complexity.
>
> By lack of separation, I mean that OLSR HELLOs are used not
> only for neighbor sensing, but also for discovering paths to
> nodes that are 2 hops away (and also for selecting MPRs),
> which to me is part of topology discovery.
>
> Please see my comments below.
>
> > Ioannis C Avramopoulos wrote (referring to OLSR):
> >  >
> >  > - It is stated that HELLO messages are transmitted on all interfaces.
Isn't
> >  > this a waste of resources?
>
> Yes, I think it is a waste of resources. In both TBRPF and OSPF, each
HELLO
> message is sent only on one interface, i.e., neighbor sensing is performed
> separately on each interface.
>
> The reason OLSR sends HELLOs on all interfaces is because HELLOs
> are used not only for neighbor sensing, but also for discovering nodes
> that are 2 hops away.  Since different interfaces might be used for the
> 2 hops, HELLOs must be sent on all interfaces.
>
> Laurent wrote:
>
> > The formal rule is what you propose: any 2-hop neighbor must have an
> > interface covered by some MPR. But the proposed heuristic selects an
> > MPR set such that any 2-hop interface is covered.
>
> > This is again for the sake of simplicity versus complex optimization
> > not so useful. Notice that you have to be careful to avoid a chicken
> > and egg problem if your computation of MPRs depend from the reception
> > of MID messages when the forwarding of MID messages depends on MPR
> > election. (You need to receive a MID message from a 2-hop neighbor to
> > know all its interfaces.)
>
> Laurent talks about simplicity, but here is one way in which OLSR is more
> complex than TBRPF.  TBRPF does not have such a chicken-egg problem, i.e.,
> parent selection does not depend on multiple interface information.
>
> Laurent may argue that TBRPF must still report all neighbors on all
interfaces
> in Topology Update messages, but not only are these sent less often than
> HELLO_INTERVAL, it provides a clean separation between HELLOs (which are
sent
> on one interface) and Topology Updates (which are sent on all interfaces).
>
> Laurent wrote:
>
> > Hello messages are transmitted on all OLSR interfaces. It is necessary
> > to monitor connectivity on all interfaces. To allow 2-hop neighbor
> > knowledge, all the information has to be transmitted on all interfaces
> > from time to time. However, we could easily allow to send different
> > messages per interface (it would naturally fit with partial Hellos)
> > but again we preferred simplicity rather than a minor optimization.
>
> Laurent suggests the possibility of sending some HELLOs on all interfaces
> and others on a single interface, to improve efficiency, but avoids this
> approach for simplicity. Note that TBRPF achieves this efficiency
> (by sending each HELLO on a single interface) as well as simplicity.
>
> I am confident that anyone who reads and understands these arguments will
> see that TBRPF is the better approach.  I only hope that enough people
> will read and understand these arguments.
>
> Since this message is about separation between neighbor sensing and
> topology discovery, I would like to summarize other advantages that
> TBRPF has in this regard:
>
> 1. If neighbor sensing is already provided in the link/mac layer (and I
> know of at least two companies that do this), then TBRPF can be used
> without HELLO messages, thus saving overhead.
>
> 2. Since TBRPF neighbor sensing performs *only* neighbor sensing, it can
> be used with other routing protocols.  Conversely, other neighbor sensing
> protocols can be used with TBRPF.
>
> 3. Because OSLR uses HELLOs to provide 2-hop information, each HELLO must
> be sent on all interfaces (as discussed above).
>
> Richard
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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


From daemon@ns.ietf.org  Thu Mar 14 09:33:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17799
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 09:33:47 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA01069
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 09:33:49 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27910;
	Thu, 14 Mar 2002 08:56:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27878
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 08:56:30 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17104
	for <manet@ietf.org>; Thu, 14 Mar 2002 08:56:28 -0500 (EST)
Received: from prisse (prisse.inria.fr [128.93.9.64])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2EDuQ502859
	for <manet@ietf.org>; Thu, 14 Mar 2002 14:56:28 +0100 (MET)
Message-ID: <016501c1cb61$d4ae6630$40095d80@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203131942.LAA17973@pit.erg.sri.com>
Subject: Re: [manet] OLSR questions 
Date: Thu, 14 Mar 2002 15:09:12 +0100
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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

People interested can read this email but we don't feel this is THAT
important to urge everyone;-)

Dear Richard,

I think your points are not a big deal. The same number of hellos will be
sent on each interface anyhow.

In order to improve the tunability of partial hellos we have introduced the
possibility of refreshing neighborhood at a possibly smaller rate than hello
rate, i.e. using partial hellos (ref to REFRESH_PERIOD and HELLO_PERIOD
parameters). This should answer the core of your remark.

One last point, OLSR protocol architecture is based on 1-hop discovery +
2-hop discovery + topology discovery. Including 2-hop discovery in neighbor
discovery or in topology discovery is just a matter of semantics.  In OSPF,
DR selection belongs to hello's protocol and is based on 2-hop informations
directly collected from Hellos, I think to remember.

Philippe

----- Original Message -----
From: <ogier@erg.sri.com>
To: <manet@ietf.org>
Cc: <ogier@erg.sri.com>
Sent: Wednesday, March 13, 2002 8:42 PM
Subject: Re: [manet] OLSR questions


>
> I urge everyone to read this message.
> It presents perhaps the clearest argument so far that
> OLSR's lack of separation between neighbor sensing and
> topology discovery results in increased complexity.
>
> By lack of separation, I mean that OLSR HELLOs are used not
> only for neighbor sensing, but also for discovering paths to
> nodes that are 2 hops away (and also for selecting MPRs),
> which to me is part of topology discovery.
>
> Please see my comments below.
>
> > Ioannis C Avramopoulos wrote (referring to OLSR):
> >  >
> >  > - It is stated that HELLO messages are transmitted on all interfaces.
Isn't
> >  > this a waste of resources?
>
> Yes, I think it is a waste of resources. In both TBRPF and OSPF, each
HELLO
> message is sent only on one interface, i.e., neighbor sensing is performed
> separately on each interface.
>
> The reason OLSR sends HELLOs on all interfaces is because HELLOs
> are used not only for neighbor sensing, but also for discovering nodes
> that are 2 hops away.  Since different interfaces might be used for the
> 2 hops, HELLOs must be sent on all interfaces.
>
> Laurent wrote:
>
> > The formal rule is what you propose: any 2-hop neighbor must have an
> > interface covered by some MPR. But the proposed heuristic selects an
> > MPR set such that any 2-hop interface is covered.
>
> > This is again for the sake of simplicity versus complex optimization
> > not so useful. Notice that you have to be careful to avoid a chicken
> > and egg problem if your computation of MPRs depend from the reception
> > of MID messages when the forwarding of MID messages depends on MPR
> > election. (You need to receive a MID message from a 2-hop neighbor to
> > know all its interfaces.)
>
> Laurent talks about simplicity, but here is one way in which OLSR is more
> complex than TBRPF.  TBRPF does not have such a chicken-egg problem, i.e.,
> parent selection does not depend on multiple interface information.
>
> Laurent may argue that TBRPF must still report all neighbors on all
interfaces
> in Topology Update messages, but not only are these sent less often than
> HELLO_INTERVAL, it provides a clean separation between HELLOs (which are
sent
> on one interface) and Topology Updates (which are sent on all interfaces).
>
> Laurent wrote:
>
> > Hello messages are transmitted on all OLSR interfaces. It is necessary
> > to monitor connectivity on all interfaces. To allow 2-hop neighbor
> > knowledge, all the information has to be transmitted on all interfaces
> > from time to time. However, we could easily allow to send different
> > messages per interface (it would naturally fit with partial Hellos)
> > but again we preferred simplicity rather than a minor optimization.
>
> Laurent suggests the possibility of sending some HELLOs on all interfaces
> and others on a single interface, to improve efficiency, but avoids this
> approach for simplicity. Note that TBRPF achieves this efficiency
> (by sending each HELLO on a single interface) as well as simplicity.
>
> I am confident that anyone who reads and understands these arguments will
> see that TBRPF is the better approach.  I only hope that enough people
> will read and understand these arguments.
>
> Since this message is about separation between neighbor sensing and
> topology discovery, I would like to summarize other advantages that
> TBRPF has in this regard:
>
> 1. If neighbor sensing is already provided in the link/mac layer (and I
> know of at least two companies that do this), then TBRPF can be used
> without HELLO messages, thus saving overhead.
>
> 2. Since TBRPF neighbor sensing performs *only* neighbor sensing, it can
> be used with other routing protocols.  Conversely, other neighbor sensing
> protocols can be used with TBRPF.
>
> 3. Because OSLR uses HELLOs to provide 2-hop information, each HELLO must
> be sent on all interfaces (as discussed above).
>
> Richard
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Thu Mar 14 12:21:09 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23182
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 12:21:09 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13003;
	Thu, 14 Mar 2002 11:42:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA12855
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 11:42:30 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21944
	for <manet@ietf.org>; Thu, 14 Mar 2002 11:42:27 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id IAA20006;
	Thu, 14 Mar 2002 08:40:29 -0800 (PST)
Message-Id: <200203141640.IAA20006@pit.erg.sri.com>
To: Joe Macker <macker@itd.nrl.navy.mil>, manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Wed, 13 Mar 2002 14:45:10 PST."
             <200203132245.OAA18566@pit.erg.sri.com> 
Date: Thu, 14 Mar 2002 08:40:29 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


TBRPF has other features that are shared by OSPF but not by OLSR
(in addition to sending each HELLO on a single interface). For example, 
neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs, 
not neighbor interfaces. This greatly improves efficiency for IPv6, 
since RIDs remain at 32 bits in OSPF for IPv6.

Richard

> > >Yes, I think it is a waste of resources. In both TBRPF and OSPF, each HELLO
> > >message is sent only on one interface, i.e., neighbor sensing is performed
> > >separately on each interface.  
> > 
> > Can you clarify your statement in relationship to OSPF..
> > 
> > from RFC2328, OSPFv2
> > "...9.5. Sending Hello packets Hello packets are sent out each functioning router i
> nterface. They are used to discover and maintain neighbor relationships...."
> 
> Joe,
> 
> It is true that Hello packets are sent out each functioning router interface
> in OSPF. The question is whether *each* Hello packet is sent out on *all* 
> interfaces (as in OLSR), versus sending *different* Hellos on different 
> interfaces (where the Hellos sent on a given interface describe only that 
> interface, as in TBRPF).
> 
> RFC2328 is not very clear about this, but you can tell from the HELLO
> packet format that a HELLO sent on a given interface contains only
> neighbors for that interface.  For example, a HELLO contains only one
> network mask, and the list of neighbors in a HELLO is described as follows,
> where a "network" (equivalent to "link" in OSPF for IPv6) corresponds
> to a single interface:
> 
>     Neighbor
>        The Router IDs of each router from whom valid Hello packets have
>        been seen recently on the network.  Recently means in the last
>        RouterDeadInterval seconds.
> 
> Richard
> 
> > 
> > RFC2740, OSPF for IPv6, has "multiple interfaces to single link" modifications wher
> e one interface Hello is only used ... BUT that is for "multiple interfaces to a sing
> le link"
> > 
> > 
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@ns.ietf.org  Thu Mar 14 12:21:10 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23192
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 12:21:09 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA17587
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 12:21:13 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13003;
	Thu, 14 Mar 2002 11:42:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA12855
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 11:42:30 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21944
	for <manet@ietf.org>; Thu, 14 Mar 2002 11:42:27 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id IAA20006;
	Thu, 14 Mar 2002 08:40:29 -0800 (PST)
Message-Id: <200203141640.IAA20006@pit.erg.sri.com>
To: Joe Macker <macker@itd.nrl.navy.mil>, manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Wed, 13 Mar 2002 14:45:10 PST."
             <200203132245.OAA18566@pit.erg.sri.com> 
Date: Thu, 14 Mar 2002 08:40:29 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


TBRPF has other features that are shared by OSPF but not by OLSR
(in addition to sending each HELLO on a single interface). For example, 
neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs, 
not neighbor interfaces. This greatly improves efficiency for IPv6, 
since RIDs remain at 32 bits in OSPF for IPv6.

Richard

> > >Yes, I think it is a waste of resources. In both TBRPF and OSPF, each HELLO
> > >message is sent only on one interface, i.e., neighbor sensing is performed
> > >separately on each interface.  
> > 
> > Can you clarify your statement in relationship to OSPF..
> > 
> > from RFC2328, OSPFv2
> > "...9.5. Sending Hello packets Hello packets are sent out each functioning router i
> nterface. They are used to discover and maintain neighbor relationships...."
> 
> Joe,
> 
> It is true that Hello packets are sent out each functioning router interface
> in OSPF. The question is whether *each* Hello packet is sent out on *all* 
> interfaces (as in OLSR), versus sending *different* Hellos on different 
> interfaces (where the Hellos sent on a given interface describe only that 
> interface, as in TBRPF).
> 
> RFC2328 is not very clear about this, but you can tell from the HELLO
> packet format that a HELLO sent on a given interface contains only
> neighbors for that interface.  For example, a HELLO contains only one
> network mask, and the list of neighbors in a HELLO is described as follows,
> where a "network" (equivalent to "link" in OSPF for IPv6) corresponds
> to a single interface:
> 
>     Neighbor
>        The Router IDs of each router from whom valid Hello packets have
>        been seen recently on the network.  Recently means in the last
>        RouterDeadInterval seconds.
> 
> Richard
> 
> > 
> > RFC2740, OSPF for IPv6, has "multiple interfaces to single link" modifications wher
> e one interface Hello is only used ... BUT that is for "multiple interfaces to a sing
> le link"
> > 
> > 
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Thu Mar 14 14:18:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26745
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 14:18:27 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA24765;
	Thu, 14 Mar 2002 13:57:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA24714
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 13:57:43 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26074
	for <manet@ietf.org>; Thu, 14 Mar 2002 13:57:35 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id KAA20299;
	Thu, 14 Mar 2002 10:55:50 -0800 (PST)
Message-Id: <200203141855.KAA20299@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Thu, 14 Mar 2002 15:09:12 +0100."
             <016501c1cb61$d4ae6630$40095d80@inria.fr> 
Date: Thu, 14 Mar 2002 10:55:49 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Philippe,

> Dear Richard,
> 
> I think your points are not a big deal. The same number of hellos will be
> sent on each interface anyhow.

But the HELLOs can be much larger, since they report all neighbors
on all interfaces.  For example, if a node has 5 interfaces, and
there are 100 neighbors on each interface, then 500 neighbors will have 
to be reported on each interface every HELLO_INTERVAL.  Also, this is 
likely to require more than one HELLO due to message size limitations.

> In order to improve the tunability of partial hellos we have introduced the
> possibility of refreshing neighborhood at a possibly smaller rate than hello
> rate, i.e. using partial hellos (ref to REFRESH_PERIOD and HELLO_PERIOD
> parameters). This should answer the core of your remark.

For example, you can set REFRESH_INTERVAL to be 5 seconds, the 
same as TC_INTERVAL, and partial/differential HELLOs can be sent more
frequently (like TBRPF). In this case, each node would need to report 
each neighbor every 5 seconds (like TBRPF).  It seems you have found
a way to incorporate TBRPF neighbor sensing without admitting it!

The OLSR draft does not mention any use for partial HELLOs
other than "due to message size limitations".  Do you expect the 
implementor to figure out that they should implement partial/differential
HELLOs similar to TBRPF?  I have a better solution.  :-)

Another disadvantage is that OLSR computes MPRs to cover all 2-hop
interfaces (which is redundant), whereas TBRPF computes parents based 
only on router IDs (equivalent to the "main address" in OLSR), 
not interfaces.

> One last point, OLSR protocol architecture is based on 1-hop discovery +
> 2-hop discovery + topology discovery. Including 2-hop discovery in neighbor
> discovery or in topology discovery is just a matter of semantics.  In OSPF,

It is not just a matter of semantics; modularity of (1-hop) neighbor 
discovery is very important, as I have already discussed.  

> DR selection belongs to hello's protocol and is based on 2-hop informations
> directly collected from Hellos, I think to remember.

I don't see how this is possible, since DRs are elected only in broadcast
and NBMA networks, in which all nodes are (logically) 1 hop from each other.

You seem to be introducing/exploring lots of new ideas to improve OLSR.  
But simulation code is available only for version 03.
I hope that you will release ns2 code soon that includes the new 
features, and that also includes link-layer notification. This will 
allow the working group to evaluate the new, improved OLSR.

Richard

> 
> Philippe
> 
> ----- Original Message -----
> From: <ogier@erg.sri.com>
> To: <manet@ietf.org>
> Cc: <ogier@erg.sri.com>
> Sent: Wednesday, March 13, 2002 8:42 PM
> Subject: Re: [manet] OLSR questions
> 
> 
> >
> > I urge everyone to read this message.
> > It presents perhaps the clearest argument so far that
> > OLSR's lack of separation between neighbor sensing and
> > topology discovery results in increased complexity.
> >
> > By lack of separation, I mean that OLSR HELLOs are used not
> > only for neighbor sensing, but also for discovering paths to
> > nodes that are 2 hops away (and also for selecting MPRs),
> > which to me is part of topology discovery.
> >
> > Please see my comments below.
> >
> > > Ioannis C Avramopoulos wrote (referring to OLSR):
> > >  >
> > >  > - It is stated that HELLO messages are transmitted on all interfaces.
> Isn't
> > >  > this a waste of resources?
> >
> > Yes, I think it is a waste of resources. In both TBRPF and OSPF, each
> HELLO
> > message is sent only on one interface, i.e., neighbor sensing is performed
> > separately on each interface.
> >
> > The reason OLSR sends HELLOs on all interfaces is because HELLOs
> > are used not only for neighbor sensing, but also for discovering nodes
> > that are 2 hops away.  Since different interfaces might be used for the
> > 2 hops, HELLOs must be sent on all interfaces.
> >
> > Laurent wrote:
> >
> > > The formal rule is what you propose: any 2-hop neighbor must have an
> > > interface covered by some MPR. But the proposed heuristic selects an
> > > MPR set such that any 2-hop interface is covered.
> >
> > > This is again for the sake of simplicity versus complex optimization
> > > not so useful. Notice that you have to be careful to avoid a chicken
> > > and egg problem if your computation of MPRs depend from the reception
> > > of MID messages when the forwarding of MID messages depends on MPR
> > > election. (You need to receive a MID message from a 2-hop neighbor to
> > > know all its interfaces.)
> >
> > Laurent talks about simplicity, but here is one way in which OLSR is more
> > complex than TBRPF.  TBRPF does not have such a chicken-egg problem, i.e.,
> > parent selection does not depend on multiple interface information.
> >
> > Laurent may argue that TBRPF must still report all neighbors on all
> interfaces
> > in Topology Update messages, but not only are these sent less often than
> > HELLO_INTERVAL, it provides a clean separation between HELLOs (which are
> sent
> > on one interface) and Topology Updates (which are sent on all interfaces).
> >
> > Laurent wrote:
> >
> > > Hello messages are transmitted on all OLSR interfaces. It is necessary
> > > to monitor connectivity on all interfaces. To allow 2-hop neighbor
> > > knowledge, all the information has to be transmitted on all interfaces
> > > from time to time. However, we could easily allow to send different
> > > messages per interface (it would naturally fit with partial Hellos)
> > > but again we preferred simplicity rather than a minor optimization.
> >
> > Laurent suggests the possibility of sending some HELLOs on all interfaces
> > and others on a single interface, to improve efficiency, but avoids this
> > approach for simplicity. Note that TBRPF achieves this efficiency
> > (by sending each HELLO on a single interface) as well as simplicity.
> >
> > I am confident that anyone who reads and understands these arguments will
> > see that TBRPF is the better approach.  I only hope that enough people
> > will read and understand these arguments.
> >
> > Since this message is about separation between neighbor sensing and
> > topology discovery, I would like to summarize other advantages that
> > TBRPF has in this regard:
> >
> > 1. If neighbor sensing is already provided in the link/mac layer (and I
> > know of at least two companies that do this), then TBRPF can be used
> > without HELLO messages, thus saving overhead.
> >
> > 2. Since TBRPF neighbor sensing performs *only* neighbor sensing, it can
> > be used with other routing protocols.  Conversely, other neighbor sensing
> > protocols can be used with TBRPF.
> >
> > 3. Because OSLR uses HELLOs to provide 2-hop information, each HELLO must
> > be sent on all interfaces (as discussed above).
> >
> > Richard
> >
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From manet-admin@ietf.org  Thu Mar 14 14:18:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26755
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 14:18:27 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23971;
	Thu, 14 Mar 2002 13:48:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23940
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 13:48:02 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25604
	for <manet@ietf.org>; Thu, 14 Mar 2002 13:47: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 NAA22601
	for <manet@ietf.org>; Thu, 14 Mar 2002 13:48:00 -0500 (EST)
Message-Id: <5.0.1.4.2.20020314132046.01c4adb8@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Thu, 14 Mar 2002 13:57:57 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: [manet] OLSR questions 
In-Reply-To: <200203141640.IAA20006@pit.erg.sri.com>
References: <Your message of "Wed, 13 Mar 2002 14:45:10 PST." <200203132245.OAA18566@pit.erg.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

At 08:40 AM 3/14/2002 -0800, ogier@erg.sri.com wrote:

>TBRPF has other features that are shared by OSPF but not by OLSR
>(in addition to sending each HELLO on a single interface). For example, 
>neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
>Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs, 
>not neighbor interfaces. This greatly improves efficiency for IPv6, 
>since RIDs remain at 32 bits in OSPF for IPv6.
>
>Richard

For historical accuracy, early versions of OLSR ( built on IMEP) used RIDs   ...perhaps before you were tracking things... .  but your comment is a good question for clarification to the OLSR authors as I would also encourage taking lessons learned from OSPF evolution, especially discussing the RID usage issue and IPv6 adaptation.

In <draft-ietf-manet-olsr-06.txt>, the originator address could be interpreted as an "old style" OSPF RID (I actually think that might have been the author's intent from a rereading, but i would refer to them to clarify)...I would recommend IPv6 considerations might also need to be updated to consider 32 bit RID use.

-joe



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


From daemon@ns.ietf.org  Thu Mar 14 14:18:28 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26763
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 14:18:28 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA26899
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 14:18:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA24765;
	Thu, 14 Mar 2002 13:57:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA24714
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 13:57:43 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26074
	for <manet@ietf.org>; Thu, 14 Mar 2002 13:57:35 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id KAA20299;
	Thu, 14 Mar 2002 10:55:50 -0800 (PST)
Message-Id: <200203141855.KAA20299@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Thu, 14 Mar 2002 15:09:12 +0100."
             <016501c1cb61$d4ae6630$40095d80@inria.fr> 
Date: Thu, 14 Mar 2002 10:55:49 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Philippe,

> Dear Richard,
> 
> I think your points are not a big deal. The same number of hellos will be
> sent on each interface anyhow.

But the HELLOs can be much larger, since they report all neighbors
on all interfaces.  For example, if a node has 5 interfaces, and
there are 100 neighbors on each interface, then 500 neighbors will have 
to be reported on each interface every HELLO_INTERVAL.  Also, this is 
likely to require more than one HELLO due to message size limitations.

> In order to improve the tunability of partial hellos we have introduced the
> possibility of refreshing neighborhood at a possibly smaller rate than hello
> rate, i.e. using partial hellos (ref to REFRESH_PERIOD and HELLO_PERIOD
> parameters). This should answer the core of your remark.

For example, you can set REFRESH_INTERVAL to be 5 seconds, the 
same as TC_INTERVAL, and partial/differential HELLOs can be sent more
frequently (like TBRPF). In this case, each node would need to report 
each neighbor every 5 seconds (like TBRPF).  It seems you have found
a way to incorporate TBRPF neighbor sensing without admitting it!

The OLSR draft does not mention any use for partial HELLOs
other than "due to message size limitations".  Do you expect the 
implementor to figure out that they should implement partial/differential
HELLOs similar to TBRPF?  I have a better solution.  :-)

Another disadvantage is that OLSR computes MPRs to cover all 2-hop
interfaces (which is redundant), whereas TBRPF computes parents based 
only on router IDs (equivalent to the "main address" in OLSR), 
not interfaces.

> One last point, OLSR protocol architecture is based on 1-hop discovery +
> 2-hop discovery + topology discovery. Including 2-hop discovery in neighbor
> discovery or in topology discovery is just a matter of semantics.  In OSPF,

It is not just a matter of semantics; modularity of (1-hop) neighbor 
discovery is very important, as I have already discussed.  

> DR selection belongs to hello's protocol and is based on 2-hop informations
> directly collected from Hellos, I think to remember.

I don't see how this is possible, since DRs are elected only in broadcast
and NBMA networks, in which all nodes are (logically) 1 hop from each other.

You seem to be introducing/exploring lots of new ideas to improve OLSR.  
But simulation code is available only for version 03.
I hope that you will release ns2 code soon that includes the new 
features, and that also includes link-layer notification. This will 
allow the working group to evaluate the new, improved OLSR.

Richard

> 
> Philippe
> 
> ----- Original Message -----
> From: <ogier@erg.sri.com>
> To: <manet@ietf.org>
> Cc: <ogier@erg.sri.com>
> Sent: Wednesday, March 13, 2002 8:42 PM
> Subject: Re: [manet] OLSR questions
> 
> 
> >
> > I urge everyone to read this message.
> > It presents perhaps the clearest argument so far that
> > OLSR's lack of separation between neighbor sensing and
> > topology discovery results in increased complexity.
> >
> > By lack of separation, I mean that OLSR HELLOs are used not
> > only for neighbor sensing, but also for discovering paths to
> > nodes that are 2 hops away (and also for selecting MPRs),
> > which to me is part of topology discovery.
> >
> > Please see my comments below.
> >
> > > Ioannis C Avramopoulos wrote (referring to OLSR):
> > >  >
> > >  > - It is stated that HELLO messages are transmitted on all interfaces.
> Isn't
> > >  > this a waste of resources?
> >
> > Yes, I think it is a waste of resources. In both TBRPF and OSPF, each
> HELLO
> > message is sent only on one interface, i.e., neighbor sensing is performed
> > separately on each interface.
> >
> > The reason OLSR sends HELLOs on all interfaces is because HELLOs
> > are used not only for neighbor sensing, but also for discovering nodes
> > that are 2 hops away.  Since different interfaces might be used for the
> > 2 hops, HELLOs must be sent on all interfaces.
> >
> > Laurent wrote:
> >
> > > The formal rule is what you propose: any 2-hop neighbor must have an
> > > interface covered by some MPR. But the proposed heuristic selects an
> > > MPR set such that any 2-hop interface is covered.
> >
> > > This is again for the sake of simplicity versus complex optimization
> > > not so useful. Notice that you have to be careful to avoid a chicken
> > > and egg problem if your computation of MPRs depend from the reception
> > > of MID messages when the forwarding of MID messages depends on MPR
> > > election. (You need to receive a MID message from a 2-hop neighbor to
> > > know all its interfaces.)
> >
> > Laurent talks about simplicity, but here is one way in which OLSR is more
> > complex than TBRPF.  TBRPF does not have such a chicken-egg problem, i.e.,
> > parent selection does not depend on multiple interface information.
> >
> > Laurent may argue that TBRPF must still report all neighbors on all
> interfaces
> > in Topology Update messages, but not only are these sent less often than
> > HELLO_INTERVAL, it provides a clean separation between HELLOs (which are
> sent
> > on one interface) and Topology Updates (which are sent on all interfaces).
> >
> > Laurent wrote:
> >
> > > Hello messages are transmitted on all OLSR interfaces. It is necessary
> > > to monitor connectivity on all interfaces. To allow 2-hop neighbor
> > > knowledge, all the information has to be transmitted on all interfaces
> > > from time to time. However, we could easily allow to send different
> > > messages per interface (it would naturally fit with partial Hellos)
> > > but again we preferred simplicity rather than a minor optimization.
> >
> > Laurent suggests the possibility of sending some HELLOs on all interfaces
> > and others on a single interface, to improve efficiency, but avoids this
> > approach for simplicity. Note that TBRPF achieves this efficiency
> > (by sending each HELLO on a single interface) as well as simplicity.
> >
> > I am confident that anyone who reads and understands these arguments will
> > see that TBRPF is the better approach.  I only hope that enough people
> > will read and understand these arguments.
> >
> > Since this message is about separation between neighbor sensing and
> > topology discovery, I would like to summarize other advantages that
> > TBRPF has in this regard:
> >
> > 1. If neighbor sensing is already provided in the link/mac layer (and I
> > know of at least two companies that do this), then TBRPF can be used
> > without HELLO messages, thus saving overhead.
> >
> > 2. Since TBRPF neighbor sensing performs *only* neighbor sensing, it can
> > be used with other routing protocols.  Conversely, other neighbor sensing
> > protocols can be used with TBRPF.
> >
> > 3. Because OSLR uses HELLOs to provide 2-hop information, each HELLO must
> > be sent on all interfaces (as discussed above).
> >
> > Richard
> >
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From daemon@ns.ietf.org  Thu Mar 14 14:18:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26789
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 14:18:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA26914
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 14:18:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23971;
	Thu, 14 Mar 2002 13:48:06 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA23940
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 13:48:02 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25604
	for <manet@ietf.org>; Thu, 14 Mar 2002 13:47: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 NAA22601
	for <manet@ietf.org>; Thu, 14 Mar 2002 13:48:00 -0500 (EST)
Message-Id: <5.0.1.4.2.20020314132046.01c4adb8@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Thu, 14 Mar 2002 13:57:57 -0500
To: manet@ietf.org
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: [manet] OLSR questions 
In-Reply-To: <200203141640.IAA20006@pit.erg.sri.com>
References: <Your message of "Wed, 13 Mar 2002 14:45:10 PST." <200203132245.OAA18566@pit.erg.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

At 08:40 AM 3/14/2002 -0800, ogier@erg.sri.com wrote:

>TBRPF has other features that are shared by OSPF but not by OLSR
>(in addition to sending each HELLO on a single interface). For example, 
>neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
>Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs, 
>not neighbor interfaces. This greatly improves efficiency for IPv6, 
>since RIDs remain at 32 bits in OSPF for IPv6.
>
>Richard

For historical accuracy, early versions of OLSR ( built on IMEP) used RIDs   ...perhaps before you were tracking things... .  but your comment is a good question for clarification to the OLSR authors as I would also encourage taking lessons learned from OSPF evolution, especially discussing the RID usage issue and IPv6 adaptation.

In <draft-ietf-manet-olsr-06.txt>, the originator address could be interpreted as an "old style" OSPF RID (I actually think that might have been the author's intent from a rereading, but i would refer to them to clarify)...I would recommend IPv6 considerations might also need to be updated to consider 32 bit RID use.

-joe



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



From manet-admin@ietf.org  Thu Mar 14 14:58:15 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28425
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 14:58:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28071;
	Thu, 14 Mar 2002 14:30:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA27994
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 14:30:15 -0500 (EST)
Received: from gauss.crhc.uiuc.edu (gauss.crhc.uiuc.edu [130.126.142.154])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27337
	for <manet@ietf.org>; Thu, 14 Mar 2002 14:30:11 -0500 (EST)
Received: from localhost (navlakha@localhost)
	by gauss.crhc.uiuc.edu (8.9.3/8.9.3) with ESMTP id PAA31617
	for <manet@ietf.org>; Thu, 14 Mar 2002 15:29:13 -0600
Date: Thu, 14 Mar 2002 15:29:13 -0600 (CST)
From: Gaurav Navlakha <navlakha@gauss.crhc.uiuc.edu>
To: manet@ietf.org
Message-ID: <Pine.LNX.4.21.0203141528510.31383-100000@gauss.crhc.uiuc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Linux DSR Implementation?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Hi,

Is a DSR implementation for linux available? Or has anyone implemented a
linux port of CMU's BSD implementation?

Thanks,
Gaurav.

--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--
 Home:                      Work:

 Gaurav Navlakha            #459, Coordinated Science Lab
 506 E. Stoughton, #14      MC - 228
 Champaign, IL 61820        1308 West Main Street
                            Urbana, IL 61801
 (217) 356-4813             (217) 244-5791

--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--




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


From daemon@ns.ietf.org  Thu Mar 14 14:58:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28436
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 14:58:16 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA01152
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 14:58:18 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA28071;
	Thu, 14 Mar 2002 14:30:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA27994
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 14:30:15 -0500 (EST)
Received: from gauss.crhc.uiuc.edu (gauss.crhc.uiuc.edu [130.126.142.154])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27337
	for <manet@ietf.org>; Thu, 14 Mar 2002 14:30:11 -0500 (EST)
Received: from localhost (navlakha@localhost)
	by gauss.crhc.uiuc.edu (8.9.3/8.9.3) with ESMTP id PAA31617
	for <manet@ietf.org>; Thu, 14 Mar 2002 15:29:13 -0600
Date: Thu, 14 Mar 2002 15:29:13 -0600 (CST)
From: Gaurav Navlakha <navlakha@gauss.crhc.uiuc.edu>
To: manet@ietf.org
Message-ID: <Pine.LNX.4.21.0203141528510.31383-100000@gauss.crhc.uiuc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Linux DSR Implementation?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Hi,

Is a DSR implementation for linux available? Or has anyone implemented a
linux port of CMU's BSD implementation?

Thanks,
Gaurav.

--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--
 Home:                      Work:

 Gaurav Navlakha            #459, Coordinated Science Lab
 506 E. Stoughton, #14      MC - 228
 Champaign, IL 61820        1308 West Main Street
                            Urbana, IL 61801
 (217) 356-4813             (217) 244-5791

--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--




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



From manet-admin@ietf.org  Thu Mar 14 15:18:13 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29179
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 15:18:13 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA00732;
	Thu, 14 Mar 2002 14:54:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15868
	for <manet@optimus.ietf.org>; Fri, 8 Mar 2002 11:54:35 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16039
	for <manet@ietf.org>; Fri, 8 Mar 2002 11:54:32 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g28GsYB11818
	for <manet@ietf.org>; Fri, 8 Mar 2002 17:54:34 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Fri Mar 08 17:54:31 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <GQ9S42BP>; Fri, 8 Mar 2002 17:54:31 +0100
Message-ID: <4DA6EA82906FD511BE2F00508BCF053802C6AAAC@Esealnt861.al.sw.ericsson.se>
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: "'manet@ietf.org'" <manet@ietf.org>, ipng@sunroof.eng.sun.com,
        "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Date: Fri, 8 Mar 2002 17:50:35 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [manet] MONET BOF
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi all, 

Sorry if you receive multiple copies of this. 

This is an announcement of the MONET BOF.
All the necessary information can be found
at:
http://www.ietf.org/ietf/02mar/monet.txt.

We look forward to your participation. 

Thierry Ernst
Hesham Soliman



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


From daemon@ns.ietf.org  Thu Mar 14 15:18:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29194
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 15:18:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA03279
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 15:18:17 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA00732;
	Thu, 14 Mar 2002 14:54:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15868
	for <manet@optimus.ietf.org>; Fri, 8 Mar 2002 11:54:35 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [193.180.251.34])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16039
	for <manet@ietf.org>; Fri, 8 Mar 2002 11:54:32 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61])
	by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g28GsYB11818
	for <manet@ietf.org>; Fri, 8 Mar 2002 17:54:34 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt461 ; Fri Mar 08 17:54:31 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19)
	id <GQ9S42BP>; Fri, 8 Mar 2002 17:54:31 +0100
Message-ID: <4DA6EA82906FD511BE2F00508BCF053802C6AAAC@Esealnt861.al.sw.ericsson.se>
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: "'manet@ietf.org'" <manet@ietf.org>, ipng@sunroof.eng.sun.com,
        "'mobile-ip@sunroof.eng.sun.com'" <mobile-ip@sunroof.eng.sun.com>
Date: Fri, 8 Mar 2002 17:50:35 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [manet] MONET BOF
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi all, 

Sorry if you receive multiple copies of this. 

This is an announcement of the MONET BOF.
All the necessary information can be found
at:
http://www.ietf.org/ietf/02mar/monet.txt.

We look forward to your participation. 

Thierry Ernst
Hesham Soliman



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



From manet-admin@ietf.org  Thu Mar 14 15:27:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29549
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 15:27:19 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA01115;
	Thu, 14 Mar 2002 14:58:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA00416
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 14:51:13 -0500 (EST)
Received: from maila.telia.com (maila.telia.com [194.22.194.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28178
	for <manet@ietf.org>; Thu, 14 Mar 2002 14:50:53 -0500 (EST)
Received: from d1o848.telia.com (d1o848.telia.com [213.66.32.241])
	by maila.telia.com (8.11.6/8.11.6) with ESMTP id g2EJosr23918;
	Thu, 14 Mar 2002 20:50:54 +0100 (CET)
Received: from h204n1fls31o848.telia.com (h204n1fls31o848.telia.com [213.66.32.204])
	by d1o848.telia.com (8.10.2/8.10.1) with ESMTP id g2EJod122148;
	Thu, 14 Mar 2002 20:50:54 +0100 (CET)
Subject: Re: [manet] Linux DSR Implementation?
From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= <erik.nordstrom@it.uu.se>
To: Gaurav Navlakha <navlakha@gauss.crhc.uiuc.edu>
Cc: manet@ietf.org
In-Reply-To: <Pine.LNX.4.21.0203141528510.31383-100000@gauss.crhc.uiuc.edu>
References: <Pine.LNX.4.21.0203141528510.31383-100000@gauss.crhc.uiuc.edu>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailer: Evolution/1.0.2 
Date: 14 Mar 2002 20:50:39 +0100
Message-Id: <1016135454.1566.4.camel@Replicator>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA00417
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

There was one made by a student at the University of Queensland,
Australia. But the webpage seem to have gone down. The implementation
had some problems also.

At Uppsala University a master's thesis student is just starting on a
new implementation for Linux.

Erik Nordström
Uppsala University,
Sweden

On Thu, 2002-03-14 at 22:29, Gaurav Navlakha wrote:
> 
> Hi,
> 
> Is a DSR implementation for linux available? Or has anyone implemented a
> linux port of CMU's BSD implementation?
> 
> Thanks,
> Gaurav.
> 
> --/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--
>  Home:                      Work:
> 
>  Gaurav Navlakha            #459, Coordinated Science Lab
>  506 E. Stoughton, #14      MC - 228
>  Champaign, IL 61820        1308 West Main Street
>                             Urbana, IL 61801
>  (217) 356-4813             (217) 244-5791
> 
> --\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--
> 
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet




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


From daemon@ns.ietf.org  Thu Mar 14 15:27:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29558
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 15:27:19 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA04383
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 15:27:22 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA01115;
	Thu, 14 Mar 2002 14:58:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA00416
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 14:51:13 -0500 (EST)
Received: from maila.telia.com (maila.telia.com [194.22.194.231])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28178
	for <manet@ietf.org>; Thu, 14 Mar 2002 14:50:53 -0500 (EST)
Received: from d1o848.telia.com (d1o848.telia.com [213.66.32.241])
	by maila.telia.com (8.11.6/8.11.6) with ESMTP id g2EJosr23918;
	Thu, 14 Mar 2002 20:50:54 +0100 (CET)
Received: from h204n1fls31o848.telia.com (h204n1fls31o848.telia.com [213.66.32.204])
	by d1o848.telia.com (8.10.2/8.10.1) with ESMTP id g2EJod122148;
	Thu, 14 Mar 2002 20:50:54 +0100 (CET)
Subject: Re: [manet] Linux DSR Implementation?
From: Erik =?ISO-8859-1?Q?Nordstr=F6m?= <erik.nordstrom@it.uu.se>
To: Gaurav Navlakha <navlakha@gauss.crhc.uiuc.edu>
Cc: manet@ietf.org
In-Reply-To: <Pine.LNX.4.21.0203141528510.31383-100000@gauss.crhc.uiuc.edu>
References: <Pine.LNX.4.21.0203141528510.31383-100000@gauss.crhc.uiuc.edu>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailer: Evolution/1.0.2 
Date: 14 Mar 2002 20:50:39 +0100
Message-Id: <1016135454.1566.4.camel@Replicator>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id OAA00417
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

There was one made by a student at the University of Queensland,
Australia. But the webpage seem to have gone down. The implementation
had some problems also.

At Uppsala University a master's thesis student is just starting on a
new implementation for Linux.

Erik Nordström
Uppsala University,
Sweden

On Thu, 2002-03-14 at 22:29, Gaurav Navlakha wrote:
> 
> Hi,
> 
> Is a DSR implementation for linux available? Or has anyone implemented a
> linux port of CMU's BSD implementation?
> 
> Thanks,
> Gaurav.
> 
> --/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--/\--
>  Home:                      Work:
> 
>  Gaurav Navlakha            #459, Coordinated Science Lab
>  506 E. Stoughton, #14      MC - 228
>  Champaign, IL 61820        1308 West Main Street
>                             Urbana, IL 61801
>  (217) 356-4813             (217) 244-5791
> 
> --\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--\/--
> 
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet




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



From manet-admin@ietf.org  Thu Mar 14 15:44:46 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00165
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 15:44:46 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02760;
	Thu, 14 Mar 2002 15:12:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02731
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 15:12:15 -0500 (EST)
Received: from ozias.inrs-telecom.uquebec.ca (ozias.inrs-telecom.uquebec.ca [192.26.211.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28972
	for <manet@ietf.org>; Thu, 14 Mar 2002 15:12:02 -0500 (EST)
Received: from hoffman.INRS-Telecom.UQuebec.CA (hoffman [192.26.211.190])
	by ozias.inrs-telecom.uquebec.ca (8.11.3/8.11.3) with ESMTP id g2EKCNb28990
	for <manet@ietf.org>; Thu, 14 Mar 2002 15:12:24 -0500 (EST)
Received: from hoffman by hoffman.INRS-Telecom.UQuebec.CA (8.9.3+Sun/SMI-SVR4)
	id PAA24622; Thu, 14 Mar 2002 15:11:32 -0500 (EST)
Message-Id: <200203142011.PAA24622@hoffman.INRS-Telecom.UQuebec.CA>
Date: Thu, 14 Mar 2002 15:11:32 -0500 (EST)
From: Jorge Nuevo <nuevo@inrs-telecom.uquebec.ca>
Reply-To: Jorge Nuevo <nuevo@inrs-telecom.uquebec.ca>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: xvT9hAA+1QdGbRpn4XCCvw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4u sparc 
Subject: [manet] Question about dependency of unicast protocols by multicast protocols
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hello,

I am trying to find out which of the multicast protocols for
ad hoc networks are unicast protocols dependent. The following
would be unicast dependent:
MAODV, AMRoute, CAMP

and non-dependent would be: AMRIS, ODMRP and MCEDAR,

but I am not sure about FGMP (Forwarding Group Multicast Protocol),
ABAM (Associativity Based Multicast) and
ADMR (Adaptive Demand-driven Multicast Routing).

Could any one help me with this doubt?

thanks 

Jorge Nuevo
nuevo@inrs-telecom.uquebec.ca


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


From daemon@ns.ietf.org  Thu Mar 14 15:44:46 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00174
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 15:44:46 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA06233
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 15:44:49 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02760;
	Thu, 14 Mar 2002 15:12:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02731
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 15:12:15 -0500 (EST)
Received: from ozias.inrs-telecom.uquebec.ca (ozias.inrs-telecom.uquebec.ca [192.26.211.164])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28972
	for <manet@ietf.org>; Thu, 14 Mar 2002 15:12:02 -0500 (EST)
Received: from hoffman.INRS-Telecom.UQuebec.CA (hoffman [192.26.211.190])
	by ozias.inrs-telecom.uquebec.ca (8.11.3/8.11.3) with ESMTP id g2EKCNb28990
	for <manet@ietf.org>; Thu, 14 Mar 2002 15:12:24 -0500 (EST)
Received: from hoffman by hoffman.INRS-Telecom.UQuebec.CA (8.9.3+Sun/SMI-SVR4)
	id PAA24622; Thu, 14 Mar 2002 15:11:32 -0500 (EST)
Message-Id: <200203142011.PAA24622@hoffman.INRS-Telecom.UQuebec.CA>
Date: Thu, 14 Mar 2002 15:11:32 -0500 (EST)
From: Jorge Nuevo <nuevo@inrs-telecom.uquebec.ca>
Reply-To: Jorge Nuevo <nuevo@inrs-telecom.uquebec.ca>
To: manet@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: xvT9hAA+1QdGbRpn4XCCvw==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4 SunOS 5.8 sun4u sparc 
Subject: [manet] Question about dependency of unicast protocols by multicast protocols
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hello,

I am trying to find out which of the multicast protocols for
ad hoc networks are unicast protocols dependent. The following
would be unicast dependent:
MAODV, AMRoute, CAMP

and non-dependent would be: AMRIS, ODMRP and MCEDAR,

but I am not sure about FGMP (Forwarding Group Multicast Protocol),
ABAM (Associativity Based Multicast) and
ADMR (Adaptive Demand-driven Multicast Routing).

Could any one help me with this doubt?

thanks 

Jorge Nuevo
nuevo@inrs-telecom.uquebec.ca


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



From manet-admin@ietf.org  Thu Mar 14 15:46:02 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00221
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 15:46:02 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA03842;
	Thu, 14 Mar 2002 15:24:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02560
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 15:09:54 -0500 (EST)
Received: from cse.uta.edu (cse.uta.edu [129.107.12.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28901
	for <manet@ietf.org>; Thu, 14 Mar 2002 15:09:50 -0500 (EST)
Received: from uta.edu (smc101.uta.edu [129.107.69.162])
	by cse.uta.edu (8.9.0/8.9.0) with ESMTP id OAA23056;
	Thu, 14 Mar 2002 14:07:26 -0600 (CST)
Message-ID: <3C9102AC.2013CCA0@uta.edu>
Date: Thu, 14 Mar 2002 14:06:04 -0600
From: Gergely Zaruba <zaruba@uta.edu>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Gergely Zaruba <zaruba@uta.edu>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA02563
Subject: [manet] CFP: MONET Journal ; Special Issue on WPANs
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Please feel free to distribute this CFP among friends and colleagues...

[Our apologies for duplicate transmissions]

            Announcement and Call for Papers

    Journal on Special Topics in Mobile Networking and
                    Applications (MONET)

                             on

       Advances in Research of Wireless Personal Area
          Networking and Bluetooth Enabled Networks

                http://crystal.uta.edu/~zaruba/monet.html


With Guest Editors:

  Dr. Gergely V. Zaruba
  Center for Research in Wireless Mobility and Networking
  Department of Computer Science and Engineering (CSE@UTA)
  The University of Texas at Arlington
  E-mail: zaruba@cse.uta.edu
  Phone: +1 (817) 272-3602
  Fax: +1 (817) 272-3784

  Per Johansson
  Berkeley Wireless Center
  Ericsson Inc.
  E-mail: Per.Johansson@ericsson.com
  Phone: +1 (310) 592-9796
  Fax: +1 (510) 666-3999


Overview:
  Wireless personal area networks (WPANs) are short to very
  short-range (from a couple centimeters to a couple of
  meters) wireless networks that can be used to exchange
  information between devices in the reach of a person. WPANs
  can be used to replace cables between computers and their
  peripherals, to establish communities helping people do
  their everyday chores making them more productive, or to
  establish location aware services.

  The best example representing WPANs is the recent industry
  standard: Bluetooth, other examples include Spike (for real
  time gaming - proprietary technology), and in the broad
  sense HomeRF. The IEEE 802 committee has also realized the
  importance of short-range wireless networking and initiated
  the establishment of the IEEE 802.15 working group to
  standardize protocols and interfaces for wireless personal
  area networking.

  One key issue of the feasibility of WPANs is the cost of the
  chips enabling the actual wireless data transfer. Companies
  developing Bluetooth chips claim, that in the near future
  complex one-chip solutions of the Bluetooth specification
  will be available in the $5 price range. With this target
  price it is predicted that not only will most PDAs, phones,
  laptops include such technology but that the number of small
  WPAN enabled devices (e.g., pens, cameras, headsets, various
  sensors) will soon outnumber the computers on the internet.

  Another key issue is the inter-working of wireless technologies
  to create heterogeneous wireless networks. For instance, WPANs
  will enable an extension of the third generation (3G) cellular
  networks (i.e. UMTS and cdma2000) into devices without direct
  cellular access. Moreover, devices interconnected in a WPAN
  will able to utilize a combination of 3G access and WLAN access
  by selecting the access that is best for the moment. In such
  networks 3G, WLAN and WPAN technologies do not compete against
  each other but enable the user to select the best connectivity
  for his/her purposes.

  We expect that the availability of a cheap short-range wireless
  technology will further fuel research and development in what,
  where and most importantly how these technologies could be used
  for.


Scope:
  This special issue will concentrate on completed or ongoing
  research in the area of wireless personal area networking (not
  manufacturing). Areas of interest include but are not limited
  to research in:

  * Bluetooth technology
  * Bluetooth scatternet formation
  * IP over Bluetooth
  * Bluetooth performance evaluation
  * Using WPAN devices to create wireless ad hoc networks
  * Routing in Bluetooth scatternets
  * Security issues of WPANs
  * Mobility management and seamless integration of WPANs
  * Heterogeneous wireless infrastructures employing WPANs
  * 3G and WLAN multi-access networking via WPAN
  * Interoperability, interference and co-existence issues
  * WPANs vs. WLANs
  * Protocols tailored to WPANs
  * Caching in WPANs
  * Service discovery in WPANs
  * QoS provisioning in WPANs


Important Deadlines:
  Submission Deadline: April 15, 2002
  Acceptance Notification: June 30, 2002
  Final Manuscripts Due: July 30, 2002


Submission Guidelines:
  Authors should email an electronic Postscript or PDF copy
  of their papers to Gergely Záruba (zaruba@cse.uta.edu) by
  April15th 2002. Submissions should be limited to 20 double
  spaced pages excluding figures, graphs, and illustrations.
  If e-mail submission is impossible then six (6) hardcopies
  of the paper should be sent (arriving prior to the due date)
  to:

  Dr. Gergely V. Zaruba
  Department of Computer Science and Engineering (CSE@UTA)
  The University of Texas at Arlington
  Box 19015
  416 Yates, 305 Nedderman Hall,
  Arlington, TX  76019-0015
  U.S.A.


--
***********************************************************
Gergely V. Zaruba Ph.D. C.S.                zaruba@ieee.org
Assistant Professor  Computer Science and Engineering Dept.
Center for Research in Wireless Mobility and Networking
The University of Texas at Arlington   phone:(817) 272 3602
***********************************************************





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


From manet-admin@ietf.org  Thu Mar 14 15:46:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00241
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 15:46:03 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA03910;
	Thu, 14 Mar 2002 15:24:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02561
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 15:09:54 -0500 (EST)
Received: from cse.uta.edu (cse.uta.edu [129.107.12.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28900
	for <manet@ietf.org>; Thu, 14 Mar 2002 15:09:50 -0500 (EST)
Received: from uta.edu (smc101.uta.edu [129.107.69.162])
	by cse.uta.edu (8.9.0/8.9.0) with ESMTP id OAA23117;
	Thu, 14 Mar 2002 14:10:02 -0600 (CST)
Message-ID: <3C910347.7B61D8D6@uta.edu>
Date: Thu, 14 Mar 2002 14:08:41 -0600
From: Gergely Zaruba <zaruba@uta.edu>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Gergely Zaruba <zaruba@uta.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] CfP: HICSS-36 Minitrack on Wireless LANs and PANs
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear Colleagues,

(We apologize if you receive multiple copies.)
Please feel free to distribute the below CfP
among colleagues, interested parties, and related lists.

Best Regards,
Sajal Das, Gergely Zaruba and Kalyan Basu

====================================================================
                          CALL FOR PAPERS

                       HICSS-36 Minitrack on

                      WIRELESS LANs AND PANs

               http://crystal.uta.edu/~zaruba/hicss36/

               Part of the Software Technology Track
                       Thirty-sixth Annual
          HAWAI'I INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES
                       January 6 - 9, 2003,
          Hilton Waikoloa Village on the Big Island of Hawaii

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

   Abstracts due:   March 31, 2002
   Full Papers due: June 1, 2002

=====================================================================


Minitrack Co-Chairs and Technical Committee

* Sajal K. Das
* Gergely V. Zaruba
* Kalyan Basu

    Center for Research in Wireless Mobility and Networking (CReWMaN)
    Department of Computer Science and Engineering (CSE@UTA)
    The University of Texas at Arlington
    Email: {das,zaruba,basu}@cse.uta.edu

Overview:
In the past quarter century we have seen the rollout of three
generations of wireless cellular systems attracting end-users by
providing efficient mobile communications. On another front wireless
technology became an important component in providing networking
infrastructure for localized data delivery. This later revolution was
made possible by the induction of new networking technologies and
paradigms, such as wireless local area networks (WLAN) and wireless
personal area networks (WPAN).

Wireless personal area networks (WPANs) are short to very short-range
(from a couple centimeters to a couple of meters) wireless networks
that can be used to exchange information between devices in the reach
of a person. WPANs can be used to replace cables between computers
and their peripherals, to establish communities helping people do
their everyday chores making them more productive, or to establish
location aware services. Wireless local area networks (WLANs) on the
other hand provide with a larger transmission range. Although WLAN
equipment usually carries the capability to be set up for ad hoc
networking, the premier choice of deployment is yet a cellular like
infrastructure mode to interface wireless users with the Internet.

The best example representing WPANs is the recent industry standard:
Bluetooth, other examples include Spike (for real time gaming -
proprietary technology), and in the broad sense HomeRF. The IEEE 802
committee has also realized the importance of short-range wireless
networking and initiated the establishment of the IEEE 802.15 working
group to standardize protocols and interfaces for wireless personal
area networking. For WLANs the most well known representatives are
based on the standards IEEE802.11 and HiperLAN with all their
different variations.

One key issue of the feasibility of WPANs is the cost of the chips
enabling the actual wireless data transfer. Companies developing
Bluetooth chips claim, that in the near future complex one-chip
solutions of the Bluetooth specification will be available in the $5
price range. With this target price it is predicted that not only
will most PDAs, phones, laptops include such technology but that the
number of small WPAN enabled devices (e.g., pens, cameras, headsets,
various sensors) will soon outnumber the computers on the Internet.

Another key issue is the inter-working of wireless technologies to
create heterogeneous wireless networks. For instance, WPANs and WLANs
will enable an extension of the third generation (3G) cellular
networks (i.e., UMTS and cdma2000) into devices without direct
cellular access. Moreover, devices interconnected in a WPAN may be
able to utilize a combination of 3G access and WLAN access by
selecting the access that is best for the moment. In such networks
3G, WLAN and WPAN technologies do not compete against each other but
enable the user to select the best connectivity for his/her purposes.

We expect that the availability of a cheap short-range wireless
technology will further fuel research and development in what, where
and most importantly how WLAN and WPAN technologies could be used
for.


Scope:
The minitrack will concentrate on completed or ongoing research in
the area of wireless local area networking and wireless personal area
networking (excluding manufacturing). Areas of interest include but
are not limited to research in:
  * QoS provisioning in WLANs and WPANs
  * TCP performance of WLANs and WPANs
  * Bluetooth for ad hoc networks (scatternets)
  * IP over Bluetooth
  * Bluetooth performance evaluation
  * Routing in Bluetooth scatternets
  * Security issues of WPANs and WLANs
  * Mobility management and seamless integration of WLANs and PANs
  * Heterogeneous wireless infrastructures employing WLANS
    and/or WPANs
  * Interoperability, interference and co-existence issues
  * WPANs vs. WLANs
  * Protocols tailored to WLANs and WPANs
  * Caching in WLANs and WPANs
  * Service discovery using WLANs and WPANs


Important Deadlines in 2002:
  * March 31, 2002 Abstracts submitted for guidance and indication of
    appropriate content.
  * June 1, 2002 Full papers submitted to Minitrack Chairs.
    Contact minitrack chairs for submission instructions.
  * August 31, 2002 Notice of acceptance or rejections of papers sent
    to Authors by Minitrack Chairs.
  * October 1, 2002 Accepted manuscripts submitted electronically to
    the publisher of the conference proceedings. At least one author
    of each accepted paper must register to attend the conference by
    this date. Registration cancellations after this date may result
    in the paper being pulled from the Proceedings prior to printing.
    See conference web site for registration fee refund policy.

NOTE:
Because HICSS is a nonprofit activity funded entirely by registration
fees, all participants and speakers are expected to have their
university/organization bear the costs of their expenses and
registration. HICSS is not able to subsidize registrations or offer
reduced fees.


Instructions for the Authors:
1. Contact Gergely Zaruba in advance for specific submission
instructions. Otherwise, submit six (6) copies of the full paper,
consisting of 22-26 double- spaced pages, including diagrams,
directly to Gergely Zaruba. (NOTE: The final paper will be 10 pages,
double-column, single-spaced.)
2. Do not submit the manuscript to more than one Minitrack Chair.
Papers should contain original material and not be previously
published, or currently submitted for consideration elsewhere.
3. Each paper must have a title page to include title of the paper,
full name of all authors, and complete addresses including
affiliation(s), telephone number(s), and e-mail address(es).
4. The first page of the manuscript should include only the title and
a 300-word abstract of the paper.
5. Individuals interested in refereeing papers should contact the
minitrack chairs directly.
6. If you have more questions or want to find out more about other
minitracks in the track, please go to the Software Technology Track
homepage.


Other Useful Information:
  Tracks at HICSS-36
    * Collaboration Systems; Co-Chairs: Jay Nunamaker; Email:
      nunamaker@bpa.arizona.edu and Robert O. Briggs; Email:
      bbriggs@GroupSystems.com
    * Complex Systems; Chair: Robert Thomas; Email: rjt1@cornell.edu
    * Decision Tech. for Management; Chair: Dan Dolk; Email:
      dolker@redshift.com
    * Digital Documents and Media; Chair: Michael Shepherd; Email:
      shepherd@cs.dal.ca
    * Emerging Technologies; Co-Chairs Ralph H. Sprague; Email:
      sprague@hawaii.edu and Hesham El-Rewini; Email:
      rewini@engr.smu.edu
    * Information Technology in Health Care; Chair: William Chismar;
      Email: chismar@cba.hawaii.edu
    * Internet & the Digital Economy; Co-Chairs: David King; Email:
      dave@comshare.com and Alan Dennis; Email: ardennis@indiana.edu
    * Organizational Systems & Tech.; Chair: Hugh Watson; Email:
      hwatson@uga.edu
    * Software Technology; Chair: Hesham El-Rewini; Email:
      rewini@engr.smu.edu

  HICSS conferences are devoted to advances in the information,
  computer, and system sciences, and encompass developments in both
  theory and practice. Invited papers may be theoretical, conceptual,
  tutorial or descriptive in nature. Submissions undergo a peer
  referee process and those selected for presentation will be
  published in the Conference Proceedings. Submissions must not have
  been previously published. For the latest information visit the
  HICSS web site at:
  http://www.hicss.hawaii.edu

  Conference Administration
    * Ralph Sprague, Conference Chair
      Email: sprague@hawaii.edu
    * Eileen Dennis, Track Administrator
      Email: eidennis@indiana.edu
      Tel: 1-812-331-0551
      Fax: 1-812-331-0564
    * Sandra Laney, Conference Administrator
      Email: hicss@hawaii.edu
      Tel: 1-808-956-3251
      Fax: 1-808-956-5759

  2003 HICSS-36 Conference Venue
    Hilton Waikoloa Village on the Big Island of Hawaii
    425 Waikoloa Beach Drive
    Waikoloa, Hawaii 96738
    Tel: 1-808-886-1234
    Fax: 1-808-886-2900
    www.hiltonwaikoloavillage.com




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


From daemon@ns.ietf.org  Thu Mar 14 15:46:04 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00252
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 15:46:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA06338
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 15:46:07 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA03910;
	Thu, 14 Mar 2002 15:24:34 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02561
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 15:09:54 -0500 (EST)
Received: from cse.uta.edu (cse.uta.edu [129.107.12.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28900
	for <manet@ietf.org>; Thu, 14 Mar 2002 15:09:50 -0500 (EST)
Received: from uta.edu (smc101.uta.edu [129.107.69.162])
	by cse.uta.edu (8.9.0/8.9.0) with ESMTP id OAA23117;
	Thu, 14 Mar 2002 14:10:02 -0600 (CST)
Message-ID: <3C910347.7B61D8D6@uta.edu>
Date: Thu, 14 Mar 2002 14:08:41 -0600
From: Gergely Zaruba <zaruba@uta.edu>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Gergely Zaruba <zaruba@uta.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] CfP: HICSS-36 Minitrack on Wireless LANs and PANs
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear Colleagues,

(We apologize if you receive multiple copies.)
Please feel free to distribute the below CfP
among colleagues, interested parties, and related lists.

Best Regards,
Sajal Das, Gergely Zaruba and Kalyan Basu

====================================================================
                          CALL FOR PAPERS

                       HICSS-36 Minitrack on

                      WIRELESS LANs AND PANs

               http://crystal.uta.edu/~zaruba/hicss36/

               Part of the Software Technology Track
                       Thirty-sixth Annual
          HAWAI'I INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES
                       January 6 - 9, 2003,
          Hilton Waikoloa Village on the Big Island of Hawaii

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

   Abstracts due:   March 31, 2002
   Full Papers due: June 1, 2002

=====================================================================


Minitrack Co-Chairs and Technical Committee

* Sajal K. Das
* Gergely V. Zaruba
* Kalyan Basu

    Center for Research in Wireless Mobility and Networking (CReWMaN)
    Department of Computer Science and Engineering (CSE@UTA)
    The University of Texas at Arlington
    Email: {das,zaruba,basu}@cse.uta.edu

Overview:
In the past quarter century we have seen the rollout of three
generations of wireless cellular systems attracting end-users by
providing efficient mobile communications. On another front wireless
technology became an important component in providing networking
infrastructure for localized data delivery. This later revolution was
made possible by the induction of new networking technologies and
paradigms, such as wireless local area networks (WLAN) and wireless
personal area networks (WPAN).

Wireless personal area networks (WPANs) are short to very short-range
(from a couple centimeters to a couple of meters) wireless networks
that can be used to exchange information between devices in the reach
of a person. WPANs can be used to replace cables between computers
and their peripherals, to establish communities helping people do
their everyday chores making them more productive, or to establish
location aware services. Wireless local area networks (WLANs) on the
other hand provide with a larger transmission range. Although WLAN
equipment usually carries the capability to be set up for ad hoc
networking, the premier choice of deployment is yet a cellular like
infrastructure mode to interface wireless users with the Internet.

The best example representing WPANs is the recent industry standard:
Bluetooth, other examples include Spike (for real time gaming -
proprietary technology), and in the broad sense HomeRF. The IEEE 802
committee has also realized the importance of short-range wireless
networking and initiated the establishment of the IEEE 802.15 working
group to standardize protocols and interfaces for wireless personal
area networking. For WLANs the most well known representatives are
based on the standards IEEE802.11 and HiperLAN with all their
different variations.

One key issue of the feasibility of WPANs is the cost of the chips
enabling the actual wireless data transfer. Companies developing
Bluetooth chips claim, that in the near future complex one-chip
solutions of the Bluetooth specification will be available in the $5
price range. With this target price it is predicted that not only
will most PDAs, phones, laptops include such technology but that the
number of small WPAN enabled devices (e.g., pens, cameras, headsets,
various sensors) will soon outnumber the computers on the Internet.

Another key issue is the inter-working of wireless technologies to
create heterogeneous wireless networks. For instance, WPANs and WLANs
will enable an extension of the third generation (3G) cellular
networks (i.e., UMTS and cdma2000) into devices without direct
cellular access. Moreover, devices interconnected in a WPAN may be
able to utilize a combination of 3G access and WLAN access by
selecting the access that is best for the moment. In such networks
3G, WLAN and WPAN technologies do not compete against each other but
enable the user to select the best connectivity for his/her purposes.

We expect that the availability of a cheap short-range wireless
technology will further fuel research and development in what, where
and most importantly how WLAN and WPAN technologies could be used
for.


Scope:
The minitrack will concentrate on completed or ongoing research in
the area of wireless local area networking and wireless personal area
networking (excluding manufacturing). Areas of interest include but
are not limited to research in:
  * QoS provisioning in WLANs and WPANs
  * TCP performance of WLANs and WPANs
  * Bluetooth for ad hoc networks (scatternets)
  * IP over Bluetooth
  * Bluetooth performance evaluation
  * Routing in Bluetooth scatternets
  * Security issues of WPANs and WLANs
  * Mobility management and seamless integration of WLANs and PANs
  * Heterogeneous wireless infrastructures employing WLANS
    and/or WPANs
  * Interoperability, interference and co-existence issues
  * WPANs vs. WLANs
  * Protocols tailored to WLANs and WPANs
  * Caching in WLANs and WPANs
  * Service discovery using WLANs and WPANs


Important Deadlines in 2002:
  * March 31, 2002 Abstracts submitted for guidance and indication of
    appropriate content.
  * June 1, 2002 Full papers submitted to Minitrack Chairs.
    Contact minitrack chairs for submission instructions.
  * August 31, 2002 Notice of acceptance or rejections of papers sent
    to Authors by Minitrack Chairs.
  * October 1, 2002 Accepted manuscripts submitted electronically to
    the publisher of the conference proceedings. At least one author
    of each accepted paper must register to attend the conference by
    this date. Registration cancellations after this date may result
    in the paper being pulled from the Proceedings prior to printing.
    See conference web site for registration fee refund policy.

NOTE:
Because HICSS is a nonprofit activity funded entirely by registration
fees, all participants and speakers are expected to have their
university/organization bear the costs of their expenses and
registration. HICSS is not able to subsidize registrations or offer
reduced fees.


Instructions for the Authors:
1. Contact Gergely Zaruba in advance for specific submission
instructions. Otherwise, submit six (6) copies of the full paper,
consisting of 22-26 double- spaced pages, including diagrams,
directly to Gergely Zaruba. (NOTE: The final paper will be 10 pages,
double-column, single-spaced.)
2. Do not submit the manuscript to more than one Minitrack Chair.
Papers should contain original material and not be previously
published, or currently submitted for consideration elsewhere.
3. Each paper must have a title page to include title of the paper,
full name of all authors, and complete addresses including
affiliation(s), telephone number(s), and e-mail address(es).
4. The first page of the manuscript should include only the title and
a 300-word abstract of the paper.
5. Individuals interested in refereeing papers should contact the
minitrack chairs directly.
6. If you have more questions or want to find out more about other
minitracks in the track, please go to the Software Technology Track
homepage.


Other Useful Information:
  Tracks at HICSS-36
    * Collaboration Systems; Co-Chairs: Jay Nunamaker; Email:
      nunamaker@bpa.arizona.edu and Robert O. Briggs; Email:
      bbriggs@GroupSystems.com
    * Complex Systems; Chair: Robert Thomas; Email: rjt1@cornell.edu
    * Decision Tech. for Management; Chair: Dan Dolk; Email:
      dolker@redshift.com
    * Digital Documents and Media; Chair: Michael Shepherd; Email:
      shepherd@cs.dal.ca
    * Emerging Technologies; Co-Chairs Ralph H. Sprague; Email:
      sprague@hawaii.edu and Hesham El-Rewini; Email:
      rewini@engr.smu.edu
    * Information Technology in Health Care; Chair: William Chismar;
      Email: chismar@cba.hawaii.edu
    * Internet & the Digital Economy; Co-Chairs: David King; Email:
      dave@comshare.com and Alan Dennis; Email: ardennis@indiana.edu
    * Organizational Systems & Tech.; Chair: Hugh Watson; Email:
      hwatson@uga.edu
    * Software Technology; Chair: Hesham El-Rewini; Email:
      rewini@engr.smu.edu

  HICSS conferences are devoted to advances in the information,
  computer, and system sciences, and encompass developments in both
  theory and practice. Invited papers may be theoretical, conceptual,
  tutorial or descriptive in nature. Submissions undergo a peer
  referee process and those selected for presentation will be
  published in the Conference Proceedings. Submissions must not have
  been previously published. For the latest information visit the
  HICSS web site at:
  http://www.hicss.hawaii.edu

  Conference Administration
    * Ralph Sprague, Conference Chair
      Email: sprague@hawaii.edu
    * Eileen Dennis, Track Administrator
      Email: eidennis@indiana.edu
      Tel: 1-812-331-0551
      Fax: 1-812-331-0564
    * Sandra Laney, Conference Administrator
      Email: hicss@hawaii.edu
      Tel: 1-808-956-3251
      Fax: 1-808-956-5759

  2003 HICSS-36 Conference Venue
    Hilton Waikoloa Village on the Big Island of Hawaii
    425 Waikoloa Beach Drive
    Waikoloa, Hawaii 96738
    Tel: 1-808-886-1234
    Fax: 1-808-886-2900
    www.hiltonwaikoloavillage.com




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



From daemon@ns.ietf.org  Thu Mar 14 15:46:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00230
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 15:46:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA06324
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 15:46:05 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA03842;
	Thu, 14 Mar 2002 15:24:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA02560
	for <manet@ns.ietf.org>; Thu, 14 Mar 2002 15:09:54 -0500 (EST)
Received: from cse.uta.edu (cse.uta.edu [129.107.12.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28901
	for <manet@ietf.org>; Thu, 14 Mar 2002 15:09:50 -0500 (EST)
Received: from uta.edu (smc101.uta.edu [129.107.69.162])
	by cse.uta.edu (8.9.0/8.9.0) with ESMTP id OAA23056;
	Thu, 14 Mar 2002 14:07:26 -0600 (CST)
Message-ID: <3C9102AC.2013CCA0@uta.edu>
Date: Thu, 14 Mar 2002 14:06:04 -0600
From: Gergely Zaruba <zaruba@uta.edu>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Gergely Zaruba <zaruba@uta.edu>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA02563
Subject: [manet] CFP: MONET Journal ; Special Issue on WPANs
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Please feel free to distribute this CFP among friends and colleagues...

[Our apologies for duplicate transmissions]

            Announcement and Call for Papers

    Journal on Special Topics in Mobile Networking and
                    Applications (MONET)

                             on

       Advances in Research of Wireless Personal Area
          Networking and Bluetooth Enabled Networks

                http://crystal.uta.edu/~zaruba/monet.html


With Guest Editors:

  Dr. Gergely V. Zaruba
  Center for Research in Wireless Mobility and Networking
  Department of Computer Science and Engineering (CSE@UTA)
  The University of Texas at Arlington
  E-mail: zaruba@cse.uta.edu
  Phone: +1 (817) 272-3602
  Fax: +1 (817) 272-3784

  Per Johansson
  Berkeley Wireless Center
  Ericsson Inc.
  E-mail: Per.Johansson@ericsson.com
  Phone: +1 (310) 592-9796
  Fax: +1 (510) 666-3999


Overview:
  Wireless personal area networks (WPANs) are short to very
  short-range (from a couple centimeters to a couple of
  meters) wireless networks that can be used to exchange
  information between devices in the reach of a person. WPANs
  can be used to replace cables between computers and their
  peripherals, to establish communities helping people do
  their everyday chores making them more productive, or to
  establish location aware services.

  The best example representing WPANs is the recent industry
  standard: Bluetooth, other examples include Spike (for real
  time gaming - proprietary technology), and in the broad
  sense HomeRF. The IEEE 802 committee has also realized the
  importance of short-range wireless networking and initiated
  the establishment of the IEEE 802.15 working group to
  standardize protocols and interfaces for wireless personal
  area networking.

  One key issue of the feasibility of WPANs is the cost of the
  chips enabling the actual wireless data transfer. Companies
  developing Bluetooth chips claim, that in the near future
  complex one-chip solutions of the Bluetooth specification
  will be available in the $5 price range. With this target
  price it is predicted that not only will most PDAs, phones,
  laptops include such technology but that the number of small
  WPAN enabled devices (e.g., pens, cameras, headsets, various
  sensors) will soon outnumber the computers on the internet.

  Another key issue is the inter-working of wireless technologies
  to create heterogeneous wireless networks. For instance, WPANs
  will enable an extension of the third generation (3G) cellular
  networks (i.e. UMTS and cdma2000) into devices without direct
  cellular access. Moreover, devices interconnected in a WPAN
  will able to utilize a combination of 3G access and WLAN access
  by selecting the access that is best for the moment. In such
  networks 3G, WLAN and WPAN technologies do not compete against
  each other but enable the user to select the best connectivity
  for his/her purposes.

  We expect that the availability of a cheap short-range wireless
  technology will further fuel research and development in what,
  where and most importantly how these technologies could be used
  for.


Scope:
  This special issue will concentrate on completed or ongoing
  research in the area of wireless personal area networking (not
  manufacturing). Areas of interest include but are not limited
  to research in:

  * Bluetooth technology
  * Bluetooth scatternet formation
  * IP over Bluetooth
  * Bluetooth performance evaluation
  * Using WPAN devices to create wireless ad hoc networks
  * Routing in Bluetooth scatternets
  * Security issues of WPANs
  * Mobility management and seamless integration of WPANs
  * Heterogeneous wireless infrastructures employing WPANs
  * 3G and WLAN multi-access networking via WPAN
  * Interoperability, interference and co-existence issues
  * WPANs vs. WLANs
  * Protocols tailored to WPANs
  * Caching in WPANs
  * Service discovery in WPANs
  * QoS provisioning in WPANs


Important Deadlines:
  Submission Deadline: April 15, 2002
  Acceptance Notification: June 30, 2002
  Final Manuscripts Due: July 30, 2002


Submission Guidelines:
  Authors should email an electronic Postscript or PDF copy
  of their papers to Gergely Záruba (zaruba@cse.uta.edu) by
  April15th 2002. Submissions should be limited to 20 double
  spaced pages excluding figures, graphs, and illustrations.
  If e-mail submission is impossible then six (6) hardcopies
  of the paper should be sent (arriving prior to the due date)
  to:

  Dr. Gergely V. Zaruba
  Department of Computer Science and Engineering (CSE@UTA)
  The University of Texas at Arlington
  Box 19015
  416 Yates, 305 Nedderman Hall,
  Arlington, TX  76019-0015
  U.S.A.


--
***********************************************************
Gergely V. Zaruba Ph.D. C.S.                zaruba@ieee.org
Assistant Professor  Computer Science and Engineering Dept.
Center for Research in Wireless Mobility and Networking
The University of Texas at Arlington   phone:(817) 272 3602
***********************************************************





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



From manet-admin@ietf.org  Thu Mar 14 22:53:48 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11888
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 22:53:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA02031;
	Thu, 14 Mar 2002 22:30:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA01917
	for <manet@optimus.ietf.org>; Thu, 14 Mar 2002 22:29:53 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10428
	for <manet@ietf.org>; Thu, 14 Mar 2002 22:29:49 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id TAA21475;
	Thu, 14 Mar 2002 19:28:04 -0800 (PST)
Message-Id: <200203150328.TAA21475@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
In-reply-to: Your message of "Wed, 30 Jan 2002 16:00:05 PST."
             <200201310000.QAA19810@pit.erg.sri.com> 
Date: Thu, 14 Mar 2002 19:28:04 -0800
Subject: [manet] Re: Manet flooding / broadcasting....
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Philippe,

It is interesting to consider the discussion I had with
you in January regarding HELLOs (see below), in light of 
your new parameter REFRESH_INTERVAL.  For example, you said
"you only need to refresh al neighbors within a certain
period".  At that time, the refresh period was HELLO_INTERVAL,
since you did not yet introduce REFRESH_INTERVAL.
I was wondering why you said "a certain period" instead
of HELLO_INTERVAL, and now I know why.

This was the main point on which I never agreed with Laurent,
and I gave up arguing with him because he avoided my main
point that in OLSR (version 05) every neighbor must be reported 
in a HELLO every HELLO_INTERVAL. 

Instead of agreeing with me that something needed to be changed,
you pretended that no change was needed, and then later 
introduced the new parameter REFRESH_INTERVAL, which would have
addressed my concern.

Adding this new parameter allows OLSR to perform neighbor sensing 
similar to TBRPF, but it also adds complexity to OLSR.
In my opinion, TBRPF is designed better than OLSR in many ways,
and you are having to patch OLSR (thus making it more complex)
in order to compete with TBRPF.  Maybe next you will find a way
to make (1-hop) neighbor discovery modular, or introduce 
differential TC messages.

Richard


> > ----- Original Message -----
> > From: <ogier@erg.sri.com>
> > To: <manet@itd.nrl.navy.mil>
> > Cc: <ogier@erg.sri.com>
> > Sent: Tuesday, January 29, 2002 8:58 PM
> > Subject: Re: Manet flooding / broadcasting....
> >
> >
> > >
> > > Since HELLOs are differential in TBRPF, this can be done with a
> > > relatively small increase in overhead.  However, in OSPF and OLSR,
> > > since each HELLO contains all neighbor IDs, this would increase
> > > overhead a lot if each node has a large number of neighbors.
> > >
> > Richard, again, OLSR HELLOs can be partial, you only need to refresh all
> > neighbors within a certain period, and you can increase the hello rate for
> > fast moving node. I think Laurent mentioned this to you before.
> 
> Philippe,
> 
> Yes, I know that HELLOs can be partial and that each neighbor must be 
> included in at least one HELLO every HELLO interval, but unless there 
> are too many neighbor IDs to fit into one packet, normally OLSR uses one 
> full HELLO per HELLO interval.  (Just check the source code.)
> 
> But this does not affect my argument.  What I am saying is that OLSR 
> must include each neighbor in a HELLO every HELLO_INTERVAL, whereas 
> TBRPF includes each neighbor only in periodic topology updates, which are 
> less frequent (e.g., 10 times less frequent if the HELLO_INTERVAL is 0.5 s 
> and the update period is 5 s).
> 
> It is the HELLO_INTERVAL that determines how quickly a failed link is 
> detected, e.g., if no HELLO is received within 3 * HELLO_INTERVAL, then 
> the neighbor is declared to be lost.
> 
> I also know that OLSR can use differential HELLOs,
> since it has recently added the LOST_LINK status (which TBRPF has
> had since version 01).  *But this does not change the requirement that 
> in OLSR each neighbor ID must be included in at least one HELLO every 
> HELLO_INTERVAL.*  You can increase HELLO_INTERVAL, but then it
> would take longer to detect a lost neighbor.  OLSR could be *modified* 
> so that each neighbor ID is reported less frequently than HELLO_INTERVAL
> (as in TBRPF), but I am not sure how this would affect MPR computation.
> 
> However don't forget that even the overhead of an empty HELLO can be non 
> > negligible.  In IEEE 802.11 the MAC-PHY overhead is around 192 usec (with 
> > option to 92 usec) which at 11 Mbps corresponds to approximately 60 IPv4 
> > addresses.
> 
> Yes, this is a good point.  With the 92 usec option, this becomes about 30 
> IPv4 addresses (or router IDs).  So if a node has 30 neighbors, then a full 
> HELLO is about twice as big as an empty HELLO.  I think that's significant.
> 
> There are lots of differences between TBRPF and OLSR that can affect
> performance, and we have already discussed many of these.
> But it is difficult to predict how these differences affect performance.
> That's what simulations are for.
> 
> Regards,
> Richard
> 

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


From daemon@optimus.ietf.org  Thu Mar 14 22:53:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11902
	for <manet-archive@odin.ietf.org>; Thu, 14 Mar 2002 22:53:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA03303
	for manet-archive@odin.ietf.org; Thu, 14 Mar 2002 22:53:52 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA02031;
	Thu, 14 Mar 2002 22:30:00 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA01917
	for <manet@optimus.ietf.org>; Thu, 14 Mar 2002 22:29:53 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10428
	for <manet@ietf.org>; Thu, 14 Mar 2002 22:29:49 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id TAA21475;
	Thu, 14 Mar 2002 19:28:04 -0800 (PST)
Message-Id: <200203150328.TAA21475@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
In-reply-to: Your message of "Wed, 30 Jan 2002 16:00:05 PST."
             <200201310000.QAA19810@pit.erg.sri.com> 
Date: Thu, 14 Mar 2002 19:28:04 -0800
Subject: [manet] Re: Manet flooding / broadcasting....
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Philippe,

It is interesting to consider the discussion I had with
you in January regarding HELLOs (see below), in light of 
your new parameter REFRESH_INTERVAL.  For example, you said
"you only need to refresh al neighbors within a certain
period".  At that time, the refresh period was HELLO_INTERVAL,
since you did not yet introduce REFRESH_INTERVAL.
I was wondering why you said "a certain period" instead
of HELLO_INTERVAL, and now I know why.

This was the main point on which I never agreed with Laurent,
and I gave up arguing with him because he avoided my main
point that in OLSR (version 05) every neighbor must be reported 
in a HELLO every HELLO_INTERVAL. 

Instead of agreeing with me that something needed to be changed,
you pretended that no change was needed, and then later 
introduced the new parameter REFRESH_INTERVAL, which would have
addressed my concern.

Adding this new parameter allows OLSR to perform neighbor sensing 
similar to TBRPF, but it also adds complexity to OLSR.
In my opinion, TBRPF is designed better than OLSR in many ways,
and you are having to patch OLSR (thus making it more complex)
in order to compete with TBRPF.  Maybe next you will find a way
to make (1-hop) neighbor discovery modular, or introduce 
differential TC messages.

Richard


> > ----- Original Message -----
> > From: <ogier@erg.sri.com>
> > To: <manet@itd.nrl.navy.mil>
> > Cc: <ogier@erg.sri.com>
> > Sent: Tuesday, January 29, 2002 8:58 PM
> > Subject: Re: Manet flooding / broadcasting....
> >
> >
> > >
> > > Since HELLOs are differential in TBRPF, this can be done with a
> > > relatively small increase in overhead.  However, in OSPF and OLSR,
> > > since each HELLO contains all neighbor IDs, this would increase
> > > overhead a lot if each node has a large number of neighbors.
> > >
> > Richard, again, OLSR HELLOs can be partial, you only need to refresh all
> > neighbors within a certain period, and you can increase the hello rate for
> > fast moving node. I think Laurent mentioned this to you before.
> 
> Philippe,
> 
> Yes, I know that HELLOs can be partial and that each neighbor must be 
> included in at least one HELLO every HELLO interval, but unless there 
> are too many neighbor IDs to fit into one packet, normally OLSR uses one 
> full HELLO per HELLO interval.  (Just check the source code.)
> 
> But this does not affect my argument.  What I am saying is that OLSR 
> must include each neighbor in a HELLO every HELLO_INTERVAL, whereas 
> TBRPF includes each neighbor only in periodic topology updates, which are 
> less frequent (e.g., 10 times less frequent if the HELLO_INTERVAL is 0.5 s 
> and the update period is 5 s).
> 
> It is the HELLO_INTERVAL that determines how quickly a failed link is 
> detected, e.g., if no HELLO is received within 3 * HELLO_INTERVAL, then 
> the neighbor is declared to be lost.
> 
> I also know that OLSR can use differential HELLOs,
> since it has recently added the LOST_LINK status (which TBRPF has
> had since version 01).  *But this does not change the requirement that 
> in OLSR each neighbor ID must be included in at least one HELLO every 
> HELLO_INTERVAL.*  You can increase HELLO_INTERVAL, but then it
> would take longer to detect a lost neighbor.  OLSR could be *modified* 
> so that each neighbor ID is reported less frequently than HELLO_INTERVAL
> (as in TBRPF), but I am not sure how this would affect MPR computation.
> 
> However don't forget that even the overhead of an empty HELLO can be non 
> > negligible.  In IEEE 802.11 the MAC-PHY overhead is around 192 usec (with 
> > option to 92 usec) which at 11 Mbps corresponds to approximately 60 IPv4 
> > addresses.
> 
> Yes, this is a good point.  With the 92 usec option, this becomes about 30 
> IPv4 addresses (or router IDs).  So if a node has 30 neighbors, then a full 
> HELLO is about twice as big as an empty HELLO.  I think that's significant.
> 
> There are lots of differences between TBRPF and OLSR that can affect
> performance, and we have already discussed many of these.
> But it is difficult to predict how these differences affect performance.
> That's what simulations are for.
> 
> Regards,
> Richard
> 

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



From manet-admin@ietf.org  Fri Mar 15 04:28:58 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24319
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 04:28:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28569;
	Fri, 15 Mar 2002 03:53:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28524
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 03:53:16 -0500 (EST)
Received: from smtp1.cluster.oleane.net (smtp1.cluster.oleane.net [195.25.12.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23743
	for <manet@ietf.org>; Fri, 15 Mar 2002 03:53:10 -0500 (EST)
Received: from oleane (upper-side.rain.fr [194.250.212.114]) by smtp1.cluster.oleane.net with SMTP id g2F8rBO00583 for <manet@ietf.org>; Fri, 15 Mar 2002 09:53:11 +0100 (CET)
Message-ID: <00c801c1cbfe$bb9c5100$1901a8c0@oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <manet@ietf.org>
Date: Fri, 15 Mar 2002 09:52:26 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00C5_01C1CC07.1D15F460"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Subject: [manet] IPCN 2002 (IP-based Cellular Networks)
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

This is a multi-part message in MIME format.

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

=20
One of the most interesting subjects of IPCN 2002 (IP-based Cellular =
Networks) is the relationship between the licensed 2.5/3G services and =
802.11 hotspots. How can optimal use be made of both environments such =
that a realistic business service is possible?=20
Carriers will bring answers next April 23-26 during the third edition of =
IPCN (Intersection of Mobile WAN and WLAN).=20
All details at:
http://www.upperside.fr/ipcn02/baipcn02intro.htm
=20

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial><FONT face=3DArial>&nbsp;
<DIV><FONT size=3D2><SPAN><SPAN class=3Dtitrepapier><SPAN =
class=3Dtitrepapier><SPAN=20
class=3Dtitreune><SPAN class=3Dtitreune><FONT color=3D#000000>One of the =
most=20
interesting subjects of IPCN 2002 (IP-based Cellular Networks) is the=20
relationship between the licensed 2.5/3G services and 802.11 hotspots. =
How can=20
optimal use be made of both environments such that a realistic business =
service=20
is possible? </FONT></SPAN></SPAN></SPAN></SPAN></SPAN></FONT></DIV>
<DIV><FONT size=3D2><SPAN><SPAN class=3Dtitrepapier><SPAN =
class=3Dtitrepapier><SPAN=20
class=3Dtitreune><SPAN class=3Dtitreune>Carriers will bring answers next =
April 23-26=20
during the third edition of IPCN (Intersection of <STRONG>Mobile WAN and =

WLAN</STRONG>). </SPAN></SPAN></SPAN></SPAN></SPAN></FONT></DIV>
<DIV><FONT size=3D2><SPAN><SPAN class=3Dtitrepapier><SPAN =
class=3Dtitrepapier><SPAN=20
class=3Dtitreune><SPAN class=3Dtitreune>All details=20
at:</SPAN></SPAN></SPAN></SPAN></SPAN></FONT><FONT=20
size=3D2><SPAN><STRONG><BR></STRONG><A=20
href=3D"http://www.upperside.fr/ipcn02/baipcn02intro.htm">http://www.uppe=
rside.fr/ipcn02/baipcn02intro.htm</A></SPAN></FONT></DIV>
<DIV><FONT=20
size=3D2><SPAN></SPAN></FONT>&nbsp;</FONT></FONT></DIV></DIV></BODY></HTM=
L>

------=_NextPart_000_00C5_01C1CC07.1D15F460--


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


From daemon@optimus.ietf.org  Fri Mar 15 04:28:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24330
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 04:28:59 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA01574
	for manet-archive@odin.ietf.org; Fri, 15 Mar 2002 04:29:01 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28569;
	Fri, 15 Mar 2002 03:53:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28524
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 03:53:16 -0500 (EST)
Received: from smtp1.cluster.oleane.net (smtp1.cluster.oleane.net [195.25.12.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23743
	for <manet@ietf.org>; Fri, 15 Mar 2002 03:53:10 -0500 (EST)
Received: from oleane (upper-side.rain.fr [194.250.212.114]) by smtp1.cluster.oleane.net with SMTP id g2F8rBO00583 for <manet@ietf.org>; Fri, 15 Mar 2002 09:53:11 +0100 (CET)
Message-ID: <00c801c1cbfe$bb9c5100$1901a8c0@oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <manet@ietf.org>
Date: Fri, 15 Mar 2002 09:52:26 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00C5_01C1CC07.1D15F460"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Subject: [manet] IPCN 2002 (IP-based Cellular Networks)
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

This is a multi-part message in MIME format.

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

=20
One of the most interesting subjects of IPCN 2002 (IP-based Cellular =
Networks) is the relationship between the licensed 2.5/3G services and =
802.11 hotspots. How can optimal use be made of both environments such =
that a realistic business service is possible?=20
Carriers will bring answers next April 23-26 during the third edition of =
IPCN (Intersection of Mobile WAN and WLAN).=20
All details at:
http://www.upperside.fr/ipcn02/baipcn02intro.htm
=20

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial><FONT face=3DArial>&nbsp;
<DIV><FONT size=3D2><SPAN><SPAN class=3Dtitrepapier><SPAN =
class=3Dtitrepapier><SPAN=20
class=3Dtitreune><SPAN class=3Dtitreune><FONT color=3D#000000>One of the =
most=20
interesting subjects of IPCN 2002 (IP-based Cellular Networks) is the=20
relationship between the licensed 2.5/3G services and 802.11 hotspots. =
How can=20
optimal use be made of both environments such that a realistic business =
service=20
is possible? </FONT></SPAN></SPAN></SPAN></SPAN></SPAN></FONT></DIV>
<DIV><FONT size=3D2><SPAN><SPAN class=3Dtitrepapier><SPAN =
class=3Dtitrepapier><SPAN=20
class=3Dtitreune><SPAN class=3Dtitreune>Carriers will bring answers next =
April 23-26=20
during the third edition of IPCN (Intersection of <STRONG>Mobile WAN and =

WLAN</STRONG>). </SPAN></SPAN></SPAN></SPAN></SPAN></FONT></DIV>
<DIV><FONT size=3D2><SPAN><SPAN class=3Dtitrepapier><SPAN =
class=3Dtitrepapier><SPAN=20
class=3Dtitreune><SPAN class=3Dtitreune>All details=20
at:</SPAN></SPAN></SPAN></SPAN></SPAN></FONT><FONT=20
size=3D2><SPAN><STRONG><BR></STRONG><A=20
href=3D"http://www.upperside.fr/ipcn02/baipcn02intro.htm">http://www.uppe=
rside.fr/ipcn02/baipcn02intro.htm</A></SPAN></FONT></DIV>
<DIV><FONT=20
size=3D2><SPAN></SPAN></FONT>&nbsp;</FONT></FONT></DIV></DIV></BODY></HTM=
L>

------=_NextPart_000_00C5_01C1CC07.1D15F460--


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



From manet-admin@ietf.org  Fri Mar 15 05:03:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25036
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 05:03:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA03425;
	Fri, 15 Mar 2002 04:46:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA03396
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 04:46:18 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24635
	for <manet@ietf.org>; Fri, 15 Mar 2002 04:46:14 -0500 (EST)
Received: from impression.inria.fr (impression.inria.fr [128.93.17.98])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2F9kCv06741;
	Fri, 15 Mar 2002 10:46:12 +0100 (MET)
Received: by impression.inria.fr (sSMTP sendmail emulation); Fri, 15 Mar 2002 10:46:07 +0100
From: Laurent Viennot <Laurent.Viennot@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15505.49887.435301.842784@impression.inria.fr>
Date: Fri, 15 Mar 2002 10:46:07 +0100
To: ogier@erg.sri.com
Cc: Joe Macker <macker@itd.nrl.navy.mil>, manet@ietf.org
Subject: Re: [manet] OLSR questions 
In-Reply-To: <200203141640.IAA20006@pit.erg.sri.com>
References: <200203132245.OAA18566@pit.erg.sri.com>
	<200203141640.IAA20006@pit.erg.sri.com>
X-Mailer: VM 6.92 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Reply-To: Laurent.Viennot@inria.fr
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Richard,

The problem with advertising RIDs in Hello is that it is not
sufficient for detecting uni-directional links in some weird
situations with wireless connections.

Suppose for example the following scenario :

        ______________            _____________
       |              |     /--= |I1           |
       | Main ->   J1 |=<--/   = |I2   <- Main |
       |              |  \__-->= |I3           |
        --------------            -------------

There are two unidirectional links between I and J: one from interface
J1 to I3 and the other from interface I1 to J1.

If J1 anounces "I hear node I" then the node I thinks it has a
bi-directional link between I3 and J1 which is false.
To deal with such weird cases, J1 has to announce "I hear I1" as
proposed in MESH.

Such a situation may occur with directional antennas for example. With
IEEE 802.11, nodes I and J cannot communicate since ACKs for unicast
transmissions will always be lost.

I agree this could be optimized for IPv6 support.

laurent

ogier@erg.sri.com writes:
 > 
 > TBRPF has other features that are shared by OSPF but not by OLSR
 > (in addition to sending each HELLO on a single interface). For example, 
 > neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
 > Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs, 
 > not neighbor interfaces. This greatly improves efficiency for IPv6, 
 > since RIDs remain at 32 bits in OSPF for IPv6.
 > 
 > Richard

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


From manet-admin@ietf.org  Fri Mar 15 05:42:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25798
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 05:42:13 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA06081;
	Fri, 15 Mar 2002 05:09:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA06051
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 05:09:12 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25133
	for <manet@ietf.org>; Fri, 15 Mar 2002 05:09:08 -0500 (EST)
Received: from impression.inria.fr (impression.inria.fr [128.93.17.98])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2FA99v07959;
	Fri, 15 Mar 2002 11:09:09 +0100 (MET)
Received: by impression.inria.fr (sSMTP sendmail emulation); Fri, 15 Mar 2002 11:09:04 +0100
From: Laurent Viennot <Laurent.Viennot@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15505.51263.987571.258275@impression.inria.fr>
Date: Fri, 15 Mar 2002 11:09:03 +0100
To: ogier@erg.sri.com
Cc: manet@ietf.org
Subject: [manet] Re: Manet flooding / broadcasting....
In-Reply-To: <200203150328.TAA21475@pit.erg.sri.com>
References: <200201310000.QAA19810@pit.erg.sri.com>
	<200203150328.TAA21475@pit.erg.sri.com>
X-Mailer: VM 6.92 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Reply-To: Laurent.Viennot@inria.fr
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


Richard,

I do not understand why you think I have avoided your arguments. I
have just tried to promote link hysteresis advanced functioning
because it allows to detect neighbor changes quicker than 2-hop
neighbor changes. Adding REFRESH_INTERVAL is just a matter of allowing
this with basic neighbor sensing functioning.

It seems you misunderstand the introduction of REFRESH_PERIOD. The
general idea behind OLSR is to allow a certain tunability. We want to
leave enough freedom to implementors so that they can optimize their
code for their specific needs. For example, depending on the link
layer performances you may implement the protocol in different ways.


laurent



ogier@erg.sri.com writes:
 > 
 > Philippe,
 > 
 > It is interesting to consider the discussion I had with
 > you in January regarding HELLOs (see below), in light of 
 > your new parameter REFRESH_INTERVAL.  For example, you said
 > "you only need to refresh al neighbors within a certain
 > period".  At that time, the refresh period was HELLO_INTERVAL,
 > since you did not yet introduce REFRESH_INTERVAL.
 > I was wondering why you said "a certain period" instead
 > of HELLO_INTERVAL, and now I know why.
 > 
 > This was the main point on which I never agreed with Laurent,
 > and I gave up arguing with him because he avoided my main
 > point that in OLSR (version 05) every neighbor must be reported 
 > in a HELLO every HELLO_INTERVAL. 
 > 
 > Instead of agreeing with me that something needed to be changed,
 > you pretended that no change was needed, and then later 
 > introduced the new parameter REFRESH_INTERVAL, which would have
 > addressed my concern.
 > 
 > Adding this new parameter allows OLSR to perform neighbor sensing 
 > similar to TBRPF, but it also adds complexity to OLSR.
 > In my opinion, TBRPF is designed better than OLSR in many ways,
 > and you are having to patch OLSR (thus making it more complex)
 > in order to compete with TBRPF.  Maybe next you will find a way
 > to make (1-hop) neighbor discovery modular, or introduce 
 > differential TC messages.
 > 
 > Richard
 > 
 > 
 > > > ----- Original Message -----
 > > > From: <ogier@erg.sri.com>
 > > > To: <manet@itd.nrl.navy.mil>
 > > > Cc: <ogier@erg.sri.com>
 > > > Sent: Tuesday, January 29, 2002 8:58 PM
 > > > Subject: Re: Manet flooding / broadcasting....
 > > >
 > > >
 > > > >
 > > > > Since HELLOs are differential in TBRPF, this can be done with a
 > > > > relatively small increase in overhead.  However, in OSPF and OLSR,
 > > > > since each HELLO contains all neighbor IDs, this would increase
 > > > > overhead a lot if each node has a large number of neighbors.
 > > > >
 > > > Richard, again, OLSR HELLOs can be partial, you only need to refresh all
 > > > neighbors within a certain period, and you can increase the hello rate for
 > > > fast moving node. I think Laurent mentioned this to you before.
 > > 
 > > Philippe,
 > > 
 > > Yes, I know that HELLOs can be partial and that each neighbor must be 
 > > included in at least one HELLO every HELLO interval, but unless there 
 > > are too many neighbor IDs to fit into one packet, normally OLSR uses one 
 > > full HELLO per HELLO interval.  (Just check the source code.)
 > > 
 > > But this does not affect my argument.  What I am saying is that OLSR 
 > > must include each neighbor in a HELLO every HELLO_INTERVAL, whereas 
 > > TBRPF includes each neighbor only in periodic topology updates, which are 
 > > less frequent (e.g., 10 times less frequent if the HELLO_INTERVAL is 0.5 s 
 > > and the update period is 5 s).
 > > 
 > > It is the HELLO_INTERVAL that determines how quickly a failed link is 
 > > detected, e.g., if no HELLO is received within 3 * HELLO_INTERVAL, then 
 > > the neighbor is declared to be lost.
 > > 
 > > I also know that OLSR can use differential HELLOs,
 > > since it has recently added the LOST_LINK status (which TBRPF has
 > > had since version 01).  *But this does not change the requirement that 
 > > in OLSR each neighbor ID must be included in at least one HELLO every 
 > > HELLO_INTERVAL.*  You can increase HELLO_INTERVAL, but then it
 > > would take longer to detect a lost neighbor.  OLSR could be *modified* 
 > > so that each neighbor ID is reported less frequently than HELLO_INTERVAL
 > > (as in TBRPF), but I am not sure how this would affect MPR computation.
 > > 
 > > However don't forget that even the overhead of an empty HELLO can be non 
 > > > negligible.  In IEEE 802.11 the MAC-PHY overhead is around 192 usec (with 
 > > > option to 92 usec) which at 11 Mbps corresponds to approximately 60 IPv4 
 > > > addresses.
 > > 
 > > Yes, this is a good point.  With the 92 usec option, this becomes about 30 
 > > IPv4 addresses (or router IDs).  So if a node has 30 neighbors, then a full 
 > > HELLO is about twice as big as an empty HELLO.  I think that's significant.
 > > 
 > > There are lots of differences between TBRPF and OLSR that can affect
 > > performance, and we have already discussed many of these.
 > > But it is difficult to predict how these differences affect performance.
 > > That's what simulations are for.
 > > 
 > > Regards,
 > > Richard
 > > 
 > 
 > _______________________________________________
 > manet mailing list
 > manet@ietf.org
 > https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Fri Mar 15 05:42:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25808
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 05:42:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA09154
	for manet-archive@odin.ietf.org; Fri, 15 Mar 2002 05:42:17 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA06081;
	Fri, 15 Mar 2002 05:09:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA06051
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 05:09:12 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25133
	for <manet@ietf.org>; Fri, 15 Mar 2002 05:09:08 -0500 (EST)
Received: from impression.inria.fr (impression.inria.fr [128.93.17.98])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2FA99v07959;
	Fri, 15 Mar 2002 11:09:09 +0100 (MET)
Received: by impression.inria.fr (sSMTP sendmail emulation); Fri, 15 Mar 2002 11:09:04 +0100
From: Laurent Viennot <Laurent.Viennot@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15505.51263.987571.258275@impression.inria.fr>
Date: Fri, 15 Mar 2002 11:09:03 +0100
To: ogier@erg.sri.com
Cc: manet@ietf.org
Subject: [manet] Re: Manet flooding / broadcasting....
In-Reply-To: <200203150328.TAA21475@pit.erg.sri.com>
References: <200201310000.QAA19810@pit.erg.sri.com>
	<200203150328.TAA21475@pit.erg.sri.com>
X-Mailer: VM 6.92 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Reply-To: Laurent.Viennot@inria.fr
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


Richard,

I do not understand why you think I have avoided your arguments. I
have just tried to promote link hysteresis advanced functioning
because it allows to detect neighbor changes quicker than 2-hop
neighbor changes. Adding REFRESH_INTERVAL is just a matter of allowing
this with basic neighbor sensing functioning.

It seems you misunderstand the introduction of REFRESH_PERIOD. The
general idea behind OLSR is to allow a certain tunability. We want to
leave enough freedom to implementors so that they can optimize their
code for their specific needs. For example, depending on the link
layer performances you may implement the protocol in different ways.


laurent



ogier@erg.sri.com writes:
 > 
 > Philippe,
 > 
 > It is interesting to consider the discussion I had with
 > you in January regarding HELLOs (see below), in light of 
 > your new parameter REFRESH_INTERVAL.  For example, you said
 > "you only need to refresh al neighbors within a certain
 > period".  At that time, the refresh period was HELLO_INTERVAL,
 > since you did not yet introduce REFRESH_INTERVAL.
 > I was wondering why you said "a certain period" instead
 > of HELLO_INTERVAL, and now I know why.
 > 
 > This was the main point on which I never agreed with Laurent,
 > and I gave up arguing with him because he avoided my main
 > point that in OLSR (version 05) every neighbor must be reported 
 > in a HELLO every HELLO_INTERVAL. 
 > 
 > Instead of agreeing with me that something needed to be changed,
 > you pretended that no change was needed, and then later 
 > introduced the new parameter REFRESH_INTERVAL, which would have
 > addressed my concern.
 > 
 > Adding this new parameter allows OLSR to perform neighbor sensing 
 > similar to TBRPF, but it also adds complexity to OLSR.
 > In my opinion, TBRPF is designed better than OLSR in many ways,
 > and you are having to patch OLSR (thus making it more complex)
 > in order to compete with TBRPF.  Maybe next you will find a way
 > to make (1-hop) neighbor discovery modular, or introduce 
 > differential TC messages.
 > 
 > Richard
 > 
 > 
 > > > ----- Original Message -----
 > > > From: <ogier@erg.sri.com>
 > > > To: <manet@itd.nrl.navy.mil>
 > > > Cc: <ogier@erg.sri.com>
 > > > Sent: Tuesday, January 29, 2002 8:58 PM
 > > > Subject: Re: Manet flooding / broadcasting....
 > > >
 > > >
 > > > >
 > > > > Since HELLOs are differential in TBRPF, this can be done with a
 > > > > relatively small increase in overhead.  However, in OSPF and OLSR,
 > > > > since each HELLO contains all neighbor IDs, this would increase
 > > > > overhead a lot if each node has a large number of neighbors.
 > > > >
 > > > Richard, again, OLSR HELLOs can be partial, you only need to refresh all
 > > > neighbors within a certain period, and you can increase the hello rate for
 > > > fast moving node. I think Laurent mentioned this to you before.
 > > 
 > > Philippe,
 > > 
 > > Yes, I know that HELLOs can be partial and that each neighbor must be 
 > > included in at least one HELLO every HELLO interval, but unless there 
 > > are too many neighbor IDs to fit into one packet, normally OLSR uses one 
 > > full HELLO per HELLO interval.  (Just check the source code.)
 > > 
 > > But this does not affect my argument.  What I am saying is that OLSR 
 > > must include each neighbor in a HELLO every HELLO_INTERVAL, whereas 
 > > TBRPF includes each neighbor only in periodic topology updates, which are 
 > > less frequent (e.g., 10 times less frequent if the HELLO_INTERVAL is 0.5 s 
 > > and the update period is 5 s).
 > > 
 > > It is the HELLO_INTERVAL that determines how quickly a failed link is 
 > > detected, e.g., if no HELLO is received within 3 * HELLO_INTERVAL, then 
 > > the neighbor is declared to be lost.
 > > 
 > > I also know that OLSR can use differential HELLOs,
 > > since it has recently added the LOST_LINK status (which TBRPF has
 > > had since version 01).  *But this does not change the requirement that 
 > > in OLSR each neighbor ID must be included in at least one HELLO every 
 > > HELLO_INTERVAL.*  You can increase HELLO_INTERVAL, but then it
 > > would take longer to detect a lost neighbor.  OLSR could be *modified* 
 > > so that each neighbor ID is reported less frequently than HELLO_INTERVAL
 > > (as in TBRPF), but I am not sure how this would affect MPR computation.
 > > 
 > > However don't forget that even the overhead of an empty HELLO can be non 
 > > > negligible.  In IEEE 802.11 the MAC-PHY overhead is around 192 usec (with 
 > > > option to 92 usec) which at 11 Mbps corresponds to approximately 60 IPv4 
 > > > addresses.
 > > 
 > > Yes, this is a good point.  With the 92 usec option, this becomes about 30 
 > > IPv4 addresses (or router IDs).  So if a node has 30 neighbors, then a full 
 > > HELLO is about twice as big as an empty HELLO.  I think that's significant.
 > > 
 > > There are lots of differences between TBRPF and OLSR that can affect
 > > performance, and we have already discussed many of these.
 > > But it is difficult to predict how these differences affect performance.
 > > That's what simulations are for.
 > > 
 > > Regards,
 > > Richard
 > > 
 > 
 > _______________________________________________
 > manet mailing list
 > manet@ietf.org
 > https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Fri Mar 15 05:48:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25893
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 05:48:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA07421;
	Fri, 15 Mar 2002 05:28:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA07391
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 05:28:24 -0500 (EST)
Received: from mailhost.cs.auc.dk (root@mailhost.cs.auc.dk [130.225.194.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25557
	for <manet@ietf.org>; Fri, 15 Mar 2002 05:28:20 -0500 (EST)
From: T.Clausen@computer.org
Received: from localhost (root@pico.cs.auc.dk [130.225.194.80])
	by mailhost.cs.auc.dk (8.12.2/8.12.2) with ESMTP id g2FASIgG000441;
	Fri, 15 Mar 2002 11:28:18 +0100 (MET)
Date: Fri, 15 Mar 2002 11:28:17 +0100 (CET)
X-Sender: voop@armada
To: ogier@erg.sri.com
cc: manet@ietf.org
Subject: Re: [manet] OLSR questions 
In-Reply-To: <200203141855.KAA20299@pit.erg.sri.com>
Message-ID: <Pine.LNX.4.21.0203151127100.730-100000@armada>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-Scanned-By: MIMEDefang 2.2
Content-Transfer-Encoding: 8BIT
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8BIT

Dear Richard,

OLSR has been based on the same stable core algorithm and functionality
since the very first versions. Our recent changes have merely concirned
maturing the details and ensure that the protocol are flexible enough not
to lock implementations into optimizations for specific scenarios.

You say, that you find the neighbor sensing of OLSR to be mature and
flexible enough to support the mechanisms and optimizations of the TBRPF
neighbor sensing. I am glad that you think so, and I take that this is an
indication that OLSR has matured in a good way.

--thomas

-- 

-------------------------------------------
  Thomas Heide Clausen
  Civilingeniør i Datateknik (cand.polyt)
  M.Sc in Computer Engineering

  E-Mail: T.Clausen@computer.org
  WWW:    http://www.cs.auc.dk/~voop
-------------------------------------------


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


From daemon@optimus.ietf.org  Fri Mar 15 05:56:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25042
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 05:03:39 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA05388
	for manet-archive@odin.ietf.org; Fri, 15 Mar 2002 05:03:42 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA03425;
	Fri, 15 Mar 2002 04:46:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA03396
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 04:46:18 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24635
	for <manet@ietf.org>; Fri, 15 Mar 2002 04:46:14 -0500 (EST)
Received: from impression.inria.fr (impression.inria.fr [128.93.17.98])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2F9kCv06741;
	Fri, 15 Mar 2002 10:46:12 +0100 (MET)
Received: by impression.inria.fr (sSMTP sendmail emulation); Fri, 15 Mar 2002 10:46:07 +0100
From: Laurent Viennot <Laurent.Viennot@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15505.49887.435301.842784@impression.inria.fr>
Date: Fri, 15 Mar 2002 10:46:07 +0100
To: ogier@erg.sri.com
Cc: Joe Macker <macker@itd.nrl.navy.mil>, manet@ietf.org
Subject: Re: [manet] OLSR questions 
In-Reply-To: <200203141640.IAA20006@pit.erg.sri.com>
References: <200203132245.OAA18566@pit.erg.sri.com>
	<200203141640.IAA20006@pit.erg.sri.com>
X-Mailer: VM 6.92 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Reply-To: Laurent.Viennot@inria.fr
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Richard,

The problem with advertising RIDs in Hello is that it is not
sufficient for detecting uni-directional links in some weird
situations with wireless connections.

Suppose for example the following scenario :

        ______________            _____________
       |              |     /--= |I1           |
       | Main ->   J1 |=<--/   = |I2   <- Main |
       |              |  \__-->= |I3           |
        --------------            -------------

There are two unidirectional links between I and J: one from interface
J1 to I3 and the other from interface I1 to J1.

If J1 anounces "I hear node I" then the node I thinks it has a
bi-directional link between I3 and J1 which is false.
To deal with such weird cases, J1 has to announce "I hear I1" as
proposed in MESH.

Such a situation may occur with directional antennas for example. With
IEEE 802.11, nodes I and J cannot communicate since ACKs for unicast
transmissions will always be lost.

I agree this could be optimized for IPv6 support.

laurent

ogier@erg.sri.com writes:
 > 
 > TBRPF has other features that are shared by OSPF but not by OLSR
 > (in addition to sending each HELLO on a single interface). For example, 
 > neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
 > Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs, 
 > not neighbor interfaces. This greatly improves efficiency for IPv6, 
 > since RIDs remain at 32 bits in OSPF for IPv6.
 > 
 > Richard

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



From daemon@optimus.ietf.org  Fri Mar 15 06:41:32 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25902
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 05:48:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id FAA09609
	for manet-archive@odin.ietf.org; Fri, 15 Mar 2002 05:48:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA07421;
	Fri, 15 Mar 2002 05:28:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA07391
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 05:28:24 -0500 (EST)
Received: from mailhost.cs.auc.dk (root@mailhost.cs.auc.dk [130.225.194.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA25557
	for <manet@ietf.org>; Fri, 15 Mar 2002 05:28:20 -0500 (EST)
From: T.Clausen@computer.org
Received: from localhost (root@pico.cs.auc.dk [130.225.194.80])
	by mailhost.cs.auc.dk (8.12.2/8.12.2) with ESMTP id g2FASIgG000441;
	Fri, 15 Mar 2002 11:28:18 +0100 (MET)
Date: Fri, 15 Mar 2002 11:28:17 +0100 (CET)
X-Sender: voop@armada
To: ogier@erg.sri.com
cc: manet@ietf.org
Subject: Re: [manet] OLSR questions 
In-Reply-To: <200203141855.KAA20299@pit.erg.sri.com>
Message-ID: <Pine.LNX.4.21.0203151127100.730-100000@armada>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-Scanned-By: MIMEDefang 2.2
Content-Transfer-Encoding: 8BIT
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8BIT

Dear Richard,

OLSR has been based on the same stable core algorithm and functionality
since the very first versions. Our recent changes have merely concirned
maturing the details and ensure that the protocol are flexible enough not
to lock implementations into optimizations for specific scenarios.

You say, that you find the neighbor sensing of OLSR to be mature and
flexible enough to support the mechanisms and optimizations of the TBRPF
neighbor sensing. I am glad that you think so, and I take that this is an
indication that OLSR has matured in a good way.

--thomas

-- 

-------------------------------------------
  Thomas Heide Clausen
  Civilingeniør i Datateknik (cand.polyt)
  M.Sc in Computer Engineering

  E-Mail: T.Clausen@computer.org
  WWW:    http://www.cs.auc.dk/~voop
-------------------------------------------


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



From manet-admin@ietf.org  Fri Mar 15 07:30:01 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27349
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 07:30:01 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14588;
	Fri, 15 Mar 2002 07:01:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14558
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 07:01:14 -0500 (EST)
Received: from mailhost.cs.auc.dk (root@mailhost.cs.auc.dk [130.225.194.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26957
	for <manet@ietf.org>; Fri, 15 Mar 2002 07:01:11 -0500 (EST)
From: T.Clausen@computer.org
Received: from localhost (root@pico.cs.auc.dk [130.225.194.80])
	by mailhost.cs.auc.dk (8.12.2/8.12.2) with ESMTP id g2FC15gG009049;
	Fri, 15 Mar 2002 13:01:06 +0100 (MET)
Date: Fri, 15 Mar 2002 12:59:58 +0100 (CET)
X-Sender: voop@armada
To: ogier@erg.sri.com
cc: manet@ietf.org
Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing
 protocols
In-Reply-To: <200203132350.PAA18795@pit.erg.sri.com>
Message-ID: <Pine.LNX.4.21.0203151259200.730-100000@armada>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-Scanned-By: MIMEDefang 2.2
Content-Transfer-Encoding: 8BIT
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8BIT

Dear Richard,

I've been running 30 different scenarios, all corresponding to the
parameters you specify and at all data rates between 1 and 10. Over
those simulations, I consistently find that, at the sample point of 6 pps,
the routing load is roughly half that of the simulations you present.
Interrestingly enough, I also get a higher delivery rate: above 90%,
rather than the (roughly) 85% you present.

--thomas

On Wed, 13 Mar 2002 ogier@erg.sri.com wrote:

> 
> Thomas,
> 
> I checked very thoroughly to make sure we are extracting
> information correctly from the ns2 trace files, and we are
> definitely doing this correctly (as you described).
> 
> I am very curious to know why our simulations differ from yours.
> Maybe we are not even running the same scenario, which is why
> I sent you our cbr and scenario script files last Friday.
> Did you run that scenario yet?  If so, did you get results
> that are similar to ours?
> 
> Richard
> 
> 
> ------- Forwarded Message
> 
> Message-Id: <200203090101.RAA10048@pit.erg.sri.com>
> To: t.clausen@computer.org, manet@ietf.org
> cc: ogier@erg.sri.com
> Reply-To: ogier@erg.sri.com
> From: ogier@erg.sri.com
> Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
> In-reply-to: Your message of "Fri, 08 Mar 2002 08:09:06 PST."
>              <200203081609.IAA08495@pit.erg.sri.com> 
> Date: Fri, 08 Mar 2002 17:01:20 -0800
> Sender: manet-admin@ietf.org
> Errors-To: manet-admin@ietf.org
> X-Mailman-Version: 1.0
> Precedence: bulk
> List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
> X-BeenThere: manet@ietf.org
> Content-Type: text
> Content-Length: 7048
> 
> 
> Thomas,
> 
> So that we can determine why our results differ, I will
> provide additional details and scripts, so that you can run
> the same experiment I ran.  I will give you the cbr 
> and scenario scripts in a separate email.
> 
> I will refer to the case with 100 nodes, 20 sources, 670x670 area, 
> no mobility, and a packet rate of 6 packets/second/source.  
> Each stream begins at a random time between 10 and 40 seconds, and 
> changes its destination to a randomly selected node every 30 seconds. 
> The size of each data packet is 512 bytes. 
> The total number of packets generated in 500 sec is 57261,
> which is slightly less than 60000 = 6 * 20 * 500.
> Is this similar to what you ran?
> 
> Richard
> 
> 
> > Thomas,
> > 
> > > The way in which I extract overhead information from the ns2 tracefiles is
> > > to look at all "send" events on the "MAC" layer from the agent
> > > "OLSR". This should yield both the number of packets being transmitted as
> > > well as the number of bytes, actually reaching the MAC layer and not
> > > being dropped somewhere else.
> > > 
> > > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > > was possible to end up with overhead figures very close those that you
> > > cite. I do believe, though, that this is a wrong way of accounting, since
> > > (1) control packets, dropped in the protocol stack (and thus not
> > > contributing to diffusion of topology information) are accounted as
> > > protocol overhead and, (2) control packets are accounted multiple times
> > > (each time a layer is sending the packet "downwards" in the stack.)
> > 
> > We counted packets exactly the same way you did, i.e., 
> > only at the MAC layer.  
> > 
> > To double check, I did the following:
> > 
> > grep "s " out.tr | grep MAC | grep OLSR   
> > 
> > and got exactly the same number of OLSR packets
> > as our perl script did.
> > 
> > I did this for the following case:
> > 100 nodes, 670x670 area, no mobility, 20 sources, packet rate = 6
> > For 500 seconds, there were 154744 OLSR packets totaling 20684584, 
> > so the average size of an OLSR packet (including the IP and MAC 
> > headers) is 133 bytes. 
> > 
> > I also would like to find out why our results differ.
> > If you have any more ideas, please let me know.
> > 
> > Regarding the 90-120% increase of overhead for the bug fix, 
> > that was for 100 nodes.  I later tried 50 nodes and found
> > the increase to be roughly 75-90%.
> > 
> > Richard
> > 
> > 
> > > Richard,
> > > 
> > > I suspect serious problems with your control overhead measures. Please see
> > > below.
> > > 
> > > On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:
> > > 
> > > > 
> > > > Thomas,
> > > > 
> > > > > Richard,
> > > > > 
> > > > > I am not quite sure what to make from your simulations. It seems to me
> > > > > that they are from a network in overload condition - in which case buff
> er
> > > > > management has a critical impact on performance. We've been simulating
> > > > > OLSR in conditions, similar to those you've been showing, and our resul
> ts
> > > > > differ significantly. We experience that a large abmount of (data and
> > > > > control) traffic in these situations are rejected from the various
> > > > > buffers.
> > > > 
> > > 
> > > <SNIP> 
> > > 
> > > > To ensure that the protocols were compared on a fair basis,
> > > > since AODV and TBRPF gave control traffic higher priority than
> > > > data traffic, we did the same for OLSR.  It has long been considered
> > > > a good idea to give control traffic higher priority.  This could 
> > > > explain why your results differ from mine.
> > > > You can do this simply by adding the line
> > > >                 case PT_OLSR:
> > > > to the function PriQueue::recv() in priqueue.cc.
> > > > 
> > > > > Also, I notice that we obtain much less overhead for OLSR when counting
> > > > > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > > > > detailed information (e.g. physical overhead etc.) ?
> > > > 
> > > > No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> > > > at the MAC layer.  
> > > > 
> > > 
> > > <SNIP> 
> > > 
> > > I've tried to reproduce your published results for OLSR, using a large set
> > > of scenario files, corresponding to the parameters you've used.
> > > 
> > > Unfortunately I fail to achieve the same results as those you present
> > > (both with and without control traffic priority): in particulary in the
> > > overload condition (packet rate of 6-8 packets/second) I find the overhead
> > > of OLSR to be significantly lower (up to 25-30%) than what your
> > > simulations show.
> > > 
> > > Also, as we were discussing in another mail, my simulations showed that
> > > the "control packet size" bug resulted in approximately 50% more overhead,
> > > whereas you cited your simulations as showing in the orders of 90-120%
> > > more overhead. I have not had success in reproducing the 90-120% figures 
> > > either.
> > > 
> > > I am basically looking for an explanation on why we have such different
> > > results.
> > > 
> > > I am well aware that a paticulary "bad" or "good" choise of scenario (even
> > > corresponding to the same general parameters such as mobility and traffic
> > > patterns) may trigger particulary good or bad results, so I've run a
> > > number of different scenarios through, all with roughly the same results.
> > > This left me wondering if our different results were just a matter of
> > > computing the overhead differently?
> > > 
> > > The way in which I extract overhead information from the ns2 tracefiles is
> > > to look at all "send" events on the "MAC" layer from the agent
> > > "OLSR". This should yield both the number of packets being transmitted as
> > > well as the number of bytes, actually reaching the MAC layer and not
> > > being dropped somewhere else.
> > > 
> > > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > > was possible to end up with overhead figures very close those that you
> > > cite. I do believe, though, that this is a wrong way of accounting, since
> > > (1) control packets, dropped in the protocol stack (and thus not
> > > contributing to diffusion of topology information) are accounted as
> > > protocol overhead and, (2) control packets are accounted multiple times
> > > (each time a layer is sending the packet "downwards" in the stack.)
> > 
> > 
> > > 
> > > -- 
> > > 
> > > -------------------------------------------
> > >   Thomas Heide Clausen
> > >   Civilingeniør i Datateknik (cand.polyt)
> > >   M.Sc in Computer Engineering
> > > 
> > >   E-Mail: T.Clausen@computer.org
> > >   WWW:    http://www.cs.auc.dk/~voop
> > > -------------------------------------------
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 
> ------- End of Forwarded Message
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

-- 

-------------------------------------------
  Thomas Heide Clausen
  Civilingeniør i Datateknik (cand.polyt)
  M.Sc in Computer Engineering

  E-Mail: T.Clausen@computer.org
  WWW:    http://www.cs.auc.dk/~voop
-------------------------------------------


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


From daemon@optimus.ietf.org  Fri Mar 15 07:30:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27363
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 07:30:03 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id HAA16069
	for manet-archive@odin.ietf.org; Fri, 15 Mar 2002 07:30:05 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14588;
	Fri, 15 Mar 2002 07:01:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA14558
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 07:01:14 -0500 (EST)
Received: from mailhost.cs.auc.dk (root@mailhost.cs.auc.dk [130.225.194.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26957
	for <manet@ietf.org>; Fri, 15 Mar 2002 07:01:11 -0500 (EST)
From: T.Clausen@computer.org
Received: from localhost (root@pico.cs.auc.dk [130.225.194.80])
	by mailhost.cs.auc.dk (8.12.2/8.12.2) with ESMTP id g2FC15gG009049;
	Fri, 15 Mar 2002 13:01:06 +0100 (MET)
Date: Fri, 15 Mar 2002 12:59:58 +0100 (CET)
X-Sender: voop@armada
To: ogier@erg.sri.com
cc: manet@ietf.org
Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing
 protocols
In-Reply-To: <200203132350.PAA18795@pit.erg.sri.com>
Message-ID: <Pine.LNX.4.21.0203151259200.730-100000@armada>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-Scanned-By: MIMEDefang 2.2
Content-Transfer-Encoding: 8BIT
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8BIT

Dear Richard,

I've been running 30 different scenarios, all corresponding to the
parameters you specify and at all data rates between 1 and 10. Over
those simulations, I consistently find that, at the sample point of 6 pps,
the routing load is roughly half that of the simulations you present.
Interrestingly enough, I also get a higher delivery rate: above 90%,
rather than the (roughly) 85% you present.

--thomas

On Wed, 13 Mar 2002 ogier@erg.sri.com wrote:

> 
> Thomas,
> 
> I checked very thoroughly to make sure we are extracting
> information correctly from the ns2 trace files, and we are
> definitely doing this correctly (as you described).
> 
> I am very curious to know why our simulations differ from yours.
> Maybe we are not even running the same scenario, which is why
> I sent you our cbr and scenario script files last Friday.
> Did you run that scenario yet?  If so, did you get results
> that are similar to ours?
> 
> Richard
> 
> 
> ------- Forwarded Message
> 
> Message-Id: <200203090101.RAA10048@pit.erg.sri.com>
> To: t.clausen@computer.org, manet@ietf.org
> cc: ogier@erg.sri.com
> Reply-To: ogier@erg.sri.com
> From: ogier@erg.sri.com
> Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
> In-reply-to: Your message of "Fri, 08 Mar 2002 08:09:06 PST."
>              <200203081609.IAA08495@pit.erg.sri.com> 
> Date: Fri, 08 Mar 2002 17:01:20 -0800
> Sender: manet-admin@ietf.org
> Errors-To: manet-admin@ietf.org
> X-Mailman-Version: 1.0
> Precedence: bulk
> List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
> X-BeenThere: manet@ietf.org
> Content-Type: text
> Content-Length: 7048
> 
> 
> Thomas,
> 
> So that we can determine why our results differ, I will
> provide additional details and scripts, so that you can run
> the same experiment I ran.  I will give you the cbr 
> and scenario scripts in a separate email.
> 
> I will refer to the case with 100 nodes, 20 sources, 670x670 area, 
> no mobility, and a packet rate of 6 packets/second/source.  
> Each stream begins at a random time between 10 and 40 seconds, and 
> changes its destination to a randomly selected node every 30 seconds. 
> The size of each data packet is 512 bytes. 
> The total number of packets generated in 500 sec is 57261,
> which is slightly less than 60000 = 6 * 20 * 500.
> Is this similar to what you ran?
> 
> Richard
> 
> 
> > Thomas,
> > 
> > > The way in which I extract overhead information from the ns2 tracefiles is
> > > to look at all "send" events on the "MAC" layer from the agent
> > > "OLSR". This should yield both the number of packets being transmitted as
> > > well as the number of bytes, actually reaching the MAC layer and not
> > > being dropped somewhere else.
> > > 
> > > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > > was possible to end up with overhead figures very close those that you
> > > cite. I do believe, though, that this is a wrong way of accounting, since
> > > (1) control packets, dropped in the protocol stack (and thus not
> > > contributing to diffusion of topology information) are accounted as
> > > protocol overhead and, (2) control packets are accounted multiple times
> > > (each time a layer is sending the packet "downwards" in the stack.)
> > 
> > We counted packets exactly the same way you did, i.e., 
> > only at the MAC layer.  
> > 
> > To double check, I did the following:
> > 
> > grep "s " out.tr | grep MAC | grep OLSR   
> > 
> > and got exactly the same number of OLSR packets
> > as our perl script did.
> > 
> > I did this for the following case:
> > 100 nodes, 670x670 area, no mobility, 20 sources, packet rate = 6
> > For 500 seconds, there were 154744 OLSR packets totaling 20684584, 
> > so the average size of an OLSR packet (including the IP and MAC 
> > headers) is 133 bytes. 
> > 
> > I also would like to find out why our results differ.
> > If you have any more ideas, please let me know.
> > 
> > Regarding the 90-120% increase of overhead for the bug fix, 
> > that was for 100 nodes.  I later tried 50 nodes and found
> > the increase to be roughly 75-90%.
> > 
> > Richard
> > 
> > 
> > > Richard,
> > > 
> > > I suspect serious problems with your control overhead measures. Please see
> > > below.
> > > 
> > > On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:
> > > 
> > > > 
> > > > Thomas,
> > > > 
> > > > > Richard,
> > > > > 
> > > > > I am not quite sure what to make from your simulations. It seems to me
> > > > > that they are from a network in overload condition - in which case buff
> er
> > > > > management has a critical impact on performance. We've been simulating
> > > > > OLSR in conditions, similar to those you've been showing, and our resul
> ts
> > > > > differ significantly. We experience that a large abmount of (data and
> > > > > control) traffic in these situations are rejected from the various
> > > > > buffers.
> > > > 
> > > 
> > > <SNIP> 
> > > 
> > > > To ensure that the protocols were compared on a fair basis,
> > > > since AODV and TBRPF gave control traffic higher priority than
> > > > data traffic, we did the same for OLSR.  It has long been considered
> > > > a good idea to give control traffic higher priority.  This could 
> > > > explain why your results differ from mine.
> > > > You can do this simply by adding the line
> > > >                 case PT_OLSR:
> > > > to the function PriQueue::recv() in priqueue.cc.
> > > > 
> > > > > Also, I notice that we obtain much less overhead for OLSR when counting
> > > > > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > > > > detailed information (e.g. physical overhead etc.) ?
> > > > 
> > > > No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> > > > at the MAC layer.  
> > > > 
> > > 
> > > <SNIP> 
> > > 
> > > I've tried to reproduce your published results for OLSR, using a large set
> > > of scenario files, corresponding to the parameters you've used.
> > > 
> > > Unfortunately I fail to achieve the same results as those you present
> > > (both with and without control traffic priority): in particulary in the
> > > overload condition (packet rate of 6-8 packets/second) I find the overhead
> > > of OLSR to be significantly lower (up to 25-30%) than what your
> > > simulations show.
> > > 
> > > Also, as we were discussing in another mail, my simulations showed that
> > > the "control packet size" bug resulted in approximately 50% more overhead,
> > > whereas you cited your simulations as showing in the orders of 90-120%
> > > more overhead. I have not had success in reproducing the 90-120% figures 
> > > either.
> > > 
> > > I am basically looking for an explanation on why we have such different
> > > results.
> > > 
> > > I am well aware that a paticulary "bad" or "good" choise of scenario (even
> > > corresponding to the same general parameters such as mobility and traffic
> > > patterns) may trigger particulary good or bad results, so I've run a
> > > number of different scenarios through, all with roughly the same results.
> > > This left me wondering if our different results were just a matter of
> > > computing the overhead differently?
> > > 
> > > The way in which I extract overhead information from the ns2 tracefiles is
> > > to look at all "send" events on the "MAC" layer from the agent
> > > "OLSR". This should yield both the number of packets being transmitted as
> > > well as the number of bytes, actually reaching the MAC layer and not
> > > being dropped somewhere else.
> > > 
> > > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > > was possible to end up with overhead figures very close those that you
> > > cite. I do believe, though, that this is a wrong way of accounting, since
> > > (1) control packets, dropped in the protocol stack (and thus not
> > > contributing to diffusion of topology information) are accounted as
> > > protocol overhead and, (2) control packets are accounted multiple times
> > > (each time a layer is sending the packet "downwards" in the stack.)
> > 
> > 
> > > 
> > > -- 
> > > 
> > > -------------------------------------------
> > >   Thomas Heide Clausen
> > >   Civilingeniør i Datateknik (cand.polyt)
> > >   M.Sc in Computer Engineering
> > > 
> > >   E-Mail: T.Clausen@computer.org
> > >   WWW:    http://www.cs.auc.dk/~voop
> > > -------------------------------------------
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 
> ------- End of Forwarded Message
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

-- 

-------------------------------------------
  Thomas Heide Clausen
  Civilingeniør i Datateknik (cand.polyt)
  M.Sc in Computer Engineering

  E-Mail: T.Clausen@computer.org
  WWW:    http://www.cs.auc.dk/~voop
-------------------------------------------


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



From manet-admin@ietf.org  Fri Mar 15 11:00:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02456
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 11:00:26 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA02002;
	Fri, 15 Mar 2002 10:44:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01970
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 10:44:18 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01935
	for <manet@ietf.org>; Fri, 15 Mar 2002 10:44:15 -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 KAA20284;
	Fri, 15 Mar 2002 10:43:36 -0500 (EST)
Message-Id: <5.0.1.4.2.20020315104139.034804c0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Fri, 15 Mar 2002 10:53:42 -0500
To: Laurent.Viennot@inria.fr
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: [manet] OLSR questions 
Cc: manet@ietf.org
In-Reply-To: <15505.49887.435301.842784@impression.inria.fr>
References: <200203141640.IAA20006@pit.erg.sri.com>
 <200203132245.OAA18566@pit.erg.sri.com>
 <200203141640.IAA20006@pit.erg.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

At 10:46 AM 3/15/2002 +0100, Laurent Viennot wrote:
>Richard,
>
>The problem with advertising RIDs in Hello is that it is not
>sufficient for detecting uni-directional links in some weird
>situations with wireless connections.
>
>Suppose for example the following scenario :
>
>        ______________            _____________
>       |              |     /--= |I1           |
>       | Main ->   J1 |=<--/   = |I2   <- Main |
>       |              |  \__-->= |I3           |
>        --------------            -------------
>
>There are two unidirectional links between I and J: one from interface
>J1 to I3 and the other from interface I1 to J1.
>
>If J1 anounces "I hear node I" then the node I thinks it has a
>bi-directional link between I3 and J1 which is false.
>To deal with such weird cases, J1 has to announce "I hear I1" as
>proposed in MESH.

True, you lose the bidirectionality test for the separate interfaces and this is outlined in RFC 2328 also.


>Such a situation may occur with directional antennas for example. With
>IEEE 802.11, nodes I and J cannot communicate since ACKs for unicast
>transmissions will always be lost.

Right, if one wanted to support unidirectionality per interface, interface type is an issue.


>I agree this could be optimized for IPv6 support.

o.k., that seems important as the design progresses and was worth pointing out.


>laurent
>
>ogier@erg.sri.com writes:
> > 
> > TBRPF has other features that are shared by OSPF but not by OLSR
> > (in addition to sending each HELLO on a single interface). For example, 
> > neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
> > Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs, 
> > not neighbor interfaces. This greatly improves efficiency for IPv6, 
> > since RIDs remain at 32 bits in OSPF for IPv6.
> > 
> > Richard
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet



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


From daemon@optimus.ietf.org  Fri Mar 15 11:00:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02466
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 11:00:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA03549
	for manet-archive@odin.ietf.org; Fri, 15 Mar 2002 11:00:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA02002;
	Fri, 15 Mar 2002 10:44:21 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA01970
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 10:44:18 -0500 (EST)
Received: from itd.nrl.navy.mil (s2.itd.nrl.navy.mil [132.250.83.3])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01935
	for <manet@ietf.org>; Fri, 15 Mar 2002 10:44:15 -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 KAA20284;
	Fri, 15 Mar 2002 10:43:36 -0500 (EST)
Message-Id: <5.0.1.4.2.20020315104139.034804c0@pop.itd.nrl.navy.mil>
X-Sender: macker@pop.itd.nrl.navy.mil
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Fri, 15 Mar 2002 10:53:42 -0500
To: Laurent.Viennot@inria.fr
From: Joe Macker <macker@itd.nrl.navy.mil>
Subject: Re: [manet] OLSR questions 
Cc: manet@ietf.org
In-Reply-To: <15505.49887.435301.842784@impression.inria.fr>
References: <200203141640.IAA20006@pit.erg.sri.com>
 <200203132245.OAA18566@pit.erg.sri.com>
 <200203141640.IAA20006@pit.erg.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

At 10:46 AM 3/15/2002 +0100, Laurent Viennot wrote:
>Richard,
>
>The problem with advertising RIDs in Hello is that it is not
>sufficient for detecting uni-directional links in some weird
>situations with wireless connections.
>
>Suppose for example the following scenario :
>
>        ______________            _____________
>       |              |     /--= |I1           |
>       | Main ->   J1 |=<--/   = |I2   <- Main |
>       |              |  \__-->= |I3           |
>        --------------            -------------
>
>There are two unidirectional links between I and J: one from interface
>J1 to I3 and the other from interface I1 to J1.
>
>If J1 anounces "I hear node I" then the node I thinks it has a
>bi-directional link between I3 and J1 which is false.
>To deal with such weird cases, J1 has to announce "I hear I1" as
>proposed in MESH.

True, you lose the bidirectionality test for the separate interfaces and this is outlined in RFC 2328 also.


>Such a situation may occur with directional antennas for example. With
>IEEE 802.11, nodes I and J cannot communicate since ACKs for unicast
>transmissions will always be lost.

Right, if one wanted to support unidirectionality per interface, interface type is an issue.


>I agree this could be optimized for IPv6 support.

o.k., that seems important as the design progresses and was worth pointing out.


>laurent
>
>ogier@erg.sri.com writes:
> > 
> > TBRPF has other features that are shared by OSPF but not by OLSR
> > (in addition to sending each HELLO on a single interface). For example, 
> > neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
> > Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs, 
> > not neighbor interfaces. This greatly improves efficiency for IPv6, 
> > since RIDs remain at 32 bits in OSPF for IPv6.
> > 
> > Richard
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet



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



From manet-admin@ietf.org  Fri Mar 15 11:00:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02484
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 11:00:36 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00142;
	Fri, 15 Mar 2002 10:27:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00113
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 10:27:19 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01483
	for <manet@ietf.org>; Fri, 15 Mar 2002 10:27:16 -0500 (EST)
Received: from zephyrin (zephyrin-wi.inria.fr [193.51.192.58])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2FFRIv27539
	for <manet@ietf.org>; Fri, 15 Mar 2002 16:27:18 +0100 (MET)
Message-ID: <00f601c1cc38$a674ec80$3ac033c1@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203141640.IAA20006@pit.erg.sri.com>
Subject: Re: [manet] OLSR questions 
Date: Fri, 15 Mar 2002 16:47:02 +0100
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Richard,

OSPF has good things and some other things that need adaptation to MANET.
Among the good things I think there are the sequence numbers that allow
obsolete informations to be removed from databases. Something worrying with
the absence of sequence numbers in TBRPF is that some obsolete information
could circulate around the network endlessly when there is mobility (not
covered by your proof).  Below is a short example of what I mean

u
|
|
v
|
|
w
|\
| \
i--j

Links i--w and j--w are alternatively alive: when link i--w is alive, link
j--w is down and vice-versa. To simplify let us assume that this switch
occur after each full update from w.

Link u--v definitively breaks when i--w is alive and let's assume that none
among i and j receive the differential update.

As you suggested, link u--v remains in TG(i) a few seconds - even if it is
not reported by w. Link u--v is thus updated in TG(j) by i, since p(u)=i at
that time for j. Then, i receives the update of w (and removes u--v) but
link i--w breaks and j--w comes up before any update from j.

Then j--w is active and link u--v is still reported by j. Now u--v is
updated in TG(i) since reported by j=p(u) for i. Again, suppose j receives
the update of w (and removes u--v) but link j--w breaks and i--w comes up
before any update from i.

The false information about the validity of the link of u--v thus endlessly
circulates between i and j.

I don't claim that this is an actual counter-example to your protocol
functionning because I don't master very well your optimizations (such as
the use of NON_TREE_PENALTY, and other penalties, etc), but I do believe
that without sequence numbers it will imply a non trivial proof of
correctness.

Philippe

----- Original Message -----
From: <ogier@erg.sri.com>
To: Joe Macker <macker@itd.nrl.navy.mil>; <manet@ietf.org>
Cc: <ogier@erg.sri.com>
Sent: Thursday, March 14, 2002 5:40 PM
Subject: Re: [manet] OLSR questions


>
> TBRPF has other features that are shared by OSPF but not by OLSR
> (in addition to sending each HELLO on a single interface). For example,
> neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
> Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs,
> not neighbor interfaces. This greatly improves efficiency for IPv6,
> since RIDs remain at 32 bits in OSPF for IPv6.
>
> Richard
>



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


From daemon@optimus.ietf.org  Fri Mar 15 11:56:32 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02493
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 11:00:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA03630
	for manet-archive@odin.ietf.org; Fri, 15 Mar 2002 11:00:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00142;
	Fri, 15 Mar 2002 10:27:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA00113
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 10:27:19 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01483
	for <manet@ietf.org>; Fri, 15 Mar 2002 10:27:16 -0500 (EST)
Received: from zephyrin (zephyrin-wi.inria.fr [193.51.192.58])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2FFRIv27539
	for <manet@ietf.org>; Fri, 15 Mar 2002 16:27:18 +0100 (MET)
Message-ID: <00f601c1cc38$a674ec80$3ac033c1@inria.fr>
From: "Philippe Jacquet" <philippe.jacquet@inria.fr>
To: <manet@ietf.org>
References: <200203141640.IAA20006@pit.erg.sri.com>
Subject: Re: [manet] OLSR questions 
Date: Fri, 15 Mar 2002 16:47:02 +0100
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.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Richard,

OSPF has good things and some other things that need adaptation to MANET.
Among the good things I think there are the sequence numbers that allow
obsolete informations to be removed from databases. Something worrying with
the absence of sequence numbers in TBRPF is that some obsolete information
could circulate around the network endlessly when there is mobility (not
covered by your proof).  Below is a short example of what I mean

u
|
|
v
|
|
w
|\
| \
i--j

Links i--w and j--w are alternatively alive: when link i--w is alive, link
j--w is down and vice-versa. To simplify let us assume that this switch
occur after each full update from w.

Link u--v definitively breaks when i--w is alive and let's assume that none
among i and j receive the differential update.

As you suggested, link u--v remains in TG(i) a few seconds - even if it is
not reported by w. Link u--v is thus updated in TG(j) by i, since p(u)=i at
that time for j. Then, i receives the update of w (and removes u--v) but
link i--w breaks and j--w comes up before any update from j.

Then j--w is active and link u--v is still reported by j. Now u--v is
updated in TG(i) since reported by j=p(u) for i. Again, suppose j receives
the update of w (and removes u--v) but link j--w breaks and i--w comes up
before any update from i.

The false information about the validity of the link of u--v thus endlessly
circulates between i and j.

I don't claim that this is an actual counter-example to your protocol
functionning because I don't master very well your optimizations (such as
the use of NON_TREE_PENALTY, and other penalties, etc), but I do believe
that without sequence numbers it will imply a non trivial proof of
correctness.

Philippe

----- Original Message -----
From: <ogier@erg.sri.com>
To: Joe Macker <macker@itd.nrl.navy.mil>; <manet@ietf.org>
Cc: <ogier@erg.sri.com>
Sent: Thursday, March 14, 2002 5:40 PM
Subject: Re: [manet] OLSR questions


>
> TBRPF has other features that are shared by OSPF but not by OLSR
> (in addition to sending each HELLO on a single interface). For example,
> neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
> Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs,
> not neighbor interfaces. This greatly improves efficiency for IPv6,
> since RIDs remain at 32 bits in OSPF for IPv6.
>
> Richard
>



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



From manet-admin@ietf.org  Fri Mar 15 16:21:46 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10720
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 16:21:46 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24986;
	Fri, 15 Mar 2002 15:53:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24955
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 15:53:52 -0500 (EST)
Received: from smtp.web.de (smtp02.web.de [217.72.192.151])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10077
	for <manet@ietf.org>; Fri, 15 Mar 2002 15:53:47 -0500 (EST)
Received: from [217.83.9.92] (helo=navayo)
	by smtp.web.de with esmtp (WEB.DE(Exim) 4.41 #2)
	id 16lyhS-0001on-00
	for manet@ietf.org; Fri, 15 Mar 2002 21:53:19 +0100
Content-Type: text/plain;
  charset="us-ascii"
From: Frank Dinies <FrankDinies@web.de>
To: manet@ietf.org
Date: Fri, 15 Mar 2002 21:54:34 +0100
X-Mailer: KMail [version 1.3.9]
MIME-Version: 1.0
Message-Id: <200203152154.34956.FrankDinies@web.de>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA24956
Subject: [manet] Fisheye State Routing
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

I have some questions about the Fisheye State Routing Algorithm in respect to 
the current draft version:

- I think the "last heard time" variable in the topology table is never used 
in current protocol operations  ! Maybe for further extensions ??

-  Nodes, once registered in the Topolgy table will never removed, i.e. if a 
node disappears, the node will not taken into account for further 
computations of the routing table, because the node was removed from the 
neighbour list. But nevertheless its entry will not be removed in the 
topology table.

Regards

Frank Dinies    

 

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


From daemon@optimus.ietf.org  Fri Mar 15 16:21:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10730
	for <manet-archive@odin.ietf.org>; Fri, 15 Mar 2002 16:21:46 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA26804
	for manet-archive@odin.ietf.org; Fri, 15 Mar 2002 16:21:50 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24986;
	Fri, 15 Mar 2002 15:53:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA24955
	for <manet@optimus.ietf.org>; Fri, 15 Mar 2002 15:53:52 -0500 (EST)
Received: from smtp.web.de (smtp02.web.de [217.72.192.151])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10077
	for <manet@ietf.org>; Fri, 15 Mar 2002 15:53:47 -0500 (EST)
Received: from [217.83.9.92] (helo=navayo)
	by smtp.web.de with esmtp (WEB.DE(Exim) 4.41 #2)
	id 16lyhS-0001on-00
	for manet@ietf.org; Fri, 15 Mar 2002 21:53:19 +0100
Content-Type: text/plain;
  charset="us-ascii"
From: Frank Dinies <FrankDinies@web.de>
To: manet@ietf.org
Date: Fri, 15 Mar 2002 21:54:34 +0100
X-Mailer: KMail [version 1.3.9]
MIME-Version: 1.0
Message-Id: <200203152154.34956.FrankDinies@web.de>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id PAA24956
Subject: [manet] Fisheye State Routing
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

I have some questions about the Fisheye State Routing Algorithm in respect to 
the current draft version:

- I think the "last heard time" variable in the topology table is never used 
in current protocol operations  ! Maybe for further extensions ??

-  Nodes, once registered in the Topolgy table will never removed, i.e. if a 
node disappears, the node will not taken into account for further 
computations of the routing table, because the node was removed from the 
neighbour list. But nevertheless its entry will not be removed in the 
topology table.

Regards

Frank Dinies    

 

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



From manet-admin@ietf.org  Sat Mar 16 11:00:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05226
	for <manet-archive@odin.ietf.org>; Sat, 16 Mar 2002 11:00:23 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19532;
	Sat, 16 Mar 2002 10:08:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19504
	for <manet@optimus.ietf.org>; Sat, 16 Mar 2002 10:08:09 -0500 (EST)
Received: from mail.flarion.com (mail.flarion.com [63.103.94.23])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04567
	for <manet@ietf.org>; Sat, 16 Mar 2002 10:08:04 -0500 (EST)
Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2653.19)
	id <G8RA91VH>; Sat, 16 Mar 2002 10:07:36 -0500
Message-ID: <8C92E23A3E87FB479988285F9E22BE4699431E@ftmail>
From: Scott Corson <Corson@flarion.com>
To: "'Jorge Nuevo'" <nuevo@inrs-telecom.uquebec.ca>, manet@ietf.org
Subject: RE: [manet] Question about dependency of unicast protocols by mul
	ticast protocols
Date: Sat, 16 Mar 2002 10:07:33 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Two more protocols:

DDM is unicast-independent
http://www.ieee-infocom.org/2001/paper/278.ps

LAM is unicast-dependent (on TORA)
http://www-users.cs.umn.edu/~hngo/WirelessNetworking/LAM.pdf

-Scott

> -----Original Message-----
> From: Jorge Nuevo [mailto:nuevo@inrs-telecom.uquebec.ca]
> Sent: Thursday, March 14, 2002 3:12 PM
> To: manet@ietf.org
> Subject: [manet] Question about dependency of unicast protocols by
> multicast protocols
> 
> 
> Hello,
> 
> I am trying to find out which of the multicast protocols for
> ad hoc networks are unicast protocols dependent. The following
> would be unicast dependent:
> MAODV, AMRoute, CAMP
> 
> and non-dependent would be: AMRIS, ODMRP and MCEDAR,
> 
> but I am not sure about FGMP (Forwarding Group Multicast Protocol),
> ABAM (Associativity Based Multicast) and
> ADMR (Adaptive Demand-driven Multicast Routing).
> 
> Could any one help me with this doubt?
> 
> thanks 
> 
> Jorge Nuevo
> nuevo@inrs-telecom.uquebec.ca
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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


From daemon@optimus.ietf.org  Sat Mar 16 11:56:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05236
	for <manet-archive@odin.ietf.org>; Sat, 16 Mar 2002 11:00:24 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id LAA22206
	for manet-archive@odin.ietf.org; Sat, 16 Mar 2002 11:00:27 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19532;
	Sat, 16 Mar 2002 10:08:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA19504
	for <manet@optimus.ietf.org>; Sat, 16 Mar 2002 10:08:09 -0500 (EST)
Received: from mail.flarion.com (mail.flarion.com [63.103.94.23])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04567
	for <manet@ietf.org>; Sat, 16 Mar 2002 10:08:04 -0500 (EST)
Received: by rrmail01.lab.flarion.com with Internet Mail Service (5.5.2653.19)
	id <G8RA91VH>; Sat, 16 Mar 2002 10:07:36 -0500
Message-ID: <8C92E23A3E87FB479988285F9E22BE4699431E@ftmail>
From: Scott Corson <Corson@flarion.com>
To: "'Jorge Nuevo'" <nuevo@inrs-telecom.uquebec.ca>, manet@ietf.org
Subject: RE: [manet] Question about dependency of unicast protocols by mul
	ticast protocols
Date: Sat, 16 Mar 2002 10:07:33 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Two more protocols:

DDM is unicast-independent
http://www.ieee-infocom.org/2001/paper/278.ps

LAM is unicast-dependent (on TORA)
http://www-users.cs.umn.edu/~hngo/WirelessNetworking/LAM.pdf

-Scott

> -----Original Message-----
> From: Jorge Nuevo [mailto:nuevo@inrs-telecom.uquebec.ca]
> Sent: Thursday, March 14, 2002 3:12 PM
> To: manet@ietf.org
> Subject: [manet] Question about dependency of unicast protocols by
> multicast protocols
> 
> 
> Hello,
> 
> I am trying to find out which of the multicast protocols for
> ad hoc networks are unicast protocols dependent. The following
> would be unicast dependent:
> MAODV, AMRoute, CAMP
> 
> and non-dependent would be: AMRIS, ODMRP and MCEDAR,
> 
> but I am not sure about FGMP (Forwarding Group Multicast Protocol),
> ABAM (Associativity Based Multicast) and
> ADMR (Adaptive Demand-driven Multicast Routing).
> 
> Could any one help me with this doubt?
> 
> thanks 
> 
> Jorge Nuevo
> nuevo@inrs-telecom.uquebec.ca
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

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



From manet-admin@ietf.org  Sat Mar 16 14:24:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08285
	for <manet-archive@odin.ietf.org>; Sat, 16 Mar 2002 14:24:24 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA28505;
	Sat, 16 Mar 2002 13:18:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA28472
	for <manet@optimus.ietf.org>; Sat, 16 Mar 2002 13:18:37 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07226
	for <manet@ietf.org>; Sat, 16 Mar 2002 13:18:34 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id KAA24525;
	Sat, 16 Mar 2002 10:16:47 -0800 (PST)
Message-Id: <200203161816.KAA24525@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Fri, 15 Mar 2002 16:47:02 +0100."
             <00f601c1cc38$a674ec80$3ac033c1@inria.fr> 
Date: Sat, 16 Mar 2002 10:16:46 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Philippe,

The example you gave assumes that links go up and down in 
synchrony with the transmission of topology update messages.
This would require an intelligent jammer who knows how the
protocol works and can tell when a node transmits a topology
update despite random jitter.

Under these assumptions, OLSR cannot be proven to be correct either,
as the example below shows.  If we wanted to resist such intelligent
jamming attacks (for either OLSR or TBRPF), other techniques can be 
used so that an adversary cannot observe when a node is transmitting 
topology updates.

Nonetheless, your example is interesting and shows that you understand
TBRPF very well.  I think that reading the correctness proof helps to 
understand TBRPF and shows that it is not so complex after all.  

The main reason for avoiding sequence numbers in TBRPF is to reduce
overhead.  Although sequence numbers are a very small percentage of 
overhead in OSPF, they would be a much larger percentage in TBRPF
because each node reports much less information. 
(However, it would not be hard to incorporate sequence numbers if 
they were found to be beneficial.)

You mentioned that mobility is not covered by my proof, which is not 
correct.  Mobility is allowed, but the proof assumes that the protocol 
is given sufficient time to converge following the last topology change.
(After all, we cannot expect all nodes to have the correct paths
immediately following a topology change.)

Richard


Example for OLSR:

x 
| \
|  \
v   w
|   |
|   |
i   j
|  /
| /
u

Links (v,i) and (w,j) are alternately alive: when link (v,i) is alive,
link (w,j) is down and vice versa.  Node v always generates a TC message 
reporting link (v,x) while (v,i) is down, and node w always generates
a TC message reporting link (w,x) while (w,j) is down.
As a result, node u never discovers a path to x, even though 
such a path always exists.


> Richard,
> 
> OSPF has good things and some other things that need adaptation to MANET.
> Among the good things I think there are the sequence numbers that allow
> obsolete informations to be removed from databases. Something worrying with
> the absence of sequence numbers in TBRPF is that some obsolete information
> could circulate around the network endlessly when there is mobility (not
> covered by your proof).  Below is a short example of what I mean
> 
> u
> |
> |
> v
> |
> |
> w
> |\
> | \
> i--j
> 
> Links i--w and j--w are alternatively alive: when link i--w is alive, link
> j--w is down and vice-versa. To simplify let us assume that this switch
> occur after each full update from w.
> 
> Link u--v definitively breaks when i--w is alive and let's assume that none
> among i and j receive the differential update.
> 
> As you suggested, link u--v remains in TG(i) a few seconds - even if it is
> not reported by w. Link u--v is thus updated in TG(j) by i, since p(u)=i at
> that time for j. Then, i receives the update of w (and removes u--v) but
> link i--w breaks and j--w comes up before any update from j.
> 
> Then j--w is active and link u--v is still reported by j. Now u--v is
> updated in TG(i) since reported by j=p(u) for i. Again, suppose j receives
> the update of w (and removes u--v) but link j--w breaks and i--w comes up
> before any update from i.
> 
> The false information about the validity of the link of u--v thus endlessly
> circulates between i and j.
> 
> I don't claim that this is an actual counter-example to your protocol
> functionning because I don't master very well your optimizations (such as
> the use of NON_TREE_PENALTY, and other penalties, etc), but I do believe
> that without sequence numbers it will imply a non trivial proof of
> correctness.
> 
> Philippe
> 
> ----- Original Message -----
> From: <ogier@erg.sri.com>
> To: Joe Macker <macker@itd.nrl.navy.mil>; <manet@ietf.org>
> Cc: <ogier@erg.sri.com>
> Sent: Thursday, March 14, 2002 5:40 PM
> Subject: Re: [manet] OLSR questions
> 
> 
> >
> > TBRPF has other features that are shared by OSPF but not by OLSR
> > (in addition to sending each HELLO on a single interface). For example,
> > neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
> > Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs,
> > not neighbor interfaces. This greatly improves efficiency for IPv6,
> > since RIDs remain at 32 bits in OSPF for IPv6.
> >
> > Richard
> >
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Sat Mar 16 14:24:25 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08295
	for <manet-archive@odin.ietf.org>; Sat, 16 Mar 2002 14:24:25 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id OAA01456
	for manet-archive@odin.ietf.org; Sat, 16 Mar 2002 14:24:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA28505;
	Sat, 16 Mar 2002 13:18:40 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA28472
	for <manet@optimus.ietf.org>; Sat, 16 Mar 2002 13:18:37 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07226
	for <manet@ietf.org>; Sat, 16 Mar 2002 13:18:34 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id KAA24525;
	Sat, 16 Mar 2002 10:16:47 -0800 (PST)
Message-Id: <200203161816.KAA24525@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Fri, 15 Mar 2002 16:47:02 +0100."
             <00f601c1cc38$a674ec80$3ac033c1@inria.fr> 
Date: Sat, 16 Mar 2002 10:16:46 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Philippe,

The example you gave assumes that links go up and down in 
synchrony with the transmission of topology update messages.
This would require an intelligent jammer who knows how the
protocol works and can tell when a node transmits a topology
update despite random jitter.

Under these assumptions, OLSR cannot be proven to be correct either,
as the example below shows.  If we wanted to resist such intelligent
jamming attacks (for either OLSR or TBRPF), other techniques can be 
used so that an adversary cannot observe when a node is transmitting 
topology updates.

Nonetheless, your example is interesting and shows that you understand
TBRPF very well.  I think that reading the correctness proof helps to 
understand TBRPF and shows that it is not so complex after all.  

The main reason for avoiding sequence numbers in TBRPF is to reduce
overhead.  Although sequence numbers are a very small percentage of 
overhead in OSPF, they would be a much larger percentage in TBRPF
because each node reports much less information. 
(However, it would not be hard to incorporate sequence numbers if 
they were found to be beneficial.)

You mentioned that mobility is not covered by my proof, which is not 
correct.  Mobility is allowed, but the proof assumes that the protocol 
is given sufficient time to converge following the last topology change.
(After all, we cannot expect all nodes to have the correct paths
immediately following a topology change.)

Richard


Example for OLSR:

x 
| \
|  \
v   w
|   |
|   |
i   j
|  /
| /
u

Links (v,i) and (w,j) are alternately alive: when link (v,i) is alive,
link (w,j) is down and vice versa.  Node v always generates a TC message 
reporting link (v,x) while (v,i) is down, and node w always generates
a TC message reporting link (w,x) while (w,j) is down.
As a result, node u never discovers a path to x, even though 
such a path always exists.


> Richard,
> 
> OSPF has good things and some other things that need adaptation to MANET.
> Among the good things I think there are the sequence numbers that allow
> obsolete informations to be removed from databases. Something worrying with
> the absence of sequence numbers in TBRPF is that some obsolete information
> could circulate around the network endlessly when there is mobility (not
> covered by your proof).  Below is a short example of what I mean
> 
> u
> |
> |
> v
> |
> |
> w
> |\
> | \
> i--j
> 
> Links i--w and j--w are alternatively alive: when link i--w is alive, link
> j--w is down and vice-versa. To simplify let us assume that this switch
> occur after each full update from w.
> 
> Link u--v definitively breaks when i--w is alive and let's assume that none
> among i and j receive the differential update.
> 
> As you suggested, link u--v remains in TG(i) a few seconds - even if it is
> not reported by w. Link u--v is thus updated in TG(j) by i, since p(u)=i at
> that time for j. Then, i receives the update of w (and removes u--v) but
> link i--w breaks and j--w comes up before any update from j.
> 
> Then j--w is active and link u--v is still reported by j. Now u--v is
> updated in TG(i) since reported by j=p(u) for i. Again, suppose j receives
> the update of w (and removes u--v) but link j--w breaks and i--w comes up
> before any update from i.
> 
> The false information about the validity of the link of u--v thus endlessly
> circulates between i and j.
> 
> I don't claim that this is an actual counter-example to your protocol
> functionning because I don't master very well your optimizations (such as
> the use of NON_TREE_PENALTY, and other penalties, etc), but I do believe
> that without sequence numbers it will imply a non trivial proof of
> correctness.
> 
> Philippe
> 
> ----- Original Message -----
> From: <ogier@erg.sri.com>
> To: Joe Macker <macker@itd.nrl.navy.mil>; <manet@ietf.org>
> Cc: <ogier@erg.sri.com>
> Sent: Thursday, March 14, 2002 5:40 PM
> Subject: Re: [manet] OLSR questions
> 
> 
> >
> > TBRPF has other features that are shared by OSPF but not by OLSR
> > (in addition to sending each HELLO on a single interface). For example,
> > neither TBRPF nor OSPF use HELLOs to discover 2-hop neighbors.
> > Also, both TBRPF and OSPF include only neighbor RIDs in HELLOs,
> > not neighbor interfaces. This greatly improves efficiency for IPv6,
> > since RIDs remain at 32 bits in OSPF for IPv6.
> >
> > Richard
> >
> 
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Sat Mar 16 21:52:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15819
	for <manet-archive@odin.ietf.org>; Sat, 16 Mar 2002 21:52:50 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA17231;
	Sat, 16 Mar 2002 21:13:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA17202
	for <manet@optimus.ietf.org>; Sat, 16 Mar 2002 21:13:49 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14114
	for <manet@ietf.org>; Sat, 16 Mar 2002 21:13:40 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id SAA25230;
	Sat, 16 Mar 2002 18:11:25 -0800 (PST)
Message-Id: <200203170211.SAA25230@pit.erg.sri.com>
To: T.Clausen@computer.org
cc: ogier@erg.sri.com, manet@ietf.org
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
In-reply-to: Your message of "Fri, 15 Mar 2002 12:59:58 +0100."
             <Pine.LNX.4.21.0203151259200.730-100000@armada> 
Date: Sat, 16 Mar 2002 18:11:25 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Thomas,

You wrote:

> > > > I am basically looking for an explanation on why we have such different
> > > > results.

I am also trying to find such an explanation.  I hope that you will
cooperate with me in this effort.

I thoroughly checked to make sure that I am extracting information correctly 
from the ns2 trace files, and I assume you have also.
Also, I am using exactly the OLSR code from your website (with the previously
mentioned bug fix).

The next logical step is to make sure we are using exactly the same scenario 
models.  I ran the experiment I mentioned (without mobility) 
again with a different randomly generated topology, and got approximately 
the same results for overhead and delivery percentage.

(Interestingly, without the bug fix, I *did* get a routing load that
is roughly half as much, and a delivery rate near 92%, but I assume
you have fixed the bug.)

Just because you are using the parameters I specified does not imply
that we are using the same model for cbr traffic.  For example, we could 
be using different methods for selecting the source-destination pairs 
(e.g., the 20 sources are fixed in my simulations),
or we could be starting the cbr traffic at different times,
or maybe one of us made an error in generating the scenario.
Or maybe we are defining the mobile node differently, e.g., using
different MAC parameters.

So as a start, if you will not run the cbr and scenario scripts that
I sent you, please send me one cbr and scenario script that you ran
so that I can run it for comparison.  

In any case, even if we are not using exactly the same scenario models,
I am using the same scenario for the different protocols,
so it is still a fair comparison.

Also, you are welcome to obtain TBRPF source code and run your own
comparisons.  We have already released the code to about 20 people,
including someone from INRIA.

Richard



> Dear Richard,
> 
> I've been running 30 different scenarios, all corresponding to the
> parameters you specify and at all data rates between 1 and 10. Over
> those simulations, I consistently find that, at the sample point of 6 pps,
> the routing load is roughly half that of the simulations you present.
> Interrestingly enough, I also get a higher delivery rate: above 90%,
> rather than the (roughly) 85% you present.
> 
> --thomas
> 
> On Wed, 13 Mar 2002 ogier@erg.sri.com wrote:
> 
> > 
> > Thomas,
> > 
> > I checked very thoroughly to make sure we are extracting
> > information correctly from the ns2 trace files, and we are
> > definitely doing this correctly (as you described).
> > 
> > I am very curious to know why our simulations differ from yours.
> > Maybe we are not even running the same scenario, which is why
> > I sent you our cbr and scenario script files last Friday.
> > Did you run that scenario yet?  If so, did you get results
> > that are similar to ours?
> > 
> > Richard
> > 
> > 
> > ------- Forwarded Message
> > 
> > Message-Id: <200203090101.RAA10048@pit.erg.sri.com>
> > To: t.clausen@computer.org, manet@ietf.org
> > cc: ogier@erg.sri.com
> > Reply-To: ogier@erg.sri.com
> > From: ogier@erg.sri.com
> > Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
> > In-reply-to: Your message of "Fri, 08 Mar 2002 08:09:06 PST."
> >              <200203081609.IAA08495@pit.erg.sri.com> 
> > Date: Fri, 08 Mar 2002 17:01:20 -0800
> > Sender: manet-admin@ietf.org
> > Errors-To: manet-admin@ietf.org
> > X-Mailman-Version: 1.0
> > Precedence: bulk
> > List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
> > X-BeenThere: manet@ietf.org
> > Content-Type: text
> > Content-Length: 7048
> > 
> > 
> > Thomas,
> > 
> > So that we can determine why our results differ, I will
> > provide additional details and scripts, so that you can run
> > the same experiment I ran.  I will give you the cbr 
> > and scenario scripts in a separate email.
> > 
> > I will refer to the case with 100 nodes, 20 sources, 670x670 area, 
> > no mobility, and a packet rate of 6 packets/second/source.  
> > Each stream begins at a random time between 10 and 40 seconds, and 
> > changes its destination to a randomly selected node every 30 seconds. 
> > The size of each data packet is 512 bytes. 
> > The total number of packets generated in 500 sec is 57261,
> > which is slightly less than 60000 = 6 * 20 * 500.
> > Is this similar to what you ran?
> > 
> > Richard
> > 
> > 
> > > Thomas,
> > > 
> > > > The way in which I extract overhead information from the ns2 tracefiles is
> > > > to look at all "send" events on the "MAC" layer from the agent
> > > > "OLSR". This should yield both the number of packets being transmitted as
> > > > well as the number of bytes, actually reaching the MAC layer and not
> > > > being dropped somewhere else.
> > > > 
> > > > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > > > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > > > was possible to end up with overhead figures very close those that you
> > > > cite. I do believe, though, that this is a wrong way of accounting, since
> > > > (1) control packets, dropped in the protocol stack (and thus not
> > > > contributing to diffusion of topology information) are accounted as
> > > > protocol overhead and, (2) control packets are accounted multiple times
> > > > (each time a layer is sending the packet "downwards" in the stack.)
> > > 
> > > We counted packets exactly the same way you did, i.e., 
> > > only at the MAC layer.  
> > > 
> > > To double check, I did the following:
> > > 
> > > grep "s " out.tr | grep MAC | grep OLSR   
> > > 
> > > and got exactly the same number of OLSR packets
> > > as our perl script did.
> > > 
> > > I did this for the following case:
> > > 100 nodes, 670x670 area, no mobility, 20 sources, packet rate = 6
> > > For 500 seconds, there were 154744 OLSR packets totaling 20684584, 
> > > so the average size of an OLSR packet (including the IP and MAC 
> > > headers) is 133 bytes. 
> > > 
> > > I also would like to find out why our results differ.
> > > If you have any more ideas, please let me know.
> > > 
> > > Regarding the 90-120% increase of overhead for the bug fix, 
> > > that was for 100 nodes.  I later tried 50 nodes and found
> > > the increase to be roughly 75-90%.
> > > 
> > > Richard
> > > 
> > > 
> > > > Richard,
> > > > 
> > > > I suspect serious problems with your control overhead measures. Please see
> > > > below.
> > > > 
> > > > On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:
> > > > 
> > > > > 
> > > > > Thomas,
> > > > > 
> > > > > > Richard,
> > > > > > 
> > > > > > I am not quite sure what to make from your simulations. It seems to me
> > > > > > that they are from a network in overload condition - in which case buff
> > er
> > > > > > management has a critical impact on performance. We've been simulating
> > > > > > OLSR in conditions, similar to those you've been showing, and our resul
> > ts
> > > > > > differ significantly. We experience that a large abmount of (data and
> > > > > > control) traffic in these situations are rejected from the various
> > > > > > buffers.
> > > > > 
> > > > 
> > > > <SNIP> 
> > > > 
> > > > > To ensure that the protocols were compared on a fair basis,
> > > > > since AODV and TBRPF gave control traffic higher priority than
> > > > > data traffic, we did the same for OLSR.  It has long been considered
> > > > > a good idea to give control traffic higher priority.  This could 
> > > > > explain why your results differ from mine.
> > > > > You can do this simply by adding the line
> > > > >                 case PT_OLSR:
> > > > > to the function PriQueue::recv() in priqueue.cc.
> > > > > 
> > > > > > Also, I notice that we obtain much less overhead for OLSR when counting
> > > > > > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > > > > > detailed information (e.g. physical overhead etc.) ?
> > > > > 
> > > > > No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> > > > > at the MAC layer.  
> > > > > 
> > > > 
> > > > <SNIP> 
> > > > 
> > > > I've tried to reproduce your published results for OLSR, using a large set
> > > > of scenario files, corresponding to the parameters you've used.
> > > > 
> > > > Unfortunately I fail to achieve the same results as those you present
> > > > (both with and without control traffic priority): in particulary in the
> > > > overload condition (packet rate of 6-8 packets/second) I find the overhead
> > > > of OLSR to be significantly lower (up to 25-30%) than what your
> > > > simulations show.
> > > > 
> > > > Also, as we were discussing in another mail, my simulations showed that
> > > > the "control packet size" bug resulted in approximately 50% more overhead,
> > > > whereas you cited your simulations as showing in the orders of 90-120%
> > > > more overhead. I have not had success in reproducing the 90-120% figures 
> > > > either.
> > > > 
> > > > I am basically looking for an explanation on why we have such different
> > > > results.
> > > > 
> > > > I am well aware that a paticulary "bad" or "good" choise of scenario (even
> > > > corresponding to the same general parameters such as mobility and traffic
> > > > patterns) may trigger particulary good or bad results, so I've run a
> > > > number of different scenarios through, all with roughly the same results.
> > > > This left me wondering if our different results were just a matter of
> > > > computing the overhead differently?
> > > > 
> > > > The way in which I extract overhead information from the ns2 tracefiles is
> > > > to look at all "send" events on the "MAC" layer from the agent
> > > > "OLSR". This should yield both the number of packets being transmitted as
> > > > well as the number of bytes, actually reaching the MAC layer and not
> > > > being dropped somewhere else.
> > > > 
> > > > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > > > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > > > was possible to end up with overhead figures very close those that you
> > > > cite. I do believe, though, that this is a wrong way of accounting, since
> > > > (1) control packets, dropped in the protocol stack (and thus not
> > > > contributing to diffusion of topology information) are accounted as
> > > > protocol overhead and, (2) control packets are accounted multiple times
> > > > (each time a layer is sending the packet "downwards" in the stack.)
> > > 
> > > 
> > > > 
> > > > -- 
> > > > 
> > > > -------------------------------------------
> > > >   Thomas Heide Clausen
> > > >   Civilingeniør i Datateknik (cand.polyt)
> > > >   M.Sc in Computer Engineering
> > > > 
> > > >   E-Mail: T.Clausen@computer.org
> > > >   WWW:    http://www.cs.auc.dk/~voop
> > > > -------------------------------------------
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > manet mailing list
> > > > manet@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/manet
> > > 
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> > 
> > ------- End of Forwarded Message
> > 
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> > 
> 
> -- 
> 
> -------------------------------------------
>   Thomas Heide Clausen
>   Civilingeniør i Datateknik (cand.polyt)
>   M.Sc in Computer Engineering
> 
>   E-Mail: T.Clausen@computer.org
>   WWW:    http://www.cs.auc.dk/~voop
> -------------------------------------------
> 

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


From daemon@optimus.ietf.org  Sat Mar 16 21:52:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15829
	for <manet-archive@odin.ietf.org>; Sat, 16 Mar 2002 21:52:50 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id VAA19095
	for manet-archive@odin.ietf.org; Sat, 16 Mar 2002 21:52:54 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA17231;
	Sat, 16 Mar 2002 21:13:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA17202
	for <manet@optimus.ietf.org>; Sat, 16 Mar 2002 21:13:49 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14114
	for <manet@ietf.org>; Sat, 16 Mar 2002 21:13:40 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id SAA25230;
	Sat, 16 Mar 2002 18:11:25 -0800 (PST)
Message-Id: <200203170211.SAA25230@pit.erg.sri.com>
To: T.Clausen@computer.org
cc: ogier@erg.sri.com, manet@ietf.org
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
In-reply-to: Your message of "Fri, 15 Mar 2002 12:59:58 +0100."
             <Pine.LNX.4.21.0203151259200.730-100000@armada> 
Date: Sat, 16 Mar 2002 18:11:25 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Thomas,

You wrote:

> > > > I am basically looking for an explanation on why we have such different
> > > > results.

I am also trying to find such an explanation.  I hope that you will
cooperate with me in this effort.

I thoroughly checked to make sure that I am extracting information correctly 
from the ns2 trace files, and I assume you have also.
Also, I am using exactly the OLSR code from your website (with the previously
mentioned bug fix).

The next logical step is to make sure we are using exactly the same scenario 
models.  I ran the experiment I mentioned (without mobility) 
again with a different randomly generated topology, and got approximately 
the same results for overhead and delivery percentage.

(Interestingly, without the bug fix, I *did* get a routing load that
is roughly half as much, and a delivery rate near 92%, but I assume
you have fixed the bug.)

Just because you are using the parameters I specified does not imply
that we are using the same model for cbr traffic.  For example, we could 
be using different methods for selecting the source-destination pairs 
(e.g., the 20 sources are fixed in my simulations),
or we could be starting the cbr traffic at different times,
or maybe one of us made an error in generating the scenario.
Or maybe we are defining the mobile node differently, e.g., using
different MAC parameters.

So as a start, if you will not run the cbr and scenario scripts that
I sent you, please send me one cbr and scenario script that you ran
so that I can run it for comparison.  

In any case, even if we are not using exactly the same scenario models,
I am using the same scenario for the different protocols,
so it is still a fair comparison.

Also, you are welcome to obtain TBRPF source code and run your own
comparisons.  We have already released the code to about 20 people,
including someone from INRIA.

Richard



> Dear Richard,
> 
> I've been running 30 different scenarios, all corresponding to the
> parameters you specify and at all data rates between 1 and 10. Over
> those simulations, I consistently find that, at the sample point of 6 pps,
> the routing load is roughly half that of the simulations you present.
> Interrestingly enough, I also get a higher delivery rate: above 90%,
> rather than the (roughly) 85% you present.
> 
> --thomas
> 
> On Wed, 13 Mar 2002 ogier@erg.sri.com wrote:
> 
> > 
> > Thomas,
> > 
> > I checked very thoroughly to make sure we are extracting
> > information correctly from the ns2 trace files, and we are
> > definitely doing this correctly (as you described).
> > 
> > I am very curious to know why our simulations differ from yours.
> > Maybe we are not even running the same scenario, which is why
> > I sent you our cbr and scenario script files last Friday.
> > Did you run that scenario yet?  If so, did you get results
> > that are similar to ours?
> > 
> > Richard
> > 
> > 
> > ------- Forwarded Message
> > 
> > Message-Id: <200203090101.RAA10048@pit.erg.sri.com>
> > To: t.clausen@computer.org, manet@ietf.org
> > cc: ogier@erg.sri.com
> > Reply-To: ogier@erg.sri.com
> > From: ogier@erg.sri.com
> > Subject: Re: [manet] Re: performance comparaison between Ad Hoc routing protocols 
> > In-reply-to: Your message of "Fri, 08 Mar 2002 08:09:06 PST."
> >              <200203081609.IAA08495@pit.erg.sri.com> 
> > Date: Fri, 08 Mar 2002 17:01:20 -0800
> > Sender: manet-admin@ietf.org
> > Errors-To: manet-admin@ietf.org
> > X-Mailman-Version: 1.0
> > Precedence: bulk
> > List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
> > X-BeenThere: manet@ietf.org
> > Content-Type: text
> > Content-Length: 7048
> > 
> > 
> > Thomas,
> > 
> > So that we can determine why our results differ, I will
> > provide additional details and scripts, so that you can run
> > the same experiment I ran.  I will give you the cbr 
> > and scenario scripts in a separate email.
> > 
> > I will refer to the case with 100 nodes, 20 sources, 670x670 area, 
> > no mobility, and a packet rate of 6 packets/second/source.  
> > Each stream begins at a random time between 10 and 40 seconds, and 
> > changes its destination to a randomly selected node every 30 seconds. 
> > The size of each data packet is 512 bytes. 
> > The total number of packets generated in 500 sec is 57261,
> > which is slightly less than 60000 = 6 * 20 * 500.
> > Is this similar to what you ran?
> > 
> > Richard
> > 
> > 
> > > Thomas,
> > > 
> > > > The way in which I extract overhead information from the ns2 tracefiles is
> > > > to look at all "send" events on the "MAC" layer from the agent
> > > > "OLSR". This should yield both the number of packets being transmitted as
> > > > well as the number of bytes, actually reaching the MAC layer and not
> > > > being dropped somewhere else.
> > > > 
> > > > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > > > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > > > was possible to end up with overhead figures very close those that you
> > > > cite. I do believe, though, that this is a wrong way of accounting, since
> > > > (1) control packets, dropped in the protocol stack (and thus not
> > > > contributing to diffusion of topology information) are accounted as
> > > > protocol overhead and, (2) control packets are accounted multiple times
> > > > (each time a layer is sending the packet "downwards" in the stack.)
> > > 
> > > We counted packets exactly the same way you did, i.e., 
> > > only at the MAC layer.  
> > > 
> > > To double check, I did the following:
> > > 
> > > grep "s " out.tr | grep MAC | grep OLSR   
> > > 
> > > and got exactly the same number of OLSR packets
> > > as our perl script did.
> > > 
> > > I did this for the following case:
> > > 100 nodes, 670x670 area, no mobility, 20 sources, packet rate = 6
> > > For 500 seconds, there were 154744 OLSR packets totaling 20684584, 
> > > so the average size of an OLSR packet (including the IP and MAC 
> > > headers) is 133 bytes. 
> > > 
> > > I also would like to find out why our results differ.
> > > If you have any more ideas, please let me know.
> > > 
> > > Regarding the 90-120% increase of overhead for the bug fix, 
> > > that was for 100 nodes.  I later tried 50 nodes and found
> > > the increase to be roughly 75-90%.
> > > 
> > > Richard
> > > 
> > > 
> > > > Richard,
> > > > 
> > > > I suspect serious problems with your control overhead measures. Please see
> > > > below.
> > > > 
> > > > On Wed, 20 Feb 2002 ogier@erg.sri.com wrote:
> > > > 
> > > > > 
> > > > > Thomas,
> > > > > 
> > > > > > Richard,
> > > > > > 
> > > > > > I am not quite sure what to make from your simulations. It seems to me
> > > > > > that they are from a network in overload condition - in which case buff
> > er
> > > > > > management has a critical impact on performance. We've been simulating
> > > > > > OLSR in conditions, similar to those you've been showing, and our resul
> > ts
> > > > > > differ significantly. We experience that a large abmount of (data and
> > > > > > control) traffic in these situations are rejected from the various
> > > > > > buffers.
> > > > > 
> > > > 
> > > > <SNIP> 
> > > > 
> > > > > To ensure that the protocols were compared on a fair basis,
> > > > > since AODV and TBRPF gave control traffic higher priority than
> > > > > data traffic, we did the same for OLSR.  It has long been considered
> > > > > a good idea to give control traffic higher priority.  This could 
> > > > > explain why your results differ from mine.
> > > > > You can do this simply by adding the line
> > > > >                 case PT_OLSR:
> > > > > to the function PriQueue::recv() in priqueue.cc.
> > > > > 
> > > > > > Also, I notice that we obtain much less overhead for OLSR when counting
> > > > > > MAC/IP overhead. Have you alterated the ns2 code to make it output more
> > > > > > detailed information (e.g. physical overhead etc.) ?
> > > > > 
> > > > > No we did not.  In addition to the 20-byte IP header, ns2 adds 52 bytes 
> > > > > at the MAC layer.  
> > > > > 
> > > > 
> > > > <SNIP> 
> > > > 
> > > > I've tried to reproduce your published results for OLSR, using a large set
> > > > of scenario files, corresponding to the parameters you've used.
> > > > 
> > > > Unfortunately I fail to achieve the same results as those you present
> > > > (both with and without control traffic priority): in particulary in the
> > > > overload condition (packet rate of 6-8 packets/second) I find the overhead
> > > > of OLSR to be significantly lower (up to 25-30%) than what your
> > > > simulations show.
> > > > 
> > > > Also, as we were discussing in another mail, my simulations showed that
> > > > the "control packet size" bug resulted in approximately 50% more overhead,
> > > > whereas you cited your simulations as showing in the orders of 90-120%
> > > > more overhead. I have not had success in reproducing the 90-120% figures 
> > > > either.
> > > > 
> > > > I am basically looking for an explanation on why we have such different
> > > > results.
> > > > 
> > > > I am well aware that a paticulary "bad" or "good" choise of scenario (even
> > > > corresponding to the same general parameters such as mobility and traffic
> > > > patterns) may trigger particulary good or bad results, so I've run a
> > > > number of different scenarios through, all with roughly the same results.
> > > > This left me wondering if our different results were just a matter of
> > > > computing the overhead differently?
> > > > 
> > > > The way in which I extract overhead information from the ns2 tracefiles is
> > > > to look at all "send" events on the "MAC" layer from the agent
> > > > "OLSR". This should yield both the number of packets being transmitted as
> > > > well as the number of bytes, actually reaching the MAC layer and not
> > > > being dropped somewhere else.
> > > > 
> > > > However, when I tried to disregard the layer (MAC, RTR, AGT etc), and just
> > > > look at all the lines in the tracefile wish an "s" event from "OLSR", it
> > > > was possible to end up with overhead figures very close those that you
> > > > cite. I do believe, though, that this is a wrong way of accounting, since
> > > > (1) control packets, dropped in the protocol stack (and thus not
> > > > contributing to diffusion of topology information) are accounted as
> > > > protocol overhead and, (2) control packets are accounted multiple times
> > > > (each time a layer is sending the packet "downwards" in the stack.)
> > > 
> > > 
> > > > 
> > > > -- 
> > > > 
> > > > -------------------------------------------
> > > >   Thomas Heide Clausen
> > > >   Civilingeniør i Datateknik (cand.polyt)
> > > >   M.Sc in Computer Engineering
> > > > 
> > > >   E-Mail: T.Clausen@computer.org
> > > >   WWW:    http://www.cs.auc.dk/~voop
> > > > -------------------------------------------
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > 
> > > > _______________________________________________
> > > > manet mailing list
> > > > manet@ietf.org
> > > > https://www1.ietf.org/mailman/listinfo/manet
> > > 
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> > 
> > ------- End of Forwarded Message
> > 
> > 
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> > 
> 
> -- 
> 
> -------------------------------------------
>   Thomas Heide Clausen
>   Civilingeniør i Datateknik (cand.polyt)
>   M.Sc in Computer Engineering
> 
>   E-Mail: T.Clausen@computer.org
>   WWW:    http://www.cs.auc.dk/~voop
> -------------------------------------------
> 

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



From manet-admin@ietf.org  Sat Mar 16 22:07:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15957
	for <manet-archive@odin.ietf.org>; Sat, 16 Mar 2002 22:07:20 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA17500;
	Sat, 16 Mar 2002 21:17:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA17471
	for <manet@optimus.ietf.org>; Sat, 16 Mar 2002 21:17:44 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14236
	for <manet@ietf.org>; Sat, 16 Mar 2002 21:17:40 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id SAA25274;
	Sat, 16 Mar 2002 18:15:38 -0800 (PST)
Message-Id: <200203170215.SAA25274@pit.erg.sri.com>
To: Laurent.Viennot@inria.fr
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Fri, 15 Mar 2002 10:46:07 +0100."
             <15505.49887.435301.842784@impression.inria.fr> 
Date: Sat, 16 Mar 2002 18:15:38 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Laurent,

> Richard,
> 
> The problem with advertising RIDs in Hello is that it is not
> sufficient for detecting uni-directional links in some weird
> situations with wireless connections.
> 
> Suppose for example the following scenario :
> 
>         ______________            _____________
>        |              |     /--= |I1           |
>        | Main ->   J1 |=<--/   = |I2   <- Main |
>        |              |  \__-->= |I3           |
>         --------------            -------------
> 
> There are two unidirectional links between I and J: one from interface
> J1 to I3 and the other from interface I1 to J1.

OK. If this is a realistic scenario, then including neighbor interface
addresses instead of RIDs in HELLOs makes sense.  Another approach
that allows more efficient operation in IPv6 is to include, for
each neighbor, a 32-bit RID *and* Interface ID (which can be 8 bits).
Perhaps the latter should be done *only* for IPv6.

Since OSPF includes only RIDs in HELLOs, and not neighbor interface 
addresses (or neighbor interface IDs), OSPF would also have to be 
modified to do this.

Including neighbor interface addresses instead of RIDs in HELLOs is just 
a simple substitution in TBRPF and does not affect parent selection,
since topology updates will still contain RIDs.  Each HELLO would still
be sent on a single interface.  

Richard



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


From daemon@optimus.ietf.org  Sat Mar 16 22:07:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15967
	for <manet-archive@odin.ietf.org>; Sat, 16 Mar 2002 22:07:20 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA19870
	for manet-archive@odin.ietf.org; Sat, 16 Mar 2002 22:07:24 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA17500;
	Sat, 16 Mar 2002 21:17:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA17471
	for <manet@optimus.ietf.org>; Sat, 16 Mar 2002 21:17:44 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14236
	for <manet@ietf.org>; Sat, 16 Mar 2002 21:17:40 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id SAA25274;
	Sat, 16 Mar 2002 18:15:38 -0800 (PST)
Message-Id: <200203170215.SAA25274@pit.erg.sri.com>
To: Laurent.Viennot@inria.fr
cc: manet@ietf.org, ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] OLSR questions 
In-reply-to: Your message of "Fri, 15 Mar 2002 10:46:07 +0100."
             <15505.49887.435301.842784@impression.inria.fr> 
Date: Sat, 16 Mar 2002 18:15:38 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Laurent,

> Richard,
> 
> The problem with advertising RIDs in Hello is that it is not
> sufficient for detecting uni-directional links in some weird
> situations with wireless connections.
> 
> Suppose for example the following scenario :
> 
>         ______________            _____________
>        |              |     /--= |I1           |
>        | Main ->   J1 |=<--/   = |I2   <- Main |
>        |              |  \__-->= |I3           |
>         --------------            -------------
> 
> There are two unidirectional links between I and J: one from interface
> J1 to I3 and the other from interface I1 to J1.

OK. If this is a realistic scenario, then including neighbor interface
addresses instead of RIDs in HELLOs makes sense.  Another approach
that allows more efficient operation in IPv6 is to include, for
each neighbor, a 32-bit RID *and* Interface ID (which can be 8 bits).
Perhaps the latter should be done *only* for IPv6.

Since OSPF includes only RIDs in HELLOs, and not neighbor interface 
addresses (or neighbor interface IDs), OSPF would also have to be 
modified to do this.

Including neighbor interface addresses instead of RIDs in HELLOs is just 
a simple substitution in TBRPF and does not affect parent selection,
since topology updates will still contain RIDs.  Each HELLO would still
be sent on a single interface.  

Richard



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



From manet-admin@ietf.org  Sun Mar 17 10:24:35 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02525
	for <manet-archive@odin.ietf.org>; Sun, 17 Mar 2002 10:24:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23615;
	Sun, 17 Mar 2002 10:02:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23584
	for <manet@optimus.ietf.org>; Sun, 17 Mar 2002 10:02:36 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01999
	for <manet@ietf.org>; Sun, 17 Mar 2002 10:02:33 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id HAA26132;
	Sun, 17 Mar 2002 07:00:49 -0800 (PST)
Message-Id: <200203171500.HAA26132@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: Manet flooding / broadcasting.... 
In-reply-to: Your message of "Fri, 15 Mar 2002 11:09:03 +0100."
             <15505.51263.987571.258275@impression.inria.fr> 
Date: Sun, 17 Mar 2002 07:00:49 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Laurent,

> 
> Richard,
> 
> I do not understand why you think I have avoided your arguments. I
> have just tried to promote link hysteresis advanced functioning
> because it allows to detect neighbor changes quicker than 2-hop
> neighbor changes. Adding REFRESH_INTERVAL is just a matter of allowing
> this with basic neighbor sensing functioning.

OK, I will be specific.
In your message dated 1/31/02 you said "Your point is doing 1 and 3 at 
a higher rate than 4", where you gave the following list:
 - 1 - detecting new neighbors
 - 2 - checking bi-directionality of links
 - 3 - detecting link breakage
 - 4 - advertising list of neighbors

No, that was not my point.  My point was more specific, that in 
OLSR (version 05) each neighbor had to be reported in a HELLO at least 
once per HELLO_INTERVAL.  (HELLO_INTERVAL has special meaning because 
making it larger can increase the time required to detect a LOST 
neighbor if link-layer notification is not used, with or without 
hysteresis.)  At that time, you and Philippe did not agree that any 
change to OLSR was needed.  Now, in OLSR version 06, each neighbor is 
no longer required to be reported every HELLO_INTERVAL, but every 
REFRESH_INTERVAL, a new parameter. This directly addresses my main 
point.  I am simply stating facts.  

> It seems you misunderstand the introduction of REFRESH_PERIOD. The
> general idea behind OLSR is to allow a certain tunability. We want to
> leave enough freedom to implementors so that they can optimize their
> code for their specific needs. For example, depending on the link
> layer performances you may implement the protocol in different ways.

I understand your new parameter perfectly.  Another posssible 
reason for allowing tunability is because you are not sure what
is the best value for the new parameter and need to conduct
simulations.  In TBRPF, we have already determined that each neighbor
should be reported once per PER_UPDATE_INTERVAL, so we do not
need another parameter, thus simplifying the protocol.

Richard

> 
> laurent
> 
> 
> 
> ogier@erg.sri.com writes:
>  > 
>  > Philippe,
>  > 
>  > It is interesting to consider the discussion I had with
>  > you in January regarding HELLOs (see below), in light of 
>  > your new parameter REFRESH_INTERVAL.  For example, you said
>  > "you only need to refresh al neighbors within a certain
>  > period".  At that time, the refresh period was HELLO_INTERVAL,
>  > since you did not yet introduce REFRESH_INTERVAL.
>  > I was wondering why you said "a certain period" instead
>  > of HELLO_INTERVAL, and now I know why.
>  > 
>  > This was the main point on which I never agreed with Laurent,
>  > and I gave up arguing with him because he avoided my main
>  > point that in OLSR (version 05) every neighbor must be reported 
>  > in a HELLO every HELLO_INTERVAL. 
>  > 
>  > Instead of agreeing with me that something needed to be changed,
>  > you pretended that no change was needed, and then later 
>  > introduced the new parameter REFRESH_INTERVAL, which would have
>  > addressed my concern.
>  > 
>  > Adding this new parameter allows OLSR to perform neighbor sensing 
>  > similar to TBRPF, but it also adds complexity to OLSR.
>  > In my opinion, TBRPF is designed better than OLSR in many ways,
>  > and you are having to patch OLSR (thus making it more complex)
>  > in order to compete with TBRPF.  Maybe next you will find a way
>  > to make (1-hop) neighbor discovery modular, or introduce 
>  > differential TC messages.
>  > 
>  > Richard
>  > 
>  > 
>  > > > ----- Original Message -----
>  > > > From: <ogier@erg.sri.com>
>  > > > To: <manet@itd.nrl.navy.mil>
>  > > > Cc: <ogier@erg.sri.com>
>  > > > Sent: Tuesday, January 29, 2002 8:58 PM
>  > > > Subject: Re: Manet flooding / broadcasting....
>  > > >
>  > > >
>  > > > >
>  > > > > Since HELLOs are differential in TBRPF, this can be done with a
>  > > > > relatively small increase in overhead.  However, in OSPF and OLSR,
>  > > > > since each HELLO contains all neighbor IDs, this would increase
>  > > > > overhead a lot if each node has a large number of neighbors.
>  > > > >
>  > > > Richard, again, OLSR HELLOs can be partial, you only need to refresh a
ll
>  > > > neighbors within a certain period, and you can increase the hello rate
 for
>  > > > fast moving node. I think Laurent mentioned this to you before.
>  > > 
>  > > Philippe,
>  > > 
>  > > Yes, I know that HELLOs can be partial and that each neighbor must be 
>  > > included in at least one HELLO every HELLO interval, but unless there 
>  > > are too many neighbor IDs to fit into one packet, normally OLSR uses one
 
>  > > full HELLO per HELLO interval.  (Just check the source code.)
>  > > 
>  > > But this does not affect my argument.  What I am saying is that OLSR 
>  > > must include each neighbor in a HELLO every HELLO_INTERVAL, whereas 
>  > > TBRPF includes each neighbor only in periodic topology updates, which ar
e 
>  > > less frequent (e.g., 10 times less frequent if the HELLO_INTERVAL is 0.5
 s 
>  > > and the update period is 5 s).
>  > > 
>  > > It is the HELLO_INTERVAL that determines how quickly a failed link is 
>  > > detected, e.g., if no HELLO is received within 3 * HELLO_INTERVAL, then 
>  > > the neighbor is declared to be lost.
>  > > 
>  > > I also know that OLSR can use differential HELLOs,
>  > > since it has recently added the LOST_LINK status (which TBRPF has
>  > > had since version 01).  *But this does not change the requirement that 
>  > > in OLSR each neighbor ID must be included in at least one HELLO every 
>  > > HELLO_INTERVAL.*  You can increase HELLO_INTERVAL, but then it
>  > > would take longer to detect a lost neighbor.  OLSR could be *modified* 
>  > > so that each neighbor ID is reported less frequently than HELLO_INTERVAL
>  > > (as in TBRPF), but I am not sure how this would affect MPR computation.
>  > > 
>  > > However don't forget that even the overhead of an empty HELLO can be non
 
>  > > > negligible.  In IEEE 802.11 the MAC-PHY overhead is around 192 usec (w
ith 
>  > > > option to 92 usec) which at 11 Mbps corresponds to approximately 60 IP
v4 
>  > > > addresses.
>  > > 
>  > > Yes, this is a good point.  With the 92 usec option, this becomes about 
30 
>  > > IPv4 addresses (or router IDs).  So if a node has 30 neighbors, then a f
ull 
>  > > HELLO is about twice as big as an empty HELLO.  I think that's significa
nt.
>  > > 
>  > > There are lots of differences between TBRPF and OLSR that can affect
>  > > performance, and we have already discussed many of these.
>  > > But it is difficult to predict how these differences affect performance.
>  > > That's what simulations are for.
>  > > 
>  > > Regards,
>  > > Richard
>  > > 
>  > 
>  > _______________________________________________
>  > manet mailing list
>  > manet@ietf.org
>  > https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Sun Mar 17 10:24:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02535
	for <manet-archive@odin.ietf.org>; Sun, 17 Mar 2002 10:24:35 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA24416
	for manet-archive@odin.ietf.org; Sun, 17 Mar 2002 10:24:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23615;
	Sun, 17 Mar 2002 10:02:39 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA23584
	for <manet@optimus.ietf.org>; Sun, 17 Mar 2002 10:02:36 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01999
	for <manet@ietf.org>; Sun, 17 Mar 2002 10:02:33 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id HAA26132;
	Sun, 17 Mar 2002 07:00:49 -0800 (PST)
Message-Id: <200203171500.HAA26132@pit.erg.sri.com>
To: manet@ietf.org
cc: ogier@erg.sri.com
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] Re: Manet flooding / broadcasting.... 
In-reply-to: Your message of "Fri, 15 Mar 2002 11:09:03 +0100."
             <15505.51263.987571.258275@impression.inria.fr> 
Date: Sun, 17 Mar 2002 07:00:49 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Laurent,

> 
> Richard,
> 
> I do not understand why you think I have avoided your arguments. I
> have just tried to promote link hysteresis advanced functioning
> because it allows to detect neighbor changes quicker than 2-hop
> neighbor changes. Adding REFRESH_INTERVAL is just a matter of allowing
> this with basic neighbor sensing functioning.

OK, I will be specific.
In your message dated 1/31/02 you said "Your point is doing 1 and 3 at 
a higher rate than 4", where you gave the following list:
 - 1 - detecting new neighbors
 - 2 - checking bi-directionality of links
 - 3 - detecting link breakage
 - 4 - advertising list of neighbors

No, that was not my point.  My point was more specific, that in 
OLSR (version 05) each neighbor had to be reported in a HELLO at least 
once per HELLO_INTERVAL.  (HELLO_INTERVAL has special meaning because 
making it larger can increase the time required to detect a LOST 
neighbor if link-layer notification is not used, with or without 
hysteresis.)  At that time, you and Philippe did not agree that any 
change to OLSR was needed.  Now, in OLSR version 06, each neighbor is 
no longer required to be reported every HELLO_INTERVAL, but every 
REFRESH_INTERVAL, a new parameter. This directly addresses my main 
point.  I am simply stating facts.  

> It seems you misunderstand the introduction of REFRESH_PERIOD. The
> general idea behind OLSR is to allow a certain tunability. We want to
> leave enough freedom to implementors so that they can optimize their
> code for their specific needs. For example, depending on the link
> layer performances you may implement the protocol in different ways.

I understand your new parameter perfectly.  Another posssible 
reason for allowing tunability is because you are not sure what
is the best value for the new parameter and need to conduct
simulations.  In TBRPF, we have already determined that each neighbor
should be reported once per PER_UPDATE_INTERVAL, so we do not
need another parameter, thus simplifying the protocol.

Richard

> 
> laurent
> 
> 
> 
> ogier@erg.sri.com writes:
>  > 
>  > Philippe,
>  > 
>  > It is interesting to consider the discussion I had with
>  > you in January regarding HELLOs (see below), in light of 
>  > your new parameter REFRESH_INTERVAL.  For example, you said
>  > "you only need to refresh al neighbors within a certain
>  > period".  At that time, the refresh period was HELLO_INTERVAL,
>  > since you did not yet introduce REFRESH_INTERVAL.
>  > I was wondering why you said "a certain period" instead
>  > of HELLO_INTERVAL, and now I know why.
>  > 
>  > This was the main point on which I never agreed with Laurent,
>  > and I gave up arguing with him because he avoided my main
>  > point that in OLSR (version 05) every neighbor must be reported 
>  > in a HELLO every HELLO_INTERVAL. 
>  > 
>  > Instead of agreeing with me that something needed to be changed,
>  > you pretended that no change was needed, and then later 
>  > introduced the new parameter REFRESH_INTERVAL, which would have
>  > addressed my concern.
>  > 
>  > Adding this new parameter allows OLSR to perform neighbor sensing 
>  > similar to TBRPF, but it also adds complexity to OLSR.
>  > In my opinion, TBRPF is designed better than OLSR in many ways,
>  > and you are having to patch OLSR (thus making it more complex)
>  > in order to compete with TBRPF.  Maybe next you will find a way
>  > to make (1-hop) neighbor discovery modular, or introduce 
>  > differential TC messages.
>  > 
>  > Richard
>  > 
>  > 
>  > > > ----- Original Message -----
>  > > > From: <ogier@erg.sri.com>
>  > > > To: <manet@itd.nrl.navy.mil>
>  > > > Cc: <ogier@erg.sri.com>
>  > > > Sent: Tuesday, January 29, 2002 8:58 PM
>  > > > Subject: Re: Manet flooding / broadcasting....
>  > > >
>  > > >
>  > > > >
>  > > > > Since HELLOs are differential in TBRPF, this can be done with a
>  > > > > relatively small increase in overhead.  However, in OSPF and OLSR,
>  > > > > since each HELLO contains all neighbor IDs, this would increase
>  > > > > overhead a lot if each node has a large number of neighbors.
>  > > > >
>  > > > Richard, again, OLSR HELLOs can be partial, you only need to refresh a
ll
>  > > > neighbors within a certain period, and you can increase the hello rate
 for
>  > > > fast moving node. I think Laurent mentioned this to you before.
>  > > 
>  > > Philippe,
>  > > 
>  > > Yes, I know that HELLOs can be partial and that each neighbor must be 
>  > > included in at least one HELLO every HELLO interval, but unless there 
>  > > are too many neighbor IDs to fit into one packet, normally OLSR uses one
 
>  > > full HELLO per HELLO interval.  (Just check the source code.)
>  > > 
>  > > But this does not affect my argument.  What I am saying is that OLSR 
>  > > must include each neighbor in a HELLO every HELLO_INTERVAL, whereas 
>  > > TBRPF includes each neighbor only in periodic topology updates, which ar
e 
>  > > less frequent (e.g., 10 times less frequent if the HELLO_INTERVAL is 0.5
 s 
>  > > and the update period is 5 s).
>  > > 
>  > > It is the HELLO_INTERVAL that determines how quickly a failed link is 
>  > > detected, e.g., if no HELLO is received within 3 * HELLO_INTERVAL, then 
>  > > the neighbor is declared to be lost.
>  > > 
>  > > I also know that OLSR can use differential HELLOs,
>  > > since it has recently added the LOST_LINK status (which TBRPF has
>  > > had since version 01).  *But this does not change the requirement that 
>  > > in OLSR each neighbor ID must be included in at least one HELLO every 
>  > > HELLO_INTERVAL.*  You can increase HELLO_INTERVAL, but then it
>  > > would take longer to detect a lost neighbor.  OLSR could be *modified* 
>  > > so that each neighbor ID is reported less frequently than HELLO_INTERVAL
>  > > (as in TBRPF), but I am not sure how this would affect MPR computation.
>  > > 
>  > > However don't forget that even the overhead of an empty HELLO can be non
 
>  > > > negligible.  In IEEE 802.11 the MAC-PHY overhead is around 192 usec (w
ith 
>  > > > option to 92 usec) which at 11 Mbps corresponds to approximately 60 IP
v4 
>  > > > addresses.
>  > > 
>  > > Yes, this is a good point.  With the 92 usec option, this becomes about 
30 
>  > > IPv4 addresses (or router IDs).  So if a node has 30 neighbors, then a f
ull 
>  > > HELLO is about twice as big as an empty HELLO.  I think that's significa
nt.
>  > > 
>  > > There are lots of differences between TBRPF and OLSR that can affect
>  > > performance, and we have already discussed many of these.
>  > > But it is difficult to predict how these differences affect performance.
>  > > That's what simulations are for.
>  > > 
>  > > Regards,
>  > > Richard
>  > > 
>  > 
>  > _______________________________________________
>  > manet mailing list
>  > manet@ietf.org
>  > https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Sun Mar 17 15:13:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09655
	for <manet-archive@odin.ietf.org>; Sun, 17 Mar 2002 15:13:42 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05938;
	Sun, 17 Mar 2002 14:44:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05912
	for <manet@optimus.ietf.org>; Sun, 17 Mar 2002 14:44:14 -0500 (EST)
Received: from ux3.sp.cs.cmu.edu (UX3.SP.CS.CMU.EDU [128.2.198.103])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA09031
	for <manet@ietf.org>; Sun, 17 Mar 2002 14:44:11 -0500 (EST)
Received: from ux3.sp.cs.cmu.edu ([127.0.0.1]) by ux3.sp.cs.cmu.edu id aa18696;
          17 Mar 2002 14:44 EST
Date: Sun, 17 Mar 2002 14:43:58 -0500 (EST)
From: Jorjeta Gueorguieva Jetcheva <jorjeta+@cs.cmu.edu>
X-Sender: jorjeta+@ux3.sp.cs.cmu.edu
To: nuevo@inrs-telecom.uquebec.ca, manet@ietf.org
Subject: re: [manet] Question about dependency of unicast protocols by multicast protocols
Message-ID: <Pine.LNX.3.95L.1020317144022.18540A-100000@ux3.sp.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


ADMR, FGMP and ABAM are all unicast-independent. 

Jorjeta

-----Original Message----- From: manet-admin@ietf.org

[mailto:manet-admin@ietf.org]
On Behalf Of Jorge Nuevo 
Sent: Thursday, March 14, 2002 2:12 PM 
To: manet@ietf.org Subject: [manet] Question about dependency of unicast
protocols by multicast protocols

Hello,

I am trying to find out which of the multicast protocols for ad hoc
networks are unicast protocols dependent. The following would be unicast
dependent: MAODV, AMRoute, CAMP

and non-dependent would be: AMRIS, ODMRP and MCEDAR,

but I am not sure about FGMP (Forwarding Group Multicast Protocol), ABAM
(Associativity Based Multicast) and ADMR (Adaptive Demand-driven Multicast
Routing). 

Could any one help me with this doubt? 

thanks

Jorge Nuevo nuevo@inrs-telecom.uquebec.ca

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


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


From daemon@optimus.ietf.org  Sun Mar 17 15:13:42 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09664
	for <manet-archive@odin.ietf.org>; Sun, 17 Mar 2002 15:13:42 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA07526
	for manet-archive@odin.ietf.org; Sun, 17 Mar 2002 15:13:45 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05938;
	Sun, 17 Mar 2002 14:44:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA05912
	for <manet@optimus.ietf.org>; Sun, 17 Mar 2002 14:44:14 -0500 (EST)
Received: from ux3.sp.cs.cmu.edu (UX3.SP.CS.CMU.EDU [128.2.198.103])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA09031
	for <manet@ietf.org>; Sun, 17 Mar 2002 14:44:11 -0500 (EST)
Received: from ux3.sp.cs.cmu.edu ([127.0.0.1]) by ux3.sp.cs.cmu.edu id aa18696;
          17 Mar 2002 14:44 EST
Date: Sun, 17 Mar 2002 14:43:58 -0500 (EST)
From: Jorjeta Gueorguieva Jetcheva <jorjeta+@cs.cmu.edu>
X-Sender: jorjeta+@ux3.sp.cs.cmu.edu
To: nuevo@inrs-telecom.uquebec.ca, manet@ietf.org
Subject: re: [manet] Question about dependency of unicast protocols by multicast protocols
Message-ID: <Pine.LNX.3.95L.1020317144022.18540A-100000@ux3.sp.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


ADMR, FGMP and ABAM are all unicast-independent. 

Jorjeta

-----Original Message----- From: manet-admin@ietf.org

[mailto:manet-admin@ietf.org]
On Behalf Of Jorge Nuevo 
Sent: Thursday, March 14, 2002 2:12 PM 
To: manet@ietf.org Subject: [manet] Question about dependency of unicast
protocols by multicast protocols

Hello,

I am trying to find out which of the multicast protocols for ad hoc
networks are unicast protocols dependent. The following would be unicast
dependent: MAODV, AMRoute, CAMP

and non-dependent would be: AMRIS, ODMRP and MCEDAR,

but I am not sure about FGMP (Forwarding Group Multicast Protocol), ABAM
(Associativity Based Multicast) and ADMR (Adaptive Demand-driven Multicast
Routing). 

Could any one help me with this doubt? 

thanks

Jorge Nuevo nuevo@inrs-telecom.uquebec.ca

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


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



From manet-admin@ietf.org  Mon Mar 18 04:50:33 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01906
	for <manet-archive@odin.ietf.org>; Mon, 18 Mar 2002 04:50:33 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21023;
	Mon, 18 Mar 2002 04:19:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA20993
	for <manet@optimus.ietf.org>; Mon, 18 Mar 2002 04:19:09 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01476
	for <manet@ietf.org>; Mon, 18 Mar 2002 04:19:05 -0500 (EST)
Received: from impression.inria.fr (impression.inria.fr [128.93.17.98])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2I9J3H04576;
	Mon, 18 Mar 2002 10:19:03 +0100 (MET)
Received: by impression.inria.fr (sSMTP sendmail emulation); Mon, 18 Mar 2002 10:19:03 +0100
From: Laurent Viennot <Laurent.Viennot@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15509.45319.113600.897944@impression.inria.fr>
Date: Mon, 18 Mar 2002 10:19:03 +0100
To: iavramop@princeton.edu (Ioannis C Avramopoulos)
Cc: Laurent.Viennot@inria.fr, manet@ietf.org
Subject: Re: [manet] OLSR questions
In-Reply-To: <3C8E6308.701B@mailserver1.Princeton.EDU>
References: <3C8E6308.701B@mailserver1.Princeton.EDU>
X-Mailer: VM 6.92 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Reply-To: Laurent.Viennot@inria.fr
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


Dear Ioannis,

Some clarifications to your second mail... 

laurent


Ioannis C Avramopoulos writes:
 > 
 > Dear Laurent,
 > 
 > thank you for your clarifications. I still have some questions. See below.
 > 
 > Ioannis
 >  
 > >> - What are the advantages of having a LOST_LINK type over having no
 > >>such type (version 4 for example did not have such link type)?
 > 
 > >It allows quicker update of one hop and especially two hop
 > >neighborhood. A node announcing a neighbor loss allows its neighbors
 > >to remove the link (without waiting for expiration) from their 2-hop
 > >neighbor set.
 > 
 > Lets assume that initially nodes A and B have a bidirectional link and at
 > some time the link becomes unidirectional from A to B (A->B). After the
 > timeout of A expires and A has not received any HELLO from B, A may instead
 > of listing B with link type LOST_LINK may not list B at all. We can simply
 > add a rule in B to consider the link with A unidirectional if B is not
 > listed in A's HELLO (instead of considering A as a unidirectional link if B
 > is listed as LOST_LINK) and therefore we don't have to wait for the
 > timeout.

Be carafull, Hellos are partial. This means that not being listed in one
Hello does not mean you won't be listed in another. This means that
the rate of Hellos is independent from how often a neighbor interface
is advertised.

An important reason for using partial Hellos is to avoid splitting
Hello messages in several MAC packets: this would increase the
probability of loosing Hello messages (if one MAC packet is lost, then
the whole message is lost even if you have received parts of it).

 > 
 > Similarly if we have another node C that is a neighbor of A and a 2-hop
 > neighbor of B (C-A-B) when the topology becomes C-A->B if B is not listed
 > in A's HELLO we may simply add a rule in C that purges B from the 2-hop
 > neighborhood.
 > 
 > If the aforementioned rule is added I still don't see why a LOST_LINK type
 > is beneficial.
 > 
 > 
 > >> - Why should a node have multiple interfaces all running the OLSR
 > >>protocol?
 > 
 > >several radio interfaces with directional antennas (and possibly same
 > >radio channel).
 > 
 > >> - Does the IEEE 802.11 specification make any provision for the
 > >>scenario of a node possessing multiple interfaces?
 > 
 > >No. It is in charge of the routing layer.
 > 
 > If you have several interfaces with directional antennas then it is
 > possible that they overlap. Packets that are transmitted over all
 > interfaces simultaneously will collide at nodes that are within the
 > overlap. Since IEEE 802.11 does not arbitrate access to the broadcast
 > channel and it is the responsibility of the routing layer then the routing
 > layer should deal with such cases.

I mean that the network layer is in charge of connectivity between the
interfaces. The IEEE 802.11 specification will treat them as if they
were on different nodes, thus providing some medium access arbitration.

 > 
 > I have one more general remark. I believe that considering multiple
 > interfaces makes the presentation of neighbor sensing not very
 > straightforward (in version 4 for example where multiple interfaces are not
 > considered the presentation is straighforward). Maybe you could consider
 > presenting neighbor sensing separately for the cases of single and multiple
 > interfaces and more clearly state the objectives and assumptions of
 > multiple interfaces. But this is just my opinion...
 > 

You are right, multiple interfaces makes neighbor sensing more complex
but we are writing a specification supporting multiple
interfaces. Some ambiguity could arise in a document that would
present twice neighbor sensing. However, we have tried to introduce
concepts in a pedagogic order for readability but the priority is the
clarity of the specification.  If you want some material about
understanding OLSR design, take a look at
http://hipercom.inria.fr/olsr/

Notice some weird situations that may occur with multiple interfaces
as discussed in other mails on the list.

If you still have questions, we are pleased to answer them.

laurent


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


From daemon@optimus.ietf.org  Mon Mar 18 04:50:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01917
	for <manet-archive@odin.ietf.org>; Mon, 18 Mar 2002 04:50:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA22967
	for manet-archive@odin.ietf.org; Mon, 18 Mar 2002 04:50:37 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA21023;
	Mon, 18 Mar 2002 04:19:12 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA20993
	for <manet@optimus.ietf.org>; Mon, 18 Mar 2002 04:19:09 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01476
	for <manet@ietf.org>; Mon, 18 Mar 2002 04:19:05 -0500 (EST)
Received: from impression.inria.fr (impression.inria.fr [128.93.17.98])
	by concorde.inria.fr (8.11.1/8.11.1) with SMTP id g2I9J3H04576;
	Mon, 18 Mar 2002 10:19:03 +0100 (MET)
Received: by impression.inria.fr (sSMTP sendmail emulation); Mon, 18 Mar 2002 10:19:03 +0100
From: Laurent Viennot <Laurent.Viennot@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15509.45319.113600.897944@impression.inria.fr>
Date: Mon, 18 Mar 2002 10:19:03 +0100
To: iavramop@princeton.edu (Ioannis C Avramopoulos)
Cc: Laurent.Viennot@inria.fr, manet@ietf.org
Subject: Re: [manet] OLSR questions
In-Reply-To: <3C8E6308.701B@mailserver1.Princeton.EDU>
References: <3C8E6308.701B@mailserver1.Princeton.EDU>
X-Mailer: VM 6.92 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid
Reply-To: Laurent.Viennot@inria.fr
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit


Dear Ioannis,

Some clarifications to your second mail... 

laurent


Ioannis C Avramopoulos writes:
 > 
 > Dear Laurent,
 > 
 > thank you for your clarifications. I still have some questions. See below.
 > 
 > Ioannis
 >  
 > >> - What are the advantages of having a LOST_LINK type over having no
 > >>such type (version 4 for example did not have such link type)?
 > 
 > >It allows quicker update of one hop and especially two hop
 > >neighborhood. A node announcing a neighbor loss allows its neighbors
 > >to remove the link (without waiting for expiration) from their 2-hop
 > >neighbor set.
 > 
 > Lets assume that initially nodes A and B have a bidirectional link and at
 > some time the link becomes unidirectional from A to B (A->B). After the
 > timeout of A expires and A has not received any HELLO from B, A may instead
 > of listing B with link type LOST_LINK may not list B at all. We can simply
 > add a rule in B to consider the link with A unidirectional if B is not
 > listed in A's HELLO (instead of considering A as a unidirectional link if B
 > is listed as LOST_LINK) and therefore we don't have to wait for the
 > timeout.

Be carafull, Hellos are partial. This means that not being listed in one
Hello does not mean you won't be listed in another. This means that
the rate of Hellos is independent from how often a neighbor interface
is advertised.

An important reason for using partial Hellos is to avoid splitting
Hello messages in several MAC packets: this would increase the
probability of loosing Hello messages (if one MAC packet is lost, then
the whole message is lost even if you have received parts of it).

 > 
 > Similarly if we have another node C that is a neighbor of A and a 2-hop
 > neighbor of B (C-A-B) when the topology becomes C-A->B if B is not listed
 > in A's HELLO we may simply add a rule in C that purges B from the 2-hop
 > neighborhood.
 > 
 > If the aforementioned rule is added I still don't see why a LOST_LINK type
 > is beneficial.
 > 
 > 
 > >> - Why should a node have multiple interfaces all running the OLSR
 > >>protocol?
 > 
 > >several radio interfaces with directional antennas (and possibly same
 > >radio channel).
 > 
 > >> - Does the IEEE 802.11 specification make any provision for the
 > >>scenario of a node possessing multiple interfaces?
 > 
 > >No. It is in charge of the routing layer.
 > 
 > If you have several interfaces with directional antennas then it is
 > possible that they overlap. Packets that are transmitted over all
 > interfaces simultaneously will collide at nodes that are within the
 > overlap. Since IEEE 802.11 does not arbitrate access to the broadcast
 > channel and it is the responsibility of the routing layer then the routing
 > layer should deal with such cases.

I mean that the network layer is in charge of connectivity between the
interfaces. The IEEE 802.11 specification will treat them as if they
were on different nodes, thus providing some medium access arbitration.

 > 
 > I have one more general remark. I believe that considering multiple
 > interfaces makes the presentation of neighbor sensing not very
 > straightforward (in version 4 for example where multiple interfaces are not
 > considered the presentation is straighforward). Maybe you could consider
 > presenting neighbor sensing separately for the cases of single and multiple
 > interfaces and more clearly state the objectives and assumptions of
 > multiple interfaces. But this is just my opinion...
 > 

You are right, multiple interfaces makes neighbor sensing more complex
but we are writing a specification supporting multiple
interfaces. Some ambiguity could arise in a document that would
present twice neighbor sensing. However, we have tried to introduce
concepts in a pedagogic order for readability but the priority is the
clarity of the specification.  If you want some material about
understanding OLSR design, take a look at
http://hipercom.inria.fr/olsr/

Notice some weird situations that may occur with multiple interfaces
as discussed in other mails on the list.

If you still have questions, we are pleased to answer them.

laurent


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



From manet-admin@ietf.org  Mon Mar 18 16:58:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21813
	for <manet-archive@odin.ietf.org>; Mon, 18 Mar 2002 16:58:36 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA07631;
	Mon, 18 Mar 2002 16:24:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA24702
	for <manet@optimus.ietf.org>; Mon, 18 Mar 2002 13:34:39 -0500 (EST)
Received: from letters.cs.ucsb.edu (letters.cs.ucsb.edu [128.111.41.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14630
	for <manet@ietf.org>; Mon, 18 Mar 2002 13:34:35 -0500 (EST)
Received: from blind (blind [128.111.49.140])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.9.3) with ESMTP id g2IIYXJ20523;
	Mon, 18 Mar 2002 10:34:33 -0800 (PST)
Date: Mon, 18 Mar 2002 10:34:33 -0800 (PST)
From: MobiHoc 2002 <mobihoc@cs.ucsb.edu>
X-Sender: mobihoc@blind
To: MobiHoc 2002 <mobihoc@cs.ucsb.edu>
Message-ID: <Pine.GSO.4.21.0203181030590.24477-100000@blind>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] MobiHoc 2002: Call for Participation
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


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

                ANNOUNCEMENT AND CALL FOR PARTICIPATION
                                   
                             MobiHoc 2002
               The Third ACM International Symposium on
                Mobile Ad Hoc Networking and Computing
                                   
                        Lausanne, Switzerland
                           June 9-11, 2002
                                   
              http://www.acm.org/sigmobile/mobihoc/2002/

      Sponsored by ACM SIGMOBILE  http://www.acm.org/sigmobile/


MobiHoc 2002 is the third of a series of annual meetings sponsored by
ACM SIGMOBILE, focusing on the latest research in the rapidly growing
area of mobile ad hoc networking and computing.  The first MobiHoc was
held in 2000 in Boston, Massachusetts, as a workshop affiliated with the
MobiCom conference also sponsored by SIGMOBILE.  Since then, MobiHoc has
become a separate symposium, held in 2001 in Long Beach, California, and
now in 2002 in Lausanne, Switzerland.  Topics of interest include all
areas of mobile and wireless ad hoc networking (above the physical
layer), ad hoc computing, and sensor networks.

PAPERS:

There will be approximately seven technical paper sessions on a wide
range of ad hoc networking topics.  The list of accepted papers can be
found at http://www.acm.org/sigmobile/mobihoc/2002/program.html. Paper
topics include routing, sensor networks, scalability, multicast,
energy consumption, TCP, and priority scheduling.


POSTERS:

There will also be a poster session, describing innovative and recent
research on ad hoc networks.


TUTORIALS:

This year there is a new component to MobiHoc: technical tutorials.
On June 9th there will be two tutorials.  "Design and Modeling of
Medium Access Control Protocols for Wireless Ad Hoc Networks" will be
held in the morning, and "Routing & Multicasting in Ad hoc Networks"
will be held in the afternoon.


HOTEL and REGISTRATION:

Hotel information is currently available on-line, and the symposium
is open for registration.  Register by April 22, 2002 to get the
early registration rates.


IMPORTANT DATES:

Early Registration Deadline:            April 22, 2002
Tutorials:                              June 9, 2002
Conference:                             June 10-11, 2002


FOR MORE INFORMATION:

Please visit the MobiHoc 2002 Home Page at
http://www.acm.org/sigmobile/mobihoc/2002/ or send email to
mobihoc@epfl.ch for any questions or for more information about
the symposium.

ORGANIZING COMMITTEE:

General Chair

  Jean-Pierre Hubaux
  EPFL (CH)
  jean-pierre.hubaux@epfl.ch

Program Co-Chairs

  J.J. Garcia-Luna-Aceves              David B. Johnson
  Univ. California, Santa Cruz (US)    Rice University (US)
  jj@cs.ucsc.edu                       dbj@cs.rice.edu

Tutorials Co-Chairs

  Adam Wolisz                          Mario Gerla
  Technical Univ. of Berlin (DE)       Univ. California, Los Angeles (US)
  wolisz@ee.tu-berlin.de               gerla@cs.ucla.edu

Finance Chair                        Local Arrangements Chair

  Rachid Guerraoui                     Silvia Giordano
  EPFL (CH)                            EPFL (CH)
  rachid.guerraoui@epfl.ch             silvia.giordano@epfl.ch

Publicity Chair                      Publication Chair

  Elizabeth M. Belding-Royer           Robin Kravets
  Univ. Calif., Santa Barbara (US)     Univ. Illinois, Urbana-Champaign (US)
  ebelding@cs.ucsb.edu                 rhk@cs.uiuc.edu
 
Steering Committee

  Andrew T. Campbell                   Charles E. Perkins
  J.J. Garcia-Luna-Aceves              Ram Ramanathan
  Mario Gerla                          Martha Steenstrup
  Joseph P. Macker                     Nitin H. Vaidya

ACM Program Director

  Ginger Ignatoff


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



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


From daemon@ns.ietf.org  Mon Mar 18 16:58:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21825
	for <manet-archive@odin.ietf.org>; Mon, 18 Mar 2002 16:58:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA09972
	for manet-archive@odin.ietf.org; Mon, 18 Mar 2002 16:58:42 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA07631;
	Mon, 18 Mar 2002 16:24:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA24702
	for <manet@optimus.ietf.org>; Mon, 18 Mar 2002 13:34:39 -0500 (EST)
Received: from letters.cs.ucsb.edu (letters.cs.ucsb.edu [128.111.41.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14630
	for <manet@ietf.org>; Mon, 18 Mar 2002 13:34:35 -0500 (EST)
Received: from blind (blind [128.111.49.140])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.9.3) with ESMTP id g2IIYXJ20523;
	Mon, 18 Mar 2002 10:34:33 -0800 (PST)
Date: Mon, 18 Mar 2002 10:34:33 -0800 (PST)
From: MobiHoc 2002 <mobihoc@cs.ucsb.edu>
X-Sender: mobihoc@blind
To: MobiHoc 2002 <mobihoc@cs.ucsb.edu>
Message-ID: <Pine.GSO.4.21.0203181030590.24477-100000@blind>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] MobiHoc 2002: Call for Participation
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


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

                ANNOUNCEMENT AND CALL FOR PARTICIPATION
                                   
                             MobiHoc 2002
               The Third ACM International Symposium on
                Mobile Ad Hoc Networking and Computing
                                   
                        Lausanne, Switzerland
                           June 9-11, 2002
                                   
              http://www.acm.org/sigmobile/mobihoc/2002/

      Sponsored by ACM SIGMOBILE  http://www.acm.org/sigmobile/


MobiHoc 2002 is the third of a series of annual meetings sponsored by
ACM SIGMOBILE, focusing on the latest research in the rapidly growing
area of mobile ad hoc networking and computing.  The first MobiHoc was
held in 2000 in Boston, Massachusetts, as a workshop affiliated with the
MobiCom conference also sponsored by SIGMOBILE.  Since then, MobiHoc has
become a separate symposium, held in 2001 in Long Beach, California, and
now in 2002 in Lausanne, Switzerland.  Topics of interest include all
areas of mobile and wireless ad hoc networking (above the physical
layer), ad hoc computing, and sensor networks.

PAPERS:

There will be approximately seven technical paper sessions on a wide
range of ad hoc networking topics.  The list of accepted papers can be
found at http://www.acm.org/sigmobile/mobihoc/2002/program.html. Paper
topics include routing, sensor networks, scalability, multicast,
energy consumption, TCP, and priority scheduling.


POSTERS:

There will also be a poster session, describing innovative and recent
research on ad hoc networks.


TUTORIALS:

This year there is a new component to MobiHoc: technical tutorials.
On June 9th there will be two tutorials.  "Design and Modeling of
Medium Access Control Protocols for Wireless Ad Hoc Networks" will be
held in the morning, and "Routing & Multicasting in Ad hoc Networks"
will be held in the afternoon.


HOTEL and REGISTRATION:

Hotel information is currently available on-line, and the symposium
is open for registration.  Register by April 22, 2002 to get the
early registration rates.


IMPORTANT DATES:

Early Registration Deadline:            April 22, 2002
Tutorials:                              June 9, 2002
Conference:                             June 10-11, 2002


FOR MORE INFORMATION:

Please visit the MobiHoc 2002 Home Page at
http://www.acm.org/sigmobile/mobihoc/2002/ or send email to
mobihoc@epfl.ch for any questions or for more information about
the symposium.

ORGANIZING COMMITTEE:

General Chair

  Jean-Pierre Hubaux
  EPFL (CH)
  jean-pierre.hubaux@epfl.ch

Program Co-Chairs

  J.J. Garcia-Luna-Aceves              David B. Johnson
  Univ. California, Santa Cruz (US)    Rice University (US)
  jj@cs.ucsc.edu                       dbj@cs.rice.edu

Tutorials Co-Chairs

  Adam Wolisz                          Mario Gerla
  Technical Univ. of Berlin (DE)       Univ. California, Los Angeles (US)
  wolisz@ee.tu-berlin.de               gerla@cs.ucla.edu

Finance Chair                        Local Arrangements Chair

  Rachid Guerraoui                     Silvia Giordano
  EPFL (CH)                            EPFL (CH)
  rachid.guerraoui@epfl.ch             silvia.giordano@epfl.ch

Publicity Chair                      Publication Chair

  Elizabeth M. Belding-Royer           Robin Kravets
  Univ. Calif., Santa Barbara (US)     Univ. Illinois, Urbana-Champaign (US)
  ebelding@cs.ucsb.edu                 rhk@cs.uiuc.edu
 
Steering Committee

  Andrew T. Campbell                   Charles E. Perkins
  J.J. Garcia-Luna-Aceves              Ram Ramanathan
  Mario Gerla                          Martha Steenstrup
  Joseph P. Macker                     Nitin H. Vaidya

ACM Program Director

  Ginger Ignatoff


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



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



From manet-admin@ietf.org  Tue Mar 19 04:08:56 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17871
	for <manet-archive@odin.ietf.org>; Tue, 19 Mar 2002 04:08:56 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA27457;
	Tue, 19 Mar 2002 03:29:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA27427
	for <manet@optimus.ietf.org>; Tue, 19 Mar 2002 03:29:20 -0500 (EST)
Received: from nomark (stn.chonbuk.ac.kr [210.117.172.212])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17340
	for <manet@ietf.org>; Tue, 19 Mar 2002 03:29:17 -0500 (EST)
Received: from nomark ([210.117.172.212]) by nomark with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 19 Mar 2002 17:29:09 +0900
Message-ID: <001101c1cf20$23fa64c0$d4ac75d2@nomark>
From: "Suk Dea Yu" <sdyu@cs.chonbuk.ac.kr>
To: <manet@ietf.org>
Date: Tue, 19 Mar 2002 17:29:09 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C1CF6B.93BD6DC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-OriginalArrivalTime: 19 Mar 2002 08:29:09.0270 (UTC) FILETIME=[23FBEB60:01C1CF20]
Subject: [manet] Why i could not run AODV simulation ???
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C1CF6B.93BD6DC0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

Hi... Everyone..

I will simulate AODV with adaptive route maintenance method.
but i can't simulate Original AODV
Error like below

C:\NetSim\ns-2.1b8a-win\aodv>ns aodv.tcl
invalid command name "Agent/rtProto/AODV"
    while executing
"Agent/rtProto/AODV instproc init args {
        $self next $args
}       "
    (file "aodv.tcl" line 20)

C:\NetSim\ns-2.1b8a-win\aodv>


#####################################
Agent/rtProto/AODV variable was set
like below

C:\NetSim\ns-2.1b8a-win\aodv>ns
% set opt(ragent)       Agent/rtProto/AODV
Agent/rtProto/AODV
% set opt(pos) NONE
NONE
% Agent instproc init args {
        $self next $args
}
% Agent/rtProto instproc init args {
        $self next $args
}
% Agent/rtProto/AODV instproc init args {
        $self next $args
}
invalid command name "Agent/rtProto/AODV"
%

------=_NextPart_000_000E_01C1CF6B.93BD6DC0
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dks_c_5601-1987">
<META content=3D"MSHTML 5.50.4913.1100" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi... Everyone..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I will simulate AODV with adaptive =
route=20
maintenance&nbsp;method.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>but i can't simulate Original =
AODV</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Error like below</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>C:\NetSim\ns-2.1b8a-win\aodv&gt;ns=20
aodv.tcl<BR>invalid command name =
"Agent/rtProto/AODV"<BR>&nbsp;&nbsp;&nbsp;=20
while executing<BR>"Agent/rtProto/AODV instproc init args=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $self next=20
$args<BR>}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "<BR>&nbsp;&nbsp;&nbsp; =
(file=20
"aodv.tcl" line 20)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>C:\NetSim\ns-2.1b8a-win\aodv&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>#####################################</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Agent/rtProto/AODV variable was =
set</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>like below</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>C:\NetSim\ns-2.1b8a-win\aodv&gt;ns<BR>% =
set=20
opt(ragent)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Agent/rtProto/AODV<BR>Agent/rtProto/AODV<BR>% set opt(pos) =
NONE<BR>NONE<BR>%=20
Agent instproc init args {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
$self=20
next $args<BR>}<BR>% Agent/rtProto instproc init args=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $self next =
$args<BR>}<BR>%=20
Agent/rtProto/AODV instproc init args=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $self next =
$args<BR>}<BR>invalid=20
command name "Agent/rtProto/AODV"<BR>%</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_000E_01C1CF6B.93BD6DC0--


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


From daemon@optimus.ietf.org  Tue Mar 19 04:08:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17882
	for <manet-archive@odin.ietf.org>; Tue, 19 Mar 2002 04:08:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA29829
	for manet-archive@odin.ietf.org; Tue, 19 Mar 2002 04:08:58 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA27457;
	Tue, 19 Mar 2002 03:29:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA27427
	for <manet@optimus.ietf.org>; Tue, 19 Mar 2002 03:29:20 -0500 (EST)
Received: from nomark (stn.chonbuk.ac.kr [210.117.172.212])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17340
	for <manet@ietf.org>; Tue, 19 Mar 2002 03:29:17 -0500 (EST)
Received: from nomark ([210.117.172.212]) by nomark with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 19 Mar 2002 17:29:09 +0900
Message-ID: <001101c1cf20$23fa64c0$d4ac75d2@nomark>
From: "Suk Dea Yu" <sdyu@cs.chonbuk.ac.kr>
To: <manet@ietf.org>
Date: Tue, 19 Mar 2002 17:29:09 +0900
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000E_01C1CF6B.93BD6DC0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
X-OriginalArrivalTime: 19 Mar 2002 08:29:09.0270 (UTC) FILETIME=[23FBEB60:01C1CF20]
Subject: [manet] Why i could not run AODV simulation ???
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_000E_01C1CF6B.93BD6DC0
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

Hi... Everyone..

I will simulate AODV with adaptive route maintenance method.
but i can't simulate Original AODV
Error like below

C:\NetSim\ns-2.1b8a-win\aodv>ns aodv.tcl
invalid command name "Agent/rtProto/AODV"
    while executing
"Agent/rtProto/AODV instproc init args {
        $self next $args
}       "
    (file "aodv.tcl" line 20)

C:\NetSim\ns-2.1b8a-win\aodv>


#####################################
Agent/rtProto/AODV variable was set
like below

C:\NetSim\ns-2.1b8a-win\aodv>ns
% set opt(ragent)       Agent/rtProto/AODV
Agent/rtProto/AODV
% set opt(pos) NONE
NONE
% Agent instproc init args {
        $self next $args
}
% Agent/rtProto instproc init args {
        $self next $args
}
% Agent/rtProto/AODV instproc init args {
        $self next $args
}
invalid command name "Agent/rtProto/AODV"
%

------=_NextPart_000_000E_01C1CF6B.93BD6DC0
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dks_c_5601-1987">
<META content=3D"MSHTML 5.50.4913.1100" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi... Everyone..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I will simulate AODV with adaptive =
route=20
maintenance&nbsp;method.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>but i can't simulate Original =
AODV</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Error like below</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>C:\NetSim\ns-2.1b8a-win\aodv&gt;ns=20
aodv.tcl<BR>invalid command name =
"Agent/rtProto/AODV"<BR>&nbsp;&nbsp;&nbsp;=20
while executing<BR>"Agent/rtProto/AODV instproc init args=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $self next=20
$args<BR>}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "<BR>&nbsp;&nbsp;&nbsp; =
(file=20
"aodv.tcl" line 20)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>C:\NetSim\ns-2.1b8a-win\aodv&gt;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial =
size=3D2>#####################################</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Agent/rtProto/AODV variable was =
set</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>like below</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>C:\NetSim\ns-2.1b8a-win\aodv&gt;ns<BR>% =
set=20
opt(ragent)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
Agent/rtProto/AODV<BR>Agent/rtProto/AODV<BR>% set opt(pos) =
NONE<BR>NONE<BR>%=20
Agent instproc init args {<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
$self=20
next $args<BR>}<BR>% Agent/rtProto instproc init args=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $self next =
$args<BR>}<BR>%=20
Agent/rtProto/AODV instproc init args=20
{<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; $self next =
$args<BR>}<BR>invalid=20
command name "Agent/rtProto/AODV"<BR>%</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_000E_01C1CF6B.93BD6DC0--


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



From manet-admin@ietf.org  Tue Mar 19 04:10:40 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17907
	for <manet-archive@odin.ietf.org>; Tue, 19 Mar 2002 04:10:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA26942;
	Tue, 19 Mar 2002 03:20:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA26908
	for <manet@optimus.ietf.org>; Tue, 19 Mar 2002 03:20:50 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17198
	for <manet@ietf.org>; Tue, 19 Mar 2002 03:20:48 -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 AAA26232;
	Tue, 19 Mar 2002 00:20:16 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g2J8K7917564;
	Tue, 19 Mar 2002 00:20:07 -0800
X-mProtect:  Tue, 19 Mar 2002 00:20:07 -0800 Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (172.21.193.185, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdsNxMS6; Tue, 19 Mar 2002 00:20:04 PST
Message-ID: <3C96F44A.9090007@iprg.nokia.com>
Date: Tue, 19 Mar 2002 00:18:18 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: Jorge Nuevo <nuevo@inrs-telecom.uquebec.ca>
CC: manet@ietf.org
Subject: Re: [manet] Question about dependency of unicast protocols by multicast protocols
References: <200203142011.PAA24622@hoffman.INRS-Telecom.UQuebec.CA>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

hi,

Another multicast protocol which does not depend on an
underlying unicast protocol

MZR
      http://people.nokia.net/vijayd/draft-vijay-manet-mzr-01.txt
      http://people.nokia.net/vijayd/mzr.pdf (ICC 2001)

Vijay

Jorge Nuevo wrote:

> Hello,
> 
> I am trying to find out which of the multicast protocols for
> ad hoc networks are unicast protocols dependent. The following
> would be unicast dependent:
> MAODV, AMRoute, CAMP
> 
> and non-dependent would be: AMRIS, ODMRP and MCEDAR,
> 
> but I am not sure about FGMP (Forwarding Group Multicast Protocol),
> ABAM (Associativity Based Multicast) and
> ADMR (Adaptive Demand-driven Multicast Routing).
> 
> Could any one help me with this doubt?
> 
> thanks 
> 
> Jorge Nuevo
> nuevo@inrs-telecom.uquebec.ca
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 



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


From daemon@optimus.ietf.org  Tue Mar 19 04:10:40 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17918
	for <manet-archive@odin.ietf.org>; Tue, 19 Mar 2002 04:10:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA29874
	for manet-archive@odin.ietf.org; Tue, 19 Mar 2002 04:10:42 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA26942;
	Tue, 19 Mar 2002 03:20:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA26908
	for <manet@optimus.ietf.org>; Tue, 19 Mar 2002 03:20:50 -0500 (EST)
Received: from mailhost.iprg.nokia.com (mailhost.iprg.nokia.com [205.226.5.12])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17198
	for <manet@ietf.org>; Tue, 19 Mar 2002 03:20:48 -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 AAA26232;
	Tue, 19 Mar 2002 00:20:16 -0800 (PST)
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id g2J8K7917564;
	Tue, 19 Mar 2002 00:20:07 -0800
X-mProtect:  Tue, 19 Mar 2002 00:20:07 -0800 Nokia Silicon Valley Messaging Protection
Received: from UNKNOWN (172.21.193.185, claiming to be "iprg.nokia.com")
	by darkstar.iprg.nokia.com smtpdsNxMS6; Tue, 19 Mar 2002 00:20:04 PST
Message-ID: <3C96F44A.9090007@iprg.nokia.com>
Date: Tue, 19 Mar 2002 00:18:18 -0800
From: Vijay Devarapalli <vijayd@iprg.nokia.com>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
X-Accept-Language: en-us
MIME-Version: 1.0
To: Jorge Nuevo <nuevo@inrs-telecom.uquebec.ca>
CC: manet@ietf.org
Subject: Re: [manet] Question about dependency of unicast protocols by multicast protocols
References: <200203142011.PAA24622@hoffman.INRS-Telecom.UQuebec.CA>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

hi,

Another multicast protocol which does not depend on an
underlying unicast protocol

MZR
      http://people.nokia.net/vijayd/draft-vijay-manet-mzr-01.txt
      http://people.nokia.net/vijayd/mzr.pdf (ICC 2001)

Vijay

Jorge Nuevo wrote:

> Hello,
> 
> I am trying to find out which of the multicast protocols for
> ad hoc networks are unicast protocols dependent. The following
> would be unicast dependent:
> MAODV, AMRoute, CAMP
> 
> and non-dependent would be: AMRIS, ODMRP and MCEDAR,
> 
> but I am not sure about FGMP (Forwarding Group Multicast Protocol),
> ABAM (Associativity Based Multicast) and
> ADMR (Adaptive Demand-driven Multicast Routing).
> 
> Could any one help me with this doubt?
> 
> thanks 
> 
> Jorge Nuevo
> nuevo@inrs-telecom.uquebec.ca
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 



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



From manet-admin@ietf.org  Tue Mar 19 17:07:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05647
	for <manet-archive@odin.ietf.org>; Tue, 19 Mar 2002 17:07:19 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18588;
	Tue, 19 Mar 2002 16:35:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18553
	for <manet@ns.ietf.org>; Tue, 19 Mar 2002 16:35:25 -0500 (EST)
Received: from cheetah.cs.ucla.edu (Cheetah.CS.UCLA.EDU [131.179.128.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04742
	for <manet@ietf.org>; Tue, 19 Mar 2002 16:35:21 -0500 (EST)
Received: from localhost (hxy@localhost)
	by cheetah.cs.ucla.edu (8.10.2+Sun/8.10.2/UCLACS-5.1) with ESMTP id g2JLZJl00512;
	Tue, 19 Mar 2002 13:35:19 -0800 (PST)
Date: Tue, 19 Mar 2002 13:35:19 -0800 (PST)
From: Xiaoyan Hong <hxy@CS.UCLA.EDU>
To: Frank Dinies <FrankDinies@web.de>
cc: Xiaoyan Hong <hxy@CS.UCLA.EDU>, Dr Mario Gerla <gerla@CS.UCLA.EDU>,
        <manet@ietf.org>
Subject: Re: [manet] Fisheye State Routing
In-Reply-To: <200203152154.34956.FrankDinies@web.de>
Message-ID: <Pine.SOL.4.33.0203191323170.22926-100000@cheetah.cs.ucla.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi, Frank,

Thanks a lot for pointing out the problem in the current FSR draft.

The lastHeardTime variable in the topology table IS for the purpose of
timing out stale entries.  However, the description of the operation
was somehow missing in the draft. A new FSR draft will be submitted very
soon.  Here is the operation on the lastHeardTime variable.

1) When a topology entry is inserted or updated, the time is stamped in
the variable. For the node itself, the field is refreshed every time
before it broadcasts its inner scope topology.
2) Timing-out the topology table is performed before a node broadcasts its
topology table ( for any broadcast frequencies). For inner scope
broadcasting, timing-out is performed after the node refreshs its own
entry.
3) Timing-out the topology table is also performed before the calculation
of shortest paths.

Best,

Xiaoyan Hong

On Fri, 15 Mar 2002, Frank Dinies wrote:

> Hi,
>
> I have some questions about the Fisheye State Routing Algorithm in respect to
> the current draft version:
>
> - I think the "last heard time" variable in the topology table is never used
> in current protocol operations  ! Maybe for further extensions ??
>
> -  Nodes, once registered in the Topolgy table will never removed, i.e. if a
> node disappears, the node will not taken into account for further
> computations of the routing table, because the node was removed from the
> neighbour list. But nevertheless its entry will not be removed in the
> topology table.
>
> Regards
>
> Frank Dinies
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>


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


From daemon@ns.ietf.org  Tue Mar 19 17:07:20 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05655
	for <manet-archive@odin.ietf.org>; Tue, 19 Mar 2002 17:07:20 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA21087
	for manet-archive@odin.ietf.org; Tue, 19 Mar 2002 17:07:21 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18588;
	Tue, 19 Mar 2002 16:35:28 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA18553
	for <manet@ns.ietf.org>; Tue, 19 Mar 2002 16:35:25 -0500 (EST)
Received: from cheetah.cs.ucla.edu (Cheetah.CS.UCLA.EDU [131.179.128.24])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04742
	for <manet@ietf.org>; Tue, 19 Mar 2002 16:35:21 -0500 (EST)
Received: from localhost (hxy@localhost)
	by cheetah.cs.ucla.edu (8.10.2+Sun/8.10.2/UCLACS-5.1) with ESMTP id g2JLZJl00512;
	Tue, 19 Mar 2002 13:35:19 -0800 (PST)
Date: Tue, 19 Mar 2002 13:35:19 -0800 (PST)
From: Xiaoyan Hong <hxy@CS.UCLA.EDU>
To: Frank Dinies <FrankDinies@web.de>
cc: Xiaoyan Hong <hxy@CS.UCLA.EDU>, Dr Mario Gerla <gerla@CS.UCLA.EDU>,
        <manet@ietf.org>
Subject: Re: [manet] Fisheye State Routing
In-Reply-To: <200203152154.34956.FrankDinies@web.de>
Message-ID: <Pine.SOL.4.33.0203191323170.22926-100000@cheetah.cs.ucla.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi, Frank,

Thanks a lot for pointing out the problem in the current FSR draft.

The lastHeardTime variable in the topology table IS for the purpose of
timing out stale entries.  However, the description of the operation
was somehow missing in the draft. A new FSR draft will be submitted very
soon.  Here is the operation on the lastHeardTime variable.

1) When a topology entry is inserted or updated, the time is stamped in
the variable. For the node itself, the field is refreshed every time
before it broadcasts its inner scope topology.
2) Timing-out the topology table is performed before a node broadcasts its
topology table ( for any broadcast frequencies). For inner scope
broadcasting, timing-out is performed after the node refreshs its own
entry.
3) Timing-out the topology table is also performed before the calculation
of shortest paths.

Best,

Xiaoyan Hong

On Fri, 15 Mar 2002, Frank Dinies wrote:

> Hi,
>
> I have some questions about the Fisheye State Routing Algorithm in respect to
> the current draft version:
>
> - I think the "last heard time" variable in the topology table is never used
> in current protocol operations  ! Maybe for further extensions ??
>
> -  Nodes, once registered in the Topolgy table will never removed, i.e. if a
> node disappears, the node will not taken into account for further
> computations of the routing table, because the node was removed from the
> neighbour list. But nevertheless its entry will not be removed in the
> topology table.
>
> Regards
>
> Frank Dinies
>
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
>


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



From manet-admin@ietf.org  Fri Mar 22 19:47:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04978
	for <manet-archive@odin.ietf.org>; Fri, 22 Mar 2002 19:47:26 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA01451;
	Fri, 22 Mar 2002 19:11:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA01419
	for <manet@optimus.ietf.org>; Fri, 22 Mar 2002 19:11:43 -0500 (EST)
Received: from deimos.hpl.hp.com (deimos.hpl.hp.com [192.6.19.190])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04686
	for <manet@ietf.org>; Fri, 22 Mar 2002 19:11:41 -0500 (EST)
Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33])
	by deimos.hpl.hp.com (8.9.3 (PHNE_24419)/HPL-PA Relay) with ESMTP id QAA22760
	for <manet@ietf.org>; Fri, 22 Mar 2002 16:11:43 -0800 (PST)
Received: from hplex1.hpl.hp.com (hplex1.hpl.hp.com [15.0.152.182])
	by hplms2.hpl.hp.com (8.10.2/8.10.2 HPL-PA Hub) with SMTP id g2N0BgV00874
	for <manet@ietf.org>; Fri, 22 Mar 2002 16:11:42 -0800 (PST)
Received: from 15.0.152.182 by hplex1.hpl.hp.com (InterScan E-Mail VirusWall NT); Fri, 22 Mar 2002 16:11:41 -0800
Received: by hplex1.hpl.hp.com with Internet Mail Service (5.5.2653.19)
	id <H1MA8PY2>; Fri, 22 Mar 2002 16:11:41 -0800
Message-ID: <40700B4C02ABD5119F00009027876644533485@hplex1.hpl.hp.com>
From: "Lee, Sung Ju" <sjlee@exch.hpl.hp.com>
To: "'manet@ietf.org'" <manet@ietf.org>
Date: Fri, 22 Mar 2002 16:11:41 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [manet] routing models for GlomoSim and MAC models for ns-2
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Hi,

I am looking for some ad hoc routing models for Glomosim and some
NS-2 MAC layer protocol models that are not already included in
the release.

Does anyone have Glomosim models of routing protocols 
(OLSR, TBRPF, STAR, ...) or NS-2 models of MAC protocols 
besides 802.11 and CSMA (e.g., MACA, MACAW, FAMA, ...)?  

If I could get the models for a research use, I'd appreciate it.

Thanks,

- SJ


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


From daemon@optimus.ietf.org  Fri Mar 22 19:47:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04987
	for <manet-archive@odin.ietf.org>; Fri, 22 Mar 2002 19:47:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id TAA04075
	for manet-archive@odin.ietf.org; Fri, 22 Mar 2002 19:47:27 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA01451;
	Fri, 22 Mar 2002 19:11:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA01419
	for <manet@optimus.ietf.org>; Fri, 22 Mar 2002 19:11:43 -0500 (EST)
Received: from deimos.hpl.hp.com (deimos.hpl.hp.com [192.6.19.190])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04686
	for <manet@ietf.org>; Fri, 22 Mar 2002 19:11:41 -0500 (EST)
Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33])
	by deimos.hpl.hp.com (8.9.3 (PHNE_24419)/HPL-PA Relay) with ESMTP id QAA22760
	for <manet@ietf.org>; Fri, 22 Mar 2002 16:11:43 -0800 (PST)
Received: from hplex1.hpl.hp.com (hplex1.hpl.hp.com [15.0.152.182])
	by hplms2.hpl.hp.com (8.10.2/8.10.2 HPL-PA Hub) with SMTP id g2N0BgV00874
	for <manet@ietf.org>; Fri, 22 Mar 2002 16:11:42 -0800 (PST)
Received: from 15.0.152.182 by hplex1.hpl.hp.com (InterScan E-Mail VirusWall NT); Fri, 22 Mar 2002 16:11:41 -0800
Received: by hplex1.hpl.hp.com with Internet Mail Service (5.5.2653.19)
	id <H1MA8PY2>; Fri, 22 Mar 2002 16:11:41 -0800
Message-ID: <40700B4C02ABD5119F00009027876644533485@hplex1.hpl.hp.com>
From: "Lee, Sung Ju" <sjlee@exch.hpl.hp.com>
To: "'manet@ietf.org'" <manet@ietf.org>
Date: Fri, 22 Mar 2002 16:11:41 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [manet] routing models for GlomoSim and MAC models for ns-2
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Hi,

I am looking for some ad hoc routing models for Glomosim and some
NS-2 MAC layer protocol models that are not already included in
the release.

Does anyone have Glomosim models of routing protocols 
(OLSR, TBRPF, STAR, ...) or NS-2 models of MAC protocols 
besides 802.11 and CSMA (e.g., MACA, MACAW, FAMA, ...)?  

If I could get the models for a research use, I'd appreciate it.

Thanks,

- SJ


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



From manet-admin@ietf.org  Sat Mar 23 17:41:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26034
	for <manet-archive@odin.ietf.org>; Sat, 23 Mar 2002 17:41:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06085;
	Sat, 23 Mar 2002 17:19:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06037
	for <manet@optimus.ietf.org>; Sat, 23 Mar 2002 17:19:40 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25818
	for <manet@ietf.org>; Sat, 23 Mar 2002 17:19:34 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id OAA08642;
	Sat, 23 Mar 2002 14:14:00 -0800 (PST)
Message-Id: <200203232214.OAA08642@pit.erg.sri.com>
To: "Lee, Sung Ju" <sjlee@exch.hpl.hp.com>
cc: "'manet@ietf.org'" <manet@ietf.org>
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] routing models for GlomoSim and MAC models for ns-2 
In-reply-to: Your message of "Fri, 22 Mar 2002 16:11:41 PST."
             <40700B4C02ABD5119F00009027876644533485@hplex1.hpl.hp.com> 
Date: Sat, 23 Mar 2002 14:14:00 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Hi SJ,

I would be happy to port TBRPF to Glomosim 
if I could obtain Glomosim/Parsec for free.
Unfortunately, it is available for free only to educational
institutions, so even though I would use it only for research
purposes, it would cost me about $25,000.
This is a big advantage for ns-2.

Richard

> 
> Hi,
> 
> I am looking for some ad hoc routing models for Glomosim and some
> NS-2 MAC layer protocol models that are not already included in
> the release.
> 
> Does anyone have Glomosim models of routing protocols 
> (OLSR, TBRPF, STAR, ...) or NS-2 models of MAC protocols 
> besides 802.11 and CSMA (e.g., MACA, MACAW, FAMA, ...)?  
> 
> If I could get the models for a research use, I'd appreciate it.
> 
> Thanks,
> 
> - SJ
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Sat Mar 23 17:41:30 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26043
	for <manet-archive@odin.ietf.org>; Sat, 23 Mar 2002 17:41:30 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA09745
	for manet-archive@odin.ietf.org; Sat, 23 Mar 2002 17:41:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06085;
	Sat, 23 Mar 2002 17:19:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA06037
	for <manet@optimus.ietf.org>; Sat, 23 Mar 2002 17:19:40 -0500 (EST)
Received: from pit.erg.sri.com (pit.erg.sri.com [128.18.100.28])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25818
	for <manet@ietf.org>; Sat, 23 Mar 2002 17:19:34 -0500 (EST)
Received: from pit.erg.sri.com (localhost [127.0.0.1])
	by pit.erg.sri.com (8.9.3+Sun/8.9.1) with ESMTP id OAA08642;
	Sat, 23 Mar 2002 14:14:00 -0800 (PST)
Message-Id: <200203232214.OAA08642@pit.erg.sri.com>
To: "Lee, Sung Ju" <sjlee@exch.hpl.hp.com>
cc: "'manet@ietf.org'" <manet@ietf.org>
Reply-To: ogier@erg.sri.com
From: ogier@erg.sri.com
Subject: Re: [manet] routing models for GlomoSim and MAC models for ns-2 
In-reply-to: Your message of "Fri, 22 Mar 2002 16:11:41 PST."
             <40700B4C02ABD5119F00009027876644533485@hplex1.hpl.hp.com> 
Date: Sat, 23 Mar 2002 14:14:00 -0800
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


Hi SJ,

I would be happy to port TBRPF to Glomosim 
if I could obtain Glomosim/Parsec for free.
Unfortunately, it is available for free only to educational
institutions, so even though I would use it only for research
purposes, it would cost me about $25,000.
This is a big advantage for ns-2.

Richard

> 
> Hi,
> 
> I am looking for some ad hoc routing models for Glomosim and some
> NS-2 MAC layer protocol models that are not already included in
> the release.
> 
> Does anyone have Glomosim models of routing protocols 
> (OLSR, TBRPF, STAR, ...) or NS-2 models of MAC protocols 
> besides 802.11 and CSMA (e.g., MACA, MACAW, FAMA, ...)?  
> 
> If I could get the models for a research use, I'd appreciate it.
> 
> Thanks,
> 
> - SJ
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Sun Mar 24 16:54:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18850
	for <manet-archive@odin.ietf.org>; Sun, 24 Mar 2002 16:54:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17514;
	Sun, 24 Mar 2002 16:27:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17488
	for <manet@optimus.ietf.org>; Sun, 24 Mar 2002 16:27:53 -0500 (EST)
Received: from nambisan.net (adsl-216-103-82-165.dsl.snfc21.pacbell.net [216.103.82.165])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18455
	for <manet@ietf.org>; Sun, 24 Mar 2002 16:27:49 -0500 (EST)
From: dineshn@pacbell.net
Received: from localhost (localhost.nambisan.net [127.0.0.1])
	by nambisan.net (8.11.6/8.11.6) with ESMTP id g2OLKF788909
	for <manet@ietf.org>; Sun, 24 Mar 2002 13:20:15 -0800 (PST)
	(envelope-from dineshn@pacbell.net)
Date: Sun, 24 Mar 2002 13:20:15 -0800 (PST)
X-X-Sender:  <dinesh@asterix.nambisan.net>
Reply-To: <dineshn@pacbell.net>
To: <manet@ietf.org>
Message-ID: <20020324131002.Q88875-100000@asterix.nambisan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Scaling of AODV
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

I was wondering as to how large a Mobile AdHoc Network (in terms of
number of nodes) the AODV routing protocol could scale to (and reasonably
support); whether the authors would be kind enough to share their opinions
on it (including the results of any tests/simulations they ran) ?
Thanks in advance,
Dinesh


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


From daemon@optimus.ietf.org  Sun Mar 24 16:54:32 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18860
	for <manet-archive@odin.ietf.org>; Sun, 24 Mar 2002 16:54:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA23621
	for manet-archive@odin.ietf.org; Sun, 24 Mar 2002 16:54:35 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17514;
	Sun, 24 Mar 2002 16:27:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA17488
	for <manet@optimus.ietf.org>; Sun, 24 Mar 2002 16:27:53 -0500 (EST)
Received: from nambisan.net (adsl-216-103-82-165.dsl.snfc21.pacbell.net [216.103.82.165])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18455
	for <manet@ietf.org>; Sun, 24 Mar 2002 16:27:49 -0500 (EST)
From: dineshn@pacbell.net
Received: from localhost (localhost.nambisan.net [127.0.0.1])
	by nambisan.net (8.11.6/8.11.6) with ESMTP id g2OLKF788909
	for <manet@ietf.org>; Sun, 24 Mar 2002 13:20:15 -0800 (PST)
	(envelope-from dineshn@pacbell.net)
Date: Sun, 24 Mar 2002 13:20:15 -0800 (PST)
X-X-Sender:  <dinesh@asterix.nambisan.net>
Reply-To: <dineshn@pacbell.net>
To: <manet@ietf.org>
Message-ID: <20020324131002.Q88875-100000@asterix.nambisan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Scaling of AODV
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

I was wondering as to how large a Mobile AdHoc Network (in terms of
number of nodes) the AODV routing protocol could scale to (and reasonably
support); whether the authors would be kind enough to share their opinions
on it (including the results of any tests/simulations they ran) ?
Thanks in advance,
Dinesh


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



From manet-admin@ietf.org  Sun Mar 24 22:12:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22644
	for <manet-archive@odin.ietf.org>; Sun, 24 Mar 2002 22:12:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA25968;
	Sun, 24 Mar 2002 21:38:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA25926
	for <manet@optimus.ietf.org>; Sun, 24 Mar 2002 21:38:06 -0500 (EST)
Received: from imc21.ex.nus.edu.sg (imc21.ex.nus.edu.sg [137.132.14.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22015
	for <manet@ietf.org>; Sun, 24 Mar 2002 21:38:01 -0500 (EST)
Received: by imc21.ex.nus.edu.sg with Internet Mail Service (5.5.2653.19)
	id <ZKDNN00R>; Mon, 25 Mar 2002 10:37:58 +0800
Message-ID: <9C4C56CDF89E0440A6BD571E76D2387F099AD21E@exs23.ex.nus.edu.sg>
From: Marwaha Shivanajay <engp1609@nus.edu.sg>
To: manet@ietf.org
Date: Mon, 25 Mar 2002 10:37:54 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [manet] Real emulation/testing (on a testbed) of ad hoc networks
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Dear all,

I've to emulate an ad hoc network using a few mobile devices. Kindly advice
on the following:

1. Which emulator/simulators have been used till now for this purpose and
how good they are?
2. How good is NS-2 for this purpose (emulating MANETs). Has anyone used it.
3. How many mobile devices should atleast be used.
4. What are the preffered wireless cards that are used. (like zircon, nokia,
lucent etc.) 
5. And what range should they be of.
6. Any experiences while emulating/testing (on a testbed) of MANETs. 

Thanks a lot.

Regards,
Shivanajay Marwaha
Research Scholar,
Dept of Electrical and Comp Engg.
National University of Singapore.
www.nus.edu.sg

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


From daemon@optimus.ietf.org  Sun Mar 24 22:12:40 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22654
	for <manet-archive@odin.ietf.org>; Sun, 24 Mar 2002 22:12:40 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA04177
	for manet-archive@odin.ietf.org; Sun, 24 Mar 2002 22:12:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA25968;
	Sun, 24 Mar 2002 21:38:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA25926
	for <manet@optimus.ietf.org>; Sun, 24 Mar 2002 21:38:06 -0500 (EST)
Received: from imc21.ex.nus.edu.sg (imc21.ex.nus.edu.sg [137.132.14.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22015
	for <manet@ietf.org>; Sun, 24 Mar 2002 21:38:01 -0500 (EST)
Received: by imc21.ex.nus.edu.sg with Internet Mail Service (5.5.2653.19)
	id <ZKDNN00R>; Mon, 25 Mar 2002 10:37:58 +0800
Message-ID: <9C4C56CDF89E0440A6BD571E76D2387F099AD21E@exs23.ex.nus.edu.sg>
From: Marwaha Shivanajay <engp1609@nus.edu.sg>
To: manet@ietf.org
Date: Mon, 25 Mar 2002 10:37:54 +0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [manet] Real emulation/testing (on a testbed) of ad hoc networks
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Dear all,

I've to emulate an ad hoc network using a few mobile devices. Kindly advice
on the following:

1. Which emulator/simulators have been used till now for this purpose and
how good they are?
2. How good is NS-2 for this purpose (emulating MANETs). Has anyone used it.
3. How many mobile devices should atleast be used.
4. What are the preffered wireless cards that are used. (like zircon, nokia,
lucent etc.) 
5. And what range should they be of.
6. Any experiences while emulating/testing (on a testbed) of MANETs. 

Thanks a lot.

Regards,
Shivanajay Marwaha
Research Scholar,
Dept of Electrical and Comp Engg.
National University of Singapore.
www.nus.edu.sg

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



From manet-admin@ietf.org  Mon Mar 25 00:11:36 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25437
	for <manet-archive@odin.ietf.org>; Mon, 25 Mar 2002 00:11:36 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA22632;
	Sun, 24 Mar 2002 23:33:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA22600
	for <manet@optimus.ietf.org>; Sun, 24 Mar 2002 23:33:32 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24796
	for <manet@ietf.org>; Sun, 24 Mar 2002 23:33:27 -0500 (EST)
Received: from zidane.cc.vt.edu (IDENT:mirapoint@zidane-lb.cc.vt.edu [10.1.1.13])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2P4XTI512313;
	Sun, 24 Mar 2002 23:33:29 -0500 (EST)
Received: from TNT (h80ad3776.dhcp.vt.edu [128.173.55.118])
	by zidane.cc.vt.edu (Mirapoint)
	with SMTP id AKP96059;
	Sun, 24 Mar 2002 23:33:28 -0500 (EST)
Message-ID: <000e01c1d3b5$f85759a0$7637ad80@workgroup>
From: "Tao Lin" <taolin@VT.EDU>
To: "Marwaha Shivanajay" <engp1609@nus.edu.sg>
Cc: <manet@ietf.org>
References: <9C4C56CDF89E0440A6BD571E76D2387F099AD21E@exs23.ex.nus.edu.sg>
Subject: Re: [manet] Real emulation/testing (on a testbed) of ad hoc networks
Date: Sun, 24 Mar 2002 23:31:43 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

We did simulations of wireless networks in a wired test bed. We build a
linux box with multiple interfaces as a dynamic switch. It can control the
connectivities between ports dynamically (it will not open any datagram,
just simply forward to one or more interfaces according to the local control
script.). By using it with some other end machines, we can build a star
topology network. The dynamic switch is the center node. Those leaves can
act as mobile hosts. The software for that swich is for Redhat 7.0 with
2.2.16 kernel. You can find it at
http://sourceforge.net/projects/dynamic-switch.


Tao Lin
ECE Dept.
Virginia Tech.



----- Original Message -----
From: "Marwaha Shivanajay" <engp1609@nus.edu.sg>
To: <manet@ietf.org>
Sent: Sunday, March 24, 2002 9:37 PM
Subject: [manet] Real emulation/testing (on a testbed) of ad hoc networks


> Dear all,
>
> I've to emulate an ad hoc network using a few mobile devices. Kindly
advice
> on the following:
>
> 1. Which emulator/simulators have been used till now for this purpose and
> how good they are?
> 2. How good is NS-2 for this purpose (emulating MANETs). Has anyone used
it.
> 3. How many mobile devices should atleast be used.
> 4. What are the preffered wireless cards that are used. (like zircon,
nokia,
> lucent etc.)
> 5. And what range should they be of.
> 6. Any experiences while emulating/testing (on a testbed) of MANETs.
>
> Thanks a lot.
>
> Regards,
> Shivanajay Marwaha
> Research Scholar,
> Dept of Electrical and Comp Engg.
> National University of Singapore.
> www.nus.edu.sg
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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


From daemon@optimus.ietf.org  Mon Mar 25 00:11:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25447
	for <manet-archive@odin.ietf.org>; Mon, 25 Mar 2002 00:11:36 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA01555
	for manet-archive@odin.ietf.org; Mon, 25 Mar 2002 00:11:37 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA22632;
	Sun, 24 Mar 2002 23:33:36 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA22600
	for <manet@optimus.ietf.org>; Sun, 24 Mar 2002 23:33:32 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24796
	for <manet@ietf.org>; Sun, 24 Mar 2002 23:33:27 -0500 (EST)
Received: from zidane.cc.vt.edu (IDENT:mirapoint@zidane-lb.cc.vt.edu [10.1.1.13])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2P4XTI512313;
	Sun, 24 Mar 2002 23:33:29 -0500 (EST)
Received: from TNT (h80ad3776.dhcp.vt.edu [128.173.55.118])
	by zidane.cc.vt.edu (Mirapoint)
	with SMTP id AKP96059;
	Sun, 24 Mar 2002 23:33:28 -0500 (EST)
Message-ID: <000e01c1d3b5$f85759a0$7637ad80@workgroup>
From: "Tao Lin" <taolin@VT.EDU>
To: "Marwaha Shivanajay" <engp1609@nus.edu.sg>
Cc: <manet@ietf.org>
References: <9C4C56CDF89E0440A6BD571E76D2387F099AD21E@exs23.ex.nus.edu.sg>
Subject: Re: [manet] Real emulation/testing (on a testbed) of ad hoc networks
Date: Sun, 24 Mar 2002 23:31:43 -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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

We did simulations of wireless networks in a wired test bed. We build a
linux box with multiple interfaces as a dynamic switch. It can control the
connectivities between ports dynamically (it will not open any datagram,
just simply forward to one or more interfaces according to the local control
script.). By using it with some other end machines, we can build a star
topology network. The dynamic switch is the center node. Those leaves can
act as mobile hosts. The software for that swich is for Redhat 7.0 with
2.2.16 kernel. You can find it at
http://sourceforge.net/projects/dynamic-switch.


Tao Lin
ECE Dept.
Virginia Tech.



----- Original Message -----
From: "Marwaha Shivanajay" <engp1609@nus.edu.sg>
To: <manet@ietf.org>
Sent: Sunday, March 24, 2002 9:37 PM
Subject: [manet] Real emulation/testing (on a testbed) of ad hoc networks


> Dear all,
>
> I've to emulate an ad hoc network using a few mobile devices. Kindly
advice
> on the following:
>
> 1. Which emulator/simulators have been used till now for this purpose and
> how good they are?
> 2. How good is NS-2 for this purpose (emulating MANETs). Has anyone used
it.
> 3. How many mobile devices should atleast be used.
> 4. What are the preffered wireless cards that are used. (like zircon,
nokia,
> lucent etc.)
> 5. And what range should they be of.
> 6. Any experiences while emulating/testing (on a testbed) of MANETs.
>
> Thanks a lot.
>
> Regards,
> Shivanajay Marwaha
> Research Scholar,
> Dept of Electrical and Comp Engg.
> National University of Singapore.
> www.nus.edu.sg
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Mon Mar 25 08:31:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09490
	for <manet-archive@odin.ietf.org>; Mon, 25 Mar 2002 08:31:47 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21763;
	Mon, 25 Mar 2002 08:09:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21723
	for <manet@optimus.ietf.org>; Mon, 25 Mar 2002 08:09:44 -0500 (EST)
Received: from smtp4.cluster.oleane.net (smtp4.cluster.oleane.net [195.25.12.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08393
	for <manet@ietf.org>; Mon, 25 Mar 2002 08:09:41 -0500 (EST)
Received: from oleane ([194.250.212.114]) by smtp4.cluster.oleane.net with SMTP id g2PD9gx22721 for <manet@ietf.org>; Mon, 25 Mar 2002 14:09:42 +0100 (CET)
Message-ID: <00dc01c1d3fe$32186ce0$1901a8c0@oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <manet@ietf.org>
Date: Mon, 25 Mar 2002 14:07:26 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00CB_01C1D406.647D2560"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Subject: [manet] "WLAN Security 2002" conference
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_00CB_01C1D406.647D2560
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

=20
The "WLAN Security 2002" conference, to take place June 25-28 in Paris, =
will feature the most eminent specialists in the domain of security =
applied to wireless local networks.=20
The call for proposals dead line has been postponed to April 5.
More details at:
http://www.upperside.fr/wlansecu/wlansecintro.htm


------=_NextPart_000_00CB_01C1D406.647D2560
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial><FONT face=3DArial>&nbsp;
<DIV><FONT size=3D2>The "<SPAN class=3Dnomspeaker>WLAN Security =
2002</SPAN>"=20
conference, to take place June 25-28 in Paris, will feature the most =
eminent=20
specialists in the domain of security applied to wireless local =
networks.=20
<BR>The call for proposals dead line has been postponed to April =
5.<BR>More=20
details at:</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://www.upperside.fr/wlansecu/wlansecintro.htm">http://www.upp=
erside.fr/wlansecu/wlansecintro.htm</A></FONT></DIV>
<DIV>&nbsp;</DIV></FONT></FONT></DIV></BODY></HTML>

------=_NextPart_000_00CB_01C1D406.647D2560--


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


From daemon@optimus.ietf.org  Mon Mar 25 08:31:54 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09499
	for <manet-archive@odin.ietf.org>; Mon, 25 Mar 2002 08:31:53 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA27436
	for manet-archive@odin.ietf.org; Mon, 25 Mar 2002 08:31:55 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21763;
	Mon, 25 Mar 2002 08:09:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21723
	for <manet@optimus.ietf.org>; Mon, 25 Mar 2002 08:09:44 -0500 (EST)
Received: from smtp4.cluster.oleane.net (smtp4.cluster.oleane.net [195.25.12.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08393
	for <manet@ietf.org>; Mon, 25 Mar 2002 08:09:41 -0500 (EST)
Received: from oleane ([194.250.212.114]) by smtp4.cluster.oleane.net with SMTP id g2PD9gx22721 for <manet@ietf.org>; Mon, 25 Mar 2002 14:09:42 +0100 (CET)
Message-ID: <00dc01c1d3fe$32186ce0$1901a8c0@oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <manet@ietf.org>
Date: Mon, 25 Mar 2002 14:07:26 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00CB_01C1D406.647D2560"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Subject: [manet] "WLAN Security 2002" conference
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

This is a multi-part message in MIME format.

------=_NextPart_000_00CB_01C1D406.647D2560
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

=20
The "WLAN Security 2002" conference, to take place June 25-28 in Paris, =
will feature the most eminent specialists in the domain of security =
applied to wireless local networks.=20
The call for proposals dead line has been postponed to April 5.
More details at:
http://www.upperside.fr/wlansecu/wlansecintro.htm


------=_NextPart_000_00CB_01C1D406.647D2560
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial><FONT face=3DArial>&nbsp;
<DIV><FONT size=3D2>The "<SPAN class=3Dnomspeaker>WLAN Security =
2002</SPAN>"=20
conference, to take place June 25-28 in Paris, will feature the most =
eminent=20
specialists in the domain of security applied to wireless local =
networks.=20
<BR>The call for proposals dead line has been postponed to April =
5.<BR>More=20
details at:</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://www.upperside.fr/wlansecu/wlansecintro.htm">http://www.upp=
erside.fr/wlansecu/wlansecintro.htm</A></FONT></DIV>
<DIV>&nbsp;</DIV></FONT></FONT></DIV></BODY></HTML>

------=_NextPart_000_00CB_01C1D406.647D2560--


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



From manet-admin@ietf.org  Tue Mar 26 00:15:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16306
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 00:15:44 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA10334;
	Mon, 25 Mar 2002 23:43:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA10299
	for <manet@optimus.ietf.org>; Mon, 25 Mar 2002 23:43:22 -0500 (EST)
Received: from sjtu.edu.cn ([202.120.2.106])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15870
	for <manet@ietf.org>; Mon, 25 Mar 2002 23:43:15 -0500 (EST)
Received: from aaron (unknown [202.120.3.109])
	by sjtu.edu.cn (WorldPost) with SMTP id 72E32FE7
	for <manet@ietf.org>; Tue, 26 Mar 2002 12:43:20 +0800 (BEIST)
Message-ID: <001b01c1d480$c2f3bb20$6d0378ca@aaron>
From: "danaus" <licheng@sjtu.edu.cn>
To: <manet@ietf.org>
Date: Tue, 26 Mar 2002 12:43:23 +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.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id XAA10300
Subject: [manet] About IEEE802.11 model in OPNET
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C ?
I encounter a strange problem when I make the following simulation using OPNET:
--------------
WLAN Scenarios 1:
Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
each node random selects a destination and transmits some packets.

WLAN Scenarios 2:
Same configured as the above Scenarios 1 except that the number of 
nodes is twenty.
--------------
I have expected that one node's throughput in Scenarios 2 should
much lower than that in Scenarios 1. But the simulation results
show that the throughput of each node is as same as that in 
Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.

Could any one tell me why the nodes in Scenarios 2 don't make 
interference to each other. 

Thanks a lot.

Sincerely, 
aaron


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


From daemon@optimus.ietf.org  Tue Mar 26 00:15:44 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16316
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 00:15:44 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA18154
	for manet-archive@odin.ietf.org; Tue, 26 Mar 2002 00:15:45 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA10334;
	Mon, 25 Mar 2002 23:43:25 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA10299
	for <manet@optimus.ietf.org>; Mon, 25 Mar 2002 23:43:22 -0500 (EST)
Received: from sjtu.edu.cn ([202.120.2.106])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15870
	for <manet@ietf.org>; Mon, 25 Mar 2002 23:43:15 -0500 (EST)
Received: from aaron (unknown [202.120.3.109])
	by sjtu.edu.cn (WorldPost) with SMTP id 72E32FE7
	for <manet@ietf.org>; Tue, 26 Mar 2002 12:43:20 +0800 (BEIST)
Message-ID: <001b01c1d480$c2f3bb20$6d0378ca@aaron>
From: "danaus" <licheng@sjtu.edu.cn>
To: <manet@ietf.org>
Date: Tue, 26 Mar 2002 12:43:23 +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.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id XAA10300
Subject: [manet] About IEEE802.11 model in OPNET
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C ?
I encounter a strange problem when I make the following simulation using OPNET:
--------------
WLAN Scenarios 1:
Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
each node random selects a destination and transmits some packets.

WLAN Scenarios 2:
Same configured as the above Scenarios 1 except that the number of 
nodes is twenty.
--------------
I have expected that one node's throughput in Scenarios 2 should
much lower than that in Scenarios 1. But the simulation results
show that the throughput of each node is as same as that in 
Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.

Could any one tell me why the nodes in Scenarios 2 don't make 
interference to each other. 

Thanks a lot.

Sincerely, 
aaron


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



From manet-admin@ietf.org  Tue Mar 26 00:35:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17036
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 00:35:06 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA15980;
	Tue, 26 Mar 2002 00:06:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA15942
	for <manet@optimus.ietf.org>; Tue, 26 Mar 2002 00:06:53 -0500 (EST)
Received: from pimout4-int.prodigy.net (pimout4-ext.prodigy.net [207.115.63.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16217
	for <manet@ietf.org>; Tue, 26 Mar 2002 00:06:52 -0500 (EST)
Received: from uta.edu (adsl-65-65-9-79.dsl.eulstx.swbell.net [65.65.9.79])
	by pimout4-int.prodigy.net (8.11.0/8.11.0) with ESMTP id g2Q56qI24764
	for <manet@ietf.org>; Tue, 26 Mar 2002 00:06:52 -0500
Message-ID: <3CA001E2.B589063@uta.edu>
Date: Mon, 25 Mar 2002 23:06:43 -0600
From: Gergely Zaruba <zaruba@uta.edu>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "'manet@ietf.org'" <manet@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] CfP Wireless LAn/PAN minitrack at HICSS-36
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear Colleagues,

(We apologize if you receive multiple copies.)
Please feel free to distribute the below CfP
among colleagues, interested parties, and related lists.

Best Regards,
Sajal Das, Gergely Zaruba and Kalyan Basu

====================================================================
                          CALL FOR PAPERS

                       HICSS-36 Minitrack on

                      WIRELESS LANs AND PANs

               http://crystal.uta.edu/~zaruba/hicss36/

               Part of the Software Technology Track
                       Thirty-sixth Annual
          HAWAI'I INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES
                       January 6 - 9, 2003,
          Hilton Waikoloa Village on the Big Island of Hawaii

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

   Abstracts due:   March 31, 2002
   Full Papers due: June 1, 2002

=====================================================================


Minitrack Co-Chairs and Technical Committee

* Sajal K. Das
* Gergely V. Zaruba
* Kalyan Basu

    Center for Research in Wireless Mobility and Networking (CReWMaN)
    Department of Computer Science and Engineering (CSE@UTA)
    The University of Texas at Arlington
    Email: {das,zaruba,basu}@cse.uta.edu

Overview:
In the past quarter century we have seen the rollout of three
generations of wireless cellular systems attracting end-users by
providing efficient mobile communications. On another front wireless
technology became an important component in providing networking
infrastructure for localized data delivery. This later revolution was
made possible by the induction of new networking technologies and
paradigms, such as wireless local area networks (WLAN) and wireless
personal area networks (WPAN).

Wireless personal area networks (WPANs) are short to very short-range
(from a couple centimeters to a couple of meters) wireless networks
that can be used to exchange information between devices in the reach
of a person. WPANs can be used to replace cables between computers
and their peripherals, to establish communities helping people do
their everyday chores making them more productive, or to establish
location aware services. Wireless local area networks (WLANs) on the
other hand provide with a larger transmission range. Although WLAN
equipment usually carries the capability to be set up for ad hoc
networking, the premier choice of deployment is yet a cellular like
infrastructure mode to interface wireless users with the Internet.

The best example representing WPANs is the recent industry standard:
Bluetooth, other examples include Spike (for real time gaming -
proprietary technology), and in the broad sense HomeRF. The IEEE 802
committee has also realized the importance of short-range wireless
networking and initiated the establishment of the IEEE 802.15 working
group to standardize protocols and interfaces for wireless personal
area networking. For WLANs the most well known representatives are
based on the standards IEEE802.11 and HiperLAN with all their
different variations.

One key issue of the feasibility of WPANs is the cost of the chips
enabling the actual wireless data transfer. Companies developing
Bluetooth chips claim, that in the near future complex one-chip
solutions of the Bluetooth specification will be available in the $5
price range. With this target price it is predicted that not only
will most PDAs, phones, laptops include such technology but that the
number of small WPAN enabled devices (e.g., pens, cameras, headsets,
various sensors) will soon outnumber the computers on the Internet.

Another key issue is the inter-working of wireless technologies to
create heterogeneous wireless networks. For instance, WPANs and WLANs
will enable an extension of the third generation (3G) cellular
networks (i.e., UMTS and cdma2000) into devices without direct
cellular access. Moreover, devices interconnected in a WPAN may be
able to utilize a combination of 3G access and WLAN access by
selecting the access that is best for the moment. In such networks
3G, WLAN and WPAN technologies do not compete against each other but
enable the user to select the best connectivity for his/her purposes.

We expect that the availability of a cheap short-range wireless
technology will further fuel research and development in what, where
and most importantly how WLAN and WPAN technologies could be used
for.


Scope:
The minitrack will concentrate on completed or ongoing research in
the area of wireless local area networking and wireless personal area
networking (excluding manufacturing). Areas of interest include but
are not limited to research in:
  * QoS provisioning in WLANs and WPANs
  * TCP performance of WLANs and WPANs
  * Bluetooth for ad hoc networks (scatternets)
  * IP over Bluetooth
  * Bluetooth performance evaluation
  * Routing in Bluetooth scatternets
  * Security issues of WPANs and WLANs
  * Mobility management and seamless integration of WLANs and PANs
  * Heterogeneous wireless infrastructures employing WLANS
    and/or WPANs
  * Interoperability, interference and co-existence issues
  * WPANs vs. WLANs
  * Protocols tailored to WLANs and WPANs
  * Caching in WLANs and WPANs
  * Service discovery using WLANs and WPANs


Important Deadlines in 2002:
  * March 31, 2002 Abstracts submitted for guidance and indication of
    appropriate content.
  * June 1, 2002 Full papers submitted to Minitrack Chairs.
    Contact minitrack chairs for submission instructions.
  * August 31, 2002 Notice of acceptance or rejections of papers sent
    to Authors by Minitrack Chairs.
  * October 1, 2002 Accepted manuscripts submitted electronically to
    the publisher of the conference proceedings. At least one author
    of each accepted paper must register to attend the conference by
    this date. Registration cancellations after this date may result
    in the paper being pulled from the Proceedings prior to printing.
    See conference web site for registration fee refund policy.

NOTE:
Because HICSS is a nonprofit activity funded entirely by registration
fees, all participants and speakers are expected to have their
university/organization bear the costs of their expenses and
registration. HICSS is not able to subsidize registrations or offer
reduced fees.


Instructions for the Authors:
1. Contact Gergely Zaruba in advance for specific submission
instructions. Otherwise, submit six (6) copies of the full paper,
consisting of 22-26 double- spaced pages, including diagrams,
directly to Gergely Zaruba. (NOTE: The final paper will be 10 pages,
double-column, single-spaced.)
2. Do not submit the manuscript to more than one Minitrack Chair.
Papers should contain original material and not be previously
published, or currently submitted for consideration elsewhere.
3. Each paper must have a title page to include title of the paper,
full name of all authors, and complete addresses including
affiliation(s), telephone number(s), and e-mail address(es).
4. The first page of the manuscript should include only the title and
a 300-word abstract of the paper.
5. Individuals interested in refereeing papers should contact the
minitrack chairs directly.
6. If you have more questions or want to find out more about other
minitracks in the track, please go to the Software Technology Track
homepage.


Other Useful Information:
  Tracks at HICSS-36
    * Collaboration Systems; Co-Chairs: Jay Nunamaker; Email:
      nunamaker@bpa.arizona.edu and Robert O. Briggs; Email:
      bbriggs@GroupSystems.com
    * Complex Systems; Chair: Robert Thomas; Email: rjt1@cornell.edu
    * Decision Tech. for Management; Chair: Dan Dolk; Email:
      dolker@redshift.com
    * Digital Documents and Media; Chair: Michael Shepherd; Email:
      shepherd@cs.dal.ca
    * Emerging Technologies; Co-Chairs Ralph H. Sprague; Email:
      sprague@hawaii.edu and Hesham El-Rewini; Email:
      rewini@engr.smu.edu
    * Information Technology in Health Care; Chair: William Chismar;
      Email: chismar@cba.hawaii.edu
    * Internet & the Digital Economy; Co-Chairs: David King; Email:
      dave@comshare.com and Alan Dennis; Email: ardennis@indiana.edu
    * Organizational Systems & Tech.; Chair: Hugh Watson; Email:
      hwatson@uga.edu
    * Software Technology; Chair: Hesham El-Rewini; Email:
      rewini@engr.smu.edu

  HICSS conferences are devoted to advances in the information,
  computer, and system sciences, and encompass developments in both
  theory and practice. Invited papers may be theoretical, conceptual,
  tutorial or descriptive in nature. Submissions undergo a peer
  referee process and those selected for presentation will be
  published in the Conference Proceedings. Submissions must not have
  been previously published. For the latest information visit the
  HICSS web site at:
  http://www.hicss.hawaii.edu

  Conference Administration
    * Ralph Sprague, Conference Chair
      Email: sprague@hawaii.edu
    * Eileen Dennis, Track Administrator
      Email: eidennis@indiana.edu
      Tel: 1-812-331-0551
      Fax: 1-812-331-0564
    * Sandra Laney, Conference Administrator
      Email: hicss@hawaii.edu
      Tel: 1-808-956-3251
      Fax: 1-808-956-5759

  2003 HICSS-36 Conference Venue
    Hilton Waikoloa Village on the Big Island of Hawaii
    425 Waikoloa Beach Drive
    Waikoloa, Hawaii 96738
    Tel: 1-808-886-1234
    Fax: 1-808-886-2900
    www.hiltonwaikoloavillage.com


--
***********************************************************
Gergely V. Zaruba Ph.D. C.S.                zaruba@ieee.org
Assistant Professor  Computer Science and Engineering Dept.
Center for Research in Wireless Mobility and Networking
The University of Texas at Arlington   phone:(817) 272 3602
***********************************************************



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


From daemon@optimus.ietf.org  Tue Mar 26 00:35:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17046
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 00:35:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id AAA22809
	for manet-archive@odin.ietf.org; Tue, 26 Mar 2002 00:35:07 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA15980;
	Tue, 26 Mar 2002 00:06:56 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id AAA15942
	for <manet@optimus.ietf.org>; Tue, 26 Mar 2002 00:06:53 -0500 (EST)
Received: from pimout4-int.prodigy.net (pimout4-ext.prodigy.net [207.115.63.103])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16217
	for <manet@ietf.org>; Tue, 26 Mar 2002 00:06:52 -0500 (EST)
Received: from uta.edu (adsl-65-65-9-79.dsl.eulstx.swbell.net [65.65.9.79])
	by pimout4-int.prodigy.net (8.11.0/8.11.0) with ESMTP id g2Q56qI24764
	for <manet@ietf.org>; Tue, 26 Mar 2002 00:06:52 -0500
Message-ID: <3CA001E2.B589063@uta.edu>
Date: Mon, 25 Mar 2002 23:06:43 -0600
From: Gergely Zaruba <zaruba@uta.edu>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "'manet@ietf.org'" <manet@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] CfP Wireless LAn/PAN minitrack at HICSS-36
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear Colleagues,

(We apologize if you receive multiple copies.)
Please feel free to distribute the below CfP
among colleagues, interested parties, and related lists.

Best Regards,
Sajal Das, Gergely Zaruba and Kalyan Basu

====================================================================
                          CALL FOR PAPERS

                       HICSS-36 Minitrack on

                      WIRELESS LANs AND PANs

               http://crystal.uta.edu/~zaruba/hicss36/

               Part of the Software Technology Track
                       Thirty-sixth Annual
          HAWAI'I INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES
                       January 6 - 9, 2003,
          Hilton Waikoloa Village on the Big Island of Hawaii

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

   Abstracts due:   March 31, 2002
   Full Papers due: June 1, 2002

=====================================================================


Minitrack Co-Chairs and Technical Committee

* Sajal K. Das
* Gergely V. Zaruba
* Kalyan Basu

    Center for Research in Wireless Mobility and Networking (CReWMaN)
    Department of Computer Science and Engineering (CSE@UTA)
    The University of Texas at Arlington
    Email: {das,zaruba,basu}@cse.uta.edu

Overview:
In the past quarter century we have seen the rollout of three
generations of wireless cellular systems attracting end-users by
providing efficient mobile communications. On another front wireless
technology became an important component in providing networking
infrastructure for localized data delivery. This later revolution was
made possible by the induction of new networking technologies and
paradigms, such as wireless local area networks (WLAN) and wireless
personal area networks (WPAN).

Wireless personal area networks (WPANs) are short to very short-range
(from a couple centimeters to a couple of meters) wireless networks
that can be used to exchange information between devices in the reach
of a person. WPANs can be used to replace cables between computers
and their peripherals, to establish communities helping people do
their everyday chores making them more productive, or to establish
location aware services. Wireless local area networks (WLANs) on the
other hand provide with a larger transmission range. Although WLAN
equipment usually carries the capability to be set up for ad hoc
networking, the premier choice of deployment is yet a cellular like
infrastructure mode to interface wireless users with the Internet.

The best example representing WPANs is the recent industry standard:
Bluetooth, other examples include Spike (for real time gaming -
proprietary technology), and in the broad sense HomeRF. The IEEE 802
committee has also realized the importance of short-range wireless
networking and initiated the establishment of the IEEE 802.15 working
group to standardize protocols and interfaces for wireless personal
area networking. For WLANs the most well known representatives are
based on the standards IEEE802.11 and HiperLAN with all their
different variations.

One key issue of the feasibility of WPANs is the cost of the chips
enabling the actual wireless data transfer. Companies developing
Bluetooth chips claim, that in the near future complex one-chip
solutions of the Bluetooth specification will be available in the $5
price range. With this target price it is predicted that not only
will most PDAs, phones, laptops include such technology but that the
number of small WPAN enabled devices (e.g., pens, cameras, headsets,
various sensors) will soon outnumber the computers on the Internet.

Another key issue is the inter-working of wireless technologies to
create heterogeneous wireless networks. For instance, WPANs and WLANs
will enable an extension of the third generation (3G) cellular
networks (i.e., UMTS and cdma2000) into devices without direct
cellular access. Moreover, devices interconnected in a WPAN may be
able to utilize a combination of 3G access and WLAN access by
selecting the access that is best for the moment. In such networks
3G, WLAN and WPAN technologies do not compete against each other but
enable the user to select the best connectivity for his/her purposes.

We expect that the availability of a cheap short-range wireless
technology will further fuel research and development in what, where
and most importantly how WLAN and WPAN technologies could be used
for.


Scope:
The minitrack will concentrate on completed or ongoing research in
the area of wireless local area networking and wireless personal area
networking (excluding manufacturing). Areas of interest include but
are not limited to research in:
  * QoS provisioning in WLANs and WPANs
  * TCP performance of WLANs and WPANs
  * Bluetooth for ad hoc networks (scatternets)
  * IP over Bluetooth
  * Bluetooth performance evaluation
  * Routing in Bluetooth scatternets
  * Security issues of WPANs and WLANs
  * Mobility management and seamless integration of WLANs and PANs
  * Heterogeneous wireless infrastructures employing WLANS
    and/or WPANs
  * Interoperability, interference and co-existence issues
  * WPANs vs. WLANs
  * Protocols tailored to WLANs and WPANs
  * Caching in WLANs and WPANs
  * Service discovery using WLANs and WPANs


Important Deadlines in 2002:
  * March 31, 2002 Abstracts submitted for guidance and indication of
    appropriate content.
  * June 1, 2002 Full papers submitted to Minitrack Chairs.
    Contact minitrack chairs for submission instructions.
  * August 31, 2002 Notice of acceptance or rejections of papers sent
    to Authors by Minitrack Chairs.
  * October 1, 2002 Accepted manuscripts submitted electronically to
    the publisher of the conference proceedings. At least one author
    of each accepted paper must register to attend the conference by
    this date. Registration cancellations after this date may result
    in the paper being pulled from the Proceedings prior to printing.
    See conference web site for registration fee refund policy.

NOTE:
Because HICSS is a nonprofit activity funded entirely by registration
fees, all participants and speakers are expected to have their
university/organization bear the costs of their expenses and
registration. HICSS is not able to subsidize registrations or offer
reduced fees.


Instructions for the Authors:
1. Contact Gergely Zaruba in advance for specific submission
instructions. Otherwise, submit six (6) copies of the full paper,
consisting of 22-26 double- spaced pages, including diagrams,
directly to Gergely Zaruba. (NOTE: The final paper will be 10 pages,
double-column, single-spaced.)
2. Do not submit the manuscript to more than one Minitrack Chair.
Papers should contain original material and not be previously
published, or currently submitted for consideration elsewhere.
3. Each paper must have a title page to include title of the paper,
full name of all authors, and complete addresses including
affiliation(s), telephone number(s), and e-mail address(es).
4. The first page of the manuscript should include only the title and
a 300-word abstract of the paper.
5. Individuals interested in refereeing papers should contact the
minitrack chairs directly.
6. If you have more questions or want to find out more about other
minitracks in the track, please go to the Software Technology Track
homepage.


Other Useful Information:
  Tracks at HICSS-36
    * Collaboration Systems; Co-Chairs: Jay Nunamaker; Email:
      nunamaker@bpa.arizona.edu and Robert O. Briggs; Email:
      bbriggs@GroupSystems.com
    * Complex Systems; Chair: Robert Thomas; Email: rjt1@cornell.edu
    * Decision Tech. for Management; Chair: Dan Dolk; Email:
      dolker@redshift.com
    * Digital Documents and Media; Chair: Michael Shepherd; Email:
      shepherd@cs.dal.ca
    * Emerging Technologies; Co-Chairs Ralph H. Sprague; Email:
      sprague@hawaii.edu and Hesham El-Rewini; Email:
      rewini@engr.smu.edu
    * Information Technology in Health Care; Chair: William Chismar;
      Email: chismar@cba.hawaii.edu
    * Internet & the Digital Economy; Co-Chairs: David King; Email:
      dave@comshare.com and Alan Dennis; Email: ardennis@indiana.edu
    * Organizational Systems & Tech.; Chair: Hugh Watson; Email:
      hwatson@uga.edu
    * Software Technology; Chair: Hesham El-Rewini; Email:
      rewini@engr.smu.edu

  HICSS conferences are devoted to advances in the information,
  computer, and system sciences, and encompass developments in both
  theory and practice. Invited papers may be theoretical, conceptual,
  tutorial or descriptive in nature. Submissions undergo a peer
  referee process and those selected for presentation will be
  published in the Conference Proceedings. Submissions must not have
  been previously published. For the latest information visit the
  HICSS web site at:
  http://www.hicss.hawaii.edu

  Conference Administration
    * Ralph Sprague, Conference Chair
      Email: sprague@hawaii.edu
    * Eileen Dennis, Track Administrator
      Email: eidennis@indiana.edu
      Tel: 1-812-331-0551
      Fax: 1-812-331-0564
    * Sandra Laney, Conference Administrator
      Email: hicss@hawaii.edu
      Tel: 1-808-956-3251
      Fax: 1-808-956-5759

  2003 HICSS-36 Conference Venue
    Hilton Waikoloa Village on the Big Island of Hawaii
    425 Waikoloa Beach Drive
    Waikoloa, Hawaii 96738
    Tel: 1-808-886-1234
    Fax: 1-808-886-2900
    www.hiltonwaikoloavillage.com


--
***********************************************************
Gergely V. Zaruba Ph.D. C.S.                zaruba@ieee.org
Assistant Professor  Computer Science and Engineering Dept.
Center for Research in Wireless Mobility and Networking
The University of Texas at Arlington   phone:(817) 272 3602
***********************************************************



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



From manet-admin@ietf.org  Tue Mar 26 09:13:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03681
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 09:13:37 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21154;
	Tue, 26 Mar 2002 08:53:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21114
	for <manet@optimus.ietf.org>; Tue, 26 Mar 2002 08:53:31 -0500 (EST)
Received: from smtp.web.de (smtp02.web.de [217.72.192.151])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02886
	for <manet@ietf.org>; Tue, 26 Mar 2002 08:53:29 -0500 (EST)
Received: from [217.83.9.78] (helo=navayo)
	by smtp.web.de with esmtp (WEB.DE(Exim) 4.43 #44)
	id 16prNk-00081B-00
	for manet@ietf.org; Tue, 26 Mar 2002 14:53:00 +0100
Content-Type: text/plain;
  charset="us-ascii"
From: Frank Dinies <FrankDinies@web.de>
To: manet@ietf.org
Date: Tue, 26 Mar 2002 14:54:27 +0100
X-Mailer: KMail [version 1.4]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200203261454.27973.FrankDinies@web.de>
Content-Transfer-Encoding: 8bit
Subject: [manet] Manet Simulations
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

I just implemented Fisheye-State-Routing uner OMNeT++. OMNeT++ is a freely 
available network simulation enviroment from the Technical University of 
Budapest. There is an ad-hoc-enviroment already implemented, in which every 
kind of ad-hoc-routing-algorithm can be insert. FSR is one of the first 
implented ones in this enviroment. It would be nice to include more for 
comparison reasons. 
So, to my question:
is there anybody out there, willing to include more, for example TORA or  
AODV. I would be very pleased to hear from you !

Regards

Frank Dinies

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


From daemon@optimus.ietf.org  Tue Mar 26 09:13:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03690
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 09:13:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA26706
	for manet-archive@odin.ietf.org; Tue, 26 Mar 2002 09:13:39 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21154;
	Tue, 26 Mar 2002 08:53:35 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21114
	for <manet@optimus.ietf.org>; Tue, 26 Mar 2002 08:53:31 -0500 (EST)
Received: from smtp.web.de (smtp02.web.de [217.72.192.151])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02886
	for <manet@ietf.org>; Tue, 26 Mar 2002 08:53:29 -0500 (EST)
Received: from [217.83.9.78] (helo=navayo)
	by smtp.web.de with esmtp (WEB.DE(Exim) 4.43 #44)
	id 16prNk-00081B-00
	for manet@ietf.org; Tue, 26 Mar 2002 14:53:00 +0100
Content-Type: text/plain;
  charset="us-ascii"
From: Frank Dinies <FrankDinies@web.de>
To: manet@ietf.org
Date: Tue, 26 Mar 2002 14:54:27 +0100
X-Mailer: KMail [version 1.4]
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <200203261454.27973.FrankDinies@web.de>
Content-Transfer-Encoding: 8bit
Subject: [manet] Manet Simulations
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

I just implemented Fisheye-State-Routing uner OMNeT++. OMNeT++ is a freely 
available network simulation enviroment from the Technical University of 
Budapest. There is an ad-hoc-enviroment already implemented, in which every 
kind of ad-hoc-routing-algorithm can be insert. FSR is one of the first 
implented ones in this enviroment. It would be nice to include more for 
comparison reasons. 
So, to my question:
is there anybody out there, willing to include more, for example TORA or  
AODV. I would be very pleased to hear from you !

Regards

Frank Dinies

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



From manet-admin@ietf.org  Tue Mar 26 10:31:06 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06758
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 10:31:06 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11747;
	Tue, 26 Mar 2002 10:09:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11659
	for <manet@optimus.ietf.org>; Tue, 26 Mar 2002 10:09:39 -0500 (EST)
Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05492
	for <manet@ietf.org>; Tue, 26 Mar 2002 10:09:36 -0500 (EST)
From: haas@ece.cornell.edu
Received: from verdi.ee.cornell.edu (verdi.ee.cornell.edu [128.84.240.71])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id g2QF9bX16138;
	Tue, 26 Mar 2002 10:09:37 -0500
Date: Tue, 26 Mar 2002 10:09:33 -0500 (EST)
X-Sender: haas@verdi.ee.cornell.edu
To: Frank Dinies <FrankDinies@web.de>
cc: manet@ietf.org
Subject: Re: [manet] Manet Simulations
In-Reply-To: <200203261454.27973.FrankDinies@web.de>
Message-ID: <Pine.GSO.4.05.10203261008370.10041-100000@verdi.ee.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi Frank,

We will be implementing the ZRP protocol in OMNeT++.

Zygmunt.
==--==-====
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Prof. Zygmunt J. Haas                    http://people.ece.cornell.edu/haas 
Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
School of Electrical Engineering         
Cornell University			 tel: +1-607-255-3454
323 Frank Rhodes Hall			 fax: +1-607-255-9072
Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
U.S.A                             
	WNL web page: http://wnl.ece.cornell.edu
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

On Tue, 26 Mar 2002, Frank Dinies wrote:

> Hi,
> 
> I just implemented Fisheye-State-Routing uner OMNeT++. OMNeT++ is a freely 
> available network simulation enviroment from the Technical University of 
> Budapest. There is an ad-hoc-enviroment already implemented, in which every 
> kind of ad-hoc-routing-algorithm can be insert. FSR is one of the first 
> implented ones in this enviroment. It would be nice to include more for 
> comparison reasons. 
> So, to my question:
> is there anybody out there, willing to include more, for example TORA or  
> AODV. I would be very pleased to hear from you !
> 
> Regards
> 
> Frank Dinies
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 


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


From daemon@optimus.ietf.org  Tue Mar 26 10:31:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06767
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 10:31:07 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id KAA18435
	for manet-archive@odin.ietf.org; Tue, 26 Mar 2002 10:31:09 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11747;
	Tue, 26 Mar 2002 10:09:43 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11659
	for <manet@optimus.ietf.org>; Tue, 26 Mar 2002 10:09:39 -0500 (EST)
Received: from memphis.ece.cornell.edu (memphis.ece.cornell.edu [128.84.81.8])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05492
	for <manet@ietf.org>; Tue, 26 Mar 2002 10:09:36 -0500 (EST)
From: haas@ece.cornell.edu
Received: from verdi.ee.cornell.edu (verdi.ee.cornell.edu [128.84.240.71])
	by memphis.ece.cornell.edu (8.11.6/8.11.2) with ESMTP id g2QF9bX16138;
	Tue, 26 Mar 2002 10:09:37 -0500
Date: Tue, 26 Mar 2002 10:09:33 -0500 (EST)
X-Sender: haas@verdi.ee.cornell.edu
To: Frank Dinies <FrankDinies@web.de>
cc: manet@ietf.org
Subject: Re: [manet] Manet Simulations
In-Reply-To: <200203261454.27973.FrankDinies@web.de>
Message-ID: <Pine.GSO.4.05.10203261008370.10041-100000@verdi.ee.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi Frank,

We will be implementing the ZRP protocol in OMNeT++.

Zygmunt.
==--==-====
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Prof. Zygmunt J. Haas                    http://people.ece.cornell.edu/haas 
Wireless Networks Laboratory		 http://wnl.ece.cornell.edu
School of Electrical Engineering         
Cornell University			 tel: +1-607-255-3454
323 Frank Rhodes Hall			 fax: +1-607-255-9072
Ithaca, NY 14853			 e-mail: haas@ece.cornell.edu
U.S.A                             
	WNL web page: http://wnl.ece.cornell.edu
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

On Tue, 26 Mar 2002, Frank Dinies wrote:

> Hi,
> 
> I just implemented Fisheye-State-Routing uner OMNeT++. OMNeT++ is a freely 
> available network simulation enviroment from the Technical University of 
> Budapest. There is an ad-hoc-enviroment already implemented, in which every 
> kind of ad-hoc-routing-algorithm can be insert. FSR is one of the first 
> implented ones in this enviroment. It would be nice to include more for 
> comparison reasons. 
> So, to my question:
> is there anybody out there, willing to include more, for example TORA or  
> AODV. I would be very pleased to hear from you !
> 
> Regards
> 
> Frank Dinies
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 


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



From manet-admin@ietf.org  Tue Mar 26 16:43:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26347
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 16:43:26 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27581;
	Tue, 26 Mar 2002 16:22:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27553
	for <manet@ns.ietf.org>; Tue, 26 Mar 2002 16:22:14 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24741
	for <manet@ietf.org>; Tue, 26 Mar 2002 16:22:09 -0500 (EST)
Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2QLMBI47167
	for <manet@ietf.org>; Tue, 26 Mar 2002 16:22:11 -0500 (EST)
Received: from ecpe15 ([208.17.194.151])
	by vivi.cc.vt.edu (Mirapoint)
	with SMTP id ANZ05346;
	Tue, 26 Mar 2002 16:22:10 -0500 (EST)
Message-ID: <001a01c1d50d$3034c3a0$97c211d0@ecpe15>
Reply-To: "Vikram Dham" <vdham@vt.edu>
From: "Vikram Dham" <vdham@vt.edu>
To: <manet@ietf.org>
References: <001b01c1d480$c2f3bb20$6d0378ca@aaron>
Subject: Re: [manet] About IEEE802.11 model in OPNET
Date: Tue, 26 Mar 2002 16:28:35 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Hi Aaaron,

I  have been using OPNET's 802.11 model for simulating manet scenarios. Make
sure that you are correctly setting the value of the range attribute.


Regards

Vikram Dham
----- Original Message -----
From: "danaus" <licheng@sjtu.edu.cn>
To: <manet@ietf.org>
Sent: Monday, March 25, 2002 11:43 PM
Subject: [manet] About IEEE802.11 model in OPNET


> Hi,
>
> Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C ?
> I encounter a strange problem when I make the following simulation using
OPNET:
> --------------
> WLAN Scenarios 1:
> Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> each node random selects a destination and transmits some packets.
>
> WLAN Scenarios 2:
> Same configured as the above Scenarios 1 except that the number of
> nodes is twenty.
> --------------
> I have expected that one node's throughput in Scenarios 2 should
> much lower than that in Scenarios 1. But the simulation results
> show that the throughput of each node is as same as that in
> Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
>
> Could any one tell me why the nodes in Scenarios 2 don't make
> interference to each other.
>
> Thanks a lot.
>
> Sincerely,
> aaron
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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


From daemon@ns.ietf.org  Tue Mar 26 16:43:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26356
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 16:43:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA04537
	for manet-archive@odin.ietf.org; Tue, 26 Mar 2002 16:43:30 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27581;
	Tue, 26 Mar 2002 16:22:17 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA27553
	for <manet@ns.ietf.org>; Tue, 26 Mar 2002 16:22:14 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24741
	for <manet@ietf.org>; Tue, 26 Mar 2002 16:22:09 -0500 (EST)
Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2QLMBI47167
	for <manet@ietf.org>; Tue, 26 Mar 2002 16:22:11 -0500 (EST)
Received: from ecpe15 ([208.17.194.151])
	by vivi.cc.vt.edu (Mirapoint)
	with SMTP id ANZ05346;
	Tue, 26 Mar 2002 16:22:10 -0500 (EST)
Message-ID: <001a01c1d50d$3034c3a0$97c211d0@ecpe15>
Reply-To: "Vikram Dham" <vdham@vt.edu>
From: "Vikram Dham" <vdham@vt.edu>
To: <manet@ietf.org>
References: <001b01c1d480$c2f3bb20$6d0378ca@aaron>
Subject: Re: [manet] About IEEE802.11 model in OPNET
Date: Tue, 26 Mar 2002 16:28:35 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Hi Aaaron,

I  have been using OPNET's 802.11 model for simulating manet scenarios. Make
sure that you are correctly setting the value of the range attribute.


Regards

Vikram Dham
----- Original Message -----
From: "danaus" <licheng@sjtu.edu.cn>
To: <manet@ietf.org>
Sent: Monday, March 25, 2002 11:43 PM
Subject: [manet] About IEEE802.11 model in OPNET


> Hi,
>
> Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C ?
> I encounter a strange problem when I make the following simulation using
OPNET:
> --------------
> WLAN Scenarios 1:
> Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> each node random selects a destination and transmits some packets.
>
> WLAN Scenarios 2:
> Same configured as the above Scenarios 1 except that the number of
> nodes is twenty.
> --------------
> I have expected that one node's throughput in Scenarios 2 should
> much lower than that in Scenarios 1. But the simulation results
> show that the throughput of each node is as same as that in
> Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
>
> Could any one tell me why the nodes in Scenarios 2 don't make
> interference to each other.
>
> Thanks a lot.
>
> Sincerely,
> aaron
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Tue Mar 26 16:54:51 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26699
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 16:54:51 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA02040;
	Tue, 26 Mar 2002 16:36:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA01916
	for <manet@ns.ietf.org>; Tue, 26 Mar 2002 16:36:15 -0500 (EST)
Received: from email.nist.gov (email.nist.gov [129.6.2.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25693
	for <manet@ietf.org>; Tue, 26 Mar 2002 16:35:49 -0500 (EST)
Received: from antd.nist.gov (stratus.antd.nist.gov [129.6.50.8])
	by email.nist.gov (8.12.2/8.12.2) with ESMTP id g2QLZoCR009206;
	Tue, 26 Mar 2002 16:35:50 -0500 (EST)
Message-ID: <3CA0E9D9.93DBD769@antd.nist.gov>
Date: Tue, 26 Mar 2002 16:36:25 -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: danaus <licheng@sjtu.edu.cn>
CC: manet@ietf.org
Subject: Re: [manet] About IEEE802.11 model in OPNET
References: <001b01c1d480$c2f3bb20$6d0378ca@aaron>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Aaron,

You say nothing about the packet rate!!  It is entirely possible that 20
or more nodes can operate in a WLAN up to a certain level of traffic.

Regards,
L. E. Miller

danaus wrote:
> 
> Hi,
> 
> Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C ?
> I encounter a strange problem when I make the following simulation using OPNET:
> --------------
> WLAN Scenarios 1:
> Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> each node random selects a destination and transmits some packets.
> 
> WLAN Scenarios 2:
> Same configured as the above Scenarios 1 except that the number of
> nodes is twenty.
> --------------
> I have expected that one node's throughput in Scenarios 2 should
> much lower than that in Scenarios 1. But the simulation results
> show that the throughput of each node is as same as that in
> Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> 
> Could any one tell me why the nodes in Scenarios 2 don't make
> interference to each other.
> 
> Thanks a lot.
> 
> Sincerely,
> aaron
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

-- 

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

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, LenMiller42@cs.com
http://w3.antd.nist.gov/wctg/
._ _. ._ ._.. _.__ ... .. ...   ._ _. _..  ... .. __ .._
._.. ._ _ .. ___ _. ___...   .__ .. ._. . ._.. . ... ...

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


From daemon@ns.ietf.org  Tue Mar 26 16:54:53 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26708
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 16:54:51 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA07468
	for manet-archive@odin.ietf.org; Tue, 26 Mar 2002 16:54:55 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA02040;
	Tue, 26 Mar 2002 16:36:22 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA01916
	for <manet@ns.ietf.org>; Tue, 26 Mar 2002 16:36:15 -0500 (EST)
Received: from email.nist.gov (email.nist.gov [129.6.2.7])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25693
	for <manet@ietf.org>; Tue, 26 Mar 2002 16:35:49 -0500 (EST)
Received: from antd.nist.gov (stratus.antd.nist.gov [129.6.50.8])
	by email.nist.gov (8.12.2/8.12.2) with ESMTP id g2QLZoCR009206;
	Tue, 26 Mar 2002 16:35:50 -0500 (EST)
Message-ID: <3CA0E9D9.93DBD769@antd.nist.gov>
Date: Tue, 26 Mar 2002 16:36:25 -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: danaus <licheng@sjtu.edu.cn>
CC: manet@ietf.org
Subject: Re: [manet] About IEEE802.11 model in OPNET
References: <001b01c1d480$c2f3bb20$6d0378ca@aaron>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Aaron,

You say nothing about the packet rate!!  It is entirely possible that 20
or more nodes can operate in a WLAN up to a certain level of traffic.

Regards,
L. E. Miller

danaus wrote:
> 
> Hi,
> 
> Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C ?
> I encounter a strange problem when I make the following simulation using OPNET:
> --------------
> WLAN Scenarios 1:
> Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> each node random selects a destination and transmits some packets.
> 
> WLAN Scenarios 2:
> Same configured as the above Scenarios 1 except that the number of
> nodes is twenty.
> --------------
> I have expected that one node's throughput in Scenarios 2 should
> much lower than that in Scenarios 1. But the simulation results
> show that the throughput of each node is as same as that in
> Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> 
> Could any one tell me why the nodes in Scenarios 2 don't make
> interference to each other.
> 
> Thanks a lot.
> 
> Sincerely,
> aaron
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

-- 

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

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, LenMiller42@cs.com
http://w3.antd.nist.gov/wctg/
._ _. ._ ._.. _.__ ... .. ...   ._ _. _..  ... .. __ .._
._.. ._ _ .. ___ _. ___...   .__ .. ._. . ._.. . ... ...

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



From manet-admin@ietf.org  Tue Mar 26 20:02:32 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01772
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 20:02:32 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA20654;
	Tue, 26 Mar 2002 19:40:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA20600
	for <manet@ns.ietf.org>; Tue, 26 Mar 2002 19:40:25 -0500 (EST)
Received: from ns0.utdallas.edu (ns0.utdallas.edu [129.110.10.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01293
	for <manet@ietf.org>; Tue, 26 Mar 2002 19:40:23 -0500 (EST)
Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9])
	by ns0.utdallas.edu (Postfix) with ESMTP
	id 91B971A08E9; Tue, 26 Mar 2002 18:40:25 -0600 (CST)
Received: by apache.utdallas.edu (Postfix, from userid 30546)
	id 2AB262235D; Tue, 26 Mar 2002 18:40:19 -0600 (CST)
Received: from localhost (localhost [127.0.0.1])
	by apache.utdallas.edu (Postfix) with ESMTP
	id 1EFE8222E5; Tue, 26 Mar 2002 18:40:19 -0600 (CST)
Date: Tue, 26 Mar 2002 18:40:19 -0600 (CST)
From: Rajesh Bhairampally <rajesh@utdallas.edu>
To: danaus <licheng@sjtu.edu.cn>
Cc: manet@ietf.org
Subject: Re: [manet] About IEEE802.11 model in OPNET
In-Reply-To: <001b01c1d480$c2f3bb20$6d0378ca@aaron>
Message-ID: <Pine.GSO.4.21.0203261834160.16852-100000@apache.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

if i am not wrong, Opnet WLAN defines throughput as "total number of bits
(in bits/sec) forwarded from wireless LAN layers to higher layers". so, it
is possible that all the stations eventually get access to media and
transfer their data. So, i think it is entairely possible that throughput
be same in both the cases.

to really look into the affect of additional stations, you can look into
other statistics such as  media access delay, number of backoffslots,
end-end dealy, -may be- control traffic exchanged b/n nodes. this may give
you a feel of how other stations are contending for media.

hth,
Rajesh


On Tue, 26 Mar 2002, danaus wrote:

> Hi,
> 
> Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C ?
> I encounter a strange problem when I make the following simulation using OPNET:
> --------------
> WLAN Scenarios 1:
> Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> each node random selects a destination and transmits some packets.
> 
> WLAN Scenarios 2:
> Same configured as the above Scenarios 1 except that the number of 
> nodes is twenty.
> --------------
> I have expected that one node's throughput in Scenarios 2 should
> much lower than that in Scenarios 1. But the simulation results
> show that the throughput of each node is as same as that in 
> Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> 
> Could any one tell me why the nodes in Scenarios 2 don't make 
> interference to each other. 
> 
> Thanks a lot.
> 
> Sincerely, 
> aaron
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

Rajesh


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


From daemon@ns.ietf.org  Tue Mar 26 20:02:33 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01783
	for <manet-archive@odin.ietf.org>; Tue, 26 Mar 2002 20:02:33 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id UAA26670
	for manet-archive@odin.ietf.org; Tue, 26 Mar 2002 20:02:34 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA20654;
	Tue, 26 Mar 2002 19:40:29 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA20600
	for <manet@ns.ietf.org>; Tue, 26 Mar 2002 19:40:25 -0500 (EST)
Received: from ns0.utdallas.edu (ns0.utdallas.edu [129.110.10.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01293
	for <manet@ietf.org>; Tue, 26 Mar 2002 19:40:23 -0500 (EST)
Received: from apache.utdallas.edu (apache.utdallas.edu [129.110.16.9])
	by ns0.utdallas.edu (Postfix) with ESMTP
	id 91B971A08E9; Tue, 26 Mar 2002 18:40:25 -0600 (CST)
Received: by apache.utdallas.edu (Postfix, from userid 30546)
	id 2AB262235D; Tue, 26 Mar 2002 18:40:19 -0600 (CST)
Received: from localhost (localhost [127.0.0.1])
	by apache.utdallas.edu (Postfix) with ESMTP
	id 1EFE8222E5; Tue, 26 Mar 2002 18:40:19 -0600 (CST)
Date: Tue, 26 Mar 2002 18:40:19 -0600 (CST)
From: Rajesh Bhairampally <rajesh@utdallas.edu>
To: danaus <licheng@sjtu.edu.cn>
Cc: manet@ietf.org
Subject: Re: [manet] About IEEE802.11 model in OPNET
In-Reply-To: <001b01c1d480$c2f3bb20$6d0378ca@aaron>
Message-ID: <Pine.GSO.4.21.0203261834160.16852-100000@apache.utdallas.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

if i am not wrong, Opnet WLAN defines throughput as "total number of bits
(in bits/sec) forwarded from wireless LAN layers to higher layers". so, it
is possible that all the stations eventually get access to media and
transfer their data. So, i think it is entairely possible that throughput
be same in both the cases.

to really look into the affect of additional stations, you can look into
other statistics such as  media access delay, number of backoffslots,
end-end dealy, -may be- control traffic exchanged b/n nodes. this may give
you a feel of how other stations are contending for media.

hth,
Rajesh


On Tue, 26 Mar 2002, danaus wrote:

> Hi,
> 
> Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C ?
> I encounter a strange problem when I make the following simulation using OPNET:
> --------------
> WLAN Scenarios 1:
> Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> each node random selects a destination and transmits some packets.
> 
> WLAN Scenarios 2:
> Same configured as the above Scenarios 1 except that the number of 
> nodes is twenty.
> --------------
> I have expected that one node's throughput in Scenarios 2 should
> much lower than that in Scenarios 1. But the simulation results
> show that the throughput of each node is as same as that in 
> Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> 
> Could any one tell me why the nodes in Scenarios 2 don't make 
> interference to each other. 
> 
> Thanks a lot.
> 
> Sincerely, 
> aaron
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet
> 

Rajesh


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



From manet-admin@ietf.org  Wed Mar 27 08:52:07 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27779
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 08:52:07 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27074;
	Wed, 27 Mar 2002 08:19:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27042
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 08:19:16 -0500 (EST)
Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26629
	for <manet@ietf.org>; Wed, 27 Mar 2002 08:19:14 -0500 (EST)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id g2RDIi826527
	for <manet@ietf.org>; Wed, 27 Mar 2002 08:18:44 -0500 (EST)
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id g2RDIhk24459
	for <manet@ietf.org>; Wed, 27 Mar 2002 08:18:43 -0500 (EST)
Received: from b-57-14.mitre.org (129.83.57.14) by mailhub1.mitre.org with SMTP
        id 9647430; Wed, 27 Mar 2002 08:18:38 -0500
Message-ID: <3CA1C6AF.27454D04@mitre.org>
Date: Wed, 27 Mar 2002 08:18:39 -0500
From: "Kevin H. Grace" <kgrace@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: MANET <manet@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] MobileMesh Opnet Model Availability
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Opnet simulation models of the MobileMesh Routing Protocol and
MobileMesh Link Discovery Protocol are now available from Opnet's
website:

 ftp://opguest:opguest@corporate7.opnet.com/433/

Included in this distribution are numerous modifications and bug fixes
to the 802.11 wireless LAN process model and related pipeline
stages. 

Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
distribution for more details.

Information about the MobileMesh protocols and Open Source Linux
distribution 
is available at:

 http://www.mitre.org/tech_transfer/mobilemesh/

-Kevin


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


From daemon@optimus.ietf.org  Wed Mar 27 08:52:08 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27788
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 08:52:08 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA05824
	for manet-archive@odin.ietf.org; Wed, 27 Mar 2002 08:52:09 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27074;
	Wed, 27 Mar 2002 08:19:19 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA27042
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 08:19:16 -0500 (EST)
Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26629
	for <manet@ietf.org>; Wed, 27 Mar 2002 08:19:14 -0500 (EST)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id g2RDIi826527
	for <manet@ietf.org>; Wed, 27 Mar 2002 08:18:44 -0500 (EST)
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id g2RDIhk24459
	for <manet@ietf.org>; Wed, 27 Mar 2002 08:18:43 -0500 (EST)
Received: from b-57-14.mitre.org (129.83.57.14) by mailhub1.mitre.org with SMTP
        id 9647430; Wed, 27 Mar 2002 08:18:38 -0500
Message-ID: <3CA1C6AF.27454D04@mitre.org>
Date: Wed, 27 Mar 2002 08:18:39 -0500
From: "Kevin H. Grace" <kgrace@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: MANET <manet@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [manet] MobileMesh Opnet Model Availability
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Opnet simulation models of the MobileMesh Routing Protocol and
MobileMesh Link Discovery Protocol are now available from Opnet's
website:

 ftp://opguest:opguest@corporate7.opnet.com/433/

Included in this distribution are numerous modifications and bug fixes
to the 802.11 wireless LAN process model and related pipeline
stages. 

Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
distribution for more details.

Information about the MobileMesh protocols and Open Source Linux
distribution 
is available at:

 http://www.mitre.org/tech_transfer/mobilemesh/

-Kevin


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



From manet-admin@ietf.org  Wed Mar 27 09:42:04 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00318
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 09:42:04 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12384;
	Wed, 27 Mar 2002 09:16:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12339
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 09:16:44 -0500 (EST)
Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28965
	for <manet@ietf.org>; Wed, 27 Mar 2002 09:16:41 -0500 (EST)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id g2RECJ809375;
	Wed, 27 Mar 2002 09:12:19 -0500 (EST)
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id g2RECHk07977;
	Wed, 27 Mar 2002 09:12:18 -0500 (EST)
Received: from dhcp-103-210.mitre.org (128.29.103.210) by mailhub1.mitre.org with SMTP
        id 9648890; Wed, 27 Mar 2002 09:12:10 -0500
Message-ID: <3CA1D33B.FE8476A6@mitre.org>
Date: Wed, 27 Mar 2002 09:12:11 -0500
From: John Stine <jstine@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: danaus <licheng@sjtu.edu.cn>
CC: manet@ietf.org
Subject: Re: [manet] About IEEE802.11 model in OPNET
References: <001b01c1d480$c2f3bb20$6d0378ca@aaron>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Opnet's wlan_mac and the support pipeline stages take some liberty in
modeling the physical layer based on the assumption that in the intended
network all nodes should be within range of each other.  As a result,
the model does not model interference correctly, but uses collisions
only as the cause of failure.  This is a severe problem when one is
studying ad hoc networking and wants to evaluate spatial reuse of the
channel.  Two nodes in a network cannot successfully transmit
simultaneously, despite separation distance.  We addressed this problem
in our modifications to OPNET's models for Kevin Grace's MobileMesh
protocols.  You should have received a message from Kevin about the
release of these models.  If you did not receive it, the text of Kevin's
message follows.

The OPNET models are for version 7.0.B but they are well documented so
with a little effort one can apply the changes to the 8.0.C version.  We
provided these models to OPNET and they have given us the indication
that they will incorporate our recommendations into a future release of
their product.

In the mean time, I would recommend anyone using the OPNET wlan_mac
model to study ad hoc networks to look at our observations and
recommendations. (See Readme-MobileMeshOpnet.pdf.)  Many conclusions
based on modeling in OPNET may need to be re-evaluated.

John

Kevin's message follows:

Opnet simulation models of the MobileMesh Routing Protocol and
MobileMesh Link Discovery Protocol are now available from Opnet's
website:

 ftp://opguest:opguest@corporate7.opnet.com/433/

Included in this distribution are numerous modifications and bug fixes
to the 802.11 wireless LAN process model and related pipeline
stages. 

Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
distribution for more details.

Information about the MobileMesh protocols and Open Source Linux
distribution 
is available at:

 http://www.mitre.org/tech_transfer/mobilemesh/

-Kevin 

danaus wrote:
> 
> Hi,
> 
> Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C ?
> I encounter a strange problem when I make the following simulation using OPNET:
> --------------
> WLAN Scenarios 1:
> Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> each node random selects a destination and transmits some packets.
> 
> WLAN Scenarios 2:
> Same configured as the above Scenarios 1 except that the number of
> nodes is twenty.
> --------------
> I have expected that one node's throughput in Scenarios 2 should
> much lower than that in Scenarios 1. But the simulation results
> show that the throughput of each node is as same as that in
> Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> 
> Could any one tell me why the nodes in Scenarios 2 don't make
> interference to each other.
> 
> Thanks a lot.
> 
> Sincerely,
> aaron
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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


From daemon@optimus.ietf.org  Wed Mar 27 09:42:04 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA00328
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 09:42:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id JAA18986
	for manet-archive@odin.ietf.org; Wed, 27 Mar 2002 09:42:06 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12384;
	Wed, 27 Mar 2002 09:16:47 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA12339
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 09:16:44 -0500 (EST)
Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28965
	for <manet@ietf.org>; Wed, 27 Mar 2002 09:16:41 -0500 (EST)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id g2RECJ809375;
	Wed, 27 Mar 2002 09:12:19 -0500 (EST)
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id g2RECHk07977;
	Wed, 27 Mar 2002 09:12:18 -0500 (EST)
Received: from dhcp-103-210.mitre.org (128.29.103.210) by mailhub1.mitre.org with SMTP
        id 9648890; Wed, 27 Mar 2002 09:12:10 -0500
Message-ID: <3CA1D33B.FE8476A6@mitre.org>
Date: Wed, 27 Mar 2002 09:12:11 -0500
From: John Stine <jstine@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: danaus <licheng@sjtu.edu.cn>
CC: manet@ietf.org
Subject: Re: [manet] About IEEE802.11 model in OPNET
References: <001b01c1d480$c2f3bb20$6d0378ca@aaron>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Opnet's wlan_mac and the support pipeline stages take some liberty in
modeling the physical layer based on the assumption that in the intended
network all nodes should be within range of each other.  As a result,
the model does not model interference correctly, but uses collisions
only as the cause of failure.  This is a severe problem when one is
studying ad hoc networking and wants to evaluate spatial reuse of the
channel.  Two nodes in a network cannot successfully transmit
simultaneously, despite separation distance.  We addressed this problem
in our modifications to OPNET's models for Kevin Grace's MobileMesh
protocols.  You should have received a message from Kevin about the
release of these models.  If you did not receive it, the text of Kevin's
message follows.

The OPNET models are for version 7.0.B but they are well documented so
with a little effort one can apply the changes to the 8.0.C version.  We
provided these models to OPNET and they have given us the indication
that they will incorporate our recommendations into a future release of
their product.

In the mean time, I would recommend anyone using the OPNET wlan_mac
model to study ad hoc networks to look at our observations and
recommendations. (See Readme-MobileMeshOpnet.pdf.)  Many conclusions
based on modeling in OPNET may need to be re-evaluated.

John

Kevin's message follows:

Opnet simulation models of the MobileMesh Routing Protocol and
MobileMesh Link Discovery Protocol are now available from Opnet's
website:

 ftp://opguest:opguest@corporate7.opnet.com/433/

Included in this distribution are numerous modifications and bug fixes
to the 802.11 wireless LAN process model and related pipeline
stages. 

Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
distribution for more details.

Information about the MobileMesh protocols and Open Source Linux
distribution 
is available at:

 http://www.mitre.org/tech_transfer/mobilemesh/

-Kevin 

danaus wrote:
> 
> Hi,
> 
> Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C ?
> I encounter a strange problem when I make the following simulation using OPNET:
> --------------
> WLAN Scenarios 1:
> Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> each node random selects a destination and transmits some packets.
> 
> WLAN Scenarios 2:
> Same configured as the above Scenarios 1 except that the number of
> nodes is twenty.
> --------------
> I have expected that one node's throughput in Scenarios 2 should
> much lower than that in Scenarios 1. But the simulation results
> show that the throughput of each node is as same as that in
> Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> 
> Could any one tell me why the nodes in Scenarios 2 don't make
> interference to each other.
> 
> Thanks a lot.
> 
> Sincerely,
> aaron
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Wed Mar 27 16:05:14 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22930
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 16:05:09 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08392;
	Wed, 27 Mar 2002 15:33:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08360
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 15:33:46 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21346
	for <manet@ietf.org>; Wed, 27 Mar 2002 15:33:43 -0500 (EST)
Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2RKXiI412159
	for <manet@ietf.org>; Wed, 27 Mar 2002 15:33:44 -0500 (EST)
Received: from ecpe15 ([208.17.194.151])
	by vivi.cc.vt.edu (Mirapoint)
	with SMTP id AOA69876;
	Wed, 27 Mar 2002 15:33:43 -0500 (EST)
Message-ID: <009a01c1d5cf$95c448e0$97c211d0@ecpe15>
Reply-To: "Vikram Dham" <vdham@vt.edu>
From: "Vikram Dham" <vdham@vt.edu>
To: <manet@ietf.org>
References: <001b01c1d480$c2f3bb20$6d0378ca@aaron> <3CA1D33B.FE8476A6@mitre.org>
Subject: Re: [manet] About IEEE802.11 model in OPNET
Date: Wed, 27 Mar 2002 15:40:07 -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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear John & Kevin:

   I agree with your pointers regarding pipeline stage.I would like to add
that instead of setting value of signal lock  & packet status at
manta_power.ps.c, you can move it to manta_snr.ps.c stage to determine
whether signal lock should be set or not and whether the packet is to be
stamped as *noise* or *valid* packet. This would take into account
interference due to other nodes without need for maintaining any additional
data structure.  For doing this you will have to maintain an additional TDA
RCV_FLAG  which should be set during the first pass of the packet through
the manta_snr.ps.c stage.

I hope the above helps.

With Best Regards

Vikram Dham
Graduate Research Assistant
Alexandria Research Institute
Virginia Tech,USA


----- Original Message -----
From: "John Stine" <jstine@mitre.org>
To: "danaus" <licheng@sjtu.edu.cn>
Cc: <manet@ietf.org>
Sent: Wednesday, March 27, 2002 9:12 AM
Subject: Re: [manet] About IEEE802.11 model in OPNET


> Opnet's wlan_mac and the support pipeline stages take some liberty in
> modeling the physical layer based on the assumption that in the intended
> network all nodes should be within range of each other.  As a result,
> the model does not model interference correctly, but uses collisions
> only as the cause of failure.  This is a severe problem when one is
> studying ad hoc networking and wants to evaluate spatial reuse of the
> channel.  Two nodes in a network cannot successfully transmit
> simultaneously, despite separation distance.  We addressed this problem
> in our modifications to OPNET's models for Kevin Grace's MobileMesh
> protocols.  You should have received a message from Kevin about the
> release of these models.  If you did not receive it, the text of Kevin's
> message follows.
>
> The OPNET models are for version 7.0.B but they are well documented so
> with a little effort one can apply the changes to the 8.0.C version.  We
> provided these models to OPNET and they have given us the indication
> that they will incorporate our recommendations into a future release of
> their product.
>
> In the mean time, I would recommend anyone using the OPNET wlan_mac
> model to study ad hoc networks to look at our observations and
> recommendations. (See Readme-MobileMeshOpnet.pdf.)  Many conclusions
> based on modeling in OPNET may need to be re-evaluated.
>
> John
>
> Kevin's message follows:
>
> Opnet simulation models of the MobileMesh Routing Protocol and
> MobileMesh Link Discovery Protocol are now available from Opnet's
> website:
>
>  ftp://opguest:opguest@corporate7.opnet.com/433/
>
> Included in this distribution are numerous modifications and bug fixes
> to the 802.11 wireless LAN process model and related pipeline
> stages.
>
> Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
> distribution for more details.
>
> Information about the MobileMesh protocols and Open Source Linux
> distribution
> is available at:
>
>  http://www.mitre.org/tech_transfer/mobilemesh/
>
> -Kevin
>
> danaus wrote:
> >
> > Hi,
> >
> > Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C
?
> > I encounter a strange problem when I make the following simulation using
OPNET:
> > --------------
> > WLAN Scenarios 1:
> > Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> > each node random selects a destination and transmits some packets.
> >
> > WLAN Scenarios 2:
> > Same configured as the above Scenarios 1 except that the number of
> > nodes is twenty.
> > --------------
> > I have expected that one node's throughput in Scenarios 2 should
> > much lower than that in Scenarios 1. But the simulation results
> > show that the throughput of each node is as same as that in
> > Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> >
> > Could any one tell me why the nodes in Scenarios 2 don't make
> > interference to each other.
> >
> > Thanks a lot.
> >
> > Sincerely,
> > aaron
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet



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


From daemon@optimus.ietf.org  Wed Mar 27 16:05:19 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22966
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 16:05:14 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA11596
	for manet-archive@odin.ietf.org; Wed, 27 Mar 2002 16:05:16 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08392;
	Wed, 27 Mar 2002 15:33:49 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA08360
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 15:33:46 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21346
	for <manet@ietf.org>; Wed, 27 Mar 2002 15:33:43 -0500 (EST)
Received: from vivi.cc.vt.edu (IDENT:mirapoint@vivi-lb.cc.vt.edu [10.1.1.12])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2RKXiI412159
	for <manet@ietf.org>; Wed, 27 Mar 2002 15:33:44 -0500 (EST)
Received: from ecpe15 ([208.17.194.151])
	by vivi.cc.vt.edu (Mirapoint)
	with SMTP id AOA69876;
	Wed, 27 Mar 2002 15:33:43 -0500 (EST)
Message-ID: <009a01c1d5cf$95c448e0$97c211d0@ecpe15>
Reply-To: "Vikram Dham" <vdham@vt.edu>
From: "Vikram Dham" <vdham@vt.edu>
To: <manet@ietf.org>
References: <001b01c1d480$c2f3bb20$6d0378ca@aaron> <3CA1D33B.FE8476A6@mitre.org>
Subject: Re: [manet] About IEEE802.11 model in OPNET
Date: Wed, 27 Mar 2002 15:40:07 -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.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear John & Kevin:

   I agree with your pointers regarding pipeline stage.I would like to add
that instead of setting value of signal lock  & packet status at
manta_power.ps.c, you can move it to manta_snr.ps.c stage to determine
whether signal lock should be set or not and whether the packet is to be
stamped as *noise* or *valid* packet. This would take into account
interference due to other nodes without need for maintaining any additional
data structure.  For doing this you will have to maintain an additional TDA
RCV_FLAG  which should be set during the first pass of the packet through
the manta_snr.ps.c stage.

I hope the above helps.

With Best Regards

Vikram Dham
Graduate Research Assistant
Alexandria Research Institute
Virginia Tech,USA


----- Original Message -----
From: "John Stine" <jstine@mitre.org>
To: "danaus" <licheng@sjtu.edu.cn>
Cc: <manet@ietf.org>
Sent: Wednesday, March 27, 2002 9:12 AM
Subject: Re: [manet] About IEEE802.11 model in OPNET


> Opnet's wlan_mac and the support pipeline stages take some liberty in
> modeling the physical layer based on the assumption that in the intended
> network all nodes should be within range of each other.  As a result,
> the model does not model interference correctly, but uses collisions
> only as the cause of failure.  This is a severe problem when one is
> studying ad hoc networking and wants to evaluate spatial reuse of the
> channel.  Two nodes in a network cannot successfully transmit
> simultaneously, despite separation distance.  We addressed this problem
> in our modifications to OPNET's models for Kevin Grace's MobileMesh
> protocols.  You should have received a message from Kevin about the
> release of these models.  If you did not receive it, the text of Kevin's
> message follows.
>
> The OPNET models are for version 7.0.B but they are well documented so
> with a little effort one can apply the changes to the 8.0.C version.  We
> provided these models to OPNET and they have given us the indication
> that they will incorporate our recommendations into a future release of
> their product.
>
> In the mean time, I would recommend anyone using the OPNET wlan_mac
> model to study ad hoc networks to look at our observations and
> recommendations. (See Readme-MobileMeshOpnet.pdf.)  Many conclusions
> based on modeling in OPNET may need to be re-evaluated.
>
> John
>
> Kevin's message follows:
>
> Opnet simulation models of the MobileMesh Routing Protocol and
> MobileMesh Link Discovery Protocol are now available from Opnet's
> website:
>
>  ftp://opguest:opguest@corporate7.opnet.com/433/
>
> Included in this distribution are numerous modifications and bug fixes
> to the 802.11 wireless LAN process model and related pipeline
> stages.
>
> Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
> distribution for more details.
>
> Information about the MobileMesh protocols and Open Source Linux
> distribution
> is available at:
>
>  http://www.mitre.org/tech_transfer/mobilemesh/
>
> -Kevin
>
> danaus wrote:
> >
> > Hi,
> >
> > Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C
?
> > I encounter a strange problem when I make the following simulation using
OPNET:
> > --------------
> > WLAN Scenarios 1:
> > Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> > each node random selects a destination and transmits some packets.
> >
> > WLAN Scenarios 2:
> > Same configured as the above Scenarios 1 except that the number of
> > nodes is twenty.
> > --------------
> > I have expected that one node's throughput in Scenarios 2 should
> > much lower than that in Scenarios 1. But the simulation results
> > show that the throughput of each node is as same as that in
> > Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> >
> > Could any one tell me why the nodes in Scenarios 2 don't make
> > interference to each other.
> >
> > Thanks a lot.
> >
> > Sincerely,
> > aaron
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
>
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet



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



From manet-admin@ietf.org  Wed Mar 27 16:24:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24442
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 16:24:51 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA10943;
	Wed, 27 Mar 2002 16:02:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA13166
	for <manet@optimus.ietf.org>; Tue, 19 Mar 2002 08:06:56 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20848
	for <manet@ietf.org>; Tue, 19 Mar 2002 08:06:53 -0500 (EST)
Received: from inria.fr (ruspina.inria.fr [128.93.17.52])
	by concorde.inria.fr (8.11.1/8.11.1) with ESMTP id g2JD6qj01018;
	Tue, 19 Mar 2002 14:06:52 +0100 (MET)
Message-ID: <3C9746FC.C281198D@inria.fr>
Date: Tue, 19 Mar 2002 15:11:08 +0100
From: Anis LAOUITI <anis.laouiti@inria.fr>
X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.4.6 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Jorge Nuevo <nuevo@inrs-telecom.uquebec.ca>
CC: manet@ietf.org
Subject: Re: [manet] Question about dependency of unicast protocols by multicast 
 protocols
References: <200203142011.PAA24622@hoffman.INRS-Telecom.UQuebec.CA>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Hello,

Here is another multicast routing protocol which is dependant on OLSR

http://hipercom.inria.fr/olsr/draft-ietf-manet-olsr-molsr.txt

Anis LAOUITI


Jorge Nuevo wrote:

> Hello,
>
> I am trying to find out which of the multicast protocols for
> ad hoc networks are unicast protocols dependent. The following
> would be unicast dependent:
> MAODV, AMRoute, CAMP
>
> and non-dependent would be: AMRIS, ODMRP and MCEDAR,
>
> but I am not sure about FGMP (Forwarding Group Multicast Protocol),
> ABAM (Associativity Based Multicast) and
> ADMR (Adaptive Demand-driven Multicast Routing).
>
> Could any one help me with this doubt?
>
> thanks
>
> Jorge Nuevo
> nuevo@inrs-telecom.uquebec.ca
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet



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


From daemon@optimus.ietf.org  Wed Mar 27 16:24:52 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24451
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 16:24:52 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA14175
	for manet-archive@odin.ietf.org; Wed, 27 Mar 2002 16:24:54 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA10943;
	Wed, 27 Mar 2002 16:02:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA13166
	for <manet@optimus.ietf.org>; Tue, 19 Mar 2002 08:06:56 -0500 (EST)
Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20848
	for <manet@ietf.org>; Tue, 19 Mar 2002 08:06:53 -0500 (EST)
Received: from inria.fr (ruspina.inria.fr [128.93.17.52])
	by concorde.inria.fr (8.11.1/8.11.1) with ESMTP id g2JD6qj01018;
	Tue, 19 Mar 2002 14:06:52 +0100 (MET)
Message-ID: <3C9746FC.C281198D@inria.fr>
Date: Tue, 19 Mar 2002 15:11:08 +0100
From: Anis LAOUITI <anis.laouiti@inria.fr>
X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.4.6 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Jorge Nuevo <nuevo@inrs-telecom.uquebec.ca>
CC: manet@ietf.org
Subject: Re: [manet] Question about dependency of unicast protocols by multicast 
 protocols
References: <200203142011.PAA24622@hoffman.INRS-Telecom.UQuebec.CA>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Hello,

Here is another multicast routing protocol which is dependant on OLSR

http://hipercom.inria.fr/olsr/draft-ietf-manet-olsr-molsr.txt

Anis LAOUITI


Jorge Nuevo wrote:

> Hello,
>
> I am trying to find out which of the multicast protocols for
> ad hoc networks are unicast protocols dependent. The following
> would be unicast dependent:
> MAODV, AMRoute, CAMP
>
> and non-dependent would be: AMRIS, ODMRP and MCEDAR,
>
> but I am not sure about FGMP (Forwarding Group Multicast Protocol),
> ABAM (Associativity Based Multicast) and
> ADMR (Adaptive Demand-driven Multicast Routing).
>
> Could any one help me with this doubt?
>
> thanks
>
> Jorge Nuevo
> nuevo@inrs-telecom.uquebec.ca
>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet



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



From manet-admin@ietf.org  Wed Mar 27 16:29:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24871
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 16:29:33 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA12147;
	Wed, 27 Mar 2002 16:08:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21009
	for <manet@optimus.ietf.org>; Mon, 25 Mar 2002 08:06:51 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08250;
	Mon, 25 Mar 2002 08:06:49 -0500 (EST)
Message-Id: <200203251306.IAA08250@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: manet@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 25 Mar 2002 08:06:49 -0500
Subject: [manet] I-D ACTION:draft-baker-manet-review-01.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: An outsider's view of MANET
	Author(s)	: F. Baker
	Filename	: draft-baker-manet-review-01.txt
	Pages		: 39
	Date		: 20-Mar-02
	
This note addresses routing in chaotic non-engineered radio networks

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-baker-manet-review-01.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-baker-manet-review-01.txt

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

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

--OtherAccess--

--NextPart--




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


From daemon@optimus.ietf.org  Wed Mar 27 16:29:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24880
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 16:29:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id QAA14555
	for manet-archive@odin.ietf.org; Wed, 27 Mar 2002 16:29:36 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA12147;
	Wed, 27 Mar 2002 16:08:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA21009
	for <manet@optimus.ietf.org>; Mon, 25 Mar 2002 08:06:51 -0500 (EST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08250;
	Mon, 25 Mar 2002 08:06:49 -0500 (EST)
Message-Id: <200203251306.IAA08250@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: manet@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 25 Mar 2002 08:06:49 -0500
Subject: [manet] I-D ACTION:draft-baker-manet-review-01.txt
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: An outsider's view of MANET
	Author(s)	: F. Baker
	Filename	: draft-baker-manet-review-01.txt
	Pages		: 39
	Date		: 20-Mar-02
	
This note addresses routing in chaotic non-engineered radio networks

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-baker-manet-review-01.txt".

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-baker-manet-review-01.txt

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

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

--OtherAccess--

--NextPart--




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



From manet-admin@ietf.org  Wed Mar 27 17:19:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27185
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 17:19:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16317;
	Wed, 27 Mar 2002 16:54:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16289
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 16:54:20 -0500 (EST)
Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [198.76.173.29])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26214
	for <manet@ietf.org>; Wed, 27 Mar 2002 16:54:18 -0500 (EST)
Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4])
	by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id g2RLsK527641;
	Wed, 27 Mar 2002 16:54:20 -0500 (EST)
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id g2RLsIJ23100;
	Wed, 27 Mar 2002 16:54:19 -0500 (EST)
Received: from dhcp-103-210.mitre.org (128.29.103.210) by mailhub1.mitre.org with SMTP
        id 9659556; Wed, 27 Mar 2002 16:54:03 -0500
Message-ID: <3CA23F86.BD51079C@mitre.org>
Date: Wed, 27 Mar 2002 16:54:14 -0500
From: John Stine <jstine@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vikram Dham <vdham@vt.edu>
CC: manet@ietf.org
Subject: Re: [manet] About IEEE802.11 model in OPNET
References: <001b01c1d480$c2f3bb20$6d0378ca@aaron> <3CA1D33B.FE8476A6@mitre.org> <009a01c1d5cf$95c448e0$97c211d0@ecpe15>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear Vikram,

	This was our first instinct but the OPNET kernel does not allow it. 
The issue is, when is the latest you can set a packet's status to
noise.  The answer is the power stage.  Below is the text of a message I
got from OPNET technical support when I asked this question.  I called
after I noticed my simulation didn't work when I waited until the SNR
stage to set the sig_lock attribute and the match status.

*** TEXT OF MESSAGE FROM OPNET
SUPPORT************************************

It sounds like you are setting OPC_TDA_RA_MATCH_STATUS to .._NOISE in
the 
SNR stage. The kernel expects the MATCH_STATUS TDA to be set at the
latest 
by the power stage, and therefore, modifying it in the SNR stage may
result 
in unexplained behaviour, including possibly the abort that you observe.
At 
any rate, changing the TDA in the SNR stage will not prevent the kernel 
from invoking the following stages (ber, etc.) because the kernel will 
still treat it as a valid packet. 

Therefore, we suggest that you try another approach to achieve the same 
goal. For example, you could mark all potential packets as VALID in the 
power stage and define your own TDA called "MY_MATCH_STATUS" and set
this 
to noise in the SNR stage if the conditions so dictate. However, since
the 
kernel does not know about this TDA, all the stages following the SNR 
stage, i.e., ber, error, ecc will still be invoked by the kernel for
this 
packet that has its MY_MATCH_STATUS TDA set to NOISE. Therefore, you
will 
have to access this TDA in the last few stages and immediately exit
using a 
FOUT if the MY_MATCH_STATUS is set to NOISE. 

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

So it may be possible to use the SNR but not without an additional data
structure to keep track of which packets are valid.  Since I cannot see
what happens inside the kernel I decided not to circumvent OPNET's
plan.  Not modeling signal lock based on SNR has little effect in the
performance of the model.  If SNR is a factor, the newly arriving packet
that we lock onto is likely to have errors and not be accepted. If we
successfully account for SNR, the duration of this packet would be
sensed as a busy channel.   So, in both cases, the effect on the
receiving node is the same.


John

Vikram Dham wrote:
> 
> Dear John & Kevin:
> 
>    I agree with your pointers regarding pipeline stage.I would like to add
> that instead of setting value of signal lock  & packet status at
> manta_power.ps.c, you can move it to manta_snr.ps.c stage to determine
> whether signal lock should be set or not and whether the packet is to be
> stamped as *noise* or *valid* packet. This would take into account
> interference due to other nodes without need for maintaining any additional
> data structure.  For doing this you will have to maintain an additional TDA
> RCV_FLAG  which should be set during the first pass of the packet through
> the manta_snr.ps.c stage.
> 
> I hope the above helps.
> 
> With Best Regards
> 
> Vikram Dham
> Graduate Research Assistant
> Alexandria Research Institute
> Virginia Tech,USA
> 
> ----- Original Message -----
> From: "John Stine" <jstine@mitre.org>
> To: "danaus" <licheng@sjtu.edu.cn>
> Cc: <manet@ietf.org>
> Sent: Wednesday, March 27, 2002 9:12 AM
> Subject: Re: [manet] About IEEE802.11 model in OPNET
> 
> > Opnet's wlan_mac and the support pipeline stages take some liberty in
> > modeling the physical layer based on the assumption that in the intended
> > network all nodes should be within range of each other.  As a result,
> > the model does not model interference correctly, but uses collisions
> > only as the cause of failure.  This is a severe problem when one is
> > studying ad hoc networking and wants to evaluate spatial reuse of the
> > channel.  Two nodes in a network cannot successfully transmit
> > simultaneously, despite separation distance.  We addressed this problem
> > in our modifications to OPNET's models for Kevin Grace's MobileMesh
> > protocols.  You should have received a message from Kevin about the
> > release of these models.  If you did not receive it, the text of Kevin's
> > message follows.
> >
> > The OPNET models are for version 7.0.B but they are well documented so
> > with a little effort one can apply the changes to the 8.0.C version.  We
> > provided these models to OPNET and they have given us the indication
> > that they will incorporate our recommendations into a future release of
> > their product.
> >
> > In the mean time, I would recommend anyone using the OPNET wlan_mac
> > model to study ad hoc networks to look at our observations and
> > recommendations. (See Readme-MobileMeshOpnet.pdf.)  Many conclusions
> > based on modeling in OPNET may need to be re-evaluated.
> >
> > John
> >
> > Kevin's message follows:
> >
> > Opnet simulation models of the MobileMesh Routing Protocol and
> > MobileMesh Link Discovery Protocol are now available from Opnet's
> > website:
> >
> >  ftp://opguest:opguest@corporate7.opnet.com/433/
> >
> > Included in this distribution are numerous modifications and bug fixes
> > to the 802.11 wireless LAN process model and related pipeline
> > stages.
> >
> > Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
> > distribution for more details.
> >
> > Information about the MobileMesh protocols and Open Source Linux
> > distribution
> > is available at:
> >
> >  http://www.mitre.org/tech_transfer/mobilemesh/
> >
> > -Kevin
> >
> > danaus wrote:
> > >
> > > Hi,
> > >
> > > Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C
> ?
> > > I encounter a strange problem when I make the following simulation using
> OPNET:
> > > --------------
> > > WLAN Scenarios 1:
> > > Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> > > each node random selects a destination and transmits some packets.
> > >
> > > WLAN Scenarios 2:
> > > Same configured as the above Scenarios 1 except that the number of
> > > nodes is twenty.
> > > --------------
> > > I have expected that one node's throughput in Scenarios 2 should
> > > much lower than that in Scenarios 1. But the simulation results
> > > show that the throughput of each node is as same as that in
> > > Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> > >
> > > Could any one tell me why the nodes in Scenarios 2 don't make
> > > interference to each other.
> > >
> > > Thanks a lot.
> > >
> > > Sincerely,
> > > aaron
> > >
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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


From daemon@optimus.ietf.org  Wed Mar 27 17:19:31 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27196
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 17:19:31 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA19383
	for manet-archive@odin.ietf.org; Wed, 27 Mar 2002 17:19:33 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16317;
	Wed, 27 Mar 2002 16:54:23 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA16289
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 16:54:20 -0500 (EST)
Received: from smtpproxy2.mitre.org (smtpproxy2.mitre.org [198.76.173.29])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26214
	for <manet@ietf.org>; Wed, 27 Mar 2002 16:54:18 -0500 (EST)
Received: from avsrv2.mitre.org (avsrv2.mitre.org [128.29.154.4])
	by smtpproxy2.mitre.org (8.11.3/8.11.3) with ESMTP id g2RLsK527641;
	Wed, 27 Mar 2002 16:54:20 -0500 (EST)
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtpsrv2.mitre.org (8.11.3/8.11.3) with ESMTP id g2RLsIJ23100;
	Wed, 27 Mar 2002 16:54:19 -0500 (EST)
Received: from dhcp-103-210.mitre.org (128.29.103.210) by mailhub1.mitre.org with SMTP
        id 9659556; Wed, 27 Mar 2002 16:54:03 -0500
Message-ID: <3CA23F86.BD51079C@mitre.org>
Date: Wed, 27 Mar 2002 16:54:14 -0500
From: John Stine <jstine@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vikram Dham <vdham@vt.edu>
CC: manet@ietf.org
Subject: Re: [manet] About IEEE802.11 model in OPNET
References: <001b01c1d480$c2f3bb20$6d0378ca@aaron> <3CA1D33B.FE8476A6@mitre.org> <009a01c1d5cf$95c448e0$97c211d0@ecpe15>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear Vikram,

	This was our first instinct but the OPNET kernel does not allow it. 
The issue is, when is the latest you can set a packet's status to
noise.  The answer is the power stage.  Below is the text of a message I
got from OPNET technical support when I asked this question.  I called
after I noticed my simulation didn't work when I waited until the SNR
stage to set the sig_lock attribute and the match status.

*** TEXT OF MESSAGE FROM OPNET
SUPPORT************************************

It sounds like you are setting OPC_TDA_RA_MATCH_STATUS to .._NOISE in
the 
SNR stage. The kernel expects the MATCH_STATUS TDA to be set at the
latest 
by the power stage, and therefore, modifying it in the SNR stage may
result 
in unexplained behaviour, including possibly the abort that you observe.
At 
any rate, changing the TDA in the SNR stage will not prevent the kernel 
from invoking the following stages (ber, etc.) because the kernel will 
still treat it as a valid packet. 

Therefore, we suggest that you try another approach to achieve the same 
goal. For example, you could mark all potential packets as VALID in the 
power stage and define your own TDA called "MY_MATCH_STATUS" and set
this 
to noise in the SNR stage if the conditions so dictate. However, since
the 
kernel does not know about this TDA, all the stages following the SNR 
stage, i.e., ber, error, ecc will still be invoked by the kernel for
this 
packet that has its MY_MATCH_STATUS TDA set to NOISE. Therefore, you
will 
have to access this TDA in the last few stages and immediately exit
using a 
FOUT if the MY_MATCH_STATUS is set to NOISE. 

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

So it may be possible to use the SNR but not without an additional data
structure to keep track of which packets are valid.  Since I cannot see
what happens inside the kernel I decided not to circumvent OPNET's
plan.  Not modeling signal lock based on SNR has little effect in the
performance of the model.  If SNR is a factor, the newly arriving packet
that we lock onto is likely to have errors and not be accepted. If we
successfully account for SNR, the duration of this packet would be
sensed as a busy channel.   So, in both cases, the effect on the
receiving node is the same.


John

Vikram Dham wrote:
> 
> Dear John & Kevin:
> 
>    I agree with your pointers regarding pipeline stage.I would like to add
> that instead of setting value of signal lock  & packet status at
> manta_power.ps.c, you can move it to manta_snr.ps.c stage to determine
> whether signal lock should be set or not and whether the packet is to be
> stamped as *noise* or *valid* packet. This would take into account
> interference due to other nodes without need for maintaining any additional
> data structure.  For doing this you will have to maintain an additional TDA
> RCV_FLAG  which should be set during the first pass of the packet through
> the manta_snr.ps.c stage.
> 
> I hope the above helps.
> 
> With Best Regards
> 
> Vikram Dham
> Graduate Research Assistant
> Alexandria Research Institute
> Virginia Tech,USA
> 
> ----- Original Message -----
> From: "John Stine" <jstine@mitre.org>
> To: "danaus" <licheng@sjtu.edu.cn>
> Cc: <manet@ietf.org>
> Sent: Wednesday, March 27, 2002 9:12 AM
> Subject: Re: [manet] About IEEE802.11 model in OPNET
> 
> > Opnet's wlan_mac and the support pipeline stages take some liberty in
> > modeling the physical layer based on the assumption that in the intended
> > network all nodes should be within range of each other.  As a result,
> > the model does not model interference correctly, but uses collisions
> > only as the cause of failure.  This is a severe problem when one is
> > studying ad hoc networking and wants to evaluate spatial reuse of the
> > channel.  Two nodes in a network cannot successfully transmit
> > simultaneously, despite separation distance.  We addressed this problem
> > in our modifications to OPNET's models for Kevin Grace's MobileMesh
> > protocols.  You should have received a message from Kevin about the
> > release of these models.  If you did not receive it, the text of Kevin's
> > message follows.
> >
> > The OPNET models are for version 7.0.B but they are well documented so
> > with a little effort one can apply the changes to the 8.0.C version.  We
> > provided these models to OPNET and they have given us the indication
> > that they will incorporate our recommendations into a future release of
> > their product.
> >
> > In the mean time, I would recommend anyone using the OPNET wlan_mac
> > model to study ad hoc networks to look at our observations and
> > recommendations. (See Readme-MobileMeshOpnet.pdf.)  Many conclusions
> > based on modeling in OPNET may need to be re-evaluated.
> >
> > John
> >
> > Kevin's message follows:
> >
> > Opnet simulation models of the MobileMesh Routing Protocol and
> > MobileMesh Link Discovery Protocol are now available from Opnet's
> > website:
> >
> >  ftp://opguest:opguest@corporate7.opnet.com/433/
> >
> > Included in this distribution are numerous modifications and bug fixes
> > to the 802.11 wireless LAN process model and related pipeline
> > stages.
> >
> > Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
> > distribution for more details.
> >
> > Information about the MobileMesh protocols and Open Source Linux
> > distribution
> > is available at:
> >
> >  http://www.mitre.org/tech_transfer/mobilemesh/
> >
> > -Kevin
> >
> > danaus wrote:
> > >
> > > Hi,
> > >
> > > Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C
> ?
> > > I encounter a strange problem when I make the following simulation using
> OPNET:
> > > --------------
> > > WLAN Scenarios 1:
> > > Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> > > each node random selects a destination and transmits some packets.
> > >
> > > WLAN Scenarios 2:
> > > Same configured as the above Scenarios 1 except that the number of
> > > nodes is twenty.
> > > --------------
> > > I have expected that one node's throughput in Scenarios 2 should
> > > much lower than that in Scenarios 1. But the simulation results
> > > show that the throughput of each node is as same as that in
> > > Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> > >
> > > Could any one tell me why the nodes in Scenarios 2 don't make
> > > interference to each other.
> > >
> > > Thanks a lot.
> > >
> > > Sincerely,
> > > aaron
> > >
> > > _______________________________________________
> > > manet mailing list
> > > manet@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/manet
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www1.ietf.org/mailman/listinfo/manet
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Wed Mar 27 17:21:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27272
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 17:21:23 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA17424;
	Wed, 27 Mar 2002 17:00:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA17367
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 17:00:22 -0500 (EST)
Received: from color.sics.se (color.sics.se [193.10.66.199])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26617
	for <manet@ietf.org>; Wed, 27 Mar 2002 17:00:15 -0500 (EST)
Received: from kanin.sics.se (kanin.sics.se [193.10.65.146])
	by color.sics.se (8.9.3/8.9.3) with ESMTP id XAA14295;
        Wed, 27 Mar 2002 23:00:16 +0100 (MET)
	env-to ()
	env-from (lmfeeney@color.sics.se)
Received: (from lmfeeney@localhost)
	by kanin.sics.se (8.8.7/8.8.7) id XAA07564;
	Wed, 27 Mar 2002 23:00:16 +0100
Date: Wed, 27 Mar 2002 23:00:16 +0100
Message-Id: <200203272200.XAA07564@kanin.sics.se>
X-Authentication-Warning: kanin.sics.se: lmfeeney set sender to lmfeeney@kanin.sics.se using -f
From: Laura Feeney <lmfeeney@sics.se>
To: manet@ietf.org
Subject: [manet] Call for Participation, Networking 2002
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


There will be a number of papers of interest to the manet community,
so I encourage you to consider attending.

Please feel free to redistribute this CFP.  Apologies if you receive
multiple copies.

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

CALL FOR PARTICIPATION

NETWORKING 2002
The Second IFIP-TC6 Networking Conference
http://www.cnuce.pi.cnr.it/Networking2002

May 19-24 2002, Pisa - Italy

Networking is the biennial Conference on Networking of the IFIP
Technical Committee on Communication Systems (TC6). Networking 2002 is
the second conference of this series --the first event was held in
Paris, May 2000

Networking 2002 is organized into three tracks: 

	  i) Networking Technologies, Services and Protocols
	 ii) Performance of Computer and Communication Networks
	iii) Mobile and Wireless Communications Systems.

This year the conference received 314 submissions coming from 42
countries from all five continents: Africa (4), Asia (84), America
(63), Europe (158) and Oceania (5). From the 314 submissions, we
finally selected 82 full papers for the presentation in the conference
technical sessions. In addition, we selected 31 short papers for
presentation in the poster sessions.

The technical program also includes a panel session, and three Invited
Talks from worldwide leaders

      Imrich Chlamtac "Managing Optical Networks in the Optical Domain"
      
      Randy Katz "The Post-PC Era: It's All About Services"

      Gerald Maguire "Personal Computing and Communication". 

The panel session, organized by Andrew T. Campbell (Columbia
University), is entitled "Post 9-11 Networking Challenges". The panel
discusses on how to cope with the communications systems'
vulnerabilities revealed by the World Trade Center attack on September
11.

The program of the conference is on five days and includes

- two tutorial days, http://www.cnuce.pi.cnr.it/Networking2002/tutorial.html

- the main conference,
http://www.cnuce.pi.cnr.it/Networking2002/at-a-glance.html

- one-day thematic workshops,
http://www.cnuce.pi.cnr.it/Networking2002/workshops.html

Advance program, registration information, and hotel information for NETWORKING
2002 are now available at http://www.cnuce.pi.cnr.it/Networking2002/info.html

If you are unable to access the above web page, please send e-mail to:
info_net2002 <networking2002@cnuce.cnr.it>.

CONFERENCE REGISTRATION: The deadline for normal registration is APRIL 20,
2002.

HOTEL RESERVATION: The deadline for hotel reservation is APRIL 22, 2002. Please
book your hotel room as soon as possible. May is a high tourist season in Pisa.
After April 22 we cannot  guarantee your reservation.


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


From daemon@optimus.ietf.org  Wed Mar 27 17:21:23 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27281
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 17:21:23 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id RAA19541
	for manet-archive@odin.ietf.org; Wed, 27 Mar 2002 17:21:25 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA17424;
	Wed, 27 Mar 2002 17:00:26 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA17367
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 17:00:22 -0500 (EST)
Received: from color.sics.se (color.sics.se [193.10.66.199])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26617
	for <manet@ietf.org>; Wed, 27 Mar 2002 17:00:15 -0500 (EST)
Received: from kanin.sics.se (kanin.sics.se [193.10.65.146])
	by color.sics.se (8.9.3/8.9.3) with ESMTP id XAA14295;
        Wed, 27 Mar 2002 23:00:16 +0100 (MET)
	env-to ()
	env-from (lmfeeney@color.sics.se)
Received: (from lmfeeney@localhost)
	by kanin.sics.se (8.8.7/8.8.7) id XAA07564;
	Wed, 27 Mar 2002 23:00:16 +0100
Date: Wed, 27 Mar 2002 23:00:16 +0100
Message-Id: <200203272200.XAA07564@kanin.sics.se>
X-Authentication-Warning: kanin.sics.se: lmfeeney set sender to lmfeeney@kanin.sics.se using -f
From: Laura Feeney <lmfeeney@sics.se>
To: manet@ietf.org
Subject: [manet] Call for Participation, Networking 2002
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


There will be a number of papers of interest to the manet community,
so I encourage you to consider attending.

Please feel free to redistribute this CFP.  Apologies if you receive
multiple copies.

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

CALL FOR PARTICIPATION

NETWORKING 2002
The Second IFIP-TC6 Networking Conference
http://www.cnuce.pi.cnr.it/Networking2002

May 19-24 2002, Pisa - Italy

Networking is the biennial Conference on Networking of the IFIP
Technical Committee on Communication Systems (TC6). Networking 2002 is
the second conference of this series --the first event was held in
Paris, May 2000

Networking 2002 is organized into three tracks: 

	  i) Networking Technologies, Services and Protocols
	 ii) Performance of Computer and Communication Networks
	iii) Mobile and Wireless Communications Systems.

This year the conference received 314 submissions coming from 42
countries from all five continents: Africa (4), Asia (84), America
(63), Europe (158) and Oceania (5). From the 314 submissions, we
finally selected 82 full papers for the presentation in the conference
technical sessions. In addition, we selected 31 short papers for
presentation in the poster sessions.

The technical program also includes a panel session, and three Invited
Talks from worldwide leaders

      Imrich Chlamtac "Managing Optical Networks in the Optical Domain"
      
      Randy Katz "The Post-PC Era: It's All About Services"

      Gerald Maguire "Personal Computing and Communication". 

The panel session, organized by Andrew T. Campbell (Columbia
University), is entitled "Post 9-11 Networking Challenges". The panel
discusses on how to cope with the communications systems'
vulnerabilities revealed by the World Trade Center attack on September
11.

The program of the conference is on five days and includes

- two tutorial days, http://www.cnuce.pi.cnr.it/Networking2002/tutorial.html

- the main conference,
http://www.cnuce.pi.cnr.it/Networking2002/at-a-glance.html

- one-day thematic workshops,
http://www.cnuce.pi.cnr.it/Networking2002/workshops.html

Advance program, registration information, and hotel information for NETWORKING
2002 are now available at http://www.cnuce.pi.cnr.it/Networking2002/info.html

If you are unable to access the above web page, please send e-mail to:
info_net2002 <networking2002@cnuce.cnr.it>.

CONFERENCE REGISTRATION: The deadline for normal registration is APRIL 20,
2002.

HOTEL RESERVATION: The deadline for hotel reservation is APRIL 22, 2002. Please
book your hotel room as soon as possible. May is a high tourist season in Pisa.
After April 22 we cannot  guarantee your reservation.


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



From manet-admin@ietf.org  Wed Mar 27 18:25:38 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29263
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 18:25:38 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA21924;
	Wed, 27 Mar 2002 17:45:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA21892
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 17:45:10 -0500 (EST)
Received: from letters.cs.ucsb.edu (letters.cs.ucsb.edu [128.111.41.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28346
	for <manet@ietf.org>; Wed, 27 Mar 2002 17:45:07 -0500 (EST)
Received: from saguaro (saguaro [128.111.40.82])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.9.3) with ESMTP id g2RMj8O12885;
	Wed, 27 Mar 2002 14:45:08 -0800 (PST)
Date: Wed, 27 Mar 2002 14:45:08 -0800 (PST)
From: "Elizabeth M. Belding-Royer" <eroyer@cs.ucsb.edu>
X-Sender: eroyer@saguaro
To: manet@ietf.org, aodvimpl-public@lists.sourceforge.net
cc: fenner@research.att.com
Message-ID: <Pine.GSO.4.21.0203271437140.29491-100000@saguaro>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] 1st AODV Interop a Success!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


We are pleased to announce a successful 1st AODV Interop.
The event was held at the University of California, Santa Barbara
on March 25 and 26th, 2002.  Attending were four IPv4 implementations
and two IPv6 implementations.  

Interoperation of the IPv4 implemenations was very successful.  
Operation was tested over wired Ethernet, over wireless links 
using ipTables to provide binary link connectivity, and over
wireless links using obstacles to provide link disconnections.  
The latter test included nodes distributed throughout a building, 
and route discovery and web page retrieval over a four node path.  
Route discovery, link break detection, and subsequent route repair 
through a different intermediate node was tested with the four
implementations and all successfully worked.  Networks with as
many as seven nodes were tested.

The IPv6 implementations successfully interoperated with
hello-based and reactive route discovery.  A more limited set of
tests (less than 3 hops) were performed with the IPv6 implementations,
primarily due to lack of adequate filtering support for IPv6 on the 
tested platforms, and a smaller number of available implementations. 
These tests provided the first evidence that the same interoperation 
as with IPv4 is feasible using the IPv6 version of the protocol.

Further details about the event are forthcoming, once post-processing
is completed.

Thanks to all who attended and helped plan the event!

Elizabeth


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


From daemon@optimus.ietf.org  Wed Mar 27 18:25:39 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29271
	for <manet-archive@odin.ietf.org>; Wed, 27 Mar 2002 18:25:39 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id SAA24255
	for manet-archive@odin.ietf.org; Wed, 27 Mar 2002 18:25:42 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA21924;
	Wed, 27 Mar 2002 17:45:13 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA21892
	for <manet@optimus.ietf.org>; Wed, 27 Mar 2002 17:45:10 -0500 (EST)
Received: from letters.cs.ucsb.edu (letters.cs.ucsb.edu [128.111.41.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28346
	for <manet@ietf.org>; Wed, 27 Mar 2002 17:45:07 -0500 (EST)
Received: from saguaro (saguaro [128.111.40.82])
	by letters.cs.ucsb.edu (8.11.6+Sun/8.9.3) with ESMTP id g2RMj8O12885;
	Wed, 27 Mar 2002 14:45:08 -0800 (PST)
Date: Wed, 27 Mar 2002 14:45:08 -0800 (PST)
From: "Elizabeth M. Belding-Royer" <eroyer@cs.ucsb.edu>
X-Sender: eroyer@saguaro
To: manet@ietf.org, aodvimpl-public@lists.sourceforge.net
cc: fenner@research.att.com
Message-ID: <Pine.GSO.4.21.0203271437140.29491-100000@saguaro>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] 1st AODV Interop a Success!
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org


We are pleased to announce a successful 1st AODV Interop.
The event was held at the University of California, Santa Barbara
on March 25 and 26th, 2002.  Attending were four IPv4 implementations
and two IPv6 implementations.  

Interoperation of the IPv4 implemenations was very successful.  
Operation was tested over wired Ethernet, over wireless links 
using ipTables to provide binary link connectivity, and over
wireless links using obstacles to provide link disconnections.  
The latter test included nodes distributed throughout a building, 
and route discovery and web page retrieval over a four node path.  
Route discovery, link break detection, and subsequent route repair 
through a different intermediate node was tested with the four
implementations and all successfully worked.  Networks with as
many as seven nodes were tested.

The IPv6 implementations successfully interoperated with
hello-based and reactive route discovery.  A more limited set of
tests (less than 3 hops) were performed with the IPv6 implementations,
primarily due to lack of adequate filtering support for IPv6 on the 
tested platforms, and a smaller number of available implementations. 
These tests provided the first evidence that the same interoperation 
as with IPv4 is feasible using the IPv6 version of the protocol.

Further details about the event are forthcoming, once post-processing
is completed.

Thanks to all who attended and helped plan the event!

Elizabeth


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



From manet-admin@ietf.org  Thu Mar 28 02:00:03 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08875
	for <manet-archive@odin.ietf.org>; Thu, 28 Mar 2002 02:00:03 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA23358;
	Thu, 28 Mar 2002 01:19:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA23326
	for <manet@optimus.ietf.org>; Thu, 28 Mar 2002 01:19:04 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08284
	for <manet@ietf.org>; Thu, 28 Mar 2002 01:19:00 -0500 (EST)
Received: from dagger.cc.vt.edu (IDENT:mirapoint@dagger-lb.cc.vt.edu [10.1.1.11])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2S6J0I38353;
	Thu, 28 Mar 2002 01:19:00 -0500 (EST)
Received: from zathras (zathras.cc.vt.edu [198.82.162.117])
	by dagger.cc.vt.edu (Mirapoint)
	with ESMTP id AWH25137;
	Thu, 28 Mar 2002 01:05:21 -0500 (EST)
X-WebMail-UserID:  vdham
Date: Thu, 28 Mar 2002 01:19:00 -0500
From: Vikram Dham  <vdham@vt.edu>
To: John Stine <jstine@mitre.org>
Cc: manet <manet@ietf.org>
X-EXP32-SerialNo: 00002964
Subject: RE: [manet] About IEEE802.11 model in OPNET
Message-ID: <3CA305A2@zathras>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: WebMail (Hydra) SMTP v3.61
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear John,

         If you manipulate  OPC_TDA_STATUS beyond dra_power stage, then you 
could be attempting to access destroyed packets (NOISE PACKETS) in later 
stages and that is why you got the error. As mentioned in OPNET's email you 
need to use another TDA to maintain packet status and set OPC_TDA_STATUS equal 
to valid for all packets so all packets are forced through all stages. I have 
just completed running a simulations scenario which takes care of interference 
from other transmissions going around. During debugging I have observed that 
interference from other transmissions is accounted for.

With Best Regards

Vikram Dham





>===== Original Message From John Stine <jstine@mitre.org> =====
>Dear Vikram,
>
>	This was our first instinct but the OPNET kernel does not allow it.
>The issue is, when is the latest you can set a packet's status to
>noise.  The answer is the power stage.  Below is the text of a message I
>got from OPNET technical support when I asked this question.  I called
>after I noticed my simulation didn't work when I waited until the SNR
>stage to set the sig_lock attribute and the match status.
>
>*** TEXT OF MESSAGE FROM OPNET
>SUPPORT************************************
>
>It sounds like you are setting OPC_TDA_RA_MATCH_STATUS to .._NOISE in
>the
>SNR stage. The kernel expects the MATCH_STATUS TDA to be set at the
>latest
>by the power stage, and therefore, modifying it in the SNR stage may
>result
>in unexplained behaviour, including possibly the abort that you observe.
>At
>any rate, changing the TDA in the SNR stage will not prevent the kernel
>from invoking the following stages (ber, etc.) because the kernel will
>still treat it as a valid packet.
>
>Therefore, we suggest that you try another approach to achieve the same
>goal. For example, you could mark all potential packets as VALID in the
>power stage and define your own TDA called "MY_MATCH_STATUS" and set
>this
>to noise in the SNR stage if the conditions so dictate. However, since
>the
>kernel does not know about this TDA, all the stages following the SNR
>stage, i.e., ber, error, ecc will still be invoked by the kernel for
>this
>packet that has its MY_MATCH_STATUS TDA set to NOISE. Therefore, you
>will
>have to access this TDA in the last few stages and immediately exit
>using a
>FOUT if the MY_MATCH_STATUS is set to NOISE.
>
>*****************************************************************************
**
>
>So it may be possible to use the SNR but not without an additional data
>structure to keep track of which packets are valid.  Since I cannot see
>what happens inside the kernel I decided not to circumvent OPNET's
>plan.  Not modeling signal lock based on SNR has little effect in the
>performance of the model.  If SNR is a factor, the newly arriving packet
>that we lock onto is likely to have errors and not be accepted. If we
>successfully account for SNR, the duration of this packet would be
>sensed as a busy channel.   So, in both cases, the effect on the
>receiving node is the same.
>
>
>John
>
>Vikram Dham wrote:
>>
>> Dear John & Kevin:
>>
>>    I agree with your pointers regarding pipeline stage.I would like to add
>> that instead of setting value of signal lock  & packet status at
>> manta_power.ps.c, you can move it to manta_snr.ps.c stage to determine
>> whether signal lock should be set or not and whether the packet is to be
>> stamped as *noise* or *valid* packet. This would take into account
>> interference due to other nodes without need for maintaining any additional
>> data structure.  For doing this you will have to maintain an additional TDA
>> RCV_FLAG  which should be set during the first pass of the packet through
>> the manta_snr.ps.c stage.
>>
>> I hope the above helps.
>>
>> With Best Regards
>>
>> Vikram Dham
>> Graduate Research Assistant
>> Alexandria Research Institute
>> Virginia Tech,USA
>>
>> ----- Original Message -----
>> From: "John Stine" <jstine@mitre.org>
>> To: "danaus" <licheng@sjtu.edu.cn>
>> Cc: <manet@ietf.org>
>> Sent: Wednesday, March 27, 2002 9:12 AM
>> Subject: Re: [manet] About IEEE802.11 model in OPNET
>>
>> > Opnet's wlan_mac and the support pipeline stages take some liberty in
>> > modeling the physical layer based on the assumption that in the intended
>> > network all nodes should be within range of each other.  As a result,
>> > the model does not model interference correctly, but uses collisions
>> > only as the cause of failure.  This is a severe problem when one is
>> > studying ad hoc networking and wants to evaluate spatial reuse of the
>> > channel.  Two nodes in a network cannot successfully transmit
>> > simultaneously, despite separation distance.  We addressed this problem
>> > in our modifications to OPNET's models for Kevin Grace's MobileMesh
>> > protocols.  You should have received a message from Kevin about the
>> > release of these models.  If you did not receive it, the text of Kevin's
>> > message follows.
>> >
>> > The OPNET models are for version 7.0.B but they are well documented so
>> > with a little effort one can apply the changes to the 8.0.C version.  We
>> > provided these models to OPNET and they have given us the indication
>> > that they will incorporate our recommendations into a future release of
>> > their product.
>> >
>> > In the mean time, I would recommend anyone using the OPNET wlan_mac
>> > model to study ad hoc networks to look at our observations and
>> > recommendations. (See Readme-MobileMeshOpnet.pdf.)  Many conclusions
>> > based on modeling in OPNET may need to be re-evaluated.
>> >
>> > John
>> >
>> > Kevin's message follows:
>> >
>> > Opnet simulation models of the MobileMesh Routing Protocol and
>> > MobileMesh Link Discovery Protocol are now available from Opnet's
>> > website:
>> >
>> >  ftp://opguest:opguest@corporate7.opnet.com/433/
>> >
>> > Included in this distribution are numerous modifications and bug fixes
>> > to the 802.11 wireless LAN process model and related pipeline
>> > stages.
>> >
>> > Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
>> > distribution for more details.
>> >
>> > Information about the MobileMesh protocols and Open Source Linux
>> > distribution
>> > is available at:
>> >
>> >  http://www.mitre.org/tech_transfer/mobilemesh/
>> >
>> > -Kevin
>> >
>> > danaus wrote:
>> > >
>> > > Hi,
>> > >
>> > > Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C
>> ?
>> > > I encounter a strange problem when I make the following simulation 
using
>> OPNET:
>> > > --------------
>> > > WLAN Scenarios 1:
>> > > Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
>> > > each node random selects a destination and transmits some packets.
>> > >
>> > > WLAN Scenarios 2:
>> > > Same configured as the above Scenarios 1 except that the number of
>> > > nodes is twenty.
>> > > --------------
>> > > I have expected that one node's throughput in Scenarios 2 should
>> > > much lower than that in Scenarios 1. But the simulation results
>> > > show that the throughput of each node is as same as that in
>> > > Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
>> > >
>> > > Could any one tell me why the nodes in Scenarios 2 don't make
>> > > interference to each other.
>> > >
>> > > Thanks a lot.
>> > >
>> > > Sincerely,
>> > > aaron
>> > >
>> > > _______________________________________________
>> > > manet mailing list
>> > > manet@ietf.org
>> > > https://www1.ietf.org/mailman/listinfo/manet
>> >
>> >
>> > _______________________________________________
>> > manet mailing list
>> > manet@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/manet
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www1.ietf.org/mailman/listinfo/manet
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet


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


From daemon@optimus.ietf.org  Thu Mar 28 02:00:08 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08898
	for <manet-archive@odin.ietf.org>; Thu, 28 Mar 2002 02:00:04 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id CAA25180
	for manet-archive@odin.ietf.org; Thu, 28 Mar 2002 02:00:06 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA23358;
	Thu, 28 Mar 2002 01:19:07 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id BAA23326
	for <manet@optimus.ietf.org>; Thu, 28 Mar 2002 01:19:04 -0500 (EST)
Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08284
	for <manet@ietf.org>; Thu, 28 Mar 2002 01:19:00 -0500 (EST)
Received: from dagger.cc.vt.edu (IDENT:mirapoint@dagger-lb.cc.vt.edu [10.1.1.11])
	by lennier.cc.vt.edu (8.11.4/8.11.4) with ESMTP id g2S6J0I38353;
	Thu, 28 Mar 2002 01:19:00 -0500 (EST)
Received: from zathras (zathras.cc.vt.edu [198.82.162.117])
	by dagger.cc.vt.edu (Mirapoint)
	with ESMTP id AWH25137;
	Thu, 28 Mar 2002 01:05:21 -0500 (EST)
X-WebMail-UserID:  vdham
Date: Thu, 28 Mar 2002 01:19:00 -0500
From: Vikram Dham  <vdham@vt.edu>
To: John Stine <jstine@mitre.org>
Cc: manet <manet@ietf.org>
X-EXP32-SerialNo: 00002964
Subject: RE: [manet] About IEEE802.11 model in OPNET
Message-ID: <3CA305A2@zathras>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: WebMail (Hydra) SMTP v3.61
Content-Transfer-Encoding: 7bit
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 7bit

Dear John,

         If you manipulate  OPC_TDA_STATUS beyond dra_power stage, then you 
could be attempting to access destroyed packets (NOISE PACKETS) in later 
stages and that is why you got the error. As mentioned in OPNET's email you 
need to use another TDA to maintain packet status and set OPC_TDA_STATUS equal 
to valid for all packets so all packets are forced through all stages. I have 
just completed running a simulations scenario which takes care of interference 
from other transmissions going around. During debugging I have observed that 
interference from other transmissions is accounted for.

With Best Regards

Vikram Dham





>===== Original Message From John Stine <jstine@mitre.org> =====
>Dear Vikram,
>
>	This was our first instinct but the OPNET kernel does not allow it.
>The issue is, when is the latest you can set a packet's status to
>noise.  The answer is the power stage.  Below is the text of a message I
>got from OPNET technical support when I asked this question.  I called
>after I noticed my simulation didn't work when I waited until the SNR
>stage to set the sig_lock attribute and the match status.
>
>*** TEXT OF MESSAGE FROM OPNET
>SUPPORT************************************
>
>It sounds like you are setting OPC_TDA_RA_MATCH_STATUS to .._NOISE in
>the
>SNR stage. The kernel expects the MATCH_STATUS TDA to be set at the
>latest
>by the power stage, and therefore, modifying it in the SNR stage may
>result
>in unexplained behaviour, including possibly the abort that you observe.
>At
>any rate, changing the TDA in the SNR stage will not prevent the kernel
>from invoking the following stages (ber, etc.) because the kernel will
>still treat it as a valid packet.
>
>Therefore, we suggest that you try another approach to achieve the same
>goal. For example, you could mark all potential packets as VALID in the
>power stage and define your own TDA called "MY_MATCH_STATUS" and set
>this
>to noise in the SNR stage if the conditions so dictate. However, since
>the
>kernel does not know about this TDA, all the stages following the SNR
>stage, i.e., ber, error, ecc will still be invoked by the kernel for
>this
>packet that has its MY_MATCH_STATUS TDA set to NOISE. Therefore, you
>will
>have to access this TDA in the last few stages and immediately exit
>using a
>FOUT if the MY_MATCH_STATUS is set to NOISE.
>
>*****************************************************************************
**
>
>So it may be possible to use the SNR but not without an additional data
>structure to keep track of which packets are valid.  Since I cannot see
>what happens inside the kernel I decided not to circumvent OPNET's
>plan.  Not modeling signal lock based on SNR has little effect in the
>performance of the model.  If SNR is a factor, the newly arriving packet
>that we lock onto is likely to have errors and not be accepted. If we
>successfully account for SNR, the duration of this packet would be
>sensed as a busy channel.   So, in both cases, the effect on the
>receiving node is the same.
>
>
>John
>
>Vikram Dham wrote:
>>
>> Dear John & Kevin:
>>
>>    I agree with your pointers regarding pipeline stage.I would like to add
>> that instead of setting value of signal lock  & packet status at
>> manta_power.ps.c, you can move it to manta_snr.ps.c stage to determine
>> whether signal lock should be set or not and whether the packet is to be
>> stamped as *noise* or *valid* packet. This would take into account
>> interference due to other nodes without need for maintaining any additional
>> data structure.  For doing this you will have to maintain an additional TDA
>> RCV_FLAG  which should be set during the first pass of the packet through
>> the manta_snr.ps.c stage.
>>
>> I hope the above helps.
>>
>> With Best Regards
>>
>> Vikram Dham
>> Graduate Research Assistant
>> Alexandria Research Institute
>> Virginia Tech,USA
>>
>> ----- Original Message -----
>> From: "John Stine" <jstine@mitre.org>
>> To: "danaus" <licheng@sjtu.edu.cn>
>> Cc: <manet@ietf.org>
>> Sent: Wednesday, March 27, 2002 9:12 AM
>> Subject: Re: [manet] About IEEE802.11 model in OPNET
>>
>> > Opnet's wlan_mac and the support pipeline stages take some liberty in
>> > modeling the physical layer based on the assumption that in the intended
>> > network all nodes should be within range of each other.  As a result,
>> > the model does not model interference correctly, but uses collisions
>> > only as the cause of failure.  This is a severe problem when one is
>> > studying ad hoc networking and wants to evaluate spatial reuse of the
>> > channel.  Two nodes in a network cannot successfully transmit
>> > simultaneously, despite separation distance.  We addressed this problem
>> > in our modifications to OPNET's models for Kevin Grace's MobileMesh
>> > protocols.  You should have received a message from Kevin about the
>> > release of these models.  If you did not receive it, the text of Kevin's
>> > message follows.
>> >
>> > The OPNET models are for version 7.0.B but they are well documented so
>> > with a little effort one can apply the changes to the 8.0.C version.  We
>> > provided these models to OPNET and they have given us the indication
>> > that they will incorporate our recommendations into a future release of
>> > their product.
>> >
>> > In the mean time, I would recommend anyone using the OPNET wlan_mac
>> > model to study ad hoc networks to look at our observations and
>> > recommendations. (See Readme-MobileMeshOpnet.pdf.)  Many conclusions
>> > based on modeling in OPNET may need to be re-evaluated.
>> >
>> > John
>> >
>> > Kevin's message follows:
>> >
>> > Opnet simulation models of the MobileMesh Routing Protocol and
>> > MobileMesh Link Discovery Protocol are now available from Opnet's
>> > website:
>> >
>> >  ftp://opguest:opguest@corporate7.opnet.com/433/
>> >
>> > Included in this distribution are numerous modifications and bug fixes
>> > to the 802.11 wireless LAN process model and related pipeline
>> > stages.
>> >
>> > Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
>> > distribution for more details.
>> >
>> > Information about the MobileMesh protocols and Open Source Linux
>> > distribution
>> > is available at:
>> >
>> >  http://www.mitre.org/tech_transfer/mobilemesh/
>> >
>> > -Kevin
>> >
>> > danaus wrote:
>> > >
>> > > Hi,
>> > >
>> > > Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C
>> ?
>> > > I encounter a strange problem when I make the following simulation 
using
>> OPNET:
>> > > --------------
>> > > WLAN Scenarios 1:
>> > > Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
>> > > each node random selects a destination and transmits some packets.
>> > >
>> > > WLAN Scenarios 2:
>> > > Same configured as the above Scenarios 1 except that the number of
>> > > nodes is twenty.
>> > > --------------
>> > > I have expected that one node's throughput in Scenarios 2 should
>> > > much lower than that in Scenarios 1. But the simulation results
>> > > show that the throughput of each node is as same as that in
>> > > Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
>> > >
>> > > Could any one tell me why the nodes in Scenarios 2 don't make
>> > > interference to each other.
>> > >
>> > > Thanks a lot.
>> > >
>> > > Sincerely,
>> > > aaron
>> > >
>> > > _______________________________________________
>> > > manet mailing list
>> > > manet@ietf.org
>> > > https://www1.ietf.org/mailman/listinfo/manet
>> >
>> >
>> > _______________________________________________
>> > manet mailing list
>> > manet@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/manet
>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www1.ietf.org/mailman/listinfo/manet
>
>
>_______________________________________________
>manet mailing list
>manet@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet


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



From manet-admin@ietf.org  Thu Mar 28 03:59:26 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19223
	for <manet-archive@odin.ietf.org>; Thu, 28 Mar 2002 03:59:25 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28911;
	Thu, 28 Mar 2002 03:22:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28885
	for <manet@optimus.ietf.org>; Thu, 28 Mar 2002 03:22:42 -0500 (EST)
Received: from tc-mail.insa-lyon.fr (tc-mail.insa-lyon.fr [134.214.202.113])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18450
	for <manet@ietf.org>; Thu, 28 Mar 2002 03:22:38 -0500 (EST)
From: ncordier@telecom.insa-lyon.fr
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tc-mail.insa-lyon.fr (Postfix) with ESMTP id 3376D13A02
	for <manet@ietf.org>; Thu, 28 Mar 2002 09:19:10 +0100 (CET)
Received: by tc-mail.insa-lyon.fr (Postfix, from userid 1151)
	id CDD4913A01; Thu, 28 Mar 2002 09:19:09 +0100 (CET)
To: manet@ietf.org
Message-ID: <1017303549.3ca2d1fdc720e@tc-mail.insa-lyon.fr>
Date: Thu, 28 Mar 2002 09:19:09 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.7
X-Originating-IP: 134.214.79.166
X-Virus-Scanned: by AMaViS snapshot-20010714
Content-Transfer-Encoding: 8bit
Subject: [manet] HELP - GLOMOSIM
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

I would like to implement power control procedures in GloMoSim. But I need routing protocols that are 
not implemented in the lastest version of Glomosim (2.03) like OLSR, TORA, TBRPF, IERP, IARP, 
BRP, FSDSR...
Is anybody know where I can find these routing protocols for GloMoSim?

Thanks for your help





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


From daemon@optimus.ietf.org  Thu Mar 28 05:12:45 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA19229
	for <manet-archive@odin.ietf.org>; Thu, 28 Mar 2002 03:59:26 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id DAA01182
	for manet-archive@odin.ietf.org; Thu, 28 Mar 2002 03:59:28 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28911;
	Thu, 28 Mar 2002 03:22:45 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA28885
	for <manet@optimus.ietf.org>; Thu, 28 Mar 2002 03:22:42 -0500 (EST)
Received: from tc-mail.insa-lyon.fr (tc-mail.insa-lyon.fr [134.214.202.113])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18450
	for <manet@ietf.org>; Thu, 28 Mar 2002 03:22:38 -0500 (EST)
From: ncordier@telecom.insa-lyon.fr
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tc-mail.insa-lyon.fr (Postfix) with ESMTP id 3376D13A02
	for <manet@ietf.org>; Thu, 28 Mar 2002 09:19:10 +0100 (CET)
Received: by tc-mail.insa-lyon.fr (Postfix, from userid 1151)
	id CDD4913A01; Thu, 28 Mar 2002 09:19:09 +0100 (CET)
To: manet@ietf.org
Message-ID: <1017303549.3ca2d1fdc720e@tc-mail.insa-lyon.fr>
Date: Thu, 28 Mar 2002 09:19:09 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: IMP/PHP IMAP webmail program 2.2.7
X-Originating-IP: 134.214.79.166
X-Virus-Scanned: by AMaViS snapshot-20010714
Content-Transfer-Encoding: 8bit
Subject: [manet] HELP - GLOMOSIM
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Hi,

I would like to implement power control procedures in GloMoSim. But I need routing protocols that are 
not implemented in the lastest version of Glomosim (2.03) like OLSR, TORA, TBRPF, IERP, IARP, 
BRP, FSDSR...
Is anybody know where I can find these routing protocols for GloMoSim?

Thanks for your help





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



From manet-admin@ietf.org  Thu Mar 28 22:06:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23336
	for <manet-archive@odin.ietf.org>; Thu, 28 Mar 2002 22:06:37 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA29083;
	Thu, 28 Mar 2002 21:35:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA29034
	for <manet@optimus.ietf.org>; Thu, 28 Mar 2002 21:35:37 -0500 (EST)
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.164.217])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22017
	for <manet@ietf.org>; Thu, 28 Mar 2002 21:35:32 -0500 (EST)
Received: from paulnb (paul1.etri.re.kr [129.254.165.60])
	by pec.etri.re.kr (8.10.0/8.10.0) with SMTP id g2T2e4Z11186;
	Fri, 29 Mar 2002 11:40:05 +0900 (KST)
Message-ID: <00be01c1d6ca$52d7b250$3ca5fe81@6neat.net>
From: "JaeHoon Jeong" <paul@etri.re.kr>
To: "Elizabeth M. Belding-Royer" <eroyer@cs.ucsb.edu>
Cc: "MANET WG" <manet@ietf.org>, "active" <active@krv6.net>
References: <Pine.GSO.4.21.0203271437140.29491-100000@saguaro>
Subject: Re: [manet] 1st AODV Interop a Success!
Date: Fri, 29 Mar 2002 11:34:59 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id VAA29038
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Dear  Elizabeth,

I am Jaehoon, researcher of ETRI in Korea.
ETRI is under the development of IPv6 ad-hoc multicast application such as video-conferencing.
Because ETRI thought there are no implementation of IPv6 AODV and IPv6 MAODV,
ETRI planned to implement IPv6 AODV and IPv6 MAODV for itself.
We are pleased to hear the news from you. We would like to know if we can get  IPv6 AODV
source code from anyone or any organization. We think the reference will be helpful for us.
I also wonder if IPv4 MAODV or IPv6 MAODV has been already implemented.
Thanks in advance.

Regards,
Jaehoon

----- Original Message ----- 
From: "Elizabeth M. Belding-Royer" <eroyer@cs.ucsb.edu>
To: <manet@ietf.org>; <aodvimpl-public@lists.sourceforge.net>
Cc: <fenner@research.att.com>
Sent: Thursday, March 28, 2002 7:45 AM
Subject: [manet] 1st AODV Interop a Success!


> 
> We are pleased to announce a successful 1st AODV Interop.
> The event was held at the University of California, Santa Barbara
> on March 25 and 26th, 2002.  Attending were four IPv4 implementations
> and two IPv6 implementations.  
> 
> Interoperation of the IPv4 implemenations was very successful.  
> Operation was tested over wired Ethernet, over wireless links 
> using ipTables to provide binary link connectivity, and over
> wireless links using obstacles to provide link disconnections.  
> The latter test included nodes distributed throughout a building, 
> and route discovery and web page retrieval over a four node path.  
> Route discovery, link break detection, and subsequent route repair 
> through a different intermediate node was tested with the four
> implementations and all successfully worked.  Networks with as
> many as seven nodes were tested.
> 
> The IPv6 implementations successfully interoperated with
> hello-based and reactive route discovery.  A more limited set of
> tests (less than 3 hops) were performed with the IPv6 implementations,
> primarily due to lack of adequate filtering support for IPv6 on the 
> tested platforms, and a smaller number of available implementations. 
> These tests provided the first evidence that the same interoperation 
> as with IPv4 is feasible using the IPv6 version of the protocol.
> 
> Further details about the event are forthcoming, once post-processing
> is completed.
> 
> Thanks to all who attended and helped plan the event!
> 
> Elizabeth
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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


From daemon@optimus.ietf.org  Thu Mar 28 22:06:37 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23344
	for <manet-archive@odin.ietf.org>; Thu, 28 Mar 2002 22:06:37 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id WAA00553
	for manet-archive@odin.ietf.org; Thu, 28 Mar 2002 22:06:40 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA29083;
	Thu, 28 Mar 2002 21:35:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA29034
	for <manet@optimus.ietf.org>; Thu, 28 Mar 2002 21:35:37 -0500 (EST)
Received: from pec.etri.re.kr (pec.etri.re.kr [129.254.164.217])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22017
	for <manet@ietf.org>; Thu, 28 Mar 2002 21:35:32 -0500 (EST)
Received: from paulnb (paul1.etri.re.kr [129.254.165.60])
	by pec.etri.re.kr (8.10.0/8.10.0) with SMTP id g2T2e4Z11186;
	Fri, 29 Mar 2002 11:40:05 +0900 (KST)
Message-ID: <00be01c1d6ca$52d7b250$3ca5fe81@6neat.net>
From: "JaeHoon Jeong" <paul@etri.re.kr>
To: "Elizabeth M. Belding-Royer" <eroyer@cs.ucsb.edu>
Cc: "MANET WG" <manet@ietf.org>, "active" <active@krv6.net>
References: <Pine.GSO.4.21.0203271437140.29491-100000@saguaro>
Subject: Re: [manet] 1st AODV Interop a Success!
Date: Fri, 29 Mar 2002 11:34:59 +0900
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by optimus.ietf.org id VAA29038
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org
Content-Transfer-Encoding: 8bit

Dear  Elizabeth,

I am Jaehoon, researcher of ETRI in Korea.
ETRI is under the development of IPv6 ad-hoc multicast application such as video-conferencing.
Because ETRI thought there are no implementation of IPv6 AODV and IPv6 MAODV,
ETRI planned to implement IPv6 AODV and IPv6 MAODV for itself.
We are pleased to hear the news from you. We would like to know if we can get  IPv6 AODV
source code from anyone or any organization. We think the reference will be helpful for us.
I also wonder if IPv4 MAODV or IPv6 MAODV has been already implemented.
Thanks in advance.

Regards,
Jaehoon

----- Original Message ----- 
From: "Elizabeth M. Belding-Royer" <eroyer@cs.ucsb.edu>
To: <manet@ietf.org>; <aodvimpl-public@lists.sourceforge.net>
Cc: <fenner@research.att.com>
Sent: Thursday, March 28, 2002 7:45 AM
Subject: [manet] 1st AODV Interop a Success!


> 
> We are pleased to announce a successful 1st AODV Interop.
> The event was held at the University of California, Santa Barbara
> on March 25 and 26th, 2002.  Attending were four IPv4 implementations
> and two IPv6 implementations.  
> 
> Interoperation of the IPv4 implemenations was very successful.  
> Operation was tested over wired Ethernet, over wireless links 
> using ipTables to provide binary link connectivity, and over
> wireless links using obstacles to provide link disconnections.  
> The latter test included nodes distributed throughout a building, 
> and route discovery and web page retrieval over a four node path.  
> Route discovery, link break detection, and subsequent route repair 
> through a different intermediate node was tested with the four
> implementations and all successfully worked.  Networks with as
> many as seven nodes were tested.
> 
> The IPv6 implementations successfully interoperated with
> hello-based and reactive route discovery.  A more limited set of
> tests (less than 3 hops) were performed with the IPv6 implementations,
> primarily due to lack of adequate filtering support for IPv6 on the 
> tested platforms, and a smaller number of available implementations. 
> These tests provided the first evidence that the same interoperation 
> as with IPv4 is feasible using the IPv6 version of the protocol.
> 
> Further details about the event are forthcoming, once post-processing
> is completed.
> 
> Thanks to all who attended and helped plan the event!
> 
> Elizabeth
> 
> 
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/manet

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



From manet-admin@ietf.org  Fri Mar 29 12:12:11 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23879
	for <manet-archive@odin.ietf.org>; Fri, 29 Mar 2002 12:12:11 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15747;
	Fri, 29 Mar 2002 11:49:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15715
	for <manet@optimus.ietf.org>; Fri, 29 Mar 2002 11:49:07 -0500 (EST)
Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22262
	for <manet@ietf.org>; Fri, 29 Mar 2002 11:49:03 -0500 (EST)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id g2TGma825923;
	Fri, 29 Mar 2002 11:48:36 -0500 (EST)
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id g2TGmVH16462;
	Fri, 29 Mar 2002 11:48:31 -0500 (EST)
Received: from dhcp-103-210.mitre.org (128.29.103.210) by mailhub1.mitre.org with SMTP
        id 9682894; Fri, 29 Mar 2002 11:48:18 -0500
Message-ID: <3CA49AD4.C482A7AF@mitre.org>
Date: Fri, 29 Mar 2002 11:48:21 -0500
From: John Stine <jstine@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: manet@ietf.org, licheng@sjtu.edu.cn
Subject: [Fwd: [manet] About IEEE802.11 model in OPNET]
Content-Type: multipart/mixed;
 boundary="------------8FCBF36B87A927711A859E85"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

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

Aaron,

I am sorry, not getting this message returned to me indicated I did not
send it to the manet list.  There is more information on the
deficiencies of the current OPNET wlan_mac model for ad hoc network
modeling.  The specific problem you are having is alluded to in the
text.  OPNET uses the receiver busy stat to indicate the channel busy
condition.  It is set early in the pipeline stages based solely on
whether the sender and the destination channels match.  The result is
when one node transmits, all other nodes sense the channel busy
regardless of separation distance.  This prevents spatial reuse and also
eliminates the problems encountered in ad hoc networking, i.e. hidden
node effects, exposed nodes, and the near far problem.  Please note,
however, that a subsequent pipeline stage makes certain that you can
only communicate to a node up to the distance specified in the range
parameter that is set in the simulation attributes.  You will see
packets fail based on separation distance.

John
--------------8FCBF36B87A927711A859E85
Content-Type: message/rfc822
Content-Disposition: inline

Message-ID: <3CA37692.2B6D5B59@mitre.org>
Date: Thu, 28 Mar 2002 15:01:22 -0500
From: John Stine <jstine@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vikram Dham <vdham@vt.edu>
Subject: Re: [manet] About IEEE802.11 model in OPNET
References: <3CA305A2@zathras>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear Vikram,

	I agree that this additional TDA can allow one to distinguish a valid
packet from a noise packet in the latter pipeline stages and that this
would be a more accurate model.  However, the fidelity of this model
only affects a small number of packet receptions and introduces another
problem, assessing the channel as busy. 

	I can think of only one situation that this model resolves that ours
does not.  It occurs as follows.  A node receives a signal that exceeds
the threshold power level but other transmissions keep the SIR too low
for it to capture the signal. Then, during this same transmission,
another node transmits and it is received at a much higher power,
sufficient to exceed the SIR threshold even with the first signal
present. In this case, the second packet could be received and would not
have been if the receiver was locked onto the first packet.  The
question is, how frequently will this sequence of events occur.  The
802.11 MAC tries to prevent it from occurring.

 	Here is the second issue.  How do you insure the clear channel
assessment mechanism works correctly?  The OPNET wlan_mac process uses
the receiver busy stat.  This is triggered in the propdel stage so it is
not useful unless we mark the packet as invalid before this stage. (This
is not an issue in the OPNET model and is what makes it a bad solution
for modeling ad hoc networks.  Nodes consider the channel busy although
in reality they could exchange packets)  A second option is to use the
received power.  The received power stat wire interrupt is triggered
everytime a power that meets the trigger criteria is written to a
packets power TDA in the power stage.  Note, it is associated with the
packet rather than the receiver.  As a result, it is not possible to
distinguish a power level going from high to low for a transmission that
is currently causing the channel to be considered busy and a distant
transmission that meets the same power level criteria.  The SNR
statistic would also be problematic since it could be triggered several
times per packet and is not triggered at the end of a packet.  So I
model the channel busy condition through the reception of a packet. 
Passing the power threshold makes the channel busy and then receiving
the packet ends the busy condition.  IF the packet is received without
errors then the node processes it, otherwise it was just a busy
condition.  I would be interested in knowing your solution to this
problem and if you implemented it with the OPNET wlan_mac process.

	It is this second issue that caused me to commit to the model I
created.


John
	

Vikram Dham wrote:
> 
> Dear John,
> 
>          If you manipulate  OPC_TDA_STATUS beyond dra_power stage, then you
> could be attempting to access destroyed packets (NOISE PACKETS) in later
> stages and that is why you got the error. As mentioned in OPNET's email you
> need to use another TDA to maintain packet status and set OPC_TDA_STATUS equal
> to valid for all packets so all packets are forced through all stages. I have
> just completed running a simulations scenario which takes care of interference
> from other transmissions going around. During debugging I have observed that
> interference from other transmissions is accounted for.
> 
> With Best Regards
> 
> Vikram Dham
> 
> >===== Original Message From John Stine <jstine@mitre.org> =====
> >Dear Vikram,
> >
> >       This was our first instinct but the OPNET kernel does not allow it.
> >The issue is, when is the latest you can set a packet's status to
> >noise.  The answer is the power stage.  Below is the text of a message I
> >got from OPNET technical support when I asked this question.  I called
> >after I noticed my simulation didn't work when I waited until the SNR
> >stage to set the sig_lock attribute and the match status.
> >
> >*** TEXT OF MESSAGE FROM OPNET
> >SUPPORT************************************
> >
> >It sounds like you are setting OPC_TDA_RA_MATCH_STATUS to .._NOISE in
> >the
> >SNR stage. The kernel expects the MATCH_STATUS TDA to be set at the
> >latest
> >by the power stage, and therefore, modifying it in the SNR stage may
> >result
> >in unexplained behaviour, including possibly the abort that you observe.
> >At
> >any rate, changing the TDA in the SNR stage will not prevent the kernel
> >from invoking the following stages (ber, etc.) because the kernel will
> >still treat it as a valid packet.
> >
> >Therefore, we suggest that you try another approach to achieve the same
> >goal. For example, you could mark all potential packets as VALID in the
> >power stage and define your own TDA called "MY_MATCH_STATUS" and set
> >this
> >to noise in the SNR stage if the conditions so dictate. However, since
> >the
> >kernel does not know about this TDA, all the stages following the SNR
> >stage, i.e., ber, error, ecc will still be invoked by the kernel for
> >this
> >packet that has its MY_MATCH_STATUS TDA set to NOISE. Therefore, you
> >will
> >have to access this TDA in the last few stages and immediately exit
> >using a
> >FOUT if the MY_MATCH_STATUS is set to NOISE.
> >
> >*****************************************************************************
> **
> >
> >So it may be possible to use the SNR but not without an additional data
> >structure to keep track of which packets are valid.  Since I cannot see
> >what happens inside the kernel I decided not to circumvent OPNET's
> >plan.  Not modeling signal lock based on SNR has little effect in the
> >performance of the model.  If SNR is a factor, the newly arriving packet
> >that we lock onto is likely to have errors and not be accepted. If we
> >successfully account for SNR, the duration of this packet would be
> >sensed as a busy channel.   So, in both cases, the effect on the
> >receiving node is the same.
> >
> >
> >John
> >
> >Vikram Dham wrote:
> >>
> >> Dear John & Kevin:
> >>
> >>    I agree with your pointers regarding pipeline stage.I would like to add
> >> that instead of setting value of signal lock  & packet status at
> >> manta_power.ps.c, you can move it to manta_snr.ps.c stage to determine
> >> whether signal lock should be set or not and whether the packet is to be
> >> stamped as *noise* or *valid* packet. This would take into account
> >> interference due to other nodes without need for maintaining any additional
> >> data structure.  For doing this you will have to maintain an additional TDA
> >> RCV_FLAG  which should be set during the first pass of the packet through
> >> the manta_snr.ps.c stage.
> >>
> >> I hope the above helps.
> >>
> >> With Best Regards
> >>
> >> Vikram Dham
> >> Graduate Research Assistant
> >> Alexandria Research Institute
> >> Virginia Tech,USA
> >>
> >> ----- Original Message -----
> >> From: "John Stine" <jstine@mitre.org>
> >> To: "danaus" <licheng@sjtu.edu.cn>
> >> Cc: <manet@ietf.org>
> >> Sent: Wednesday, March 27, 2002 9:12 AM
> >> Subject: Re: [manet] About IEEE802.11 model in OPNET
> >>
> >> > Opnet's wlan_mac and the support pipeline stages take some liberty in
> >> > modeling the physical layer based on the assumption that in the intended
> >> > network all nodes should be within range of each other.  As a result,
> >> > the model does not model interference correctly, but uses collisions
> >> > only as the cause of failure.  This is a severe problem when one is
> >> > studying ad hoc networking and wants to evaluate spatial reuse of the
> >> > channel.  Two nodes in a network cannot successfully transmit
> >> > simultaneously, despite separation distance.  We addressed this problem
> >> > in our modifications to OPNET's models for Kevin Grace's MobileMesh
> >> > protocols.  You should have received a message from Kevin about the
> >> > release of these models.  If you did not receive it, the text of Kevin's
> >> > message follows.
> >> >
> >> > The OPNET models are for version 7.0.B but they are well documented so
> >> > with a little effort one can apply the changes to the 8.0.C version.  We
> >> > provided these models to OPNET and they have given us the indication
> >> > that they will incorporate our recommendations into a future release of
> >> > their product.
> >> >
> >> > In the mean time, I would recommend anyone using the OPNET wlan_mac
> >> > model to study ad hoc networks to look at our observations and
> >> > recommendations. (See Readme-MobileMeshOpnet.pdf.)  Many conclusions
> >> > based on modeling in OPNET may need to be re-evaluated.
> >> >
> >> > John
> >> >
> >> > Kevin's message follows:
> >> >
> >> > Opnet simulation models of the MobileMesh Routing Protocol and
> >> > MobileMesh Link Discovery Protocol are now available from Opnet's
> >> > website:
> >> >
> >> >  ftp://opguest:opguest@corporate7.opnet.com/433/
> >> >
> >> > Included in this distribution are numerous modifications and bug fixes
> >> > to the 802.11 wireless LAN process model and related pipeline
> >> > stages.
> >> >
> >> > Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
> >> > distribution for more details.
> >> >
> >> > Information about the MobileMesh protocols and Open Source Linux
> >> > distribution
> >> > is available at:
> >> >
> >> >  http://www.mitre.org/tech_transfer/mobilemesh/
> >> >
> >> > -Kevin
> >> >
> >> > danaus wrote:
> >> > >
> >> > > Hi,
> >> > >
> >> > > Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C
> >> ?
> >> > > I encounter a strange problem when I make the following simulation
> using
> >> OPNET:
> >> > > --------------
> >> > > WLAN Scenarios 1:
> >> > > Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> >> > > each node random selects a destination and transmits some packets.
> >> > >
> >> > > WLAN Scenarios 2:
> >> > > Same configured as the above Scenarios 1 except that the number of
> >> > > nodes is twenty.
> >> > > --------------
> >> > > I have expected that one node's throughput in Scenarios 2 should
> >> > > much lower than that in Scenarios 1. But the simulation results
> >> > > show that the throughput of each node is as same as that in
> >> > > Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> >> > >
> >> > > Could any one tell me why the nodes in Scenarios 2 don't make
> >> > > interference to each other.
> >> > >
> >> > > Thanks a lot.
> >> > >
> >> > > Sincerely,
> >> > > aaron
> >> > >
> >> > > _______________________________________________
> >> > > manet mailing list
> >> > > manet@ietf.org
> >> > > https://www1.ietf.org/mailman/listinfo/manet
> >> >
> >> >
> >> > _______________________________________________
> >> > manet mailing list
> >> > manet@ietf.org
> >> > https://www1.ietf.org/mailman/listinfo/manet
> >>
> >> _______________________________________________
> >> manet mailing list
> >> manet@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/manet
> >
> >
> >_______________________________________________
> >manet mailing list
> >manet@ietf.org
> >https://www1.ietf.org/mailman/listinfo/manet

--------------8FCBF36B87A927711A859E85--



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


From daemon@optimus.ietf.org  Fri Mar 29 12:12:16 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23887
	for <manet-archive@odin.ietf.org>; Fri, 29 Mar 2002 12:12:12 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id MAA18281
	for manet-archive@odin.ietf.org; Fri, 29 Mar 2002 12:12:15 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15747;
	Fri, 29 Mar 2002 11:49:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA15715
	for <manet@optimus.ietf.org>; Fri, 29 Mar 2002 11:49:07 -0500 (EST)
Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [129.83.20.90])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22262
	for <manet@ietf.org>; Fri, 29 Mar 2002 11:49:03 -0500 (EST)
Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58])
	by smtpproxy1.mitre.org (8.11.3/8.11.3) with ESMTP id g2TGma825923;
	Fri, 29 Mar 2002 11:48:36 -0500 (EST)
Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31])
	by smtpsrv1.mitre.org (8.11.3/8.11.3) with ESMTP id g2TGmVH16462;
	Fri, 29 Mar 2002 11:48:31 -0500 (EST)
Received: from dhcp-103-210.mitre.org (128.29.103.210) by mailhub1.mitre.org with SMTP
        id 9682894; Fri, 29 Mar 2002 11:48:18 -0500
Message-ID: <3CA49AD4.C482A7AF@mitre.org>
Date: Fri, 29 Mar 2002 11:48:21 -0500
From: John Stine <jstine@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: manet@ietf.org, licheng@sjtu.edu.cn
Subject: [Fwd: [manet] About IEEE802.11 model in OPNET]
Content-Type: multipart/mixed;
 boundary="------------8FCBF36B87A927711A859E85"
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

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

Aaron,

I am sorry, not getting this message returned to me indicated I did not
send it to the manet list.  There is more information on the
deficiencies of the current OPNET wlan_mac model for ad hoc network
modeling.  The specific problem you are having is alluded to in the
text.  OPNET uses the receiver busy stat to indicate the channel busy
condition.  It is set early in the pipeline stages based solely on
whether the sender and the destination channels match.  The result is
when one node transmits, all other nodes sense the channel busy
regardless of separation distance.  This prevents spatial reuse and also
eliminates the problems encountered in ad hoc networking, i.e. hidden
node effects, exposed nodes, and the near far problem.  Please note,
however, that a subsequent pipeline stage makes certain that you can
only communicate to a node up to the distance specified in the range
parameter that is set in the simulation attributes.  You will see
packets fail based on separation distance.

John
--------------8FCBF36B87A927711A859E85
Content-Type: message/rfc822
Content-Disposition: inline

Message-ID: <3CA37692.2B6D5B59@mitre.org>
Date: Thu, 28 Mar 2002 15:01:22 -0500
From: John Stine <jstine@mitre.org>
Organization: The MITRE Corporation
X-Mailer: Mozilla 4.76 [en]C-20010313M  (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Vikram Dham <vdham@vt.edu>
Subject: Re: [manet] About IEEE802.11 model in OPNET
References: <3CA305A2@zathras>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Dear Vikram,

	I agree that this additional TDA can allow one to distinguish a valid
packet from a noise packet in the latter pipeline stages and that this
would be a more accurate model.  However, the fidelity of this model
only affects a small number of packet receptions and introduces another
problem, assessing the channel as busy. 

	I can think of only one situation that this model resolves that ours
does not.  It occurs as follows.  A node receives a signal that exceeds
the threshold power level but other transmissions keep the SIR too low
for it to capture the signal. Then, during this same transmission,
another node transmits and it is received at a much higher power,
sufficient to exceed the SIR threshold even with the first signal
present. In this case, the second packet could be received and would not
have been if the receiver was locked onto the first packet.  The
question is, how frequently will this sequence of events occur.  The
802.11 MAC tries to prevent it from occurring.

 	Here is the second issue.  How do you insure the clear channel
assessment mechanism works correctly?  The OPNET wlan_mac process uses
the receiver busy stat.  This is triggered in the propdel stage so it is
not useful unless we mark the packet as invalid before this stage. (This
is not an issue in the OPNET model and is what makes it a bad solution
for modeling ad hoc networks.  Nodes consider the channel busy although
in reality they could exchange packets)  A second option is to use the
received power.  The received power stat wire interrupt is triggered
everytime a power that meets the trigger criteria is written to a
packets power TDA in the power stage.  Note, it is associated with the
packet rather than the receiver.  As a result, it is not possible to
distinguish a power level going from high to low for a transmission that
is currently causing the channel to be considered busy and a distant
transmission that meets the same power level criteria.  The SNR
statistic would also be problematic since it could be triggered several
times per packet and is not triggered at the end of a packet.  So I
model the channel busy condition through the reception of a packet. 
Passing the power threshold makes the channel busy and then receiving
the packet ends the busy condition.  IF the packet is received without
errors then the node processes it, otherwise it was just a busy
condition.  I would be interested in knowing your solution to this
problem and if you implemented it with the OPNET wlan_mac process.

	It is this second issue that caused me to commit to the model I
created.


John
	

Vikram Dham wrote:
> 
> Dear John,
> 
>          If you manipulate  OPC_TDA_STATUS beyond dra_power stage, then you
> could be attempting to access destroyed packets (NOISE PACKETS) in later
> stages and that is why you got the error. As mentioned in OPNET's email you
> need to use another TDA to maintain packet status and set OPC_TDA_STATUS equal
> to valid for all packets so all packets are forced through all stages. I have
> just completed running a simulations scenario which takes care of interference
> from other transmissions going around. During debugging I have observed that
> interference from other transmissions is accounted for.
> 
> With Best Regards
> 
> Vikram Dham
> 
> >===== Original Message From John Stine <jstine@mitre.org> =====
> >Dear Vikram,
> >
> >       This was our first instinct but the OPNET kernel does not allow it.
> >The issue is, when is the latest you can set a packet's status to
> >noise.  The answer is the power stage.  Below is the text of a message I
> >got from OPNET technical support when I asked this question.  I called
> >after I noticed my simulation didn't work when I waited until the SNR
> >stage to set the sig_lock attribute and the match status.
> >
> >*** TEXT OF MESSAGE FROM OPNET
> >SUPPORT************************************
> >
> >It sounds like you are setting OPC_TDA_RA_MATCH_STATUS to .._NOISE in
> >the
> >SNR stage. The kernel expects the MATCH_STATUS TDA to be set at the
> >latest
> >by the power stage, and therefore, modifying it in the SNR stage may
> >result
> >in unexplained behaviour, including possibly the abort that you observe.
> >At
> >any rate, changing the TDA in the SNR stage will not prevent the kernel
> >from invoking the following stages (ber, etc.) because the kernel will
> >still treat it as a valid packet.
> >
> >Therefore, we suggest that you try another approach to achieve the same
> >goal. For example, you could mark all potential packets as VALID in the
> >power stage and define your own TDA called "MY_MATCH_STATUS" and set
> >this
> >to noise in the SNR stage if the conditions so dictate. However, since
> >the
> >kernel does not know about this TDA, all the stages following the SNR
> >stage, i.e., ber, error, ecc will still be invoked by the kernel for
> >this
> >packet that has its MY_MATCH_STATUS TDA set to NOISE. Therefore, you
> >will
> >have to access this TDA in the last few stages and immediately exit
> >using a
> >FOUT if the MY_MATCH_STATUS is set to NOISE.
> >
> >*****************************************************************************
> **
> >
> >So it may be possible to use the SNR but not without an additional data
> >structure to keep track of which packets are valid.  Since I cannot see
> >what happens inside the kernel I decided not to circumvent OPNET's
> >plan.  Not modeling signal lock based on SNR has little effect in the
> >performance of the model.  If SNR is a factor, the newly arriving packet
> >that we lock onto is likely to have errors and not be accepted. If we
> >successfully account for SNR, the duration of this packet would be
> >sensed as a busy channel.   So, in both cases, the effect on the
> >receiving node is the same.
> >
> >
> >John
> >
> >Vikram Dham wrote:
> >>
> >> Dear John & Kevin:
> >>
> >>    I agree with your pointers regarding pipeline stage.I would like to add
> >> that instead of setting value of signal lock  & packet status at
> >> manta_power.ps.c, you can move it to manta_snr.ps.c stage to determine
> >> whether signal lock should be set or not and whether the packet is to be
> >> stamped as *noise* or *valid* packet. This would take into account
> >> interference due to other nodes without need for maintaining any additional
> >> data structure.  For doing this you will have to maintain an additional TDA
> >> RCV_FLAG  which should be set during the first pass of the packet through
> >> the manta_snr.ps.c stage.
> >>
> >> I hope the above helps.
> >>
> >> With Best Regards
> >>
> >> Vikram Dham
> >> Graduate Research Assistant
> >> Alexandria Research Institute
> >> Virginia Tech,USA
> >>
> >> ----- Original Message -----
> >> From: "John Stine" <jstine@mitre.org>
> >> To: "danaus" <licheng@sjtu.edu.cn>
> >> Cc: <manet@ietf.org>
> >> Sent: Wednesday, March 27, 2002 9:12 AM
> >> Subject: Re: [manet] About IEEE802.11 model in OPNET
> >>
> >> > Opnet's wlan_mac and the support pipeline stages take some liberty in
> >> > modeling the physical layer based on the assumption that in the intended
> >> > network all nodes should be within range of each other.  As a result,
> >> > the model does not model interference correctly, but uses collisions
> >> > only as the cause of failure.  This is a severe problem when one is
> >> > studying ad hoc networking and wants to evaluate spatial reuse of the
> >> > channel.  Two nodes in a network cannot successfully transmit
> >> > simultaneously, despite separation distance.  We addressed this problem
> >> > in our modifications to OPNET's models for Kevin Grace's MobileMesh
> >> > protocols.  You should have received a message from Kevin about the
> >> > release of these models.  If you did not receive it, the text of Kevin's
> >> > message follows.
> >> >
> >> > The OPNET models are for version 7.0.B but they are well documented so
> >> > with a little effort one can apply the changes to the 8.0.C version.  We
> >> > provided these models to OPNET and they have given us the indication
> >> > that they will incorporate our recommendations into a future release of
> >> > their product.
> >> >
> >> > In the mean time, I would recommend anyone using the OPNET wlan_mac
> >> > model to study ad hoc networks to look at our observations and
> >> > recommendations. (See Readme-MobileMeshOpnet.pdf.)  Many conclusions
> >> > based on modeling in OPNET may need to be re-evaluated.
> >> >
> >> > John
> >> >
> >> > Kevin's message follows:
> >> >
> >> > Opnet simulation models of the MobileMesh Routing Protocol and
> >> > MobileMesh Link Discovery Protocol are now available from Opnet's
> >> > website:
> >> >
> >> >  ftp://opguest:opguest@corporate7.opnet.com/433/
> >> >
> >> > Included in this distribution are numerous modifications and bug fixes
> >> > to the 802.11 wireless LAN process model and related pipeline
> >> > stages.
> >> >
> >> > Please refer to the file "Readme-MobileMeshOpnet.pdf" in the
> >> > distribution for more details.
> >> >
> >> > Information about the MobileMesh protocols and Open Source Linux
> >> > distribution
> >> > is available at:
> >> >
> >> >  http://www.mitre.org/tech_transfer/mobilemesh/
> >> >
> >> > -Kevin
> >> >
> >> > danaus wrote:
> >> > >
> >> > > Hi,
> >> > >
> >> > > Is there anyone here familiar with the IEEE 802.11 model in OPNET 8.0.C
> >> ?
> >> > > I encounter a strange problem when I make the following simulation
> using
> >> OPNET:
> >> > > --------------
> >> > > WLAN Scenarios 1:
> >> > > Two wlan_station_adv(fix) nodes in a 500m X 500m rectangle area,
> >> > > each node random selects a destination and transmits some packets.
> >> > >
> >> > > WLAN Scenarios 2:
> >> > > Same configured as the above Scenarios 1 except that the number of
> >> > > nodes is twenty.
> >> > > --------------
> >> > > I have expected that one node's throughput in Scenarios 2 should
> >> > > much lower than that in Scenarios 1. But the simulation results
> >> > > show that the throughput of each node is as same as that in
> >> > > Scenarios 1. The more eighteen nodes in Scenarios 2 seem do nothing.
> >> > >
> >> > > Could any one tell me why the nodes in Scenarios 2 don't make
> >> > > interference to each other.
> >> > >
> >> > > Thanks a lot.
> >> > >
> >> > > Sincerely,
> >> > > aaron
> >> > >
> >> > > _______________________________________________
> >> > > manet mailing list
> >> > > manet@ietf.org
> >> > > https://www1.ietf.org/mailman/listinfo/manet
> >> >
> >> >
> >> > _______________________________________________
> >> > manet mailing list
> >> > manet@ietf.org
> >> > https://www1.ietf.org/mailman/listinfo/manet
> >>
> >> _______________________________________________
> >> manet mailing list
> >> manet@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/manet
> >
> >
> >_______________________________________________
> >manet mailing list
> >manet@ietf.org
> >https://www1.ietf.org/mailman/listinfo/manet

--------------8FCBF36B87A927711A859E85--



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



From manet-admin@ietf.org  Sun Mar 31 23:42:43 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06249
	for <manet-archive@odin.ietf.org>; Sun, 31 Mar 2002 23:42:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA27511;
	Sun, 31 Mar 2002 23:22:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA27479
	for <manet@optimus.ietf.org>; Sun, 31 Mar 2002 23:22:05 -0500 (EST)
Received: from hawk.ece.nus.edu.sg (hawk.ece.nus.edu.sg [137.132.153.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05544
	for <manet@ietf.org>; Sun, 31 Mar 2002 23:22:00 -0500 (EST)
From: ccfoo@hawk.ece.nus.edu.sg
Received: from localhost (ccfoo@localhost)
	by hawk.ece.nus.edu.sg (8.9.3+Sun/8.9.1) with ESMTP id MAA23006;
	Mon, 1 Apr 2002 12:06:17 +0800 (SGT)
Date: Mon, 1 Apr 2002 12:06:17 +0800 (SGT)
X-Sender: ccfoo@hawk
To: manet@ietf.org
Message-ID: <Pine.GSO.4.05.10204011155030.23004-100000@hawk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Prior work on manets with ring topologies?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi,

Is there anybody currently (or in the past) who has worked on wireless
mobile ad hoc networks using ring topologies?

Are there key papers on this topic of manets with ring topologies?

Thank you and best regards,
Foo Chun Choong
Open Source Software Lab,
National University of Singapore
http://opensource.nus.edu.sg


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


From daemon@optimus.ietf.org  Sun Mar 31 23:42:57 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06268
	for <manet-archive@odin.ietf.org>; Sun, 31 Mar 2002 23:42:56 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id XAA28716
	for manet-archive@odin.ietf.org; Sun, 31 Mar 2002 23:42:46 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA27511;
	Sun, 31 Mar 2002 23:22:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id XAA27479
	for <manet@optimus.ietf.org>; Sun, 31 Mar 2002 23:22:05 -0500 (EST)
Received: from hawk.ece.nus.edu.sg (hawk.ece.nus.edu.sg [137.132.153.14])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05544
	for <manet@ietf.org>; Sun, 31 Mar 2002 23:22:00 -0500 (EST)
From: ccfoo@hawk.ece.nus.edu.sg
Received: from localhost (ccfoo@localhost)
	by hawk.ece.nus.edu.sg (8.9.3+Sun/8.9.1) with ESMTP id MAA23006;
	Mon, 1 Apr 2002 12:06:17 +0800 (SGT)
Date: Mon, 1 Apr 2002 12:06:17 +0800 (SGT)
X-Sender: ccfoo@hawk
To: manet@ietf.org
Message-ID: <Pine.GSO.4.05.10204011155030.23004-100000@hawk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [manet] Prior work on manets with ring topologies?
Sender: manet-admin@ietf.org
Errors-To: manet-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Mobile Ad-hoc Networks  <manet.ietf.org>
X-BeenThere: manet@ietf.org

Hi,

Is there anybody currently (or in the past) who has worked on wireless
mobile ad hoc networks using ring topologies?

Are there key papers on this topic of manets with ring topologies?

Thank you and best regards,
Foo Chun Choong
Open Source Software Lab,
National University of Singapore
http://opensource.nus.edu.sg


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



