From exim@www1.ietf.org  Thu Oct  2 09:08:27 2003
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 JAA17403
	for <ans-research-archive@odin.ietf.org>; Thu, 2 Oct 2003 09:08:27 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A53Bb-0006MT-Dy
	for ans-research-archive@odin.ietf.org; Thu, 02 Oct 2003 09:08:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92D83gk024447
	for ans-research-archive@odin.ietf.org; Thu, 2 Oct 2003 09:08:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A53Bb-0006ME-Ad
	for ans-research-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 09:08:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17394
	for <ans-research-web-archive@ietf.org>; Thu, 2 Oct 2003 09:07:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A53BZ-0000Gx-00
	for ans-research-web-archive@ietf.org; Thu, 02 Oct 2003 09:08:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A53BZ-0000Gt-00
	for ans-research-web-archive@ietf.org; Thu, 02 Oct 2003 09:08:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A53BZ-0006L6-F0; Thu, 02 Oct 2003 09:08:01 -0400
Received: from falcon.mail.pas.earthlink.net ([207.217.120.74])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A53Az-00069J-OL
	for ans-research@www1.ietf.org; Thu, 02 Oct 2003 09:07:25 -0400
Received: from sdn-ar-014casfrmp228.dialsprint.net ([158.252.218.230] helo=earthlink.net)
	by falcon.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 1A53Ae-0004Nl-00; Thu, 02 Oct 2003 06:07:05 -0700
Message-ID: <3F7C22F6.2010605@earthlink.net>
Date: Thu, 02 Oct 2003 06:07:02 -0700
From: Richard Ogier <ogier@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 (emach0202)
X-Accept-Language: en-us
MIME-Version: 1.0
To: Onur Arpacioglu <oa27@ece.cornell.edu>
CC: "'Cesar Santivanez'" <csantiva@bbn.com>, ans-research@www1.ietf.org
Subject: Re: [Ans-research] Absolute, optimal, sufficient scalability?
References: <005301c386a7$8ced05b0$1f88fd80@Palio>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Onur, Cesar, and all:

I want to comment on "sufficient scalability".  The following paragraph
by Onur clarifies the term and helps to support the point I will make.

> I understand what you mean. It is actually equivalent to comparing two
> methods w.r.t. a metric; Method 1: Actual routing protocol. Method 2:
> Genie routing protocol. Metric: Total bandwidth consumption (including
> traffic load). If the methods are EQUALLY scalable w.r.t. the metric
> (see section 2.6. of the draft for the definition of EQUALLY scalable),
> then your definition calls method 1 'sufficiently scalable'.

It is possible that a genie method is "more scalable" than an 
"optimally scalable" (real) method, but an "optimally scalable" 
method cannot be "more scalable" than a genie method.
Therefore, a "sufficiently scalable" method is also "optimally
scalable", so the term "sufficiently scalable" is not needed.

The reason it might not have looked this way in Cesar's original example
(using total overhead) is because total overhead is not an appropriate
choice for a metric, since it is actually the *difference* between the
total bandwidth consumption and the genie bandwidth consumption.
"Total bandwidth consumption" would be the appropriate metric in this case,
although I am not sure it should be one of the primary metrics that define
"absolute scalability" (and possibly "maximal scalability").

I would also like to make a point regarding end-to-end delay as a metric.
If the network model is such that the average distance between source
and destination is unbounded, for example O(N^0.5), then the genie method,
and an optimal method, should achieve an average end-to-end delay that
is O(N^0.5). It might therefore be better to redefine "absolute scalability"
to require only that the average end-to-end delay is proportional to the 
average number of hops between source and destination. Or perhaps omit
end-to-end delay from the set of primary metrics, and include only
per-hop delay (requiring it to be bounded by a constant).  

Regards,
Richard



_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Thu Oct  2 16:14:25 2003
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 QAA23770
	for <ans-research-archive@odin.ietf.org>; Thu, 2 Oct 2003 16:14:25 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A59ps-0007nq-A5
	for ans-research-archive@odin.ietf.org; Thu, 02 Oct 2003 16:14:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h92KE4Nh029990
	for ans-research-archive@odin.ietf.org; Thu, 2 Oct 2003 16:14:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A59ps-0007nd-6g
	for ans-research-web-archive@optimus.ietf.org; Thu, 02 Oct 2003 16:14:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23739
	for <ans-research-web-archive@ietf.org>; Thu, 2 Oct 2003 16:13:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A59pn-00067X-00
	for ans-research-web-archive@ietf.org; Thu, 02 Oct 2003 16:13:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A59pn-00067U-00
	for ans-research-web-archive@ietf.org; Thu, 02 Oct 2003 16:13:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A59po-0007mn-BH; Thu, 02 Oct 2003 16:14:00 -0400
Received: from aragorn.bbn.com ([128.33.0.62])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A59pU-0007jR-B3
	for ans-research@www1.ietf.org; Thu, 02 Oct 2003 16:13:40 -0400
Received: from bbn.com (raisin.bbn.com [128.89.80.35])
	by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id h92KCgTW001020;
	Thu, 2 Oct 2003 16:12:42 -0400 (EDT)
Message-ID: <3F7C87EC.9E2BEA72@bbn.com>
Date: Thu, 02 Oct 2003 16:17:48 -0400
From: Cesar Santivanez <csantiva@bbn.com>
Organization: BBN Technologies (a Verizon's unit)
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Richard Ogier <ogier@earthlink.net>
CC: Onur Arpacioglu <oa27@ece.cornell.edu>, ans-research@www1.ietf.org
Subject: Re: [Ans-research] Absolute, optimal, sufficient scalability?
References: <005301c386a7$8ced05b0$1f88fd80@Palio> <3F7C22F6.2010605@earthlink.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Richard,

I agree with most of your coments.  BElow I am addressing the discrepancies.

Richard Ogier wrote:

> Onur, Cesar, and all:
>
> I want to comment on "sufficient scalability".  The following paragraph
> by Onur clarifies the term and helps to support the point I will make.
>
> > I understand what you mean. It is actually equivalent to comparing two
> > methods w.r.t. a metric; Method 1: Actual routing protocol. Method 2:
> > Genie routing protocol. Metric: Total bandwidth consumption (including
> > traffic load). If the methods are EQUALLY scalable w.r.t. the metric
> > (see section 2.6. of the draft for the definition of EQUALLY scalable),
> > then your definition calls method 1 'sufficiently scalable'.
>
> It is possible that a genie method is "more scalable" than an
> "optimally scalable" (real) method, but an "optimally scalable"
> method cannot be "more scalable" than a genie method.
> Therefore, a "sufficiently scalable" method is also "optimally
> scalable", so the term "sufficiently scalable" is not needed.

A sufficient scalable method is not necesarily `optimally scalable'.
To see this let's consider a networking scenario where the bandwidth
consumption of the genie-approach is O(N^1.5) where N is the
network size. Let's see two cases.

Case 1. There exist an optmally scalable protocol Opt that induces an extra
bandwidth  consumption (total overhead) that is O(N^1.25). There is also
a protocol P  whose total overhead is O(N^1.4).
Both protocols (Opt and P) are sufffient scalable, since in both cases the
total bandwidth consumption is O(N^1.5)

For Opt:  Bandwidth consumption = O(N^1.5) + O(N^1.25) = O(N^1.5)
For P:      Bandwidth consumption = O(N^1.5) + O(N^1.4) = O(N^1.5)

So, P is NOT optimally scalable but it is sufficent scalable. Note that for very
large netwroks it may make sense to prefer P over Opt in some implementations
if P is simpler to implement.

Case 2. The optimally scalable routing protocol Opt for this networking scenario
induce - for argument sake -- an extra  bandwidth consumption (total overhead)
that is O(N^2). Protocol Opt is NOT suffient scalable since

For Opt:  Bandwidth consumption = O(N^1.5) + O(N^2) = O(N^2)

Protocol Opt bandwidth consumption O(N^2) increases faster than the genie
approach O(N^1.5).

Note that for a protocol be deemed `sufficient scalable' in this case 2, the protocol's
total overhead consumption should be O(N^1.5) or less. Thus, there is no `sufficient
scalable' protocol in this scenario.



> The reason it might not have looked this way in Cesar's original example
> (using total overhead) is because total overhead is not an appropriate
> choice for a metric, since it is actually the *difference* between the
> total bandwidth consumption and the genie bandwidth consumption.
> "Total bandwidth consumption" would be the appropriate metric in this case,
> although I am not sure it should be one of the primary metrics that define
> "absolute scalability" (and possibly "maximal scalability").

Yeah.  When defining `absolute scalability' you want to use a routing metric such
as `extra bandwidth consumption'. We typically call that : `overhead'. Some people
refer to it as `control overhead', and we refer to `total overhead' since
we have to take into account extra transmissions due to route's sub-optimality.
So, when defining `absolute' or `maximal' scalability we refer to total overhead,
and when we talk about `sufficent' scalability we talk about `total bandwidth
consumption'. This may seem confusing but we actually refer to the same
quantity: bandwidth consumption. It may seem that we don't since we use a different
term (`overhead'), but we should keep in mind that overhead is not other thing that
`extra bandwidth consumption'.

The same can be said about delay, energy, and other metrics of interest.

Regards

Cesar


--
Cesar Santivanez, Ph.D.
Network Scientist
Internetwork Research
BBN Technologies (A verizon unit)




_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Fri Oct  3 09:16:28 2003
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 JAA05521
	for <ans-research-archive@odin.ietf.org>; Fri, 3 Oct 2003 09:16:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5Pms-00050T-Rz
	for ans-research-archive@odin.ietf.org; Fri, 03 Oct 2003 09:16:06 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h93DG2aF019239
	for ans-research-archive@odin.ietf.org; Fri, 3 Oct 2003 09:16:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5Pms-00050E-NN
	for ans-research-web-archive@optimus.ietf.org; Fri, 03 Oct 2003 09:16:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05513
	for <ans-research-web-archive@ietf.org>; Fri, 3 Oct 2003 09:15:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Pmr-0000Y2-00
	for ans-research-web-archive@ietf.org; Fri, 03 Oct 2003 09:16:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Pmq-0000Xy-00
	for ans-research-web-archive@ietf.org; Fri, 03 Oct 2003 09:16:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5Pmq-0004zS-Q5; Fri, 03 Oct 2003 09:16:00 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5PmY-0004yb-5U
	for ans-research@www1.ietf.org; Fri, 03 Oct 2003 09:15:42 -0400
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <4D6J4YKC>; Fri, 3 Oct 2003 09:15:03 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A0255378E@ftmail.lab.flarion.com>
From: Corson Scott <Corson@flarion.com>
To: "'ans-research@www1.ietf.org'" <ans-research@www1.ietf.org>
Date: Fri, 3 Oct 2003 09:13:48 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Subject: [Ans-research] Slides/Minutes Posted
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>

The Slides and Minutes from the most recent ANS meeting can be found on the web at...

http://www.flarion.com/ans-research/Mobicom2003/Materials.htm

_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Fri Oct  3 10:10:26 2003
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 KAA08299
	for <ans-research-archive@odin.ietf.org>; Fri, 3 Oct 2003 10:10:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5QdA-0007d3-KW
	for ans-research-archive@odin.ietf.org; Fri, 03 Oct 2003 10:10:05 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h93EA4M0029319
	for ans-research-archive@odin.ietf.org; Fri, 3 Oct 2003 10:10:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5QdA-0007co-G2
	for ans-research-web-archive@optimus.ietf.org; Fri, 03 Oct 2003 10:10:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA08265
	for <ans-research-web-archive@ietf.org>; Fri, 3 Oct 2003 10:09:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Qd7-0001Gb-00
	for ans-research-web-archive@ietf.org; Fri, 03 Oct 2003 10:10:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A5Qd7-0001GW-00
	for ans-research-web-archive@ietf.org; Fri, 03 Oct 2003 10:10:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5Qd8-0007bq-LC; Fri, 03 Oct 2003 10:10:02 -0400
Received: from harrier.mail.pas.earthlink.net ([207.217.120.12])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A5QcI-0007aV-9u
	for ans-research@www1.ietf.org; Fri, 03 Oct 2003 10:09:10 -0400
Received: from sdn-ar-016casfrmp224.dialsprint.net ([158.252.220.226] helo=earthlink.net)
	by harrier.mail.pas.earthlink.net with esmtp (Exim 3.33 #1)
	id 1A5Qc3-0005Is-00; Fri, 03 Oct 2003 07:08:56 -0700
Message-ID: <3F7D82F5.1080903@earthlink.net>
Date: Fri, 03 Oct 2003 07:08:53 -0700
From: Richard Ogier <ogier@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 (emach0202)
X-Accept-Language: en-us
MIME-Version: 1.0
To: Cesar Santivanez <csantiva@bbn.com>
CC: Onur Arpacioglu <oa27@ece.cornell.edu>, ans-research@www1.ietf.org
Subject: Re: [Ans-research] Absolute, optimal, sufficient scalability?
References: <005301c386a7$8ced05b0$1f88fd80@Palio> <3F7C22F6.2010605@earthlink.net> <3F7C87EC.9E2BEA72@bbn.com>
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

<html>
<head>
</head>
<body>
Hi Cesar,<br>
<br>
Please see my comments below. <br>
<br>
Cesar Santivanez wrote:<br>
<blockquote type="cite" cite="mid:3F7C87EC.9E2BEA72@bbn.com">
  <pre wrap="">Hi Richard,<br><br>I agree with most of your coments.  BElow I am addressing the discrepancies.<br><br>Richard Ogier wrote:<br><br></pre>
  <blockquote type="cite">
    <pre wrap="">Onur, Cesar, and all:<br><br>I want to comment on "sufficient scalability".  The following paragraph<br>by Onur clarifies the term and helps to support the point I will make.<br><br></pre>
    <blockquote type="cite">
      <pre wrap="">I understand what you mean. It is actually equivalent to comparing two<br>methods w.r.t. a metric; Method 1: Actual routing protocol. Method 2:<br>Genie routing protocol. Metric: Total bandwidth consumption (including<br>traffic load). If the methods are EQUALLY scalable w.r.t. the metric<br>(see section 2.6. of the draft for the definition of EQUALLY scalable),<br>then your definition calls method 1 'sufficiently scalable'.<br></pre>
      </blockquote>
      <pre wrap="">It is possible that a genie method is "more scalable" than an<br>"optimally scalable" (real) method, but an "optimally scalable"<br>method cannot be "more scalable" than a genie method.<br>Therefore, a "sufficiently scalable" method is also "optimally<br>scalable", so the term "sufficiently scalable" is not needed.<br></pre>
      </blockquote>
      <pre wrap=""><!----><br>A sufficient scalable method is not necesarily `optimally scalable'.<br>To see this let's consider a networking scenario where the bandwidth<br>consumption of the genie-approach is O(N^1.5) where N is the<br>network size. Let's see two cases.</pre>
      </blockquote>
All your examples use "total overhead" as the metric. &nbsp;My whole point is
that this is not an<br>
appropriate metric, since it is actually the *difference* between the total
bandwidth<br>
consumption with an actual method and with a genie method. &nbsp;The appropriate
metric<br>
is "total bandwidth consumption". &nbsp; &nbsp;With this metric, a sufficiently scalable
method<br>
is always optimally scalable. &nbsp;<br>
      <blockquote type="cite" cite="mid:3F7C87EC.9E2BEA72@bbn.com">
        <pre wrap=""><br><br>Case 1. There exist an optmally scalable protocol Opt that induces an extra<br>bandwidth  consumption (total overhead) that is O(N^1.25). There is also<br>a protocol P  whose total overhead is O(N^1.4).<br>Both protocols (Opt and P) are sufffient scalable, since in both cases the<br>total bandwidth consumption is O(N^1.5)<br><br>For Opt:  Bandwidth consumption = O(N^1.5) + O(N^1.25) = O(N^1.5)<br>For P:      Bandwidth consumption = O(N^1.5) + O(N^1.4) = O(N^1.5)<br><br>So, P is NOT optimally scalable but it is sufficent scalable. Note that for very<br>large netwroks it may make sense to prefer P over Opt in some implementations<br>if P is simpler to implement.<br><br>Case 2. The optimally scalable routing protocol Opt for this networking scenario<br>induce - for argument sake -- an extra  bandwidth consumption (total overhead)<br>that is O(N^2). Protocol Opt is NOT suffient scalable since<br><br>For Opt:  Bandwidth consumption = O(N^1.5) + O(N^2)
 = O(N^2)<br><br>Protocol Opt bandwidth consumption O(N^2) increases faster than the genie<br>approach O(N^1.5).<br><br>Note that for a protocol be deemed `sufficient scalable' in this case 2, the protocol's<br>total overhead consumption should be O(N^1.5) or less. Thus, there is no `sufficient<br>scalable' protocol in this scenario.<br><br></pre>
        <blockquote type="cite">
          <pre wrap="">The reason it might not have looked this way in Cesar's original example<br>(using total overhead) is because total overhead is not an appropriate<br>choice for a metric, since it is actually the *difference* between the<br>total bandwidth consumption and the genie bandwidth consumption.<br>"Total bandwidth consumption" would be the appropriate metric in this case,<br>although I am not sure it should be one of the primary metrics that define<br>"absolute scalability" (and possibly "maximal scalability").<br></pre>
          </blockquote>
          <pre wrap=""><!----><br>Yeah.  When defining `absolute scalability' you want to use a routing metric such<br>as `extra bandwidth consumption'. We typically call that : `overhead'. Some people</pre>
          </blockquote>
I am not sure the phrase "you want to" is justified. &nbsp; Why do you want to
use "extra bandwidth consumption" <br>
instead of "total bandwidth consumption"&nbsp; for defining absolute scalability?
&nbsp;<br>
I can see that the metric "total overhead" is useful and have read your paper
on it, but I don't think<br>
it is an appropriate metric for defining scalability, since it is a "difference
metric" (as I explained above). <br>
For defining absolute or maximal scalability, we need to carefully select
a few appropriate metrics, <br>
called "primary metrics" &nbsp;in the scalability draft. &nbsp; The draft specifies
a preliminary set of primary metrics, <br>
which does not include "total overhead". <br>
          <blockquote type="cite" cite="mid:3F7C87EC.9E2BEA72@bbn.com">
            <pre wrap=""><br>refer to it as `control overhead', and we refer to `total overhead' since<br>we have to take into account extra transmissions due to route's sub-optimality.<br>So, when defining `absolute' or `maximal' scalability we refer to total overhead,<br>and when we talk about `sufficent' scalability we talk about `total bandwidth<br>consumption'. This may seem confusing but we actually refer to the same<br>quantity: bandwidth consumption. It may seem that we don't since we use a different<br>term (`overhead'), but we should keep in mind that overhead is not other thing that<br>`extra bandwidth consumption'.</pre>
            </blockquote>
This is exactly my point (and I was not confused by it). &nbsp;In my opinion,
"total bandwidth consumption" <br>
is an appropriate metric for defining scalability (whether absolute or optimal
or maximal or sufficient).<br>
"Total overhead" is a useful metric, but I don't think it is appropriate
for defining scalability. &nbsp;<br>
If the metric "total bandwidth consumption" is used, then "sufficient scalability"<br>
is the same as "optimal scalability", which keeps things simple.<br>
            <br>
It looks like we could use another opinion. &nbsp;Onur?<br>
            <br>
Regards,<br>
Richard<br>
            <br>
            <blockquote type="cite" cite="mid:3F7C87EC.9E2BEA72@bbn.com">
              <pre wrap=""><br><br>The same can be said about delay, energy, and other metrics of interest.<br><br>Regards<br><br>Cesar<br><br><br>--<br>Cesar Santivanez, Ph.D.<br>Network Scientist<br>Internetwork Research<br>BBN Technologies (A verizon unit)<br><br><br><br><br></pre>
              </blockquote>
              <br>
              </body>
              </html>


_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Wed Oct  8 12:56:23 2003
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 MAA27346
	for <ans-research-archive@odin.ietf.org>; Wed, 8 Oct 2003 12:56:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7HbX-0002Re-2P
	for ans-research-archive@odin.ietf.org; Wed, 08 Oct 2003 12:56:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h98Gu3Om009394
	for ans-research-archive@odin.ietf.org; Wed, 8 Oct 2003 12:56:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7HbW-0002RR-TR
	for ans-research-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 12:56:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27315
	for <ans-research-web-archive@ietf.org>; Wed, 8 Oct 2003 12:55:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7HbU-00017x-00
	for ans-research-web-archive@ietf.org; Wed, 08 Oct 2003 12:56:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7HbU-00017t-00
	for ans-research-web-archive@ietf.org; Wed, 08 Oct 2003 12:56:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7HbV-0002RH-5p; Wed, 08 Oct 2003 12:56:01 -0400
Received: from fmr05.intel.com ([134.134.136.6] helo=hermes.jf.intel.com)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7Hac-0002LT-TU
	for ans-research@www1.ietf.org; Wed, 08 Oct 2003 12:55:09 -0400
Received: from petasus.jf.intel.com (petasus.jf.intel.com [10.7.209.6])
	by hermes.jf.intel.com (8.12.9-20030918-01/8.12.9/d: outer.mc,v 1.66 2003/05/22 21:17:36 rfjohns1 Exp $) with ESMTP id h98GsThH026726
	for <ans-research@www1.ietf.org>; Wed, 8 Oct 2003 16:54:29 GMT
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206])
	by petasus.jf.intel.com (8.11.6-20030918-01/8.11.6/d: inner.mc,v 1.35 2003/05/22 21:18:01 rfjohns1 Exp $) with SMTP id h98GmSV02952
	for <ans-research@www1.ietf.org>; Wed, 8 Oct 2003 16:48:28 GMT
Received: from orsmsx331.amr.corp.intel.com ([192.168.65.56])
 by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2003100809535919566
 ; Wed, 08 Oct 2003 09:53:59 -0700
Received: from orsmsx410.amr.corp.intel.com ([192.168.65.64]) by orsmsx331.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 8 Oct 2003 09:53:59 -0700
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Subject: RE: [Ans-research] Slides/Minutes Posted
Date: Wed, 8 Oct 2003 09:53:57 -0700
Message-ID: <26BDFAFFB541B047B24179002EBE6D2714FFCE@orsmsx410.jf.intel.com>
Thread-Topic: [Ans-research] Slides/Minutes Posted
Thread-Index: AcOJsICPsMezKx+iTP+g9MN402TIsAEDCtZg
From: "Yang, Lily L" <lily.l.yang@intel.com>
To: "Corson Scott" <Corson@flarion.com>, <ans-research@www1.ietf.org>
X-OriginalArrivalTime: 08 Oct 2003 16:53:59.0320 (UTC) FILETIME=[C4E4C180:01C38DBC]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Scott- When are we going to meet at Mineapolis?=20

Lily

> -----Original Message-----
> From: ans-research-admin@ietf.org=20
> [mailto:ans-research-admin@ietf.org]On
> Behalf Of Corson Scott
> Sent: Friday, October 03, 2003 6:14 AM
> To: 'ans-research@www1.ietf.org'
> Subject: [Ans-research] Slides/Minutes Posted
>=20
>=20
> The Slides and Minutes from the most recent ANS meeting can=20
> be found on the web at...
>=20
> http://www.flarion.com/ans-research/Mobicom2003/Materials.htm
>=20
> _______________________________________________
> Ans-research mailing list
> Ans-research@ietf.org
> https://www1.ietf.org/mailman/listinfo/ans-research
>=20

_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Wed Oct  8 17:41:23 2003
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 RAA10635
	for <ans-research-archive@odin.ietf.org>; Wed, 8 Oct 2003 17:41:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7M3L-0004MN-8H
	for ans-research-archive@odin.ietf.org; Wed, 08 Oct 2003 17:41:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h98Lf3mn016749
	for ans-research-archive@odin.ietf.org; Wed, 8 Oct 2003 17:41:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7M3K-0004M3-Uf
	for ans-research-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 17:41:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10619
	for <ans-research-web-archive@ietf.org>; Wed, 8 Oct 2003 17:40:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7M3I-0004qw-00
	for ans-research-web-archive@ietf.org; Wed, 08 Oct 2003 17:41:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7M3H-0004qt-00
	for ans-research-web-archive@ietf.org; Wed, 08 Oct 2003 17:40:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7M3J-0004Lf-8i; Wed, 08 Oct 2003 17:41:01 -0400
Received: from mail.flarion.com ([63.103.94.23] helo=ftmail.lab.flarion.com)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7M2V-0004Jg-PN
	for ans-research@www1.ietf.org; Wed, 08 Oct 2003 17:40:11 -0400
Received: by ftmail.lab.flarion.com with Internet Mail Service (5.5.2656.59)
	id <4D6JVG90>; Wed, 8 Oct 2003 17:39:35 -0400
Message-ID: <748C6D0A58C0F94CA63C198B6674697A02553C41@ftmail.lab.flarion.com>
From: Corson Scott <Corson@flarion.com>
To: "'Yang, Lily L'" <lily.l.yang@intel.com>,
        "'ans-research@www1.ietf.org'" <ans-research@www1.ietf.org>
Subject: RE: [Ans-research] Slides/Minutes Posted
Date: Wed, 8 Oct 2003 17:39:29 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>

A request has been sent to the agenda folks.  I have not yet received a reply.  IETF mtgs generally have priority over IRTF mtgs, but I've not heard that we've been denied either.  Will keep the list informed.

-Scott

> -----Original Message-----
> From: Yang, Lily L [mailto:lily.l.yang@intel.com] 
> Sent: Wednesday, October 08, 2003 12:54 PM
> To: Corson Scott; ans-research@www1.ietf.org
> Subject: RE: [Ans-research] Slides/Minutes Posted
> 
> 
> Scott- When are we going to meet at Mineapolis? 
> 
> Lily
> 
> > -----Original Message-----
> > From: ans-research-admin@ietf.org 
> > [mailto:ans-research-admin@ietf.org]On
> > Behalf Of Corson Scott
> > Sent: Friday, October 03, 2003 6:14 AM
> > To: 'ans-research@www1.ietf.org'
> > Subject: [Ans-research] Slides/Minutes Posted
> > 
> > 
> > The Slides and Minutes from the most recent ANS meeting can 
> > be found on the web at...
> > 
> > http://www.flarion.com/ans-research/Mobicom2003/Materials.htm
> > 
> > _______________________________________________
> > Ans-research mailing list
> > Ans-research@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ans-research
> > 
> 

_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Wed Oct  8 19:44:22 2003
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 TAA15148
	for <ans-research-archive@odin.ietf.org>; Wed, 8 Oct 2003 19:44:22 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7NyM-00028V-7l
	for ans-research-archive@odin.ietf.org; Wed, 08 Oct 2003 19:44:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h98Ni2P1008205
	for ans-research-archive@odin.ietf.org; Wed, 8 Oct 2003 19:44:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7NyM-00028G-2U
	for ans-research-web-archive@optimus.ietf.org; Wed, 08 Oct 2003 19:44:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15135
	for <ans-research-web-archive@ietf.org>; Wed, 8 Oct 2003 19:43:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7NyJ-00060L-00
	for ans-research-web-archive@ietf.org; Wed, 08 Oct 2003 19:44:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A7NyJ-00060I-00
	for ans-research-web-archive@ietf.org; Wed, 08 Oct 2003 19:43:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7NyK-00027b-Tb; Wed, 08 Oct 2003 19:44:00 -0400
Received: from gehenna.ece.cornell.edu ([128.84.95.235])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A7NxW-00027E-My
	for ans-research@www1.ietf.org; Wed, 08 Oct 2003 19:43:10 -0400
Received: from verdi (verdi.ece.cornell.edu [128.84.210.27])
	by gehenna.ece.cornell.edu (Postfix) with ESMTP
	id 236CC1E8005; Wed,  8 Oct 2003 19:43:10 -0400 (EDT)
Date: Wed, 8 Oct 2003 19:41:37 -0400 (EDT)
From: "haas@ece.cornell.edu" <haas@ece.cornell.edu>
To: "'ans-research@www1.ietf.org'" <ans-research@www1.ietf.org>
Cc: Onur Arpacioglu <oa27@cornell.edu>, Tara Small <tsmall@cam.cornell.edu>,
        Zygmunt Haas <haas@ece.cornell.edu>
In-Reply-To: <748C6D0A58C0F94CA63C198B6674697A02553C41@ftmail.lab.flarion.com>
Message-ID: <Pine.GSO.4.05.10310081844010.168-100000@verdi.ece.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ans-research] Recent discussions
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>

Dear All,

There were some interesting discussions here recently regarding the
scalability draft.

We will summarize some of these discussions and bring a recommendation to
the group to see whether we can achieve some sense of consensus.

The goal would be to update the draft before the next meeting, so that it
reflects the discussions here.

We hope to be able to post the above summary early next week.

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
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-


_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Mon Oct 20 01:00:26 2003
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 BAA00258
	for <ans-research-archive@odin.ietf.org>; Mon, 20 Oct 2003 01:00:26 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABS9E-0003ad-3w
	for ans-research-archive@odin.ietf.org; Mon, 20 Oct 2003 01:00:04 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9K503m6013758
	for ans-research-archive@odin.ietf.org; Mon, 20 Oct 2003 01:00:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABS9D-0003ZO-99
	for ans-research-web-archive@optimus.ietf.org; Mon, 20 Oct 2003 01:00:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00215
	for <ans-research-web-archive@ietf.org>; Mon, 20 Oct 2003 00:59:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABS9A-0003xy-00
	for ans-research-web-archive@ietf.org; Mon, 20 Oct 2003 01:00:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABS99-0003xu-00
	for ans-research-web-archive@ietf.org; Mon, 20 Oct 2003 00:59:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABS9B-0003YQ-H9; Mon, 20 Oct 2003 01:00:01 -0400
Received: from fmr06.intel.com ([134.134.136.7] helo=caduceus.jf.intel.com)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABS8C-00032O-6P
	for ans-research@www1.ietf.org; Mon, 20 Oct 2003 00:59:00 -0400
Received: from talaria.jf.intel.com (talaria.jf.intel.com [10.7.209.7])
	by caduceus.jf.intel.com (8.12.9-20030918-01/8.12.9/d: outer.mc,v 1.66 2003/05/22 21:17:36 rfjohns1 Exp $) with ESMTP id h9K4wDGu029526
	for <ans-research@www1.ietf.org>; Mon, 20 Oct 2003 04:58:13 GMT
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206])
	by talaria.jf.intel.com (8.11.6-20030918-01/8.11.6/d: inner.mc,v 1.35 2003/05/22 21:18:01 rfjohns1 Exp $) with SMTP id h9K4F1K15122
	for <ans-research@www1.ietf.org>; Mon, 20 Oct 2003 04:15:02 GMT
Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60])
 by orsmsxvs040.jf.intel.com (NAVGW 2.5.2.11) with SMTP id M2003101921582718551
 for <ans-research@www1.ietf.org>; Sun, 19 Oct 2003 21:58:27 -0700
Received: from orsmsx410.amr.corp.intel.com ([192.168.65.64]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Sun, 19 Oct 2003 21:58:27 -0700
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C396C6.CC0EECCA"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Sun, 19 Oct 2003 21:58:26 -0700
Message-ID: <26BDFAFFB541B047B24179002EBE6D2715005B@orsmsx410.jf.intel.com>
Thread-Topic: a draft describing some common Ad Hoc Network Usage Scenarios
Thread-Index: AcOWxssyDagFo+/ARSmLVZiMTcsQ1w==
From: "Yang, Lily L" <lily.l.yang@intel.com>
To: <ans-research@www1.ietf.org>
X-OriginalArrivalTime: 20 Oct 2003 04:58:27.0086 (UTC) FILETIME=[CC3EBAE0:01C396C6]
X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang)
Subject: [Ans-research] a draft describing some common Ad Hoc Network Usage Scenarios
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>

This is a multi-part message in MIME format.

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

Hi,=20

=20

Per our discussion at the MobiCom IRTF ANS meeting, it was considered
useful to define a set of common network usage scenarios to facilitate
this group's effort in studying and evaluating a given method's
scalability in the context of ANS charter. So a group of colleagues here
at Intel including myself submitted a draft defining a small subset of
the scenarios. Here is the draft:
http://www.ietf.org/internet-drafts/draft-irtf-yang-ans-scenarios-00.txt

=20

The scenario list is by no means complete and the description is
admittedly rough due to the publish time constraint before the
Minneapolis meeting. Nevertheless we believe it can be used as a
starting point for the group.  So your comments are most welcome. If
anybody would like to volunteer to describe other usage scenarios and
add to the list, it would also be most welcome. =20

=20

Thank you,

=20

Lily

=20


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

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"\@SimSun";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Hi, </span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Per our discussion at the =
MobiCom
IRTF ANS meeting, it was considered useful to define a set of common =
network
usage scenarios to facilitate this group's effort in studying and =
evaluating a
given method's scalability in the context of ANS charter. So a group of
colleagues here at Intel including myself submitted a draft defining a =
small
subset of the scenarios. Here is the draft: <a
href=3D"http://www.ietf.org/internet-drafts/draft-irtf-yang-ans-scenarios=
-00.txt">http://www.ietf.org/internet-drafts/draft-irtf-yang-ans-scenario=
s-00.txt</a></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>The scenario list is by no =
means
complete and the description is admittedly rough due to the publish time
constraint before the </span></font><font size=3D2 face=3DArial><span
  =
style=3D'font-size:10.0pt;font-family:Arial'>Minneapolis</span></font><fo=
nt
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> meeting. Nevertheless
we believe it can be used as a starting point for the group.&nbsp; So =
your comments
are most welcome. If anybody would like to volunteer to describe other =
usage
scenarios and add to the list, it would also be most welcome.&nbsp; =
</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Thank =
you,</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Lily</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>
=00
------_=_NextPart_001_01C396C6.CC0EECCA--

_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Mon Oct 20 08:23:24 2003
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 IAA23277
	for <ans-research-archive@odin.ietf.org>; Mon, 20 Oct 2003 08:23:24 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABZ3u-0008BW-Iu
	for ans-research-archive@odin.ietf.org; Mon, 20 Oct 2003 08:23:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KCN2MA031459
	for ans-research-archive@odin.ietf.org; Mon, 20 Oct 2003 08:23:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABZ3u-0008B7-8T
	for ans-research-web-archive@optimus.ietf.org; Mon, 20 Oct 2003 08:23:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23238
	for <ans-research-web-archive@ietf.org>; Mon, 20 Oct 2003 08:22:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABZ3s-0007R5-00
	for ans-research-web-archive@ietf.org; Mon, 20 Oct 2003 08:23:01 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABZ3s-0007R0-00
	for ans-research-web-archive@ietf.org; Mon, 20 Oct 2003 08:23:00 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABZ3s-0008A3-Lm; Mon, 20 Oct 2003 08:23:00 -0400
Received: from gehenna.ece.cornell.edu ([128.84.95.235])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABZ3d-000835-5V
	for ans-research@www1.ietf.org; Mon, 20 Oct 2003 08:22:45 -0400
Received: from verdi (verdi.ece.cornell.edu [128.84.210.27])
	by gehenna.ece.cornell.edu (Postfix) with ESMTP id 422261E8005
	for <ans-research@www1.ietf.org>; Mon, 20 Oct 2003 08:22:44 -0400 (EDT)
Date: Mon, 20 Oct 2003 08:21:09 -0400 (EDT)
From: "haas@ece.cornell.edu" <haas@ece.cornell.edu>
To: "'ans-research@www1.ietf.org'" <ans-research@www1.ietf.org>
Message-ID: <Pine.GSO.4.05.10310200818310.5860-100000@verdi.ece.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ans-research] Recent discussions on the Notes on Scalability draft
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>

Dear All,

Please see appended below a summary of recent discussions on the
Notes on Scalability draft and some suggested changes to the draft.

As always, comments are welcome.

We will modify the draft and submit shortly.

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
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

==========================================================================
Summary of comments and proposed changes to the Notes on Scalability draft
==========================================================================
Thank you to everyone who submitted comments on the scalability draft. We summarize them 
and provide our comments on them below.

We've discussed the fact that 'absolute scalability' discussed in the draft may not be 
possible in a given environment, and in such a situation, one may be more interested in 
the best achievable scaling properties w.r.t. a given (environment, independent parameter, 
primary metric(s)). In the revised version of the draft, we intend to classify methods 
that have this property under the suggested 'optimal scalability' definition. It will be 
defined as follows:

	A method is termed optimally scalable w.r.t. a given (environment, independent 
	parameter, primary metric(s)) triple, if it is more scalable than any other method 
	with respect to the same triple.

We agree that the definition could provide more insight for the development of new methods 
or protocols, since this knowledge can help us not to waste time and effort to search for 
methods that are better than the optimal.

We also want to emphasize that all of the definitions, including optimal scalability, 
requires the precise statement of the (environment, independent parameter, primary metric(s)) 
triple, since different selections of the components of this triple can lead to different 
conclusions. For example, a routing protocol can be optimally scalable w.r.t. the bandwidth 
consumption metric, but it may not be optimally scalable w.r.t. to another metric such as 
memory consumption.

The term 'maximal scalability' has also been suggested; it was suggested that a method is 
termed 'maximally scalable' if there does not exist another method that is 'more scalable' 
w.r.t. at least one primary metric, without being less scalable w.r.t. another metric. 
However, it was noted that with this definition, many maximally scalable methods that have 
different scaling properties (in terms of the metrics) can exist at the same time. Therefore, 
we feel that the information this definition provides may not be very useful.

The term 'sufficiently scalable' (w.r.t. a certain triple), which requires defining a "genie"
method, has also been suggested. It was suggested that a method is termed 'sufficiently 
scalable' w.r.t. an (environment, independent parameter, primary metric) triple(s), if the 
method is not less scalable than a genie method w.r.t. the same triple. An equivalent 
definition in terms of 'equal scalability' definition present in the draft was also noted. 
It was also suggested that a sufficiently scalable method is not necesarily 'optimally 
scalable' through the following example:

	  >Consider a networking scenario where the bandwidth consumption of
	  >the genie-approach is O(N^1.5) where N is the network size.
	  >Suppose there exist an optmally scalable
	  >protocol Opt that induces an extra bandwidth  consumption (total
	  >overhead) that is O(N^1.25). There is also a protocol P whose total
	  >overhead is O(N^1.4). Both protocols (Opt and P) are suffiently
	  >scalable, since in both cases the total bandwidth consumption is O(N^1.5)
	  >For Opt:  Bandwidth consumption = O(N^1.5) + O(N^1.25) = O(N^1.5)
	  >For P:    Bandwidth consumption = O(N^1.5) + O(N^1.4)  = O(N^1.5)
	  >So, P is NOT optimally scalable but it is sufficently scalable.
	  
However, we think that 'sufficient scalability' implies 'optimal scalability' if they are both 
defined w.r.t. the same metric. The reason this does not appear so in the above example is that 
there are two different metrics above. One is the bandwidth consumption(m1), and the other is 
the overhead(m2). Both Opt and P are *sufficiently scalable w.r.t. m1*, and they must also be 
optimally scalable w.r.t. m1, since, w.r.t. m1, they perform in the best way they can; that is,
as good as the genie method.  On the other hand, P is not optimally scalable w.r.t. m2, since 
Opt is more scalable than P w.r.t. m2. It is obviously possible that a method can be sufficiently 
scalable w.r.t. a metric, but not optimally scalable w.r.t. another metric. However, for a given 
metric, sufficient scalability w.r.t. the metric implies optimal scalability w.r.t. the metric, 
since no method can be more scalable than the genie method w.r.t the metric. So, sufficient 
scalability is just a degree of optimal scalability, where the optimally scalable method is 
equally scalable with the genie method that is associated with the metric.

We feel that, at this stage, there are not well enough established rules to determine the genie 
method for any possible metric. Since this can cause different interpretations of the genie method 
and lead to opposing views on the sufficient scalability of a method, we prefer not to introduce 
the new term 'sufficient scalability' into the draft at this stage.

As suggested by William Su, we will also add "Amount of available spectrum" to the environmental 
parameters of the draft.  Another suggestion regarding network lifetime was adding the condition 
that the network dies when it becomes fragmented. We found that this condition is already present 
in the draft, since it corresponds to the dying of the network when the the maximum number of 
possible connections decreases below N(N-1), i.e., the fraction of possible connections gets below 
the threshold 100%.
==============================================================================================



_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Mon Oct 20 14:15:23 2003
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 OAA06340
	for <ans-research-archive@odin.ietf.org>; Mon, 20 Oct 2003 14:15:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABeYY-0007Il-Ky
	for ans-research-archive@odin.ietf.org; Mon, 20 Oct 2003 14:15:03 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KIF2gW028061
	for ans-research-archive@odin.ietf.org; Mon, 20 Oct 2003 14:15:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABeYY-0007ID-By
	for ans-research-web-archive@optimus.ietf.org; Mon, 20 Oct 2003 14:15:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06336
	for <ans-research-web-archive@ietf.org>; Mon, 20 Oct 2003 14:14:52 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABeYV-00032x-00
	for ans-research-web-archive@ietf.org; Mon, 20 Oct 2003 14:14:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABeYV-00032u-00
	for ans-research-web-archive@ietf.org; Mon, 20 Oct 2003 14:14:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABeYX-0007Hq-B4; Mon, 20 Oct 2003 14:15:01 -0400
Received: from gehenna.ece.cornell.edu ([128.84.95.235])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABeXw-00076I-4x
	for ans-research@www1.ietf.org; Mon, 20 Oct 2003 14:14:24 -0400
Received: from verdi (verdi.ece.cornell.edu [128.84.210.27])
	by gehenna.ece.cornell.edu (Postfix) with ESMTP
	id 4E9821E8002; Mon, 20 Oct 2003 14:14:22 -0400 (EDT)
Date: Mon, 20 Oct 2003 14:12:47 -0400 (EDT)
From: "haas@ece.cornell.edu" <haas@ece.cornell.edu>
To: "'ans-research@www1.ietf.org'" <ans-research@www1.ietf.org>
Cc: Onur Arpacioglu <oa27@cornell.edu>, Tara Small <tsmall@cam.cornell.edu>,
        Zygmunt Haas <haas@ece.cornell.edu>
Message-ID: <Pine.GSO.4.05.10310201410220.7258-100000@verdi.ece.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ans-research] An updated draft on "Notes on Scalability"
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>

Hi Everyone,

The new updated draft on "Notes on Scalability of Wireless Ad Hoc
Networks," <draft-irtf-ans-scalability-notes-00.txt>, is now available
at:

http://wnl.ece.cornell.edu/Publications/draft-irtf-ans-scalability-definition-01.txt

Best,

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
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-




_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Mon Oct 20 14:16:23 2003
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 OAA06374
	for <ans-research-archive@odin.ietf.org>; Mon, 20 Oct 2003 14:16:23 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABeZW-0007gu-Vq
	for ans-research-archive@odin.ietf.org; Mon, 20 Oct 2003 14:16:02 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9KIG2Dh029558
	for ans-research-archive@odin.ietf.org; Mon, 20 Oct 2003 14:16:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABeZW-0007gf-Qp
	for ans-research-web-archive@optimus.ietf.org; Mon, 20 Oct 2003 14:16:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA06359
	for <ans-research-web-archive@ietf.org>; Mon, 20 Oct 2003 14:15:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABeZU-00033K-00
	for ans-research-web-archive@ietf.org; Mon, 20 Oct 2003 14:16:00 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ABeZT-00033H-00
	for ans-research-web-archive@ietf.org; Mon, 20 Oct 2003 14:15:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABeZV-0007eA-RW; Mon, 20 Oct 2003 14:16:01 -0400
Received: from gehenna.ece.cornell.edu ([128.84.95.235])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ABeZD-0007Ui-Lv
	for ans-research@www1.ietf.org; Mon, 20 Oct 2003 14:15:43 -0400
Received: from verdi (verdi.ece.cornell.edu [128.84.210.27])
	by gehenna.ece.cornell.edu (Postfix) with ESMTP
	id CB5031E8002; Mon, 20 Oct 2003 14:15:41 -0400 (EDT)
Date: Mon, 20 Oct 2003 14:14:07 -0400 (EDT)
From: "haas@ece.cornell.edu" <haas@ece.cornell.edu>
To: "'ans-research@www1.ietf.org'" <ans-research@www1.ietf.org>
Cc: Onur Arpacioglu <oa27@cornell.edu>, Tara Small <tsmall@cam.cornell.edu>,
        Zygmunt Haas <haas@ece.cornell.edu>
Message-ID: <Pine.GSO.4.05.10310201413160.7258-100000@verdi.ece.cornell.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Ans-research] An updated draft on "Notes on Scalability" (corrected)
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>

Hi Everyone,

The new updated draft on "Notes on Scalability of Wireless Ad Hoc
Networks," <draft-irtf-ans-scalability-notes-01.txt>, is now available
at:

http://wnl.ece.cornell.edu/Publications/draft-irtf-ans-scalability-definition-01.txt

Best,

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
~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-





_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Wed Oct 29 14:00:24 2003
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 OAA27282
	for <ans-research-archive@odin.ietf.org>; Wed, 29 Oct 2003 14:00:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEvY3-0006Lb-T6
	for ans-research-archive@odin.ietf.org; Wed, 29 Oct 2003 14:00:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9TJ034i024379
	for ans-research-archive@odin.ietf.org; Wed, 29 Oct 2003 14:00:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEvY1-0006Kj-7s
	for ans-research-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 14:00:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27022
	for <ans-research-web-archive@ietf.org>; Wed, 29 Oct 2003 13:59:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEvXy-0000Kp-00
	for ans-research-web-archive@ietf.org; Wed, 29 Oct 2003 13:59:58 -0500
Received: from sausage.foretec.com ([4.17.168.5] helo=manatick)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEvTm-0000BX-03
	for ans-research-web-archive@ietf.org; Wed, 29 Oct 2003 13:55:39 -0500
Received: from [132.151.6.22] (helo=optimus.ietf.org)
	by manatick with esmtp (Exim 4.24)
	id 1AEvMQ-0007Fs-3E
	for ans-research-web-archive@ietf.org; Wed, 29 Oct 2003 13:48:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEvMP-0005V1-F3; Wed, 29 Oct 2003 13:48:01 -0500
Received: from letters.cs.ucsb.edu ([128.111.41.13])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEvLe-0005RJ-B4
	for ans-research@www1.ietf.org; Wed, 29 Oct 2003 13:47:14 -0500
Received: from yosemite.cs.ucsb.edu (yosemite [128.111.40.103])
	by letters.cs.ucsb.edu (8.11.7+Sun/8.11.7) with ESMTP id h9TIl9211169;
	Wed, 29 Oct 2003 10:47:09 -0800 (PST)
From: Elizabeth Belding-Royer <ebelding@cs.ucsb.edu>
To: ans-research@www1.ietf.org
Cc: corson@flarion.com, ebelding@cs.ucsb.edu
Content-Type: text/plain
Message-Id: <1067453230.32664.49.camel@yosemite.cs.ucsb.edu>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) 
Date: 29 Oct 2003 10:47:11 -0800
Content-Transfer-Encoding: 7bit
Subject: [Ans-research] ANS meeting announcement
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi,

The next ANS meeting is scheduled for Wednesday, November 12th,
at 3:30pm.  This meeting will be held in Minneapolis, MN,
together with the IETF meeting.  See
http://www.ietf.org/meetings/agenda_58.html for the full
IETF agenda.

We are soliciting presentations for this meeting.  There
are now three Internet Drafts that have been submitted
to the group.  We will discuss each of these documents,
along with any other recent research results on scalable
ad hoc networks.

If you would like to give a presentation, please send a
paragraph describing your talk and the anticipated talk
length to Scott (corson@flarion.com) and myself (ebelding@cs.ucsb.edu).

Hope to see you all there,
Elizabeth


_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



From exim@www1.ietf.org  Wed Oct 29 14:59:21 2003
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 OAA01742
	for <ans-research-archive@odin.ietf.org>; Wed, 29 Oct 2003 14:59:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEwT8-0004eq-Hl
	for ans-research-archive@odin.ietf.org; Wed, 29 Oct 2003 14:59:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9TJx2pI017900
	for ans-research-archive@odin.ietf.org; Wed, 29 Oct 2003 14:59:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEwT8-0004ed-ED
	for ans-research-web-archive@optimus.ietf.org; Wed, 29 Oct 2003 14:59:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01729
	for <ans-research-web-archive@ietf.org>; Wed, 29 Oct 2003 14:58:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEwT5-0001y0-00
	for ans-research-web-archive@ietf.org; Wed, 29 Oct 2003 14:58:59 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AEwT5-0001xx-00
	for ans-research-web-archive@ietf.org; Wed, 29 Oct 2003 14:58:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEwT7-0004d0-6N; Wed, 29 Oct 2003 14:59:01 -0500
Received: from letters.cs.ucsb.edu ([128.111.41.13])
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AEwSZ-0004X0-9z
	for ans-research@www1.ietf.org; Wed, 29 Oct 2003 14:58:27 -0500
Received: from yosemite.cs.ucsb.edu (yosemite [128.111.40.103])
	by letters.cs.ucsb.edu (8.11.7+Sun/8.11.7) with ESMTP id h9TJwM218902
	for <ans-research@www1.ietf.org>; Wed, 29 Oct 2003 11:58:22 -0800 (PST)
From: Elizabeth Belding-Royer <ebelding@cs.ucsb.edu>
To: ans-research@www1.ietf.org
Content-Type: text/plain
Message-Id: <1067457505.32664.68.camel@yosemite.cs.ucsb.edu>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) 
Date: 29 Oct 2003 11:58:25 -0800
Content-Transfer-Encoding: 7bit
Subject: [Ans-research] Mobihoc 2004 CFP!
Sender: ans-research-admin@ietf.org
Errors-To: ans-research-admin@ietf.org
X-BeenThere: ans-research@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=unsubscribe>
List-Id: Ad hoc Network Scaling Research <ans-research.ietf.org>
List-Post: <mailto:ans-research@ietf.org>
List-Help: <mailto:ans-research-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ans-research>,
	<mailto:ans-research-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

======================================================================

CALL FOR PAPERS

The Fifth ACM International Symposium on Mobile Ad Hoc
Networking and Computing 
MobiHoc 2004
www.sigmobile.org/mobihoc/2004/

May 24-26, 2004
Tokyo, Japan

MobiHoc 2004 is the fifth 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 at Long Beach, 
California, in 2002 at Lausanne, Switzerland, in 2003 at Annapolis,
Maryland, and now in 2004 at Tokyo, Japan.

PAPERS:

Technical papers describing original, previously unpublished research,
not currently under review by another conference or journal, are
solicited. In general this symposium is interested in papers that
address networking or computing problems in the context of mobile and
wireless ad hoc networks, ad hoc computing systems, and sensor
networks, with the focus being on issues above the physical layer.
Specific topics of interest include the following:

* Routing protocols (unicast, multicast, geocast, content-based, etc.)
* Media access techniques
* Transport-layer issues
* Hardware and software platforms, systems, and testbeds
* Applications for ad hoc networks
* Power-aware, low-power, and energy-efficient designs
* Quality-of-service issues
* Security and fault tolerance issues
* Self-configuration in ad hoc networks
* Processing and fusion of data in sensor networks
* Location discovery and management
* Timing synchronization
* Distributed algorithms for ad hoc networks
* Biologically inspired mechanisms
* Ad hoc networks of autonomous intelligent systems
* Analytic methods and modeling for performance evaluation
* Cross-layer interactions, including between higher and physical layers
* Other ad hoc networking and computing topics above the physical layer

Please consult the program co-chairs Charlie Perkins
<charles.perkins@nokia.com> and Leandros Tassiulas <leandros@uth.gr> if
you are uncertain whether your paper falls within the scope of the
symposium.

SUBMISSION INSTRUCTIONS:

All submissions will be handled electronically and must be in PDF or
PostScript format. Papers must not exceed 15 pages (US "Letter" size,
8.5 x 11 inches) including text, figures and references. The font size
must be at least 10 points. Accepted papers will be published in the
symposium proceedings.

We will adopt a double-blind process for paper review, where the
identities of the authors are withheld from the reviewers. Authors'
names and their affiliations must not be revealed or mentioned anywhere
in the paper or in the PDF or PostScript file. Submitted papers should
describe original research, not published and not currently under review
for any other conference or journal. Papers not following these
guidelines will be summarily rejected.

To submit a paper, please refer to the paper submission link at the
conference website, www.sigmobile.org/mobihoc/2004/. Questions about the
submission process should be directed to the Program Co-Chairs.

TUTORIALS:

Proposals for tutorials are solicited. Evaluation of proposals will be
based on the expertise and experience of the instructors, and on the
relevance of the subject matter for the symposium. Potential
instructors are requested to submit a tutorial proposal of at most 5
pages, including a biographical sketch, to the Tutorial Chair,
Maria Papadopouli <maria@cs.unc.edu> by the paper submission deadline
below.


IMPORTANT DATES:

Paper Submission Deadline           December 11, 2004
Notification of Acceptance          March 10, 2004
Camera-ready version Due            March 25, 2004

Please visit the MobiHoc 2004 Home Page at
www.sigmobile.org/mobihoc/2004/,
or send email to the General Chair, Jun Murai
<jun-mobihoc2004@wide.ad.jp> or to <mobihoc2004@isrmail.isr.umd.edu> for
any questions or for more information about the symposium.




_______________________________________________
Ans-research mailing list
Ans-research@ietf.org
https://www1.ietf.org/mailman/listinfo/ans-research



